Quote:
Originally Posted by gpvecchi
(Post 3338826)
I read it, this doesn't help, they are just general infos took from manuals. As wireless Android auto works, cast had to work too.
|
What those should be telling you is that Android Auto is a different protocol from Screen Mirroring. They don't operate the same way, and the Pixel phones do not support the protocol type that allows them to screen mirror to all capable devices. Timurrr was pretty spot-on with his reply earlier as well
Quote:
Originally Posted by timurrrr
(Post 3338437)
I vaguely remember that "Display Mirroring" requires the phone to support a certain protocol that most Android phones don't support.
|
Phones like LG and Samsung have shown fewer compatibility issues with screen mirroring than the Pixel line. Why? Well the idea behind this is Google dropping Miracast support on their hardware. What this means for the end user on Pixel phones is that if it's not a true Google Cast device that you're trying to mirror to, it probably isn't going to work. This is why many posts across the web suggest using a Chromecast on an HDMI port to get around the issue, and why Google's own support staff in one of those links (basically) says it's Chromecast or bust with the Pixel line. The Kenwood unit isn't a Google device, so likely it's using a variant of the Miracast protocol, not Google Cast. You need that type of connection for Pixel to work with it. Unfortunately like you said, this headunit doesn't have an HDMI input, so adding a Chromecast with a local hotspot isn't an option here.
Android Auto isn't a cast protocol, it's independent of that. This is because Android Auto is run through a specific Google app that allows the communication to work. Mirroring doesn't. Because of this, they can ensure Android Auto works across virtually any device. They have much better control over the connection and protocols, which means a stable, uniform experience across virtually any device. That's the true selling point of it, and where the bulk of Google's development and support sits. Screen mirroring is significantly less important to them, and as such is just a root system service that doesn't get much attention, and is limited.
From a personal perspective, I as the driver of the car can't see why I'd want my phone to wirelessly mirror to a headunit automatically at startup. Passenger, ok perhaps. But 9 times out of 10 I want the optimized Android Auto interface to be the one booting up over wireless. If someone in the passenger seat needs to do more, they can just plug in and off they go. I personally don't tailor my car to the experience of the passengers, I tailor it to mine as the driver. They can deal with those things. Having said all that, if there's a specific thing or app you want to be able to do that Android Auto doesn't do for you, there could be workarounds tailored to that specifically.
I am genuinely trying to help here. I hope I'm not coming across rudely in all this. As with all tech, things could change, but as of now this is a common question for Pixel users, and it always seems to have the same answer: Chromecast.
