user It's a new bug, probably upstream. Some discussions is here https://discuss.grapheneos.org/d/26285-grapheneos-version-2025090800-released Even if you allow the 100% calibration it will reset at the next reboot.
flomuc user Let's see how things turn out, after I tried to charge it to 100%. If it is a bug, hopefully it will get sorted out soon.
flomuc I charged it to 100% and then let it drop to 30% and then charged it again. Unfortunatly the situation is unchanged. It gives me a warning that the 80% threshold has been reached but keeps charging anyway. Until recently the charging icon would change and indicate that it stopped charing. The charging level would then never go above 80%. So to me this looks like it has to be another problem. as "user" indicated.
whiskeywalrus flomuc Did you take it off the charge when it hit 100%? You need to leave it charging at 100% for at least the time until it's 99%, but maybe even until it's 79% (if the 99% doesn't resolve it). Edit: Apparently the shield icon disappears once the calibration is complete and you can detach the charger?
floracapsule Here's what I did and it's been working ever since. Charged to 100. Disconnected from charger. Toggled charging optimization off. Rebooted. Toggled charging optimization on. Plugged in charger. Shield showed up. Unplugged and went about my day.
flomuc floracapsule floracapsule in the end, this did the trick. I had the one charged at 100% and let it continue to charge for 30 minutes but the shield-icon would not appear. I then did as you described. Now, the shield icon is back.
starglider This is definitely an upstream bug. See https://piunikaweb.com/2025/09/08/google-pixel-charge-limit-bug-september-update/ and https://www.reddit.com/r/GooglePixel/comments/1ne5sre/ever_since_the_recent_update_the_phone_recharges/ and https://www.reddit.com/r/GooglePixel/comments/1naooj3/80_limit_not_working/ and https://www.reddit.com/r/GooglePixel/comments/1n9xj4l/having_issues_with_80_charge_limit_after/ https://www.reddit.com/r/GooglePixel/comments/1n9xj4l/having_issues_with_80_charge_limit_after/ All of that within just the last few days. GOS devs probably can't do much about this, and I'm sure debugging this AOSP code isn't a priority for them. Android generally just seems like a total mess right now. They already had to remove some pixel AI features because of performance, and it seems just chaotic. IMHO, the reason they haven't pushed QPR1 to AOSP yet has more to do with bugs and general disorganization than anything too nefarious. They might just be embarassed to have the code out there right now, or there were a bunch of ugly hacky workarounds to get things working on the Pixel 10s by release time. Unfortunately, I think we all just need to wait for Google to get through release season and get their act together.
Watermelon starglider Thank you for this. Before the recent firmware updates that GrapheneOS delivered us, I tried to find anyone online that mentions how calibration was broken in the past three months or so. Even some of the links you posted only mention the breakage after the recent updates and no word about the breakage before them.
floracapsule flomuc I am glad to hear it worked for you. There are a few threads about this issue. I took someone else's solution and condensed it down so it would be simpler to understand. I have rebooted and had a software update since fixing the issue and I haven't had to repeat the process.
KitsuneNoBaka Watermelon there was thread about battery have no calibration routine for 3 months - but it was closed when calibrating always bug was introduced
Watermelon KitsuneNoBaka Yes I was tracking those threads too. But I meant anyone not using GrapheneOS. Random reports on the web. I found nothing
nervousball can confirm have the same issue. was working fine, unticked optimisation settings to charge till 100% as i was travelling. now everytime i charge it doesnt stop at 80 but charges all the way to 100% on every single charge
thure It seems that not only GrapheneOS is affected, but also stock OS. Therefore, it may well be an upstream bug, and we will probably have to wait until Google has fixed it and published the sources for it.