16

I have an Asus Zenbook UX31A, the Asus 13" unit from first generation ultrabooks. I run Ubuntu 12.10 up to date on it.

Before a week or two I used to enjoy more that 5 hours of battery life, especially when watching movies with VLC and hardware accelerated playback. I can't link my issue to some update I did but for several days now and after about 2 to 3 hours, my laptop shutdown abruptly without warning for critical nor low battery level.

I suspect this is battery related since the battery charge curve show that the battery charge plummets from 50-40% to 0% before the shutdowns. Upon reboot, I have to run a "killall Xorg" since the greeter won't load and drop me to something like a black console with lines about battery I can't remember on top of my head right now and an arrow cursor.

After a while, usually 1 to 3 minutes, the laptop shutdown again.

I can't pinpoint the component that cause this. I know it's a software problem since after such an event I can't run it for at least 1h30 in Windows without issues. I lost patience after that but it reported still 1h of autonomy when I powered it off.

Any hint on how to solve or at least identify the culprit ? Any log I can check maybe ?

Thanks.

thomas
  • 321

4 Answers4

2

It's probably a calibration problem. I used to face a somewhat similar problem on my laptop too. Back when I was using Windows 10, I used to enjoy about 4 to 5 hours of battery life and after switching to Ubuntu, my battery life came down to about 3 hours. I did some research online and found tons of advice, but none of them seemed to be as effective as recalibrating. Here's what you gotta do...

  • Charge your laptop to 100% and let it remain plugged in for about 30 to 40 minutes.
  • After that, unplug it and make sure to use your laptop until it shuts down
  • After this try switching it on, if it doesn't switch on, then well and good. However, if it does switch on, then that would mean that there is still some charge left in your battery.
  • Make sure that your battery is fully drained.
  • Wait for up to 2 to 3 hours and then plug it back in and let it charge all the way up to 100 percent.

After this you should be good. This is a manual recalibration. This will probably fix your inaccurate battery meter readings.

Zanna
  • 72,312
Uday Kumar
  • 161
0

The previous answer for changing power setting to "do nothing" at critical doesn't seem to apply for Ubuntu 20.04 (that dconf setting no longer exists). To achieve that, you will have to edit /etc/UPower/UPower.conf and set PercentageAction=0 and TimeAction=0

A cleaner approach would probably be to set CriticalPowerAction to None or Suspend but this feature was rejected

Relevant discussion

Rufus
  • 943
0

I had the same issue in a Dell laptop when running Windows and Linux

To get basic values about the battery performance, use in Linux

acpitool -B

or in windows 

Powercfg -energy

Both commands can give you a lot of info about power consumption check man acpitool and powercfg /h

What I think is the problem is that the OS Bios Hardware it is not getting the right charge value from the battery, since this is hard to get usually this info is stored by the OS from calculations in the Bios and hardware when some power fluctuation introduce a bug (safety battery protection will always avoid overcharge)

Usually Calibrating the battery will fix the problem, to reset the process is to do a full charge without interruptions and later a full battery discharge, if it's possible let the laptop in some stable power situation, while you are not using it and avoiding that enter into auto hibernation, sleep etc, some laptops have a utility or the manufacturer recommend a special procedure to reset the battery.

user5286776117878
  • 23
0

I suggest changing your power setting to "do nothing" at critical. This way an erroneous reading will not shut down your system.

Alt + F2 and launch dconf-editor --you will need to install this if you don't already have it: sudo apt-get install dconf-editor

Navigate to org.gnome.settings-daemon.plugins.power and change the critical-battery-action to interactive or do nothing (this is for 16.04)

This does not fix the bug, but mitigates the impact. If your computer is not really at critical, just tell it to do nothing an continue.

Pablo Bianchi
  • 17,371
John
  • 11