Luiz Augusto von Dentz wrote:
> Sorry I just interpret this all wrong, as the application has been
> sending 00:00:00:00:00:00, but yeah you seem to be doing it right
> although Im not sure you can have more than one SCO connection active,
> but that doesn't explain the host is down error, so perhaps there is
> something else blocking you.
I attempted briefly to go through the code and see what exactly is causing the error. It appears that bluetoothd starts a search for the headset and is unable to find it (or prevented from finding it). I am unclear why it cannot find the headset when another audio stream is in progress. It could be that there is some sort of locking mechanism in place. The code is relatively new to me. Maybe as you mentioned it is requesting another SCO connection and prevented from creating one with another device? I will try to dig deeper and see where it is actually getting blocked.
- Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
