GrapheneOS version 2025090800 released

abednego

GrapheneOS This one is my first post on this forum. Please understand I may be innacurate at best; I do not own a smartphone (I will consider buying a PIxel running GrapheneOS in the near future), only a Pixel tablet bought a week ago, running GrapheneOS, so I am not familiar to cellular technologies.

Just want to note that GrapheneOS release 2025090500 (a release that did not achieved the "Stable" status before being replaced by 2025090600) includes a cellular radio firmware update to the Android 16 QPR1 version. Either this firmware update, or the Google Messages app may be the source of current problems with RCS.

I would not rule out a problem on Google's side... other non-GrapheneOS groups are registering —since a week ago— complains from users of Android devices that have similar problems to the ones described here.

GrapheneOS

abednego People were reporting RCS issues from August 31st onwards which became more frequent since then. Look in the main RCS thread. It doesn't make sense to blame something occurring for many people since September 2nd on a September 8th release.

Syberkonda

Update: just got an indication on the messages beta that my device does not meet security requirements for RCS. This is a Google issue and it's probably intentional.

Pocketstar

x-pve Your tablet is brand new, therefore a battery defect is more unlikely... (Not impossible) However, the dock is suposed to charge slowly (in my experience) while a 25-30W adapter charges alot faster, perhaps it "crawls" slowly to a 100% while docked? (Especially the latter percentages it takes its time to prevent heat)
It does heat up the battery less prominently through the dock however, which is a good thing.
Perhaps you can test out if it reaches 100% by turning it completely off and let it charge on a USB adapter, just give it some time to charge, batteries can be a bit quirky sometimes.
Sadly, this is as far as my knowledge on batteries go, perhaps anyone else has an idea?
And did you turn off charge optimisation under battery settings? (Which limits the charge to 80%, which can be a good thing for your battery on the long run)

x-pve

Pocketstar It's buggy, dock and usb too (I've high power charger and FNIRSI FNB58 USB monitor). It doesn't charge to 100 %, doesn't matter if "Optimize to 80 % is turned on or off. Unpredictable.
It worked perfectly on 2025081400, after upgrade to 20250908 it's broken.
We should move to this https://discuss.grapheneos.org/d/26371-battery-optimized-charging-not-working-anymore thread and stop spamming here

GrapheneOS

x-pve The tablet limits charging to 90% in the dock. The 80% charge limit requires going to 100% for a while in order to calibrate itself. Charge it with a regular charger and leave it on that for a while and the 80% limit will kick in again. It's the same behavior as the stock OS with Android 16, although maybe they've improved it with Android 16 QPR1.

Pocketstar

GrapheneOS Ah, that explains it well, thanks!
I rarely use the dock myself, but have battery optimization enabled, and sometimes I turn it off completely and will then charge to 100% when I need the full charge.

x-pve

GrapheneOS Thanks, I followed your instruction, charged to 100% using regular charger. Then I turned on charging optimization. It worked well till reboot. Now the battery is charged and maintained at 90% (tablet in dock). ?

abednego

GrapheneOS I suppose most people here only noticed the RCS failure after september 8th because RCS messages do not arrive in a predictable pattern; in any case, this one looks more like a global "RCS outage" than a GrapheneOS-specific bug — as I read more and more generic Android forums, it seems something went wrong on Google's side in the last weeks.

I hope that now that Amit Mehta —a FISA court judge— has ruled that Google does not need to sell the Android and Chrome divisions, everything will return to the way it was before.

23Sha-ger

My battery also went to 100% charge instead of the usual 80%. Didn't notice it until now since I usually postpone updates until a few days since release.

AtmosphericIgnition

No problem with any of my use cases or connectivity.

GrapheneOS

abednego RCS is having problems in general seemingly due to a shift to relying on carriers more instead of only a Google service but it impacts GrapheneOS users more.

abednego

GrapheneOS Found your thread about these issues on Mastodon. Very informative reading!

Panda-na

x-pve If the phone is plugged in at reboot, it continues to charge past the limit. Then it needs a new calibration. So for next time, don't reboot with it plugged in if it has stopped on the charge limit.

x-pve

Panda-na Charged to 100 % using usb high power charger (9V), discharged to about 50%, put in the dock, charging optimization enabled. Charged by dock to 90%, again :-(

phone-company

Same with original Google devives .... Since last Update

« Previous Page