All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] emporia/mega-Headset and btsco problems
Date: Sat, 02 Jul 2005 15:26:32 -0600	[thread overview]
Message-ID: <42C70688.9050407@xmission.com> (raw)
In-Reply-To: <20050702172632.3d3b3dcd.andy.boehler@gmx.at>

Andreas,

This is an unintended consequence of a change a few months ago to make 
the sco connection fire up only on demand.

One thing we have needed to do for a long time that would help this is 
to rebuild the rfcomm connection when it goes bad (or even make it 
happen on demand). With other headsets, the rfcomm connection only goes 
bad if the headset goes out of range. Holding the rfcomm connection open 
isn't great anyway because I think it prevents a laptop from suspending.

As far as I can tell, phones hold the rfcomm connection open and only 
fire up sco on demand. I wonder if they have to accommodate this too...

Brad

Andreas Böhler wrote:
> Hi!
> 
> I recently purchased a Mega BT-Headset and fetched, compiled and installed btsco from bluetooth-alsa.sf.net. 
> Pairing works fine and sending and receiving audio from and to the headset also works - for a while. 
> My problem is, that the headset disconnects after a very short time if no audio is transmitted!
> I think that this is the same problem as with the Jabra BT-110: "Jabra BT110 (will turn off very soon after the last audio packets have been transmitted and btsco will quit with "RFCOMM channel lost")" -> quote from bluetooth-alsa.sf.net main page.
> I'm wondering if someone has solved this problem? Isn't it possible that btsco simply reconnects to the headset? Or that it transmits empty or quiet audio-frames just to keep the connection alive?
> I tried what is done using Windows: When you connect the headset, it rings as if the phone was ringing and you have to pick it up (headset-button), then the connection is established. I wonder if this would also work under Linux? Or is this the implementation of the Hands-Free profile and not the Headset-Profile?
> 
> Any help is appreciated, 
> 
> thanks,
> 
> Andreas Böhler
> 
> PS: I'm using Linux 2.6.12, custom compilation, D-Link DBT-120 (or Digitus DN-3008), SoL-Linux 18.00, BlueZ-stack and Mega BTHS-6023-F (manufacturer is Emporia, www.emporia.at)
> 


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-07-02 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02 15:26 [Bluez-devel] emporia/mega-Headset and btsco problems Andreas Böhler
2005-07-02 21:26 ` Brad Midgley [this message]
2005-07-02 22:47   ` Andreas Böhler
2005-07-03  8:35     ` Brad Midgley
2005-07-03 16:02       ` Andreas Böhler
2005-07-04  3:29         ` 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=42C70688.9050407@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.