Android Auto + Widescreen
I myself am a Software Engineer and my role has required presenting information to the leadership with the data required to make key company decisions like these within a very large company, weighing tradeoffs among multiple options, feasibility analysis, building bridge solutions, etc. and just pointing out typical management practices.
Of course as I said, if the executives higher up do feel inclined to hear these concerns and address them, I wouldn't mind. I encourage folks to contact mbusa and complain about these issues. At the same time, do not maintain unrealistic expectations that you will see this addressed.




does anyone have android auto connectivity issue?
When I connect my phone, android auto is loading in and in 5 seconds phone or the car is cuting the connection.
A differebt phons is working with the car (same cable) and the phone is working with a different car as well.
I have absolutely no clue what the issue might be.
Thanks for your help, Z
As many of you know, Android Auto is not quite compatible with our W213 widescreen, it only used half of the screen and the left side is an ugly AA logo.
A coupe of days ago, Android Auto released an updated with "Widescreen support for select vehicles", I ran to my car and test it and seem doesn't worked. I cannot find any list of selected vehicles in internet.
anyone was lucky enough to make is work?
https://play.google.com/store/apps/d...ction.gearhead
Best regards!
AA delivered a solution for $69 where Mercedes failed.
My car is a 2017 E300 and my phone is a Pixel 5a running Android Auto 10.96.
AA delivered a solution for $69 where Mercedes failed.
My car is a 2017 E300 and my phone is a Pixel 5a running Android Auto 10.96.




The Best of Mercedes & AMG
I'll probably go with the Ottocast in the hopes a higher price may possibly equate to a higher quality.
I had AA in my W205 and I miss it. I have not used AA since I bought my W213 for the same reason I would not watch a television where the whole left 1/3 of the screen was black with a Sony logo.

I'll probably go with the Ottocast in the hopes a higher price may possibly equate to a higher quality.
I had AA in my W205 and I miss it. I have not used AA since I bought my W213 for the same reason I would not watch a television where the whole left 1/3 of the screen was black with a Sony logo.

Any way, I have one very important question about AAWireless and Ottocast. Since it uses Carplay protocol, does it also mean that Waze/Google maps wont show in hud? Currently Headup display shows navigation for android auto, but doesnt work on carplay. So I wonder if using Android via carplay protocols means only fixing the screen space, or also crippling the navigation on hud. Can @ardenne90 give some insight?




Any way, I have one very important question about AAWireless and Ottocast. Since it uses Carplay protocol, does it also mean that Waze/Google maps wont show in hud? Currently Headup display shows navigation for android auto, but doesnt work on carplay. So I wonder if using Android via carplay protocols means only fixing the screen space, or also crippling the navigation on hud. Can @ardenne90 give some insight?




