Most of us have to pay attention to battery life these days. And as a dumb end user there is only so much I can do to regulate battery life. Turning devices off, dimming screens, shutting down wireless connections and, in general, just not using my devices are the sorts of things end users can control.
Of course, that sort of defeats the purpose of having always-on devices, doesn't it? Application developers can do some things to help when they create apps, and hardware engineers can do some things when they design devices.
Ironically, we are so "digital" these days that radio frequency engineering is almost a lost art, as you might infer from the antenna issues the iPhone 4 has been having.
But Android developers can do some things when they develop code that has a direct bearing on power consumption.
Wednesday, June 30, 2010
Coding for Android Device Battery Life
Gary Kim has been a digital infra analyst and journalist for more than 30 years, covering the business impact of technology, pre- and post-internet. He sees a similar evolution coming with AI. General-purpose technologies do not come along very often, but when they do, they change life, economies and industries.
Subscribe to:
Post Comments (Atom)
-
We have all repeatedly seen comparisons of equity value of hyperscale app providers compared to the value of connectivity providers, which s...
-
It really is surprising how often a Pareto distribution--the “80/20 rule--appears in business life, or in life, generally. Basically, the...
-
One recurring issue with forecasts of multi-access edge computing is that it is easier to make predictions about cost than revenue and infra...
No comments:
Post a Comment