public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Headset reconnection
Date: Tue, 16 Aug 2005 12:20:54 -0600	[thread overview]
Message-ID: <43022E86.7080909@xmission.com> (raw)
In-Reply-To: <1124215347.21719.31.camel@pc7.dolda2000.com>

Fredrik,

You can get pdfs from bluetooth.org. The relevant ones are 6_headset.pdf 
and "HFP Spec Version 1_0.pdf"

Most headsets attempt to make the rfcomm connection to the last-used 
handset (or only handset if they only keep one pairing) on power-up. The 
stereo headsets tend to wait until the first click of the answer button.

I don't think we are doing the device class or sdp stuff to even make 
the headset aware that it can make this connection. On top of that, we 
need to be listening for connections.

a2recv listens for connections, but it may not be the clearest example. 
the way a2recv gets run is like this:

  # add a2dp to the class bitmap (I don't know which bit(s) it is)
  hciconfig hci0 class 0x200404
  # advertise through sdp
  sdptool add A2SNK
  ./a2recv

The way sdptool gets invoked there, A2SNK is advertised on the standard 
channel. You could also add --channel to change that.

Brad

Fredrik Tolf wrote:
> Hi!
> 
> I'm wondering about how BT headsets and mobile phones usually work
> together, in hope of implementing automatic connection in btsco.
> 
> Normally, it seems that a mobile phone and a headset manage to keep
> their link, even across "reboots" and other disconnections. Does a phone
> periodically scan for headsets that it knows, or does the headset
> somehow try to automatically reconnect to the phone under certain
> circumstances, or is it something completely different?
> 
> Can anyone tell me where to find info on this?
> 
> Fredrik Tolf
> 
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-08-16 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 18:02 [Bluez-devel] Headset reconnection Fredrik Tolf
2005-08-16 18:20 ` Brad Midgley [this message]
2005-08-16 19:50   ` [Bluez-devel] No sound in Plantronics M2500 Nelson Murilo
2005-08-22 23:52   ` [Bluez-devel] Headset reconnection Fredrik Tolf

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=43022E86.7080909@xmission.com \
    --to=bmidgley@xmission.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