v63 - The wireless ADB debugging prompt shows a black screen.
Hi, Two tickets were opened here : https://communityforums.atmeta.com/t5/Get-Help/PTC-v63-The-wireless-debugging-prompt-does-not-appear-and-shows/m-p/1171644 and here https://communityforums.atmeta.com/t5/Get-Help/PTC-v62-The-USB-debugging-prompt-does-not-appear-when-the/m-p/1171979 But I was asked to post this here. To resume : On Q2, Qpro and Q3 (v62, v63) when the authorize WiFi debugging through adb prompt shows up, the Quest will first enter a black screen state. Then, we must click the home button on the right controller to make this window show. If I do not click the home button, it will remain in a black screen state. USB debugging prompt had same problem on v62 but it has been fixed on v63 thank to the new look/UI of the prompt. But the wireless debugging prompt have not been updated and still run into this problem. To fix the problem, Meta developers should update the wireless debugging prompt to the new look/UI.771Views0likes0CommentsBluetooth mouse problem after v62 update
The Bluetooth mouse was working correctly before Oculus v62 update but now whenever I move the mouse Unity receives it as an arrow key like this: if (Input.GetKeyDown(KeyCode.LeftArrow)) { // This shouldn't be triggered by mouse } Also sometimes I get this warning from InputMethodManager Warn InputMethodManager Unable to send input event to IME: com.oculus.vrshell/com.oculus.panelapp.keyboardv2.KeyboardInputMethodService dropping: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_DPAD_LEFT, scanCode=0, metaState=META_NUM_LOCK_ON, flags=0x400, repeatCount=0, eventTime=107623773, downTime=107623773, deviceId=-1, source=0x101, displayId=-1 } Looks like it's trying to send mouse movement as a D-Pad button. Has anyone else experienced this?464Views0likes0Comments