public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Patryk Zawadzki" <patrys@pld-linux.org>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>,
	"BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [Bluez-users] Motorola S9 and BlueZ 4.14
Date: Sun, 19 Oct 2008 17:55:53 +0200	[thread overview]
Message-ID: <89b6ba3a0810190855g2aa8bd00v9fe2c782fe5efb3e@mail.gmail.com> (raw)
In-Reply-To: <48FA49A4.9040908@powercraft.nl>

After some digging in the current GIT head:

bluetoothd[20589]: AVCTP: connected to 00:0D:FD:15:F0:3E
bluetoothd[20589]: AVRCP: uinput initialized for 00:0D:FD:15:F0:3E
bluetoothd[20589]: AVDTP: incoming connect from 00:0D:FD:15:F0:3E
DEBUG: trying to change from OPEN to OPEN
bluetoothd[20589]: stream state change failed: Input/output error

So for me it tries to change the stream state top OPEN twice.

Another debugging effort with pulseaudio bluetooth init:

bluetoothd[20589]: Received SET_CONFIGURATION_CMD
DEBUG: initializing stream sock to -1
[...]
bluetoothd[20851]: Audio API: received BT_SETCONFIGURATION_REQ
bluetoothd[20851]: config a2dp - device = 00:0D:FD:15:F0:3E access_mode = 2
bluetoothd[20851]: codec sbc - frequency = 2 channel_mode = 1
allocation = 1 subbands = 1 blocks = 1 bitpool = 44
bluetoothd[20851]: a2dp_source_config: selected SEP 0xb851c630
bluetoothd[20851]: avdtp_ref(0xb8521398): ref=4
bluetoothd[20851]: setup_ref(0xb8519490): ref=1
bluetoothd[20851]: setup_ref(0xb8519490): ref=2
bluetoothd[20851]: SEP 0xb851c630 locked
DEBUG: stream sock is -1
bluetoothd[20851]: Unable to get stream transport
bluetoothd[20851]: config failed

The stream socket does not seem to be set anywhere else along the way
(added debug prints to all stream socket changes in bluez code).
That's why get_transport returns FALSE. Still not sure if the bug is
in pulseaudio or in bluez.

Also sending this to bluez-devel, please don't shoot me for crossposting.

-- 
Patryk Zawadzki

-------------------------------------------------------------------------
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
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-10-19 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.81198.1224358186.3608.bluez-users@lists.sourceforge.net>
2008-10-18 19:48 ` [Bluez-users] Motorola S9 and BlueZ 4.14 Patryk Zawadzki
2008-10-18 20:40   ` Jelle de Jong
2008-10-19 15:55     ` Patryk Zawadzki [this message]
2008-10-19 16:09       ` [Bluez-devel] " Patryk Zawadzki
2008-10-19 16:35         ` Johan Hedberg
2008-10-19 16:54           ` Patryk Zawadzki
2008-10-19 17:06             ` Patryk Zawadzki
2008-10-19 17:16               ` Johan Hedberg
2008-10-20 20:53           ` Luiz Augusto von Dentz
2008-10-20 21:05             ` Johan Hedberg

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=89b6ba3a0810190855g2aa8bd00v9fe2c782fe5efb3e@mail.gmail.com \
    --to=patrys@pld-linux.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --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