On 6/23/2010 4:33 AM, Gary Birkett wrote:
On T
correct. there are, by design, no special APIs in MeeGo for applications to
be power friendly.
It must be sufficient for an application to be well behaving [*] for it to
be power friendly in MeeGo.
would it be wise to document all the best practices in one place though?
sure makes sense
also for applications to be well behaved, they should know something
about their environment
to that end should know where to look for the charging status for instance
applications should ABSOLUTELY NOT care about charging status. That
thinking is the first fundamental
mistake many people make :-)
1. Apps should in general not care about AC/DC. Really. Many people
think "only on battery do I need to be power efficient".
That's just not true for many reasons (ask any datacenter operator)
2. Apps should not do "if the battery is less than 20% I should be power
efficient" kind of thing. The last 20% of battery is not where it matters
to save power... it's the first 80%! Lets say that if you did nothing,
you would have an hour left at 20%, and if you did the special thing,
you'd have two hours left.
You'd say, great, I gave the user an extra hour.
But... if you had done the right thing from the start, for the first
80%, you'd have given the user 5 hours of extra battery!
Or in other words... the amount of savings in the last 20% is not going
to be very much, because there's just not much left.... you're going to
do a %age improvement over an already small number
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
