ACPI battery level stops updating

Hello,
I have a strange problem with battery level (displayed using xfce4-power-manager). At startup it updates but not very precisely (not percent by percent), after some minutes it stops updating.
I thought it was an xfce problem, so I installed xfce4-power-manager-git. But reading acpi status and getting /sys/class/power_supply/BAT0/ info reports same results as xfce. ACPI does not update battery level!
Why acpi stops updating my battery level?
I'm using kernel 3.15.10-1
xfce4-power-manager-git
xfce4-power-manager 1.4.1-1
upower 0.99
lah

No one interested about this problem?
Now, to get battery level I'm manually polling using a cron job executing acpi -V command...
I've not yet found another solution to get battery level update working.
I found another interesting point. When I resume from suspend battery level updates... Here are my logs when suspending / resuming
dmesg
[ 1137.086386] wlo1: deauthenticating from 00:1f:9f:e7:22:53 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1137.092006] cfg80211: Calling CRDA to update world regulatory domain
[ 1137.168083] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 1137.307402] PM: Syncing filesystems ... done.
[ 1137.390588] PM: Preparing system for mem sleep
[ 1137.390812] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 1137.392234] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 1137.393433] PM: Entering mem sleep
[ 1137.393499] Suspending console(s) (use no_console_suspend to debug)
[ 1137.394631] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1137.394711] sd 0:0:0:0: [sda] Stopping disk
[ 1137.557027] e1000e: EEE TX LPI TIMER: 00000011
[ 1137.809968] PM: suspend of devices complete after 416.371 msecs
[ 1137.823466] PM: late suspend of devices complete after 13.483 msecs
[ 1137.824416] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 1137.824592] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 1137.824603] e1000e 0000:00:19.0: System wakeup enabled by ACPI
[ 1137.824680] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 1137.836734] PM: noirq suspend of devices complete after 13.269 msecs
[ 1137.837000] ACPI: Preparing to enter system sleep state S3
[ 1137.853504] PM: Saving platform NVS memory
[ 1137.853505] Disabling non-boot CPUs ...
[ 1137.853535] intel_pstate CPU 1 exiting
[ 1137.854780] kvm: disabling virtualization on CPU1
[ 1137.854790] smpboot: CPU 1 is now offline
[ 1137.855147] intel_pstate CPU 2 exiting
[ 1137.856377] kvm: disabling virtualization on CPU2
[ 1137.856383] smpboot: CPU 2 is now offline
[ 1137.856949] intel_pstate CPU 3 exiting
[ 1137.858168] kvm: disabling virtualization on CPU3
[ 1137.858180] smpboot: CPU 3 is now offline
[ 1137.859931] ACPI: Low-level resume complete
[ 1137.859980] PM: Restoring platform NVS memory
[ 1137.861096] CPU0 microcode updated early to revision 0x1b, date = 2014-05-29
[ 1137.861225] Enabling non-boot CPUs ...
[ 1137.861272] x86: Booting SMP configuration:
[ 1137.861273] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 1137.873339] kvm: enabling virtualization on CPU1
[ 1137.875919] CPU1 is up
[ 1137.875970] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 1137.887493] CPU2 microcode updated early to revision 0x1b, date = 2014-05-29
[ 1137.888105] kvm: enabling virtualization on CPU2
[ 1137.890491] CPU2 is up
[ 1137.890527] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 1137.902171] kvm: enabling virtualization on CPU3
[ 1137.904609] CPU3 is up
[ 1137.908608] ACPI: Waking up from system sleep state S3
[ 1138.663122] acpi LNXPOWER:02: Turning OFF
[ 1138.663203] acpi LNXPOWER:01: Turning OFF
[ 1138.675606] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 1138.675825] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[ 1138.675838] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 1138.722182] PM: noirq resume of devices complete after 58.952 msecs
[ 1138.722883] PM: early resume of devices complete after 0.648 msecs
[ 1138.723159] mei_me 0000:00:16.0: irq 32 for MSI/MSI-X
[ 1138.723478] e1000e 0000:00:19.0: System wakeup disabled by ACPI
[ 1138.726178] snd_hda_intel 0000:00:1b.0: irq 33 for MSI/MSI-X
[ 1138.731841] sd 0:0:0:0: [sda] Starting disk
[ 1138.841851] e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
[ 1138.928730] usb 1-1.3: reset high-speed USB device number 4 using ehci-pci
[ 1139.045227] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1139.045398] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 1139.045414] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
[ 1139.045416] usb 3-2: hub failed to enable device, error -22
[ 1139.047871] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 1139.057847] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 1139.058273] ata1.00: configured for UDMA/133
[ 1139.205382] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 1139.205409] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
[ 1139.205412] usb 3-2: hub failed to enable device, error -22
[ 1139.365138] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
[ 1139.378870] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b3b73120
[ 1139.841774] usb 3-2.6: reset low-speed USB device number 3 using xhci_hcd
[ 1139.841797] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[ 1139.841800] usb 3-2.6: hub failed to enable device, error -22
[ 1140.098137] usb 3-2.6: reset low-speed USB device number 3 using xhci_hcd
[ 1140.098161] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[ 1140.098165] usb 3-2.6: hub failed to enable device, error -22
[ 1140.101400] tpm_tis 00:01: TPM is disabled/deactivated (0x7)
[ 1140.101410] rtc_cmos 00:03: System wakeup disabled by ACPI
[ 1140.354747] usb 3-2.6: reset low-speed USB device number 3 using xhci_hcd
[ 1140.370114] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800b3b73180
[ 1140.370126] usb 3-2.6: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 1140.380774] PM: resume of devices complete after 1658.753 msecs
[ 1140.381265] PM: Finishing wakeup.
[ 1140.381268] Restarting tasks ...
[ 1140.381412] acpi PNP0501:00: Still not present
[ 1140.382480] usb 2-1.6: USB disconnect, device number 3
[ 1140.389100] done.
[ 1140.421569] pci_bus 0000:01: Allocating resources
[ 1140.421585] pcieport 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 01] add_size 1000
[ 1140.421589] pcieport 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000
[ 1140.421599] pci_bus 0000:02: Allocating resources
[ 1140.421622] pcieport 0000:00:1c.2: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
[ 1140.421624] pcieport 0000:00:1c.2: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
[ 1140.421632] pci_bus 0000:03: Allocating resources
[ 1140.421658] pcieport 0000:00:1c.3: bridge window [io 0x1000-0x0fff] to [bus 03] add_size 1000
[ 1140.421660] pcieport 0000:00:1c.3: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
[ 1140.421663] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 1140.421668] pcieport 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 1140.421670] pcieport 0000:00:1c.2: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 1140.421672] pcieport 0000:00:1c.3: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 1140.421674] pcieport 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 1140.421676] pcieport 0000:00:1c.2: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 1140.421677] pcieport 0000:00:1c.3: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 1140.421687] pcieport 0000:00:1c.0: BAR 15: assigned [mem 0xbf200000-0xbf3fffff 64bit pref]
[ 1140.421697] pcieport 0000:00:1c.2: BAR 15: assigned [mem 0xbf400000-0xbf5fffff 64bit pref]
[ 1140.421702] pcieport 0000:00:1c.3: BAR 15: assigned [mem 0xbf600000-0xbf7fffff 64bit pref]
[ 1140.421707] pcieport 0000:00:1c.0: BAR 13: assigned [io 0x3000-0x3fff]
[ 1140.421710] pcieport 0000:00:1c.2: BAR 13: assigned [io 0x4000-0x4fff]
[ 1140.421713] pcieport 0000:00:1c.3: BAR 13: assigned [io 0x5000-0x5fff]
[ 1140.421980] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 1140.422076] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[ 1140.549726] e1000e: enp0s25 NIC Link is Down
[ 1140.550076] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[ 1140.577868] usb 2-1.6: new full-speed USB device number 4 using ehci-pci
[ 1140.662671] usb 2-1.6: string descriptor 0 read error: -22
[ 1140.684516] e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
[ 1140.771126] usb 2-1.8: new full-speed USB device number 5 using ehci-pci
[ 1140.784983] usb 2-1.6: USB disconnect, device number 4
[ 1140.787680] e1000e 0000:00:19.0: irq 34 for MSI/MSI-X
[ 1140.971041] usb 2-1.6: new full-speed USB device number 6 using ehci-pci
[ 1141.055968] usb 2-1.6: string descriptor 0 read error: -22
[ 1144.446140] wlo1: authenticate with 00:1f:9f:e7:22:53
[ 1144.455094] wlo1: send auth to 00:1f:9f:e7:22:53 (try 1/3)
[ 1144.457056] wlo1: authenticated
[ 1144.459038] wlo1: associate with 00:1f:9f:e7:22:53 (try 1/3)
[ 1144.463874] wlo1: RX AssocResp from 00:1f:9f:e7:22:53 (capab=0x411 status=0 aid=1)
[ 1144.463995] wlo1: associated
lah

