Previous 1 2 3 4 5 Next 65 Replies Latest reply: Apr 24, 2012 11:42 AM by skogkatt79 Go to original post
  • Big Joon Level 1 Level 1 (25 points)

    Has anyone tried the 10.7.1 update?  I'm wondering if the new update has resolved this bluetooth connection issue...

  • Steve Friedberg Level 1 Level 1 (0 points)

    It's early, but 10.7.1 seems to have resolved all of my connectivity problems.  The mouse and Trackpad are both working smoothly, and I'm not seeing abrupt connetcivity drops.  I think it's interesting that they are apparently not acknowledging that this was a problem.

  • Big Joon Level 1 Level 1 (25 points)

    10.7.1 did not resolve my problem.  My magic mouse is still not connecting after waking up from sleep.  I still have to disconnect, then reconnect to use the mouse...  Dang...

  • Big Joon Level 1 Level 1 (25 points)

    Anyone has a fix yet???  My magic mouse is still not connecting after waking up from sleep.  It is still requiring me to disconnect, then reconnect again to use the mouse...  So much hassle every time it wakes up from sleep.

  • jpn621 Level 1 Level 1 (0 points)

    I'm at 10.7.1 with Logitech BT Laser Travel Mouse. Had the 10.7.1 update since its release but only had trouble with BT starting today. Suddenly my mouse frequently lost connection and won't reconnect.


    • Installing fresh mouse batteries does not help.
    • Turn BT off/on does not help.
    • Rebooting does not help.
    • Deleting the device from BT panel does not work.


    It's consistent: the BT Device Setup wizard detects my mouse and correctly identifies it, but will not pair.


    It does the same with my iPhone - the problem is not limited to BT mouse support.



    Late-2007 Macbook 3,1

    2.2 GHz Core 2 Duo

    Boot ROM: MB31.008E.B02

    4 GB 667MHz DDR2

    500 GB SATA drive

    Apple Bluetooth Software Version:  2.5.0f17

    BT Firmware Version:  1965

  • Steve Friedberg Level 1 Level 1 (0 points)

    I spoke too soon.  Same problems are once again occuring; connections between the mouse or trackpad and the computer come and go...the keyboard unilaterally starts typing multiples of the same letter for no reason, and more.  This is clearly a BT problem, and I hope Apple is taking note.

  • robs89 Level 1 Level 1 (10 points)

    I have the same problem. Magic Mouse and Bluetooth keyboard are not working after waking up my Macbook Pro.

  • Steve Friedberg Level 1 Level 1 (0 points)

    And it's gotten to the point where I simply have ditched the Magic Trackpad/Mouse and BT Wireless Keyboard.  I went out and bought a Logitech K350 Solar Keyboard and a Logitech Anywhere MX mouse.  Yes, they're 2.4GHz and I need to use a USB port for the receiver.  Guess what:  they simply work, and I no longer find myself wondering how/when my BT peripherals will abruptly quit working.


    Thanks for listening, Apple. I guess you're too busy with iPads to listen to what's not working with iMacs.

  • David Mundy Level 1 Level 1 (5 points)

    My iMac will sleep and wake any number of times and recognise my blutooth mouse, keyboard and trackpad....however, at what seems random intervals the iMac will not respond to the blutooth peripherals to wake from sleep.  Using a spare wired keyboard and mouse I am able to wake the computer from sleep however when I try turning blutooth off and then on from preferences I get the spinning beachball......activity monitor does not show any stalled processes......killing the blutooth process and restarting it does not solve the problem.....only a full reboot of the iMac will bring back blutooth functionality....


    Looking at the kernel.log file there are multiple errors regarding many discussion threads mention this problem.....I am hopeful that Apple will address the issue in upcoming updates....??

  • myaffee Level 1 Level 1 (0 points)

    I'm having the same problem many of you are experiencing. I have Lion running on a 2011 MBP and every time I wake it from sleep, it won't recognize either my bluetooth mouse or keyboard. My morning ritual has become to turn off bluetooth from the menu widget and then turn it back on which restores bluetooth connectivity for the remainder of my session. I'm not getting any drops once it's connected, only after waking from sleep.


    I turned off "wake on sleep" because my cats inevitably step on my keyboard or mouse and wake my computer while I’m away so keeping this setting on is not a viable option, even if it solved the problem, which it doesn't sound like it does. Also, I haven't checked to see if blued is running but I don't see how that matters. It might be an explanation but it's not a fix unless someone knows how to launch the process automatically on waking from sleep?

  • MMaaMM Level 1 Level 1 (0 points)

    Same problem on my imac 27 2009 after upgrading to Lion.

  • gtmagnet Level 1 Level 1 (20 points)

    checking to see if blued is running is confirmation that it is the same problem other people are seeing and not something new. It is not intended as a fix, just debug info.


    sounds like you are seeing the same thing as many others are. doesn't your computer go back to sleep eventually, even if the cats step on the keyboard? or do they sleep on the keyboard? :-) And yes, setting this checkbox fixes the problem for a lot of people. maybe you should try it once?

  • frochild Level 1 Level 1 (0 points)

    Please GOD someone fix this problem!!!!!!!!!!!!!!!!

  • gtmagnet Level 1 Level 1 (20 points)

    will 10.7.2 deliver us?

  • J. Exby Level 1 Level 1 (0 points)

    OS X 10.7.2 has done NOTHING to resolve the conflict between the bluetooth kext driver and the kext WiFi driver.

    it's clear on my MacBook Air 11" 2011 that when I am connected to 802.11g wifi with bluetooth Off.

    open Terminal--- run a constant ping to the IP address of my name server.  steady results in the 2-3ms range.

    turn on Bluetooth

    watch as packet times drastically increase to the 180-260ms range and even DROP packets

      if the WiFi is ever turned off and back on, the WiFi connection will not even re-connect.

        (various messages seen in Console)


    anyway, the only relevant fix appears to be downgrading the kext WiFi driver itself as documented here:




    I am unsure if the driver alone is to blame or if actual radio signal interference is possible between the chipsets.