PTC v76 Release Thread

Upgrading to Android 14 supposedly gives lower latency for Bluetooth devices:

https://www.reddit.com/r/OculusQuest/comments/1g7f367/meta_connect_low_latency_bluetooth_coming_2025_w/

Contacted support about the charging issue. Apparently they still have no idea, even though myself and countless others have told them, and we have a 15 page thread on it among others. Yet at the end of our talk, they told me to use this forum to let them know of any bugs or problems. Lol. I don't know what they're playing at. 

I too tried to update to fix the issue but I'm still plagued with it. And with no abily to roll back to v72, my headset is perma broken. Also, I haven't been able to downgrade back to v74. Might have to manually factory reset. 

Moriarti4  upgrading to android 14 give you the opportunity to experience extra meta borkdates.

Has anybody used additional profiles with this PTC V76 update? I've currently got a support request open for V74 where additional profiles constantly display controllers and hand outlines in games as well as a phantom menu bar. Menu's in the home environment are also not always displaying, and performance is extremely laggy.  I've done multiple factory resets, tested on different headsets, and tried with different user profiles.

I've posted about it in the Get Help forum and other users are experiencing the same problem. It would be interesting to hear if anybody who was experiencing the issue on V74 has tested with this V76 release to see if the issue is still present

Can anyone try this on v76 for me?  Very simple screen shot with MQHD, 2 eyes.

With PTC V76 MQHD take a 2 eye screen shot. 

In v74 all the capture images and video recording images are rotated incorrectly + or - 20°.

In v72 they were ok.  Below: 3 screen shots.  Logo in v76 wrong, Skiing in v72 ok, proof OS version is 74 latest.

 I have a outstanding Meta Case #08093678 but no progress.

fails in OS v74 (taken in MQDH)ok in back in OS v72using latest OS v74

Meta Support requested I do a Factory Reset.  That did not help.  Of course it is a pain to backup, Factory Reset and the reload apps, settings.....

MisterC72  I suggest you only enable the security updates option on the update panel.  Then just manually update things yourself.  that's what I've done for a while now and seem to have fewer issues than some seem to always have.

I found a bug in version 76. When I connect or disconnect the mouse or keyboard using Bluetooth, the interface restarts, closing all programs. Logcat below:"

03-28 19:18:01.138 1997 2326 E bt_btm : packages/modules/Bluetooth/system/main/bte_logmsg.cc:105 LogMsg: no pending resolving list operation
03-28 19:18:01.224 1997 2326 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 3
03-28 19:18:01.224 1997 2326 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 4
03-28 19:18:01.224 1997 2326 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 5
03-28 19:18:01.224 1997 2326 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 6
03-28 19:18:01.224 1997 2326 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 10
03-28 19:18:01.224 1997 2326 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 11

Does anyone know if there is any way to drop out of the v76 PTC? Ive tried to leave it, but to no avail. It doesnt pop up in the headset, and since it updated android itself, I wonder if its actually possible? I was able to drop from v74 down to v72, but this one just doesnt trigger in the headset. And a factory reset didnt help. 

TomCgcmfc Suggesting to only enable security updates would be great in theory... if Meta didn't eventually require non security updates to be installed anyway, some time after they are released. That's what the "this update will be automatically installed on:" thing means; once that update is available, your current version has an expiry date and will be replaced with that version on that date no matter what you do.

This is the critical flaw with the way Quest updates are done. You kinda CAN'T hang back on a known good version for very long, because if the fix takes ages to come out, you'll be yanked onto that broken one automatically before a fix is available.

Hirothefox  I realize that with only security updates enabled is time X'd and will eventually get an auto update but this is usually ~1 month later.  So in theory, after a better stable version is out there.  I've had a lot fewer issues since only using this option, as well as un-enrolling in the quest headset PTC program.  Occasionally going in/out of the meta link pc app beta is no problem though imho.

Aside;  BTW, to properly un-enroll from PTC you need to change the settings with your smartphone app, then restart everything.