Owners of Xiaomi, Redmi and POCO smartphones often face the need to monitor the status of the battery. Understanding how often and at what time the charge occurred, allows you to identify anomalies in the operation of the device or confirm the wear of the energy storage. The standard MIUI or HyperOS interface does not always provide a detailed log of events in a user-friendly way, hiding technical information in the depth of system reports.
But there are a few proven ways to access this data: you can use built-in engineering menus, analyze system logs through ADB, or use third-party utilities that read information directly from the power controller. Each method has its advantages: some give instant results, others allow you to track history over a long period of time.
In this article, we'll take a look at all the diagnostic tools that we've been working on, and you'll learn to read hidden codes, interpret energy flow charts, and determine the actual number of recharge cycles, which will not only help you understand when your phone was charging, but also extend its life by adjusting your usage habits.
Analysis of statistics through system settings
The most accessible, though not always detailed, way is through the built-in consumption analyzer. Android, on top of which the MIUI shell runs, keeps a record of battery life since the last full charge. To get into this section, you need to go to Settings β Battery and Performance. Here's a graph showing the periods of activity and downtime.
Notice the time stamps on the graph. Sharp charge surges or long periods of connection to the network, displayed as no consumption, can indicate charging time. If you see that at 3 a.m. the battery percentage did not change or rose sharply, then the device was connected to the power source. Use statistics are reset after each full discharge cycle to 0% or after rebooting, so the data is only relevant for the current session.
β οΈ Attention: Standard schedule in MIUI It only shows consumption, not the charging process directly. Long, flat sections of the graph can mean both charging and deep (standby mode), so the method requires logical analysis of the time of day.
For a deeper dive, you should explore the section βBattery consumption by application.β If there is no active consumption at a certain time (for example, at night), but the phone does not discharge, this is an indirect sign of a network connection. Modern Xiaomi algorithms can also display the status βchargedβ in the battery widget on the desktop, if the function is enabled in the interface settings.
Use of the engineering menu and USSD-code
A more professional approach to diagnostics involves the use of hidden system menus. The MIUI Engineering menu contains sections dedicated to testing hardware components, including the battery. The code ##6484## or ##4636## is usually used to enter the testing menu. Depending on the firmware version and device model (for example, Redmi Note 12 or Xiaomi 13), the command set may vary.
Once you enter the code, you'll see a list of tests, and you'll be interested in the Battery Info or Version section, and you'll find parameters like current voltage, temperature, and, importantly, connection status. While the exact time of the last charge may not be displayed as a calendar here, you'll see a Cycle Count and current health status.
- π Cycle Count β shows how many full charge-discharge cycles the battery has gone through.
- β‘ Current Status β shows whether the phone is currently charging or disconnected.
- π‘οΈ Temperature β critical parameter; high temperature may indicate recent fast charging.
- π Voltage - battery voltage, which helps to assess the degree of wear.
Some firmware versions have a tab called Battery Use available via the #4636## menu, which may provide a more detailed history of events, including the time of the last USB connection, but this functionality is often cut down by manufacturers in global versions of the software.
π‘
If the ##4636### code doesn't work, try typing it through the Phone app or downloading a third-party dialer. On some devices, access to the engineering menu is blocked by the operator.
Detailed diagnostics through ADB and system logs
For users who need accuracy up to a second, the only reliable way is to analyze system logs through the debugging interface. ADB (Android Debug Bridge. This method allows you to pull raw data from the system log, where you record every connection and power outage event. You'll need a computer, USB-cable and installed driver Xiaomi USB Driver.
First, activate the developer mode. Go to Settings β About Phone and press the build number seven times (MIUI Version). Then in the advanced settings, turn on βDebugging USB.β Connect your smartphone to your PC and execute the command to read the log (battery):
adb logcat -b events | grep batteryIn the event stream, you'll look for lines that contain charging, discharging, or plug tags. Android records these events in real time. By analyzing the timestamps in the log, you can reconstruct the exact connection chronology for the last hours or days until the log was overwritten by new events.
β οΈ Attention: Working with ADB Do not turn off the cable while reading logs, and do not try to enter system modification commands if you are not qualified. Mistakes can lead to unstable software operation.
An alternative for advanced users is to use the dumpsys batterystats command, which produces a huge array of battery status data, including charging history broken down by charge level, and the output can be filtered by saving it to a text file:
adb shell dumpsys batterystats > battery_log.txtOnce you open the file, you will find the Discharge steps and Charge steps, which show the time intervals for battery change, the most comprehensive source of technical information available without root rights.
What are root rights and do they need them?
Third-party monitoring applications
If you think it's too hard to do code and command line work, you'll find special applications in the Google Play Store that help you, like AccuBattery, Battery Charge Limit, or GSam Battery Monitor, that can read system data and present it in a graphical way, and they automatically log the moment a charger is connected.
AccuBattery, for example, starts to keep its own statistics after installation, and in the Charging section, it will show how many times and how long the phone has been connected to the network since the application was installed, and it also calculates the actual battery capacity in mAh, comparing it with the manufacturer's declared capacity.
- π Detailed statistics β shows the charging speed in mA for each session.
- π Notifications β you can adjust the signal when you reach 80% or 100% charge.
- π Discharge history β shows which applications have the most energy between charges.
- πΎ Data export β the ability to upload the report to CSV PC-analysis.
It's important to understand that third-party applications don't have access to the history they've accumulated before they're installed. They only start collecting data from the moment they first run. So if you need to know when the phone was charging yesterday or the day before yesterday, this method won't work unless the application was installed in advance.
π‘
Third-party applications are the best choice for continuous monitoring of battery health in the future, but are useless for retrospective analysis of past events.
Decoding of charging and wear cycles
The concept of a charging cycle is often confused with the number of connections to the outlet. One full cycle is a consumption of 100% of the battery capacity, which does not necessarily happen at a time. For example, if you discharged the phone from 100% to 50%, charged it back, and then again discharged it to 50%, this will total one cycle. For lithium polymer batteries used in Xiaomi, the number of cycles directly affects the residual capacity.
The average life of a modern battery is about 500-800 full cycles, and then the capacity drops to about 80 percent of the original one, and knowing the approximate date of purchase and the frequency of charge, you can assume the current state of the battery, and if you've been charging your phone every day for two years, the cycle counter will be close to the limit.
Below is a table of approximate correspondence of cycles and battery status:
| Number of cycles | Residual receptacle | Recommendation |
|---|---|---|
| 0 - 300 | 95-100% | It's in good condition, normal. |
| 300 - 500 | 85-95% | Normal wear, you can turn on charging optimization. |
| 500 - 800 | 75-85% | A noticeable decrease in working time, you should avoid fast charging. |
| 800+ | Less than 75% | Replacement of the battery is recommended for comfort of use. |
You can check your current health status through the same engineering codes or applications, and if the system says "Good," there's no critical error, and if you have "Bad" or "Overheat" status, you need to be diagnosed.
βοΈ Checklist
Charging optimization function in MIUI and HyperOS
Xiaomiβs modern shells are equipped with intelligent algorithms that analyze your charging habits. Learns your routine. If you normally put your phone on overnight charging, the system will charge it up to 80%, stop the process, and complete charging to 100% just before you wake up.
To check if this feature is active and how it affects the schedule, go to Settings β Battery β Battery Protection. You can see the restrictions settings here. Enabling the βCharge Limit to 80%β feature (available on some new models) forcibly stops charging at this level, which significantly extends the life of battery chemistry, although it reduces autonomy.
If you notice that your phone hangs 80 percent at night and then charges abruptly in the morning, that's a routine optimization job. It's going to look like intermittent charging in the system logs. Understanding this mechanism is important so that you don't think there's anything wrong with the device or the charger.
β οΈ Attention: The optimization algorithm doesn't work right away. 1-2 weeks of regular use with the same sleep pattern to learn how to predict your charging time.