You are reading a single comment by @Velocio and its replies.
Click here to read the full conversation.
London Fixed Gear and Single-Speed is a community of predominantly fixed gear and single-speed cyclists in and around London, UK.
This site is supported almost exclusively by donations. Please consider donating a small amount regularly.
@Velocio
Battery technology isn't increasing at the same rate that CPU, GPU and screens are.
I firmly think that increasing capacity isn't an answer that works in the long-term. That hardware designers need to think holistically about power use and main board layout and features, such that the battery life is balanced along with features and speed. I know these are considerations already, but the importance of them is secondary to features and speed.
Android itself needs to be more power efficient. For a good start it could move to the very latest Linux kernel (ICS is on 3.0 and the latest is 3.4 which has had some major improvements in power management and efficiency).
Then I believe that app designers should be constrained. I believe that the developers should be given a sandbox that is memory constrained and power constrained. When they exceed the constraints their app should be killed. That sounds excessive, but if it were there from day 1 every app would have conformed by necessity. Today developers would find it hard to fit into any constraints of an explicit sandbox purely because they've been sloppy and wasteful with CPU cycles, RAM use, screen rendering, etc. All of which use power.
Bigger batteries only take us so far. Android needs to go back to basics if it's going to get faster, more beautiful and more functionally powerful over the coming years.