GrapheneOS

@ElysianEve@toot.community It's also possible you simply use an app which connects to it. We haven't confirmed if there's still an issue of Samsung gnssd using the ntp.org pool itself instead of the OS time. It's just a possibility it does.

@ElysianEve@toot.community GrapheneOS uses HTTPS network time itself. There may be a connection to ntp.org from the Samsung gnssd service which we may still need to replace. Blocking it should be harmless as long as it knows to fall back to the OS time. This isn't intended to happen but is a potential recent regression. Pixel 8a and 9th generation Pixels use Samsung GNSS instead of Broadcom GNSS and this potential issue is limited to them. We need to research it and replace it if it still happens.

@ElysianEve@toot.community It's still possible to disable those apps via ADB, we just turn off the option in Settings similarly to what AOSP / stock Pixel OS do for many OS components because people don't realize they'll break stuff.

@ElysianEve@toot.community You can disable it on profiles where you don't use it. The same applies to most of the built-in apps. Camera is a special case providing very basic OS functionality to other apps. It can still be disabled via ADB. Messaging and Dialer are similar to Camera where they're expected to be present and aren't really meant to be disabled. We don't change how it works for those 2, that's standard. We gray out disable for Camera, Keyboard and WebView since otherwise people break apps.

@ElysianEve@toot.community It would be broken to disable the system camera app. It always provides the system media capture intents and therefore disabling it is grayed out in the Settings app on GrapheneOS. You still need the system Camera app to provide photo and video capture for apps using the system media capture intents instead of providing their own camera UI. It's still technically possible to disable it via ADB but we don't recommend it since apps using these intents often don't check for errors.

@ElysianEve@toot.community It's worth noting that our PDF Viewer has a unique, highly secure approach to PDF rendering and other PDF viewers largely have atrocious security. The only one with reasonable security would be the Chromium PDFium one which can be enabled in Vanadium via chrome://flags but is still significantly less secure than our PDF Viewer which is why it's disabled by default. Significant improvements will be made to our PDF Viewer such as adding swiping between pages in a single view.

@ElysianEve@toot.community Vanadium browser and Vanadium WebView are already separate apps. You can disable the Vanadium browser without disabling the WebView. Vanadium is the most secure available browser and what we recommend as a general purpose browser though.

> Also is it possible to allow the removal of calculator clock contacts and gallery (and info / pdf viewer)?

You can disable apps which you aren't interested in using. It prevents them running. You just have the option to enable them again.

This is our first official release based on Android 16. It's still experimental and whether or not this release will reach the Alpha channel depends on the feedback from users manually installing it prior to Alpha. There are several known issues but nothing major reported yet.

@blue Private Space VPN has always been separate. Nothing about that has changed. Per-profile VPNs have been part of Android for many years and Private Space is a recent feature added in Android 15.

@blue@layer8.space That's an issue with your setup, not any recent OS update. Each profile has their own VPN setup. Your VPN setup in your Private Space is broken and you need to fix it.

@Frorscher@social.anoxinon.de We need to do another release today to fix an issue with the RIL backports but then it should be good to make it through Alpha and Beta testing to reach Stable, unlike the most recent release which had call related regressions reported very quickly in Alpha testing which are now resolved.

@Frorscher@social.anoxinon.de We added a note about when the full 2026-06-05 Android patch level was shipped to clarify this. Backported the Mali kernel driver update from Android 16 covered the 2025-06-05 Android patch level but not the 2025-06-05 Pixel patch level mainly because that includes RIL patches and we needed to backport those too. We also don't know if the Wi-Fi and Bluetooth patches in the Pixel bulletin are in the drivers or firmware so we updated the firmware in the most recent release too.