Automotive experts

Conjure is a global leader in innovation and digital products within the Automotive sector, working at the forefront of innovative technologies with the likes of Android Automotive and the Android Open Source Project (AOSP). For almost a decade, Conjure has been designing and developing connected car applications, Infotainment (IVI) and cluster displays. During that time we have worked globally with numerous OEM and Tier 1 suppliers on multiple vehicle programmes.

When it comes to technology, Conjure has delivered projects utilising Android Auto, Android Automotive (AOSP) and Apple Car Play. We’ve also delivered a number of projects using proprietary connected car systems from OEM and Tier 1 manufacturers.

Services

  • AOSP customisation and custom component development
  • IVI, cluster and passenger display UX and UI design
  • Full design and SDLC for OEM and Consumer mobile apps
  • Connected car (V2X) and keyless entry application development
  • App and systems prototyping

What is Android Automotive (AOSP)?

The Android Open Source Project (AOSP) is a set of Open Source components, documentation and device requirements provided by Google that supports the Android Operating System across consumer devices including mobile devices and embedded hardware.

Android Automotive, despite its similar name, differs from Android Auto which is an app for smartphones that enables in-vehicle infotainment (IVI) systems to mirror content from a consumers device. Android Auto is the Google equivalent of CarPlay from Apple.

Android Automotive AOSP Architecture Diagrame

Modern cars are complex systems that use a number of buses and protocols (CAN, LIN, Ethernet, MOST, etc) to communicate between vehicle subsystems. These communication buses vary between manufacturers and sometimes even different vehicle models from the same brand.

The Android Automotive hardware abstraction layer (HAL) provides a consistent interface between Android and vehicle communication layers. This is implemented by the vehicle manufacturer so that application developers have a consistent application development layer to benefit from.

Android Automotive used to power the IVI of the Polestar 2
Android Automotive AOSP powered automotive instrument cluster in the Polestar 2

Android Automotive running in the Polestar 2 being used to drive the IVI (left) as well as the cluster display (right). Photos Copyright of Polestar.

Android Automotive Experience

At Conjure we believe that AOSP will become commonplace within vehicles within the next 5 years, with some manufacturers (including GM and Volvo) already committed to model lines that will exclusively use AOSP as the infotainment operating system. This is in line with numerous other brands we have worked with and spoken to, who are ensuring that they are ready for this shift in the status quo and consumer expectations.

In summary, our Android Engineering and Experience Design teams have commercial experience in designing and building native Android and AOSP applications and components that comply with the Android and AOSP guidelines. Further to this, all developers within our Android engineering team are Google Certified Developers.

Click here to speak to us about your next AOSP or connected car project, or complete the form to the right and one of our team will get right back to you.

Recent Projects

PHYSICALLY BASED RENDERING (PBR) USING FILAMENT IN ANDROID

From our experience in developing IVI and instrument cluster user interfaces (UIs), we know the importance of 3D rendered content, both from an OEM and customer perspective. We have been using Filament to bring 3D elements to our in-vehicle interfaces with great results!

REVERSE PARKING ASSISTANT USING ANDROID CAMERA FRAMEWORK

When thinking about how AOSP can be used to replace all in-vehicle infotainment (IVI) systems, we wanted to try building out some of the more advanced driver information and ADAS systems using only Android frameworks and components. A great candidate for this was the reverse camera assistant which we built through utilising the native Camera HAL.  Further improving the user experience, we observe the GEAR_SELECTION property through the Vehicle Hardware Abstraction Layer (VHAL) enabling the IVI to bring up the parking assistant app automatically.

A SEAMLESS IVI AND INSTRUMENT CLUSTER EXPERIENCE

The connection between the IVI and Cluster displays is of paramount importance to the driver and passenger experience and is rightly a focus for our OEM customers. This is currently an evolving part of AOSP which we wanted to investigate in order to understand the current and capabilities and restrictions.

Driver Distraction

Understanding the Driver Distraction Guidelines is an important part of the UX and technical architecture of IVI and Cluster applications for AOSP. We built a reference application to fully explore the required architecture within the context of common UX and UI actions.

OEM Android Automotive Adoption

Whilst most Automotive OEMs have undertaken feasibility studies, a number have already made a commitment to adopt Android Automotive OS in a all, or a selection of their future vehicles. The table below tracks the status of each. If you have any further information on these or other OEM projects, then drop us a line.

OEM Announcement date Models / Supported by
Polestar February 2018 Polestar 2 (2020 release)
Renault Nissan Mitsubishi Alliance September 2018 Vehicles starting 2021
Fiat Chrysler Automobiles (FCA) May 2019 Vehicles starting 2022
General Motors September 2019 Vehicles starting 2021
Groupe PSA July 2020 Vehicles starting 2023

Related Reading