Closed GoogleCodeExporter closed 9 years ago
I've noticed this too. I think it's because PT is using less memory and thus
has a
better shot at staying open longer while in the background.
Original comment by netbym...@gmail.com
on 25 Jan 2009 at 9:33
Battery usage is one of those things that's damn near impossible to nail down,
and I
can't think of much I would have done for .61 that would have changed it.
The only thing I can think of is some manual Garbage Collection I implemented
as a
quick-fix for reducing memory usage. I've removed that in the latest dev build.
If you can try and compare the latest dev build (http://is.gd/1do7) against
.62, let
me know if it helps any with the battery life.
Original comment by jakestevenson
on 26 Jan 2009 at 3:02
Yesterday @ this time I got my battery alert after 5 hours of normal use. Today
I'm
still @ 70% battery with 0.60.
Installed dev build today at lunch and my phone was dead before I got home. It
wasn't the most fair test, so I'm going to give it another shot tomorrow.
The battery drain is really significant to me. I'm surprised more people have
not
been commenting on it. I hope it's not something that's just isolated to my
phone.
That would suck.
Normally battery life for my crappy Smartphone (Verizon SMT5800) is about 9 - 10
hours for normal usage (thanks largely in part to the data). I'm lucky to get 5
hours running anything after 0.60.
I'll report my findings tomorrow with another day using the dev build.
Original comment by craig.la...@gmail.com
on 28 Jan 2009 at 10:14
I really haven't seen more of a drain on my mogul -- it's off the charger from
7AM to
7PM.
Are you getting a lot of communication errors? I look forward to hearing
whether the
dev build was any better.
Original comment by jakestevenson
on 29 Jan 2009 at 1:45
Almost four hours of use and I got my battery alert using the dev build. I
have been
seeing quite a few communications messages pop up, but 0.60 seems fine.
Dunno. Guess I'll stick with 0.60 for now and hope that something gets
revealed in
the future.
Original comment by craig.la...@gmail.com
on 29 Jan 2009 at 3:45
[deleted comment]
[deleted comment]
Are you changing any settings from the default? Have you enabled any
notifications?
Original comment by jakestevenson
on 29 Jan 2009 at 4:29
Ok, here are my settings for the Smartphone:
Manage Accounts
craig_lambert (just the one twitter account)
Avatar Settings
Show Avatars Selected
High-Quality Avatars Selected
UI Settings
Max Length: 100
Show Times Selected
Clickable Links Selected
Merge all Timelines Selected
Theme: Highlight Blue
Other Settings
Automatically Check New Version Selected
Automatic Update: 10 Minutes
Configure Notifications (untouched and blank)
That should do it. Let me know if I can do anything else for ya.
Original comment by craig.la...@gmail.com
on 29 Jan 2009 at 5:05
[deleted comment]
The merge timelines may adversely affect battery life. It takes a good bit of
computation to mix all three sets of items together!
Do you have any notifications enabled?
Original comment by jakestevenson
on 29 Jan 2009 at 5:18
Nah, no notifications. I did, but it just would go off every 10 minutes
anyway. :)
I still like the feature.
Tomorrow I'll run the dev build again without the timelines merged and report
back to
you.
Original comment by craig.la...@gmail.com
on 29 Jan 2009 at 5:51
Doesn't having 2 screen names invoke the same merging routine that the
friends/messages timeline does? If it does I've had 2 accounts set up in PT for
a
while without a battery life problem. Now it seems to be eating mine up. To
test this
I only had PT open during lunch today. I came home with a lot more battery than
usual.
Original comment by netbym...@gmail.com
on 30 Jan 2009 at 12:38
I think I finally found the problem. A bug in the popup-notification
("Updating..."
and "Communication Error") caused the screen to constantly redraw itself several
times a second. I'm really surprised this did NOT affect my battery
noticeably, it
definately should.
I have fixed it in the dev build (http://is.gd/1do7) as of 10:00 central time.
You
may want to download it and try it to be sure it helps for you.
Original comment by jakestevenson
on 30 Jan 2009 at 3:56
Definitely a lot better. Thanks so much. I got about 7 hours before the
battery
alert came up. I thought it was completely charged, but there is a chance it
wasn't.
Regardless, I saw a noticeable improvement. I'd swear I could just watch the
battery
drain from it before. :)
Awesome job. I love this ap!
Original comment by craig.la...@gmail.com
on 30 Jan 2009 at 11:29
Fixed in v.63
Original comment by jakestevenson
on 31 Jan 2009 at 7:31
Original issue reported on code.google.com by
craig.la...@gmail.com
on 25 Jan 2009 at 7:25