I’ve been using it for around a year mainly for connecting my PS4 controller. I have paired the controller and I could connect it in headless mode right away.
About few days ago I couldn’t do that anymore. Whenever I was trying to connect it was unsuccessful. After trying to connect for about 3 mins it can connect sometimes. (after trying non stop)
I have done a test where I have plugged in the display to see Bluetooth settings as it connects. It appears that they connect for half a second and immediately disconnect. (the on/off switch in main Bluetooth settings for this device).
Also the task bar Bluetooth symbol disappears and comes back with a lock on (like when it worked) and then immediately disappears again and Bluetooth symbol with no lock appears.
I have further tested:
Different Controller
Ordered a new WiFi/Bluetooth module
Got a different SD card and loaded up a fresh JetPack 4.5.
Prior to this incident I haven’t done anything remotely close that would cause this issue. It’s for my final year project in my university and I don’t have any idea what else I could try.
1st part - on JetPack 4.5 there is a bug in nvargus-daemon and it crashes. (something I will try to fix later)
2nd part - for some reason ps4 controller needs to be reseted when pairing between different versions of JetPack (I’ve tested this on 4.5 and 4.4). 4.4 works flawlessly so far
maybe it’s to do with ubunut 18.4 update for Bluetooth manager
Even though the topic says “fix inside” and marked as “solved”, I do not see a fix for the issue. Was you able to find a solution? I am using the same 8265 module and my issue was caused by upgrade to JetPack 4.5 too.
With JetPack 4.4 my Bluetooth keyboard with touchpad worked as expected: pairing without errors, after turning off and on it automatically connected. After upgrade to 4.5, it stopped working well. After pairing it fails to connect automatically, but I can connect it manually if I activate pairing mode on the keyboard and then choose connect from the menu in Bluetooth devices. Without the keyboard and touchpad, I cannot control the cursor, so I have to use VNC or ssh connection to get my keyboard and touchpad working by manually connecting after switching the keyboard with touchpad to pairing mode. If I do not use the keyboard for a while, it disconnects and never connects automatically again. But it seems it tries to connect automatically but fails, here is the log after the keyboard is turned on (since it is paired and trusted, it should have successfully connected but it did not):
Mar 1 08:12:46 jetson bluetoothd[4931]: src/adapter.c:connected_callback() hci0 device 54:46:6B:17:38:FA connected eir_len 5
Mar 1 08:12:46 jetson bluetoothd[4931]: src/device.c:device_set_class() /org/bluez/hci0/dev_54_46_6B_17_38_FA 0x000540
Mar 1 08:12:47 jetson bluetoothd[4931]: src/adapter.c:dev_disconnected() Device 54:46:6B:17:38:FA disconnected, reason 3
Mar 1 08:12:47 jetson bluetoothd[4931]: src/adapter.c:adapter_remove_connection()
Mar 1 08:12:47 jetson bluetoothd[4931]: plugins/policy.c:disconnect_cb() reason 3
Mar 1 08:12:47 jetson bluetoothd[4931]: src/adapter.c:bonding_attempt_complete() hci0 bdaddr 54:46:6B:17:38:FA type 0 status 0xe
Mar 1 08:12:47 jetson bluetoothd[4931]: src/device.c:device_bonding_complete() bonding (nil) status 0x0e
Mar 1 08:12:47 jetson bluetoothd[4931]: src/device.c:device_bonding_failed() status 14
Mar 1 08:12:47 jetson bluetoothd[4931]: src/adapter.c:resume_discovery()
I confirmed with bluetoothctl that it is trusted and paired. So far I haven’t found any workaround. The issue is still present after upgrade to latest JetPack 4.5.1.
For me Bluetooth does not work properly at all but it has different issues with each device. For example, with keyboard/mouse the issue is that it does not connect automatically (this is regression and used to work perfectly in JetPack 4.4 but stopped working in JetPack 4.5, I tried to reinstall twice to be sure). This makes Bluetooth keyboard unusable since I am forced to use USB keyboard and mouse anyway in order to manually connect Bluetooth keyboard/touchpad. With headphones, it is stuck in low quality headset mode and I cannot switch to high quality A2DP mode. As it is right now, it is almost like not having Bluetooth at all. If there is anything I could try, please let me know.
Connect and pair it as usually. It will work at first.
Turn it off and back on, or reboot Jetson Nano. Bluetooth keyboard/touchpad will not work connect automatically with JetPack 4.5 (with JetPack 4.4 it worked as expected).
With Bluetooth headphones the issue is even worse because they do not work properly at all. My guess the issue would be reproducible with any Bluetooth headphones with built-in microphone. They will be stuck in low quality audio headset mode and will refuse to switch to A2DP mode which is necessary to actually hear good quality audio. It does not matter what method to switch to A2DP I use, both in GUI or in command-line, it just does not work. I can try to get more debugging information later (when I figure out how; right now I’m not sure exactly how to debug this).
in my case it is a sony ps4 controller with jetpack 4.5.
It connects for a second and disconnects.
I should try atleast 5 times to get it connected.
This problem does not occur in jetpack 4.3 when i tested. please confirm
thank you
i must confirm that ps3 controller behaves just the same as ps4, with the complication that it never completes the connection, the status keep jumping from connected to disconnected and, of course, it never works (if not connected via usb)
If I pair my Microsoft BT Notebook Mouse 5000 and my Apple Wireless BT Keyboard from the Ubuntu desktop, the connection is stable. But after a reboot, the devices seem to connect and disconnect within a second whenever activated (e.g. when the mouse is moved). The following can be seen in the syslog while physically moving the mouse:
But after a reboot, the devices seem to connect and disconnect within a second whenever activated (e.g. when the mouse is moved). The following can be seen in the syslog while physically moving the mouse:
Can more people here confirm that this issue requires a reboot? And if this issue is only happens on jetpack4.5?