From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] avrcp start
Date: Tue, 29 Nov 2005 21:37:10 +0100 [thread overview]
Message-ID: <1133296630.23817.5.camel@blade> (raw)
In-Reply-To: <438C8EDE.1010309@xmission.com>
Hi Brad,
> I've started an avrcp receiver in the btsco cvs.
>
> I hope it doesn't seem like a case of extreme laziness to put the sdp
> stuff in sdptool. I suppose I should get serious and put it in my app
> too. Did I write the patch right with regard to protocol names, etc?
>
> Also, is there a separate UUID for AVRCP? I only found AVCTP UUID
> definitions, but it seems like PID in the AVCTP header needs to indicate
> AVRCP specifically.
>
> With the changes above, I got my headset to connect but it seems to put
> in the value "0e11" for the pid in the first AVRCP packet I got out of it.
you actually copied to much from on of the A2DP record handlers. The
specification definces the AVRCP CT service record like this:
Attribute 0x0000 - ServiceRecordHandle
UINT32 0x00010000
Attribute 0x0001 - ServiceClassIDList
Sequence
UUID16 0x110e - RemoteControl
Attribute 0x0004 - ProtocolDescriptorList
Sequence
Sequence
UUID16 0x0100 - L2CAP
UINT16 0x0017
Sequence
UUID16 0x0017 - AVCTP
UINT16 0x0100
Attribute 0x0005 - BrowseGroupList
Sequence
UUID16 0x1002 - PublicBrowseGroup
Attribute 0x0009 - BluetoothProfileDescriptorList
Sequence
Sequence
UUID16 0x110e - RemoteControl
UINT16 0x0100
Attribute 0x0100
String AVRCP CT
Attribute 0x0311
UINT16 0x000f
You need the supported features attribute. The correct PSM and protocol
and profile descriptors. The AVRCP TG looks like this:
Attribute 0x0000 - ServiceRecordHandle
UINT32 0x00010001
Attribute 0x0001 - ServiceClassIDList
Sequence
UUID16 0x110c - RemoteControlTarget
Attribute 0x0004 - ProtocolDescriptorList
Sequence
Sequence
UUID16 0x0100 - L2CAP
UINT16 0x0017
Sequence
UUID16 0x0017 - AVCTP
UINT16 0x0100
Attribute 0x0005 - BrowseGroupList
Sequence
UUID16 0x1002 - PublicBrowseGroup
Attribute 0x0009 - BluetoothProfileDescriptorList
Sequence
Sequence
UUID16 0x110e - RemoteControl
UINT16 0x0100
Attribute 0x0100
String AVRCP TG
Attribute 0x0311
UINT16 0x000f
Functions for both records are in the CVS now.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-11-29 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 17:24 [Bluez-devel] avrcp start Brad Midgley
2005-11-29 20:37 ` Marcel Holtmann [this message]
2005-11-29 22:38 ` Brad Midgley
2005-11-30 2:08 ` Brad Midgley
2005-11-30 3:29 ` Marcel Holtmann
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=1133296630.23817.5.camel@blade \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).