Hi guys,
Please be patient with me, if this method is already well known, but as I neither found it here nor at one of my preferred german forums, I'll post it:
Since I updated from Honeycomb to ICS I have been extremely disappointed about the battery drain. My transformer never got to deep sleep, etc. YES, I KNOW there are several threads about this, talking about cpuspy, autoflightmode and so on, BUT for sure in my case and also for many many others the deep sleep problem hasn't to do anything with wlan...
So I tried several custom roms (actually I'm running Revolver 4) because I knew from the past, when Honeycomb itself has had this annoying problem, Revolver did it for me.
Well, Revolver 4 didn't...
So I did the following, please read carefully and don't only check IF this value is set at your devices and discard:
Go to developer settings (I'm german, may be my description doesn't match exactly) . There should be a point "display always on" or equal. The checkmark is NOT checked, when first installed stock or Revolver BUT for some reason I don't know, the transformer doesn't recognizy it's empty state. This is why it never sleeps and always wakes on mouse movement, etc. So you have to do the following easy steps: Check the checkmark (in words: ENABLE display always on) and directly after that (no need to switch to homescreen first) DISABLE it again.
This should solve the annoying problem with deep sleep and battery drain.
You can test it by turning off your display, wait several seconds, maybe up to a minute, and try keypress or mouse movement. You may NOT have the cable plugged in, it only works if on battery usage. The trasformer now should not wake up and after refreshing cpuspy stats you should see some seconds more deep sleep.
I hope this has helped someone as I for myself spent hours with autoflightmode and so on until I found out this simple and a bit strange trick.
greets,
Cutterfly
cutterfly said:
Hi guys,
Please be patient with me, if this method is already well known, but as I neither found it here nor at one of my preferred german forums, I'll post it:
Since I updated from Honeycomb to ICS I have been extremely disappointed about the battery drain. My transformer never got to deep sleep, etc. YES, I KNOW there are several threads about this, talking about cpuspy, autoflightmode and so on, BUT for sure in my case and also for many many others the deep sleep problem hasn't to do anything with wlan...
So I tried several custom roms (actually I'm running Revolver 4) because I knew from the past, when Honeycomb itself has had this annoying problem, Revolver did it for me.
Well, Revolver 4 didn't...
So I did the following, please read carefully and don't only check IF this value is set at your devices and discard:
Go to developer settings (I'm german, may be my description doesn't match exactly) . There should be a point "display always on" or equal. The checkmark is NOT checked, when first installed stock or Revolver BUT for some reason I don't know, the transformer doesn't recognizy it's empty state. This is why it never sleeps and always wakes on mouse movement, etc. So you have to do the following easy steps: Check the checkmark (in words: ENABLE display always on) and directly after that (no need to switch to homescreen first) DISABLE it again.
This should solve the annoying problem with deep sleep and battery drain.
You can test it by turning off your display, wait several seconds, maybe up to a minute, and try keypress or mouse movement. You may NOT have the cable plugged in, it only works if on battery usage. The trasformer now should not wake up and after refreshing cpuspy stats you should see some seconds more deep sleep.
I hope this has helped someone as I for myself spent hours with autoflightmode and so on until I found out this simple and a bit strange trick.
greets,
Cutterfly
Click to expand...
Click to collapse
This explains why I never had this problem but other people say they did. The first thing I did after I upgraded was go into the settings and played around with all these settings to make sure everything was what I wanted. So, without knowing it, I solved a problem before it even became a problem.
Good job in noticing this!
cutterfly said:
Hi guys,
Please be patient with me, if this method is already well known, but as I neither found it here nor at one of my preferred german forums, I'll post it:
Since I updated from Honeycomb to ICS I have been extremely disappointed about the battery drain. My transformer never got to deep sleep, etc. YES, I KNOW there are several threads about this, talking about cpuspy, autoflightmode and so on, BUT for sure in my case and also for many many others the deep sleep problem hasn't to do anything with wlan...
So I tried several custom roms (actually I'm running Revolver 4) because I knew from the past, when Honeycomb itself has had this annoying problem, Revolver did it for me.
Well, Revolver 4 didn't...
So I did the following, please read carefully and don't only check IF this value is set at your devices and discard:
Go to developer settings (I'm german, may be my description doesn't match exactly) . There should be a point "display always on" or equal. The checkmark is NOT checked, when first installed stock or Revolver BUT for some reason I don't know, the transformer doesn't recognizy it's empty state. This is why it never sleeps and always wakes on mouse movement, etc. So you have to do the following easy steps: Check the checkmark (in words: ENABLE display always on) and directly after that (no need to switch to homescreen first) DISABLE it again.
This should solve the annoying problem with deep sleep and battery drain.
You can test it by turning off your display, wait several seconds, maybe up to a minute, and try keypress or mouse movement. You may NOT have the cable plugged in, it only works if on battery usage. The trasformer now should not wake up and after refreshing cpuspy stats you should see some seconds more deep sleep.
I hope this has helped someone as I for myself spent hours with autoflightmode and so on until I found out this simple and a bit strange trick.
greets,
Cutterfly
Click to expand...
Click to collapse
You're a friggen genius! This worked instantly
Sent from my Transformer TF101 using xda premium
How did you discover this fix? Also, have contacted Asus about this? They may not know yet....
Sent from my Transformer TF101 using xda premium
Thanks trying this now.
Sent from my Transformer TF101 using xda premium
Can't believe the fix was that easy
Sent from my SGH-T959 using xda premium
eminembdg said:
How did you discover this fix? Also, have contacted Asus about this? They may not know yet....
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I discovered this by pure chance. After I noticed it I installed several times fresh stock, fresh Revolver, fresh Revolution HD. In all cases it has been the thing with the display setting. So I thought it to be worth to tell you here.
I didn't inform ASUS or some of the great developers of custom roms here, because I also can't believe it to be that easy. I know from OLD programming languages, that you have to declare a boolean in a function to be true or false state, otherwise it will be ignored, but I hardly believe Java / Android would have such old problems. So I just hope my trick will work until someone verifies this to be the original problem or will supply us with a better workaround.
greets,
Cutterfly
Well it's working for me. I sent Asus an email and linked to your solution here on xda.
Sent from my SGH-T959 using xda premium
nvermind
Are you talking about "Stay Awake (Screen will never sleep while charging)? I don't see anything else under Developer options.
Sent from my DROID RAZR using Tapatalk
Sziehr said:
Are you talking about "Stay Awake (Screen will never sleep while charging)? I don't see anything else under Developer options.
Sent from my DROID RAZR using Tapatalk
Click to expand...
Click to collapse
I think he's talking about this,
1/Settings
2/Developer Options
3/Stay Awake option
4/If this option is unticked then tick it
5/Now untick the option immediately
6/Return Home
7/Test it.
Anyway this worked for me. Thanks OP
This doesn't seem to have worked on mine. I might try flashing a different rom.
Also doesn't seem to work for me.
Tried the OP's suggestion, then I had my tablet turned off. Before turning off the tab battery was at about 83% and the keyboard battery was at about 30%.
Boot up tablet and now tablet battery is at 94% and keyboard battery is at 3%.
Seems the tablet was being charged while it was off. This has never happened before. Running ARHD Rom.
Sent from my Transformer TF101 using Tapatalk
Hey folks,
I'm sorry if it doesn't work for all, but when talking about "turning off" and "rebooting" it would be interesting to know what exactly you mean.
Do you really turn off and reboot the next day? I for myself use to short press power button, this isn't really "turning off" the tablet. It sets the tablet in deep sleep mode after about 30 seconds (so you could easily resume your work by just a finger stroke during the first seconds when the screen gets dark, but if you don't do so, it will fall asleep).
The keydock of course loads the tablet while "turned off" (same as while awake) if its capacity is more than 3%, that's absolutely normal behaviour, so if someone didn't see this before it is CAUSED by the bug: Of course if there is just 216mhz mode with higher power consumption over night than capacity, it won't look like something has been loaded at all.
I then short press the power button (i. e. the next morning) again and the tablet wakes up.
So I really wonder why someone (apart from those who have the draining bug) should really restart the tablet.
BTW: Yes, I definately mean the point "stay awake" which here in germany is described as "display will never fall asleep while loading". I think the problem is the following: This setting is visually set to "not active/disabled" while it is internally set as "true". So if one doesn't touch this after a fresh ICS installation, every time we are docked, the tablet "thinks": Okay, I get loaded (by dock), therefor I just darken the screen but don't really turn it off, and while screen is on I cannot fall into deep sleep and have to stay at 216 mhz all the time"
If then the user itself enables and disables the checkmark, it is internally set as false and everything works fine (at least for me).
Only thing I still dislike: While plugged, my tablet will stay in 216mhz mode all night long. I don't know why but this doesn't matter too much for me, as the power it gets while plugged is much more than the consumption it uses to stay at 216 mhz so my tablet is although fully loaded during some hours. As I told you in my first post, you cannot test this (neither touchpad awake nor deep sleep mode) while plugged. You need to test this while on battery usage.
greets,
Cutterfly
Excellent catch!
Great job...... Such an easy fix. Love these types of workarounds
Works
Fantastic,
Thank you very much - thats worked, my transformer is usable again!
Rik
eminembdg said:
How did you discover this fix? Also, have contacted Asus about this? They may not know yet....
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
German efficiency
I had to do the same thing to get the touch sounds working right after the OTA upgrade to ICS. Interesting - and good catch!
Dear OP
Wasn't meant to knock you in any way, it seems your method is working for many people.
When I say "turning off" I mean shutting it down completely, rather than putting it in standby.
I was under the impression that when the tablet is completely shut down no battery should be draining from the dock.....
browngeek said:
Dear OP
Wasn't meant to knock you in any way, it seems your method is working for many people.
When I say "turning off" I mean shutting it down completely, rather than putting it in standby.
I was under the impression that when the tablet is completely shut down no battery should be draining from the dock.....
Click to expand...
Click to collapse
If your TF still drains while the tablet is completely shut down, then you have a hardware problem.
Related
Hey guys,
Just updated to the x10 after my samsung galaxy died on me, so far i am rather happy - except for the lack of root, but that will come.
I have noticed many complaints on the forum about battery life, and have experienced the same thing myself. From my experience, i think this looks like the same issue that was faced on a leak of 1.6 for the galaxy - it was referred to as the "No Sleep Bug".
TBH, the name says it all - for some reason, in many builds of android 1.6, phones were not sleeping correctly. There are many theories as to why, from cpu not being allowed to sleep, to permanent communication with google servers.
Despite all these different theories, one thing seemed to fix the problem - turning off all location services. Some people argue that a different carrier build, turning off just 'share with google' under location, turning off just AGPS etc. would fix it, but from my experience, the only real way to fix the issue was to turn off all GPS usage unless you need it. The once you have used it, reboot your phone.
This fix obviously sucks, and a new fix has recently been released by a veritable android-demigod around the Galaxy.
HERE IS A THREAD ABOUT NO SLEEP ON i7500 GALAXY;
(ok, some stupid rule says i can't post links - can a mod help me out?)
HERE IS THE FIX FOR THAT PARTICULAR BUG;
(ok, some stupid rule says i can't post links - can a mod help me out?)
LINKS ARE IN POST #5 - THANKS TO ONDOTEAM (would still be nice to get them in this original post though)
Now, from my experience, no sleep behave exactly the same way on the x10 as it does on the Galaxy;
1) I turn of all location services, and my battery life at least doubles.
2) After said turning off of services, 'spare parts' no longer says 100% running time under battery usage - in fact it can be as low as 10%.
These two factors are identical to my experience with Galaxy. SO; is there any way drakaz's fix can be applied to our X10's? It seems to me that the files he mods are standard Android system files, not sony/samsung specific.
Now i am no developer, so i dont know it this is possible - the first question that comes to mind for me is "do we need root access, or can this be done through developer tools using the android SDK?"
Can anyone help shed anymore light on this?
Seems to work for me. I disabled all location services. Spare Parts went down from 100% to 7.6%.
I'll just have to enable GPS when I need to use it..
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
n3man said:
Awesome! Glad to hear it has helped.
Let's keep testing this guys - if it does show up to be a big cause, then perhaps the devs around this place can help is figure out a patch for Drakas' mod to make it work with our x10's!
Click to expand...
Click to collapse
Hello send me a PM with links, I will try to post it
http://androidforums.com/samsung-i7500/61168-no-sleep-has-nothing-do-anything.html
http://androidforums.com/samsung-i7500/78471-no-sleep-bug-fixed-drakaz.html
Links from n3man
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
ronnyuk said:
No sleep is easy to fix, took me a while to figure it...
Turn your screen brightness from manual to auto, spare parts will now start showing proper running stats, no more 100% running.
The screen is a little dark in auto but it will cure the 100% running.
GPS and location services etc make no difference to my X10i, I am running the 1.6 version unbranded UK handset, the only thing to stop mine running 100% is to put the screen on Auto.
Click to expand...
Click to collapse
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
I can't see "Spare Parts" in About Phone -> Battery Info
tuxStyle said:
I can't see "Spare Parts" in About Phone -> Battery Info
Click to expand...
Click to collapse
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Spare Parts is a standalone Program ...
(i don't know for sure if it is in the market or downloadable as .apk from somewhere here in the forum ...)
Bax
im_iceman said:
Me neither.. I was wondering about that myself!..
Although I'd half assumed that they were referring to the total "up-time" figure which you can see at the bottom of the "about phone"; "Status" screen.. But perhaps not.?
Click to expand...
Click to collapse
You can download it here
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
n3man said:
Spare parts is indeed available from the market - it is a much more powerful tool for indicating battery usage than the regular android methods. The galaxy stared on 1.5 which had NO indicator of battery usage statistics at all, so we all learned about spare parts very fast.
Perhaps that is why no x10 users have realised about the potential no sleep bug; because so far only the android usage indicators have been used?...
Anyway, hopefully this can help us all understand the way our phones are working better together
Click to expand...
Click to collapse
14% it's mine value for running time, not 100%. By the way thats 30 minutes of 210 in total :S
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
mimok said:
I'm also experiencing "No sleep bug" after i used GPS. I use Battery Graph to plot my power consumption and after I use GPS, I can clearly see that power consumption is high even if i turn the phone in plane mode.
In addition SE widget, used to turn on/off GPS, seems to not work very well for me. So, to fix the bug, i manually disable GPS in parameter menu and restart my phone. After that power consumption is hardly null (20% in 8h with MP3 on almost all the time).
Click to expand...
Click to collapse
Do you have 3G always on?
My phone has no trouble sleeping.
Gps hasn't really been an issue but I keep it off when not needed.
Here's my solid settings:
1) No auto sync
2) No moxier
3) Gps off
4) Restart after using wireless
As long as it's like this my phone lasts 2 days easily
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
Yes, but I made a lot of test with and without 3G enabled and 3G seems not to be a problem for me. I think my problem comes from GPS.
ondoteam said:
Do you have 3G always on?
Click to expand...
Click to collapse
3G always on.
n3man said:
LOL... this is already going the way of the Galaxy thread!
My phone came out of the box with auto-brightness and i never changed that option, yet i still had no sleep.
Drakaz has done some fairly deep digging and is next to certain that it is an artefact of the geolocation bug discussed in the thread in which the problem was fixed.
Click to expand...
Click to collapse
I have been playing with mine for a month to work out what caused mine to not go into sleep, I keep GPS wifi etc on 24/7 but in spare parts I was running 100%, after numerous reinstalls and removing everything i chanced on turning on auto screen brightness, now when i unplug my x10 the running sits at the correct level.
No Geolocation bug here
I have this problem with 100% on and off. Sometimes when I check its under control (~10%), other times its at 100%. I have GPS off, no WiFi, auto brightness... don't know why it sometimes just gets stuck at 100% :/
So, my battery has been draining ridiculously fast and I think I found the culprit. For some reason, my TF is running at 100% awake time. This isn't the case with my friend's TF, so it can't be normal.
My TF is not rooted or anything, so I don't know how this came about. Any ideas on how to clear this out?!
Thanks!
Have you tried a factory reset?
Sent from my captivate BLAZING on firefly 3.0
Factory Reset should indeed help, as I believe it's a rogue app or service that's keeping your device awake.
It would be a better idea to try and troubleshoot which app/service is the culprit so you can make sure it doesn't happen again.
To do this, search XDA for 'bathisgb.apk', which is a modified version of the "Spare Parts Battery History" function, and this will show you which processes are keeping the device awake. Run the app, then choose "Partial Wake Usage" from the dropdown list, and if any have large blue bars, those are your culprits.
Hope that helps!
I have Battery Monitor Widget app and SystemPanel to monitor. The only app that I discovered to be consuming more battery than I minded was Skype. I uninstalled it but it seems that the Awake time is still going. =/
Nobody else having/had this issue?!
I did have this issue and ran the battery history app referenced above. My problem seemed to be with Google Voice. I installed the version from XDA for honeycomb.
Now I need to figure out which is worse. Shorter battery life or no text message from the device.
I was having this issue as well... not sure if your still looking, but here is a link that helped me.
http://forum.xda-developers.com/archive/index.php/t-905650.html
I updated all the radios, prl, ect
Then wiped data/cache/dalvik
Then wiped ALL
then flashed the same ROM
ALL of this before rebooting using RA recovery.
Also, when checking the progress, make sure your not connected USB to your computer!!
Hope it helps someone....
I was having the same issue (100% awake time), and the problem for me was simple. I was using the Lock Screen App (Kenneth Cheng), which I am still successfully using on my android smartphones, and that app seems for unknown reasons unable to put the Honeycomb on sleep like it does with previous versions of android.
I was also thinking at complicated scenarios, did factory reset the TF twice etc. but always used to install that app among the firsts ones cause it saves the hardware power button from aging to quick (which happened on my HTC Desire).
If you are using any app of that kind, it might be your answer too.
stnel said:
I was having the same issue (100% awake time), and the problem for me was simple. I was using the Lock Screen App (Kenneth Cheng), which I am still successfully using on my android smartphones, and that app seems for unknown reasons unable to put the Honeycomb on sleep like it does with previous versions of android.
Click to expand...
Click to collapse
Damn, I like Lock Screen too. Did you manage to find another app that does the same thing without causing the Transformer to not enter sleep?
EDIT: nevermind, it looks like "Screen Off and Lock" doesn't have the awake bug that Lock Screen app has so using that on my Transformer now.
I updated to CM 7.1 RC1 last week and I've noticed a few times where the device has locked up after "going to sleep". Essentially, if I leave it on the coffee table with WiFi on and let the screen turn itself off, it won't respond when I return to it 20-30 minutes later. I have to force reboot via the power button + nook button.
Just curious if anyone else has noticed it or if it's just me. If it's a common issue I'll escalate to the CM folks, if it looks like just me I'll start the long and tedious process of uninstalling apps one by one. =)
I have at least one every day. I figure its just a price I pay. Over all its the best rom I have used.
Sent from my NookColor using XDA Premium App
Only once have I had the issue you described. I leave WiFi on some of the times, but majority of the time I have it off when I am done using it. I know some people have mentioned using Tasker or something similar to turn WiFi off when screen goes off so that it can perhaps be prevented.
EDIT: I don't believe I can link yet on my account, but search General for the post "NC, CM7, Dalingrin OC kernel.. Sleep of Death" and start about post #6.
Thanks bio, that looks like the exact issue I'm experiencing.
For the next guy with this issue: Link to the thread biohazard mentioned
Installing Droid wall has fixed the problem for me and has doubled my battery life
Sent from my NookColor using XDA Premium App
mrkavanagh said:
Installing Droid wall has fixed the problem for me and has doubled my battery life
Click to expand...
Click to collapse
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?
I'm facing random freezes when I open an application like tweetdeck or mercury and leave it updating from the internet. After some time, I'm not using it, it just stucks. To get it back to life I have to press for a few seconds the power button to shutdown it and then again to power it on. I have used different nightlies, voltages or governors but it is still here.
Now, I don't have freezes since yesterday that I really reduced the voltages but I'm not sure if my problem is solved.
configuration: 144 nightly 300-1100mhz xlv profile
not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.
skylar.sutton said:
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?
Click to expand...
Click to collapse
I'm sorry. I use the white list feature and only check mark the current application that I want to use and allow to access the internet. It keeps everything else from using background data.
For example right now I selected xda and updated rules.
Sent from my NookColor using XDA Premium App
Phatdawg said:
not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.
Click to expand...
Click to collapse
It seems that I solved it reducing the voltages. When sod occurs a black screen appears right? I never had sod, only random freezes.
Sent from my Nook Color
So I had my a500 fully charged Saturday afternoon. I go to turn it on and its dead. Something is wrong here for sure because I use to go a week on standby. I posted some pictures of what my battery life looks like. Its a straight linear decline and I can't figure it out. I'm rooted, and thinking maybe I'm trying to receive the 3.2 update and I can't due to be rooted. I checked system update and it says I'm up to date. Please, any help?
tu3218 said:
So I had my a500 fully charged Saturday afternoon. I go to turn it on and its dead. Something is wrong here for sure because I use to go a week on standby. I posted some pictures of what my battery life looks like. Its a straight linear decline and I can't figure it out. I'm rooted, and thinking maybe I'm trying to receive the 3.2 update and I can't due to be rooted. I checked system update and it says I'm up to date. Please, any help?
Click to expand...
Click to collapse
Check to make sure your Bluetooth is turned off, and your wireless is set to disconnect when screen turns off.
tu3218 said:
So I had my a500 fully charged Saturday afternoon. I go to turn it on and its dead. Something is wrong here for sure because I use to go a week on standby. I posted some pictures of what my battery life looks like. Its a straight linear decline and I can't figure it out. I'm rooted, and thinking maybe I'm trying to receive the 3.2 update and I can't due to be rooted. I checked system update and it says I'm up to date. Please, any help?
Click to expand...
Click to collapse
From the pictures you've posted it does look like something is up. Awake time is supposed to coordinate more or less with Screen On time. That's a general rule of thumb. Background things will wake the tablet and work very briefly sometimes but it doesn't look like that and generally takes seconds, adding up to mere minutes in total over days of that behavior. In essence awake time is supposed to follow screen on time closely with mere pips in difference. Yours is pretty much solid.
You could be right about the update, though I don't see how or why it would cause that anomaly, since it doesn't try to check for the update if the wifi is off, and even if the wifi is on it doesn't download it unless you tell it to. Plus, you can always turn off the automatic/scheduled check entirely.
Other issues I can come up with are net' related (stuck weather update, account sync, browser sync, picture sync, etc.) but are all invalidated since your wifi use is not that bad. I'm thinking any of these would trigger your wifi to stay on.
What's left, perhaps a rogue task manager? Something that's killing a necessary task which is then quickly restarted and so the loop goes on till your battery dies. If I can think of anything else I'll post it.
My only recommendation for now is to stop any task manager you have running, as well as locale or tasker if you have those. Restarting and then seeing how things fare after a day of standby.
i have similar situation.......
battery drain on my HoneyVillain 1.2 with Richard's Kernel is unbelievable.
It is not keeping even a half day. With Honeycomb 3.1 or 3.0 it was much much better.
What i see right now:
- on the battery usage graph i see that "Screen" is eating 80% of the battery - is it correct???
- when i'm at work, where my tablet is connected only to internal WLAN Network (no internet access) - the battery is going down much slower
What i have installed (and running in background)
- exchange mails (3 accounts - push method) with exchange widget
- simple calendar widget
- asus weather widget
- extented controls
- hacker's keyboard
looks like i got the same issue
proxonic said:
i have similar situation.......
battery drain on my HoneyVillain 1.2 with Richard's Kernel is unbelievable.
It is not keeping even a half day. With Honeycomb 3.1 or 3.0 it was much much better.
What i see right now:
- on the battery usage graph i see that "Screen" is eating 80% of the battery - is it correct???
- when i'm at work, where my tablet is connected only to internal WLAN Network (no internet access) - the battery is going down much slower
What i have installed (and running in background)
- exchange mails (3 accounts - push method) with exchange widget
- simple calendar widget
- asus weather widget
- extented controls
- hacker's keyboard
Click to expand...
Click to collapse
80% is harsh but I suppose that could be correct, especially if you use the tablet a lot. Following my own tablet as an example, at any point in time my screen takes more juice than anything else on the tablet. I have my screen set to 40%. Auto brightness isn't as sensitive as I like it so it always falls to maybe 60% when I'm fine with it at 40% or so so I manually adjust that while at home.
My screen follows my awake time almost to a T.
Wifi also does seem to be eating a bit more than it did in 3.1 - maybe Acer increased the transmit/receive power in the chips so people stop having wifi connect/disconnect issues? Who knows. I've always had my wifi on 24/7 and overall it never took more than 10% of the battery from full to dying. Now it's considerably higher, 15% or more depending on how much I use the tablet.
But that 80% is still more normal than the awake time posted by the OP.
Have you tried turning down the brightness or adjusting the timeout? Indoors 30-40% is fine for me though I can go even lower, especially when I'm in bed or in the living room and the lights are off in the area. Outdoors I set it to auto or to 50/60% depending on whether I'm using it in my car or during shopping. Also, setting the perfect timeout can matter too. I set mine to 1m, but a really good practice is to set it to 30s and just set your browser or media player to keep it awake while in use. I'm too lazy to do those things
Neoprimal, thanks for the response! I just got home from work, and come greeted with what I suppose is the 3.2 update(~357mb). Now I don't know if that is my issue or not but it could have been. I'm rooted but stock everything. Am I okay to download this 3.2 update?
tu3218 said:
Neoprimal, thanks for the response! I just got home from work, and come greeted with what I suppose is the 3.2 update(~357mb). Now I don't know if that is my issue or not but it could have been. I'm rooted but stock everything. Am I okay to download this 3.2 update?
Click to expand...
Click to collapse
The 3.2 update has no root, do you have setcpu installed?
Sent from my A500 using xda premium
Quick suggestion.
Try changing ROM maybe it will solve your problem.
Neoprimal, thanks for your answer.
I reflashed my iconia back to 3.1 - honeyvillain 1.05a and i have no more battery drain issue.
Screen battery usage is as well at level about 80% so as you said it seems to be normal.
I tried as well other 3.2 cooked roms like taboonay or revolver port - everywhere i got unbelievable high battery drain.
So for me it looks like 3.2 issue.
You can be right with higher wifi power consumption in terms of better signal with honeycomb 3.2.
With3.2i had all the times all stripes blue - with 3.1 signall seems to bea little weaker but anyways strong enough for the internet.
proxonic
proxonic said:
Neoprimal, thanks for your answer.
I reflashed my iconia back to 3.1 - honeyvillain 1.05a and i have no more battery drain issue.
Screen battery usage is as well at level about 80% so as you said it seems to be normal.
I tried as well other 3.2 cooked roms like taboonay or revolver port - everywhere i got unbelievable high battery drain.
So for me it looks like 3.2 issue.
You can be right with higher wifi power consumption in terms of better signal with honeycomb 3.2.
With3.2i had all the times all stripes blue - with 3.1 signall seems to bea little weaker but anyways strong enough for the internet.
proxonic
Click to expand...
Click to collapse
Hey Proxonic, as you can see it can't be a '3.2 issue' because I'm on 3.2 and I don't have the issue.
Uploaded with ImageShack.us
I barely used my tablet this week because my wife asked me to 'break in' her Touchpad. The brand new one she got had a massive screen problem and we didn't discover it until days later because she never used it much during the week. Pray this never happens to your A500!
Anyway, this is showing that I have my wifi off when the screen is off - the screen on times are generally when I use the tablet to start music, usually before heading to bed.
Most of the awake time is the music playing, but some is probably IM programs and apps looking for internet. I use either google music, pandora/tunein radio/iheartradio or 2player Network Music Player; the radios and 2player NMP use wifi while I've cached a couple playlist or 2 worth of google music to the tablet. I also ran a test for another thread where person(s) reported their Acer Media app turning music off when the screen goes off, I suspect that'd be that long block of awake time without wifi.
Point is though, that I don't think 3.2 has a battery drain issue. Not in regards to while the tablet is sleeping/hibernating anyway. It sounds like maybe you just have some app gobbling up either cpu cycles or something else causing it.
Glad you at least got it fixed with the ROM though.
P.S The touchpad screen, btw looks like this...keep in mind, this is on a good day. When it got bad it was just a huge black block or tons of moving lines. Did a factory reset using Webdoctor and that didn't fix it. The replacement we got seems to be fine so far. The picture's really bad, sorry - took it in the car at a shopping center.
Uploaded with ImageShack.us
I have the same issue I am 100% stock on mine and ever since the 3.2 update i will have it fully charged at 8am and at 8 pm I am down to 20% and i never touched it the thing just sat in my bag while I was at work. and i have a 100% uptime. I don't use task mangers and have no idea what is draining it.
downer06 said:
I have the same issue I am 100% stock on mine and ever since the 3.2 update i will have it fully charged at 8am and at 8 pm I am down to 20% and i never touched it the thing just sat in my bag while I was at work. and i have a 100% uptime. I don't use task mangers and have no idea what is draining it.
Click to expand...
Click to collapse
That definitely sounds like a rogue application.
Any app in your accounts and sync section has the ability to cause that sort of uptime, so take a look through them. Force a sync and go through each of them to see if anything gets 'stuck' syncing. Twitter and Facebook are always suspect, especially if you're 'busy' on them (meaning you have lots of tweets/facebook posts to sync).
Furthermore, the system is SUPPOSED to close away/sleep some apps after they move from foreground to background however, some of these apps can become locked for some reason and not close (thus the definition of a rogue app). Running processes, etc. may do this. So in addition to programs found under account and sync; any app that plays media (video or music) or connects to download data (news, social apps, shopping/deal apps) can cause this sort of uptime.
I know it can be frustrating but the fix may be as simple as removing the offending app.
Good Luck.
I figured my problem out last night. On all 3 of my gmail accounts it was trying to sync picasa and google photos constantly.
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