|
>do you have either? have you switched phones because your car >only had one? (i think my coworker just did this lol)
old car I added a head unit specifically so I could do this. new car has both.
>i got it in the new car and im still a bit eh about it. i have >an android, the car has both options. > >let me know why i should be using it. what are some cool >things i should know about? > >what i know right now is i need to plug-in my phone to usb, it >will play my music at full quality (nice) and make it really >inconvenient for me to actually use my phone while driving >(ok). i think google maps will display in dash too if i need >navigation so thats cool.
the one reason I dropped Geld on a head unit 3 years ago: to get my phone's navigation on my car's screen. now back then I was still using my iPod for actual music (because Android Auto's controls for such are still... trash)
now it's a little more usable, but I still have to use a second app (OBD2AA from the XDA Labs app store) to take away the chief thing that pisses me off about Android Auto: the screen touch limit.
trying to get you to use your voice for everything is just bullshit. more on that later.
>i dont like having to plug-in but i might get used to it. if i >need navigation then i think its very worth it. even for any >long trip. for getting to work in a rush i want to just jump >in the car and go. so far it has a delay and sometimes gives >me an error that the phone is not responding. i have an s8 >with a wireless charging mount so im used to just dropping it >in there. having to unplug the cable from the mount to plug in >my phone is kind of annoying but could be worth it. > >definitely like the quality of the audio and the fact that i >can still use the steering wheel controls to change tracks >instead of fumbling with my phone if i were to use aux. >displaying the music in the dash using google play looks >awkward but its good to have the music info in the dash unlike >aux.
some cars can support wireless Android Auto, but you have to basically have in-car wifi for that. and I think certain phones are eligible. The Pixel is one.
>also, i got a message the other day while driving, i got the >notification on my phone first then in the dash. the dash >showed i got a notification but i had to press home then click >on the message in order for it to play it. that seems dumb. >are there options for this? i would like an audio prompt >asking if i want to listen to the message or dismiss it. >having to touch the screen while driving seems to defeat the >purpose of it. i have to be doing it wrong right??
technically you can "OK Google" and ask to read your messages (or touch the voice button on your car's steering wheel/the screen). I haven't done that in a while, though.
>for now im thinking ill stick to bluetooth for my work commute >but use android auto for other drives.
you can actually still use Android Auto directly on your phone without plugging it in. instead of fumbling through the controls of your phone, the Android Auto screen takes over your phone and you can still do the voice commands for music, messages, and navigation while your phone is mounted (like on an airvent, etc).
Now let me talk about CarPlay:
CarPlay is actually superior for driving use, now that it supports Google Maps and Waze. for one: no scroll restrictions. rewind/fast forward works on the steering wheel, the touch areas are much larger and simplified, and voice controls (such as the ones used to send messages) have on-screen fallbacks (like if you want to confirm, re-do, or cancel a message, there are buttons on the screen for that).
This is probably due to the fact that Apple recognizing that Siri is some shit. But I will say this: Siri easily found the music on my phone when I called for it. Playlists, even. And I have a pretty huge local library, and playlists with some odd names.
Android, it's basically a crap shoot. Which is why for years I used an iPod for actual music. Since an iPhone is essentially an iPod with phone stuff, that's not needed for CarPlay.
|