GrapheneOS version 2026092500 released

GrapheneOS

GrapheneOS version 2026092500 released:

https://grapheneos.org/releases#2026092500

See the linked release notes for a summary of the improvements over the previous release.

VAULT

Installing now... will advise of any issues :]

P10P XL

VAULT

Pocketstar

2026092501 is working nicely on my P6a, P7, Pixel Tablet and P9Pxl. Another great update! Thank you!
I have not tested cellular nor Play Services.

Novaliss

P6a, cell and Sandboxed Google Play, no apparent anomalies.

GoSaM

Installing alpha on daily driver 9PF now. Guess my last comment in this thread 😘

FreeFrags22

All works fine but I have a question. Will a prompt that shows every time when I turn on mobile data be disabled or I'll have option to turn off this prompt like on stock Android? Probably it's in AOSP code.

Novaliss

FreeFrags22 prompt that shows every time when I turn on mobile data

This prompt? https://ibb.co/zj3nDbL
I don't think this could be disabled.

Momud

Novaliss I think Android 17 QPR1 added a way to disable it, so we will probably get it when GrapheneOS will be based off Android 17 QPR2.

FreeFrags22

Novaliss
Yes, it can be disabled on stock Android from 17 QPR1.

Momud
Why in QPR2 if it's available in QPR1?

wizoatk

FreeFrags22 Why in QPR2 if it's available in QPR1?

Google no longer releases public source for QPR1 or QPR3.

envelope

Pixel 8 on 2026092500 couldn't join 5 GHz AP. OpenWrt 25.12.5 (MediaTek MT7981, WPA3 and WPA2/WPA3 mixed, 802.11r on, RSN overriding on). Phone just reports "wrong password", but it worked on 2026091900.

I triaged it with an LLM and was able to resolve the issue. Turning 802.11r off on the AP (ieee80211r '0') fixed it. RSN overriding is still on. Looks like Google issue 536585787: the Android 17 QPR1 Wi‑Fi stack picks FT‑SAE, the driver runs plain SAE, and the phone aborts association after SAE succeed. I can provide dmesg logs from my AP if GOS devs would be willing to fix this upstream issue themselves.

Emmy

Apparently there's an issue with unlock pattern or PIN not being recognised on stock OS:

https://www.androidauthority.com/google-pixel-september-2026-pattern-pin-unlock-bug-3715425/

Would GrapheneOS be affected by this, too?

iyanmv

I notice my Pixel 8 a bit slower slower with 2026092500 than with 2026091900. For now, I cannot give objetive numbers, just a feeling while using the phone. Anyone else?

Stewart

iyanmv I thought it was just me, but yes, I can confirm that the phone has become really slow since installing the latest update – it’s almost unusable.
I’m actually on a Pixel 10a.

MSR

Stewart interesting, my 10PXL is like before. I dont feel any difference

Stewart

MSR I get the impression that the slowness issue mainly affects the other profiles.
In the owner profile (I don’t have any apps installed), I don’t have any slowness issues; however, on my main profile (where all my apps are installed), using the phone is unbearable – it’s extremely slow.
That’s all I’ve noticed so far; we’d need feedback from other people to confirm this – it’s practically unusable.

Stewart

The problem may also stem from other services such as Play Services; I haven’t installed it on my secondary account but on my main one – we’ll have to see.

Novaliss

Stewart we’d need feedback from other people to confirm this –

To confirm what?

Stewart

Novaliss Whether the problem is down to the different profiles, Play Services or something else.
My phone is running really slowly.

iyanmv

I would not say "unusable", it's mostly the animations lagging a bit (e.g., when opening/closing the keyboard), changing tabs in the browser, etc. But yeah, the feeling is that it became slower after the update. This is on the main profile with Google Services installed. But I can notice the issue also in a secondary profile withour Google and almost no apps. Happy to provide more logs, or test possible solutions.