GrapheneOS version 2026062200 released

de0u

koocmit Seems like it will be corrected in AOSP itself.

Given Google's current release pattern, if Google's secret internal AOSP has this change today then it will be released into the public AOSP repositories in around six months. ☹️

koocmit

de0u if only google read past the the word "Android" in the Android Open Source Project, but alas

Carrousel7956

FreeFrags22 damn they really added this warning for data but not for airplane mode!

Quantum

If the code already has been written, but will take some time to deploy, maybe the GOS devs can apply it themselves...?

de0u

Quantum If the code already has been written, but will take some time to deploy, maybe the GOS devs can apply it themselves...?

If the code is in Google's secret internal AOSP, nobody but Google and their OEM partners can "apply" it.

In theory the GrapheneOS developers could reverse-engineer it... and then manually merge their code out in favor of Google's code in six months... but would that be a good use of their time?

Johnnyloans

koocmit https://xcancel.com/MishaalRahman/status/2069526071004053592

Does this mean we have A17 beta 4?

Quantum

de0u Next time I'll actually read your previous message properly and see that your wrote secret internal ASOP

GrapheneOS-Jub

About phone / Android version 17 / Android version 17 (tap 10x and follow the circle stars. Viola Android 17 flying in outer space! I did notvproceed to press hold the Android 17 logo.
If i activate the screen saver, will it give metadata to Google?

Carrousel7956

GrapheneOS-Jub it doesn't let you close without winning or restarting so I don't recommend. I cant win either.

grayway2

Nearby devices permission is automatically allowed for almost all apps. Is that normal ?

GrapheneOS

grayway2 It didn't automatically grant the full Nearby Devices but rather only local network access. You need to read the explanation at the bottom of the permission screen for it with apps with the partial compatibility mode granted to them due to not targeting Android 17 yet. There was no control over local network access prior to Android 17 and now you can revoke it via revoking the partial Nearby Devices access. No additional access was granted to those apps. Android explains it with the standard UI.

Johnnyloans

Carrousel7956

At any point, I was able to push the back button

Carrousel7956

Johnnyloans lets you leave but it doesn't disappear.

Quantum

I dont know if it's a bug or not. Most apps will be set to allow only over local network in the nearby devices permission, not fully allowed though. But if you deny it access, but wanna switch on for it to work over your local network again you can only allow it full access to the permission. As in working over bluetooth also.

Maybe it works this way because apps arent coded for this yet?

GrapheneOS

Quantum That's the standard way it works on Android 17. Nearby Devices gives filtered Bluetooth scanning access, not the ability to freely pair with anything without consent. Filtered Wi-Fi scans for direct pairing also fall under it. Local network access was added to the permission in Android 17 which is why there's a compatibility mode granted by default. They chose to have these as part of 1 permission since local network access is similarly invasive in many cases due to people having all kinds of insecure IoT devices treating local network access as authentication along with other local services on desktops/laptops, etc.

Bear in mind it grants access to ALL local networks, not only on a specific local network. A better approach would have been to grant access to specific local networks to an app and not to tie it to any coarse permission toggle but we don't choose how the baseline Android permission model works. How we would do it isn't the same as how they did it.

anonymousgrapheneperson

GrapheneOS Thanks for the new features. There are also no bugs on my Pixel 9 Pro XL.

Pocketstar

GrapheneOS-Jub Perhaps a reboot may solve the issue?
With me all USB pheripherals are working fine, I also have a Pixel 9 Pro XL. (I will also try other storage devices soon, like a Samsung T7 and several flash drives to see if I can replicate this issue)
I think a factory reset is a bad idea until a developer have commented on the bug you've reported, especially if it did not happen on Android 16 before.
Otherwise a next update might just fix this.
I did have a USB-related crash however, but that was a one-off and did not replicate the issue you've descibed:
https://wormhole.app/9o08qp#la7EGhFeCOufJOzhC2lloQ
(Crash log, you can view it on wormhole without having to download it) This happened once during the use of my Xreal One glasses, I plugged it in repeatedly, I guess it was a bit too fast, it did not happen again after that.

Canardo_Sanchez

Am I the only one that lost VoLTE and WifiCall since this update ?
I was on latest stable 16 before that.

I reseted network parameters and rebooted to no avail, overrides carrier parameter doesn't work either.
I'm using Sosh (Orange network) in France.

Halp :)

Canardo_Sanchez

If anyone has the same issue, the solution for me was to disable data saver and forced metered WiFi connection. Volte and WiFi call option reappears, then you can re-enable everything.

Pocketstar

GrapheneOS-Jub Just to get back to you about the testing USB stuff;
I tried a number of USB pheriperals from USB flash drives to several hard drives, an SSD, several OTG adapters to try, gamepads, a mouse, a keyboard, a USB to (micro)SD adapter, a Yubikey, Bluetooth and WiFi adapters.
At least, alot of hardware has now been tested on Android 17. (See photo of the stuff I tried on wormhole, and again downloading is not required)
https://wormhole.app/xmdbEX#9gsrjOocd3w1CfEIN87XJQ
I also enabled all notification options. (Bubbles, etc)
Everything worked as advertised, I could not replicate the bug. I am on 2026062201.
Perhaps the USB port is dirty or it is a hardware issue?
I hope you can find someone who can figure it out for you though, sadly, I have exhausted my possibilities of replicating this error. I hope a developer can help you along the way, they know so much more about the system than me.

GrapheneOS-Jub

Pocketstar Thanks for doing the tests. So perhaps it is only on my P9PXl unit. Not bothering me though as notif is gone when i switch profiles and back. Let'
s enjoy our toys 🤣

Pocketstar

GrapheneOS-Jub Thanks for doing the tests. So perhaps it is only on my P9PXl unit. Not bothering me though as notif is gone when i switch profiles and back. Let'
s enjoy our toys 🤣

No problem! Tests like these are always useful regardless. Perhaps you can try a different OTG-adapter if you are using one of those. If it is not the phones' hardware at error, it may be the connector in between, that would also explain the malfunctioning of other pheriperals.
But you may want to discuss it with a dev, I am a n00b with electronics and software.

Edit: Wait, it is the notifications that disappear whem switching profiles with a USB device inserted? I have not tried that myself.
It may be the case that I have misunderstood what the issue was here, you definitely want to ask someone else instead of me!
My apologies for the inconvienence.

GrapheneOS-Jub

Pocketstar Thanks for coming back. Inserted USB works normally. But if i delete/move a file inside that USB flash drive, the notification appears but it does not disappear even if it has completed 100% of its task. Have you tried deleting or moving a file from a USB, notif shows and once task is gone, notification disappears? On mine, it remains on the screen 😥

D3vray

Hi I have a compilation error : in file included from build/make/core/config.mk:428
in file included from build/make/core/envsetup.mk:350

build/make/core/product_config.mk:226 error cannot locate config makefile for product tegu

GrapheneOS

D3vray You appear to have skipped the adevtool process.

« Previous Page Next Page »