Jump to content

E6410 - Monitoring of aftermarket battery


jkl555

Recommended Posts

You're right, especially since there is more then one maintenance out there...
 
Initially i used patel's one from the Official guide for E6410 nVidia, and let me quote myself when i did the aforementioned change:
 
 

Initially, the built in battery monitor from apple was toast, very inconsistent results, then i got SmartBatterySlim but even this one showed very odd numbers due to the battery being a double one (i think).
 
What i did is, updated these:
 
https://github.com/RehabMan/OS-X-ACPI-Battery-Driver
http://sourceforge.net/projects/hwsensors/ ( http://www.hwsensors.com/releases seems more updated) which will update FakeSMC as well.
 
Now HWSensors ICON in the BAR can be changed to show the percentage of the battery. So far, this has been the only way for me to have accurate battery output.

 

 

Basically i have no idea which one i've used, the packaged one or RehabMan's :(...

Link to comment
Share on other sites

I don't quite remember which version of FakeSMC I am using either. Anyway, I try the DSDT patch for Dell XPS 18 even though it is not the same model (https://github.com/RehabMan/Laptop-DSDT-Patch/tree/master/battery) and revert the AppleACPIPlatform.kext from  patel's one from the Official guide for E6410 nVidia back to stock version and it seems to fix the problem.

Link to comment
Share on other sites

forgive me for the delay peeps

 

Again, i have no idea why i have two FakeSMC's, one in Clover and the other in S/L/E, and i really doubt this may be the reason why the percentage reading disappear randomly time to time (HWSensors doesnt read anything)

 

so this is the FakeSMC at Clover:

 

2yo3j45.png

And kextstat shows the same version:

xxx:~ xxx$ kextstat | grep Fake
   24    3 0xffffff7f82e4c000 0x11000    0x11000    org.netkas.driver.FakeSMC (1613) <11 7 5 4 3 1>

and this is the one from S/L/E:

 

ddc7c1.png

 

weird...and noobish ofc

Link to comment
Share on other sites

  • Administrators

they have different file sizes so i would imagine they are different.

maybe one you used the package installer and it installed to S/L/E.

hwmonitor app usually has to be used with the version of fakesmc it came bundled with.

so either make both the same or remove one. if you look inside the kext you might see the version numbers inside it's info.plist to compare them. remember to rebuild your caches if you add or remove kexts from S/L/E.

Link to comment
Share on other sites

  • Administrators

SysProfiler->Software->Extensions will list the various kexts installed and loaded along with version numbers and file location. You'll then be able to eventually remove the extra/unecessary duplicate FakeSMC.

Link to comment
Share on other sites

×
×
  • Create New...