Cannot detect Mighty mouse after waken from Sleep

If i wake my book from sleep, the bluetooth app will not be able to detect the might mouse. And I also cannot switch off the blue tooth app at that time. I was trying to restart the bluetooth assistant but it fails.
Any of you has such problem ?

all I can say is, you are not alone. I've got the same problem just as many other with my BT Mighty Mouse and BT Keyboard.

Similar Messages

Jumpy mouse after waking from sleep?

Ever since I installed Leopard (clean install, not an upgrade) I've been experiencing this problem. Everything has been running flawless but after about 6+ days uptime, the mouse will start lagging/jumping like crazy after waking it from sleep.
For example, I closed my Macbook Pro screen about an hour ago to head to my parents house and put it in my bag. I get here and open up the screen to wake it up and the mouse is just jumping around like crazy. I waited a few minutes thinking maybe something was loading in the background sucking up all the CPU cycles/resources, but that's not the case. This is about the third time I've seen this problem and it always occurs after waking the computer from sleep with a 5-6+ day uptime.
Anyone else experience this issue? This was never a problem in Tiger and I had 30+ day uptimes there.

I'm taking the same cruise to frustration island. My trackpad just started getting really jumpy in the last couple of days. This is after a very irritating bout with random keyboard freezes (which I still have not resolved, but feel better that I'm again on a boat with plenty of others: http://discussions.apple.com/thread.jspa?threadID=1206602&tstart=0).
I've tried to figure out if there's a process that's hogging things, but that does not appear to be the case.
I guess I'll just have to wait for another OSX update or something to get this issue resolved.

Turning off Mighty Mouse wakes computer from sleep

Two part issue:
After sleeping the computer I find that the "power down" on the Mighty Mouse causes the computer to awake!! Does anyone have a solution to this Mouse-killing problem?
I find no instruction about shutting the Mighty Mouse (MM) off when it is not in use (say for overnight). I do see references to relatively short battery life so I imagine that we should power-down the MM when possible. But, the MM appears to be engineered pretty cheaply and it appears that it may not survive many cycles of power up-down. Anyone with thoughts on this?

Bluetooth or USB devices won't wake up a portable running off of battery power. That probably doesn't help you, but I thought I'd note that. I don't think moving the switch actually triggers the wakeup. Of course you can't do that without holding it by the shell, which almost always senses a button press because of the design of the entire shell as right or left buttons.
If you leave your mouse powered-on for a while, it should eventually go into standby mode with reduced power consumption. I use rechargeable batteries, so I don't worry too much about battery life. The batteries lasts several weeks before I need to recharge them and I can keep a charged set handy.
So I take it you're using the mouse to select going to sleep in the pull-down menu and then try turning off the mouse. At least with a portable I can turn the mouse off first then either use the trackpad to put it to sleep or just close the lid.

Odd Keyboard/mouse failure after waking from sleep

Here's an odd problem that's been bugging me for awhile now.
Occasionally my iMac will not allow me to log in after waking from sleep. I always log out of the machine when I'm not using it, and after a bit it goes to sleep (usually I'll just click the "sleep" button on the login display).
It wakes up with a wiggle of the mouse (Wacom Graphire), a tap of the keyboard (recent wired but numeric-keypadless Apple) or if I hit the button on my Griffin Power Mate.
But then I cannot do anything. If I click any of the edit boxes in the login window, or any of the buttons, the mouse jumps to the "sleep" button but does not click it. I can't enter a username or password because those edit boxes never get focus.
The machine is otherwise alive, as I can ssh to it from another computer or my iPhone and then from the command-line do a
$ sudo /sbin/shutdown -r now
for an orderly reboot.
Very bizarre and rather annoying ... this has persisted since I installed Snow Leopard. Clues, anyone?

Some, but not all of the time that the tower goes to sleep, when it wakes up the mouse works, but the keyboard does not. A restart solves the problem, but that's not practical.
My aluminum keyboard did exactly the same thing when used with the USB extension cable, but not when plugged directly to the computer. Usually, unplugging the keyboard for a few seconds would fix it. The Apple store replaced the keyboard, and I have had no problems with the new keyboard.

