From: Zheng Tao-B46827 <b46827@freescale.com>
To: <linux-bluetooth@vger.kernel.org>
Subject: BlueZ for Android 4.4.3
Date: Tue, 10 Feb 2015 09:51:37 +0800 [thread overview]
Message-ID: <54D96429.8000304@freescale.com> (raw)
Hi, Peers
Thanks for your hard work that let us can experience BlueZ for Android.
But I am faced with a audio/a2dp problems that stick me many weeks.
I’m try to port Bluez to kitkat 4.4.3, and many common profiles, such as
HIDP/FTP/GATT can function successfully. But the A2DP profile failed.
So, I try to debug it using haltest tool as follows(with USB Bluetooth
Dongle):
1.bluetooth init
2.bluetooth enable
3.bluetooth get_profile_interface a2dp
4.bluetooth start_discovery
5.bluetooth create_bond xxxxxxxx
6.audio init
7.audio open_output_stream
Then it will prompts:
D/BlueZ ( 1106):
external/bluetooth/bluez/android/hal-audio.c:audio_open_output_stream()
D/BlueZ ( 1106):
external/bluetooth/bluez/android/hal-audio.c:ipc_open_stream_cmd()
E/BlueZ ( 1106): audio: Invalid cmd socket passed to audio_ipc_cmd
E/BlueZ ( 1106): audio: cannot open output stream
when I debug it , I found that
BlueZ ( 1106):
external/bluetooth/bluez/android/hal-audio.c:ipc_handler() Waiting for
connection ...
And it seems that there is no audio socket to connect it.
I’m not familiar with Bluez stack details, can you give some advice?
What should I do to enable audio/a2dp functionality and execute audio
play command? Thanks.
----------------------------------------------
*Best Regards!*
Tony Zheng
next reply other threads:[~2015-02-10 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 1:51 Zheng Tao-B46827 [this message]
2015-02-11 8:16 ` BlueZ for Android 4.4.3 Lukasz Rymanowski
2015-02-11 9:37 ` Zheng Tao-B46827
2015-02-11 11:41 ` Lukasz Rymanowski
2015-02-12 2:22 ` Zheng Tao-B46827
2015-02-13 16:02 ` Lukasz Rymanowski
2015-03-02 6:54 ` Zheng Tao-B46827
2015-03-04 11:43 ` Lukasz Rymanowski
[not found] ` <54FD4B0E.9010306@freescale.com>
2015-03-16 10:16 ` Lukasz Rymanowski
-- strict thread matches above, loose matches on Subject: below --
2015-02-10 1:37 Zheng Tao-B46827
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=54D96429.8000304@freescale.com \
--to=b46827@freescale.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.