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.
Related
found this on another site don't know if it has any relevance since i just tried it but will keep you posted:
Disclaimer: the following may *not* to the HTC EVO! And yes, of course we should NEVER have to deal with this kind of kluge. But it might help…
There’s a known bug in the cell radio software on at least one other HTC Android phone (Eris) that can significantly reduce battery life. Basically, it thinks it doesn’t have a signal (though it’s connected) and frequently keeps trying to connect, which steadily drains the battery, even when the phone is apparently idle.
To check if this is affecting your phone:
From the home screen, press Menu, Settings.
Scroll down to the bottom and press About Phone.
Press Battery
Press Battery Use
Press Cell Standby.
Take a look at Time Without Signal. If it’s 0% or a bit higher, then your phone is not affected and you can stop reading. If it’s 50% or significantly higher than you know it should be (e.g. you were in cell range all or most of the time), then the phone is being affected by this problem. BTW, Time Without Signal may not be displayed in some circumstances – try again later. AFAIK, all HTC Eris’s are affected, not sure about other phones.
The good news is that there’s a simple way to fix it (usually called the Airplane Mode trick):
Power your phone off and then restart it.
Once it’s fully booted, plug in the charger.
From the Home screen, press Menu, Settings and Wireless & Networks.
Press Airplane Mode and wait until it’s checked and back to full brightness.
Unplug the charger.
Press Airplane mode and make sure that it’s unchecked.
That’s it!
Will this fix cut down down on searching for a cell signal? Can anyone verify thi works?
Trying this now. Will report back in a few hours.
It doesn't make any sense, but I think this might have worked. I tried this about 4 hours ago and I'm still at 0%. I was getting as much as 50% without service. I'll report back again after I have some more time to test it.
I'm at 10 hours now and it's still at 0%. I don't know why this works, but it appears to actually work. I was even able to turn on always on data with no negative battery consumption since I don't really have much auto-syncing.
Thank you very much OP.
biscodude said:
I'm at 10 hours now and it's still at 0%. I don't know why this works, but it appears to actually work. I was even able to turn on always on data with no negative battery consumption since I don't really have much auto-syncing.
Thank you very much OP.
Click to expand...
Click to collapse
Same here, went from 4:00pm yesterday to 5:00am this morning and still had 50% battery. Watched some trailers, used a flashlight app ( alot, thanks to being without power till this morning), did some texting, and was watching weather radar. My time without a signal is staying at 0% also.
Thanks also.
Here's an easier way to do this from a previous post. FYI - I did this a few days ago. Here's my current battery test stats (I'm letting it drain itself out and see how long I can go).
Uptime: 32 Hours, 45 Minutes
Awake Time: 4 Hours, 30 Minutes
It has not been on a charger since it was last fully charged. Love it.
http://forum.xda-developers.com/showthread.php?t=700601&highlight=battery
Wow, my stand by was at 58%, though I am inside a building with horrible reception, I sure hope this fixes it.
Will this fix be permanent or will I have to do this every time I plug the phone back in or after reboot?
Ketty said:
Will this fix be permanent or will I have to do this every time I plug the phone back in or after reboot?
Click to expand...
Click to collapse
The original thread stated it had to be done every time, but mine has stuck since I changed it using the method here: http://forum.xda-developers.com/showthread.php?t=700601&highlight=battery.
One other thing to note: If you download the app in the Market called "Network", you can access the screen to change it without having to do the dialing or airplane mode thing. This would be the easiest way to do it if you happen to have to do it every time you reboot.
Final stats:
Uptime: 35:15
Awake Time: 5:15
This is about twice as good as I was getting before.
I think I've discovered a bug on the X that's causing battery drain.
I installed Spare Parts and saw my phone had been unplugged for about 12 hours and that my phone was been Running (not sleeping) for 100% of that time.
After being methodical and getting data points after opening various programs, I determined that after I opened any program that accessed the GPS, the phone no longer would go into sleep mode.
To get the phone to start sleeping again, all I have to do is toggle GPS off and then back on again.
It's completely reproducible every time on my phone.
Now, I don't know what kind of effect this will have on battery life, but seems like it probably would have some effect.
If others can test this and see if it affect you at all, it'd be helpful to see if there's a potential major software bug here or if it's just something with my phone.
Easiest way to test is to start with a fresh reboot with GPS toggle on, install Spare Parts, plug in the phone for a second (to reset the counters), let it sit sleeping for a few minutes, then read the Running % in Spare Parts. Should be pretty low. Plug in the phone to reset the counters again. Then start Google Maps or any other program that will activate your GPS. Close that program and then let the phone sit idle for a few minutes. Check Spare Parts running time again and, for me, it's pegged at 100%.
It stays like that until I toggle the GPS off or reboot the phone.
Very curious to see if others get the same results.
lexluthor said:
I think I've discovered a bug on the X that's causing battery drain.
I installed Spare Parts and saw my phone had been unplugged for about 12 hours and that my phone was been Running (not sleeping) for 100% of that time.
Click to expand...
Click to collapse
I'm not trying to flame... but, after 12 hours your phone was unplugged, and still working... battery drain doesn't seem like a huge issue for me based on this information.
I would recommend an app called Tasker. I use it to turn gps off when it's not in use. I open google maps, gps starts. I close maps, gps off. I put my phone into the car mount, bluetooth starts, gps on, pandora on. unplug it, then everything off. I can have the cell radio off at night, but come on every 30 minutes to check for sms, email or whatever. I have Wifi turn on automatically when I get home, based on gps of course, and when I get out of the car, gps turns off and wifi turns on.
It saves a ton of battery for me, and might be something you'd appreciate. I have my phone running on performance mode all the time, and it still lasts all day and has 30+% to spare when I go to sleep. I'm a heavy user. almost 4GB of data this month with no tether.
That's not really the point.
The point is that there's potentially a bug with the phone that's not allowing the phone to go into sleep mode.
Seems like that might be a pretty important thing.
Point blank, the Droid X is one of the only Androids who last more than on day on the same charge! And what you all don't know is that if you use the blk taskbar and services.jar V.8 from teenfaces you will literally double or triple your life!
I have been unplugged for about 7 hrs and still have a sturdy 70%. All this with a normal discharge rate of about 5% every hour! That'd not bad! But then you have ATK set to aggressive... then the batt manager set to smart then cache mate running at full blast clearing caches every half hour. Plus the apps are killed and shut down when te screen ia off! So technically the X is dead till you power it up!
Take a look... I promise many will agree, that is if they did it right and are using V8.
Sent from my DROIDX via Telepathic DLNA.
What in the world is services.jar V.8 from teenfaces?
Ok, so then both of you are saying that the fact that the phone doesn't ever go to sleep once the GPS has been activated (even after the program that did so exists), isn't an issue?
Seems to me that you can only further improve battery life by having the phone sleep when it's not being used.
But who am I to argue I guess.
Seems like you dint understand my previous post. There is mod to change the task bar and shade. Like V8 is the latest with the services.jar replacment. Now how this affected my batt life i don't know, but, it did.
Now i see a lil longer batt life than with the original items.
Sent from my DROIDX via Telepathic DLNA.
this post is hilarious.
homeboy is trying to get bug testers, and people are talking about how to change the color of their taskbar : /
ixobelle said:
this post is hilarious.
homeboy is trying to get bug testers, and people are talking about how to change the color of their taskbar : /
Click to expand...
Click to collapse
Lol yea. Im gonna head home and try what ur saying. I use tasker for turning wifi on and off for maps and the new google places thing (because most of the time im in buildings) but maybe i should use it for gps too. My friend with the evo has his turned off all the time he says its a huge battery drainer. I say how could that be if it only runs when the icon is up. But this might just explain that as well.
Also other logging programs might keep it awak but this one ur suggesting doesn't i take it. Good to keep in mind. Will update later today
Sent from my DROIDX using XDA App
Sorry, I guess I'm lost/confused.
No one really has a concern that this is a potential system problem that's causing excess battery drain?
I do we still don't have an extended battery im very curious to what we can do with the battery life. If this is true id imgine tasker is the way we would go around fixing it. But went we getting 2.2 next week? Maybe that will fix it. Like i said when i get home im going to try what u said when i get home
Sent from my DROIDX using XDA App
Just noticed something, I formated my phone just today. (for some reason i had to activate again. is that normal never had to do that with my WM phone when i would put roms on it and stuff)
During setup it asked if i wanted to share anymous location info to google, which i know the fist time i said yes (actually maybe the guy at verizon said yes for me) in any case it says under it something "will anonymously collect your location data even if a location app isn't running"
which could explain why it stays on when the gps is on
if you can go into your system settings and it's on for you try turning it off and see if then leaving the gps switched on will still keep the phone on.
mavermc said:
Just noticed something, I formated my phone just today. (for some reason i had to activate again. is that normal never had to do that with my WM phone when i would put roms on it and stuff)
During setup it asked if i wanted to share anymous location info to google, which i know the fist time i said yes (actually maybe the guy at verizon said yes for me) in any case it says under it something "will anonymously collect your location data even if a location app isn't running"
.
Click to expand...
Click to collapse
I think that's the option in settings->privacy, which I turned off the other day, so I don't think that's it.
Good find. Seeing the same thing. Repeated your test, and yep, system stays on till gps is bounced.
Certainly doesn't look right. Is it that once satellite fix is established, it's maintained (even if not used)? And on GPS on/off, the fix is lost and the system forgets about GPS till it's actually called?
Next step would be to see how it affects power consumption. Will try to run some more tests later in the day.
Is there an easy way to test power drain? it'll be very interesting to see what effect this is really having.
lexluthor said:
Is there an easy way to test power drain? it'll be very interesting to see what effect this is really having.
Click to expand...
Click to collapse
Unfortunately with the Droid X only showing battery power in 10%, it's not easy to discern small differences without waiting for hours.
I wonder if looking at the voltage would offer more precision. But, not sure how reliable that is. After all, if it was, why wouldn't the 3rd party battery meters use that to show more precise % readings.
exempli_gratia said:
Unfortunately with the Droid X only showing battery power in 10%, it's not easy to discern small differences without waiting for hours.
I wonder if looking at the voltage would offer more precision. But, not sure how reliable that is. After all, if it was, why wouldn't the 3rd party battery meters use that to show more precise % readings.
Click to expand...
Click to collapse
You'd actually have to write an event for every single percent in the Android system for anything to detect the battery much more accurately and Motorola is too lazy to do that. Its only gonna show every 10% because thats what Android was programmed to show.
just an update, i said no to google doing it's data mining off my gps. but then i found in location, when i check "use wifi" it asked me again. My guess is thats how they know where you are when you turn on wifi, because if you want that feature you also have to be used in mining data of where the wifipoints are physically located.
So maybe that has something to do with it.
Saw this on Android Central Yesterday.
I can confirm it, when used with fancy widget. When standard weather app is used, no major power drain. Fancy widget seems to pin the GPS and run it hard the entire time.
hijackerjack said:
You'd actually have to write an event for every single percent in the Android system for anything to detect the battery much more accurately and Motorola is too lazy to do that. Its only gonna show every 10% because thats what Android was programmed to show.
Click to expand...
Click to collapse
I would think that if Android had 1% events some app would take advantage of it (there are certainly plenty of battery monitors in Market). But I don't know of any that show anything other than 10%. The HTC phones do 1%, and the battery widgets on HTC phones show likewise. Must be a Motorola implementation limitation.
Recently I have noticed on several occasions that my phone have gotten hot and started eating away the battery. One time I had around 30% battery and the phone was laying in my pocket. I felt the heat through the pockets and took it up to see what's up. It then had 0% battery and turned itself off.
When looking at battery use in settings, it's hard to pick out one specific application that might do this. If anything it would have to be "Android system", right now it's tied with the screen on 40%, but I charged the phone an hour ago and I haven't used the screen much.
Edit: I should add that the same thing just happened, from 99% to 89% then it stopped. That's why the information above about battery usage is relevant.
Do you think it might be hardware-related, like a partial short circuit or something, or is it most likely a software thing?
Bump. 10 signs.
Had mine for a few days, have not experienced anything like what you describe
I have though felt the screen get hot when turned on full brightness and reading a e-book on it (white - black text)
Well this is while it's laying in my pocket, with the screen off, so it's not the screen. (it's the battery that gets hot)
Take it back.
[Funny story that probably isn't relevant. I had a dodgy micro sd card that made my phone drain battery super fast and as a result my phone got incredibly hot. Took it out and it's back to normal.]
Sounds software related to me, your android system should definitely not be 40% of your battery. It sounds like some rogue app/process is utilizing your cpu and thus your battery very heavily. If you select the "Android system" in the battery usage list, does it not give you a further breakdown of what is included in that that is using your battery? Also, what does it say for the cpu time for the android system?
May be firmware bug
I've had this happen to me a few times when I was running the original firmware. In some early firmware there was a bug related to switching between wifi and 3G, which would get it stuck so that you couldn't toggle wifi on or off. The times this happened to me, it was also stuck in the wifi bug (although I had the wifi bug and it didn't drain the battery).
I now run the newer firmware (JG4) and both problems have stopped.
I've had this problem with my asian i9000 since the beginning. The app called Top showed me that it is ksoftirq/d that is running and System Panel showed me that the cpu was running at 100% at 1ghz.
At first the only solution seemed to be restarting the phone. However some information shared on this forum led me to try restarting wifi which also works. For that thread search for "ksoftirq/d."
David
Sent from my GT-I9000 using XDA App
I have had the "stuck wifi" bug, but I'm not sure if it was happening the last time this happened. I'll check it out the next time.
There's no official firmware update on Kies for Norway yet, so I think I'll wait for one.
Had exactly the same problem and tracked the culprit - it was Fancy widget in my case. Removed it, installed Beautiful widget and all is well since
Sent from my GT-I9000 using XDA App
That might actually be it. If I'm not mistaken Fancy Widget had 30% battery consumption when I checked. I deleted it just to see if it would make a difference. So far so good.
Some details:
Fancy Widget will hit the 100% cpu on auto-refresh if there's no data connection available (either wifi or cellular). It seems there are 2 bugs with Fancy Widget; it ignores "auto-refresh off" option and it tries to connect to server even when offline.
A dirty work around would be to set refresh time to let's say 12 hours and make sure to manually refresh at least once every
That makes me even more convinced that Fancy Widget is the culprit. I usually have cellular network disabled (APNDroid On/Off Widget) to save battery and my wifi connection keeps loosing connection, probably due to some software bug in XXJF3 stock firmware.
So, I'm at a loss of what to do here. No matter what settings I seem to use I can't get good/decent battery life.
In fact, I get terrible battery life. With light to moderate usage I have to charge my phone at least two times a day, mostly three. Current widget reads that at standby I'm anywhere between 55mA-70mA and when in use 200mA-500mA. When charging it reaches 400mA-600mA
I see everyone talking about being able to get 5-10mA and I'm amazed at this. I've searched and read most "Battery saver" threads and none of it seems to work.
I was originally using Chucky rom lite and when I noticed the drain was abnormal I switched to the set up that chiasoft uses in his ReadMe for the ROM (stock 2.10ROM/2.08 radio).
Although since switching to the stock WinMo ROM I had repeated BSOD and SOD issues. To the point that it became unusable. I switched over to latest Energy ROM.I installed EBL and on both Stock and this Energy ROM. I am still having BSOD/SOD problems. Could it be the EBL? I plan on upgrading the radio to 2.12 in a few after I test out this EBL theory.
My setup as of this post is this:
WinMo ROM: Energy.BLACKSTONE.21916.Sense2.5.Nov.08 (Switched back to Stock 2.10)
Radio: 2.08.50.08_2 (Switched to 2.12)
Android: MooMoo Froyostone Sense 3.2 w/hastrain kernel
SetCPU:
998max/245min Ondemand on boot
Profiles: Screen off; Priority 100; 384max/245min ondemand
Battery <25% 576max/245min Priority 0 ondemand
Sampling 20000; Up Threshold 40
Advanced Task Killer:
Kill Level Agressive
I really don't want my LI-ON battery to die before I've even had the phone for the year. So if anyone can think of anything to help I'd be ever so grateful.
And of course, thanks to all the people who make all this possible.
(Sorry for the tl;dr post. I wanted to give as much info as possible.)
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
mofoahh said:
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
Click to expand...
Click to collapse
idk what it is fully charged. I'll be sure to check it later though. How do you calibrate the battery?
Also, I realized that I made an oversight on my part. When I switched to the stock WinMo rom I hadn't realized fully that it changed my Radio to 2.08 even though I posted it.
The rom chef recommends 2.10ROM/2.12 Radio, so that's what I switched to to check out that combination.
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
mofoahh said:
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
Click to expand...
Click to collapse
I don't have interactive in my options.
what version are you running?
mofoahh said:
what version are you running?
Click to expand...
Click to collapse
2.03 I got it through here.
Just installed 2.04 and there still isn't an interactive.
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
mofoahh said:
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
Click to expand...
Click to collapse
Yeah. No interactive settings. Also, that guide recommends 1190 max, but mine only goes up to 998.
Also, I finally got it to down to 7mA in standby. When I changed the radio to 2.12 and using a 2.10 stock WinMo rom.
no issues here getting 48 hours of light use, or a full 24 of moderate use...
I've yet to "condition" my battery. I'm worried it'll do more harm than good. Especially since I just got it finally to a decent mA draw. Although I'm worried my phone won't charge up to 100%. Always stop at 95.
Is conditioning really necessary/important?
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
t1h5ta3 said:
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
Click to expand...
Click to collapse
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
mofoahh said:
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
Click to expand...
Click to collapse
Yeah, 48 hours seems improbable. I finally got it down to 7-10mA on standby, and I think it charges up to 4.2 but I'll find out for sure tonight.
same
I had the same problem, make sure you use EBL android launcher and set to autoboot at 3 seconds. Make sure you restart your phone anytime youw ant to load android. I assure you this will work.
My HD2, like all others can be flattened in 2-3 hours with windows/android if used hard, the difference seems to be on very light usage/standby win mobile could last 4 days... with everything turned off and basically not used Android would struggle to last 2 days !
Same phone same network/signal levels etc, can only be poor power management within Android, and I think that means voltages for all the processor and comms modules, not just a simple case of turning down speeds.
What do others think ?
Update: Upon switching to WinMo:2.10 and Radio:2.12+ MooMoo's MMS fixed froystone3.2 I was achieving 6-10mA in standby. The phone would last all day with a two-three hour charging period with moderate usage. Low battery use, rare DC's. Perfect. Best build I've used so far.
I'm noticing a new problem however, and I wonder if it's happened to Chiasoft who recommended this build. I'm getting serious touch screen freezes since last night. Anytime before that the set up was working AMAZINGLY.
Now? It's almost unusable sometimes. This morning it was happening in Android so I switched to WinMo and surprisingly enough it happened in there too. So I read touch freezes are Radio problems mostly. Is this true? Should I switch to a new radio? I'm confused as to why it would just randomly start happening though and worried it would mess up my battery troubles I just solved.
Any advice?
Hmm. I noticed that it almost always freezes when I hold down the end home button to turn off the phone or data or to silence it. I can't actually use the touch screen again until I hit the button again to put it to sleep.
I wonder if it's hardware related because it was happening in WinMo that way as well.
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
pretzdothack said:
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
Click to expand...
Click to collapse
I give you only a very short suggestion
You have just to DELETE SETCPU
and delete ANY TASK KILLER (you can keep it just to close any apps that could hang, but not to "free up ram")
Android is not Windows, you dont need to free up ram, and you dont need to overclock/undervolt to gain some minutes of battlife despite stability.
Talk to any Dev and they will confirm this.
Good Luck
This is my first android phone and I'm wondering if I am doing anything wrong. Yesterday I charged my phone and it was at 83%. I unplugged the phone and went to sleep, when I woke up this morning the battery was completely drained.
This happens a lot. Even if I am not doing anything it still drains like crazy. I just text, make some phone calls and it barely makes it through the day. I don't play any games, no gps, no Bluetooth or anything. With my plan, I don't have a data connection so I can't connect to 3g/4g so that shouldn't drain anything.
What could I be doing wrong? When I'm done using the phone I tap the power button on top, the screen goes black - to sleep I presume and I put it away. I had an iphone before this and I did exactly the same thing and the battery lasted for 3-4 days on one charge.
Whenever I see what's using up the battery, the display tops the list. The display is using up 75-80% of the battery. If the phone is asleep for most of the time why is the display using up that much battery? Am I not putting the phone to sleep correctly?
Faizt20 said:
This is my first android phone and I'm wondering if I am doing anything wrong. Yesterday I charged my phone and it was at 83%. I unplugged the phone and went to sleep, when I woke up this morning the battery was completely drained.
This happens a lot. Even if I am not doing anything it still drains like crazy. I just text, make some phone calls and it barely makes it through the day. I don't play any games, no gps, no Bluetooth or anything. With my plan, I don't have a data connection so I can't connect to 3g/4g so that shouldn't drain anything.
What could I be doing wrong? When I'm done using the phone I tap the power button on top, the screen goes black - to sleep I presume and I put it away. I had an iphone before this and I did exactly the same thing and the battery lasted for 3-4 days on one charge.
Whenever I see what's using up the battery, the display tops the list. The display is using up 75-80% of the battery. If the phone is asleep for most of the time why is the display using up that much battery? Am I not putting the phone to sleep correctly?
Click to expand...
Click to collapse
If you cant connect to 3g/4g, you should turn it off in settings. Otherwise, Your phone will constantly look for a signal, draining your battery.
Battery life is all relative. Every single person will experience different battery life. The apps you have installed, the amount of time you spend on it and the time you spend on/in each app, distance from cell towers, distance from Wi-Fi sources, settings you have for every app and things like sync and what not.
The first thing to check is if your phone is being affected by the init or suspend bugs. The good news is the former has an easy fix, and the latter can be temporarily fixed by a reboot.
First, download & install Watchdog Lite from the market. Then open its preferences and check "include phone processes," "monitor phone processes," and "display all phone processes." Then just use your phone as normal. It may take a while before you get an alert from Watchdog (and maybe you never will and it ends up you have a different problem). But if you do, note the process that is the culprit.
If it is the init process, go to settings>applications>development> check "usb debugging."
If it is the suspend process, reboot the phone. It should keep it from happening again for a while.
I know the second answer isn't really an answer, but so far it's all we've got for that problem. There is more information on the 2 problems in these threads:
Init:
http://forum.xda-developers.com/showthread.php?t=839935
Suspend:
http://forum.xda-developers.com/showthread.php?t=872839
Good luck...I had both of the problems and my phone didn't last to dinner time. Now I get better battery life than the iphone 3GS I had before this...about a day and a half of moderate use.
EDIT: also you'll probably want to go to settings>wireless & networks>uncheck "mobile network" since you don't have a data plan. No reason to have that on since you don't have a data plan.
werk said:
First, download & install Watchdog Lite from the market. Then open its preferences and check "include phone processes," "monitor phone processes," and "display all phone processes." Then just use your phone as normal. It may take a while before you get an alert from Watchdog (and maybe you never will and it ends up you have a different problem). But if you do, note the process that is the culprit.
Click to expand...
Click to collapse
I installed this using the Moderate setting, and then selected those options as recommended in preferences.
Does Watchdog use a lot of system resources when running in this manner? Will it cause the battery to drain noticeably faster?
netter123 said:
I installed this using the Moderate setting, and then selected those options as recommended in preferences.
Does Watchdog use a lot of system resources when running in this manner? Will it cause the battery to drain noticeably faster?
Click to expand...
Click to collapse
Completely unnoticeable, IMO.
I installed watchdog lite and I have had couple of alerts. I got suspended couple of times and I also got Android system once.
Android system - 50.1%
Foreground
Suspend - 54.4%
Linux Process
I turned off the data usage from the settings and it did help save battery. The display is not using so much battery life anymore. It went from using 70% to 35%.
Edit: Battsatt reported that the battery was at 93%. When I saw the two alerts above I rebooted the phone and Battsatt now starts reporting the phone is fully charged.
Make sure the GPS is turned Off, too...
All these answers and the easy ones were not mentioned..
Make sure you shut your AUTO SYNC off...
Make sure you lower your brightneess....
Make sure you turn off GPS(was stated above me)
Turn off your wifi if you are not using it.. make sure you are not transmitting your hot spot stuff...
Faizt20 said:
Suspend - 54.4%
Linux Process
Click to expand...
Click to collapse
You just summed it up right there. You are experiencing the 'suspend' issue, period. There is no app you can install to fix it. There is no app you can uninstall to fix it. There is no setting you can adjust to fix it. There is no fix for the 'suspend' issue, literally.
I started the following thread in an attempt to consolidate posts and hopefully work toward flushing out what the real issue is...
http://forum.xda-developers.com/showthread.php?t=872839
This is a real, legitimate issue with Android 2.2.x Froyo. As I linked in my post, this is Issue # 11126 on Google Code...
http://code.google.com/p/android/issues/detail?id=11126
If there was an app or setting that fixed the 'suspend' issue, we wouldn't even be discussing this right now. There are fixes/workarounds for a lot of things, but right now, the 'suspend' process issue truly is a mystery. No one, not a single person has yet to post, "this is the cause of the issue," let alone a fix for it.
I wish you had a fix man, I really do. My fiancee experiences this and there's only one way she's found to sort of workaround it, sort of - she reboots her phone every morning. This seems to keep it at bay, at least more so than when she doesn't reboot each morning, once she takes it off the charger. She still gets it though and she's just used to looking for Watchdog and checking her processes now.
This thread could go on and on forever but it comes down to this:
- The MT4G does not have insane battery drain and will give you about 12 hours of life, under normal>medium usage. If your battery is draining insanely quickly AND if you're seeing the suspend process jacked up so high, then there.is.no.fix.yet.
There might be a ton of other replies after this about uninstall this, install that, change this, don't use widgets, use widgets, etc. Those attempts will be futile.