MG4 Software Update Thread

[BingBong]

68.4.7.0

Hi, i am going to the dealer for software updated, in order to fix the r63 charging bar, he just need to select FICM at OnePress function (even if there is a V near FICM)?

 

[NLMGSAN]

Hi, i am going to the dealer for software updated, in order to fix the r63 charging bar, he just need to select FICM at OnePress function (even if there is a V near FICM)?

Huh? Thought that was an issue with R59?

 

[BingBong]

Huh? Thought that was an issue with R59?

no, the charging bar problem is only for R63 after USB update

 

[NLMGSAN]

So you could not set the charge level with r63?

 

[haloweenhamster]

Not without the car being connected to SIPs & having the config updated

 

[HazardLights]

Car's been in for an annual service; it's come back with R63 installed and the chuffin Bluetooth issues are back. No, no, no! I don't want to pair every time I get into the car. What a crock of shit.

Does anyone know what the fix is? I am constantly being asked to repair my Pixel 8 and changes in infotainment software version have made no difference to this (I suspect a module upgrade would be required).

 

[NLMGSAN]

Does anyone know what the fix is? I am constantly being asked to repair my Pixel 8 and changes in infotainment software version have made no difference to this (I suspect a module upgrade would be required).

It would be nice if everyone reporting issues after an update would include the latest versions of the modules from the engineering menu. It will not provide answers on the "why" in everything, but in several case there could be hint in it.

 

[Mouss]

Does anyone know what the fix is? I am constantly being asked to repair my Pixel 8 and changes in infotainment software version have made no difference to this (I suspect a module upgrade would be required).

I got the pairing issue with my Pixel 8 Pro.
Sometimes it's every single day, sometimes it's once a week.
With R46, it was almost never but since R63 update, it comes often...

 

[haloweenhamster]

Also pixel 8 pro, Bluetooth issues with R40, R46, R59 & R63

I think the issue is the fact the FICM generates MAC addresses, they don't seem to be programmed with a fixed MAC addresses

I don't think it's anything we can do, MG needs to tie the MAC address to a serial number or VIN etc something visible to the FICM but unique

As it stands there's a possibility of your phone connecting to any MG4

 

[hojnikb]

Also pixel 8 pro, Bluetooth issues with R40, R46, R59 & R63

I think the issue is the fact the FICM generates MAC addresses, they don't seem to be programmed with a fixed MAC addresses

I don't think it's anything we can do, MG needs to tie the MAC address to a serial number or VIN etc something visible to the FICM but unique

As it stands there's a possibility of your phone connecting to any MG4

That's gonna be a hard one to explain, when ur phone connects to ur wife's sisters MG4

 

[AndyL61]

Does anyone know what the fix is? I am constantly being asked to repair my Pixel 8 and changes in infotainment software version have made no difference to this (I suspect a module upgrade would be required).

You shouldn't have to actually re pair. While the message is still on the screen (disappears after a short time) press and hold home until the screen goes off. When it reboots the Bluetooth connection is restored. Then cancel re pair message on the phone. Much easier than re pairing. The frequency of having to do this is reduced by always waiting for the system to fully boot up before pressing the brake pedal , (Bluetooth is usually the last thing to show up).

 

[Deanicus]

Also pixel 8 pro, Bluetooth issues with R40, R46, R59 & R63

I think the issue is the fact the FICM generates MAC addresses, they don't seem to be programmed with a fixed MAC addresses

I don't think it's anything we can do, MG needs to tie the MAC address to a serial number or VIN etc something visible to the FICM but unique

As it stands there's a possibility of your phone connecting to any MG4

Another Pixel 8 Pro user here with issues. Starting to wonder if there is a link?

However the random mac address thing is supposedly normal behaviour for most devices these days. It stops people being able to track you

From my limited reading of android documentation, while the mac changes, when paired it is supposed to share a unique key that allows both devices to recognise each other in the future. It seems the issue is with this process

 

[siteguru]

SE SR rather than a Trophy, but ... I've had no BT issues with my old Moto G8 Plus or my current Xiaomi Redmi Note 13 Pro+ 5G (Yes, Chinese phone manufacturers like long model names)

 

[Bam Bam]

I used to get automatic pairing. But since adding Pebbles' phone as well it doesn't seem to do that any more.

Does anyone know if it makes a difference if there is more than one linked phone?

 

[Geekice]

SE SR rather than a Trophy, but ... I've had no BT issues with my old Moto G8 Plus or my current Xiaomi Redmi Note 13 Pro+ 5G (Yes, Chinese phone manufacturers like long model names)

Same for me with the SE SR, but with an iphone. I’ve never had any issues. When I connect my iPhone via CarPlay, it disappears from the list of paired devices in the car’s Bluetooth settings. But as soon as I disconnect CarPlay, it reappears and works fine. In fact, if I don’t use CarPlay, my phone always connects to the car via Bluetooth automatically.

 

[HazardLights]

It would be nice if everyone reporting issues after an update would include the latest versions of the modules from the engineering menu. It will not provide answers on the "why" in everything, but in several case there could be hint in it.

My current versions are in this post but they don't fix anything:

MG4 Software Update Thread

Is it really a temperature difference? to me it feels that after 20/30 minutes in the car, the hvac starts to blow significantly colder then it did at the beginning of the ride... But this behaviour was the same on R46, 59 and 63, so it's not (only) a FICM issue I always knew there were two...

www.mgevs.com

You shouldn't have to actually re pair. While the message is still on the screen (disappears after a short time) press and hold home until the screen goes off. When it reboots the Bluetooth connection is restored. Then cancel re pair message on the phone. Much easier than re pairing. The frequency of having to do this is reduced by always waiting for the system to fully boot up before pressing the brake pedal , (Bluetooth is usually the last thing to show up).

I had just been cancelling the message and it mostly works. I will try your suggested method. I like your tip about waiting although it's not my strong point!

 

[AndyL61]

I had just been cancelling the message and it mostly works. I will try your suggested method. I like your tip about waiting although it's not my strong point!

It definitely makes a difference if you can wait until you see the Bluetooth symbol appear before pressing the brake. Mine is on R33 and is pretty stable. But the reboot while the message is on the screen definitely works.

 

[HazardLights]

It definitely makes a difference if you can wait until you see the Bluetooth symbol appear before pressing the brake. Mine is on R33 and is pretty stable. But the reboot while the message is on the screen definitely works.

Thanks. The February Android update supposedly fixes Bluetooth issues so I will need to see if that helps although it may be a car issue rather than phone.

 

[sk8sara8]

Hello all Just left the mg garage after updating to R63 noticed that when on android auto I'm not able to swipe down for the air con setting or the brightness and elk menu any suggestion??? Is this expected to happen after the update to r63

 

[HazardLights]

Hello all Just left the mg garage after updating to R63 noticed that when on android auto I'm not able to swipe down for the air con setting or the brightness and elk menu any suggestion??? Is this expected to happen after the update to r63

Yes. You need to press the home button to take you out of AA first. Phone button, or selecting AA on screen to go back, or an android voice command will do too.