Skip to contentSkip to conversation

Why always disconnect the headset?

Bluez-devel Ludovico Cavedon 2 participants 3 messages Jul 27, 2008 – Aug 24, 2008 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

Hi all,
I noticed that every time an application closes a SCO audio device, my headset gets disconnected (HEADSET_STATE_DISCONNECTED). This means that when the application reopens the device, it requires some seconds to get the audio working.

So, why is the headset disconnected and not just left in the state HEADSET_STATE_CONNECTED? (i.e. the same stat that the headset enters when I turn it on and pairs with my pc).

Thanks,
Ludovico

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#1 lore raw

Hi Ludovico,

Quoted 10 lines · Ludovico Cavedon

I noticed that every time an application closes a SCO audio device, my headset gets disconnected (HEADSET_STATE_DISCONNECTED). This means that
when the application reopens the device, it requires some seconds to get
the audio working.

So, why is the headset disconnected and not just left in the state HEADSET_STATE_CONNECTED? (i.e. the same stat that the headset enters when I turn it on and pairs with my pc).

You didn't mention which version of BlueZ you use, but in recent versions the logic is such that only implicitly created connections are automatically disconnected (after a 3 second timeout) but explicitly created connections stay up until you manually disconnect them. An implicitly created connection would be one caused by an ALSA application when it opens the audio device. Connections that fall into the explicitly created category are those that happen when you turn the headset on and it connects to the PC or when you call the Headset.Connect() D-Bus method and the PC connects to the headset.

Johan

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel

#2 lore raw

Hi Johan,

Quoted 12 lines · Johan Hedberg
Quoted 10 lines · Ludovico Cavedon

I noticed that every time an application closes a SCO audio device, my headset gets disconnected (HEADSET_STATE_DISCONNECTED). This means that
when the application reopens the device, it requires some seconds to get
the audio working.

So, why is the headset disconnected and not just left in the state HEADSET_STATE_CONNECTED? (i.e. the same stat that the headset enters when I turn it on and pairs with my pc).

Quoted 9 lines

You didn't mention which version of BlueZ you use, but in recent versions the logic is such that only implicitly created connections are automatically disconnected (after a 3 second timeout) but explicitly created connections stay up until you manually disconnect them. An implicitly created connection would be one caused by an ALSA application when it opens the audio device. Connections that fall into the explicitly created category are those that happen when you turn the headset on and it connects to the PC or when you call the Headset.Connect() D-Bus method and the PC connects to the headset.

Sorry I forgot: I am using 3.26 provided with Ubuntu hardy. Good news, I'll update my bluez version!

Thank you for your answer,
Ludovico

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel