Oculus pro controllers won’t update
Hello. I have had my pro controllers for about a year. I’ve taken very good care of them and have always kept them charged. But just three days ago when I went to get on my quest 2 a notification popped up that said “controller update in progress” and it just disappeared. Now for the past 3 days I have not been able to use my controllers and every time I turn on my quest 2 it says “controller update in progress. The controllers lights don’t blink and I can still use the home button but the controller itself just won’t track at all. I’ve tried factory resetting my quest, updating controllers from phone app, unlinking and linking again, And none of it worked. If anyone could help me I’d really appreciate it.
Pro controllers refuse to update after V79 update on headset
I've run loops with the support team with no help so thought I would come to the forums I have a quest 2 and I have the meta pro controllers after the recent software update they've refused to update I've tried resetting them unpairing and repairing charging them and when nothing worked I contacted meta support which the guy told to me factory reset and guess what it didn't work so now I'm stuck with a factory reset headset that I can't start the set up on because I don't got working controllers because they still say they need to update I don't know how to fix it I don't got a computer that I can use and I don't have another headset that I can pair the controllers to is there anyway to fix this? since Meta support did not help at all
Weak haptics on Pro controllers + Quest 3 in v.78.1027 and 1030
Pretty much what title says - since update 78.1027, native apps had no or extremely weak haptic response. After updating to 1030, they now do have, but it still very weak. (Basically it is not possible to feel the vibrations in game like Beatsaber, breaking the immersion completely) I tried to solve this issue in the past (v.74) and only rollback to v.73 helped. Not the same annoying bug is back again. I honestly have hard time to understand how this can happen. (Disregarding completely different issue, that i have disabled autoupdates, and it updated to v.78 anyway). I did send the bugreport from quest.