- Joined
- Mar 31, 2011
- Messages
- 1
- Motherboard
- Gigabyte GA-EX58
- CPU
- Intel Core-i7 920 @ 2.66
- Graphics
- GTX 270
- Mac
- Classic Mac
- Mobile Phone
Same problem here with the Apple Bluetooth Keyboard and CSR BT Dongle with product ID: 0x0001 vendor ID: 0x0a12 ver: 19.5. Also, I am running Mountain Lion 10.8.2 with USBBusFix (incase that matters).
I put the CSRAppleBluetooth.kext into S/L/E/IOBluetoothFamily.Kext/Contents/Plugins
I deleted CSRUSBBluetoothHCIController.kext but left behind CSRHIDTransitionDriver.kext
For some reason, I thought it might help with the pairing with my keyboard since, you know, HID = Human Interface Device = KEYBOARDS. Thought it might be useful.
I wonder, does S/L/E/IOBluetoothFamily.kext/ContCSRHIDTransitionDriver.kext/Contents/Info.plist need a little tweaking in order to get it to work with CSRAppleBluetooth.kext?
Then i went to /Library/Preferences and deleted com.apple.Bluetooth.plist and emptied the trash.
Repaired permissions, ran kext utility, and restarted.
Everything else seems to work well, except for my gosh darn Apple BT keyboard. I'll mess around with it a bit more and see what I can do but it may just have something to do with the firmware.
I put the CSRAppleBluetooth.kext into S/L/E/IOBluetoothFamily.Kext/Contents/Plugins
I deleted CSRUSBBluetoothHCIController.kext but left behind CSRHIDTransitionDriver.kext
For some reason, I thought it might help with the pairing with my keyboard since, you know, HID = Human Interface Device = KEYBOARDS. Thought it might be useful.
I wonder, does S/L/E/IOBluetoothFamily.kext/ContCSRHIDTransitionDriver.kext/Contents/Info.plist need a little tweaking in order to get it to work with CSRAppleBluetooth.kext?
Then i went to /Library/Preferences and deleted com.apple.Bluetooth.plist and emptied the trash.
Repaired permissions, ran kext utility, and restarted.
Everything else seems to work well, except for my gosh darn Apple BT keyboard. I'll mess around with it a bit more and see what I can do but it may just have something to do with the firmware.
