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
Related
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
Setting a static IP fixed it temporarily but now it doesn't work again.
Hi, I'm new to this so I hope I'm posting in the right place. I have an HTC Desire running AdamG's Oxygen v1.0.4, but I'd like to put some of the old HTC apps back on the phone, like the music player/widget, news and weather app/widget, etc..
So what I've done so far is extracted the system.img file from my Nandroid backup with unyaffs to get the apk files. I then put the app folder back onto my SD Card and tried to use Root Explorer to copy the apks I wanted back into the system/app folder on my phone, but when I try this, nothing is copied across. I have it in R/W mode and it flashes pasting quickly on the screen but when that disappears, there is no copied app and no less space in the folder.
Is it even possible to install HTC's system apps onto a different version of android? If so, what am I doing wrong? Also, if I do manage to copy the apks into the system/apps folder, do they need the corresponding odex files to work?
Thank you.
I've been trying to do the same thing. I unyaff'd the image, then tried 'adb install HTCAlbum.apk'
This fails with "Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]"
Googling around says this is to do with it not being signed. However checking this with "jarsigner -verify -verbose -certs HTCAlbum.apk" shows it is signed OK. Have tried re-signing it too, but that made no difference.
logcat output from the install:
Code:
D/AndroidRuntime( 1943): >>>>>> Booting Oxygen by AdamG <<<<<<
D/AndroidRuntime( 1943):
D/AndroidRuntime( 1943): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 1943): CheckJNI is OFF
D/dalvikvm( 1943): creating instr width table
D/AndroidRuntime( 1943): Calling main entry com.android.commands.pm.Pm
D/dalvikvm( 1485): GC_EXPLICIT freed 5K, 54% free 2558K/5511K, external 1625K/2137K, paused 24ms
W/ActivityManager( 147): No content provider found for:
D/dalvikvm( 147): GC_EXPLICIT freed 120K, 44% free 6780K/11911K, external 4453K/5026K, paused 75ms
D/AndroidRuntime( 1943): Shutting down VM
D/dalvikvm( 1943): GC_CONCURRENT freed 212K, 71% free 301K/1024K, external 0K/0K, paused 0ms+0ms
D/jdwp ( 1943): adbd disconnected
There are several different provider apk's but they don't seem to install either...
Posting this in the hope this gives you a pointer and you get further.
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
+++++--------+++++
Hi All,
Having some issues with my phone. I'm on CNexus' 4.3 stock MK3 rom. The only mods I've done to it is disabling some of the bloat with TB and also have Wanam Xposed installed.
Note that I have seen this behavior on other roms too.
Usually within a day or 2 of doing a reboot, the "system" process will begin using 50% CPU all the time. No wakelocks show up in BBS, and "android system" doesn't show increased usage in the stock battery stats, however other apps can see it happening.
I took a few screenshots with System Panel to show - after running it's monitoring function for a few hours. I also used the command "top" in terminal emulator to generate a text file showing the results:
Code:
User 23%, System 34%, IOW 0%, IRQ 0%
User 13 + Nice 141 + Sys 228 + Idle 271 + IOW 0 + IRQ 0 + SIRQ 0 = 653
PID PR CPU% S #THR VSS RSS PCY UID Name
778 0 49% S 143 771668K 149192K fg system system_server
10258 0 4% R 1 1336K 644K root top
381 1 1% S 8 10628K 1808K root /system/bin/netd
8713 1 0% S 1 0K 0K root kworker/u:4
1668 0 0% S 5 5244K 608K root /system/bin/mpdecision
I have renamed qsiff_daemon to .bak to see if it would help with the issue, however it did not. Qosmgr file apparently doesn't exist in this rom.
As you can see in the screenshots, System is at maximum CPU (this is with my phone sitting idle), and it is using a lot of CPU time when my phone was otherwise doing nothing. I also attached a screenshot of OS Monitor showing the process in detail.
Does anyone else have this issue? Any ideas on how to solve it? I can't seem to find a way to get any details as to what "System" is and if there are sub-processes that make it up.
EDIT: More details. Ran Top again, this time so it would name the thread:
Code:
User 23%, System 38%, IOW 0%, IRQ 0%
User 14 + Nice 162 + Sys 284 + Idle 283 + IOW 0 + IRQ 0 + SIRQ 0 = 743
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
778 1283 0 48% R 779916K 146584K bg system CountryDetector system_server
12255 12255 1 8% R 1840K 1152K fg u0_a210 top top
8455 8455 0 0% S 0K 0K root kworker/u:3
778 903 0 0% S 779916K 146584K fg system er.ServerThread system_server
1668 1687 0 0% S 5244K 608K root mpdecision /system/bin/mpdecision
CountryDetector??
dirkdigles said:
Hi All,
Having some issues with my phone. I'm on CNexus' 4.3 stock MK3 rom. The only mods I've done to it is disabling some of the bloat with TB and also have Wanam Xposed installed.
Note that I have seen this behavior on other roms too.
Usually within a day or 2 of doing a reboot, the "system" process will begin using 50% CPU all the time. No wakelocks show up in BBS, and "android system" doesn't show increased usage in the stock battery stats, however other apps can see it happening.
I took a few screenshots with System Panel to show - after running it's monitoring function for a few hours. I also used the command "top" in terminal emulator to generate a text file showing the results:
Code:
User 23%, System 34%, IOW 0%, IRQ 0%
User 13 + Nice 141 + Sys 228 + Idle 271 + IOW 0 + IRQ 0 + SIRQ 0 = 653
PID PR CPU% S #THR VSS RSS PCY UID Name
778 0 49% S 143 771668K 149192K fg system system_server
10258 0 4% R 1 1336K 644K root top
381 1 1% S 8 10628K 1808K root /system/bin/netd
8713 1 0% S 1 0K 0K root kworker/u:4
1668 0 0% S 5 5244K 608K root /system/bin/mpdecision
CountryDetector??
Click to expand...
Click to collapse
Same issue here. I tried strace'ing the process, and it stopped spinning. I also could no longer wake my screen and performed a 'reset' from adb.
I was seeing a slew of "SensorManager Error: Sensor Event is null for Sensor: null" messages going through.
lsuchocki said:
Same issue here. I tried strace'ing the process, and it stopped spinning. I also could no longer wake my screen and performed a 'reset' from adb.
I was seeing a slew of "SensorManager Error: Sensor Event is null for Sensor: null" messages going through.
Click to expand...
Click to collapse
My error ended up having to do with location services... I ended up enabling "Access to my location" and "Use GPS Satellites" in location services, but left "use wireless networks" disabled.
Since then I have installed decimalman's 12/26 kernel. Running rock solid with no abnormal wakelocks since (however my idle battery life seems a little worse).
Right, so I've been an absolute idiot and I uninstalled mediatek-res.apk. I was probably very tired and I was stupid enough to forget to make a backup in recovery. The phone is a Chinese clone (Jiake JK3) and I can't find any stock firmware on the internet. It's now stuck in bootloop, so somehow I need to restore mediatek-res.apk so I can boot it up. I can get adb access with root when I'm in recovery. I've tried pushing it to /system/framework with the correct permissions, but that hasn't worked. The log (when I boot up) says:
Code:
D/PackageManager( 1699): scan package: /system/framework/mediatek-res.apk , start at: 66650ms.
D/asset ( 1699): AssetManager-->addDefaultAssets CIP path not exsit!
and
Code:
I/PackageManager( 1699): /system/framework/mediatek-res.apk changed; collecting certs
D/dalvikvm( 1699): GC_CONCURRENT freed 1976K (15855), 34% free 4069K/6124K, paused 1ms+2ms, total 19ms
and
Code:
E/PackageManager( 1699): Package com.mediatek has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 1699): Signature mismatch for shared user : SharedUserSetting{41de1470 android.uid.system/1000}
I have no idea what any of this means but I'm a fairly capable user so if someone could let me know what it means that'd be great.
mediatek-res.apk problem [FIXED]
rowan.allen.rules said:
Dude this is the easiest problm to fix
The path you have entered is incorrect
you enter:::: /system/framework/mediatek-res.apk
Should enter::::
PHP:
/system/framework/mediatek-res/mediatek-res.apk
This is because there is a folder mediatek-res and inside it there should be mediatek-res.apk:good:
Try this and if you could fix this error then leave a THANkS:victory:
Click to expand...
Click to collapse