Skip to main content
Participant
August 23, 2026
Question

Quest Pro controller disconnect loop after update — root cause (rev 0x30, GkSync)

  • August 23, 2026
  • 5 replies
  • 258 views

My left Touch Pro controller disconnects/reconnects every ~10 seconds after updating to the latest OS, making it unusable — same as several other threads here (1369940, 1259627, 1337529, 1184642). I pulled adb logs from the headset and found the actual cause:

 

- The controller's radio is fine — the Wi-Fi link connects cleanly every cycle (handshake + DHCP ACKed).

- Version check passes (otaRequired=0, no update needed).

- But GkSync — the headset pushing config to the controller — fails every single cycle. ~10s later a watchdog drops the controller (disconnected detached update-required), then it reconnects and loops forever.

- Over 90s: my left controller = 8 GkSync failures / 7 disconnects; right controller, same headset = 0 and 0.

- The only hardware difference: broken left is HW revision 0x30, working right is 0x31. Same firmware on both.

 

It's not a dead radio and not reset-fixable — I tried controller factory reset (X+Menu), unpair/re-pair, Wi-Fi reset, and a full headset factory reset. No change. It's recurred across OS versions, always "solved" only by replacement.

 

If you're affected, please reply with:

1. Controller hardware revision (0x30? 0x31?) — small label in the battery area, or in the headset's controller settings.

2. Left or right controller.

3. Did it start right after an update?

 

If we're all on 0x30, this is a software regression Meta can fix.
Also filed on the Developer Feedback Center with full logs.

5 replies

Participant
August 24, 2026

I just started experiencing this issue after the update to the most recent update on August 20, 2026. I'm on GA and not PTC. I'm not on pro, I'm on Quest 3

 

 

Honored Contributor
August 24, 2026

That's not good. I see you've reported it as a bug so hopefully they'll fix it soon. 🤞🤞 

herve76Author
Participant
August 24, 2026

the recent update is broken. Please Meta, fix it.

Honored Contributor
August 24, 2026

Report it as a bug through the bug reporting tool on your headset if you haven't already.  It's not so likely that they'll see this. It seems to affecting others too, hopefully they'll fix it quickly. Good luck! 🤞🤞🤞🤞 

herve76Author
Participant
September 15, 2026

any update on this issue?