Hi everyone !
I haven't seen this info anywhere on XDA, at least on this forum, but i think everyone should know this.
Not trying to take credit in any way, because OP made a terrific job at researching and testing, just wanna spread the knowledge.
Basically : Charging your phone at night or leaving it charging even while at 100% for a few hours will have a big impact on how it behaves and how your battery holds up.
Quick explaination : Since Nougat, you don't get the App Optimization screen anymore on the first boot.
That's because Google has delayed it, and it triggers only in specific conditions : When the device is idle, fully charged, and still plugged in.
This optimzation allows to build the ART cache, which speeds up the system and apps, saving CPU power because it avoids using the JIT (Just In Time) compiler, thus, saving battery juice.
This also means wiping cache isn't going to help with your battery life, quite the opposite.
You'll see he made a test with other users, and the results are quite clear.
Here is a link to the post with detailled explaination and testing, thanks a lot to anupritaisno1 for all this info :
https://forums.oneplus.com/threads/...-and-battery-calibration-myths-busted.993896/
Forced the building through "cmd package bg-dexopt job" on my own OP6 running Pixel Experience, took like 15mn. SOT improved quite a lot.
Interesting read, thanks
What if you charge it at night while the phone is OFF?
Thank you for sharing this :laugh:
---------- Post added at 11:42 PM ---------- Previous post was at 11:41 PM ----------
SOCOM-HERO said:
What if you charge it at night while the phone is OFF?
Click to expand...
Click to collapse
Read the thread linked in OP.
The system works harder when you charge your phone while it's off.
Very interesting read. Basically debunks majority of the stuff people preach to maximize phone performance and battery.
SOCOM-HERO said:
What if you charge it at night while the phone is OFF?
Click to expand...
Click to collapse
If the phone is OFF it can't trigger the optimization task, this won't be beneficial.
In the article he actually made a test about this, you should read it !
Interesting, but... who claimed that clearing the cache helps with the *battery*?
Also, what happened to the old adage "never leave your phone plugged in" because it causes battery wear?
krakout said:
Interesting, but... who claimed that clearing the cache helps with the *battery*?
Also, what happened to the old adage "never leave your phone plugged in" because it causes battery wear?
Click to expand...
Click to collapse
A lot of people claim this, that you should clear the cache after an update, without clear reason why. At least we have a reason not to.
And this old adage is indeed old, like the "Fully discharge it for calibration". We're not in 2002 anymore. Modern technology had the nice idea to remember to stop the charge, and use Lithium batteries haha !
Leaving it plugged at 100% is not causing any wear. The post mentions a response from an electrical engineer, saying the battery is in fact on stand by and the phone is running off the charger only.
krakout said:
Also, what happened to the old adage "never leave your phone plugged in" because it causes battery wear?
Click to expand...
Click to collapse
Debunked here
Totone56 said:
A lot of people claim this, that you should clear the cache after an update, without clear reason why. At least we have a reason not to.
And this old adage is indeed old, like the "Fully discharge it for calibration". We're not in 2002 anymore. Modern technology had the nice idea to remember to stop the charge, and use Lithium batteries haha !
Leaving it plugged at 100% is not causing any wear. The post mentions a response from an electrical engineer, saying the battery is in fact on stand by and the phone is running off the charger only.
Click to expand...
Click to collapse
That's just one way to read it. Leaving it plugged in does not, indeed, mean that it keeps trying to charge. But once it goes down, it will charge up again. Also, supposedly, the fuller the battery is when charging, the higher the temperature and hence, the wear. Cannot attest to that, that's just how the argument goes.
casual_kikoo said:
Debunked here
Click to expand...
Click to collapse
Yes, but that's irrelevant. Totally different issue, I was not talking about calibration.
krakout said:
That's just one way to read it. Leaving it plugged in does not, indeed, mean that it keeps trying to charge. But once it goes down, it will charge up again. Also, supposedly, the fuller the battery is when charging, the higher the temperature and hence, the wear. Cannot attest to that, that's just how the argument goes.
Click to expand...
Click to collapse
Indeed. But from the looks of it, and what i've read in other places, it waits for it to drop a bit. If the battery is not used, it won't fall to 99% in a night, and won't be charged again until you unplug it. Kinda like when your phone is off. It's gonna be a long time before the battery goes down on it's own.
Interesting, gotta try it.
Still, does the <50, >70% not apply in terms of battery wear? I mean, even for straight-forward charges?
krakout said:
Interesting, gotta try it.
Still, does the <50, >70% not apply in terms of battery wear? I mean, even for straight-forward charges?
Click to expand...
Click to collapse
I'd say yes, it still applies. It's a different topic ! Everithing said here is related to software and charging control, when this is more related to battery chemistry. But you're right, it's still true.
To sum it up :
- Charging above 70 or 80% and discharging under 30% (Thoses are the values i read about) is indeed not the best thing for your battery health on the long term.
- BUT, the superior battery life your phone will get with these app optimizations easily counter-balances it. If the phones lasts twice longer, it means 2 times less chaging cycles required, when you think about it (Ofc not accurate, but you see what i mean)
Best thing you can do, if you really want to get the best of both worlds, is staying in between those ideal values, and triggering the optimization manually via the Linux Terminal Emulator
Although, i don't think i'm not personally going to bother, i'll just charge my phone, use it, and charge it again in the evening.
Two days after triggering dexopt manually, without flashing or changing anything, using the phone the same way, i went from 16h idle/2h SOT at the end of the day with 50% remaining to 20h idle/2h15 of SOT with 70% remaining, that's quite a drastic improvement.
Ooh can you share more?I tried googling about triggering the optimization but came up empty...
Yes, that's logic in that, if optimization is so dramatic!
PS I meant 80, not 70, just as you mentioned.
Sent from my ONEPLUS A6000 using Tapatalk
krakout said:
Ooh can you share more?I tried googling about triggering the optimization but came up empty...
Yes, that's logic in that, if optimization is so dramatic!
PS I meant 80, not 70, just as you mentioned.
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Yes, it's hard to get an info about this, wierd.
Run any terminal app on you phone, type "su" to ask for root permission, then enter "cmd package bg-dexopt-job" (without quotes).
It will run for a certain amount of time (between 10mn and more than an hour, depending of the number of apps you have installed).
When you get the shell back (A line appears under the last one to enter another command), it means it's complete.
If you wanna be sure, run it again, it will finish very fast, because the cache will be up to date (It still checks it, so it's not an instant completion).
Do it plugged in the charger, but with like 30% charge, maybe on USB so it doesn't get to 100% too fast, to avoid the awkward situation where it overlaps with the actual automatic background process doing the same thing haha
The phone can heat up a bit because the CPU is working quite a bit.
You can also run the command through an ADB shell on a PC, if you're not rooted.
Or just leave it charging during a night for once, works too
Best way seems to let if charge for the night regularly though (Quote from the OP) :
"I just say overnight because the device being idle is a condition for the optimisation to begin
Also the optimisation is profile guided. If you were to AOT compile your entire base system it would take 4-5 GB off your storage and that is just the base system we haven't even considered the apps you'll install. Since optimisation generates huge optimisation files it is more sensible to only compile what is slow for JIT to do at runtime. This might seem weird but it takes the cache size down to less than 1 GB on most devices
In other words every time you use your phone the runtime sees what is slow and queues it up for optimisation the next time the condition is satisfied"
Wow. This should be pinned somewhere!
I'll do it in the terminal just for fun, but will also leave it (for my first time ever) overnight too.
Thanks, man!
Sent from my ONEPLUS A6000 using Tapatalk
krakout said:
Wow. This should be pinned somewhere!
I'll do it in the terminal just for fun, but will also leave it (for my first time ever) overnight too.
Thanks, man!
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
I think everyone should read this yes, even if it's just for the sake of knowing how things really work.
And i can confirm again, my battery life is so much better ...
A few days ago, going to work, listenting to Spotify on my motorcycle for 20mn, and checking my mails for 2m got me to 96% battery.
Yesterday, and today, same routine, an an hour after that i'm still at 100% ... That's very impressive.
Really interesting.
Sadly the command does nothing on my device.
Sent from my OnePlus6 using XDA Labs
Stroky said:
Really interesting.
Sadly the command does nothing on my device.
Sent from my OnePlus6 using XDA Labs
Click to expand...
Click to collapse
Are you sure ? It doesn't display anything, that's true. But you'll know it's over when the shell returns.
Or you can juste leave your phone plugged for a night or two, same result.
My battery goes from 100% to ~97% within minutes without using it after unplugging the phone from the charger when charging overnight.
Why is that and how can I get rid of it? It occurs since a few days on custom rom as well as on oos now again.
Related
In several threads I've seen it recommended that you charge to 100% before flashing your phone. Are there any facts behind this or is it just voodoo?
What's the reasoning behind it?
Thanks,
-Brett.
Dont Die
If you phone dies whilst flashing it becomes a nice shiny brick! You can try and fix it but it wont be easy.
If you're at 100% there is little chance of the phone turning off.
zzoinks said:
In several threads I've seen it recommended that you charge to 100% before flashing your phone. Are there any facts behind this or is it just voodoo?
What's the reasoning behind it?
Thanks,
-Brett.
Click to expand...
Click to collapse
CustomRUU will not start when your battery is under 50%.
When your battery is over 50% loaded you can flash safely.
There is no reason why it should be fully loaded.
i would suggest it being more than the required 50%.. flashing a phone takes alot out of the battery....
I think I phrased my original question wrong: I understand that sufficient charge is needed for the actual act of flashing.... however, I've seen it suggested that having a 100% charge has positive effects even after the flash. i.e., it somehow makes your phone perform better post-flash.
Any truth to this?
Thanks for the replies so far!
-Brett.
Sounds like voodoo to me. You're not polishing a car, you're putting bits of information in places. It's either there, or not there.
zzoinks said:
I think I phrased my original question wrong: I understand that sufficient charge is needed for the actual act of flashing.... however, I've seen it suggested that having a 100% charge has positive effects even after the flash. i.e., it somehow makes your phone perform better post-flash.
Any truth to this?
Click to expand...
Click to collapse
No, it's not truth.
zzoinks said:
I think I phrased my original question wrong: I understand that sufficient charge is needed for the actual act of flashing.... however, I've seen it suggested that having a 100% charge has positive effects even after the flash. i.e., it somehow makes your phone perform better post-flash.
Any truth to this?
Thanks for the replies so far!
-Brett.
Click to expand...
Click to collapse
I have flashed ALOT of units in my PDA days.. never bricked a unit.
They have been from 50-100% in charge.
Used both card and USB flash.
No difference noticed.
Carlis.
I do not see any scientific fact in the 100% thing never done in my 1000+ flashes
zzoinks said:
Are there any facts behind this or is it just voodoo?
Click to expand...
Click to collapse
It's just voodoo. The point is just to be sure that you have enough power to prevent the phone from shutting down because that will crab it up and good.
If you look at the number of complete idiots here that simply cannot be bothered to read what are often very very simple instructions, it makes sense to make your point as simple as possible without a bunch of caveats.
'Nuff said.
Not just voodoo
I'll admit that I, personally, have not given much thought to this nor have I thoroughly tested it, but the reasons I've come to understand for fully charging your battery before flashing is to ensure that you get completely accurate battery readings post flash. It has nothing to do with the required 50% to flash. That is requirement is just as it sounds. 50%. I've never had a problem with my battery meter when I didn't flash at 100%, but I can see the logic in the claim
Not totally voodoo.
Having the battery at 100% seems to work better for the calibration of the battery indicator. After a Hard Reset it seems that the OS expects the battery to be at 100% and if it isn't you can get some interesting effects such as the battery charge dropping 40% in five minutes, or reading 100% until it's nearly dead. After a while this behavior sort of settles down but why put up with it if you don't have to?
I take reports of unusually fast battery drains with a grain of salt -- more often than not it's a charge calibration issue or an unusally active/buggy radio ROM that's the culprit.
Mind you, this isn't technically a flashing issue. You could probably flash at 50% battery and then charge it up before you do your first Hard Reset. Of course, if any of you are like me you want to play with a new ROM right away, so I rarely do this.
rob.ocelot said:
Not totally voodoo.
Having the battery at 100% seems to work better for the calibration of the battery indicator. After a Hard Reset it seems that the OS expects the battery to be at 100% and if it isn't you can get some interesting effects such as the battery charge dropping 40% in five minutes, or reading 100% until it's nearly dead. After a while this behavior sort of settles down but why put up with it if you don't have to?
Click to expand...
Click to collapse
I always flash on what ever battery i have left. If i have under 50% and something hot is out, i just wait until the 50% is there and flash... Havent noticed anything like above...
I probably never had the full 100%...
hey im a noob here so im sorry if this has been asked before but right now i upgraded my phone to ics and the battery life is horrible and im too cheap to get a battery extender so is there anything i can do to improve it or am i just going to have to deal with it?
Get your phone to 100% battery and then just play whatever you like until it completely dies. Then, plug it in to charge and dont touch it until it gets back up to 100%. That is supposed to increase the battery lasting time by 20%. It only works once...so dont do it 5 times hoping for results. This is supposed to be done when you first get the phone, but if its never been you've never done it, its worth the shot.
Sent from my SGH-T959V using xda app-developers app
rygtuu said:
hey im a noob here so im sorry if this has been asked before but right now i upgraded my phone to ics and the battery life is horrible and im too cheap to get a battery extender so is there anything i can do to improve it or am i just going to have to deal with it?
Click to expand...
Click to collapse
Let the ROM 'soak' in. It'll get better. You are probably busy messing with it figuring out all the features which is normal and makes the battery seem terrible. But overall it is pretty good.
And the post above is an old wives tale these days. It's funny to read people still recommending it.
lumin30 said:
Let the ROM 'soak' in. It'll get better. You are probably busy messing with it figuring out all the features which is normal and makes the battery seem terrible. But overall it is pretty good.
And the post above is an old wives tale these days. It's funny to read people still recommending it.
Click to expand...
Click to collapse
Kinda, when you first flash with a factory reset, you don't have a battery stats file. This is another good reason to flash when your battery is 100% charged. When Senior Members here say "soak in", they are saying that the first boot all of the system apk (application packages) are cached to /cache. Doing too much while these apps are being cached screws up the statistics of the battery stats. If I really want good battery life, I totally wipe, and let the phone sit for 10-15 minutes. I leave usb plugged in till it's 100%, then pull the usb and use the phone until it totally dies.
By this time, the day is over and it needs to be charged anyways. I plug it into the charger before bed and let it charge up all the way with nothing running (no wifi, no bt, no background apps running).
After that charge, battery life seems soo much better. ymmv. it would be good to know if that works for you too.
Otherwise, everyone uses their phone differently, and some people install stupid apps that have intensive background services running that eat batteries, then complain about the rom sucking instead of introspecting about how they use their phone.
bhundven said:
Kinda, when you first flash with a factory reset, you don't have a battery stats file. This is another good reason to flash when your battery is 100% charged. When Senior Members here say "soak in", they are saying that the first boot all of the system apk (application packages) are cached to /cache. Doing too much while these apps are being cached screws up the statistics of the battery stats.
Click to expand...
Click to collapse
Just to clarify - battery stats file have nothing to do with battery performance and the battery stat file "is reset every time you unplug from power with a relatively full charge (thus why the battery usage UI data resets at that point)." Google Engineer Dianne Hackborn
ahh ok thanks guys ill do what you guys said and see if it helps
you can also install one of the battery saver apps on the market, like juice defender or similar. They will typically help and some can control how often background services are allowed to collect data.
mike-y said:
you can also install one of the battery saver apps on the market, like juice defender or similar. They will typically help and some can control how often background services are allowed to collect data.
Click to expand...
Click to collapse
These arent as helpful as they use to be. I have seen and challenged people to run with and without and the added battery life is either very minimal or actually worse with these apps.
Battery saver apps where created when android was very young and had bad management of the battery power. The way it works now it should lower the power to the radios low enough to save battery but not completely shut off the radios. Shutting them off will actually harm battery life because it takes so much more power to turn them on and off repeatedly then to let them idle.
no i think it was more designed for froyo and gb because if you try those battery savers in froyo or gb you can see it works and battery last long but if you test it in ics or jb (i have test juice defender with jb in the sgs3) and what i can see its that sometimes it lags (not always just when you like two or three apps open which for me in the sgs3 was weird) and data sometimes hangs i mean it doesn't load pages
Sent from my SGH-T959V using Tapatalk 2
Download Gemini from the play store and manage the autorun for apps. That's what I do and it saves quite a bit of battery
Sent from my SGH-T959V using xda app-developers app
solrac1212 said:
no i think it was more designed for froyo and gb because if you try those battery savers in froyo or gb you can see it works and battery last long but if you test it in ics or jb (i have test juice defender with jb in the sgs3) and what i can see its that sometimes it lags (not always just when you like two or three apps open which for me in the sgs3 was weird) and data sometimes hangs i mean it doesn't load pages
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
Ill agree with you on froyo but gingerbread towards the end was much better.
The biggest thing is people dont realize how much power is used to start and stop things. Letting them idle will use battery but not nearly as much if you start and stop many times a day. Now at night if you want to turn off those things then yeah go for it. But if you are a frequent phone checker then starting and stopping them everytime will chew through the battery.
A good example is this, its summertime go outside and look at your electric meter when the ac first turns on. It will spin reeal fast for a minute or so while the system gets everything going then it will slow down. This same thing applies to your phone and its radios. Each time you shut it off it has to go through a process so you dont get corrupted data. And when you turn it on it has to use a lot of battery to make sure things dont get messed up and get to the proper operating form.
So any app that shuts off the radios manually and such will end up costing you battery if you are a power user.
If you can follow the steps exactly as i wrote them, then install the team FAH-Q kernel found in the dev section...
Sent from my SGH-I727 using xda app-developers app
thomas.raines said:
If you can follow the steps exactly as i wrote them, then install the team FAH-Q kernel found in the dev section...
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I put FAH-Q kernal on AOKP and it seemed to help a bit. I was using systempanel and it said facebook was sucking cpu at night while the phone was resting... so i took off facebook for the moment to see if any other apps/processes could be causing a drain.
side note:
I spend 15-20 min in the morning going through stuff on my phone. Then I will listen to music in the car on my way to work 35 min. My phone will be at 80% by the time i walk in to work. I check things during the work day once and a while and by 2pm I will be around 40%. leaving work I will have 35-30% .... ok i'll just quit now and say running 12hrs i will have about 15% left. I think I am an average phone user. not sure how much everyone else uses theirs.
justiz33 said:
I put FAH-Q kernal on AOKP and it seemed to help a bit. I was using systempanel and it said facebook was sucking cpu at night while the phone was resting... so i took off facebook for the moment to see if any other apps/processes could be causing a drain.
side note:
I spend 15-20 min in the morning going through stuff on my phone. Then I will listen to music in the car on my way to work 35 min. My phone will be at 80% by the time i walk in to work. I check things during the work day once and a while and by 2pm I will be around 40%. leaving work I will have 35-30% .... ok i'll just quit now and say running 12hrs i will have about 15% left. I think I am an average phone user. not sure how much everyone else uses theirs.
Click to expand...
Click to collapse
Music soaks up a lot of battery as well as display, data, and sync. You can try turning off sync and data when you don't need them. But it sounds like you are doing better. I am still concerned with what else you have running in the background though... however, 12-16 hours isn't bad at all...
Sent from my SGH-I727 using xda app-developers app
bhundven said:
.... If I really want good battery life, I totally wipe, and let the phone sit for 10-15 minutes. I leave usb plugged in till it's 100%, then pull the usb and use the phone until it totally dies.
Click to expand...
Click to collapse
What do you mean by totally wipe? do you mean go into recovery to wipe data, cache, and davlik cache? then restore after the battery is fully charged?
HKSpeed said:
What do you mean by totally wipe? do you mean go into recovery to wipe data, cache, and davlik cache? then restore after the battery is fully charged?
Click to expand...
Click to collapse
Yes, as well as /system/ and at least .android_secure on your microSD
I would recommend against fully discharging your battery as a matter of course. While this might have been useful in the days of NiCads, deep discharges and heat are the Kryptonite of LiIon batteries.
Rooted -- Calkulin's Stock "Battery Saver" ROM -- Xposed Framework -- a few mods from XBlast Tools running.
First off, a Root Explorer search for com.android.systemui returned nothing.
What is com.android.systemui? I don't think I saw this in my usage until a couple of days ago.
Why does 31 seconds of CPU and 1 second of keep awake = almost TRIPLE the battery use of 12 minutes of screen-on time?????
moseso said:
Rooted -- Calkulin's Stock "Battery Saver" ROM -- Xposed Framework -- a few mods from XBlast Tools running.
First off, a Root Explorer search for com.android.systemui returned nothing.
What is com.android.systemui? I don't think I saw this in my usage until a couple of days ago.
Why does 31 seconds of CPU and 1 second of keep awake = almost TRIPLE the battery use of 12 minutes of screen-on time?????
Click to expand...
Click to collapse
It's the actual System User Interface. So most likely a combination of the rom and xposed are causing this. Also, dirty flashes of ROMs can cause this.
If you installed a new xposed module and noticed a battery drain the uninstall that module. Otherwise remove other xposed modules. You could always try a frew full wipe in recovery as well.
I have had this issue with mostly with dirty flashing which is my queue to do a clean flash. It's also possible if you restored any apps with data, like from Titanium Backup, could potentially cause this as well.
moseso said:
Rooted -- Calkulin's Stock "Battery Saver" ROM
Click to expand...
Click to collapse
you got caught up in a lie, with buzzwords that are pushing for you to use the rom. theres no such thing as a battery saving rom. all those scripts/mods being used in the rom are just buzzwords. battery life is all dependent on how you personally use your device, how you set up your device, and your data/phone signal quality. a rom will not save you battery.
Thanks for the help, Tom. A visit to recovery to wipe caches and fix permissions and a reboot caused this -->
simms -- I do understand that. I am not really disappointed in my battery life -- and it doesn't seem to have changed much in the week that I've had the phone. But the reporting of it had, and that sort of alarmed me...
moseso said:
Thanks for the help, Tom. A visit to recovery to wipe caches and fix permissions and a reboot caused this -->
simms -- I do understand that. I am not really disappointed in my battery life -- and it doesn't seem to have changed much in the week that I've had the phone. But the reporting of it had, and that sort of alarmed me...
Click to expand...
Click to collapse
wow, your android system is high, even though only 10% battery was used. a reboot might fix that though. you might have to go through your settings and setup again, disable stuff like google location reporting/history(it wont disable your location).
simms22 said:
wow, your android system is high, even though only 10% battery was used. a reboot might fix that though. you might have to go through your settings and setup again, disable stuff like google location reporting/history(it wont disable your location).
Click to expand...
Click to collapse
I'm beginning to think the issue I'm having is in the reporting -- not actually a battery use problem. I've only had the phone a week, so my data base is small, but I haven't really seen bad battery life nor any real change in it. Even with some use and a bunch of time fiddling with the mods and stuff, I've yet to go to bed with less than 50% left. Mostly, more...
Here's the latest pics. com.android.systemui is back on top in the overview with 36% The detail page shows 39% and a whole 2 seconds of CPU. That just CAN'T be right...
moseso said:
I'm beginning to think the issue I'm having is in the reporting -- not actually a battery use problem. I've only had the phone a week, so my data base is small, but I haven't really seen bad battery life nor any real change in it. Even with some use and a bunch of time fiddling with the mods and stuff, I've yet to go to bed with less than 50% left. Mostly, more...
Here's the latest pics. com.android.systemui is back on top in the overview with 36% The detail page shows 39% and a whole 2 seconds of CPU. That just CAN'T be right...
Click to expand...
Click to collapse
Can u show the battery graph? And also why is your bluetooth on every time.
varuntis1993 said:
Can u show the battery graph? And also why is your bluetooth on every time.
Click to expand...
Click to collapse
Which battery graph? You mean the current usage graph I showed in the OP, from Battery Monitor Widget?
Re Bluetooth: I just leave it on, so when I step in the car it just connects to the car. No muss, no fuss, no bother.
I suppose I could try turning it off and see how much battery I save. I know with my previous phone (EVO4G) the point at which I started leaving the bluetooth on all the time didn't change my battery life to any noticeable extent.
Here's battery monitor widget current use. The EVO idled at 70 - 95 ma. This one does seem to draw a lot more at idle. I don't know what's "normal."
moseso said:
Which battery graph? You mean the current usage graph I showed in the OP, from Battery Monitor Widget?
Re Bluetooth: I just leave it on, so when I step in the car it just connects to the car. No muss, no fuss, no bother.
I suppose I could try turning it off and see how much battery I save. I know with my previous phone (EVO4G) the point at which I started leaving the bluetooth on all the time didn't change my battery life to any noticeable extent.
Here's battery monitor widget current use. The EVO idled at 70 - 95 ma. This one does seem to draw a lot more at idle. I don't know what's "normal."
Click to expand...
Click to collapse
Stock battery app like this
varuntis1993 said:
Stock battery app like this
Click to expand...
Click to collapse
Not very interesting. It keeps resetting, every time I plug in to USB to transfer the screenshots to my mac for posting here. I'm not leaving it plugged in very long -- I just move the pics and unplug it. I unplugged it this morning at 7:30 AM. It's now almost seven hours later and I'm at 93%. That ain't bad. It's a gradual descent -- no big drops like the one in your post.
moseso said:
Not very interesting. It keeps resetting, every time I plug in to USB to transfer the screenshots to my mac for posting here. I'm not leaving it plugged in very long -- I just move the pics and unplug it. I unplugged it this morning at 7:30 AM. It's now almost seven hours later and I'm at 93%. That ain't bad. It's a gradual descent -- no big drops like the one in your post.
Click to expand...
Click to collapse
Mine stats those are from my nexus 7 2013, Sot of around 4 and still 55% battery left.
I just showed u for sample. A simple restart should fix as simms told
I m on stock rom with x blast tool never happened with me....u can try to use ur phone in safe mode and see...I know its a system app but u can give a try with bluetooth off. Or flash a diff rom and see
If your phone is vibrating a lot and you have extra UI elements installed this seems normal.
When you only use a small percentage of the full battery smaller drains appear large.
Bit off topic, but have you thought of using WiFi to move your files over? No messing with the wire and you could even automate the task.
Sent from my Nexus 5 using Tapatalk
bblzd said:
Bit off topic, but have you thought of using WiFi to move your files over? No messing with the wire and you could even automate the task.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the push. Found a nifty WiFi file transfer app this morning. Boy, is that slick!
I'm not too sure how to go about this, but when I try to charge my nexus 5, regardless of the cable or charger i use, it won't charge faster than 1a unless I blow into the micro USB port hard, and I'm not sure if it's dust, because if I unplug it and plug it back in again it will go back down to 1a charging, when i blow into it, it can charge as high as 1700mAh...
Sorry for the noob question, it's my first post.
What are you using to determine the mAh?
N00TN00T said:
I'm not too sure how to go about this, but when I try to charge my nexus 5, regardless of the cable or charger i use, it won't charge faster than 1a unless I blow into the micro USB port hard, and I'm not sure if it's dust, because if I unplug it and plug it back in again it will go back down to 1a charging, when i blow into it, it can charge as high as 1700mAh...
Sorry for the noob question, it's my first post.
Click to expand...
Click to collapse
Lethargy said:
What are you using to determine the mAh?
Click to expand...
Click to collapse
He's just going through throttling which is normal. My phone does the same when battery is higher than 80%. My phone charges at 1.7A from 0-80% then 1A to 90%, then 0.6A to 100%. It's all pre dictated by the onboard battery chip
topgeardave said:
He's just going through throttling which is normal. My phone does the same when battery is higher than 80%. My phone charges at 1.7A from 0-80% then 1A to 90%, then 0.6A to 100%. It's all pre dictated by the onboard battery chip
Click to expand...
Click to collapse
Yeah, or that. But if he's measuring the mAh from within Android its kinda inaccurate too anyways.
Lethargy said:
Yeah, or that. But if he's measuring the mAh from within Android its kinda inaccurate too anyways.
Click to expand...
Click to collapse
Yeah true, I find the estimation by current widget to be alright for general current usage when comparing chargers. As long as the battery doesn't take several hours to charge, there's no need to be concerned
It was below 80%, and i realize that current estimates aren't 100% accurate but I don't think they would be 600mah different to the original...
I'm using battery monitor widget, I'll post screenshots when my battery drops to about 70%.
I'm not sure if my micro USB port is faulty or maybe it's just dusty, even though it doesn't look dusty, does anyone else have this same issue?
Lethargy said:
What are you using to determine the mAh?
Click to expand...
Click to collapse
I'm using battery monitor widget, but it shouldn't vary so much just by blowing into the charging port, should it?
Here's before and after blowing into it, I'm using the nexus charging accessory from the play store with a 1.8a output.
I know exactly what you're going through, OP. This technique was the only way I could Legend of Zelda to work.
Sent from my iPhone 6 using Tapatalk
_MetalHead_ said:
I know exactly what you're going through, OP. This technique was the only way I could Legend of Zelda to work.
Sent from my iPhone 6 using Tapatalk
Click to expand...
Click to collapse
Haha, which fittingly has been described by Nintendo to be a placebo effect. If you just took the cartridge out and placed it back in, apparently that had the same chance of working.
I think the same can be said for this situation.
OP, mA current as reported by Android jumps all over the place. I could take a screenshot of it showing 1600mA, 1000mA and 600mA all within 20 seconds of each other. The only thing that you can do to try and prove this is happening (which I seriously doubt) is to use a log to plot the charging level over time. Even then the results could be skewed by whatever the phone happens to be doing during that time.
bblzd said:
Haha, which fittingly has been described by Nintendo to be a placebo effect. If you just took the cartridge out and placed it back in, apparently that had the same chance of working.
I think the same can be said for this situation.
OP, mA current as reported by Android jumps all over the place. I could take a screenshot of it showing 1600mA, 1000mA and 600mA all within 20 seconds of each other. The only thing that you can do to try and prove this is happening (which I seriously doubt) is to use a log to plot the charging level over time. Even then the results could be skewed by whatever the phone happens to be doing during that time.
Click to expand...
Click to collapse
No that's not it, it does junp a little but never that much for me, it might be a problem with your charger if you're getting that...
Changed the rom and kernel and the problem was solved, i still can't explain it but meh, I'm happy with it now, if only I could do something about battery life now...
You can only do so much with 2300mah in such a high powered device...
N00TN00T said:
No that's not it, it does junp a little but never that much for me, it might be a problem with your charger if you're getting that...
Changed the rom and kernel and the problem was solved, i still can't explain it but meh, I'm happy with it now, if only I could do something about battery life now...
You can only do so much with 2300mah in such a high powered device...
Click to expand...
Click to collapse
This was with the stock 1.2A charger. It's actually just my phone's usage constantly changing that causes the spikes, if logs were able to update more than once per second it would be jumping even more as I'm able to see with manual refresh. This happens during charging, full load and idle situations but your issue might have had something to do with the USB fast charge settings in certain ROMs.
I find the 2300mAh battery can be pushed surprisingly far, depending on your usage. If you're willing to sacrifice certain settings it can make things easier. This is on stock and unrooted, 20% brightness. I disabled Locations, Auto Syncs only allowed periodically at preset times, and used apps that are fairly battery efficient.
That was mostly WiFi, but this was with more mobile usage. Two work days on a weak 3G signal, 40% brightness using mostly Hangouts, Feedly, and 2 hours of video. Check out the [Battery Life Help] thread for more tips.
That's pretty impressive, i usually get about 3 hours SoT, with a bit under an hour phone calls usually and occasional snapchat, usually just internet browsing, underclocked to 1.7 and i almost half an hour SoT improvement without any loss to performance, cause i don't use my phone for gaming...
bblzd said:
This was with the stock 1.2A charger. It's actually just my phone's usage constantly changing that causes the spikes, if logs were able to update more than once per second it would be jumping even more as I'm able to see with manual refresh. This happens during charging, full load and idle situations but your issue might have had something to do with the USB fast charge settings in certain ROMs.
I find the 2300mAh battery can be pushed surprisingly far, depending on your usage. If you're willing to sacrifice certain settings it can make things easier. This is on stock and unrooted, 20% brightness. I disabled Locations, Auto Syncs only allowed periodically at preset times, and used apps that are fairly battery efficient.
That was mostly WiFi, but this was with more mobile usage. Two work days on a weak 3G signal, 40% brightness using mostly Hangouts, Feedly, and 2 hours of video. Check out the [Battery Life Help] thread for more tips.
Click to expand...
Click to collapse
Hi guys,
as we are approaching nearly 1.5 years since the Pixel 5 was released, I am curious what everyone's Battery Health is.
You can use Accubattery.
BatteryGuru also has it included in their app.
It will take a few charges to get an accurate reading.
I take pretty good care of my battery, by never going below 20% and only gone about 80% maybe 10 times.
I just got Accubattery on my device so I will update where I am in a little bit.
Well since I feel itt'll take a good 4-5 charges before any type of "accurate" measurement is shown, I decided to do a full charge and I'm very happy, I feel like this is at least 90% the capacity still. Right now BatteryGuru is showing 70% but I expect it to *hopefully* go up, since accubattery is showing 85%, but this is only after 1 charge.
Running Android 11 crDroid v7.15
I did 1 full charge (35% => 100%) with AccuBattery, says my battery health is 93% (3 718 mAh / 4 000).
Not bad I guess, for a 16 month old phone which I used to charge regardless to "efficiency rules".
I used stock rom, and rooted couple of months ago. And only recently switched to lineageos 18.1 and elementalx kernel so I can't tell if there's a difference.
I'll take a look at crDroid, but I can't help installing some google stock apps - force of habits.
If I see any significative change after some charging cycles I'll give an update.
Btw are you using a custom kernel?
AnyNameYouWish said:
I did 1 full charge (35% => 100%) with AccuBattery, says my battery health is 93% (3 718 mAh / 4 000).
Not bad I guess, for a 16 month old phone which I used to charge regardless to "efficiency rules".
I used stock rom, and rooted couple of months ago. And only recently switched to lineageos 18.1 and elementalx kernel so I can't tell if there's a difference.
I'll take a look at crDroid, but I can't help installing some google stock apps - force of habits.
If I see any significative change after some charging cycles I'll give an update.
Btw are you using a custom kernel?
Click to expand...
Click to collapse
Thanks for posting my friend! That's a great starting point, I hope that it only gets better for you!
I'll upload images from what accubattery and batteryguru are currently showing, now that I have a few charges completed. I hope to see a higher health.. but it could always be worse. I remember my htc 10 bring at like 70% at this point in it's ownership.. though Android wasn't as up-to-date with battery adaptivities.
I used to use ElementalX but since lack of updates for Android 11 I've been pretty happy with crDroid stock kernel. (Though I have used the last update that was out and it ran quite nicely before I moved fully to crDroid. So I may give it a go and see what type of battery I am getting compared to crDroid stock).
CrDroid also comes with PixelGapps installed, which I personally love. So you'll get Pixel launcher, Camera and other Google apps/goodies .
I am not a very patient man, and a few minutes reading about this rom convinced me to try it asap !
Love it so far, I really like the stock experience with easy tweaks possibilities - I also already shared my gratitude and first issues in the main thread
I'll keep stock kernel for a few weeks and share accubattery and batteryguru screenshots here, before giving a try to elementalx kernel and see if there's a difference
This is all stock with root and some modules installed. I received my device in November of the year it was released
elong7681 said:
This is all stock with root and some modules installed. I received my device in November of the year it was released
Click to expand...
Click to collapse
Dang! That's awesome health! You do anything special?
Mine is down to 87% for some reason.
andybones said:
Dang! That's awesome health! You do anything special?
Mine is down to 87% for some reason.
Click to expand...
Click to collapse
Just kept my battery charged between 80% to 20%
90% here. Have the phone almost since launch and accubattery since then. Don't follow the 80% rule too much. I use to follow it religiously but then read a comment somewhere that by following it, you are at 80% health effectively so... it made sense.
ribogushter said:
90% here. Have the phone almost since launch and accubattery since then. Don't follow the 80% rule too much. I use to follow it religiously but then read a comment somewhere that by following it, you are at 80% health effectively so... it made sense.
Click to expand...
Click to collapse
So after few weeks I'm 90% on Accubattery and 85% on Batteryguru. I did noticed the stats were pulled down when I charged only to 80%, so I would tend to agree...
andybones said:
I used to use ElementalX but since lack of updates for Android 11 I've been pretty happy with crDroid stock kernel. (Though I have used the last update that was out and it ran quite nicely before I moved fully to crDroid. So I may give it a go and see what type of battery I am getting compared to crDroid stock).
Click to expand...
Click to collapse
I installed ElementalX a couple of days ago, I've let it just as it is out of the box, no personnal settings. It seems to be very efficient with battery usage but maybe too much because I don't receive whatsapp calling notifications anymore, only "missed call" once it's too late... gonna take a look on the official topic to check it out.
AnyNameYouWish said:
So after few weeks I'm 90% on Accubattery and 85% on Batteryguru. I did noticed the stats were pulled down when I charged only to 80%, so I would tend to agree...
I installed ElementalX a couple of days ago, I've let it just as it is out of the box, no personnal settings. It seems to be very efficient with battery usage but maybe too much because I don't receive whatsapp calling notifications anymore, only "missed call" once it's too late... gonna take a look on the official topic to check it out.
Click to expand...
Click to collapse
Thanks for posting!
I am at 90% myself actually, and noticed it actually went up from 88% to 90% when I charged it over 80% to 85%.
So maybe with all the new changes and upgrades to batteries, etc, charging to 100% is just fine?
I think it is the charging overnight for more than 8 hours can possibly be harmful.
I think I'll start charging to 90%.
Maybe try adding whatapp to battery optimization, is you haven't already to see if you start getting the notifications.
andybones said:
So maybe with all the new changes and upgrades to batteries, etc, charging to 100% is just fine?
I think it is the charging overnight for more than 8 hours can possibly be harmful.
I think I'll start charging to 90%.
Maybe try adding whatapp to battery optimization, is you haven't already to see if you start getting the notifications.
Click to expand...
Click to collapse
Already tried that but thanks for suggestion
About battery, I'm far from being an expert but I think it's still good to charge up to a lower lever eg. 80-90%, in order to preserve battery health and loose less capacity at each cycle. However, in order to properly measure the battery's performance, you'll have to give it a full charge or the stats will be inaccurate, as @ribogushter mentionned.
I would suggest, wipe your Accubattery and/or Batteryguru stats and give your phone a full charge from 20 to 100% and see if it impacts your health score
AnyNameYouWish said:
Already tried that but thanks for suggestion
About battery, I'm far from being an expert but I think it's still good to charge up to a lower lever eg. 80-90%, in order to preserve battery health and loose less capacity at each cycle. However, in order to properly measure the battery's performance, you'll have to give it a full charge or the stats will be inaccurate, as @ribogushter mentionned.
I would suggest, wipe your Accubattery and/or Batteryguru stats and give your phone a full charge from 20 to 100% and see if it impacts your health score
Click to expand...
Click to collapse
Darn sorry, wish I knew what else for you to try.
I think I will keep my stats in accubattery as it gets better with time, but I will charge it to 100% and see if it drops, goes up, or just stays the same at 90% health.
Edit: both accubattery and battery guru dropped a bit after charging to 100%.. down from 90% to 88% accubattery, and 89% to 86% battery guru.
I think I will probably do 90% from here-after though, I still think charging all the way to 100% all the time isn't the best, but I really don't know anymore!
I'd like to read more about getting the only 80%, I mean it's just common sense that you get actually only 60% if you run from 80%-20%, but that is charge capacity, not battery health capacity.
I do wish Google/Android had some documentation on this. Even cApple at least has a battery capacity built into its settings, and I saw they have a setting that tells if say the screen was replaced was it done using official cApple products, very good idea actually.
Also how has ElementalX been running?
I decided to flash it and see how it compares to the stock kernel in crDroid_v7.17 (Android 11)
I always loved it when I used it, but it is a little out-dated, (over a year now) but I think it's still fine.
Proton kernel is also really good.
andybones said:
Darn sorry, wish I knew what else for you to try.
Click to expand...
Click to collapse
I think it was becase I enabled data saving, and since I put Whatsapp on the exception list the problem seems to be solved. Once again, the problem was between the chair and the screen ^^
andybones said:
I think I will keep my stats in accubattery as it gets better with time, but I will charge it to 100% and see if it drops, goes up, or just stays the same at 90% health.
Edit: both accubattery and battery guru dropped a bit after charging to 100%.. down from 90% to 88% accubattery, and 89% to 86% battery guru.
I think I will probably do 90% from here-after though, I still think charging all the way to 100% all the time isn't the best, but I really don't know anymore!
Click to expand...
Click to collapse
As you said, we probably never will have a 100% effective method to quantify battery health until it's native to Android ¯\_(ツ)_/¯
andybones said:
Also how has ElementalX been running?
I decided to flash it and see how it compares to the stock kernel in crDroid_v7.17 (Android 11)
I always loved it when I used it, but it is a little out-dated, (over a year now) but I think it's still fine.
Proton kernel is also really good.
Click to expand...
Click to collapse
Really smooth, I'm not experiencing any lags or freeze, or any problem so far and battery life seems to have improved. As a pure rookie, I don't understand what would make a given kernel different or better than the other, so I tried the one that seemed to be the most popular but I noticed only afterward that it hadn't been updated for a while and that the developer is focusing on his apps (he mentioned it on some thread).
Proton kernel's latest update is also almost 1y old, I'll stick with ElementalX until next update or give a try to CleanSlate which seems to be the most active.
Btw, I guess you're using ACC? If so, which charging switch are you using?
Best way to measure your battery is to charge it with an USB tester such as UM24 or UM25 . You can see how much mAH your battery can absorb and calculate the health . Phone needs to be turned off and charged with a regular charger, not fast-charger .
I'm looking for a good benchmark for the battery , i tried Geekbench4 , PC Mark ..do you any other good ones ?
Not that I think it helps I am always on my PC and just charge through the usb-c.
charges pretty fast too, like 45 min.
I may invest into UM24 orUM 25, thanks @arcadekidflo
If you only use usb-c to usb-c you can get TC-66c , from the same company . If you also use regular chargers you can get UM-25c .
AnyNameYouWish said:
I think it was becase I enabled data saving, and since I put Whatsapp on the exception list the problem seems to be solved. Once again, the problem was between the chair and the screen ^^
As you said, we probably never will have a 100% effective method to quantify battery health until it's native to Android ¯\_(ツ)_/¯
Really smooth, I'm not experiencing any lags or freeze, or any problem so far and battery life seems to have improved. As a pure rookie, I don't understand what would make a given kernel different or better than the other, so I tried the one that seemed to be the most popular but I noticed only afterward that it hadn't been updated for a while and that the developer is focusing on his apps (he mentioned it on some thread).
Proton kernel's latest update is also almost 1y old, I'll stick with ElementalX until next update or give a try to CleanSlate which seems to be the most active.
Btw, I guess you're using ACC? If so, which charging switch are you using?
Click to expand...
Click to collapse
I accidentally charged to 100% again, and health went up in accubattery.
Maybe I will start fully charging..
Oh yea. One thing that helped for me for late notifications is to turn off "Adaptive Notifications"
-- It's been working for me.
some ROMs (such as crDroid) it turns it back back on after every reboot.
I just make a shortcut on my homescreen using Activity Launcher
arcadekidflo said:
If you only use usb-c to usb-c you can get TC-66c , from the same company . If you also use regular chargers you can get UM-25c .
Click to expand...
Click to collapse
Many thanks my friend! Very much appreciated.
Mine looks like it's around 94% - ordered it on release day, so about 1.5 years old now.
I've not followed the 20% - 80% rule, most of the time just letting the phone charge fully over night.
Maybe the 20% - 80% doesn't really make any difference?
IMO it's pretty silly to only use a portion of your battery's indicated capacity. The nature of lithium ion batteries is such that both over and undercharging can cause damage, so manufacturers don't actually use 100%, or even 80%, of their full voltage potential. The battery circuitry itself, as well as the phone's power monitor, do a sufficient job of limiting charge and discharge, so its really not necessary to do it yourself. Use your phone as you normally would, but be aware that keeping it charged all the time may reduce battery life.