On Thu, 2026-05-14 at 23:46 +0930, Tim via users wrote:
> On Thu, 2026-05-14 at 12:57 +0100, Patrick O'Callaghan wrote:
> > ...[snip]... I moved to a BT mouse recently, after my trusty
> > Logitech failed (it was 10 years old). The downside is that the
> > mouse
> > has a built-in sleep timer that kicks in when not in use and which
> > cannot be changed, at least from Linux (it's a HP model), so I have
> > to
> > wake it up occasionally by restarting the bluetooth service. This
> > is
> > pretty irritating, though otherwise the mouse works well.
>
> Is it (the timeout) something you could reprogram from Windows, and
> the setting could be permanent?
I did some further digging (using ChatGPT if you must know) and had an
epiphany: the relevant timeout isn't what's built into the mouse, it's
what the kernel is applying to the bluetooth port. In my case it's a
USB dongle, so after identifying the manufacturer and device ID via
'lsusb' I created the following:
# cat /etc/udev/rules.d/99-cambridge-silicon-radio.rules
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0a12",
ATTR{idProduct}=="0001", TEST=="power/control", ATTR{power/control}="on"
# echo on|tee /sys/bus/usb/devices/1-11/power/control
on
I added the second line because otherwise the attribute was set to
'auto', which may or may not matter (I didn't check). Then after
applying 'udevadm control --reload-rules; udevadm trigger' it now seems
to work, fingers crossed.
poc
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
