Support
All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.
Forum closed
This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview 

AuthorThread
User

20.04.2009 10:38:16
Re: ...

This posting is older than 6 months and can contain outdated information.
Short: 
This isn't a problem.

Long: 
The same as I said before - in much more detail:

1) Remote Buddy does what is required to operate the Wii Remote: 
Remote Buddy has to periodically and actively try opening a connection 
to the Wii Remote because the Wii Remote lacks the required 
capabilities to do this on its own with standard Bluetooth hardware. 
Other remotes - including the Sony PS3 BD Remote have this capability 
- the Wii Remote hasn't. You can use Remote Buddy's standard, seamless 
support for the Wii Remote.

Or you can do everything by hand and without any automatisms: if you 
don't want Remote Buddy to do what is needed to automatically connect 
to the Wii Remote when the remote is turned on, you can enable "Stop 
searching for paired remote controls after 1 minutes". One minute 
after Remote Buddy was started, you'll then have to walk through the 
Setup Wizard to manually pair with the Wii Remote as a new device 
every time. Ask yourself whether you want to waste your time on doing 
everything by hand (instead of using a working, automatic solution) 
for the solve purpose of suppressing essentially meaningless OS X 
debug messages that neither cause a problem, nor suggest any problem, 
nor have any potential to waste harddrive space (=> more on this in 
point 4).

2) If a connection request fails (which is and always has been the 
expected result when the Wii Remote is turned off), Apple's Bluetooth 
Daemon blued now logs it, whereas previously it didn't.

3) So, yes, the debug output comes from Apple's Bluetooth Daemon 
(blued). I have no influence on what Apple choses to log. If you don't 
want Apple's Bluetooth Daemon to log this event, please be sure to 
file a bugreport with Apple at http://bugreporter.apple.com/ so they 
know about it.

4) Logfile entries don't have any impact on functionality. Nor are 
they a sign that there is any problem. Nor do they cause problems. Nor 
do they fill up your harddrive over time: from your logfile, I gather 
that about 320 bytes are added to the logfile by blued per hour. It 
needs 3276.8 hours (or 136 days) until this makes up 1 (one!) 
megabyte. OS X automatically shrinks repeated, identical messages to a 
single line as you see in your logfile. In addition, OS X rotates (or 
"shortens") logfiles periodically, keeping them small, so chances are 
this logfile will never even reach one megabyte in size on your system.

Best regards, 
Felix Schwarz 

Thread-display::