Skip to main content
NomadsAnIsland
Honored Contributor
November 7, 2023
Question

No MTP notification even when enabled.

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.

27 replies

mxnpips
New Participant
November 7, 2023

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..

NomadsAnIslandAuthor
Honored Contributor
November 8, 2023

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.

Synthercat
Participant
November 8, 2023

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.

    max325007
    New Participant
    February 20, 2025

    Thank you, adb shell svc usb setFunctions mtp worked. I was ready to factory reset

    NomadsAnIslandAuthor
    Honored Contributor
    November 11, 2023

    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.

    MetaStoreHelp
    MetaStoreHelp
    Community Manager
    November 16, 2023

    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! 

    If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
    Synthercat
    Participant
    November 17, 2023

    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.

    NomadsAnIslandAuthor
    Honored Contributor
    December 13, 2023

    Update to v60 did not solve the problem either. Thankfully I am still able to use MTP transfers with ADB.

    MetaStoreHelp
    MetaStoreHelp
    Community Manager
    December 13, 2023

    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.

    • Have you tried connecting to another PC?
    • What cable are you using to transfer files? (Please note that the charging cable that came with the headset isn't good for transferring data like that; it can transfer data but may be inconsistent.)
    • Is the DND (do not disturb) turned on within the headset?

    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!

    If you're the author of a thread, remember to mark a reply as the Accepted Solution to help others find answers!
    NomadsAnIslandAuthor
    Honored Contributor
    December 14, 2023

    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).

    FenneKOff
    New Participant
    December 6, 2024

    I have the exact same problem... "12/06/2024" and still no fixes for theses issues ??????

    Above all, I have the impression that the problems are piling up instead of being corrected, and I'm coming across problems that have already existed for 2 years. I've tested all the possible solutions over the last 2 years and all I can say for sure is that the next 2 years will be nothing but new problems piling up on top of the previous ones... It's good to offer updates with new content but it wouldn't be REALLY GOOD to think a bit about the BUGS that have been around for years!!!!
    Just look at the ratings for your new application, which is literally worse than the previous one. Can't even go to the settings cuz my headset is "not connected" to the phone (fun fact : IT IS CONNECTED THROUGHT BLUETOOTH) but I still can use mirroring thing, LMAO ?
      jpateftnt
      Participant
      January 6, 2025

      It does work for me if I log into the ADMIN account on the headset, other accounts always just show the charging warning. (v72)

      N0TInf3rnus
      N0TInf3rnus
      New Participant
      January 23, 2025

      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.

      NomadsAnIslandAuthor
      Honored Contributor
      March 13, 2025

      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.

        NomadsAnIslandAuthor
        Honored Contributor
        March 15, 2025

        14 versions and months later and the problem still exists.

        JakeSullyAvatar
        New Participant
        March 29, 2025

        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. 

        JakeSullyAvatar
        New Participant
        March 29, 2025

        By the way, none of this was an issue before that update, they should have just not even touched anything ADB related.

        Terms & ConditionsAccessibility statement