Android Auto v2.5 prepares to offer navigation cards based on your calendar...

Android Auto v2.5 prepares to offer navigation cards based on your calendar appointments [APK Teardown]

0 18

A fresh update to the Android Auto app began rolling out yesterday, but it doesn’t appear to include any notable changes to the interface on either the phone or in the car. But that doesn’t mean this update is just for bug fixes, there isn’t something interesting floating around inside the apk that can only be seen through the lens of a teardown. We can look forward to at least one important new feature: Auto will soon get to use our calendar appointments to suggest directions when we’re on the way to a destination. As always, grab the apk from the link at the bottom if you don’t have it on your phone already.
Teardown

Disclaimer: Teardowns are based on evidence found inside of apks (Android’s application package) and are necessarily speculative and usually based on incomplete information. It’s possible that the guesses made here are totally and completely wrong. Even when predictions are correct, there is always a chance that plans could change or may be canceled entirely. Much like rumors, nothing is certain until it’s officially announced and released.
The features discussed below are probably not live yet, or may only be live for a small percentage of users. Unless stated otherwise, don’t expect to see these features if you install the apk.

Calendar access
Android Auto is often criticized for being a bit too cautious and missing opportunities to do good things with information from Google’s assorted services. While there’s much left to do, the in-car experience is about to get just a little more intuitive about your schedule. Android Auto will soon be able to access your Google Calendars and offer timely directions to your upcoming appointments.

Next, allow Android Auto to easily work with navigation, music, calls, messages, calendar, and voice commands.
Need directions to your next appointment?Tap to give Android Auto

Article originally published at: Android Police