Related
Hi There,
Im trying to find out why my battery is getting sucked dry so quickly so I've installed acb Power Monitor.
On first install it seemed to work fine (although my drain of 250+MaH seemed excessive) but now when I load the program up the figures are all wierd.
my X range goes from 0mA to 4.5E+09mA ?
also my NOW says 42949672 AVG 46684295 TOTAL 110953....ect ect a load of unreadable rubbish.
Is this an uncompatible issue with WM6 or Kaiser?
Cheers for any help.
Sideburnt said:
Hi There,
Im trying to find out why my battery is getting sucked dry so quickly so I've installed acb Power Monitor.
On first install it seemed to work fine (although my drain of 250+MaH seemed excessive) but now when I load the program up the figures are all wierd.
my X range goes from 0mA to 4.5E+09mA ?
also my NOW says 42949672 AVG 46684295 TOTAL 110953....ect ect a load of unreadable rubbish.
Is this an uncompatible issue with WM6 or Kaiser?
Cheers for any help.
Click to expand...
Click to collapse
Try giving a try to acbTaskMan; in the free (lite) mode, it's about as informative as acbPowerMeter but is, otherwise, much better and newer.
Let me know what happens.
I have just tried acbTaskMan but I am getting a reading of N/A under my Power (mA) field. I read on their site that this function is hardware compatability dependant. Strange since I got acbPower Monitor working once on first install (but not since)
I have just emailed the company for advice, but has anyone else had this program runing on a kaiser? im sure I read so, as there have been quite a lot of reports of people assessign battery drain with BT/Wifi enabled ect.
any other advice welcome, ta
Had them both, unfortunately same issue as you describe........no problem on my old P3600 though.....
@Menneisyys
I've been playing the flash-n-flash game with Dutty's and soon Q's ROMs.
With all of the discussion about battery life, screen stalls, etc, it got me remembering an old utility that I had once played with that would track such things.
It happens that it was acbPowerMeter
I went to their website, did some searching, found your great write-up on acbTaskMan from last March as well as this thread.
I have not yet downloaded/installed it but was curious about why it doesn't seem to be used by some of the ROM Chefs in their quests for the perfect ROM?
Hopefully this 'bump' will get a few folks who admittedly are MUCH smarter than I looking into it and finding a fix for the problems indicated above.
michi123 said:
Had them both, unfortunately same issue as you describe........no problem on my old P3600 though.....
Click to expand...
Click to collapse
Yup, it seems it's not possible to get the current on both the TI OMAP and Qualcomm platforms; only with Xscale and Samsung. Definitely bad news.
Sideburnt said:
I have just tried acbTaskMan but I am getting a reading of N/A under my Power (mA) field. I read on their site that this function is hardware compatability dependant. Strange since I got acbPower Monitor working once on first install (but not since)
Click to expand...
Click to collapse
Are you sure it DID show you an always-changing value? On TI OMAP, for example, it is constantly showing the same value, showing it's unable to meter the current.
Unforrtunately, in these cases, all you can do is
1. wiring a current meter between the battery and the battery slot (pretty hard to do)
2. running very long (can take days) tests to find out the battery usage of a given feature.
I've done the latter a lot with, for example, assessing the power usage of the BT unit on my TI OMAP-based Wizard. As I have several phones, I could just put it in a drawer for some days to have as dependable a result as possible.
What's weird about both acbTaskMan and acbPowerMeter is that if you have the Kaiser plugged in and charging then the software can correctly read and chart the current usage. When you then unplug the charger the software reports garbage.
Solution!
It won't work at all for me on my Kaiser, however HomeScreen++ works great for me.
http://www.chi-tai.info/cs_batterystatus_xda_neo_wm5_im_cs.htm#DownloadBeta
Unfortunately it doesn't have the graph like acb has. This means you have to switch back and forth to see the numbers when generating load in another application or game.
It does have some other cool statistics though.
Regards,
Sarel
I got my Diamond back from repair 4 days ago (my Wi-fi chip was dead and the cpu kept crashing) and it really works much better now.
The repair sheet says:
1 x Sub-assy to 82H, generic, Navi pre-assy w/ keycap
1 x ME Gasket, IP-RP797, Diamond
What strikes me as improvements is the following:
- when surfing using wi-fi, the phone runs MUCH cooler now
- wi-fi connection is extremely stable now (even in "best battery" mode)
- wi-fi range is vastly improved
- Battery lasts for 4.5 hours while surfing actively
- No more crashes so far (no soft resets necessary yet)
- It still gets hand-warm when using GPS navigation but my impression is that it is less bad than before.
I did some power measurements using Powerguard:
- Charging current using HTC cable on HTC power supply: 450-595 mA
- Charging current using HTC cable on laptop's USB: 235 mA
- Charging current using home-made USB cable on HTC power supply: 235 mA
(only + and - USB wires connected)
So it appears it makes a difference what kind of USB charging cable you use. A home-made cable that uses only the + and - wires gives you less than half the charging current than the original HTC cable (I assume it uses some additional wires to indicate a higher charging current is permissible). The reduced charging current has the positive side-effect of less heat being generated in the phone, so I now use my home-made cable for GPS car-navigation use.
Here are some power consumption measurements of my Diamond after repair:
- Power consumption when idle (screen on): 71 mA
- Power consumption while navigating using GPS: 266 mA
- Power consumption while surfing (using wi-fi, "best battery" mode
205, 165, 156, 86 mA (discrete steps, depending on cpu and wifi load, steps will only change in 30-s intervals)
Do you have music lag?
Zodler said:
Do you have music lag?
Click to expand...
Click to collapse
Sorry, what is music lag? Lagging behind what? Video?
Hey That sounds great^^ I should send mine to repair too ;-)
I had the same "cooling" effect after flashing another Radio... do u know what version is installed on your Diamond?
My experience after sending my Diamond back to repair is very similar to yours, as I said on this other thread.
http://forum.xda-developers.com/showthread.php?t=441762
I suspect that they are more careful about which phone they give you the second time, when you've been fussy enough about quality!
riri22 said:
I suspect that they are more careful about which phone they give you the second time, when you've been fussy enough about quality!
Click to expand...
Click to collapse
repair would be the same phone. as he has listed, just a couple of new bits.
Here:
http://forum.xda-developers.com/showthread.php?t=412065
mugglesquop said:
repair would be the same phone. as he has listed, just a couple of new bits.
Click to expand...
Click to collapse
No, in my case it is not the same phone. The IMEI has changed. they either changed the mother board and all the chips, or more probably, there are no parts from my previous phone. Even the battery doesn't look the same.
Therefore I suspect they chose carefully which phone they were giving me this time. Everything works better in the new phone: no more over-heat, the wifi is definitely working better, everything is faster and smoother.
ROM 1.93.404.1 NLD dated 07/10/08
Radio 1.00.25.05
protocol 52.29.25.12W
IMEI unchanged
Only tweaks I used:
- registry tweak to enhance touchscreen sensitivity
- registry tweak to disable screen blackout during call
- registry tweak to enable 4-column display in "programs"
In need to know the voltage across the diamond standard battery (900mAh) when the battery is fully charged and when the battery is fully discharged (the phone automatically switched off)
Could someone give me this information?
When my battery is low I read 3.2V
When my battery i high I read 4.1V
Is this correct?
That's about right, +-.1
Thanks, I've a lot of problems with the charging and discharging cicles, this information could help me to understand
While which is the charge current when the battery is fully discharged?
For my Diamond it can be very high, up to 800mA (I know it from BatteryStatus), it is a normal value?
wasm said:
While which is the charge current when the battery is fully discharged?
For my Diamond it can be very high, up to 800mA (I know it from BatteryStatus), it is a normal value?
Click to expand...
Click to collapse
Try a program, "PowerGuard", it's a very nice (and free) program developed by Muyz that will give you current and temp info, including graphs with a lot of flexibility in settings. You can get a good feel of where the current draws are. I think charge current is in the area of 700-800mA on initial charge.
Or another called Battlog. It,s better because it logs the measurements - on Powerguard it's difficult to see the actual (current, not in electrical, but in time sense ) measurement.
Thanks I'm going to try them
For now I'm testing Batlog...
This evening I'm going to make a full charging log, so I could post it tomorrow
Could you do the same? This could give me the possibility to compare them
I'm experimenting some problems with the charging circuit
mjaxa said:
Or another called Battlog. It,s better because it logs the measurements - on Powerguard it's difficult to see the actual (current, not in electrical, but in time sense ) measurement.
Click to expand...
Click to collapse
I agree with mjaxa, since your post I've found and installed Battlog. Works great on my Diamond. Very robust program and easy to read the log file or import into excel for analysis.
I have no idea why I didn't find this software when searching for a good battery monitor for my Diamond except I must have not used "log" in my searchs.
Thanx mjaxa.......
JRMX said:
Works great on my Diamond. Very robust program and easy to read the log file or import into excel for analysis.
Thanx mjaxa.......
Click to expand...
Click to collapse
I should, of course, also thank Palladium TD now that I've found the source for this fine program.
I'll also add that while the data logging is very good, I found that some of the functions do not work on my Diamond (US ROM 1.93). I know it's a beta program or maybe I just haven't figured it out yet. Using 0.2.3.130 beta I have noted:
No response on the help and other icon on the left side, battery temp read is off by a factor of 10 (noted on the Battlog thread) and cum use (mAh) does not display.
I'll post the comments on the correct thread.
In the following I reported the log of my battery charging cycle in txt and graphic format
If you can post comments or other logs, I'll appreciate
P.s. another bug in Battlog (I'think) is related to the sampling interval, as you can note observing the X axis on my plots: it is not constant in time
No one want help me with a charge/discharge log?
With the holidays I haven't had too much time to work with battlog and the phone use is not typical. I did run about 16 hrs of data and it does give some insight.
Charging overnight looked normal with current draw cycles at 2hr intervals for mail checks.
I was going to upload the excel file, but the format isn't permitted. The txt file is too large. I'll mess with it some more, but I didn't see anything that was unlike your data. 800ma on initial charges, -200ma on using various applications and phone calls, as much as -800ma on internet use and -9 to -20ma on locked standby. I did not see what I'm looking for which is an unexplainable deep discharge, overnight or during the day, I'll keep monitoring.
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.
General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
beache said:
General tips I can think of are:
Use black theme on display settings,
greenify doze setting using adb.
Any suggestions just post below.
Click to expand...
Click to collapse
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Craz Basics said:
I take it you mean non-root?
- Brightness!!!!
- Apps running in the background and preventing phone from sleeping permission; Downlaod Shizuku Manager and App Ops from the Play Store, run the script via adb and limit the apps you don't want to have those permissions. Instant messaging: Don't limit run in background
- Did I mention brightness!?!?
- I don't do this one, but don't charge your phone past 80%. This is more of a long term battery saver, as it will cause less damage to the battery. Also don't keep your phone plugged in overnight. (I don't leave mine in)
- Disable radios while not in use. I never use NFC or nearby device scanning, I turn those off. Wi-Fi and Bluetooth are never on while not in use. You'll get in the habit of turning them off it you start.
Click to expand...
Click to collapse
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Tips for better battery life.
And a lot of common sense.
tuncan said:
Tips for better battery life.
And a lot of common sense.
Click to expand...
Click to collapse
very helpful thanks
chewingum16 said:
very helpful thanks
Click to expand...
Click to collapse
Tnx. :good:
Zombie said:
Leaving the phone plugged in all night wont do any damage to the battery. Once charged the current to the battery is cut off except for when it needs trickle charging throughout the night, the power used by the phone will then come from the wall adapter. But if you dont want to charge your phone all of the way, then thats when you dont leave it plugged in all night unless you have a circuit to disconnect power at a certain battery percentage. Oh man that gives me an idea.
I should make a small circuit thats linked via bluetooth to an app, so pretty much a power adapter that you plug your phone into, but once you reach a certain percentage, the phone tells the adapter to cut power and only turn on to get it back up to that certain percentage.
Okay that was really side tracked.
Back to the post.
Like Craz said, brightness and radios.
If you are rooted, download KA or EXKM and underclock your cpu, thatll help out a bit, also if rooted you could try a custom kernel
Root:
Force Doze
Naptime
Greenify
Custom kernel
CPU underclock
Use tasker to limit cpu speed when screen off or in certain apps
Non Root:
Dark themes
Lower brightness
Make sure apps arent running in the background that use a lot of power
Disable location services
Disable radios unless in use (tasker helps especially with root)
If you plan to have your phone for over a year or two, then the charge limits, but capacity wont change much within the first few hundred cycles
Use Wifi as much as possible (cell uses more power)
Disable screen off gestures
Make sure doze and advanced optimizations are enabled
Click to expand...
Click to collapse
yes it will on many cases, but I can't tell with the OP5. Is the circuit will cut-off the battery from the phone to avoid drain? If yes, in that case, it won't hurt significantly the battery.
In general , what can hurt li based batteries : time, heat and numbers of time of electrons changing direction.
Having the phone plugged in, every X time the % will drop, and the charging circuit will trigger the battery.
As I said, can't tell how op5 is working, and it probably be minimal anyway. But technically it will reduce the capacity : http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
Heat : 20W charger, even if its a vooc, at one point the battery will get a high current load = heat, and chemical li-po arrangement changes.
Time : cant do nothing here, chemical arrangement will degrade, its a normal process for most battery, specially li based one.
But at the end, not much people would see any difference, since nowadays people changing their phone every 1-2 years, fck ridiculous...
Back to topic :
Pixel off apps , many of them on the play strore, can't tell which one is good or not.
Basically, it will turn off pixels on the screen.
https://play.google.com/store/apps/details?id=com.anrapps.pixelbatterysaver&hl=fr
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
dkryder said:
i find if i turn off the wifi always scanning feature and also turn off keep wifi on during sleep saves battery. actually i keep all wifi off unless i'm currently using it. as already mentioned, location services off, since i keep phone on all the time i get data through that. i've experienced battery times up to 6 days if calls in&out are 10 or lower each day and each call no more than 3 min, i'm a firm believer in hello, just facts, goodbye. i know people that live life via a phone find that strange but they will die of brain cancer not me. my neighbor is on phone no less than 7 hours a day just bullsh*tting and he talks real funny, i think his brain is rotting already. check to see which apps run all the time and kill those you do not need. as mentioned, lower screen brightness. 90% of the time mine is a couple clicks from as low as it can be and it is fine. i'd do the dark thing but it f*cks with my eyes. keep all apps closed you are not presently using instead of loaded in background.
Click to expand...
Click to collapse
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
shangxor said:
I can't really tell if you are joking about the brain cancer part or not. Some people might take you seriously
Click to expand...
Click to collapse
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
dkryder said:
oh, sorry about that.
https://www.jrselectrohealth.com/in...ween-1985-and-2015-in-the-u-k/?c=cf13ce20305c
Click to expand...
Click to collapse
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
[/COLOR]
shangxor said:
"While the new plots in themselves say nothing about any possible links between cell phones and brain tumors, they go a long way toward puncturing the argument offered by numerous public health officials and media outlets that such an association is highly unlikely because the overall incidence of brain tumors has remained relatively stable over the last number of years."
http://microwavenews.com/short-takes-archive/changing-mix-uk-bts
He had based part of his study on incorrect data also.
Click to expand...
Click to collapse
yes, i offered the link as a punchline to your comment about joking. however i do have a question about your comment,
"He had based part of his study on incorrect data also"
why didn't you include the part of the study and the incorrect data? because, when statement like this is made it is left to the reader to determine the part of the study and the incorrect data which may lead to misunderstandings.