[PATCH] Check if the battery comes from bluetooth keyboard or mouse.

Peter Wu lekensteyn at gmail.com
Thu Aug 29 06:47:59 PDT 2013


Hi,

On Thursday 29 August 2013 18:00:32 Shih-Yuan Lee wrote:
> Hi,
> 
> I'm sorry that previous output of "upowerd -v" is based on the latest
> linux kernel (3.2.0-52-generic) on Ubuntu 12.04, and it seems not to
> have much information.
> So I collect other outputs of "upowerd -v" from 3.5.0-39-generic and
> 3.8.0-29-generic.

Those logs are indeed better. Some observations below:

17:11:11	added native-path: /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:42/0005:05AC:030D.0005/power_supply/hid-28:CF:DA:BB:74:1B-battery
17:11:11	using id: generic_id
17:11:11	failed to get data from /usr/local/var/lib/upower/history-rate-generic_id.dat as file does not exist

"generic_id" is bad, this means that no model information or serial
was provided. Result: multiple devices with this non-unique ID will use
the same history files.

I have no further suggestions at this point other than the one mentioned
before: use udev functions in favor of path manipulation. And although
up-device-hid looks useful, it seems a misnomer (a better name would be
up-device-ups I think).

Regards,
Peter
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?


More information about the devkit-devel mailing list