Xiaomi mobiles could start to complain if you have replaced their battery without using an authorized supplier, at least in China. This is clear from the APK of the Xiaomi Mi Security app, which includes a warning message when it detects an unofficial battery, as they have discovered in XDA.
Xiaomi’s security application prepares a warning when it detects that the terminal battery is not official, in which case loading speed is reduced not being able to guarantee its security.
Original battery or slower charge
{“videoId”: “x81mnrg”, “autoplay”: true, “title”: “Xiaomi Hypercharge, Xiaomi’s 200W fast charge”}
Over time, cell phone batteries lose capacity. Those who extend the life of their mobiles for a few years can make it more bearable by replacing their battery. Those who do without going through the official Xiaomi technical service They may end up being a surprise, at least in China.
According to XDA investigations, Xiaomi’s security application can detect if a Xiaomi Mi 9, Wed 10 or Mi 10 Pro includes a non-genuine battery. This detection is currently only active in China, although its text is translated into English, so it cannot be ruled out that it could be extended to other more advanced regions.
Upon detection, a message is displayed stating that the terminal battery appears to be unauthorized, so load capacity will be reduced, remembering to Apple from a couple of years ago.
Of course, the message gives good reasons for this limitation, the system cannot guarantee that an unknown battery supports the fast charging of the terminal, which could lead to bulging, overheating and, in the worst case, it could catch fire.
This is especially relevant if we take into account that terminals such as the Xiaomi Mi 10 Pro supports 65W fast charging, while other recent releases such as the Xiaomi Mix 4 arrive at 120W load. That’s a lot of watts to throw without guarantees to an unknown battery.
Via | XDA
–
The news
Original battery or slower charge: thus the notice that Xiaomi prepares for its mobiles in China
was originally published in
Engadget Android
by
Ivan Ramirez
.
