PTC v53 Release Megathread

Since updating to the PTC my Quest pro controllers have been simultaneously randomly losing tracking for a few seconds. This happens in the menus and games. Due to the previously mentioned inability to roll back I'm stuck with this problem until it is patched or I'm allowed to roll back by the looks of it.

I'm having similar controller tracking issues as others are reporting with the most recent v53 update.  In my case, I am also unable to connect to 6GHz wifi from my Google Nest Wifi Pro 6e router and have been troubleshooting that - but noticed that the controllers are communicating on the same channel as my wifi router and wonder if interference is causing the tracking losses/dropouts/etc. 

I don't have the ability to change what channels my wifi router uses, turn bands on/off, or have separate SSIDs for different bands which I suspect is at least one of the reasons I can't connect to 6GHz, but also wondering if this could be part of the controllers issue as well.  

Back to v51 from PTC v53. It made factory reset... I don't know why, but this problem (I posted before) was gone.

So probably PTC v53's bug?

Hello Ryanality,

I hope you are well!  I am curious if with the release notes of v53 going live and the blog post announcement stating v53 is beginning to roll out to devices, does that mean the build which was released Monday evening US time is the final version of v53, or will we expect another update still on the PTC?

I ask as right now I do not have any update available, have the v53 PTC release from Monday installed, but if I turn off PTC I am presented the option to downgrade to v51 in headset, showing v53 is not available to me on the stable channel.  I dont want to downgrade to v51, but also don't want to be thrust into whatever the next PTC cycle is (like I was with v53) before I understand if I want to or not.

Thank you!

Update to my post from Tuesday..

airlink 200 fixed still working perfectly (HEVC) sub 10ms encoding/trans/decoding

bumped airlink from 600 to 800 (h264) and still smooth, no hiccups pegged at 90fps, 10-15ms encoding/trans/decoding time.

*Note: you can check bitrate by using ODBT and select performance summary on the bottom then selecting oculus link below it (not link detail)

more importantly no lag spikes.

53.2 corrected my issues. hopefully it stays this way. 

also no more controller overheating notices.

OMG, if they are going to releas v53 to all users - it will be a disaster. This version still is terrible. With Wi-Fi 5 controllers keep disconnecting, Wi-Fi 2.4 gives a DFS warning (how the hell can it be if DFS is possible in Wi-Fi 5 only?).Now I understand why they skipped v52, and they should have skipped the v53 as well.

ever since ptc v51 my controllers dont do anything when tapping them together.  i have the switch in the experimental tab, so i assume the feature would have worked. i also notice that if you turn off auto switch it also turns off the double tap switch. i dont like the auto switch, but would like to use double tap. Can someone let me know if there's something I'm overlooking to make the double tap feature work?  thank you

There is a new setting that when switched on will turn on hand tracking by double tapping your controllers together. Seemed to work for me, but I ended up switching it back off.

I'm not currently able to launch Oculus Home. A while back, something happened that made the Home icon disappear from my dash bar. I found the Home2 exe file and was able to launch it that way, which actually makes an Unreal window pop up, when usually it doesn't put up a window on the desktop.

Still it was working, up until V53.

Does anyone know how to get the home button back onto my dash?

The blue dot flag for notifications often appears when there are no notifications listed in the related window. 

Accidentally took a picture in game tonight and the popup didn't fade away, even if I clicked on it and went into the photo section. I had to fully exit the game to get rid of it. The video recording popup works as expected/fades normally.

I am having to send my left Pro controller in for repair/investigation. The menu button on that controller no longer works as it should and can't be used to re-pair the controller to the app. I believe it may have been something in the firmware release prior to the latest one. I have seen other reports on reddit for left controller issues from people who are part of the PTC

Ryanality  I have found (and bug reported) a problem with v51 final and v53PTC with my Quest 2.  My headset battery will no longer charge above 88%.  The problem is that because of this the green (fully charged) light never comes on so I'm never sure when to take it off the charger.  My workaround right now is to use an external 20000mahr battery pack and this automatically stops the charge when it senses that the pack is full (88% in this case). 

The same thing happens with my Elite battery strap but at least its battery will charge up to 100%.  With my Elite battery strap my workaround is to use an external battery pack.  Once the external battery stops charging I just disconnect the Elite headset cable.  Next time I startup it always then shows the headset battery at 88% and the external battery at 100%.

I think that there is an android 12 bug effecting the Q2 battery management.  I don't see this problem with my Quest Pro btw.