Like a birthmark were, Android has always sin of a sad energy management. The autonomy of smartphones with Android has always been, generally, less than its nearest rivals (iOS and Windows Phone), a decisive factor for many users when the time came to purchase a new device .
Historically, autonomy has not been strong platform Android
The situation has been improving over time, yes, but it has done by brute force: progressively increasing capacity batteries. Inevitably, this translates into greater autonomy -always than other variables (energy consumption of the other components) invariables- stay, but not the only way to achieve that desired independence from the charger.
The other formula is based on the optimization software, carefully regulating energy consumption (both intensity and frequency) of the different components that make up a smartphone. And that is precisely what Google tried to achieve Volta Project, a series of measures implemented in Android 5.0 Lollipop -version we could initially announced during the past Google I / O 2014 -.
How does Volta Project ?
Project Volta, a roughly , we can divide it into three main parts:
JobScheduler
One of the virtues-and defects-time Android is the freedom it gives Google developers to run background tasks. Applications can “wake” the device at any time to perform tasks in the plan even if it meets the muffled screen, causing, as a result, a significant decrease of the autonomy of the device.
To try to regulate these consumptions in the background, Google developed the API JobScheduler , which, as its name suggests, is a task scheduler.
How does JobScheduler ? Very briefly, this part of Project Volta handles group different application processes performed in the background , organizing them by priority and trying to reduce the number of “awakenings” device. For this, application developers must set a number of priority parameters to be considered by JobScheduler , who will allow the execution of these when possible.
JobScheduler regulates number of “awakenings” device
For example: Google Play, by default, does not check pending updates until the device is charging and connected to a Wi-Fi network. JobScheduler is responsible for Google Play prohibit the execution of these processes until the above conditions are met.
In addition to the context (connectivity, remaining battery, etc.), JobScheduler takes into account the priority of processes-which is also fixed by the developers of applications included. If an application requires internet access to update your database, JobScheduler retain this process until the right circumstances or, alternatively, are given until a specific number of processes are grouped Similar . Where one of the two situations, JobScheduler allows execution of these processes. Thus, instead of “awakening” 100 times the device, it will wake up 10 thereby significantly reducing the time the terminal is active in the background and, therefore, increasing autonomy.
Battery Historian
Google knows that consuming applications is the main reason why the autonomy of Android devices has been so poor since its inception. Therefore, in Project Volta incorporated a new utility called Battery Historian , which enables developers to learn in a more visual and detailed processes that are running their applications and simultaneously how much energy you are consuming each.
In this way, Google aims to provide developers optimize energy consumption applications, thus reducing the energy consumption of these and, in parallel, increasing the length of the autonomy of any Android device inside the hostel.
Battery Saver Mode
The third component of Project Volta is Battery Saver Mode (power saving mode in Spanish), which, as its name suggests, is a energy saving mode , similar to that leading manufacturers including years on their Android devices.
Very conditioned but a really useful way in certain situations
This power saving mode reduces the maximum CPU frequency, limits the maximum the background processes and carefully controlled device connectivity, thus prolonging the autonomy. Yes, this extra juice is priced terminal response to more comprehensive tasks is obviously lower than usual (slower, less fluent, etc.), so use only recommended in extreme situations like that dreaded moment autonomy reaches the remaining 15% –
Has taken effect Volta Project
The first tests on the preview Android L were encouraging. ArsTechnica said an increase of 36% in the time of web browsing on Wi-Fi taking as a basis a Nexus 5-, something really commendable (though not decisive).
But that was not the final version of Android 5.0 Lollipop or all devices running a clean version such as the Nexus family or web browsing is the only work we do on our smartphone. Therefore, these initial tests were somewhat incomplete.
Fortunately, GSMArena has made a series of deeper tests, throwing the various figures. But of them all, the test to which we should pay more attention to the total duration is at rest, because the conditions are the most homogeneous to judge the influence of Volta Project -not influences the technology nor the consumption of the display does not influence optimization of foreground applications, etc.-. In it we see how differences to Android 4.4 KitKat are not overly noteworthy , which many considered failure
However, there is an explanation to so little improvement. Developers . Although many have interpreted as such, Project Volta is not a miracle in the form of software ; is a set of tools that allows developers to improve the energy efficiency of their applications, thus prolonging the full autonomy of the device. Therefore, the responsibility of the effectiveness of Project Volta falls on them : If you do not make proper use of these tools properly -fijando parameters for JobScheduler and analyzing the consumption with Battery Historian -., the increase in total autonomy of the device is minimal
So while Volta Project is a breakthrough and, as time passes, we will see greater importance, can not call it like that bird saving many expected , unlike other similar projects as Project Butterworth. We’ll have to keep waiting for developers and manufacturers to make better use of these tools and / or Google releases new functions more importance in this area. Perhaps we see in the next Google I / O
.
No comments:
Post a Comment