Bug 208119 - 5.6.7 bluez don't show battery status on YiChip 1201 based bluetooth 4.0 mouses.
Summary: 5.6.7 bluez don't show battery status on YiChip 1201 based bluetooth 4.0 mouses.
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: linux-bluetooth@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-10 09:28 UTC by Pavel
Modified: 2020-06-10 09:32 UTC (History)
0 users

See Also:
Kernel Version: 5.6.7
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Capture (13.98 KB, application/octet-stream)
2020-06-10 09:29 UTC, Pavel 		Details
Bluez output (98.05 KB, text/plain)
2020-06-10 09:32 UTC, Pavel 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Pavel 2020-06-10 09:28:53 UTC 
I have a Rapoo m550 mouse based on YiChip 1201.

It has a battery service on Gatt, but no battery attribute.

Device ED:8E:0E:BF:E0:B8 (random)
	Name: RAPOO BT4.0 MS
	Alias: RAPOO BT4.0 MS
	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)
	Modalias: usb:v1235pAA22d0001
Comment 1 Pavel 2020-06-10 09:29:57 UTC 
Created attachment 289593 [details]
Capture
Comment 2 Pavel 2020-06-10 09:32:26 UTC 
Created attachment 289595 [details]
Bluez output
Note You need to log in before you can comment on or make changes to this bug.