Paul2perth

Q: iMac wireless mouse/keyboard unavailable after awakening from sleep - OS X 10.10.3

I am using an iMac21 inch late 2012. Has been working perfectly until I upgraded to OS X 10.10.3. Now when the iMac wakes from sleep neither the mouse or keyboard are connected. The only recourse is to force a hard restart with the power button.

 

i have tried the following to no avail:

 

  • SMC reset
  • PRAM/NVRAM reset
  • reboot (reconnects until computer sleeps & reawakens)
  • bluetooth off/on
  • repaired Bluetooth devices
  • Removed & reconfigured devices

 

I have set sleep (in Energy Preferences) to wait indefinitely & that has 'resolved' my issue. Albeit with an increase in energy use. Of course this isn't a fix.

 

I Would be grateful if anybody had some tips on how to resolve this situation.

 

thanks

paul

iMac, OS X Yosemite (10.10.3)

Posted on Apr 12, 2015 7:06 AM

Close

Q: iMac wireless mouse/keyboard unavailable after awakening from sleep - OS X 10.10.3

  • All replies
  • Helpful answers

  • by PrimeNumber,

    PrimeNumber PrimeNumber Apr 12, 2015 9:54 AM in response to Paul2perth
    Level 1 (0 points)
    Apr 12, 2015 9:54 AM in response to Paul2perth

    I have the exact same issue and have tried all of the same "fixes".

     

    If I connect a USB mouse, the machine will wake from sleep (after a significant delay), but Bluetooth is broken. It recognizes neither the wireless keyboard or Trackpad. If I try to turn Bluetooth on/off after I wake it this way, the Bluetooth settings become non-responsive (I am unable to turn it off or do anything else). I have to reboot in order to restore normal functionality.

     

    I am hoping someone has a fix for this.

  • by PrimeNumber,

    PrimeNumber PrimeNumber Apr 12, 2015 10:11 AM in response to Paul2perth
    Level 1 (0 points)
    Apr 12, 2015 10:11 AM in response to Paul2perth

    By the way, are you seeing something like this in your system logs?

     

    Apr 12 12:07:13 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 1 ****

    Apr 12 12:07:23 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 2 ****

    Apr 12 12:07:33 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 3 ****

    Apr 12 12:07:43 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 4 ****

    Apr 12 12:07:53 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 5 ****

    Apr 12 12:08:03 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 6 ****

    Apr 12 12:08:13 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 7 ****

    Apr 12 12:08:23 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 8 ****

    Apr 12 12:08:33 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 9 ****

    Apr 12 12:08:43 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 10 ****

    Apr 12 12:08:53 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 11 ****

    Apr 12 12:09:03 iMac kernel[0]: **** [IOBluetoothHCIController][TransferACLPacketToHW] -- commandSleep(&mSystemOnTheWayWakingUp) failed -- counter = 12 ****

  • by LivingAimlessly,

    LivingAimlessly LivingAimlessly Jun 7, 2015 1:21 PM in response to PrimeNumber
    Level 1 (14 points)
    iPhone
    Jun 7, 2015 1:21 PM in response to PrimeNumber

    Yes I'm getting this and have this exact problem you're experiencing. Ever since 10.10.3 (not in 10.10.2). Wired keyboards and mice are fine. Support wants me to reinstall as their solution but I'm a little reluctant. And rather annoyed that it doesn't seem theres any acknowledgement that other people have having this problem and it's a bug.

     

    Really very frustrating.

     

    Have you guys found a solution?

  • by LivingAimlessly,

    LivingAimlessly LivingAimlessly Jun 8, 2015 10:46 PM in response to Paul2perth
    Level 1 (14 points)
    iPhone
    Jun 8, 2015 10:46 PM in response to Paul2perth

    bump

  • by Paul2perth,

    Paul2perth Paul2perth Oct 18, 2015 4:19 AM in response to Paul2perth
    Level 1 (0 points)
    Oct 18, 2015 4:19 AM in response to Paul2perth

    Can anyone share their experiences on this issue affecting bluetooth mouse and keyboard after sleep now that OS X 10.11 El Capitan is out. Is it now fixed?

     

    Thanks

    Paul

  • by LivingAimlessly,

    LivingAimlessly LivingAimlessly Oct 27, 2015 2:26 PM in response to Paul2perth
    Level 1 (14 points)
    iPhone
    Oct 27, 2015 2:26 PM in response to Paul2perth

    Hey Paul. So far El Cap has been working for me and my stock bluetooth apple mouse and keyboard are reliably waking my iMac as well as bluetooth remaining functional after wake.

     

    That being said, my computer had been working great with Yosemite 10.10.1 and 10.10.2 as well, then suddenly developed the problem immediately after 10.10.3.

     

    So I guess I'm saying, I'm worried a future El Cap update will break it again considering Apple never seemed to address the problem was happening or fix the issue in Yosemite for those few of us experiencing it. And moreover, looking through the forums, it appears this issue was a problem in past generations of OS's too... I'll keep my fingers crossed but I'm not going to be so silly as to hold my breath (and certainly didn't throw away my wired keyboard and mouse which was the only good workaround I found...).