@modem_down @beep @Semi_Hemi_Demigod The software walks the person using it through enabling Android Debug Bridge and extracting data with it. It's either not going to work or will be able to see many signs of what happened. GrapheneOS is well known to the forensic data companies and they make a point of trying to support it. They haven't had much success with locked GrapheneOS devices but they can certainly handle detecting it and detecting if a feature like this was used via ADB.

@orclev Standard operating procedure is increasingly to extract data with standard forensics software. If it doesn't go smoothly then they'll likely detain people and get experts to deal with it.

@modem_down @beep @Semi_Hemi_Demigod It would be trivially detected by widely distributed standard forensic software including the non-Premium variant of Cellebrite able to run on a laptop.

@Roxxor Yes, the past release deliberately didn't reach Stable since we knew this one was coming and it hasn't reached Stable yet. This one has no actual relevant fixes though, only a fix for a feature flag that's not enabled. It has no security fixes.

@zahox That sounds like an app bug.

@x_tof It's from the Android 16 QPR1 UI overhaul. It majorly improved quick tiles and you can now have 4 per row instead of 1 along with more functionality being added to certain ones like Bluetooth when they're expanded to being 2 wide. You can use the reset button at the bottom of the quick tile edit menu shown with the edit button in the notification tray to switch to the new default layout which has much more compact/dense functionality while still having the same information as before.

@zahox It doesn't matter. You can just say no, but there's no negative consequence beyond insignificant wasted space if you install that useless app. It doesn't do anything on GrapheneOS. You can configure the spell checking which is related to the keyboard but configurable separately in the language settings. You may need to switch the spell checker and keyboard if it's for a non-English language it doesn't support well and you want to have spell checking and suggestions for it.

@ferrex That's the issue, 3rd generation Pixels no longer even have that bare minimum support anymore. We've kept sandboxed Google Play working on end-of-life 4th/5th gen Pixels but without updates to it. Current Vanadium has also been kept working on those, although there have been regressions which weren't noticed for a while. Pixel 6 and later are what's actually supported and we don't try to keep 3rd gen working beyond not deliberately taking down the network services it uses for XTRA, etc.

@ferrex The new update is currently in the Beta and Alpha channels of the App Store.Which device do you have GrapheneOS installed on? The App Store has a self-dependency of Vanadium on a certain version of Vanadium due to required OS changes for it to work properly. We could eventually drop that when we completely stop caring about breaking end-of-life devices or people installing it outside GrapheneOS without support for those operating systems yet.

@felix196 All releases start out in Alpha, then go to Beta and then Stable if no major issues are found. It should be in the Beta channel very soon, perhaps within an hour.

@2babcc That's an upstream bug which may be partially resolved now.

@privacyDuck It's a nice small improvement but is unlikely to make even a tiny difference for security. It's quite a small amount of code with most of the functionality having been moved into the PSP and elsewhere anyway. That's probably why they're willing to do it in the first place, since they no longer consider there to be any important intellectual property included in it. The overall hardware/firmware is closed source and will likely remain so. Opening it would be nice but not more secure.