Help me with my laptop on Mojave (Inspiron 5570)

[Trunyce]

8 hours ago, Jake Lo said:

@kostas54

 

I've been looking over the issue with the Battery status.

I had installed CoconutBattery and confirmed the issue.

I've tested both ACPIBatteryManager and SMCBatteryManager.

I've tested on my E7470, E7450 and E7440 ( Skylake, Broadwell and Haswell respectively)

I've tested on Sierra, High Sierra, and Mojave, it appears to the same issue across the board.

I'll have to test Sierra with an older ACPIBatteryManager and see if issue occur even further back.

 

Crazy thing is i thought i was the only one facing that issue on my E7440 running Mojave. I had Sierra running on this machine prior to doing a fresh install due to having to switch to another SSD.. I even tried older battery kext and the problem still persists..Hope you will be able to find the solution to this problem.  Also if i might add, i love the gestures on the trackpad, however, it feels too sensitive when doing two finger scrolling.

[kostas54]

2 hours ago, Jake Lo said:

https://www.coconut-flavour.com/coconutbattery/

 

 

Perhaps this statement is true for MacOS too. 

You could ask the developer with that question.

chris(at)coconut-flavour.com

It's not just between macos and coconut. Bios also agrees with coconut.

On my previous dell 3542 laptop didn't have this problem. On both HS and Mojave.

Biggest problem is that if you want to optimise battery life and unplug when  macos says it's fully charged , then actually battery needs additional 15-20min to fuly charged.

[kostas54]

@Jake Lo , I'm facing another problem.

When lid close and reopen system reboot.

Can you take a look? Maybe something wrong with my hotpatch?

debug_8975.zip

[gebele04]

Hello Kostas54,

 

With your previous EFI Folder version, I don't observed this kind of problem. I can close and open the lid without reboot.

 

Grég

[kostas54]

Started hotpatching from the scratch and everything working fine , except this lid opening thing.

[viking1304]

13 hours ago, Jake Lo said:

I've been looking over the issue with the Battery status.

I had installed CoconutBattery and confirmed the issue.

I've tested both ACPIBatteryManager and SMCBatteryManager.

I've tested on my E7470, E7450 and E7440 ( Skylake, Broadwell and Haswell respectively)

I've tested on Sierra, High Sierra, and Mojave, it appears to the same issue across the board.

I'll have to test Sierra with an older ACPIBatteryManager and see if issue occur even further back.

 

 

I don't see this issue on my system (E7450 + VirtualSMC + SMCBatteryManager).

dragon:~ viking$ ioreg -w0 -l | grep "Capacity"
      |         "AppleRawCurrentCapacity" = 1194
      |         "AppleRawMaxCapacity" = 5456
      |         "MaxCapacity" = 5456
      |         "CurrentCapacity" = 1194
      |         "LegacyBatteryInfo" = {"Amperage"=18446744073709549617,"Flags"=4,"Capacity"=5456,"Current"=1194,"Voltage"=7366,"Cycle Count"=0}
      |         "DesignCapacity" = 6660
      |         "BatteryData" = {"StateOfCharge"=5376,"Voltage"=7366,"QmaxCell1"=0,"ResScale"=0,"QmaxCell2"=0,"QmaxCell0"=0,"CycleCount"=0,"DesignCapacity"=6660}

As you can see MaxCapacity is same as AppleRawMaxCapacity and CurrentCapacity is same as AppleRawCurrentCapacity. Since there is no difference, it's expected to get same results whatever value is used. There might be slight difference because of different number rounding rules.

 

In this example 1194 is 21.8841642228739 percent of 5456.

 

CoconutBattery:

 

 

iStatMenus:

 

 

macOS:

 

 

Looks like Cycle Count and Battery Temperature are always 0 with virtualSMC. Coconut wrongly displays absolute zero when it reads 0 value for temperature. 

[kostas54]

I don't have these "raw" entries.

[kostas54]

Ok, solved the "lid opening" problem.

 

Apart from the vattery readings , everything seems fine. But I'm not an expert and hotpach is very tricky.

 

@Jake Lo , I need your help and time for one more time.

Can you look at my config to see if there are any errors with hotpatching , errors in logs etc ?

Thank you in advance.

 

debug_1628.zip

[viking1304]

2 hours ago, kostas54 said:

I don't have these "raw" entries.

You don't see those values because you are using FakeSMC.kext and ACPIBatteryManager.kext, but that is not an issue here.

 

Values that you are getting from command line are same as those from Coconut. I made a test with ACPIBatteryManager.

 

First I checked Coconut:

 

 

And few seconds later I checked ioreg from terminal:

dragon:~ viking$ ioreg -w0 -l | grep "Capacity"
    | |   |   "Configuration" = {"Correct16bitSignedCurrentRate"=Yes,"UseDesignVoltageForDesignCapacity"=Yes,"EstimateCycleCountDivisor"=6,"UseExtraBatteryInformationMethod"=Yes,"UseDesignVoltageForMaxCapacity"=Yes,"UseExtendedBatteryInformationMethod"=Yes,"CorrectCorruptCapacities"=Yes,"StartupDelay"=0,"FirstPollDelay"=4000,"CurrentDischargeRateMax"=20000,"UseDesignVoltageForCurrentCapacity"=Yes}
    | |         "MaxCapacity" = 5527
    | |         "CurrentCapacity" = 3341
    | |         "LegacyBatteryInfo" = {"Amperage"=18446744073709550173,"Flags"=4,"Capacity"=5527,"Current"=3341,"Voltage"=7601,"Cycle Count"=188}
    | |         "DesignCapacity" = 6660
dragon:~ viking$

 

And that is perfectly fine since there was a few seconds difference.

 

3353 is 60.66582232676% of 5527.
3341 is 60.448706350642% of 5527.

 

So, Coconut and ioreg are in sync. So everything looks fine, but...

 

iStatMenus showed this:

 

 

And same (wrong) percentage was displayed by OS:

 

 

Since those values are higher than real ones, there are only two potential reasons:

 

1. one of two values (or even both) used for calculation that system gets are wrong - but this is almost impossible since ioreg values are correct

2. system gets result with delay - is even more problematic to comprehend the possible reason for this

 

@Jake Lo I am totally confused now, since you wrote that you noticed this difference even with VirtualSMC. I will revert VirtualSMC and repeat those tests again. 

[kostas54]

No , I'm using virtualsmc and smcbattery kexts.

 

Something interesting , which could be the reason for this problem is that , as I said before , when I use hot patch I don't get raw values.

But I tried again with a dsdt static patch and battery percentage is the same both for coconut and macOS and raw value are back.

 

Something missing from ACPI hotpatch ?