Inside Project Volta: lazies first, or how Google plans to boost battery life on Android L by up to 20%
Improving battery life sounds like a noble idea, but how can Google do it? At the core of the effort comes an interesting find: the company monitored stats from the Nexus 5 revealing that roughly every 1 second of unnecessary active time (this would be the processor waking up to do a task it could do later) results in a 2-minute reduction in stand-by time. Now, imagine this on your average smartphone with 50 apps running, each taking 1 second of unnecessary active time per hour. Those seemingly small interruptions add up to a massive 100-minute reduction of your stand-by battery time for every hour all those apps run! And 1 second of unnecessary activity per hour might even be an optimistic scenario for some apps.
Project Volta: Lazies first
Project Volta pushes devs to think about battery optimizationsThis finding pushed Google to find a solution with an approach the company calls ‘lazy first’. Lazy first is basically a principle that encourages developers to schedule non-urgent tasks to be executed in the last possible moment. That’s a radical change from the current, purely performance-driven thinking apps schedule even non-urgent operations on a first-come first-serve basis.
With the new ‘lazy first’ approach, the effect accumulates for multiple apps running on this principle, so you can coalesce activity together for execution, rather than have every app continuously wake up the phone to do its operations. Let’s be clear about this push, though - it is good for tasks that do not need to return immediate user feedback. For the remaining cases, a developer would still build on a first-come first-serve basis.
JobScheduler makes lazy-fying your app easier
Of course, in order for users to fully feel the benefit, Google is making an effort to convince its third-party developers to optimize their apps as well. To make this easier, with Project Volta, Google is introducing a new API called JobScheduler.
Now, this is not a completely new approach to improving battery life - it looks a lot like the optimizations that Microsoft implemented in Windows 8 and that Apple introduced in OS X Mavericks, but Android seems to be among the pioneers of this approach in mobile.
Another element of Project Volta that will be instrumental in achieving a notable battery improvement on Android devices is the stat-laden Battery Historian tool. This is purely a developer-oriented tool that you can use to see how your app performs with an immense level of detail (down to each wake-up event it causes in a per-second timeline).
With Battery Historian developers will be able to see the problem - if there is one - with their app and why it is draining battery. You cannot fix a problem, if you cannot see it, right? Battery Historian gives devs the tools to now see the issue very clearly.
Battery Saver mode: squeeze 90 minutes more out of your dying battery
- reduce the refresh rate of the display
- limit background data
Project Volta improvements: 20% better battery life with Android L
Good news is that Project Volta is not just a theoretical initiative with no real results. Quite the opposite - Google's simulation with Project Volta on the Nexus 5 shows 15-20% improvements in battery life, and we have no reasons to doubt that - when all phone makers optimize their apps - other phones should see a similar battery life boost.
Inside Project Volta Fullscreen
More popular slideshows
iOS 7 release date and time are today (Sep 18), get ready to update!
18 Sep 2013, 04:00
Inside Project Volta
reference: Google, AnandTech
1. ArtSim98 (Posts: 2173; Member since: 21 Dec 2012)
"JobsScheduler" lol. I like your typos. And you made it 2 times in a row :)
2. Victor.H (Posts: 404; Member since: 27 May 2011)
Ha! Thanks, fixed it now - at least it wasn't iJobsScheduler!
8. PhoneArenaUser (Posts: 5422; Member since: 05 Aug 2011)
Victor, I see what you did there. :D
11. Finalflash (Posts: 1416; Member since: 23 Jul 2013)
Actually, knowing Android's internal naming scheme for hidden and non-public classes within an API, the JobsScheduler object likely relays to an iJobsScheduler object for its core tasks. So you wouldn't be wrong even then.
3. azalucel (Posts: 63; Member since: 27 Dec 2013)
Last line should be other phones will see similar battery life boost not wont see
4. AstronautJones (Posts: 239; Member since: 01 Aug 2012)
Good news. Now, maybe OEMs will concentrate on batteries a little too. (I don't need a 6mm thick phone, add more battery!)
6. deathgod (Posts: 119; Member since: 23 Nov 2011)
You know what would also improve battery life? An optional black theme in your apps for oled users like they used to have!
7. Stuntman (Posts: 707; Member since: 01 Aug 2011)
You know what this means. Phone makers will put smaller batteries in their phones and users will be stuck with the same battery life as before.
12. renz4 (Posts: 202; Member since: 10 Aug 2013)
to them it was a nice opportunity to save cost (using much smaller capacity battery) and increase the profit margin (the phone will still cost the same as always despite cheaper part being used).
13. tarek1980 (Posts: 48; Member since: 07 Jan 2014)
For me I have Samsung Galaxy S4, my next upgrade will be 64 bit hardware smartphone with Android L & at least 3200 nMh battery (replaceable), 5" screen.
For less than that I will not upgrade.
9. gigantos (Posts: 39; Member since: 25 Jul 2013)
'Eliminate UI'? Then what's left? Lol. Maybe you mean lags in UI gestures.
10. AfterShock (Posts: 2050; Member since: 02 Nov 2012)
This isn't the os your thinking of, this is the leader of others that aren't number 1.