Skip to content
Snippets Groups Projects
New look: Off

n900 i3status "no battery"

    • Closed Imported Issue created by Administrator @root

    Created by: fxkrait

    i3 status wont display the battery percentage. By default it will say "no battery"

    in i3status.conf, I set battery path path = "/sys/class/power_supply/bq27200-0/uevent/"

    and I get "no '%d' in battery path"

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: sicelo

      in i3status.conf, I set battery path path = "/sys/class/power_supply/bq27200-0/uevent/"

      and I get "no '%d' in battery path"

      shouldn't that be: path = "/sys/class/power_supply/bq27200-0/uevent" without the trailing /

      i also observed the issue you are reporting though, and was also going to have a look later

      By * postmarketOS Bot on 2018-04-28T10:19:51

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: fxkrait

      Yeah you're right. Still same error though.

      By * postmarketOS Bot on 2018-04-28T18:35:11

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      The error message sounds like it expects a literal %d in the battery path.

      Here's the code: https://github.com/i3/i3status/blob/82d25dc36295bc59cdf37af8e23c644a9c2e6aad/src/print_battery_info.c#L438

      I recommend to make sure that the battery indicator in /sys/class/... works in general (run cat on the values, I've read that it needs to be calibrated on the N900 or something), and if you are sure that it works, then asking in the i3 community for help with that specific configuration. Finally after figuring it out, it would be super nice to create a pull request that fixes the configuration in the postmarketOS package.

      By * postmarketOS Bot on 2018-04-28T22:14:18

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: fxkrait

      Has this been "officially" fixed? I'm using my own change of path, but I see @sicelo submitted #1470. Is it being reviewed?

      By * postmarketOS Bot on 2018-05-16T22:22:36

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: sicelo

      On your device, with the change of path, does the correct battery capacity show?

      By * postmarketOS Bot on 2018-05-17T05:21:29

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: fxkrait

      Yes. It's shown as a percent. I have extended battery so its like 333 percent when full. It's the change of path, and some other stuff you can see above. However in format = "%status %percentage %remaining" .... I have gotten rid of %status and %remaining as they do not function. I can update my pr if you're having issues with yours.

      By * postmarketOS Bot on 2018-05-18T05:05:02

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: sicelo

      I believe 333% is incorrect, even for an extended battery. FWIW, it was showing around 180% for my standard BL-5J. Such values are nowhere to be found in raw bq27200 output. Also, at least to me, values like these (higher than 100%) have no value (pun :stuck_out_tongue: ).

      Overall, maybe I just like seeing my battery reporting as close as possible to how it is reported in Maemo (and even on laptops, etc.), which might be different to what others like. Therefore, it might be best to withdraw my PR, and keep my changes local.

      For %status, you can use the workaround mentioned at https://github.com/postmarketOS/pmbootstrap/pull/1450#issuecomment-386832258 and yes, %remaining doesn't work.

      By * postmarketOS Bot on 2018-05-18T19:35:54

      Edited by Ghost User
    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: fxkrait

      Ok I agree that POWER_SUPPLY_CHARGE_FULL_DESIGN should be calibrated to actual battery, and the percent should have a max at 100. The 333 percent is "correct" based off raw values uevent (ENERGY_NOW / CHARGE_FULL_DESIGN).

      Your PR is the better solution, so I would say lets use that.

      By * postmarketOS Bot on 2018-05-19T01:21:06

    • Administrator
      Administrator @root · Imported
      Author Owner

      Created by: ollieparanoid

      Fixed in #1470, thanks to both of you!

      By * postmarketOS Bot on 2018-05-20T13:53:18

    Please register or sign in to reply