GrapheneOS GrapheneOS version 2026070500 released: https://grapheneos.org/releases#2026070500 See the linked release notes for a summary of the improvements over the previous release.
ClickClickDrone GrapheneOS kernel (6.1, 6.6, 6.12): backport fixes for CVE-2026-46242 I hate to ask, but why is the fix backported for kernel 6.1? Isn't it immune? Thanks for your hard efforts either way!
Norman GrapheneOS any update on the issues people are having with using wireless android auto in a non-owner profile (or the owner private space)? see: https://discuss.grapheneos.org/d/37131-wireless-android-auto-not-working-since-a17 and other separate threads complaining about it. I also asked in the Discord and got more confirmations that people have been having issues with it specifically since the Android 17 update.
Misanthropic1 GrapheneOS My 10 Pro XL and my Pixel tabler both updated to 2026070501 on the beta channel.
GrapheneOS ClickClickDrone I hate to ask, but why is the fix backported for kernel 6.1? Isn't it immune? The GitHub repository with information on the vulnerability is wrong. The change introducing the vulnerabilities has been backported in the Android LTS branch since 2024. The patch for the other vulnerability was already included by GrapheneOS and now these patches are too.
horde GrapheneOS does it patch this? https://rootme.nebusec.io/ The first browser-to-kernel full-chain RCE on Android 17 https://news.ycombinator.com/item?id=48869191
Pocketstar Again, 2026070501 is working well so far on my P6a, P7, Pixel Tablet and P9pxl. Great work as usual, thank you!
Johnnyloans ClickClickDrone The comment below by tuxsec is helpful for private space Android auto enjoyers Edit: thank you
Norman ClickClickDrone I really hope they look at it because it is practically unusable in its current state.
DarkerWolf Johnnyloans Sadly not really a long term solution. Still hoping for a real fix with a future update, something clearly changed with Android 17 that broke it
hiGOS I hope an update will be released soon that fixes the physical SIM card issue. The notification problem from other profiles isn't as important right now. The phone simply doesn't work as a phone ((
GrapheneOS hiGOS There aren't known issues with physical SIMs specific to GrapheneOS. Nothing related to it is being worked on.
IilliI Ever since this update when connecting to Android auto it prompts me to temporarily connect to the car's wifi. Is there a way to just allow it to connect automatically without unlocking my phone to tap the notification?
job_shredder69 I noticed a bug on the Accessibility page after a restart doesn't list the app/s that requires accessibility ie Bitwarden. This is to detect if there's a login page, Bitwarden will show up as an option when putting in your credentials. The option does show up in the accessibility page after some time. https://imgbox.com/0KGsf265
GrapheneOS-Jub job_shredder69 P9PXL here. Referring your SS, mine has Downlaoded Apps and Screen Reader above the Display box. Mesntime on Interaction controls Accessibility Menu is the 1st box, then Timing controls. Perhaps putting your phone model may help so others may know/compare.