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

Hi Peter, Thank you for your review. For https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1153488. The code base is a little old, so I made two patches for it. One is https://launchpadlibrarian.net/146285357/02-try-to-work-out-if-the-device-is-powering-the-system.patch to fix the power-supp

Luminosity level, battery status of K750 (was: Re: UPower 0.9.21)

On Tuesday 27 August 2013 23:08:07 Julien Danjou wrote: > On Tue, Aug 27 2013, Peter Wu wrote: > >> I still the light meter I had implemented back then (don't know why it's > > > > "light meter"? You mean the current lux value? Where should it be > > visible? > > Yes, that's what I meant. My init

Re: UPower 0.9.21

On Tue, Aug 27 2013, Peter Wu wrote: >> I still the light meter I had implemented back then (don't know why it's > > "light meter"? You mean the current lux value? Where should it be > visible? Yes, that's what I meant. My initial patch (git log) implemented it. > What is wrong here? Perhaps the

Re: How should I diagnose "no voltage values" issues?

Hi, On Tuesday 27 August 2013 14:10:56 Timothée Ravier wrote: > My laptop is a Sony VAIO VGN-FW4 (more in the dmesg log attached). > > I forgot to mention that my battery is currently dying which is probably > part of the issue. > > [..] > > Which is missing one entry as: > > $ ls /sys/class/p

Re: UPower 0.9.21

Hi Julien, On Tuesday 27 August 2013 22:33:14 Julien Danjou wrote: > Using Peter Wu's patchset fixes a few things, I get this instead: > > Device: /org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx0005 > native-path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/ > 2-1.1:1.

Re: UPower 0.9.21

On Fri, Jul 26 2013, Julien Danjou wrote: > Does that release fixes the various regression on the HID++ protocol? > Most of the code I provided for the K750 keyboard and others devices has > been broken since the code refactor happened some months ago… It doesn't fix the K750 code, it's still bro

Re: How should I diagnose "no voltage values" issues?

Hi, On Monday 26 August 2013 14:40:21 Timothée Ravier wrote: > I'm running an updated Arch Linux with Linux 3.10 / 3.11rc7, upower 0.9.21. > > My logs are filled with those lines: > > upowerd[927]: (upowerd:927): UPower-Linux-WARNING **: no voltage values, > using 10V as approximation > > which

What happened to the "scope" sysfs attribute?

Hi, UPower assumes a "scope" attribute[1] to determine whether a battery powers the system or something else. I see that the kernel patches were queued for 3.3[2], but I cannot find these commits back in mainline. Was that patchset dropped without anyone noticing? Anton and Richard, can you sh

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

Hi, On Friday 02 August 2013 18:07:53 Shih-Yuan Lee wrote: > From: "Shih-Yuan Lee (FourDollars)" > > First, checking the device path. If it contains 'bluetooth', it is a > bluetooth devices. Second, checking if there is an input folder. If there > is mouse folder under the input folder, it is a

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

Hi, It seems this patch doesn't bring up much attention. This patch is for upower. I find some relative bug reports. https://bugzilla.redhat.com/show_bug.cgi?id=816775 https://bugs.launchpad.net/bugs/1153488 https://bugs.launchpad.net/bugs/1066208 I think this patch might be able to fix them all.