GrapheneOS version 2026060600 released

GrapheneOS

GrapheneOS version 2026060600 released:

https://grapheneos.org/releases#2026060600

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

wildoil

replace our implementation of restoring compatibility with apps opting into a combination of two separate anti-competitive Play Store features preventing using their apps on GrapheneOS when combined together by replacing the insecure Play Store installer check injected into the app with a secure Play Source source stamp check by the OS

Is there more context on this?

Johnnyloans

GrapheneOS

Thanks for the great update! 🧑‍🍳🤌

Please consider reviewing release notes for wordiness, run-on sentences, and excessive-modifier convolution. I know that I'm calling the kettle black.

For example, this is 1 sentence:

replace our implementation of restoring compatibility with apps opting into a combination of two separate anti-competitive Play Store features preventing using their apps on GrapheneOS when combined together by replacing the insecure Play Store installer check injected into the app with a secure Play Source source stamp check by the OS (this will fix compatibility with the new Play Store injected code that's being rolled out for apps using this)

The convolution with so many modifiers stacked together.
Too many ideas in 1 sentence:

Replace our implementation ... Restoring compatibility ... opting into a combination of ... Features preventing ... When combined ... By replacing ... Inject into the app with a ... Check by the OS.

❤️

Native speakers would struggle with this -- translation services and ESL users even more so.

keycap_puller

Should the security patch level be 2026-06-05? It's not mentioned in the release.

GrapheneOS

keycap_puller Pixels haven't had a stock OS release for June 2026 so we don't know what will be in the 2026-06-05 Pixel patch level yet. We may start using the field for solely the Android security patch level but then we'd need to determine if any 2026-06-05 patches listed in the bulletin require a stock Pixel OS update for new firmware, etc.

We ship the AOSP userspace patches 2-6 months early in our security preview releases. The whole YYYY-MM-01 patch level is always already included in our security preview release at least 1 month early. We ship the upstream kernel patches around 4-6 months early so the upstream kernel patches listed in the 2nd half of the bulletin are never relevant. If you're using our security preview releases then the device-related driver/firmware patches in the 2nd half of the Android bulletin and the ones in the Pixel bulletin are the only new patches. Most of the Android bulletin ones aren't relevant to Pixels but it's hard to determine what they refer to in many cases. For example, the Pixel 7a has Qualcomm Wi-Fi so one of the Qualcomm patches could be relevant.

The patches for the Pixel device support code including firmware depend on them releasing a stock OS update at which point we can request the new kernel sources and use the new firmware, etc. from the stock OS.

x-pve

Changes since the 2026052400 release:

Should be Changes since the 2026060100, right?

GrapheneOS

x-pve Yes, it's fixed now.

plazmafire

Have they fixed the Legacy Bluetooth Connection failure yet?

Johnnyloans

plazmafire

No, I don't believe so. Android 17 should be out in a few months. Google claims they fixed the bug.

Pocketstar

Update 2026060601 is working fine on my P6a, P7, Pixel Tablet and P9Pxl, thank you!
I haven't tested Google services though. (I do not have it installed)

xxx

Fine on P9 & P6.

Eirikr70

Running fin on my P6a, as usual!

Norman

Thank you for fixing the tethering offload issue so quickly, love you guys <3

Developer-Dude

Working good on my 9a! Funny because I randomly got a thought, "wonder if the latest updates Stable yet?" and as soon as I had thought that I got a notification 'Downloading System Update'! :D Thanks @GrapheneOS and team for another smooth update! 🚀

MrLinux

P9a updated everything is working good so far no issues.

pixel---fold

Updated fine! Thank you Graphene team!

wyse

Update 2026060601 full ok (10 pro xl), thanks.

kucopile

After this update i have this BT crash 3 times in a row:
P9PXL; stable ver. 601

type: crash
osVersion: google/komodo/komodo:16/BP4A.260205.002/2026060601:user/release-keys
osVersion: google/komodo/komodo:16/BP4A.260105.004.E1/2026011301:user/release-keys
uid: 1002 (u:r:bluetooth:s0)
cmdline: com.android.bluetooth
processUptime: 0s

signal: 6 (SIGABRT), code -6 (SI_TKILL)
threadName: droid.bluetooth
MTE: enabled

backtrace:
    /apex/com.android.runtime/lib64/bionic/libc.so (__ioctl+12, pc e970c)
    /apex/com.android.runtime/lib64/bionic/libc.so (ioctl+160, pc 8ba30)
    /system/lib64/libbinder.so (android::IPCThreadState::transact(int, unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+1680, pc 65080)
    /system/lib64/libbinder.so (android::BpBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+276, pc 88054)
    /system/lib64/libbinder.so (android::BpBinder::getInterfaceDescriptor() const+240, pc 87ad0)
    /system/lib64/libbinder_ndk.so (AIBinder_associateClass+92, pc 1c1ec)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (aidl::android::hardware::bluetooth::IBluetoothHci::fromBinder(ndk::SpAIBinder const&)+72, pc be3b08)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::hal::HciBackend::CreateAidl(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&)+952, pc be1c18)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::hal::HciHalImpl::HciHalImpl(bluetooth::os::Handler*, bluetooth::hal::LinkClocker&, bluetooth::hal::SnoopLogger*)+316, pc be06bc)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::shim::Stack::handle_start_up(std::__1::promise<void>)+108, pc 3dfc5c)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (base::internal::Invoker<base::internal::BindState<void (bluetooth::shim::Stack::*)(std::__1::promise<void>), base::internal::UnretainedWrapper<bluetooth::shim::Stack>, std::__1::promise<void>>, void ()>::RunOnce(base::internal::BindStateBase*)+84, pc 3e12a4)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::os::Handler::handle_next_event()+316, pc 9f2e3c)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::os::Reactor::Run()+832, pc 9f4790)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::os::Thread::run(bluetooth::os::Thread::Priority)+288, pc 9f5360)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (void* std::__1::__thread_proxy[abi:nn210000]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void (bluetooth::os::Thread::*)(bluetooth::os::Thread::Priority), bluetooth::os::Thread*, bluetooth::os::Thread::Priority>>(void*)+76, pc 9f553c)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*) (.__uniq.67847048707805468364044055584648682506)+180, pc 91584)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68, pc 813d4)

