From: "Frédéric DALLEAU" <frederic.dalleau@palmsource.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP Profile Certification
Date: Wed, 21 Jun 2006 18:50:04 +0200 [thread overview]
Message-ID: <449978BC.8020202@palmsource.com> (raw)
In-Reply-To: <44965944.6090908@palmsource.com>
Hi brad,
I've been looking at what you did in a2play.
>>I put code in a2play so it will listen on the control link for
>>suspend/resume from a2dp headset (*if* you use -p for pthreads). This
>>should be a decent model for getting it into the alsa plugin if you want
>>to look at that.
>> =
>>
>I will have a look by the end of the week.
> =
>
I used -p options but I have some problems :
When reading /dev/rtc, I always read 0x8C0 and I only get 50 read per =
sec. If you strip the low byte, it's 8 ticks but the sbc data is 23 ms =
long (190 ticks). So decreasing the tick count to 0 nefore sending data =
takes nearly one second and I have intermittent sound. I fixed it by =
commenting out the "while(ticks <=3D 0)" line, I also tried smaller rtc =
frequency without success. Why not use gettimeofday?
>>This is how we find out a combo headset is taking a voice call.
>>
> noticed that my headset stopped streaming when pressing the main =
>button and didn't get back playing after pressing the button again.
>Is that what you mean?
> =
>
I don't receive control commands when doing this. What model do you use?
>>We're still missing something here... we don't listen for new control
>>connections from the set. You could look at a2recv.c for code that will
>>listen for new connections. This will be more complicated since you may
>>want to use dbus to start up the media player in response.
>> =
>>
>I was wondering how to generate such connections? Simply switch on the =
>headset? Any ideas?
> =
>
Last but not least, I receive the frame sent by the headset but it is a =
2 byte "0x00 0x01". Is does not look like a stream_cmd. And only one of =
my heasets sends data.
plus the weather is bad, sad day...
Fr=E9d=E9ric.
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-21 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 15:19 [Bluez-devel] A2DP Profile Certification Frédéric DALLEAU
2006-05-30 15:32 ` Brad Midgley
2006-05-30 15:50 ` Frédéric DALLEAU
2006-05-30 16:30 ` Brad Midgley
2006-05-30 16:33 ` Marcel Holtmann
2006-06-19 5:33 ` Brad Midgley
2006-06-19 7:59 ` Frédéric DALLEAU
2006-06-19 14:49 ` Brad Midgley
2006-06-19 15:20 ` Frédéric DALLEAU
2006-06-21 16:50 ` Frédéric DALLEAU [this message]
2006-06-21 17:24 ` Brad Midgley
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=449978BC.8020202@palmsource.com \
--to=frederic.dalleau@palmsource.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;
as well as URLs for NNTP newsgroup(s).