thedroidgeek
Autostart and activate adb after boot
Is it possible to run this app and activate wireless adb automatically after a new boot? Everything works fine until a reboot is done.
Does the Wireless ADB mode and .apk work with Meta Quest 3 headsets?? Perhaps a full demo of how to set all this up might alleviate the questions people have. I know I am very interested in having this work. This means I won't have to connect to my computer each and every time I load certain programs in my Meta.
Is it possible to run this app and activate wireless adb automatically after a new boot?
AFAIK That's not possible unless you have root perms.
Everything works fine until a reboot is done.
That happens because ADBs don't persist through reboots.
Does the Wireless ADB mode and .apk work with Meta Quest 3 headsets??
It works with any android device.
Perhaps a full demo of how to set all this up might alleviate the questions people have.
Paraphrasing the README:
- Download the APK
- Open command prompt and use
cdto change your directory to the place where you downloaded it - Connect your Quest to your PC through USB
- Execute the following commands:
adb install app-debug.apkadb shell pm grant tdg.oculuswirelessadb android.permission.WRITE_SECURE_SETTINGSadb shell pm grant tdg.oculuswirelessadb android.permission.READ_LOGS
- That's it
To enable the tcpip 5555 mode:
adb tcpip 5555(first-time needed only)- Go into the app, turn the
tcpip 5555 modeon and turn on ADB through it at least once with it on - You're done.
ok thanks @ShockedCoder, at least for USB connected adb it works fine after reboots.
Oh, you meant ADB in general? I thought you were talking about ADB in-context of the app.
And please disregard what I previously said about it only being possible with root, I was thinking about something else. Depending on your phone, it is possible to have the application to start on boot and there could be functionality in the app to check for a Wi-Fi connection to start wireless ADB.
However, while I'm not an expert in this field, in my opinion that would use a relatively large amount of juice to constantly check for a Wi-Fi connection to start wireless ADB in response to. But as it's as simple as opening an app and flipping a switch, I do not believe there to be a big enough incentive for somebody to implement this, so I would not hold my breath waiting for it.
If your issue is solved, then please close this issue, but if there's still something unclear, I'll be here to help.
This app only tells the system to enable the native ADB wireless functionality, so if triggered after boot (assuming you're already automatically connected to a WiFi network, which is a requirement to enable the service), it would show the system prompt to accept running the service in the current WiFi network, which would require wearing the headset anyway.
I therefore don't see a valid need for this feature, especially considering that a long USB-C cable would work a lot better for use cases where frequent reboots are needed.
