public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Iain Hibbert <plunky@rya-online.net>
To: Julius Schwartzenberg <julius@zgod.cjb.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Logitech Bluetooth mouse batteries drain quickly
Date: Thu, 5 Nov 2009 19:43:54 +0000 (GMT)	[thread overview]
Message-ID: <1257450234.926723.29928.nullmailer@galant.ukfsn.org> (raw)
In-Reply-To: <4AF2B5EB.40202@zgod.cjb.net>

On Thu, 5 Nov 2009, Julius Schwartzenberg wrote:

> Yes, it's indeed not days, but months. Here is the output from hcitool:
> Link policy settings: RSWITCH HOLD SNIFF PARK
>
> So this looks good I guess?

guess so

> When I look at the info, I get this:
> Requesting information ...
>         BD Address:  00:07:61:DF:0D:C7
>         Device Name: Bluetooth Laser Travel Mouse
>         LMP Version: 2.0 (0x3) LMP Subversion: 0x229
>         Manufacturer: Broadcom Corporation (15)
>         Features: 0xbc 0x02 0x04 0x38 0x08 0x00 0x00 0x00
>                 <encryption> <slot offset> <timing accuracy> <role switch>
>                 <sniff mode> <RSSI> <power control> <enhanced iscan>
>                 <interlaced iscan> <interlaced pscan> <AFH cap. slave>
>
> Could the problem be related to the "power control" feature which may not be
> fully used right now?

No, that relates to Link Manager Protocol which is carried out entirely
within the controller and I don't think there is any way for the host to
influence any decisions regarding that..

My suggestion is to use rechargeables. They will likely last longer than
alkalines, and I normally have spares already charged (use AA for bicycle
lights) so it never really bothered me to have a flat..

iain



      reply	other threads:[~2009-11-05 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 23:47 Logitech Bluetooth mouse batteries drain quickly Julius Schwartzenberg
2009-11-03  9:06 ` Iain Hibbert
2009-11-05 11:24   ` Julius Schwartzenberg
2009-11-05 19:43     ` Iain Hibbert [this message]

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=1257450234.926723.29928.nullmailer@galant.ukfsn.org \
    --to=plunky@rya-online.net \
    --cc=julius@zgod.cjb.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /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