Any way, I have one very important question about AAWireless and Ottocast. Since it uses Carplay protocol, does it also mean that Waze/Google maps wont show in hud? Currently Headup display shows navigation for android auto, but doesnt work on carplay. So I wonder if using Android via carplay protocols means only fixing the screen space, or also crippling the navigation on hud. Can @ardenne90 give some insight?
Any way, I have one very important question about AAWireless and Ottocast. Since it uses Carplay protocol, does it also mean that Waze/Google maps wont show in hud? Currently Headup display shows navigation for android auto, but doesnt work on carplay. So I wonder if using Android via carplay protocols means only fixing the screen space, or also crippling the navigation on hud. Can @ardenne90 give some insight?
I have the 2017 S213 wagon with P3 package including Heads Up Display, 12.4" LCD speedometer cluster, Distronic cruise control, and radar based accident prevention (the main reason for getting the P3).
I have used several AndroidAuto wireless adapters including the AA Motorola, Ottocast (two generations) and AAWireless.
I love the convenience of just getting in and driving with nothing to connect, especially when I have set up the destination on my desktop/laptop and sent it to the phone, or already set a destination in the house and the phone stays in my pocket.
Battery life can suffer on long trips, so I just make sure to power it with a charging cable in the console.
The AA Motorola device is reliable, but does not support firmware updates for bug fixes, compatibility and features.
When connecting it for Android Auto (AA) over the Android Auto interface (/AA) or "AA/AA", it does show the directions in the Heads Up Display (HUD), and in the secondary navigation display in the speedometer cluster when selected in the customization.
It does not take advantage of the extended Wide Screen Display resolution (WD), and instead shows the annoying Standard Display resolution (SD) Android Auto logo.
Connections are reliable and easy, it's a good unit for AA/AA.
My AAWireless device works about the same as the AA Motorola device in AA/AA mode, but with the benefit of control, customization and updates through their Android App.
It supports the additional Second Screen (SS) in the speedometer cluster and HUDbut just standard display resolution (SD) on the 12.4" center LCD - essentially the same as the AAMotorola device.
Connections are also reliable and easy.
When I tried the OttoCast devices (older and newer generations) it was similar similar to the AA Wireless, except for the App for updates and Beta program, so I returned them both.
I have been working with the AAWireless folks as a Beta tester and provided significant feedback. images and videos to get the unit working with Android Auto over CarPlay or "AA/CP"
The first was to get the MB controller dial to work and allow clicking and jogging to switch and navigate active Apps - and they have fixed, broken and fixed again that for me - and you :-)
Beta firmware updates are as often as weekly or even daily to support different vehicles and fix bugs - I appreciate they are very active.
It now properly supports Widescreen Display (WD) with a larger and detailed map using the full space. No noticeable stretching of fonts - you can select from several resolutions. Text is slightly on the small size - especially to the big fonts used in CarPlay.
Jogging the controller goes between Android Apps and rotating scrolls through the icons.
A long press of the Voice Control (VC) button triggers the Android voice input for navigation and other commands.
I immediately found that the icons for Android App selection were partly blocked from view by the steering wheel, so I switched the icon position from Auto (car detect) to fixed, pushing them to the passenger side, in the Android Auto App options on the phone.
Unfortunately the AAWireless in AA/CP mode does not support HUD or the Second Screen (SS).
The HUD is a big deal in city traffic or at busy exits. I have often thought things like the HUD, Keyless Go, auto high beam dimming, Wireless AA, were gimmicks, but quickly found they are very convenient features I don't want to lose.
I am not sure the HUD is actually a supported feature in CarPlay, as when I connect an iPhone to the car with a cable in CP/CP mode, the HUD and Second Display (SD) are not shown either.
This makes me believe the CarPlay interface in the S213/W213 does not support HUD, so getting that functionality in AA/CP is unlikely to ever come along.
I have asked AA Wireless about supporting the HUD but not got a reply on that - so the answer is probably no.
Probably the end of my story is that I have both the AA Motorola device, and will plug that in if I need the HUD.
For everyday use I keep the AA Wireless device plugged in for the widescreen benefit.
If anyone has got the HUD display working on CarPlay either AA/CP or CP/CP - please post which iPhone version, S213/W123 year, model and options package.
Last edited by HiTach; Dec 19, 2023 at 11:56 AM.
AA delivered a solution for $69 where Mercedes failed.
My car is a 2017 E300 and my phone is a Pixel 5a running Android Auto 10.96.
Scroll down and set the CarPlay (Beta) slider option.
Then in your car go to the Connect option and look for your device in the Apple CarPlay list.
Connections are also reliable and easy.
Unfortunately the AAWireless in AA/CP mode does not support HUD or the Second Screen (SS).
I have asked AA Wireless about supporting the HUD but not got a reply on that - so the answer is probably no.
For everyday use I keep the AA Wireless device plugged in for the widescreen benefit.
My AAWireless device works about the same as the AA Motorola device in AA/AA mode, but with the benefit of control, customization and updates through their Android App.
If anyone has got the HUD display working on CarPlay either AA/CP or CP/CP - please post which iPhone version, S213/W123 year, model and options package.
If I could clarify some points:
"AA Motorola" point - AA/AA works the same with most of the phones (I have tried Google Pixels, Samsungs) - both work great aswell, limitation is the car implementation.
"AAWireless device works same as Android device in AA/AA mode, but with the benefit of control" point - Main problem here is that limitation is the Car implementation, so we cant get much benefits. Updating the AAwireless dongle doesnt mean updating the cars AA implementation unfortunatelly.
"If anyone has got the HUD display working on CarPlay either AA/CP or CP/CP" point = I have tested lot of the iphones, various iOS versions. HUD doesnt work, but Its not because of Carplay in generall, Its because of W213 preFL Carplay implementation.
We basically got car, that has buggy both AA and Carplay implementations. But both have different bugs:
W213 AA protocol/implementation = not full screen, hud works, different audio profile.
W213 carplay protocol/implementation= Almost as good as carplay can get, but without HUD (=hud is bugged/non existent), different audio profile. Audio in carplay is much more flat, but there is less cut of frequencies (sounds better, if you can fix your EQ). Also has better resolution than Android Auto.
=Used phone doesnt matter, car headunit protocol selection between AA or CP decides what will work.
But, If AAWireless team could teardown, how the protocol works (what "code" does working AA HUD use to work) compared to Carplay, maybe they could help us with some hybrid solution built up into the AAWireless dongle.
Other than that, only future command (car SW) update can help us. But even the latest version of SW from 2021 still has this problem, and Benz wont probably release any more updates for preFL.
I am also thinking about enabling engineering mode in my car (basically coding inside headunit), to see if there are any relevant parameters to change to fix the AA/Carplay issues. Without EM, there is only ability to change call volume, volume separation, dynamic volume and other useless crap.
Last edited by matrixhaj; Dec 18, 2023 at 03:59 PM.
I'm probably just thinking out loud here, but I'm leaning more towards the AAWireless box now.
Myself, I'm just looking for a stable solution to provide full large screen AA display without audio quality loss from what I currently get from my phone's Bluetooth direct audio connection.
I can live without the instrument cluster and HUD nav options, but it would be a cool bonus.




I was not aware of the differences in audio quality between AA/AA and AA/CP, and now ill probably be more disappointed!
Bottom line, we are likely stuck with the current choice:
either HUD + SS + audio + Logo or Widescreen Display (WD)
I understand that retro-active software changes to debug and support newer hardware on a huge number of vehicles and options is a big deal for the manufacturer.
I don't have HUD in my car, but I do have the in-dash AA view that shows up when I turn on Navigation using AA. Most likely I will lose this once I enable carplay mode, but I can live with that since I don't use that view most of the time, especially if I can get a full widescreen view on the main display.
I will share how it goes once I receive the dongle this week.




