[pulseaudio-discuss] [PATCH v2 4/5] bluetooth: Do not switch to hfgw unless Playing

Mikel Astiz mikel.astiz.oss at gmail.com
Fri Jul 27 07:41:23 PDT 2012


From: Mikel Astiz <mikel.astiz at bmw-carit.de>

If no audio stream exists to the remote device during discovery,
setting the profile to hfgw would request it. This means BlueZ will try
to initiate a SCO connection, which the remote end (the phone) will
typically reject. Thus, module-bluetooth-device will fail to load.
---
 src/modules/bluetooth/module-bluetooth-discover.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/src/modules/bluetooth/module-bluetooth-discover.c b/src/modules/bluetooth/module-bluetooth-discover.c
index d4e056e..695fc14 100644
--- a/src/modules/bluetooth/module-bluetooth-discover.c
+++ b/src/modules/bluetooth/module-bluetooth-discover.c
@@ -107,7 +107,7 @@ static pa_hook_result_t load_module_for_device(pa_bluetooth_discovery *y, const
                 args = tmp;
             }
 
-            if (d->hfgw_state >= PA_BT_AUDIO_STATE_CONNECTED)
+            if (d->hfgw_state >= PA_BT_AUDIO_STATE_PLAYING)
                 args = pa_sprintf_malloc("%s profile=\"hfgw\"", args);
             else if (d->audio_source_state >= PA_BT_AUDIO_STATE_CONNECTED)
                 args = pa_sprintf_malloc("%s profile=\"a2dp_source\" auto_connect=no", args);
-- 
1.7.7.6



More information about the pulseaudio-discuss mailing list