Similar Messages

Battery state not updating

ok so I'm running arch linux on my laptop (Lenovo IdeaPad 510 G) and I've got a problem wit my battery, it doesn't update it's state to power managers (meaning that both xfce power manager and batti get an initial reading when I turn my laptop on but then they stop updating the battery state, so if I start my laptop with 100% battery that is what they will show for the whole session even if it drops to 1%), I've checked the wiki and tried using acpi, neither the battery nor the ac modules run but when I use acpi -i I do get my correct battery state.
I'm starting to run out of ideas here, has anyone faced this kind of problem before?

This is due to a recent upower update. upower 0.99 uses a whole new set of api's which means that all the power managers need to be updated to work with it. I had the exact same issue on MATE but mate-power-manager got patched yesterday which fixed the issue. Until xfce4-power-manager is patched, you'll need to use an alternative battery applet that does work with the new upower (if there is one) or downgrade to an older version of upower. Here's the link if you want to downgrade: http://seblu.net/a/arm/2014/03/31/extra/os/x86_64/
EDIT: Don't bother downgrading upower. The issue has already been reported: https://bugs.archlinux.org/task/39893
and a new version of xfce4-power-manager which fixes the issue is in the testing repo: https://www.archlinux.org/packages/test … r-manager/
Last edited by Chazza (2014-04-26 15:05:45)

