Closed GoogleCodeExporter closed 8 years ago
(Sorry it took so long to get a reply to this, I naively assumed I would get
notified
by default of any bug submitted. I've made sure that's the case now.)
I've seen a couple of comments related to this possible issue, however I have
never
seen it happen on my test device and can't see a reason why Contact Owner would
use
much battery. Basically all it does is get notified when the screen turns off
and
(re)setting the lock screen message at that time. Other than that it doesn't
use CPU
or any other resources. It doesn't even try to keep a wake lock at any time
(preventing the CPU from going to sleep).
You can figure out what is draining your battery by running the "Battery Info"
app
that comes preinstalled on the device. It's not accessible by default, so
you'll have
to get AnyCut first and use it to create a link to the "Battery Info" activity.
It
will show you all kinds of interesting usage statistics: CPU, wireless, wake
locks,
sensors. Let me know if the cause is indeed Contact Owner or not.
And thanks for taking the time to submit this bug.
Original comment by paranoid...@gmail.com
on 4 Jun 2009 at 5:02
Original comment by paranoid...@gmail.com
on 4 Jun 2009 at 5:07
Thanks for the response!
I should have later followed up but it took me a while to figure this one out.
This
was the only application I installed since my battery drained but what I later
found
out is that a simultaneous update to another previously installed app is what
was
draining my battery. I too was confused how this application could drain your
battery but saw nothing else that could have drained it. I now realize it
wasn't
your application.
I think you meant to suggest 'Battery History'. WOW! What a great suggestion.
I
didn't know that existed. I had an AnyCut shortcut to 'Status' for battery
information but this is far more extensive. I will be examining this closely.
Thanks again for the creativity in this application - it is a great workaround
to
editing the lock screen.
I am reinstalling the application now and will follow up if by chance this
application (in conjunction with the update from the other) was draining the
battery
too but I doubt it.
Original comment by davech...@gmail.com
on 4 Jun 2009 at 5:14
Fingers crossed! :o)
Yes, I meant Battery History. It's just that I forgot my phone at home this
morning so
I had to rely on my (otherwise useless) memory.
Original comment by paranoid...@gmail.com
on 4 Jun 2009 at 5:32
Original issue reported on code.google.com by
davech...@gmail.com
on 1 Jun 2009 at 8:02