X41 Weird Battery state

Hi,
I have an X41, running XP. The battery status on this is weird. Here's what's happening:
The battery apparently has no charge - without the AC plugged in, the machine does not boot. When AC is removed when the machine is 'ON', it turns off. So far consistent with a dead battery.
Next, when I do turn the machine on with the battery in the slot, the machine boots. The Power Manager guage shows a constant charge of 42%. It neither increases, nor decreases. The baloon when the mouse points to this guage says:
(42%) remaining
Then, I fire up the Power Manager, and go to the 'Battery Information' tab.
Again, it shows:
Remaining Battery: 42%
Batteries installed: 1-main battery
Condition: Good (with a green battery)
The battery is in good condition.
At this point, I'm totally confused. I have checked the battery contacts, and the slot itself. All seem OK. I dont know what to believe. Do I have a dead battery? Or does it somehow have a disconnect internally?
Thanks for looking, and thanks in advance for responses.
lsiravi

i reinstalled lenovo's battery utility and opened it up to battery. i ran the reset which is supposed to charge to 100 then discharge to 0 then charge to 100. well it discharged just fine but wouldn't charge from 0. so i put the battery in an x40 and charged it to 93. i have the utility set to charge at 96. it said it was charging but the percentage remained the same. i then put the battery back in the x40 and charged it to 100. put it back in the x41 and ran the utility until it discharged to 90. then i turned off the utility and turned it back on and it said it was charging but it wasn't. i then called the co. that i got it from and me an tech support determined that the charging system on the board was bad. there are no resets, no fuses to change the only thing i can do is change the motherboard so we agreed to exchange it for an x40 which they had. i guess i'll go back to the old tried and true x40. the funny thing about this whole thing is the green light indicator showed a battery, the utility showed a battery, it showed the voltage of the battery, the voltage of the charging system, the only thing that didn't show on the utility was the time it was to take to charge it up to 100.
T430u, x301, x200T, x61T, x61, x32, x41T, x40, U160, ThinkPad Tablet 1838-22R, Z500 touch, Yoga Tab 2 Windows 8.1, Yoga Tablet 3 Pro
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
If someone helped you today, pay it forward. Help Someone Else!
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

Similar Messages

Battery state not present

Hi everybody
I have a Acer Aspire 5820TG TimelineX which is a really good laptop. But I have a big problem. I can't read the state of the battery.
This is what I get from acpi -V,
Battery 0: Unknown, 0%, rate information unavailable
Battery 0: design capacity 4400 mAh, last full capacity 4400 mAh = 100%
Adapter 0: on-line
Thermal 0: ok, 40.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 105.0 degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 98.0 degrees C
Cooling 0: LCD 0 of 9
Cooling 1: LCD 0 of 9
Cooling 2: Processor 0 of 10
Cooling 3: Processor 0 of 10
Cooling 4: Processor 0 of 10
Cooling 5: Processor 0 of 10
from /proc/acpi/battery/BAT1/state
present: yes
design capacity: 4400 mAh
last full capacity: 4400 mAh
battery technology: rechargeable
design voltage: 11100 mV
design capacity warning: 300 mAh
design capacity low: 132 mAh
cycle count: 0
capacity granularity 1: 32 mAh
capacity granularity 2: 32 mAh
model number: BAT1
serial number: 11
battery type: 11
OEM info: 11
As you can see, ACPI is well aware that the battery is present and its infomation
Some output from dmesg | grep ACPI if it helps
BIOS-e820: 00000000bb73b000 - 00000000bb7bf000 (ACPI NVS)
BIOS-e820: 00000000bb7e1000 - 00000000bb7ff000 (ACPI data)
modified: 00000000bb73b000 - 00000000bb7bf000 (ACPI NVS)
modified: 00000000bb7e1000 - 00000000bb7ff000 (ACPI data)
ACPI: RSDP 00000000000fe020 00024 (v02 ACRSYS)
ACPI: XSDT 00000000bb7fe120 0007C (v01 ACRSYS ACRPRDCT 00000001 01000013)
ACPI: FACP 00000000bb7fc000 000F4 (v04 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: DSDT 00000000bb7ed000 0BA9D (v02 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: FACS 00000000bb75f000 00040
ACPI: ASF! 00000000bb7fd000 000A5 (v32 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: HPET 00000000bb7fb000 00038 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: APIC 00000000bb7fa000 0008C (v02 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: MCFG 00000000bb7f9000 0003C (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: SLIC 00000000bb7ec000 00176 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: BOOT 00000000bb7e9000 00028 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: ASPT 00000000bb7e5000 00034 (v04 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: WDAT 00000000bb7e4000 00224 (v01 ACRSYS ACRPRDCT 00000001 1025 01000013)
ACPI: SSDT 00000000bb7e3000 009F1 (v01 PmRef CpuPm 00003000 INTL 20051117)
ACPI: SSDT 00000000bb7e1000 01E0F (v01 AmdRef AmdTabl 00001000 INTL 20051117)
ACPI: Local APIC address 0xfee00000
ACPI: PM-Timer IO Port: 0x408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x05] enabled)
ACPI: LAPIC (acpi_id[0x05] lapic_id[0x00] disabled)
ACPI: LAPIC (acpi_id[0x06] lapic_id[0x00] disabled)
ACPI: LAPIC (acpi_id[0x07] lapic_id[0x00] disabled)
ACPI: LAPIC (acpi_id[0x08] lapic_id[0x00] disabled)
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
#6 [0000012000 - 0000016000] ACPI WAKEUP
ACPI: Core revision 20100121
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
ACPI: bus type pci registered
ACPI: EC: Look up EC in DSDT
ACPI: Executed 1 blocks of module-level executable AML code
ACPI: BIOS _OSI(Linux) query ignored
ACPI: SSDT 00000000bb691c18 003AE (v01 PmRef Cpu0Ist 00003000 INTL 20051117)
ACPI: SSDT 00000000bb68f018 00891 (v01 PmRef Cpu0Cst 00003001 INTL 20051117)
ACPI: SSDT 00000000bb690a98 00303 (v01 PmRef ApIst 00003000 INTL 20051117)
ACPI: SSDT 00000000bb68ed98 00119 (v01 PmRef ApCst 00003000 INTL 20051117)
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: EC: GPE = 0x16, I/O: command/status = 0x66, data = 0x62
ACPI: No dock devices found.
PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
ACPI: PCI Root Bridge [CPBG] (0000:7f)
ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 *7 10 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 *7 11 12 14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
PCI: Using ACPI for IRQ routing
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 11 devices
ACPI: ACPI bus type pnp unregistered
pcieport 0000:00:01.0: Requesting control of PCIe PME from ACPI BIOS
pcieport 0000:00:01.0: Failed to receive control of PCIe PME service: ACPI _OSC failed
pcieport 0000:00:1c.0: Requesting control of PCIe PME from ACPI BIOS
pcieport 0000:00:1c.0: Failed to receive control of PCIe PME service: ACPI _OSC failed
pcieport 0000:00:1c.5: Requesting control of PCIe PME from ACPI BIOS
pcieport 0000:00:1c.5: Failed to receive control of PCIe PME service: ACPI _OSC failed
ACPI: resource 0000:00:1f.3 [io 0x4000-0x401f] conflicts with ACPI region SMBI [io 0x4000-0x400f 64bit pref disabled]
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI: Power Button [PWRB]
ACPI: Lid Switch [LID0]
ACPI: Sleep Button [SLPB]
ACPI: Power Button [PWRF]
ACPI: Thermal Zone [_TZ] (40 C)
ACPI: AC Adapter [ACAD] (on-line)
ACPI: Battery Slot [BAT1] (battery present)
ACPI: WMI: Mapper loaded
ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
[Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
ACPI: Video Device [PEGP] (multi-head: yes rom: no post: no)
[Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
I'm using the latest kernel from [testing] (2.6.34-ARCH).

docwario wrote:you should try to update the bios with the latest one from acer (actually 1.13),
battery state is now available
I updated BIOS to v1.15 - still no solution. I have, however, found out why I can't see if the battery is charged or not. Appearantly, Acer is not using the standard ACPI spec. Just look at this:
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20100121 [Feb 6 2010]
Copyright (c) 2000 - 2010 Intel Corporation
Supports ACPI Specification Revision 4.0
dsdt.dsl 5231: Method (_Q0E, 0, NotSerialized)
Warning 1088 - ^ Not all control paths return a value (_Q0E)
dsdt.dsl 6596: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 6600: Name (_T_1, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_1)
dsdt.dsl 6659: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 6663: Name (_T_1, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_1)
dsdt.dsl 6831: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 6835: Name (_T_1, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_1)
dsdt.dsl 6894: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 6898: Name (_T_1, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_1)
dsdt.dsl 7777: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 7870: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 7874: Name (_T_1, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_1)
dsdt.dsl 7941: Name (_T_2, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_2)
dsdt.dsl 8008: Method (OEMN, 0, NotSerialized)
Warning 1088 - ^ Not all control paths return a value (OEMN)
dsdt.dsl 8105: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 9124: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)
dsdt.dsl 9152: Name (_T_1, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_1)
dsdt.dsl 9182: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 9248: Method (_WED, 1, NotSerialized)
Warning 1088 - ^ Not all control paths return a value (_WED)
dsdt.dsl 9248: Method (_WED, 1, NotSerialized)
Warning 1081 - ^ Reserved method must return a value (_WED)
dsdt.dsl 9254: Return (OEMN ())
Warning 1093 - ^ Called method may not always return a value
dsdt.dsl 9399: Method (WMBH, 3, NotSerialized)
Warning 1088 - ^ Not all control paths return a value (WMBH)
dsdt.dsl 9456: Method (WMBI, 3, NotSerialized)
Warning 1088 - ^ Not all control paths return a value (WMBI)
dsdt.dsl 9518: Method (WMBJ, 3, NotSerialized)
Warning 1088 - ^ Not all control paths return a value (WMBJ)
dsdt.dsl 9616: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)
dsdt.dsl 9661: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)
ASL Input: dsdt.dsl - 12143 lines, 396315 bytes, 5129 keywords
AML Output: dsdt.aml - 47766 bytes, 1103 named objects, 4026 executable opcodes
Compilation complete. 0 Errors, 8 Warnings, 18 Remarks, 6 Optimizations
So I properly need to make a correct DSDT table to solve my problem. However, I can't make heads or tails in the ACPI spec document, and most infomation about such a issue is highly outdated.

2610 signal & battery state not visible

The display on my 2610 is difficult to see in bright light. I have set contrast to maximum and selected the basic theme to get black on white however the battery state and signal strength bars are still in light blue which is impossible to see in bright light. How do I change the colour of the bars to black?

go to display settings and you can select diff colours
If i have helped at all a click on the white star below would be nice thanks.
Now using the Lumia 1520

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)

Please help. two weird battery? icons...

Okay well recently I went to go plug in my ipod and I got this strange icon that looked like a battery with a lightning bolt and it was black..it didnt start updating my ipod or charing it so I got worried...I went to go do something and when I came back...everything was normal! Okay and the other day I was listening to my iPod and the battery went dead and said that I needed to charge it...that I did...so now yesterday i was listening to it and it wasnt dead yet and i thought that i would listen to it until the battery died but instead it just stopped (before the battery was fully gone I believe) and I got this weird battery icon with a WARNING! sign...can someone please tell me what those icons mean? and also...how long is the ipod suposed to take to charge and die out? I have the 30g new ipod. thanks again!

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Weird Battery Behavior in 7.1.1

Has anyone else noticed weird behavior after upgrading to 7.1.1 - on my 5s its not that the battery is draining quickly - in fact its showin 5 hours 40 minutes usage with 75% remaining - which i find hard to believe
whats weird is standby time equals the usage time but i have turnd off and aback on the iPhone - I even did a hard reset - i have a monitor program which is showing the cpu as mostly idling at 90% or more ( although the monitor probably doesnt know about the M7 chip - it probably doesnt even know about the A7 chip too)
The battery percentage is not going down quickly - it seems to be thr same rate as with 7.1 but i dont believe these numbers
Im going to let the battery drain completely and do a battery calibration - that some times helps after IOS upgrades
But i was wondering if anyone else was seeing this and had any suggestions

Grant Hiesterman wrote:
Out of curiousity, how were the issues fixed/resolved other the past? With IOS updates? Other?
The problem has always been an errant app that got stuck in a loop. It can happen any time, but is more likely to happen right after an update. My hypothesis is that the update process suspends running apps, and sometimes after the update they "lose their place" and spin their wheels trying to find it. (It's easier to say it that way then to talk about race conditions.) What will frequently fix it is to run the battery all the way down until the phone shuts off. This terminates all processes, even those that cannot be killed from the Quick Launch screen.
You can also try to find the app; if it's email turning off any Push email accounts, rebooting, and turning them back on will frequently fix it. If it's a 3rd party app killing all apps in the Quick Launch will frequently fix it.
Sometimes just turning off the phone for a few minutes will fix it.
Restoring the phone as new will usually fix it, but restoring from backup may not, because the app state may be preserved in the backup.
It really just a matter of trying things like these one at a time. One of them will work.
Do you or Trevor have a CPU monitoring app you believe is a quality application?
I've tried several, and haven't found any that I like. I like Trevor's answer.

Weird battery dillema

as soon as i unplug the nano from the computer, the nano battery indicator goes down, it sits on the computer till full.
any clues anyone?

@Sir McHillard
I know many people are having battery issues, but this one is weird, an automatic power down at 20% of the battery.
Thank you.

Weird battery behavior

A week ago while running on battery power my machine shutdown with no warning. I couldn't get it to power up until I plugged in the charger. My battery indicator at that time said "0" but I had been running on somewhere north of 70% when the shutdown occured. It obtained a full charge, according to the indicator, in about 20 minutes, which is unheard of for me when starting from zero.
Today, again while running on the battery, my machine hung for just a couple of seconds when I opened it and was about to resume work. (I hadn't logged out or put it to sleep prior, but simply closed the display, which is what I generally do when security isn't an issue.) I noticed almost immediately that my battery indicator read "0" where I would have expected it to be close to fully charged. Nevertheless, the machine didn't power down, and I used it for several minutes before rebooting to see it rebooting would reset the power indicator. It didn't. I used it for a few more minutes, then did a full shutdown. When I returned to the machine an hour later, it wouldn't power up until I switched to a different battery.
I have practically no experience with laptops and battery issues. This particular battery is less than a year old. This all reminds me of mobile phones I've had in the past that would suddenly power down or refuse to power up because the battery had become loose from use. A temporary fix for that was a business card wedged between the phone and the battery, but I don't think that's a great idea with laptop.
Anyway, just wondering if anyone has had a similar experience?
I'll keep you posted as the situation plays out.

There are known issues with the MBP batteries, which resulted in Apple extending warranty coverage for batteries to two years for all Core Duo laptops (they did not extend C2Ds, but those are all still under warranty). That extension is described on the linked page below, along with the statement "Apple has recently discovered that some batteries used in its MacBook and MacBook Pro notebooks may have battery performance issues."
http://www.apple.com/support/macbook_macbookpro/batteryupdate/
Check your cycle count in Utilities > System Profiler > click on Power. If the Full Charge Capacity is less than 4400 mAh for a 15" MBP or less than 5000 mAh for a 17" MBP, the battery is failing. Also check the cycle count. If you have more than 300 cycles on your battery, Apple will tell you that your battery is failing normally, and you will need to buy a new one. If you have less than 300 cycles on the battery, based on the symptoms you describe they will replace if for free (as they did for my 15 month-old out-of-warranty MBP).
Hope this helps...

Weird Battery Timing

Hey everyone, I have a MacBook Pro that I purchased about five months ago. Everything was fine until I downloaded Battery Update 1.2 At this point everytime I ran the machine with the battery I would receive incorrect times as to how much battery power was left. I would have a fully charged battery, and while pulling out the AC adapter it would state that I only have about 5 minutes left, and then it would put the message on screen that I'm running in low power mode, then the computer would shut off. I took my computer to the Genius Bar and had my battery replaced for a brand new one. I calibrated the battery but the timing issue still seems to be present. As I use my battery the time left fluctuates, it goes up and down. Before the update everything was nice and consistent. Any help would be much appreciated.
MacBook Pro Mac OS X (10.4.9)

Based on your description, it may suggest a conflict within permissions. You can verify permissions to see if your system identifies a conflict or otherwise perform the repair.
Repairing Permissions and/or Resetting the Power Management Unit (PMU) is known to resolve certain anomalies or conditions, and may help with your symptom. Neither process will compromise or harm anything with your Mac so it’s worth a shot.
Repair Permissions:
Go to: Applications/Utilities/Disk Utility
Select: your Hard Drive
Select: the First Aid tab
Select: Repair Permissions
Resetting the Power Management Unit (PMU)
If the computer is on, turn it off.
Disconnect the AC Adapter and remove the computer's battery.
Press and hold down the power button for 5 seconds and then release the button.
Reconnect the battery and AC Adapter.
Press the Power button to restart the computer.
Ref:
PMU: http://docs.info.apple.com/article.html?artnum=303319
User's Guide: page-95
Regards,

Weird Battery Usage Using the Dock's Line-Out

I have noticed something particularly weird about using my iPod w/the dock's line-out. (I have the original 60GB photo).
When I use the dock's line-out to connect to my home stereo via an RCA cable, I get roughly 3 hours of continuous play on a full charge before the battery meter changes decreases.
But when I use the dock's line-out to connect to my PC computer speakers via an RCA cable (at work), I get roughly 2 hours of continuous play on a full charge before the battery meter changes decreases.
Anyone have any ideas what may be causing the shorter battery life while listening via PC speakers?
Lisa

Hi Carl - thanks for the reply. I consistently get 15 hours of continuous play from my battery. Yep, the battery & meter are properly calibrated (in fact, I'm pretty anal about that!) I'm not sure I'm getting less battery life, per se, I just find it interesting that I get 2 different readings from using the line-out in 2 different configurations. I'm assuming that maybe the PC speakers are using more power? I'm not electrically-inclined, and maybe I'm just going on a wild goose chase!
Lisa

Weird Battery Activity: It regenerates!!

Never experienced this panorama experience before...
I am using SONY XPERIA sola and I updated the device (myself using the Update center in the phone) to the latest GingerBread firmware...
...and soon I realised that it drained the battery like HELL!! (but I already get used to it anyway since it still new to me...)
What really weird is that somehow, though the battery drain super-fast (when running CPU-hungry apps) and the battery dropped like a rollercoaster...
...I found out that somehow the battery REGENERATES itself...
-See at the middle- (I DID NOT EDIT!)
There's a bit lift off in the middle line and as you can see I DIDN'T CHARGE IT at that time...
It isn't just my phone, some of my friends (which they were WALKMAN series users) also had this weird condition happen...
So... What did you put into making a battery, SONY? XD (or my phone and/or battery had problems??)
Solved!
Go to Solution.

Anyone... Help!!
Can anyone teach me how to fix the firmware of my phone using the PC Companion (without having upgrade to ICS because I have a feeling that it won't fix my problem but making it worse!)?
My battery is worsened by the minute...
...and don't tell me to use the method:
1. Turn off the phone, open the phone's back cover, remove it, wait 5 mins, and so on...
...because the problem here is that my phone is locked with screws...
Anyone can help, many thanks and appreciated..

Weird Battery Time

I recently charged my battery, and was using the option of showing how much time it has before the battery was drained...The time said it was 11:00 but then after a few minutes it changed to the actual believable time.
Why does it show that weird time, but then go back to normal?

Not to woory. Mine said 13 hours until I actually did something.

Weird battery charging behaviour

Ok, I'll start by saying that this is a problem that has been coming and going for quite a while (definitely months, maybe years). But for the sake of illustration, I'll describe what happened today.
So last night I was using my laptop on the couch (not plugged in) and fell asleep. Woke up to a dead battery. No problem, I plugged it in and woke it up and was good to go. Several hours later I noticed that my battery charge was still at 1 or 2%, though clearly it was running just fine off AC power. Looking at the light on the power adapter, I thought it was completely off until I read a few support posts and found out that "dim green" is an option. Upon close examination, yep, dim green. System Information said the battery itself was ok (cycle count 153, condition normal) but not charging. Under AC Charger Information, it said Connected: yes, Charging: no.
Unplugging and replugging the adapter a few times didn't seem to do anything. There's no obvious gunk in around the terminals. I shut down and reset SMC, no change. Finally I just fiddled with the adaptor (unplug, replug, flip around, wiggle up and down) until the light turned briefly green, and then orange. Now it's clearly charging (up to 38% now, and battery icon has a little lightning bolt) although System Info still says it isn't charging.
Oh, hang on. I just quit and restarted System Info, and now it says it is charging! Huh.
Addendum: While adding tags I noticed that the light on the adapter is back to dim green. System info still says it's charging, and battery % charged numbers are still going up.
I'm guessing it's an issue with the magsafe adaptor, just not sure how you end up with a temporary situation where the laptop can run on AC power but can't charge the battery.
Oh, and in case it's relevant: I'm running a 13" mid-to-late 2009 MacBook Pro, the kind with a non-removable battery, though I did have the battery replaced (by a friend who is Apple-certified) less than a year ago. The AC adaptor I'm using is the one that came with the computer. I'm pretty sure the problem pre-dates the new battery (since it comes and goes, and because I spend a lot of time using the laptop at home while plugged in, I don't always notice).

I had this exact same problem with my mid-2009 MBP as well. My adapter (white connector) has suddenly stopped charging the computer and displayed a very dim-green LED instead of the normal orange or bright green.
I came to the conclusion that the adapter has been shorted out in some way (possibly due to old age) and that was the cause of this. Sure enough my local Apple retailer sold me a new adapter that everything has been fine ever since. I even enjoy the new design - the metal-tipped connector that faces sideways.
Unfortunately the adapter cost me $80, but was a small price to pay as opposed to replacing my laptop. Since this sounds like the exact same issue I faced, I would recommend you purchase a new MagSafe. Just make sure you get the right one for your model (should be a 60W MagSafe)
Hope this helps you out!

Lumia series has very weird battery usage, please ...

Hey. I have a lumia 920 and a 1020, and my wife has a 925. All of them does the same thing, and I can not for the life of me figure out why it does it.
Suddenly it will use the battery like crazy. I mean crazy as in losing 50% in an hour laying idle. It might even restart sometimes. I have played around with all sort of settings making sure nothing is turned on that does not need to be on.
It does this at random, and at random times. It might be days between.
I tried all sort of battery apps to see if I could find one that would specify what the battery was used on, but as fare as I can see there is no such app. There is graphs and % per hour and so on, but no specific power usage app.
I really hope that I am not alone in this, and there is a solution out there. It is a really big problem as the phone has ran out of power in the middle of the night, and I use it as an alarm clock. It has used 100% just laying on the table in 1 night, though I am not sure when exactly it ran out of juice.
Anyone know **bleep** is going on? This is the 3ed phone that does it, and I dont know whats wrong here.

There have been instances where I have experienced excessive battery drain on my Lumia phones. The worst was due to my Exchange account which tore through my battery in just a few short hours. What actually happened was that my company decided to block all access to everyones accounts while they were carrying out some security work but my phone went into overdrive trying to constantly synchronise with the servers and failing. This caused the battery to drain very rapidly indeed.
So my first tip would be to check out all accounts and apps that have a regular sync interval or require an active internet connection to function. Things like instant messenger apps (Viber, WhatsApp and Skype) and also have a look at your Email accounts.
Sometimes though, it can something as simple as a stuck process using the CPU but these can be difficult to identify and pin down.
Another major cause of excessive battery drain is when the phone is looking for a 3G/4G signal when you are in an area with poor 3G/4G coverage. 4G especially will be a big power hog and have more of an impact on your battery than 3G because it naturally uses more power than 3G.
Lastly, you can search the forum for "Excess battery drain" or words to that effect for other help and advice, as this topic has been discussed quite a bit already.

Weird import statement problem

Hi
I have a strange problem with an application I just developed. Once compiled, if I try to run it on another machine other than the one I developed on, I get a NoClassDefFoundError relating to a class that I did not use. I look at the class file (in a decompiled state) and there is an import statement in there that is not in the source file!! Can anyone tell me why this might have happened?
the import is a symantec class/package I have never used to my knowledge at all and yet it shows up in the binary class file after compilation.
Thanks for any suggestions.

I did use Visual Cafe during parts of the development but I have never imported anything like what is in the class file. I assumed it was VC that was doing it but wasn't sure.
Thanks.

X41 Weird Battery state

Similar Messages

Maybe you are looking for