Closed GoogleCodeExporter closed 8 years ago
I'm not able to replicate this. The app does not do any kind of constant
polling.
Can you try leaving the app in the foreground, wait 10 minutes then go to Home
screen > settings > battery use. See if it is Keepassdroid eating up your
battery?
Original comment by bpel...@gmail.com
on 15 Jan 2011 at 4:36
Unfortunately it is not reproducible at will. It happened to me only twice and
in both cases I had the application open. Since I use keepassdroid so rarely I
was able to correlate the battery drainage to the app. I remember though that
when I checked for the app that killed my battery the battery use did not show
the name keepassdroid but if I remember correctly it showed a 3 letter name and
1 digit. I really cannot recall the name. That app showed 19% battery usage.
Now that I am thinking about it, is it possible there is an interaction problem
between KPD and DropBox? I keep my password file on DropBox so they way I use
it is that I first start DropBox and then click on the password file in order
to open it with KPD.
Original comment by the1avi
on 24 Jan 2011 at 3:16
I was never able to reproduce this.
Original comment by bpel...@gmail.com
on 25 Jun 2011 at 4:58
I am having the same battery draining issue. I am using the latest version of
the app on Galaxy Nexus.
Original comment by husainsfabbas
on 7 Jul 2012 at 6:15
I could never reproduce this. In 1.9.17, even the briefly running service that
KeePassDroid uses has been removed.
It should be impossible now for the app to wake up the phone from sleep.
Original comment by bpel...@gmail.com
on 13 Sep 2012 at 3:48
Same problem with the latest 1.9.18.3 installed today. Drained the battery in
about thee hours. GSam records show Keepass used 22% of the power during that
time (although it was NOT running in the foreground and the phone was in
standby with the screen off.)
Original comment by rjl...@gmail.com
on 24 Sep 2012 at 9:08
Twice in the past couple of months: Keepass 1.9.18.3 drained my battery in a
matter of hours while it whas not even been started and the phone was on
standby. Definitely an issue there.
Original comment by rjl...@gmail.com
on 3 Dec 2012 at 4:24
Original issue reported on code.google.com by
the1avi
on 15 Jan 2011 at 12:54