From: Mr Jie Liu <s4048156@student.uq.edu.au>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] problem with hstest
Date: Tue, 18 May 2004 19:33:36 +1000 [thread overview]
Message-ID: <20561a20c28e.20c28e20561a@uq.edu.au> (raw)
I try to play sound through my HBH-35 headset. I am using the hstest program of the bluez package to test the headset profile. But I can't hear anything through the headset. The voice setting is right(0x0060). I can establish rfcomm and soc link with the headset and the AT command seems to work fine because I can hear the RING tone. When I push the button on the headset, the AT command could also be printed out correctly. I use "hstest recor
d sound X:X:X:X:X:X X" to record a file. Then I try to replay it by "hstest play sound X:X:X:X:X:X X". But there is nothing from the headset and the program also has no error message. Has anyone experienced this before? What kind of information should I provide to analyse it?
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-05-18 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 9:33 Mr Jie Liu [this message]
2004-05-18 9:39 ` [Bluez-devel] problem with hstest Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-05-18 10:00 Mr Jie Liu
2004-05-18 10:10 ` Marcel Holtmann
2004-05-20 10:05 ` cuanyu
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=20561a20c28e.20c28e20561a@uq.edu.au \
--to=s4048156@student.uq.edu.au \
--cc=bluez-devel@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