GrapheneOS version 2026091900 released

GrapheneOS

GrapheneOS version 2026091900 released:

https://grapheneos.org/releases#2026091900

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

VAULT

Installing now... will advise of any issues found. P10PXL

VAULT

UpFourAGoodTime

No issues so far on Pixel 8 Pro.

nonoodle

Third update today with a new build number.
All is good again for our P8a. We have no Gapps at all, with one user only.

This morning we reset Vanadium because this web page was not opening normally (no icon/no color).
Fennec f-droid was opening normaly. The browser was updated too: Vanadium 153.0.801.

This morning we also test full reset to see if it comes back to previous build number, it does, but the channel was set back to stable default.

Under the previous beta channel build (091700), all apps were successfully installed offline before enabling WIFI(apk). The store is Droid-ify with default repos (2).

For the two previous builds, reboot was an issue (twice), not this time, it was shown under notification.

Thank you all,

Build number is now 2026091901

Pocketstar

There are no apparent issues at 2026091901 on my P6a, P7, Pixel Tablet and P9Pxl thus far.
Thank you for all the time and attention that went into this update!

GoSaM

Installed beta on 9PF now, will report issues in the unlikely event, but don't expect any 😘

xxx

Fine on P9.

Eirikr70

Running fine on P6a. Cheers!

Novaliss

All seemingly quiet on the P6a front. Paste only option. ❤️

pynosh

Working fine on p9

keycap_puller

Is it ok that the release has already reached the stable channel? It was published only 18 hours ago.

userofgos

keycap_puller why wouldn't it be ok?

wizoatk

keycap_puller

Yes, OK. It was intentional not a mistake.

Axel-de-Water

GrapheneOS Got three Bluetooth crash messages right after updating to 2026091901 on my Pixel 9 Pro XL. These happened after the update but before unlock. Here one of the error logs:

type: crash
osVersion: google/komodo/komodo:17/CP2A.260805.005/2026091901:user/release-keys
flags: dev options enabled
osVersion: google/komodo/komodo:16/BP4A.260205.002/2026042101: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 e938c)
    /apex/com.android.runtime/lib64/bionic/libc.so (ioctl+160, pc 8b6b0)
    /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 be3c28)
    /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 be1d38)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::hal::HciHalImpl::HciHalImpl(bluetooth::os::Handler*, bluetooth::hal::LinkClocker&, bluetooth::hal::SnoopLogger*)+316, pc be07dc)
    /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 9f2f5c)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::os::Reactor::Run()+832, pc 9f48b0)
    /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::os::Thread::run(bluetooth::os::Thread::Priority)+288, pc 9f5480)
    /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 9f565c)
    /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*) (.__uniq.67847048707805468364044055584648682506)+180, pc 91204)
    /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68, pc 81054)

Johnnyloans

Axel-de-Water

Disable Developer options to confirm it still happens after and try turning the phone off for 5 minutes.

Settings > system > developer options > very top is the off toggle

Axel-de-Water

Johnnyloans I'll look into it some more in a moment, it happened only just now: I don't even know if I can reproduce the error messages or whether Bluetooth is functional. I just immediately reported it while the error messages were still there.

newbie24689

Axel-de-Water Regardless the cause, Thank you for promptly reporting this to everybody!!!!

Axel-de-Water

Axel-de-Water Johnnyloans Bluetooth was working fine, even in the same session as the one where the crash reports showed up. Was unable to reproduce the crash notifications in successive restarts. So it was probably something that had to do with the update process.

newbie24689 Of course, even though it isn't causing any issues. Everything works fine, just strange that the crash messages showed up.

popcorn

Ever since updating to GOS Android 17 port, PIN scrambling is no longer working on private space. I get a standard, unscrambled keypad that doesn't match the main, scrambled unlock keypad. I'm on Pixel 9. This issue is continuing with the latest update. Anyone know if this bug is reported or of there's a plan to revert to the previous functionality of Android 16 GOS where private space PIN was scrambled?

Gdz616

Thank you @GrapheneOS my pin dont work anymore.