System UI does not load after setting oculess as device owner, when unlock pattern is set

[antonioludusanu1]

After sideloading oculess, removing all accounts, setting oculess as the device owner and disabling telemetry, i gave the headset a restart, and on boot it shows the 3 loading dots infinitely, preventing the user from doing anything. I reset the headset and tried it again and the same issue happened.

[ikrowni]

I'm having the same issue on the quest 3.

[threethan]

This is concerning - I'll add a warning to the README.

If either of you have a chance, could you try restoring oculus and meta accounts after setting device owner and before restarting the device? (To see if this problem comes from removing accounts or from setting device admin)

[antonioludusanu1]

@threethan I've done some testing after posting this and it has nothing to do with the removal/restoration of the accounts, the headset only bricks if you set oculess as owner and have an unlock pattern set

[chicaneau]

hey @antonioludusanu1 et al, can anyone confirm if this issue is only occuring if you have an unlock pattern set?

[ikrowni]

hey @antonioludusanu1 et al, can anyone confirm if this issue is only occuring if you have an unlock pattern set?

I did a factory reset and tried again and it's working now. The only problem I'm running into now is that when I open discord and click a voice channel I can't click join because it's not on the screen. I can do a direct call to someone though.

[threethan]

hey @antonioludusanu1 et al, can anyone confirm if this issue is only occuring if you have an unlock pattern set?

I did a factory reset and tried again and it's working now. The only problem I'm running into now is that when I open discord and click a voice channel I can't click join because it's not on the screen. I can do a direct call to someone though.

This is an issue with the Discord app and not Oculess.
If you want less janky Discord and working Spotify, please use https://github.com/threethan/LightningLauncher, which does not require special privileges (device owner).

I've updated the readme and issue name, thanks for the additional info. I'll keep the issue open since it's still present, but I do not believe it is possible to fix.

[yodaluca23]

Does this occur if a pattern is enabled at all or only if it's enabled for unlocking specifically?