Xavier NX bluetooth connection issue

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hi Team,
We are trying to connect Xavier NX BT with a remote BT device. But as soon as the device gets connected, it disconnects just after that i.e. connection does not persist. I have tried the connection with multiple devices like my Linux laptop, cell phone, etc.

We are following the below procedure:

anycon@ubuntu:~$ hciconfig -a
hci0: Type: Primary Bus: USB
BD Address: 70:66:55:B1:4E:28 ACL MTU: 1021:6 SCO MTU: 255:12
UP RUNNING
RX bytes:964 acl:0 sco:0 events:47 errors:0
TX bytes:2195 acl:0 sco:0 commands:47 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: ‘ubuntu’
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Version: (0xa) Revision: 0x98a
LMP Version: (0xa) Subversion: 0x42f7
Manufacturer: Realtek Semiconductor Corporation (93)

root@tegra-ubuntu:/home/anycon# hcitool scan
Scanning …
F4:96:34:78:79:53 vvdn-pc
D8:9C:67:6C:11:C8 3059–HW–G

^C

root@tegra-ubuntu:/home/anycon# hcitool info F4:96:34:78:79:53
Requesting information …
BD Address: F4:96:34:78:79:53
OUI Company: Intel Corporate (F4-96-34)
Device Name: vvdn-pc
LMP Version: 4.2 (0x8) LMP Subversion: 0x1000
Manufacturer: Intel Corp. (2)

root@tegra-ubuntu:/home/anycon# bluetoothctl
[NEW] Controller 70:66:55:B1:5B:C4 tegra-ubuntu [default]
Agent registered
[bluetooth]# show
Controller 70:66:55:B1:5B:C4 (public)
Name: tegra-ubuntu
Alias: tegra-ubuntu
Class: 0x00000000
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0530
Discovering: no
[bluetooth]#

[bluetooth]# trust F4:96:34:78:79:53
Changing F4:96:34:78:79:53 trust succeeded

[bluetooth]# pair F4:96:34:78:79:53
Attempting to pair with F4:96:34:78:79:53
[CHG] Device F4:96:34:78:79:53 Connected: yes
[CHG] Device F4:96:34:78:79:53 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 0000112d-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device F4:96:34:78:79:53 ServicesResolved: yes
[CHG] Device F4:96:34:78:79:53 Paired: yes
Pairing successful
[CHG] Device F4:96:34:78:79:53 ServicesResolved: no
[CHG] Device F4:96:34:78:79:53 Connected: no

[bluetooth]# connect F4:96:34:78:79:53
Attempting to connect to F4:96:34:78:79:53
[CHG] Device F4:96:34:78:79:53 Connected: yes
[CHG] Device F4:96:34:78:79:53 ServicesResolved: yes
Failed to connect: org.bluez.Error.InProgress
[CHG] Device F4:96:34:78:79:53 ServicesResolved: no
[CHG] Device F4:96:34:78:79:53 Connected: no

[bluetooth]# connect F4:96:34:78:79:53
Attempting to connect to F4:96:34:78:79:53
[CHG] Device F4:96:34:78:79:53 Connected: yes
[CHG] Device F4:96:34:78:79:53 ServicesResolved: yes
Failed to connect: org.bluez.Error.InProgress
[CHG] Device F4:96:34:78:79:53 ServicesResolved: no
[CHG] Device F4:96:34:78:79:53 Connected: no
[bluetooth]#

###################################################################################
tried Connection with my mobile phone
[bluetooth]# trust F0:D7:AA:D4:C3:73
[CHG] Device F0:D7:AA:D4:C3:73 Trusted: yes
Changing F0:D7:AA:D4:C3:73 trust succeeded

