Well, headset just updated to v59. The option for "MTP Notification" is enabled but no notification appears when connecting USB (official Link cable). MTP can be established with ADB commands at which time file transfers via Windows UI is possible.
Of course Meta's response will be to do a factory reset. These have always been a complete waste of time and solved nothing.
I am experiencing the same problem since today. Is there a way to check when my device was upgraded to latest version?
EDIT: I just discovered that my headset had entered DND mode (do not disturb) which failed the notification to pop up. I don't know if this is due to the update or if I somehow managed to trigger it myself by accident..
Do Not Disturb is disabled. No notification.
Do Not Disturb was enabled after the update but I disabled it before testing the MTP connection. The USB connection dialog stopped popping up on v57 for me and the Developer setting to enable the USB connection dialog was removed on my headset. I was hoping this would be fixed in v59 but no. The MTP notification setting is there but no notification appears.
As usual, it will probably take Meta at least three version updates (v62+) to fix this, if ever.
I had the same issue. I had to use adb command adb shell svc usb setFunctions mtp as a solution. I played around with the other settings to see how they act. The answer is "with zero logic!" for example even if you disable oculus link, you still get a popup to use it when you connect. I wish Meta starts taking care of such issues soon.
Thank you, adb shell svc usb setFunctions mtp worked. I was ready to factory reset
That did it for me! Thank you very much!
People keep telling me to use this fix but then never tell me where to actually put the command, please someone help
Press WIN button + X and select "Terminal" it will pop up a terminal window that accepts commands, Then connect your quest via USB to your computer and type in the adb shell svc usb setFunctions mtp command in that terminal and press enter, enjoy!
Put the Quest 2 on yesterday morning, message saying there is an update and to restart to apply. Check the App Library and notifications which doesn't show any app updates. Restart the headset in hopes the update will fix the lack of MTP notification. Nope. Just have to wait another six months I guess.
Hey there, NomadsAnIsland. While we know factory resets can seem scary or annoying to perform, they are actually best for clearing possible glitches or allowing updates to reflect on the device if not seen. With this concern, we do recommend completing a factory reset as well as reinstalling the PCVR app. Prior to doing so, please make sure your Cloud Backup is up-to-date to save as much game data as possible. Of course, if there are any issues, do let us know! We want to make sure you're all set!
MetaStoreHelp I understand that factory reset seems to fix everything. For example on my Quest-1, it was the only thing that fixed my tracking, but also I also ALL progress on so many games. Cloud backup is only supported by few games. BTW, the problem with the MTP affects both my Quest-2 & Quest-3. However, I use the adb command to bypass this.
Hey Synthercat! We truly appreciate you taking the time to share what has worked for you! Hopefully it'll also work for everyone else in the community who runs into this issue! In the meantime, we'll pass this along to our team for their review to hopefully see changes in future updates. We definitely want to make sure those hours on hours spent in VR are saved, as they hold so much value and your achievements.
As anticipated a factory reset solved absolutely nothing except lose all my Move statistics, some state settings of apps and waste 60+ hours to reload my apps and experiences (slow Internet). And thankfully I am not hit with the large/many file USB transfer bug plaguing many users (after 6+ months) and I can still reload my 167 GB of videos with the Link Cable via ADB.
I should have waited to see if the v60 update would fix the problem.
Update to v60 did not solve the problem either. Thankfully I am still able to use MTP transfers with ADB.
Hey there, NomadsAnIsland! We see you're having issues with your MTP notifications. No worries; we're here to get you back on track! We'd like to ask a few questions to get an insight on what troubleshooting you've done on your end.
Additionally, we'd like to suggest trying this:
1. Toggle off MTP notifications.
2. Perform a soft reboot of the device (power off, then back on).
3. Toggle on MTP notifications.
Please let us know if this helps; we look forward to tackling this with you!
1. Tried different PC. No MTP notification alert.
2. Genuine Oculus/Meta Link cable used.
3. DND is not enabled.
4. Tried the toggle and reboot. Still no notification alert.
5. Headset updated twice this morning (v60). Updates made no difference.
6. Transfers are still possible via Link cable, and MTP enabled via ADB.
7. I already tried a factory reset. I am not going to waste another 60-70 hrs (the amount of time it takes for me to reload my apps, games, experiences and videos transferred via cable).
I have the exact same problem... "12/06/2024" and still no fixes for theses issues ??????
It does work for me if I log into the ADMIN account on the headset, other accounts always just show the charging warning. (v72)
Not sure if this will help anybody out there but I had the same problem on my quest two, the most I was able to do was make the notification pop up but I wasnt actually able to interact with it, so my solution was to open the meta horizon mobile app and from there open the menu->devices->quest 2->headset settings->developer mode and enable the developer mode, if you have the setting enabled on both your headset and meta horizon app it should work, hope it helps someone.
If you bought Quest Games Optimizer you can use it to open the Android settings app. Once you enable developer options you can set the USB default to "file transfer". From then on your headset will attach as a MTP drive without any prompts at all.
QGO is a paid for app you have to sideload. Instructions on enabling developer mode on Android devices is readily found on the Internets.
14 versions and months later and the problem still exists.
I have been having this same issue with my vr for a week already, spoke to support for four days in a row and in the end they suggested I send the headset in for a replacement. I'll try doing that but I doubt they're going to actually give me a replacement headset or even check the adb issue to begin with, the most they will probably do is tell me nothing is wrong with it and send me it back.
It still tells me on command prompt that there are no adb devices detected even though I set file transfer as a default for whenever the usb is plugged in and I clicked allow file transfer...Any idea on why that might be?
Jake_Sully_Avatar have you tried using the QGO app to get the headset seen by the PC -
Re: Is there anyway to disable the need to verify ... - Meta Community Forums - 1099492
By the way, none of this was an issue before that update, they should have just not even touched anything ADB related.