digest

Updated from stable branch and the update seems to have misaligned all of my home-screen icons with some just disappearing. More of an annoyance that anything else.

stupor0180

digest same here. Random misalignment, resorting, deletion of apps from home screen. Especially missing some bookmarks added to home screen - not all, though. Looks pretty random.

MineralWater

Since this update (security channel) i have problems on some sites with Proton Pass Auto fill.

On some sites when clicking into a account field (name or password) to trigger the auto fill service, it immediately closes the process instantly, means it is impossible to fill in data manually because the cursor doesn't stay.

Is this a problem of the Firmware or Proton Pass?

Here on the Forum website Proton pass is working. On some other sites it is not, independent from if Vanadium or Brave is used, it happens in both browsers.

GrapheneOS

wildoil It restores compatibility with apps opting into both restricting their Play Store listing to Google certified devices and also opting into Google's automatic anti-tampering code injection which enforces the app being installed from the Play Store. It detects the valid Play Store source stamp signature and bypasses the Play Store installer checker which provides compatibility without interfering with anti-tampering. We'll be using the same Play Source source stamp signature to bypass apps checking for the Play Store being the installer. This wouldn't be a priority if Google didn't have a toggle to enforce Play Integrity API levels for Play Store listings. Since they provide that as an option, we need to work around Play Store installer checks since it isn't always an option.

userofgos

GrapheneOS There's no toggle to enable this in App info settings since it's all done in the background and/or behind the scenes right?