Oculus quest wifi adb

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

An app that enables wireless ADB from within a Meta Quest device without requiring a USB cable.

License

thedroidgeek/oculus-wireless-adb

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

Git stats

Files

Failed to load latest commit information.

README.md

An app that enables wireless ADB from within a Quest 2/Quest Pro VR headset.

This is done through the Android global settings provider (requires manually granting WRITE_SECURE_SETTINGS ).

Since the TCP port is random each time, parsing is done on logcat output ( READ_LOGS permission required) in order to display it within the app.

adb install app-debug.apk adb shell pm grant tdg.oculuswirelessadb android.permission.WRITE_SECURE_SETTINGS adb shell pm grant tdg.oculuswirelessadb android.permission.READ_LOGS 

After ADB wireless is enabled, a script can be used to automatically discover and connect to it with the help of the mDNS protocol.

This app now also has a tcpip mode, which allows unauthorized/insecure connections to come through — this however needs a computer to set up for the first time, so that the embedded ADB client can be authorized so that it can enable the mode by itself in the future.

This can be achieved by running the command adb tcpip 5555 from a computer, then activating ADB from within the app, with the tcpip mode option checked.

About

An app that enables wireless ADB from within a Meta Quest device without requiring a USB cable.

Источник

Connect ADB wirelessly to a Oculus Quest

When developing VR games and experiences for my Oculus Quest and Quest 2, I often wanna export an .apk file to the headset to check performance or just be untethered from my computer. Usually I transfer it using a Link cable (just a fancy USB 3 cable), but it’s a bit of a hazel having a cord connected all the time. But recently I learned you can connect through ADB using a WIFI connection!

Here’s the steps to connect to your Quest over WIFI:

(I also provide some .bat files for Windows user so you don’t need to type and remember this every time):

1. Connect your headset with a USB 2 or 3 data transfer cable (like the official Link cable), take on your headset and accept any incoming connection in your headset.
2. Make sure the headset and computer is connected to the same WIFI-network.
3. Get the IP address of the headset: In your terminal where you have adb(Android Device Bridge) installed (in Windows this is the Command Prompt), you can write adb devices to see if your device is conencted to your computer, and then write adb shell ip addr show wlan0 . After the text inetyou will see your device IP adress, ex 192.168.1.2 .
4. Now restart adb with port 5555: adb tcpip 5555
5. Lastly we want to connect the device to this connection: adb connect 192.168.1.2:5555 .

Now you can remove the cable and enjoy sending new builds from ex Unity to your device, cable free!

Bonus content:

Show IP address and connect it to ADB using TCP/IP using an interative .bat file

Make sure the path to your SDK platforms-tools is correct* (usually it’s just to change the Unity version to the one you have installed), and copy this code inside a text file and save it as “connectWirelesslyToAndroidDevice.bat” and put in your project or Desktop:

cd C:\Program\Unity\Hub\Editor\2020.2.6f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools\ && adb devices && adb shell ip addr show wlan0 set /p IpAddress=What is the devices IP address? adb tcpip 5555 adb connect %IpAddress%:5555 echo If no error, you may now remove the cable and close this window cmd /k

Now you can just double-click the file, copy the IP-address, paste it and press enter to confirm. Much faster then needing to write everything yourself all the time.

* This is so that you have the same ADB server running as Unity is using. If you ever seen this message, you know what I mean:

adb server version (40) doesn't match this client (41); killing. 

Источник

Oculus quest wifi adb

I’m trying to set up wireless ADB access to my Quest with no success.

I can connect via USB, I’ve got Developer Mode on, drivers installed, I can access files and sideload to it.

But setting up wireless access doesn’t work.

First, I can’t ping the wireless IP. Should it be responding to pings? I can ping other computers / devices on the network.

I’m on the same wireless network with the PC and Quest.

I set up the USB connection, start tcpip with port 5556 (tried 5555 and others too) and try and connect.

Sometimes it says «already connected to 192.168.0.16:5556 » and other times «failed to connect to 192.168.0.16:5556 «

