Hi,
I intend to use the A2DP profile of BlueZ, by playing some music
over my desktop(Having Broadcom USB bluetooth adaptor) and listering it on
BT-headset.
System Details:
Linux Flavour: Fedora Core 4
Linux Kernel: 2.6.26
BlueZ version: 4.18
DBUS version: 1.2.4
GLIB version: 2.14
ALSA version: 1.013
HCID:
When I start bluetooth service, hcid throws error: Unable to get
on DBUS and continues to run. I proceed further to pair with headset,
wherein in gives, Can't connect: Input/Output error. But surprisingly it
can connect with other bluetooth devices like mobile phones. Behaviour is
alike irrespective of pin-helpers,bluepin or bluez-pin.
Bluetoothd:
Yes, I know that version 4.xx replaces hcid wiht bluetoothd. I
edited the /etc/ini.d/bluetooth script to spawn bluetoothd daemon, instead
of hcid daemon. Even Bleutoothd daemon throws error: Unable to get on
DBUS and exits.
Im attaching the debug log herewith. Any help in this regard is deeply
appreciated.
Warm Regards
- dhinakaran
Dhinakarank K
Software Engineer, EmSyS ( : +91 821 240
5638
Larsen and Toubro Limited, Mysore Campus ( : +91 821 240 5489
KIADB Industrial Area, Hebbal - Hootagalli Ê : +91 821
2403752
Mysore - 570 018 š :
[email protected]
India ý :
http://www.Lntemsys.com
This mail is classified as
L&T EmSyS Proprietary L&T EmSyS Internal Use
L&T EmSyS Confidential L&T EmSyS General Business
Hi,
> I intend to use the A2DP profile of BlueZ, by playing some
> music over my desktop(Having Broadcom USB bluetooth adaptor) and
> listering it on BT-headset.
>
> System Details:
> Linux Flavour: Fedora Core 4
> Linux Kernel: 2.6.26
> BlueZ version: 4.18
> DBUS version: 1.2.4
> GLIB version: 2.14
> ALSA version: 1.013
>
> HCID:
> When I start bluetooth service, hcid throws error: Unable to
> get on DBUS and continues to run. I proceed further to pair with
> headset, wherein in gives, Can't connect: Input/Output error. But
> surprisingly it can connect with other bluetooth devices like mobile
> phones. Behaviour is alike irrespective of pin-helpers,bluepin or
> bluez-pin.
> Bluetoothd:
> Yes, I know that version 4.xx replaces hcid wiht bluetoothd.
> I edited the /etc/ini.d/bluetooth script to spawn bluetoothd daemon,
> instead of hcid daemon. Even Bleutoothd daemon throws error: Unable
> to get on DBUS and exits.
>
> Im attaching the debug log herewith. Any help in this regard is deeply
> appreciated.
your system is seriously screwed up and old. Why don't you just upgrade
to a more recent Fedora 10. The A2DP support should work out of the box
there using ALSA, GStreamer or PulseAudio.
Regards
Marcel
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users