Battery replacement odd behavior
Hello IFIXIT community,
I recently bought the MacBook Pro replacement battery kit that IFIXIT provides to their customers so they can do Apple’s job at a cheaper price. I was able to install the battery with no issues at all.
But, after a day, while using my computer after calibrating the battery for better results I decided to restart the laptop for some testing not related to its battery life. Before I rebooted, the machine life was at 69% but after turning it back on, the battery was showing me a 6% battery life which is super odd and insane at the same time.
If there is anyone that experienced this with their replacement and/or noticed but went away later after constantly using the machine, please let me know. I am an IT guy myself, but I do want to make sure I am not the only one that has seen this odd behavior on a computer.
I hope that somebody can share any thoughts and or a solution to this. In the meantime, I will disconnect the battery adapter and put it back in just to see if it is just a mistake I made.
Hope somebody answers soon. Cheers community!!
Is this a good question?
9 Comments
Please post a snapshot of CoconutBattery so we can see the batteries status Adding images to an existing question
by Dan
Hello Dan,
Thank you for commenting on my post. I have edited the content and the image should be now displayed. To me everything looks fine on the battery, also checked other battery apps while waiting for this response last night. Is there anything in mind that could be causing this?
by Daniel Mazariego
@danj Today while using two different battery use checkers or whatever you want to call them, I noticed that they provide different numbers from the battery's charge for example:
The mac battery shows 73% and so does the app "Battery Monitor". While coconut battery shows 67% and the mac battery shows 73%.
Do you have any idea why this could be?
Thank you
by Daniel Mazariego
@poporobright Coconut battery always shows a lower percentage except for when battery is fully charged.
by arbaman
@arbaman - Correct! This is mostly do to the lag between the OS call to SMC from the app and its reply. Unlike the OS's native access to SMC.
by Dan
Show 4 more comments