Contribute
Register

DW1830 Bluetooth not available (power saving issue?)

RehabMan

Moderator
Joined
May 3, 2012
Messages
188,974
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
MacBook Air
Mobile Phone
iOS
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.
Why is HS04 active, marked as connected to internal device (UsbConnector=255), but nothing connected?
 
Joined
Mar 9, 2013
Messages
122
Motherboard
Dell XPS 13 9360
CPU
Intel i7-8550U
Graphics
Intel HD620
Why is HS04 active, marked as connected to internal device (UsbConnector=255), but nothing connected?
It's the internal Touchscreen. Now is deactivated in BIOS. Should I remove it?
 
Joined
Mar 9, 2013
Messages
122
Motherboard
Dell XPS 13 9360
CPU
Intel i7-8550U
Graphics
Intel HD620

Attachments

RehabMan

Moderator
Joined
May 3, 2012
Messages
188,974
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
MacBook Air
Mobile Phone
iOS
Done, thank you.
Still USBX device is not loading properties I think (I Have it implemented into my SSDT-UIAC.aml).
USBX is in your DSDT.aml.
Strange place to put it...
 
Joined
Mar 9, 2013
Messages
122
Motherboard
Dell XPS 13 9360
CPU
Intel i7-8550U
Graphics
Intel HD620
USBX is in your DSDT.aml.
Strange place to put it...
Thank you for pointing me that out, don't really know why it was there. I removed it, and now USB X Properties are loading correctly.
BT issue is still present tho :cry::banghead:
 

Attachments

RehabMan

Moderator
Joined
May 3, 2012
Messages
188,974
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
MacBook Air
Mobile Phone
iOS
Thank you for pointing me that out, don't really know why it was there. I removed it, and now USB X Properties are loading correctly.
BT issue is still present tho :cry::banghead:
The ioreg you attached "ioreg-rightaftersleep.ioreg", shows BT working.
 
Joined
Mar 9, 2013
Messages
122
Motherboard
Dell XPS 13 9360
CPU
Intel i7-8550U
Graphics
Intel HD620
The ioreg you attached "ioreg-rightaftersleep.ioreg", shows BT working.
Yes, but you can see is discovered as "BCM2045A0" (it was "BCM920703" before sleep). This happens only when I wake up when on battery (with AC it is discovered as "BCM920703").
From the second ioreg "ioreg-afterBTconnect" you can see that BT disappear. This happens as soon as I open my AirPods case. Or, if I don't connect anything it disappears after 2-3 mins (but only when discovered as BCM2045A0!).

Again, if I wake up on AC (and BT is discovered as "BCM920703") everything works fine

Thank you for all your time!
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
188,974
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
MacBook Air
Mobile Phone
iOS
Yes, but you can see is discovered as "BCM2045A0" (it was "BCM920703" before sleep). This happens only when I wake up when on battery (with AC it is discovered as "BCM920703").
From the second ioreg "ioreg-afterBTconnect" you can see that BT disappear. This happens as soon as I open my AirPods case. Or, if I don't connect anything it disappears after 2-3 mins (but only when discovered as BCM2045A0!).

Again, if I wake up on AC (and BT is discovered as "BCM920703") everything works fine

Thank you for all your time!
ACPI/origin files are too old. You forgot to press F4. Please read "Problem Reporting" again. Carefully.
 
Joined
Mar 9, 2013
Messages
122
Motherboard
Dell XPS 13 9360
CPU
Intel i7-8550U
Graphics
Intel HD620
ACPI/origin files are too old. You forgot to press F4. Please read "Problem Reporting" again. Carefully.
Here you have!

It may be something related to BrcmPathRAM2?
I quote what I wrote some posts before this:
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".
... I think that devices gets called BCM920703 only when BrcmPatchRAM correctly upload the firmware. (ADD: how could this be related to the fact that doesn't work only when on battery?)
Again, can't see any log about the kext (maybe I have to enable debug mode somewhere?).
Thank you again
 

Attachments

Top