📱AAWireless Two+ / -Wireless- Apple Carplay & Android Auto dongle

[MrGneissGuy]

@MrGneissGuy

Good chance the "acting up" you saw was directly related to "Here We Go".

Recently, I have been seeing atypical behavior too .... ..... I have narrowed down that atypical behavior to "Here We Go"...

Once I take Here We Go off of Android Auto's launch list the atypical behavior when using Wireless Android Auto/AAWireless dongle) is history.

.

I deleted Here We Go and I'm still getting the issues. I haven't done a factory reset yet, as I want to try a new cable first to see if that fixes it. What I can't tell, as I'm driving and don't want to start staring at screens, is if the problem is the AAWireless connection to the UConnect or if it's the connection between my phone and the AAWireless. Though if I leave the AAWireless unplugged long enough, it will usually start working again for a while. It actually seems to be increasing in frequency and is getting harder to get back up and running. I'm picking up a new cable on my way home today and will let that go a couple days, then if I still have issues, I'll do a factory reset.

It is probably coincidence, but a few times when the connection was lost I was in the same area where I would temporarily lose connection with the MA1. The MA1 would reconnect on its own when I got out of that area, the AAWIreless is not.

Sponsored

 

[BullMoose1776]

I have recently noticed 2 intersections in my little Texas town, one in town, one just out of town, same "highway", and when I am caught at the light at either of those intersections, the MA1 just flat out stops functioning.

I have had the same experience on i-10, in one particular place, very remote from towns or cities.

Any ideas?

I can only speculate; maybe it's the controllers of the lights or cameras, and there is an electronic interference with the wireless signal of the MA1.

 

[Rhinebeck01]

I have recently noticed 2 intersections in my little Texas town, one in town, one just out of town, same "highway", and when I am caught at the light at either of those intersections, the MA1 just flat out stops functioning.

I have had the same experience on i-10, in one particular place, very remote from towns or cities.

Any ideas?

I can only speculate; maybe it's the controllers of the lights or cameras, and there is an electronic interference with the wireless signal of the MA1.

@BullMoose1776

The MA1 is running with 5G ... there is an operational requirement for both the MA1 and the smartphone on 5G to stop transmitting and change channel, if the device detects any sort of radar.

With that said, that is undoubtedly why you are seeing the disconnects and reconnects you mention.

Note: The AAWireless , Android Auto Wireless adapter's companion app allows the AAWireless to be switched to run on 2.4G versus 5G and thus running 2.4G, not be impacted by the above disconnects and channel changes.

I have not used the companion app to have my AAWireless run with 2.4G as I have not had the need to thus far at my current locale.

.

 

[Ratbert]

@MrGneissGuy

Good chance the "acting up" you saw was directly related to "Here We Go".

Recently, I have been seeing atypical behavior too .... ..... I have narrowed down that atypical behavior to "Here We Go"...

Once I take Here We Go off of Android Auto's launch list the atypical behavior when using Wireless Android Auto/AAWireless dongle) is history.

.

I'm seeing similar behavior w/o Here We Go. AAWireless disconnected four times today during two hours of driving. It eventually reconnected.

While on the trail yesterday UConnect completely forgot my Pixel 7 Pro's Bluetooth connection twice. I had to manually add it back in both times. That was weird / unexpected.

Note that this seems to have started with the January Android update.

 

[Rhinebeck01]

I'm seeing similar behavior w/o Here We Go. AAWireless disconnected four times today during two hours of driving. It eventually reconnected.

While on the trail yesterday UConnect completely forgot my Pixel 7 Pro's Bluetooth connection twice. I had to manually add it back in both times. That was weird / unexpected.

Note that this seems to have started with the January Android update.

Whoa.... hold up... I never said anything about any disconnect issues, forgetting of phone or anything of that magnitude.

All I had, was Here We Go acting abit off the wall lets say.. Mainly, it asking me to unlock the phone and open the Here We Go app before I could make selections in Android Auto.

Anyway, all that went away as soon as I took Here We Go off of the Android Auto, load list.

My AAWireless is running great. 150 mi. trip today and no issues with Wireless Android Auto.

I am running Android Auto 8.7.130204-release.daily beta. Using a Samsung S22.

.

 

[Ratbert]

Whoa.... hold up... I never said anything about any disconnect issues, forgetting of phone or anything of that magnitude.

All I had, was Here We Go acting abit off the wall lets say.. Mainly, it asking me to unlock the phone and open the Here We Go app before I could make selections in Android Auto.

Anyway, all that went away as soon as I took Here We Go off of the Android Auto, load list.

My AAWireless is running great. 150 mi. trip today and no issues with Wireless Android Auto.

I am running Android Auto 8.7.130204-release.daily beta. Using a Samsung S22.

.

Sorry, I shouldn't have quoted you with those comments. Mine's just been acting weirder than usual after the latest Android update.

 

