Multi-User Detection?

[cyclone018]

Hi,
I just wanted to say that your work is phenomenal, and your tools are great to use (especially in a pinch.)

However im having a slight problem... I have multiple users on one quest, and I am able to adb to all users without a problem. However I believe your program is always pointing and looking at user 0 (the admin user), I need the program to look at user 11 (a guest user, in which is where Beat Saber is installed.) Any suggestions to help fix this problem?

[Lauriethefish]

Hey.
So unfortunately, it's actually not possible (AFAIK) for ADB to modify files for any user but the main account on the Quest. This is why the functionality isn't yet implemented into MBF.

it would however make sense for MBF to detect and warn if a secondary account is detected, to explain the situation.

[cyclone018]

Hey. So unfortunately, it's actually not possible (AFAIK) for ADB to modify files for any user but the main account on the Quest. This is why the functionality isn't yet implemented into MBF.

it would however make sense for MBF to detect and warn if a secondary account is detected, to explain the situation.

Ah ok, that would be great thanks.

[antgiant]

I'm pretty sure ADB works fine on secondary accounts as long as developer mode is explicitly turned on for the secondary accounts too.

Any chance this will be revisited? I would really love to have this working on my secondary accounts too again.

[Lauriethefish]

Unfortunately you're mistaken. Developer mode is a global option for the whole headset. Even if it's enabled, ADB can't access secondary accounts - it can only edit files on the main account.

[antgiant]

You are correct. My mistake.

I spent some time tonight trying to figure this out and I appreciated your code being accessible it helped me test a few theories. (Sadly none of the theories I tested worked out.)

However, I did find one idea via ChatGPT I don't have the tooling set up to test out. ChatGPT's claim is that this technique should work

1. Create a minimal Android APK (app.apk) that runs your agent executable using Runtime.getRuntime().exec()
2. Push it into /data/local/tmp along with your agent and other files
3. Grab the secondary user id adb shell pm list users (we'll assume it was 10 for the remaining steps)
4. Install the APK as the secondary user adb shell pm install --user 10 /data/local/tmp/app.apk
5. Launch the installed app as the secondary user adb shell am start --user 10 -n com.example.app/.MainActivity

Theoretically, that should give you your agent running as the secondary user and therefore the ability to mod the secondary user's copy of BeatSaber.