OSX dithering - Help wanted
That's interesting that you're noticing some difference at the boot-up screen, comforting to know that it is doing something. After I spoke to the original developer he confirmed that it does do exactly what we want it to, but it checks for hardware belonging to the company that it was developed for - perhaps it does this after you log in. I'm guessing your MacOS desktop doesn't look any different?
We just need to find a way to bypass this check!
- Edited
I managed to unload the ahkinject.kext files, and nothing has changed. It turned out that both the glitch halfway through the loading process and that washed-off effect in the initial page where I select the account, well they were not related to the Amulet Hotkey kext but they are instead just some Apple bugs introduced in this latest release. Not surprising, since the quality of software updates by Apple has been appaling for some time now.
I'm afraid I have long since abandoned Macbook laptops - they just won't work for me, and I also believe that Apple is intending to deprecate the KEXT system in favour of System Extensions, which would mean a rewrite of the code.
The main issue is that the KEXT checks for the Amulet hardware being attached by USB - so you could reverse engineer the code to bypass this check but I'm not entirely sure who to approach to do that. The key info the developer gave me was:
- Crucially, they were only able to develop the kext because of a tight relationship between the company he was working for and ATI/AMD, who guided them on how to tweak the right parameters to disable the dithering. They didn't speak to Apple at all, this was done entirely with ATI/AMD as temporal dithering exists at the GPU driver level in MacOS - it's an abstraction the kernel has no interest in handling directly, it just tells the GPU/driver what colour it was where in the framebuffer
- There is a hardware check as a 'dongle' for the kext. This could be bypassed by patching the kext to USB vendor ID that the kext looks for to verify hardware. I think this is where we should focus our attention as once bypassed it will at the very least allow us to rule out temporal dithering as the root cause of our issue in MacOS.
Hope that helps somehow!
MAS-76 'bricked' the machine? if you just mean rendering the operating-system inoperable having a backup of the kext directory thats restored in single-user mode and clearing the kext-cache should get you going again.
sadly the steps for this can vary on the operating-system version. the internet is your friend.