01-20-2023, 07:40 PM
(01-19-2023, 07:47 PM)TheOldPresbyope Wrote: @romain
It will be interesting to hear what you come up with.
Here's more grist for your mill.
Start udevadm on an Pi4B running moOde 8.2.4 player---with BT controller enabled and Pairing agent turned on---and then scan, pair, and connect from my Pixel 6a phone.
Code:pi@m824p4b:~ $ udevadm monitor -s bluetooth
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[7994.513293] add /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:12 (bluetooth)
UDEV [7994.518096] add /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:12 (bluetooth)
When I then disconnect the phone I see the following two lines added, as expected
Code:KERNEL[8281.508354] remove /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:12 (bluetooth)
UDEV [8281.516595] remove /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:12 (bluetooth)
Contrast that with the output I get when I scan, pair, and then connect from another moOde 8.24 player (on a Pi3A+)
Code:pi@m824p4b:~ $ udevadm monitor -s bluetooth
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[8755.970141] add /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:11 (bluetooth)
UDEV [8755.974968] add /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:11 (bluetooth)
KERNEL[8762.224259] remove /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:11 (bluetooth)
UDEV [8762.227890] remove /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:11 (bluetooth)
KERNEL[8804.418090] add /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:12 (bluetooth)
UDEV [8804.423059] add /devices/platform/soc/fe201000.serial/tty/ttyAMA0/hci0/hci0:12 (bluetooth)
The first four lines (device hci0:11) appear when I paired, the last two lines (device hci0:12) appear when I connected.
Looking at the tail of /var/log/kern.log I see
Code:Jan 19 13:31:58 m824p4b kernel: [ 7994.402194] Bluetooth: hci0: ACL packet for unknown connection handle 12
Jan 19 13:31:58 m824p4b kernel: [ 7994.623526] Bluetooth: hci0: ACL packet for unknown connection handle 12
Jan 19 13:31:58 m824p4b kernel: [ 7994.651044] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:32:02 m824p4b kernel: [ 7998.108644] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:32:02 m824p4b kernel: [ 7998.227364] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:32:02 m824p4b kernel: [ 7998.228620] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:32:02 m824p4b kernel: [ 7998.381153] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:32:05 m824p4b kernel: [ 8001.229134] input: Pixel 6a (AVRCP) as /devices/virtual/input/input4
Jan 19 13:36:45 m824p4b kernel: [ 8281.530293] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:44:40 m824p4b kernel: [ 8756.639904] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:44:40 m824p4b kernel: [ 8756.658637] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:45:28 m824p4b kernel: [ 8804.635065] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:45:28 m824p4b kernel: [ 8804.653827] Bluetooth: Unexpected continuation frame (len 0)
Jan 19 13:45:29 m824p4b kernel: [ 8805.166811] input: m824p3a Bluetooth (AVRCP) as /devices/virtual/input/input5
Maybe my glasses are extra smudged today but I don't see a difference between my udevadm entries and yours. Are you proposing that there's something going on behind the scene?
Regards,
Kent
Kent,
for the while I'm stuck because enabling hciuart.service and serial interface didn't change anything to the actual situation :\ I have to do more researches
Romain
