diff options
| author | Nick Pelly <npelly@google.com> | 2009-09-22 15:19:46 -0700 |
|---|---|---|
| committer | Colin Cross <ccross@android.com> | 2011-06-14 09:09:16 -0700 |
| commit | 5c9b4de70db251b1b8e9d927948e9604a5aaeccd (patch) | |
| tree | 64e71850f4e803ad767e131d42a359d9f047852b /init | |
| parent | 40a803df07b9954d28258f77ca14ecc83d087891 (diff) | |
| download | kernel_samsung_aries-5c9b4de70db251b1b8e9d927948e9604a5aaeccd.zip kernel_samsung_aries-5c9b4de70db251b1b8e9d927948e9604a5aaeccd.tar.gz kernel_samsung_aries-5c9b4de70db251b1b8e9d927948e9604a5aaeccd.tar.bz2 | |
Bluetooth: Fallback to SCO on error code 0x10 (Connection Accept Timeout).
This is to support the Motorola HF850 carkit which reports the error code 0x10
for an eSCO attempt, even though it advertises eSCO support. Here is the
hcidump:
2009-09-22 15:40:24.492391 < HCI Command: Setup Synchronous Connection
(0x01|0x0028) plen 17
handle 1 voice setting 0x0060
2009-09-22 15:40:24.493002 > HCI Event: Command Status (0x0f) plen 4
Setup Synchronous Connection (0x01|0x0028) status 0x00 ncmd 1
2009-09-22 15:40:30.594869 > HCI Event: Synchronous Connect Complete (0x2c)
plen 17
status 0x10 handle 257 bdaddr 00:50:CD:20:C6:84 type eSCO
Error: Connection Accept Timeout Exceeded
With this patch we will retry with a SCO connection, which succeeds.
Unfortunately the Moto HF850 also takes 5 seconds to return the error for the
eSCO attempt, so it will still take 5 seconds to fallback to SCO with this
patch.
Signed-off-by: Nick Pelly <npelly@google.com>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions