Xiaomi has just launched the rollout of the MIUI 12.5 Enhanced update on the Poco F3s. Unfortunately, this version of the operating system causes random reboots on the mid-range smartphone.
In August, Xiaomi announced a new update named “MIUI 12.5 Enhanced”. This new version of the Android interface brings several improvements compared to the MIUI 12.5 update. Among the optimizations announced by Xiaomi is a reduction in the consumption of background RAM, energy and internal storage space allocated to the operating system. The firmware also corrects overheating issues encountered by some phones.
In the wake of the announcement, the Chinese giant launched update deployment on a handful of smartphones in its catalog. Soon after, Xiaomi pushed MIUI 12.5 Enhanced Edition on devices sold by its Indian subsidiary, Poco.
Read also: Xiaomi adds 3 GB of virtual RAM to the Mi 11, Mi 10 and Poco F3
Some Poco X3 restart in a loop
A few days ago, the firmware made its appearance on the Poco F3, a mid-range phone. Despite its many improvements, the MIUI 12.5 Enhanced update causes random reboots on some Poco X3. According to testimonials that appeared on the Poco support forums, on Reddit or on Twitter, the smartphone regularly turns off for no reason.
“The phone restarted after I paused a Youtube video. I went to do something and saw the MIUI boot logo on the screen ”, explains a user on the official Poco forum.
According to some accounts, the Poco F3 sometimes restarts in fastboot mode. This is a mode in which you can launch your phone, usually by starting it up while holding down the “Volume Down” key, in order to write data directly to the flash memory of the device. Apparently, a protocol called “framework” is at the origin of these untimely restarts.
For now, Xiaomi has not yet announced the arrival of a patch. While waiting for the firm to propose a patch, we advise you to do not install MIUI 12.5 Enhanced update on your Poco F3. We will tell you more as soon as possible. While waiting for more information, feel free to give your opinion on this bug in the comments below.