GrapheneOS version 2026110200 released

GrapheneOS

GrapheneOS version 2026110200 released:

https://grapheneos.org/releases#2026110200

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

Novaliss

Installing.

phone-company

Me too...

porta

After the update i got the following crash:

type: logcat
osVersion: google/komodo/
buffers: crash


--------- beginning of crash
11-03 21:51:20.407  1000   669   714 F libc    : Fatal signal 11 (SIGSEGV), code 9 (SEGV_MTESERR), fault addr 0xa00c3e2fcb9e35c in tid 714 (android.hardwar), pid 669 (android.hardwar)
11-03 21:51:20.521  1000   787   787 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
11-03 21:51:20.521  1000   787   787 F DEBUG   : Build fingerprint: 
11-03 21:51:20.521  1000   787   787 F DEBUG   : Kernel Release: '6.1.182-android14-11-gae67dbef00c8'
11-03 21:51:20.521  1000   787   787 F DEBUG   : Revision: 'MP1.0'
11-03 21:51:20.521  1000   787   787 F DEBUG   : ABI: 'arm64'
11-03 21:51:20.521  1000   787   787 F DEBUG   : Timestamp: 2026-11-03 21:51:20.460915043+0000
11-03 21:51:20.521  1000   787   787 F DEBUG   : Process uptime: 0s
11-03 21:51:20.521  1000   787   787 F DEBUG   : Executable: /vendor/bin/hw/android.hardware.composer.hwc3-service.pixel
11-03 21:51:20.521  1000   787   787 F DEBUG   : Cmdline: /vendor/bin/hw/android.hardware.composer.hwc3-service.pixel
11-03 21:51:20.521  1000   787   787 F DEBUG   : pid: 669, ppid: 1, tid: 714, name: android.hardwar  >>> /vendor/bin/hw/android.hardware.composer.hwc3-service.pixel <<<
11-03 21:51:20.521  1000   787   787 F DEBUG   : uid: 1000
11-03 21:51:20.521  1000   787   787 F DEBUG   : tagged_addr_ctrl: 000000000007fff7 (PR_TAGGED_ADDR_ENABLE, PR_MTE_TCF_SYNC, PR_MTE_TCF_ASYNC, mask 0xfffe)
11-03 21:51:20.521  1000   787   787 F DEBUG   : pac_enabled_keys: 000000000000000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
11-03 21:51:20.521  1000   787   787 F DEBUG   : esr: 0000000092000011 (Data Abort Exception 0x24)
11-03 21:51:20.521  1000   787   787 F DEBUG   : signal 11 (SIGSEGV), code 9 (SEGV_MTESERR), fault addr 0x0a00c3e2fcb9e35c (read)
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x0  0000000000000000  x1  0000c11f00c90b88  x2  0000000000000018  x3  000000002f500a6b
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x4  00ffffffffffffff  x5  0000000000001306  x6  00000000ffffffff  x7  3a736c745f646e61
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x8  0000000000000001  x9  0000000000000002  x10 0000000000000002  x11 2fabe40ef215f700
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x12 0000000000000009  x13 000000007fffffff  x14 0000000000001306  x15 000000002f5143d7
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x16 0000c45c153f2100  x17 0000c45c0d500d20  x18 0000c11efd634000  x19 0800c242239f1800
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x20 0000c11f00c90be0  x21 0000c11f00c90bc0  x22 0a00c3e2fcb90000  x23 0800c242239f1868
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x24 0000000000000002  x25 0a00c3e2fcb9e000  x26 7ffffffed5fa0e00  x27 000000012a05f200
11-03 21:51:20.521  1000   787   787 F DEBUG   :     x28 000000000000e3b8  x29 0000c11f00c90c30
11-03 21:51:20.521  1000   787   787 F DEBUG   :     lr  0000c45c13a44dd4  sp  0000c11f00c90bc0  pc  0000c45c13a44e0c  pst 0000000020001000
11-03 21:51:20.521  1000   787   787 F DEBUG   :     esr 0000000092000011  vg  0000000000000002
11-03 21:51:20.521  1000   787   787 F DEBUG   : 4 total frames
11-03 21:51:20.521  1000   787   787 F DEBUG   : backtrace:
11-03 21:51:20.521  1000   787   787 F DEBUG   :       #00 pc 00000000000c7e0c  /vendor/lib64/libexynosdisplay.so (ExynosDevice::dynamicRecompositionThreadLoop(void*)+572) (BuildId: 3b14c3325b4c04e7ae5cf960894c29ae)
11-03 21:51:20.521  1000   787   787 F DEBUG   :       #01 pc 00000000000cbb1c  /vendor/lib64/libexynosdisplay.so (void* std::__1::__thread_proxy[abi:nn220000]<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct>>, void* (*)(void*), ExynosDevice*>>(void*)+44) (BuildId: 3b14c3325b4c04e7ae5cf960894c29ae)
11-03 21:51:20.521  1000   787   787 F DEBUG   :       #02 pc 0000000000096fe4  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*) (.__uniq.67847048707805468364044055584648682506)+180) (BuildId: 1c11eb7593faec120ef862d0d8b91391)
11-03 21:51:20.521  1000   787   787 F DEBUG   :       #03 pc 0000000000085fd4  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68) (BuildId: 1c11eb7593faec120ef862d0d8b91391)
11-03 21:51:20.521  1000   787   787 F DEBUG   : Note: To display stack pointer information, use the pbtombstone tool:
11-03 21:51:20.521  1000   787   787 F DEBUG   :         pbtombstone --display-sp tombstone_XX.pb
11-03 21:51:20.521  1000   787   787 F DEBUG   : Learn more about MTE reports: https://source.android.com/docs/security/test/memory-safety/mte-reports
11-03 21:51:23.131  root  1130  1130 F libc    : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 1130 (init), pid 1130 (init)
11-03 21:51:23.175  root  1130  1130 F libc    : Crash due to signal: crash_dump helper failed to exec, or was killed

