Pshcwartz,

Android Auto is part of Android L, thus is not compatible with phones that run KitKat (4.4), Jellybean, Ice Cream Sandwich, or anything prior. There is only one phone right now that can run Android L and that is the Nexus 5. Chromecast is an unrelated TV adapter that does not provide a basis for inferring software and device compatibility. Installing the Google Now Launcher simply returns a basic Android feature that Samsung should have never removed in the first place, it doesn't help a Samsung owner get an OS update for Android Auto compatibility.

These hardware and software compatibility nightmares aren't a factor for Apple's Carplay, because Apple has total control over both the software and the hardware, while Google has very little, if any, control over the hardware that runs Android.

 

If Android Auto isn't compatible with previous versions of Android when it's released or shortly thereafter, it's DOA. For many of the reasons you state. And just because it's "baked" into Android L doesn't mean it won't be available to previous versions of Android as a standalone app in the Play Store just like they've done with all of the other google apps.

I am comparing it to Chromecast because it uses a similar idea of using your phone to drive the apps you see on the screen.

 

<p></p>
<p>&nbsp;</p>
<p>I think I understand it now why manufacturers are hesitant. With Android Autos ability to offload infotainment, get updates, new apps, etc in effect the system that the car comes in for service with can be totally different than when it left the showroom floor...potentially a service and support nightmare. The phone maker, Google, and the car maker will all be pointing fingers at each other if there is an issue.</p>
<p>&nbsp;</p>
<p>Also, I don't ever remember trying to fiddle with the radio or anything else while turning....I hope you don't actually do that no matter what car you have.</p>

 

The problem is distracted driving is much like driving drunk. No one ever really thinks they are drunk enough,or distracted enough, not to be able to drive a car. Some people even think they're better drivers when drunk.

How true is that?

 

Please stay on subject. This thread is about the possibility for Android Auto coming to the 2015 Honda Fit.

But really, saying "Google play Misfits" is EXACTLY the same as being drunk</sarcasm>

 

Android L is a significant overhaul of major Android APIs, notifications in particular, to make notifications integrate with Android Wear and Android Auto. It is unlikely that Android Auto and the operating system APIs that support it can be separated from it's parent operating system and made to work on older versions of Android.

Elementrace,

Could you please provide a source for your statement that "manufacturers are hesitant" about Android Auto? Android Auto has wide support from the auto industry. How can you claim otherwise?

When you bring your car in for service because of an issue, the task of isolating the cause of that issue will be easier because of the clearly defined role responsibilities of the hardware and software components of Android Auto. This is not the case with HondaLink which is an integrated and closed system. My entire head unit has to be replaced because of a minor glitch and now I have to get a rental car. I would much rather just be dealing with a software update.

I'm not surprised you can't recall specific memories of mundane details like changing volume. That doesn't mean nobody does or should change the volume in their car while the wheel is twisted if it can be done safely. In all other cars I have driven, it is very easy to take your right hand off the wheel, feel blindly for the volume knob, and twist to silence the music. As long as your eyes are on the road and you can observe there are no immediate threats, and your left hand has control, I don't see a danger in taking your right hand off the wheel for a moment to twist a volume knob. Unfortunately this safe volume change is not possible in the Honda Fit if the wheel twisted. The wheel being twisted doesn't necessarily mean the driver is in the act of turning. The car could be parked, or the driver could be waiting to make a turn. Take for example hopping in a car to drive somewhere when all of a sudden the music starts blasting, this is a situation when it is not uncommon for the wheel to be twisted such as when parking on an incline.

I think those who are concerned about distracted driving will greatly appreciate the design fundamentals and solutions offered by Android Auto.

HondaLink ALREADY SUPPORTS text/call notifications, music apps like Pandora, navigation, etc... and is regarded as a clunky interface that requires the driver to take their eyes off the road. Android Auto will make these functions safer. It's not as if Android Auto is adding new distractions, it's reducing the distraction of existing features.

 

The worst is technology has existed for decades to shut off phones that towers detect are moving except for 911 calls. yeah, I know passengers must be able to use their mobile phones. Sure they do.

 

Manufacturers being hesitant was just my assumption because I haven't heard of it being used in production. Can you provide a source of it being widely supported? As in actually being used in production?

 

