This posting is older than 6 months and can contain outdated information.
That's not what I meant to say. What I meant to say is "try turning
off Bluetooth [support in Remote Buddy]". You can do this in
Preferences > Hardware > Bluetooth Receiver > .. - or temporarily just
via Remote Buddy's pull down menu.
As I've stated already, this disconnects any Bluetooth remote from your computer, which doesn't really solve the issue. I might as well just turn Remote Buddy off, because it will achieve the same effect.
It sure is easy to point fingers at Remote Buddy, but it doesn't
change the matter of fact that this is a problem in Apple's drivers,
not Remote Buddy.
I'm not pointing fingers at Remote Buddy as the only problem. As I also stated before, the same issue occurs with Apple's Bluetooth Setup Assistant when it is actively looking for new devices. However, once Bluetooth Setup Assistant FINDS those devices, it stops looking and network transmission resumes properly.
Remote Buddy does NOT do this, because it is ALWAYS looking for new devices. Something that can easily be fixed by creating a timer (adjustable by the user, if necessary) that tells Remote Buddy to stop looking for new devices after so many minutes unless a key-combination or menu selection is used to re-trigger active searching.
Apple's Bluetooth Mouse and Keyboard drivers run as kernel extensions
and thus *have* to use a *private*, kernel-level Apple API. Bluetooth
userspace APIs are *NOT* available to kernel extensions. Everybody
else, including Remote Buddy, has to use the only publicly documented,
userspace Bluetooth APIs of OS X.
Again, this is a misunderstanding of the issue we're describing and a deflection back toward a problem with the OS. If this were an issue that affected all Bluetooth software programs, it would be front page tech news, by now. I mean, DarwiinRemote works perfectly fine with multiple Nintendo Wii remotes, so it can clearly be done.
I'm not upset in any way by what Remote Buddy does well, but there is clearly an issue with the latest version if JohnV's experiences can tell us anything. Perhaps instead of playing the blame game, we could work together as developers and end users to find and resolve the issue so that we end users feel comfortable recommending this software to other users, as I have done in the past.
