MacsAre1

I had it in SLE. Weirdest thing -- I uninstalled the kext due to the kernel panics, and Bluetooth is still working, even after a cold boot. Maybe I don't need this after all to get my adapter working? Or is there any chance the firmware upload could stick? So, yeah, as long as BT works I'm probably not going to reinstall.

I'm not using the wifi since as far as I know there are no drivers for this card. The only other nonstandard kexts I was running were FakeSMC and the patched AppleIntelCPUPM. I uninstalled the BTFirmwareUploader and it seems to be working fine at the moment. Bluetooth is also still working as I have only done restarts since doing that, no cold boots yet.

Here's my ioreg file: ioreg.ioreg.zip I switch frequently from OS X to Windows so really need this to work quickly. Having to bend down under my desk to reach the power button isn't helpful as part of the process. Oh, and regarding my current boot issue: I had issues booting even using my "known good" Clover off my install USB stick. When Mavericks boots it seems to boot up fine, then logs in automatically and promptly restarts. I checked the kernel panic logs and the first extension in backtrace is com.apple.iokit.IOBluetoothFamily. Unfortunately this seems to point fingers at this kext. I'm going to uninstall and see if my system works properly. This panic/restart doesn't happen every time, as the system booted now and I was able to pair my mouse. I can send my panic logs if it helps. When it doesn't panic, I get messages during startup for BTFirmware Uploader : Failed to get device state, error. This is repeated three times with -536854449 twice and -536870163 once. Then it says "failed to patch the firmware" but apparently tries again as it eventually says "Successfully patched the firmware and loaded sysconfig into device" and then works.

My system is currently not booting to Mavericks so I can't check that just yet. Presumably this is because I was playing around trying to improve my Clover SSDT settings, hopefully not because of the BT kext. But I found this thread by searching for the device ID. I believe it was the PID e004 you have listed. Dell calls it the 1703. I do have another question, though. After installing this kext and it worked fine in Mavericks, now my Bluetooth mouse kept losing its connection after idle in Windows 8.1. This hadn't happened before. Now it wouldn't reconnect until I opened up the Bluetooth devices Metro control panel. I turned off the option to power the device off to save power in Device Manager to see if it made a difference. So far it seems to be behaving better. Now there's just a short delay waking up after idle. Keeping my fingers crossed this fixes it--but I have to ask, is there a way to make sure that the firmware upload does not impact Windows? If I change the settings to select a different firmware will that work?

Thanks for your work on this! Installed 2.5.2 and was able to get Bluetooth working on the Atheros 3012 combo card that came with my Dell XPS 8500! Saves me having to buy another adapter and use up a USB port! There was a slight delay after I rebooted before Bluetooth showed as available, but it did come up and I was able to pair a mouse.