You try to record a voice message or use a built-in voice recorder on Xiaomi, but instead you see an annoying notification saying, "The recorder is being used by another application." The system blocks access, even though you certainly didn't run any recordings. What's the matter?
This error is a common problem for MIUI smartphones (especially for versions 12-14), where system services and third-party applications can conflict over access to the microphone and audio subsystem.
- 🔊 Voice assistants (Google Assistant, XiaoAI) working in the background;
- 📱 Social networks (WhatsApp, Telegram) that "forgot" to release the microphone after the call;
- 🛠️ System processes (com.android.phone or com.miui.voiceassist) that block resources;
- 🚨 Viruses or suspicious applications masquerading as system services.
This article provides a full analysis of the causes and 5 working ways to fix the error, including hidden MIUI settings that are not described in the official documentation, and a table of compatibility with popular models Redmi, POCO and Xiaomi.
Why the Error is Error: Technical Reasons
At the Android level, access to the microphone and audio recording is regulated by the AudioPolicyManager system service. When an application requests a resource, the service checks if it is busy with another process. If it is busy, it emits an error. In MIUI, this mechanism works differently:
1. System Application Priority: Xiaomi services (e.g. XiaoAI or Mi Sound Recorder) are of the highest priority and can lock the microphone even after closing.
2. Errors in audio system cache: /data/misc/audio/ files are sometimes corrupted, causing the system to "think" that the recorder is busy.
3. Permissions conflict: If two applications are requested simultaneously RECORD_AUDIO, MIUI It may not be able to process the request correctly.
According to the analysis of Xiaomi logs (source: MIUI Forum, most often the error occurs on devices with 4 GB of RAM or less, where the system aggressively controls background processes. MIUI Global and MIUI Europe versions 12.5–14.0.3.
Method 1: Forced Stop of Conflicting Applications
The first step is to find and stop the process that the recorder is taking.
- Open Settings → Applications → Application Management.
- Slip on the three dots in the upper right corner and select "Show System Processes".
- In search, enter the keywords: 🔍 voice (voice assistants); 🔍 recorder (dictophones); 🔍 telephone (telephone services).
"Forced stop"
"Clear the cache."
XiaoAI (com.miui.voiceassist)
Google (com.google.android.googlequicksearchbox)
Mi Sound Recorder (com.miui.soundrecorder)
Phone (com.android.phone)-->
If the error disappeared after the stoppage, the problem was in one of these services, to prevent it from happening again:
⚠️ Note: Do not disable system applications through ADB Or a root access, if you're not sure what the consequences are, and it can cause the microphone to lose functionality in the calls.
Method 2: Resetting the audio system settings
If the forced shutdown didn't work, it could be a damaged audio cache, and MIUI has a hidden option to reset it:
- Go to Settings. → The phone.
- Tap 7 times on the MIUI version to activate the developer mode.
- Back to Settings → Additionally. → For developers.
- Find the option “Audio Effects Reset” (or Audio Effects Reset) and confirm the action.
After restarting the device, check the recorder. If the error persists, proceed to the next method.
💡
Before resetting audio settings, write down current sound profiles (e.g. equalizer settings in Mi Music) as they will be reset to factory ones.
Method 3: Verifying permissions for applications
Sometimes, the error is caused by multiple applications accessing the microphone at the same time.
- Open Settings → Privacy → Application permissions → Microphone.
- Sort the list by "Last Use."
- Disable microphone access for all applications except: 📞 Telephone (for calls); 🎤 Mi Sound Recorder (System Dictaphone); 🤖 Google Assistant (if you use voice search).
Reboot your smartphone.
If the recorder is running after that, gradually return permissions to other applications to identify the culprit of the conflict.
| Xiaomi model | Frequent Cause of Error | Recommended method of correction |
|---|---|---|
| Redmi Note 10/11 | The conflict between XiaoAI and Google Assistant | Method 1 + disabling XiaoAI in settings |
| POCO X3/X4 | The damaged audio cache | Method 2 (resetting audio settings) |
| Xiaomi 12/13 | Background activity of Mi Sound Recorder | Method 3 (permission check) |
| Redmi 9/9A | Lack of RAM (background processes do not release the microphone) | Method 4 (memory cleaning) |
Method 4: Cleaning the memory and cache of the system
On devices with 4GB of RAM or less, MIUI may not properly manage background processes, leaving resources (including the microphone) locked to fix this:
- Open Settings → Applications → Cleaning.
- Click on “Deep Cleanup” and wait for the process to be completed.
- Go to Settings → Memory and click “Clear Cache”.
- Restart the device in safe mode (press the power button → “Reboot in safe mode”) and check the recorder.
For discharge:
- Go to Settings → About the phone → Reset settings.
- Select “Delete all data”.
- Confirm the action and wait for the completion (it will take 5-10 minutes).
⚠️ Note: Some Xiaomi models (such as the Redmi Note 8 Pro) may require re-assigning your Mi Account to unlock the bootloader after a reset!
💡
If the error "Dictorphone is used by another application" appeared after the MIUI update, try to roll back to the previous version via the Mi Flash Tool.
Additional advice and prevention
To avoid recurrence of the error:
- 🔄 Clean the app cache regularly through Settings → Warehouse;
- 🚫 Turn off auto-start for unnecessary applications (Settings) → Annexes → Auto-start);
- 🔒 Install. MIUI Optimization Disabler (required Root) if your device often forgets to release the microphone;
- 📱 Update your firmware to the latest stable version (check on the official website).
If the problem only occurs in a specific app (such as WhatsApp or Telegram), try:
- Update the application to the latest version;
- Clear its cache and data (Settings → Apps → [name] → Storage);
- Reinstall it from an official source (Google Play or APKMirror).