Now I know Google has a lot of very smart people, but you would be hard pressed to prove that to me based on some of the rather inexplicable design decisions made for Android Auto, especially when you consider that one of its primary goals is to minimize distraction when interacting with Android.
Let's start with the voice button. I know it is in the top right corner of our phones and tablets, but that is a lousy reason to locate it in the same place on your car's display. For US drivers, it seems the most inconvenient place for it.
Moving on to how messages are handled, it feels as though Google wants your right hand off the wheel, and your eyes off the road. Consider that when a message comes in, Android Auto interrupts your audio to inform you of that. Does it read it to you, or offer to read it to you at that point? No. It expects you to touch the top of the screen, but you better do it quickly as it will be gone in a few seconds. Then you will most likely have to make several taps on the screen to have Android Auto read you the message, and return to the screen you were previously on.
And when it does read you a message, it tells you can reply by tapping the voice button (that one at the far right corner of the screen). Why doesn't it just ask you if I want to reply instead of requiring more physical interaction with the screen?
There are other distractions as well, albeit fairly minor when compared to the above. For instance, when my phone is connected solely via Bluetooth and I am listening to something, when I exit and then return to my vehicle, playback resumes. But if I'm connected to Android Auto, again I am required to interact with the screen. It is the same with navigation... turn off the car for any reason and you will have to reestablish your route again when you startup.
Now maybe it's just me, but having Android Auto for just a week or so, these seem like pretty big potholes on the road of usability, and some seemingly so obvious that I'm was surprised to experience them.
So, is it really just me? How do you feel about Android Auto's workflow? Do you find it unnecessarily distracting? Does it require more of your attention than it should?
AA has many issues that need to be fixed.
But I feel confident that Google WILL fix these things.
Connected cars are and will be BIG business and Google will not abandon it as they've done with some other things.
Consider how much was fixed and improved in Android itself from v1 through to 5.1.
Note that we've all been waiting for decades for something like AA in our cars. Google has been working on AA for years, and it will take years more to work out the kinks.
Plugging a phone into an AA head unit is a model that has problems but is somewhat temporary. Googles goal is to have Android itself running in the car or HU* and this solution will be superior. I think we will hear more about this at I/O; Android 6 allegedly has AA "baked in".
*Many HUs (Pioneer, Chinese) are already running Android and I think Honda is working on this now.
AFAICT, most people who have seen AA and Apple CarPlay prefer AA, so Google has the advantage here.
mikereidis said:
Consider how much was fixed and improved in Android itself from v1 through to 5.1
Click to expand...
Click to collapse
I have... which is a big reason why I bit the bullet. For me, Android was way too rough 'till JB (which is when I switched from iOS). I am hopeful AA's path will be on road with a much higher speed limit.
Have just returned my Xtrons unit due to various issues, and looking to change it for a proper Android Auto unit.
Had a look at the Pioneer AVH-X8700BT and quite disappointed, horrible buttons and a creaky flexy facia, and the onscreen menus etc are cluttered and unintuitive. This is a shame as I could have got 20%/£100 off in Halfords.
So interested to hear from anyone who has tried the others. I keep seeing comments about a JBL unit but it seems the launch date keeps getting shoved back. Kenwood - I've not found much about these but not hugely impressed by the look of the on screen menus in the static photos.
The one that has really got my attention is the Sony XAV-AX100 that has supposedly just been released. The unit looks smart and doesn't appear to need neon footwell lamps and extra boost gauges to complement it, (!) and the Sony menus have similar clean/uncluttered look like the Android Auto section. Apparently its only available via Sony Centres and both my local stores haven't come back yet with availability
I agree with your analysis of the options but i don't think the Sony product is released until December:
https://www.amazon.co.uk/exec/obidos/ASIN/B01LY8222N/geizhals07-21/ref=nosim?m=A3P5ROKL5A1OLE
I personally got the Pioneer F88DAB (which is a european model) and I like the way it works. the menu is working quite well and I like the fact that I am able to adjust the screen tilt.
Android Auto works great at the device and I will upload a video of the device with android auto, so you can see how the menu and all the functions look like.
amazon
that JBL has been pushed back so many times, I would not have any faith in it. The top of the line Kenwood is over a grand, but I have seen some really good reviews on it and few bad reviews. That was my backup plan if I didn't like my Joying, but I love my Joying
Sir_Nomad49 said:
I personally got the Pioneer F88DAB ...amazon
Click to expand...
Click to collapse
At £850, it's poor value - you could professionally install a tablet for a lot less. I think I'll wait for the Sony for x-mas
kc1 said:
At £850, it's poor value - you could professionally install a tablet for a lot less. I think I'll wait for the Sony for x-mas
Click to expand...
Click to collapse
That is true, but it was easier to install and I personally like the interface of it.
The Sony is a good choice. With a pioneer device you can use appradio or mirra cast.
When I am home, I will upload a video on how it is usable.
Sent from my SM-N9005 using XDA Free mobile app
kc1 said:
I agree with your analysis of the options but i don't think the Sony product is released until December:
https://www.amazon.co.uk/exec/obidos/ASIN/B01LY8222N/geizhals07-21/ref=nosim?m=A3P5ROKL5A1OLE
Click to expand...
Click to collapse
I'm also looking forward to getting the Sony unit later this year. :good:
CayenneGTS said:
I'm also looking forward to getting the Sony unit later this year. :good:
Click to expand...
Click to collapse
Looks like it's available to order now
http://amzn.eu/1V2elbz
http://a.co/byhPOFu
Sir_Nomad49 said:
I personally got the Pioneer F88DAB (which is a european model) and I like the way it works. the menu is working quite well and I like the fact that I am able to adjust the screen tilt.
Android Auto works great at the device and I will upload a video of the device with android auto, so you can see how the menu and all the functions look like.
amazon
Click to expand...
Click to collapse
I have the previous model the Pioneer F77 DAB. Works very well. Back in the day halfords had it for something over £800 then by accident halfords listed at £600 so reserved one sharpish. Couple of days later it was back at its original price. I think someone had cocked up.
Far as android auto is concerned it works faultlessly. It's pretty quick booting up from off and reverse camera works straight away, not having to wait for unit to boot. Occasionally when turning vehicle key to on unit comes on as normal but if you then hesitate to start engine it seems to crash and take maybe a minute to boot again. Even reverse camera does not work when this happens. Unit comes on when key is turned to power but cranking engine robs power from unit so it turns off and on again. The crash is something to do with the stage of boot when power drops. In all the time I've had it, it has only happened maybe half a dozen times. Other than this it works faultlessly. Pioneer want stupid money for mapping updates for the built in satnav on the downside but half the time I use Google maps in AA for quickness. Pioneer has an app to connect the phone to on board sat navigation - AVICSYNC. It works but is very clunky. Waiting for Waze to become AA compatible but not holding my breath on that one.
Well after failing miserably with two local Sony centres and also Sony online, I managed to find the unit for sale on Amazon! I'd set my heart on it and after three months with a gaping hole in the dashboard, its finally fitted!
First of all, its single DIN behind the facia so plenty of room for wiring looms, and simply slides in unlike the Android units that would need 30 minutes of trying to pull the cables around and still failing to get the facia flush. Also, as expected, it comes with a cage and standard mounting brackets so no bodging needed. Once fitted the unit sits neatly within the existing double din facia.
It starts up fast, works with my factory fitted reversing camera (unlike the Android units) and is simple to navigate. I was concerned about the 'cheap' resistive screen, but its actually very responsive and only needs a light touch.
The only issues I have so far;
1) The volume control knob needs a fair bit of spinning, it needs two or three goes to crank the volume down. I need to check the settings again to see if you can make the adjustment less fine.
2) If I connect the phone and play music on Spotify, and then start the engine, the unit powers down as normal during engine start. When it resumes, the music starts playing on the phone...I have to swipe across to a second screen and press a '+' speaker button to get the audio back through the vehicle speakers. A bug with my phone, or the radio? Something to look in to.
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
4) Just to answer my own questions about the unit; No, the facia is not removable. No, it doesn't come with a remote control (a shame for a campervan!) And unlike the Android units, everything works seamlessly. i.e it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load, and if you start the radio, Spotify etc will stop, rather than having two lots of audio competing for your attention
Spooky_b329 said:
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
Click to expand...
Click to collapse
Android Auto uses the phones GPS and maybe accelerometer to know when you've stopped.
On my Kenwood unit the handbrake sensor is grounded all the time and I still get that message.
Spooky_b329 said:
Well after failing miserably with two local Sony centres and also Sony online, I managed to find the unit for sale on Amazon! I'd set my heart on it and after three months with a gaping hole in the dashboard, its finally fitted!
First of all, its single DIN behind the facia so plenty of room for wiring looms, and simply slides in unlike the Android units that would need 30 minutes of trying to pull the cables around and still failing to get the facia flush. Also, as expected, it comes with a cage and standard mounting brackets so no bodging needed. Once fitted the unit sits neatly within the existing double din facia.
It starts up fast, works with my factory fitted reversing camera (unlike the Android units) and is simple to navigate. I was concerned about the 'cheap' resistive screen, but its actually very responsive and only needs a light touch.
The only issues I have so far;
1) The volume control knob needs a fair bit of spinning, it needs two or three goes to crank the volume down. I need to check the settings again to see if you can make the adjustment less fine.
2) If I connect the phone and play music on Spotify, and then start the engine, the unit powers down as normal during engine start. When it resumes, the music starts playing on the phone...I have to swipe across to a second screen and press a '+' speaker button to get the audio back through the vehicle speakers. A bug with my phone, or the radio? Something to look in to.
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
4) Just to answer my own questions about the unit; No, the facia is not removable. No, it doesn't come with a remote control (a shame for a campervan!) And unlike the Android units, everything works seamlessly. i.e it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load, and if you start the radio, Spotify etc will stop, rather than having two lots of audio competing for your attention
Click to expand...
Click to collapse
Re "And unlike the Android units, everything works seamlessly", not true - please see your points 1 and 2 !!
Re "unlike the Android units . . . it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load", Android units per se dont have this problem, one particular type, with only 1GB RAM, Lollipop and a later version of Google Maps does, this can easily be sorted.
Glad youre happy with your new unit, enjoy.
Spooky_b329 said:
Well after failing miserably with two local Sony centres and also Sony online, I managed to find the unit for sale on Amazon! I'd set my heart on it and after three months with a gaping hole in the dashboard, its finally fitted!
First of all, its single DIN behind the facia so plenty of room for wiring looms, and simply slides in unlike the Android units that would need 30 minutes of trying to pull the cables around and still failing to get the facia flush. Also, as expected, it comes with a cage and standard mounting brackets so no bodging needed. Once fitted the unit sits neatly within the existing double din facia.
It starts up fast, works with my factory fitted reversing camera (unlike the Android units) and is simple to navigate. I was concerned about the 'cheap' resistive screen, but its actually very responsive and only needs a light touch.
The only issues I have so far;
1) The volume control knob needs a fair bit of spinning, it needs two or three goes to crank the volume down. I need to check the settings again to see if you can make the adjustment less fine.
2) If I connect the phone and play music on Spotify, and then start the engine, the unit powers down as normal during engine start. When it resumes, the music starts playing on the phone...I have to swipe across to a second screen and press a '+' speaker button to get the audio back through the vehicle speakers. A bug with my phone, or the radio? Something to look in to.
3) There is a limit to how many menu presses you can navigate, and unlike running Android Auto on the phone, instead of a momentary warning, it sticks until you navigate back home. Thats fine, although really irritating if your passenger is trying to find some tunes. But it does the same when stationary...I'm sure my handbrake is wired correctly but regardless, I'll be over-riding that feature as its in a campervan and I normally have a passenger!
4) Just to answer my own questions about the unit; No, the facia is not removable. No, it doesn't come with a remote control (a shame for a campervan!) And unlike the Android units, everything works seamlessly. i.e it doesn't freeze or get laggy, you don't need to wait ages for the unit to boot or Google Maps to load, and if you start the radio, Spotify etc will stop, rather than having two lots of audio competing for your attention
Click to expand...
Click to collapse
My unit came with a remote. I also find what I believe is a software bug, if you turn on the dimmer the maps will always be in night mode.
leonkernan said:
Android Auto uses the phones GPS and maybe accelerometer to know when you've stopped.
On my Kenwood unit the handbrake sensor is grounded all the time and I still get that message.
Click to expand...
Click to collapse
I've got the same issue. As of 2.0 Android Auto uses the head units' GPS data. If your head unit doesn't have built in navigation (GPS), it won't remove the limitation even if stationary.
Link: https://productforums.google.com/d/msg/android-auto/8mvJEDnJUpU/pmejOMunAgAJ
terre08 said:
My unit came with a remote. I also find what I believe is a software bug, if you turn on the dimmer the maps will always be in night mode.
Click to expand...
Click to collapse
I found out it's by design by reading the user manual a bit better. The dimmer is connected to the headlights and when you turn on the lights it will go into night mode, unfortunately I use the lights 24/7 so I will install a toggle switch instead to turn on/off the daylight and the night mode. Pioneer has a a similar setting using the headlights but they also have a setting where you can set the time for night mode, hopefully Sony will have something similar in a future update.
Thanks for the replies!
I've worked out that the unit is detecting the handbrake as the video playback from an SD card is interrupted. I see the comment about the Sony not having built in GPS causing Android Auto to keep the 6 press limit, thats annoying, lets hope its fixed in an update. Surely it can use my phones GPS signal to work out when I'm stopped!
Terre08, I'll send you a PM regarding your remote...interesting!
I have a moto x pure connected with chevy volt using android auto. It used to work perfect with the stock rom.
Recently I have installed the orionos custom rom, and the screen resolution in the car is totally wrong. I can only see the very top left portion of the screen, I think it is a screen resolution issue, but do not know how to solve it.
Any help is appreciated.
same issue
I have a brand new Skoda connected to an LG Optimus G updated to Android 6.0.1 and exactly the same issue. The screen is completeley screwed up and showing only the top left quarter of the screen way too large (huge fonts, etc.) Is there a way to fix this? Would even be good to know if this is a bug in the phone, in the car system or in the Android Auto app.
Anyone else facing this?
Is it possible you may have downloaded a 1024x600 rom instead of a 800x480?
I have a HTC 10, completely stock rom and a Pioneer head unit. Maps always worked perfectly in over a year with this phone and previous phone.
About a week ago I started to have this same issue. Maps is totally useless since.
I will try and get a photo tomorrow and reply again with it.
Just to let you know not only one.
I could fix my display issue by upgrading my phone to an Android 7 custom ROM.
duflez said:
I have a HTC 10, completely stock rom and a Pioneer head unit. Maps always worked perfectly in over a year with this phone and previous phone.
About a week ago I started to have this same issue. Maps is totally useless since.
I will try and get a photo tomorrow and reply again with it.
Just to let you know not only one.
Click to expand...
Click to collapse
Same thing here, HTC10, but with stock+magisk/xposed, same issue in Maps - until I saw this I thought that is because of one of xposed module. I cleanup the storage data several times, reinstalled aa also, disabled magisk/xposed, played with app settings xposed module in order to try to change the screen dp. Could not find the issue.
Interesting part is that on the same car but with different phone (moto x 2nd, xposed, same aa version, same google maps version) the Maps is displayed properly.
I have the same problem after updating my rom to a 1024x600. My unit was 800x480 and thats why the screen is cut off. What can i do?
In my case issue was related to Boost+ app "optimization", see this post https://forum.xda-developers.com/htc-10/help/android-auto-google-maps-issue-t3533388
Hi there, i am not too sure if i need to start a new topic, but i guess this is the best way to get your expertise on my issue.
I am driving a seat leon 1p (2008) which had the RNS510 (seat media system so whitout the sd card slot) built in. Sadly the display died (full white) and i had to search for something else.
I bought me a RK3188 device (it says ERISIN in the advert, i cannot find that name on the box or device itself) with a load of nice features. Most of them are working like they should, others have some hickups and 1 is really bothering me. I have made a youtube video and the seller says they don't see whats wrong. I bought it trough eunavi on aliexpress.
Here my explanation, the leon is fitted with a large dot matrix mfd screen in the dashboard (boardcomputer) (there are versions with a smaller display)
the big display is served with the windscreen wiper handle, which has 3 buttons, up, down, and ok/reset.
When i want to reset my computer (trip, avg fuel etc.) i need to press the reset button about 3 seconds. the radio then decides to shutdown... once i release the reset button, the radio decides it doesnt want to shutdown.
Quite weird in my opinion. So i tried programming the wheelkey settings, according to the manual. first i go into wheelkey settings, then i press clear / reset.. then i need to press any wheelkey (so allso the volume up / down, next, previous etc etc.) the radio does respond to that, but not with the wheelkey settings programme. I'll try to add the youtube link here as well.
next to this, some weird things happen.
1.The display is way too bright, so i asked the seller what to do, they told me they will send a new display which i should fit myself. In my opinion not the best solution from a shop but i understand their marigins aren't enormous and they try to fix it cheap. the display hasn't arrived yet so i can't say if the new display gives the solution for me.
2. when i have the tuner on, with af-rds function, it seems to scan to any rds station once the signal gets weak. Maybe i'm spoiled, but i think AF needs to search for the station with the same ID as the one i was tuned in to.
3. the dab+ dongle and window antenna give poor reception now. this is presumeably caused by the way i fitted the aerial, on top of the ventilation shafts behind the dashboard. I want to move the antenna to behind the rear view mirror (horizontally) which will hopefully give good reception. (does anyone know if horizontal positioning of the antenna is okay for dab+ ?)
<- the issue with the MFD input
<- the whiteness of the display (cannot be edited with standard settings) it was quite cold when i made this video, it seems it is a little better now or i am getting used to it
so quite a long story and i have my fingers crossed on your response !
maybe good to let you know:
MCU version
MTCD_LM_V1.90_1
sep 23 2016 09:37:48
Android-sersion
5.1.1
Kernel-version
3.0.101+
[email protected] #90
Fri Sep 9 16:24:49 CST 2016
Build-number
rk3188-userdebug 23092016.13:30:50