New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Update: Found the Fix and possible reasons Oculus Go's will not connect to PCs for file transfer

kingzopekingzope Posts: 197
Art3mis
edited May 2018 in Support
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

Best Answer

«1

Answers

  • kingzopekingzope Posts: 197
    Art3mis
    Ok this appears to be a known issue now.  It would really be helpful if someone from Oculus would acknowledge this.  I now have a second Go on hand and the second one immediately asks if I'd like to make my files available.  I can choose yes and on my desktop nothing happens but on my laptop it shows VR device which I can access the file system.  My initial 64GB Go does not even give the prompt.  This is very inconsistent and others are reporting it.
    DK1 Order No: 574XX (US)
    Status: Received
    DK2 Order No: GP-1055XXX
    Status: Received
    CV1 Order No:6130000XXXXXXX
    Status: Received
    Oculus Go
    Status: Received
  • kingzopekingzope Posts: 197
    Art3mis
    DK1 Order No: 574XX (US)
    Status: Received
    DK2 Order No: GP-1055XXX
    Status: Received
    CV1 Order No:6130000XXXXXXX
    Status: Received
    Oculus Go
    Status: Received
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Interesting. I will share with the team.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • BlackBansheeBlackBanshee Posts: 15
    NerveGear
    edited May 2018
    Same problem.  Can't access the Oculus Go with my Windows 10 machine.  Have tried resetting via device manager and I even did a full factory reset on the Oculus Go.  No luck.  I can see the "VR headset" in windows, but when I click on it I just get an empty folder.
    Rocket Scientist and VR Junkie
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Can you please contact us? Thanks. https://support.oculus.com/
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • JoshuaJSloneJoshuaJSlone Posts: 61
    Hiro Protagonist
    Same problem.  Can't access the Oculus Go with my Windows 10 machine.  Have tried resetting via device manager and I even did a full factory reset on the Oculus Go.  No luck.  I can see the "VR headset" in windows, but when I click on it I just get an empty folder.
    A few others over at Reddit and I have run into the same thing-- VR-Headset showing, but appears empty and won't allow files to be copied.
  • sanderbossanderbos Posts: 94
    Hiro Protagonist
    edited May 2018
    Same for me (Windows 10 1803).

    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....
  • sanderbossanderbos Posts: 94
    Hiro Protagonist
    edited May 2018
    Quick follow up: So once I gave permission within the Go, I could copy mp4's to the Movies folder, and PANO 360 jpegs to the Pictures folder, and they immediately showed and worked in gallery accessible from main toolbar.
    Awesome!
  • JoshuaJSloneJoshuaJSlone Posts: 61
    Hiro Protagonist
    Hmm. For me it was only after giving permission within the Go that I saw the empty VR-Headset at all.
  • KdragosKdragos Posts: 19 Oculus Start Member
    My fix for this was to do a factory reset on the Go. I uninstalled the drivers. I didn't do the "Permanently allow this computer" thing. I resetup the Go and now it works fine (without the windows drivers). 
  • kingzopekingzope Posts: 197
    Art3mis
    edited May 2018
    Cyber this may be good info to pass along.

    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.
    DK1 Order No: 574XX (US)
    Status: Received
    DK2 Order No: GP-1055XXX
    Status: Received
    CV1 Order No:6130000XXXXXXX
    Status: Received
    Oculus Go
    Status: Received
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Thanks.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • sleepermmasleepermma Posts: 11
    NerveGear
    edited May 2018
    I installed Go ADB and now I can't access my GO through Windows 10 File Explorer.

    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.
  • qqqturingqqqturing Posts: 2
    NerveGear
    Just don't install the GO adb drivers they don't work... Install the samsung adb drivers, they work fine.
  • JoshuaJSloneJoshuaJSlone Posts: 61
    Hiro Protagonist
    OK, I can confirm the Samsung thing worked for me. I didn't do a factory reset on the Go (what a pain redownloading everything would be, so last resort). Went to Device Manager > Portable Devices, right clicked on VR-Headset and told it to uninstall device. Then downloaded and installed Samsung drivers from here from here. After this it again showed empty VR-Headset. But looking back in the Go it again asked for permission to do file transfers, and after giving it again VR-Headset in Explorer now showed "Internal shared storage", with all the folders within.

  • spiraloidspiraloid Posts: 7
    NerveGear
    factory reset go.
    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!
  • brianlasbrianlas Posts: 5
    NerveGear
    I would like to add my experiences with the Go to this thread. I am running the latest version of Windows 10, and have a 64GB version of Go. I have tried many combinations of Factory Reset; installing and uninstalling the Go adb and the Samsung adb; turning Developer Mode on and off; rebooting my PC, and only on a couple occasions have I been ever able to see adb report the Go as an attached device - usually the list of devices attached is blank. Also, I have NEVER seen the VR Headset folder in File Manager. At this point, I do not know how to proceed, and would greatly appreciate some help in getting all of this to work. Thank you so much!
  • preston.mccauleypreston.mccauley Posts: 35 Oculus Start Member
    I'm running into the same issue. I've uninstalled and installed, rebooted both and adb in unity doesnt pick it up.
  • BackendGamesBackendGames Posts: 3
    NerveGear
    I am also having the same problems. It is very frustrating. Actually returned my Go back to Best Buy. I thought it was a usb hardware problem on the headset. It worked for the first couple of times and then stopped working  No USB access to the Go and cannot now access files on the Go.. 
  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Can you try this new developer driver and see if that helps?
    https://developer.oculus.com/downloads/package/oculus-go-adb-drivers/
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • PeepinTheGamePeepinTheGame Posts: 9
    NerveGear
    Can you try this new developer driver and see if that helps?
    https://developer.oculus.com/downloads/package/oculus-go-adb-drivers/
    This did not help me :(
  • PeepinTheGamePeepinTheGame Posts: 9
    NerveGear
    I'm running into the same issue. I've uninstalled and installed, rebooted both and adb in unity doesnt pick it up.
    Have you figured this out yet?
  • Slydog43Slydog43 Posts: 5
    NerveGear
    This is a huge problem.  I'm not about to do a factory reset when that might not even fix it.  ADB drivers have always been troubling for me as I have developed for many android devices over the years, and it seems that adb has caused me so many headaches.  Come on Oculus, fix this now.  I tried the Samsung ones, but windows says it already has the best drivers.

  • cyberealitycybereality Posts: 26,156 Oculus Staff
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • ShozenShozen Posts: 2
    NerveGear
    I had the same problem but I fixed it by using a different USB cable than the one that was shipped with it.
  • omni_shankeromni_shanker Posts: 4
    NerveGear
    I was having this problem.  Fixed it by simply typing "adb devices", which starts the adb server of course.  Then it showed up fine.  My Go is in developer mode.  Perhaps this is normal for developer mode?
  • davegaltdavegalt Posts: 3
    NerveGear
    When I first got my Oculus Go, I connected it to my PC and transferred a 360 video, and everything worked fine. Now when I connect the Oculus Go to my PC it doesn't show up in File Explorer, and neither does the Oculus Go prompt me to accept the connection (it only temporarily displays the charging percentage) I tried this on a separate PC which I had never connected to before and got the same problem so I assume the issue is with the Oculus Go and not the PC's. Watching my own 360 videos was the main reason for buying the Oculus Go, so I'm very interested in getting this connection working again. I also bought Oculus Go's for both of my sons who want to use it for the same thing, so I hope there's a solution to this problem.
  • VMCVMC Posts: 1 Oculus Start Member
    edited August 2018
    I found this workaround that works pretty consistently for me:
    1. In the Oculus app on your phone go to Settings
    2. Select Oculus Go XXXXXXXXXXXXXXX (serial number)
    3. Select More Settings
    4. Select Developer Mode
    5. Toggle Developer Mode Off (Windows Explorer should now see your Oculus Go, but you won't be able to navigate any folders)
    6. Toggle Developer Mode On (Windows Explorer will no longer see your Oculus Go)
    7. 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.
  • yerneroyernero Posts: 2
    NerveGear
    VMC said:
    I found this workaround that works pretty consistently for me:
    1. In the Oculus app on your phone go to Settings
    2. Select Oculus Go XXXXXXXXXXXXXXX (serial number)
    3. Select More Settings
    4. Select Developer Mode
    5. Toggle Developer Mode Off (Windows Explorer should now see your Oculus Go, but you won't be able to navigate any folders)
    6. Toggle Developer Mode On (Windows Explorer will no longer see your Oculus Go)
    7. 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.
    Then how do I make everything work for developer mode? Im trying to upload my app but I need to authorize my device it thought?

«1
Sign In or Register to comment.