Bluetooth problem with OSX Yosemite: Magic Mouse and Keyboard

As a followup, notice that the design charge of the NiMH cells is 1.2 V, or 2.4 V for two of them. That is below the level at which I took them out today, and the devices were already behaving funnily for a while. Of course, 1.2 V is their specified charge not what they actually charge up to. But again, for Alcaline cells, the design charge would be 3.0 V.

If that is confirmed, the only real thing we can complain about is that those devices make very poor use of the available charge - essentially, you can go down from 3.0+ to 2.5 V and have problems (to be confirmed). So that's rather, then, an issue of ecology.

That's what I just said. It's likely not linear, but you go down .25 V and that brings you down 68 %.

As an upside, I can probably fabricate an AAA to AA adapter, use the rechargeable batteries for my headset first inside my keyboard and mouse, like for a week or so, then take them out and drive them much further down in my headset.

I start to understand why Apple recently has bought Beats.

It's only because they're so environmentally aware!

Let's see how this perform 🙂

This solution fixed my problem.

Oh Oh!

10.10.2 beta 3 and lost connection to magic mouse on restart with 75% power in battery - not a good start...

Same here. Also, though I switched to Alkaline, had the same issues today, but only briefly.

Perhaps, that's actually a good thing...

https://code.google.com/p/google-security-research/issues/detail?id=136

lost connections is not a Yosemite related problem. I just found out that my father has the same problem on a Maverick system. I had to buy him a corded mouse...

Hi nashntk,

"everything were solved by resetting SMC Intel-based Macs: Resetting the System Management Controller (SMC). "

The SMC reset solved my bluetooth issues. After doing the SMC reset, my bluetooth worked perfectly to connect to my external bluetooth keyboard. Also resolved an issue I had not noticed whereby my iPad mini had stopped connecting by bluetooth.

SMC reset also resolved a problem I had of programs loading slowly and icons bouncing too long. I didn't even know that was a fixable problem.

Thanks for the suggestion.

Sorry friends, BUT Resetting each of the ways you're finding ONLY sets you up for another failure. YES, resetting SMC or deleting the BLUETOOTH plist and other things will get it to work after a restart, but ONLY temporarily. Apple's dragging it's butt so don;t kid yourself.

I've tried everything I have read in this very very long thread.

No permanent solution

The sad thing is, that it is no longer beta. It is 10.10.2 (14C109) production version, latest at the moment. I use a trackpad instead of the magic mouse mouse but the issue is the same. It will work after reboot and re-pair of the device. But after I get home from office, where I have another identical Apple trackpad it would stop working. I have to redo the whole song and dance again to get it to work.

Yosemite has proven to be the buggiest release Apple has made in a decade.

My dad had the same problem with Maverick. So I don't think it is related to Yosemity. Could it be a hardware problem?

Possible, but consider this: I have two trackpads. One at the office, one at home. So if it is weekend I only use the one at home. I can put the machine to sleep in between uses and for the night. It does not fail to recognize the trackpad when it wakes up. So using one single trackpad or a magic mouse all the time works - no problem.

The problem arises when I alternate between tow trackpads. One at home and one at office where I work.

Only after I go to the office does it have problems recognizing either trackpads and require me to remove them, reboot, re-pair. After that it will work again until I use trackpad "home" and trackpad "office" once. Once I return back from the office the home trackpad is not recognized, neither is the office trackpad if I do nothing to the computer setup and return to the office the next day.

Started right after I upgraded to Yos. (Unfortunately this is not the only issue with Yosemite, the "name (2)" is another issue, which messes up my MySQL server setup, but that is a different thread)

Say, we already KNOW this is a software problem since the WiFi/Bluetooth issues are all over the place. It points to a lousy Yosemite and possibly Mavericks and includes 10.10.2, at least here on my iMac since the keyboard took a hike this morning until reboot.

Well well well, since every Chinese geek now bought an IPhone making Apple a ridiculously cash-rich company, the LEAST Apple can do is ship a wired keyboard AND mouse to EVERY owner under warranty. It's incredible that 10.10.2 didn't make a difference but it made no difference here except to **** me off.

There are massive amounts of devices out there and a couple of hundreds in this thread. I'm not so sure. If it is a software problem, why haven't they fixed it? And how do they fix it for all those people who have a Apple care protection plan /guarantee?

I obviously don't have the answer but can say I'm one of those that brought my otherwise fine IMac to an Apple store a month ago and waited around for them to tell me they found nothing. All this is real peachy except that a simple device like a bluetooth keyboard and mouse cut out. Frankly, I don't give that much of a hoot. I switched to a USB mouse weeks ago and will now dig up my old USB keyboard since the upgrade to 10.10.2 is useless as it relates to this. In closing, it simply makes no sense and no one from Apple bothers to admit it...that's the real kick in the head.