Contribute
Register

DW1830 Bluetooth not available (power saving issue?)

Status
Not open for further replies.
ZombieBest said:
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.
Click to expand...

Why is HS04 active, marked as connected to internal device (UsbConnector=255), but nothing connected?
 
RehabMan said:
Why is HS04 active, marked as connected to internal device (UsbConnector=255), but nothing connected?
Click to expand...
It's the internal Touchscreen. Now is deactivated in BIOS. Should I remove it?
 

Attachments

  • debug_2601.zip
    4.8 MB · Views: 63
ZombieBest said:
Done, thank you.
Still USBX device is not loading properties I think (I Have it implemented into my SSDT-UIAC.aml).
Click to expand...

USBX is in your DSDT.aml.
Strange place to put it...
 
RehabMan said:
USBX is in your DSDT.aml.
Strange place to put it...
Click to expand...
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

  • debug_7017.zip
    5.5 MB · Views: 77
ZombieBest said:
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:
Click to expand...

The ioreg you attached "ioreg-rightaftersleep.ioreg", shows BT working.
 
RehabMan said:
The ioreg you attached "ioreg-rightaftersleep.ioreg", shows BT working.
Click to expand...
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!
 
ZombieBest said:
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!
Click to expand...

ACPI/origin files are too old. You forgot to press F4. Please read "Problem Reporting" again. Carefully.
 
RehabMan said:
ACPI/origin files are too old. You forgot to press F4. Please read "Problem Reporting" again. Carefully.
Click to expand...
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?).
Click to expand...

Thank you again
 

Attachments

  • debug_11215.zip
    1.3 MB · Views: 90
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top