Related
Some battery threads:
http://forum.xda-developers.com/showthread.php?t=978269
http://forum.xda-developers.com/showthread.php?t=1004760
updated tl;dr for most of you lately:
Your problem is probably that you flashed a new ROM or kernel recently, which causes battery stats to be very inaccurate. The most common symptom is that suddenly the battery drains like crazy, when before it just dripped. The opposite can also happen - you flash a new ROM and it seems like the best battery life ever. Until it suddenly jumps from 60 down to 10. This can happen even if you erased stats after flashing. You need a few days with your new ROM first, then you should see what your battery usage is really like. Do full charge cycles to speed up this process. (Bump charge, erase stats, drain, charge, don't bump charge or erase stats anymore, drain, charge, drain, charge, etc.) Simply put: you cannot judge battery performance after flashing a ROM. Often it can be a week or more before battery performance and battery level reporting becomes stable.[/tl;dr]
Every time a chef makes a new ROM available, or even among those using stock OS, there seems to be wildly inconsistent feedback on battery life. Many report catastrophic battery drain, while others using the same hardware/firmware/kernel/ROM say it's the best battery life they've ever gotten.
It would seem that a battery can run away on you for a variety of reasons, and flashing back, or returning to the store, doesn't have to be the first thing you do to fix it. This thread is to consolidate many of the complaints around xda about sudden battery drain, and discuss proven (or superstitious) fixes for it. This is not another discussion on tips and tweaks to extend battery life. There's a good wiki on that already. This is specifically about when you experience an unexplained dramatic increase in how fast your battery is draining, and the usual tweaks aren't having any effect.
And, in some cases, if you are experiencing battery drain associated with one of the "more interesting" issues below, you might be experiencing lag for the same reason. Please attempt all of the below to the best of your ability before making a post about battery drain or lag with a particular ROM or kernel.
We'll start with the simple.
Don't rule out your imagination or neurotic behavior as the main problem.
I hate to open with a "shut-up-noob," but this one is real. I know I've almost fallen victim to the disease of "let me turn on the screen just one more time to check the battery %." Or hours of "man this new lagfix is great watch how fast I can swipe screens and load apps over and over!" Both of which, obviously, result in more battery usage. Then there's also the case where you just installed a numerical battery meter for the first time, and watching it tick down is weighing on your psyche much harder than the previous, barely noticeable movement of the bar and making you think your battery is draining wildly. Which then can also then lead back to disease #1 in a vicious cycle of psychosomatic battery abuse.
It may just be the battery itself. Some are reporting an apparent quality control problem with the batteries. You might get a great one, or if nothing below helps you then maybe you got a dud. I can't help much there. Try reporting the problem to AT&T or Samsung. I hear AT&T is a lot better to deal with.
Check the basic battery usage stats. Settings -> About Phone -> Battery Use. This won't necessarily tell you a whole lot, it isn't always accurate, but it can give you an idea of what the system thinks is using most of the battery. Such as whether it's playing with the screen too much, or making a lot of phone calls, etc. Keep in mind... I'm pretty sure that these stats are only based on the time period listed at the top of the screen. A lot of people get confused when it shows the display using 90% of the battery. But if that's only based on the 30 seconds since you unhooked the charger, then it isn't all that confusing anymore.
Be wary of the "battery full" status. I have repeatedly found, at least in leaked 2.2 ROMs, that this alert actually goes off long before the battery is finished charging. This bug often continues even after you've done all of the other various tricks and tweaks and recalibrations. It says "100" and that the battery is full and to disconnect the charger, but when you disconnect, it instantly drops into the low 90s and drains quickly from there. Rather, if you ignore the alert and keep charging for considerably longer, it will actually be at 100 when you disconnect, and will drain slowly.
Click to expand...
Click to collapse
I'm quoting out the above, since I can't find the strikethrough tag. With new accurate battery mods, this isn't true anymore. Your battery doesn't need to go to 100%. It will be high-90s when you unplug, this is normal.
Drain and charge.
Sometimes the battery meter will seem to plummet, but then sit at <10 for hours before it finally shuts off. Giving a full drain may help calibrate where the "zero" really is. Run a long video, or just leave the camera up, until it shuts itself off. Then charge it back to 100%.
The bump charge (now commonly referred to as recalibrating).
Maybe your phone forgot where zero really is, or maybe he forgot where 100 really is. Here's the bump charge. Read carefully; I did it wrong for a while before I got it right. Charge the phone to 100% while it's on. As soon as it hits 100%, unplug the charger and power off. Now plug in the charger while the phone is off, and charge to 100 again. As soon as it hits 100, unplug the charger and power on. Wait until it boots completely, then don't charge this time, just power right back off. Now charge to 100 one more time with the power off. Power on and you are bump charged. Many also consider a stats wipe to be essential to this process as well. See below.
See joeybear's post (linked below) for more info on bum charges and battery stats, such as different procedures for CyanogenMod.
Erasing the battery stats (for you rooters/flashers)
Sometimes you just want your phone to forget everything he thinks he knows about his battery, and re-learn it from scratch. Your phone maintains a file with statistics on battery usage, which in turn is used to help calculate battery life at any given time. Sometimes, especially if you've been playing with ROMs, kernels, and lagfixes, the stats in the file just aren't applicable anymore to how the hardware is being used, so you get crazy battery drain.
Clockwork Recovery has a simple function to wipe the battery stats. If you can't run Clockwork, use ADB or a terminal emulator (search the market) to delete that battery stats file located at /data/system/batterystats.bin. The link at the bottom to joeybear's thread has a little more info.
The general idea is to start by trying the above - make sure it isn't your own fault or maybe just a bad battery, then drain, bump charge, and wipe stats - in that order.
There are lots of ideas about what may or may not happen when you experiment with the above. Wiping battery stats after a ROM flash that already wiped them for you is at least redundant and may even contribute to a battery drain problem. Some say you should wipe first and then drain and bump charge. Be careful about wiping stats and bump charging too much, though. Over-charging your battery will hasten its demise.
HOWEVER, if you're like I was when I first started this thread, you've seen the above recommended many times, and none of it has ever helped you one bit with an actual sudden battery drain problem.
Now for more interesting work.
Occam's razor. The simplest answer is the most likely. Battery appear to be suddenly draining faster? Well, it could be that you need to retrain your phone (or your mind) by using the procedures above. It could be that your battery suddenly went bad. A more simple answer is that something is draining your battery. Something is abusing your CPU, your memory, or your network interfaces. Try to find out what, or at least stop it even if you don't find out what. Simply looking at the stock report of battery usage isn't likely to tell you everything you need to know, though.
If you've recently flashed something, try your flash again, and this time be more aggressive. Make sure you turn off any lagfixes you've installed beforehand. Make sure you've got the most charge you possible can before flashing (see above - you want a true 100% charge immediately before flashing). Take the plunge and opt for repartitioning, data wiping, formatting, master clearing, or any other options you may have to start with a clean slate with the new ROM. Even flash stock first. Pay close attention to battery usage as you re-install apps and get your phone set up again. It may be one app in particular that was responsible.
Uninstall all task killers. Yes, uninstall. I know task killers are supposedly battery savers, but 99% of you (including me) don't know what we're doing when we get our hands on a good task killer. It is very possible you've got one service that is constantly trying to load and call home, and another that is constantly auto-killing it. If you really want to include task killing as part of your phone maintenance and battery tweaking processes, then download an app that is specifically designed and configured just for battery efficiency, not a general-purpose task killer that will allow you to hose up your Android system.
Check your background syncs. Experiment with turning them off, one at a time, and see if there's improvement. The app may have gotten confused after all your flashing and is doing something crazy as it syncs. If you isolate one that makes a difference, reinstall it or try living without it.
Live wallpapers. They actually improve your battery life, no lie. Ok, actually that is a lie. Some of them look awesome, but many users, myself included, experience a significant increase in battery drain when there's a fancy full-screen animation running non-stop on the phone. Try getting rid of them and see. There are some nice, simple, dark wallpapers that don't animate but are still pretty enough to impress the ladies at the bridge club. Live wallpapers can also create some majorly noticeable lag in your other apps, too.
Install OSMonitor. Set it to sort process by load, descending order. There shouldn't be much in the list, the OSmonitor app itself should show up near the top, at around 20%. Other apps should be in a 0% wait state or occasionally grabbing a few %. If you recognize an app sitting consistently at 50%+, that could be your problem. Make sure you know what it is first (not a critical system service) and try uninstalling it.
Is kswapd0 taking a lot of CPU? This is the memory swap / page file process. It's normal for it to be grabbing little chunks of CPU here and there, but if it's sitting at a high %, or jumping in frequently to a high %, then something's going on with your memory cache. Unistall your lagfix and try a different one. If you aren't using a lagfix, get OCLF and use it to install EXT2 and then OCLF V2+. Despite the changelogs and debates that claim otherwise, several have found OCLF to be very useful after flashing to any Froyo ROM (unless that ROM already includes a lagfix such as voodoo or stumpy's). If none of that works, your kernel may be the problem. Swap it or go back to stock.
Look at data/network usage. If you have a router or other device on your home wireless network that can give you some info, try that. Does your phone appear to be trying to send or receive an unusually high number of packets/data even when you're not doing anything with it? Also, while off wifi, watch the little green and red data icon in you notification bar (the 3G / E icon). Are they spasming green and red constantly every 2 or 3 seconds, even when you don't think you're doing much data transfer?
OSMonitor can also again be your friend here. Under "Network" you can expand each interface and look at live data transfer #s. Does one of them seem to be really active despite you not doing anything in particular with your phone right now?
If you have any of these signs of heavy data usage, go back to OSMonitor and look at Connections. Turn on DNS reverse lookups in settings. Turn on some whois. Ignore any loopback (127.0.0.1) and likely you can ignore the 1e100.com stuff, that's just Google (get it? 1x10^100). Are there any other established connections? Does the reverse lookup (the domain name) indicate what application might have the connection open? For example, if it's weather.com, that might be a Weather Channel widget or app. That one was responsible for destroying my battery one time. Use whois and similar tools in OSMonitor and on the Internet to help you figure out what your phone is connecting to. If you've got heavy data usage and an app or apps have open connections, uninstall / reinstall those apps and see if the battery drain stops.
Under-volting. Xan's Voltage Control App. There's a lot more of this going around now that there are several overclocking and undervolting kernels available. There isn't a whole lot to be said here. Different CPU clock steps can be individually adjusted to pull a little less juice from the battery. Make sure you keep them as temporary settings and do not "set on boot" until you're sure you've got a stable configuration. If you set something to a level your phone can't handle and script-save it for booting, you might not be able to boot again. Anyway, under-volting will not suddenly revolutionize your battery performance, but it can help.
Also, switching UV settings can significantly affect your battery meter after reboot. If you've recently switched UV settings and rebooted, your battery meter might suddenly show 20% more or less batterly life than before. This is simply what the meter thinks to be the case, obviously your battery did not just jump 20%.
Backlight notifications. I don't have hard data to back it up yet, but I've noticed that when a backlight notification is active, my battery starts racing to zero.
Cyanogenmod. It's available on Captivate now. It isn't stable/supported. It has a lot of debug code enabled. That means it uses more battery than it will someday when it's stable RC and debug code is commented out.
I've successfully used all of the "interesting steps" above in different cases where I had sudden battery drain and the basic steps didn't fix it. Anyone else have success with these? Any other tactics to share? Please post.
Thanks to joeybear23 for good info on recalibrating the battery.
Great info on the battery.
And you mentioned Occams Razor... the simplest answer is the most likely!
Ok, maybe your batteries are actually no good. Many have found theirs to be faulty and that after replacing them all is well again.
I just got a spare and the new one is great!
Maybe a batch of samsung batteries has problems and they begin to lose charge quite quickly after they have been in use a month or 2 (Or they get confused after multiple Flash's of ROMS .
Basically, I bought a cheap aftermarket battery as a spare and decided to try it in my phone today. I have made several calls and installed some apps and have played around with the phone as per normal. After 7 hours it is at 53%. MUCH better than before. With old battery it would be at 10-15% after a day at work.
Only thing different is I did install the lag fix over the Beta 5.5 to see if it helps speed.
Is it the battery or the phones software causing the problem??? Well if they have a chip in them maybe it IS the battery...???
Great read there! I haven't really been having any problems with battery life lately, but installed OS Monitor anyway just to see what was running. Nothing too out of the ordinary, as everything seems as you say it should be. OS Monitor is up there at 15-20%, android system is at another 8-10%, and system/bin/sensorserver_yamaha is running at anywhere from 7-16%. I assume this is the sensor that monitors what position my phone is in. Other than that, I don't see any other process taking more than a small slice of CPU or so from time to time.
I have done all of the suggestions before; bump charging, draining, and wiping stats, but I also feel that there may be differences since I am using a few different batteries. If I seem to get amazing battery life from a battery after wiping the stats and then using it til it dies, when I put in the next battery, it may work differently, thus screwing with the stats yet again. I have tried to not be as worried about battery life, especially since I have multiple batteries, but it's still something of interest to me.
I'll be subscribing to this thread, and look forward to reading some other users' thoughts/experiences with their batteries.
Scott -
In my own experience, putting lagfix on cog 5.5 has a huge beneficial effect on battery drain. I'm not sure yet but I believe the Unhelpful kernel uses a lot of cpu trying to manage swap unless you put an ext cache on it.
However, it's also true that you can great great life out of a new battery for the first 2 or 3 charge cycles. But a battery suddenly draining faster than normal is probably something your phone system is doing and not a bad battery.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cog 2.2 beta 5.5 with OCLF
Also, Demented, don't forget to look at antennae/network abuse, not just CPU. I once had a malfunctioning weather widget that wasn't using much CPU but was going berserk on my 3G and sucking batt juice so fast that you could hear the battery whimpering a little bit.
Sent from my SAMSUNG-SGH-I897 using XDA App
Cognition 2.2 Beta 5.5 with OCLF
There should be a college class on correct battery usage.
Thank you so much for this thread, my battery thanks you as well!
Sorry if i shouldnt be posting this here. But i just read that wiki link at top and i was wondering what you guys think about leaving use wireless networks and power saving mode checked on to save battery???
Sent from my SAMSUNG-SGH-I897 using XDA App
Good thread; subscribed. I'll be trying some of this stuff out and reporting back here.
roadrash7 said:
Sorry if i shouldnt be posting this here. But i just read that wiki link at top and i was wondering what you guys think about leaving use wireless networks and power saving mode checked on to save battery???
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Some of the stuff there is valid; not sure I agree with using the task killer or the advice about leaving "Use Wireless Networks" on and GPS off. I leave both off, and when I want GPS access I turn on the GPS from the power control widget.There's no need for your Wi-Fi adapter to always be searching for networks and associating with Skyhook, etc.
Regarding leaving Wi-Fi on rather than 3G, it does make sense when you are using data. However, if the phone is idle, I doubt leaving the Wi-Fi card enabled will actually save battery life, as it will have to maintain connection with the access point (see your Wi-Fi sleep settings). I think a few short bursts of 3G download/upload when syncing, etc. will be less drain on the battery than leaving Wi-Fi enabled just for those small amounts of data that will be used when syncing. But, if you always want to be ready to browse, or do a lot of DL/UL at a moment's notice, I could see how keeping it on would be justified.
If manually syncing is acceptable to you, then by all means turn off the background data and auto syncing... personally I feel like the phone is really being limited and you have to balance utility and battery life, so I leave those options enabled.
Just some thoughts, if anyone can correct me on anything, I'm eager to learn.
TheYar said:
I'm not sure yet but I believe the Unhelpful kernel uses a lot of cpu trying to manage swap unless you put an ext cache on it.
Click to expand...
Click to collapse
I'm not really sure what you mean by that? There is no swap in use unless you add your own script to mount a swapfile.
Sent from my SAMSUNG-SGH-I897 using XDA App
Update
Updated the OP with some other items I forgot.
Unhelpful said:
I'm not really sure what you mean by that? There is no swap in use unless you add your own script to mount a swapfile.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sorry I wasn't being very accurately descriptive there of what I've seen. I rarely know for certain what caused or fixed a battery drain issue. Thanks for calling me out on this one, because going back over my history on this it looks like I was largely mistaken in thinking your kernel had much to do with it. One of my worst experiences with battery drain, it seemed that I had some apps/widgets that just didn't work well after the kernel swap, but Cog also made some non-specific references at that time to battery issues with the kernel and that stuck in my head. Another time with a Cog ROM I believe I may have misread the changelog and I was under the impression that I was on a new Unhelpful kernel, when I wasn't. Looks like that time it was actually a stock kernel partly responsible for the drain, which makes sense. Was I totally confused thinking Cog 2.2B5.5 uses an Unhelpful kernel?
As for what I was seeing (thinking now it was actually not on your kernel), kswapd0 was going berserk on my CPU. All I know is that is generally the name of kswapd0 is referring to virtual memory management, and putting OCLF on fixed it.
Well, vm also allows clean pages that are backed by files to be "swapped" out by freeing them, without using a swapfile, because the data already exists in storage.
A release or two ago I had some battery drain issues that were resolved by reverting some config changes.
Cognition 2.2 can't use any of my kernels, the froyo leak uses a different kernel version, and we don't have Samsung's modified sources yet.
Sent from my SAMSUNG-SGH-I897 using XDA App
Unhelpful said:
Cognition 2.2 can't use any of my kernels, the froyo leak uses a different kernel version, and we don't have Samsung's modified sources yet.
Click to expand...
Click to collapse
Right, which makes sense when I look back over my flashing history. DG had two versions in one changelog, and a line about re-adding your kernel to Cog 2.1.7 slipped in between some changelogs about Cog 2.2 beta releases. So I originally misread and figured that you'd somehow made a 2.2 kernel. It started draining my battery like crazy, which is exactly what happened the previous time I used an Unhelpful kernel (though again probably unrelated or only somewhat related to the kernel), and so I figured I was on to something. I was wrong. My b.
The issue that still remains is that I believe many people who flash to Cog 2.2.B5.5 (and perhaps 6), without master clearing and stocking first, end up with some odd behavior with whatever kswapd0 does (e.g., odd behavior like constantly using up to 90% of CPU for no dang reason). This is probably a cause, or the cause, of the Lagfixgate scandal and maybe Sudden Rapid Battery Drain Syndrome. And for whatever reason, OCLF fixes it.
I master-cleared and flashed 2.1 stock and then Cog 2.2B6, and kswapd0 and lag are no longer an issue even without OCLF. Battery is too soon to tell, though. Seems to be fairly normal, but not as good as some of what I used to see on Eclair with various other kernels swapped in.
Great resource here. Please keep updating! Subscribed...
Although you can't see it so well in the vid, the lagfix demo I captured also demonstrated a couple of points of battery life improvement.
http://forum.xda-developers.com/showpost.php?p=8631303&postcount=15
Bumped for updates in the OP.
With any of the 2.2 builds my cpu runs at constant 10%. We know its beta but worth looking into. Only info i have seen on my phone was android system. So im unsure what it is. Havent tore into it yet. But that was all stock with no apps installed. Even cog 6 i have the same cpu readings. So who knows.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guess its not really 10% but up there
Just a tip. I was using latitude and wasnt getting the normal battery life i usually was when i wasnt using it.
I didnt know it was effecting it though cause you dont see it in task manager but you will in applications/running services. Anyways i signed out of latitude and battery life is back to normal.
It wont be remarkably better but it was noticeable to me. Just a tip.
Sent from my SAMSUNG-SGH-I897 using XDA App
smokestack76 said:
With any of the 2.2 builds my cpu runs at constant 10%. We know its beta but worth looking into. Only info i have seen on my phone was android system. So im unsure what it is. Havent tore into it yet. But that was all stock with no apps installed. Even cog 6 i have the same cpu readings. So who knows.
Guess its not really 10% but up there
Click to expand...
Click to collapse
How does that compare to when you're on earlier (eclair) builds? I expect there'd always be a little utilization going on.
Simple Poll.
Have you seen a decrease or increase?
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
nagash91 said:
Someone can explain this battery drain?
in a lot of roms based on 2.2.1 there is a big battery drain, in some other there isn't.
Click to expand...
Click to collapse
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
OK I have done.. but the problem is that when I use it 3 o 4 minutes (for example I install an application using a file explorer, then I read a message and then I come back to home) m battery get 5% lower...
In standby I lose 10% in 6 - 7 hours (I think this is normal).
AndDiSa said:
Reboot after unplugging from USB and battery drain is gone. For further improvement install SetCPU and reduce min/max frequency. I am getting more or less the same lifetime as with donut ROMs.
Click to expand...
Click to collapse
I am currently without a computer therefore immune to this USB bug. I flashed CM6.1 to this and the other g1 and both suffered substaintial amounts of battery drain so I nandroid restored back to CSDIv4 and still the lowest frequencies and settings did little to combat the descending digits. So I tried this...
Recalibrated my battery
Flashed SuperWipe.zip
Reboot
Flashed SparksMod's latest
Reboot
Wiped battery stats
Unplugged...reboot
Battery lasted 23 hours the first day never seen anything like it.
Lifes great.
Sent from my HTC Grandaddy via XDA app
Sent from my HTC Grandaddy via XDA app
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
nagash91 said:
I'm using TMUS-G1-Froyo CM6 remix..
and I'm using the new radio with +14mb.
The rom flies but the battery go down too fast.
I'm using setCPU with 256 - 528 mhz while screen is on, 122 - 256 mhz while screen off.
If I go to battery use in settings I see
Cell standby 45%
display 28%
phone idle 22%
android system 3%
I don't think is normal... cell standby is the battery use by cell radio..
I wonder if the new radio give a big battery drain..
Click to expand...
Click to collapse
I got real excited when I heard about the new radio and hboot even thought that its exclusion was the source of the the battery issues. Haven't been able to try it as I'm without a up-to-date PC at the moment.
It would be real nice if I could find a seasoned dev who understands battery consumption. I thought the kernal was the main culprit but I've tried two different roms with the same kernal and one has notably better battery life than the other. So confusing.
Sent from my HTC Grandaddy via XDA app
I can't use my phone with this battery drain...
I will come back to official android OTA-AOSP 1.6.. with +14mb.
So I'll test if this kernel with 14mb is a cause of battery drain.
PS: I'm not a lover of rom customizations.. I think the official roms are the best.
The other are all too heavy. I'm not a fan of cm kernel, that is too heavy for g1.
I would see an official OTA 2.2 without customizations, so every one could customize as he want, and if he want.
PS: OK I flashed AOSP 1.6 using ezBiff_kernel to have 15mb (cause I have new radio and spl, so I can flash roms only using this kernel).
Result: my battery life is similar to froyo 2.2 roms... so the problem is:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
2) New radio/spl?
3) My battery (I don't think so.. it's new battery. I buy it 2 weeks ago and in the beginning it works so well.. but then I flashed new radio/spl and new kernel for 15mb..)
nagash91 said:
1) Kernel? (ezBiff_kernel is based on cyanomod kernel... ... ... heavy as death)
Click to expand...
Click to collapse
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Cm/pershoot have some interesting new power management code from other htc devices.. So hopefully soon all will be better. (I merged most of it to my kernel but there are some loose ends.. works well untill the phone locks up.. so no public release yet)
ezterry said:
Come now.. the cm pershoot kernels are super optimized so they don't collapse under the heavy as death rom that is usually on top of it..
I get mixed results with that kernel between testing and feedback.
A test phone can idle on wifi+2g for days on the stock g1 battery even after a usb unplug.. but on more common use with syncing services its not performing as well as I'd like..
Some of it is fixed with less swap/compcache or changing clock speeds 122/480 for most the speed but lower voltage levels. Also the interactive governor may work better.. I'm testing these ideas if results are good my next kernels defaults will use them.
Click to expand...
Click to collapse
Ok sorry I talk without knowledge. I really don't know the effect of the cm kernel. I only know that all roms based on cm release, with cm kernel, are so heavy and slow.
I like your rom (2.2.1 AOSP) and I love your new way to get 14mb.
But I have this orrible problem. My phone has a lot of battery drain when I use it. With screen off, no problems.
I have never used swap or compcache in this days, and I also try different clock speeds (not over 528mhz).
The result is that when I unlock my phone, I go to settings, I see for example 95% battery. Ok, I return to home, I open a message, I return to home, I open contacts and I scroll some contacts without make calls.
Then I come back to battery settings and I see that is 92-93%..
in 2 minutes of soft use.. I think this is impossible. If I open stupids 2D games... ahah in 5-10 minutes my battery lose 10 - 20%.
I remember 1 year ago, with 1.6 (no cyanomod) my battery was good.
Now it isn't (I have a new battery).
Today I flashed aosp 1.6 with your kernel for 14mb (I have new radio&spl) but nothing... I lose a lot of battery percent as in froyo.
So I think problem is or battery calibration, or something to wipe, or cm kernel, or new radio&spl + your new kernel...
Now I'm recalibrating battery (is at 1% from 2 hours, I'm not using it.. ) then I will recharge for 8 - 9 hours and then wipe battery state, but I have done this process a lot of time without a benefit.
I'll try to remove the new radio+spl (so also using standard kernel) if my battery continue to lose percents so fast.
I'll keep you update on my "story".
PS: Sorry for my bad english!! XD
OK.. after a day of low discharging and a night of 8 hour of recharging, I wiped battery states, I wiped data-cache-ext ecc... I flashed aosp 1.6 and ezbiff kernel..
"battery drain" continue...
I will try tomorrow to reflash death-spl and old radio..
BTW, is normal for hours battery 4v at 90%?
On the back of the battery sais 3.7v... I thought 3.7 was the voltage for 100%
Update
I know this thread is a little old, but I ran into this problem as well. What I found was that the official US radio (2.22.23.02) used considerably more battery than the international one (2.22.19.26i). The other thing I noticed is that switching to "use 2G networks only" in mobile networks settings and disabling data over mobile drastically improved battery life.
I also noticed that wifi used a fair bit of juice so my recommendation is to disable wifi if you're going to be on the go for a bit, and disable data/3g if you're just going to be hanging out in the local webcafe, your/a friend's house, or some other location with wifi access for a while.
If you wanted to be ambitious and cared enough you could write a script to use as a shortcut on the home screen to do the swap automatically (detect which setting(s) are enabled and swap them to the opposite).
With those changes, you should get much better battery life. My thoughts on different Froyo flavors is that possibly different builds have different settings by default. Cyanogen comes with data and 3g enabled by default so this will quickly suck out your battery if you're running your 3g, 2g and wifi antennas all at once.
The stock build (1.6) got about the same battery life as I'm getting now with those settings applied. With either build, having all antennas on all the time will drain your battery very rapidly. Being a little more cognizant of the settings (perhaps you also had it set to 2g only on the stock build) you're using will significantly improve your battery life. And when I say significantly, I mean night and day (but the antenna version definitely does also make a difference... at least in my case).
I have not yet updated my Captivate to 2.2. Reading posts in regard to the update I am very bothered by a common complaint that battery life has just died. My Captivate has excellent battery life using it fairly heavily over a 1 day period. I charge it every nite. Also, my GPS is workng fine in 2.1. So am considering not updating it due to the problems I am hearing about.
Anyone else have input on battery life after the update??
I went from STOCK 2.1 to Cognition 4.1 (built on Froyo 2.2) and my battery life is about the same. My usage varies wildly from day to day, but as best as I can tell, overall battery consumption is about equal.
I wonder if the people complaining about battery life have set up their phone "post-update" with different apps or turned on "apps syncing background data"...
Battery life did reduce on 2.2 but it is obvious in my point of view. But its not too bad either.
it's about the same, i upgraded to stock 2.2, feel no difference on the battery life. moderate usage last mine for about more than 24 hrs, u should update to froyo for you to experience it.
Sent from my SAMSUNG-SGH-I897 using XDA App
SnackCracker said:
I went from STOCK 2.1 to Cognition 4.1 (built on Froyo 2.2) and my battery life is about the same. My usage varies wildly from day to day, but as best as I can tell, overall battery consumption is about equal.
I wonder if the people complaining about battery life have set up their phone "post-update" with different apps or turned on "apps syncing background data"...
Click to expand...
Click to collapse
I upgraded Stock 2.2 end of Feb and noticed a big drop in my battery life the first week. But just reading above, i did turn on "apps syncing background data" so i think that's my problem. Just turned that off so we shall see...
Let your phone go through a week or so recharging cycle before judging its battery life after a ROM flashing. You just lost all your battery stats when flash a new ROM. Your phone/OS has no clue how your battery will operate until it has time to learn or you manually calibrate it.
For what it is worth, my battery life is about the same or slightly better than leaked 2.2 ROM as well as 2.1 ROM. No big changes.
My battery has been about the same since the 2.2 upgrade. At first it felt like my battery was draining quicker but I also noticed I was playing with more phone more. The screen is the biggest power drain on the phone so just playing with menus and looking at new settings can cause a small dent.
Give it a week or two after upgrading and you'll notice it'll be about the same. Unless of course you have more accounts or programs syncing data in the background.
Why upgrade to 2.2
Thanks everyone for the input. The more I read and hear the more I am leaning toward not upgrading to 2.2. On different forums I am seeing and hearing problems with battery life and some saying about the same battery life. Also, seeing GPS not being fixed or going from working ok or good to not working so good. Right now my phone does everything I want, GPS works really good, email works fine, internet works fine, battery life is outstanding, mp3 works great, screens all are clean and to my liking, I have an easy work around for turning off 3G and one tap returning my volumes to normal after using a USSD code.
REally cannot see any advantage to upgrading and risking introducing a problem I don't need. The list of new features really does not thrill me.
gstreff said:
Thanks everyone for the input. The more I read and hear the more I am leaning toward not upgrading to 2.2. On different forums I am seeing and hearing problems with battery life and some saying about the same battery life. Also, seeing GPS not being fixed or going from working ok or good to not working so good. Right now my phone does everything I want, GPS works really good, email works fine, internet works fine, battery life is outstanding, mp3 works great, screens all are clean and to my liking, I have an easy work around for turning off 3G and one tap returning my volumes to normal after using a USSD code.
REally cannot see any advantage to upgrading and risking introducing a problem I don't need. The list of new features really does not thrill me.
Click to expand...
Click to collapse
2.2 ROM is a big step forward, not backward, IMO. Sure it didn't solve GPS issue but it is not making it worse either. GPS issue is purely hardware issue. If you have a good one, it doesn't matter which stock firmware you use.
I just can't see any disadvantage for upgrading (other than slightly more difficult to root or unlock, but not impossible). Battery life thing is as I mentioned above. You will see all kinds of complaints (either dain too fast or too slow) after a new firmware comes out, any firmware. You don't know what you're missing until you upgraded.
I noticed a big improvement in battery life. Sometimes with light use it will last up to four days, whereas before with 2.1 it would putter out after maybe two days.
GPS isn't fixed, but drop one of many GPS fixes in and it will get somewhat normal performance.
Wifi sleep policy
You may also want to check the Wifi sleep policy after the upgrade to Froyo. In my case, the default was "Never sleep". Changing this to "When screen turns off" improves battery life on 2.2, as it does on 2.1.
Just my $.02 worth.
foxbat121 said:
Let your phone go through a week or so recharging cycle before judging its battery life after a ROM flashing. You just lost all your battery stats when flash a new ROM. Your phone/OS has no clue how your battery will operate until it has time to learn or you manually calibrate it.
For what it is worth, my battery life is about the same or slightly better than leaked 2.2 ROM as well as 2.1 ROM. No big changes.
Click to expand...
Click to collapse
I'm on stock 2.2 since the day it came out. My battery life is actually trending worse day-by-day. I did a full battery clear/reset this weekend and after 4 days I'm finding battery life is not improving at all. The degradation from stock 2.1 is significantly noticeable to me.
For the first couple of days post-update it seemed actually to be better, but got worse and worse, to where I was lucky to find the phone working 12 hours after disconnecting from the charger @ 100% ... even if I hadn't -touched- the phone during the day. My applications loaded are virtually identical to before.
I did have Background Data on, so I've just disabled it, but was this option not in 2.1? I know that Google Voice, etc, were doing background syncs in 2.1.
It can't be WiFi, as for the last 2-3 days I've kept WiFi turned off. However just for sanity I did adjust the sleep policy.
I'm wondering ... my battery woes seemed to start when I hooked up my Microcell. Could having a strong 3G signal so close to the phone actually be causing problems?
jahfry said:
I did have Background Data on, so I've just disabled it, but was this option not in 2.1?
Click to expand...
Click to collapse
it is the same as in 2.1.
I'm wondering ... my battery woes seemed to start when I hooked up my Microcell. Could having a strong 3G signal so close to the phone actually be causing problems?
Click to expand...
Click to collapse
That might be your problem. I don't know. I know 2.1 doesn't work very well with microcell either.
Yep. I'm pretty convinced it is the microcell now. Phone works great with it from a call/data/signal standpoint. However after unplugging my microcell last night, charging my phone to 100%, and then letting the phone discharge normally with no microcell ... I'm now 10 hours later and have an almost full battery.
Sad, because our reception here is so spotty that we lose calls and data regularly without the microcell. My wife says her phone charge has been pretty normal, so I'm getting ready to move the cell away from my desk and see if distance helps the story.
So, as far as this thread is concerned, my results for 2.2 and battery life are great ... better than with 2.1 ... just don't use it with a microcell.
Froyao 2.2 Battery Usage Dillema
I see no significant or excess battery drain while riding the KB1 over the JF6.
Just a thought for those experiencing excessive or significant battery drain. KB1 loads some new features and new additional bloatware that loads on boot and runs as a service, process and both.
If you're familiar with poking around your system settings and understand what doesn't need to always be running in the background, or what doesn't need to load on boot, you can simply kill the process and even alter the way a certain application handles on boot.
By killing many unneeded or unwanted processes at boot time, it will significantly save you hours upon hours of battery life in the longer scheme.
Another FYI, Lithium Ion batteries have memory. You need to train or retrain the batteries memory over time in order to sustain a longer life for it.
Tips:
Don't continually through the charger on your device after minimal drainage. Let the battery run down before fully recharging it again.
When flashing to another ROM wipe your battery stats.
When flashing any new code to your device - a few forced charge deaths to purge the battery and reset the memory again prior to recharging may be a good idea...
Hope this helps...
Peace-
Liv33viL
Anyone have any views on which of all roms and official releases have best battery?
i think best gingerbread rom is iceandfire
As far as battery life is concerned, my oppinion, nothing beats a clean stock Eclair (official), followed closely by a clean stock Froyo (official). All mods are great, but battery life is better in the official ROMs in my own experience.
HinotoriBR said:
As far as battery life is concerned, my oppinion, nothing beats a clean stock Eclair (official), followed closely by a clean stock Froyo (official). All mods are great, but battery life is better in the official ROMs in my own experience.
Click to expand...
Click to collapse
Are you serious?
iceandfire v2.1 is the best ROM I've found so far in terms of battery life. Don't know why, but it just lasts SO long!
I use ice and fire loads its good but I wish it could be a lot better, testing froyomod now, am considering buying a new phone mainly for battery life as the milestones is sooo bad!
Sent from my Milestone using XDA Premium App
mcdevtingz said:
Anyone have any views on which of all roms and official releases have best battery?
i think best gingerbread rom is iceandfire
Click to expand...
Click to collapse
As mentioned, nothing beats Eclair. And if we talk about Eclair, nothing beats Telus Lite.
I have CM7 installed.
Your battery mileage may vary depending on your usage habits... But I'm typically a pretty heavy user. Lots of Angry Birds/other games, surfing, Pandora, etc. I go to sleep at around 11pm with my phone unplugged at a full charge (100%), and I can use my phone until the next day mid to late afternoon - that's about 15-18 hours. Granted, a lot of it is when I'm asleep (until about 7am) and during my working hours, but it's still pretty decent considering how I use the phone. ESPECIALLY with all I've heard about CM7 having terrible battery life.
I DO have several apps and tweaks to try to lengthen my battery life though...
Some things you can do:
- install "Network Switcher" from the market. You can set conditions between certain hours and the screen off to turn off WiFi and 3G. I have mine set turn off all data between 11:15pm and 7:15am when the screen is off.
- install the "Toggle 2G" app. This automatically switches the phone to 2G mode when the screen is off. 2G typically sucks less juice than 3G. (get it here: http://forum.xda-developers.com/showthread.php?t=739530)
- tweak your /system/build.prop file so your wifi scan interval is a higher number. I have mine set to 360 seconds (that's 6 minutes). I don't know about you, but I don't need my wifi scanning every 15 seconds for an open or known signal.
- also in the build.prop file; change your ro.telephony.default_network setting from 3 to 0. 3 means GSM/WCDMA mode; 0 means WCDMA preferred. From everything I've read, WCMDA preferred tends to switch signal types less often, which benefits your battery.
Heck, even if you DON'T have a Milestone w/CM7 installed, these tweaks can help immensely with your battery life.
Froyo should beat out Gingerbread... They're roughly equal for me, but the memory issues of GB make me have to keep my phone on longer to wait for tasks to complete, thus draining more battery overall.
pippocannelunghe said:
Are you serious?
Click to expand...
Click to collapse
Yep, I've tried pretty much any Froyo and/or Ginger Bread mods (and I've specially liked CM7 / ShadowMOD, but all other ROMs are great as well), no one is close to the stock Froyo as far as battery life is concerned. But, I have to say, it is not absolutely stock, but, with exactly the same VSEL/CLOCK settings I've tried in other roms (which save some battery since it uses lower vsel).
HinotoriBR said:
Yep, I've tried pretty much any Froyo and/or Ginger Bread mods (and I've specially liked CM7 / ShadowMOD, but all other ROMs are great as well), no one is close to the stock Froyo as far as battery life is concerned. But, I have to say, it is not absolutely stock, but, with exactly the same VSEL/CLOCK settings I've tried in other roms (which save some battery since it uses lower vsel).
Click to expand...
Click to collapse
Have u tried the ROM that is banned from XDA yet?
dmo580 said:
Froyo should beat out Gingerbread... They're roughly equal for me, but the memory issues of GB make me have to keep my phone on longer to wait for tasks to complete, thus draining more battery overall.
Click to expand...
Click to collapse
Have u tried AutoKiller Memory Optimizer with my recommended settings (see video below)?
http://youtu.be/z1vBcNsDkn0
mcdevtingz said:
I use ice and fire loads its good but I wish it could be a lot better, testing froyomod now, am considering buying a new phone mainly for battery life as the milestones is sooo bad!
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
Get either an extra battery or extended battery if u are a heavy user.
pcphobic said:
Have u tried AutoKiller Memory Optimizer with my recommended settings (see video below)?
http://youtu.be/z1vBcNsDkn0
Click to expand...
Click to collapse
That doesn't come remotely close to the V6 SuperCharger script.
The minfree levels is only one aspect of it.
AKMO doesn't fix groupings or priorities.
With those settings, all your apps are getting killed at 28 mb - because of the screwy groupings they are in the 5th slot while slot 3 are 4 are basically empty holes.
And that whole "banned rom" spiel is getting pretty annoying.
I'd bet money that HONO's SuperCharged CM7 kicks Cronos' ass with those AKMO settings.
zeppelinrox, have I offended u in anyway?
I have even introduced your method to calibrate battery to other people.
Why do u need to reply in such an arrogant and nasty tone towards me?
I agree with zeppelinrox, running his V6 supercharge scripts work wonders.
And no matter what ROM I use, i always use SetCPU to auto-adjust the processor speed based on certain scenarios. For example, I'm using CM7 right now, which auto overclocks to 1000mhz. That's great for performance but crappy on the battery. However, with SetCPU I can force the CPU to run between 250mhz and 400mhz when the screen is turned off. There's simply no need to let it go up to 1000mhz if I'm not even using the thing! Calls still come through fine, as do emails and messages. But it really extends your battery life. You can go as low as 125mhz, but then things do start messing up. As soon as the screen turns on, the phone is automatically allowed to run at 1000mhz again.
It's also useful for when your phone gets really hot, as a precaution. If my phone reaches 42*C it automatically underclocks as well. I picked that number out of a hat though. It's just a number I felt was too hot based on my own experience with the phone.
SetCPU:
https://market.android.com/details?id=com.mhuang.overclocking&feature=search_result
pcphobic said:
zeppelinrox, have I offended u in anyway?
I have even introduced your method to calibrate battery to other people.
Why do u need to reply in such an arrogant and nasty tone towards me?
Click to expand...
Click to collapse
I think you're reading too much into it. I didn't think he was being arrogant/nasty. He was just being straight forward.
Just my 2 cents though
No not offended.
Everybody knows that gingerbread memory management is screwed up and fiddling with minfree levels alone ain't fixing anything.
AKMO alone does nothing to fix memory management it doesn't even tell you what apps are where.
One set of settings on one rom has a totally different effect on another rom.
The groupings in CM6 and froyo mod are nothing like CM7 and Cronos.
So those settings would make froyo roms dog slow but are kind of aggressive in CM7 and Cronos and of course do nothing to make the launcher more responsive in both cases.
The only way to know what kind of effect minfree levels would have is if you know where the apps are.
And the only way to be certain of where they are is to tell android where to put them.
Which is why the SuperCharger script works on all roms the same way... it puts apps in their place so that the OS will run in a predetermined and predictable fashion and therefore the lowmemorykiller settings will have the exact effect that the user expects.
So no, I'm not offended.
But kind of annoyed that I spent quite a number of weeks perfecting it and somebody who knows this is fiddling around with AKMO settings while they really truly can have a phone with fixed memory management.
btw, if you check the memory groupings with AMM, you will see that AKMO is annoyingly in memory way too often. Which is ridiculous.
zeppelinrox said:
No not offended.
Everybody knows that gingerbread memory management is screwed up and fiddling with minfree levels alone ain't fixing anything.
AKMO alone does nothing to fix memory management it doesn't even tell you what apps are where.
One set of settings on one rom has a totally different effect on another rom.
The groupings in CM6 and froyo mod are nothing like CM7 and Cronos.
So those settings would make froyo roms dog slow but are kind of aggressive in CM7 and Cronos and of course do nothing to make the launcher more responsive in both cases.
The only way to know what kind of effect minfree levels would have is if you know where the apps are.
And the only way to be certain of where they are is to tell android where to put them.
Which is why the SuperCharger script works on all roms the same way... it puts apps in their place so that the OS will run in a predetermined and predictable fashion and therefore the lowmemorykiller settings will have the exact effect that the user expects.
So no, I'm not offended.
But kind of annoyed that I spent quite a number of weeks perfecting it and somebody who knows this is fiddling around with AKMO settings while they really truly can have a phone with fixed memory management.
btw, if you check the memory groupings with AMM, you will see that AKMO is annoyingly in memory way too often. Which is ridiculous.
Click to expand...
Click to collapse
Ah yes, now your tone of voice is much better... more professional and more matured as compared to when u said wrote b4.
Thank you for clearing this up.
Hope to see you back in Cronos forum as I recalled how much u were impressed with Cronos Ginger.
Best Battery -> Official 2.1-update1. Simple as that.
pcphobic said:
Hope to see you back in Cronos forum as I recalled how much u were impressed with Cronos Ginger.
Click to expand...
Click to collapse
I check it out time to time.
Cronos is good and feeyo is cool but lack of updates, v1.2 had issues plus I needed to test other roms.
Btw the memory managent on cm7 and cronos mimics my strategy from v5 anyway - which was to give the laubcher its own OOM grouping/slot but everything else is just weirdly placed far down the list so still not as good as v5.
Tthen V6 simply out does v5 hands down.
Sent from my Milestone using Tapatalk
Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
PCdumb said:
Hi,
I don't have sufficient posts to be able to participate directly in that forum, so have no other choice but to raise my queries here.
I've just flashed over from Overcome "Hermes" to "Jupiter". All's well except that the battery performance is quite drastically affected for me.
I've been reading the improved battery life "Jupiter" gets over earlier versions of the Overcome ROMs, but I seem to be experiencing the opposite.
Already did the batt stat wipe via recovery menu. Do I need to so call "run-in" before it reflects correctly? Even if accuracy is one thing... but dropping 3% just on bootup.... is this typical of an uncalibrated battery?
Appreciate any advise here on what I should do. (Apart from a fresh wipe install )
Thanks
Click to expand...
Click to collapse
According to the Tweaks section at the team overcome website, it will take several charge cycles before you notice an improvement after the stat wipe. Try giving it a few days before going any further.
PS Not to question your ability to follow instructions (sometimes we miss things) but did you charge to 100% with the tab off?
Yes, I did charge to 100% with the Tab off.
Now upon reading the instructions once more..... I might have conducted it slightly different from the written procedure.
I unplugged the Tab from the mains, then only booted up and wiped the batt stats before re-booting. Hmmm.... maybe I'll go try booting up while still plugged into the mains, do the batt stat wipe, and re-boot. (all while plugged into the mains). Then only unplug the charger.
Wonder is there any diff in doing so.....
Would definitely try re-doing it with the tab plugged in while doing the stat wipe. And if it doesn't seem to fix it, do go through a few cycles before reverting back to a previous ROM.
It's important to completely drain your battery before recharging it to 100% in order to complete a cycle.
Hope you fix it. Battery life results vary between tab's even if they are used very similarly, I'm running the OVERCOME Jupiter ROM with IMPROVED battery life. I keep my Bluetooth, Wifi and GPS on all the time. I also flash quite often and have not seen a decrease in overall battery life. It seams that each tab is a bit different, hardware wise, than one another. Everything from battery to board it seems is slightly different coming out of the manufacturing process.
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
PCdumb said:
Thanks. Will try that out.
But it just seems strange coming from Overcome ver 1.4 (Froyo) which had no batt drain problem.... to Hermes which was better in batt performance.... to Jupiter which I'm experiencing heavy drain.
As I did a NoWipe install, all apps and setting are similar (except the new market app).
I was able to run 2 movies back to back (about 3 hours total) and still have at least 40% life left (usually about 45 to 50%). Now on Jupiter, just fiddling around testing the various features for functionality, plus maybe an hour of NFS (total about 3 hours as well).... the batt drops to about 10% life.
Anyway, I'll re-do the calibration and and give it some time to "settle in". Hopefully, that is all that is needed. (I would hate to have to do a full wipe install... and re-installing all apps)
Click to expand...
Click to collapse
As mentioned in the Tweaks section, perform the Stat wipe and then two full recharge cycle
recharge to 100% (while the Tab is closed) then drain the battery till it is off then repeat the cycle and you will enjoy it man
Please tell me if you need anything
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
where you were hiding this all ? i bet you were so damn angry to say all of this , i never saw you writing more than 3-4 lines , chill out buddy .
@The OP flashing custom roms means battery need to re-life back
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
Viewed purely from an engineering perspective, I'm unable to see any significant connection between the flashing of the ROM and a degradation of battery capacity. Further, in the event that the TAB was connected to a charger during the flashing, I can see absolutely no connection at all! Please help me understand your logic.
Ok Back on topic. PCdumb (dude what's with the username lol). Check your app list. It could a new app you or an old app you updated or an app you didnt use before but you use now that is being a battery hog. A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Thanks for the advise. That was one of the 1st few things I did to check that there's nothing out of the ordinary running in the background and taking up the juice.
Mine's actually draining alot when in usage. Not too sure about when in standby.... will check later.
If after a few charge cycles and the drain is still bad, guess my only next best option is to do a full wipe, re-stock and re-install.....
I did not get any effect from Battery calibration. As expeced. Anybody did actually?
The background services instead might have an effect on power consumption, I agree. But needs numerous testing...
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
If you want to confirm that JUPITER is the reason that you are experiencing poor battery life, try re-installing a previous version that you feel worked better for you. Maybe reverting back to a previous version may yield better battery results, and I sure hope so, this way you will know if it's the ROM or other elements affecting the abnormal battery drain.
If you do see an increase in battery life, try flashing JUPITER again, see what the results are. I don't know if flashing and re-flashing will have a negative long term effect on your SGT, I know that I flash every time a new release is out (Stock safe, cooked ROM, Kernel) and if i'm not happy with the release i go back to a proven one by flashing another three times (stock safe, cooked ROM, Kernel) and so far I have not had any (knock on wood) abnormal battery activity.
It's worth giving it a shot (if you haven't already).
EDIT: I know, I know the proper sequence is stock safe, kernel, rom.
after week of using the Overcome ROM i can confirm that the battery performance is between 85 and 90% from the Orignial stock ROM performance
No problem since this is normal as we are using a cooked ROM
bongski55 said:
I appreciate the enthusiasm these coding geniuses have in rolling out update after updates in the ROMS yet I am apprehensive about the effect of these frequent flashing on the Galaxy Tab components itself. This includes the battery.
My job involves electronic repair and there is a so called number of hours before an equipment goes for a thorough check(preventive maintenance) say for example 1000 hours on a meter. Unfortunately the galaxy tab (or any tablet) does not have this. So if you frequently do a flashing on your tab you subject the electronic components to unnecessary stress,thereby affecting the life of the components like the battery.
In "normal" everyday use of the tab you will seldom do any restart/reboot of your tab,yet in flashing ROMs as many as 3 reboots is needed. As I don't know how to measure the surge in current during reboot, I can just imagine how high an initial current during startup is generated, thus putting a big strain on the battery.
Unfortunately the battery is not user detachable.
There was an author here in XDA describing himself/herself as an "flashing addict"(or something similar). I would like to appeal to everyone-please don't be a flashing addict.
As for battery issue read here
JUST MY FEW CENTS!
Click to expand...
Click to collapse
WOW ! This was an eye opener for me...
Thanks for clarifying this...... I didn't know this was so bad for the hardware ....
Sent from my GT-I9003 using Tapatalk
PCdumb said:
Batt recal did not give me better battery life. There's no difference in the battery performance after 3 recharge cycles.
My tab can at most get slightly more than 5 hours of continuous usage compared to about close to 7 hours on hermes. This is when i dial down the OC from smartass mode to conservative and also put the min freq to 200 instead of 400 which was the setting i was using all the while.
Doesn't seem to be anything else running in the background. On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes.
Guess I'll have to live with this if i want the speed and smoothness. Still contemplating whether to restock and do a clean flash.
Click to expand...
Click to collapse
After reading all this superb discussion....
I would just recommend you to go back to your older rom.....
Its forbthe best....
Sent from my GT-I9003 using Tapatalk
I do get 4 to 5 hours of continuous use with overcome Jupiter, mostly browsing the web over
WLAN or umts. Hermes release didn't gave me so much more juice, probably 5 hours.
In the background I have emai push, contacts and calendar sync and some instant messaging apps, if I switch off all that I might get an hour or so more.
PCdumb said:
...On standby overnight, i only lose about 3% which is not too bad. But when in use, that's where the Batt drains fast. Just for comparison, i only lost 1% at most for overnight standby of about 7 hours when running hermes...
Click to expand...
Click to collapse
Wow, maybe your tab is one of the ones with a battery from the bad batch, and it's finally on its way out. I upgraded from the stock AT&T Rom to Overcome Jupiter, and on Airplane Mode with all stock settings (no overclock or undervolt), mine only drops 1% in standby over 14 hours and I can get about 5 hours of video watching straight with the brightness on max before it dies!
DarkPal said:
A small trick I learned is checking apps running services in the background. Go to Settings, applications, running services and check (why is skype working after Isigned out its not a battery drainer but I hope you got the picture).
Click to expand...
Click to collapse
I also been experiencing a major increase in battery drain even after doing a couple wipes exactly according to the tweak guide. I went from about 24 hour normal use down to 6-8 hours normal use.
Checked the services as per your suggestion above and found a couple major battery drainers running. Skype and Yahoo but also Google+. What I dont understand is why Skype and Yahoo would be running even though I had not started either since at least several re-boots ago. I had Skype and Yahoo installed for quite a while Google+ is a new one. Anyway I killed all of them and now and will see what happens next.
Not sure thought that this is all there is to the issue. Recahrging is finiky as well. I can turn off the tab and let it charge all night just to find that it charged to about 70% if I re-plug it might charge to 90%-95% and then if re-plug it might get to 100%. The drain from 100% to 60%-70% is extremely fast and still quite fast from there. On one occasion after complete drain I couldnt get it to start charging at all for about 5-10 minutes. I was checking power, cables, connections and starting to panic when all of a sudden it started to charge.
Any advice on possible reasons or solution woud be appreciated. Not sure I want to go beck to stock ROM and un-root just to take it to service center for repairs.