Not sure I'd agree with that. If thorough testing had been done they would know these issues existed and would or should have done something about them.
I am pretty sure they knew about the issues. Beta software is the modern way. If it was all perfect you’d have to wait until mid next year to get the car. Like all things it is a tradeoff and I’d rather get the car earlier with bugs than wait.
I’m developer, we test our stuff thoroughly but bugs can still slip through. As long as they patch it soon enough I’ll give them the benefit of the doubt.
I have merged the two threads but used my title as it has better SEO value (meaning people searching the interwebs for this issue will have a better chance of finding this thread).It is the thread named Drowsiness warning
It certainly put me off during test drive, my dealer wrongly said it could be permanently disabled along with the other problematic safety features (lane-keep assistance in particular).
It does make you wonder about all the trade journo testing. Surely they encountered this issue, yet never thought to mention it in reviews. Client journalism?
I obviously haven't watched every one, but the vast majority of video reviews I've seen were not a Trophy. Maybe that's why it's not been widely reported?
I covered it with my finger during the test drive I had recently, and it cured the problem. So, some black electrical tape cut to the shape of the sensor might work until MG fix what is clearly an issue. I had the same problem when I did a test drive in a Toyota BZ4x a couple of months back. I was warned by the salesperson to turn it off if it became annoying.
True and also also I bet the Trophies that were reviewed had the sound already turned off.
Really?! Just pull that fuse and nothing else is disabled?
Doesn’t mean you won’t get another error
“Yeah, the fatigue monitoring module is just a bit fatigued, poor thing needs a rest”
