public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "colorant" <colorant@163.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] When Connect A2DP : Error 22 while configuring device
Date: Thu, 19 Jun 2008 16:20:53 +0800	[thread overview]
Message-ID: <011101c8d1e5$63fd26b0$6e01a8c0@Raymondpc> (raw)
In-Reply-To: 008e01c8d113$c65174b0$6e01a8c0@Raymondpc

Hi

    I am try to connect A2DP with Bluez

    When useing Aplay to try it , I have following problems :

~ # aplay -D bluetooth demo.wav
ALSA lib pcm_bluetooth.c:1158:(bluetooth_cfg) Error 22 while configuring 
device
aplay: main:510: audio open error: Invalid argument

Can Someone point out what might be the reason ?

My config file is :

~ # cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#

# HCId options
options {
        # Automatically initialize new devices
        autoinit yes;

        security auto;

        pairing multi;

        offmode devdown;

        passkey "1234"; // I use my pc with usb dongle to provide the a2dp 
service, so this is set to1234 not 0000 or 8888 etc.
}

# Default settings for HCI devices
device {
        name "%h-%d";

        class 0xff0100;
        # Default packet type
        #pkt_type DH1,DM1,HV1;

        iscan disable; pscan enable;

        # Page timeout (10s)
        pageto 16384;

        # Discoverable timeout (0 == disabled)
        discovto 0;

        lm accept;

        lp rswitch,hold,sniff,park;
}


~ # cat /etc/bluetooth/audio.conf
# Configuration file for the audio service

# This section contains options which are not specific to any
# particular interface
[General]

# If we want to disable support for specific services
# Defaults to supporting all implemented services
# disable=Sink

# SCO routing. Either PCM or HCI (in which case audio is routed to/from 
ALSA)
# Defaults to HCI
SCORouting=PCM

# Headset interface specific options (i.e. options which affect how the 
audio
# service interacts with remote headset devices)
[Headset]

# Set to true to only support HSP
# Defaults to false
DisableHFP=true

# Just an example of potential config options for the other interfaces
#[A2DP]
SourceCount=2






-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-06-19  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 12:07 [Bluez-users] Bluez build problem Voni Hakau
2008-06-13 15:25 ` Mumia W..
2008-06-16 12:05   ` Voni Hakau
2008-06-16 22:41     ` Mumia W..
2008-06-30 12:06       ` Voni Hakau
2008-06-30 12:09         ` Voni Hakau
2008-07-01 15:09           ` jayjwa
2008-07-02  7:56             ` Voni Hakau
2008-07-03 22:18               ` jayjwa
2008-06-18  7:20   ` [Bluez-users] Error encounter when connecting A2DP following wiki instruction ! How to connect A2DP ? colorant
2008-06-19  8:20     ` colorant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-19  8:23 [Bluez-users] When Connect A2DP : Error 22 while configuring device colorant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='011101c8d1e5$63fd26b0$6e01a8c0@Raymondpc' \
    --to=colorant@163.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox