Related
I switched from a highly modified DroidX (which I still own) to a new Charge recently (which I absolutely love).
The X had GB flashed with Liberty ROM and the battery life was really exceptional. It did increase when I swapped from froyo to GB, but I don't really remember how much. Using the VZ extended battery (the small one that fits into a stock case) I easily got a full days use out of it with GPS always running, weather updating every 30 minutes, gmail running push and Bluetooth on quite a bit. I can't remember ever once having to swap out the battery before I got home from a day at work.
With the Charge, on the very first boot (before it was even activated), I opened it in odin and flashed to gummycharged 191. The thing runs totally awesome, fast and fluid as hell-completely lag free and has never frozen up once. It blows away the X in every way except battery life.
Today, I started on a mugen 1800 battery and ran that until it had 2% charge left. That took about 4 hours running EXACTLY THE SAME apps that I always ran in the X. I then stuck in an aftermarket 1800 battery and ran that one until it was totally dead also before I left work.
Other than the battery life, I am 100% totally happy with the swap from the X to the Charge. I have three extra batteries and an external charger for the Charge, so having to swap batteries etc is not the end of the world, but I am wondering how much better the battery life would be if I swapped to a GB ROM at this point??
I am open to any/all suggestions at this point......
~John
to add to this, I am running LPP+ launcher with the identical screen/widget setup as I was running in the X.
~John
There's three things you need to be aware of for battery life for this phone:
1. Your kernel - This affects your battery, not the ROM.
2. The screen - The screen is awesome on this phone, but unfortunately it is a battery killer, this can be solved by turning off auto brightness or downloading the Screen Filter app. The screen is also the main draw for the battery in terms of drain.
3. The 4G LTE Radio - this is the largest difference between your last phone and this. If you live in an area where your LTE is spotty, I suggest turning off your LTE and leave it at 3G CDMA. An easy way to get to the toggle is to download the LTE Switch from the Android market. The reason the LTE destroys the battery is due to the fact that your phone is constantly searching for an LTE signal, thus draining the battery faster than a non-4G phone would. If you're in a strong LTE area, it shouldn't affect it much, but turning off LTE does help the battery in most cases. The LTE radio is the second main draw of battery power.
Finally, be sure to remember to wipe your battery stats after flashing the new ROM and fully charging your phone to 100%. Hope all this helped!
EDIT: Also be wary when flashing to one of the Gingerbread leaks. People have been getting mixed signals in terms of battery life, since the leaks aren't exactly stable. I tried out GB for awhile, but wasn't too fond of the instability that Froyo still offered, so I flashed back after a week.
I turned off the auto brightness setting immediately. I run it on 25% most of the time, i only turn it up when I'm outside.
I have been thinking about trying a few different kernels to see what difference that makes, any recommendations as to which one might be best?
I did calibrate the battery after flashing the ROM.
I do have the 4g switch (and I'm in a 4g area) but I haven't tried running for a day in 3G. I think I will try that tomorrow and see what difference it makes.
~John
jmorton10 said:
I turned off the auto brightness setting immediately. I run it on 25% most of the time, i only turn it up when I'm outside.
I have been thinking about trying a few different kernels to see what difference that makes, any recommendations as to which one might be best?
I did calibrate the battery after flashing the ROM.
I do have the 4g switch (and I'm in a 4g area) but I haven't tried running for a day in 3G. I think I will try that tomorrow and see what difference it makes.
~John
Click to expand...
Click to collapse
Kernels–if you don't care about overclocking I recommend imnuts non–OTB kernel.
Sent from my Droid Charge running GummyCharged 2.0
First of all, hi XDA! I wanted to use my beginning thread to praise the people here, but sadly problems has occurred with my phone, details below:
Post Root and flash to CM7.1 offical, my phone was fine to begin with, I noticed only a slight improvement in battery life, which was much improved when I flashed Tiamat 1.13 kernel which, fantastically, doubled my battery life on a day to day usage routine. However some time later I stumbled across the thread on this forum listing how to best get maximum battery life from the Desire S made by LaKraven in the Desire S General section.
Which I followed and took the necessary steps to further improve my battery life. It kinda worked. What seems to be the biggest problem is the battery configuration, which I attempted two times. Two problems occurred the first time, even though the phone was charged up to a 100 percent it still listed the battery meter at 99 to my annoyance. I went ahead and re-calibrated the battery using the app mentioned and whittled down my battery to full discharge. Charged it up full as per the XDA thread suggested and again used it until it was discharged, however this time I made the mistake of allowing the phone to the battery for a good few hours after the green light was on.
I thought the only reasonable thing to do was to again re-calibrate the battery, since the over charging derailed the process. Re-attempted it and everything went well.
But then the ‘fallout’ began. Since re-calibrating, I have had a worse battery life then I did whilst I was on stock. I thought the radio was to blame, but the battery drain happens no matter what I do with the device. Internet, video, music, using apps, even browsing though options make the battery drop almost like a stone. On stock, a 1-2 hour constant usage would drop the percentage around 20%, on CM7 and Tiamat Kernel before calibration, a mere 6-8%. But now it results in a 30% drop, with battery saving features applied. I re-calibrated a week ago, and allowed the battery to 'settle in' as per the thread linked suggested, but it has made no difference.
It happens when the device is on standby as well, without airplane mode enabled and quiet mode on, there is on average a 5-7 percent drop in battery life. With airplane mode on, it stays high, but drops a few points only a minute after airplane mode is off. A total contrast to stock, where the overnight standby resulted in no battery loss at all. With or without airplane mode on, surprisingly.
Interestingly enough, games don’t really tax that battery that much, Samurai vengeance 2 drains less battery then Jorte does when making my weekly schedule, usually a 15 minute task. The same goes for other, less demanding games, like Game dev story or PewPew.
Continuing from this, oddities occurred after calibration, firstly whatever percentage I charged up to (e.g 75) would result the battery staying at that level for a unusually long time, but as soon as it drops to the number below the drain kicks in all over again.
Secondly, whilst the phone is charging, performing my daily reboot results the phone shooting up 10 percent in battery charge which only happened post calibration.
Stats from the battery section in the 'about phone' menu in the option menu lists mobile standby and phone idle as the biggest battery eaters, at 32% and 29% respectively. Wifi is listed at 3 percent.
I'm at a loss on what to do, and thought it would be best to consult much better experienced and knowledgeable people on the matter.
Finally, using the clockwork mod boot into recovery option results in the phone freezing when the blue android robot and file is displayed. Any help on how to sort this out? I would really like to get the honeycomb boot animation on my phone.
Thank you for reading a long post!
Hello, First things first,I'd suggest returning to basics, I'd even go as far as suggesting installing a stock based ROM like hyperion
I'd recommend that you perform a Full wipe ie factory reset, format all partitions to ext4 using the 4ext recovery, I'd also suggest that for the first few days you try to install as few applications as possible.
Install battery monitor widget, setting battery capacity to 1450, , then full charge and perform the battery calibration and start again.
You never mentioned what hboot and radio version you have so please re-post this information
Swyped from my Desire S using XDA Premium
Hey, thanks for the info so far!
My radio is: 3805.06.02.03_M
My Hboot is as follows: 6.98.1002
Whilst readying the phone for re-flashing, I thought to check the tiamat kernel thread since I have read around the net that different ROMS require different kernals in order to operate effectively.
It lists on the thread that it offers no suuport for ROMS built on sense. Will Hyperion flash it's own kernal? If not, will there be any adverse or permanent damage resulting from a sense ROM and tiamat kernel combo?
Well! I reflashed the phone to CM7 (missed the look of it when I went with Hyperion) and did the battery calibration once again. It solved the problem! Phone is now having awesome battery life and I have tiamat 1.15.
Thanks for the help, much appreciated.
Now to solve that pesky recovery problem!
Here is my situation:
I flashed CyberGR v.11 with air kernel (weekly 05/08/12) yesterday.
I woke up today with a dead phone. I realized it was out of battery (I went to bed with around 30%).
Throughout the day today, i noticed whenever I wake up the phone, the signal would go from no bars to full bars. I went to settings>battery and checked the "History details" and saw that during sleep, the mobile network signal colour is either red or yellow.
So that explained why i woke up with a dead phone. Searching for signal KILLS battery.
Today CyberGR v.12 came out, so i decided to flash that rom (with a clean install from CyberGR's instructions) but this time with morfic's t12 56hz kernel. I thought maybe it was because i had deep idle on when i had air kernel, but instead of testing with deep idle off, i decided to update to v.12 since it came out and tried a kernel without deep idle. Nothing changed.
I'm on ondemand, and have tried up to min 400mhz to see if that it'll keep my phone from losing signal when it sleeps, but it didn't help.
I also tried changing my radio from KI1 (which, from user experience from this thread says is most ideal for my network WIND mobile) to KF1, but that didn't help either.
I have the i9020T from WIND that i got in january. I did not have problems when i was using BM's 3.0 ICS and gummy 1.0.4 (both with air kernel and DI on), but i did have initial problems with those two roms when i first flashed them. I would randomly lose signal throughout the day, but after a day or so it wouldn't lose connection.
Also, i've been getting a lot of radio_dump_[date and time].bin files in my sdcard since this issue surfaced.
I am fairly new to android (this is my first device) and if anyone could help me fix this issue, it would be greatly appreciated.
Thanks for reading my long post!
Intermittent faults are really difficult to diagnose. Do you get the exact same issues with all radios?
I've tested the KI1, KD1, KF1, KB3.
It actually got worse with the other radios. Before, my phone used to reconnected with my network when i woke it from sleep automatically, but now it doesn't do that and it can't even search for available networks.
Also tested with matrix 19.5 and the new stable air kernel, but to no avail...
Hey Guys,
Let me start by saying that I've spent the better part of 3 days searching XDA, google, reading various other forums for answers to my problem before I decided to post this. Even if the answer was close, or for a different phone I tried all the recommendations to no avail.
I recently just got into the whole rooting and flashing thing. I first tried cyanogenmod9 nightly, and then Embryo 3.2 which I immediately fell in love with. When I flashed, I followed the instructions step by step - wiped all the data, cache, dalvik, formatted then did it all again. Everything is working without a problem. My issue is that cell standby and phone idle is absolutely crushing my battery. I went from getting 17+ hours of normal use with room to spare before charging for the night to barely getting through a day of work.
I installed better batter stats, badass battery monitor, and as a last ditch effort juice defender - hoping that if I let it control the radios and have them off it would curb the problem. Juice defender checks my emails n' all once an hour and it's no help at all. I've burned up almost 20% in 4 hours and i haven't even touched my phone except to see if JD was actually working. Badass battery monitor shows the radio as the biggest drain, and better battery stats... well, frankly, the info it reports is WAY over my head..
My phone is a fresh install of Embryo 3.2, UCLE2 radio, and cymbaline 1.5 kernal. I'm running go launcher, beautiful widgets for time/weather, and go contacts widget. That's it. I read about the phone idle, charged it to 100%, cleared the battery stats in CWM trying to calibrate it and it seems to have done nothing.
Also, I understand the radio works different for everyone. I think my issue is that if UCLE2 is from 2.3.6 OTA, which is what I was using post root/rom, and what i'm currently using now.. why is it a problem now vrs before?
Should I just download all the available radios for the skyrocket, and try a new one every few days to see which works better?
I'm really just seeking a comprehensive answer to my problem which I can't seem to find anywhere. I wouldn't have posted this if I didn't believe I exhausted all my available options. sorry for the wall of text and thanks for taking the time to help!
It's very obvious that many, many people have this problem, but everyone tries to tell you to battery saving tips that just help to cope with the problem but don't fix it at all.
UCLE2 is not from 2.3.6, it's from the second most recent 4.0.4 leak, by the way. I don't really think this is a radio issue, though I did notice I have a problem in UCLF3 and UCLD2 Odin, but not in UCLE2 or Gingerbread. I'm convinced it's something to do with how these ROMs are flashed. I'm going to try CWM to UCLF3 from UCLE2 and see how that goes.
Yea, please let me know what you find. I'll try a new radio when I get home. I'm not going to bother trying to flash a new rom, or this one over again as i've already done it multiple times - the issue has not changes...
cell standby, phone idle..
Get rid of jd first. It makes ics worse. In fact better battery stats is the only "battery assistance" you should keep. Then reflash everything. If you restore with titanium backup, don't restore system data. You'll have to re enter your email accounts and stuff but your contacts should sync once you do. And every time you flash a new ROM it needs a few days to settle. It will burn extra battery in those few days. And I don't know how go contacts widget works, but it may have some interaction with the phone apk that mohan hasn't engineered for, keeping it awake. I'd go without it for awhile too and see if that helps.
Also get CPU spy. To see if your phone's getting any sleep. You could be having some kind of wake lock. Reboot when you pull it off the charger.
Sent from my part of the problem
I think it is in part a wake lock problem, however rebooting after taking it off the charger doesn't help.
st0nez0r said:
Yea, please let me know what you find. I'll try a new radio when I get home. I'm not going to bother trying to flash a new rom, or this one over again as i've already done it multiple times - the issue has not changes...
cell standby, phone idle..
Click to expand...
Click to collapse
New radio won't change that. Unless you're not using the one mohan provides in the embryo thread. Something is bugging out the phone apk. You may want to try embryo 3.2 without the cymbaline kernel also, and see if that's any better.
Also I should say again, whatever is causing your drain problem, jd is making it worse.
Anything that might be keeping the phone awake. Maybe a Bluetooth or like I mentioned, possibly the go contacts widget.
Sent from my part of the problem
boobah204 said:
Get rid of jd first. It makes ics worse. In fact better battery stats is the only "battery assistance" you should keep. Then reflash everything. If you restore with titanium backup, don't restore system data. You'll have to re enter your email accounts and stuff but your contacts should sync once you do. And every time you flash a new ROM it needs a few days to settle. It will burn extra battery in those few days. And I don't know how go contacts widget works, but it may have some interaction with the phone apk that mohan hasn't engineered for, keeping it awake. I'd go without it for awhile too and see if that helps.
Also get CPU spy. To see if your phone's getting any sleep. You could be having some kind of wake lock. Reboot when you pull it off the charger.
Sent from my part of the problem
Click to expand...
Click to collapse
Alright, thanks.
I've done as you suggested and will report back.
I've installed BBS and CPUSpy. (I don't know how to read bbs, so perhaps point out some things i should keep an eye on would help.. )
I've removed juice defender, go contact widget, and badass battery monitor. I'm pretty much stock except for go launcher ex and beautiful widgets for time/weather.
I'll also remove and reset the battery cache in CWM
When i get home tonight i'll re-wipe/format etc etc and start from scratch again... *pout* lol
boobah204 said:
New radio won't change that. Unless you're not using the one mohan provides in the embryo thread. Something is bugging out the phone apk. You may want to try embryo 3.2 without the cymbaline kernel also, and see if that's any better.
Also I should say again, whatever is causing your drain problem, jd is making it worse.
Anything that might be keeping the phone awake. Maybe a Bluetooth or like I mentioned, possibly the go contacts widget.
Sent from my part of the problem
Click to expand...
Click to collapse
Yep, thanks for the info. I won't change the radio, and i'll keep using whats in mohans embryo thread. I'll re-flash and leave off the kernal (which, i like because when i talk on phone it doesn't get hot like it used too).
I removed JD, contacts widget, and everything else except data is off.
What specifically should I be looking for under CPUSpy and BBS
THe phone has currently been on for an hour and 50 minutes
spu spy states deep sleep of 80% for 1:26:28
and bbs under "other" reports 69.4% for both no or unknown signal and no data connection for 1hr and 16 min both
st0nez0r said:
I'll also remove and reset the battery cache in CWM
When i get home tonight i'll re-wipe/format etc etc and start from scratch again... *pout* lol
Click to expand...
Click to collapse
No, don't do any of that and don't reset the battery cache in cwm. This might be your problem actually. When you reset battery in cwm you essentially make a new 100% mark. Like, if you do that when you're at fifty percent battery, you just cut your Max battery life in half. So do THIS when you get home. Turn the brightness all he way up. Download angry birds or something and play it until your phone is dead dead DEAD. Then plug your phone to the OEM charger. The one that has a USB plug on the wall end. Let it charge all the way when it's turned off. Then when you turn it back on, hold power and volumes and go straight to recovery. That's the correct time to reset your battery cache in cwm.
Sent from my part of the problem
st0nez0r said:
(which, i like because when i talk on phone it doesn't get hot like it used too).
I removed JD, contacts widget, and everything else except data is off.
What specifically should I be looking for under CPUSpy and BBS
THe phone has currently been on for an hour and 50 minutes
spu spy states deep sleep of 80% for 1:26:28
and bbs under "other" reports 69.4% for both no or unknown signal and no data connection for 1hr and 16 min both
Click to expand...
Click to collapse
Keep everything the way you have it now and do he charger thing. If you're at&t. If you're rogers change to ruxlf3 radio. Actually trying a different radio may not be a bad idea but give each one a day to see how it does. See if that "no or unknown signal" in bbs changes. You aren't having wake locks. Deep sleep is what you're looking for in cpuspy. I think jd turning on and off the data and searching for a new signal caused a lot of the burn so far. Are you in an LTE area? The other thing to do is make sure your apn (settings > more > mobile networks > access point names) matches what is listed in the embryo thread. Keep your kernel and don't reflash anything except a radio. Try ruxlf3 or u...f5 tomorrow.
Sent from my part of the problem
boobah204 said:
Are you in an LTE area? The other thing to do is make sure your apn (settings > more > mobile networks > access point names) matches what is listed in the embryo thread.
Sent from my part of the problem
Click to expand...
Click to collapse
I'm in AT&T and I work smack dab in the middle of an LTE area with good signal.
I live 60 mi from work, in a non LTE area but still have good signal.
My apn settings were actually set by the phone when i received a call straight after flashing. Att PTA - internet + mms, i'll check mohans thread and see what's up there.
THanks a lot for your help, I really appreciate it.
Ok, I've had some luck getting normal-ish battery life (~15 hours). Still seems a little below what it should be and performance is also slightly sluggish compared to stock, but it's clearly miles better than the dead in 7 hours life I was getting.
Now, I don't know if I just got lucky finally or if any of this actually helped, but here's what I did:
* Flashed UCLE2 with Odin.
* Ran battery all the way down
* Charged battery all the way up with phone off. Unplugged it, left it off, and recharged it a few times.
* Wiped battery stats
* Odin flash CWM (NON-TOUCH version this time)
* Darxide Superwipe (x2)
* Flash CM9, Gapps
* Boot
* Darxide Superwipe again
* Flash CM9, gapps again
* Boot, drain battery all the way down
* Charge battery all the way up while phone is off.
Again, not saying this is a fix just saying what I did in as much detail as possible in case it helps anyone.
just go download embryo 4.0 fast and stable.
http://forum.xda-developers.com/showthread.php?t=1754473
I've been running Synergy/Ziggy combo for a while now and recently noticed I'd drop network connection while still being able to do regular phone stuff (text/call). I discovered I was running KT1 or some other older baseband and figured I'd throw on MF1 with an AIO zip install. After figuring out a workaround to getting the camera to work I was psyched as 4g lte was coming in strong and speeds seemed to have resumed their regular pace.
Problem is that I've noticed my battery life has pretty much crapped the bed now. I used to ride to work with Pandora playing with wired headphones and noticed I'd get to work with about 95%+ battery life. By the time I was at work, it showed high 80s. With very minimal use by lunch time I was showing down to the high/mid 60% mark where I'm still usually at around 70-80% with random facebooking, texting and instagram stuff. None of which I really did as I wanted to see whether the battery death was in my imagination.
Anyone else notice issues with battery life after flashing new firmware? Is it possible my phone's still working out which towers to lock onto with the new antenna?
Look at your battery stats, if android system is at the top, then you need to do more investigating. I would fix permissions and or flash the kernel again to start.
Surge1223