Skip to content

Seems not working anymore on Quest 2 v76 #7

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

Closed
crazymonster999 opened this issue May 12, 2025 · 7 comments
Closed

Seems not working anymore on Quest 2 v76 #7

crazymonster999 opened this issue May 12, 2025 · 7 comments

Comments

@crazymonster999
Copy link

Hello,

I'm using your Oculus Wireless ADB tool to enable Wireless ADB for scrcpy usage. It was working like a charge for few months.

Wireless ADB functionality is no longer working on my Meta Quest 2.
Once I try to enable with or without 5555 option, the app doesn't display anymore the headset IP, but a "-" instead.
You can find a screenshot here

I identified this issue on v74, and I tested updating to v76, even after troubleshooting steps:

  • Factory reset
  • Fresh install of both Quest Game Optimizer and Oculus Wireless ADB
    I re-enable the wifi adb using SideQuest from USB connection first. However the app still not works.
    I also tested to install Termux and it opens well, but the launch of adb tcpip 5555 doesn't works

Please note that your app works well on my Quest 3, v74 (I did not upgraded it to v76).
Let me know if you need more logs or anything that can help to diagnose and solve this issue.

@zengqf1985
Copy link

I also encountered a similar problem.

@bossman90
Copy link

+1

@Dnw1
Copy link

Dnw1 commented May 19, 2025

+1, Had to use LADB as an alternative for project since ow-adb stopped working after Quest 74+

@thedroidgeek
Copy link
Owner

Hi, thanks for letting me know. I'll troubleshoot this when I get a chance.

@cgapk123
Copy link

Is it possible to add a wireless pairing code method similar to Quest Games Optimizer or QGT for pairing? And a separate game optimization solution?

Quest Games Optimizer or QGT are all commercial software, and there is currently no open source free Quest optimization APP program

@thedroidgeek
Copy link
Owner

From an initial look I took, it seems that the issue comes from a change in Android that adds the requirement of explicit consent from the user every time an app tries to read logcat (even with the permission manually granted via ADB):

Screenshot_20250522-154056~2.png

For some reason this dialog fails to open on the Quest - there's a mention of the activity name in logcat but nothing actually shows up.

I will have to do more digging and see what change should be introduced in order to detect the port more reliability.

@thedroidgeek
Copy link
Owner

I released 1.3 with mDNS port detection and completely ditched logcat, works fine on my Quest 3, let me know if there's any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants