Macbook Air (mid 2012, 13") charging very…

Macbook Air (mid 2012, 13") charging very slow after update to Yosemite

Hi everyone,

3 days ago, after the update to Yosemite, my Macbook Air (mid 2012, 13") battery (with around 130 charging cycles) started to charging very slow. I mean, very very slow. In this moment I have 34% charged, MagSafe plugged in and 20 hours (!!!) of estimated time in order to fully charge.

Here's the screenshot:

When MagSafe is not plugged in the battery drain is normal. It just takes very long time in order to charge.

I tried to use another charger (from a Macbook Pro Retina) but the problem is still there.

Anyone has experienced the same issue or have an idea on how to solve this?

Thanks for any help!

MacBook Air (13-inch Mid 2012), OS X Yosemite (10.10)

Posted on Oct 22, 2014 3:22 PM

Nov 28, 2016 8:28 AM in response to beppe86bs

I had exactly the same problem, with mid 2012 13" Air. Took three days to charge to 82%, and sometimes battery was shown with an X on it. When X was shown disconnecting the power supply would instantly go to black screen. But oddly enough reconnecting would cause the state to be restored to where it was before it went black.

FIXED:

Today I opened the back, and was going to swap the Power PCB (Has Mag connector one it. top right when upside down and keyboard towards you) from another working machine to see I could prove it was this at fault, and thus could order a new one. So I disconnected the 5cm ribbon jumper connector between the main PCB and the smaller power PCB, it can easily be prised off with a screw driver, or finger nail, but gently. I did also notice the keyboard connector looked as if it was not quite in, well I presume it was a keyboard connector, but may be wrong. It was mid-way up and slight to the left of canter. I pushed, and wiggle a few other connectors, on the power PCB, and decided not to change over the power PCB, so reconnected the jumper I had previously removed.

Screwed the back, back on and all appears to works fine now!

So what part of that procedure fixed it I don’t know… It could be removing the jumper reset something. But may be of help to someone else.