Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About muttonhead411

  • Rank
    Advanced Member

The recent visitors block is disabled and is not being shown to other users.

  1. Since we have it a bit of roadblock with bluetooth, I decided to go out and buy a bluetooth dongle to test out. I bought the following CSR Bluetooth USB dongle: Steps that I followed: - removed all traces of Rehabman's kext so that bluetooth is not showing in System Information - plugged in bluetooth dongle What happens next is surprising: - Bluetooth dongle lights up, it is working - Bluetooth shows up on menubar, bluetooth is functioning But... when it try to connect to my bluetooth mouse, it does NOT work. It exhibits the same behaviour as DW1820a! Device discovery is fine, but it cannot connect to any device. I'm beginning to think it is not a hardware issue (since both dongle and dw1820a both don't work), but the way we are configuring bluetooth on our machines Paging for @Hervé @Jake Lo. Any thoughts on what could be happening?
  2. When your firmware shows correctly, it means firmware is loaded successfully. You will be able to detect devices, but can’t connect to any at all... is that correct?
  3. @Hervé - I tried your kext as well... same behaviour as before. If sysinfo is showing v7 c5799, it probably means firmware isnt being loaded. When this happens, you will be able to connect to devices, but they will randomly disconnect, and have "choppy" behaviour. I'm surprised all is good on your end... -jealous-
  4. Hi everyone, Through testing, I've managed to confirm the following, FYI @Hervé maybe it will be of use. When using Rehabman kext to inject firmware (BrcmPatchRam2& BrcmFirmwareRepo/Data), bluetooth is: - Able to be enabled - Able to detect bluetooth devices - NOT able to sustain connection to bluetooth devices When using Rehabman kext to ONLY inject bluetooth (using BrcmBluetoothInjector.kext, or when firmware fails to load), bluetooth is: - Able to be enabled - Able to detect bluetooth devices - Able to connect to bluetooth devices, but not stable/jumpy connection, and will disconnect/crash bluetooth after a while It is weird, but without firmware upload, the card is able to do more with bluetooth, than without firmware upload. However, the card is still not usable with this setup. Note also that this behaviour is only happening to 1028:0021cards. for 1028:0023, there are no bluetooth issues, but wifi is garbage on this model
  5. I've been doing further testing on bluetooth and wifi for DW1820a. Here are my observations so far: - Bluetooth connection stutters. When using bluetooth mouse, the cursor jumps on the screen. When using AirPods, the audio skips. - When left idle, bluetooth devices will disconnect on their own - Bluetooth is more stable when wifi is running on 2.4ghz, or turned off Initial suspect is related to power management to the card, or some form of interference. On windows the card works perfectly, which means it is not an antenna problem. @Hervé do you observe the same as well?
  6. @Hervé You are absolutely amazing. Thanks to you and the community, we now have a fully working DW1820a, both wifi and BT together! you solved this issue in a matter of hours, which I couldn't even do over several weekends! Look at this... 2 devices at once!! My work on Dell 7490 is almost perfect... what a beauty it is. Thanks again!!
  7. @Hervé I've tried my best to read up on this, and figure out how to fix my bluetooth issues, but I can't seem to succeed. Would like to get your guidance Symptom: Bluetooth is recognised, and is able to discover devices, but is unable to connect to any device successfully (mouse, AirPods, non of them work) Since its likely a USB discovery issues, I've attached the following materials, maybe you can point me in the right direction for this... I am using a very similar setup as your 7490 on 10.14.5 (except I'm on i5, without thunderbolt) ioreg profile posted as well. Thank you!
  8. Unfortunate to be the bearer of bad new, but your card has low success of being used for hackintosh. Suggest to get one with 1028, 0021 card instead
  9. @Hervé - some updates, the new DW1820A card from ebay finally arrived, installed, and working as it should. No hangs, no kernel panics. Things are looking good. However, there are 2 things I noticed: - Bluetooth isnt working well. When setting properties through clover: 14e4:4331 does not detect bluetooth at all, but 14e4:4353 detects bluetooth correctly - However, with 4353 detecting bluetooth, in actual fact nothing can connect to it. It discovers available bluetooth devices correctly, but will not successfully connect to them (i tried both airpods and bluetooth mouse, both didnt pair successfully). Thanks.
  10. Hi @micheajp - Wanted to update you that I managed to fix the pink/magenta tint issue in 2 ways: - use patch-edid.rb patch to create custom profile override to force RGB output when OSX thinks you're connected to a TV. I followed this video for instructions - or, use a USB-C to HDMI output and route display using USB-C port - no patching required for this. This has the added benefit of properly routing audio out to your monitor if it has built in speakers, or a TV I still have buzzing sound when headphones are connected with a jack. I'll have to figure this part out separately.
  11. Hi, would you mind posting your kexts? I've tried your setup but it freezes after ~30mins into connecting wifi...
  12. Hi everyone, Wanted to give an update here, that I managed to fix my update issues by moving kext from Clover to /L/E. Not sure why that made a difference when in 10.14.4 it didnt, but now touchpad and audio out works. Maybe it has something to do with SEP... not sure @Hervé audio out still has high pitch buzzing sound... are you facing similar issue on your 7490?
  13. Nope I didn't change anything else other than the 3 steps above. Just as per @Hervé guide before.
  14. Actually, it's now behaving like the USB installer, where trackpad doesnt work, but external mouse works (recall we discussed this behavior). I did face some update installation issues (didnt complete successfully acoording to the error page), but a few reboots later it updated successfully. If i did indeed botch the update, how should I best retry the update? Should I: 1) download the delta update package and retry 2) download the combo update package and retry 3) time machine my data and start fresh? @Hervé is your audio out working properly?
  15. @wtv1234 in case you did anything differently, i did 2 specific steps only (via injection): 1) place AirportBrcmFixup to Clover/Kext/Others 2) add boot option brcmfx-driver=1 via clover configurator 3) Reboot If i did anything beyond this, the system would not boot... Hope this helps.
  • Create New...