2011-07-14

Listen Up Android Team

OK, Google Android team, listen and listen good.  I love my Droid-X, really, I do, but I've just gotta get this off my chest.  I just lost about the thousandth opportunity to take a spontaneous picture on my phone, all because of you.  The camera circuitry is fine, the 1GHz CPU is adequate; it's not Motorola's fault, it's yours.

The pictures are lost because it takes so very long to stop everything and pull up the Camera App.  When I press and hold down that camera button, I want a hardware interrupt to surge through the kernel and have a kernel module (not user-space) to kill/suspend my current process and renice every other process on that phone to 20, and pump up the Camera App process priority to -20. See, because when a photo opportunity presents itself, I don't care if somebody just tweeted the cutest picture of their cat, I just want to take the picture before the opportunity is over.  And it's always over by the time the camera is ready on an Android phone.

For you non-Linux heads, in UNIX/Linux, priorities range from 20 to -20, where 20 is the lowest priority and -20 is the highest.

I've heard it from numerous users both personally (our company uses Android phones) and on the 'Net.  Even Microsoft has poked fun at this problem in their Windows Phone 7 commercial; you know, the one where the guys are sky-diving.

Related to this is the fact that we, the users, need control of the daemons/services running in the back ground.  No, not just the baby game of letting me kill services, we need to be able to control what services are allowed to start-up.  Otherwise, they just re-spawn all over again, eating our resources and causing latencies.  And if the Carriers like Verizon, AT&T, or Sprint try to stop it, call them out in public by name and let the consumers make their voices heard.

There.  It's off my chest.  I feel a little better.