From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] Re: [9front] ThinkPad X380 Yoga, aux/acpi reports 13245% battery charge
Date: Wed, 17 Apr 2024 17:42:35 -0400 [thread overview]
Message-ID: <BAAD8481B43B0A652D1DC2B0FD4D5388@gaff.inri.net> (raw)
In-Reply-To: <6850E9167D7501D38DF2CFFAB70744EA@ftrv.se>
> Can you try killing aux/acpi, starting a new one and checking
> if there is any difference? Maybe it should query all of the
> battery info every single time.
the first time i did this, the readings looked more or less accurate.
did it again, and now the readings are definitely wrong again.
sl
prev parent reply other threads:[~2024-04-17 21:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 0:43 sl
2024-04-16 0:46 ` Noam Preil
2024-04-16 0:55 ` [9front] " Stanley Lieber
2024-04-16 2:29 ` Noam Preil
2024-04-16 2:41 ` [9front] " Stanley Lieber
2024-04-18 2:45 ` Noam Preil
2024-04-16 3:09 ` Sigrid Solveig Haflínudóttir
2024-04-16 16:19 ` sl
2024-04-17 21:24 ` sl
2024-04-17 21:30 ` Sigrid Solveig Haflínudóttir
2024-04-17 21:42 ` sl [this message]
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=BAAD8481B43B0A652D1DC2B0FD4D5388@gaff.inri.net \
--to=sl@stanleylieber.com \
--cc=9front@9front.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).