![]() ![]() I worked around this problem byĪpplying an ugly patch to upowerd so that power status change is MAYBE in Windows power connect/disconnect is triggered by power adapterĬhanging status instead than by battery. Is "frozen" in the status after power on / resume after suspend. (the status of the power adapter) gets updated correctly, while theīattery status (charging/ discharging), as found in > instantaneous when all was well the night before. > recognised - but it takes several seconds rather than being almost > Windows, lid closure still fails but power connect/disconnect still > Power connect/disconnect fails to be acted upon properly by Ubuntu. Next morning, lid closurefails to be recognised by Ubuntu. Then, in Ubuntu 12.04, I suspended the system > recognition in both Windows and Ubuntu 12.04 and suspend on lid closure. > Yesterday, after updating the BIOS I tested power connect/disconnect > After BIOS update all was well for 15hours only!Īlso for me, things worked well (both lid and power status) during theįirst weeks of life of the laptop (a Series 5 Ultrabook). ![]() UpgradeStatus: No upgrade log present (probably fresh install) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) "lshal -m" doesn't report anything when I plug the charger in or out. However a number of applications make their decisions based on this state (battery monitor, jupiter, etc.) and therefore behave incorrectly. So the state is the only thing that is incorrect. The percentage and time are correctly updated when the battery is actually charging or discharging - regardless of the reported state. When booted with charger disconnected and charger is now connected:īattery #1 : discharging, 47.00%, 00:53:43 When booted with charger disconnected and charger is still disconnected:īattery #1 : discharging, 47.00%, 01:39:44 When booted with charger connected and charger is now disconnected: When booted with charger connected and charger is still connected: Here is output from "acpitool -a -b" in various situations: Basically the state what was at the time of boot stays active all the time - regardless of the ac-adapter state. 3.I have a new Samsung 9-series laptop (NP900X3B) and the battery state is detected incorrectly. This command is equivalent to running upower -e, followed by upower -i for each device, and thus saves us one step in the process. Updated: Thursday 21 April 2022 07:52:12 AM (57 seconds ago) Updated: Thursday 21 April 2022 07:42:11 AM (658 seconds ago)ĭevice: /org/freedesktop/UPower/devices/battery_BAT0 This essentially prints information for all the connected devices: $ upower -dĭevice: /org/freedesktop/UPower/devices/line_power_AC These days, most devices have only a single battery, so we can also use the upower command with the -d parameter. $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 | grep state | cut -d ':' -f2 | xargs Needless to say, we can use grep or other commands to process the output into a format we need: $ upower -i /org/freedesktop/UPower/devices/battery_BAT0 | grep percentage | grep -o "*" Icon-name: 'battery-full-charging-symbolic' $ upower -i /org/freedesktop/UPower/devices/battery_BAT0
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |