Search results

Thanks, I can confirm everything is back to the roots here. Also, no 0xffff temperature reported. Cheers

Ah, no problem. Find it attached.

They do, but they are compiled with different code having one subtle difference. The 'sw' dump is taken with original 1.70.0 installed, whereas the 'hw' has the following applied: diff --git a/AppleSmartBatteryManager/AppleSmartBattery.cpp b/AppleSmartBatteryManager/AppleSmartBattery.cpp index...

Yeah, I guess it has to do with Apple software treating the battery having a valid serial number properly, whereas a number that is part unknown doesn't result in the 'service battery' indication. Like I said, the diff I've posted earlier is the only code change I've done (hw) compared to the...

Yeah, that I was aware of. Was just giving an example of how it was written prior to switching to the new kext. Was after a way of getting the data from RMCF That worked wonders, thanks! Looking at your code snipped I've realized that I've managed to miss ACPI spec 6.0 completely .. need to...

Thanks for this new opportunity, that seems like a neater solution compared to what we have been using for ages! I have a question in regards to getting to the data from the ACPI config. I used to use the SAVE method with ACPIBacklight to properly store the backlight level for soft/cold boot...

It's the one I've linked to in the post, this would be the exact place: 469517ba2d54b844371b9a30081fb6830980ef8b - 'ACPI-based configuration' et al. No, it's not that. The battery has indeed seen better times, the capacities are reported OK and even with all the corrective flags left at default...

Ok, that method did suffer changes - original pre-1.60 commit. The serial construct method used to be void and wasn't being passed any args. It was being called from setBatteryBST, which at the time already had fDeviceName and fSerialNumber from evaluating BIF using setBatteryBIF earlier .. not...

All is does is concatenates two strings:- device name and serial number with a dash in between. Did look through the commits and nothing has changed indeed, perhaps a timing issue .. but then BST would have had a change to update it a later time, but it never does. I will try to build some of...

Hey there, finally catching up with things ... installing your latest releases and getting around with setting them up. Stumbled upon a bug when comprising the serial number for system profile? 06.25.16 9:29:38.000 PM kernel[0]: ACPIBatteryManager: setBatteryBIF: acpibat_bif size = 13...

There's nothing else that would tell the driver F9 has to be pressed, since you are calling an ACPI method for scan code of Fn+F9 instead of a proper F key and the method itself doesn't produce any notifications to PS2K. I may be wrong though, but when mapping reverse actions the only way I...

I was reversing pesky EC behavior for my touchpad LED, which resulted in an iffy solution. EC enables the LED way too fast, so the RKA1 that does the Not on the current value falls behind and I can see the LED flashing rapidly when I want to access F3 through Fn+F3 having the keys swapped. Is...

Here are some hints as to how one can align BIOS backlight levels with what ACPIBacklight sets upon reading value from nvram so that it's consistent. If you are in a boat like me, when writing LEVL value to registers used by BIOS on boot doesn’t really play that well, because it ends up lost not...

I think it does indeed send something .. just not sure what the mechanism is. I had just checked the setting in Keyboard preferences to "Use F keys as standard function keys" an upon adjusting both sound and brightness they change by two bars at a time, so the BT keyboard interferes on NX events...

WOW. You can't even imagine the BS behind this problem :D It's the apple bluetooth keyboard that does this kind of crap. If you have the keyboard connected (my Dekstop was off for the past couple of days, so the keyboard was connecting to laptop because it's pared here too when I have it on a...

Well, I'm now writing just the required register directly to allow BIOS to recover the levels. I'm genuinely curious though as to why it works at the login screen at all times and then randomly doesn't when I'm logged in. It this seriously an OSX bug? If so, how come it's so random ...

I meant that you are mapping adb 90 and 91 to RKAs in order to turn on display if it's off. P.S. After another restart even with the buttons remapped it has stopped working again :| I'm lost.

Well, I'm actually relying on it being unchecked, as the mode I was trying to fix is the *special mode* .. which doesn't require Fn press. Seems like it fixed it though .. Since I no longer need to run the original EC queries, because I've transplanted everything needed for NVRAM...

ok, something really odd here in regards to the issue I was describing initially. when I'm logged in, having the backlight control key pressed down doesn't do anything. it adjusts the level by one on key down and thats it. when I release the key the up event is generated: 2/13/15 7:03:50.000...

I have my _BCL matching the original backlight levels already, so all is fine there. It works exactly the same as it did before, but way cleaner! // the range is set to comply with what windows sets - 6% to 90% with 6% increments, then 100% Thanks for hinting about this!