Mouse skipping wildly after waking from sleep

Not sure if I've fixed this already yet or not but, sometimes after waking from sleep my wireless mighty mouse has a bad delay (skips around a bit too). I'm using Steer Mouse (which seemed to preform normally) but have uninstalled it just to see if it was the problem. So far, so good: no mouse problem after sleep, though I've only tried it a few times.
Anyone having this problem who doesn't have Steer Mouse installed?

same prob but with the trackpad. I don't think it is a prob with your particular mouse. There is a few other topics covering this.
Common theme... only a reboot will fix.

Update to 10.6.8 - system hang (mouse issue) after resume from sleep

I am on older
MacBook Pro3.1
Intel Core 2 Duo
2.6GHz
Run on 10.6.8 almost flawelessly. Shortly after upgrade to 10.6.8 system started to hang periodically after resuming from sleep. Symptoms are that it stops responding to mouse (be it touch pad or USB mouse). Keyboard seems to be ok but system doesn't seem to be fully functional. I am able to ssh from the other computer and 'shutdown -r now' after reboot system seem to be ok until next resume from sleep. What interesting though is that this problem newer manifests then I am using external monitor.

Found problem. It was due to magic mouse that I left on. I carry this mouse in the laptop bag but rarely use it. Last time I used it (around the same time I install the update) I left it on in the bag. It was apparently disconnecting/connecting on its own and by some reason sometimes was breaking touch pad and other usb mouse connected to laptop, as soon as I switched magic mouse off broblem was fixed

Cannot login after awaking from sleep (login screensaver sleep problem)

After awaking from sleep or returning from the screensaver, the "loginwindow" of system.login.screensaver (visible after checking "details") does not recoginze the correct password. It is not possible to login this way anymore.
Very annoying!
Fortunately, I found a workaround using the functionality to switch users. The standard OS X welcome screen recognizes my password.
Anyone experiencing the same or with a way to correct the initial problem?
PS: the user account in question is a "network user"; it works as expected for a local user

More info:
It seems to be the screen going to sleep, not the computer. When I come back and touch the mouse or the keyboard, as the screen lights up, there is a flash of the web pages I left up, then they vanish.
Yikes!!!

After waking from sleep, my iMac (Lion) is unresponsive. The mouse moves, but when I click things it won't open them.

After waking from sleep, my iMac (Lion) is unresponsive. The mouse moves, but when I click things it won't open them.
This has happened EVERY time the iMac goes to sleep for the last few days.. the only way I have found to resolve the issue is to manually restart the computer each time via the button on the back of the iMac.
Any and all help is appreciated!
Thanks

FWIW, I never sleep my machines or their HDs, just their displays and never have an issue waking up the displays, usually run 24/7. Give that a shot.

Unable to get keyboard or mouse focus back after waking from sleep

Here's a problem with very specific symptoms, which I've seen on a number of Macs that I support:
- After waking from sleep, the Macs are unable to fully achieve focus on any window. All windows, in all apps, appear to be in the background -- their frames have the lighter gray look of backgrounded windows.
- I can grab any window and move it around, and even interact with elements of the window by clicking on them. I cannot, however, ever really bring the window to the front.
- I can't type anywhere.
- Regardless of what window I click on, the OS menu bar remains "stuck" on whatever app was in the foreground when the Mac went to sleep. Sadly, though, none of the menus can be selected or pulled down.
The only way out of this state is to force a restart.
I am wondering if anyone else has seen this behavior, or, better yet, has actually solved it.
Thanks in advance!

Check the Display & Enhance Contrast settings - System Preferences/Universal Access
Or repair permissions and restart your computer.
Or *Disconnect all peripherals from your computer.* Boot from your install disc & run _*Repair Disk*_ from the utility menu. To use the Install Mac OS X disc, insert the disc, and restart your computer while holding down the C key as it starts up.
Select your language.
Once on the desktop, select Utility in the menu bar.
Select *Disk Utility.*
Select the disk or volume in the list of disks and volumes, and then click *First Aid.*
Click _*Repair Disk.*_
Restart your computer when done.
Repair permissions after you reach the desktop-http://docs.info.apple.com/article.html?artnum=25751 and restart your computer.

