GrapheneOS version 2025092700 released

nandohyphen1

GrapheneOS ErnestThornhill thanks. So it is quite a process to test the new releases. Really really like the OS, and the different release channels is a nice feature because anyone who wants to can test the release - not just devs. Thanks for all the work that goes into this project! :)

monogram

@GrapheneOS

nandohyphen1 Changes since the 2025092500 release: • add SystemUI and Settings integration for detecting and notifying Pixel 6a users with batteries impacted by the fire hazard issue resulting in capacity and charging being throttled along with directing users to the support options for getting a free battery replacement, $150 credit or $100 cash as compensation for the faulty battery.

Hi, did you already manage to add a toggle for disabling it?

GrapheneOS

monogram No, we don't have a toggle for disabling it. We strongly recommend replacing the battery if you have one of the ones impacted by this regardless of whether we end up adding a toggle.

patienttruth99

Nice work! Your work with RCS is much appreciated.

EndoPlant

Thank you for the fix!

ron

So RCS is basically a privacy nightmare because Google Messages is getting the device identifiers?

phone-company

ron just read again :)

patienttruth99

ron RCS is basically a service by Google. Unfortunately it's the most widely adopted cross platform communication tool after SMS. RCS is presumably more private and secure as it's end to end encrypted in most cases. I personally would prefer RCS to not be run by Google, but it's still the case. You're certainly welcome to only use SMS.

Until we get wider adoption of Signal, this is my primary short message platform with most others, so I'm stoked on the attention the team put into the fix.

GrapheneOS

ron There can theoretically be other RCS apps but RCS is largely a set of Google services even if you use another app. It's a lot less of a privacy nightmare than SMS/MMS between Google Messages and itself due to end-to-end encryption support. When you send SMS/MMS messages, multiple carriers and other get access to those along with them being archived for future access.

GrapheneOS

patienttruth99 iOS doesn't have end-to-end encryption support for RCS yet but will be adding it via the new MLS RCS standard and it will be interoperable with Google Messages.

HIghQualityH2o

Who would prefer to maintain use of SMS with carrier logging content vs E2EE routing with meta data capture by Google and why one vs the other? Which do you prefer in the "trade-off" and why?

de0u

HIghQualityH2o Who would prefer to maintain use of SMS with carrier logging content vs E2EE routing with meta data capture by Google and why one vs the other?

I can imagine that some people who have convinced most of their contacts to switch to a more-secure messaging system, such as Signal (which is not particularly tracked by Google) might be ok with having a few low-importance SMS messages (including their content) known to their carrier (who already knows where they are all the time) versus disclosing more information to Google.

Evoke0512

If we previously got RCS to work by using adb to enable device identifiers for GMS package should we now go back in via adb and deny access for that instead of allow before updating to this new release?

userx04197321065

Evoke0512
I'm wondering the same thing. Did you ever find out?

Pocketstar

Thanks! Awesome work! (-:
2025092701 works well on the P7, Pixel Tablet and P9Pxl thus far.
So far 2025092700 works well on the P6a.
No Play Services nor cellular connection have been tested.

abednego

2025092701 works fine on the Pixel Tablet, as others noted before on this thread.

faxe

2025092701 working fine on Pixel 6

neotux

Two device got updated to 2025092701. 8Pro and 6a.

While 8Pro seems to be working fine so far, I have the Setting app crashing on me on 6a. It happens when I tap the "Safety & Emergency" tab.

Should I post the crash report here or open a new topic?

GrapheneOS

neotux You can post the crash report here.

neotux

GrapheneOS

I am so sorry for making noise. And I feel a bit ashamed remembering that it was my own doing.
Now I realize the reason for the recommendation from advanced users here that one should never mess around with system apps. Lesson learnt.

I/We have had but smooth and nice experience with GrapheneOS and updates, even Alphas, for which we are grateful to all of you working so hard on this project. Unfortunately, I don't find an edit button to edit my previous post to add that this was caused by me and not by the update to the system.

metalsped

OK so if I download the referenced Alpha release, should it work again, or do I need to essentially remove the tethered # info from my account and 'start over'?

« Previous Page Next Page »