[NeilP]

For those with... who are running with an AAWireless dongle....

DO, update your AAWireless companion app. Get the AAWireless for Android Auto™ 3.12.0 update here.. Made available by AAWireless today, 1/26/23

Note: This is a new version of the AAWireless companion app.... it is not a firmware upgrade for your AAWireless dongle itself.

Can you pair the wireless adapter (MA1) to multiple phones or is it limited to just one?

 

[Rhinebeck01]

Can you pair the wireless adapter (MA1) to multiple phones or is it limited to just one?

Yes, you can pair with more then one Android smart phone with the MA1 and the AAWireless dongles.

IF you have not purchased a dongle yet, do read through the whole thread. AAWireless is the pic of the litter to use with the JL/JT... read through the whole read and you will read why.

 

[NeilP]

Yes, you can pair with more then one Android smart phone with the MA1 and the AAWireless dongles.

IF you have not purchased a dongle yet, do read through the whole thread. AAWireless is the pic of the litter to use with the JL/JT... read through the whole read and you will read why.

I purchased the MA1 and it arrived today. I'm already wishing that I'd purchased the AAWireless.

 

[Rhinebeck01]

I purchased the MA1 and it arrived today. I'm already wishing that I'd purchased the AAWireless.

Well, you could return the MA1. Easy to do if purchased from Amazon, especially.

The interaction of the MA1 and your smartphone for 1 hr. after ignition is off will really annoy most guys. I know it annoyed me.... otherwise the MA1 is aok.

 

[NeilP]

Well, you could return the MA1. Easy to do if purchased from Amazon especially.
The interaction of the MA1 and your smartphone for 1 hr. after ignition is off will really annoy most guys. I know it annoyed me.

It was a "seller doesn't accept returns" eBay purchase. I'm just gonna bite the bullet and order the AA Wireless and I'll off the Motorola to another eBay user.

 

[MrGneissGuy]

I'm seeing similar behavior w/o Here We Go. AAWireless disconnected four times today during two hours of driving. It eventually reconnected.

While on the trail yesterday UConnect completely forgot my Pixel 7 Pro's Bluetooth connection twice. I had to manually add it back in both times. That was weird / unexpected.

Note that this seems to have started with the January Android update.

I got mine back running mostly normal. I did the reset through the app (though at the time, it said it couldn't do it, but when I opened the app later, I had to go through the initial setup process again), and got a new cable. I'm not sure which did the trick, though I suspect it was the cable.

I say mostly because, oddly, it is actually disconnecting at the exact same spot on my work commute that the MA1 was. Having said that, it seems to reconnect faster than the MA1 did. I'm hoping that some future firmware update will stop that from happening.

 

[Rhinebeck01]

Slightly off topic but related.... Do update your Waze to the beta version that was released on 1/23/23 .... 4.91.70.700 beta

I have been running since 1/23 and lots of miles.... the version is stable..

Yes, a beta version but do update to it... much improved.... no, don't ask me to tell you how. Can tell you though if you are in Waze, do this upgrade. You will like....
https://www.apkmirror.com/apk/waze/...c-alerts-live-navigation-4-91-70-700-release/

 

[Rhinebeck01]

I got mine back running mostly normal. I did the reset through the app (though at the time, it said it couldn't do it, but when I opened the app later, I had to go through the initial setup process again), and got a new cable. I'm not sure which did the trick, though I suspect it was the cable.

I say mostly because, oddly, it is actually disconnecting at the exact same spot on my work commute that the MA1 was. Having said that, it seems to reconnect faster than the MA1 did. I'm hoping that some future firmware update will stop that from happening.

@MrGneissGuy

Glad you got it squared away!

The cable, its max transfer speed, etc. make a big difference.
I did not even both using the AAWireless cable and just from the get go went with a superior cable.

You may very well find if you change the Wifi settings in the companion app that you will no longer see that disconnect on your commute. Try 2.4 or a different 5 channel... higher channel # the better.

Reality is though, since the AAWireless reconnects so fast after a signal related disconnect that the disconnect is no big deal.

MA1 uses .... Channel 150 by the way

 

[MrGneissGuy]

So yesterday I tried switching the WiFi to a higher channel. Everything got all screwed up again (the AAWIreless flashing green, no connection to the UConnect, spotty connection to the phone). I tried switching it back, still messed up. Switched it to auto, still messed up. Reset my phone, reset UConnect, unplugged AAWireless, no luck. Deleted cache, nothing. Deleted all storage on my phone for AAWireless and Android Auto and went through the setup process for the AAWireless from scratch. Got it back.

And bonus, this morning I didn't lose connection in that spot (we'll see about heading home in a bit), AND I have CoolWalk running. Didn't get much chance to mess with it, but I mostly like it. Already a couple of things I'd like to see with it, though honestly it may be there in the settings someplace, so I'll hold off on saying anything further on that.

Sponsored