-
All replies
-
Helpful answers
-
Mar 12, 2016 1:14 PM in response to fjigsdslijgsdlkjby KimUserName,I found this on their website. Not sure if it will help. http://support.logitech.com/en_ca/article/Connect-the-MX-Anywhere-2-mouse-to-a-B luetooth-device?product=a0qi0000008tB99AAE#mac_osx
Kim
-
Mar 12, 2016 1:36 PM in response to KimUserNameby fjigsdslijgsdlkj,Yeah I've got it connected, it just won't recognize it until I login. Thanks anyway. This is driving me nuts!
-
Mar 13, 2016 8:49 AM in response to fjigsdslijgsdlkjby babowa,★HelpfulThat can sometimes happen because: the Mac can't "see" the mouse (or whatever) when it is not on and the sequence for a) booting up, b) the startup chime (the audible notification that all is well with the Mac), and c) recognizing any wireless devices is so narrow that it sometimes overlaps (difficult to explain). For that reason, I always have an older USB keyboard and mouse "standing by" and ready to take over if necessary. It also sometimes helps to move around the mouse, turn it off/back on, etc.
-
Mar 13, 2016 9:00 AM in response to babowaby fjigsdslijgsdlkj,Yeah the startup sequence seems to be a real problem for OS X. I've got it connected to my TV as an external display. That's a crap shoot whether or not that will be displaying at the startup screen. Same goes for my wireless apple keyboard. For someone who switches between windows and os x this is super obnoxious.
I have a dongle with this mouse, which solves the problem of recognition, but wouldn't it be slick if I could use it as intended? Wow, imagine.
I'll do some more research on boot up issues but I'm guessing it's a "deal with it" situation.
Thanks for the reply!
-
Mar 13, 2016 9:19 AM in response to fjigsdslijgsdlkjby Barney-15E,If you have trouble with your Apple wireless keyboard, I would imagine you have some interference in your Bluetooth, either the signal or some third-party software. I've never had any problems with the keyboard being recognized nor my Majic Trackpad. Bothe are fully functional at startup.
Potential sources of Wi-Fi and Bluetooth interference - Apple Support
If your Apple wireless mouse, keyboard, or trackpad aren't working as expected - Apple Support
http://osxdaily.com/2013/05/06/fix-bluetooth-device-disconnecting/
Does oes the mouse require any drivers or can it be just used as a basic Bluetooth mouse? If you have installed drivers, have you tried just uninstalling them and using it with basic mouse functionality to test if it is a driver problem?
-
Mar 13, 2016 9:26 AM in response to Barney-15Eby babowa,I've never had any problems with the keyboard being recognized nor my Majic Trackpad. Bothe are fully functional at startup.
Mine are usually (95% of the time); however, that average goes down to about 50% if/when I need to employ any keys at startup (recovery or whatever - it makes no difference) and a Senior Advisor pointed out the milli-second sequence that has to happen in order for the keys to be recognized (the Mac has to be on before it'll recognize the keyboard, but you have to press the keys in a way so it is on but before it goes to its' normal bootup sequence).
-
Mar 13, 2016 9:29 AM in response to babowaby Barney-15E,babowa wrote:
I've never had any problems with the keyboard being recognized nor my Majic Trackpad. Bothe are fully functional at startup.
Mine are usually (95% of the time); however, that average goes down to about 50% if/when I need to employ any keys at startup (recovery or whatever - it makes no difference)
Using startup key sequences is flakey, but that is not the problem here.
-
Mar 13, 2016 9:34 AM in response to Barney-15Eby babowa,Yes, I know; however, to me the two are related as they all have to do with the Mac recognizing the peripherals.
-
Mar 13, 2016 12:37 PM in response to babowaby Barney-15E,Well, they should be Recognized by the login screen regardless of whether startup key sequences work.
-
Mar 16, 2016 3:56 AM in response to Barney-15Eby fjigsdslijgsdlkj,It does have it's own software with the mouse. Maybe that's the problem. My mac is in the shop for an unrelated issue right now but I'll try that when I get it back.