In recent years we have witnessed unprecedented technological progress; we have turned our habits upside down with many technological gadgets: the most important is surely the smartphone that with its great versatility and the vastness of its functions has managed to guarantee itself a fixed place in our pockets, supporting us in our everyday life managing to change even the mobility of large cities (the term SmartCity has even been coined) where it is no longer a problem to find public transport or other sustainable means of transport nearby.
This progress, however, has not affected the various hardware components in the same way: batteries, for example, have not had a major innovation and therefore suffer the weight of an old technology; it is rare to find smartphones that exceed 24 hours of autonomy so we are forced to limit ourselves in their use.
There are several approaches to try to solve the problem but there are very few ones that allow you to get real increases in autonomy: there are programs that aim to better manage the hardware components by activating and deactivating the connection, the GPS, the synchronization of our APPs ; or you can still minimize the brightness of the display but all this personally I find it a fallback: many times, especially using APP for the management of consumption, the result is that you take more memory and add workload to the CPU unnecessarily.
The solution lies in eliminating the problem at the source and that is: what are the applications that have consumed the most battery? are applications that I need always active or can I activate them manually when I need them?
very often because of poor optimization, some apps keep active parts of the hardware that obviously consume battery. It is therefore necessary to analyze their behavior specifically, thanks to WakeLock Detector (link Play Store)
This application allows you to comb through specifically what they were the processes that have awakened the various parts of our phone and for how long they have remained active: in the initial screen we will find a list of installed applications and a bar that shows us the percentage of time in which the mobile has remained active since the last full charge (awake).
from the top menu we can find some items:
- Screen Wakelock: applications that have activated the smartphone screen with the overall activity time attached
- CPU Wakelock: applications that have activated the CPU
- Wakeup triggers: list of applications that have activated the smartphone with indication of how many times they have done it
- Kernel Wakelock: list of processes that have activated other hardware components such as the NFC
we can also sort the application list by consumption order (recommended): to be able to visualize quickly which are the voices have more impact on the battery.
The items in red are active applications / processes while those in black they are not running in the background; if we click on any item in the list CPU wakelock we have the possibility of end it o uninstall (if it is a user application) if start it, useful in case we don't remember which application it is or even if open it directly in the playstore.
once the operation of WakeLock Detector let's analyze the list CPU Wakelock, let's order it by order of consumption, and look at the top positions: if we find an application external to the android system and google services, which we don't use often and that does not need to remain in the background forever, it is good to terminate it and also evaluate its uninstallation.
If we find excessive consumption by the Google services, the only advice is to manually terminate the application process from the application menu Google maps, which often causes excessive battery consumption.
Let us now analyze the part relating to Kernel Wakelock: unfortunately this operation is much more difficult than the previous one, as the names of these processes are often incomprehensible; the best thing is to order the list by consumption order (usage) and look for the name of the processes directly on the web to understand what it is and what the solution is.
Click here for a list of some wakelock kernels directly from the androidiani forum.
in subsequent charge cycles we must make sure that the autonomy is improved after the removal of suspected wakelock, if not, we can proceed using other solutions such as deactivating services that do not use for example the NFC or google now ... waiting anxiously a solution from the producers.