ext Matthew Garrett wrote:
On Fri, May 28, 2010 at 10:37:13AM +0100, Alan Cox wrote:
The other vendors appear to be managing nicely without magic blockers. I
conjecture therefore there are other solutions.
Actually, no. A badly behaved application will kill the N900's battery
life. Nobody else has "managed nicely" - they've just made life harder
for application developers and users, which may have something to do
with the relative levels of market adoption of Maemo and Android. I'm
not aware of any form of resource management framework in MeeGo either,
so as far as I know it'll have exactly the same problem.
It's true that a braindead app can kill the battery.
However we provide a version of powertop that is tailored to the N900,
there is a nokia energy profiler meant to give graphical representation
of the battery current, there is htop available and you can even get the
processor activity visualized on the leftmost and rightmost keyboard
backlight LEDS, when in RD mode and with screen blanked.
I would advice you to not start debating on company strategies, this is
not the right place.
Otherwise I'll have to ask what's the expected threshold of devices sold
with broken sw design to get automatic admission into the mainline
kernel source tree.
But this is not the direction we want to take.
Notice also that we _do_ have a store and official repository where apps
are monitored for sanity, also with feedback from users and their help
to promote new apps to trusted state.
Former Maemo 6, now MeeGo do introduce resource management from security
POV, but that will also have the side effect of discriminating between
signers.
igor
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
