On Mon, May 17, 2010 at 11:39 AM, Felipe Balbi <me@xxxxxxxxxxxxxxx> wrote: > Hi, > > On Mon, May 17, 2010 at 11:26:59AM -0700, Brian Swetland wrote: >> We (Google) would like to allow completely open app distribution with >> minimal hurdles, and avoid the walled garden approach. Toward this >> goal we're not even requiring the use of a central app store for >> distribution. > > I understand that, but still we should be telling developers what > they're doing wrong so that they can improve themselves as professionals > and still make the final device better. > We currently do track power usage per-application which is displayed in the phone UI. (Settings -> About Phone -> Battery Usage). We also provide several (although not perfect) command line utilities for developers to see their power impact system. We are constantly working on ways to improve tracking and make such power data more accessible to developers so they can see how their applications are impacting battery life. >> Obviously, given the ability to run *any* app, users will run into bad >> (or perhaps just less-than-optimal-powerwise) apps. Being able to >> provide the best possible battery life (in spite of >> sometimes-nonoptimal userspace apps) and simultaneously informing >> users about which apps are better/worse for their battery life is a >> goal here. > > I see. Just hope MeeGo doesn't venture on the same waters :-s > >> For a large majority of apps, running in the background while the >> device is asleep (screen off) is not essential, they don't request the >> "keep device awake" permission, never hold a wakelock, etc. Those >> that do need to do this have the permission, may hold suspend >> blockers, and are accounted for. > > but can anyone write an app that holds a suspend_blocker ?? If so, then > your goal is already broken, right ? I mean, if anyone can keep a > suspend_blocker held forever, you'll never ever sleep, right ? While > with runtime, if you keep the keypad open, only the keypad and the paths > directly related to it (probably the i2c controller and the power domain > where the i2c controller sits) will be kept alive, no ? > Any app can grab a suspend blocker, and the stats are logged, and if you're app is abusing wakelocks and CPU resource it will show up in the "Battery Use" panel. -- Mike >> Unrelated to apps, the ability to say "please enter suspend as soon as >> there's no more work (kernel or userspace) preventing it", in a >> simple, non-racy way is useful. > > I just tend to agree with Kevin on questioning how different how > different this actually is from runtime_pm. I guess I would need to dig > through some documentation in order to understand but it seems really > similar. > > -- > balbi > -- > 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 > -- 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
