• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

AAWireless - General discussion and support

Search This thread

DevAuto

Member
Mar 9, 2013
40
21
Cables people cables¡

Cables, cables cables!!!

I finally got the Motorola I'm using for hopefully a few days going. This afternoon I could see it was doing everything but the headunit was not seeing it for some reason, though nothing had changed since yesterday when it worked that one time.

I brought it inside and reset it on a power supply, took it back to the car and re-did setup from scratch. Same outcome, flashing blue light, waiting for the headunit.

Decided to try my other shorter cable I had before (I went back to using the cables AAW came with due to other testing) and viola, it worked right away and worked again coming home.

Now, I drove home yesterday with the Motorola and 1.3 FW but it seemed quite good. Now I'm on 1.4 and music seems really good, so far. Hopefully this continues when I am using my S20+ again, but earlier this week I used it after a factory reset and I did notice a lot more glitching in the music than of late, sort of like it gets a bit better over time, but still does the odd glitch? I also experienced my first reboot of the AAW device in a while. Headunit did not reset, it was the AAW unit. Not sure how scientific that is.

Either way, I was looking forward to at least seeing how life is with a different phone to compare, so now I will be playing music all the time and then see how it goes with the Samsung later.

I am still noticing on this phone just now that Google doesn't mute the music playing to hear me speak/respond. The music is quieter when Google says something, but when it's waiting to hear from me the music stays at playing volume. Odd. I should test it with a cable.
Yes, cables are important! I'm glad to see it seems to be working for you now. As for the speak/respond issue, I have the same issue sometimes. It seems to be random though, usually it works as expected but sometimes it does exactly what you describe. More interesting is that it starts out working properly, but then after 2 or 3 voice commands it stops muting the music. If I have the music volume low, I can still use voice commands, but if it is turned up, it can't hear my voice over the music. This continues until I disconnect and reconnect to the AAWireless. I have tested with a cable, but have not seen this happen. Unfortunately, that isn't definitive because it is sporadic when it happens, but I will say that I did not have this happening before switching to AAWireless. I'm interested to hear if you have the problem when connected over a cable.
 

alaskazachguy

New member
Jun 10, 2021
2
0
I've had a pretty intermittent AAwireless experience, and I thought 1.3.0 finally got it working smoothly. It worked great for a few days in a row without any problems, then suddenly the wifi refuses to connect. I connect on bluetooth, I can change settings on the device, but it never seems to actually connect to the wifi portion. The light on the device blinks green, and there's no change on the head unit. I can't upgrade to 1.4.0, as it says its trying to connect to the device.

Thoughts?

Pixel 3
2020 Jeep Wrangler
AAwireless on 1.3.0
 

DevAuto

Member
Mar 9, 2013
40
21
I've had a pretty intermittent AAwireless experience, and I thought 1.3.0 finally got it working smoothly. It worked great for a few days in a row without any problems, then suddenly the wifi refuses to connect. I connect on bluetooth, I can change settings on the device, but it never seems to actually connect to the wifi portion. The light on the device blinks green, and there's no change on the head unit. I can't upgrade to 1.4.0, as it says its trying to connect to the device.

Thoughts?

Pixel 3
2020 Jeep Wrangler
AAwireless on 1.3.0
Try disconnecting the AAWireless from your car and connecting it to a wall plug. If you can connect to the settings, I believe you should be able to do the 1.4.0 update. I had a problem updating when connected to the head unit, but taking it out of the car and plugging it into the wall fixed that for me.

Also, @alaskazachguy once you do get it updated, go into settings and try setting USB Mode to "Default" ... It fixes problems for a lot of folks and may make it better for you as well.
 

mc01319

Senior Member
Sep 5, 2010
88
18
Firmware 1.4 was supposed to fix the Nissan problem. USB Mode has to be set to 'Default' in the Settings with the app. Then disconnect and reconnect the device. This method has cured several Nissan models when we were testing it.

Avoid Start / Stop for now.

LeRoy
I confirm that with the "Default" USB setting I have successful functionality with my Nissan Qashqai 2019 J11 and Samsung Galaxy S20+ 5G.
 

alaskazachguy

New member
Jun 10, 2021
2
0
Try disconnecting the AAWireless from your car and connecting it to a wall plug. If you can connect to the settings, I believe you should be able to do the 1.4.0 update. I had a problem updating when connected to the head unit, but taking it out of the car and plugging it into the wall fixed that for me.

Also, @alaskazachguy once you do get it updated, go into settings and try setting USB Mode to "Default" ... It fixes problems for a lot of folks and may make it better for you as well.
Unfortunately even after resetting everything I can find to reset and plugging into a wall, and starting the setup from scratch,it still doesn't want to connect even enough to upgrade the firmware. Not sure what else I can try.

