Google Launches Android Automotive Consortium
DeviceGuru writes "Google announced an initiative with Audi, GM, Honda, Hyundai, and Nvidia aimed at fostering and standardizing Android in-vehicle infotainment (IVI) systems. The Open Automotive Alliance (OAA) is dedicated to a common platform that will drive innovation, and make technology in the car safer and more intuitive for everyone, says the group. The OAA is further committed to bringing the Android platform to cars starting in 2014. In its FAQ, the OAA suggests that this is not a full-blown Android in-vehicle infotainment (IVI) system, but rather a standardized integration stack between automotive systems and mobile Android devices. However, the OAA FAQ also discloses broader ambitions for 2015 and beyond: 'We're also developing new Android platform features that will enable the car itself to become a connected Android device.'"
Looks like QNX is going to see some brutal competition.
Google wants Android in the dash of cars so they can track you. "Hey, you just passed one of our ... um, I mean, you just passed a Carl's Jr. - aren't you hungry?"
I guess self driving cars aren't enough for Google. They want to be in the driver's seat of dashboard technology too.
Think of the kind of computer or phone you had 5 or 10 years ago. Do you want a 5-10 year old device hard-wired into your car 5-10 years from now?
And no matter how "open" Google tries to make things, vehicle OEMs are just as bad as handset OEMs and cellular carriers and they WILL make these things suck. I know a guy who has a $100 windshield-mount GPS in his GPS-equipped car because he didn't want to pay the dealer $hundreds to update the maps in his built-in unit. So now he has a device on his windshield with a dangling cord and some dead space in his dash.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
Creating a standard interface that only easily (and fully supports) the connection of Android-based devices. Frankly, I'm shocked Apple didn't already make this move. If this happens (and spreads), the only devices you'll want to hook up to your car will be Android-based since those will probably be the only ones you can interact with using steering wheel controls, etc.
We already know Google will sue if a phone manufacturer tries something other than pure Android while being part of the Android consortium. Will Google sue all these manufacturers for using QNX or Sync as well as offering Android?
Do no evil, my arse.
This is another PR stunt by Google, the "Open" part is a misnomer. To be part of the OAA you are forced to use only Android as your IVI system and are explicitly forbidden from using any competing Android-fork. So much for openness and freedom.
--
Disclaimer: I work for TAGA (The Arrogant Google Assholes)
"...enable the car itself to become a connected Android device."
hmm. It's one thing for me to carry an android device around in my pocket. It's quite another to have an android carry me around in it's pocket.
Just imagine: instead of ACPI and driver issues, we can have life threatening kernel panics!
I'm sure this will be just as effective as the Open Handset Alliance.
Apple beat them to the punch
http://screwtapefiles.blogspot.com/2013/09/apple-is-looking-interesting-again.html
I want knobs. Knobs and physical buttons. Let them surround a fancy whizz-bang touchscreen if you want, but I damn well want to be able to turn up the heat or volume without looking.
>>> "We're also developing new Android platform features that will enable the car itself to become a connected Android device"
I prefer my cars air-gaped. Why? First, I don't trust automotive manufacturers to introduce adequate security measures. Second, I don't trust automotive manufacturers to stay on top of patching security holes over car's expected useful lifetime.
Creating a standard interface that only easily (and fully supports) the connection of Android-based devices. Frankly, I'm shocked Apple didn't already make this move. If this happens (and spreads), the only devices you'll want to hook up to your car will be Android-based since those will probably be the only ones you can interact with using steering wheel controls, etc.
They already have
http://screwtapefiles.blogspot.com/2013/09/apple-is-looking-interesting-again.html
Just imagine: you go out for a drive, and your car starts communicating with other cars in the next lane and suddenly its a beowulf cluster of them...
I don't need or want a intelligent components when inexpensive, simple, proven and reliable mechanical components have done fine for decades.
Just because you can isn't always a valid reason.
---- Booth was a patriot ----
I don't know how many of you it bugged, but it bugged me that the different auto manufacturers were developing their own devices. All that non standardized nonsense would have actually not want to buy one of those vehicles with integrated tablets.
God spoke to me
I couldn't make it into work today because my car had a kernel panic.
FORCE AT GUNPOINT the following...
1 Easy to use UI for automotive cases. Big fleshy sausage sized buttons on screen, and a default User hard button or communications interface to steering wheel hard buttons.
On screen volume controls are an epic fail, they MUST be physical buttons.
Next, put in place priority levels for apps. I need the radio to have top priority, then navigation, then other stuff. Happy fun app should never be able to override my navigation and cause the unit to lock up due to a bad app. Low priority apps get killed by the OS Violently if they do not instantly respond to a "STFU" request from the OS or the user.
Android on it's own is junk for a car stereo. It's missing a LOT of things that makes it happy in a car environment. such as it should use sram instead of Dram so I can turn off the car and have android sleep in less than .1 seconds, then on startup it wakes and starts running from sram again in that same 0.1 seconds. Using less than 50ma while in sleep mode so the car can sit unused for 2 weeks without killing the battery. No boot times, no shutdown times. it MUST be instant based on power input from the car.
Right now Android is not suited to car use. and when Microsoft designed their AutoPC platform they made all the above failures UI sucked for meaty fingers, long boot and shutdown times, bad device interface design, etc...
Do not look at laser with remaining good eye.
Well, if you needed proof of a higher power then here it is. Standard operating systems in cars are long overdue.
Smartphones and tables are getting this powerfull that it makes much more sense to have a charging station + screen mirroring for your phone.
Those solutions already exist: http://www.customgadz.com/store/
Wouldnt that make life a lot easier?
Cars are so 20th century. Even flying robot cars.
Hell, even Microsoft's in that market. That just proves that only old people drive cars.
Hyperloop's where it's at in the 21st century, chelloveck.
"I can't come in to work today because my car has a virus" becomes a legitimate excuse.
That was the turning point of my life--I went from negative zero to positive zero.
The simple solution seems to be mirroring the device onto the car's dash-mounted display and accepting remote touch from the dash display, and, ideally, some kind of button protocol to standardize button interactions.
Presumably you'd want to develop some kind of car-specific mirroring protocol so it would be device agnostic, but that would require device makers to include and support it, although as long as it was a superset of their own mirroring protocols it probably wouldn't be that hard for them to support it.
Those of us who want "infotainment" systems simply jsut want our car to be able to do what our phone does, with a larger screen so it's not as distracting when we're trying to use it in a split second - i.e. navigation.
I don't want Tom tom. I don't want Garmin. They suck. Their implementations are ridiculously slow. My Nexus 4 (and without even mentioning, my Nexus 5 and Nexus 10) blow all of that hardware out of the water. The only thing those devices DON'T do is integrate well with stereos.
You know how you fix this, auto manufacturers? Put bleeding edge mobile hardware (yes, that's right, Nexus 10 guts!) inside the car! No optical media player - because people don't need or want them. Let me pay $10 a month foa data connection, or just pack wifi in the device so I can use my Nexus 5 cell connection for streaming media AND GOOGLE MAPS AND GOOGLE NAVIGATION WHICH IS ALWAYS UPDATED AND I DON'T HAVE TO SPEND MONEY FOR.
It's not hard. This problem doesn't have to be re-solved. Why aftermarket headunit companies (Yeah, I'm talking about you Kenwood, Pioneer, Alpine, Parrot and all you others who can't see to implement Android in any intelligent way) can't do this correctly is beyond me. There's going to be some dipshit faggotass who says "I don't want a quad core computer in my car", but fuck them. I want my car to provide my music and maps to me PROPERLY and not half assed.
How about car manufacturers provide an option for NO computer in the car? My newest vehicle is a 1998 Volvo S70, but if I were to buy a new car I would be attracted to a NO COMPUTER option and a $2000 savings. I really have not used GPS or a smartphone in my car ever and I want to keep it that way. If I really wanted a computer in my car, I would much more appreciate an interface such as OBDII (OBDIII?) that expanded access and control to things like climate control and audio system. I could then choose my device (and OS) and connect to the car using an app written for that device to interface with cars. This, of course would make car dealers very unhappy. How else can they charge $900 for GPS maps update then? We as consumers must clamor for no hardware from auto maker other than the standard interface to have some basic control over the vehicle. Then BYODevice and BYOApp and you're off. That would be truly open, everything else is a lock-in. Perhaps I am just old fashioned, but in-car infotainment is a recipe for disaster on the roads anyway. But that's a whole other discussion.
The car's entertainment and communications systems should be completely detached from the safety and automotive systems, sharing only a (filtered) power supply.
I have the latest greatest Toyota infotainment system (which is really pretty lame) and their latest GPS (which is absolute and utter crap - it's actually dangerous to follow its instructions) and it's all networked and integrated with the onboard computer systems.
If the "infotainment" system was a completely separate android system the size of two packs of cigarettes, Toyota could offer more value at less cost and create a thriving aftermarket that would drive more sales of their cars.
But I don't think Toyota is smart enough, outside the engine compartment. These are the same people who have been making Priuses for the US market for over ten years, and the instrument cluster still has knobs and indicators that aren't readily visible to a 6' driver. I have to duck and bob to see things in my plug-in model3 just as much as I had to in the 2002 model1. Great drive train, with innovation and ingenuity galore, but utterly horrible driver ergonomics and controls with scads of unnecessary, half-baked antifeatures....
...would be a nice start.
I'd be happy if they could get kenwood, alpine, and other aftermarket head unit manufacturers on board. But these guys hate open systems. Friggin' pioneer wants around $300+ just for a navigation add on, last I checked.
Basically automotive engineers, especially the IC engine worshiping kind, hate electrical engineering. They have been playing in the pissing contest of 0 to 60 time, and quarter mile time since 1930s. Their game is strapping heavier and heavier, increasingly powerful IC engines on to piddly little frames that can hardly hold the huge engines in. Then they go to track after track, magazine after magazine touting their cars and the 5.4 sec and 4.8 sec times.
But the IC engine is fundamentally unsuitable for automobiles. Their engines can not pull a car from rest. They have come up with frustratingly complex set of gears and clutches and "hydromatic" torque converters and slip disks and this and that to get the car to go to 0 to 2 mph. From 2 or 5 or 7 mph they can accelerate it well. But even there if they just used an IC engine running at constant speed to turn a generator and drive the car through electric motors they could have won their quarter mile races and 0 to 60 times nicely. It might not be economical, it might not make consumer grade, but in their concept cars, in their brand image cars and the super luxury segment where cost does not matter, they could have tried it. But they did not. It is not that the concept is unknown. Diesel electric locomotives have been in operation since 1950s. In fact the steam engines were replaced by diesel electric locomotives so fast, many steam locomotives made by Baldwin Loco Works, Philadelphia went straight from production line to scrap yard! Seeing the enormous torque these electric motors were delivering did not inspire even one auto engineers to try to have a flag ship concept car that would see if an electric motor would help them in their pissing contests. It took an outsider Musk who is not afraid of electricity to show them what an electric motor could do in a car with Tesla.
When they did not even understand electrical technology well, why would they do well with electronics?
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
Does that mean we can now swipe left ?
Tizen already does it for some time. There were already a number of Tizen release - for IVI.
I think Google has recently read a press release about Tizen on mobiles. They have looked it up and found out that it is already available and used in IVI market for few years now.
Or, the claimed "Android App compatibility" Tizen 3.0 feature might have gotten them worrying. So they have decided to jump on it before it gets too big.
All hope abandon ye who enter here.
I want to keep g00gle OUT of my next truck. Will that mean I will have to pay for that OPT OUT? If that is so, that is fucked up.
Can't wait for non-upgradeable Android in cars as well. "But sir, your car is more than 18 months old, so we don't support it anymore. Buy a new car."