site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com Hello, I will fill a radar bug on this issue. Best Regards, Camille Hi, Thank you for your help! Best, Camille _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... I sent an email on the 11th of march describing a problem I have on some computers when connecting to a Nintendo Wiimote. As a reminder, this problem manifests itself as follows: - on machines with one cpu (eg. G4 power-pc), it is impossible to connect to the device ; - on machines with two cpus (eg. daul G5, MacBook Pro), the connection succeed on the second try ; - if we enable only one cpu or two cpus with the CHUD tools on a Mac Pro the above cases are reproducible. A cure to that problem is to remove the device entry in the Bluetooth preferences pane before each connection. My guess is that after the first connection, the blued.plist is corrupted.

From what I can learn from the the logs, it seems the Bluetooth HID layer tries to connect to the Wiimote and invokes the AppleBluetoothHIDMouse driver, which indeed fails to start. For me this is an error, and I would like to know if there is a workaround other than hacking blued.plist. I am trying to understand why a connection to a Wiimote fails when running a G4 computer. I actually found that enabling only one core on a Mac Pro produced the same results. Enabling all cores on the computer does not lead to that problem. It is possible to connect to the Wiimote when the device is removed from the recent devices list in the Bluetooth Preference Pane. I haven't found a way to do this programmatically. When the device fails to connect, a log is added in system.log as follows: Mar 11 22:33:01 Hippolyte kernel[0]: [IOBluetoothHIDDriver] [handleStart] final device setup failed

Mar 11 22:33:01 Hippolyte kernel[0]: [IOBluetoothHIDDriver] [handleStart] Failed. If I remove the device from the recent devices list, here is what is logged: Mar 11 22:44:44 Hippolyte kernel[0]: [IOAppleBluetoothHIDDriver] [getDevicePropertiesWL][00-19-1d-93-eb-85] Error retrieving device properties. Mar 11 22:44:44 Hippolyte kernel[0]: [IOAppleBluetoothHIDDriver] [probe] Couldn't retrieve device properties Mar 11 22:44:44 Hippolyte kernel[0]: [AppleBluetoothHIDMouse] [getDevicePropertiesWL][00-19-1d-93-eb-85] Error retrieving device properties. Mar 11 22:44:44 Hippolyte kernel[0]: [AppleBluetoothHIDMouse] [probe] Couldn't retrieve device properties Mar 11 22:44:44 Hippolyte kernel[0]: [IOBluetoothHIDDriver] [getDevicePropertiesWL][00-19-1d-93-eb-85] Error retrieving device properties. Mar 11 22:44:44 Hippolyte kernel[0]: [IOBluetoothHIDDriver] [handleStart] Could not get device properties Mar 11 22:44:44 Hippolyte kernel[0]: [IOBluetoothHIDDriver] [handleStart] Failed. I would like to know if this is a bug in the Apple bluetooth driver and if there is a way to workaround this by programmatically remove the device from the recent devices list. This email sent to site_archiver@lists.apple.com