Omega Owners Forum
Chat Area => General Car Chat => Topic started by: grifter on 08 December 2020, 09:32:04
-
My partner usually buys a new pug every 3 years, and just got a new 2008 in August.
Just recently the carplay navigation/infotainment system has been rebooting itself and the garage checked/updated to the most recent software, they also said to use genuine apple cables, however with either the phone connected via apple or 3rd party cable, or disconnected, it will turn itself off then when turning back on it makes this horrible sound through the speakers, what I can only describe as sounding like a snowball hitting the windscreen, like a dull thud sound. Another thing we are now seeing since the update is sometimes the key not detected message, even though the key is right next to us.
Back in to stealership today and they've reported "no fault codes found". How could it be the phone when it does this when the phone isn't even connected?
Any thoughts? It sounds like a hardware intermittent fault, and what is that strange noise when carplay is restarting.
Thanks
-
None constructive... ::)
-
Apparently they've said there must have been another update since the last one, barely 2 weeks ago, and this has fixed the issue.....sounds like they never updated it the first time round, as they had convinced themselves it was our fault for using non-Apple cables!
-
It's cold outside, meaning the heaters in the car are on. Peugeot Dashboard and extra heat are not best friends.
We've got a couple of the new Peugeot Experts (van) in work, and as soon as the cold weather hits, the Stereo (also a SatNav) shits itself.
-
Mr DTM was talking about this from a JLR perspective a few weeks ago. IIRC a recent Apple update that buggered the interaction between car and phone on carplay and they were going to have to push out another one to fix it.
I realise that doesn't address the second part of your question though! ::)
-
Yes, given the age I expect its wired carplay and not wireless.
As an overview, Apple carplay requires an approved interface chip and sign off by Apple in order to support the functionality, however Apple then screw up the interface at every update >:( I would always advise avoiding Crapple updates for the first 4-6 weeks.....
As for the cables, the dealer is actually correct, the data loading Carplay (and Android Auto, Bidu etc) put on the system means you need a decent cable and not just the cheap tat which people only use for charging, long cables can also create issues.
Unfortunately the system in the Pugs is running on the edge and the software gets chopped and 'optimised' just to get it working so can be a bit flaky (hence why you might see a fresh 'oh shit' release shortly after you get an update)......it doesn't help that they don't have Software Over The Air (SOTA) working either.
We see loads of customer complaints following Phone updates..........the car has not changed, the phone has yet its the cars fault (happens on Android to but, much less often and not on Android Auto, not seen an issue for over 12 months and that was only on our older systems as they moved to a new Bluetooth stack and 'forgot' to enable backward compatibility).
I should add, it does sound like there is a more fundamental issue given the audio distortion, pretty much every system these days has a DSP audio processing stage to support cabin audio tuning, echo cancellation (voice calls) etc, it sounds like this is not loading correctly......as for the system crashing, this also points to a software install issue. The trouble is the dealer wont actually be able to do a full fresh software install so would be a head unit swap out (If it was me I would be looking to re-load the audio config files......but the dealers might not have this ability)
-
Yes, given the age I expect its wired carplay and not wireless.
I hope you didn't think it's from 2008? That's the model.
As an overview, Apple carplay requires an approved interface chip and sign off by Apple in order to support the functionality, however Apple then screw up the interface at every update >:( I would always advise avoiding Crapple updates for the first 4-6 weeks.....
As for the cables, the dealer is actually correct, the data loading Carplay (and Android Auto, Bidu etc) put on the system means you need a decent cable and not just the cheap tat which people only use for charging, long cables can also create issues.
Unfortunately the system in the Pugs is running on the edge and the software gets chopped and 'optimised' just to get it working so can be a bit flaky (hence why you might see a fresh 'oh shit' release shortly after you get an update)......it doesn't help that they don't have Software Over The Air (SOTA) working either.
We see loads of customer complaints following Phone updates..........the car has not changed, the phone has yet its the cars fault (happens on Android to but, much less often and not on Android Auto, not seen an issue for over 12 months and that was only on our older systems as they moved to a new Bluetooth stack and 'forgot' to enable backward compatibility).
I should add, it does sound like there is a more fundamental issue given the audio distortion, pretty much every system these days has a DSP audio processing stage to support cabin audio tuning, echo cancellation (voice calls) etc, it sounds like this is not loading correctly......as for the system crashing, this also points to a software install issue. The trouble is the dealer wont actually be able to do a full fresh software install so would be a head unit swap out (If it was me I would be looking to re-load the audio config files......but the dealers might not have this ability)
The Kia Dealer next to them is having a similar issue and they have said it's a common issue with updates, it's still doing the issue even now. I find that odd that you have to go to a site, download the update to a pen drive and install it by plugging that in to the car, that seems mad, especially as it's done sweet FA to fix the operations of the unit. As you said over the air updates, I would have thought that should be easy enough, especially these days.
Leaves you high and dry with a brand new car, which effectively doesn't work and can't be fixed!
-
SOTA is far from easy (and don't I know it ;D ;) ), to do well you need a module dedicated to it with its own sim card, antenna etc just so you can get a reasonable level of security AND be able to get five nines success (you do not want to be randomly bricking modules on a car overnight whilst sat on a customers drive.......so all modules need dual software banks........and most dont)........then there is the on-going data charges to the manufacturer, off-board secure servers, version inventory management.
That may give a bit of an indication why today your cheaper cars don't have it :y
USB update is used because for infotainment the files are huge, squirting via a diag tool is slow (due to the protocols) so its the quickest (and hence cheapest) way to do it. We have now moved all cars to 100% SOTA (we are the first to do this, having already supported infotainment and telematics SOTA on the previous vehicles from a specific software version) based on having a module handling it and sending custom deltas to keep file size down (although the latest pack I saw was 1.2G still). There also parts of the module you don't touch, particularly if its related to legals, firmware on microcontrollers etc