I fixed this, after months of research.
This is not an issue of bluez.
hidp/uhid really IS the problem. I don't know what makes a Linux decide to
load `uhid` or `hidp`, my "good" and "bad" Linux SSD are dd'ed from same
source, and they even have same partition uuid.
long story short, blacklist hidp and force load uhid kernel module, all
mice work happily now!
echo "blacklist hidp" | sudo tee /etc/modprobe.d/blacklist-hidp.conf
echo -e "# Fix BLE mouse issue\nuhid" | sudo tee /etc/modules-load.d/uhid.conf
cp --update=none /etc/bluetooth/input.conf{,backup}
sudo sed -ie "s:.*UserspaceHID=.*:UserspaceHID=true:" /etc/bluetooth/input.conf
then reboot.
On Fri, Jan 26, 2024 at 12:52 PM Terrance Hendrik <
terrance.hend...@gmail.com> wrote:
> Update 2024-01-26
>
> 1. It has nothing to do with GUI. In text mode the issue is the same.
>
> 2. it has nothing to do with DKMS, removing it changes nothing.
>
> 3. I swapped SSD between 2 computers, the issue goes with the SSD. So it's
> not a hardware issue
>
> 4. I `apt purge` bluez and blueman, removed /etc/bluetooth, then reinstall
> them, the issue persists.
>
> 5. I compared files in /etc/udev/rules.d and /lib/modules on both
> computer, they are identical.
> only difference is modules.dep*, modules.symbols* and extra dkms modules.
>
> 6. other info
>
> on the working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... blueman-manager[7228]: blueman-manager 18.32.55 WARNING
> ManagerDeviceList:396 _monitor_power_levels: Failed to get power levels,
> probably a LE device.
> ... kernel: input: MX Anywhere 3 Mouse as
> /devices/virtual/misc/uhid/0005:046D:B025.000D/input/input37
> ... kernel: hid-generic 0005:046D:B025.000D: input,hidraw5: BLUETOOTH HID
> v0.14 Mouse [MX Anywhere 3] on
> ```
>
> on the NOT working OS, connecting a logitech mouse has 2 syslog messages
> ```
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ... thWJ16P bluetoothd[7933]: src/service.c:service_accept() input-hog
> profile accept failed for F6:8C:E4:DD:B8:6B
> ```
>
> 7. Final Question:
> What else can affect the behavior between bluez and the kernel??
>
>
> On Fri, Nov 17, 2023 at 8:36 AM Debian Bug Tracking System <
> ow...@bugs.debian.org> wrote:
>
>> Thank you for the additional information you have supplied regarding
>> this Bug report.
>>
>> This is an automatically generated reply to let you know your message
>> has been received.
>>
>> Your message is being forwarded to the package maintainers and other
>> interested parties for their attention; they will reply in due course.
>>
>> Your message has been sent to the package maintainer(s):
>> Debian Bluetooth Maintainers
>>
>> If you wish to submit further information on this problem, please
>> send it to 1051...@bugs.debian.org.
>>
>> Please do not send mail to ow...@bugs.debian.org unless you wish
>> to report a problem with the Bug-tracking system.
>>
>> --
>> 1051432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051432
>> Debian Bug Tracking System
>> Contact ow...@bugs.debian.org with problems
>>
>
