Related
Ive noticed a significant decrease in battery life ever since i updated my phone to FRF83. I can leave it on at 100% and it drains down to 75% or even lower the following morning. It usually drains no more than 10% if i leave it running overnight.
I dont have any apps running in the background, and my task killer is set to auto kill 3 mins after screen blankout. Auto refresh is, and has always been on since the day i got the phone though.
I manually updated to FRF85B and the battery life is still as bad as ever. Ive never gotten this problem with android 2.1 or any of the earlier froyo builds. Someone care to tell me whats wrong? Ive heard others reporting that their battery life has increased after updating to froyo, why am i getting the opposite?
I have this issue because of my exchange server.
Ive never set up and exchange server on my phone. The only constant apps that should be auto syncing are gmail, calander and twitter, which is set to refresh once every 1 hour.
Same for me, battery life sucks lately.
Mokurex said:
Same for me, battery life sucks lately.
Click to expand...
Click to collapse
Then there are people reporting that their battery life has increased after updating to froyo. In fact mine was ok at first, until i started using FRF83 onwards then it all started to go downhill. This morning i woke up with the battery at 44% when i last saw it, it was at 90% the night before. It drained that much overnight and its not supposed to happen!
Mine was very good since updating to froyo ( starting from first builds leaked). Its very good now too, better than before anyway. I used to run of juice by 9PM, now i have ~ 20% left with the same usage.
Check out what apps are consuming the battery, i got terrible batt life when i tried the droidx live wallpaper.
App usage are the usual stuff.
Display being the highest, followed by android system, then cell standby, phone idle, twitter, android OS, launcher pro..etc
something seems to be sucking up my battery and i dont know what
I'll be the first one, I guess - I blame the task killer. It's widely known that you shouldn't need a task killer, unless you have some rogue app.
EarthsiegeTA said:
I'll be the first one, I guess - I blame the task killer. It's widely known that you shouldn't need a task killer, unless you have some rogue app.
Click to expand...
Click to collapse
But if your task killer is set to auto-kill on screen-off, even if various apps restart then that should only be in the first few minutes and shouldn't reduce the battery that much.
I have taskiller installed but only for manual killing of problem apps (a rare occurrence) and I have noticed poor battery life since moving to FRF85b - didn't notice anything of the sort in the Froyo versions before 85b though.
Well i just uninstalled task killer, i'll leave the phone running overnight again to test the battery again. But from the looks of it. It seems battery life has improved slightly, but it could be just me.
drewstiff said:
But if your task killer is set to auto-kill on screen-off, even if various apps restart then that should only be in the first few minutes and shouldn't reduce the battery that much.
I have taskiller installed but only for manual killing of problem apps (a rare occurrence) and I have noticed poor battery life since moving to FRF85b - didn't notice anything of the sort in the Froyo versions before 85b though.
Click to expand...
Click to collapse
Yeah thats true. It shouldnt suck up that much battery cos it only kills apps once. It could be an issue with the task killer causing it to drain the battery, because after uninstalling it i think the battery lasts a little longer. But i'll leave it running overnight again to confirm.
My quick story:
- frf72 and earlier - about 12 hours battery life for me. Used task killers, 2 emails on push. WiFi, BT off. Also tried juicedefender and setCPU. They made my battery life even worse.
- frf82+ (now frf91). Read up on how Android manages tasks and power. Got rid of all the task managers, setCPU and JD. Only use OSMonitor every once in a while to see if any dumbass app using up CPU in wakelock. So far none.
- EVERYTHING is ON. Wifi, BT, GPS - always on. I never use 2G, it's always 3G/HSDPA. GMAIL on PUSH, Exchange PUSH or 10minutes (no difference in battery for me)
- After a 24-hour test (from which 8 hours were on standby at night) I lost 80% battery life, so 20% still remain.
My advice: uninstall anything like setCPU, JD or taskkillers. Let Android handle that. Install OSMonitor and make sure nothing's in wakelock. Wipe cache if you want. If you're not getting 18-20+ hours, perhaps time to calibrate ur battery.
Thanks for the tip, just installled OSmonitor. The interface is pretty messy! But at least i understand whats going on. So all i need to do is keep track of which apps are at the highest load?
Is it really necessary to kill unwanted apps (Twitter, goggles, gmail..etc) because they are taking up RAM to improve battery life while idling?
OR you could just take Paul's advice and not use a task killer. My money is on him =)
FAQ: Why You Shouldn’t Be Using a Task Killer with Android
Wow thats a very informative read! Thanks for the link. I too also thought that an unwanted running task means i need to kill it to free RAM in order to speed things up and improve battery life. Didnt know im actually doing it harm.
Looks like i'll ditch my task manager for good and have faith in the OS.
Using LauncherPro Beta? I think some battery issues have been traced back to the way LP is handling updating widgets right now. Hoping for an update to fix it soon.
Well guess what. I just used the phone for an entire day and left it on since last night. It dropped down to 25% when i got home and was about to replace the battery pack. So it looks like task manager was the cause of the problem.
Launcherpro doesnt seem to be affecting the battery life.
cr0wnest said:
Well guess what. I just used the phone for an entire day and left it on since last night. It dropped down to 25% when i got home and was about to replace the battery pack. So it looks like task manager was the cause of the problem.
Launcherpro doesnt seem to be affecting the battery life.
Click to expand...
Click to collapse
Well it won't show up in the battery usage as affecting the battery. It has something to do with the widget updating not launcherpro. I removed BBC News, Beautiful Widgets and my Battery Info widget and my battery is now holding steady.
I'd be interested if you'd run an experiment, remove all updating widgets, notification widgets, etc and try again.
I reset my battery stats 2 days ago after doing a full charge and drain and full charge again my battery is at 94% after 1 hour. My time without signal is only 3%, phone idle is 42%, and only 15 minutes without sleeping. Does this sound normal or am I being anal?
Sent From My Hero!
That kind of sounds like mine. Extrapolating the percentage loss over time for me almost always yields a rate of about 100%/24 hours discharge, +/- 3 hours depending on use. I've always been concerned about the battery, especially after hearing so many people saying they get almost 48 hours on a single charge with moderate/heavy use
My battery is new. My Hero is less than a month old, but I haven't put on a custom ROM yet. I think a custom ROM and kernel is supposed to help. Mine is rooted and running SetCPU with profiles. I found that whenever my phone felt hot (which is a lot of the time, actually), it's usually an indication that battery is draining fast. I also read many peoples' Hero's run very cool, and don't get that warm when charging. Mine can get pretty warm when charging, close to 40C, and 42-43C when using while charging. These observations have caused me to wonder if my battery is bad, or if newer Heros are somehow different from old ones. Does this sound like yours?
I've learned that the battery usage is not linear.
So dont' worry about 1 hr sampling of your battery, use a minimum of 4-6 hrs and if it still losing 5%/hour after that w/out much use, then you may have an issue, but I wouldn't worry about it.
I'm using Crunchy's buufed rom with the OC'd kernel. My temp stays pretty even but I did add auto memory manager yesterday. I wonder if that's contributing.
Sent From My Hero!
I just figured it out. The stock sms is still locking up the dialer and keeping the phone awake. I figured that was fixed in these custom roms. So I disabled all notifications on stock sms and downloaded handcent. All is well.
Sent From My Hero!
I believe your aren't supposed to use things like autokiller and auto memory manager with an Oc'd rom.
I agree on the task manager but I thought the memory manager would tweak the built in settings from conservative to aggressive. Am I wrong?
Sent From My Hero!
It still does that but I've read posts by devs saying not to use autokiller with and overclocked rom, I don't understand why either but that's what it said.
Thanks for the heads up!
Sent From My Hero!
No problemo.
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.
ok so i own the sprint htc hero obviously and i keep switching between plain cm6 and blackmod every few months or so. For my Kernel i use
Decad3nce-DecaFuct #589 691mhz CFS stable
i keep it clocked at 245-691 with collins battery tweak
i charge my phone to 100% and then unplug it. screen off, gps, mobile data, sync, bluetooth, 3g, everything is off. brightness is as low as it can go. so im doing everything i can to save battery power. if i leave it in my pocket all day it CAN last about8 hours....that being said at that point its basically a brick. however if i turn anything on obviously it dies faster. if im online for 45 min my phone will die. a five minute youtube video costs me 32% of my battery. there is no way that my phone should be acting this way and im out of ideas. i have tried switching roms, wiping battery stats, running through battery cycles reverting back to stock via the RUU nothing works.
PLease if you wonderful people have any ideas *PLEASE* help me with this.....
Well you could try running a more current rom like CM7 or Aosp's CM7 GingerBread. Also you could try running your roms without the Collins battery tweak. You could try using dec's battery tweak if you prefer to use one. You could try calibrating your battery. Just a few things you could try that might help.
Edit: Also do you have an on screen off screen profile set with the battery tweak???
Yea its me Again With the
Modified Hero-
laie1472 said:
Well you could try running a more current rom like CM7 or Aosp's CM7 GingerBread. Also you could try running your roms without the Collins battery tweak. You could try using dec's battery tweak if you prefer to use one. You could try calibrating your battery. Just a few things you could try that might help.
Edit: Also do you have an on screen off screen profile set with the battery tweak???
Yea its me Again With the
Modified Hero-
Click to expand...
Click to collapse
i have tried cm7 and still had the same issue. and i am partial to the battery tweaks because setcpu and ocwidget seem like they would eat up resources wouldnt they?....i dont think ive heard of decs battery tweak tho....unless you mean the DECAmod one and i thought that was only for 2.1 roms.....maybe i got my facts mixed up tho...i calibrate my battery everytime that i flash a new rom to the phone. as far as i know the version i have does not allow for seperate profiles for screen on screen off.
I had the same problem and out of curiosity i dropped my processor speed from 710 to 576. Yeah its slower but on Aosp/CM7 and with sd-ext done its plenty fast. and with everything on and the phone in my pocket i drop about 4% every hour.
lycancowboy1989 said:
i have tried cm7 and still had the same issue. and i am partial to the battery tweaks because setcpu and ocwidget seem like they would eat up resources wouldnt they?....i dont think ive heard of decs battery tweak tho....unless you mean the DECAmod one and i thought that was only for 2.1 roms.....maybe i got my facts mixed up tho...i calibrate my battery everytime that i flash a new rom to the phone. as far as i know the version i have does not allow for seperate profiles for screen on screen off.
Click to expand...
Click to collapse
Deca's BattMod will work on CM7/aospCM7. However with CM7 you really don't need it (or anything else to overclock/underclock) as CPU settings are in the ROM itself. In fact, it is recommended that you don't, as they will/could fight with each other.
If properly calibrating the battery (properly is the key word) doesn't get you at least a solid day with moderate use, I would say it's time to look for a new battery. How old is it? Mine is about two years old and I still get about 2 days, stock aospCM7 ROM and kernel, moderate use with ONDEMAND 176/729
whodatxevg said:
I had the same problem and out of curiosity i dropped my processor speed from 710 to 576. Yeah its slower but on Aosp/CM7 and with sd-ext done its plenty fast. and with everything on and the phone in my pocket i drop about 4% every hour.
Click to expand...
Click to collapse
I'd still say that 4% an hour, without using the phone is way too much. If your battery is still good, you should be able to get better than that by at least half (2% an hour drop).
I have been up for two hours (unplugged at 6AM, it's now 8:56AM) and am still at 99% and that is with moderate usage (a couple texts, sent and received an email, one 3 minute phone call, some Facebook and XDA).
See ^^ for my settings. Give it a try
My brothers hero would die incredibly fast also no matter what we tried. We ended up RUUing and taking it into sprint. They did a battery test said they didn't know why it died so fast and ordered him a brand new one. He had normal batt life again after that.
So if all else fails try taking it into sprint and see what they tell you.
Sent from my HTC Hero CDMA using XDA App
lycancowboy1989 said:
ok so i own the sprint htc hero obviously and i keep switching between plain cm6 and blackmod every few months or so. For my Kernel i use
Decad3nce-DecaFuct #589 691mhz CFS stable
i keep it clocked at 245-691 with collins battery tweak
i charge my phone to 100% and then unplug it. screen off, gps, mobile data, sync, bluetooth, 3g, everything is off. brightness is as low as it can go. so im doing everything i can to save battery power. if i leave it in my pocket all day it CAN last about8 hours....that being said at that point its basically a brick. however if i turn anything on obviously it dies faster. if im online for 45 min my phone will die. a five minute youtube video costs me 32% of my battery. there is no way that my phone should be acting this way and im out of ideas. i have tried switching roms, wiping battery stats, running through battery cycles reverting back to stock via the RUU nothing works.
PLease if you wonderful people have any ideas *PLEASE* help me with this.....
Click to expand...
Click to collapse
When you go to the battery usage stats in Settings--About Phone, what does it show you? That may show/tell what is eating up your battery so much.
What is your signal like? Are you in an area with poor signal? If so that could possibly cause the battery drain -- a phone working hard to keep a decent signal eats battery pretty quickly. Consider upgrading to the newest .29 radio baseband (if you're on Sprint) if you haven't already.
Try to check out the battery usage in your Settings and report back what it shows. We may can help you notice anything out of the norm.
ranger61878 said:
Deca's BattMod will work on CM7/aospCM7. However with CM7 you really don't need it (or anything else to overclock/underclock) as CPU settings are in the ROM itself. In fact, it is recommended that you don't, as they will/could fight with each other.
If properly calibrating the battery (properly is the key word) doesn't get you at least a solid day with moderate use, I would say it's time to look for a new battery. How old is it? Mine is about two years old and I still get about 2 days, stock aospCM7 ROM and kernel, moderate use with ONDEMAND 176/729
Click to expand...
Click to collapse
my phone is about 7 months old. so battery *shouldnt* be crapping out quite yet as battery life on one of these seems to typically be about two years before it starts to crappify.
@MrDowntown12
i thought about that but was worried that the ruu doesnt get it COMPLETELY back to stock. good to know it does and that someone pulled one over on sprint ^_^ if all else fails then ill try this but in all honesty they will prob still charge me $50 and i just dont have it.....
@chromiumleaf
battery usage is:
Display 59%
cell standby 12%
Phone idle 11%
android OS 8%
Media 5%
setcpu 3%
google search 2%
gallery 3d 2%
"top -m 5 -n 1" returns
process id 2337 at 8% and 163 which i believe is the phone itself if im not mistaken is at 5%......everything else is zeros.
also i think my coverage is pretty average. throughout the day i typically have about three bars but my dbm is 80-100 the whole day and im not sure if thats high.
fyi these stats are while doing my battery cycles if it matters. and ive been unplugged for about 25 min and ive dropped from 100 to 91 with doing nothing but checking battery stats and running the terminal for a minute.
Edit: i know that android os is getting more and more popular....do you think its possible that i caught some kind of virus somehow???? the only ones ive seen are in china but is it likely that my phone is infected? also i want to run cm7 but as far as i can tell there really arent any stables out yet just the experimental nightlies and ive tried it and it didnt fix drain *immediately* but maybe after batt cycles? second edit^_^ i apologize i did not know exactly what you meant by signal. after finding THIS
-105 to -100 = Really bad
-99 to -90 = Not great
-89 to -80 = Pretty good
-79 to -65 = Good
Over -65 = Excellent
i now understand and my dbm hovers at about 88 half the time and the other half it shoots to 97
lycancowboy1989 said:
battery usage is:
Display 59%
cell standby 12%
Phone idle 11%
android OS 8%
Media 5%
setcpu 3%
google search 2%
gallery 3d 2%
"top -m 5 -n 1" returns
process id 2337 at 8% and 163 which i believe is the phone itself if im not mistaken is at 5%......everything else is zeros.
fyi these stats are while doing my battery cycles if it matters. and ive been unplugged for about 25 min and ive dropped from 100 to 91 with doing nothing but checking battery stats and running the terminal for a minute.
Click to expand...
Click to collapse
Ok so if all you were doing in 25 mins was checking battery stats and running the terminal for a little bit, it seems strange that Google Search, Gallery 3d, and Media would have some battery pull on them -- did you even open/use them at all? If not, then it seems like maybe you have some programs running non-stop in the background that are eating your battery even when you're not using them. Try clearing data and cache for any of those in your Settings-->Applications-->Manage Applications menu.
Also, just curious...when you change roms, do you wipe everything (data, dalvik, ext) before flashing to a new one?
ranger61878 said:
I'd still say that 4% an hour, without using the phone is way too much. If your battery is still good, you should be able to get better than that by at least half (2% an hour drop).
I have been up for two hours (unplugged at 6AM, it's now 8:56AM) and am still at 99% and that is with moderate usage (a couple texts, sent and received an email, one 3 minute phone call, some Facebook and XDA).
See ^^ for my settings. Give it a try
Click to expand...
Click to collapse
I forgot to say that i have music playing through headphones whenever im awake lol, but yeah ill give that a try.
No I had not used any of those. I tried what you suggested and the battery is draining faster T^T. And I always do a full wipe. I wipe data and dalvik reformat my sd and as soon as I her the rom on my phone I go through three battery cycles.
HAHA Solved! for me anyway.
ok so my guess is that its not reading my batts full capacity because i didnt charge fully before one of my flashes. so what i did was:
*charge to full
*run my ruu to revert back to stock
*with phone -ON- charge til green
*power -OFF-
*charge for another two hours
*boot into recovery
*flash like you normally would
*Run through your Battery cycles like normal
since i have done that my battery has been fine. or as good as a battery on a smartphone can be anyway lol
Hey Guys, I've posted in other conversations about bad battery life with blitzkrieg and it seems pretty split down the middle between those who experience good battery life and those who don't. I did follow the advice and wait several days after I re-flashed blitz and my battery has yet to level out. I keep background data off at night when I go to bed, I went to bed with 93% battery left and woke up 7 hours later with a 23% battery life - while the phone was at rest.
I also have a problem about once every two days my phone will freeze up and restart. When it happens it just gets froze on screen and the whole phone vibrates for 20-30 seconds and then restarts.
Has anyone experiences these problems and found a solution to them? Should I change my settings at all?
I really don't want to get an extended battery but with the life my phone is currently getting I don't see much more of an option.
Thanks guys,
The phone freeze/reboot is a known issue with no known resolution. Before I dropped my last phone it had that problem consistently from stock v4 through every variant of the ota updates, revolt roms, gingervolt roms, kennels, scripts, no scripts, blah blah etc.
Now, however, I picked up a second Revo and have run it through gb and flashed gv 1.3, blitz 2.1 and various scripts and tweaks virtually mirroring my old device. I did that Monday morning and haven't had a single instance yet! These guys here do awesome work..
As for the battery draining, I haven't put my extended battery back on this phone yet because I was curious how the stock would perform with these mods. For the first couple days I was discharging at an even 10% an hour. Yesterday and today its dropped to 7.5%. Why? No damn idea. But I can live with that.
So, nothing terribly helpful here but just a disclaimer that your mileage may vary and a nod to the devs here doing kickass work. Good enough that I actively went looking for another Revo instead of fussing with a second line upgrade. That speaks volumes.
Oh yeah I'm not dissing the devs at all they're great!
The revo is a strange device all the reboots due to GPS and airplane mode I'm sure is a hardware fault because every revo I've had has done it and I'm on my third. I love blitz and can't live without my overclock lol I'm just wondering if there's special settings or CPU governors I'm not using that would help.
Sent from my VS910 4G using XDA App
I've used CPU Master and am on ROM toolbox now. Can't say I've seen a significant difference between the two as far as battery goes. I've used both ondemand and smoothass, same deal.
I did have some luck limiting reboots on my first by bumping up the min to 768 but haven't needed to bother on this phone so its 2 something. No extra settings or anything. : )
Guess it's just the screwy differences in hardware that make some a better build quality than others. Well I said I wouldn't do it, but I lied...
I'm restoring to my GV 1.3 pre-blitz image as I type this. Guess I like battery over performance, we'll see...I may be back to blitz.
Can somebody explain the difference between ondemand and smoothass. I still don't understand them that well. Thanks!
I didn't read the whole thread but seeing profiles for the kernel helps a lot like when my screen is off my phone is set to minimum on the min and max which sometimes causes lag turning on but once the screen comes on it's up and running fine. At that level if I keep the screen off it takes nearly an hour to drop a percent.
Sent from my VS910 4G using xda premium
Perhaps this is not the best reference but here is one about charging your Lion battery:
This link won't paste:
[URL="http://dottech.org/tipsntricks/17705/tip-condition-your-new-cell-phones-battery-to-make-it-last-longer-but-be-sure-to-condition-it-properly/[/URL]
It points out two possible issue:
1) over discharge (perhaps our meters account for this,
2) getting the battery hot, my phone does warm up setting on the charger, sounds like the usb port charging might be better for the battery?