Send it to me first so I can test it in my 2021 RDX. I'll even pay for your postage both ways (to return).

In any case, I have AAwireless now, but the damn connection keeps dropping out. I need to rule out the device to place blame on the Pixel 6 Pro but, you know, everybody and their mother--and bots bought the MA1 and are going on ebay for a kidney and liver smh.
Seriously though. Don't return it. I'm beginning to wonder though. When I had the Pixel 5, Android 11, no issue. Android 12 = disconnects.

 

My Samsung Note 10+ updated to Android 12 last week and so far no hiccups with the MA1.

 

No issues with my Samsung S20 Ultra, Android 12 and the AAWireless dongle, either. Looks like they made some good changes to Android Auto on the process. About to upgrade to the S22 and hoping that doesn't break anything.

 

As a fellow android user, I don't like how Google Maps shows random locations when the map is selected. I was also disappointed to see that the right part of the screen won't show the current song that is playing through Spotify, but instead just says 'Android Auto' for currently playing.

Currently using an s20+ but I haven't tried in again in a few months so there may have been updates to AA since then. My work phone is an iPhone 11 and it doesn't suffer from either of these issues. What are your thoughts on AA?

 

The maps are a bit more cartoonish than the Acura NAV, but more usable due to all the Google capabilities. It doesn't seem to handle other apps very well. I have them all turned off. Music from the phone is confusing. You can play it through AA or through the car's BT link. I like the latter better. I've upgraded to the S22 Ultra, with Android 12 and OneUI 4.1. Seems to work the same Not sure what you mean about maps showing random locations. Mine starts out showing the present location.
The AAWireless thing works ok, but it kinda takes over the whole entertainment system after about 30 seconds. I generally plug the phone in via cable, because I need to charge it if I'm using it for longer drives anyway.

 

I did some testing last night with both phones and there's a few limitations of AA that bug me.

1. I can't open Google Maps on the phone while I have AA open in the car. I can get around this by having Waze as well, but that seems counterproductive as my work iPhone allows Google Maps to be open while displaying it in CarPlay.
2. Use of the Acura wide/split screen. I touched on this before, but not making full use of the right third of the screen for audio while having Google Maps open is another disappointment. If I have AA open, the right portion just states 'Android Auto' for audio and doesn't display the album art or track info, yet if I go back to the Acura Maps it shows up. CarPlay does not have this issue, as it'll display the full map in the 2/3rds and the audio info in the 1/3rd. Whether this is an Acura issue or an AA issue, I do not know.
3. Google Maps in AA has the search bar at the top left, which is fine, but when driving without a destination inputted, it'll pull up all the old places I've searched as it tries to predict where I want to go. That's cool and all, but I should be able to turn this off, as it takes up a good portion of the screen real estate. CarPlay Google Maps does not have this issue. Plus the maps themselves just seem to be much better looking in Apple than in Android.
4. Why is there no split screen view for maps and audio like iOS has? For smaller (and normal ratio) screens, it's perfect!
5. The touchpad with both iOS and AA is a pain, as it functions like a mousepad on a laptop, without seeing the cursor. I wish it kept the true touch interface. Hopefully the next gen RDX is redesigned to have a touchscreen as well.

To preface, I've been an Android user since '09, and for my daily driver I will always be. But I just like the implementation of how CarPlay is done in the RDX. Moving forward I'll probably just hook up the work iPhone when I need to use turn by turn. So much more convenient. IF Google fixes AA to allow you to open maps while connected to the car while using the Acura Maps so I can see the album art, I may consider getting a wireless dongle. It's rare I need turn by turn, but seeing album art instead of the Bluetooth logo may make the purchase worth it to me.

 

Good comments. This implementation strikes me as one that Google half-assed to get it out the door. It took them forever to get it done in the first place. If I let AA manage the Bluetooth, it flashes the name of the next track on the screen, which just gets in the way. Probably the most infuriating thing is your item 5. Using relative positioning on the touchpad just doesn't work - especially since you can't set the sensitivity. You scroll forever, can't tell where the cursor went, and it's too much head-down time while driving. As much as people complain about it, the absolute positioning Acura uses for their side of things is the right implementation for a moving vehicle.

 

My biggest complaint was the change in touch pad performance when using AA. IF it stayed absolute positioning it would be fine, otherwise give me a touch screen.

OH, and I have the Motorola MA-1 for wireless Android Auto that I use in my current vehicles... it works well.

 

Agree 110% JB in AZ . . . absolute positioning for AA should have been the only option for Acura. I use Google Assistant for almost everything in order to eliminate the need to interact w/the touchpad. The HUD and steering mounted controls help a ton as well.

Also have the MA-1 . . . works flawlessly!

 

Looks like we're getting an update to Android Auto here soon:

https://www.autoblog.com/2022/05/16/...2022-new-look/

My question is how will it work with the way Acura splits their screen.