Forum Discussion
Solved
No Allow USB Debugging Dialogue Appears
I need help getting my Quest 2 to connect to my MacBook Pro via USB because, unlike this guy - https://neerajjaiswal.com/how-to-setup-for-quest-2-development-on-mac-using-unity-without-bootcamp, I can't get the connection to work.
I've followed the instructions in the link above, but just to summarise:
- I have verified my developer Oculus account, where I've set up an organisation for app' development
- I have the Oculus phone app', which has connected to my Oculus 2, where it's enabled developer mode
- The system settings on my Quest 2 show a developer section, and I've enabled the USB connection dialogue
- I've installed the Meta Quest Developer Hub (MQDH) and tried ADB drivers from Unity, Android SDK, Android File Transfer, and MQDH itself
- I can see the USB C cable connects because whenever I plug it in, I get an "extended battery" notification
However, the EFFING ALLOW DEBUGGING NOTIFICATION NEVER APPEARS. GRRRRR
Meanwhile, I've done a hard reset on the Quest 2 several times and bought three cables. I've also tried SideQuest.
I've installed large complex systems for a living, but I don't reckon anything has proved as effing difficult as me trying to get a simple USB connection between Quest 2 and my MacBook so I can create a VR scene running in Unity - HELP!
Aha! Well, this is embarrassing - I think the moral of the story is RTFM...
So it turns out I was plugging into the wrong USB C port on the headset - I was plugging into the extended battery that came with the headset I was given, whereas I should've been plugging into the USB C port on the headset itself. Now I've done that - huzzah!
Turns out, there was a clue in my original posting, as I said, "I can see the USB C cable connects because whenever I plug it in, I get an 'extended battery' notification"; if there was any support here, they might've picked up on that. Ah well.Anyway, whatevs - I can now see my Oculus in Unity - onwards and upwards!
7 Replies
Bump
Bump Bump
Same problem, bump
Bump, Bump, Bumpedy Bump
Okay - so I'm guessing there's no available help here because this is some system/software issue that no one other than the Meta Guys themselves can help sort (maybe through some patch or software update). So does anyone know how I can engage directly with the Meta guys? I've looked around, and it ain't obvious to me.
Just some background as to why I'm trying to get this thing working: this is my background research into a possible research project on student engagement at the university for which I work...Bumpedy Bump, de Bumpedy Bump /sigh
Aha! Well, this is embarrassing - I think the moral of the story is RTFM...
So it turns out I was plugging into the wrong USB C port on the headset - I was plugging into the extended battery that came with the headset I was given, whereas I should've been plugging into the USB C port on the headset itself. Now I've done that - huzzah!
Turns out, there was a clue in my original posting, as I said, "I can see the USB C cable connects because whenever I plug it in, I get an 'extended battery' notification"; if there was any support here, they might've picked up on that. Ah well.Anyway, whatevs - I can now see my Oculus in Unity - onwards and upwards!
