Users of smartphones based on the operating system Android often encounter mysterious entries in the lists of running processes or discover hidden applications whose names mean nothing. One of these system utilities is Factorykit Test, which raises many questions among owners of devices from Xiaomi, Redmi i Poco. Many people mistakenly believe that this is a virus or third-party software, but this app is an integral part of the factory software.
The main purpose of this tool is to carry out in-depth diagnostics of the gadget’s hardware components immediately after assembly on the assembly line or in service centers. Factorykit Test is not an application for the average user and does not have a graphical interface in the usual sense, being launched through special engineering codes or ADB commands. Understanding the principles of operation of this utility will help you avoid accidentally resetting settings or activating unnecessary test modes that could affect on the stability of the device.
In this material we will analyze in detail the functionality of the hidden menu, consider the risks of independently interfering with the operation of system tests and answer the question of whether an ordinary user needs to worry about the presence of this process in memory smartphone. You will learn how factory testing differs from standard diagnostics and what capabilities are hidden from the owner's eyes.
⚠️ Attention: Making changes to system files or forcibly stopping critical processes via ADB can lead to unstable operation of the operating system. Use diagnostic tools only if you are completely confident in your actions.
Purpose and functions of Factorykit Test
The utility Factorykit Test is a comprehensive set of scripts and executable files integrated into the device firmware at the production stage. Its main task is to automate the functionality check of all physical modules of a smartphone: from the display and touchscreen to radio modules and light sensors. Unlike custom benchmarking applications, this tool has access to low-level hardware drivers.
Factory engineers use this app to quickly verify build quality. If any component fails (does not pass the test), the device is marked as defective. For the end user, the presence of an active process com.android.factorytest or similar names in the task manager usually means that the system periodically conducts background self-diagnosis or waits for commands from the service menu.
The app's functionality covers almost all aspects of the hardware. It can generate test images on the screen to check for dead pixels, emit audio signals of different frequencies to check speakers and microphones, and also activate a vibration motor. Moreover, the utility checks communication with base stations, the operation of the GPS module and even the calibration of the accelerometer.
- 📱 Checking the display matrix for dead pixels and backlight uniformity.
- 🔊 Testing the main and earpiece speakers, as well as microphones for sensitivity.
- 📡 Diagnostics of the operation of communication modules: Wi-Fi, Bluetooth, NFC and cellular networks.
- 🔋 Monitoring charging processes and calibrating the battery indicator.
How to launch the engineering diagnostic menu
Access to functionality Factorykit Test hidden from the average user to prevent accidental configuration changes. However, manufacturers leave special codes for entering the engineering menu (CIT - Customer Integration Test). To run diagnostics on Xiaomi and Redmi devices, the combination ##6484## or ##4636##.
The code is entered via a standard telephone dialer. As soon as you enter the last number or symbol, the normal dialer interface will disappear and a list of available tests will instantly open on the screen. It is important to understand that the set of codes may vary depending on the shell version MIUI or HyperOS, as well as on the specific processor model.
If standard codes do not work, the manufacturer may have blocked access to them for your regional firmware version. In this case, enthusiasts sometimes resort to using third-party hidden menu activator applications that emulate entering USSD commands, but this requires installing APK files from unverified sources, which carries security risks.
If the code does not work, try entering it in the Phone application without pressing the call button - the menu often opens automatically after entering the last character.
There is also a more complex access method via USB debugging and a computer. Using the platform Android Debug Bridge (ADB), you can send commands directly to the system. This method requires a connected PC and an installed device driver.
adb shell am start -n com.android.factorytest/.FactoryTestThis command forces the test activity to start if the package is installed and not removed by the system. However, on modern versions of Android with enhanced security, this method may be blocked by access rights.
Interface and main testing sections
After successfully entering the menu, a list, often called the CIT Menu, opens in front of the user. The interface here is spartan and utilitarian: it consists of a list of components with buttons to start checking each of them. The design does not follow the rules of Material Design and looks like a standard system window.
Each list item corresponds to a specific module. Clicking on an element runs a specific test. For example, by selecting "Touchpanel", you will enter a mode where you need to draw lines with your finger so that the system checks the responsiveness of the touchscreen over the entire area. Errors in the operation of the sensor will be immediately visible if the lines are interrupted or drawn with a delay.
Particular attention should be paid to sections related to wireless interfaces. Wi-Fi and Bluetooth tests may attempt to find available networks or devices. If an error appears in this section, this may indicate a hardware malfunction of the antenna or drivers, which requires contacting service.
| Menu section | Check function | Expected result |
|---|---|---|
| Version | Software information | Display firmware and kernel versions |
| Touchpanel | Touchscreen test | Drawing lines without breaks |
| Receiver | Checking the speaker | Clear sound without wheezing |
| Vibrator | Vibration motor test | Vibration when pressing a button |
| LED | Checking the indicators | The flash or LED lights up |
Some sections may require physical interaction: for example, the accelerometer test will ask you to place the phone on a flat surface, and the proximity sensor test will ask you to close the top of the screen hand. The system itself will tell you what actions need to be performed to pass the verification.
Differences between models and versions of Android
Implementation Factorykit Test highly depends on the device manufacturer and operating system version. On smartphones Samsung the analogue is a menu with a code #0#which has its own unique interface and set of tests. Devices from Huawei or Honor also use their own modifications of the engineering menu, accessible through code. ##2846579##.
With the release of new versions Android (12, 13, 14 and newer), Google is tightening security policies, limiting the access of applications and hidden menus to critical functions. This leads to the fact that some items in the old instructions may stop working or require additional confirmation of access rights.
⚠️ Attention: The interface and available codes may change depending on firmware updates. If the standard code does not work, this does not necessarily mean a breakdown; perhaps the manufacturer has changed the access method in the new version of the software.
Owners of custom firmware (LineageOS, Pixel Experience) may find that the factory test menu is completely cut out from the system. Developers of unofficial builds often remove these components to reduce the size of the system and increase privacy, since the average user rarely needs them.
Why may codes not work?
Manufacturers often change or block USSD codes in new firmware versions to prevent users from accidentally resetting settings. Also, codes may be specific to a certain region of sale of the device.
Safety and potential risks of use
Although the utility itself Factorykit Test is safe, incorrect use of its functions can lead to unpleasant consequences. For example, running a proximity sensor calibration test unnecessarily can reset the settings, causing the screen to stop going dark during a call.
The possibility of resetting data is also a danger. Some versions of the engineering menu have items marked “Format” or “Clear eMMC”, which initiate a full reset of the device to its factory state without warning. Pressing such buttons will result in the loss of all user data, photos and contacts.
In addition, constantly running heavy tests (for example, loop video recording or CPU stress test) on a device with a low battery charge can lead to deep discharge or overheating of components. Protection systems may not have time to react to a sudden load surge initiated by diagnostic software.
- 🚫 Do not press buttons labeled "Format", "Wipe" or "Clear" unless absolutely necessary.
- 🔋 Make sure the battery charge is above 50% before running long tests.
- 📉 Avoid interrupting the testing process to avoid damaging app sections.
If you do not understand the purpose of a particular button or parameter, it is better to refrain from experimenting. Incorrect actions may require flashing the device at a service center.
☑️ Check before entering the engineering menu
Frequently asked questions (FAQ)
Is it possible to remove Factorykit Test from your phone?
Technically, you can remove this system component only after receiving root access and using special utilities to freeze or remove system applications. However, this is strictly not recommended. Removing it can lead to errors in the system, endless reboots (bootloop) or the inability to diagnose in the event of a breakdown.
Why does the Factorykit Test process consume battery?
Under normal conditions, this process should not run in the background and consume energy. If you notice high battery drain associated with it, it may have failed and the test is stuck in the active state. In such a situation, rebooting the device will help. If the problem persists, you may need to reset the settings.
Does Factorykit Test affect the warranty?
Merely entering the engineering menu and viewing the parameters does not void the warranty. However, if as a result of your actions in this menu (for example, resetting calibration or flashing through hidden options) the device fails, the service center may refuse free repair, citing violation of operating rules.
Is there a difference between Factorykit Test and Recovery mode?
Yes, these are different tools. Recovery Mode is used to reset settings, install updates, and work with memory partitions. Factorykit Test is intended solely for checking the health of hardware components (hardware) and is not intended to manage the user's file system.
Factorykit Test is a powerful diagnostic tool that should remain in the hands of specialists. For an ordinary user, it is enough to know about its existence, but not to interfere with its work unnecessarily.