From owner-freebsd-bluetooth@FreeBSD.ORG  Sat Aug 23 15:48:20 2014
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
Delivered-To: freebsd-bluetooth@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C91864D8
 for <freebsd-bluetooth@freebsd.org>; Sat, 23 Aug 2014 15:48:20 +0000 (UTC)
Received: from bein.link (unknown [IPv6:2a02:2770:3:0:21a:4aff:fee6:9061])
 by mx1.freebsd.org (Postfix) with ESMTP id 928903FDD
 for <freebsd-bluetooth@freebsd.org>; Sat, 23 Aug 2014 15:48:20 +0000 (UTC)
Received: from quad.localnet (unknown [172.16.32.6])
 by bein.link (Postfix) with ESMTPSA id 0B886404D0
 for <freebsd-bluetooth@freebsd.org>; Sat, 23 Aug 2014 17:47:57 +0200 (CEST)
From: Maxim V FIlimonov <che@bein.link>
To: freebsd-bluetooth@freebsd.org
Subject: A2DP on FreeBSD 10-RELEASE
Date: Sat, 23 Aug 2014 19:48:09 +0400
Message-ID: <3066592.rAOiKGONB3@quad>
User-Agent: KMail/4.12.5 (FreeBSD/10.0-RELEASE; KDE/4.12.5; amd64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
 <freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth/>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Aug 2014 15:48:20 -0000

Hi, I got a bluetooth dongle and a wireless headset. I managed to pair the 
devices (the headset responds and acts just like it's connected), but don't 
know what to do next. Is A2DP support implemented in 10.0-RELEASE? If not, 
when could it be implemented? Is there a simple workaround to hear at least 
anything from the headset?
-- 
wbr, Maxim Filimonov
che@bein.link