4 ms·
How about the bug where you need to force quit coreaudiod to restore sound to the speakers after resuming from sleep?
by imron 10y ago
How about the bug where you need to force quit coreaudiod to restore sound to the speakers after resuming from sleep?
- lostlogin 10y agoHow about the computer randomly going back to sleep 2 min after opening. Happens on 3x MacBooks. Force restart.
- qubex 10y agoMe too!
- stephenr 10y agoFunny I have the opposite. I often need to induce a sleep/wake cycle to restore detection of external speakers. Killing coreaudiod does not fix it, but a restart or (I recently learned) sleep/wake does.
- imron 10y agoPlugging headphones in and taking them out again also seems to fix it sometimes, but I don't always have a pair of headphones by my desk.
- stephenr 10y agoYeah so my issue is pretty much opposite of yours it seems. If I have headphones/speakers plugged in, and unplug them (usually to swap from headphones to speakers, or vice-versa), often after I unplug, it won't recognise that I plug something back in. I used to think this happened when some perhaps-not-so-diligent audio using apps were open (I'm looking at you Skype) but it seems to happen more and more. Then again I'm already on my 3rd logic board for this MBP (both times replaced because of dedicated GPU failure), which is the 2nd MBP I've had that's had that same problem fixed twice.
- imron 10y agoSkype and Mail are the two ones I notice.