All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugene <it.had.even@gmail.com>
To: gunnar_thielebein@gmx.net,
	BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] audio bluetooth connectivity in gutsy
Date: Sun, 20 Jan 2008 13:13:46 +1000	[thread overview]
Message-ID: <4792BC6A.6000708@gmail.com> (raw)
In-Reply-To: <47928635.2030400@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

Gunnar Thielebein writes:
> Hi group,
>
> I am trying to connect my headset in gutsy with default kernel 
> 2.6.22-14-generic. I tried all four(?) possible solutions: old sco way, 
> plugz, bluetooth-alsa (at least the package in gutsy) and bluez-audio 
> which all ends finally with a hardlock of my system when the connection
> was established with headset.
>
> Authentication and sdp browsing works fine at least in kde.
>
> I tested sound play with smplayer,mplayer,aplay,play.
>
> I also tested with the unstable packages from sid libbluez, bluez- 
> bluez-audio, gstreamer-plugins
>
> Could you tell if I need a more current kernel version than 22?
> Or is it something with my hardware?
>
> my hardware spec:
>
> Headset: HBH-PV700
> ---
> Dongle: Bus 001 Device 003: ID 0f4d:1000 Microtune, Inc. Bluetooth Dongle
> ---
> arch: amd64 - 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 
> x86_64 GNU/Linux
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>   
My BT stereo headset works well in Ubuntu Gutsy:
Linux gr11n 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 
GNU/Linux
I use bluez version 3.24 compiled from sources. Audacious also works 
without troubles.
You should describe your problem with more details (logs and 
configuration files), to understand it clearly.

Regards,
Eugene

[-- Attachment #2: it_had_even.vcf --]
[-- Type: text/x-vcard, Size: 55 bytes --]

begin:vcard
fn:Eugene
n:;Eugene
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #4: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-01-20  3:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-19 23:22 [Bluez-users] audio bluetooth connectivity in gutsy Gunnar Thielebein
2008-01-20  3:13 ` Eugene [this message]
2008-01-20  4:41 ` Brad Midgley
2008-01-20 12:54   ` Christophe-Marie Duquesne
2008-01-20 13:04   ` Gunnar Thielebein
2008-01-20 14:39     ` Brad Midgley
2008-01-21 13:50       ` Benito Torres
2008-01-21 18:19         ` Brad Midgley
2008-01-22  5:16 ` Johan Brannlund

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=4792BC6A.6000708@gmail.com \
    --to=it.had.even@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=gunnar_thielebein@gmx.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 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.