So I have an update to my post from a couple of weeks ago. I did a few full charging sessions and they all showed estimated capacity around 4700mAh:
Then yesterday I found this curious setting, after updating to Android 16 QPR1:
I turned it off, did a full charge session and I got this estimate:
And that result looks to be right back to the normal cycle degradation line:
I’ll do a few more full charge sessions but we have a tentative culprit. Google seems to have introduced a battery capacity cap under this setting, presumably to extend the cycle life of the battery.
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It’s fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
deleted by creator
Can’t. Too busy blocking side loading.
Installing apps*
Yeah we shut change the terminology for what it is. Installing apps, just like you do with a computer.
I mean… That command is “adb sideload”
Or just installing an apk directly from a file manager. I haven’t installed an application with
adb sideload
since… Shit I don’t even remember. Been using Android since 2010.“adb install path_to_apk” you mean?
Both are valid commands.
adb install is for individual apk files.
adb sideload is for compressed zip files to load images and system files that usually include apps.
But yes, I did conflate the two and forgot the command syntax.
Either way, I don’t fully understand the hate for the word “sideload”. I don’t find it has a negative implication, but I can see how some other people might.
Installing apps from Aurora, F-Droid, etc. are not “sideloading”, though, and that does bug me how people conflate the two like the Play Store is the only valid way of installing apps on your phone. If you’re installing them from within an environment on your phone, it shouldn’t be called that. Only when you’re loading apps from a PC via adb should it be called “sideloading”.
You know what sideloading is, masses do not. It’s easy to generate negative connotation with a word that has less context.
Everyone knows what install means to them already, and no one hates sideloading as a word. It’s about fighting a disinformation war and trying to get you to join in, just without explaning it.
Can recommend Fairphone for exactly this.
Another full charge session clocks at 96%.
Thanks for doing the research on this! Not seeing that setting on my device yet, but I might need a newer build of 16 or something. Good info to know!
I had to search for it using the search function, it wasn’t in the same place as the other screenshot that was posted
Just did the latest GrapheneOS update and still dont see it - maybe it’s only in stock Android?
Graphene has had a better version of this for ages
Nice, going to flip that switch
I bet it’s not on grapheneOS. I saw a couple posts surrounding GOS where people were complaining about the feature, so I’m wondering if they removed it in favor of allowing you to set a charging limit like we had before this feature was added.
Unfortunately the only pixel I have GOS on is my pixel 6 pro, so I can’t be of more assistance.
Charging limit is a far better implementation as it prevents the rapid aging in the first place
100% agree! I try to keep the 20/80 rule for all of my devices. Lately, however, my 8 pro has felt extra bad with battery, so I’m hoping disabling this battery health assistance feature will help.
I’ve almost factory reset my phone a couple of times too, hopefully this is the missing link.
I only used 22% on my 8 pro battery today, how old is your 8 pro? Maybe something stopping the phone sleeping? I have noticed one of my Bluetooth devices stops the phone sleeping
Wait, did Android 16 QPR 1 remove the charging limit for newer Pixels? My 7a has both the Battery health assistance option and the original optimization modes (off, adaptive charging and 80%).
It’s still there in there latest Android 16 builds
Right, but the commenter above me seems to suggest that GrapheneOS removed the battery management in order to bring the charging limit back, which is why I asked.
Would you kindly post that image in the comments section? It just display a blank area for me.
But basically search for “battery health assistance” and you should find it.