public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Nick Pelly <npelly@google.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: How to automatically initiate sniff mode
Date: Tue, 17 Feb 2009 03:37:05 +0100	[thread overview]
Message-ID: <1234838225.13496.20.camel@californication> (raw)
In-Reply-To: <35c90d960902161542j7d0826b7qbcbcb914fa706d15@mail.gmail.com>

Hi Nick,

> We have come across a headset (HTC M200) that does not send out a
> sniff mode request when in idle. Our Bluez based stack also does not
> send a sniff mode request, so we sit in a higher power state that
> necessary. (20mA instead of 1mA).
> 
> Some quick research suggests that we would need to send HCI Sniff Mode
> Command (OCF 0x03) to initiate sniff mode, and that this is not yet
> done in the Bluez code base. We do send the HCI Write Default Link
> Policy Settings Command but, as I understand, this is only applied to
> incoming sniff mode requests by the link manager and will not initiate
> an LMP sniff request.
> 
> We compared to two non-bluez mobile stacks and found the other phones
> did automatically initiate an LMP sniff mode request.
> 
> Is there a reason for Bluez not automatically sending HCI Sniff Mode
> Command, or is it just a case of no-one getting around to hitting the
> problem / implementing a fix? Or have I missed something simple?

actually BlueZ has automatically sniff mode since a long-long time ago.
It also would do sniff-subrate in case of Bluetooth 2.1 modules. However
you have to enable it since by default it is off.

Check /sys/class/bluetooth/hci0 for idle_timeout, sniff_max_interval and
sniff_min_interval. Use idle_timeout and the others to control the
interval values.

Regards

Marcel



  reply	other threads:[~2009-02-17  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 23:42 How to automatically initiate sniff mode Nick Pelly
2009-02-17  2:37 ` Marcel Holtmann [this message]
2009-02-17  2:45   ` Nick Pelly

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=1234838225.13496.20.camel@californication \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=npelly@google.com \
    /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