Car Android system first exposure: readily available

At this year's CES conference, Google (Weibo) and Nvidia announced a partnership with GM, Honda, Audi and Hyundai Motors to set up an open Auto Alliance (Automotive Alliance). The message they first announced was vague, mentioning only the core principles of the program and the goal of extending Android to cars. Since then, we have heard little about the relevant news. Now we have a look at Google's vision for the car version of Android, internally called Gearhead. The credibility of this rumor is about 70%. We believe that Google's car version of the Android interface will be very close to what we see today. Of course, carmakers may add their own design elements to the auto version of Android. At a news conference, Google emphasized openness, customization and size, so carmakers could take advantage of the flexibility to create personalized software that distinguishes them from others ' car versions of Android. The launch of the Open Auto Alliance said its goal was to extend Android to cars from 2014 onwards. Now, halfway through, it's time to announce the car version of Android. But things are always changing. The information to be discussed in this article comes from the beginning of this year, so the actual interface may have improved a lot. In the news, Huang, the president and CEO of Nvidia Jen-hsun Huang, said the car was the ultimate mobile computer, pointing out that as the car was equipped with a supercomputer chip, our dream future car would no longer be science fiction. The current car version of Android, which has no official name yet, does not look like a fictional artifact of science fiction. Many of the practical features in automobiles are infused with new ideas. Based on the information we have, the Android basic interface of the car version basically revolves around four different features: navigation, music, phone and search. We can't fully describe all the aspects of the interface, but we know what it's like to call and send text messages and what its music interface is. One aspect that we are not aware of is the case of third-party applications. It is reported that the car version of Android does not have a primary key or application drawer. We expect third-party applications to appear in the automotive version of Android, but are unsure how users can download or open them. We speculate that applications like Spotify or audible are ideal for settling in cars as long as they have an interface for driving situations, which is to set minimal physical interaction and screen display information. Evidence as usual, we will not rashly publish pictures of unpublished software. We do this for a reason, and protecting our informant is of course one of the reasons. We have shown you the interface we have redrawn based on the information we have obtained, and we will of course be as loyal as possible to the original image. We can seeAn application running in a car has a semi-transparent status bar similar to play Music (and the recent play Store). We also have the ability to see larger, more visible, pressing controls, a familiar system navigation bar and the Google search icon we've seen in the Android Wear. Make a call according to our judgment, users can enter the Dial-up interface, choose a common contact or dial number, but the user can also use voice to activate the phone, they simply say, well, Google, please call (contact name), as in Google Mobile search application. We speculate that the user's mobile phone will be connected to the car system via Bluetooth. Sending SMS messages can also be done through voice commands. Users only need to say, send text messages or send text messages to (contact name), can activate the car's SMS function. In the current design of Google's voice command, Blue says Google is talking to users. In the process, Google will confirm to users what kind of information they want to use-for example, who they want to send information to, and what kind of information to send. Once the confirmation is complete, the information is sent out. In addition, users can also use voice to enter information, they just say, well, Google, send a message to (contact name): I may arrive at the meeting one o'clock in the evening. Google will send such information. The interesting thing about this interface is that it doesn't show the user what information is about to be sent before it sends the message. Instead, Google will repeat the information that is about to be sent and ask if the user is willing to send it. Of course, users can also manually send information without waiting for Google Voice commands to start. This approach is very intimate, because it is dangerous for users to see the display in the driving process. The car version of Android uses voice interaction to significantly reduce the distraction of users during driving. It also makes clear why Google prefers to use voice commands in search capabilities to reduce the number of hands-on operations. Other things voice commands can also activate navigation and general search functionality. The car icon on the right-hand side of the auto version will also display information about the car, which the automaker decides. In addition, there is evidence that users may also see Google Now in a separate area of the interface. The final version of Android's actual interface will ultimately be decided by the automaker. But it's not hard to imagine that a basic Google-style interface will appear at least in the first car version of Android. But that's not to say that what we've just seen is the final version. The car version of Android is still being developed, so it can still change a lot before it is released.