GrapheneOS version 2026062300 released

BurningMoreThanWords

DohnJoe will spawn the "legacy" keypad.

There's an issue already open for it.

userofgos

jonasdoe do you have the Lift to check phone gesture enabled in Settings > System > Gestures > Lift to check phone? And also Tap to check phone

That makes it bearable for me on my P8a, hardly any inconvenience/delay.

John634

Hi, thank you for the update. There has been an issue with contact scopes after the update. An app (WhatsApp) is no longer adding/removing contacts according to changes in contact scope.

I've tried resyncing in phone settings accounts, in WhatsApp contact refresh, it gives an error (please try again later) due to contact scopes. If I give full contacts permission, then it sync correctly.

Hat

fid03 This is already noted here (actually in bold text): https://grapheneos.org/faq#vpn-support

It's good that it was added last year. I was still referring to the "For Now" forum post. Of course, I can look for updates on GitHub for GrapheneOS.org, but it's not very practical to rely on commits.

I think "recommended" settings will vary according to each person's needs / threat model

I have nothing against "threat modeling" even if it is not my point.

I read the whole website four years ago and have only reread specific sections since then. My idea behind "basic but important setting recommendations" even though I may not have expressed it well, was a short reference guide for correctly setting up the OS at launch. For example, the DNS setup should be the same for all users with a VPN.

The reason why all securities are not active by default is well justified by the official project account:

We didn't want to create a bunch of work and confusion for new users so it's opt-in for most user installed apps.

The exploit protection parameters form a key part of the GrapheneOS team's work and communication.

It is clear to me that users who are sensitive to such issues should be encouraged to activate these options as soon as the advantages outweigh the disadvantages.

My suggestion is to easily take full advantage of all the available hardware security features on the device through GrapheneOS.

jonasdoe

userofgos Thanks for recommendation, I tried it before, somehow it was even worse :D You put the finger on the scanner mid turn-on, screen turns on, scanner doesn't trigger.. At least without Lift to check phone you tap somewhere, so your finger has something else to do while waiting..

userofgos

jonasdoe interesting. I have no issues with it. As soon as I pull my phone out of my pocket or pick it up from a table, the display is on and I can scan my fingerprint

mortuary_jab

type: crash
userType: full.secondary
osVersion: google/cheetah/cheetah:17/CP2A.260605.012/2026062301:user/release-keys
uid: 1110092 (u:r:untrusted_app_34:s0:c92,c256,c523,c768)
cmdline: app.vanadium.browser
processUptime: 22s

signal: 11 (SIGSEGV), code 1 (SEGV_MAPERR), faultAddr 268
cause: null pointer dereference
threadName: anadium.browser

backtrace:
/data/app/UNbzKAKOPwNtno3IuPB9lg==/app.vanadium.trichromelibrary_782719734-HWYOjum7GNfvludc_o4ylg==/base.apk!libmonochrome_64.so (pc 8b7a3e8)
/data/app/UNbzKAKOPwNtno3IuPB9lg==/app.vanadium.trichromelibrary_782719734-HWYOjum7GNfvludc_o4ylg==/base.apk!libmonochrome_64.so (pc 8b7a38c)
/data/app/UNbzKAKOPwNtno3IuPB9lg==/app.vanadium.trichromelibrary_782719734-HWYOjum7GNfvludc_o4ylg==/base.apk!libmonochrome_64.so (pc 5dc724c)
/data/app/UNbzKAKOPwNtno3IuPB9lg==/app.vanadium.trichromelibrary_782719734-HWYOjum7GNfvludc_o4ylg==/base.apk!libmonochrome_64.so (pc 5dc699c)
/data/app/UNbzKAKOPwNtno3IuPB9lg==/app.vanadium.trichromelibrary_782719734-HWYOjum7GNfvludc_o4ylg==/base.apk!libmonochrome_64.so (pc 5dc6194)
/data/app/UNbzKAKOPwNtno3IuPB9lg==/app.vanadium.trichromelibrary_782719734-HWYOjum7GNfvludc_o4ylg==/base.apk!libmonochrome_64.so (pc 51ac7d4)
/data/app/UNbzKAKOPwNtno3IuPB9lg==/app.vanadium.trichromelibrary_782719734-HWYOjum7GNfvludc_o4ylg==/base.apk!libmonochrome_64.so (Java_J_N_VIJOOOOO+120, pc 28b8780)
/data/app/AeRhl8WjYoc0vyIzrZiBOw==/app.vanadium.browser-1uH6-ZAxmGoTlFAqihSr0Q==/oat/arm64/base.odex (art_jni_trampoline+196, pc 866a64)
/data/app/AeRhl8WjYoc0vyIzrZiBOw==/app.vanadium.browser-1uH6-ZAxmGoTlFAqihSr0Q==/oat/arm64/base.odex (cb4.n+2776, pc c78ed8)
/data/app/AeRhl8WjYoc0vyIzrZiBOw==/app.vanadium.browser-1uH6-ZAxmGoTlFAqihSr0Q==/oat/arm64/base.odex (ta4.a+1660, pc 1ec304c)
/data/app/AeRhl8WjYoc0vyIzrZiBOw==/app.vanadium.browser-1uH6-ZAxmGoTlFAqihSr0Q==/oat/arm64/base.odex (dy4.a+156, pc e65e5c)
/data/app/AeRhl8WjYoc0vyIzrZiBOw==/app.vanadium.browser-1uH6-ZAxmGoTlFAqihSr0Q==/oat/arm64/base.odex (my4.run+260, pc 15bf504)
/data/app/AeRhl8WjYoc0vyIzrZiBOw==/app.vanadium.browser-1uH6-ZAxmGoTlFAqihSr0Q==/oat/arm64/base.odex (ly4.a+372, pc 150dd54)
/data/app/AeRhl8WjYoc0vyIzrZiBOw==/app.vanadium.browser-1uH6-ZAxmGoTlFAqihSr0Q==/oat/arm64/base.odex (gxf.run+124, pc 10f811c)
/system/framework/arm64/boot-framework.oat (android.os.Handler.dispatchMessageImpl+68, pc 4dade4)
/system/framework/arm64/boot-framework.oat (android.os.Handler.dispatchMessage+44, pc 4dad7c)
/system/framework/arm64/boot-framework.oat (android.os.Looper.loopOnce+1480, pc 517d58)
/system/framework/arm64/boot-framework.oat (android.os.Looper.loop+244, pc 517714)
/system/framework/arm64/boot-framework.oat (android.app.ActivityThread.main+1700, pc 250b04)
/apex/com.android.art/lib64/libart.so (art_quick_invoke_static_stub+640, pc 2a3460)
/apex/com.android.art/lib64/libart.so (_jobject* art::InvokeMethod<(art::PointerSize)8>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject, _jobject, jobject, unsigned long)+552, pc 2942f8)
/apex/com.android.art/lib64/libart.so (art::Method_invoke(JNIEnv, _jobject, _jobject, jobjectArray) (.uniq.165753521025965369065708152063621506277)+36, pc 64b1e4)
/system/framework/arm64/boot.oat (art_jni_trampoline+116, pc 2e4114)
/system/framework/arm64/boot-framework.oat (com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run+116, pc 7e14d4)
/system/framework/arm64/boot-framework.oat (com.android.internal.os.ZygoteInit.main+4648, pc 7e84b8)
/apex/com.android.art/lib64/libart.so (art_quick_invoke_static_stub+640, pc 2a3460)
/apex/com.android.art/lib64/libart.so (art::JValue art::InvokeWithVarArgs<jmethodID>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject, jmethodID, std::va_list)+772, pc 2a0ea4)
/apex/com.android.art/lib64/libart.so (art::JNI<false>::CallStaticVoidMethodV(JNIEnv, _jclass, jmethodID, std::va_list)+148, pc 6d8554)
/system/lib64/libandroid_runtime.so (JNIEnv::CallStaticVoidMethod(_jclass, _jmethodID, ...)+104, pc 129e98)
/system/lib64/libandroid_runtime.so (android::AndroidRuntime::start(char const, android::Vector<android::String8> const&, bool)+1028, pc 1c2924)
/system/bin/app_process64 (main+1296, pc 25f0)
/apex/com.android.runtime/lib64/bionic/libc.so (libc_init+124, pc 71b4c)