Why am i getting mouse lag after wake from sleep?

both cordless mmouse and corded wacom tablet are displaying lag after waking from sleep. restart usually, but not always, helps. usb devices are on a powered external hub. noticing this after upgrading from nvidia geforce 8800 to ati 5770. compatibility issue?
specs are:
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro3,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2.8 GHz
Number Of Processors:          2
Total Number Of Cores:          8
L2 Cache (per processor):          12 MB
Memory:          8 GB
Bus Speed:          1.6 GHz
Boot ROM Version:          MP31.006C.B05
SMC Version (system):          1.25f4
ATI Radeon HD 5770:
Name:          ATY,Hoolock
Type:          Display Controller
Driver Installed:          Yes
MSI:          Yes
Bus:          PCI
Slot:          Slot-1
Vendor ID:          0x1002
Device ID:          0x68b8
Subsystem Vendor ID:          0x106b
Subsystem ID:          0x00cf
Revision ID:          0x0000
Link Width:          x16
Link Speed:          5.0 GT/s
NVIDIA GeForce GT 120:
Name:          NVDA,Display-B
Type:          Display Controller
Driver Installed:          Yes
MSI:          Yes
Bus:          PCI
Slot:          Slot-2
Vendor ID:          0x10de
Device ID:          0x0640
Subsystem Vendor ID:          0x106b
Subsystem ID:          0x0010
ROM Revision:          3386
Revision ID:          0x00a1
Link Width:          x16
Link Speed:          5.0 GT/s

That's normal. It just lets you know the call has ended.

My macbook pro (lion 10.7.2) takes several minutes to connect to the internet after waking from sleep. Is there any way to make this instant?

Hi
My Macbook Pro 15 inch takes several minutes to be able to connect to the internet after waking from sleep. Does anyone else have this problem and is there a fix?
Alan

coxorangepippin wrote:
The message that comes up when I click on "TomTom Home Install" is "You cannot open Home Install because Power PC applications are no longer supported." Does this mean that the TomTom, which is absolutely vital to my life - well, not literally but you know what I mean - can no longer be used with my MacBook Pro?
What that means is that is can't be used with Lion 10.7. PowerPC was the chip Apple used up until 2006 when they switched to Intel. At that point, they created the Rosetta emulator to allow for PPC support for 5 years. They finally dropped the support with the release of Lion. It will only work with OS X 10.6 or earlier. The other option is to purchase a new GPS, which can be had for $100 for a decent one.

External Hard Drive Fail After Waking from Sleep

Hi,
I've been having this issue for over a year (since upgrading to Lion, and now still persists after upgrading to Mountain Lion), and I haven't been able to find the exact answer I need after searching through the posts here, and on the internet.
I have a 2011 MBP, and after upgrading to Lion last year, I've noticed that my WD external hard drive for the Mac has issues to be recognized after the laptop wakes from sleep. The drive icons are still there on the desktop, and all the files are listed. However, I cannot open any of the files, and Time Machine backup automatically fails.I am able to eject the drives by dragging the icons into the trash can. However, nothing happens if I simply unplug the fire wire 800 cable and re-plug it into the computer after ejecting the drives. I need to reset the external drive by unplugging both the fire wire cable and the power supply, and replug everything.
Aside from being a hampering process after waking from sleep, this is also very stressful on the drive itself, so I would like to fix this. Does anyone know the issue behind this or have a solution? Thanks in advance!

