"Repairing" a broken Pairing (after update to 10.4.11)
"Repairing" a broken Pairing (after update to 10.4.11)
- Subject: "Repairing" a broken Pairing (after update to 10.4.11)
- From: Martin Häcker <email@hidden>
- Date: Mon, 19 Nov 2007 11:19:27 +0100
Hi there,
because of current events (the update to 10.4.11) I again start
having lots of troubles with broken Pairings of e.g. Nokia phones.
As I said in my last post (A better Way to detect a broken pairing?)
I currently rely on -requestAuthentication of IOBluetoothDevice fame.
However this method consistently returns 2 - which according to the
docs means the pairing is broken (or at least that's what I read out
of them) and has to be redone.
However, we have a) found lots of devices work perfectly if the
return code is 2 and b) if you open the device with the Bluetooth
"Browse Device" Utility from Apple not only will the device work
(even if all our attempts to talk to the device end in errors) but
most interesting of all, after you do that the device returns 0 from
that method again and everything works dandy.
Which is... kind of interesting.
So, what magic do I have to incantate to "repair" the pairing if we
get errors from -requestAuthentication and which errors are repairable?
I'd really like to spare end users the hassle of repairing the device
every time apple puts out a system update - even a small one - if
it's unnecessary (and who knows what settings those re-pairings break).
Help?
Thanks,
Martin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden