I'm having problems with It shutting off overnight while charging. Anybody else having this problem?
bjh2379 said:
I'm having problems with It shutting off overnight while charging. Anybody else having this problem?
Click to expand...
Click to collapse
I just discovered this "feature" this morning as well. -_-
Did u find how to fix this?
I love the feature where the A500's battery doesn't last overnight with the screen off. I didn't think I needed to charge it overnight since the battery was at 95% anyways, so I just set it on the table next to my bed and went to sleep. Woke up this morning and it wouldn't power on. Pretty cool. Wonder what is draining the battery? My DroidX can sit on the same table for almost a week w/o being charged.
I haven't seen it, then again I play music from getting into bed till I wake up so ill try leaving it to sleep and see what happens.
Sent from my A500 using Tapatalk
Me too
Same issue here.
i have not tried the trick that I just found that seems to extend the batery life....I put the tablet in "airplane mode" , enable the WiFi and the battery looks like it is draining alot slower. There is power being used for "cell standby" even though is a wifi only tablet
Same problem here with shutdown on charge. Right now it seems fairly consistent-
I'm experiencing them same thing when leaving asleep for extended periods. It first happened while I was charging... now it happened again when I left for dinner and came back. I don't see any setting options for that
Same here. Thought it was a "feature" to keep from using as much battery.
Sent from my A500 using XDA Premium App
So shutting off notifications seems to stop the problem for me.. except that I don't get notifications At least it boots pretty fast
Lets run some tests, shall we?
bjh2379 said:
I'm having problems with It shutting off overnight while charging. Anybody else having this problem?
Click to expand...
Click to collapse
I don't think they're shutting off, I think they're crashing/freezing during sleep and not rebooting.
This is speculation by me, and could be different for different people.
Finding the problem:
The test.
Night/Bedtime
This is an overnight/while you sleep test and requires about 2hrs. of your time beforehand. Record your figures if you can and post them for debunking. A couple hours before bed and while you use the tablet during the evening, charge it. After 100% and once it's off the charger please don't use it for anything. We want to simulate the sleep process for about 90m before bed. So if you use the tablet even for a quick web surf, plug it in and getting back to 100%. We're going to allow ~3% for errors anyway but we want to be as close to accurate as possible.
90m before you're ready for bed remove the charger. Don't use the tablet simply set the brightness to auto and take note of your battery level and the time. 60m in take a look at that battery charge again and record the time and charge level. 90m in is the last check and after this whether you go to bed or not please don't wake the tablet. Don't worry if it seems to wake and go back on it's own. That's inconsequential for this test. Just put it somewhere that no one will bother it and resist using it until you wake up. Please
Morning/Wake time
Wake it up.
1. Comes on? Record the charge level and time for posterity so we get an idea of idle drain here on the thread. Everyone gets different values. You'll have to run this test at another time as your shutdown/freeze hasn't been reproduced this time.
2. Doesn't come on? Try a power on press. Comes on? Same as 1. Record the charge level and time and post it here.
3. Doesn't come on? Try a power on press. Doesn't come on? Plug it in and power it on. Now do the same as 2. Record the charge level and time and post it here.
I hypothesize a few different scenarios the summary of which is that I don't think they're shutting down, but this is mostly based on the assumption that the batteries are being charged while the unit is frozen. If they do not charge then my entire test would have to be re-designed. I surmise they freeze and don't restart so they either run out of juice or they're actually frozen when you try to power them on and the long press is rebooting the unit, not powering it on. If I am right then we should see that the batteries are drained as if they have been on all night. This is going to be very imprecise, but my idea is that we'll take the charge % of your bedtime check which is a 60m mark check and just times that by the amt. of hours you were sleeping.
So if you were at 95% when you touched the tablet for the last time, this would mean a drain of ~5% give or take ~1% due to your use while checking, per hour. You take that and multiply it by how many hours you've slept and you'd get X x 5 = 40% which leaves the tablet with ~60% battery when you wake up, again give or take 3% for errors, syncing during the night etc.
If you're seeing a somewhat accurate numerical representation of this formula then it means the tab drained all night.
If you're seeing something way off like the tablet still having way more than it should then it means at some point in the night it really did shut down on its own.
People who are actually saying it shut off probably just reboot the tablet without realizing it as it was on the charger when it froze. Since a power off/reboot press of the power button is roughly the same length as a power on press, it's difficult to differentiate sometimes.
Solving the problem:
I have had this happen twice and it was while I left GPS on.
I haven't had an android cell phone yet that hasn't frozen or reboot itself when I left GPS on for extended periods (aka overnight) so the first time this happened I instantly knew to check and I purposely left it on the second time to reproduce and the second time, the tablet ended up rebooting not freezing. If you're not technical the easiest way to know if your tablet reboot during the night is to leave a web page or IM window on the screen or leave music playing.
You may want to skip the above "finding the problem" tests and attempt this "solving the problem" test. As I mentioned, this is all speculation so I'm just trying to get to the bottom of it and I'm sure we can as a grp.
Once you rule out hardware though, then it's a problem. So if it is indeed NOT the GPS then we're at the mercy of Acer and Google because otherwise there'd be just too many factors to track down.
I'm getting this and i'm loosing a ton of battery somewhere in the process too. I think the above poster is right.
I plug in tabby. go to bed. wake up to pee. see tabby is 100% battery. unplug and go back to bed. wake up to go to work and tabby is powered off completely and battery is anywhere between 85%-90% in a matter of 2-3 hours after being unplugged.
Its likely a rogue app I would get a program like advanced task killer watch it and see what apps are loading in background after you kill all apps.look for apps you installed.not so much the ones Acer put on your tab.
With Ti backup freeze the first one you think should not run give it a day.if that's not the issue keep going down the list.
Had a similar issue it was a app I got from amazon.that was So CALLED FREE.they are not so I uninstalled everything from amazon. No more battery drain.
SOME APPS do not fallow the drained android or social rules
Watching the apps to be sure nothing is running CPU cycles allow the time I loose about 2 to 3 % batter life over night with wifi set to stay awake.
This is ideally from 11 pm until around 10 am the fallowing day.
Yes I sleep in alot giggles
re-flashed with Taboonay v.2.0/Richardtrips v.3.3 Kernel and it fixed everything.
JiggaGeazY said:
re-flashed with Taboonay v.2.0/Richardtrips v.3.3 Kernel and it fixed everything.
Click to expand...
Click to collapse
had this on my tab for 2 days and reflashed back to stock because battery life was awful.
Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)
Seems to be working fine for me, would I have to do this for every nightly.
Sent from my SGH-T959
great find +1 the battery life of cm7 drove me away to a JVQ rom but imma try this find and use it!
I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?
I like this. I can actually stream music while charging without slowly losing charge.
I'm going to try this and see what happens
Hope this gets run through Atinm.
kleineschatz said:
Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)
Click to expand...
Click to collapse
I hope this works, but when i first went to phone info and did radio band, it asked for country, i choose usa, it didnt FC thou, then when my setting was already GSM/CDMA (prl) . I will report back tommorow how it goes. thanks
I'm guessing the same would apply to MIUI?
It definitely seems to be doing something. My signal hasn't dropped below the full four bars yet, which is weird considering it's normally around 1 or 2. The phone also seems to go to sleep faster, but that could be placebo.
Sent from my SGH-T959 using XDA App
duboi97 said:
I'm guessing the same would apply to MIUI?
Click to expand...
Click to collapse
yes i tried this it didnt seem to work for me i dont think i got it to stick on im gona try it again
didnt get Force closed at the select radio band. Now what should I do?
on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.
ferhanmm said:
on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.
Click to expand...
Click to collapse
Thanks! Finally I got it to force closed and I did everything else. But I went into cell standby I saw my TWS% is 71 when my cell standby is only 21%. Is that a problem?
SuperJMN said:
I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?
Click to expand...
Click to collapse
I had this same problem. Apparently alot of others did too, but no one seems to have a solution that I have seen.
Sent from my SGH-T959 using XDA App
Effect of USB Charging on CPU Idle Utilization CM7
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.
THAT is what I'm experiencing TOO.
I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).
ginzberg said:
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.
Click to expand...
Click to collapse
i usually reboot after i charge when i wake up then i send a few texts and work the phone a bit my battery life isnt too bad
romitkin said:
I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).
Click to expand...
Click to collapse
no i have the same problem for some reason i cant get this fix to work either
Gave it a try, will see what happens. Battery life is now the only bummer on CM, if this solves it, I'll be a happy guy.
I've been using the Aria for 2 years now, and just 2 days ago I ran into an unexpected battery drainage problem.
1. When I am speaking during a call and not holding the phone close to my ear, the proximity sensor is not always triggered which causes the screen to stay on. While the screen is on, the battery drains 1% every minute (or every 30s). When I turn the screen off, the drainage is fine.
2. When I receive text messages (voicemails from my landline trigger a text message on my Aria), the battery drainage is very bad (1% per minute or 30s).
I never use data networks (turned off), background data and autosync are both turned off, gps is always off, wifi is always off, screen brightness is always custom at the 3rd lowest brightness setting. Basically, I try to conserve battery life and only use the phone for talking.
When I looked at battery usage, it was mostly due to Android System, Voice Calls, and Cell Standby.
I'm running the very old Liberty Froyo Rom (the version released like 2 years ago) and the default CM7 kernel. Also, I upgraded to the newest radio to fix this problem, but it didn't seem to make a difference. I don't think these things should be causing the problems since it only occurred 2 days ago while these things have been constant.
Any ideas what is going on or what I can do to make my phone last longer? Talking on the phone for 30 min from full charge takes my phone down to 25%...
honestly at this point my battery meter is completely wonky. the percents mean nothing now. i still get roughly the same battery life but it'll burn through large chunks of percentage in minutes but sit at a single percent for hours or active use.
i'd say try a new battery
If you've got clockworkmod installed, boot into recovery and wipe battery stats. If you're still experiencing this, try a different rom. I've been using CyanogenMod 7 for a long time with no issues.
If this fails, it's probably your battery. It might just be pooped out. If you get a new one always buy and OEM battery! Don't get anything off-brand.
really? its about the battery? not the OS itself?
after 2 years of use it's safe to assume that it's the battery and no necessarily the rom.
2 years with the same battery? old battery i say and is usually the life expectancy with it. i say you get a new battery. or try charging your battery all the way full. wipe the battery stats. then let your phone die, then completely recharge it all the way up again. that worked for me.
Battery life with ANY Android phone is hit and miss, but the Aria is notoriously terrible with it. However, there are several "tweaks" you could do to help it (note: I said help, not fix.). Beyond the basic system setting adjustments, I have found the "Die Hard Battery Calibrator" script by zeppelinrox to be helpful. Look for his V6 SuperCharger thread here on XDA to find it (as well as other useful scripts). Of course, the usual caveats apply: S-OFF, root, magic powers, etc.