If you've ever looked at the memory settings of your Xiaomi smartphone, you've probably noticed a strange item called a log buffer, which takes anywhere from a few megabytes to hundreds of megabytes, but what is it and can it be removed? In this article, we'll go into detail about why you need a log buffer, how it affects your phone, and what happens if you clean it.
Many users mistakenly believe that the log buffer is just a βjunk fileβ that can be deleted, but it is actually a system component that stores debugging information about how Android and MIUI work. Without it, it becomes almost impossible to diagnose crashes, but the buffer can grow to an unnecessarily large size, especially on devices with custom firmware or after frequent use of the developer mode.
In this article, you will find not only the theoretical part, but also practical instructions: how to safely clean the magazine buffer when it is really necessary, and what to do if after cleaning problems arise. POCO F3) The magazine buffer takes up much more space than the others.
What is a magazine buffer and why is it needed?
Log buffer is a special memory area where Android and the MIUI shell store logs of system events.
- π Starting and stopping applications (including crashes and forced closures)
- π± Iron: processor, memory, battery, sensors
- π Network activity: Wi-Fi connections, mobile network, Bluetooth
- π§ System errors and preventable critical failures
- π Software updates and configuration changes
These logs are primarily used for debugging. When a phone is unstable (like spontaneously restarting or "lagging"), Xiaomi engineers or custom firmware developers analyze the log buffer to find the cause of the problem, and without that data, diagnostics becomes guesswork.
On most smartphones, the magazine buffer takes from 5-20 MB, but on some devices (especially with an unlocked bootloader or custom recavator), its size can reach 500 MB or more (ADB Developer Options: The system starts recording advanced logs that are usually hidden from the user.
Where is the magazine buffer on Xiaomi and how to find it?
Unlike a regular app cache, the log buffer doesn't appear in the standard file manager, so you need to go to the memory settings to see it:
- Open Settings β Memory (or Settings β Storage on new versions of MIUI).
- Scroll down to the Other Files or System Data section.
- Tap on the item Buffer log (may be called Log Buffer or System Logs).
On some firmware (e.g. MIUI Global or MIUI China), this item may be hidden, in which case it can be found through the developer mode:
- Activate Developer Options (7 times tap the MIUI version in Settings β About Phone).
- Go back to the Settings β Additional β Developer settings.
- Find the Log Warehouse or Log Buffer item.
If you use custom recaps (TWRP), the log buffer can appear as a separate section in the Mount or Advanced menu, usually called /dev/log or /data/log.
Why can a magazine buffer take up hundreds of megabytes?
Can I clean the magazine buffer and what happens if I do it?
Yes, the log buffer can be cleaned, but with reservations. Unlike the application cache, removing it won't free up a lot of space permanently -- the system will just start writing new logs on top of old ones.
- π Buffer takes over >200 MB and prevents system updates (lack of space in the section) /data).
- π The phone is unstable after firmware or reset settings.
- π οΈ You are preparing your device for sale and want to remove all traces of use.
- π‘ Before sending the phone to the service (so that the logs do not interfere with the diagnosis).
What happens after cleaning:
- β 5-500 MB of memory (depending on buffer size).
- β οΈ Disappeared logs of recent failures β if the phone is bugged, it will be more difficult to diagnose the cause.
- β οΈ Some system applications (such as Mi Fit or Mi Home) can restart once.
- β The application cache will not be deleted β this is a separate operation.
β οΈ Note: If you clear the log buffer before contacting the Xiaomi service center, tell the wizard. Without the logs, the diagnosis will take longer, and you may be denied warranty repairs because of "insufficient data for analysis".
How to Clean a Magazine Buffer on Xiaomi: 3 Ways
There are several ways to clean up the log buffer β from the simplest (through settings) to the most advanced (through settings). ADB). Choose the method according to your model and version MIUI.
Method 1: Using standard settings (without root)
This is the safest method that works on most devices:
- Open Settings β Memory β Buffer of the magazine.
- Then, put it in the sleeve (or remove).
- Confirm the action.
On some firmware (MIUI 12.5+), this item may be hidden. In this case, use method 2.
Method 2: Recovery mode (Recovery)
If the log buffer is not cleared through the settings, try doing so through stock Recovery:
- Turn off the phone.
- Press the Power button + Volume up to enter Recovery Mode.
- Select Wipe & Reset β Wipe Cache (on some versions of Advanced Wipe β Log Buffer).
- Confirm the cleanup and restart the device.
β οΈ Note: If you have a custom recap (TWRP), Do not use the Wipe option. β Advanced Wipe β Log is unnecessary.This can cause system applications to crash if they depend on logs to work.
Method 3: Through ADB (for advanced users)
If the first two methods did not work, you can clear the log buffer through the command line:
adb shell
su
logcat -c
rm -rf /data/log/*
rm -rf /dev/log/*This method requires an unlocked bootloader and root rights, and without them, commands won't work.
Make a backup copy of important data|Check the battery charge (>50%)|Disable two-factor authentication (if used)|Close all background applications|Make sure your phone is not connected to the PC.-->
Why the magazine buffer is filling up again quickly
Many users complain that after cleaning the log buffer grows back to its previous size in a few days, which is normal behavior of the system, but there are factors that speed up its filling:
| Reason. | How it manifests itself | Decision |
|---|---|---|
| Active use of ADB or Fastboot | Buffer grows by 50β100 MB/day | Disable USB debugging in Developer Settings |
| Brushing Firmware (LineageOS, Pixel Experience) | The buffer takes >300 MB continuously | Install the kernel with extended logging disabled |
| Frequent application failures | Logs are filled with error records | Update problematic apps or reset their settings |
| Developer mode is on. | Buffers grow even without active action | Disable unnecessary options in Developer Settings |
| Viruses or malware | Unknown processes are written in logs | Check your phone with an antivirus (Malwarebytes or Dr.Web) |
If the log buffer fills up too quickly (for example, 100 MB per hour), this may indicate a hardware problem, such as a memory module malfunction or driver conflict, in which case it is better to contact the service.
π‘
If you often clean the log buffer but it grows back, try disabling the extended logging via the adb shell setprop log.tag.DEBUG false command. This will reduce the amount of data being written, but may hide important debugging messages.
What to do if after cleaning the log buffer, the phone began to work worse
In rare cases, after cleaning the log buffer, problems may arise:
- π Spontaneous reboots (the system cannot write critical logs).
- π± Freezes when starting a camera or heavy apps.
- π Network problems (Wi-Fi or mobile internet not connected).
- π Fast battery discharge (the system is constantly trying to recover logs).
Here's what we can do:
- Reboot your phone β often this solves temporary crashes.
- Reset network settings (Settings) β SIM-maps and mobile networks β Resetting network settings).
- Clear the /data partition cache through the recavers (Wipe β Wipe Cache).
- Reverse to the previous version of MIUI if the problem has occurred after the update.
- Perform reset to factory settings (last resort).
β οΈ Warning: If after cleaning the log buffer, the phone stopped turning on or stuck on the logo MI, Don't try to stitch it yourself. This could be a sign of damage to the partition. /data. Contact the service center with an indication that you cleared logs before the crash.
π‘
If there was a major malfunction after cleaning the log buffer, it's probably not the logs that were the problem, but the system itself, and the logs were just masking it, and after cleaning it, it showed up, so you'd better back up and reflash the phone.
Xiaomi models, on which the magazine buffer behaves unusually
On some Xiaomi devices, the magazine buffer works differently than on most smartphones, due to the peculiarities of hardware or firmware.
| Model | Feature of the magazine buffer | Recommendations |
|---|---|---|
| Redmi Note 8 Pro | Buffer can take up to 1 GB due to conflict with the chip Mediatek Helio G90T | Update your firmware to MIUI 13+ or disable logging via ADB |
| POCO F3 / Redmi K40 | After upgrading to Android 12, the buffer wonβt be cleared through the settings | Use ADB or TWRP for cleaning |
| Xiaomi Mi 11 Ultra | The buffer is divided into two sections: /data/log and /persist/log. | Clean both sections through Fastboot |
| Redmi 9A / 9C | The log buffer is reset with each MIUI update. | Donβt clean it manually β the system will do it automatically. |
If you have one of these models, make sure to check the relevant information on forums (e.g. 4PDA or XDA Developers) before cleaning the log buffer.