From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: RE: [Bluez-users] Bluetooth Voice Setting
Date: Wed, 07 Dec 2005 12:08:31 +0100 [thread overview]
Message-ID: <1133953711.3752.4.camel@blade> (raw)
In-Reply-To: <HCEOIFALKKLBLJPENPNOOEGECAAA.khaled@ipbill.com>
Hi Khaled,
> > > Can someone tell me how to set the bluetooth voice settings
> > when using sco
> > > and what to set it to?
> > > My hcidump shows voice setting as (0x03|0x0025) - what does
> > this mean? Also,
> > > the hcidump shows that a connection is created for DM* and DH*
> > packet types:
> > > for sco, should this not be HV* packet types?
> >
> > you don't need to worry about it. The packet types and the voice setting
> > are not related (from the HCI viewpoint). If you wanna know details
> > about it, look at the HCI part of the Bluetooth specification. The value
> > is a bitmask and it is explained in detail there.
> >
>
> I was curious because I am not getting any sound through my machine
> (configured as a headset - 0x200404 device class).
> Also there are no service classes defined when I do hciconfig -a (as shown
> below).
this is now the class of device. You are mixing things up here.
> Although a headset icon appears on my 6310i and I get no sound at the actual
> mobile phone (because the headset is connected), I still cannot hear or say
> anything that can be heard from my computer.
> Therefore, I am trying to study the hcidump output but its almost impossible
> to interpret.
No it is not. Use "hcidump -X -V" as stated almost everywhere in the
mailing list archives.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-12-07 11:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 10:17 [Bluez-users] Bluetooth Voice Setting Khaled
2005-12-07 10:48 ` Marcel Holtmann
2005-12-07 10:54 ` Khaled
2005-12-07 11:08 ` Marcel Holtmann [this message]
2005-12-07 11:14 ` Khaled
2005-12-07 11:36 ` Marcel Holtmann
2005-12-07 11:38 ` Khaled
2005-12-07 11:52 ` Marcel Holtmann
2005-12-07 11:58 ` Khaled
2005-12-07 12:09 ` Marcel Holtmann
2005-12-07 12:18 ` Khaled
2005-12-07 12:26 ` Marcel Holtmann
2005-12-07 12:24 ` Khaled
2005-12-07 14:48 ` Steven Singer
2005-12-07 15:00 ` Khaled
2005-12-07 16:06 ` Steven Singer
2005-12-07 16:26 ` Marcel Holtmann
2005-12-07 16:39 ` Khaled
2005-12-07 16:27 ` Khaled
2005-12-07 15:03 ` Brad Midgley
2005-12-07 15:06 ` Khaled
2005-12-07 15:30 ` Khaled
2005-12-07 16:51 ` Brad Midgley
2005-12-08 11:53 ` Khaled
2005-12-08 14:55 ` Brad Midgley
2005-12-08 14:59 ` Khaled
2005-12-08 15:18 ` Brad Midgley
2005-12-08 15:42 ` Khaled
2005-12-08 14:56 ` Khaled
2005-12-07 12:06 ` [Bluez-users] Bluez-users/Bluez-devel FAQ [Was: Bluetooth Voice Setting] Steven Singer
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=1133953711.3752.4.camel@blade \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).