How to get a user profile's unlocked status programmatically?

traveller

From what I understand, until the non-owner user is unlocked, its user data section if fully encrypted and all the apps are stopped.
For some reason though the

UserManager userManager = (UserManager) getSystemService(USER_SERVICE);
bool isUnlocked = userManager.isUserUnlocked(UserHandle.getUserHandleForUid(uid));

for the locked user's uid (or for any user's uid in general) always returns true.
Does anyone know what may be causing such response (I suppose this may be some older API that is just not functioning properly on Android 16?), and is there a more or less reliable way to detect whether the user's session is active or not?

This is a platform (system) app and I do have android.permission.MANAGE_USERS permission requested.

traveller

The UserManager's isUserUnlocked() method has the following comment:

     * Return whether the provided user is already running in an
     * "unlocked" state or in the process of unlocking.
     * On devices with direct boot, a user is unlocked only after they've
     * entered their credentials (such as a lock pattern or PIN). On devices
     * without direct boot, a user is unlocked as soon as it starts.
     * When a user is locked, only device-protected data storage is available.
     * When a user is unlocked, both device-protected and credential-protected
     * private app data storage is available.

on my pixel it behaves like the "direct boot" is not supported, however from what I understand on every device with the most recent Android direct boot is on? Or does it need to be switched on manually for the newly created user profile?

The same "always true" response i get from the isUserRunning(uid) call - even if the user with the uid was never switched to after reboot.

de0u

traveller I believe GrapheneOS includes Direct Boot. If not, then a rebooted device would not have access to, for example, Wi-Fi network passwords.

traveller

de0u thanks for your reply. Graphene indeed uses direct boot, just like normal Android.
The problem i was having was that there's a confusing naming in AOSP between uid and userid: uid includes an app identifier in it, and I was using a wrong function for getting UserHandle object (UserHandle.getUserHandleForUid() instead of UserHandle.of()).
Problem is solved.

P.S. I wasn't able to find any AOSP platform development community that is more or less alive - would anyone know any, apart from google groups suggested here which seem like barely active?

de0u

traveller I am not really in a position to recommend an Android development community... except maybe XDA?