Skip to content
Snippets Groups Projects
  1. Jul 21, 2022
    • Benjamin Berg's avatar
      Release 1.90.0 with larger refactorings · d4259c00
      Benjamin Berg authored
      The version number has been bumped to be able to maintain multiple
      branches without conflict. This version bump is not associated with a
      API/ABI break.
      v1.90.0
      d4259c00
    • Benjamin Berg's avatar
      battery: User power/current reading from battery · c2d77ae2
      Benjamin Berg authored
      This switches to always use the power/current reading if we had a
      sensible reading at some point in the past.
      
      In contrast to the older UPower code, will will however ignore the
      reading for 10 seconds after a discontinuity (power plug/unplug or
      resume) unless we read an explicit zero value after the event happened.
      
      We do this under the assumption that the readings may be wildly off, and
      it is better to not show an estimate rather than one that is wildly
      incorrect.
      
      Note that this commit also normalises negative power readings while
      discharging to be positive.
      
      Closes: #199
      c2d77ae2
    • Benjamin Berg's avatar
      battery: Make repolling more explicit · 1ab1b70d
      Benjamin Berg authored
      Estimation code can request a battery poll if the value is not good
      enough at the point. Make this a little bit more explicit by renaming
      the intenral variable to "repoll_needed" and automatically resetting it
      to FALSE.
      1ab1b70d
    • Benjamin Berg's avatar
      battery: Better separate power usage estimation code · 9dd78a74
      Benjamin Berg authored
      The up_device_battery_estimate function did more than just estimating
      the current power consumption (and doing some state guessing). Move the
      time to full/empty checking out of the function. Also, let it directly
      modify the reported state before it is pushed into the ring-buffer.
      9dd78a74
    • NorwayFun's avatar
      Add Georgian translaton · e6a5d9a7
      NorwayFun authored and Benjamin Berg's avatar Benjamin Berg committed
      e6a5d9a7
  2. Jul 12, 2022
    • Benjamin Berg's avatar
      daemon: Reevaluate polling timeout after resume · e88e90fa
      Benjamin Berg authored
      When polling is resumed the timeout needs to be reevaluated. This
      requires running the polling handler once (in the next mainloop
      iteration).
      
      Set the ready time to zero to ensure this is happening. Without this, we
      would be stuck without actually polling until we get a uevent from the
      kernel on one of the power supplies.
      
      Fixes: #198
      e88e90fa
  3. Jul 11, 2022
  4. Jul 08, 2022
  5. Jun 22, 2022
  6. Jun 21, 2022
  7. Jun 15, 2022
  8. Jun 14, 2022
  9. Jun 09, 2022
    • Benjamin Berg's avatar
      test: Properly wait for idle handler after uevents · a78ee603
      Benjamin Berg authored
      The state aggregation test requires an idle handler to run, which can be
      a bit unreliable as it may or may not run twice.
      
      Force running it twice and add code to wait for it to complete. Do so
      properly by waiting for the correct log messages rather than sleeping so
      that everything is ordered nicely while not slowing down the test a lot.
      
      Closes: #193
      a78ee603
  10. Jun 08, 2022
  11. Jun 07, 2022
    • Benjamin Berg's avatar
      68d4f370
    • Benjamin Berg's avatar
      test: Test all possible inputs for daemon state aggregation · 1587b377
      Benjamin Berg authored
      This adds a test that checks all possible inputs for the battery state
      aggregation. Not all states are actually tested in this case, as some
      states may be handled through state inference and others might not be
      well defined.
      1587b377
    • Benjamin Berg's avatar
      daemon: Update aggregate state matching and handle UNKNOWN state · 13f7cc7b
      Benjamin Berg authored
      Stop trying to guess a battery state based on the AC information for a
      single battery. Instead, just do the guessing in the display device.
      
      This means that cases with more than one battery work fine. It also
      means that we still report an UNKNOWN state for the battery itself.
      
      Also get the on_battery information from the display devices discharging
      state, there is no need to iterate all of the batteries to figure that
      out.
      
      Note that we don't really have a well defined state for the display
      device in all cases. We'll add a test in the next step, marking those
      cases as TBD or ANY to show where the issues are. AFAICT we do not have
      a regression though, so this should be fine for now.
      
      Fixes: #146
      13f7cc7b
  12. Jun 03, 2022
  13. May 27, 2022
  14. May 25, 2022
  15. May 20, 2022
Loading