Never happened before and no new APP was installed before this crash.

Device: PX9 Pro XL

Pocketstar

Thank you for this amazing update as well as the kernel updates, that was blazing fast!
No issues on 2026110201 at my P6a, P7, Pixel Tablet and Pixel 9 ProXL.
I haven't tried cellular nor Play Services.

GrapheneOS

porta That's an existing upstream bug unrelated to the changes.

Sonic

No issues to note on my Pixel 10 Pro after about 1-2 hours of usage. Will update if any is found.

porta

GrapheneOS thanks for the explanation.

SBMe25

Just did the update on Pixel 9 Pro and had a kernel panic and it rebooted on it's own. Seems ok now though. I did save the text file, it is very, very long though.

Novaliss

All seems good on P6a. Mobile network, Sandboxed Google Play.
Another one of the updates making the device feeling 'snappier'.

GrapheneOS

SBMe25 Please email the crash log to logs@grapheneos.org.

phone-company

10a ist fine untill now. Nothing unexpected found.

GoSaM

Installing on 6P 😘

MrLinux

9a updated everything works so far no issues.

Goldy

P10 pro, play services still crashing after boot

Goldy

Okay second reboot didn't crash the play service.
But installing and updating takes very long on the P10, maybe I'm missing something, because the Pixel tablet is fast when installing apps.

GrapheneOS

Goldy Goldy There's no known issue with Play services. Provide the crash report. It's likely from enabling a feature that's not supported such as motion assist.

shaylyn

I have had problems with the last two releases. I think Graphene is amazing. This is just feedback.

(Nevermind it was user error from me)

Manky

Just had a kernal crash running pixel 10 with this update. Browsing then phone locked up and shut down. Have emailed report to log email provided above.

VanDerKarbargenbok

Goldy no problems on my 10 Pro with sandboxed play services.