DISCLAIMER: The following post is a user-submitted post. Accessible Android editorial staff members have not tested the service, and using it is at your own risk.
I’ve been an Android developer for 2 years and a power user for more than 5. It’s rare that apps amaze me and actually manage to win the game in my “to pick” list.
AppManager by MuntashirAkon is incredible and very advanced, but at the same time as simple as you want it to be, depending on what you do with it.
Table of Contents
Important Warning
With great power comes great responsibility. App Manager, especially in the elevated ADB mode you’re going to use after reading this post, can be potentially dangerous if used incorrectly, such as: If ignoring, instead of denying the “GET_AUDIO_FOCUS” app operation for an application, the application is not going to start and crash instead. Before executing any app operations, denying and/or allowing permissions, debloating any app, or making any change to any app with AppManager, make sure you research the specific permission, app, operation or task, and then choose wisely.
If you want to go deeper than we’ll do today in AppManager’s world and unlock its full ADB power, then I recommend
reading its documentation here.
MuntashirAkon and I are not responsible for improper use of this application, nor to anything that happens to your phone, or any of the apps by using any of the features of AppManager.
Installing Apps with AppManager
As any of you might know by now, Google took the world by storm as they announced that Android sideloading will be limited to ADB only, and unverified apps, even outside the Google Play, won’t be allowed to be installed. While this issue will be easy to overcome by custom ROM developers, the majority of users won’t be installing a custom ROM, because it requires extended know how.
AppManager by MuntashirAkon, however, overcame this issue since back in 2024, by introducing an ADB mode, and its installer UI could be used through ADB. In the following few minutes, you’ll be able to install any Android app, from any app store, in 2027 and onward, and I’ll show you how to install AppManager both now, and then.
First, no matter which method you’re going to use,
download the AppManager’s installer file from here.
Method 1: Install AppManager through Package Installer (only possible until the new Android rollout)
If using Chrome or Brave, you’ll see the “Open” button on the right top side of your screen, on the “File Downloaded” notification popup. In case you missed it, open your file manager. Under recent files, or in the downloads folder, you’ll find the file.
In case you didn’t sideload any app before, you’ll receive a popup like this: “For your security, your phone is not allowed to install apps from this source.” You have a cancel button, and a settings button. Click on settings, allow the permission:
- On Android 12 and older: search for the app and check it.
- On Android 13 and newer: it will open the “Install Unknown Apps” overlay for the specific app.
No matter if it’s the browser or your file manager, any installed app on your device needs this permission to install apps.
After the permission is granted, depending on the Android version, you’ll either have to press back, or the package installer may overlay on top asking you to install the app. Click install, then click done if you want to continue with this later, or open if you want AppManager to open right after it has been installed.
Method 2: Via Shell
If you’re reading this article in 2027, do note that AppManager most likely won’t be trusted by Google, as a single developer won’t most likely pay the fees to Google for it. Follow the next steps instead:
- Open a command line with the SDK platform tools. This tutorial doesn’t include a way to configure and setup platform tools on your PC.
- Download AppManager’s file on your computer.
- Copy AppManager’s path into your clipboard.
- Type this command into the command line window after your phone is connected, and USB debugging is granted:
adb install -g "file_path_here.apk"
Replace the string in between quotes with the path of AppManager on your computer.
If you are not able to use a computer, type this command in Termux:
pm install -g /storage/emulated/0/Download/"AppManagerFileName.apk"
Replace AppManagerFileName.apk with the actual name of the APK.
First Launch and Setup
Now that AppManager has been installed, it’s time to open it. As you open it, you’ll see a string of numbers and letters. As the app explains, this is the keystore of AppManager. It’s recommended to save this somewhere should you need it, visit documentation for more details, then click close.
Please now wait. If AppManager quits, then it means it is required to restart. Open the app again.
You’ll see a disclaimer almost like the one I just posted. You can check to not show again, and then click agree. Clicking Exit the app will quit, and the checkbox’s state will not be saved.
After clicking accept, you’ll be shown a list of your available system and user apps, all grouped together in a unified list. App sorting and filtering options aren’t the scope of this first post in the AppManager Wonderland series, so I’ll just mention it so you can get familiar with the app’s layout. The data the app displays about an app is the time it’s been updated, month day, year, plus data from the app’s signature, such as the address and name of the developer posted in the app’s signature file. As we can see, AppManager doesn’t shy away from showing us real, valuable data from the very start.
Pairing with Wireless Debugging
Let’s now click the More options button on the top right corner. A menu will appear. From this menu, we’ll choose settings, as the first step is for us to pair AppManager with the wireless debugging.
From the settings menu, choose mode of operation. At this time it’s set on no root. Both mode of operation mode and the inferred mode are set on no root. Click here and open it.
If you don’t want to use wireless debugging, you can use the shell server. The app is self explanatory there. If you want to use wireless debugging, though, click on change mode button. In the little popup, click wireless debugging, then click apply.
In the “Choose what to do” popup, click Pair. The next popup is self explanatory: click the “Go” button. You’ll have a notification from AppManager “Wireless Debugging: Searching…”
Navigate to wireless debugging, and turn it on. In the wireless debugging window, click “Pair device with pairing code.” Now you have the pair with device popup appear. Don’t back out of this. Instead focus the pairing code string, then use functions menu → copy on it. Alternatively if they’re unified, like on a watch or smaller DPI/screen, use selection mode to copy the 6 digit code.
After the code is in your clipboard, open the notification shade, and instead of searching, you’ll see a notification with the already found port. Click on the “Pairing code” button near it, and then paste the pairing code. After that, click send.
The “Pair with device” window will disappear, and you’ll see a notification from AppManager “Wireless debugging: Paired!”. To confirm this, AppManager will be in the list of ADB devices remembered by your phone.
It’s also recommended to disable the “Disable ADB Authorization Timeout” by finding it back in the root of the developer options menu, usually near Wireless Debugging, to prevent AppManager from being forgotten by your phone in case it’s not being active for 7 days.
Remember that after each reboot, opening AppManager turns on Wireless Debugging, and of course, you’ll need a Wi-Fi connection for this method to work. In case you want it connected via shell, do that from AppManager’s mode popup.
Final Step: Configuring the App Installer
AppManager supports a few spoofing options for its installer, plus automatic app optimisations right on install, so we’ll do that as a last step. In AppManager’s settings, go to app installer. Here are its settings:
- Install Storage: Automatic, internal, external. It can be configured here.
- Block trackers: Blocks all tracker libraries right on installing the app. I don’t recommend this, as it automatically blocks all trackers, including useful ones, such as location for a GPS app.
- Display changes: This option is already checked and is one of the most beautiful perks of this installer. It will show you new deltas for components, version deltas, Target and minimum SDK deltas, and more. I recommend this on.
- Installer app: Set this to Google Play Store (Recommended as more apps check it).
- Request Update Ownership: This option should be checked and it already is by default.
- Default package source: Set this to “Store app”.
- Set Package Origin And URI: This should be checked.
- Sign APK: Not recommended to check for basic/casual users. Building a signature requires a little bit of Java knowhow.
- Immediately Perform DEX optimization: It is recommended to check this.
- Install in the background: You decide: Should you be able to open the app from UI, or show the notification that it’s been installed, this is your choice.
Installing APKs
When asking what to open an APK, APKS, XAPK, and APKM file with, click app manager – install, then click always. Remember, AppManager starts Wireless Debugging and/or the server when it starts, so don’t worry about anything, if only you’re on a different Wi-Fi network.
To install multiple APKs, select them in your file manager, then share them to AppManager’s install intent. Please remember that this setup is a one-time configuration. Any app going forward will be installed with AppManager, and no additional complicated setup will be needed.
Conclusion
MuntashirAkon’s AppManager is one of the most powerful apps I’ve ever seen, an app I recommend for the fullest user agency and transparency.
The installer is only a smaller part of AppManager and I promise I’ll cover other amazing features from this app going forward in the “AM Wonderland” series. But since Google’s new restriction on APK sideloading is a topic not only of trend, but also a great threat to accessibility and user agency in the name of privacy and protection, I decided to start by covering the installer first.
Comments