GrapheneOS version 2026030500 released

GrapheneOS

GrapheneOS version 2026030500 released:

https://grapheneos.org/releases#2026030500

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

Murcielago

rename geocoder options to "GrapheneOS server" and "OpenStreetMaps server" since we're now self-hosting Nominatim instead of providing a proxy to the OpenStreetMaps instance

Awesome, thanks for your hard work on improving GOS with every update.

xxx

Network location: GrapheneOS Apple proxy
Geocoder: GrapheneOS server
SUPL: GrapheneOS proxy
PSDS: GrapheneOS server

Phew.
Kudos for/to the team.

amilia

Finally 1.4 Vulkan driver on P10, thank you

forgottennick

After the update, my rear camera stopped working. It shows me a message "Could not detect rear camera. Please try again later." Am I the only one with this problem? My device is Pixel 8.

User19375792037474

forgottennick same thing, same device model. Flashlight doesn't work either, in quick tiles it says that camera is in use, although I don't think that's really the case.

GrapheneOS

forgottennick User19375792037474 It's a known issue for the regular Pixel 8 and will be resolved in the next release. We cancelled the current release due to the issues for the Pixel 10 Pro Fold and regular Pixel 8.

MSX2GOS

Pix 9a

All good including camera and torch

Sindbad

Is the new Pixel 10 graphic drivers included that was released with official Android 16 QPR3 by Google for Stock PixelOS?

Johnnyloans

0xdnote channel "stable" it still lists version 2026030200

Every channel lists this version, even alpha. These announcements means it'll be in at least alpha. It takes days to reach stable.

The patch was cancelled due to some issues.

GrapheneOS We cancelled the current release due to the issues for the Pixel 10 Pro Fold and regular Pixel 8.

anruen

Pixel 9 Pro, everything works fine

AgentJ

On original pixel fold, having serious issues with Samsung health app immediately following the update. Background processes keep failing over and over again, leading to new notifications every two seconds and warnings that the application was failing continuously every five minutes until I disabled the app. Opening the app itself worked, but content was syncing with servers or wearable slowly, if at all,and didn't preclude failure of background processes. Crash log below:
`type: crash
osVersion: google/felix/felix:16/BP4A.260205.001/2026030201:user/release-keys
package: com.sec.android.app.shealth:6311013, targetSdk 36
process: com.sec.android.app.shealth:remote
processUptime: 2491 + 579 ms
installer: com.android.vending

com.google.android.gms.common.api.ApiException: 8:
at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus(Unknown Source:14)
at com.google.android.gms.common.api.internal.TaskUtil.setResultOrApiException(SourceFile:4)
at com.google.android.gms.common.api.internal.TaskUtil.setResultOrApiException(SourceFile:1)
at com.google.android.gms.internal.health_tracking_eap.zzco.onResult(Unknown Source:7)
at com.google.android.gms.common.api.internal.IStatusCallback$Stub.zaa(Unknown Source:14)
at com.google.android.gms.internal.base.zab.onTransact(Unknown Source:20)
at android.os.Binder.execTransactInternal(Binder.java:1522)
at android.os.Binder.execTransact(Binder.java:1457)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [q0v{Cancelling}@28a749c, ST-W] `

Johnnyloans

AgentJ serious issues with Samsung health app

gms.common.api.ApiException: 8

Review this thread
https://discuss.grapheneos.org/d/32750-samsung-health-constantly-crashing/2

AgentJ

Johnnyloans thank you

AtmosphericIgnition

No issues on P8P. Both geocoding options seem to work as expected.

0xdnote

The new version is not available for me yet (7th of March).
"Device is up-to-date." (About Phone/Build number: 2026030201)

On the releases page I can see 2026030500 listed, but under device for channel "stable" it still lists version 2026030200 for the Pixel 9a.

Some people above report no issues with the update. But on the releases page all devices are still on the stable 2026030200 version. Not sure how to proceed to get the update. I'll try a reboot.