What is QMMI on Xiaomi and why is it being removed?
If you notice the com.qualcomm.qti.qmmi (or simply QMMI) process in Xiaomiβs Task Manager that is constantly hanging in the background, consuming charge and loading the processor, youβre not alone. This system service from Qualcomm is built into the firmware of most devices on Snapdragon chipsets, including the Redmi, POCO and flagship Mi lines. It is responsible for the interaction between modem modules and the main OS, but often becomes a source of problems.
Users complain that QMMI loads the battery (up to) 10-15% The processor overheats (especially on budget models like Redmi). 9A or POCO M3), Sometimes it even blocks the Internet connection due to conflicts with the Internet. SIM-And Xiaomi's official documentation doesn't say anything about how to operate this service -- it's just not in the standard settings -- and that's what's creating the myth that some people are telling you to turn it off. QMMI through ADB, Not understanding the risks, others suggest deleting system files, which can lead to a device "brick.
In this article, we will understand:
- π What is it? QMMI In fact, and why do you need it in the sleeve? MIUI.
- β‘ How to safely disable a service without root rights and communication consequences.
- β οΈ What can not be done not to turn a smartphone into a brick".
- π οΈ Alternative ways to reduce the load QMMI, if disconnection is not possible.
QMMI: Technical Details and Why It Can't Be Deleted
The com.qualcomm.qti.qmmi (Qualcomm Modem-Middleware Interface) service is the intermediate layer between Android and Qualcomm's proprietary modem.
- πΆ Management SIM-cards (switching between them, working with eSIM).
- π‘ Network signal processing (3G/4G/5G, handover).
- π Data exchange between the modem and the processor (e.g. when calling or SMS).
- π Optimizing the power consumption of a modem chip (although often works with the opposite effect).
The problem is that Xiaomi (and other manufacturers) are not optimizing this service for its MIUI shell.
| Symptoms. | Reason. | Affected models |
|---|---|---|
| Fast battery discharge | QMMI does not go into sleep mode, constantly polls the modem | Redmi Note 10/11, POCO X3/X4 |
| Overheating on standby | Conflict with processor cores with weak network signal | Mi 11 Lite, Redmi 9T |
| Internet cliffs | Handover processing failures between 4G and 5G | Xiaomi 12/13 with Snapdragon 8 Gen 1/2 |
| Hanging on calls | Processor load at simultaneous operation of QMMI and telephony | POCO F3/F4 |
Many "gurus" advise that QMMI be removed via ADB or Magisk, but it is extremely dangerous.
β οΈ Note: On devices with Snapdragon 4xx/6xx/7xx (For example, Redmi Note 8 pro POCO M2 Pro) removal QMMI And it's going to cause a total loss of communication, and it's going to stop catching the network, even after it's flashed. 13 Ultra) could fall off 5G VoLTE.
Method 1: Disable QMMI via ADB (without root)
This is the safest method, but it doesn't work on all versions of MIUI.
- π₯οΈ Computer with Windows/Linux/macOS.
- π Cable USB (better-than-original).
- π± Included debugging by USB smartphone.
Step-by-step:
- Download ADB Tools and unpack the archive.
- Connect the phone to the PC and confirm the debugging permission.
- Open the command line in the folder with ADB and type: adb shell pm disable-user --user 0 com.qualcomm.qti.qmmi
- Reset the device.
If the team doesnβt work, try an alternative:
adb shell cmd package disable-user --user 0 com.qualcomm.qti.qmmiOpen Task Manager (long press on the Home button)
Check for no process com.qualcomm.qti.qmmi
Make sure that the phone and the internet are working
Watch the battery. 1-2 day-day-->
β οΈ Important: On some firmware (for example, MIUI 13/14 for Snapdragon 865/870) This command can return the Operation not allowed error, which means that Xiaomi has blocked the shutdown of system services, in which case root or factory firmware reset will help.
π‘
Before disabling QMMI via ADB, back up your data. If the network goes missing after the reboot, follow the command adb shell pm enable com.qualcomm.qti.qmmi to return it all back.
Method 2: Partially disable via MIUI settings (for beginners)
If ADB seems complicated, you can try to limit QMMI activity to standard means, which will not remove the service completely, but will reduce its effect on the battery:
- Go to Settings β Applications β Application Management.
- Click on the three dots in the upper right corner and select "Show Systems".
- Find QMMI Service (or Qualcomm QMMI) and open it.
- Select "Battery" β "Limit background activity".
- In the "Mobile Data" section, disable "Background traffic".
It is also recommended that:
- π΅ Disable automatic network search in Settings β SIM-maps and mobile networks β Network Search (Select Manual Mode).
- π Establish an energy saving regime for QMMI manually (if available).
- π« Disable the auto-start service through Settings β Annexes β Auto-start.
These actions will not remove QMMI, but will reduce its activity by 30-50%.
What if QMMI is not listed in the app list?
Method 3: Disconnect via Magisk (for advanced users)
If you have root rights (installed by Magisk), you can disable QMMI more radically. But this is risky! On some devices (e.g. Xiaomi 12S Ultra), this can lead to the loss of VoLTE or 5G.
Instructions:
- Install Magisk and the App Systemizer module (available in the Magisk repository).
- In App Systemizer, search com.qualcomm.qti.qmmi and select "Convert to User App".
- Reboot the phone.
- QMMI will now appear in the standard list of applications β it can be disabled or removed.
Alternative method (for experienced):
- π Open up. /system/priv-app/QmmiService via Root Explorer.
- π Rename the file QmmiService.apk at QmmiService.apk.bak.
- π Delete the QmmiService.odex file (if any).
- π Reset the device.
β οΈ Note: On devices with Dynamic Partition (e.g. Xiaomi 13 Pro), modification of the system partition can lead to bootloop ( loop boot). TWRP Or OrangeFox.
What to do if QMMI cannot be turned off: alternative solutions
If none of these methods worked (or youβre afraid to take risks), try to lower your QMMI load indirectly:
| Problem. | Decision | Efficiency |
|---|---|---|
| High battery consumption | Shut down. 5G (If not used, in Settings β SIM-map β Type of network | ββββ |
| Processor overheating | Install Greenify and βfreezeβ QMMI (root required) | βββ |
| Internet cliffs | Reset network settings: Settings β SIM-map β Resetting mobile network settings | ββ |
| Hanging on calls | Disable VoLTE in the settings SIM-map | βββ |
Additional advice:
- πΆ Use applications like Network Signal Guru to monitor the signal. -110 dB, QMMI Will actively try to find the best tower - this is the reason for the load.
- π Regularly update the firmware. MIUI 14 for Snapdragon 8+ Gen 1 (e.g. Xiaomi) 12T Pro) partially optimized work QMMI.
- π οΈ If nothing works, consider switching to custom firmware (like LineageOS or Pixel Experience) where QMMI often removed or replaced with a lighter analogue.
π‘
Shutdown QMMI β If the problem is a weak network signal, even after the service is deactivated, the battery will go down quickly due to the modem's constant attempts to connect to the tower.
Xiaomi models that are the most problematic for QMMI
Analysis of user complaints shows that the owners of the following devices most often face QMMI:
- π± Redmi Note 10/10 Pro/11 (Snapdragon 678/680) β bug with endless battery consumption in standby mode.
- π± POCO X3 Pro/X4 Pro (Snapdragon 860/695) β overheating 4G.
- π± Xiaomi 11 Lite 5G NE (Snapdragon 778G) β conflicts with VoLTE, call interruptions.
- π± Redmi 9A/9C (Snapdragon 662/665) β QMMI processor 20-30% for no apparent reason.
- π± Xiaomi 12/12 Pro (Snapdragon 8 Gen 1) β trouble 5G high battery consumption.
On flagships (Xiaomi 13 Ultra, Mix Fold 2), QMMI tends to be more stable thanks to more powerful hardware and streamlined firmware, while on budget and mid-budget models (Redmi/POCO), service is often the main cause of discontent.
Interesting fact: on devices with MediaTek processors (for example, the Redmi Note 12 with Helio G88) there is no analogue of QMMI - instead, MediaTek's own solution is used, which less often causes problems.