Attachment 70251 Details for Bug 57239 – bluez audio config file

bluez audio config file

audio.conf (text/plain), 1.47 KB, created by alium on 2012-11-19 13:29:47 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: alium

Created: 2012-11-19 13:29:47 UTC

Size: 1.47 KB

patch

obsolete

># Configuration file for the audio service
>
># This section contains options which are not specific to any
># particular interface
>[General]
>Enable=Socket
>
># Switch to master role for incoming connections (defaults to true)
>#Master=true
>
># If we want to disable support for specific services
># Defaults to supporting all implemented services
>#Disable=Gateway,Source,Socket
>
># SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
># Defaults to HCI
>#SCORouting=PCM
>
># Automatically connect both A2DP and HFP/HSP profiles for incoming
># connections. Some headsets that support both profiles will only connect the
># other one automatically so the default setting of true is usually a good
># idea.
>AutoConnect=true
>
># Headset interface specific options (i.e. options which affect how the audio
># service interacts with remote headset devices)
>[Headset]
>
># Set to true to support HFP, false means only HSP is supported
># Defaults to true
>#HFP=true
>
># Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
>MaxConnected=1
>
># Set to true to enable use of fast connectable mode (faster page scanning)
># for HFP when incoming call starts. Default settings are restored after
># call is answered or rejected. Page scan interval is much shorter and page
># scan type changed to interlaced. Such allows faster connection initiated
># by a headset.
>FastConnectable=false
>
># Just an example of potential config options for the other interfaces
>#[A2DP]
>#SBCSources=1
>#MPEG12Sources=0

Actions: View

Attachments on bug 57239: 70206 | 70207 | 70208 | 70251 | 70252

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.