Thanks for this, and apologies for delay in replying...in between seeing your post I backed up the ext hdd to another mac and used the disc utility to erase and repair and then re mounted the ext hdd. OK. I have then tested the ext hdd being recognised when waking from sleep mode a few times and everything appears to be fine. If this doesn't work (long term) I will follow the instructions as you have suggested....
I now have a new problem with my HP printer (Photosmart Plus) which is not being recognised by a new wireless router..Ok whilst the router is switch on and I have reconfigured the printer..but when the router is switched off overnight and then switched back on...I get a 'printer is not connected' message and have to go through the re configure routine all over. I am minded to think this is a router problem as the same issue is happening to my wifes Mac Book Pro (which is only a few weeks old)...any suggestions..

Logic Pro X inaccessible after waking from sleep when using an MCU Control Surface

I'm having a problem I cannot seem to get around without force quitting Logic every time. If I have a Control Surface setup as a Mackie Control (v1.0); and if the computer goes to sleep, and then i turn off the controller while the computer is asleep (for any reason), and then wake the computer without turning on the controller first, Logic becomes completely unusable and must be force quit.
My controller in this example is Solid State Logic's Nucleus controller, however it happens with other Mackie Control compatible controllers (i have another one i tested against), BUT not a real Mackie Controller sold by Mackie (i tested with that as well); more details below.
For the SSL controller, Logic automatically sets it up like this:
Now if the computer goes to sleep, and i wake it up, i get the following dialog, which is fine:
After clicking on "Continue" button or hitting the enter key, Logic is rendered useless, as if there is a modal dialog still open somewhere. Clicking anywhere on the gui results in white flashes and nothing else. doing cmd+Q to quit actually makes it try to quit (a save dialog appears), but it never does successfully quit, making me resort to force-quitting. For an example, here's a pic of the file menu at this point:
I also have a regular Mackie Control Unit (MCU Pro) and the strange thing is with that unit, everything works fine after sleep, turning off controller, and re-awakening. However, there is a difference in what kind of dialog is displayed after the sleep, which probably has something to do with this issue.
Here is the setup screen of the MCU Pro:
And here is the dialog for the missing ports after waking from sleep:
This dialog is completely different than the other control surface's missing ports dialog. When clicking on "Keep unassigned" here, Logic resumes working fine.
The project is as minimal as possible; nothing is loaded, all that's there is an empty instrument track and a Control Surface configured.
I'm using a Mac Mini (late 2012)
Processor 2,6 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics Intel HD Graphics 4000
Software OS X 10.9.4 (13E28)
with Logic Pro X 10.0.7
Any help would be greatly appreciated!!

Did you ever figure out a solution to this problem?
I just pulled out my original Emagic Logic Control (MIDI) and I have having the same problem.

After upgrading to Tiger, freeze after waking from sleep on PM G4

