Recent content by kusakata

Idk about that... ARM processors have no balls, compared to Intels' newer gen i5/i7 Didn't Apple move away from PPC mostly because of lacking performance? Seems like an idiotic move to go down the same road Hell, if anything, they should port macOS to iPad, rather than shift to ARM. I have much...

God damn what a monstrosity of an update :eek: Sticking with El Cap for the next 6 months minimum, doesn't seem like Sierra will reach "daily driver" usable status, not anytime soon at least.

Well, I guess I just haven't ran into any scenario where BT didn't work as expected. Airdrop and regular file transfer to/from other devices is solid. Along with BT headset working very reliably, any possible trade off is worth it at this point for me. I keep reading the hotspot function...

Alright just for completeness sake, and to officially mark this solved, thought I'd wait a bit before reporting back. So, for the last 10 days since I've replaced BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext with BrcmBluetoothInjector.kext, I haven't had even one issue with BT; comes back after...

Airdrop is working also, can send & receive files without any issue As for Handoff and Instant Hotspot, I don't have any iPhones or iPads to test on; I'm very happy Airdrop is working :headbang:

BT is definitely working, I have my BT headphones paired and working flawlessly. Also tested pairing it with my phone and sending/receiving files from laptop; works without any fuss

Ahh okay, so pretty much I just won't get the bells and whistles (A2DP, aptX, etc.)? I guess I could live with that....at this point I just want BT reliability. I miss Yosemite...:cry:

I'm not sure why, but it seems to be working. I removed both BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext, installed the BrcmBluetoothInjector.kext, rebuilt caches and rebooted. Made sure that the old kexts were not being loaded by checking kextstat. I've put the laptop to sleep and woken it up...

The frequency of this happening has gone down, stays OK for about 3 days and then it craps itself. I wanted to be sure before giving IORegistry logs. I'm looking around on the bitbucket page and I see other options, I wanted to try the BrcmBluetoothInjector.kext but can't find links to it...

Seems like bluetooth is still dying upon wake, even without AFT Man, Yosemite really was a better operating system in every way I can think of... el cap has been nothing but troublesome and sacrifices :\ BrcmPatchRAM2: [0a5c:21e1]: device request failed ("0xe0005000 (UNDEFINED)" 0xe0005000)...

Thanks again for the input! I had noticed earlier that by feeding it the darkwake=11 flag, I wasn't seeing anything at all in the system log/dmesg/ about wakeups. Time machine was also not completing. Removed the flag and restarted, hopefully no extra configuration necessary

Thanks a lot, seems to be working fine after wake up now (4 wakes in so far, all good); now to figure out the default/best value for darkwake, starting with 11 (seems to be default) and going from there. Glad I took the plunge(usually never touch working systems), a little bit readier to...

That's so weird, I've always used Android File Transfer, as long as it's been out. I use OSX everyday. I will try without it, never would have seen the link between the two, thanks for suggestion

Here's the support zip I was going to upload yesterday. I added an IOREG dump of before and after sleeping. If there's anything else I can add to help let me know. I had trouble with Bluetooth with PBI also, to get around the issue I remember experimenting with kexts I used in Yosemite, none of...

That's weird, the only way I know of to reliably boot without caches is pressing SPACE in clover (don't trust -f or UseKernelCache flags); I'm just glad the sound issue worked out... however it's murphy's law at work... I'm being punished for fixing a working system :lol: The bluetooth appears...