Content by Mouss in January, 2026

Yes, no new FICM MCU for R69 It's not an issue, it's the normal use for AA/CarPlay for security reason (no more overlay)

Hello What I learned since 2 years and half with this car : when a Bluetooth issue show up, it's because the car MAC address is changed by itself (IDK why but still trying to figure it out). How I know that ? Early 2024, 6 month after having the car, I got a Bluetooth issue and after trying...

Nope. Build are regional and depends of market. EU and UK got SWI68, SWI69, SWI132 and SWI133 build according version (SE/Standard, SE Extended Range/Comfort or Trophy/Luxury) and Model Year. But if I remember correctly, I saw Turkish MG4 with EU build, a Luxury with SWI68-29958-1300R59 firmware

Don't know yet, I would have said it if I knew

Hi SWI69-29958-1100R42 is rolled out for Standard (EU)/Comfort (EU)/SE (UK)/SE Extended Range (UK) SWI68-29958-1300R69 is rolled out for Luxury (EU)/Trophy (UK)/XPOWER (EU and UK) People claim files !

Something interesting : SWI69-29958-1100R42 is rolling out but don't know since when...

Bluetooth pairing fix, some new languages and few minors fixes

The latest since June is SWI69-29958-1100R40

Hello, yes. TBOX was swap like you but Dealer doesn't perform "Replacement" in SIPS. Read from here, I left some feedbacks https://www.mgevs.com/threads/ismart-cannot-bind-to-mg4-merged-threads.17178/post-258848

R33 fix: Screen freezing, Bluetooth pairing disconnecting, Screen “jumping”, Android Auto/Apple Car play not connecting, Navigation Freezing