bilbo
Standard Member
Has anyone else had this error with the S5? It's not related to anything plugged into the USB sockets, but rather a problem with the DAB radio. See below from the MG4 forum:
I've had this twice now, i.e. get the message, then radio freezes. After the first time I did the dis/re connect -ve battery terminal which fixed it. A week later it happened again, so did the fix again. It was after the second fix that the 12V battery drained. The car is used pretty much daily, but all short journies.
We do generally have the radio on V2 from the south hampshire dab multiplex and do sometimes travel out of the area and keep it on V2 until the signal is lost, but haven't noticed if that triggers the error, so I need to experiment.
I've attached a photo of the error.
So that makes 3 of us with the same issue using the same garage..... what's the chances?!?!
After the last update I hadn't had any issues and was starting to feel it had been resolved. Until I recently suffered 3 three re-occurrences close together - standard USB disk identification error followed by loss of all radio (which would have undoubtedly lead to a dead 12V battery if I hadn't DC'd the battery when the radio stopped working).
Anyway, I believe I can trace these to very specific scenarios and you're right that it's nothing to do with connecting a phone (I haven't done that since the earlier problems).
When Wave 105 was sold out I changed to Nation Radio South - which can only be accessed via the South Hampshire DAB radio group. On all 3 occasions I was listening to Nation and drove some way out of county (London x 2 and Swindon). Each time, the radio stopped working (as you'd expect on leaving the broadcast area) but soon after I got the usual USB error. Next time I came to the car no-radio at all - on any channel. So I am utterly convinced it's a software issue - I think as it isn't a national DAB channel it just "didn't know where to go" when it couldn't get a signal and got caught in a loop. So I DC'd on return to Hants each time and, hey presto, everything was restored and no further problems (till the next out of county trip...)
I reported this to Richmond Southampton and, after waiting several weeks for them to see it, took it in today to be greeted by the same warm, welcoming and re-assuring staff (not!). Anyhow, they "found no faults" (again, of course, because DC'ing and reconnecting removes the error codes) BUT they have upgraded the software from R33 to R38 - see pic - and asked me to "monitor it". They were "optimistic" that would solve it, but that's what they said after each of the last updates too....
View attachment 35414
Will update further with any news......
I've had this twice now, i.e. get the message, then radio freezes. After the first time I did the dis/re connect -ve battery terminal which fixed it. A week later it happened again, so did the fix again. It was after the second fix that the 12V battery drained. The car is used pretty much daily, but all short journies.
We do generally have the radio on V2 from the south hampshire dab multiplex and do sometimes travel out of the area and keep it on V2 until the signal is lost, but haven't noticed if that triggers the error, so I need to experiment.
I've attached a photo of the error.