Windows 8.1 and ACPI Battery Issues

We have a Dell Inspiron 15R (model 5537), which came with Windows 8 factory installed. The machine worked perfectly, with no flaws. Then we upgraded it to Windows 8.1, and the began having problems with the battery. The system would work fine
for a while, it is primarily used as a desktop computer, with the AC power plugged in 80% of the time. Then we would notice the power icon change to indicate was running on battery, even though it was still plugged in. Unplugging it and plugging
it back in SOMETIMES solved the problem, at least for a few hours. We have seen various suggestions for solving this problem, including disabling the Microsoft ACPI Compliant Battery module. As it worked perfectly in Windows 8, we can only assume
that the problem lies in a fault ACPI driver in Windows 8.1. Is there any permanent solution to this, perhaps Microsoft is issuing an update to the ACPI Battery drivers?

We have a Dell Inspiron 15R (model 5537), which came with Windows 8 factory installed. The machine worked perfectly, with no flaws. Then we upgraded it to Windows 8.1, and the began having problems with the battery. The system would work fine
for a while, it is primarily used as a desktop computer, with the AC power plugged in 80% of the time. Then we would notice the power icon change to indicate was running on battery, even though it was still plugged in. Unplugging it and plugging
it back in SOMETIMES solved the problem, at least for a few hours. We have seen various suggestions for solving this problem, including disabling the Microsoft ACPI Compliant Battery module. As it worked perfectly in Windows 8, we can only assume
that the problem lies in a fault ACPI driver in Windows 8.1. Is there any permanent solution to this, perhaps Microsoft is issuing an update to the ACPI Battery drivers?

