Problems with Lion Bluetooth Connection

Try ENABLING the "Allow Devices to Wake This Computer" checkbox in the Advanced pane of the Bluetooth preferences and see if you still have the issue. if you DO still have it, open Activity Monitor, and see if "blued" is running.

I'm having similar issues. My keyboard will randomly disconnect and then connect. Neither the magic mouse nor the keyboard would wake the iMac from sleep. And now the mouse at times is VERY sluggish and the cursor "skips" across the screen. I've tried rebooting but that's it so far. Immediately after the upgrade everything was fine. It was only after going to sleep that this started. Unfortunately I just kicked off the upgrade on my wife's macbook before I noticed this. Hopefully her mouse isn't affected the same way.

Did just connect a wired mouse and all is well with it. Seems like Bluetooth is jacked.

I am having this same exact issue. And it's popping up all over the net. I have a 2009 iMac 3ghz core2duo.

Let me just say that Snow leopard ran PERFECT on this machine.

My iMac is set to sleep after 30 min of inactivity. Usually my Bluetooth devices will wake it from sleep. I have a magic mouse and a logitech dinovo edge mac edition Bluetooth keyboard.

I upgraded to lion on the day it came out. July 20th. The upgrade went smooth...no issues.

Since then, on 3 different occasions, I could not wake the iMac from sleep with the keyboard or mouse, I had to manually push the button. The keyboard and mouse was not responding at all so I had to plug a USB mouse/keyboard. I was able to get to Bluetooth settings and both devices were showing as connected. But they were not responding. I also noticed that I could not get on the Internet. (I am using a wired connection, wifi is off on the iMac). I could not see my networked IP printer or any other computers on my home network. I launched terminal and I am not able to ping anything. I am able to ping the loop back address. (127.0.0.1)

Finder was locking up also. Sometimes it opened, sometimes it didn't. Hoping they come out with an update.

I hear others are having the same issue while watching a flash video/youtube. I haven't been to youtube since the upgrade, but I'll check that out next to see if I can re-create the issue manually. Others also stated they had the issue when switching desktops with the keyboard shortcuts. ctrl-left arrow or ctrl-right arrow. But that works fine for me.

The fix....Reboot my iMac. All comes back and works fine. But I have no idea what is causing this or why. I have no weird scripts or startup programs running.

That's what I get for jumping the broome. 🙂 Like I said, Snow leopard ran GREAT.

Message was edited by: Rcarter236

If you open "Console" application, select kernel.log, and filter for the word "error" (no quotes), do you see any when this issue occurs?

There are now several different discussions on-going here on the boards about blue tooth problems and Lion, so it obviously is not due to one person's problem. I've tried all the mouse/keyboard fixes suggested including the "Allow devices..." suggestion. I was able to get them to work initially on my internal drive and then to an exact external (non-TM) clone.

I never powered off since a clean installlation last week, until today. Bam! No mouse and no keyboard. I rebooted, did all the "tricks", changed batteries, etc. with no success. I tried the pristine original backup, with the same negative results. One thing I've found is that a connected keyboard or mouse would always reconnect from sleep (when it was working), but it always loses the connection(s) on a reboot.

For now, I can "struggle" and get the mouse reconnected (3X), but no luck at all with the keyboard. I love Lion so far, but I think this is 10.0 related, particularly when you've tried all the fixes.

If you open "Console" application, select kernel.log, and filter for the word "error" (no quotes), do you see any when this issue occurs?

also, does it work if you shutdown then power on? there is a big difference between shutting down and restarting (one removes power to the BT device, ones does not).

(1) Yes, error messages are indicated. (See below):

Jul 25 19:46:36 localhost kernel[0]: [AppleBluetoothHIDKeyboard][handleStart] staticPrepControlChannelAction returned error e00002c0

Jul 25 19:47:42 Jays-MacBook-Pro kernel[0]: [AppleBluetoothHIDKeyboard][getExtendedReport] getReport returned error e00002d6

