Update: So I found the fix for both issues. The one is simple.
If you are prompted to allow access to the file system but nothing comes up you need to go into device manager and totally uninstall and delete the oculus ADB driver.
If you aren't prompted at all the only fix I found was to Factory Reset the Oculus Go from the Oculus App and add it back. Upon doing that it worked when connecting to my PCs.
I saw that the Oculus Go can be connected to a PC for file transfer however every PC I connect it to no prompts come up and I never see the drive in my file system.
DK1 Order No: 574XX (US)
Status: Received
DK2 Order No: GP-1055XXX
Status: Received
CV1 Order No:6130000XXXXXXX
Status: Received
Oculus Go
Status: Received
0
Answers
Status: Received
DK2 Order No: GP-1055XXX
Status: Received
CV1 Order No:6130000XXXXXXX
Status: Received
Oculus Go
Status: Received
Status: Received
DK2 Order No: GP-1055XXX
Status: Received
CV1 Order No:6130000XXXXXXX
Status: Received
Oculus Go
Status: Received
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
I get the empty VR-Headset folder, and cannot copy any file to it (Dutch Windows message, something about device disconnected).
So what is supposed to appear there? Are there supposed to be precreated folders there already? I do not know what I should expect.
Also in what category in the Device Manager is this Oculus Adb Driver? I cannot find it. Does the Go need to be connected? I do find in device manager a 'VR Headset' under portable devices.
https://support.oculus.com/212288649367669/
Edit: Oh wait, you have to give permission within the Go, now I see a storage device, and in it many folders.
Up next: trying to get a video and 360 photo on this thing....
Awesome!
www.BeazleBee.com
www.KristinDragos.com
So for the heck of it I tried to recreate the problem and was successful in one regard. It appears that installing the Oculus ADB driver completely stops your ability to access the Go via Windows 10 filesystem. It will still prompt to allow within the Go but nothing becomes available. The second issue is with developer mode. When I turned on developer mode the Go stopped asking for access to the file system and no matter where I plug it in it doesn't work. I assumed the easy fix would be to turn it off however somehow the developer mode sticks. I turned it off within the app yet the Go still says it's on. I tried reboots, closing the app, and toggling multiple times yet it persisted until I wiped the Go again.
Hopefully this information help.
Status: Received
DK2 Order No: GP-1055XXX
Status: Received
CV1 Order No:6130000XXXXXXX
Status: Received
Oculus Go
Status: Received
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
I can confirm this is the same issue on MAC too. Once you turn on Developer Mode, you're no longer able to access the device to transfer files.
enable developer mode in oculus companion app.
uninstall oculus adb driver in windows device manager.
unplug go, replug go.
in prompt, tell windows to do nothing when this device is plugged in.
and now adb sees the go every time I plugin. thankyou!
https://developer.oculus.com/downloads/package/oculus-go-adb-drivers/
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
- In the Oculus app on your phone go to Settings
- Select Oculus Go XXXXXXXXXXXXXXX (serial number)
- Select More Settings
- Select Developer Mode
- Toggle Developer Mode Off (Windows Explorer should now see your Oculus Go, but you won't be able to navigate any folders)
- Toggle Developer Mode On (Windows Explorer will no longer see your Oculus Go)
- Put on your Oculus Go and accept the device connection confirmation (Windows Explorer should see your Oculus Go again, and you'll be able to navigate folders).
So it appears that somewhere between Windows 10 and the Oculus Go, when the Go is disconnected or powered off, the Developer Mode authentication is forgotten and needs to be reconnected. Not sure if this is a feature or a bug, but it is confusing.Hope this helps others.