Secondary profiles won't load

grphosc1x

I am a new user of grapheneos and have setup a brand new p8a with 1 primary and 1 secondary profile. Unfortunately, within days of setting up the secondary it will fail to load. This seems to happen gradually and get worse. Primary works fine without issue. I've tried deleting the secondary profile and creating a new one with no improvement. I have searched the forums and issue tracker but can't seem to find a cause or solution. Please advise. Thanks.

de0u

grphosc1x I am a new user of grapheneos and have setup a brand new p8a with 1 primary and 1 secondary profile. Unfortunately, within days of setting up the secondary it will fail to load.

Is it possible to describe in detail what "fail to load" means? What exactly goes wrong?

Is the secondary profile using the standard GrapheneOS launcher or some other launcher?

grphosc1x

de0u It is the same issue reported by others where the initial user screen (colored circle w/ human profile and text "switching to ...") displays but never proceeds to keypad-unlock screen. Instead it hangs for 20 seconds or so and then shows the graphene logo and ultimately reloads the primary user profile. This is not an issue every time but rather the majority of the time. Maybe 8 out of 10 attempts. I have not installed any other launcher.

de0u

grphosc1x Which unlock method is the owner profile using, also the secondary profile? PIN, passphrase, fingerprint...?

grphosc1x

Both use PIN.

de0u

grphosc1x If you look in the system logs, do you see either crash found in Issue #4661?

grphosc1x

I do get a crash report. Can I ask, is it safe to post it here or does it contain any private/sensitive information?

de0u

grphosc1x I do get a crash report. Can I ask, is it safe to post it here or does it contain any private/sensitive information?

If you are nervous, maybe inspect the first 10 lines or so for personal information and post that much, because that would likely be diagnostic. In general crash reports are designed to be ok to share. System logs are more likely to contain private information.

Note that I asked whether you have either crash that was already posted. If so, indicating which one would be useful even without posting anything.

grphosc1x

de0u OK sorry you're right. I've compared my report and it is very similar to the first one listed in the link.
Also, I did not check the logs as you asked. Please let me know if you need this information as well.

de0u

grphosc1x I've compared my report and it is very similar to the first one listed in the link.

The "Keyguard is not shown in 20 seconds" crash dump in the GitHub issue does not appear to me to contain any sensitive content. If you have a GitHub account and wish to post your crash dump there, plus the other details you've provided in this thread (recurrence; stock launcher; PIN in both profiles; etc), I think that would be reasonable. If you don't have a GitHub account I can make the post for you.

One other thing that might be helpful would be a list of the apps in the secondary profile.

grphosc1x

That would be really helpful de0u. I don't have a github account and would prefer to avoid creating one if it doesn't cause you too much trouble. As for the apps in the secondary profile, there are only 2 besides the defaults which I pushed from the primary when it was created. They are Orbot and Organic Maps.

de0u

grphosc1x Are you comfortable posting the crash dump here?

grphosc1x

Sure de0u no problem ...

type: crash

SystemUptimeMs: 48509176
Process: system_server
Timestamp: 2025-01-25 20:19:24.573-0500
Build: google/akita/akita:15/AP4A.250105.002/2025011500:user/release-keys
Crash-Handler: com.android.internal.os.RuntimeInit$KillApplicationHandler
Loading-Progress: 1.0
Dropped-Count: 0

java.lang.RuntimeException: Keyguard is not shown in 20 seconds
	at com.android.server.am.UserController$Injector.lockDeviceNowAndWaitForKeyguardShown(UserController.java:4168)
	at com.android.server.am.UserController.startUserInternal(UserController.java:1993)
	at com.android.server.am.UserController.startUserNoChecks(UserController.java:1834)
	at com.android.server.am.UserController.startUser(UserController.java:1788)
	at com.android.server.am.UserController.startUser(UserController.java:1747)
	at com.android.server.am.UserController.startUserInForeground(UserController.java:2106)
	at com.android.server.am.UserController.handleMessage(UserController.java:3523)
	at android.os.Handler.dispatchMessage(Handler.java:105)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at android.os.HandlerThread.run(HandlerThread.java:85)
	at com.android.server.ServiceThread.run(ServiceThread.java:46)

de0u

grphosc1x Thanks for providing the details! The report is here: https://github.com/GrapheneOS/os-issue-tracker/issues/4661#issuecomment-2614214529

grphosc1x

de0u Thank you I really appreciate this.

GrapheneOS

@grphosc1x Did you disable animations? That's known to cause a lot of upstream Android user interface bugs. The same applies to a lesser extent to using 3-button navigation instead of the default gesture navigation.

grphosc1x

GrapheneOS Did you disable animations? That's known to cause a lot of upstream Android user interface bugs. The same applies to a lesser extent to using 3-button navigation instead of the default gesture navigation.

No to disable animations and yes to 3-button nav. I have tried returning to gesture navigation and disabling animations in both profiles with no success.
I think it might be useful to reinstall gos and try creating a secondary user immediately with everything else left unchanged. This could confirm the cause is in fact a third party app or some change to the system settings.

grphosc1x

GrapheneOS Did you disable animations? That's known to cause a lot of upstream Android user interface bugs.

Could you please clarify whether it is disabling or NOT disabling that is a problem?

de0u

grphosc1x I believe disabling animations has been a problem in the past. But if you have made other UI changes, that would be good to know about.

grphosc1x

Thank you de0u, that is not what I had expected but good to know.
I do have an update that may be of some help. I deleted the secondary and created an new one. Without making any changes to the settings or installing apps the problem hasn't occurred even once. Now I'm going to make some changes one at a time and see if I can identify a cause. Will hopefully be back soon with something of value.