Developer settings and USB debugging on User Profiles

gos_pixel_4a5g

Hey fellow GOS user!

I am trying to enable ADB Wifi on a non-owner profile. and I am unable to find the developer options. I do not have a non-GOS device on hand to test.

Can someone please confirm if developer options and USB debugging is disabled for user profiles? and whether it is a GOS feature or stock android behavior.
Also I would greatly appreciate if someone can provide a solution to toggle it back on for a user profile.

Thanks.

flawedworld

Developer options can only be managed from Owner, and are device-wide.

gos_pixel_4a5g

flawedworld
Thank you for clarifying this.

Is there any way to enable USB Debugging for a user profile then?
I'm trying to give Tasker ADB Wifi access when it is installed on a user profile.

flawedworld

It's device-wide

gos_pixel_4a5g

flawedworld
I have USB debugging enabled from owner profile but running any ADB shell command from user profile using Tasker says:
"USB debugging not allowed. The user currently signed in to this device can't turn on USB debugging. To use this feature, switch to the primary user."

Maybe its a Tasker issue and it tries to always check USB debugging status before executing ADB commands. In that case its irrelevant to ask here.

f13a-6c3a

You need specify a user id in your adb command

gos_pixel_4a5g

If I'm understanding correctly, ADB commands can only be executed by the primary/owner profile but an additional user id can be provided in those commands to manipulate other user profiles.

I was looking for a way to perform ADB commands from the user profile instead. But that fails because USB debugging is not enabled for that user profile.

I have Tasker installed on both the owner and the user profile. And Tasker has the ability to send and intercept intents.
Will owner profile receive intents from the user profile and vice versa if I were to try and send ADB commands(through intents) from user to owner for execution? My gut says NO as inter-profile communication should be extremely limited in GOS but maybe the owner profiles' Tasker can hack its way thanks to ADB and communicate with the non-ADB Tasker...

Any thoughts or ideas? : )

indiDing

It´s not a issue with tasker. I was facing the same issue -> "USB debugging not allowed. The user currently signed in to this device can't turn on USB debugging. To use this feature, switch to the primary user." The trick which did it, was to check "Always allow this computer ..." when connecting with adb on the primary profile.