[Android 14] Switching between profiles is buggy

IksNorTen

Hello everyone,

Android 14 was updated this morning and I found an annoying issue when switching profiles.

First of all let me explain what worked before Android 14.

I have a PIN code + fingerprint on all my profiles.

Let's assume I'm on a secondary profile (I'll call it P2) and I want to switch on owner profile (P1) WITHOUT ending session. So I go to P1 and I juste have to use my finger to unlock (because the phone remembers I already unlocked it with my PIN code before), if I want to switch back to P2 I juste have to unlock with my finger too (for the same reason, phone remembers that I unlocked before with PIN).

So everything was fine.

Since update to Android 14, when I want to switch between profiles WITHOUT ending session It's ALWAYS asking for PIN CODE, for exemple if I go from P1 to P2 when I use my finger it says something like "PIN code required after rebooting" but I never reboot...

other8026

IksNorTen

I just updated today and my profiles are not logging out when I switch between them. Maybe double check to make sure your profile can run in the background.

While in the owner profile, go to Settings > System > Multiple Users > *select desired user* > Allow running in background.

Set this to "on" if it's off and try again.

[deleted]

IksNorTen Upstream issue:

https://discuss.grapheneos.org/d/5731-bug-fingerprint-unlock-disabled-after-profile-change/18
https://discuss.grapheneos.org/d/7875-grapheneos-android-14-experimental-release/64

IksNorTen

other8026 Still have the issue. Someone said that reinstalling grapheneOS will probably fix the issue. Can I reinstall it without deleting my profiles and applications on each profile ?

IksNorTen

[deleted] What is upstream issue ?

other8026

IksNorTen

If you choose to do a factory reset or reflash GrapheneOS, then no you cannot do so without wiping the whole device.

I have had the same issue you're describing (like related to the upstream issue dismount was talking about), but I've always been able to fix it by restarting my phone. Have you tried that?

I saw that they plan on releasing another build today to fix some minor issues people have been running into. Since today is the first day that Android 14 was pushed out to everyone running the stable releases you can imagine some small things have come up. Maybe your issue will be fixed in that update? Releases can take a few days to get to stable, so not sure how long you're willing to wait, although you can switch to alpha or beta if you'd like (instructions on how to switch to beta are on the website here).

[deleted]

IksNorTen In this context, it just means that the issue from AOSP upon which GrapheneOS is based. It means it affects stock Android too, so Google needs to fix it.