Modern operating system-based smartphones Android often come with a huge amount of pre-installed software. Users often encounter a situation where the standard list of apps displays only those utilities that were installed from the store Google Play. However, “under the hood” of the device there are dozens and sometimes hundreds of system processes and services that are responsible for the stability of the gadget.
The need to see the entire list can arise for various reasons: from banal curiosity to an urgent need to free up space in memory or disable unnecessary manufacturer services. The standard settings interface often hides this information so that an inexperienced user does not accidentally remove a critical component, turning the phone into a “brick.”
In this material we will analyze in detail all the available methods for viewing hidden system applications. You'll learn how to use native system tools, developer options, and powerful command-line tools to get a complete picture of what exactly is running on your device.
Standard Android settings: finding hidden sections
The first and most obvious way is to delve deeper into your smartphone's settings menu. Depending on the version Android and the installed shell (for example, MIUI, OneUI or ColorOS), the path to this information may differ significantly. On “clean” Android the list is often hidden behind an additional switch.
To find hidden apps, you need to go to the app management section. Usually it is located along the Settings → Applicationspath. Here you will see the main list. However, to see system processes, you often need to click on the menu icon (three dots) in the upper right corner of the screen and select "Show system processes".
On some devices from manufacturers Samsung or Xiaomi this item may not be explicitly form. In this case, the system displays only user applications by default. This is done intentionally to simplify the interface. If the switch is not found, it is worth checking the "Accessibility" or "Device Manager" sections, where information about services is sometimes duplicated.
It is important to understand the difference between user and system data. User applications can be completely uninstalled, while system applications can often only be disabled. Trying to remove a critical component through third-party tools without root access may lead to unstable operation.
⚠️ Attention: Do not try to forcefully stop processes with names containing the words "System", "Framework" or "Telephony" unless you are 100% sure of their purpose. This may cause the device to reboot or lose connection.
Before any manipulations with the list of applications, make a complete backup of your data via Google Account or locally to your computer.
Activating developer mode for advanced access
If the standard menu does not provide complete answer, the next step is to activate hidden mode for developers. This mode provides access to advanced diagnostics and more detailed system control. Activation occurs by repeatedly clicking on the build number.
Go to Settings → About phone (or "About device"). Find "Build Number" and quickly click on it 7 times in a row. The system will ask for your PIN code or pattern, after which it will inform you that you have become a developer. Now a new section will appear in the main settings menu.
Inside the menu for developers you can often find the item “Running services” or “Process statistics”. The currently active applications, including system ones, are displayed here, indicating the amount of RAM they occupy. This is a useful tool for identifying apps that “eat up” resources in the background.
In addition, background process limit settings are available in this section. While this doesn't directly allow you to see a complete list of all installed system packages, it does give you an idea of which ones are active right now. For a complete audit of installed packages, this method is an intermediate step.
- 🔍 Build number —a unique identifier of the firmware version of your device.
- ⚙️ USB debugging —a key function of the developer mode, necessary for communication with a computer.
- 📊 Memory — section showing average RAM consumption for 3, 6 or 12 hours.
Using ADB to get a complete list of packages
The most professional and comprehensive way to see absolutely all system applications is to use the toolkit ADB (Android Debug Bridge). This method requires connecting the smartphone to the computer via a USB cable and having the driver and platform tools installed on the PC.
First make sure that developer mode is activated USB Debugging. Connect your phone to your computer and confirm permission to debug in the pop-up window on your smartphone screen. Next, open a command line or terminal on your computer in the ADB tools folder.
To list all installed packages, including system ones, use the following command:
adb shell pm list packagesThis command will produce a huge list of all packages in the format package:package_name. To filter only system applications, you can add the -sflag. The command will look like this:
adb shell pm list packages -sIf your goal is to see only those applications that are not system (user) ones, use the flag -3. The combination of flags allows you to flexibly control the output of information. For example, a list of paths to APK files is displayed by adding the flag -f.
⚠️ Attention: Command line interfaces do not have a Cancel button. Be extremely careful when entering commands, especially those related to deletion (
uninstall), since an error can lead to data loss without the possibility of recovery through the recycle bin.
How to install ADB on Windows?
Download the "Platform Tools" archive from the official Google site. Unpack it into a convenient folder (for example, C:\adb). Hold Shift and right-click in an empty space in the folder, select "Open a PowerShell window here" or "Open Command Prompt."
Analysis of system applications through third-party utilities
For those who do not want to bother with cables and the command line, there are specialized manager applications. They provide a graphical interface for viewing, analyzing, and managing system components. One of the most popular and reliable tools is Package Name Viewer or App Inspector.
Such utilities scan the registry of installed apps and display information in a convenient form: icon, application name, package name, version, size and installation date. Many of them can divide the list into “User” and “System” tabs, which greatly simplifies navigation.
Some advanced managers, such as SD Maid or Titanium Backup (requires Root), allow you not only to view, but also to freeze or delete system software. However, using such features without a deep understanding of the architecture Android is extremely risky.
When choosing a third-party application, pay attention to the permissions it requests. To view a list of installed apps, basic rights are usually sufficient. If an application requires access to contacts or a microphone to perform this task, this is a reason to be wary.
| Name of the utility | Presence of Root | Functional | Complexity |
|---|---|---|---|
| Package Name Viewer | No | View package names | Low |
| App Inspector | No | APK analysis, view components | Medium |
| SD Maid SE | No (partially) | Cleaning, managing applications | Average |
| Titanium Backup | Yes (required) | Full backup, freezing, deleting | High |
Third-party utilities are the best choice for visual analysis, but ADB remains the only method of mass management without installing unnecessary apps on the phone itself.
Differentiating system applications from user ones
Understanding the difference between application types is critical for security devices. System applications are located in a protected memory section /system/app or /system/priv-app. They are signed with the firmware developer key and have priority in operation.
User applications are installed in the partition /data/app. They operate in an isolated environment (sandbox) and do not have access to critical kernel functions without explicit user permission. Deleting a user application simply erases its files from the data partition.
An attempt to delete a system application without superuser rights (Root) is usually blocked by the system. Even if the interface allows you to click the "Delete" button, often only the "Disable" option is available. This hides the application from the menu and stops its processes, but the file remains in memory.
There is also a category of pre-installed applications from telecom operators or manufacturers (Bloatware). Technically, they are often system-specific, but are not critical to the operation of the OS. Removing them is usually safe, but requires the use of ADB or specialized software.
- 🛡️ Privileges —system applications have access to hardware functions that are closed to ordinary apps.
- 🗑️ Uninstall —user applications are deleted completely, system applications are most often only disabled.
- 🔄 Update —system applications are updated only through OTA firmware updates or manually.
⚠️ Attention: Package names are not always obvious. The application with the name
com.android.mmsis messages, butcom.google.android.gmsis Google Play services, the removal of which will disrupt the operation of most modern apps.
☑️ Check before deleting a system application
Safe management and possible risks
Viewing system applications is just the first step. Often users want to optimize the system by removing unnecessary things. However, the ecosystem Android is deeply integrated, and removing a useless component can cause a chain reaction of errors.
For example, removing a system component responsible for supporting a particular codec can cause a camera or video player to stop working. Removing input services may block your ability to type. Therefore, the “measure seven times” rule is more relevant here than ever.
If you decide to delete a system application via ADB, use the command pm uninstall -k --user 0 package_name. The key --user 0 deletes the application only for the current user, without physically affecting the system partition. This allows you to return the application back through a factory reset in case of failure.
Always check that information about specific packages is up to date. The structure of system applications changes from version to version. What was safe to delete on Android 10may be critical on Android 14.
⚠️ Attention: Command parameters and the structure of system partitions may change with the release of new versions of Android. Before performing destructive actions, check the official documentation or reputable technical forums for your specific device model.
Frequently asked questions (FAQ)
Can I remove system applications without root access?
Complete physical deletion from a partition /system without superuser rights is impossible. However, you can "delete" the application for the current user via ADB, which will hide it and stop working, freeing up some user memory, but the file itself will remain on the system partition.
Is it safe to disable Google Play services?
No, this is highly not recommended. Services Google Play (com.google.android.gms) are responsible for push notifications, geolocation, account synchronization and the operation of most third-party applications. Disabling them will lead to the inoperability of many apps.
How to return an application deleted via ADB?
If you used a command with the flag --user 0, the application can be restored with the command adb shell pm install-existing package_name. If a Factory Reset was performed, all standard system applications will return automatically.
Why do some system applications take up a lot of space?
System applications can accumulate cache and data in the same way as regular ones. In addition, some of them are wrappers for web services or contain resources for different languages and screens, which increases their original size.
Does removing system junk affect the warranty?
Using ADB to remove apps for the current user usually does not violate the warranty, since it does not require unlocking the bootloader. However, obtaining root access and modifying the system partition almost always voids the manufacturer's warranty.