-
Notifications
You must be signed in to change notification settings - Fork 8
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesnt connect wirelessly IP #9
Comments
Wireless adb cannot be installed without running adb tcpip 5555, sorry, but this is how Wireless adb works on Quset (it works in Meta Quest Developer Hub). |
Fixed in 62e59e0 |
ZeroConf doesnt work, only old way working and wont start ADB or connect by ADB. all getting is failed connect ADB error no other errors. |
Have you tried installing an addon for this? (And try update headset firmware to v55) |
i check if my headset is v55 but apk already installed |
partly my update is v54 and no update for v55 |
Have you run the app on the headset at least once? |
yes but when run it auto closes |
Well you can try this as alternative https://github.com/thedroidgeek/oculus-wireless-adb |
i managed got update v55 but still doesnt work on app |
but havent tried that other app yet |
I'll try to fix my app, I reinstalled it and it too started to close after launching |
I rebuilt the app, hope it works https://github.com/Sergey004/Quest2-VRC/releases/tag/New_Addon |
Reopen if you need |
Now is 100% working even on non Quest device |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
it doesnt connect wirelessly without been cable plugged in PC. i did all ADB connections and fully connected. but app doesnt see wireless and forcing use link cable on checks.
not sure pose do that, but pose be wireless supported too.
i normally use wireless connection since my PC doesnt keep my headset full charged. even since has type-c port supported
The text was updated successfully, but these errors were encountered: