The same thing happens on my 6a (2024101900) as well. Not a big thing, nevertheless I can confirm the issue.
GrapheneOS version 2024102100 released
Carpool7341 Uninstalling it isn't recommended since some things it used to define may not move properly with it removed. It won't be present for a fresh install of sandboxed Google Play though.
Got it already on my P7a and everything seems to be working just fine
- Edited
Updated to stable on a Pixel 8 Pro but currently experiencing issues with accessibility settings toggles. So far I have tested colour correction, inverted colours, and extra dim mode and in all three cases toggling the settings off has no effect. Is anyone else able to reproduce the same issue(s)?
Just got the update on my Pixel Tablet. Seems stable so far, no issues. Thanks to the GOS team for your great work!
The only thing I'm wondering: is there any possiblity currently, to install Apps into Private Space from something else than Play Store / GOS App Store? (e.g. Obtanium, Aurora, F-Droid, Sideloading)
schuubert44 The only thing I'm wondering: is there any possiblity currently, to install Apps into Private Space from something else than Play Store / GOS App Store? (e.g. Obtanium, Aurora, F-Droid, Sideloading)
You can use any app store and you can sideload. The "Install" button in the Private Space home drawer depends on the app store supporting being opened by that button; Accrescent supports that now, don't know about the others.
fid02 You can use any app store and you can sideload. The "Install" button in the Private Space home drawer depends on the app store supporting being opened by that button; Accrescent supports that now, don't know about the others.
Thanks! You're right, sideloading works. Just downloaded the Aurora Store Apk with Vanadium, installed it and now I can install Apps from Aurora inside Private Space. (But Aurora doesn't support the "Install button")
But would be cool to have something similar like the "Install available apps" feature for secondary users also for Private Space.
- Edited
Possible undesiderd behavior detected.
I have owner, profile B and profile C.
Inside profile B, in Settings > Notifications > Conversations it shows I made a "change" to an app that profile B shouldn't know exists, as it is only installed in profile C.
I checked Settings > apps > all apps and the app doesn't appear, as I believe should be.
Edit: just checked owner, and there's nothing there, completely empty
Is that ok?
The race condition between keyboard and fingerprint sensor when switching to profiles with fingerprint seems to be solved.
phnx These already required a reboot to kick in properly in many cases before Android 15.
@xxx The article you've linked is unsubstantiated. Journalists should not be reposting unverified claims from a few posts on social media and presenting it as an issue impacting many people. We don't want this kind of clickbait linked here.
Just updated and got this crash... Pix8a
Is it update related or am I hacked?
https://discuss.grapheneos.org/d/16654-hardware-crash-after-boot-libcso-liblogso-libbaseso
fid02 Not only profile C wasn't running, I haven't even started it since rebooting to install 2024102100.
And I also haven't made any changes to that app's notification settings since installing it over a year ago.
I've never seen "conversations" in Settings before. Is it a new a15 thing? All other "conversations" in this page are phone numbers from messaging apps, none of them are the apps themselves, this is the only case. And it even shows the app's icon.
Hb1hf I've never seen "conversations" in Settings before. Is it a new a15 thing?
Since Android 11, as far as I'm aware.
GrapheneOS The article you've linked is unsubstantiated
Sorry I didn' t know. So I asked here. I' m an enduser and no android expert. So the news was not true?
xxx it says in the article that they're aware of two users on Reddit who had bricked phones. If it was a widespread problem, there'd be a lot more people with bricked phones.
It's possible those two people did something unsupported or even just had hardware problems that showed up during a big update.