Xiaomi and Redmi smartphone owners often encounter an intrusive system message that blocks the device from working normally after changing the screen or protective glass. This is the result of a proximity sensor hidden under the top end of the display. MIUI aggressively protects this functionality, considering any overlap of the sensor as a foreign object or defective film.
It is impossible to ignore this message because it blocks access to the desktop and menu. Sensor calibration is the first step that official services offer, but in-house interventions are often required. In this article, we will examine the technical reasons for blocking and provide working algorithms for different versions of the firmware.
Now, the problem is not software failure, but the physical design of modern screens. Manufacturers are trying to minimize the frames by hiding the light and proximity sensors directly under the matrix or in a narrow strip at the top of the case. OLED-The panels often don't have a separate sensor cutout, relying on software to interpret the reflection of light through the pixels, which is why even high-quality black-framed glass can cause hardware conflict.
Reasons for System Warning
The main reason is because the approach sensor is operating algorithmically, and it emits infrared light and reads the reflection of the light, and if there is an obstacle in the path of the beam (thick glass, wrong sticker, contamination), the system treats it as bringing the phone to the ear or having an object, and as a result, it blocks the touchscreen at the top of the screen and displays a warning.
And the quality of the installed parts also has an impact. Cheap copies of displays often have misaligned holes or lack of transparency in the sensor area. The phone's engineering menu reads the readings in real time, and if the values go beyond the permissible limits, protection works, and this is especially true for models with subscreen sensors, where every micron error in the assembly is important.
Also worth noting is the role of software: In MIUI updates, calibration algorithms are getting stricter. What worked on Android 10 may cause an error on Android 12 or 13. The system may require recalibration after each setup reset or firmware reflash if the hardware doesn't perfectly match the factory reference values.
Diagnostics of the status of the proximity sensor
Before we start taking any radical action, we need to know exactly what the sensor is in, and to do that, there's a hidden engineering menu in the MIUI shell that's available without root rights, and it allows us to see raw sensor data and see if the phone sees an obstacle.
To enter Diagnostic mode, use the standard command set in the Phone app. Enter the code ##6484## or ##4636##. In the menu that opens, select Proximity sensor or Approximation Sensor. Here you will see two values: distance in centimeters and status (Near/Far).
If the values change and the status switches between Near (close) and Far (far), the hardware is in good working order, and the problem is probably calibration or thickness of the security glass, and if the values don't change or are constantly showing "close" even when there's nothing in front of the screen, you'll need a software reset or physical cleaning.
βοΈ Diagnosis before repair
Software calibration through the engineering menu
The safest and most effective method of fixing an error is forced calibration, which forces the system to overwrite the reference values of the "clean" state of the sensor, which helps in 90% of cases if the sensor is physically fit.
To start, open the Phone app and dial ##6484##. In the test list, look for the Proximity sensor section. You'll see a screen with instructions and two buttons. First remove all items from the top of the smartphone, then press Calibrate or Start.
The system will ask you to close the sensor with your hand. Do this, wait for the vibration or the sound signal, then remove your hand. If the Pass message appears in the status bar, then the calibration is successful. After that, you need to completely restart the device to take effect. Don't miss the reboot, because temporary files can cache old values.
β οΈ Warning: If status does not change to Pass after calibration, don't keep trying indefinitely, which may indicate physical damage to the plume or glue sticking the sensor.
Using ADB to reset sensor settings
In cases where the standard menu doesn't work, you can use USB debugging. This method requires a computer connection and ADB drivers. It allows you to send a command to reset the sensor configuration at a deeper level than normal calibration.
Connect your smartphone to your PC, turn on debugging mode in the Developer menu, and start the command line. Enter a command to check the connection, and then reset. Often, the command that forces the sensor to activate helps:
adb shell settings put system proximity_sensor_use_enabled 1Some firmware versions require you to reset specific settings through the SQLite settings database, but this requires root rights. It's safer for ordinary users to use the Sensor Service Restart Command if it's available in your version of Android. After completing the commands, be sure to turn off and turn on the phone.
What if the ADB canβt see the phone?
Physical Causes and Protection Modification
If software methods are powerless, the reason lies in the physical overlap. Often users buy protective glasses with a black frame that is wider than the original, which can partially or completely overlap the area of operation of the infrared emitter.
In this situation, it helps to carefully modify the protective glass, using a thin drill or needle, you can expand the cutout in the black area of the glass above the speaker, you need to do this with extreme care so as not to damage the display itself, and it also helps to remove a thick case that can press on the edges of the screen.
Another common problem is the residue of glue or dirt in the speaker's grid. When disassembling the phone, the glue could get into the sensor hole. Cleaning this area with alcohol or a special cleaner often returns to work. Ultrasonic cleaning of the speaker can also help to knock dust out of the depths of the channel.
| Method of decision | Efficiency | Risk of damage | Essential tools |
|---|---|---|---|
| Calibration on the menu | Tall. | No. | No. |
| Removal of the protective glass | Medium | Low. | Fryer, sucker. |
| ADB teams | Medium | Low. | PC, cable |
| Replacement of the plume | Tall. | High-pitched | Screwdrivers, new plume. |
Specifics of working in safe mode
Sometimes, third-party applications that intercept sensor control (such as call recording or gesture control apps) cause conflict. To rule out this factor, launch your smartphone in safe mode.
Press the off button and then the Turn off icon on the screen until you have a suggestion to go to Safe Mode. If the "Do not close the speaker area" error disappears in this mode, then one of the installed applications is to blame. Delete the recently installed programs one by one, checking the result.
In Safe Mode, you can also try to calibrate again, sometimes background processes block access to the sensor for calibration, and a clean environment allows you to complete the procedure successfully. Once the problem is fixed, just restart the phone as usual.
π‘
When installing a new protective glass, use a special template frame for precise positioning. A 1 mm shift can block the proximity sensor.
Frequent Questions and Answers (FAQ)
Will resetting to factory settings help?
Can you just turn off the proximity sensor?
Why did the error occur without a screen replacement?
Does the temperature affect the sensor?
π‘
If no software method has helped, the problem is likely a physical defect in the sensor plume or the display module itself, which requires replacement of the spare part.