Xiaomi’s response to a startling “runaway” SU7 incident shows just how seriously it’s treating safety in its self-driving and remote-assist features. The company recently moved quickly to investigate after an owner reported that his SU7 rolled out of a parking spot on its own while no one was in the car. Surveillance footage from outside his apartment shows the sedan parked by the door before it begins to move; startled, the owner rushes outside to chase it.
Initially, the owner insisted he hadn’t touched his phone. After pulling detailed backend data and phone operation logs with the user’s consent, Xiaomi found that the vehicle received a remote parking assist command from an iPhone 15 Pro Max linked to the owner’s account. According to the company, the timestamps, operation logs, and the vehicle’s exit command matched perfectly, ruling out a vehicle quality defect. Xiaomi’s system includes a feature akin to a “summon” function that can maneuver the car into or out of a parking space. In this case, the instruction to exit was inadvertently triggered via the phone.
An early customer service misstep added confusion. During initial communication, a representative misread Apple’s internal device identifier and said the command came from an “iPhone 16,” when the logs actually indicated an iPhone 15 Pro Max (identifier iPhone 16,2). The owner, understandably skeptical, asked to review the full logs. After going through the data together, both sides confirmed the command originated from the iPhone 15 Pro Max. Xiaomi apologized for the miscommunication and clarified that activation of the parking assist feature requires close-range Bluetooth proximity to the phone, which was met at the time of the incident.
While the outcome points to an accidental phone input rather than a malfunctioning car, the episode raises a broader issue: how to prevent unintended activation of remote driving and parking features, especially when no one is in or around the vehicle. It has sparked discussion about adding stronger safeguards and clearer user feedback to reduce the risk of accidental triggers.
The company has already been under intense scrutiny after issuing a recall linked to a rare driving scenario that was not originally covered in its ADAS testing and was associated with a fatal crash. Against that backdrop, this parking incident underscores how complex human-device interactions can be—and why layered safety checks matter just as much as the underlying autonomy.
What SU7 owners and EV drivers can do right now
– Review phone and app permissions for remote vehicle control features.
– Use available confirmation prompts or “press and hold” actions to execute remote commands, if supported.
– Keep the vehicle’s software and the companion app up to date for the latest safety improvements.
– Be mindful of Bluetooth proximity; if your phone is within range, an inadvertent touch could send a command.
– Consider disabling remote parking or summon features when you don’t plan to use them, if the app allows.
As automakers converge smartphones and cars more tightly, tiny UI choices—like how long a button must be pressed, or how clearly a command is confirmed—can have outsized safety consequences. Xiaomi’s quick investigation, data transparency with the owner, and acknowledgment of the customer service error are positive steps. The next crucial step across the industry is making accidental remote activation much harder, without sacrificing the convenience that drivers expect from modern EVs.
