Android Auto + Widescreen
CarPlay is however different in this aspect and supports four different resolutions at three different aspect ratios.
- 800px × 480px 5:3
- 960px × 540px 16:9
- 1280px × 720px 16:9
- 1920px × 720px 8:3
CarPlay in fact supports 1920x720 as a native resolution, and might be one of the reasons why MB decided to build support for this.
The only thing they do now is to upgrade navigation maps for a limited period of time. One must cite a specific problem to get a software upgrade under warranty. Otherwise, it is what you bought is what you get. With technology I do not expect free or paid upgrades. I totally agree with MB upgrade philosophy.
The only thing they do now is to upgrade navigation maps for a limited period of time. One must cite a specific problem to get a software upgrade under warranty. Otherwise, it is what you bought is what you get. With technology I do not expect free or paid upgrades. I totally agree with MB upgrade philosophy.
There is no doubt that this is an MB issue for choosing to implement AA on the headunit that way. It would have been very well possible for MB to plan ahead and support both non-widescreen and widescreen AA options, and write code to handle it. The negotiation protocols are designed to handle these capabilities correctly (i.e. only phone supports widescreen but not headunit, only headunit supports widescreen but not the phone, etc.). However in the interest of costs (R&D costs money), MB would have very well decided to invest these costs for later year models since it gives customers one more reason to upgrade to these later year models.
I like MB's cars mechanical aspects, but not a big fan of their software development, look at the mbusa website configurator - it's as if some college intern coded this during their summer internship. MB Connect app and service is another joke, and they have been gradually removing features from this app. The browser MB Connect experience is much worse.
Because of all these reasons, I feel MB will support widescreen AA but I doubt we are going to see it in our current year cars. 2021+ year models would be my best guess.
The Best of Mercedes & AMG
I have a BMW, Hyundai and Volkswagen in my stable and have experienced similar issues with all of them. Believe me, it happens with every brand.
My sales person does this with every vehicle I purchase because many of them are new models, sight unseen in the US (such as my order for an EQC400).
Note that the phone's software is generic as per the AA standard, and the headunit negotiates as per this standard. If the headunit doesn't understand widescreen AA, there is nothing Google or the phone can do to fix this.
What you're rather referring to is that many manufacturers have lower resolution screens and they won't support the widescreen UI. I've seen these lower res screens in many of my rental cars - Dodge, Nissan, Ford, Honda.
The MB infotainment in the current gen E class (and other newer 2019/2020 models with wider screens) supports HD resolutions and is indeed widescreen capable as per the specs, but the software on the headunit is not utilizing this capability unless MB fixes this.
Last edited by Tuxdude; Oct 12, 2019 at 02:12 PM.
I didn't know the EQC400 could even be ordered! Looks like a great vehicle.
https://support.google.com/androidau.../8844203?hl=en
https://support.google.com/androidau.../8844203?hl=en
With software releases, regression testing is one of the key aspects. There is the saying that if nothing is broken, why fix it? In other words, making a change in software always has the potential to impact other things which where working earlier. Sure there are ways to make a very specific and narrow change in software to limit this, but it is not always possible and you need good software engineering expertise to make such wise decisions.
It is cost nevertheless in terms of Software engineering headcount, and there are priorities among projects that headcount is funded for. Higher level executive make such decisions on which projects are a priority, and how much additional funding need to be secured for them when they plan each quarter.
With newer models, this cost is built-in (i.e. the overhead is minimal) in the R&D for launching that newer model.
I was a software development engineer for decades before going into consulting. I've seen too many "one line of code" changes break an entire system.
I'm well aware of the complexities of coding and making changes. I also know that simply changing resolution is normally a quite simple thing.
But you're right: MB probably isn't going to bother with us. Especially if we don't even really expect them to. It appears that is their way, which is really a shame. I've never before seen a place where the customers make excuses for the product and why it can't be made right, rather than ask for improvements. Assuming anyone from MB frequents here, they know you don't expect much at all, so why spend the time.








