I've had this on my Quest 2 since v76. They've refused to officially address it and I've tried a lot to fix it on my end. Going as far as to buy another USB-C ribbon cable and install that. It's not your cable, it's not the USB-C connector, it's their firmware.
Hey there, thank you for contacting Meta Quest Support!
We understand that Quest Link issues are holding back your Metaverse experience, and we're keen to help sort out your performance problems! First of all, please ensure that your headset's software, Quest Link app, and PC drivers are up to date, as each update will come with it's own fixes and may help with your software issues.
If you have completed all of your updates, and the problem is persisting, please try the following process to see if this helps!
We hope this helps, but if the problem persists, we recommend getting in touch with over Private Message as we'll need to gather some more details about your PC build, and we can see what options are available!
Okay, so... first off OVRService is not the name of any Windows service... There's Oculus VR Library Service and Oculus VR Runtime Service.
Oculus VR Runtime Service was originally set to automatic and I set it to manual because I am sick of the invasive run all the time route Meta has taken. I humored this step since I already knew this wouldn't affect the tearing/stuttering in the slightest. The client will maybe always start on launch as opposed to it sometimes going into an infinite loading loop now, but it sure as hell did not resolve the tearing/stuttering. Second, even if this does have any affect on the UNRELATED link launch issue, why is this change not even in the PTC for link?
And third... There's no way in hell I am doing private messages with support. Either you tell your entire community how to resolve issues in these threads, or I ain't communicating with support at all.
Hello there, thank you for trying those steps and getting back to us.
We understand that you would like transparency with your troubleshooting, but to help with your issue, our team would most likely need to collect some logs from your computer, to fully diagnose the problem. So, that is why we would require you to contact our support team privately, so that we can get those logs and give you the best advise possible for your issue.
