No matter what you think of Cadillac’s CUE infotainment system, the fact remains that the Linux-based software utilizes a 3-core ARM 11 processor to handle all of its different functions. Two of those three cores are utilized by the system for voice recognition, which is designed to operate the system and vehicle functions (instead of the touch screen or capacitative-touch controls). But some of the hardware on which CUE runs isn’t in use by the current implementation of the software, GM Authority has learned. The calculated decision by engineers to leave “room for growth” allows CUE a certain level of future-proofing.
What’s more, the hardware that isn’t being put to use today is said to be reserved for an upcoming CUE update that will bring applications to the infotainment system. Whether the app functionality will be part of the upcoming CUE update isn’t known at this point.
However, GM announced in January of this year an SDKÂ (Software Development Kit) that will furnish programmers with the ability to create apps for the infotainment systems of GM vehicles. The automaker hasn’t provided a timeframe for the app functionality to be delivered to vehicles, but we expect the app store to be called the “GM App Catalog”.
The GM Authority Take
We don’t mean to rush The General, but we’re really looking forward to spending some time with some in-vehicle applications — which we expect to be “app bridges” rather than full-fledged apps. App Bridges (our term) would allow the user to control existing applications on their smartphones with the built-in controls on their vehicles, such as voice commands and/or buttons on the steering wheel or touchscreen.
Comments
If GM used the Linux operating system for CUE, then they should publish the distribution version and APIs (Application Program Interface – for non-computer readers) so a smart owner can add their own applications. I wonder if it is Android-compatible, so most android apps can be adapted for CUE.
At least we know that CUE will never suffer the BSOD!
Raymond, using Linux as the foundation doesn’t mean much… and doesn’t guarantee that the final product will be stable or good. It’s exactly what they make of the software running atop the core/kernel that matters.
Also, just because an OS is Linux doesn’t make it necessarily Android. And making the API widely available isn’t a good idea, since this is your car we’re talking about… only high quality, tested, and proven apps should be allowed in.
Guys, the apps in question will be “bridge” software, providing you with the ability to interact with the apps on your smartphone via voice, and in-vehicle controls (sliders, touch screens, steering wheel buttons, etc).
They won’t be full-fledged apps per se, so allowing Android apps into the ecosystem isn’t their purpose per se