Sorry I was just thinking that because one of the OP's arguments is that Android Auto will reduce distracted driving by allowing you to do everything by voice or whatever. My point being that all this interfacing with the car, while seemingly doesn't take a lot of brain power, does require you to momentarily focus on putting together a certain set of commands to get the system to do something. While not entirely like being drunk, my point was most people won't admit to either even when they are, being distracted or drunk while driving. Just making a point that while Android Auto will make things easier to do, it will also allow you to do more things while driving, in effect won't that be distracting somehow?

 

It's not so much the interface, but the simple addition of non-driving-related tasks that distract drivers.

A silly example is playing Angry Birds via voice commands while driving. Nobody would do that, right?

How about updating a facebook page while driving? Yes, people would do that.

 

I think you misinterpret the volume know thing. You said that using the steering wheel mounted controls was not a good solution because how would you change volume while turning the wheel. What I said was why would I be changing the volume while turning the car? Please read my post again and then read what you wrote previously. I don't have a problems with volume knobs while driving, but I still prefer as a matter of safety not to do it in certain conditions like on/off ramps, right turns, parking garages etc. I mean if you think its safe to do all that stuff while driving that's on you, but I've driven long enough to know that as I get older everything gets that little bit harder to do and not everyone has the same driving skill set to do what you think should be mindlessly easy.

And anyway you're trying to make a case for your point of view, and this is a forum. Am I not allowed to share my opinions and arguments?

 

Moving on....

One of the things I'm looking for is offline navigation. Would Android Auto be capable of something like that? Or would it be something more like the iOS implementation, which I think requires data for the maps?

Does it use the phone's GPS or the cars GPS?

 

If Android, IOS, et. al. want to be on the dashboard, why not just mount a tablet device on the dash? That way, if the device gets outdated you toss it and replace it with a newer device. The only "interface" needed on the vehicle is a standardized mount for the tablet and perhaps a bluetooth connection for audio.

It's not a good idea to integrate hardware that will be obsolete in 2 years into a vehicle that will last for 10 or 15 years. Look at how poorly the current phone/nav interfaces work on the Display Audio system. Are we going to expect Honda's implementation of other interfaces to be any better?

 

From what I understand Android Auto is dependent on the phone itself and doesn't require much processing from the tablet itself. I did see in one of the videos that I watched that L will be the first version they support but they did say they were "going to try" to support older versions (I am guessing the cut-off would be 4.0). However, Apple CarPlay would not be 100% dependent on the phone. From what I heard is that you can continue playing your iTunes independent of the phone so I am guessing that Apple users might have to contend with sluggish performance from older tech (which is right up Apple's profit motives).

Whoever says that Android Auto will be distracting seriously has not seen the videos:

1) It is all pretty much voice enabled/or the ability to be controlled for the steering wheel
2) It disables the keyboard so there will be no texting
3) Google is working with many safety agencies to get this approved

And those of you say that it will be a distraction......which is more of a distraction?

a) saying play a song
b) looking down at the speedometer
c) talking/arguing with passenger
d) reaching over to turn up the volume or putting in a new CD.
e) lighting a cigarette while driving

I would argue "A" would be the least distracting.

If anything it would take away from current road hazards, such as idiots who text while driving (I hate them with a passion) because they would NOT be able to do that and use Android Auto.

 

Pretty much what he said. Although I did read that something that supported his one fact that some manufacturers are a little hesitant about letting Android Auto in the car because of Google starting to get into the car industry (with self-driving cars). I guess no company wants another company coming into their territory. I work for a large company and our motto is "do what we do best and outsource the rest". Honda should stick to building great cars and leave the "infotainment" systems to others. Hondalink is terrible.

 

Sure, here are some sources. FYI these are the top three Google results for "Android Auto".

Android Auto
Open Automotive Alliance
http://en.wikipedia.org/wiki/Android_Auto
28 auto makers have joined the Open Auto Alliance whose members are committed to supporting Android Auto. This includes nine of the top ten automakers. In addition, manufacturers of 3rd-party head units such as Pioneer, Clarion and Alpine have joined for a total of 45 members.

"Widely supported" and "being used in production' are different things, but here are some press releases from manufacturers announcing release next year. Audi's XC90 will debute two months from now.

Audi USA News : Home
https://www.media.volvocars.com/glob...ration-of-cars
Honda Vehicles to Seamlessly Integrate Android Smartphone Features with Android Auto - Honda.com

