Contribute
Register

DW1830 Bluetooth not available (power saving issue?)

Status
Not open for further replies.
Thank you, I compiled and installed BrcmRAM2.kext
Will report back as soon as I see if it works or not. Just a question, after sleep I noticed that the name of BT card changes in ioreg. Is that normal?
Schermata 2018-02-27 alle 18.33.27.png
 
Last edited:
UPDATE: it doesn't work, but I have noticed something different now.
When I come back after sleep BT device shows up in ioreg and the icon in status bar is "on".
Schermata 2018-02-27 alle 18.38.59.png

Then as soon as I open up the AirPods case BT device disappears and icon in status bar become "not available"
Schermata 2018-02-27 alle 18.39.17.png

It may be something related to the fact that BT is identified as a different device after first sleep?

UPDATE: I can confirm that when is detected as BCM920703 it works correctly, when is detected as BCM2045A0 does not.

Schermata 2018-02-27 alle 22.09.31.png

So the question now is... why sometimes is detected the "wrong way"?
 
Last edited:
So the question now is... why sometimes is detected the "wrong way"?

No idea. Might be because firmware is already partially loaded/in process of being loaded.
 
No idea. Might be because firmware is already partially loaded/in process of being loaded.
Any way to force loading the card as BCM920703? Because it works with zero issues when is detected like that.
What can I try? 'caue i have zero ideas. Thank you

Small update: right after sleep BT card is detected as BCM2045A0 for some seconds, then it become BCM920703. If I try to pair something while still BCM2045A0 it disappears. Sometimes it also remains BCM2045A0 without becoming BCM920703
 
Last edited:
Any way to force loading the card as BCM920703? Because it works with zero issues when is detected like that.
What can I try? 'caue i have zero ideas. Thank you

Small update: right after sleep BT card is detected as BCM2045A0 for some seconds, then it become BCM920703. If I try to pair something while still BCM2045A0 it disappears. Sometimes it also remains BCM2045A0 without becoming BCM920703

You would need to look at the BrcmPatchRAM logs in order to determine the problem.
Also, you did not provide complete "problem reporting" files as per FAQ.
 
You would need to look at the BrcmPatchRAM logs in order to determine the problem.
Also, you did not provide complete "problem reporting" files as per FAQ.
Thank you. I will provide complete "problem reporting" files in a moment.
Meanwhile I looked into BrcmRAM source code (as I can't see any message in system.log from Brcm) and I found out that in the firmware folder of my BT card id (0a5c_6410) there are two firmware and not one. Also I found this discussion on an external site on Ubuntu. This is what the guy wrote: "I may be wrong, but BCM20703A1 and BCM2045A0 seem to be different partnumbers for the same device. Depending on the firmware that's loaded, the device is called "BCM920703" or "BCM2045A0".
Now, for some reason, if I don't use BrcmPatchRAM2 at all, device is loaded as BCM2045A0 anyway (and it doesn't work correctly), so I think that devices gets called BCM920703 only when BrcmPatchRAM correctly upload the firmware.
Again, can't see any log about the kext (maybe I have to enable debug mode somewhere?).

Meanwhile I'm going back to your fork, reboot, and provide you all the reporting files.
Thank you

EDIT: Problem Reporting Files Attached
 

Attachments

  • debug_2044.zip
    4.8 MB · Views: 93
Last edited:
Here is a second debug took some minutes after sleep (BT stop working after 3 minutes of idle)

Update: i noticed (and tested A LOT) that if the laptop is connected to AC Power when it comes out from sleep (or when it powers on), then the BT card works correctly and it's identified as "BCM920703".
If the laptop is on battery then the BT card is identified as "BCM2045A0" and doesn't work properly.
 

Attachments

  • debug_18768.zip
    4.8 MB · Views: 108
Last edited:
Here is a second debug took some minutes after sleep (BT stop working after 3 minutes of idle)

Update: i noticed (and tested A LOT) that if the laptop is connected to AC Power when it comes out from sleep (or when it powers on), then the BT card works correctly and it's identified as "BCM920703".
If the laptop is on battery then the BT card is identified as "BCM2045A0" and doesn't work properly.

You didn't implement USB power properties:
https://www.tonymacx86.com/threads/guide-usb-power-property-injection-for-sierra-and-later.222266/

Also, your USB port configuration looks wrong (you have 3x SSxx port marked UsbConnector=3, but only 2x HSxx ports marked UsbConnector=3).
https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/
 
You didn't implement USB power properties:
https://www.tonymacx86.com/threads/guide-usb-power-property-injection-for-sierra-and-later.222266/

Also, your USB port configuration looks wrong (you have 3x SSxx port marked UsbConnector=3, but only 2x HSxx ports marked UsbConnector=3).
https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/
Going to implement that right now.

Right, I have 2 USB 3.0 ports on this laptop. SS01 (and HS01) is the left one, SS02 (and HS02) is the right one. SS03 I don't know why is there. Gonna remove it now. Just a question Type C is not included in this ports right?
 
Fixed USB port configuration (should be good now).
I have also implemented USB Power Properties this way:
-Enabled ECDV to EC Clover hot patch (AppleBusPowerController showing in ioreg)
-Added SSDT-USBX in ACPI/patched but not sure it's loading. If I added the device directly in SSDT-XHC, then port configuration didn't work anymore, so I used an external aml.

Also, this broke sleep. Now sleep results in clean boot. If I remove SSDT-USBX.aml sleep works.
Also, same behavior with BT card after fixing SSDT-UIAC

Edit: I also tried to implement it using USBInjectAll injection (removing SSDT-USBX), but with no success (still 2 values in USBX). I attach the dsl file I tried to implement and io reg.
 

Attachments

  • debug_9861.zip
    4.8 MB · Views: 97
  • try_with_usbInjectAll_Injection.zip
    617.5 KB · Views: 68
Last edited:
Status
Not open for further replies.
Back
Top