> Marcelo wrote: >> You can force as someone else suggested, but in this particular case >> the operation is in fact dangerous, so it's not a good idea... think >> for example about the situation where someone figures out that >> Freerunners running Android have this "property", it would be easy to >> write an application to fry hardware under certain conditions :-(
Yes I have thought about that. One one hand it is helpful to have it exposed so that people can write power monitor applications. (there is a lot that could be done for it to be easier/more safe to use...) But on the other and there are serious security issues, especially with such a function (after all it is even called "_dangerous" !). What is needed I think is to have access to this settings protected via an Android permission. I do not know well existing permissions, but maybe here we should define a new one. Not sure if it can be a generic Android permission or specific for Openmoko, but anyway we could have its name reflect the risk, just as for the sys property (ie permission POWER_SETTINGS_DANGEROUS or something like that...) Wouldn't that be consistent with security model in android ? Yes, still there might be ways, when granting this right to applications to do some badness to hardware... but hey, at least you were warned, and after all with a dumb phone designed to draw up to 1A anyway, it can be dangerous too if plugged in the wrong charger... _______________________________________________ android-freerunner mailing list [email protected] http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
