83
Follow up on the Pixel 8 Pro battery life post from a couple of weeks ago (lemmy.ca)
submitted 1 year ago by to c/android@lemmy.world
25 comments fedilink hide all child comments
 

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.

all 26 comments

sorted by: hot top controversial new old
[+] 86 points 1 year ago (9 children)
[deleted]
  • permalink
  • fedilink
  • source
  • hideshow 9 child comments
    •
  • [–] 62 points 1 year ago (7 children)

    Can't. Too busy blocking side loading.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 29 points 1 year ago (6 children)

    Installing apps*

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 6 points 1 year ago (5 children)

    Yeah we shut change the terminology for what it is. Installing apps, just like you do with a computer.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 year ago (4 children)

    I mean..... That command is "adb sideload"

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 1 year ago* (2 children)

    "adb install path_to_apk" you mean?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago* (1 child)

    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".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 1 year ago

    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.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 14 points 1 year ago (11 children)

    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!

  • permalink
  • fedilink
  • source
  • hideshow 11 child comments
    •
  • [–] 7 points 1 year ago (10 children)

    I had to search for it using the search function, it wasn't in the same place as the other screenshot that was posted

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 5 points 1 year ago (9 children)

    Just did the latest GrapheneOS update and still dont see it - maybe it's only in stock Android?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 5 points 1 year ago (6 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 5 points 1 year ago (2 children)

    Charging limit is a far better implementation as it prevents the rapid aging in the first place

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 1 year ago (2 children)

    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%).

    1000035026

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • [–] [S] 1 point 1 year ago*

    Reactivated the Battety health assistance setting and we're back to 91% capacity:

  • permalink
  • fedilink
  • source
    •
    [–] [S] 1 point 1 year ago

    Another full charge session clocks at 96%.

  • permalink
  • fedilink
  • source
    •
    [–] 0 points 1 year ago (1 child)

    Then yesterday I found this curious setting, after updating to Android 16 QPR1:

    Would you kindly post that image in the comments section? It just display a blank area for me.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •