Related
Yo
heres a brutally simple battery monitor software thingy that graphs your usage and battery level - top graph is mAh usage (15000ms refresh (os updates info every 30 secs)) and bottom graph is battery life (60000ms refresh)
i wrote this thing to monitor my batt usage cause my bat life is utter crap, barely lasts 8 hours with my level of use/cellular climate, which sucks its just a straight up .exe, just copy to where-ever and run it
this version here is so pre-alpha-uber-dev-debug-build its not funny but i thought id put it up for you lot anyway as i have found it useful just to glance at from time to time - there are no user controls, i spazzed this out in a hurry but i intend to improve on it and implement any features you lot might think useful.
best i can get out of my raph with screen on with celluar, gprs and bt ad2p connected is -63mAh - whats the best you can get?
just tryin to put smt back into the community <3
p.s. this is a debug build (i kept getting microsoft error reporting crap on the emulator, so i dunno how itll go on other devices)
p.p.s. i take no responsibility if this bricks your device, sleeps with your wife, sets your house on fire or kills your cat etc etc (but it works ok on my raph
***UPDATED 25.03.09***
SEE POST #9 IN THIS THREAD BELOW
going to try this out soon, loving the simple graph
now i can see whats happening when 40% of my battery dies overnight as i sleep >:O
works good, any way of making it show the current time on the x-axis? or able to scroll left and rigth to see what happened earlier?
and whats the bottom graph for?
07accordEX said:
any way of making it show the current time on the x-axis? or able to scroll left and right to see what happened earlier?
Click to expand...
Click to collapse
both of these features are on the todo list (which ill put up when i get a moment)
and whats the bottom graph for?
Click to expand...
Click to collapse
read the initial post.
the top graph shows the past hour of activity (ish, its actually more like 57.5 mins), the bottom graph shows the past 8 hours (ish, more like 7.7hrs).
no data is collected when the device is asleep - and the graph doesnt get updated during these times, so you only see 'active' use in the graphs - i plan to implement some sort of visual cue system to signify times of sleep and also to keep the temporal coherency of the graph more contiguous (lol, e.g. a graphed minute will be 8 pixels wide no matter what).
i believe its impossible to collect data while the device is asleep as afaik when the processor goes to sleep the only part of it that functions is the bit that listens for interrupts (from i.e. the phone management cpu, etc) (and maybe a timer (for alarms etc?)) - if im wrong on these details please enlighten me.
fusi
Nice app I would love to see it becoming more mature, will probably end up with my standard equipment, thanks 12
12aon said:
Nice app I would love to see it becoming more mature, will probably end up with my standard equipment, thanks 12
Click to expand...
Click to collapse
thanks, watch this space should have something new up by the weekend
This opens up a blank white page on my phone. Did I do something wrong?
behrouz said:
This opens up a blank white page on my phone. Did I do something wrong?
Click to expand...
Click to collapse
the graphs dont refresh as soon as you open the app - youll hve to wait for the first update (15 and 60seconds) before anything is rendered - this will be fixed soon.
ok, a bit later than advertised but here is an updated version - fixed most things, still working on scrolling through the history - will add more features in coming days (colour customisation, toggling graph display, scrolling through history, exporting graphs as images, user customisable update intervals, etc)
btw ive added in support for unattended mode - this keeps the cpu alive when the device is asleep - i dont recommend keeping this on unless you are trying to debug unexplained power drain in standby - unattended mode keeps my raph ticking along at -21mAh, when im pretty sure true idle for this handset is more like -4mAh. so yah, not recommended to leave it on
im pretty sure there arent bugs but if you find one please let me know!
enjoy
fusi
fusi said:
ok, a bit later than advertised but here is an updated version - fixed most things, still working on scrolling through the history - will add more features in coming days (colour customisation, toggling graph display, scrolling through history, exporting graphs as images, user customisable update intervals, etc)
btw ive added in support for unattended mode - this keeps the cpu alive when the device is asleep - i dont recommend keeping this on unless you are trying to debug unexplained power drain in standby - unattended mode keeps my raph ticking along at -21mAh, when im pretty sure true idle for this handset is more like -4mAh. so yah, not recommended to leave it on
im pretty sure there arent bugs but if you find one please let me know!
enjoy
fusi
Click to expand...
Click to collapse
I'm curious to know what you think the power consumption caused by this program is. Like you, I get about 21mA drain with the phone screen off - but I'm getting that with your old version. I use S2U2 with the "but only blank screen" option and turned off standby in Windows power management so I think that's effectively putting the phone in unattended mode. Normally (without your program running) I see pretty modest battery drain with the phone in unattended mode. Just off the top of my head I'd say that 5-15% battery drain per hour would be about what I'm used to with zero usage - phone just sitting in my pocket or on a desk in "unattended mode" but just now while running your older EXE my phone went from 65% to about 40% in under an hour while "unattended" (locked, screen off). Looking at the graph for that time period I see a consistent 21mA drain. If 21mAh=25% capacity, I'm in trouble. I know my battery isn't that far out of whack because I get what I'd consider (based on reading other's experiences) pretty normal life out of it. Maybe the drain characteristics for that "portion" of the battery are a little different - I'm not sure whether the capacity is judged solely on capacity minus drain or it figures voltage levels in as well...?
To be clear, I'm basing my sense of normal battery consumption on nothing more than "took it off the charger in the morning, didn't use it all day at work and have ~50% when I get home 9 or ten hours later" so it's anecdotal at best.
I'll keep playing - I love this tool. Maybe I'll be a little more scientific about my testing and see if I'm imagining things.
Hi thanks for posting
if your just turning the screen off, i dont think thats unattended mode, unattended mode actually powers down non essential parts of the device.
if unattended mode is off in the program and your phone goes into standby, it wont consume any battery as when the phone goes into standby everything is shutdown and the cpu pretty much stops functioning (apart from a very small part) - but this also means the historical data and graphs dont get updated . if unattended mode is on and your phone hits that standby timeout, it wont go into standby but unattended mode instead where it just turns off a lot of the non-essential stuff, like voltage to the sd card, the screen, etc - but it keeps the cpu running and the operating system pumping its messages.
i think a chunk of that 21mAh is going to be the operating system - but not all of it - currently the program registers 2 timers with the os, one has a 15second timeout and the other has a 60 second timeout. timers do drain battery, as the cpu keeps having to go 'is it time yet? is it time yet?' ad infinitum.
btw, when i said 'true idle' in my prev post i meant that that is the current used in true standby.
one way to calculate how much current its drawing is to leave your phone running it for 24hours (airplane mode on etc) and see how much its depleted over that time, then do it again without it running. using that information you can figure out how much current its using - i havent done this yet, i cant put the thing down for 5 minutes let alone 24 hours
im currently working on a system that doesnt use timers, it might work, might not if it does i hope to see that 21mAh reduce, but i dont imagine itll go down by that much. there are however loads of optimisations that can be done, and im investigating them atm.
im no battery scientist but as far as battery capacity, i think li-ion batteries judge their capacity by their voltage, from something like 3v up to 4.2v (0% -> 100% [wiki link below]) - i could be wrong on that though.
http://en.wikipedia.org/wiki/Lithium_ion_battery <-- this is a good informative read.
i dont think the battery is very capacious tbh - any amount of drain and it seems to go down very fast - i think the saving grace of the device is that is consumes minimal power when in standby - on days where im constantly using it heavily, im practically tethered to a power outlet as the battery just drains far too fast - i think the manufacters banked on the assumption that users would mostly have the phone in standby mode for most of the day. i usually use it for music while im at work and have putty sessions open etc, so its always on - i barely get 8 hours use without a charge .
ive noticed with my battery that even though the drain is constant (i.e. 21mAh or 63mAh) the charge level of the battery does not decrease linearly - e.g. ive noticed my phone suddenly start going down and lose 10% in 5 minutes before, and then the charge level would level out and stay at the same capacity for like 10 minutes before starting to go down again - this to me seems a little funny, as if the circuitry reporting the capacity isnt quite accurate - i think there a many factors, including battery temperature, the drain on the battery in mAh (i think a spike of higher drain may cause the battery do the nose-dive-then-level-out thing) - but i also think that the battery just doesnt deplete linearly, it seems to always have lumps and bumps in the graph, no matter how smooth the drain is.
glad you like the app ill be posting an update to it in a week or so.
peace
fusi
I'm not sure what exactly S2U2's "but only blank screen" does, but it leaves me with a 21 mA draw, so it can't be much different from unattended mode. I haven't tried to monitor it in that mode with (for example) an active Wifi connection or a program accessing the SD card to see if that changes things, but as it is it seems to be running the same things your set is.
The only reason I think the capacity calculation must not run off of only the voltage is that it has a definite "learning" capability. I think it must be doing some more complex things behind the scenes in terms of monitoring consumption and recalibrating periodically based on charge and discharge rates. I know I've seen it sit at 99% charging for a (very) disproportionately long time. The only good explanation for that is that it wasn't perfectly calibrated and the battery is still accepting charge at a higher rate than an almost full battery would. I've seen the same behavior in a lot of charge monitoring systems as they "learn" the characteristics of a battery. I guess it could be basing that purely on voltage, but I doubt it. While connected to a charge, the system will report a substantially higher voltage than it will as soon as the charging voltage is disconnected.
I don't know, I'm just kind of thinking aloud here. It would be great if there were a way to poll the power consumption without affecting the power consumption - sort of a Heisenberg's uncertainty problem... I'd really like to know what the power consumption is in unattended mode as well as true standby. Even if you do the 24 hour test you have to assume a lot of things about the battery's initial condition and the accuracy of the meter to arrive at a consumption number (and, like you, I'll never have a day I don't want to putter around with this phone). I suppose if you were really into it you could stick an ammeter between the battery and phone and control for the added loss
It's definitely true that the discharge isn't linear, even given a constant discharge rate. This has to be an artifact of including battery voltage in the capacity calculation. If it was using purely capacity minus usage the relationship would have to be linear.
Anyways, keep up the good work. I love stuff like this, just from an academic standpoint. Practically speaking I'm pretty much tethered to my chargers, too...
hyachts said:
I'm not sure what exactly S2U2's "but only blank screen" does, but it leaves me with a 21 mA draw, so it can't be much different from unattended mode.
Click to expand...
Click to collapse
That's exactly the case, this setting causes your device to run in unattended mode (backlight off, audio off, wi-fi off, ...)
hyachts said:
I think it must be doing some more complex things behind the scenes in terms of monitoring consumption and recalibrating periodically based on charge and discharge rates. I guess it could be basing that purely on voltage, but I doubt it. While connected to a charge, the system will report a substantially higher voltage than it will as soon as the charging voltage is disconnected.
Click to expand...
Click to collapse
Microsoft's reference battery driver for PXA270 CPU is calculating battery percentage based on voltage exclusively. HTC's custom driver for Qualcomm cores seems to have some kind of more advanced logic behind it, but it doesn't work well/smooth.
hyachts said:
I don't know, I'm just kind of thinking aloud here. It would be great if there were a way to poll the power consumption without affecting the power consumption - sort of a Heisenberg's uncertainty problem... I'd really like to know what the power consumption is in unattended mode as well as true standby.
Click to expand...
Click to collapse
Not without external tools, it should be possible to hook up an external multimeter to the battery directly to measure the voltage accurately in standby. Using the battery driver information you can only evaluate it and the evaluation is likely to be pretty rough.
Attached are some charts from my Touch HD...
The battery level graph seems to follow consumption graph very closely.
You can barely notice the resemblance with the voltage graph though.
These charts depict my device's utilization over 2 days, assuming 0 mah consumption when in standby. This assumption is apparently not accurate, as the battery capacity is 1350 mah and only about 1000 mah were utilized. Out of these 48 hours the device was in standby for about 40 hours, so my estimated standby utilization is -350mah/40h => -8.75mah. This doesn't sound reasonable, as according to manufacturers specs, the device is capable of 450h of standby, with 1350mah battery standby consumption should be -1350mah/450h => -3.375mah. I would agree with fusi, that taking manufacturer's estimation errors it should be safe to assume standby consupmption is around -4mah.
40*-4mah=160mah, so I have about -190mah remaining unaccounted for. I blame measurement accuracy for this... IMO, with this degree of inaccuracy, standby consumption can not be accurately estimated and has to be assumed based on manufacturers specs only.
I'm running more tests to reconfirm these observations, but I doubt the results will be extremely different.
For your reference, I get -69mah on Touch HD when idling with minimal backlight level and -27mah in suspended mode.
Hello guys,
lately my Nexus One abttery consumption gets more and more consumptive. I dunno why, I already reduced the home screen from 7 became 5 and reduce the widgets too. but the battery life now did't even reach one day.
I read that someone has their nexus one running 3 days with browsing and GPS n Sync ON.
any advice how to conserve battery life?
There are plenty of threads discussing that same question. Basically the answer is that there's no perfect formula. Experiment and see what you can achieve.
Personally I tend to turn off most of automatic syncing stuff, but it's not because of battery life, but rather because I want more control.
Also, if your mobile reception is constantly low, your battery life will be significantly shorter.
heres what i did to increase my battery life.
turn off wifi/bluetooth
i leave my screen brightness at 100% (i like my screen bright) and leave gps on since its only used when gps is required
download a battery saving kernal. im using intersectraven 925mv kernal. less power consumption=less battery used. its been shown that 925mv is the best voltage compared to 800mv/1000mv
download "Task Manager" from the market. use it to set all apps to "kill list" so that everything is killed when you put ur phone on lock/sleep. This app helped me save tons of battery. Power doesnt drain at all when your phone is idle and my phone is at constant 250+/- memory.
other then that my phone has all the widgets on the homescreen and battery is good
d0mo said:
download "Task Manager" from the market. use it to set all apps to "kill list" so that everything is killed when you put ur phone on lock/sleep. This app helped me save tons of battery. Power doesnt drain at all when your phone is idle and my phone is at constant 250+/- memory.
Click to expand...
Click to collapse
I don't suggest doing it, since it brings nothing good and no power saved. If you kill widgets that update themselves - you might as well not put them on the screen, since they do nothing. If you kill system services - you might as well uninstall the programs that run them, since they're not working. And for everything else - you're just wasting the CPU time required to kill and then relaunch programs, and the memory that can be used better.
d0mo said:
heres what i did to increase my battery life.
turn off wifi/bluetooth
i leave my screen brightness at 100% (i like my screen bright) and leave gps on since its only used when gps is required
download a battery saving kernal. im using intersectraven 925mv kernal. less power consumption=less battery used. its been shown that 925mv is the best voltage compared to 800mv/1000mv
download "Task Manager" from the market. use it to set all apps to "kill list" so that everything is killed when you put ur phone on lock/sleep. This app helped me save tons of battery. Power doesnt drain at all when your phone is idle and my phone is at constant 250+/- memory.
other then that my phone has all the widgets on the homescreen and battery is good
Click to expand...
Click to collapse
1+2 = Nonsense.
1 - Kernel
2 - Task Killers cause more problems then they help.
Battery life is simply a function of how much CPU time is being used, how much data is being transferred, and how much the screen is on. Poor reception is another thing to consider, in most cases it's one of the three things above. Of course there are other factors, like how much you're talking on the phone, etc, but it boils down to three major things.
CPU time generally is only a problem when using the phone, games, live wallpapers (particularly 3D ones), and sometimes bad processes or badly designed programs. You can evaluate all of this using System Panel in the market.
How much data is being transferred you can control directly by setting your sync settings, or if you want to isolate it completely, disable syncing on all apps and otherwise use the phone normally. If you have Facebook, Twitter, MySpace, GMail, IM (Gtalk/whatever others), Weather, etc all syncing, it's going to be a lot of random traffic. Setting the phone to EDGE-only will reduce some of the battery usage from this, but controlling the syncing itself IMO is a better option than using EDGE.
Screen of course is how much you are playing with the phone, and I think this is the one that most people have problems with. If you're messing with the phone all day long, yes, it's going to "eat battery", and it's going to be caused from all three things above. CPU from you doing stuff, probably network traffic from you doing stuff, and the power to drive the screen. Some people suggest using black themes or backgrounds. Yes, AMOLED uses more power to drive a bright white than an LCD, and much more power to drive bright white vs black or dark, but think about how much you're staring at the background.. Only on the launcher. Do you stare at the launcher all day? But perhaps if you're reading a book for an extended period it's worth it to set it to white on black, vs black on white. Sometimes you can't control this, such as the browser is (generally) a white background.
I'm no expert, but god I'm tired of hearing nonsense around everything "eating battery".
I see, thanks 4 d advice you all
maybe the good way out is the Kernel flashing.
any recommendation maybe? which kernel are the best?
I don't want to downgrade my 1GHz clock though...
and URL is appreciated
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.
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.
I just bought this phone, one thing i dont know why because battery's using time is short, only 5 hours. I want to know that everyone the same as me?
You either have a n app eating thru your battery or a faulty battery.
Check in Settings/Battery. If nothing special pops out there, you might want to try a factory reset and see if that still happens.
In the past I also used GSam to get more info on battery usage.
maddler said:
You either have a n app eating thru your battery or a faulty battery.
Check in Settings/Battery. If nothing special pops out there, you might want to try a factory reset and see if that still happens.
In the past I also used GSam to get more info on battery usage.
Click to expand...
Click to collapse
Thanks buddy, what rom are using in phone and the time on screen'battery
Having the same issue with the same model.
Follow the 2nd post.
(SOT) Leaderboard - post your longest SOT's here 👍🏻
Looking at the OnePlus 10 pro on paper, it has everything you would possibly need to achieve incredible screen on times. The idea behind this besides some healthy competition is to whittle out the bugs and battery draining apps and habits.... in...
forum.xda-developers.com
Keep all social apps insta FB and WhatsApp with restrictions of background and foreground activity and keep auto launch off . That's make your battery long lasting. Keep optimization on in battery settings.
U can check other apps which are battery hungry and keep activity restricted.
Do not use always on display function.
dladz said:
Follow the 2nd post.
(SOT) Leaderboard - post your longest SOT's here 👍🏻
Looking at the OnePlus 10 pro on paper, it has everything you would possibly need to achieve incredible screen on times. The idea behind this besides some healthy competition is to whittle out the bugs and battery draining apps and habits.... in...
forum.xda-developers.com
Click to expand...
Click to collapse
As far as I know I am the current leader of the SOT thread with 12.5 hours SOT and 23% battery left, unfortunately I literally didn't even try to get it at first and was in 120hz 1440p (no auto switch) with no battery saver at all lol. If you want a lot of SOT you can cheese it by streaming and doing nothing else thanks to the Snapdragon 8's efficiency with video
jld2k6 said:
As far as I know I am the current leader of the SOT thread with 12.5 hours SOT and 23% battery left, unfortunately I literally didn't even try to get it at first and was in 120hz 1440p (no auto switch) with no battery saver at all lol. If you want a lot of SOT you can cheese it by streaming and doing nothing else thanks to the Snapdragon 8's efficiency with video
Click to expand...
Click to collapse
That would be great. Do you have the screenshots you would need to register your sot?
As per the requirements?
If so I'll be happy to add your time
If you're experiencing rapid battery drainage with your OnePlus 10 Pro, there are a few steps that you can take to solve this issue.
First and foremost, it is important for you to understand why the battery drains quickly. There are several factors that may contribute to this problem, such as the presence of background apps running in the background without your knowledge and an inefficient power management system.
To address the first factor, reducing or disabling any applications running in the background can help improve battery performance significantly. To do so: go into Settings > App Manager > Running Apps, where you can see which apps are currently active on your device. You should close or uninstall any unnecessary apps as they consume energy even when not actively used by you.
For further improvement of your device’s power efficiency, it also helps to recalibrate its internal Power Management System (PMS). This process involves resetting how much power is allocated for different tasks on your OnePlus 10 Pro allowing it to run more efficiently and effectively utilize whatever charge remains in its unit’s battery pack while still providing optimal performance. It is recommended that this procedure be done at least once per month or after factory resets – but no more than three times per month – as excessive PMS calibrations will only lead to shorter lifespan of both software and hardware components over time instead of better performance gains and improved efficiency levels.
Finally if these two solutions fail then eventually replacing/repairing parts inside phone such as motherboard may prove beneficial for fixing Oneplus 10 pro Battery Drain Fast issue permanently however seeking professional help from authorized service centers would be necessary before attempting similar DIY repairs within home due safety related issues involved with components which are sensitive enough handle with proper care & expertise .
Some tips I've shared over the years.
Change 5G to 4G
Remove tiktok it is 100% dodgy Chinese spyware.
Remove Facebook use web based
Remove Facebook messenger use web based
Remove Twitter use web based
Remove any ad based apps pay for the pro version
Turn off gestures like lift to wake
Change from QHD to FHD (No difference)
Allow auto brightness
Turn off WiFi overnight
Turn all updates to manual not auto (play store)
Remove any so you don't use
Change back up to once a month (WhatsApp)
Turn off location history (Google)
Use titanium to remove any system apps you don't need
Don't allow anonymous usage statistics for any app ever.
Don't allow tracking cookies on any website
Use adaway (root needed)
Don't open web pages in Google app (I use Samsung browser)
Don't use xposed.
If you game you will not get high SOT scores, period.
Don't bother with battery saving apps or monitoring apps.
Streamline your apps, if you don't use it, remove it.
Don't allow WiFi scanning (as in letting other apps use it when it's not on)
Never allow personalised ads.
Never allow notifications from websites
Always decline cookies unless your absolutely have to allow some tracking (common sense prevails here)
Optimise as many apps as possible unless it affects performance.
Don't allow apps to remain open in the notification area.
Change your launcher, my preferred launcher is lawn chair and this did actually burn up some battery when compared to the OnePlus launcher.
Don't use live widgets (yes they look cool, but they annihilate your battery)
Live wallpaper, again very cool, but battery burners.
Again! Don't charge overnight, make a note of your percentage then see what it is in the morning, you shouldn't be losing more than 5% really, if you've done well then it'll be reflected here, the good SOT results will follow.
Turn off live read outs of network speed, RAM usage in the status bar.
Turn off NFC unless in use.
Leave location on in quick settings.
Don't overcharge your phone, IE: overnight
Don't allow your phone to fully deplete the battery.
Whatever anyone says, this does 100% damage batteries, there is no argument here and I won't entertain anyone who says otherwise, Ive seen through real life tests what this results in, bloated, inefficient, possibly dangerous lithium batteries.
Keep your phone out the sun.
Keep it out of extreme cold.
Keep your device clean dust free.
Snapchat, Viber, house party, apps like that tends to use more battery as they don't have great dormancy periods.
Apps like speed test by Ookla tend to have location tracking, similarly they tend to turn themselves on and off when they feel like it, my advice, install test and uninstall.
Allow a couple of battery cycles between tweaking sets, to give you an idea of how much of a difference you've made.
Use BBS to see what is being used, once you've removed problems, remove BBS.
I've just written this from the top of my head so o probably missed some things, the general idea is to keep your device clean and fresh, remove files you don't need any more.
Keep an eye on apps that misbehave or aren't wanted, index your folders so they aren't a mess.
The more good things you do means the more potentially bad apps you can have on your phone, eg if you really need Facebook, you could keep it so long as you clean up other areas of your phone.
Good luck.
When it comes to battery optimization for the OnePlus 10 Pro, version 2213, I have a few suggestions that might help you maximize your device's battery life.
Firstly, it's important to note that OnePlus devices generally come with a variety of built-in battery optimization features. To begin, make sure you have enabled the battery optimization settings on your device. You can usually find these settings in the device's "Battery" or "Power" section within the settings menu.
Additionally, I recommend keeping your device's operating system up to date. Manufacturers often release software updates that include battery optimizations and improvements. So, regularly check for updates and install them as they become available.
Another effective approach to conserving battery life is by managing your apps and their power consumption. Identify any apps that are known to drain battery excessively and either limit their usage or consider uninstalling them if they are not essential. You can find battery usage statistics in the device settings, usually under "Battery" or "Power."
Furthermore, adjusting the screen brightness and timeout settings to a level that suits your needs can significantly impact battery life. Lowering the brightness and reducing the screen timeout duration can help conserve power.
Lastly, keeping unnecessary features and connections turned off when not in use can make a difference. Features like Wi-Fi, Bluetooth, and GPS can consume additional power if left enabled unnecessarily.
Maria1991 said:
When it comes to battery optimization for the OnePlus 10 Pro, version 2213, I have a few suggestions that might help you maximize your device's battery life.
Firstly, it's important to note that OnePlus devices generally come with a variety of built-in battery optimization features. To begin, make sure you have enabled the battery optimization settings on your device. You can usually find these settings in the device's "Battery" or "Power" section within the settings menu.
Additionally, I recommend keeping your device's operating system up to date. Manufacturers often release software updates that include battery optimizations and improvements. So, regularly check for updates and install them as they become available.
Another effective approach to conserving battery life is by managing your apps and their power consumption. Identify any apps that are known to drain battery excessively and either limit their usage or consider uninstalling them if they are not essential. You can find battery usage statistics in the device settings, usually under "Battery" or "Power."
Furthermore, adjusting the screen brightness and timeout settings to a level that suits your needs can significantly impact battery life. Lowering the brightness and reducing the screen timeout duration can help conserve power.
Lastly, keeping unnecessary features and connections turned off when not in use can make a difference. Features like Wi-Fi, Bluetooth, and GPS can consume additional power if left enabled unnecessarily.
Click to expand...
Click to collapse
Good post
Would you say the Oneplus 10 Pro is still a good phone for this year even? Very new?