Hi, guys!
I've tried rooting my DesireZ using "Downgrading guide from gingerbread to froyo" (link was destroyed by forum rules)
It is really clear and easy to do guide. But I ran into a problem because I can't make a root backup after gaining Temporary root on HTC DESIRE Z (2.42.405.2). When fixsu.sh ends I am starting "Root check basic" app and it has show me the result is OK. Then I starts MyBackupPro. The first time it shows me new menu item with root operations, but after that it refusing do anything instead of message "There is no properly root access". Titanium Backup behaves in the same way: it properly starts, but does not work with system applications. The only step in the guide I have missed is "Changing version number", but I think the problem is not the case, is it true? Could you tell me please, what may be a reason?
I really fear to begin change the ROM before to have full backup...
Try a full power off. turn the phone off, pull the battery out for a minute, then turn it back on and retry the temp-root.
Sometimes the 'fastboot' feature of sense roms messes with the temp-root.
-Nipqer
Nipqer said:
Try a full power off. turn the phone off, pull the battery out for a minute, then turn it back on and retry the temp-root.
Sometimes the 'fastboot' feature of sense roms messes with the temp-root.
-Nipqer
Click to expand...
Click to collapse
unfortunately, did not help.
Here is log after I turned device:
C:\Documents and Settings\htc>adb devices
List of devices attached
HT0BHRT01025 device
C:\Documents and Settings\htc>adb shell
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Potential exploit area found at address fbb52000:1000.
Exploiting device...
C:\Documents and Settings\htc>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./fixsu.sh
./fixsu.sh
# cat /system/etc/passwd
cat /system/etc/passwd
root::0:0:root:/data/local:/system/bin/sh !!ROOT is really getting!
# cat /system/etc/passwd
cat /system/etc/passwd
keychar xV4 9 0 0 0 # !!After MyBackup Pro start
#
I think the problem is the destruction of the memory area, where exploit works.
Maybe there are other ideas?
All:
I have been having this strange problem with my ion and I thought maybe I will post here to see if someone can help. I updated to the stock ICS using PC companion and that worked well and I was quite happy with the update, but lately I am seeing this very strange behavior on the device that has really hurt my battery life - Android OS and system_server are taking up a lot of resources and battery.
I have been trying to get to the bottom of this - and here is what I am seeing:
The device boots up and works fine - all processes within normal CPU use.
Device goes to sleep, and about a minute after that, I get the following on my Logcat:
10-10 18:41:06.533: I/Adreno200-EGLSUB(3124): <CreateImage:893>: Android Image
10-10 18:41:06.533: I/Adreno200-EGLSUB(3124): <GetImageAttributes:1102>: RGBA_8888
10-10 18:41:06.543: D/memalloc(3124): /dev/pmem: Allocated buffer base:0x428ef000 size:3674112 offset:44937216 fd:50
10-10 18:41:06.553: D/memalloc(3155): /dev/pmem: Mapped buffer base:0x6a993000 size:48611328 offset:44937216 fd:245
10-10 18:41:06.573: I/Adreno200-EGLSUB(3124): <CreateImage:893>: Android Image
10-10 18:41:06.573: I/Adreno200-EGLSUB(3124): <GetImageAttributes:1102>: RGBA_8888
10-10 18:41:06.733: I/Adreno200-EGLSUB(3124): <CreateImage:893>: Android Image
10-10 18:41:06.733: I/Adreno200-EGLSUB(3124): <GetImageAttributes:1102>: RGBA_8888
Right after this happens, top starts showing something like this:
User 23%, System 7%, IOW 0%, IRQ 0%
User 73 + Nice 0 + Sys 22 + Idle 215 + IOW 0 + IRQ 0 + SIRQ 0 = 310
PID PR CPU% S #THR VSS RSS PCY UID Name
3155 0 22% S 80 667232K 79664K fg system system_server
3124 0 3% S 10 155268K 11184K fg system /system/bin/surfaceflinger
5444 0 3% R 1 1092K 496K fg root top
903 0 0% S 5 5280K 548K fg root /system/bin/mpdecision
81 0 0% S 1 0K 0K fg root kworker/0:2
So system_server and /system/bin/surfaceflinger takes up 25% of CPU and keeps going like this until I turn the device on. Then everything is again back to normal.
My question is - what is the Adreno200-EGLSUB doing in the background? Is it creating some kind of a system image that I will just need to let happen until it is done and hopefully the battery life will improve then? If anyone else is seeing the same behavior and have found a way to fix it, I would greatly appreciate some pointers.
Thanks so much!
Jit
When I have a battery issue I usually clear the cache and fix permissions and it clears up but it may not be your case
Sent from my LT28at using xda premium
Strange I would suggest the following.
Back up with titanium and cwm.
Clear cache and dalvic via cwm.
No solution uninstall app via titanium and restore without data. In the event this causes issues restore via cwm or titanium.
If still not fixed freeze the apk via titanium ans allow normal use to check for a fix or other issues.
Still nothing reflash. Sorry
This is the method I usually fallow for issues such as this. Give it a go. Hope this helps.
+++++--------+++++
Sent from:
Xperia Ion(lt28i) ICS
Rooted with CWM
+++++--------+++++
I followed all the instructions for adb and successfully installed twrp, and the firefirefire bootloader, I then went on to make a backup and flash the smoothrom rom and g apps. Everything was fine except that I noticed when the screen would turn off with the 30-second timer, it wouldn't "suspend" the kindle, but completely turn it off; in addition it sometimes happened when clicking the power button. I also encountered that whilst using the stock wall charger either letting it lock, or using the button the screen would go gray and not suspend, which sometimes followed by turning off completely.
I've done a clean install 5 times, and even installed the CM10 Hellfire rom to see if that one was free from the grasp of this bug, but it also shares the same fate. Does anyone have a solution to this, because I've searched the forum, and the threads themselves and it seems like I'm the only one suffering from this.
In also turns off after 30 minutes of not using it?
Do you know how to get a logcat? Get one and put it in pastebin or something similar, and post a link here. Don't post your entire logcat here.
Also, what is your governor set to?
http://pastebin.com/ihqRfzWz
Bowsa2511 said:
http://pastebin.com/ihqRfzWz
Click to expand...
Click to collapse
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
soupmagnet said:
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
Click to expand...
Click to collapse
This has happened on all the roms I've tried, the governor is "interactive-cfq", the minimum is 300 and max 1200. The problem doesn't occur when it's plugged in, but occurs when it's not; what I mean by this is that when the 30 second screen-off timer sets off, instead of just locking the device, it turns off completely and I have to boot the kindle once more. Pressing the lock button on the bottom also triggers this and I've tried clicking "fix permissions" in twrp to see if that does anything, but it doesn't.
soupmagnet said:
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
Click to expand...
Click to collapse
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Bowsa2511 said:
This has happened on all the roms I've tried, the governor is "interactive-cfq", the minimum is 300 and max 1200. The problem doesn't occur when it's plugged in, but occurs when it's not; what I mean by this is that when the 30 second screen-off timer sets off, instead of just locking the device, it turns off completely and I have to boot the kindle once more. Pressing the lock button on the bottom also triggers this and I've tried clicking "fix permissions" in twrp to see if that does anything, but it doesn't.
Click to expand...
Click to collapse
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
twa_priv said:
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Click to expand...
Click to collapse
The computer doesn't even detect the kindle via adb, or any types of mounting anymore; I only followed the instructions, wiped what needed to be wiped, installed the rom, then gapps and rebooted. Even in it's pristine state it still suffers from the problem.
soupmagnet said:
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
Click to expand...
Click to collapse
I've also tried doing that with SetCPU to see if it was the slowness of 300mhz causing the SoD, but the same symptoms occured
Edit: I'm going to download today's build, with the latest g apps then do the following:
•1. Wipe factory reset.
•2. Wipe cache.
•3. Wipe dalvik.
•4. Wipe system.
•5. Flash Rom zip.
•6. Flash gapps zip.
•7. Select reboot, then system if prompted.
Doing that would technically be doing everything in the pristine manner (Unless I have to change a frequency or governor?)
Just in case you missed it...
soupmagnet said:
...try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
Click to expand...
Click to collapse
soupmagnet said:
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
Click to expand...
Click to collapse
soupmagnet said:
Just in case you missed it...
Click to expand...
Click to collapse
Here's the log
twa_priv said:
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Click to expand...
Click to collapse
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
twa_priv said:
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
Click to expand...
Click to collapse
I occasionally get a sleep of death as well. I have had it happen with the CyanogenMod Nightly dated cm-10.1-20130311-NIGHTLY-otter.zip. It did not happen when my kindle was running the stock rom. I'm still working to get fully up to speed on how to chase this sort of thing, and all of you guys posting helpful info is appreciated.
twa_priv said:
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
Click to expand...
Click to collapse
I flashed the stock rom, and the modaco gr9 rom and the problem doesn't persist on either, i'm going to flash CM10 once more and do that
Interestingly enough, this 4.1 build doesn't have the sleep of death, wonder what the difference is
http://goo.im/devs/loosethisskin/otter-cm10/cm-10-20121211-1416-otter-sgt7.zip
Interesting, I may try that one if bumping up the governor to 600 does not solve the problem.
Sent from my Amazon Kindle Fire using XDA Premium HD app
muiriddin said:
Interesting, I may try that one if bumping up the governor to 600 does not solve the problem.
Sent from my Amazon Kindle Fire using XDA Premium HD app
Click to expand...
Click to collapse
Yeah i tried everything from trying out kindle roms, 4 different roms , gapps, permission fixing, dreamscape settings; inactivity settings, governors and clock frequencies, they all have the same problem. That test build i posted has been running perfectly all day now! No bugs with or without charger and no sleep of death! Its 4.1.2, but that is worth not having an unusable kindle
Don't forget to flash the CM10 (4.1) gapps
After one and a half days of testing I have not gotten a SOD with twa_priv's rom from this forum here:
http://forum.xda-developers.com/showthread.php?t=2051331
To be specific, I'm using 20130323-2135-otter-sgt7.zip with gapps-jb-20130301-signed.zip
This is running 4.2.2 instead of 4.1.2. If I do get one I will probably start running soupkits logcat script to chase the issue further.
Okay this morning before work the device appears to be in a SOD. Hopefully I have time to look at it tonight when I get home. It did go for around four days before this happened.
This one was different from the past my battery was down to 0% even though it was on a charger?
I managed to get it recharged only by plugging it into a computer for a while.
Sent from my KFTT using Tapatalk HD
Yesterday, I had re-installed from scratch (0.36) and rooted.
My Google Play-systemupdate was DOWNGRADED from September back to August (as reported by others).
Today, during a boot of the phone, the Google logo appeared during the boot animation with a small moving line indicating "something" was happening.
However it kept going for a couple of minutes like that ...
I looked into the logcat and saw:
Code:
11-13 11:47:21.196 926 926 I update_engine: [INFO:cleanup_previous_update_action.cc(124)] CleanupPreviousUpdateAction scheduled task ID 123 for WaitBootCompleted
11-13 11:47:23.199 926 926 I update_engine: [INFO:cleanup_previous_update_action.cc(112)] Executing task 123
11-13 11:47:23.202 926 926 I update_engine: [INFO:cleanup_previous_update_action.cc(124)] CleanupPreviousUpdateAction scheduled task ID 124 for WaitBootCompleted
11-13 11:47:25.205 926 926 I update_engine: [INFO:cleanup_previous_update_action.cc(112)] Executing task 124
11-13 11:47:25.208 926 926 I update_engine: [INFO:cleanup_previous_update_action.cc(124)] CleanupPreviousUpdateAction scheduled task ID 125 for WaitBootCompleted
11-13 11:47:27.211 926 926 I update_engine: [INFO:cleanup_previous_update_action.cc(112)] Executing task 125
11-13 11:47:27.216 926 926 I update_engine: [INFO:cleanup_previous_update_action.cc(124)] CleanupPreviousUpdateAction scheduled task ID 126 for WaitBootCompleted
And it kept cycling and counting up ...
I guess that it was trying to update (something? Play-systemupgrade?) but got stuck.
So I just rebooted from adb and then the phone booted normally.
Strange! I wonder if some differences of what was on slots a and b were related to this issue, although I wouldn't understand how or why since flashing the .036 firmware should reset everything everywhere. Thanks for sharing. I wonder if any more knowledgeable folks will have any ideas.
OK ... fixed ... did a factory reset ... was upgraded from Play-systemupdate September -> November.
This time it was kept after reboot (even when rooted) so looks OK right now.