From: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
To: Bastien Nocera <hadess-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org>
Cc: linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-input <linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Apple Bluetooth devices: Battery level?
Date: Sun, 07 Jun 2009 17:52:13 +0200 [thread overview]
Message-ID: <1244389933.23850.104.camel@localhost.localdomain> (raw)
In-Reply-To: <1244384236.30768.5690.camel-MYKcRh6MmTE/Ra3EetS/fF6hYfS7NtTn@public.gmane.org>
Hi Bastien,
> I just got an Apple Bluetooth Mighty Mouse, and was wondering whether
> anyone had information on how to get the battery level from the device
> (the keyboard apparently also allows that):
> http://support.apple.com/kb/TA27118?viewlocale=en_US
>
> Anyone with an idea? An unparsed HID event? Does it need "poking"?
I think that Apple ones used an actually HID HUT conform descriptor for
that. I did reverser engineered that a long time ago, but then never got
around to do anything with it. Can't find my notes right now. Just run
hcidump and eventually you will see the report.
Regards
Marcel
next prev parent reply other threads:[~2009-06-07 15:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 14:17 Apple Bluetooth devices: Battery level? Bastien Nocera
[not found] ` <1244384236.30768.5690.camel-MYKcRh6MmTE/Ra3EetS/fF6hYfS7NtTn@public.gmane.org>
2009-06-07 15:52 ` Marcel Holtmann [this message]
2009-06-08 13:33 ` Jiri Kosina
2009-06-09 23:22 ` Bastien Nocera
[not found] ` <1244589738.5973.1954.camel-MYKcRh6MmTE/Ra3EetS/fF6hYfS7NtTn@public.gmane.org>
2009-06-10 7:03 ` Marcel Holtmann
2009-06-12 13:25 ` Jiri Kosina
[not found] ` <alpine.LNX.2.00.0906121521490.7457-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2009-06-12 13:27 ` [PATCH 2/2] HID: use debugfs for events/reports dumping Jiri Kosina
2009-06-12 13:27 ` [PATCH 1/2] HID: use debugfs for report dumping descriptor Jiri Kosina
2009-06-10 7:14 ` Apple Bluetooth devices: Battery level? Dmitriy Geels
[not found] ` <78f5d6bf0906100014r5b7f5c14p4544ef13442c8f0b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-10 7:24 ` Marcel Holtmann
2009-06-10 8:25 ` Bastien Nocera
2009-06-10 8:25 ` Jiri Kosina
[not found] ` <alpine.LNX.2.00.0906101023460.7457-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2009-06-10 14:25 ` Bastien Nocera
[not found] ` <alpine.LRH.2.00.0906081530330.31685-1ReQVI26iDCaZKY3DrU6dA@public.gmane.org>
2009-06-10 14:06 ` Bastien Nocera
[not found] ` <1244642769.2690.51.camel-MYKcRh6MmTE/Ra3EetS/fF6hYfS7NtTn@public.gmane.org>
2009-06-10 18:19 ` Iain Hibbert
2009-06-12 13:31 ` Jiri Kosina
[not found] ` <alpine.LNX.2.00.0906121529210.7457-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2009-06-13 13:16 ` Iain Hibbert
[not found] ` <1244898975.477818.1961.nullmailer-miDnOI7kXJ/y0YX2dClxIw@public.gmane.org>
2009-06-16 9:59 ` Jiri Kosina
2009-06-16 13:37 ` Marcel Holtmann
2010-02-12 15:41 ` Bastien Nocera
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=1244389933.23850.104.camel@localhost.localdomain \
--to=marcel-kz+m5ild9qbg9huczpvpmw@public.gmane.org \
--cc=hadess-0MeiytkfxGOsTnJN9+BGXg@public.gmane.org \
--cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).