Are you able to connect via adb now? This solves the problem:
adb shell pm clear com.oculus.vrshell
v83 is a full of never-solved bugs, some of them open for a very long time and so far no updates from Meta, who doesn't even read this forum. My only suggestion is to get out of PTC like I did and hope these bugs won't be present in live firmware (which is likely).
Star.Knight v83 is definitely buggy, all PTC releases are. They're never solved until the public release arrives when hopefully the vast majority will be solved. If you feel unhappy about that don't join the PTC program and stick to final releases. As a PTC participant, your device is a guinea pig for testing. You are right that Meta software developers are unlikely to be reading this forum......That's what the bug report option within the headset is for. You need to understand the process involved in developing firmware and software. If you don't understand what you're getting yourself into, you should not be in it.
The headset would not allow me to file a bug report because of the bug I was explaining. I've since reported the bug via the Horizon App instead.
I really appreciate responses from people who will try to help even though it's not their job instead of making assumptions and trying to belittle people they've just met. Please don't respond again.
I've seen eternal Meta bugs long enough to know your gripe is valid but it doesn't help me right now.
Why are you torturing yourself with using PTC software and then moan about it. Leave the program. PTC will be full of bugs. If you can't take the heat, get out of the kitchen. 😉 There is only one person responsible for your problem.....You.
I wasn't blaming anyone for anything except being unhelpful. You're now taking the unhelpfulness even farther into harassment territory.
