January 4th, 2024 | Updated on November 4th, 2025
5 Takeaways:
- Android 14’s Optimization Efforts
- Automatic App Activation
- OEM Flexibility
- GMS Bundle Allowlisting
- Industry-wide Adoption Concerns
Android 14, having been available on various smartphones for several months, continues to unveil new features and optimizations.
Recently, a reliable source has unveiled a particularly useful feature aimed at tackling the persistent issue of bloatware.
Mishaal Rahman, a meticulous investigator of Android code, shared on Patreon that Android 14 incorporates a feature designed to alleviate the memory and battery usage associated with pre-installed applications.
Rahman elucidates that Android 14 initiates a scan of system partitions during the initial boot-up process.
If this scan identifies a new application with an “exported launcher activity” (indicating an app launchable via a home screen icon), the app is placed in a “STOPPED” state until the user actively opens it.
In practical terms, this signifies that many preloaded apps, which are launchable by the user, will not consume system resources until the user decides to launch them.
Rahman refers to Google’s own description of the feature, highlighting that it “significantly reduces the system resource usage, such as memory or battery.”
This discovery underscores Android 14’s ongoing efforts to optimize user experience by addressing the impact of bloatware on system performance, showcasing the platform’s commitment to enhancing efficiency and resource management.
How Will This Work In Practice?
Google intends to implement the new feature, as discovered by Mishaal Rahman, by default in the Android Open Source Project (AOSP).
However, the company is reportedly giving Android Original Equipment Manufacturers (OEMs) the flexibility to opt-out of the feature if they choose to do so.
Alternatively, OEMs have the option to embrace the feature but can create an allowlist specifying particular preloaded apps that can still consume system resources without requiring user activation.
An interesting observation made by Rahman is that the Google Mobile Services (GMS) bundle provided to OEMs, which they integrate into their software, already includes several Google apps that are pre-approved for system resource consumption.
Notable apps on this allowlist include Chrome, the Play Store, Photos, Files, YouTube Music, Contacts, and others.
This strategic inclusion ensures that critical functionalities like contact syncing, automatic app updates, and general data syncing remain unaffected.
Despite the potential benefits of this feature in combating the impact of pre-installed apps, its effectiveness relies on widespread adoption by OEMs.
The concern is raised that if OEMs choose to allowlist some of their own apps, it could potentially diminish the overall impact of the feature.
The hope is that Android manufacturers will embrace this capability to enhance user experience and system performance, emphasizing the need for industry-wide adoption to fully realize the benefits of this novel approach to managing pre-installed applications.
