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 11:34:17
Re: Re: ...

This posting is older than 6 months and can contain outdated information.
 
So it's not just me, but every user on 10.5.6 now has this in their 
system.log file ??

 
Yes. For every connection that's tried to be opened, but can't be 
established because the device is turned off, out of range, ...

As I said before, as a matter of fact, automatic pairing with the Wii 
Remote can't be supported in any other way for technical reasons. It's 
not a question of coding style, capabilities or software quality. It's 
a Wii Remote hardware requirement. If you want automatic pairing for 
the Wii Remote, that's how it'll have to work.

Where device-side auto-connect is supported - for example with the 
Sony PS3 BD Remote - Remote Buddy knows about it and uses it and does 
never try to open a connection by itself. Instead it let's the device 
open it itself as soon as it the device is turned on.

Device-side auto-connect, however, is not supported by the Wii Remote. 
Thus the necessity for the different solution for this remote.

What I don't understand is if this is RB looking for the wii remote, 
why does it only happen 266 times every 27 minutes, and not every 
second of every minute, it does not sound very logical !

 
A connection attempt is not immediately suceeding or failing. It needs 
quite some time before it times out. When this timeout occurs is 
subject to Apple's Bluetooth stack.

I have set RB to disconnect the remote after 1 minute for testing 
(normally use 15 minutes), after 1 minute it disconnects silently 
and stays silent until 27 minutes later when it fires off and 
thereafter every 27 minutes ?!

 
This is not the option I talked about. I talked about the "Stop 
searching for remotes after .. minutes".

Problem with all of these entries in the log file, is that I inspect 
it once a week to look for any errors, their used to be just a few 
lines, now I am going to have to look through many archive files as 
well as the current ones, it also means the disk will never sleep.

 
Thanks for sharing your perspective.

But as I said before, I can't do anything about this. This is 
unnecessary debug output submitted to the logfile from Apple's blued 
software, not Remote Buddy. Unnecessary, because developers are 
provided with dedicated, much richer and much more detailed Bluetooth 
debug tools by Apple for several years now.

Best regards, 
Felix Schwarz 

Thread-display::