GrapheneOS version 2026091000 released

starglider

mspbonn Still missing bubbles functionality on the Tablet.

I think this is an AOSP issue; there are lots of complaints about it on Reddit and elsewhere, not limited to GOS. I think Google has pretty much just abandoned that product (it's formally discontinued now). So, unless GOS writes a specific patch to fix this, I suspect we'll never get it. Which, in fairness to the devs, us tangorpro users are a tiny sliver of the user base.

Johnnyloans

Love you all.
Thanks for making several update diffs too :)

SoundOfSilence

What does the 'Contact Scopes: improve compatibility with certain apps' mean exactly?

userofgos

SoundOfSilence back during the initial transition to Android 17 there was an issue with Contact Scopes not working properly on WhatsApp. It may be related to additional fixes to that, or it may be something similar/different.

See here:

SoundOfSilence

userofgos

Might be it indeed.

I was hoping it was related to this: https://discuss.grapheneos.org/d/33381-contact-scopes-incompatible-with-carddav

userofgos

SoundOfSilence maybe it would be useful to make a github issue for that one.

Johnnyloans

SoundOfSilence

Have you tested it again and it still doesn't work?

SoundOfSilence

Johnnyloans
userofgos

I have not tested it again, but will test it in the coming days.
It's probably the same root cause as this issue: https://github.com/GrapheneOS/os-issue-tracker/issues/7477

SoundOfSilence

Did a quick test and, when using full contacts it does seem to work. When using it with just the phone number, it doesn't.

overcoat42

Hello. I'm on build number 2026091001 and it broke my wifi, Bluetooth and hotspot. I'm on a Pixel 8 Pro.

Should I post the log here? Or what's the correct way to provide information to debug this issue.

otterfoghornrainfall

overcoat42 Creating an issue on GitHub

Johnnyloans

overcoat42

Create a new discussion on this site before putting anything on github.
Does your Bluetooth work? Try going into safe mode.
What do you mean by broken? Slow? Can't connect? No WiFi networks found? Wifi HAL crashes with an error pop-up?

overcoat42

Johnnyloans

Thank you for your response friend.
I
Bluetooth doesn't work, it keeps crashing. In safe mode its no different. Broken as in Bluetooth crashes, wifi and hotspot never turn on.

This is the Bluetooth log

type: crash
osVersion: google/husky/husky:17/CP2A.260805.005/2026091001:user/release-keys
flags: dev options enabled
package: com.android.bluetooth:37, targetSdk 37
sharedUid: android.uid.bluetooth
process: com.android.bluetooth

signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'system/gd/hal/hci_backend_aidl.cc:103 operator(): The Bluetooth HAL died.'

backtrace:
      #00 pc 0000000000083230  /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: e988e7c35b6f1e7ad2dd459ae0a61e05)
      #01 pc 000000000061d6ec  /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+604) (BuildId: 0f651191bb3e69ddf4844270b26ad1a2)
      #02 pc 0000000000016bb4  /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_0::__invoke(char const*)+84) (BuildId: 5431b597074b540e87bfbe10ceaf4d44)
      #03 pc 0000000000e334ac  /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::log_internal::vlog(bluetooth::log_internal::Level, char const*, bluetooth::log_internal::source_location, std::__1::basic_string_view<char, std::__1::char_traits<char>>, std::__1::basic_format_args<std::__1::basic_format_context<std::__1::back_insert_iterator<std::__1::__format::__output_buffer<char>>, char>>)+844) (BuildId: cda3fcddb714782f3300cfc57e9d42c8)
      #04 pc 0000000000caad08  /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::log::fatal(std::__1::basic_format_string<char>, bluetooth::log_internal::source_location)+72) (BuildId: cda3fcddb714782f3300cfc57e9d42c8)
      #05 pc 0000000000caacb0  /apex/com.android.bt/lib64/libbluetooth_jni.so (bluetooth::hal::AidlHci::AidlHci(char const*)::'lambda'(void*)::__invoke(void*)+112) (BuildId: cda3fcddb714782f3300cfc57e9d42c8)
      #06 pc 0000000000014044  /system/lib64/libbinder_ndk.so (AIBinder_DeathRecipient::TransferDeathRecipient::binderDied(android::wp<android::IBinder> const&)+68) (BuildId: 0b57b1cbabe5e9f96395db9503992872)
      #07 pc 000000000006f03c  /system/lib64/libbinder.so (android::BpBinder::sendObituary()+268) (BuildId: 71ff964c84905384e3a820f9225c4d9c)
      #08 pc 000000000005a374  /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+5060) (BuildId: 71ff964c84905384e3a820f9225c4d9c)
      #09 pc 00000000000982fc  /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+300) (BuildId: 71ff964c84905384e3a820f9225c4d9c)
      #10 pc 00000000000981bc  /system/lib64/libbinder.so (android::PoolThread::threadLoop()+28) (BuildId: 71ff964c84905384e3a820f9225c4d9c)
      #11 pc 0000000000019648  /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+264) (BuildId: 215535cfe80abfb3eb3348fdfb429558)
      #12 pc 00000000001cc30c  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+108) (BuildId: e617dcc9ee2f26b4928fc585b40d6e1c)
      #13 pc 000000000001bc18  /system/lib64/libutils.so (libutil_thread_trampoline(void*) (.__uniq.226528677032898775202282855395389835431)+24) (BuildId: 215535cfe80abfb3eb3348fdfb429558)
      #14 pc 0000000000096ee4  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*) (.__uniq.67847048707805468364044055584648682506)+180) (BuildId: e988e7c35b6f1e7ad2dd459ae0a61e05)
      #15 pc 0000000000086cf4  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: e988e7c35b6f1e7ad2dd459ae0a61e05)
