EV Risk Index logo EV Risk Index

Volvo / Polestar AAOS rearview camera FMVSS 111 software recall

Volvo / Polestar AAOS-based vehicles (EX30, EX40, EX90, XC40 EV, C40, others) · Model years 2022–2026 · Updated 2026-05-05

Manufacturer
Volvo / Polestar
Model
AAOS-based vehicles (EX30, EX40, EX90, XC40 EV, C40, others)
Years affected
2022–2026
Risk type
Software / visibility / FMVSS 111 violation
Issue
NHTSA campaign 25V250 (April 2025) covers Volvo vehicles built on the Android Automotive Operating System (AAOS) infotainment platform — including 2025 EX30, EX40, EX90, and other Volvo models. Software defects may cause the rearview camera display to freeze, crash, or become unresponsive when the vehicle is placed in reverse, failing to comply with FMVSS No. 111, 'Rear Visibility.' This is part of a broader pattern of FMVSS 111 violations affecting AAOS-based vehicles across the Geely/Volvo/Polestar group — Polestar's RP1069 / 25V615 covers the same regulatory standard with the same operating system. Approximately 400,000+ vehicles affected globally per related class-action filings.

Summary

NHTSA campaign 25V250 (April 2025) addresses a software defect in Android Automotive Operating System (AAOS) infotainment platforms that causes rearview camera displays to freeze, crash, or become unresponsive. The defect violates Federal Motor Vehicle Safety Standard No. 111 ('Rear Visibility'). Affected vehicles include the Volvo EX30, EX40, EX90, XC40 EV, C40, and related AAOS-based platforms. The same operating system is used by Polestar — whose Polestar 2 has been the subject of three separate FMVSS 111 remedy attempts (RP1016 / RP1056 / RP1069) for the same underlying issue.

Timeline

April 2025: NHTSA recall 25V250 issued. Volvo to deliver software updates via OTA or dealer visit at no cost. Owner notification letters mailed.

Mid-2025: Owner reports continue alleging the camera defect persists after the recall remedy. Forum and class-action research begin documenting cases.

January 27, 2026: Class-action lawsuit filed against Volvo alleging the recall remedy does not actually resolve the underlying defect. The complaint specifically identifies the AAOS architecture as the root cause. The plaintiff alleges Volvo's superior knowledge of the defect creates a duty to disclose that the company has not met. Approximately 400,000+ vehicles potentially affected per the lawsuit's class definition.

Consumer impact

This is the fourth EV platform on this index with FMVSS 111 rearview camera issues — joining Polestar 2 (three failed AAOS remedies), the Toyota bZ4X / Lexus RZ / Subaru Solterra family (PVM camera freeze, e-TNGA platform), and the Audi Q6 e-tron family (PPE platform, hardware replacement required). The cross-platform pattern is consistent: software-defined vehicle platforms are repeatedly shipping with FMVSS 111-violating rearview camera implementations, and the remedies vary in effectiveness. Hardware-replacement remedies (Audi 916C) actually fix the problem. Software-only remedies have repeatedly proven insufficient (Polestar 2, Volvo). Owners should verify campaign completion via NHTSA VIN lookup, monitor the active class-action lawsuit for potential additional remedies or settlement, and document any post-remedy defect persistence with photographic or video evidence.

Help other owners — file with the regulator

If your vehicle is affected by this defect, filing a complaint with NHTSA, Transport Canada, DVSA, or your regional regulator helps build the data record. Each report contributes to pattern detection that can trigger formal investigations and recalls — protecting other owners of the same vehicle, not just you.

You can file at any time, even if your dealer or manufacturer is already handling repairs. The regulatory complaint is a separate channel that helps every owner of your vehicle.

File a regulatory complaint →

Verify your vehicle with the regulator

The regulator in your jurisdiction is always the authoritative source for whether your specific VIN is affected by an open safety campaign. Check the database below using your vehicle identification number.

EV Risk Index editorializes around public recall data; we do not replace regulatory guidance. If you believe your vehicle is affected by a safety recall, contact the manufacturer and check the regulator database for your jurisdiction using your VIN.