Elitebook 1050 G1:Battery status is not accurate

[Kuque]

100% of the battery will last a long time before it starts to drop.Then get inaccurate battery remaining percentage.
Remaining mAh of the battery is inconsistent with the percentage status.Errors will exist for a long time and will not be corrected automatically.

 

[RehabMan]

100% of the battery will last a long time before it starts to drop.Then get inaccurate battery remaining percentage.
Remaining mAh of the battery is inconsistent with the percentage status.Errors will exist for a long time and will not be corrected automatically.

You need to do further analysis... is the problem present in ioreg, or just the system battery status not responding to changes in ioreg?
If system is just no updating, but ioreg data from ACPIBatteryManager.kext is accurate, look into abm_firstpolldelay kernel flag.

 

[Kuque]

ioreg data from ACPIBatteryManager.kext is accurate

thanks for your help.
Accurate.Now the battery has 95% remaining power, the system status shows 100% and full charge.

abm_firstpolldelay kernel flag

Using this parameter to set the post-start delay to 8 seconds will automatically display the battery status, but the battery percentage is still incorrect.
I set it to 8000, and now OSX shows that the battery status does not need to be manually turned on.

 

[RehabMan]

thanks for your help.
Accurate.Now the battery has 95% remaining power, the system status shows 100% and full charge.
View attachment 345121


Using this parameter to set the post-start delay to 8 seconds will automatically display the battery status, but the battery percentage is still incorrect.
I set it to 8000, and now OSX shows that the battery status does not need to be manually turned on.

You might try larger abm_firstpolldelay.
Or install to HFS+J instead of APFS.
Or different SMBIOS (MacBookPro11,1).

Also, looking at your ioreg, Android File Transfer is causing problems. See FAQ for details:
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

And you should be using AptioMemoryFix.efi instead of OsxAptioFixDrv-64.efi+EmuVariableUefi-64.efi. If OsxAptioFixDrv-64.efi is required, don't forget that RC scripts are required when using EmuVariableUefi-64.efi.

 

[Kuque]

Or install to HFS+J instead of APFS.
Or different SMBIOS (MacBookPro11,1).

All right,I will check it out from other places.

Android File Transfer is causing problems

Uninstalled.

you should be using AptioMemoryFix

The BIOS often reports "clock power is exhausted." So canceled...


In the new system version 17G2112, the matching Thunderbolt 3USB controller driver was obtained, and of course the Thunderbolt devices itself could not be operated...

 

[hasodikis]

You might try larger abm_firstpolldelay.
Or install to HFS+J instead of APFS.
Or different SMBIOS (MacBookPro11,1).

Also, looking at your ioreg, Android File Transfer is causing problems. See FAQ for details:
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

And you should be using AptioMemoryFix.efi instead of OsxAptioFixDrv-64.efi+EmuVariableUefi-64.efi. If OsxAptioFixDrv-64.efi is required, don't forget that RC scripts are required when using EmuVariableUefi-64.efi.

What if the problem is present in IOReg?
What is the next step in such a case?