Thanks for your interest... The source code of the second example I posted is identical to the SDK provided BluetoothChat source(http://developer.android.com/resources/ samples/BluetoothChat/index.html), except for the UUID changed from:- private static final UUID MY_UUID = UUID.fromString("fa87c0d0- afac-11de-8a39-0800200c9a66"); to:- private static final UUID MY_UUID = UUID.fromString("00001124-0000-1000-8000-00805F9B34FB");
The UUID is intended to be the HID UUID. I found this at http://forum.btframework.com/index.php?topic=172.0 The UUID reported near the final line of the logcat (0000110b-0000-1000-8000-00805f9b34fb) matches:- AudioSinkServiceClass_UUID: TGUID = '{0000110B-0000-1000-8000-00805F9B34FB}'; I think this may be the original class of the phone being reported on some sort of error tidyup. Could the failure have happened earlier in the log and the device is now returning to the default class on a cleanup? What was significant to me is that the PC recognised that I had set the device to a HID UUID as he PC reported:- "Registering a HID device to this system. Please Wait." and then "Registration Failed". Confusing... -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