Edit: It's gotten worse. After a reset (pin press for 5 seconds) now the LED is green for about 8 seconds straight, goes out, then back to green for 8 seconds straight, rinse, repeat. Makes me think its in a boot loop. It does this regardless of if its powered into the car or a wall charger.
 
Last edited:

DevAuto

Member
Mar 9, 2013
40
21
Unfortunately even after resetting everything I can find to reset and plugging into a wall, and starting the setup from scratch,it still doesn't want to connect even enough to upgrade the firmware. Not sure what else I can try.

Edit: It's gotten worse. After a reset (pin press for 5 seconds) now the LED is green for about 8 seconds straight, goes out, then back to green for 8 seconds straight, rinse, repeat. Makes me think its in a boot loop. It does this regardless of if its powered into the car or a wall charger.
Have you opened a support ticket yet? https://cpeb.freshdesk.com/support/home
 

Snirpo

Senior Member
Jan 23, 2007
96
121
Unfortunately even after resetting everything I can find to reset and plugging into a wall, and starting the setup from scratch,it still doesn't want to connect even enough to upgrade the firmware. Not sure what else I can try.

Edit: It's gotten worse. After a reset (pin press for 5 seconds) now the LED is green for about 8 seconds straight, goes out, then back to green for 8 seconds straight, rinse, repeat. Makes me think its in a boot loop. It does this regardless of if its powered into the car or a wall charger.
Most probably defective, please open a support ticket at cpeb.freshdesk.com
 
  • Like
Reactions: DevAuto

Genebaby

Senior Member
Dec 11, 2013
680
82
My experience today using the loaner phone via the different cable to last week.

Initially good in regards to audio dropouts, I was thinking, wow, is it my Samsung and this mid tier phone works better? But then the audio glitches came around. The worst one just now on the way home where it stopped completely for many seconds and then I got a new kind of error.

Previously in my VAG cars the headunit hasn't rebooted, but it seems the AA connection was able to be killed and then it will pick it up back up. This time I got a message about APP Connect and I was kicked into the Vehicle Status screen. For the rest of the trip it would not re-connect again. Appconnect didn't do anything and AAW was blinking green, so wasn't connecting to my phone again.

I will be driving again soon so I'll see if it will work next drive.

The audio issue with the Assistant and music. I did a test and right away the Assistant doesn't lower the volume to hear me speak, I have to compete with the volume the music is set to, but when it is talking it lowers the music volume.

I'll drive a bit more with AAW and then use a cable to compare experiences.
 

Genebaby

Senior Member
Dec 11, 2013
680
82
It worked fine the rest of the afternoon, not very glitchy with 1.40 and this other phone, but it can glitch. Still a great experience being wireless.

Next I'll use a cable and see if the Assistant audio muting thing is still happening.
 

djbolden

Senior Member
Aug 23, 2011
62
8
For what it's worth regarding the music playing during interaction with Assistant...

I have the AAWireless in my truck with Ford Sync 3. I also have a car with an aftermarket Kenwood unit with native AA wireless capability. At least a couple of times now it has continued to play music - lower while Assistant is speaking and sometimes still lower while I answer, but I think a couple of time the music has returned to full volume while I was talking. I'll pay more attention - maybe this is an AA bug???
 

benhur06