Flex 2 14 Battery Level Dropped from 57 to 7 in seconds

I've been using my Flex 2 14 for around 3 months. However, recently I've encounter a situation whereby my battery level had dropped from 57% to 7% in split second when I'm not plugged in. I was wondering could it be an manufacturing defect and what should I do to fix this problem?
Note: I use this laptop while plugging into the charger most of the time. The battery level is usually kept at around 55~60 only with the help of energy manager. Also, I had performed battery gauge reset once.
Any suggestions will be appreciated.

SOLUTION FOUND !
I just found a solution to my battery issue that is apparently due to a bug on the latest update of Snow leopard (10.6.8). Parallels desktop that was in the Dock was making the Dock taking 100% of the CPU activity (checked in the activity monitor) using battery and heating my computer.
After I checked for such cases on teh web (see: http://forums.macrumors.com/showthread.php?t=1181176 ), I removed Parallels Desktop and Windows Applications folder from the Dock and situation seems to be back to normal...
RF

6500 slide False Battery Level Reading.

Hi,
Just wondering if anyone has had their battery level showing as full when it is actually very low.
This started happening after I updated my phone to firmware v 8.30, but probably more relevant after discharging the battery fully (as recommended)to improve battery life.
Thanks.

I have a 6500 classic and the battery started doing the weird levels.
Showed that the battery didn't need charging as said was full but when took it off the charger it said battery low.
Would not charge even after being on the charger all night.
Sometimes works in the car charger (needed one as battery doesn't even last 1 day at work since bought the phone) but after showing 3/4 full, get 1 call and then beeps at me to show about to go flat.
Phone is only 1 year old.
Ordered a new battery so will see how it goes when it comes in on Monday....

TOC stopped updating properly...

Hello - I'm having an issue with my Table of Contents. It has stopped updating properly. I have a 90+ page manual where I had the TOC working fine. I have been saving revisions of the manual when edits were made. The issue is that when I go to Update TOC, it clears the entire TOC of all the headings for the main body content. It keeps the "title" and the "Index" heading which happens to be the last entry for the TOC (this heading/page is not threaded with the rest of the main body).
I went back and looked at TOC for previous revisions, and I changed something 2 revisions ago and since then the TOC stopped working. The only significant format change I can remember is that the TOC originally was not threaded in with the main content of the document. Looking back a couple of revisions ago I had gone in and threaded it to the main body of the document. By the time I realized there was an error occurring I had saved yet another revision. But in this last revision I went in an unthreaded the TOC from the rest of document but it did not correct the issue. Needless to say, I have made several edits within the document that I haven't necessarily tracked (grammer, spelling). So going back several revisions to the properly working TOC would require re-edits of that revision....something I'd rather not have to do.
I'm using 3 levels of Section Headings/Paragraph Styles in my TOC --- and i've gone into the main body and those headings are still properly set as their respective paragraph style. I've even tried creating a completely NEW TOC in my latest revision with just one paragraph style and nothing comes up in my TOC. Its like nothings there or it can't see the tagged style in the document, but I know it is there.
Any ideas? Please help.
THANKS!

Hallelujah! I believe I've fixed it. Thank you to whoever added that "more like this" box on the side of the forums! And for the following forum post from 2008. Ain't the internet grand?
This appears to have fixed the issue: http://forums.adobe.com/message/1313052#1313052
I knew through my back revisions it was a threading issue. So I followed the above poster's advice and I basically CUT my entire manual and then deleted all the empty pages. Added 2 pages back and then pasted my content into those pages. Tested the TOC and when it asked me If i wanted to include overset text I knew I'd fixed it and that it was looking at all the headings. The whole content came up just like its supposed to. Then I added 90 more pages and expanded the thread back. All seems to be good.
Do NOT put TOC in your threaded story. Not cool. I had it right at first and then put it in there ---- that's what screwed me up.
....now back to work!

Cannot lower Critical Battery Level in Power Options

I am wanting to adjust the Critical Battery Level in Power Options to something lower than the default 7% that HP has set. When I try to change the number, it will not save and it just magically jumps back to 7%. This means that my laptop will hibernate when the battery level reaches 7% and I cannot turn it back on unless I plug it into AC power. 7% equates to roughly 40 minutes of battery time and I find this setting way too conservative.
I have done some research on this issue and have found the following:
Some suggest that PC manufacturers will somehow lock this setting to an arbitrary minimum and the user cannot change it to anything below this minimum (it appears HP have set it at 7% in my instance).
This link suggests using power.cfg and the command line to make the changes How To Lower the Critical Battery Level to 1% in Windows 7
Steps I have taken to try and resolve this:
I have tried the powercfg.exe method described in the aforementioned link to change the critical battery level to 3% and initially it appears to work. When I open up the Power Options screen, it indeed says 3%. However, when I actually test it out by using the laptop, it will still automatically hibernate at 7% battery level - it simply ignores the 3% setting.
I have also tried using powercfg.exe to change the Critical Battery Action to "Do Nothing" and likewise this setting is ignored and the laptop hibernates anyway.
I have phoned HP support and the only useful information that I got from them so far, is that the PC manufacturer has set it to 7% and it cannot be changed. They said they will escalate this matter to the research team and give me a call back.
I phoned Microsoft support and the consultant seemed to be confident that he could fix the issue but would not divulge the answer because he said that doing so would void the HP warranty and he didn't want to be to one to do that. He suggested that I call HP and request a conference call with Microsoft and they could then fix it. He seemed to be of the belief that if HP has set the 7% minimum that they should be the one to remove the limit.
If nothing works, I wonder if completely formatting the laptop (including removing the HP recovery partition) and then reinstalling a different Windows 8.1 (or Windows 7) will let me have full customization of the Critical Battery Level?
I would really appreciate your thoughts on how to fix this. It really fustrates me that HP thinks they know better and that the user needs to have 7% battery reserved - it is such a waste not to be able to utilize a battery to its full potential.

Hi @Sparkles1 ,
There must be an alternative solution to this.
What is the reasoning behind HP locking this setting at 7% minimum? I understand that a battery should not be run down to 0% as this will damage the battery but 7% is unreasonably high and in fact this does not conform with ACPI standard specification. I refer to the following document: https://msdn.microsoft.com/en-us/library/windows/hardware/dn481320%28v=vs.85%29.aspx
In particular, please see the table where it says that the critical battery level must be set to a value between 0 and 5%
Can you please advise how to change this? I believe this is a software related issue (specifically, the battery drivers). Can you issue an alternative driver to install? If you insist that it cannot be done, I will have no other option than to return the laptop and request a full refund.

My E-mail won't stop updating itself?

Hi, as I said above the E-mail hasn't been able to stop updating itself and it's depleting my battery quicker than usual. I've tried turning off the push option and turned the iPhone off and on several times. It still does the updating on its own. Is this just a bug or is there a problem? Would also appriciate some tips or advise. Thanks in advance.

Change your Fetch schedule to a longer period (Settings>Mail,Contacts,Calendars>Fetch New Data).

Simple critical battery level warning script

This is a little script I wrote for use on my laptop. I wanted to have some kind of visual cue to let me know when the battery charge gets below a certain level and this is what I came up with:
#!/bin/bash
# Configuration
interval=120 #in seconds
critical_level=10 #percent
icon="/usr/share/icons/Tango/48x48/devices/battery.png" #notification icon
battery_id="BAT1" #ACPI battery identifier
ac_adapter_id="ADP1" #ACPI power adapter identifier
while true
do
if [ "$(cat /proc/acpi/ac_adapter/$ac_adapter_id/state | grep -o off)" == "off" ]; then
battery_max=`cat /proc/acpi/battery/$battery_id/info | head -3 | tail -1 | awk '{print $4}'`
battery_current=`cat /proc/acpi/battery/$battery_id/state | head -5 | tail -1 | awk '{print $3}'`
battery_level=$((100*$battery_current/$battery_max))
[ $battery_level -le $critical_level ] && \
notify-send -u critical -i "$icon" -t 15000 \
"Battery level is low!" "Only $battery_level% of the charge remains."
fi
sleep $interval
done
This script uses notification-daemon (or notification-daemon-xfce) package. It can be configured by editing values in the "Configuration" section. I just autostart it with my openbox session. It all should be pretty self-explanatory otherwise.
I hope someone finds it useful.
EDIT: Some improvements to the script.
Last edited by fwojciec (2008-07-09 13:11:14)

robmaloy wrote:
thx, really cool i always forget to look after my battery percentage
maybe you can replace "BAT1" and "ADP1" with variables, so configuration would be easier
Thanks I made changes according to your suggestion.
moljac024 wrote:laptop-mode tools has an option of running commands when battery charge reaches a certain level. You could just run notify-send from there.
You mean in the auto-hibernate section? I use it as it was supposed to be used -- for hibernating -- and I think you can only set one command that's executed according to a specified battery level in laptop-mode-tools. Plus it would be sort of complicated, since displaying the notification depends on two conditions in this script -- specified battery level and power cord being disconnected.

Help! iPhone 5 restarting by itself! Battery level won't change after charging.

HELP!
I have a 3 month old iPhone 5 that was recently updated to iOS 7. After a few days of use, I noticed after a night of charging, which I always do, the battery level indicator and percentage did not change. Next, in my carpool ride in to work, when using the iPhone, randomly the screen would freeze, then turn a random color and would shut off and restart.
Then all of a sudden it was fine, no issues.
Then today, the same thing is happening. The battery level, freezing/color changing on the screenscreen/restarting issues are back.
I don't know whats going on. Never had an issue with any of 3 past my iPhones.
Thanks in advance,
Josh

I'm sorry, it seems that the problem is that my phone WON'T restore. I just tried restoring again and it keeps giving me the 2001 error. Help.

Battery level software bug

All of a sudden the battery level of my iPhone 5 started to go down from %100 to 30, 20, 10 then 1% in less that a minute and then shuts down!! This happens sometimes after just a few minutes of unplugging the phone from the charger. This problem appeared only two weeks ago so I spent sometime searching for a solution or similar stories, and am certain that the battery charge level calibration in the new iPhone software has a bug in it..!! I am sure the capacity of the battery is fine, its just the charge level drops for some reason and the phone shuts down immediately though the battery is still full because when I plug it to the charger it takes a minute then it turns on showing 100% charge !!

As an update, I restored my iPhone to the factory settings but unfortunately it didn't work. I don't think I will take the phone to any Apple shop because there is no one in my city and the closest is around 40 miles away! Also my phone is just less than 1.5 years old so the timing for getting a fault was just perfect after the end of the warranty, so I guess I better fix it myself (most likely change the battery first).

Missing battery files in /proc/acpi/battery

I'm trying to employ this script:
http://mindspill.net/computing/linux-no … y-warning/
to get low battery warnings. It draws info from files like
BAT_STATE="/proc/acpi/battery/BAT1/state"
BAT_INFO="/proc/acpi/battery/BAT1/info"
but folder /proc/acpi/battery/ does not exist in my system. I do have /sys/class/power_supply/BAT0/ folder, but it does not containt 'state' or 'info' files.
What should I do to make this work?
Last edited by Lockheed (2012-06-06 10:49:13)

Maybe I am being a bit thick, but am not well versed in scripts.
I already modified the script to use notify-send rather than zenity
#!/bin/bash
# Location of acpi files.
BAT_STATE="/proc/acpi/battery/BAT1/state"
BAT_INFO="/proc/acpi/battery/BAT1/info"
# Minutes from the in-built warning level that measures should be taken to prevent loosing data.
BAT_ALERT_TIME=15
# Log to syslog & /var/log/acpid
LOGGER="/usr/bin/logger -t ACPID"
if grep -q discharging $BAT_STATE
then
BAT_REMAIN=`awk '/remaining/ { print $3 }' $BAT_STATE` # Remaining mAh.
BAT_DISCHARGE=`awk '/rate/ { print $3 }' $BAT_STATE` # Discharge rate in mA.
BAT_WARN=`awk '/warning/ { print $4 }' $BAT_INFO` # Warning level in mAh.
BAT_LOW=`awk '/low/ { print $4 }' $BAT_INFO` # Low level in mAh.
BAT_ALERT=$(( ( ( $BAT_DISCHARGE / 60 ) * $BAT_ALERT_TIME ) )) #+ $BAT_WARN )) # Work out the charge that will have been used in $BAT_ALERT_TIME minues (and add the warning level charge as a buffer zone).
#echo "BAT_REMAIN = $BAT_REMAIN"
#echo "BAT_ALERT = $BAT_ALERT"
# These environment variables are needed so that the script can post to the current display (using the zenity command). Change mention of steph to whatever your username is.
export XAUTHORITY=/home/steph/.Xauthority
export DISPLAY=:0
if
then
# Log the fact that the (critically) low level has been reached.
$LOGGER -p daemon.warn "Battery capacity is critically low, shutting down the system."
# Pop up critical warning.
/usr/bin/notify-send "Battery critically low." "HIBERNATING ($BAT_REMAIN)" &
# zenity --warning --title "Battery Critically Low" --text "Battery capacity is critically low, shutting down the system. (remain = $BAT_REMAIN)" &
# This is probably a good place to shut down the computer to make sure all data is written to disk. It may even be too late by now, in which case shut down the computer when it reaches the in-built warning level.
dbus-send --system --print-reply --dest="org.freedesktop.UPower" /org/freedesktop/UPower org.freedesktop.UPower.Hibernate
elif
then
# Log the fact that the warning level has been reached.
$LOGGER -p daemon.warn "Battery capacity is low."
# Pop up warning.
/usr/bin/notify-send "Battery low." "(remain = $BAT_REMAIN)" &
# zenity --warning --title "Battery Low" --text "Battery capacity is low. (remain = $BAT_REMAIN)" &
elif
then
# Log this to let the system know that there's only a few minutes left of battery before it hit the warning level of the battery pack
$LOGGER -p daemon.info "Battery capacity alert."
# Pop up info.
/usr/bin/notify-send "Battery depleting." "(remain = $BAT_REMAIN)" &
# zenity --info --title "Battery Alert" --text "Battery capacity alert. (remain = $BAT_REMAIN)" &
fi
fi
However, I suppose changing it to use acpi -V would involve more in-depth modifications which I am not sure of.

Why has apple stopped updating the ipod touch 2g

my ipod touch 2gen is on the latest vesion that is out for it but apple just stopped updating it

Only Apple knows why. It's likely that Apple decided that the newer versions of iOS would put too much of a strain on the iPod or that the iPod simply lacked the necessary hardware to operate with an acceptable level of performance using the newere versions of iOS.
B-rock

Battery Level Gauge for E61i - Help please

The battery indicator on the menu of these phones is hopeless and don't appear to be any better in the various themes available. Does anyone know where I can get a good basic battery guage - preferably freeware but I don't mind paying a few ££.
Thanks for any help.
Queensparker

With the headset switched on and connected wirelessly go to:
Settings > Accessories and you'll see the battery level there.
If you don't see it you need to make sure your Nokia apps are fully up to date, especially Accessories and Audio. You can find the codes to update them on this link:
http://discussions.nokia.com/t5/Pool-of-Knowledge/Nokia-Windows-Phone-8-App-Updates/td-p/1640082

Itunes never shows the battery level as charged.

left the shuffle connected overnight yet the battery level indicator in itunes remains a charging thunderbolt. any clue what gives? don't have the issue with the classic.

hmmm ... apparently an itunes glitch: it failed to notice when the other ipod was sated as well (the classic is a bit easier than the shuffle to independently determine its battery status). seems to be a random failure as for the last couple connections, the battery status for the shuffle was updated.

ACPI battery level stops updating

Similar Messages

Maybe you are looking for