From: Sebastian Arnhold <sebastian.arnhold387@gmail.com>
To: Bastien Nocera <hadess@hadess.net>, linux-input@vger.kernel.org
Subject: Re: Stylus battery reported as having 1% charge even though fully charged
Date: Thu, 21 Jul 2022 16:39:06 +0200 [thread overview]
Message-ID: <9ba2643b-5fd5-d49d-74fd-fc682b7836f6@gmail.com> (raw)
In-Reply-To: <28d18d2f39fef4da00021d21cf2ccd7eb4a29ac9.camel@hadess.net>
Sadly, I'm not a programmer. Anyways, I wanted to report it - and would
be very thankful if this bug could be fixed in one of the next kernel
releases. :) Thanks in advance, Sebastian
Am 21.07.22 um 10:53 schrieb Bastien Nocera:
> On Tue, 2022-07-19 at 11:38 +0200, Sebastian Arnhold wrote:
>> Dear developers,
>>
>> when using GNOME 42.3 on Wayland on my ASUS ExpertBook B5 Flip, it
>> reports my stylus battery to be stuck at 1% all the time, independent
>> of
>> its actual charging status. This is also independent from the stylus
>> I
>> use, as I've tried with two different ones.
>>
>> The battery device registers as ELAN9008:00 04F3:2E12 in GNOME energy
>> settings.
>>
>> The GNOME developers helped me track the bug down to upower, as
>> upower
>> itself shows the charging status to be stuck at 1%. The upower
>> developers then sent me here.
>>
>> My kernel version is 5.18 on an x86_64 architecture on Fedora 36. My
>> upower version is 0.99.19.
>>
>> Observed behaviour: Kernel reports 1% after pen is switched on and
>> touches the touchscreen for the first time. upower reports this to
>> GNOME
>> which then throws a "Battery low"-warning message.
>> Expected behaviour: Kernel reporting the correct charging percentage
>> from the pen to upower, or 0% if charging status cannot be
>> determined.
>> The latter would be a workaround since 0% seems to be ignored by
>> GNOME.
>>
>> Can you help me to resolve this bug?
> You'll probably want to implement a patch similar to this one:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f3193ea1b6779023334faa72b214ece457e02656
>
> Cheers
next prev parent reply other threads:[~2022-07-21 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 9:38 Stylus battery reported as having 1% charge even though fully charged Sebastian Arnhold
2022-07-21 8:53 ` Bastien Nocera
2022-07-21 14:39 ` Sebastian Arnhold [this message]
2022-07-21 19:32 ` Gregor Riepl
-- strict thread matches above, loose matches on Subject: below --
2022-01-25 19:48 Sebastian Arnhold
2022-01-25 21:46 ` Bastien Nocera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ba2643b-5fd5-d49d-74fd-fc682b7836f6@gmail.com \
--to=sebastian.arnhold387@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).