{"id":8563,"date":"2021-08-19T19:20:08","date_gmt":"2021-08-19T17:20:08","guid":{"rendered":"http:\/\/plus.maciejpiasecki.info\/index.php\/2021\/08\/19\/android-automotive-everything-you-need-to-know\/"},"modified":"2021-08-19T22:06:12","modified_gmt":"2021-08-19T20:06:12","slug":"android-automotive-everything-you-need-to-know","status":"publish","type":"post","link":"https:\/\/plus.maciejpiasecki.info\/index.php\/2021\/08\/19\/android-automotive-everything-you-need-to-know\/","title":{"rendered":"Android Automotive: Everything You Need To Know"},"content":{"rendered":"

Over the past few years, Google has really been talking up this new \u201cAndroid Automotive\u201d platform, at Google I\/O. And it\u2019s about time we talked about what exactly Android Automotive is. Particularly now that GM is fully on-board with Android Automotive and will be using it with all of their upcoming vehicles \u2013 starting with the new Hummer EV.
\nAndroid Automotive is very exciting, especially for those that are Android users. Imagine having your car running the same operating system as your smartphone and tablet. Now that is pretty cool. And Google is slowly getting car makers on-board with using it in their vehicles. Like with Android Auto, it\u2019s going to take time to make it widespread.
\nWhat is Android Automotive?
\nAndroid Automotive is essentially the operating system that will run your car\u2019s infotainment system. It runs directly on the in-vehicle hardware. It is a full-stack, open source and highly customizable platform, that powers the infotainment system. And it supports apps built for Android, and those built for Android Auto.
\nLike we\u2019ve seen with early videos for GM\u2019s new Hummer that uses Android Automotive, car makers can still heavily customize Android Automotive.
\nWhich means we could see some heavy skins on Android Automotive, like we have seen on Android. It\u2019s a way for car makers to differentiate their vehicles to the competitors, and also make it blend in better with the car\u2019s interior. Like the Hummer EV in the video above, it looks way better with what you\u2019d expect from a Hummer, versus the vanilla Android Automotive experience. And it also gives you bigger touch targets.
\nAndroid Auto vs Android Automotive
\nAndroid Auto has been around since 2015. Which makes Android Automotive even more confusing. But Google does actually do a good job of making it easier to decipher the difference between the two on its Developer website:
\nAndroid Auto is a platform running on the user\u2019s phone, projecting the Android Auto user experience to a compatible in-vehicle infotainment system over a USB connection. Android Auto supports apps designed for in-vehicle use.
\nAndroid Automotive\u00a0is an operating system and platform running directly on the in-vehicle hardware. It is a full-stack, open source, highly customizable platform powering the infotainment experience. Android Automotive supports apps built for Android as well as those built for Android Auto.
\nEssentially, Android Auto is an experience that is powered by your smartphone, while Android Automotive runs natively on the hardware within your car \u2013 no smartphone required.
\nAndroid Automotive gives users a better experience. As they can just get in the car and start using their streaming service of choice, Google Maps, and even make phone calls, without having to plug in their phone. That might sound like a minor thing, but it can make a big difference. Of course, you can do this with Wireless Android Auto, but Android Automotive will not use up your phone\u2019s battery life. Which is really nice.<\/p>\n

What is Google Automotive Services?
\nEven though Google doesn\u2019t talk about it, you\u2019ve likely heard about Google Mobile Services. This is basically the license that smartphone OEMs can apply for, to be able to run Google services on their phone. You\u2019ve probably heard a lot more about GMS since the whole Huawei fiasco, and it losing access to GMS since President Trump banned them from working with US companies.
\nWell, Google Automotive Services or GAS, is essentially the same thing. As Google puts it \u201cis a collection of applications and services that automotive OEMs can choose to license and integrate into their in-vehicle infotainment (IVI) systems.
\nBasically, if a car is using Android Automotive, it is in their best interest to license GAS, which will make their user experience even better. As GAS does include every Google service out there. That includes Google Assistant, YouTube Music, Google Maps, and much more. Including the underlying Google Play Services.
\nAre apps available in the Google Play Store?
\nAs mentioned before, Android Automotive works with Android and Android Auto apps, which means that apps for Android Automotive are available within the Google Play Store. Including apps to control the temperature of your car. In fact, Polestar\u2019s app for climate control is available in the Play Store (though you\u2019ll only see it if you have a Polestar 2 on your Google account). But, not all Android Auto apps are available for Android Automotive. Currently the list of Android Automotive apps is pretty short.<\/p>\n

This opens up a lot of possibilities, as Polestar (and other car makers) could also opt to really change up the interface of the car. Or add additional modes. As all it takes is a simple app update. It\u2019s pretty similar to what Motorola was doing almost a decade ago, where it pushed a lot of its system apps to the Play Store and updated them that way. Instead of through a system update.
\nIt\u2019s a pretty interesting way to improve your infotainment experience, but this means that you could choose between different navigation apps like Google Maps or Waze, for example. Of course, this is just the early days of Android Automotive, so this could change vastly in the coming years.
\nWhat apps are available and what do they look like?
\nLike with Android Auto, apps on Android Automotive are forced to stick within strict design guidelines. And the point in this is so that you don\u2019t spend a ton of time looking at the screen while you are driving. So the apps look similar to how they would in Android Auto, but perhaps in a different aspect ratio. That means bigger touch targets, which makes it easier to use while driving.
\nHowever, with Android Automotive, app developers do get a bit more leeway in how they can design their apps. Spotify, for example, looks sort of like how it does on the desktop. But with a larger DPI, of course.<\/p>\n

There are still design guidelines for Android Automotive, but they aren\u2019t as strict. As we\u2019ve seen with Polestar and Hummer so far, companies don\u2019t need to stick with material design for Android Automotive. Though when it comes to media apps, the touch targets will mostly be in the same area, across different apps. So you can use muscle memory to change songs, and such. Without having to look at the display for long.
\nThen there\u2019s sign ins. That\u2019s still something that Google, developers and car makers need to address. As signing in on the screen in your car isn\u2019t particularly user friendly. Though, a screen like the Polestar 2 has, is a lot easier. As it is a larger portrait orientation screen.
\nCar makers are also releasing their own apps to find chargers, particularly for electric and hybrid vehicles. Which is going to be a lot easier to use, then to pull out your phone and open the PlugShare app to find where you can charge your Polestar 2. These are apps that are needed for newer cars, which are also electric.
\nDo I need to login to use my car?
\nGoogle is going to want you to sign in, and of course that will make it easier to download and use apps. But it is not required. But we would highly suggest you do, as the Android Automotive software can bring in cloud preferences and user customization from your account.
\nNotably, offline Android Automotive should work pretty much the same as\u00a0 it does when you are logged in. All of the vehicle apps will work. Meaning you don\u2019t need to sign into your Google account to change the temperature on your AC.
\nSo why is Google making Android Automotive usable without an account? China. Countries like China where Google services are not available, need to be able to use these cars too. And in China, it would be pretty much impossible to use. But they can still use apps like WeChat, QQ Music and Baidu Maps. Though it will be interesting to see how the Polestar 2 would look in China.<\/p>\n

What vehicles support Android Automotive?
\nAs of right now, there is only one car maker that has vehicles on the road powered by Android Automotive. And that is Volvo. The Volvo XC40, and the Polestar 2 \u2013 which is Volvo\u2019s performance car brand.
\nHowever, many other manufacturers have come on-board and are going to be bringing in Android Automotive to its vehicles int he future. In September 2018, the Renault-Nissan-Mitsubishi alliance announced that they would use Android Automotive in its upcoming vehicles \u2013 starting with 2021 models. Then in September 2019, GM announced that they will use Android Automotive in all of its future cars. And finally Stellantis announced in July 2020 that it would use it, and Ford announced in 2021.
\nSo Google does have most of the bigger car companies on-board for using Android Automotive. Though things do move pretty slowly in the automotive space. So even though we should start seeing Android Automotive vehicles in 2021, it might be a year or two later before they become more popular.
\nThese are the current cars that have Android Automotive built-in:
\nVolvo XC40 (electric and gas-powered models)
\nVolvo XC60
\nVolvo XC90
\nVolvo C40
\nGMC Hummer EV
\nPolestar
\nPolestar 2
\nWhy would a car maker use Android Automotive over their own system?
\nA big question with Android Automotive is, why would a car maker like Toyota want to use it over its own system? As you might have noticed, Toyota has not jumped on board yet. Though they were pretty slow in adopting Android Auto too.
\nAnd that\u2019s what Google has been trying to talk car makers into doing. Allowing them, a software company, build the software for their vehicles. Which also means that they will get tighter integration into Google services like Google Maps, Google Assistant, and others. Which is much better than say, Ford\u2019s built-in navigation and voice commands. Which is why vehicle makers are starting to jump on board with Google pretty quickly.
\nHow does Android Automotive benefit the user?
\nThe biggest benefit is, this is going to be software you are already familiar with. Particularly if you use Android. Instead of some cumbersome software that the manufacturer threw together, which is typically pretty terrible.
\nIt\u2019s also going to bring all of your favorite apps to your vehicle, without having to plug in your phone to use them. Like Spotify, Google Maps, Waze, Google Assistant and much more. Imagine being able to ask the Google Assistant to turn down the AC in your Hummer EV. That will be possible thanks to Android Automotive, which is huge.
\nBut the biggest benefit is definitely the usable software. We\u2019ve all used the software from companies like Ford, GM, Chrysler, Toyota and others, and know just how bad it really is. And Google will change that with Android Automotive here.
\nWill my next vehicle have Android Automotive?
\nMost likely. Even though the automotive space does move pretty slowly, your next car will most likely have Android Automotive. Unless you are buying a new car this month.
\nWhere Google has Ford, Chrysler, Dodge, Chevy, Cadillac, Buick, GMC, Nissan, Mitsubishi, and Volvo all on-board already for Android Automotive. It\u2019s very likely that your next vehicle is going to sport it. And as an Android user, that\u2019s going to make for an exciting drive.
\nThe post Android Automotive: Everything You Need To Know appeared first on Android Headlines.
\n
\nSource: ndroidheadlines.com <\/p>\n","protected":false},"excerpt":{"rendered":"

Over the past few years, Google has really been talking up this new \u201cAndroid Automotive\u201d platform, at Google I\/O. And […]<\/p>\n","protected":false},"author":5,"featured_media":8564,"comment_status":"false","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-8563","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bez-kategorii"],"_links":{"self":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8563","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/comments?post=8563"}],"version-history":[{"count":1,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8563\/revisions"}],"predecessor-version":[{"id":8565,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/8563\/revisions\/8565"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media\/8564"}],"wp:attachment":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media?parent=8563"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/categories?post=8563"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/tags?post=8563"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}