6 ms·
This is why Carplay/Android Auto are so key. They're safer than using your actual phone, they offer legitimate maps apps (Google Maps/Bing Maps/Apple Maps/etc),
by Someone1234 10y ago
This is why Carplay/Android Auto are so key. They're safer than using your actual phone, they offer legitimate maps apps (Google Maps/Bing Maps/Apple Maps/etc), and are somewhat future proof.
Too bad the MirrorLink consortium dropped the ball so epically. MirrorLink arguably does the same thing as Carplay/Android Auto and has been deployed to millions of vehicles, but nobody uses MirrorLink 1.1, why? Because to get your app certified takes tens of thousands of dollars, months, and tons of paperwork.
Carplay/Android Auto literally exist because the MirrorLink group created so many rules, regulations, and nonsense in the name of safety that MirrorLink 1.1 has like twenty apps total after two years(!). So if your vehicle has MirrorLink on the feature list, just laugh and forget it exists, you won't be using it.
PS - MirrorLink 1.0 allowed two way screen sharing, which was legitimately useful. MirrorLink 1.1 is a very different beast, most newer cars and phones only have MirrorLink 1.1 (no 1.0 at all). 1.1 defines things like how big buttons have to be, what kind of animations can play, how many button presses to reach each task, etc. Then everything has to be certified by an independent auditor.
PPS - Most depressing part is: MirrorLink could certify Carplay/Android Auto themselves, and instantly add both to millions of existing vehicles on the road. But they're never going to simply because they're effectively in competition with both.
- UVB-76 10y agoThe average age of cars on the road in the US is something like 11 years [0] Even if CarPlay/Android Auto last more than five years, I expect new versions will come out which render old vehicles incompatible. [0] http://www.latimes.com/business/autos/la-fi-hy-ihs-average-car-age-20150729-story.html http://www.latimes.com/business/autos/la-fi-hy-ihs-average-c...
- mrpippy 10y agoApple takes backwards-compatibility very seriously for MFi protocols, because they know that the "accessories" are cars that people keep for a long time. I used to work at a company making iPod car kits--we took an interface from 2006 (with a hard-wired 30-pin connector), hooked it through a FireWire->USB charging adapter, a 30-pin->Lightning adapter, and it worked fine with an iPhone 6.
- izacus 10y agoI distinctly remember iPhones complaining about "obsolete device" when plugging them into a few years old Audi and VW cars around iPhone 4 era. That was then followed up with connectivity and charging issues. So what was the deal with that?
- monknomo 10y agoI have an old car and it definitely doesn't work with anything newer than a 2G iPhone. No errors indicated, just can't hack it. It does work with a usb stick full of mp3s, though.
- mrpippy 10y agoCould be FireWire charging--the original iPhone and earlier iPods could charge off 12V (FireWire), whereas the 3G and up only took 5V (USB). Adapters were available (although Apple didn't make them themselves) Also with the early iPhones, if accessories were just "Made for iPod" certified but not "Made for iPhone" (which usually required TDMA emissions testing and iPhone testing) a message would pop up.
- Someone1234 10y agoWhy would new versions cause incompatibility? Carplay/Android Auto are just, at their core, dumb protocols for transmitting screen information and receiving back touch inputs. If you go disassemble Mirrorlink 1.1 apps they use the VNC protocol behind the scenes, the protocol isn't complex (the certification nonsense is all artificially added). The reason for the fragmentation and pain in this particular space (infotainment units) is a combination of: raw greed, vehicle makers trying in vein to retain control, not-invented-here syndrome, and "safety." The only issue I see with Carplay/Android Auto is that Apple & Google should have worked together to create a single protocol, which would have made implementation easier and likely resulted in a faster rollout. They both benefit by having the infotainment unit hand off to their respective smartphone OS.
- zeveb 10y ago> Why would new versions cause incompatibility? Because CarPlay in 2016 doesn't support the new hotness of 2018, because we are an industry of attention-deficit twentysomethings. Granted, were I forced to choose between attention-deficit twentysomethings and bureaucratic, glacial fiftysomethings … well honestly, I don't know which I'd choose.
- tormeh 10y agoI believe you're describing the choice between Tesla and Mercedes...
- lagadu 10y agoIf you're describing mercedes as the glacial50somethings, you're not aware that more often than not Mercedes are the first to market with a huge amount of every feature imaginable in the history of automaking. Want to see what features regular cars will have in 10 years? Go check out an S class today. Things like onboard navigation, voice controls, parking sensors? All 90s technology on the S class. Autopilot came before the Tesla's, radars, adaptive suspension, etc are all things from several years ago in the S class land. They just use that line to showcase all the cool things that a car can do.
- Retric 10y agoStandards can last a fairly long time. DVI and 802.11b are both over 16 years old and backwards compatibility is still common. Even if they just default to a remote desktop with touch screen interface, that's still fine for most in car applications.
- filereaper 10y agoYup, bought a new Accord specifically for CarPlay/Android Auto support over all the competitors models. CarPlay works well enough though no Google Maps, having issues with Android Auto mostly due to issues on my phone side :(
- serialpreneur 10y agoSimilar here. Bought Civic '16 specifically b/c it comes w/ Android Auto + Carplay! Has been working pretty smoothly with my Nexus 5X.
- tdkl 10y agoWhy would I pay hundreds of $currency for a new head unit or thousands for a new car, if I'm already walking around with a device capable doing all that? Android Auto/Car play should just run as a dedicated mode on the phone.
- masklinn 10y ago> Why would I pay hundreds of $currency for a new head unit or thousands for a new car Larger display and physical buttons are really quite a good idea when you're driving 2 tons of steel at 60mph.
- hughes 10y agoI think display placement is much more important than size. Using a phone for nav that's sitting in your cupholder is terribly dangerous, but using one clipped to your dash inside your field of view seems okay.
- tdkl 10y ago> Larger display and physical buttons GPS units like Garmin use touchscreen instead of physical buttons and are safe, road legal. Tesla ships cars with a huge touchscreen console - safe and road legal. That's a pretty weak excuse. We could also debate that things that hinder concentration while handling "2 tones of steel" are : - listening to the radio, - talking to the passenger(s), - singing.
- dexterdog 10y agoLooking at billboards
- deleted 10y ago[deleted]
- mikeryan 10y agoBecause for the most part in the US its actually illegal to use that capable device while you're driving your car.
- legulere 10y agoThe problem with Android Auto, at least by the test I saw done by c't magazine is that it doesn't always work. It's a M android device to N cars relationship, creating a lot of combinations that need to be tested. At least in the test I saw if it worked depended on the phone. Pretty much the same problem miracast has and why google probably developed the chromecast. I guess MirrorLink is trying to solve that problem by more thorough testing.
- sangnoir 10y ago> It's a M android device to N cars relationship, creating a lot of combinations that need to be tested I'm certain that Android Auto compatibility is part of the Android Compatibility Test Suite that all OHA OEMs have to run for phones in order to get Google apps. The tests probably are not perfect
- closeparen 10y ago>They're safer than using your actual phone Not sure about that. In many cars you have to take your eyes pretty far down from the road to look at the radio. Touchscreens honestly don't belong down there, I'd much rather have physical controls I can operate by feel. Phones can be mounted in the visual scan across the windshield (close and small enough to not occlude anything).