User

28.10.2007 03:12:28

Hi,

I was wondering if anyone has been able to pair their Wiimote with Remote Buddy in 10.5? 

User

28.10.2007 19:24:01

It used to work fine with all developer previews of Leopard. I'm able 
to reproduce the problem with the Leopard GM, though, which I 
installed only an hour ago.

I'll look into it.

Best regards, 
Felix 

User

28.10.2007 21:13:02

I've now done some further testing and it turns out that the BT stack 
in Leopard has at least one issue where it notifies applications that 
it has successfully retrieved the name of a new device. A call on the 
BluetoothDevice's getName selector in Cocoa will return NULL, though, 
meaning it in fact has not received back the name - or at least 
doesn't share it with Remote Buddy at that point.

It will, however, eventually repeat the notifications and then also 
deliver the names - but with great delay, so that the Wiimote most 
likely is no longer in pairing mode and a connection fails.

Further examination has given me clues that pre-existing pairing 
information from older OS releases *may* cause these issues. This 
solved the issue for me:

1) Enter System Preferences > Bluetooth 
2) Remove all Bluetooth devices 
3) Start Remote Buddy and pair as usual - works just fine for me now 
(tried with a set of different remotes).

That only the Bluetooth device adresses were listed in the prefs prior 
to this - and that they are now listed by name again (as was 
previously the case in OS X 10.4) - seems to at least partially 
confirm for me that this is an internal issue of the BT stack's 
"paired devices" storage, not Remote Buddy or other BT apps themselves.

After all: 
- the name of the device is the only way Remote Buddy can recognize 
the remote 
- the device name is definately stored along with the list of paired 
BT devices 
- if a device's address is displayed instead of the device's name in 
the prefs, something must have gone wrong there

Best regards, 
Felix 

User

29.10.2007 03:57:30

Clearing all the devices in the Bluetooth preference pane did the trick, though the pairing did indeed seem longer than usual. Guess I'll have to wait for 10.5.1.

Thanks.

User

31.10.2007 00:11:21

Actually, noticed something odd. Not sure if it's Leopard or if it was the recent Remote Buddy update.

Sometimes, when I switch to another application using the mouse and use my Wiimote, it won't detect the application change and still process they key event under the context of the previous application.

e.g. 
In Safari. Use mouse to switch to iTunes. Press left arrow key on Wiimote. RB will make Safari active again and process it as pressing the left arrow key in Safari.

 

User

31.10.2007 13:59:07

Remote Buddy will need half a second before it switches Behaviours. 
This delay is needed to work around a timing issue in NSWorkspace that 
did previously lead to the automatic relaunch of applications you just 
quit.

Best regards, 
Felix 

User

04.11.2007 19:11:07

Hi,

Was using my Wiimote today and all of a sudden it stopped working. RB was still responding so it wasn't hanging because of iTunes, had to restart RB.

Console logs had this:

Nov 4 13:06:25 j kernel[0]: BT_USB Controller: SuspendDevice(0) failed with error e0004051 
Nov 4 13:06:25 j kernel[0]: BT_USB Controller: SuspendDevice(0) we are still connected to our hub so .. plain reset 0x40c0b00 
Nov 4 13:06:34 j kernel[0]: [InterruptReadHandler] Received kIODeviceNotResponding error - retrying: 1. 
Nov 4 13:06:34 j kernel[0]: E:[AppleUSBBluetoothHCIController][BulkInReadHandler] Received kIOReturnNotResponding error - retrying: 1. 
Nov 4 13:06:34 j Remote Buddy[196]: Error 268435459 0x10000003 sending: 
Nov 4 13:06:34 j kernel[0]: E:[AppleUSBBluetoothHCIController][BulkInReadHandler] immediate error (-536854449) queueing next read. 
Nov 4 13:06:34 j kernel[0]: IOBluetoothHCIController::terminateWL .. done 
Nov 4 13:06:35 j kernel[0]: CSRHIDTransitionDriver::start [] 
Nov 4 13:06:36 j kernel[0]: CSRHIDTransitionDriver::switchToHCIMode legacy

Last edited: 04.11.2007 19:11:47 

User

10.11.2007 01:40:10

Thanks for posting. This looks like a problem in Apple's Bluetooth 
drivers, which subsequently leads to the breakdown of the connection 
and in consequence Remote Buddy placing an error message on the 
console that it could not send data to the remote control. Please 
consider filing a bug with Apple's Bugreporter on this if you find a 
way to reproduce it or it occurs without an apparant reason (like 
empty batteries).

Best regards, 
Felix 

User

10.11.2007 06:26:52

Thanks for responding.

Since it's not a RB bug, I'll file a report with Apple the next time it happens (only twice so far).