From: Veit Guna <veit.guna@gmx.de>
To: linux-bluetooth@vger.kernel.org
Subject: PS3 remote battery drain
Date: Sun, 8 Nov 2015 12:51:21 +0100 [thread overview]
Message-ID: <563F3739.7030405@gmx.de> (raw)
Hi.
I'm currently using the latest OSMC media center (successor of raspbmc)
on the raspberry pi 2.
It uses the bluez packages (5.12 AFAIR) for handling the bluetooth
connections.
Connecting and using the ps3 remote (1st gen) works quite ok with that.
The problem I have is, that the remote doesn't seem to go to standby and
batteries drain very quickly (2-3 weeks).
Before OSMC, I used raspbmc. It had the same problems initially. But a
user named "kitlaan" applied patches
to the original bluez packages to get standby working. After replacing
the original bluez packages with the
patched ones, standby worked and batteries lasted at least 6 months.
One could easily recognize the standby when hitting a button on the
remote. It lagged a second before the button press
went through to kodi. After it had woken up, pressing a button worked
instantly - without a delay.
Back then, the patch used the 4.98 version of bluez. Now I can see that
the latest official bluez version is 5.36.
Now I'm wondering, whether the patches have made it somehow into the
official bluez version.
Testing with 5.12 showed, that standby didn't work as expected. Also
when using a IdleTimeout of 1 minute within
the input.conf.
Basically one can get it to work with that (there are the patches
mentioned):
https://www.mythtv.org/wiki/Sony_PS3_BD_Remote
Does anybody have a clue whether the patches - or some parts of them -
have made it into bluez?
Thanks
Veit
next reply other threads:[~2015-11-08 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 11:51 Veit Guna [this message]
2015-11-09 12:11 ` PS3 remote battery drain Luiz Augusto von Dentz
2015-11-09 12:21 ` 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=563F3739.7030405@gmx.de \
--to=veit.guna@gmx.de \
--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 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.