Unity doesn't find Quest for play & build (go-adb driver is installed).

Same Unity issue here.

Ok nevermind. 10 minutes with the Quest conected via usb C and suddenly windows recognized it.

What I find is that I forget that a window pops up in the headset asking for permissions -- I think you can tick a box to have it always connect so it stops asking in the headset. For side loading/deleting I've found this app useful, https://headjack.io/tutorial/sideload-install-app-apk-oculus-go-quest/#tool. Maybe others could suggest a better tool?

bcoyle said:

What I find is that I forget that a window pops up in the headset asking for permissions -- I think you can tick a box to have it always connect so it stops asking in the headset. For side loading/deleting I've found this app useful, https://headjack.io/tutorial/sideload-install-app-apk-oculus-go-quest/#tool. Maybe others could suggest a better tool?

Why didn´t you just use Unity for the Build?

Of course I'll do it that way if I'm working in Unity and have the headset on hand to push the build into. But others have been commenting on side loading apks and also for me I have another headset at home that I'll send builds to my home computer to sideload into that headset.

All good now.

I've also found that the quest will randomly disconnect after a while, it will no longer be in adb's device list. It's not sleeping or anything, this can be right after actual use. In that case, disconnecting and reconnecting the USB cable may fix it but more often than not the device itself needs to be restarted by holding down the power button and selecting "Restart" from the dialog that pops up.

This might be offtopic, but adb has a wirless mode. Did anyone manage to setup Unity/Quest to use the wirless mode for build&run?