Oculus 2 will not boot, possible sensor issue? Log cat included
Hello everyone. I apologize for such the low level question but I am not sure where else to turn. Out of nowhere, my oculus 2 stopped booting and is stuck on the logo. I know the proximity sensor was on the way out bc I would have to turn it off in the MQDH app in order for the screen to come on. But now, it is just stuck on the boot logo. I have not factory reset, because I do not want to lose connectivity to SideQuest and MQDH, but I have sideloaded the latest Firmware 63.0.0.146.363.566760361 via adb in the bootloader, but still the same issue. Any other suggestions? Thanks to all PS I have a more verbose logcat available however I did not want to attach here due to size restrictions. https://drive.google.com/file/d/1MemNFUiJ3-taw-i0BSZ1MDDEyj_YCqUI/view?usp=sharingCannot pass VRC.Quest.Performance.3 on a built Unity APK
We are struggling to hit the 4 second requirement for AppLab submissions in Unity 2019.4.7f1. Our app takes around 8 seconds to hit our empty scene except a canvas image and some text. Upon testing a sideloaded standard empty URP project with the Oculus SDK it takes longer than 4 seconds just to get into an empty scene with nothing but the default URP and Oculus SDK assets!! A splash screen seem to doesn't improve this at all either? - Worth noting that we are still needing to use the Legacy Oculus VR SDK as we need to remain cross-platform with SteamVR for the PC client. I was wondering how it's possible that apps like Superhot and Beat Saber have managed to have a logo above the three Quest loading dots. And if that's something we would be able to set up for our app and would be appropriate to meet the VRC.Quest.Performance.3 criteria? I have done much Googling for this and have come up completely short, this is completely stumping me so I hope someone can help!