Jul 25 19:47:45 Jays-MacBook-Pro kernel[0]: [AppleBluetoothHIDKeyboard][getExtendedReport] getReport returned error e00002d6

Jul 25 19:48:53 Jays-MacBook-Pro kernel[0]: [AppleBluetoothHIDKeyboard][getExtendedReport] getReport returned error e00002d6

Jul 25 19:48:57 Jays-MacBook-Pro kernel[0]: [AppleBluetoothHIDKeyboard][getExtendedReport] getReport returned error e00002d6

This is only a partial listing, as I've tried to fix this for most of the last two hours. The common error as you can see is e00002d6 and that contines all the way through. Somewhat later the error stays the same but then it mentions sniffing/unsniffing (?) (see below):

Jul 25 21:10:32 Jays-MacBook-Pro kernel[0]: [SendHCIRequestFormatted] ### ERROR: [0x0804] (Exit Sniff Mode) -- Send request failed (err = 0x000C (kBluetoothHCIErrorCommandDisallowed))

Jul 25 21:10:32 Jays-MacBook-Pro kernel[0]: ### ERROR: Exit sniff failed (probably already unsniffed) (err=c)

Jul 25 21:10:42 Jays-MacBook-Pro kernel[0]: [SendHCIRequestFormatted] ### ERROR: [0x0804] (Exit Sniff Mode) -- Send request failed (err = 0x000C

I find the Console useful, but this is way beyond me.

(2) If I am connected, and reboot, the connection(s) are lost. I can, with difficulty, get the mouse re-connected, but the keyboard seems a lost cause for now. Sometimes I gert the numerical code to type in, but it isn't accepted, and other times it appears to be connected, but it is immediately dropped and the searching starts again.

As a follow-up tp (2), I tried twice more and both times got the keyboard code to enter to connect but even though all numbers were typed in, they were not accepted. I can't remember if the "enter" key shows being depressed, as I've never specifically looked for it, but it appears that the "enter" key box doesn't work. (I have a one-month old MBP, so it isn't my actual hardware return key on the key pad-I checked).

Those are keyboard driver errors; I hit this today as well. Powering off the keyboard ddi the trick for me, but it sounds like you did that.

Try this:

1) SHUTDOWN the computer

2) power off keyboard (hold power for 5 seconds)

3) power on computer

4) allow computer to come up and say there is no keyboard connected. at this point, power ON the keyboard but hold the power button for 10 SECONDS. this should put it into pairing mode. re-pair it when prompted, and yes hit the enter key.

once it is working, try rebooting and see if the connection persists at this point, or if the console errors show up again. And don't worry about those "Exit Sniff Mode" messages, they are harmless.

Power cycling the keyboard seems to have done the trick for me as well. Mouse also started to "magically" start working again for me.

Also reply to Redstang:

I did your suggestions and it worked! Also, Restang, I noticed that unlike last night, the mouse worked "magically" as well at startup even before the keyboard pairing, which seemed to instantly happen this time.

I paired both without any drama last week after a clean ground-up install, but the problems showed up out of the blue yesterday afternoon after a kernal panic. (I was away from home when that happened). I wrestled with this for three hours last night; I guess some time away from it for me and the MBP did some good.

I've been in the habit of only sleeping the MBP instead of powering off because for the moment I'm using the MBP with a Cinema Monitor and the laptop sits behind the monitor. I'll start powering off at night until there is a tweek in a point release or a specic fix is released. I'll remember these instructions too.

Thanks again for your help; btw, you really seem to know your stuff!

great, glad that worked for you guys. you should not have to shutdown your system. In this case it just seemed like the keyboard or the keyboard<->Mac bluetooth module got into a bad state. I suspect that won't happen to often. in fact, it would be interesting to see if you continue "life as usual" and see if it happens again...

Then I'll sleep it tonight and then I can tell for sure. If you don't hear from me on this again, putting the computer to sleep is OK again also.

Update, my iMac went to sleep today and I was able to wake it with my bluetooth mouse with no issues. Keyboard working fine etc... go figure. I will check console for errors and update when the issue re-occurs.