Battery Percentage Issue After Full Charge

taranarat

Novalissoide its happened everyday since the update

Novalissoide

And if you just use the phone for several hours, it stays at 100%? Have you tested, say, six hours?

taranarat

Yes, percentage stays stuck at 100% until I restart device and then it jumps down to the appropriate percentage of battery.

Also yes, tried multiple different lengths of time to test it. 2hour, 6hours, 8hour, etc....Each time the same issue occurs.

I've literally just unplugged my device from charging overnight.
I'll let you know how it goes over the next few hours.

Novalissoide

taranarat yes, we'll see if there's any other users experiencing this, else it must be in your phone. 🤔

taranarat

Novalissoide Well 1 hour in now and battery percentage has reduced appropriately to device usage.

Did some web browsing and streamed a 10minute video to test it, battery reduced to 96%

One thing I did do before device use, was change the USB-C port settings. Changed it to "off" then back to "charging only". Then used device as mentioned in above paragraph.

Perhaps the USB-C port settings has a minor bug that holds the percentage at 100% ??
And perhaps just changing the USB-C port settings kind of 'resets' that bug ??

Watermelon

taranarat Perhaps the USB-C port settings has a minor bug that holds the percentage at 100% ??
And perhaps just changing the USB-C port settings kind of 'resets' that bug ??

I was about to suggest you to save a system log when the bug is occurring before rebooting, so you could send it to the devs. But now that it's solved, unless you can trigger the bug again, they might not be able to fix it for the next time it occurs to you or other people.

Novalissoide

taranarat yes, it seems like the toggling made the change, but I'm putting a tiny open possibility that it was unrelated, just to not lock this single observation in.

taranarat

Watermelon That was going to be my next question; please point me in the direction on how to submit this to the devs?

I saved two system logs on 18Nov
And save one system log on 19Nov.
I'll save another system log right after this, 20Nov.

Watermelon

taranarat A system log from a time the bug is not occurring would probably not be useful to them. They're very large logs, so it could be wasting their time. I suggest you to try to replicate the issue first, and save the system log before you reboot.

Note that system logs are potentially sensitive! You want to send them privately, delete the sent copy once they've received it (e.g. deleting the message on Matrix/Telegram, deleting the copy of your email message from the sent mail folder, etc), and you might want to avoid sending them by email. You can optionally use age to encrypt the file to the GrapheneOS team.

One way is they have a dedicated email address for this: logs@grapheneos.org
Another way is by privately contacting them on Matrix/Telegram/etc.
https://grapheneos.org/contact

taranarat

Novalissoide I completely agree with you!
It could be something else I did on the device without even knowing or realizing that I did it.

I simply mention toggling of the settings it as it was the only 'intentional' change I made in the device settings - and with that sharing my observations.
I'm by no means a developer or have knowledge of the deeper technicalities on how pixel devices with gOS operate & function.

I appreciate your help with this, I never would have thought to toggle the setting if I wasn't chatting with you about it😁👍

Novalissoide

taranarat lovely!

taranarat

Watermelon
Excellent, thank you so much for providing the information.
Noted, about the system logs👍
If the issue can be replicated, I'll follow through on your advice and send the logs via the appropriate avenue.