Wrong battery state reading cause brutal shutdownPower Management only has the option of “Do Nothing” for...

When obtaining gender reassignment/plastic surgery overseas, is an emergency travel document required to return home?

Does a paladin have to announce that they're using Divine Smite before attacking?

Why did the villain in the first Men in Black movie care about Earth's Cockroaches?

Hosting images in SFMC - is it a good idea?

Why do neural networks need so many training examples to perform?

Could an Apollo mission be possible if Moon would be Earth like?

What makes papers publishable in top-tier journals?

Best way to strengthen a wheel?

Coworker asking me to not bring cakes due to self control issue. What should I do?

Eww, those bytes are gross

What game did these black and yellow dice come from?

Potential client has a problematic employee I can't work with

How do you get out of your own psychology to write characters?

Why do we have to make "peinlich" start with a capital letter and also end with -s in this sentence?

What's the oldest plausible frozen specimen for a Jurassic Park style story-line?

What is a good reason for every spaceship to carry a weapon on board?

How can the probability of a fumble decrease linearly with more dice?

Removing whitespace between consecutive numbers

How much mayhem could I cause as a fish?

Why didn't Tom Riddle take the presence of Fawkes and the Sorting Hat as more of a threat?

Microtypography protrusion with Polish quotation marks

What senses are available to a corpse subjected to a Speak with Dead spell?

"Starve to death" Vs. "Starve to the point of death"

What is the difference between "...", '...', $'...', and $"..." quotes?



Wrong battery state reading cause brutal shutdown


Power Management only has the option of “Do Nothing” for critically low battery in 17.10Laptop drains of quickly with batteryThe battery indicator& Power setting panel shows wrong battery stateBattery life starts at 2:30 hrs (99%), but less than 1 minute later is only 1:30 hrs (99%)Ubuntu 13.10: Improving Power Consumption (Thinkpad T530)Battery information is wrongBattery information acting weirdBattery only charging when shutting down by holding the power button or in suspended modeCan't power on if once after battery drains the last dropWhy is Ubuntu 18.04 battery life superior to Lubuntu 18.04 in a Dell 7577Ubuntu shutting down arbitrarily when charger not connected despite sufficient battery













11















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.










share|improve this question























  • Do you get any issues in Windows as well?

    – Wilf
    May 28 '15 at 9:05











  • you might also, if you're tchnically inclined. remove the battery, boot, clean shutdown, reinstall the battery, boot and test further as this has worked in the past for me to get accurate readings on my laptop batteries just make sure to check accuracy against what windows determines your battery charge to be

    – heypaleblue
    May 28 '15 at 20:28













  • It would be helpful if you will take a photograph of what ever lines you saw on the black screen and update the post with it.

    – daltonfury42
    May 29 '15 at 12:27













  • you can or can't use it for 1:30 hts after shutdown.

    – totti
    May 29 '15 at 15:07











  • After a fully rechage, run on windows OS and check how much backup you get.

    – totti
    May 29 '15 at 15:11
















11















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.










share|improve this question























  • Do you get any issues in Windows as well?

    – Wilf
    May 28 '15 at 9:05











  • you might also, if you're tchnically inclined. remove the battery, boot, clean shutdown, reinstall the battery, boot and test further as this has worked in the past for me to get accurate readings on my laptop batteries just make sure to check accuracy against what windows determines your battery charge to be

    – heypaleblue
    May 28 '15 at 20:28













  • It would be helpful if you will take a photograph of what ever lines you saw on the black screen and update the post with it.

    – daltonfury42
    May 29 '15 at 12:27













  • you can or can't use it for 1:30 hts after shutdown.

    – totti
    May 29 '15 at 15:07











  • After a fully rechage, run on windows OS and check how much backup you get.

    – totti
    May 29 '15 at 15:11














11












11








11


1






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.










share|improve this question














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.







laptop asus battery ultrabook






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 1 '13 at 15:19









thomasthomas

18618




18618













  • Do you get any issues in Windows as well?

    – Wilf
    May 28 '15 at 9:05











  • you might also, if you're tchnically inclined. remove the battery, boot, clean shutdown, reinstall the battery, boot and test further as this has worked in the past for me to get accurate readings on my laptop batteries just make sure to check accuracy against what windows determines your battery charge to be

    – heypaleblue
    May 28 '15 at 20:28













  • It would be helpful if you will take a photograph of what ever lines you saw on the black screen and update the post with it.

    – daltonfury42
    May 29 '15 at 12:27













  • you can or can't use it for 1:30 hts after shutdown.

    – totti
    May 29 '15 at 15:07











  • After a fully rechage, run on windows OS and check how much backup you get.

    – totti
    May 29 '15 at 15:11



















  • Do you get any issues in Windows as well?

    – Wilf
    May 28 '15 at 9:05











  • you might also, if you're tchnically inclined. remove the battery, boot, clean shutdown, reinstall the battery, boot and test further as this has worked in the past for me to get accurate readings on my laptop batteries just make sure to check accuracy against what windows determines your battery charge to be

    – heypaleblue
    May 28 '15 at 20:28













  • It would be helpful if you will take a photograph of what ever lines you saw on the black screen and update the post with it.

    – daltonfury42
    May 29 '15 at 12:27













  • you can or can't use it for 1:30 hts after shutdown.

    – totti
    May 29 '15 at 15:07











  • After a fully rechage, run on windows OS and check how much backup you get.

    – totti
    May 29 '15 at 15:11

















