- Joined
- May 30, 2011
- Messages
- 11
- Motherboard
- x230t Lenovo
- CPU
- i7-3520M
- Graphics
- Intel HD 4000
- Mac
- Classic Mac
- Mobile Phone
I found a way to block the system from communicating with the digitizer so that Controller Mate can take over. However, it's not a really good option cause the kext that I'm disabling could possibly be used by other HID devices in the futur and on top of that, I didn't find a way yet to enable the pressure sensitivity and eraser on the digitizer. You could try this to see what you think about this not so good workaround:
In your Terminal
- sudo su (enter your password)
- cd /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/
- mv IOHIDEventDriverSafeBoot.kext IOHIDEventDriverSafeBoot.kext.bak
after that, repair permissions with Kext Utility and reboot. If you get any kernel panic, reboot with ignoring caches (-f) at the first restart.
Then Controller Mate will be the only one using your Tablet. If you want to reenable the IOHIDEventDriver, you need to redo the previous steps but "mv" the IOHIDEventDriverSafeBoot.kext.bak to IOHIDEventDriverSafeBoot.kext, then repair and reboot.
Here's the Controller Mate file that I'm working on.
In your Terminal
- sudo su (enter your password)
- cd /System/Library/Extensions/IOHIDFamily.kext/Contents/PlugIns/
- mv IOHIDEventDriverSafeBoot.kext IOHIDEventDriverSafeBoot.kext.bak
after that, repair permissions with Kext Utility and reboot. If you get any kernel panic, reboot with ignoring caches (-f) at the first restart.
Then Controller Mate will be the only one using your Tablet. If you want to reenable the IOHIDEventDriver, you need to redo the previous steps but "mv" the IOHIDEventDriverSafeBoot.kext.bak to IOHIDEventDriverSafeBoot.kext, then repair and reboot.
Here's the Controller Mate file that I'm working on.