Good point. This is why all Android Auto interactions that involve looking at a display are tested with an occlusion headset to ensure they can be completed in less than two seconds.

This is a silly example. Please stay on topic. Android Auto has nothing to do with Angry Birds or Facebook. Android Auto does not provide any additional functions not already performed by HondaLink, which has a terrible interface that is difficult to use safely while driving.

You are allowed to share opinions and arguments as long as they are valid and supportable. It is not appropriate to claim that I said "steering wheel mounted controls was not a good solution" when I said nothing of the sort. It is not appropriate to share false assumptions about industry support when this information is so easy to find, especially since links to information about Android Auto and auto maker support have already been provided earlier in this thread.

There are apps that work offline but I am not aware of a mechanism that would allow them to integrate with Android Auto. At this time the only 3rd-party apps that can integrate with Android Auto are music/audio apps that leverage the media services API. Android Auto uses Google Maps which does require a data connection. You would probably have to just use your phone if you need offline capability.

The reason why Android Auto does not use a mounted tablet is because Android Auto leverages the vehicle's built-in hardware which is superior to a mobile's hardware, thus can provide a safer and more seamless experience. A vehicle has much better sensors and interfaces such as directional microphones, directional speakers, wheel speed sensor, built-in steering wheel buttons, and more accurate accelerometer, GPS and compass.

Where would one mount a tablet that would not block the windshield or dashboard and still be in reach of the driver?

ANDROID AUTO DOES NOT INTEGRATE HARDWARE. It is software integration. The Android Auto software runs on your phone which can be replaced in two years when it is obsolete. The Android Auto software will be updated continuosly throughout the lifetime of your vehicle. The hardware in your car such as microphones and speakers are basic technology that are unlikely to be obsolesced before the end of a vehicle's lifetime.

 

I thought of making this point yesterday and didn't, and I guess now I'm just going to endorse the fact that you have made it for me. I would suggest with near certainty that all of those who are vehemently against anything like Android Auto, who suggest that "anything" which takes "any" attention from driving / concentration is to be shunned, would probably admit to engaging in conversations with passengers on occasion. I don't imagine that they have either declined to ever haul passengers, or insisted that the passengers remain absolutely quiet during the entirety of the trip. So in my view they cannot reasonably be completely against the idea of things which can distract the driver -- they're just very selective about what those things are.

 

Sure, the software can be replaced when it is obsolete, but the fact is that by then hardware will likely have changed and the up-to-date software won't be able to run on the older stuff. There's no incentive to support hardware that has already been sold. Legacy smartphones are commonly left behind as new versions of android comes out and legacy cars will be no different.

Promises of "continuous updates" sure sound promising, but they seldom happen in real life. I'm not going to buy a device or technology on promises.

Oh, and you can put a tablet in many places if the car is physically designed for it. A Fit really isn't, but my Scion could accommodate two full size tablets within easy reach and vision of the driver without obstructing any views. It's really just a matter of making space for the tablet rather than filling the space with oversize instruments and controls.

 

NO, the PHONE can be replaced! How did you misinterpret this sentence! Good god man, you are hopeless...

No, your statement indicates a fundamental misunderstanding of the new software model provided by Android Auto. Legacy cars WILL BE DIFFERENT if they support Android Auto/CarPlay because they will not be left out of continued updates of those software platforms.

Very good point. I wouldn't believe such promises either, instead I would look at the historical track record of a manufacturer's software updates, something few people do when purchasing a phone.

Take Apple for example, they have a proven track record of ALWAYS updating their phones once a year. Their customers with devices as old as three years can update to the latest iOS 8, day one of the software availability. The fragmented Android ecosystem can not compete on software support with a platform so tightly integrated by a focused company with total control of their mobile hardware and software. This will be an advantage for CarPlay.

Google's Nexus brand phones have ALWAYS been updated to the latest Android OS day one of their release. Their two year old Nexus 4 runs the latest version of Android. Most other Android manufacturers, like Samsung, only update their flagship phones just once, and usually over a year after that software update is available. For the most future proof Android phone it is important to stick with the Nexus brand. Like stated earlier, the Nexus 5 is the only phone that can run Android Auto, although it looks like the Moto X will be updated soon too.

 

Maybe we should wait until we see it implemented in a production car to see how well it can be implemented, because in theory it seems pretty good.