Related
I starting a bounty for fixing the android os bug.
Anyone that fixes this bug gets the bounty. (not samsung or google tho)
Donations so far:
Doc 30$
dan13l 30$
TML1504 30$
Has anyone checked to see if its google maps chewing it up? It did this on some other phones with the latest update.
neubauej said:
Has anyone checked to see if its google maps chewing it up? It did this on some other phones with the latest update.
Click to expand...
Click to collapse
Keep the discussions in the other threads.
But maps is not the cause.
Switch Wifi sleep policy to "never sleep"
From the page for this issue on Google Code (others have linked to this page already but apparently no one here has bothered to actually read it):
code.google.com/p/android/issues/detail?id=15057
There appear to be two main causes of extreme battery consumption by the Android OS process.
#1 is the Wifi sleep policy of "wifi off when screen off", which is usually the default. If you haven't made a point of changing yours, it's probably still on this setting. In the Wifi settings page (where the SSID list is), press menu, then advanced, then Wifi sleep policy. Change it to "Never". A more blunt-force solution is to keep Wifi switched off all the time.
#2 is some combination of Google Latitude and location services (GPS and Wifi). This one seems to be less common and many people say it's definitely not the problem. It may be related to #1 in that a problem with the Wifi is causing location requests to fail, somehow causing extra processing.
Comment 23:
The increased consumption only occurs, when I have the wifi sleep policy set to "sleep while display is off". In this case the battery consumption is very high while the display is off.
Comment 31:
Only changing Wi-Fi sleep policy to Never from "Never when plugged in" fixed this for me for now.
Comment 40:
I can confirm that "Always on" WiFi policy solves the problem for me
Comment 53:
By putting "always on" to the wifi sleep policy, I'm now at 25% battery after 1 day 7 hours of usage (since last charge)
Comment 54:
The recommendation of changing the wifi sleep setting to 'Never' appears to have worked for me as well.
Comment 88:
Both "always on wifi" as well as "turning wifi off manually" work for me. The heavy battery drain only occurs in combination with the "wifi sleep while screen is off" policy.
Comment 90:
I have 'never sleep' policy for WiFi, and battery life is just fine.
Phone easily can sustain a day with some 40% battery remaining.
Click to expand...
Click to collapse
And so on...
A poll to see whether these solutions work for everyone would be good. I probably can't make it because I just registered.
Disclaimer: I have ordered but not yet received my Galaxy S II. The info in this post is not my firsthand knowledge, just some quick research.
ninewise said:
From the page for this issue on Google Code (others have linked to this page already but apparently no one here has bothered to actually read it):
code.google.com/p/android/issues/detail?id=15057
There appear to be two main causes of extreme battery consumption by the Android OS process.
#1 is the Wifi sleep policy of "wifi off when screen off", which is usually the default. If you haven't made a point of changing yours, it's probably still on this setting. In the Wifi settings page (where the SSID list is), press menu, then advanced, then Wifi sleep policy. Change it to "Never". A more blunt-force solution is to keep Wifi switched off all the time.
#2 is some combination of Google Latitude and location services (GPS and Wifi). This one seems to be less common and many people say it's definitely not the problem. It may be related to #1 in that a problem with the Wifi is causing location requests to fail, somehow causing extra processing.
And so on...
A poll to see whether these solutions work for everyone would be good. I probably can't make it because I just registered.
Disclaimer: I have ordered but not yet received my Galaxy S II. The info in this post is not my firsthand knowledge, just some quick research.
Click to expand...
Click to collapse
These fixes wont cure it for sgs 2.
See attached. It's not the wifi policy.
I too will pledge $30 for a working fix once I've verified that the problem is solved.
Sent from my GT-I9100 using XDA Premium App
dan13l said:
See attached. It's not the wifi policy.
I too will pledge $30 for a working fix once I've verified that the problem is solved.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Nice, i will update 1st post with all the findings so far.
"android os" bug is NOT:
Wifi bug (always on)
Maps bug
Any installed apps bug
Operator bug
Latitude bug
count me in with $30 as well
DocRambone said:
Nice, i will update 1st post with all the findings so far.
"android os" bug is NOT:
Wifi bug (always on)
Maps bug
Any installed apps bug
Operator bug
Latitude bug
Click to expand...
Click to collapse
I had similar issue on SGS, my problem was because aparently I got a faulty modem file, I noticed my signal bar going up and down continously.
Has anyone tried changing modem?? I don't have a SGS2 so I don't really know if there are modems to choose from...
Good Luck Doc.
gtluis said:
I had similar issue on SGS, my problem was because aparently I got a faulty modem file, I noticed my signal bar going up and down continously.
Has anyone tried changing modem?? I don't have a SGS2 so I don't really know if there are modems to choose from...
Good Luck Doc.
Click to expand...
Click to collapse
Getting a good idea now, a first setup on 3g network (no wifi), avoid the dir 655 routers and you be fine.
Wifi policy is set to "never" by default, so I can't see why it would help anyway.
That said with KE1 and a factory reset, although I have higher than would usually be expected AOS usage, my battery drain issue hasn't been all that bad - from a full charge today (7hr 15 on battery) to 83% with maybe 20 minutes angry birds, and the occasional checking of emails, texts and facebook and playing around with it a bit...
Screen on time 31 minutes... Android OS at 20% now and Wifi Sharing(!?) on 13%.
So not too bad, but it could be better IMHO - equates to about one and a half days of light use - definitely room for improvement.
There are so many threads about battery so not sure which one I should post it but..
I saw some strange things in Logcat. I get alot of those errors :
E/lights ( 2701): write_int: path /sys/class/backlight/pwm-backlight/brightness, value 170
E/lights ( 2701): write_int: path /sys/class/leds/blue/brightness, value 0
I don't exactly know what the error means(well they are related to the menu and return backlight I think), but the E/ stands for error in case you didn't knew.
Do you guys get the same kind of errors in logcat?
I've noticed 2 things:
If I wake it up, the cpu frequency doesn't go below 800mHz. (with only 4% load)
Only after I've started an app (not a widget etc.) it went down to 200.
(look at the "Temp+CPU V2" widget on the screenshot)
And the camera seems to run further if you don't go back out.
After a shot in school, I pressed the power button and at home, it felt VERY hot (front and back) and the battery level went down in 3% steps every 1-2 minutes.
But the camera wasn't listed in the battery stats, only Android OS, which was eating 70%.
Screenshot
Android OS Battery bug
Hi!
1. Install SystemPanelLite Task Manager from the market.
2. Run SystemPanel and open settings and check the "System processes" option. Close settings.
3. Scroll down in the process list until you find the process "android.process.media". If you have a CPU usage of more then 10-30s and the process usage gauge to the left moves up and down you probably have the Android OS battery bug.
At this point you can try the following;
- Shut down your phone. (Not just turn it of. The complete shut-down-power-off-thingy)
- Remove your external SD card.
- Start up your phone again.
- When the scan media is complete, do step 3 above again. If you don't see the problem at step 3 your SD card has a corrupt filesystem. And needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Unmount SD card
- Format SD card
- Restore files from your backup.
If the problem persists your internal SD card might have a corrupt filesystem and needs to be reformated. Follow these steps;
- Backup your data first!!!
- Settings -> SD card & phone storage
- Format internal storage
- Restore files from your backup.
More details; What happens when you have a corrupt filesystem is that android.process.media tries to read a file but fails over and over again. The filesystem might not look corrupt to you. And you can read and write files on the SD card without problems. But at some point the android.process.media failes to read the files and loops like crazy, draining your battery.
I had a corrupt filesystem (FAT32) on my external SD card. I also had Android OS battery usage of 60-70% and a fast draining battery. I hope this can help others.
Best regards,
/Pontus
My android.process.media is 27 secs. Is this in the acceptable range?
Hi!
It's a bit high I'd say. I've got like 2000+ photos and I'm at 9 s after a days use.
Take a look here;
Settings -> Applications -> Battery usage
If Android OS is above 50% then you should consider my suggestions.
Most importans, does your phone get hot and use a lot of battery without heavy use?
Removing your external SD card and rebooting your device isn't that much work. If that gets rid of your problems, then reformat your SD card.
FAT32 isn't the most robust filesystem.
Best regards,
/Pontus
how can i remove the languages which i dont need?
what's causing the battery drain inside Android OS
After doing further investigations with watchdog, the Android OS battery drain is caused in stand-by by:
1. suspend (linux process)
2. events/0 (linux process)
They use heavily the processor while in standby... I've seen alert of up to 80% of CPU in both processes.
Not sure how to search on the XDA app, so please forgive me if this is already a topic... does anyone have any tips/tricks for avoiding the Sleep Of Death?
-XDA Premium on CM7 Nook Color
What version CM7 are you on?
Latest SOD fixes were put into a kernel which is available as separate zip but have not made it into a nightly build as the build has not been working since mid November.
You may be able to use the kernel update if you are on a fairly recent version or you could switch to the KANG MiRaGe ROM which does include the kernel fix together with other improvements which have not made it into a nightly. Look for the main MiRaGe thread in the development forum.
Other than that before applying this kernel fix people were using various techniques for switching wifi off rapidly when suspending which seemed to be a work-around.
I haven't had a SOD since using the new kernel when it first appeared and as now as embodied in MiRaGe.
I'm on cm7.1.0, I don't get SOD all the time just on occasion without pattern
-XDA Premium on CM7 Nook Color
Widgets...
Don't use Beautiful Widgets. That causes SoD's. Other widgets may cause the same problem.
I have found that every widget that has weather causes SOD for me. All others are okay.
Sent from my NexusHD2 using xda premium
I had to switch ROM's from MIUI to Phiremod to get this to stop. Works fine now even with Beautiful Weather Widget active.
The KANG ROM you describe is the one I have been on since it was introduced. I had the SOD fix but it still occured albeit infrequently. My "fix" is to just shut my Nook down every night. I haven't had one since.
Setting wifi to shut off when screen goes off also works for me (the issue seems to be wifi related). You can also use tasker to shut wifi off when the screen turns off.
Both beautiful widgets and the go weather widgets have caused the sleep of death for me. Without any widgets, my Nook would be up for weeks at a time.
stephen_liu said:
Setting wifi to shut off when screen goes off also works for me (the issue seems to be wifi related). You can also use tasker to shut wifi off when the screen turns off.
Both beautiful widgets and the go weather widgets have caused the sleep of death for me. Without any widgets, my Nook would be up for weeks at a time.
Click to expand...
Click to collapse
Indeed the tasker wifi fix worked for me
-XDA Premium on CM7 Nook Color
vessamj, could you explain what you did with Tasker to prevent SOD?
Quick Tasker fix for SOD
Thomas Droid said:
vessamj, could you explain what you did with Tasker to prevent SOD?
Click to expand...
Click to collapse
Certainly...
I'm assuming you have a basic understanding of how to use Tasker, if this is not so please let me know and I'll be more in-depth. I created a profile named WIFISLEEP with the condition being "Display Off". The first step of the internal task is to wait 5 minutes, with the "IF" box checked and the "IF" condition reading "%SCREEN ~ off". The second step is to set Wifi to off, with the same "IF" condition as the first step. The third step is to play a notification sound (not required, but nice to be assured that your profile actually executes), with the same "IF" condition as the first two steps. I already had a "Display On" profile (for setting the CPU governor and speed), so I just added the next part to the pre-existing profile. If you don't already have such profiles you can just create another profile (named something like "Display On"). The condition, of course, being "Display On", and the first task being "WiFi set On" with the "IF" condition being "%SCREEN ~ on". The second task being "WiFi Net Action Reconnect", with the same "IF" condition as the first task. Not only does this fix my SOD problems, but it will also save you quite a bit of battery when not in use for long periods of time. There will be a slight (10-20 sec.) delay waiting for the WiFi to reconnect after you turn the screen on (as long as it's been more than 5 min of course), but it's definitely worth it. The reason I have a 5 minute wait is so that downloads can finish before they are cut off, you can set the wait time longer if your downloading times take longer. Overall, this did the trick for me on SOD.
*EDIT* I did also get ahold of a much better WiFi management application called Green Power. Instead of having Tasker turn off the WiFi after 5 minutes of the screen being off no matter what, Green Power throws in a few more conditions to look for. Through Green Power I have it set to turn off the WiFi after 20sec of the screen being off IF WiFi traffic is at 1Kb or less. If it is not at 1Kb or less, the app will re-check the traffic every 10sec until it is at or below that level, then shut it off. Also, while the display is off, Green Power will re-enable the Wifi for 2min every 30min to allow data sync to occur. When the screen is turned on, WiFi will be re-enabled automatically. However, if the device can't successfully connect (after 30sec) OR if the strength at connection is less than 20% signal, the WiFi will be temporarily disabled so that there is no battery wasted continually trying to connect/stay connected. This setup is perfect for finishing a download after the screen goes off and then putting the WiFi to sleep, and quickly giving up on the reconnect if there is low/no signal and trying again later. This also fixes the SOD for me, with better overall management than what Tasker can provide as far as WiFi is concerned.
Hey guys, just wanted to post what I used to fix my problems related to SoD.
I was getting SoD all the time with any ROM that I used, no matter 7.1.0 or 7.2. So recently i started fresh on a 7.1.0 stable rom and moved the ROM from SD to EMMC, but the problems still persisted.
After seeing this thread, it gave me some insight regarding the root problem... For me, it seemed that wifi being on when the screen was off was the culprit. So I downloaded the free app called "Easy Battery Saver+ Task Killer" found here:
https://market.android.com/details?...SwxLG51bGwsImNvbS5lYXN5LmJhdHRlcnkuc2F2ZXIiXQ..
I set it to the "General Power Saving Mode" profile, which basically turns off the wifi whenever the screen is off.
That seems to have fixed the problem, now I never get a SoD! So I recommend giving it a try!
If you are interested in my opinion...
switch81 said:
Hey guys, just wanted to post what I used to fix my problems related to SoD.
I was getting SoD all the time with any ROM that I used, no matter 7.1.0 or 7.2. So recently i started fresh on a 7.1.0 stable rom and moved the ROM from SD to EMMC, but the problems still persisted.
After seeing this thread, it gave me some insight regarding the root problem... For me, it seemed that wifi being on when the screen was off was the culprit. So I downloaded the free app called "Easy Battery Saver+ Task Killer" found here:
https://market.android.com/details?...SwxLG51bGwsImNvbS5lYXN5LmJhdHRlcnkuc2F2ZXIiXQ..
I set it to the "General Power Saving Mode" profile, which basically turns off the wifi whenever the screen is off.
That seems to have fixed the problem, now I never get a SoD! So I recommend giving it a try!
Click to expand...
Click to collapse
The problems I see here are that there is no WiFi traffic check (at least from what you've explained) before it kills the WiFi, and the Task Killer part. Task Killers actually cause more battery usage because the Android System will have to use more battery to re-start many of the killed processes. This is because the OS is programmed to keep some/most of those background processes running and will continually re-start them no matter how many times a task-killer stops them. It is better to have apps such as Ram Manager Pro (http://forum.xda-developers.com/showthread.php?t=1111145) or V6 SuperCharger script (http://forum.xda-developers.com/showthread.php?t=991276) to optimize your RAM for much better smoothness and crisp response, with much better battery savings. Combine one (or both depending on what parts you use for different activities) with Green Power app, which will give a hand-full of extra conditions to look for before turning off the WiFi at screen off and thus fixing your SOD and providing better performance with extra battery savings. I hope this helps!
I've been having a recurring problem where my phone will lock up in a deep sleep, leaving the phone completely off. In order to restart the phone, I have to hold Power and Vol Down which takes me to a charging logo, and then hit power again. This generally happens overnight when the phone is charging, but I've also had it happen once while making a VoIP call. I thought I resolved the issue by wiping the phone and flashing the stock 4.2 ROM. However, the issue just occurred last night after 4 days of bug-free usage.
My question is whether this is some sort of weird software bug or a hardware issue. I haven't seen others report identical behavior but I've seen lots of complaints about freezing and random reboots that seem to be due to software. Should I request an RMA?
+ 1 . I am having the same issue. I would say hang tight. Call the support team and let them know you are having issues. If atfer a few weeks the problem persists perhaps go through an rma. I suspect it is software related. Lets say you did RMA still had the issue then had a dead pixel or other problem? It would suck and you would have to go through the whole process again. rinse and repeat. Only if you want to return the device for a full refund, then I would say hurry up and make that call. My .02 Good luck.
NexUsandThem said:
+ 1 . I am having the same issue.
Click to expand...
Click to collapse
+1
Having the same issue. Although no clear pattern is visible. Sometimes I find the phone dead-locked after putting it aside for 10 minutes and sometimes it seems to run for a day or even two without issue. Running _motley kernel right now without any change on this front.
I rather think it's a software issue than hardware. So I am not going to RMA it.
Strangely when I power off the phone on such a lock-up and then reboot it I will see a substantial drop in battery after the reboot. So the phone seems to be in some state where it still drawns more battery than in normal operation. E.g. with _motley kernel and limited clocks I typically see 3-5% battery drop over night only. When it locks up during the night and I reset it in the morning then battery usually drops much more (e.g. 30-50% is gone). Maybe it's caused by some hanging/deadlocked driver.
If you full factory reset and flashed then i'd say some app of yours is causing the issue.
shotta35 said:
If you full factory reset and flashed then i'd say some app of yours is causing the issue.
Click to expand...
Click to collapse
In fact I got the device in dec 2012. Started to set it up and then decided to root it (including full factory reset). I only have a very minor amount of system-level applications installed. Actually the main reason to root was to use Voltage Control as I intended to limit clock rates and (if possible) voltages the same way I was used to do it on my Galaxy Tab 7 (P1000) where I was very pleased with 6-days battery lifetime.
Initially I found the minimum clock rate was set to 1GHz and I have reduced it to 304MHz (minimum with stock kernel). When I discovered first freezes/lock-ups then I reverted to default settings and found it still locking up occasionally. Meanwhile I am using _motley kernel which seems to include some voltage mod as well. Although Voltage Control does not show options to modify voltages. Then I found Trickster MOD which shows some voltage control but it seems to have no effect (at least I was used my galaxy tab to crash when undervolting too much and it's pretty "strange" to be able to set all clock voltages to 0.6V while still running stable; so I guess the settings won't have any effect right now).
I have also tried to remove all modifications and applications and/or profiles which could cause the issue without any difference. Even when run stock settings it occasionally completely locks-up the device.
Edit: I was wrong regarding voltages. In fact I found my device happily works at 1134MHz using 600mV. Since I am used to limit max clock rates to 810MHz I could simply put all voltages to 600mV without seeing a crash/reboot.
CAUTION: This does not necessarily have to apply to all devices. My one is "faster" binned Rev. 11 device. Some voltages of different users are collected here: https://docs.google.com/spreadsheet/ccc?key=0AnlqtEwFJwR6dE55WkZYSThEM3U4SGtKMVl2V1VqMmc#gid=0
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
nando_pt said:
Hello!
I bought Nexus 10 at nearly two weeks, and since the beginning i have noticed an issue i thought would be Software related. As the device is on idle, everything works pretty well. Watching movies, web surfing, etc. Doesn't matter if it's for 5mins or 5 hours. But when it goes to sleep mode (automatically or forced by me), it just turns off consequently. I would say 90% of the times. An then Nexus just turn back to life after a long power button press, like 10 secs or more.
First i read about some people who have problems caused by autosleep function related with some cases. When i remove my tablet from the Poetic case, it keeps going off.
Then i read about Location services. It's turned off too. Such as the wi-fi in sleep mode. Didn't solve either.
Any idea?
PS: I'm from Portugal and my English is not the best. Sorry about that.
Click to expand...
Click to collapse
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
bigmatty said:
You can view my profile for my posts I've been working on that problem for over month. Sorry this is short reply - pressed for time right now.
Click to expand...
Click to collapse
Thanks for the response anyway.
Is that thread about freezing? My Nexus is not freezing.
Hello! Yes, that is one of the threads Im talking about. I found it to hard to find people who posted with as good of detail as you did, so I had to "latch on" to the biggest group that was vocal about their problems. But mine manifests itsself almost always as sleep of death, and NOT reboot - just like yours. Here are some links:
Google: https://groups.google.com/a/googleproductforums.com/d/msg/mobile/-/GFnACv1nC0MJ
On of the XDA: http://forum.xda-developers.com/showthread.php?t=1998496&page=39
As I say on the Google thread:
My thoughts on the error:
1) The most logical explanation I've heard yet is the memory leak that B has been posting about
2) I think this memory leak/problem can manifest its self as crash, reboot, or sleep of death
Right now I am trying Stock 4.2.2, rooted, using KTmanta kernal. This is the second day Im on a non-stock kernal, too early to post any useful info.
Good luck on this,
bm
---------- Post added at 02:09 PM ---------- Previous post was at 02:05 PM ----------
say, quick question since you are in same boat as me - does your device's serial # start with R32C or R32D?
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
nando_pt said:
My device is R32D.
I guess i will call the seller tomorrow and figure out if it's possible to return the tablet. At this point, it's completely unusable.
Click to expand...
Click to collapse
I agree that the inability of this device to reliably stay powered on is a deal breaker, at least in a work scenario.
I actually bought mine "just for games", but have been really concerned about trying to resolve this issue to verify its not a hardware issue and I miss my warranty period. I cant honestly say I think its a harware issue, so I am really trying to find a ROM/Kernal/settings combo that resolves this.
I have a lot of faith in the dev community for ROMs and kernels, but I think its absolutely scandalous and horrible that I have to click past a warning that says 'may void your warranty' to install softare on my device to make it perform AS IT SHOULD HAVE direct from Google.
If not for all these issues I would have NEVER gone custom recovery, root, and new kernel. Im glad this has forced me to do so because Ive loved finally having a justification for "risking" my expensive device, but again that learning experience is NOT what Google is taking $500 payments for here https://play.google.com/store/devices/details?id=nexus_10_32gb so Google should be SHAMED!
Thanks for the info on your serial number, that actually relieves a concern of mine that somehow the 'newer' units werent having this problem. Mine's a C.
bm
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
jamir5 said:
just bought my nexus 10 yesterday. it also turning off when sleepmode. but when i update it to 4.2.2 its gone.
Click to expand...
Click to collapse
I hope it stays that way for you. It will take a few more days with the device to know for sure. If the problem comes back it'd be worth noting here for troubleshooting. :good:
I called back the seller, and they will do the return. Really bad situation...
i left my n10 in my house and its idle with 41% on battery i just got home and open the device it consume only 1% without random reboots. hope itll stay this way ill root this and install crom maybe nextweek.
So - now I am 2.5 days into testing 4.2.2 OS with a different kernel. And so far, NO sleep of death! AND I've been using the tablet a lot more than my "minimal use" in my other tests! This of course is the ultimate test - I'm posting/talking about it on the internet so certainly if its going to blow up in my face, now would be the time. But as of right now - it looks like the alternate kernal is better for my device than Google's...
I am using the KTmanta kernel.
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
neatchee said:
It is important to note that the issue described in this thread does NOT involve the device turning itself off. Rather the issue is that the device is unresponsive when in sleep mode. You can tell this is the case in a few ways, but two obvious ones are that the notification light continues to function and the device requires a 10-second power button reset (the procedure for forcibly rebooting the device).
Personally, I am on CM10.1 night lies with Ktmanta kernel and still experiencing this problem.
Bigmatty, can you tell me what governor, i/o scheduler and clock settings you are using? Thanks.
Click to expand...
Click to collapse
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/clock settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Oh, and the LED flashing does not mean the unit is actually on, you can test that by plugging in a charger before attempting a long (power on) press = if you get instant battery charge indicator your unit was actually off.
bigmatty said:
Well, the majority of the complaint threads do not specifically or mainly focus on the device turning its self off, but this thread actually does.
My sleep- of- death problem on my old unit persisted on any scheduler/click settings I tried, and I tried a lot w/ KTmanta. But it was RMA my device to get a new one that fixed my SoD.
Click to expand...
Click to collapse
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
neatchee said:
That's REALLY weird, because based on a number of findings by a number of people, it turns out that this issue is related to a bug in the GPU driver that is causing a massive memory leak. You can check by opening a Terminal Emulator and running the command "ps su" This will show the memory usage for the "surfaceflinger" application, which is where the memory leak manifests. Memory usage should never go above ~70mb for that application, but on the N10 it balloons up above ~300mb before the system locks up.
Apparently we're all waiting on Samsung to fix the problem :\
Click to expand...
Click to collapse
After my two months of trouble shooting I feel strongly that there are two main issues: memory leak and "something to do with power". Likely a software/driver/OS problem on the memory leak like the majority says. BUT - not everyone has the power problems. I think the power problems are hardware related.
Only a couple other users have talked about experiencing the power problems...
If I was going to place a bet, I'd say based on your description of symptoms you too have the power problem. Ask the others in threads you are following if they have the LED thing, I'm guessing they don't.
Rxnelson on these forms does. He's seen it on two physical units. For me, it didn't appear on my second physical unit.
Good luck!!
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Also please note the tip I shared about diagnosing if it's off or on via the charger I posted above, handy trick another user taught me.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
neatchee said:
"LED thing?" The LED thing is just the notification light continuing to flash even when surfaceflinger has locked the system. Don't really see how that's related to power in any way. The way that LED notification lights work is that the system sends an "on" signal to the LED control chip which then just runs the notification light pattern in a loop until it receives the "off" signal from the system. If you don't have any notifications prior to surfaceflinger going ballistic, or if you have the notification light disabled (many people do) you'd never notice this particular symptom.
Click to expand...
Click to collapse
Not quite what it seems. If the unit was on, plugging in the charger would not instantly,w/out delay, display the powered off charging indicator.
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
neatchee said:
Ahh, okay, bit of a miscommunication. I'm not referring the power-on notification light. I'm referring to the notification light flashing that occurs when you have a notification waiting (new email, new gTalk message, etc). The charging light is something different, and not what I was referencing
NOTE: This is a function of CyanogenMOD 10.1 that is not present in the stock ROM, I think, so that may be where the confusion lies. Sorry about that
Click to expand...
Click to collapse
Yes dude, I understand. Just test what I am saying. When I saw my white gmail led flash, but then couldn't turn on I thought the exact same thing you typed. Then while discussing w/power users someone told me to try that. Next time it happened I tried it, was SHOCKED to see what happened, knew I had a problem (that was not just shell reboot.)
My tablet just started doing this as well. It's never done it before, it started about a week ago. What could be causing this? I just factory reset to see if it'll fix the problem. I'll report back in a few days to see if this fixes the issue.
Sent from my Nexus 10 using xda app-developers app
I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup
TheNupster said:
I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup
Click to expand...
Click to collapse
A factory reset is probably the next step if you prefer not to root. Also try to identify the source with a monitoring app like BBS or GSAM (I prefer the latter). You'll need to grant a few extra permissions via ADB on an unrooted device to get the full picture. GSAM walks you through the procedure via the overflow (3 dot) menu. Good luck.
I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?
TheNupster said:
I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?
Click to expand...
Click to collapse
If it's the 1768 then the retail firmware should be fine (I'd say preferable even). Unless you need that extra software that is.
After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)
TheNupster said:
After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)
Click to expand...
Click to collapse
Did you grant permissions (via ADB) to allow GSAM to disambiguate resource consumption on an unrooted device. Try using Greenify to rein in bad app behaviors. Works a treat on rooted devices and *should* be effective on user installed apps if unrooted.
I'll try that. And yes, despite using my laptop to give GSAM permissions, it only showed Android system as using the power. I'll install Snapchat, see if the problem appears again, open GSAM, and give it some time. I'll also install the other app and set that up too.
Between those two, I should be able to determine if Snapchat is causing this issue; and if so, what part is. (Phone is unrooted, because I don't want to void warranty (Motorola needs to give me the key to root, and I don't want to do THAT just yet) so we'll see what happens)
Okay. After extensive testing, the phone has finally "cooled down". Snapchat no longer hogs battery, and now I get more battery life than before this problem even began. I wonder if, somehow, somewhere, a system file became corrupted, instead of Snapchat causing the problem...
Whatever the cause, a full system reset forced the loop to break.
Now I'll use Snapchat (and every other app) with caution now... I have a CPU monitoring app running 24/7 (it uses almost no battery)
Feel free to close this thread