Disable the "Controllers not connected" message
Hi, Please help. I developed an app that doesn't require controllers, hands, or gaze (just relax and watch). But after a while, the users get an annoying "(Right \ Left) Controllers not connected, press any key" popup message at each run. Is there a way to disable it through code or settings? (I am using Unity, OpenXR, and OVR) Thanks764Views1like0CommentsMeta Quest PRO will not pair, connect or anything after Factory reset
Hi Developer team I am reaching out here in kind of a desperation! At this point Meta has granted me a "Replacement" of the Meta Quest PRO, because in their opinion, I have recieved a faulty headset. However; they will require a return procedure of 8 - 12 days, and that is totally unacceptable to me, as I am on a tight deadline, with a client that travels very far to see the result of my work on the headset. SO ... in total desperation I would like to hear if someone has some advice to maaaaaybe make my headset work. If you have any thoughts on the matter, please let me know. I am desperat here. Here is what is going on: - I can not connect with either my controllers or my phone. Here is the settings, and what I have tried: - The phone and the headset is on the same Wifi network. I tried several networks and routers. - I have updated to the latest version of the app on the phone and the software on the headset. - I have restarted the phone several times and the headset several times - I updated the phones iOS to the latest version. (The phone is an iPhone 14 pro.) And the headset could not connect with the phone on the previous iOS version either. - I have reset the headset to factory settings. - When resetting to Factory settings, in the setup; it will not pair with either of the controllers. It will not connect to both of them in the setup for both. It will not connect with either of them individually. - Both the headset and the controllers are fully charged. - The Controllers are not showing green even thought they are fully charged. They will blink between blue and red and the light that indicates power, on the headset is kind of purple - I have tried to connect via Bluetooth on the phone. The phone can not see the headset. Sometimes it sees it for a short while and then it jumps of. The "i" - I have tried to connect via the app after resetting of Factory settings, with the "Pair your headset with Meta Quest app" and the 5 digits number. But I get a "Headset not found" after i put in the 5 digits, and have waited a long time searching for it. So ... any suggestions, or do I just have to eat the 8 - 12 days return policy? I have been in contact with Meta Quest support several times, begging and begging and begging for help and for them to do something to speed up the return process, since this is an extraordinary situation with a tight deadline and a client that will. be very unhappy if they travel from the other side of the world to have a cool VR experience and there is not headset to have the experience on. Thanks in advance. Have a great day, // Brokop609Views0likes0CommentsPairing to IPhone 6 , 6S , SE 1st gen isn't supported
Thanks to a support assistant Christopher R., I know the exact reason why pairing doesn't work on my phone. IPhones 6 and 6S are also having this kind of issue, and my IPhone SE (1st generation) has the same chip as IPhone 6S, so that's why. So, still, I have to wait for a friend to arrive so I can ask them for help which I hope will happen soon. Wondering if a software update will be released specifically to fix this bug in the meantime.786Views0likes0CommentsPairing Santa Cruz dev kit with Oculus App fails every time
I have a Santa Cruz dev kit from early 2018 (EAS-M10) and ever since the firmware updated OTA a week ago I have been unable to pair the device with the Oculus App on any iOS device I own (I don't have an Android device to try this with). I have tried: Turning bluetooth on and off on both iOS devices I tried this with (an iPhone X and an iPad Air 2) Restarting all devices Trying to follow the instructions in the pairing process exactly - ie turning off the Quest while it's plugged in, turning it on at the appropriate time, etc I tried leaving the Quest on over night to fully charge and hopefully do any more OTAs Tried factory reset via fastboot menu Tried ADB logcat to see what happens during the pairing process, and it seems like the devices are communicating via bluetooth but maybe some connectivity issues on the device? 03-21 19:48:24.531 1458 1767 W CompanionServer: No connection 03-21 19:48:27.200 1245 1723 I bt_btm_ble: btm_ble_resolve_random_addr_on_conn_cmpl unable to match and resolve random address 03-21 19:48:27.200 1245 1723 W bt_btm : btm_acl_created hci_handle=11 link_role=1 transport=2 03-21 19:48:27.528 1245 1723 W bt_smp : smp_br_connect_callback is called on unexpected transport 2 03-21 19:48:27.528 1245 1723 W bt_btm : btm_read_remote_version_complete: BDA: 5a-ab-aa-0d-aa-4e 03-21 19:48:27.528 1245 1723 W bt_btm : btm_read_remote_version_complete lmp_version 9 manufacturer 15 lmp_subversion 16910 03-21 19:48:27.528 1245 1723 E bt_btif : bta_dm_acl_change new acl connetion:count = 1 03-21 19:48:27.528 1245 1723 W bt_btif : bta_dm_acl_change info: 0x0 03-21 19:48:27.528 1245 1723 W bt_l2cap: L2CA_SetDesireRole() new:x1, disallow_switch:0 03-21 19:48:27.529 1245 1360 D BtGatt.GattService: onConnected() connId=5, address=5A:AB:AA:0D:AA:4E, connected=true 03-21 19:48:27.529 1245 1360 D bt_btif_dm: remote version info [5a:ab:aa:0d:aa:4e]: 0, 0, 0 03-21 19:48:27.529 1245 1360 E BluetoothRemoteDevices: aclStateChangeCallback: Device is NULL 03-21 19:48:27.529 1458 1470 D BluetoothGattServer: onServerConnectionState() - status=0 serverIf=5 device=5A:AB:AA:0D:AA:4E 03-21 19:48:27.530 1458 1470 I com.oculus.companion.server.BleModule: GATT Connected to device: 5A:AB:AA:0D:AA:4E 03-21 19:48:27.615 1245 1723 E bt_att : MTU request PDU with MTU size 517 03-21 19:48:27.615 1245 1723 W bt_att : Call back not found for application conn_id=3 03-21 19:48:27.615 1245 1723 W bt_att : Call back not found for application conn_id=4 03-21 19:48:27.615 1245 1723 W bt_att : Call back not found for application conn_id=6 03-21 19:48:27.615 1245 1360 D BtGatt.GattService: onMtuChanged() - connId=5, mtu=517 03-21 19:48:27.616 1458 1472 D BluetoothGattServer: onMtuChanged() - device=5A:AB:AA:0D:AA:4E, mtu=517 03-21 19:48:27.616 1458 1472 I com.oculus.companion.server.BleModule: Setting MTU to: 512 03-21 19:48:28.037 1245 1360 D BtGatt.GattService: onResponseSendCompleted() handle=42 03-21 19:48:28.099 1245 1360 D BtGatt.GattService: onResponseSendCompleted() handle=42 03-21 19:48:28.100 1458 2469 D CompanionBLEReceiver: Received HELLO Request 03-21 19:48:28.102 1458 2469 E com.oculus.companion.authentication.CertificateModule: !!!DeviceCert is null. Returning temp certificate!!! 03-21 19:48:28.157 1245 1360 D BtGatt.GattService: onResponseSendCompleted() handle=42 03-21 19:48:28.217 1245 1360 D BtGatt.GattService: onResponseSendCompleted() handle=42 03-21 19:48:28.276 1245 1360 D BtGatt.GattService: onResponseSendCompleted() handle=42 03-21 19:48:28.610 1245 1723 W bt_btif : bta_gattc_conn_cback() - cif=3 connected=0 conn_id=3 reason=0x0013 03-21 19:48:28.610 1245 1723 W bt_btif : bta_gattc_conn_cback() - cif=4 connected=0 conn_id=4 reason=0x0013 03-21 19:48:28.610 1245 1723 W bt_btif : bta_gattc_conn_cback() - cif=6 connected=0 conn_id=6 reason=0x0013 03-21 19:48:28.610 1245 1723 I bt_btm_sec: btm_sec_disconnected clearing pending flag handle:11 reason:19 03-21 19:48:28.610 1245 1723 W bt_l2cap: L2CA_SetDesireRole() new:x1, disallow_switch:0 03-21 19:48:28.610 1245 1360 D BtGatt.GattService: onConnected() connId=5, address=5A:AB:AA:0D:AA:4E, connected=false 03-21 19:48:28.611 1245 1360 E BluetoothRemoteDevices: aclStateChangeCallback: Device is NULL 03-21 19:48:28.611 1458 1472 D BluetoothGattServer: onServerConnectionState() - status=0 serverIf=5 device=5A:AB:AA:0D:AA:4E 03-21 19:48:28.611 1458 1472 I com.oculus.companion.server.BleModule: GATT Disconnected from device5A:AB:AA:0D:AA:4E 03-21 19:48:28.611 1458 1767 W CompanionServer: No connection 03-21 19:48:34.766 1835 2210 I OVRPlatform: [FBNS] ClientImpl.cpp:209 Failed to connect to the MQTT server (edge-mqtt.facebook.com:443): 15 Lookup error. 03-21 19:48:34.766 1835 2210 I OVRPlatform: [FBNS] ClientImpl.cpp:127 Received a CONNACK without valid credentials Happy non-informative screen I see till the end of time:2.2KViews0likes3Comments