I tried to compile CWM to my Trend 2 SM-G313HN and after flashing the recovery image and booting to recovery mode, a red exclamation mark appeared to the top left corner of the boot screen and the boot process stopped there. At first I thought that the compilation failed, but then I tried to unpack the original recovery.img, edit the default.prop (changed ro.secure to 0) and it happened again. Any changes to the recovery ot boot image seemed to trigger that error. There is a picture in the attachments, sorry about the quality, took it with my old Galaxy Gio.
Atleast I managed to root the phone by manually adding superuser to the system.img and flashing it via Odin, but a recovery would be nice.
EDIT: I discovered that there is a small bootloader hidden in the stock boot/recovery images. Got CWM to boot. (but no graphics yet, but I can connect via ADB) I am working on to get the recovery working.
Can you tell me what procedure you do to compile CWM ?
Link to source code, specific device *.ini or *.xml, linux/gnu x64 system...etc.? I would also like to compile it for Galaxy Trend 2, since there are no any other rooting option for sm-g313hn without octopus box.
adeii said:
Can you tell me what procedure you do to compile CWM ?
Link to source code, specific device *.ini or *.xml, linux/gnu x64 system...etc.? I would also like to compile it for Galaxy Trend 2, since there are no any other rooting option for sm-g313hn without octopus box.
Click to expand...
Click to collapse
https://github.com/TheNikiz/android_device_samsung_vivaltonfc3g
Here is the device configuration. It seems like the bootloader checks if the boot/recovery image is unmodified before continuing, if not, it will show the red "!" in the top left corner of the screen. :/
Nikiz said:
https://github.com/TheNikiz/android_device_samsung_vivaltonfc3g
Here is the device configuration. It seems like the bootloader checks if the boot/recovery image is unmodified before continuing, if not, it will show the red "!" in the top left corner of the screen. :/
Click to expand...
Click to collapse
Thanks a lot, Nikiz. I'll try it.
Do you had use Odin 3.0x and device in download mode to flash it?
Had you tried to compile TWRP: Team-Win-Recovery-Project-Samsung ?
Use Dees_Troy's injecttwrp program to inject the recovery-ramdisk.img into the boot.img
Click to expand...
Click to collapse
adeii said:
Thanks a lot, Nikiz. I'll try it.
Do you had use Odin 3.0x and device in download mode to flash it?
Had you tried to compile TWRP: Team-Win-Recovery-Project-Samsung ?
Click to expand...
Click to collapse
Yes, I flashed it with Odin 3.10. I have not tried TWRP yet. But it seems that anythin other than the stock boot.img/recovery.img does not work. It seems like the bootloader checks if the image is stock Samsung before booting. I tried to edit the stock recovery a little, not changing the functionality any way, but it triggers the error.
EDIT: Well, I have the Cyanogenmod 11 source code downloaded and the system.img is not protected, I started to work on porting CM11 to this phone. Few hours (and beers) later, it booted! But it is not usable yet, it throws a "unfortunately android.phone has stopped working" error repeately and I cannot continue to test it further. There might be a library missing or something.
Nice! Keep the good work!
Flashed it again and this time I opened logcat and see what caused the phone app to crash. Made some changes to the source code, recompiling..
Code:
W/dalvikvm( 4576): Unable to resolve superclass of Lcom/android/phone/MSimIccProvider; (730)
W/dalvikvm( 4576): Link of class 'Lcom/android/phone/MSimIccProvider;' failed
D/AndroidRuntime( 4576): Shutting down VM
W/dalvikvm( 4576): threadid=1: thread exiting with uncaught exception (group=0x415a1ce0)
E/AndroidRuntime( 4576): FATAL EXCEPTION: main
E/AndroidRuntime( 4576): Process: com.android.phone, PID: 4576
E/AndroidRuntime( 4576): java.lang.RuntimeException: Unable to get provider com.android.phone.MSimIccProvider: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.MSimIccProvider" on path: DexPathList[[zip file "/system/priv-app/TeleService.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
E/AndroidRuntime( 4576): at android.app.ActivityThread.installProvider(ActivityThread.java:4922)
E/AndroidRuntime( 4576): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4514)
E/AndroidRuntime( 4576): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4454)
E/AndroidRuntime( 4576): at android.app.ActivityThread.access$1500(ActivityThread.java:144)
E/AndroidRuntime( 4576): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1265)
E/AndroidRuntime( 4576): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 4576): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 4576): at android.app.ActivityThread.main(ActivityThread.java:5146)
E/AndroidRuntime( 4576): at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime( 4576): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 4576): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 4576): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 4576): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 4576): Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.phone.MSimIccProvider" on path: DexPathList[[zip file "/system/priv-app/TeleService.apk"],nativeLibraryDirectories=[/vendor/lib, /system/lib]]
E/AndroidRuntime( 4576): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
E/AndroidRuntime( 4576): at java.lang.ClassLoader.loadClass(ClassLoader.java:497)
E/AndroidRuntime( 4576): at java.lang.ClassLoader.loadClass(ClassLoader.java:457)
E/AndroidRuntime( 4576): at android.app.ActivityThread.installProvider(ActivityThread.java:4907)
E/AndroidRuntime( 4576): ... 12 more
W/ActivityManager( 2003): Process com.android.phone has crashed too many times:killing!
I found out something! There is a small secondary bootloader hidden inside the recovery image. I noticed it when I compared the stock recovery to a repacked one. The repacked image did not have it. I tried manyally add it to the CWM build and.. The red exclamation point appeared.. But the screen went blank after that, so it did something! I will experiement with this a bit.
EDIT: Yup, fired up ADB while the screen was blank and got a shell. Now I need to get some graphics out of it.
Nikiz said:
I found out something! There is a small secondary bootloader hidden inside the recovery image. I noticed it when I compared the stock recovery to a repacked one. The repacked image did not have it. I tried manyally add it to the CWM build and.. The red exclamation point appeared.. But the screen went blank after that, so it did something! I will experiement with this a bit.
EDIT: Yup, fired up ADB while the screen was blank and got a shell. Now I need to get some graphics out of it.
Click to expand...
Click to collapse
I found these files in official firmware update here. And you are right, recovery.img have hidden stuff.
Got the recovery working! Well, sort of. I have to fix the mounts so it can be used.
EDIT: We now have a working recovery! Link: [RECOVERY][SM-G313HN] CWM-Based Recovery 6.0.5.1 for Trend 2
Congrats, Nikiz!
can you share root files with us, or procedure
Very good,thank you for your work.Successfully rooted with UPDATE-SuperSU-v2.40.zip after flashing your recovery.
Nikiz said:
I found out something! There is a small secondary bootloader hidden inside the recovery image. I noticed it when I compared the stock recovery to a repacked one. The repacked image did not have it. I tried manyally add it to the CWM build and.. The red exclamation point appeared.. But the screen went blank after that, so it did something! I will experiement with this a bit.
EDIT: Yup, fired up ADB while the screen was blank and got a shell. Now I need to get some graphics out of it.
Click to expand...
Click to collapse
Hello ! I'm also making a recovery for another samsung phone, and i noticed like you that little red exclamation. Could you explain what did you do to get it working please ? Thanks in advance !
Well,IMHO, this is only sign that phone detected that recovery (or just bootloader) is not original/stock and nothing more. On SM-G313HN, it appears only in recovery mode and everything works great.
About how to compile new recovery, I would also want to know all steps from Nikiz.
adeii said:
Well,IMHO, this is only sign that phone detected that recovery (or just bootloader) is not original/stock and nothing more. On SM-G313HN, it appears only in recovery mode and everything works great.
About how to compile new recovery, I would also want to know all steps from Nikiz.
Click to expand...
Click to collapse
I think you can follow this guide Porting ClockworkMod Recovery to a New Device. I've build cwm and twrp for my samsung device using this guide.
cleverior.ipul said:
I think you can follow this guide Porting ClockworkMod Recovery to a New Device. I've build cwm and twrp for my samsung device using this guide.
Click to expand...
Click to collapse
Thank you very much for guide.
Nikiz said:
I tried to compile CWM to my Trend 2 SM-G313HN and after flashing the recovery image and booting to recovery mode, a red exclamation mark appeared to the top left corner of the boot screen and the boot process stopped there. At first I thought that the compilation failed, but then I tried to unpack the original recovery.img, edit the default.prop (changed ro.secure to 0) and it happened again. Any changes to the recovery ot boot image seemed to trigger that error. There is a picture in the attachments, sorry about the quality, took it with my old Galaxy Gio.
Atleast I managed to root the phone by manually adding superuser to the system.img and flashing it via Odin, but a recovery would be nice.
EDIT: I discovered that there is a small bootloader hidden in the stock boot/recovery images. Got CWM to boot. (but no graphics yet, but I can connect via ADB) I am working on to get the recovery working.
Click to expand...
Click to collapse
How your fixed this? i have same problem with Gt-s5312c. help me
Onko sulla ideoita miten sais helpoiten tän samsung galaxy trend 2 sm-g313hn puhelimen rootattua ja asennettuu cm11
jonne1 said:
Onko sulla ideoita miten sais helpoiten tän samsung galaxy trend 2 sm-g313hn puhelimen rootattua ja asennettuu cm11
Click to expand...
Click to collapse
Sori näin myöhäinen vastaus. En tätä ketjua seuraile muutenkuin satunnaisesti.
Helpoin tapa rootata on asentaa custom recovery ja flashata sen kautta SuperUser-paketti.. En oo löytänyt mitään "parin klikkauksen" tapaa, mikä tällä puhelimella toimisi. Kannattaa kuitenkin ottaa huomioon, että menetät takuun roottauksen jälkeen.
Custom recoveryn asennus:
Lataa jostain Odin-ohjelma. Versio 3.10 ainakin toimii. Googlaa Odin 3.10 ja valitse ensimmäinen linkki.
Lataa täältä tuo Odin-paketti: (Odin-package) http://forum.xda-developers.com/ace-4/development/recovery-cwm-based-recovery-6-0-5-1-t2987827
Sammuta puhelin ja käynnistä uudelleen painamalla alas-, koti- ja virtanäppäintä yhtäaikaa. Siihen pitäisi ilmestyä varmistusruutu. Yhdistä USB-kaapeli tietokoneeseen ja paina ylä-näppäintä.
Avaa Odin tietokoneella, valitse tuo .tar.md5-tiedosto minkä latasit PDA/AP-kohtaan. Varmista, että "Option"-kohdassa on pelkästään "Auto reboot" ja "F. Reset Time" valittuna.
Sitten painat vain "Start"-nappia ja se asentaa tuon custom recoveryn. Puhelimen pitäisi käynnistyä uudelleen recovery-tilaan, kun se on valmis.
Roottaus:
Lataa tämä puhelimen muistikortille: https://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip?retrieve_file=1
Käynnistä puhelin uudelleen recovery-tilaan painamalla ylös-, koti ja virtanäppäintä yhtäaikaa.
Recovery-tilassa voi liikkua painalamma äänenvoimakkuus-näppäimiä ja valita painamalla virtanäppäintä. Takaisin pääsee normaalisti painamalla takaisin-näppäintä.
Valitse "Install zip", "Install from /storage/extSdCard" (Jos latasit irroitettavalle kortille) ja valitset ladatun .zip-tiedoston. Se kysyy varmistusta ja valitset "Yes".
Sitten kun se on valmis, painat vain takaisin-näppäintä valitset "Reboot system now", niin puhelin käynnistyy uudelleen.
Tuo CyanogenMod 11 on vielä hieman keskeneräinen. Esimerkiksi Facebookissa ja joissain muissakin ohjelmissa ei toimi videot (Youtube tosin toimii), etukameran videokuvaus ei toimi ja muita "pikkuvikoja".
Löydät sen täältä: http://forum.xda-developers.com/ace-4/development/rom-cyanogenmod-11-galaxy-trend-2-t3189325
Lataukset löytyy "Latest builds can be downloaded here"-linkistä ja valitsemalla uusimman version.
Sen asennus tapahtuu samalla periaatteella kuin roottaus, mutta puhelimen tiedot pitää tyhjentää ennen sitä.. Kannattaa varmuuskopioida alkuperäinen Android valitsemalla "backup and restore", "backup to /storage/extSdCard". Tässä menee muutama minuutti. Jos haluaa vaihtaa takaisin alkuperäiseen Androidiin, valitse "backup and restore", "restore from /storage/extSdCard" ja valitse varmuuskopio.
Tietojen tyhjäys tapahtuu "wipe data/factory reset"-kohdasta.
CyanogenModia ei tarvitse rootata, sen saa käyttöön Asetukset -> Superuser-kohdasta. En muista pitikö kehittäjävaihtoehot olla käytössä, mutta ne saa käyttöön Asetukset -> Tietoja puhelimesta ja napauttamalla muutaman kerran "Ohjelmistoversion numero"-kohtaa.
Play-kauppaa tuossa ei ole valmiina mukana, niin se pitää ladata täältä: http://opengapps.org/
Valitset vain ARM ja 4.4. Kannattaa valita Micro-paketti ja asentaa muut ohjelmat Play-kaupasta. (Youtube, Google Maps, yms.) Nuo isommat ei yleensä mahdu muistiin kun päivittää CyanogenModia, niin ne joutuu asentamaan uudelleen.
Tuon OpenGapps-paketin asentaminen tapahtuu myös samalla periaatteella kuin roottaus.
Eiköhän näillä pääse alkuun.. Pitäisi tehdä selkeämmät ohjeet kuvilla, jos vain joskus jaksaisi.
Related
Hi.
Summary: the AndroidRuntime process fails when starting the Connectivity Service, causing my phone into a boot loop.
Sorry for the very verbose post.
Background: I've spent quite a bit of time trying to resolve a problem that causes my Sony Ericsson Xperia X10 Mini (from O2) to go into a boot loop. I've rooted the phone some time ago using this process: (sorry the forum prevents me from posting link, please copy and paste this: android.doshaska.net/x10miniroot).
I then proceeded to remove some of the redundant programs from /system/app.
Everything worked fine for several weeks until the phone started complaining about the storage being filled up. I could see that /data was getting full and I suspected that the K9 email client I had installed was using lots f space to keep the IMAP folders synced.
I can't remember if the phone rebooted itself or if I did it manually, but it never managed to boot up again, and is ever since stuck at the Sony Ericsson logo.
adb logcat tells me that the AndroidRuntime process fails when starting the Connectivity Service. It's stuck in this loop, but I've isolated one single loop in the attachment logcat.txt. The crash file references has been attached as 1279210811.txt.
The final fatal crash is:
I/SystemServer( 1297): Starting Connectivity Service.
W/dalvikvm( 1297): threadid=51: thread exiting with uncaught exception (group=0x2aac9a28)
E/AndroidRuntime( 1297): Uncaught handler: thread ConnectivityThread exiting due to uncaught exception
E/AndroidRuntime( 1297): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
E/AndroidRuntime( 1297): java.lang.NullPointerException
E/AndroidRuntime( 1297): at android.app.ActivityThread.getProvider(ActivityThread.java:3938)
E/AndroidRuntime( 1297): at android.app.ActivityThread.acquireProvider(ActivityThread.java:3967)
E/AndroidRuntime( 1297): at android.app.ApplicationContext$ApplicationContentResolver.acquireProvider(ApplicationContext.java:1527)
E/AndroidRuntime( 1297): at android.content.ContentResolver.acquireProvider(ContentResolver.java:579)
E/AndroidRuntime( 1297): at android.content.ContentResolver.query(ContentResolver.java:147)
E/AndroidRuntime( 1297): at android.provider.Settings$NameValueCache.getString(Settings.java:476)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getString(Settings.java:1701)
E/AndroidRuntime( 1297): at android.provider.Settings$Secure.getInt(Settings.java:1741)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.getPersistedNetworkPreference(ConnectivityService.java:182)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:123)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService.<init>(ConnectivityService.java:47)
E/AndroidRuntime( 1297): at com.android.server.ConnectivityService$ConnectivityThread.run(ConnectivityService.java:87)
I've had a look at the JavDoc for android.app.ActivityThread.getProvider, but I've not been able to find any useful information. I have to guess that the start-up process fails to read the provider (network) specific settings for some reason. I don't have a clue whether the source is a file, database or something else.
A wild guess is that something got corrupted when the data partition filled up. There are some upset earlier in the log (line 180) when the PackageManager is reading an XML file that relates to the PackageManager settings that seems to have been corrupted:
E/PackageManager( 1297): Error reading package manager settings E/PackageManager( 1297): org.xmlpull.v1.XmlPullParserException:
Premature end of document. (position:line -1, column -1) caused by:
org.apache.harmony.xml.ExpatParser$ParseException: At line 1, column 0: no element found
I've seen a few similar posts, but nothing exactly like this nor anything that I could use to resolve it.
Stupid section
I've got myself into this through a combination of stupidity and bad luck. I've backed up all .APK that I've removed and created a log of what I removed (that I'm still looking for). I thought this was all that I needed and I don't have a full backup.
Unfortunately, the root access now gives me a segmentation fault and the root process requires the GUI to work, so I can't repeat the process. I don't want to try another root process before I've tried what I can to get the phone back in a reasonable state.
Fortunately, I still have full adb access, so I have visibility and some control over the phone.
Any help on this would be much appreciated. At least I've saved you the time pointing out that I'm an idiot not doing a full backup
Regards,
Dan
I am very happy to propose you my first custom rom for the HTC JetStream! This rom is based on the released rom from AT&T 1.30.502.1 and should work for both American and Canadian tabs. The system has been made as light as possible and all "unnecessary" application has been removed.READ CAREFULLY:
This rom does NOT include any kernel but works exclusively with DoomLord Kernel v1
Installing this rom will WIPE your device but can be done if this feature is needed
You need [URL="http://forum.xda-developers.com/showthread.php?t=1418084"]ClockWorkMOD [/URL]to install this ROM
You are doing this at your own risks
Rom Description:
This rom is my daily driver, I like my tablet, clean without any bloatware or unneccessary app or widgets from AT&T or HTC
Zipaligned / Deodexed
Rooted - latest version
Removed all unnecessary applications - see second post
Latest version 2.03.10:
Careful, this version will WIPE your device, make a backup!
Careful, the new version will WIPE your phone, make a backup!
I am not asking for donation but press the thanks button and please Vote for this thread tooCredits:
DooMLoRD for the kernel and CWM
mendozinas, for his online kitchen
dsixda, for his kitchen
Before asking a question, use this button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and watch this , thanks:
v2.03.10
New Boot animation
Roboto fonts included
Battery in %
Ad-Away an No-Frill included
All bloatware removed
Phone functions enabled
Tethering activated
Rooted
Latest Market
Busybox installed
Zipaligned
Fully de-odexed
Frequently Asked Questions:
Will this rom work with the default kernel?
Most probably yes but...
Wi-Fi will be broken
Can I revert to the default kernel on this rom?
Yes now you can! but follow the steps and I won't babysit
Download the file from my site called: Jetstream_OsiMood_DefaultKernelFiles.rar
Inside you will find 2 files JetStream_OsiMood_DefaultKernel_WiFi_Module.zip and defaultBoot.img
Once those two files unzipped in a folder
Move the zip file to your SD-Card
Once done, reboot in bootloader: adb reboot bootloader
Now time to flash the default kernel: fastboot flash boot defaultBoot.img
Now go in recovery and install the attached zip, the patch will install the correct WiFi module and wipe your cache
Reboot, you have now the default kernel running and WiFi working
Try to reboot in recovery if it does not work just re-install the DooMLoRD recovery
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
tyrannos said:
Nice work - looking forward to flashing this tonight!
FYI - Link currently broken on DL page.
Click to expand...
Click to collapse
I know for the link, working on it... will let you know when back up
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Simply because it is working smoothly for me @1.8ghz and that is more than enough
The link is up
Downloading now, looking forward to trying this one!
Wait, so this will still work with the stock kernel, right?
guru_shastri said:
it's great to see some movement here. one question - why must it work with doomlords kernel? that thing is quite unstable..
Click to expand...
Click to collapse
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Sent from my HTC PG09410 using XDA
Click to expand...
Click to collapse
I am going to see what I can do for that as it seems I am also facing some random reboots
Market
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
dcd17 said:
Gotta agree here, its great to see a custom rom for this device but after spending an hour reverting and wiping back to stock kernel just yesterday because of 2 weeks of rebooting and freezes with the custom kernal, I'd be really hesitant to go back to it.
I would absolutely love to see an option to stick with stock kernel if possible. Thanks for the work on this rom, its great to finally see some movement on this forum!
Click to expand...
Click to collapse
You can now roll back to the default kernel
juannicolas said:
Hello. Thanks, finally somebody have action, good to see people taking time to work with this great device.
I just download your rom and installed and runs very smooth and clean. One issue tho, the Market aka Google Play is giving me an error FC
Code:
D/AndroidRuntime( 3044): Shutting down VM
W/dalvikvm( 3044): threadid=1: thread exiting with uncaught exception (group=0x4001c798)
E/AndroidRuntime( 3044): FATAL EXCEPTION: main
E/AndroidRuntime( 3044): java.lang.NullPointerException
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.Sha1Util.secureHash(Sha1Util.java:46)
E/AndroidRuntime( 3044): at com.google.android.finsky.utils.FinskyLog.scrubPii(FinskyLog.java:57)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.recordPackageInstalled(Reconstructor.java:139)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.Reconstructor.reconstruct(Reconstructor.java:109)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.updateFromReconstruct(ReconstructDatabaseService.java:135)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService.access$000(ReconstructDatabaseService.java:26)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:68)
E/AndroidRuntime( 3044): at com.google.android.finsky.services.ReconstructDatabaseService$1.onResponse(ReconstructDatabaseService.java:49)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:141)
E/AndroidRuntime( 3044): at com.google.android.vending.remoting.api.VendingRequest.deliverResponse(VendingRequest.java:40)
E/AndroidRuntime( 3044): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:113)
E/AndroidRuntime( 3044): at android.os.Handler.handleCallback(Handler.java:587)
E/AndroidRuntime( 3044): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime( 3044): at android.os.Looper.loop(Looper.java:152)
E/AndroidRuntime( 3044): at android.app.ActivityThread.main(ActivityThread.java:4606)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3044): at java.lang.reflect.Method.invoke(Method.java:491)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
E/AndroidRuntime( 3044): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
E/AndroidRuntime( 3044): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 300): Force finishing activity com.android.vending/com.google.android.finsky.activities.TosActivity
W/ActivityManager( 300): Force finishing activity com.android.vending/.AssetBrowserActivity
D/ActivityManager( 300): isSketcherDisabledInCurrentTask():false, ActivityRecord{40a49db8 com.android.vending/com.google.android.finsky.activities.TosActivity}
D/ViewRoot( 300): ## mIsSketcherDisabledInCurrentTask is false
D/WindowManager( 300): call linkToDeath, this=Window{4114a998 Sorry! paused=false}
Click to expand...
Click to collapse
No clue why, empty the cache of the app and try again
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
for CWM - reset the device - and after the screen goes black press and hold vol. down.
so to install this rom we need to install the doomlord kernel and then go back to stock? or we can just install it over the stock?
can anyone actually work with the doomlord kernel to improve it? i think it was great at its base..perhapes just removing the voltage control..i think that's the problem it had.
CarpeNoctem said:
You can now roll back to the default kernel
No clue why, empty the cache of the app and try again
Click to expand...
Click to collapse
Tried that but since the app have never being opened there is no clean/clear cache option active for it.
NJFM said:
This is going to sound stupid but how do you boot the device in recovery? I've loaded CWM through adb but any button combo won't work. I would really like to test out this ROM, thanks for any help!
Click to expand...
Click to collapse
the simplest way, install this: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot&hl=en
CarpeNoctem said:
I am going to see what I can do for that as it seems I am also facing some random reboots
Click to expand...
Click to collapse
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Sent from my HTC Rezound™ using xda premium
k2trill said:
I really don't think the level is the issue. my Jetstream ran the MOST STABLE with Doomlords kernel. I had more random reboots before I ever rooted it or anything. I think Honeycomb just sux or maybe the version of Sense we have over Honeycomb sux and is waaaaay underdeveloped from factory. just my 2 cents....
Click to expand...
Click to collapse
Now you have the choice at least you, stock or DooMLoRD
its a fact that some devices sufford random reboots only when using the kernel. i think the kernel has a great base, and my device never ran faster - but it still crashed him.
i think it's got something to do with the Voltage control, but i can't really be sure.
ParanoidAndroid build from sources with the new 2.6.53 kernel from TheWhisp; see more detail about this project on http://www.paranoid-rom.com/
please, when you have a problem, attach a logcat
-How to install:
Transfer the .zip file to your SD card
Reboot into ClockworkMod, choose the option Install zip from sdcard -> choose zip from sdcard. Select the current release, and confirm the update by selecting Yes.
Reboot and enjoy!
Remember: if you come from any other version of android that isn't PA jb (or PA jb based) you'll have to wipe data from CWMR
-Gapps:
use jb-20121017-KonstaKANG on modaco
http://www.mediafire.com/?qscnhfuadsujki1
-How to check file's hash:
i recommed you to install hashtab, so just right-click on the file, click propriety and go to hash file tab
-2.99:
updated to android 4.2
it uses modified libstagefright from Rashed97
built whit gcc 4.6 + some trick to reduce apk size
hash: [md5sum] 3f572d3b240ad124f35e93bd0aa240e1
http://depositfiles.com/files/4m6sx4gre
-2.55:
first release, see what works/not works down here
http://depositfiles.com/files/spbfpz8xj
Working:
2D & 3D acceleration with triple-buffering (Butter UI)
Camera (Barcode Scanner mode also works)
GPS
Headset
Lights
Sensors
Touchscreen
USB Mass Storage
keys
Not Working:
Telephony (calling, mobiledata & messaging)
bluetooth
wifi
sdcard isn't recognized
Partially working:
Video camera (can capture video, but saved media will have artifacts/low FPS)
OMX video encoders/decoders
Not working:
USB tethering
Wifi tethering
Thanks to:
Motafoca
TheWhisp, squadzone & all contributors associated with the shared Samsung msm7x27 jellybean kernel & device config used as a base for the galaxy5 port
nend for MAD Manager & general assistance
KonstaT for his reduced gapps-jb package
Rashed97 for his modified libstagefright
richie161cfc (madteam) for testing many test build
All other testers for your patience & support - thank you.
Good work and thanks! :thumbup:
Sent from my GT-S5360 using xda premium
XdaNoob98 said:
Good work and thanks! :thumbup:
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
thanks; did you tested it? if yes can you attach a logcat?
thenks. currently downloading
---------- Post added at 06:03 PM ---------- Previous post was at 05:04 PM ----------
First of all checked wifi but was not able to find my network. Now when I tried to dial a number it just dropped the call after 10 secs without connecting. There is also no ringing tone on incoming call. Cancel call button long press is not showing the boot menu so I don't know how to reboot it without a battery pull. Pressing home button is doing nothing. Rebooted by battery pull but same issues.
---------- Post added at 06:51 PM ---------- Previous post was at 06:03 PM ----------
Well, now I am unable to reboot into recovery for a nand restore as reboot is not working and I cannot do it with odin as I have installed ubuntu and removed windows. Can you help me with this?
sixline said:
thenks. currently downloading
---------- Post added at 06:03 PM ---------- Previous post was at 05:04 PM ----------
First of all checked wifi but was not able to find my network. Now when I tried to dial a number it just dropped the call after 10 secs without connecting. There is also no ringing tone on incoming call. Cancel call button long press is not showing the boot menu so I don't know how to reboot it without a battery pull. Pressing home button is doing nothing. Rebooted by battery pull but same issues.
---------- Post added at 06:51 PM ---------- Previous post was at 06:03 PM ----------
Well, now I am unable to reboot into recovery for a nand restore as reboot is not working and I cannot do it with odin as I have installed ubuntu and removed windows. Can you help me with this?
Click to expand...
Click to collapse
thanks for reporting, to fix button problem you can try to substitute the folder usr inside system with the one from psyke's cm10
for wifi try substitude the folder wifi with the one from psyke's cm10
next update will fix them all; can you attach a logcat?
manuel100 said:
thanks; did you tested it? if yes can you attach a logcat?
Click to expand...
Click to collapse
Perhaps (I think its "perhaps" or is it "unfortunately" ) my G5 is actually bricked but i'll get it back soon and i'll give logcat asap ok?
Sent from my GT-S5360 using xda premium
Yeah sure I can try those but I have a very slow internet connection.Can you upload these folders? And I am still trying to get into recovery...
XdaNoob98 said:
Perhaps (I think its "perhaps" or is it "unfortunately" ) my G5 is actually bricked but i'll get it back soon and i'll give logcat asap ok?
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
ok
Yeah sure I can try those but I have a very slow internet connection.Can you upload these folders? And I am still trying to get into recovery...
Click to expand...
Click to collapse
here: http://depositfiles.com/files/0edassb32
i need a logcat for the sound problem
updated the rom to pa 2.99 (4.2), i need some testers and many logcats
Like i said i will test it a give logcats in six days if it isn't too long?
Sent from my GT-S5360 using xda premium
I tested your rom, stuck on boot animation, after 10 minutes repeating the boot animation, the phone finally booted, a android phone fc notification appears, and when i press ok, it's appears again, here is a logcat.
IDntKnwHowUse said:
I tested your rom, stuck on boot animation, after 10 minutes repeating the boot animation, the phone finally booted, a android phone fc notification appears, and when i press ok, it's appears again, here is a logcat.
Click to expand...
Click to collapse
thanks fro testing, i'm trying to undestand why it fc; any information is useful
@XdaNoob98; don't worry, attach it when you can
here's the error with phone, extracted from IDntKnwHowUse's logcat:
E/AndroidRuntime( 2510): FATAL EXCEPTION: main
E/AndroidRuntime( 2510): java.lang.RuntimeException: Unable to create application com.android.phone.PhoneApp: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4384)
E/AndroidRuntime( 2510): at android.app.ActivityThread.access$1300(ActivityThread.java:145)
E/AndroidRuntime( 2510): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1271)
E/AndroidRuntime( 2510): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2510): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2510): at android.app.ActivityThread.main(ActivityThread.java:4978)
E/AndroidRuntime( 2510): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 2510): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 2510): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime( 2510): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime( 2510): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime( 2510): Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:155)
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhones(PhoneFactory.java:59)
E/AndroidRuntime( 2510): at com.android.phone.PhoneApp.onCreate(PhoneApp.java:470)
E/AndroidRuntime( 2510): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:999)
E/AndroidRuntime( 2510): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4381)
E/AndroidRuntime( 2510): ... 10 more
E/AndroidRuntime( 2510): Caused by: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at java.lang.Class.classForName(Native Method)
E/AndroidRuntime( 2510): at java.lang.Class.forName(Class.java:217)
E/AndroidRuntime( 2510): at java.lang.Class.forName(Class.java:172)
E/AndroidRuntime( 2510): at com.android.internal.telephony.PhoneFactory.makeDefaultPhone(PhoneFactory.java:148)
E/AndroidRuntime( 2510): ... 14 more
E/AndroidRuntime( 2510): Caused by: java.lang.NoClassDefFoundError: com/android/internal/telephony/SamsungMSMRIL
E/AndroidRuntime( 2510): ... 18 more
E/AndroidRuntime( 2510): Caused by: java.lang.ClassNotFoundException: com.android.internal.telephony.SamsungMSMRIL
E/AndroidRuntime( 2510): at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:61)
E/AndroidRuntime( 2510): at java.lang.ClassLoader.loadClass(ClassLoader.java:501)
E/AndroidRuntime( 2510): at java.lang.ClassLoader.loadClass(ClassLoader.java:461)
E/AndroidRuntime( 2510): ... 18 more
W/ActivityManager( 1494): Process com.android.phone has crashed too many times: killing!
I/Process ( 2510): Sending signal. PID: 2510 SIG: 9
I/ActivityManager( 1494): Process com.android.phone (pid 2510) has died.
Click to expand...
Click to collapse
OK I'm so exited because paranoid is the best rom for me:thumbup:
Sent from my GT-S5360 using xda premium
Paranoid Android doesn't work! It boots after 10 minutes. FC's on telephony every second
Sent from my GT-I5500 using xda premium
manuel100 said:
thanks fro testing, i'm trying to undestand why it fc; any information is useful
@XdaNoob98; don't worry, attach it when you can
here's the error with phone, extracted from IDntKnwHowUse's logcat:
Click to expand...
Click to collapse
You have to point the RIL to boardconfig. As I said here:
Paul L. said:
Is the RIL working? You can make it work by pasting the propietary RIL java class to the optional telephony package and pointing it out in the boardconfig by using the example from the lastest commit from codeworkx to the CM10.1 staging branch
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Which, by the way, it's not enough. You will have to adapt SamsungMSMRIL to Android 4.2
Why don't you ask some other developers to help you? Or simply post it to madteam?
Sent from my superphone in 2000 BC
How on earth has this been released IV never seen such a mess of a rom, the most important parts don't work and people are flashing this when its unusable really and your asking them to logcat for you lol if your going to make a rom use cm7 there isn't any faults and its a good easier starting block for adding and customizing I would remove this rom or at least the download link until the faults are fixed
Sent from my GT-S5830 using xda premium
brewy said:
How on earth has this been released IV never seen such a mess of a rom, the most important parts don't work and people are flashing this when its unusable really and your asking them to logcat for you lol if your going to make a rom use cm7 there isn't any faults and its a good easier starting block for adding and customizing I would remove this rom or at least the download link until the faults are fixed
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Well, the dev's doing the right thing. He is building the ROM from source code, not change/theming someone else's work!. He is doing the right thing asking for logcats. That is how its actually done!.
You might not have been here when development on cm7 started. It was pretty bad. Everything was broken/not working. Psyke eventually fixed everything and made it what it is now.
So stop your nonsense talk and try contributing to the development.
Sent from my GT-I9300 using xda-developers app
Hello thanks for your work bro why not you come to madteam , there you will get more tester and your development goes more fast.
Battery Shutdown Manager
Download @ Google Play
Do you know that moment when you're on 1% of battery and think "I'll just use my device 20 more seconds then I'll get my charger" - and at exactly that moment it'll switch to 0% and you'll see the threaded "Shutting down" dialog and know it's too late now?
This Xposed module will help by showing you a dialog with a countdown before the actual shutdown, so you'll have time to attach your charger.
The module achieves this by postponing the shutdown for a couple of seconds to give you time to connect the charger.
Please post any kind of feedback or ideas you have regarding this app :fingers-crossed:
I tested the module a lot but can't possibly test it for all those different phones and versions out there.
Thus I will flag it as beta for now so you can provide feedback before I'll release the 1.0 version.
It would be great if some more people could test it. I used the StabilityTest app to quickly drain my battery down to 0%.
Compatibility:
I wrote this module and tested it with AOSP devices as well as on Cyanogenmod.
It should work without any issues on all Nexus and Google Play Edition devices from Android 4.2 to 5.1+.
As almost all Custom ROMs are based on either AOSP or CM they should work without issues, too.
Some vendors might have changed the original code and thus render this module incompatible on their device. Nothing bad will happen when you install it, it just won't work.
Compatible:
Nexus / AOSP / GPE ROMs
Cyanogenmod
Almost all custom ROMs (as they're usually either based on AOSP or CM)
Sony Stock ROMs
Not compatible:
Currently not working for LG Stock ROMs due to internal code changes by LG.
Android devices <4.2. Support for Android 4.0.3+ and 4.1 might be added when I see a greater demand for it.
Installation:
- Download the app
- Activate the module in the Xposed Insaller
- Reboot your device
- Open the app to change it's options to your liking
Bugs/Issues:
If you encounter any bugs just report them here and I'll try to fix them. Always include as much information as possible, including your device model, android version and exact ROM details.
Note that I will most likely need a log to fix the issue, a generic "doesn't work on phone xyz" won't help me fixing the issues.
There are two possibilities to get a log.
Use the Catlog app. In the app press Menu > Record Log before the device shuts down, then attach the logcat to your bugreport.
Alternatively you need to use adb to grab the log.
Unfortunately logging is a bit more complicated for this module as the interesting part happens on shutdown.
The best solution (and what I do personally for debugging this app) is to use ADB over WiFi (e.g. with this app) and grab the log.
Download:
Google Play Store
Xposed Module Repository
Google+:
www.google.com/+thetonyp
Last but not least an obligatory huge thanks to @rovo89 for his amazing Xposed framework!
If you like this module don't forget to press thanks, rate this thread with 5 stars, consider a donation etc. etc.
:fingers-crossed:
I love your icon pack!
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Samsung galaxy s3 i9300 4.3 mk6 stock rom, bootloops.
Sent from a stolen phone!
Bootloop on Nexus 4, Stock Android 4.3.3...
EDIT Because OP asked how the bootloop occurs on Nexus 4, Android 4.3.3:
Bootloop occurs after activating module and normal (not soft) reboot.
Before reboot app can be runned and configurated.
I have no log app running, so I'm not able to deliver logs.
Yes, please send me a logcat. Bootloops are great, then you can just get the log after the reboot. I literally can't do anything without a log.
mobihack said:
Tried it on my cm12.1. No bootloops here. Will edit after full uncharging
EDIT: Turned turning on full brightness, hot spot, gps, flashlight, mobile data, etc... Still 8% to go. Your module and me are waiting eagerly lol
EDIT2: Finally reached 0
And tonyp, I am pleased to say your module works in cm12.1
Suggestion: Make the dialog box closable. So if I am playing a game or writing to a File I can save my progress. Hope you understand.
And I appreciate your idea. Well implemented.
And do you mind sharing that icon pack :hungry:
Click to expand...
Click to collapse
Thanks for the feedback, then I will add 5.1 to the compatibility at the Play Store.
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
tonyp said:
Thanks for the feedback, then I will add 5.1 to the compatibility at the
Regarding the closable dialog, I made it non closable on purpose but I'll consider adding an experimental feature to change that. At first I'd like to fix the bugs, though.
Click to expand...
Click to collapse
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
bootloops
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
akhilkbaby said:
Bootloop on MMX Canvas Magnus stock ROM (JB 4.2.1)
Click to expand...
Click to collapse
I'd like to fix the issue, could you kindly send me a logcat of the bootloop?
Unfortunately there is literally nothing I could possibly do without a log.
mobihack said:
More suggestions:
Add some animations to the dialog
Add option for an alert tune or notification 1min before
Add buttons to dialog box for shutdown(sometimes I dont like to wait)[optional]
Happy with what you had already done and you forgot me an icon pack
Click to expand...
Click to collapse
I'm using the stock dialog which guarantees the highest possible compatibility with other devices.
Regarding the notification, I don't know when the battery will be empty before, so there's no way to display a message one minute before. All I could do is starting the dialog at 1% (which I'm considering for a future version), but that would be quite different.
I like the idea for a shutdown button, an option to include that will be in an upcoming version.
Oh, true, the icon pack is called etched material.
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
HydraS4 said:
Phone freezes when I get a notification from an app. Specifically when I get a notification from Messenger(Facebook app). Is it possible to grab a log if it freezes and I have to restart?
And to make sure it wasn't anything else, I uninstalled it and the freezing stopped.
Galaxy S4 4.4.2 Stock ROM w/ Root
Thanks
Click to expand...
Click to collapse
This sounds very strange, the module is only hooking into one class which has nothing to do with receiving messages.
Yes, usually it works to log the freeze, just start logging (best would be with adb logcat) before it happens.
Can not install on 4.1
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
---------- Post added at 02:41 PM ---------- Previous post was at 01:49 PM ----------
Fif_ said:
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
Click to expand...
Click to collapse
There we go, I have it.
This is a logcat of the behavior I was describing earlier: after the countdown, the system performs a soft reboot instead of shutting down.
I have seen this behavior on Nexus 4/5/10 (mako/hammerhead/manta) on CM11 M11.
The logcat below is on a Nexus 4 running CM11 M11 and Battery Shutdown Manager 0.93:
Code:
I/Xposed ( 1726): BatterySM: invokeOriginalMethod. batteryLevel=2, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=false, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: Showing dialog. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=null, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: AlertDialog is showing, postpone shutdown. batteryLevel=0, isPoweredLocked=false, chosenTime=30, alertDialog=true, showedDialog=true, prefScreenOff=false, isScreenOn=true
D/SystemPanel( 4621): Recorder Update, force=false
I/Xposed ( 1726): BatterySM: Dismiss dialog
W/InputMethodManagerService( 1726): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
D/AndroidRuntime( 1726): Shutting down VM
W/dalvikvm( 1726): threadid=1: thread exiting with uncaught exception (group=0x415e4ce0)
E/AndroidRuntime( 1726): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 1726): java.lang.NoSuchMethodError: com.android.server.BatteryService#processValuesLocked(java.lang.Boolean)#bestmatch
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:271)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.findMethodBestMatch(XposedHelpers.java:284)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedHelpers.callMethod(XposedHelpers.java:947)
E/AndroidRuntime( 1726): at com.thetonyp.batteryshutdownmanager.BatteryDialog$2.onFinish(BatteryDialog.java:258)
E/AndroidRuntime( 1726): at android.os.CountDownTimer$1.handleMessage(CountDownTimer.java:118)
E/AndroidRuntime( 1726): at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 1726): at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(SystemServer.java:1289)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.ServerThread.initAndLoop(Native Method)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(SystemServer.java:1386)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:631)
E/AndroidRuntime( 1726): at com.android.server.SystemServer.main(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1726): at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime( 1726): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime( 1726): at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
E/AndroidRuntime( 1726): at dalvik.system.NativeStart.main(Native Method)
W/DropBoxManagerService( 1726): Dropping: system_server_crash (1667 > 0 bytes)
I/Process ( 1726): Sending signal. PID: 1726 SIG: 9
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Mubasher96 said:
I am trying to install it on my xperia x10 running cm10 but it does not install. Please help me so that I can test the module on it.
Click to expand...
Click to collapse
The module currently requires Android 4.2 or higher. You can't install the module on CM10 as that is based on Android 4.1.
To support Android 4.0 and 4.1 I need to write some custom code which I need some people to test, so everyone interested in this module on a 4.0 or 4.1 device (including CM9 / CM10 etc of course) please write here or send me a PM and I'll contact you as soon as I have a version ready for testing! Can I count you in?
Fif_ said:
I am also experiencing odd behavior on CM 11 M11 on two devices: Nexus 5 and 10.
The behavior I'm seeing is that when the battery is running low, the dialog shows up.
When the countdown completes, the device then reboots (seems to be doing a soft boot) instead of shutting down.
I am running some experiments, on a Nexus 4 and I'm hoping to capture a logcat.
...
I've trimmed the logcat, but it's available to the dev in its entirety, if needed.
Click to expand...
Click to collapse
Thank you very much for the logcat! It contained exactly what I needed!
Thanks to that I identified the issue and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Additionally this version fixes a potential bootloop cause for devices running Jellybean (4.2 / 4.3).
Could the affected people please test this and confirm? Again, if you manage to get me a log it will make it a lot easier for me to fix any issue whatsoever.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Nice! This is so necessary… I'm gonna test it.
tonyp said:
Thank you very much for the logcat! It contained exactly what I needed!
I believe I identified the issue thanks to the log and pushed out a new version (0.94) to fix it.
It will probably take a couple hours in the Google Play Store to appear, in the meantime you can find the new version at the Xposed Repo or attached to this post.
Changelog v0.94:
fixed a soft reboot on Kitkat devices when the countdown reaches 0
fixed a potential bootloop on Jellybean devices
Click to expand...
Click to collapse
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Fif_ said:
The 0.94 update fixes the soft-reboot after countdown problem for me on CM11 M11 for Nexus 5. I haven't checked the other devices, and won't be any time soon.
Also, I just bought the Pro version on one device.
The Pro option won't unlock on the other devices, I get a "You already own this item." Error.
Click to expand...
Click to collapse
No worries, they're using the same codebase so it will work on all devices.
Thanks a lot for buying pro
That purchase should work on all devices of course sometimes it takes a little while to propagate at Google, when you still have the issue after a couple more hours could you please drop me a PM? I did test the IAP purchases with all possible ways Google offers for me, but unfortunately that's something that could be greatly improved on their side.
exodius48 said:
@tonyp I'm using WSM Manager (Xposed for MIUI) , but this app still ask to download xposed installer. How to fix this?
Click to expand...
Click to collapse
Ah, I didn't know there exists an alternative manager. I'm explicitly checking for the Xposed Installer. You can ignore the warning for now and I will push an update which recognizes the WSM Manager as well
No bootloops on moto g stock 5.0.2
After trying to boot my phone several times with an almost empty battery the phone won't boot any more. The boot process hangs in the Jiayu logo (the phone is a Jiayu S3). The phone gets hot, so maybe it is doing something CPU intensive??? I can connect to the phone via adb. Command "adb logcat" shows several messages flowing constantly. The most severe message as far as I can tell is the following:
Code:
E/AndroidRuntime( 841): *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E/AndroidRuntime( 841): java.lang.RuntimeException: Unable to find android system package
E/AndroidRuntime( 841): at com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java:2069)
E/AndroidRuntime( 841): at com.android.server.SystemServer.startBootstrapServices(SystemServer.java:500)
E/AndroidRuntime( 841): at com.android.server.SystemServer.run(SystemServer.java:338)
E/AndroidRuntime( 841): at com.android.server.SystemServer.main(SystemServer.java:241)
E/AndroidRuntime( 841): at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 841): at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime( 841): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959)
E/AndroidRuntime( 841): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754)
E/AndroidRuntime( 841): Caused by: android.content.pm.PackageManager$NameNotFoundException: android
E/AndroidRuntime( 841): at android.app.ApplicationPackageManager.getApplicationInfo(ApplicationPackageManager.java:286)
E/AndroidRuntime( 841): at com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java:2051)
E/AndroidRuntime( 841): ... 7 more
I think that the error comes from this line in com.android.server.am.ActivityManagerService.setSystemProcess(ActivityManagerService.java):
Code:
ApplicationInfo info =
mSelf.mContext.getPackageManager().getApplicationInfo(
"android", STOCK_PM_FLAGS);
Is there a fix for the message "Unable to find android system package" (package "android")? For example, would re-installing an .apk (which one?) fix this?
I would rather not reflash the ROM. I would like to preserve the data I have, such as text messages, WiFi passwords and WhatsApp contents.
I have already tried twice wiping cache and Dalvik cache.
My phone is Jiayu S3 with stock Android 5.1. It is rooted and has TWRP.
Now only fastboot, adb and TWRP Terminal work for my phone (Jiayu S3). Android user interface won't start, it just shows the Jiayu logo. Is there any command (in fastboot, adb or TWRP Terminal) which would reset the Android user interface so that I could boot into the graphical user interface again?
The phone is the "Jiayu Deutschland" version and it has TWRP 2.8.7.0 and Android 5.1.1. I do not have the original ROM files so I can't just reflash it.
I still haven't made any progress. Android boot just shows the logo and does not open the normal UI. adb logcat displays repeated error "Unable to find android system package". The only things that work are fastboot, adb and TWRP. So basically I have the command line, but not the graphical user interface.
How could I debug error "Unable to find android system package"? Are there any helpful logs? So far I have looked at adb logcat, dmesg and files in /data/anr.
How can I verify that CLASSPATH is OK during boot? What file contains the android system package, how can I verify it? Should I try regenerating dex files? I have already wiped cache and Dalvik cache.