Do you get any issues in Windows as well?

– Wilf
May 28 '15 at 9:05





Do you get any issues in Windows as well?

– Wilf
May 28 '15 at 9:05













you might also, if you're tchnically inclined. remove the battery, boot, clean shutdown, reinstall the battery, boot and test further as this has worked in the past for me to get accurate readings on my laptop batteries just make sure to check accuracy against what windows determines your battery charge to be

– heypaleblue
May 28 '15 at 20:28







you might also, if you're tchnically inclined. remove the battery, boot, clean shutdown, reinstall the battery, boot and test further as this has worked in the past for me to get accurate readings on my laptop batteries just make sure to check accuracy against what windows determines your battery charge to be

– heypaleblue
May 28 '15 at 20:28















It would be helpful if you will take a photograph of what ever lines you saw on the black screen and update the post with it.

– daltonfury42
May 29 '15 at 12:27







It would be helpful if you will take a photograph of what ever lines you saw on the black screen and update the post with it.

– daltonfury42
May 29 '15 at 12:27















you can or can't use it for 1:30 hts after shutdown.

– totti
May 29 '15 at 15:07





you can or can't use it for 1:30 hts after shutdown.

– totti
May 29 '15 at 15:07













After a fully rechage, run on windows OS and check how much backup you get.

– totti
May 29 '15 at 15:11





After a fully rechage, run on windows OS and check how much backup you get.

– totti
May 29 '15 at 15:11










3 Answers
3






active

oldest

votes


















1














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.






share|improve this answer

































    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.






    share|improve this answer
























    • In my case, I doubt it is a calibration problem: my computer will shutdown after 10 to 30 minutes where I used to enjoy a good 6 hours of battery on Windows.

      – 7hibault
      Jun 23 '15 at 16:13



















    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.






    share|improve this answer

























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f262723%2fwrong-battery-state-reading-cause-brutal-shutdown%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      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.






      share|improve this answer






























        1














        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.






        share|improve this answer




























          1












          1








          1







          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.






          share|improve this answer















          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.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 23 '16 at 15:11









          Zanna

          50.9k13136241




          50.9k13136241










          answered Dec 23 '16 at 14:21









          Uday KumarUday Kumar

          3610




          3610

























              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.






              share|improve this answer
























              • In my case, I doubt it is a calibration problem: my computer will shutdown after 10 to 30 minutes where I used to enjoy a good 6 hours of battery on Windows.

                – 7hibault
                Jun 23 '15 at 16:13
















              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.






              share|improve this answer
























              • In my case, I doubt it is a calibration problem: my computer will shutdown after 10 to 30 minutes where I used to enjoy a good 6 hours of battery on Windows.

                – 7hibault
                Jun 23 '15 at 16:13














              0












              0








              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.






              share|improve this answer













              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.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jun 8 '15 at 15:46









              user5286776117878user5286776117878

              136




              136













              • In my case, I doubt it is a calibration problem: my computer will shutdown after 10 to 30 minutes where I used to enjoy a good 6 hours of battery on Windows.

                – 7hibault
                Jun 23 '15 at 16:13



















              • In my case, I doubt it is a calibration problem: my computer will shutdown after 10 to 30 minutes where I used to enjoy a good 6 hours of battery on Windows.

                – 7hibault
                Jun 23 '15 at 16:13

















              In my case, I doubt it is a calibration problem: my computer will shutdown after 10 to 30 minutes where I used to enjoy a good 6 hours of battery on Windows.

              – 7hibault
              Jun 23 '15 at 16:13





              In my case, I doubt it is a calibration problem: my computer will shutdown after 10 to 30 minutes where I used to enjoy a good 6 hours of battery on Windows.

              – 7hibault
              Jun 23 '15 at 16:13











              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.






              share|improve this answer






























                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.






                share|improve this answer




























                  0












                  0








                  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.






                  share|improve this answer















                  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.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 16 mins ago









                  Pablo Bianchi

                  2,75821533




                  2,75821533










                  answered Jul 10 '16 at 3:53









                  JohnJohn

                  111




                  111






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f262723%2fwrong-battery-state-reading-cause-brutal-shutdown%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Is there a lightweight tool to crop images quickly?Cropping Images using Command Line Tools OnlyHow to crop...

                      List of shipwrecks in 1808...

                      Unit packagekit.service is masked Announcing the arrival of Valued Associate #679: Cesar...