New member
Aug 15, 2020
3
1
Hello all.
I report a problem with AA (not AAwireless).
Phone : Samsung S10e
Car : Audi A1 40 TFSI with Bang & Olufsen sound (https://corporate.bang-olufsen.com/en/partners/automotive/audi/a1)

For me, AAwireless is working good. No problem of connection, and until now, no disconnection.
I m using AAwireless mostly to have AA connected automatically, without cable, on the MMI, to display a GPS into the MMI (Google, Waze or Sygic)
AAwireless is working really good, but as soon AA connect to the car, the music change dramatically.
The MMI continue to play the music (source is a SD card) but the sound lost the spatialisation, the treble and the bass, and become "flat". The "11 active speakers - Class-D technology - 16-channel amplifier - 560 watts - Symphoria® Virtual 3D algorithm - by Fraunhofer IIS" from Bang & Olufsen are dead. Killed by AA.

AA take the control of the sound system of the car, and ruins it.
I can understand that a GPS or an other application need to play sounds, but why do not simply play those sounds thru the car system, without erasing it ?

please forgive me my poor english
 
Last edited:

Snirpo

Senior Member
Jan 23, 2007
96
121
Hello all.
I report a problem with AA (not AAwireless).
Phone : Samsung S10e
Car : Audi A1 with Bang & Olufsen sound (https://corporate.bang-olufsen.com/en/partners/automotive/audi/a1)

For me, AAwireless is working good. No problem of connection, and until now, no disconnection.
I m using AAwireless mostly to have AA connected automatically, without cable, on the MMI, to display a GPS into the MMI (Google, Waze or Sygic)
AAwireless is working really good, but as soon AA connect to the car, the music change dramatically.
The MMI continue to play the music (source is a SD card) but the sound lost the spatialisation, the treble and the bass, and become "flat". The "11 active speakers - Class-D technology - 16-channel amplifier - 560 watts - Symphoria® Virtual 3D algorithm - by Fraunhofer IIS" from Bang & Olufsen are dead. Killed by AA.

AA take the control of the sound system of the car, and ruins it.
I can understand that a GPS or an other application need to play sounds, but why do not simply play those sounds thru the car system, without erasing it ?

please forgive me my poor english
Sounds like a problem in the head unit software itself :/
 

janz25

Member
Sep 28, 2006
13
0
Updated my unit to fw 1.4 however, im still experiencing spotify stuttered and gmap is lag at the same time. I have to unplugged and plug back to make it work asp normal.
 

osm0sis

Senior Recognized Developer / Contributor
Mar 14, 2012
14,664
33,044
Halifax
GT-i9250
Nexus 7 (2013)
Updated my unit to fw 1.4 however, im still experiencing spotify stuttered and gmap is lag at the same time. I have to unplugged and plug back to make it work asp normal.
Did you enable "Remove tap restriction" ? If so, try disabling it again. You should also try "Force 2.4Ghz" if that has no effect. Enabling "Passthrough" would rule out some things too if both of those don't work.
 

JimmyDoodle

New member
Jun 12, 2021
1
0
Thanks, Emil.

Just got my AA Wireless unit yesterday. The setup was very easy, the OTA upgrade from 1.2.0 to 1.4.0 was flawless, and the device works perfectly. Love it so far!!

Galaxy S21
Android 11
2016 GMC Sierra Denali 1500
 

ahecht

Senior Member
Oct 23, 2010
518
308
I have been experiencing what I think are constant intermittent problems with audio sinking.

After the latest 1.4.0 firmware update, my Pixel 3a is connecting reliably with the MyLink in my 2018 Chevrolet Volt. The picture is great, but the audio cuts out briefly somewhere between once every second and once every 10 seconds.

Sometimes, if the volume on my phone is high enough, I can hear the audio come out of my phone's speakers for a split second while it is cutting out on my car's speaker, which is why I think it's an audio sinking problem. The audio works fine when I plug AAWireless's cable directly into my phone instead, or when I'm just playing audio over the car's bluetooth.

Enabling or disabling passthrough made no difference, and neither did forcing 2.4Ghz. I don't have "disable tap restriction" turned on.
 
  • Like
Reactions: iTaiwan

sibesaver

Senior Member
Sep 30, 2010
94
14
Moore, OK
I have been experiencing what I think are constant intermittent problems with audio sinking.

After the latest 1.4.0 firmware update, my Pixel 3a is connecting reliably with the MyLink in my 2018 Chevrolet Volt. The picture is great, but the audio cuts out briefly somewhere between once every second and once every 10 seconds.

Sometimes, if the volume on my phone is high enough, I can hear the audio come out of my phone's speakers for a split second while it is cutting out on my car's speaker, which is why I think it's an audio sinking problem. The audio works fine when I plug AAWireless's cable directly into my phone instead, or when I'm just playing audio over the car's bluetooth.

Enabling or disabling passthrough made no difference, and neither did forcing 2.4Ghz. I don't have "disable tap restriction" turned on.
Experiencing the same issue on my Pixel 2XL with my Kenwood head unit. I never had the issue with versions prior to 1.4. Using Waze voice guidance and YT music.
 

Top Liked Posts

  • 1
    Yes mine is unusable also. It's frustrating as it connects so quickly and it's an awesome bit of kit for the few minutes it works. I've tried a reset tonight as advised by support but this doesn't seem to have helped. Will try again tomorrow before I reply to them
    I thought it might be my phone and i tried on my son's xiaomi x3 nfc. It is the same. It just disconnected itself almost instantaneously upon connected.

    Will try to reset and retry again on different mode. So far I had tried default and direct both yielded the same results, keep DC.
  • 14
    Hello. What's new in 1.5?
    A full changelog for each release would really be appreciated :)
    Thanks for all the hard work!
    Yes, I'll write a full changelog next week from 1.0.0 to 1.5.0 and put it on GitHub + add a link in the app.
    9
    @KRGrayson

    The 'new' Default USB Mode is what fixed issues with many GM infotainment systems.

    Instead of presenting what should be the correct USB mode for Android Auto to the Head Unit (direct), or what most phones present as their default mode ( MTP and its variations); Default USB Mode presents a USB Mode that no Head Unit supports. When the Head Unit sees an unsupported USB Mode, USB protocol calls for it to ask the AAWireless device what modes it does support. The Head Unit then selects the correct Android Auto mode and life is good.

    Prior to firmware 1.4.0, some head units (GM was not alone) would not confirm what USB Mode was being presented and begin to communicate in an inappropriate mode for Android Auto.
    7
    @Snirpo is there any source to download older firmware files to downgrade manually for troubleshooting? It would have helped with my last issue after updating to 1.4.

    It would be nice if there were an option in the companion App to choose a specific version.
    Yes, there is: https://drive.google.com/folderview?id=18R-KYbOSt5jBeb3dtqRs-EPrBRaGE9sX

    I did think about adding a downgrade option in the app, but it's a bit tricky. If we do that, we don't only need to test updates from version x to y, but also downgrades all the way back down to 1.0.0. Normally it wouldn't break, but I don't really feel like testing from the newest version to the oldest, to be sure the board doesn't accidentally brick :) It gets a bit too easy to just switch around versions all the time if we provide it via the app. And we don't really want people to use older versions.
    However what I could do is provide an option to switch back to the previous version (which is still on the board actually, cause it has an A/B partition layout).
    6
    Here are the LED codes for OTA firmware 1.5.0. Solid White is now used for Start / Stop standby mode.

    Solid Green, the device is booting, should complete in under 12 seconds. Both the Bluetooth and WiFi are not active until after the boot is completed.

    Blinking Green, the device has activated Bluetooth and is waiting for a WiFi connection from your phone. You will only be able to pair while under blinking green.

    Solid White, Start / Stop standby mode. The device has completed boot and is waiting for the Head Unit Bluetooth to connect with your phone. When your Head Unit Bluetooth disconnects from your phone, the device will return to Start / Stop standby mode for as long as it is powered. The device will not take over the Wi-Fi on your phone while it is solid white. You will be able to connect your phone to any other Wi-Fi network. Use the Start / Stop Option to enable this mode.

    Blinking Blue, the device has fully connected with your phone and is attempting to connect with your head unit via USB.

    Solid Blue, the device is full connected with your phone and the head unit. The first time you connect you may need to set some Android Auto permissions and some head units may also produce prompts for you to answer.

    Solid Yellow, the device is loading an OTA update into memory.

    Red, an error has occurred, the device will attempt recovery after a timeout.

    None / Black The LED will not be active when you first apply power for a very brief time. And the LED will not be active at all when the device is ready to be flashed from your computer. It will remain inactive until the flash program completes loading the firmware and reboots the device.

    RIP Blinking White
    The change from Blinking White to Solid White was based on feedback from this forum. Users saw the Blinking White drift to other colors over time. It turns out that the drivers for the RED, GREEN and BLUE LEDs on the device are not coordinated for the blinking feature. Blinking the primary colors is fine, but blinking Yellow, Cyan, Magenta and White will cause drift to other colors.

    LeRoy
  • 28
    This thread is dedicated for AAWireless users.

    AAWireless is a device which allows you to transform your existing wired Android Auto compatible unit into a Wireless Android Auto unit.

    General chat, experience sharing and community support should be expected as well as support from the developers of the product: @Snirpo and myself.
    15
    We fixed the "VW Headunit crashing on skipping tracks" issue now completely. Confirmed it's a bug on the HU side, latency makes it worse. We will probably push a new firmware by the end of this week.
    I will also submit a bug report to Google, cause they can fix/workaround this issue as well for cabled users.
    14
    Hello. What's new in 1.5?
    A full changelog for each release would really be appreciated :)
    Thanks for all the hard work!
    Yes, I'll write a full changelog next week from 1.0.0 to 1.5.0 and put it on GitHub + add a link in the app.
    9
    @KRGrayson

    The 'new' Default USB Mode is what fixed issues with many GM infotainment systems.

    Instead of presenting what should be the correct USB mode for Android Auto to the Head Unit (direct), or what most phones present as their default mode ( MTP and its variations); Default USB Mode presents a USB Mode that no Head Unit supports. When the Head Unit sees an unsupported USB Mode, USB protocol calls for it to ask the AAWireless device what modes it does support. The Head Unit then selects the correct Android Auto mode and life is good.

    Prior to firmware 1.4.0, some head units (GM was not alone) would not confirm what USB Mode was being presented and begin to communicate in an inappropriate mode for Android Auto.