Either way I get this when I show devices.

Any suggestions? I’d REALLY like to get this to work while I’m still traveling so I can cast to groups of people.

I can get wired USB casting working but I might as well have brought my wired Rift. 😐

EDIT: Something is wrong with the networking. using adb shell I can ping internet sites, I can ping the router (now that doesn’t work either), I can ping Quest’s IP, but I can’t ping any other device on the network. All other devices (Laptop, Phone, PC) can ping each other.

So the Quest can ping the router, a PC connected to Ethernet but NOT any device on wireless.

Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0

Well, after a million things, I manually added the Quest’s WLAN interface to my laptop’s ARP table, and now it works great.

Thanks for all the suggestions. I can’t explain why that worked though. I was sending pings from the Quest, that should have populated ARP tables.

More posts you may like

Related Meta Quest Virtual Reality headset Meta Platforms, Inc. Virtual reality Social media Information & communications technology Technology

Источник

Enabled ADB Wifi via a Smartphone or PC or Linux or Mac

You can use at least 5 methods to enable ADB wireless connection :

Via an Android Smartphone (2 possibilities)

NO USB CABLE SOLUTION (please read below the Youtube video) :

Via PC or Linux or Mac (3 possibilities)

1. Installer + Instructions (PC and Linux only) (in the download section) (in the download section)
2. Meta Quest Developer Hub (MQDH) It is easier to use than SideQuest and you can drag and drop an .apk and enable ADB Connection with only one action with this tool. You can see all your installed apps, manage images, videos, take screenshots and see metrics, view log and run command in the main screen

What is ADB ?

ADB is the basic tool for developers and all hackers who want to operate their Android device from a computer. It is part of the SDK (Android Software Development Kit). ADB stands for Android Debug Bridge. It is a bridge between the Android system and our computer, or more generally our Android device and another device. It allows developers (and others in the Android ecosystem) to communicate with their device through commands. Everything works on the client-server (or slave-master) model. adbd, the ADB daemon (background process) runs on the Android device and can receive commands from an ADB server, installed on a computer or other device, and thus execute them. In most cases, it is used through a USB connection. This is what happens when we plug the Meta Quest into our computer. The client (our headset), goes into debug mode and receives commands from the server (our computer and SideQuest), such as changing the resolution of textures via a Shell command.

You have to enable ADB wireless connection with a physical USB connection, via PC or Android Smartphone each time you complete reboot your headset in order QGO to apply correctly the profiles because the ADB modifications and daemon, which allow the headset to perform modifications are reset every time you complete reboot the headset AND the ADB daemon need to be waked up. SideQuest have the same problems when it is used wirelessly. It is the same for all Android devices such as smartphone and smartwatches or tablets running Android 10.

The Quest can’t wake up its ADB service on its own. Android works like that. The only way is for another device capable of executing ADB commands, to tell it, via a USB connection, to wake up its hosted ADB service. Android Debug Bridge works as master/slave. The master is the computer or smartphone and the slave is the Quest. The same goes for activating the ADB wireless service on a smartphone. A PC (master) must tell the phone (slave), via ADB commands, to wake up the phone’s ADB service.

QGO uses a local ADB loop to call itself. It therefore emulates a PC call by pretending to be a PC. This is the reason why you can turn off your PC/Smartphone after waking up the ADB service in the quest.

ADB wireless mean the PC or smartphone can send ADB commands to the headset without to be plugged. How QGO use ADB is that by enabling wireless connection, it wakes up the embedded QGO ADB service loop back on the Quest and thanks to that, the Quest is capable to send commands to himself without the need of a USB cable. Quest just call himself and simulate PC or Smartphone command.

==> UNFORTUNATELY THERE ARE NO WORKAROUND. IT IS AN ANDROID LIMITATION

Waiting for the root access on the device could be a game changer, or waiting for Android 11 to bypass USB wired connection. You can also keep your headset in standby mode.

Get Quest Games Optimizer

Quest Games Optimizer

Use and create graphics and performance profiles by applications for your Quest 1 / 2 / Pro

Источник