โ€œDonโ€™t close the speaker areaโ€: how to remove the warning on Xiaomi Redmi Note and disable the function

Owners of Xiaomi Redmi Note smartphones (especially Redmi Note 10/11/12 series models) often face an annoying notification: โ€œDonโ€™t close the speaker area.โ€ The message appears even when the speaker is not closed, interferes with listening to music, speakerphone conversations and using multimedia. What is the reason for this bug, why the system mistakenly detects the speaker lock โ€“ and most importantly, how to turn off the function forever without risk to the device?

In this article, weโ€™ll look at all the ways to solve the problem, from simple audio settings to deep changes in system files (for advanced users), and explain why turning off the proximity sensor or resetting doesnโ€™t always help, and which Redmi Note models are most susceptible to this bug. If youโ€™re tired of constant pop-ups and want to return comfortable use of your smartphone, read on.

Why does the warning โ€œDonโ€™t close the speaker areaโ€ appear?

The message "Do not close the speaker area" is a MIUI security function that works when the detects system locks the speaker (for example, with your palm, case or fingers).

  • ๐Ÿ”Š Overheating of the speaker with prolonged sound reproduction in a closed state;
  • ๐ŸŽต Sound distortion due to resonance in a confined space;
  • ๐Ÿ“ต Drop in microphone volume during calls (if the speaker is closed by hand).

However, in practice, Xiaomi Redmi Note sensors often give false positives.

  1. Pollution of the proximity sensor (dust, greasy fingerprints);
  2. Damage to the plume after falling or repairing;
  3. Software bug in MIUI (especially in versions 12-14)
  4. Incompatibility of covers with a cutout under the speaker.

Interestingly, the problem is more common on models with stereo speakers (Redmi Note 10 Pro, Note 11S, Note 12 Pro+), where the system analyzes the operation of both speakers. If one of them is partially closed (for example, with a finger while horizontally holding), an alert is triggered.

๐Ÿ“Š Which Redmi Note model is your problem?
Redmi Note 10/10 Pro
Redmi Note 11/11S/11 Pro
Redmi Note 12/12 Pro
Another model
I don't have that problem.

Simple ways to remove notifications (without root)

Before resorting to radical measures, try safe methods that do not require superuser rights:

1. Cleaning of the proximity sensor

Most often, the problem is solved by a simple cleaning, the sensor is located next to the front camera (top of the screen).

  • ๐Ÿงด Wipe the area with a cotton swab soaked in alcohol (60% and higher);
  • ๐Ÿ’จ Use a spray of compressed air to remove dust;
  • ๐Ÿ“ฑ Reboot your smartphone after cleaning.

2. disable notifications in sound settings

In some versions of MIUI, the warning can be disabled via the menu:

  1. Go to Settings โ†’ Sound and vibration โ†’ Additional settings;
  2. Find the Dynamic Warnings (or Dynamic Protection) item and deactivate the slider.
  3. If there is no item, try the following method.

3. Resetting the sound settings

You can reset the sound settings to the factory without losing data:

Settings โ†’ System and device โ†’ Resetting settings โ†’ Resetting sound settings

This method helps if the failure is caused by a settings conflict after the MIUI update.

โ˜‘๏ธ What to do before resetting the sound settings

Done: 0 / 3

Advanced methods: disabling through ADB and system files

If standard methods don't work, you'll have to use a developer tool, which requires connecting your smartphone to your PC and having a basic knowledge of ADB.

Method 1: Disconnect via ADB (without root)

This will require:

  • ๐Ÿ–ฅ๏ธ Computer with Platform Tools installed;
  • ๐Ÿ“ฑ Included debugging by USB on a smartphone (Settings) โ†’ The phone. โ†’ Version. MIUI โ†’ 7 times tap to activate the developer mode, then enable debugging in Settings โ†’ Additionally. โ†’ For developers);
  • ๐Ÿ”Œ USB-cable (preferably original).

Instructions:

  1. Connect your smartphone to your PC and open the Command Prompt (Windows) or Terminal (macOS/Linux) in the folder with the platform-tools;
  2. Enter the command to check the connection: adb devices (the name of your device should appear);
  3. Execute the command to disable the warning: adb shell settings put global speaker_protection_enabled 0
  4. Reboot your smartphone.

โš ๏ธ Note: This method does not work on all versions. MIUI. If the warning comes back after the reboot, try an alternative command:

adb shell settings put system speaker_protection_disabled 1

Method 2: Editing system files (requires root)

If you have root rights, you can permanently disable the function by changing the system file:

  1. Install a root-enabled explorer (such as Root Explorer or FX File Explorer)
  2. Cross the path: /system/etc/device_features/
  3. Find the file miui.xml and open it in the text editor.
  4. Add a line: <bool name="speaker_protection_support">false</bool>
  5. Save the file, set the rights to 644, and restart the device.

