From: Marcel Holtmann <marcel@holtmann.org>
To: Bernard Mentink <Bernard.Mentink@trimble.co.nz>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Keeping keyboards alive
Date: Mon, 15 Mar 2004 12:29:24 +0100 [thread overview]
Message-ID: <1079350163.3405.6.camel@pegasus> (raw)
In-Reply-To: <8285CB7241FCFC4BB721A6F953F9B35EFB30EB@nzc-ap-xch-01.ap.trimblecorp.net>
Hi Bernard,
> I have been using my Apple Bluetooth keyboard sucessfully for some weeks now with the stack and am very happy with it.
>
> My only niggle is the lack of support for regular polling of the keyboard to keep it awake.
> (The keyboard goes into deep sleep after about 10mins of inactivity, I then have to cycle the power to reconnect)
there is a similar problem with the Microsoft devices, but I thought I
fixed it. Keeping the device connected is bad for battery. For example
my Apple mouse never disconnects. My only missing Bluetooth HID device
is the Apple keyboard and so I think that I can't tell you anything
useful.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-03-15 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 20:07 [Bluez-devel] Keeping keyboards alive Bernard Mentink
2004-03-15 11:29 ` Marcel Holtmann [this message]
[not found] <8285CB7241FCFC4BB721A6F953F9B35E0F38D8@nzc-ap-xch-01.ap.trimblecorp.net>
2004-03-15 19:37 ` Marcel Holtmann
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=1079350163.3405.6.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Bernard.Mentink@trimble.co.nz \
--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