mellca

Wi-Fi is broken on Google Pixel 6 and Google Pixel 8 pro after this update 2026062300

Here is a thread with this report. https://discuss.grapheneos.org/d/37229-unable-to-connect-to-wifi

It only happened on this last build. It might have something to do with the network changes on this ROM.

I expect a quick update on this at least on the next beta, otherwise I will have to flash previous stable version that was working.

Novaliss

mellca 2026062800 is up as beta release now.

de0u

mellca Wi-Fi is broken on Google Pixel 6 and Google Pixel 8 pro after this update 2026062300

Here is a thread with this report. https://discuss.grapheneos.org/d/37229-unable-to-connect-to-wifi

It only happened on this last build. It might have something to do with the network changes on this ROM.

Any time 250,000+ devices write a lot of data to flash storage and reboot, some small number of them will fail. If there are two reports of a Wi-Fi problem, one of which is from a device known to have water damage, that does not implicate the OS.

mellca I expect a quick update on this at least on the next beta, otherwise I will have to flash previous stable version that was working.

If enough independent reports are received (from devices that are not known to have physical damage) to suggest there is a problem with the new OS (including perhaps new Wi-Fi firmware), the developers are likely to look into the issue (perhaps by soliciting log information from devices).

I could be completely wrong, but I expect that if that device is flashed to a previous GrapheneOS release, or even to Google's stock OS, then the problem will continue to be observed on that device.

Fay_Wilmont

@jonasdoe I found a way to make screen-off fingerprint unlock work again using Tasker:

create a profile that's triggered by the Any Sensor event
set Type to Proximity Gated Long Press Gesture (wake-up) (just tap the magnifying glass and select it from the list, may be called differently on other devices)
connect it to a task that runs the Turn On (display) action

This should be possible with any automation app that let's you react to the sensor being triggered. A standalone app that does this could also be written.

mellca

After some research I realized this issue had to do with Android 17 itself and the way applications validate internet connection.

It seems for some apps, if the "nearby devices" permissions are not enabled, the app will not be able to connect to Wi-Fi. Once this permission is active for each app, then it will work normally.

fgrrffgggr

After receiving update 2026062301 I have problem connecting to the devices WiFi Hotspot. Another Android unit usually succeeds in connecting after a few tries. A Windows 7 PC took me half an hour of tries to be able to connect.

I did not have these problem prior to the update.

chinook

mellca does that mean that from what you seee any application that wants to use the internet connection provided via WiFi must have nearby devices granted, otherwise it cannot access the internet?

Apologies if I'm wrong, its just how I read it.

ciao-hound

What apps are people using for RCS messaging?

GrapheneOS

fgrrffgggr 2026062301 is not the current release in Stable. 2026062801 was released since then and another release is coming.

GrapheneOS

ciao-hound Not related to this thread.

« Previous Page