Your browser is not supported. Please update it.

4 July 2014

Google announces Android Auto, adds 40 members to its car alliance

Google unveiled Android Auto at its I/O conference last week and added 40 new members to its Open Automotive Alliance as it seeks to make its OS as dominant in connected vehicles as it is in handsets.

The first Android Auto cars are scheduled to launch by the end of the year. Android Auto – one of a series of platform extensions announced at I/O to take the OS into every type of device and screen – will allow users to plug Android handsets into cars to control both the vehicle and phone. They will then be able to navigate the phone using a combination of voice, touchscreen and physical knobs and buttons.

The main aim is to provide the functionality of the phone without the dangerous and distracting motion of looking down at a device to control it, and to that end Android Auto will disable text-heavy and video-based content when the car is on the move. While plugged in, the phone is locked and doesn’t accept user input, simply displaying the Android logo.

Consequently, Google has decided that there will be strict layouts that must be adhered to in Android Auto. This means that apps can change the look of their buttons and logos but cannot deviate from the layout of the template that dictates where the touchscreen’s buttons will be located. This is to ensure that the least amount of time possible is spent looking at the controls for an app so that users can remain focused on the road ‘ time limits that are currently mandated by the OEMs.

We’ve previously reported that BlackBerry’s QNX operating system currently enjoys over 50% of the market for in-vehicle infotainment systems (IVI), but the approach seen by Google and Apple is notably different. In the former, the car is an independent system, while in the latter the car is effectively empowered by the phone ‘ acting as an extension of the user interface rather than a central intelligence. However, Audi reports that its QNX based Multimedia Interface (MMI) system coexists quite happily with Android Auto, so interoperability should prevent difficult buyer decisions in showrooms.

For automotive OEMs, this device-centric approach removes the onus from them to develop their own systems. Deferring to a handset allows the manufacturer to simply add the necessary I/O features to their cars and let the customer decide how to use them ‘ an extension of the dumb-screen/smart-box argument found in the television sphere. All that would be needed based on the features announced so far is a display with manual controls or a touchscreen, integration for microphone input and audio output over the car’s speakers, and lastly the all-important bridge between car and device ‘ a simple cable. In this regard, GM has said it is quite straightforward to build its Chevrolet Spark to accommodate both platforms.

The native systems in the car such as the radio and climate controls will not fall under the control of Apple and Google. Those systems will be left in the hands of the OEMs because the car still needs to functional if a phone is never plugged into it.

There are a considerable number of manufacturers who are now publicly working on supporting both Apple and Google’s plans for the car. There is a large incentive for this action, as between them the two companies control around 90% of the smartphone market. To list the dual-system makers: Audi, Chevrolet (GM), Ford, Honda, Hyundai and its 32.8% owned subsidiary Kia, Mitsubishi, Nissan, Opel (GM), Subaru, Suzuki and Volvo. The Apple-only manufacturers are BMW, Peugeot and its subsidiary Citroen, Ferrari, Jaguar Land Rover, Mercedes Benz and Toyota.

The manufacturers who are currently Android-only are: the Fiat Group brands that include Abarth, Fiat, Maserati and Alfa Romeo; the Chrysler group which is majority-held by the Fiat Group that includes Dodge, Jeep and Ram; Mazda, Renault, and the Volkswagen Group’s Bentley, Seat and Skoda and Volkswagen itself; Acura (Honda) and lastly Infiniti (Nissan).

Other new partners that don’t directly produce automotive components include Alpine Electronics, Fujitsu-Ten, Freescale Semiconductor, LG, Pioneer, Panasonic, and chip vendor Renesas. Pioneer and Alpine both appear on Apple’s list of CarPlay compatible vendors and Apple says they will allow users to add CarPlay via aftermarket systems. It is almost certain that the two companies’ roles in the OAA are to a similar end.

Android Auto should also support advanced services such as vehicle diagnostics and roadside assistance systems. This could alert a driver to a potential issue and recommend or schedule maintenance before it becomes enough of a problem to leave the car on the side of the road. The assistance service will be for those unavoidable accidents.

Google wants to simplify the route to market for both OEMs and software developers. Patrick Brady, Google’s engineering director, said: ‘It was a deliberate choice for Android Auto that we could ensure safety and make sure that app developers were not burdened by the ISO standards. You need to make this work in a touchscreen interface in a Honda or a Volkswagen, as well as an Audi MMI-based interface, and you realize that the screens are going to a different distance from the user, which affects font and image size, and you need to go through distraction testing, and you need to make sure it feels like every part of the car. That’s an impossible ask of developers.’

Evidently Google feels confident that Android Auto’s simplicity of implementation will make it a must-have feature for the OEMs.

Automotive Grade Linux delivers first software stack, based on Tizen:

The Automotive Grade Linux (AGL) project has announced that its first open source software stack is now available for download. The group hopes that the release will bring the automotive industry one step closer to a Linux-based connected car platform ‘ although both BlackBerry’s QNX and now Apple and Google software have quite a significant head start on AGL.

AGL says it is building the only fully open automotive platform. It hopes that automakers will be able to use it to create a branded user experience, which is something of the reverse of both Apple and Google’s plans.

The system is based on Tizen IVI. You will recognize the name as Samsung’s open source language that it is trying to push as an Android alternative in its phones, watches and even in the smart home. Tizen is based on Android, so Google Maps will be making an appearance in the system. AGL insists that open collaboration will reduce R&D, which is somewhat beside the point as it seems late to the market.

Ford and Intel collaborate on Mobii in-vehicle cameras:

Ford and Intel are working on systems that would allow users to monitor the interior of their connected car and enable a vehicle to identify its owner and occupants by facial recognition. The project is called Mobile Interior Imaging, or Project Mobii, and hopes to use pre-existing sensors and cameras to create a more personalized driving experience.

‘Our goal with the Mobii research is to explore how drivers interact with technology in the car and how we can then make that interaction more intuitive and predictive,’ said CTO and VP of Ford Research and Innovation Paul Mascarenas.

Exterior cameras are already used in a range of functions on vehicles such as parking assistance and accident avoidance. New areas that might be enabled by this research include driver authorization, recognition and loading of personalized settings and privacy controls to recognize when not to push personal information to an in-car display. If a driver is not recognized, a photographic record can be sent to the cloud and a designated smartphone for authorization. This functionality might be particularly useful for parents who trust their cars to their children, and the Mobii system can enable them to set prerequisites for driving when the camera recognizes a child ‘ such as seatbelts engaged and music not playing excessively loudly.