Bluetooth on ASUS K73SV - Firmware Bug

[Philipp87]

Update:

Code: Select all

philipp@ASUS-K73SV:~$ hciconfig -a
hci0:	Type: Primary  Bus: USB
	BD Address: 7C:5C:F8:A7:1C:D1  ACL MTU: 1021:5  SCO MTU: 96:6
	UP RUNNING PSCAN ISCAN INQUIRY 
	RX bytes:194797 acl:10088 sco:0 events:1226 errors:0
	TX bytes:35242 acl:84 sco:0 commands:849 errors:0
	Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH HOLD SNIFF 
	Link mode: SLAVE ACCEPT 
Can't read local name on hci0: Connection timed out (110)
philipp@ASUS-K73SV:~$ sudo service bluetooth status
[sudo] Passwort für philipp:            
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-05-15 20:53:58 CEST; 39min ago
       Docs: man:bluetoothd(8)
   Main PID: 637 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9330)
     Memory: 4.2M
     CGroup: /system.slice/bluetooth.service
             └─637 /usr/lib/bluetooth/bluetoothd

Mai 15 20:54:02 ASUS-K73SV bluetoothd[637]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSink/sbc
Mai 15 20:54:02 ASUS-K73SV bluetoothd[637]: Endpoint registered: sender=:1.32 path=/MediaEndpoint/A2DPSource/sbc
Mai 15 20:54:05 ASUS-K73SV bluetoothd[637]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSink/sbc
Mai 15 20:54:05 ASUS-K73SV bluetoothd[637]: Endpoint unregistered: sender=:1.32 path=/MediaEndpoint/A2DPSource/sbc
Mai 15 20:54:05 ASUS-K73SV bluetoothd[637]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSink/sbc
Mai 15 20:54:05 ASUS-K73SV bluetoothd[637]: Endpoint registered: sender=:1.43 path=/MediaEndpoint/A2DPSource/sbc
Mai 15 20:59:16 ASUS-K73SV bluetoothd[637]: No cache for F1:76:EE:A9:B4:E6
Mai 15 20:59:19 ASUS-K73SV bluetoothd[637]: bt_uhid_send: Invalid argument (22)
Mai 15 20:59:19 ASUS-K73SV bluetoothd[637]: bt_uhid_send: Invalid argument (22)
Mai 15 20:59:19 ASUS-K73SV bluetoothd[637]: bt_uhid_send: Invalid argument (22)

[Philipp87]

Today I wanted to show the problem to a colleague. I connected the laptop to the Internet via Bluetooth tethering and used my bluetooth mouse. Everything worked fine.

So I think, the combination wifi with bluetooth is a problem. ...

[kato181]

Ok lets try this command again since you have a new card..

Code: Select all

In terminal type in the following...
bluetoothctl
It should respond with the following...
Agent registered.

It should be now in root..
[bluetooth]#
Type in..
scan on
Should result in..
Discovery started
It should return with..
[New] Device (eg) F0:65:DD:67:55:09 Name of bluetooth mouse

Then type..
pair F0:65:DD:67:55:09
The results should say..
Pairing Successful

Then type..
connect F0:56:DD:67:55:09
The results should say..
Connection Successful.

Then type...
trust F0:65:DD:67::55:09
They result should say..
Trust succeeded

[Philipp87]

The mouse lost the connection after approx 10 minutes. Although it is listed as connected and worked.

Code: Select all

philipp@ASUS-K73SV:~$ bluetoothctl
Agent registered
[MX Anywhere 2S]# list
Controller 7C:5C:F8:A7:1C:D1 ASUS-K73SV [default]
[MX Anywhere 2S]# paired-devices
Device E4:FD:A1:AA:8C:C0 Handy Philipp
Device F1:76:EE:A9:B4:E9 MX Anywhere 2S
[MX Anywhere 2S]# show 7C:5C:F8:A7:1C:D1
Controller 7C:5C:F8:A7:1C:D1 (public)
	Name: ASUS-K73SV
	Alias: ASUS-K73SV
	Class: 0x001c010c
	Powered: yes
	Discoverable: yes
	DiscoverableTimeout: 0x00000000
	Pairable: yes
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0535
	Discovering: yes
Advertising Features:
	ActiveInstances: 0x00
	SupportedInstances: 0x05
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
[MX Anywhere 2S]# info F1:76:EE:A9:B4:E9
Device F1:76:EE:A9:B4:E9 (random)
	Name: MX Anywhere 2S
	Alias: MX Anywhere 2S
	Appearance: 0x03c2
	Icon: input-mouse
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00010000-0000-1000-8000-011f2000046d)
	Modalias: usb:v046DpB01Ad0003
[MX Anywhere 2S]# exit
philipp@ASUS-K73SV:~$ 

[Philipp87]

I saw an interesting behavior. When I first connect my phone, and then connect the bluetooth mouse, everything works:

Code: Select all

philipp@ASUS-K73SV:~$ bluetoothctl
Agent registered
[CHG] Controller 7C:5C:F8:A7:1C:D1 Pairable: yes
[Handy Philipp]# paired-devices
Device E4:FD:A1:AA:8C:C0 Handy Philipp
Device F1:76:EE:A9:B4:E9 MX Anywhere 2S
[DEL] Device 6C:9C:1C:76:86:6E 6C-9C-1C-76-86-6E
[CHG] Controller 7C:5C:F8:A7:1C:D1 Discovering: yes
[CHG] Controller 7C:5C:F8:A7:1C:D1 Discoverable: yes
[CHG] Device E4:FD:A1:AA:8C:C0 ServicesResolved: no
[CHG] Device E4:FD:A1:AA:8C:C0 Connected: no
[CHG] Device E4:FD:A1:AA:8C:C0 RSSI: -84
[bluetooth]# exit

[Philipp87]

Update:
I switched the kernel to version 5.13.0-41
On my system bluez 5.53 is installed. Currently I try to update to the newest version 5.64 following this description:
https://budimir.cc/2022/01/08/compile-b ... om-source/

[Philipp87]

Update:

I have updated bluez according to the mentioned instructions to 5.64.

Code: Select all

philipp@ASUS-K73SV:~$ bluetoothctl --version
bluetoothctl: 5.64

Unfortunately, the update did not solve the problem, that the bluetooth mouse stops working, although it is still displayed as connected.

Update II:
With logitech unifying software I also checked, if there is a firmware update for the mouse available. The mouse has the newest firmware: 013.000.00003

[Philipp87]

I created a dual boot system. On a second ssd drive I installed windows 11. I also bought a Logitech MX Keys keyboard, which can also be connected via bluetooth.

Initially bluetooth was not detected at all. So I manually installed the driver:
https://www.intel.com/content/www/us/en ... -3160.html

The bluetooth mouse and the keyboard do their job without any lag or error. So I guess the intel "driver" for linux is not correct. Does anyone know, which software I have to install? I found a Linux support page from Intel:
https://www.intel.com/content/www/us/en ... eless.html

Thank you!

PS: my wifi / bluetooth card: Intel Dual Band Wireless-AC 7260 - PCI Express Half Mini Card (7260.HMWWB.R)

[Philipp87]

Next steps? Check again the firmware?

https://www.intel.com/content/www/us/en ... eless.html

Thanks.