My experience with Tiger in the past week as not been great. The reason I upgraded was to get iSync 2.1, so that my Moto E815 phone could be sync'd with my OSX AddresBook and iCal. This wasn't possible with the latest version of Panther.
So, I upgraded to Tiger 10.4.3, and now my G4 freezes immediately after waking from sleep. After pressing the 'return' key to wake the computer, the G4 sends a signal to wake the monitor, but on top of the screen saver is a black text box which states there was a problem I must press (and hold) the power button to restart the Mac. It's written in four languages.
When I installed Tiger, I used the 'archive' option.
My computer is a bit of a FrankenMac: Originally a G4/350 with AGP, upgraded with a Sonnet 1GHz G4 processor card, 1.12GB RAM, a 160GB HDD, an nVidia GeForce3 64MB AGP video card, Samsung DVD/CR-RW drive (Patchburn3) and a Belkin PCI card with 2 additional Firewire ports and 3 additional USB 2.0 ports. When I performed the upgrade, I had the keyboard and mouse plugged into the case USB 1.1 ports, a Logitech Notebook Pro USB camera plugged into the other case USB 1.1 port, and a D-Link BT120 USB->BT adapter plugged into one of the three USB 2.0 ports on the Belkin PCI card.
When I check the Console logs after the rebooting, I see a kernal panic in the panic.log. Apple has received this a number of times from me in the past week as I keep sending them 'talkback' logs after the fact.
I also see an error in the system.log which may reveal what is going on:
Nov 20 18:54:40 localhost kernel[0]: standard
timeslicing quantum is 10000 us
Nov 20 18:54:40 localhost mDNSResponder-107.3 (Aug 22
2005 11: 46:54)[44]: starting
Nov 20 18:54:40 localhost kernel[0]:
vmpagebootstrap: 284852 free pages
Nov 20 18:54:40 localhost kernel[0]:
migtable_maxdispl = 70
Nov 20 18:54:40 localhost kernel[0]: 71 prelinked
modules
Nov 20 18:54:40 localhost kernel[0]: Copyright (c)
1982, 1986, 1989, 1991, 1993
Nov 20 18:54:40 localhost kernel[0]: The Regents of
the University of California. All rights reserved.
Nov 20 18:54:40 localhost kernel[0]: using 2949 buffer
headers and 2949 cluster IO buffer headers
Nov 20 18:54:40 localhost kernel[0]: USBF: 14.270 Bus
9 already taken
Nov 20 18:54:40 localhost kernel[0]: USBF: 14.270
AppleUSBOHCI[0x2057000]::start OHCI controller will be
unloaded across sleep
Nov 20 18:54:40 localhost kernel[0]: FireWire (OHCI)
TI ID 8019 built-in now active, GUID 000a27ff
feb38fe6; max speed s400.
Nov 20 18:54:40 localhost kernel[0]: FireWire (OHCI)
VendorID 1033 ID cd PCI now active, GUID 0000303c
0008c32e; max speed s400.
Nov 20 18:54:40 localhost kernel[0]: Security auditing
service present
Nov 20 18:54:40 localhost kernel[0]: BSM auditing
present
Nov 20 18:54:40 localhost kernel[0]: disabled
Nov 20 18:54:40 localhost kernel[0]: rooting via
boot-uuid from /chosen:
474ACE52-2523-3EE7-9C54-DDC3734C7922
Nov 20 18:54:40 localhost kernel[0]: Waiting on <dict
ID="0"><key>IOProviderClass</key><string
ID="1">IOResources</string><key>IOResourceMatch</key><string
ID="2">boot-uuid-media</string></dict>
Nov 20 18:54:40 localhost kernel[0]: Got boot device =
IOService:/Core99PE/pci@f2000000/AppleMacRiscPCI/pci-bridge@D/IOPCI2PCIBridge/ma c-io@7/AppleKeyLargo/ata-4@1f000/KeyLargoATA/ATADeviceNub@0/IOATABlockStorageDri ver/IOATABlockStorageDevice/IOBlockStorageDriver/HDS722516VLAT80
Media/IOApplePartitionScheme/AppleHFS_Untitled2@10
Nov 20 18:54:40 localhost kernel[0]: BSD root:
disk0s10, major 14, minor 10
Nov 20 18:54:40 localhost kernel[0]: jnl:
replay_journal: from: 2668032 to: 12288 (joffset
0xe04000)
Nov 20 18:54:40 localhost kernel[0]: Jettisoning
kernel linker.
Nov 20 18:54:40 localhost kernel[0]: Resetting
IOCatalogue.
Nov 20 18:54:40 localhost kernel[0]: Matching service
count = 2
Nov 20 18:54:40 localhost kernel[0]: Matching service
count = 4
Nov 20 18:54:40 localhost kernel[0]: Matching service
count = 4
Nov 20 18:54:40 localhost kernel[0]: Matching service
count = 4
Nov 20 18:54:40 localhost kernel[0]: Matching service
count = 4
Nov 20 18:54:40 localhost kernel[0]: NVDANV20HAL
loaded and registered.
Nov 20 18:54:40 localhost kernel[0]: CHUDProf.kext
version: 4001000
Nov 20 18:54:40 localhost kernel[0]: raw version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT
2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
Nov 20 18:54:40 localhost kernel[0]: CHUDUtils.kext
version: 4001000
Nov 20 18:54:40 localhost kernel[0]: raw version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT
2005; root:xnu-792.6.22.obj~2/RELEASE_PPC
Nov 20 18:54:40 localhost kernel[0]: IPv6 packet
filtering initialized, default to accept, logging
disabled
Nov 20 18:54:41 localhost kernel[0]: UniNEnet:
Ethernet address 00:0a:27:b3:8f:e6
Nov 20 18:54:41 localhost launchd: Server 292f in
bootstrap 1103 uid 0: "/usr/sbin/lookupd"[42]: exited
abnormally: Hangup
Nov 20 18:54:41 localhost lookupd[56]: lookupd
(version 365) starting - Sun Nov 20 18:54:41 2005
Nov 20 18:54:41 localhost diskarbitrationd[36]:
disk0s10 hfs
474ACE52-2523-3EE7-9C54-DDC3734C7922 Onyx
Nov 20 18:54:41 localhost kernel[0]: jnl:
replay_journal: from: 1374208 to: 1564160 (joffset
0x624000)
Nov 20 18:54:41 localhost diskarbitrationd[36]:
disk1s10 hfs
947C0EA5-F775-330F-82D9-D2F8B65F7357 Backup
/Volumes/Backup
Nov 20 18:54:43 localhost kernel[0]: NVDA,NVMac: vram
[98000000:08000000]
Nov 20 18:54:43 localhost
/System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow:
Login Window Application Started
Nov 20 18:54:43 localhost loginwindow[72]: Login
Window Started Security Agent
Nov 20 18:54:44 localhost mDNSResponder: Adding browse
domain local.
Nov 20 18:54:45 localhost kernel[0]:
UniNEnet::monitorLinkStatus - Link is up at 100 Mbps -
Full Duplex
Nov 20 18:54:45 Jason-Radtkes-Computer configd[34]:
setting hostname to "Jason-Radtkes-Computer.local"
Nov 20 18:54:47 Jason-Radtkes-Computer configd[34]:
executing
/System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-netw ork
Nov 20 18:54:47 Jason-Radtkes-Computer configd[34]:
posting notification
com.apple.system.config.network_change
Nov 20 18:54:47 Jason-Radtkes-Computer lookupd[82]:
lookupd (version 365) starting - Sun Nov 20 18:54:47
2005
Nov 20 18:54:49 Jason-Radtkes-Computer configd[34]:
target=enable-network: disabled
I suspect the problem where the USB devices are started, because I had that Bluetooth adapter plugged in at the time of the upgrade. I'm speaking of the lines in the log which start with 'USBF'. The keyboard and mouse are useless when the black screen shows up after waking from sleep.
I've tried some of the suggestions I've found for the iBook 'wake from sleep' postings on macfixit.com and here - resetting NVRAM and removing a few of the .plist files. This didn't seem to help.
I would greatly appreciate help in resolving this issue. I've been a Mac owner since the original Macintosh (it's still in my house) and am frustrated that this is the first problem I've encountered.
Thanks in advance for your help.

Thanks. In fact I had bought a new keyboard and mouse (Macally) and sure enough, if I unplug it before it reboots, the CD drive door stays closed and I can boot from a CD! I did not try any of the other stuff. Is there any way to get it to stop this? Why does a USB peripheral cause the CD to eject anyway? Would love to know!
Ron

External monitor flashes on and off randomly after wake from sleep

I have a Mid-2009 13" MacBook Pro 2.26GHz hooked up to a Samsung SyncMaster 2033 External monitor via the MiniDisplayPort-DVI connector.
After waking from sleep, the external monitor will go blank for a fraction of a second at random intervals (display on the MBP remains normal). The flickering clusters are about minutes apart, while flickers within a cluster (usually 2-3 flickers per cluster) is of order seconds apart. "Detect displays" will not make this go away. The only way I can make it go back to normal is to unplug-and re-plug the MiniDisplayPort connector on the MBP.
Anyone else got a more elegant solution to this that does not involved wearing down the displayport?

I tried this. No change. However, I did start playing with the Display settings. Oddly enough, when I change the disfunctioning monitor to 720p it starts working again. Does this mean anything to anyone?

Cannot detect Mighty mouse after waken from Sleep

Similar Messages

Maybe you are looking for