Related
I've had my battery replaced, I've wiped my phone from ROMs, and I've used aggressive SetCPU profiles...
What is annoying though is setCPU recently updated and I decided to see how my phone ran without it.. battery life is horrific with a simple UV kernel.. Why is this?
I mean I take my phone off the charger at 11am and by 10pm its less than 15% remaining. I now have a second battery from HTC after a warranty replacement but I saw very little change. I have a task manager that auto kills everything now which helps but it is annoying since I lost my car charger my phone is discharging all day.
Is this normal and I'm just freaking out or do I have a real problem?
Running Kang-o-rama ROM with ~20 apps
I know 3 things about the N1 battery:
1) it took a couple of weeks for my battery life to max. Lithium batteries need a break-in period. They have no memory, and the recommended approach of not using the phone until it's full charged is bunk. Just use it normally and it will work as it should.
2) Switching between 2G and 3G constantly murders the battery, 4 hours and you're dead. If you're going to be in an area like that for a while, force it to one or the other.
3) Watch your apps. If your phone is acting even slightly sluggish it's CPU is maxed which is killing your battery. Slowly swipe between homescreen pages, it should be silky smooth without any stutter. Try and track down which one it is and either install/reinstall (which fixed an issue with Better Keyboard for me) or completely uninstall if you can't fix it. Check for apps that ping the network too often, or ones that start up on their own.
I will add that the built-in 2.1 battery usage tracker is not 100% accurate. In my Better Keyboard example, Android said it was the screen using all the juice, not the app. Might have to do with video graphics drivers, I really don't know. Point is, after uninstall/reinstall my screen used 55% of my battery instead of 75%, so don't trust it.
XFreeRollerX said:
...I mean I take my phone off the charger at 11am and by 10pm its less than 15% remaining.
Click to expand...
Click to collapse
Are you kidding? You're running your N1 for nearly 12hours and you STILL have 15% juice left?!?
Search the forums, 12hrs and still having juice left would be considered excellent to many.
...Then again, you haven't mentioned what your usage is like. If we were talking about your phone being in sleep mode for most of those 12hrs with just an occasional call or 2 that only lasted very briefly...Then that's a different story.
Have a look at Juicedefender, it will limit your internet access to 1Min on every 15Mins when the phone is asleep/screen is off. Does wonders for battery life
I can't post in the Development area yet, so I'm posting it here.
2nd day using CyanogenMod 7, and here's my feedback:
- Very stable
- It seems to have solved my Nexus One touchscreen issue. I've tried CM6 and Enomther before, and this was never resolved before.
- The Wifi is stable with no drop (is it because of the new radio in CM7 ??)
- Super duper battery life!! Even way better than Enomther. By noon, usually I'm at 81-85% with very light activities (browsing, reading emails, etc) and nothing running on the background except Corporate Email and a couple GMail accounts sync. Today it's still 89% and this is fabulous. Note that I've set the Wifi to "Never Sleep". The battery life is SIMPLY AMAZING!
- I can't notice speed differences with ENomther.
- I couldn't care less for the animation or eye candies, but the touchscreen keyboard fix, wifi stability, and long battery life are very important. FYI I wiped everything (data, Dalvik Cache, battery stats, rotation, etc)
THANK YOU, CYANOGEN!
you should judge your battery on a whole days worth of use. The ~5% difference in a couple hours could easily be made by one app or game being run. I'm getting ~36 hours out of my MIUI setup. Though I block and limit many background syncs.
No doubt CM7 is great, huge step from what many android phones are stuck with out there. ps, CM7 doesn't include a radio.
foreverwinter said:
I can't post in the Development area yet, so I'm posting it here.
2nd day using CyanogenMod 7, and here's my feedback:
- Very stable
- It seems to have solved my Nexus One touchscreen issue. I've tried CM6 and Enomther before, and this was never resolved before.
!
Click to expand...
Click to collapse
What touchscreen issue?
And it still has the mic-not-working in a call problem, so it's useless if I can't use my phone as a phone.
My N1 has a touchscreen issue since day 1 ... seems to have been fixed in this release.
http://www.lmgtfy.com/?q=nexus+one+touchscreen+problem
Mic is definitely working here. Talked on the phone twice yesterday.
Battery life is definitely awesomeeeeeeee. I have 4 accounts in my N1 (2 corporates, 2 GMail).
Kimd41 said:
What touchscreen issue?
And it still has the mic-not-working in a call problem, so it's useless if I can't use my phone as a phone.
Click to expand...
Click to collapse
My gps loses its signal right after it gets a lock. I'm using CoPilot. Anybody having gps issues?
Sent from my Nexus One using XDA App
Yeah same experience here. What current draw are you seeubf during idle use? I'm seeing 4-5 mA which is great.
I don't think daily usage is a good way to determine battery life.
Best way is to see how much % drops overnight.
CM6 I was seeing 3-7% overnight, CM7RC4 I am seeing 7-20%.
Haven't had CM7 final long enought to check but first night I lost around 10%.
This is with all data off, 2G only and no services running apart from the basics.
behelit said:
This is with all data off, 2G only and no services running apart from the basics.
Click to expand...
Click to collapse
Yeah, that's totally the best way to determine usable battery life.
/sarcasm
LOL .. 2G and no services running?
I have GPS, Wifi, 3G all ON. 4 sync accounts (2 MS Exchange, 2 GMail). I have no Facebook sync, however. 3rd day ... still really amazed with the battery life. FWIW, I set the brightness to low (I don't need it that bright anyway) as usual. Same way I usually set it with my 2.2 Enomther ROM and CM6 and stock ROM. Battery life on CM7 is simply AMAAAAAAAAZZZZINGGG or maybe I'm just lucky
GPS locks in seconds, but I haven't done an extensive test with it yet. I'm going to use it (I have both CoPilot and Sygic Aura).
The only weird thing is that ADW Launcher closed and I had to reboot the phone once yesterday to bring it back on ???
Other than that, I'm super duper happy with CM7, especially the battery life
behelit said:
This is with all data off, 2G only and no services running apart from the basics.
Click to expand...
Click to collapse
Kimd41 said:
And it still has the mic-not-working in a call problem, so it's useless if I can't use my phone as a phone.
Click to expand...
Click to collapse
Search for and install "dewonkificator." It has fixed all of my call related problems, along with several others.
I also think that Gingerbread should be given much of credit for the Wifi fixes.
Im finding my battery getting eaten up noticeably faster from CM6 but its worth it for all the fixes/features.
best battery life ever, I pick my phone up ... IT'S COLD!
I've been using Kang-o-Rama 1.1, which is based on CM 6. I tried several different kernels and settled on the wildmonk kernel (2.6.35.10 though I'm sure there are newer versions now), because it gave me a similar excellent battery life as others have described here. I had been using various ROMs before that (those that are close to stock, with a few nice features added) and always had pretty bad battery life.
CM 7 therefore isn't necessary if you want stability (e.g. a phone that always works as a phone, no random crashes etc.) and excellent battery life. I'm cautious about CM 7 (and the soon-to-be-released Kang-o-Rama based on CM7) until the "wonkiness" issue is fully addressed - I don't consider having to install the dewonkifier program fully addressing the issue!
I like to have the latest and greatest, but having a potentially unstable phone is really annoying! Just have to be patient. Regardless, Cyanogen and everyone working on custom ROMs must be applauded for their efforts, don't know what I'd do without them
I have to say I'm a bit miffed about not being able to post in the development forum, which is the main reason I read xda...
Has anyone noticed a difference in battery performance between the first discharge and subsequent discharge cycles on the later cm7 builds? I've noticed that my phone will drains faster the over longer uptimes. The first discharge cycle after a boot discharges at an average rate of 3% to 5% per hour, averaged over a full day. Use over a full day for me is fairly light with some texting, one or two brief calls, and maybe some web and facebook. The battery is usually over 60% in after 8 or 10 hours on battery on that first discharge. After a full recharge, the drain rate on the next discharge seems higher. I've observed that similar use through a second discharge cycle is typically 5% per hour or more. I sometimes struggle to get more than 10 hours use out of the phone on that second charge.
I have noticed the Status Bar app seems to account for an abnormally large amount of battery use. Where's My Droid Power app reports the Status Bar consistently as the top power consumer on the device. Status Bar's power consumption in that first discharge cycle is usually reported around 10%, but jumps to 30% on subsequent discharge cycles. Other known power hogs consistently consume 5% to 6% according to the app. I don't know how the power monitoring app derives its data, but nothing shows up as strange in the Spare Parts battery history. I'm beginning to wonder whether the "where's my droid power" app's statistics gathering might be being baised somehow. It leads me to question my data.
So, does anyone have similar observations on frst discharge versus second discharge rates? Does anyone know what the Status Bar app actually does, and whether it might actually be contributing to higer battery drain? Finally, is there a better power monitoring app i should be looking at to track down rogue apps?
Solidgrue said:
Has anyone noticed a difference in battery performance between the first discharge and subsequent discharge cycles on the later cm7 builds? I've noticed that my phone will drains faster the over longer uptimes. The first discharge cycle after a boot discharges at an average rate of 3% to 5% per hour, averaged over a full day. Use over a full day for me is fairly light with some texting, one or two brief calls, and maybe some web and facebook. The battery is usually over 60% in after 8 or 10 hours on battery on that first discharge. After a full recharge, the drain rate on the next discharge seems higher. I've observed that similar use through a second discharge cycle is typically 5% per hour or more. I sometimes struggle to get more than 10 hours use out of the phone on that second charge.
I have noticed the Status Bar app seems to account for an abnormally large amount of battery use. Where's My Droid Power app reports the Status Bar consistently as the top power consumer on the device. Status Bar's power consumption in that first discharge cycle is usually reported around 10%, but jumps to 30% on subsequent discharge cycles. Other known power hogs consistently consume 5% to 6% according to the app. I don't know how the power monitoring app derives its data, but nothing shows up as strange in the Spare Parts battery history. I'm beginning to wonder whether the "where's my droid power" app's statistics gathering might be being baised somehow. It leads me to question my data.
So, does anyone have similar observations on frst discharge versus second discharge rates? Does anyone know what the Status Bar app actually does, and whether it might actually be contributing to higer battery drain? Finally, is there a better power monitoring app i should be looking at to track down rogue apps?
Click to expand...
Click to collapse
There is a bug in the status bar process. If you have battery percent enabled in the status bar, when you plug in the charger, the status bar process uses 10-30% CPU for the next hour during charging. If you disable batt percent and charge this does not happen.
I looked at the source code and was gonna try a fix soon.
On previous cyan 6, charging temp disabled the percent. Also this slows things down and home screen scrolling gets super choppy.
RogerPodacter said:
There is a bug in the status bar process. If you have battery percent enabled in the status bar, when you plug in the charger, the status bar process uses 10-30% CPU for the next hour during charging. If you disable batt percent and charge this does not happen.
Click to expand...
Click to collapse
I do have battery percentage enabled, so that could explain that. Thanks for the feedback! I could convince myself I tried disabling battery percentage before, but who pays attention to the little things when you're having so much fun?
Oh, and an update on the battery discharge thing. I left my Wifi on full time after my last full charge, and i'm about to roll over 2 days runtime with about 10% left. I haven't seen performance like that since i enabled a Corporate Email account.
Yeah I'm getting superb standby battery life on cyan #39 right now. Idle current draw overnight for 8 hours, with wifi on, is seeing 7 mA current drain steadily.
CyanogenMod 7 not working!
I just upgraded to the new CyanogenMod 7 on my Nexus 1 and unfortunately it is not loading. It gets to the CyanogenMod screen, with the Android guy on the stake board and the arrow going around him, but it just wont go passed that screen. It has never gone passed this screen.
What i have tried:
Taking out the battery and restarting it
letting it run for 30 minutes
If anyone one can help me I would greatly appreciate it
Regards,
What kernel are you guys using on CM7 for such awesome battery life? I've tried stock for one week, then redstar with minimal improvement.
I don't know if it's my imagination, but since the 2.4.6 update, my battery life has dropped a bit. By the time I get into my office from my morning commute, I'm anywhere in the 65-70% battery life after unplugging from a full charge. I haven't done anything new. I always unplug around 8:30 am when I head out, I do some light chatting with gf, browse some sites, check facebook (usually very briefly), and maybe sometimes do a little reading on my device. By the time I get into the office around 9:30 or 10 AM, I'm usually around the 80-85% area with battery.
Lately, doing the same thing, I'm seeing the aforementioned 65-70%.
Is anyone else experiencing decreased battery life since 2.3.6?
I'm on a Tmobile Nexus S, running stock 2.3.6 (no custom ROMs).
2.4.6 ? .... maybe 2.3.6 ... and yes, I also noticed a slight increase in power consuption after the upgrade. The stand-by is still great .. about 0.8 - 1% per hour.
Sorry, yes I meant 2.3.6.
Thanks for replying Ro_explorer. Is your increased power consumption significant? Seeing 65-70% when I'm used to seeing 80-85% as I get into my office, I find, is a large change. To be frank, the battery life of the Nexus S in general isn't so fantastic to begin with... this hit makes it worse.
Anyone else?
I used to get home with about 40-50% after a whole "normal day" (unplugged at 8AM, and getting back home at ~8PM) .. now (with the same average usage) I'm getting home with ~30-40% ... that why I said "slight increase" ...
Not your imagination, I too have noticed this. I hope the next update, will fix this - as I used to get pretty good battery life (even with over 250 apps).
When I recently updated to the 2.3.6, it caused a bug of continuous reboot (every 1-3 minutes), so I had to do a hard reset - now it works fine, but I only have added back about 15 apps - and the battery life sux!
Downgrade OS' it will be ok.
This is so weird. Why is the battery life worse?
onthecouchagain said:
Sorry, yes I meant 2.3.6.
Thanks for replying Ro_explorer. Is your increased power consumption significant? Seeing 65-70% when I'm used to seeing 80-85% as I get into my office, I find, is a large change. To be frank, the battery life of the Nexus S in general isn't so fantastic to begin with... this hit makes it worse.
Anyone else?
Click to expand...
Click to collapse
You want bad battery life? Try an Evo 4g with a Sense rom. I averaged about 6hrs using a 1500mAh battery, in stock form.
The nexus is pretty light on power consumption, if you ask me. I average 15hrs on the stock 2.3.7 rom/kernel combo, with stock battery.
Sent from my Nexus S 4G using XDA App
I'm on 2.3.6 and need to charge every two days. I text a lot and do light gaming. I'm typing this from my phone. Maybe you could drain the battery and wipe battery stats? I'm not even at 50% yet and I charged yesterday.
Sent from my Nexus S using Tapatalk
I also noticed that the battery last less time
I've been waiting to see if anybody else reporting this issue
i noticed a decent increase in battery life going to 2.3.7 and thought that previously the battery life had been fairly poor :\
I am non rooted, and get around 20 hrs on light to moderate use. Again. Stock, non rooted.
How do I recalibrate my battery? I wonder if it could be that...
There are many was to recalibrate. Some involve wiping batt stats, some plugging and unplugging phone several times after charge.
I have always found that using the battery almost all the way down, but not past 5%, and then full recharge conditions it very well.
Oh I've been here to solve the problem
"Why last 2 weeks my Nexus s drain battery so fast ? or I have to calibrate it"
Thank for your notice about update OS to 2.3.6.
I think that's a root cause for me too.
1. Could I rollback to 2.3.4 ,how?
2. Does battery calibration is useful for this case , how?( someone suggest to calibrate when flashing new rom )
Thank you very much..
i want to know who have some methods to do with this stuff
borrowedchief said:
There are many was to recalibrate. Some involve wiping batt stats, some plugging and unplugging phone several times after charge.
I have always found that using the battery almost all the way down, but not past 5%, and then full recharge conditions it very well.
Click to expand...
Click to collapse
Whenever switching roms, kernels, or batteries, i always perform the following :
1. Charge to a true 100% (Battery Monitor Widget will register +0 to +2 mA)
2. Wipe battery stats using recovery (Amon RA has this option for the Evo, not sure about cwm), Battery Monitor Widget, or a dedicated app.
3. Discharge battery to 0% with normal usage. When the phone shuts down, I pull and re-install the battery and power back up (it will shutdown again very quickly).
4. Recharge battery and be on my merry way.
Sent from my Nexus S 4G using XDA App
I found one workaround solution for this issue on
ww.google.com/support/forum/p/Google+Mobile/thread?tid=1684c50cea15282a&hl=en&fid=1684c50cea15282a0004af022e5ed212
Sproogle77 's solution
Problem solved. Using the OS Monitor app, I found that the main culprit was Google Services - the Contacts sync specifically. Even though I had this disabled (only Gmail was being allowed to sync) it was constantly working, apparently trying to fix a location. The message log showed that it was generating continuous debug messages, all about locations - around 10 of these every second.
I have solved the problem by disabling 'Use wireless networks' under the Locations & Security settings.'Use GPS satellites' is still running. This immediately dropped my CPU usage - which had been running around 30 to 40% even when otherwise idle, to around 10%. Google contacts sync is now using 0% of the CPU. The difference in battery life was pretty much immediate and is now back to what it was before - the change in the slope on the battery usage graph is remarkable!
This doesn't really seem like a solution to me, and I don't know whether other aspects of my functionality are being affected, but at least my phone is properly useable again.
I'm testing for 1 day and I think that's working for me.
onthecouchagain said:
This is so weird. Why is the battery life worse?
Click to expand...
Click to collapse
One reason is that the new version of the stock kernel removed a speed stepping, so it'll power to higher levels faster, thus using more battery.
rentaric said:
One reason is that the new version of the stock kernel removed a speed stepping, so it'll power to higher levels faster, thus using more battery.
Click to expand...
Click to collapse
That actually isn't the problem. I'm using netarchy's kernel and still get this problem.
My battery life dropped from 16 hours --> 6 hours. the slope on my battery usage life is horrible the system is also awake almost constantly even when I'm not touching it / getting no messages.
I will try the fix suggested on the google support forum and see if that does the trick. sloppy update.
I have an extended battery (1500mah) vs the OEM 1300mah. I run MIUI and Incredikernel. I was getting good battery life. My phone was lasting all day up until the about 2 weeks ago. I havent changed ROM's or kernels for well over a month.
My battery now on a good day will go 10 hours or so and be totally drained.
Just wondering what it could possibly be? The only thing I can think of is I added PlayerPro and have a widget on one screen and I put about 4-5Gbs of music on my SD Card. That is all I have changed.
Anyone have a clue? I may consider switching kernels.
Hard to say, but I would suspect a rogue app...have you tried system panel or watchdog to see how long apps run in the background?
Alright, so I'm not a very heavy user on the phone but I've started getting 36 hours of use on my phone. I was blown the hell away! I usually would get a Max of up to 25 or 26 hours or so before this. Even then a full 10 hours extra is magnificent!
Here's what I've got going on:
Running MIUI 2.3.23 ROM with Bulletproof Add On pack
Using Tiamat 1.1.5 kernel
Juice Defender Plus on Advanced mode
Recaibrated my batter with Battery Callibrator app
Overclocking at 1039 MHz and underclocking at 184 mhz using SetCPU
After calibrating my battery I let the battery run out completely a couple of times and voila!
I took a screenshot of my usage statistics but I can't find the damn thing now. I guess you're just got to trust me on this. This was definitely worth sharing.
All the best!
Sent from my HTC Desire Z using XDA
How many hours of screen on time did you have at the end of that charge? The longest battery life i've ever had for my phone was actually 3 days and 3 hours with 5 hours of screen on time. I'm a light to moderate user and i achieved that result with CM7.2 RC1 without any tweaks.
I really like the look of MIUI but i don't find it to be as fast as it really should be. I get frustrated by the scrolling lag that is present in the settings menu and the fact that video playback is much slower in comparison to other ROMs. Web pages were also always SO much more laggy in MIUI for me than on Sense or AOSP based ROMs. That's my personal experience, i think i've just about given up on MIUI and Sense based ROMs. I haven't touched either of those for a while now.
I get 36 hours normally with the stock Sense 2.1 ROM and Unity V10 kernel. Overclocked to 1Ghz with the standard governor.
I use it quite lightly though, 10 to 20 SMS, bit of internet / Facebook and 30 mins FM radio in the morning. Also accounts sync automatically, mail picked up every hour, data always on. That was with the stock battery, with the Anker 1600 mah I get to 36 hours with about 30% to spare!
On a side note, underclocking below 245Mhz has been know to cause problems. Standby of Death (or Sleep of Death), and possibly dropped SMS etc.
Craig
craiglay said:
I get 36 hours normally with the stock Sense 2.1 ROM and Unity V10 kernel. Overclocked to 1Ghz with the standard governor.
I use it quite lightly though, 10 to 20 SMS, bit of internet / Facebook and 30 mins FM radio in the morning. Also accounts sync automatically, mail picked up every hour, data always on. That was with the stock battery, with the Anker 1600 mah I get to 36 hours with about 30% to spare!
On a side note, underclocking below 245Mhz has been know to cause problems. Standby of Death, and possibly dropped SMS etc.
Craig
Click to expand...
Click to collapse
*sleep of death or SOD... i think S is for sleep not standby...
———————————————
i didn't mean to flame you, nor to mock you in any kind of way
thats quite insane @[email protected];;
i get about 13~15 hours of charge each time @[email protected];;
i use my phone mainly for texting and emails
no games on the phone...
i should give that a try, thats quiet insane ;o
lil-devil said:
thats quiet insane @[email protected];;
i get about 13~15 hours of charge each time @[email protected];;
i use my phone mainly for texting and emails
no games on the phone...
i should give that a try, thats quiet insane ;o
Click to expand...
Click to collapse
Hehe the word you're looking for is "quite" and not "quiet(as in low sound)".
Ace42 said:
Hehe the word you're looking for is "quite" and not "quiet(as in low sound)".
Click to expand...
Click to collapse
woops typo
magic_android said:
How many hours of screen on time did you have at the end of that charge? The longest battery life i've ever had for my phone was actually 3 days and 3 hours with 5 hours of screen on time. I'm a light to moderate user and i achieved that result with CM7.2 RC1 without any tweaks.
I really like the look of MIUI but i don't find it to be as fast as it really should be. I get frustrated by the scrolling lag that is present in the settings menu and the fact that video playback is much slower in comparison to other ROMs. Web pages were also always SO much more laggy in MIUI for me than on Sense or AOSP based ROMs. That's my personal experience, i think i've just about given up on MIUI and Sense based ROMs. I haven't touched either of those for a while now.
Click to expand...
Click to collapse
I'm not sure how much screen on time I had. I'll give it a check next time I'm monitoring my performance.
Sense UI has been a pain for me from the moment I started. I tried CM 7 but it had a bug where it wouldn't vibrate when I got a message unless it was in silent mode. Since I SMS quite a bit, it was quite annoying. I tried a couple of Virtuous ROMs too but they were glacial in their speed. Couldn't stand the lag.
I find MIUI to be the perfect balance between features, UI and speed. It might be a tad laggy in some places, but on the whole, it looks great, works great and doesn't give me problems in the parts I use the most. It doesn't seem quite as laggy with me as you seem to describe it. But anyhoo, for the first time since I bought my DZ, I feel like I have a good phone that I can rely on.
Thanks for your comments, man.
craiglay said:
I get 36 hours normally with the stock Sense 2.1 ROM and Unity V10 kernel. Overclocked to 1Ghz with the standard governor.
I use it quite lightly though, 10 to 20 SMS, bit of internet / Facebook and 30 mins FM radio in the morning. Also accounts sync automatically, mail picked up every hour, data always on. That was with the stock battery, with the Anker 1600 mah I get to 36 hours with about 30% to spare!
On a side note, underclocking below 245Mhz has been know to cause problems. Standby of Death, and possibly dropped SMS etc.
Craig
Click to expand...
Click to collapse
WOw! Really? Stock giving 36 hours! That's pretty sweet man. Never happened to me.
And thanks for the advice on the underclocking. Maybe I should up it a notch, just in case.
lil-devil said:
thats quite insane @[email protected];;
i get about 13~15 hours of charge each time @[email protected];;
i use my phone mainly for texting and emails
no games on the phone...
i should give that a try, thats quiet insane ;o
Click to expand...
Click to collapse
Go for it bro! And let me know if it works for you.
Right now, I've already hit 33.5 hours and have just hit 15% battery. And this is including a few games of Angry Birds. woohoo!
lunarplexus said:
After calibrating my battery I let the battery run out completely a couple of times and voila!
Click to expand...
Click to collapse
Letting the battery drain to shutdown is not a good idea. Not good for long term life of Li ion batteries. Also, its unlikely, but possible that draining to shutdown will render the battery unable to take a charge. Fail safes on the device and battery are supposed to prevent this in theory, but in reality they don't always work. Several reports on this device of people that drained to shutdown, and then couldn't charge their battery.
The battery meter is not accurate enough to necessitate draining to zero. Just drain to 10 or even 20%, charge to full, repeat a couple times. No value added whatsoever to draining to shutdown.
I have easily gotten 48 hours+ with light usage on various ROMs, including ILWT and Virtuous Unity (which is Sense 3, and claimed by some to be a "battery hog"). This is with Bluetooth and WiFi always on, and no special battery calibration or battery saving apps.. So many things affect battery life. But my personal hunch is that the ROM, clocking, radio, and data reception in your area (and of course usage) have more to do with battery life than other factors. And with radio and reception being the really big drivers.
That's definitely very helpful. I've always heard that rechargeable batteries are supposed to be drained completely and charged at least periodically to extend its life. Your proposition is contrary to this belief but then, I don't know that much about the battery and those aspects of the device itself to be able to refute what you're saying. Best to be on the safe side though.
Current record for my battery is 42 hours as of today. I'm pretty thrilled. My device was giving at least 10-15 hours less before I made these customisations. So I feel it probably has helped. However, there are a lot of factors at play, as you said.
Thanks for the response!
lunarplexus said:
That's definitely very helpful. I've always heard that rechargeable batteries are supposed to be drained completely and charged at least periodically to extend its life. Your proposition is contrary to this belief but then, I don't know that much about the battery and those aspects of the device itself to be able to refute what you're saying. Best to be on the safe side though.
Click to expand...
Click to collapse
There are various types of rechargeable batteries with very different behaviors. What you mention is known as battery conditioning, where you periodically drain to (nearly) empty and charge to full, and is recommended for older type NiCd (nickel cadmium) batteries. This is to avoid "memory effect" where the battery will remember how much was discharged in past cycles, and not deliver any more than demanded before. Kind of a "use it or lose it" principle.
Lithium (Li) ion cells (the type on most smartphones) do not suffer from memory effect. And full discharge cycles actually hurt the long term life of the battery. Charging frequently is actually the best for this type of bettery. But a couple nearly full cycles are needed to properly calibrate the battery meter on the phone.
If you want to educate yourself on the Dos and Don'ts of batteries, this website is a good one:
http://batteryuniversity.com/