- Joined
- Oct 19, 2013
- Messages
- 103
- Motherboard
- NUC Kit NUC8i7BEH
- CPU
- i7-8559U
- Graphics
- Iris Plus 655
You have a weird post, couldn't tell who it was from. Meanwhile I think you are confused or I confused you. You have two separate issues you are posting about and one has your name it, one doesn't. The audio issue is not causing your sleep/ wake issue, you just don't have clear sound. In terms of Audio IDs 0x1c000000 = 28, you have to work backwards to try the other IDs and convert the numerical value to hex. I think you understood that but I was questioning if you were doing it correctly. 28 has worked better according to the most recent user postings but I've also used 3 successfully forever.
As to your second issue correct USB port limit configuration, Bluetooth and Sleep/Wake behavior absolutely and irrevocably intertwined. Its well documented through out this forum (and others). Improper port limit patching = a device that wakes immediately, won't wake at all or wakes to a black screen (and other issues). Flakey bluetooth behavior is also typically related to improper port patching because it relys, at least partially, on correct USB functioning.
Sleep wake issues are very, very, very common and one of the most reported issue here in this thread and generaly solved by using USBInjectall.kext with a custom UIAC-SSDT you create yourself for the ports you need. The other way is to replace USBInjectall.kext with a custom USBPorts kext but both do the same thing.
If you haven't noticed a difference with sleep configuring ports vs. USB inject all its either because something else is causing interference, like a DAC or other input devices, or more likely you still need to correct your port limit patching situation.
Have you tried following this guide? If you haven't you are spinning your wheels....mine too.
The New Beginner's Guide to USB Port Configuration
Important Update: June 2023 From Big Sur 11.3 on the built-in OpenCore XhciPortLimit quirk no-longer worked as described. This became a known "bug", though in reality it was Apple changing their internal code, making a simple "peek and poke" to keep it operating, a difficult task. However, with...www.tonymacx86.com
I believe you may have replied to me instead of another user asking about his audio issue, he posted right after me.
I do NOT post as a different user.
Either way, I have followed the above guide, but as you pointed out, maybe it's not USB port configuration, but a DAC, in fact I do use a USB DAC, you were spot on on that one.
Wether this is the cause or not it is yet to be seen. So many variables.
Always thankful for your input.