When the screen of the Xiaomi Redmi smartphone does not go out when it is brought to the ear, it is one of the most common and annoying problems of owners of budget and medium-budget devices, which leads to accidental cheek pressing, resetting calls or, conversely, turning on the speakerphone at the most inopportune moment, most often the reason lies not in a physical failure, but in a software calibration failure or banal contamination of the upper speaker area.
In this article, we will take a look at all possible diagnostic and troubleshooting methods, from simple actions that any user can perform to more complex manipulations of the engineering menu, learn how to properly clean the touch zone, recalibrate through hidden MIUI settings and determine whether your device needs intervention in the service center.
═══ Section 1: Causes of Necrorective Work and Primary Diagnostics ═══
The main reason for the proximity sensor failure on Xiaomi smartphones is a software error that occurs after updating the operating system or installing third-party applications that conflict with system processes. Often the failure occurs because the system misinterprets the data coming from the sensor, believing the object is present where it is not, or ignoring the real obstacle.
The second most common cause is physical pollution, where there's a tiny sensor window at the top of the screen, usually above the speaker, and a protective glass that's broken in technology or tight covers can block infrared radiation, making it impossible for the module to work, and even a thin layer of fat or dust can distort the readings.
⚠️ Warning: Before any manipulations, make sure that the protective glass is glued flat and does not overlap the top of the display. Cheap glass with a black border often closes the sensor, in which case only the replacement of the accessory will help.
To test the functionality of the module, you don't have to go into complex settings right away, you just need to turn on speaker while you're calling and hold your hand to the top of the screen, and if the indicator in the call menu reacts by changing color or condition, then the sensor is physically healthy, and the problem lies in the software logic of the signal processing.
═══ Section 2: Cleaning and checking of physical factors ═══
Before you start software resets, you need to eliminate the banal pollution. Wash the top of the display carefully with a soft microfiber moistened with a special tool for screens. Pay special attention to the areas above the speaker, where the infrared sensor is usually hidden.
If you have a safety glass on the device, look at the edges of the glass, and it's often the top of the glass that gets unstuck, creating an air cushion that scatters the light of the sensor, and in those cases, even a perfectly functioning module will give the system the wrong data.
- 🧼 Carefully degrease the screen surface in the upper third of the device with an alcohol napkin.
- 📱 Remove the case if its sides go to the front panel of the smartphone.
- 🔍 Check for cracks or chips in the upper speaker area.
It's also worth checking whether the ambient temperature affects the sensor, and in extreme cold or extreme heat, the materials that make up the screen and the protective glass can change their transparency properties for infrared radiation, which temporarily disrupts the function.
💡
Try pressing your finger tightly against the sensor area for a few seconds during the call, and if the screen goes out but immediately lights up while the finger is still pressed, then the problem is calibrating the response distance.
═══ Section 3: Calibration through Engineering Menu CIT ═══
The most effective way to fix a software failure is to recalibrate through the CIT (Customer Interface Test) engineering menu, which is built into the MIUI shell and allows you to directly interact with hardware modules, bypassing standard system settings.
To enter the menu, you need to open the standard Phone app and type a special code. Once you enter the last digit, the menu will open automatically. Find the item "Proximity Sensor" or "Proximation Sensor" in the list. Before starting the test, remove all protective films from the screen.
##6484##In the window that opens, you'll see the current sensor readings. Close your hand on the top of the screen, which should change (usually from 5.0 to 0.0 or vice versa, depending on the model). If you have a reaction, press Calibrate. It's important to keep your hand tightly pressed during the process, and then remove it at the command of the system.
⚠️ Warning: Do not interrupt the calibration process until you have received a successful completion report. If the calibration did not pass the first time, repeat the procedure. 2-3 The sensor can “remember” the wrong reference value.
After successful calibration, the system will give a notification. Be sure to restart the device so that the new parameters are stored in non-volatile memory and will take effect for all applications, including the standard “bell ringer” and instant messengers.
☑️ Calibration checklist
═══ Section 4: In-app TELEPHONE EXPLAINTS ═══
Modern versions of the MIUI shell and the Google Phone app, which is often installed by default on global versions of Xiaomi Redmi, have custom settings that can override system settings. If calibration didn’t help, it’s worth checking the internal settings of the call app itself.
Open the Phone app, click three dots in the corner of the screen, and select Settings. Find the Incoming Calls section. There may be an option called Approximation Sensor. Make sure the switch is active. In some firmware versions, this setting is hidden and only accessible through a hidden menu.
- 📞 Go to the settings of the application “Phone” through a menu of three points.
- ⚙️ Go to the section “Incoming calls” or “Call settings».
- 🔘 Check the presence and status of the proximity sensor switch.
If you use a third-party caller (like Truecaller or Go Contacts), the system sensor may be ignored, in which case it is recommended to temporarily return to the standard application to check if the problem persists, which will help to localize the source of the conflict.
Hidden settings in Google Phone
═══ Section 5: Code and Action Table for Different Models ═══
Different Xiaomi and Redmi models may have slight differences in the codes for accessing the engineering menu or in the behavior of the sensor. Below is a table that will help you navigate depending on the version of your operating system and device model.
| Model/Series | Access code | The way is on the menu | Feature |
|---|---|---|---|
| Redmi Note 8/9/10 | ##6484## | Single Item Test → Proximity | Frequent failure after MIUI 12/13 update |
| Xiaomi Mi 9/10/11 | ##6484## | CIT → Proximity Sensor | It requires a tight arm clamping. |
| POCO X3/X4/N3 | ##6484## | Hardware Test → Proximity | Sensitive to protective glass |
| Redmi 9A/9C/10A | ##6484## | Version → CIT → Sensor | Low sensitivity, multiple calibration is required |
Note that on some devices with very new Android versions (12, 13, 14), access to the engineering menu may be restricted by the manufacturer for security reasons.If the code doesn't work, try entering it in Xiaomi's Phone app, not Google's.
If none of the codes work, you can use the Engineering Mode app from the Play Market, which provides a graphical interface to access the same features that are hidden behind the software. USSD-It works in places where standard methods are powerless.
💡
Code ##6484## is universal for Xiaomi devices, but if it doesn’t work, use third-party apps to access the code. CIT-menu.
═══ Section 6: Complex Methods and Disposal of Attacks ═══
When simple methods fail, more radical measures are needed: Resetting all phone settings to factory-based (Hard Reset) often eliminates deep software conflicts that have accumulated in the system over time, but make sure to back up all important data before you do so, as it will be completely deleted.
There is also a method of disabling the sensor through ADB-team, but it requires a computer and debugging skills USB. This is a way for power users who understand what they're doing. Commands are typed into a console on a PC when a smartphone is connected.
adb shell settings put system proximity_on_call 0This command forcibly disables the sensor check during a call, and the screen will stop going out altogether, which will solve the problem of random taps, but will require getting used to manually controlling the screen during a conversation, a temporary solution that allows you to comfortably use the phone before visiting the service.
- 💾 Make a full backup of contacts and photos before resetting.
- 🔄 Reset via the menu "Extended settings» → «Recovery and discharge».
- 📲 Check the sensor immediately after the initial system setup, before installing applications.
⚠️ Note: If the problem persists after a complete system reset and only the original updates are installed, the probability of hardware failure is 95.
═══ Section 7: Ambient issues and responses ═══
If software methods, calibration and resets didn’t work, it’s a physical breakdown. On Xiaomi Redmi smartphones, the proximity sensor is often made as a separate plume or soldered into the top of the display module. In budget models, it can fail due to voltage surges or moisture.
A common problem is that the sensor plume is moving away from the motherboard, which can happen after the phone falls, or even just because of the time and vibration of the speaker, and in the service center, the wizard will open the device and reconnect the contact, which often solves the problem instantly.
Rarely, replacement of the sensor itself or the entire display unit assembly is required if the sensor is integrated into the screen array, and the cost of such repairs varies depending on the model, but for most Redmi series devices it remains affordable.
Don't try to disassemble your smartphone yourself unless you have the experience and tools.The top of the case is often glued, and a careless opening can damage the plumes of the display or battery, which will turn minor repairs into an expensive housing replacement.
═══ FAQ: Frequent questions ═══