[xarball]

I work in the auto industry in HMDs, and I think the last comment was somewhat on the right track, but perhaps missing bits of a larger issue at hand.

We can get the impression that Waze was built on a lot of technical debt by the amount of corners Google had to cut to even get it on screen -- how much it doesn't fit in their UI framework, and how poorly it runs when streamed to the HMD. Even Google Maps in satellite view runs terribly on the 90% of vehicles on the road that implement Android Auto. The underlying protocol used to convey that amount of data to the HMD runs like crap on most vehicles, and for better or worse the current protocol is pretty much frozen in time because most vehicles don't apply OTA updates yet. (Some manufacturers even charge labor for applying updates!)

The reason I'm picking on Waze specifically though is because HMD's have much stranger User <-> Interface considerations for what is safe, legal, and not crappy UI design. Add fire to fury, the performance is barely passable today.

Apps must have this, and so will Google if they are to be successful here. Whether Google even knows where they're going with a reliable HMD framework for using cookie-cutter UI components is largely unknown, but I don't think they're satisfied with the current API.

[sofaofthedamned]

That's exactly the sort of comment I come here for.

We retrofitted (i.e. hacked) AA onto my wifes 124 Spider. I've noticed it judders a lot when in satellite mode, but not in normal. Assumed this wouldn't be the case as it's essentially a video stream being played with touch events sent back and USB audio. Maybe some headunits are a bit underpowered for this?

That said on my Kia Cee'd it runs like a dream regardless, there is never a glitch.

Any more insight on the way AA and Carplay work from a manufacturers PoV?

[BoorishBears]

Did you install the AA hardware from Mazda, or are you using the software tweak, which is not known for performance

[sofaofthedamned]

Can I put the Mazda hardware in the spider?

[BoorishBears]

Yes, the infortainment (and almost all of the interior) is Mazda parts.

https://21stcenturyfiat124spider.wordpress.com/2019/02/18/un...

If you go through with it, pay attention to the version numbers.

I personally didn’t install it yet because previously you’d lose some functionality like navigation for the next owner. With the new tweaks that’s not an isssue.

-

The software AA is laggy because it’s essentially simulating proper AA.

There’s a note saying it’s not recommended anymore for being out of date and buggy

[sofaofthedamned]

Awesome, thank you!

[cardiffspaceman]

> ...most vehicles don't apply OTA updates yet. (Some manufacturers even charge labor for applying updates!)

Some vehicles' nav systems do not refresh the navigation data in any way unless you pay for the update and, as you say, pay labor to install the update. In other words the application code and navigation data are bundled. The update costs run about one iPhone XS per annum. From experience, the update is not even satisfying.

I certainly won't be looking to built-in nav in the future: too many opportunities to test my resolve to not feel bad about something expensive, disappointing, and out of my control. As long as smart phones fit in the cupholder I will use my phone.

[bingobob]

could be base on the limits imposed by the video codec that they use to stream to the HMD this page https://www.mathieupassenaud.fr/build-your-own-android-auto-... talks about H264 but they also need USB data also for the touch controls

[solarkraft]

Thanks for posting this.

> Android auto is just a remote screen. Nothing is generated by the car display. A H264 video stream is generated by the Android App on the smartphone.

So ... the car really just needs to implement h264 streaming to be compatible? So there's exactly nothing special about bringing an app to Auto (in theory)?