โš ๏ธ Warning: Incorrect editing of system files can lead to bootloop ( looped boot!

What if MIUI does not start after editing?
If the smartphone does not boot after changing system files, try: 1. log into TWRP and restore the backup. 2. Fastboot MIUI (instructions for 4PDA). 3. Reset the settings to factory (loss of data!).

Alternative solutions: covers, settings of uniformity

If the software methods didnโ€™t help, try to get around the problem physically:

1.Use a case with the correct neckline

Many Redmi Note cases close the bottom speaker, which causes false positives.

  • ๐Ÿ“ The cutout under the speaker should be wider than 5 mm from the edges;
  • ๐Ÿ•ณ๏ธ The microphone holes should not be closed;
  • ๐Ÿ›ก๏ธ Avoid covers with ears on the sides โ€“ they often block sensors.

2.Setting uniformity (EQ) to reduce load

Sometimes the warning comes from overloading the speakers at high frequencies.

  1. Open Settings โ†’ Sound and vibration โ†’ Uniformity
  2. Select the preset "Basy" or "Voice" - they reduce the load on the high-frequency speaker;
  3. Reduce the volume by 1-2 divisions from the maximum.

3. disabling stereo speakers (for some models)

On the Redmi Note 10 Pro and Note 11 Pro, you can turn off the second speaker via the engineering menu:

##36446337##

From the menu, select Hardware Testing โ†’ Audio โ†’ Speaker Test and deactivate the second speaker, which will lower the sound quality, but remove the warning.

๐Ÿ’ก

If the engineering menu doesn't open, try the code ##4636## โ†’ Audio โ†’ Dynamic Type and select Mono.

Table: Methods compatible with Redmi Note models

ModelCleaning the sensorADB-teamEditing by miui.xmlCase with a neckline
Redmi Note 10 / 10Sโœ… Yes.โœ… Yes.โš ๏ธ Requires root.โœ… Yes.
Redmi Note 10 Pro / 10 Pro Maxโœ… Yes.โŒ No (bug) MIUI 13)โœ… Yes.โœ… Yes.
Redmi Note 11 / 11Sโœ… Yes.โœ… Yes.โš ๏ธ Requires root.โœ… Yes.
Redmi Note 12 / 12 Proโœ… Yes.โœ… Yes (MIUI 14)โœ… Yes.โŒ No (sensor elsewhere)

โš ๏ธ Note: On the Redmi Note 12 series, the proximity sensor is different, so physical cleaning may not help. ADB-method MIUI last-minute.

What to do if nothing helps

If you've tried all of these, but the "Do not close the speaker area" warning keeps coming up, it's probably a hardware malfunction.

1. Diagnostics of the proximity sensor

Check the sensor with the test code:

##6484##

In the Manual Test โ†’ Proximity Sensor menu, cover the sensor with your hand - the value should change from 5 to 0. If there is no reaction, the sensor is defective.

2. Testing of the plume dynamics

After falls or repairs, the plume connecting the speaker to the motherboard could have been damaged.

  • ๐Ÿ”Š The sound disappears when the phone is tilted;
  • ๐Ÿ“ต The warning appears even when the speaker is open;
  • ๐Ÿ”ง In the service center diagnosed with โ€œbreakdown of contactsยป.

3.Update or rollback MIUI

Some versions of MIUI (e.g., 13.0.4โ€“13.0.6 for the Redmi Note 11) had a massive false positive bug.

  • ๐Ÿ”„ Update. MIUI until the last stable version;
  • ๐Ÿ”™ Reverse to the previous firmware (if the bug appeared after the update).

If the warranty is still valid, contact the Xiaomi service center. SPEAKER_BLOCKED You should replace the sensor or plume free of charge.

๐Ÿ’ก

Before visiting the service, make a backup copy of the data - a reset to factory settings may be required for diagnosis.

FAQ: Frequent questions about the "Don't close the speaker area" warning

Can the proximity sensor be completely turned off?
The sensor is not only responsible for the dynamic warning, but also for the: ๐Ÿ“ž Automatically switching off the screen during a call (when you hold your phone to your ear); ๐Ÿ”ฆ Adjusting brightness when approaching the face; ๐ŸŽฎ Turning off the sensors in games (so that the palm doesn't interfere with the control), you only have to turn it off if you're willing to put up with the inconvenience. ADB: adb shell settings put global proximity_sensor_disabled 1
Why does the warning appear only in some applications?
Some apps (e.g. YouTube, TikTok, WhatsApp) use their own speaker protection algorithms. If the alert only occurs in them, try: Clear the app cache; Turn off uniformity (EQ) in the audio settings; Use external speakers or headphones.
Will the reset to factory settings help?
Resetting helps if the problem is caused by a setting conflict after updating or installing third-party applications: ๐Ÿงน The contaminated sensor, no; ๐Ÿ”ง The damaged plume, no; ๐Ÿ“ฑ No hardware defect. Save the data before reset, as all files will be deleted.
Can I turn off the warning via TWRP?
Yes, if you have customized recaps (TWRP) installed. To do this: Download the Disable Speaker Warning module for Magisk; Install it via TWRP; Reboot the device. For links to modules, look for the 4PDA or XDA-Developers forums (make sure the module is compatible with your model!).
Why did this warning appear after the screen was replaced?
Most likely, when replacing the screen: ๐Ÿ”Œ The approach sensor plume was damaged; ๐Ÿ“ฑ Incorrectly connected flexible cable speaker; ๐Ÿ› ๏ธ Used a non-original screen without a sensor. Go back to the service and ask to check the connection of the plumes. If the sensor is missing, it can be turned off programmatically (see methods above).