Note: To display stack pointer information, use the pbtombstone tool:
        pbtombstone --display-sp tombstone_XX.pb

This is a portion of the error logs.

09-17 23:52:51.252  1300  1957 E WifiChipAidlImpl: configureChip failed with service-specific exception: android.os.ServiceSpecificException: , timed out (code 9)
09-17 23:52:51.253  1300  1957 E WifiChipAidlImpl: getMode failed with service-specific exception: android.os.ServiceSpecificException:  (code 5)
09-17 23:52:51.255  1300  1957 E HalDevMgr: executeChipReconfiguration: configureChip error
09-17 23:52:51.256  1300  1957 E HalDevMgr: Teardown Wifi internal state
09-17 23:52:51.256  1300  1957 E WifiHalAidlImpl: Unable to call isStarted because IWifi is null.
09-17 23:52:51.256  1300  1957 E WifiHalAidlImpl: Unable to call isStarted because IWifi is null.
09-17 23:52:51.256  1300  1957 E WifiHalAidlImpl: Unable to call isStarted because IWifi is null.
09-17 23:52:51.256  1300  1957 E HalDevMgr: createIfaceIfPossible: Failed to create iface for ifaceType=4, requestorWs=WorkSource{1010}
09-17 23:52:51.256  1300  1957 E WifiNative: Failed to allocate new Nan iface
09-17 23:52:51.259  1300  1957 E WifiAwareNativeManager: Was not able to obtain a WifiNanIface (even though enabled!?)
09-17 23:52:51.259  1300  1957 E WifiAwareNativeApi: getCapabilities: null interface
09-17 23:52:51.263  1300  1957 E WifiActiveModeWarden: One of the native daemons died. Triggering recovery
09-17 23:52:51.281  1300  1957 E WifiSelfRecovery: Triggering recovery for reason: WifiNative Failure
09-17 23:52:51.281  1300  1957 E WifiSelfRecovery: Already restarted wifi 10 times in last 1 hour. Disabling wifi
09-17 23:52:51.293  1300  1957 E WifiChipAidlImpl: getMode failed with service-specific exception: android.os.ServiceSpecificException:  (code 5)
09-17 23:52:51.295  1300  1957 E WifiChipAidlImpl: getMode failed with service-specific exception: android.os.ServiceSpecificException:  (code 5)

Johnnyloans

overcoat42

Sorry mate. Your situation looks just like when the WiFi and Bluetooth hardware fails. You could try sideloading a full ota .zip file

Instructions
https://grapheneos.org/usage#updates-sideloading

Go to settings > about phone > build number

and match the end of the URL below with your build number

https://releases.grapheneos.org/husky-ota_update-2026091000.zip

https://releases.grapheneos.org/husky-ota_update-2026091001.zip

overcoat42

So you mean there was an issue during the install and I need to reinstall again?

I can do that and hopefully it works :/

Johnnyloans

overcoat42

I failed to mention that the process of sideloading does not delete your data. If you re-install, then you delete your data. So do not turn on OEM unlocking. Do not use developer options at all.

Hopefully it works. If not, it is probably a hardware failure for WiFi/Bluetooth.

You don't need to unzip the .zip file you download.

de0u

overcoat42 So you mean there was an issue during the install and I need to reinstall again?

The described symptoms are consistent with the Bluetooth and Wi-Fi hardware suddenly breaking, which happens on some devices, sometimes at the same time but not always.

Sometimes turning the device off for a while (5 minutes?) and restarting it helps. But if that cycle happens twice then probably the hardware is on its way out.

overcoat42

Oh no, I was so happy with my phone! I'm really hoping it's not the hardware. Isn't is kind of strange that it coincided with the software update?

de0u

overcoat42 Isn't [it] kind of strange that it coincided with the software update?

It's not that strange. This kind of thing often turns up when a device is restarted, and lots of people don't restart their phones a lot when there isn't an update.

Here are some posts from users reporting "The Bluetooth HAL died":

Since this particular issue is almost certainly not related to the 2026091000 release, it would probably be best for further discussion to occur in a different thread.

Pocketstar

overcoat42 So you mean there was an issue during the install and I need to reinstall again?

Before you do a reinstall, perhaps you can first try to reset Bluetooth and WiFi in the reset options (Settings/System/Reset Options/) and do a reboot afterwards?

« Previous Page Next Page »