From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] itech "radio" headset shakedown
Date: Sat, 6 Oct 2007 11:16:34 -0600 [thread overview]
Message-ID: <d89ddf300710061016k23fdca8bh403c50fa6d287f8c@mail.gmail.com> (raw)
Hey
FYI, I have an itech radio headset now. Has FM, HFP/HSP/A2DP/AVRCP but
doesn't quite have it all:
bt2.0 but no EDR
no mp3 decoder
the avrcp profile has a couple of new ops:
Fast forward (opcode is 0xc9)
Rewind (opcode is 0xc8)
if you tap the play button, the message it sends alternates between
play and pause, unlike the previous r35 model which always sent play
for a tap and pause for tap-and-hold.
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2007-10-06 17:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d89ddf300710061016k23fdca8bh403c50fa6d287f8c@mail.gmail.com \
--to=bmidgley@gmail.com \
--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