[bluetooth]# pair F0:D7:AA:D4:C3:73
Attempting to pair with F0:D7:AA:D4:C3:73
[CHG] Device F0:D7:AA:D4:C3:73 Connected: yes
Request confirmation
[Spar1m[agent] Confirm passkey 789578 (yes/no): yes
[CHG] Device F0:D7:AA:D4:C3:73 Modalias: bluetooth:v001Dp1200d1436
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Device F0:D7:AA:D4:C3:73 ServicesResolved: yes
[CHG] Device F0:D7:AA:D4:C3:73 Paired: yes
Pairing successful
[CHG] Device F0:D7:AA:D4:C3:73 ServicesResolved: no
[CHG] Device F0:D7:AA:D4:C3:73 Connected: no

[bluetooth]# connect F0:D7:AA:D4:C3:73
Attempting to connect to F0:D7:AA:D4:C3:73
[CHG] Device F0:D7:AA:D4:C3:73 Connected: yes
[CHG] Device F0:D7:AA:D4:C3:73 ServicesResolved: yes
Failed to connect: org.bluez.Error.InProgress
[CHG] Device F0:D7:AA:D4:C3:73 ServicesResolved: no
[CHG] Device F0:D7:AA:D4:C3:73 Connected: no

[bluetooth]# connect F0:D7:AA:D4:C3:73
Attempting to connect to F0:D7:AA:D4:C3:73
[CHG] Device F0:D7:AA:D4:C3:73 Connected: yes
[CHG] Device F0:D7:AA:D4:C3:73 ServicesResolved: yes
Failed to connect: org.bluez.Error.InProgress
[CHG] Device F0:D7:AA:D4:C3:73 Connected: no

We have also followed these steps:

https://docs.nvidia.com/jetson/l4t/#page/Tegra%2520Linux%2520Driver%2520Package%2520Development%2520Guide%2Fasoc_driver.18.2.html%23wwpID0E0AV0HA

But this is also not working.

Kindly help.

3

Hi Team,

Kindly help us resolving this issue.

4

Hi Team,

We are currently stuck here. Kindly help us here.

5

WeChat Image_20200929202144
WeChat Image_202009292021441080×2400 59.5 KB

WeChat Image_20200929202158
WeChat Image_202009292021581080×1080 83.1 KB

I’m not sure what happend on your side. I just check with my NX. it works well.

The only thing I have done is update to ExecStart=/usr/lib/bluetooth/bluetoothd -d

6

@sparsh.srivastava

The rootcause of the failed of bluetoothctl is lack of pulseaudio-module-bluetooth

Pls try again after sudo apt install pulseaudio-module-bluetooth

7

Hi Alanz,
We have already tried " sudo apt install pulseAudio-module-bluetooth" but still facing the same issue.

PS. We are testing this scenario with command line, no x11 is available.
And we checked with “ps -aux” command that pulseaudio is running for “gdm” user. So is there any dependy of gdm here??

8

Hi, sparsh.srivastava

There is a version mismatch between gdm and pulseaudio-module-bluetooth.
If you can sucessfully install the pulseaudio-module-bluetooth.
Connect via bluetoothctl should work well.
You can check with
pactl unload-module module-bluetooth-discover
pactl load-module module-bluetooth-discover

9

Hi Alanz,
We have tried loading and unloading bluetooth-discover module on root terminal as well as non-root terminal:
pactl unload-module module-bluetooth-discover
pactl load-module module-bluetooth-discover
but facing connection refused issue.

Results are:
root@ubuntu:/home/anycon# pactl unload-module module-bluetooth-discover
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
root@ubuntu:/home/anycon# pactl load-module module-bluetooth-discover
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
root@ubuntu:/home/anycon# exit
exit
anycon@ubuntu:~$ sudo pactl unload-module module-bluetooth-discover
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
anycon@ubuntu:~$ sudo pactl load-module module-bluetooth-discover
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

10

Hi Alanz,
We have tried loading and unloading bluetooth-discover module on root terminal as well as non-root terminal:
pactl unload-module module-bluetooth-discover
pactl load-module module-bluetooth-discover
but facing connection refused issue.

Results are:
root@ubuntu:/home/anycon# pactl unload-module module-bluetooth-discover
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
root@ubuntu:/home/anycon# pactl load-module module-bluetooth-discover
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
root@ubuntu:/home/anycon# exit
exit
anycon@ubuntu:~ sudo pactl unload-module module-bluetooth-discover Connection failure: Connection refused pa_context_connect() failed: Connection refused anycon@ubuntu:~ sudo pactl load-module module-bluetooth-discover
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

11

Hi Alanz,

We checked again on the system GUI also. The device is able to send the files (as you have shown above). But the connection is not maintained, only pairing is done. There is no active bt connection so only sending is successful, receiving is not working.

We are testing this with the default SD card image (no changes are done from our side).

We are not able to resolve the issue, kindly help.