But, Google dropped Android Auto from Android Version 12?
Not sure if that is a question but Google dropped Android Auto FOR PHONE SCREENS from Android 12. Android Auto for Phone Screens shutting down 'soon' - 9to5Google
4 Likes
If you havenât followed the issues on the Android app repo, you must have missed that Android Auto support was there for years, due to what limitations/barriers Google put in the way.
Just recently an opportunity have arisen to add Android Auto support to the app, as Google published some new ways to integrate apps. And they guys jumped on the opportunity and added it in the simplest way to see if the Google published documentation working or not. Nobody expected anything fancy as it is the first iteration. It is just awesome that finally the app is available on Android Auto, officially. A huge step forward.
I was one of the first people who tried it and since then I added the first feature request for Android Auto to add a way to declutter it, limit the number of entities, etc. And once something new will be added, I will grab the latest release of the app from GitHub and I will try it and give feedback. If I would know more how to code it, I would do that as well, but unfortunately I donât have enough knowledge for that.
I am really thankful how @dshokouhi and the others are managing and developing the Android app.
9 Likes
Hear hear!
1 Like
Yes, that would make it a lot easier and more safe to use.
I would be happy with just a favorites view as default view. Now I have a lot of entities to scroll thru to get to my âturn off alarmâ.
Open the garage door was easier 
I have the home assistant mostly working in my 2020 Ram truck, but what doesnât work is the navigation part. It says Android auto isnt responding. What am I missing for that feature?
Brian
I already have that selected Deedzy, but thank you for the reply.
Brian
1 Like
does this happen when trying to view the list of items in navigation or when attempting to navigate to an entity?
I can access the entities, switches, scenes, and all the other options, but just not the the Navigation option. I even tested some of my home lights from my truck and it worked fine. That tells me home assistant is working properly at least.
Brian
Are there any errors in the companion app on the phone?
No errors, companion app works great.
Brian
Make sure to open the phone app, reproduce the issue in android auto and then check the companion app logs for errors.
Settings > Companion App > Show and share logs.
When you select Navigation you should see a list of supported device trackers, zones, persons and sensors that have location coordinates so its possible some entity is not playing nice and the logs will show that.
Thank you for the advice, I will do that next time. Currently at work. Will check on drive home or might possibly sneak out to the parking lot here in a bit 
Brian
Here are the first few lines of the log after I selected Navigation from the menu:
04-17 21:22:06.092 18930 18962 D LogcatReader: Done reading logcat for pid 18930
04-17 21:22:09.310 18930 18930 I MainVehicleScreen: Navigation clicked
04-17 21:22:09.355 18930 18930 W BpBinder: Large outgoing transaction of 1666352 bytes, interface descriptor <uncached descriptor>, code 2
04-17 21:22:09.355 18930 18930 E JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 1666352)
04-17 21:22:09.355 18930 18930 E CarApp.Dispatch: Host unresponsive when dispatching call getTemplate onSuccess
If more is necessary I can post it. Didnât want to take up too much room
Brian
Can you please open a new issue on GitHub with the logs and issue template completed? Mention the steps you take to reproduce the issue. Also please mention how many zones, device trackers, person and sensors with location coordinates you have. Those entities need to have longitude and latitude as separate attributes to get picked up. The error sounds like too many entities but tough to tell. We may need to debug more in the issue.
OK, will do. I only have 2 device trackers and persons, but I do have quite a few zones for the map, about a 150 to 200 maybe. TY for help
Brian
1 Like
This is an awesome feature.
One problem is I use firmata auto to access my HA with web. But canât log in. The username and password input textbox not working somehow. Probably Firmata bug
I figured out, it must be a refresh issue. I was just sitting in front of it, when two entity was updating the last changed time, and every time when a new time was displayed, like changed from â5 seconds agoâ to â7 seconds agoâ, the selector was flashing. With longer lists it must be longer period to get a full refresh, ao the last position of the cursor must be stored when scrolling through and the refresh puts it back to the last saved position before the refresh.
Not too many comments lately. Curious if not many people are using this or is it just problematic? As previously stated, everything works on mine except navigation, and to me it is the most important part.
Brian