Android 14 prevents bloatware from using memory and battery
Android 14, the newest version of the green robot, has been available officially for a while now, and its ubiquity across the range of devices available on the market keeps growing. Despite its age, new features concealed within the code of this operating system are still being discovered and shared online. The installation of an extensive array of unwanted and typically unnecessary applications is what happens when smartphone manufacturers do this. Some manufacturers continue to clutter their devices with applications that customers find uninteresting. Now it appears Google has developed a potential fix, which is concealed in Android 14.
Most consumers do not want software that comes pre-installed on a device, which is referred to as bloatware. On Android phones, manufacturers and carriers frequently pre-install a number of large applications. They only clog your system and silently drain your battery if you are not using them. The developer found a hidden feature in Android 14 code that should lower the memory and battery relationship of the pre-installed app, as per Mishal Rahman on Patreon. The system will be able to search through the apps on the smartphone at first startup. Should it find an app that it deems to be “exported startup activity,” it will block it until the user opens it.
In order to carry out this function, the tipster further notes that the GMS package that the business sends to OEMs includes a number of Google apps that are on the white list. All this is because of the possibility that depriving some of these applications of system resources could seriously impair the system’s overall functionality. As per Rahman, the feature in issue “significantly reduces the use of system resources,” therefore “many preloaded apps that can be launched by the user will not consume system resources until the user actually starts them,” states Google’s description of how it works.
Note that while this feature isn’t available right now on Android 14 smartphones, Google plans to enable it by default in the AOSP code and provide the option for different manufacturers to disable it. OEMs can choose to activate the feature, but they can also add particular programs to the white list to avoid being impacted by it. This way, the programs can use system resources without having to be activated first. Google’s way of handling it may look practical, but things needed to be decided only after looking into the responses from other manufacturers.