• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

AAWireless - General discussion and support

Search This thread

DevAuto

Member
Mar 9, 2013
43
22
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
43
22
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
43
22
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
111
152
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
699
85
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
699
85
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
4
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
111
152
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,745
33,290
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
310
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.
 

sibesaver

Senior Member
Sep 30, 2010
97
26
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

  • There are no posts matching your filters.
  • 5
    @Snirpo
    when are feature improvements and new features going to be tackled? It was several months back that you said that they would be tackled after the new version of the start/stop feature was released but we are still waiting for this. Surely Gen2 has been resolved now.
    Gen2 has not been resolved yet, we are very close but not there yet. That's why we are producing 16k Gen1 units now (with a lot of effort to actually get components), to fill the gap and finally get off Indiegogo.
    Gen2 is a huge risk for us, we don't want to mess it up. We are planning to produce Gen2 in large quantities (20k+) batches. If we mess up a 20k batch of devices we can bassicly pack up and go.
    We already felt the pain of messing up a batch (batch 2) and this was only one of 6k units.
    I'm sorry it might seem like we are not doing much, but in the background a lot is going on, not only technically.
    Features will come, and they will come this year. But I cannot give any short term deadlines anymore.

    On the app side, if you want to test bleeding edge builds you can join here: https://appdistribution.firebase.dev/i/5196d378c8e122d7

    I might also set up the same thing for the board-side. Only there it's a bit trickier, because of the chance of "bricking" the device.
    2
    Posted via Indiegogo and thought I would post here too. Glad to hear you’ve managed to move forward with production again. I’m not asking for an ETA – more of a timeline, do you have an idea when there will be updates to the firmware/app for those who have received their devices? I understand you want to get devices shipped but if you are amongst the group that has bugs/issues with the current firmware, this device is pretty much being used as a paperweight. Once again, I'm not trash talking this device because I love it while it works but some transparency on the development side would be nice since we only hear about the manufacturing side on Indiegogo
    1
    2018 Mazda CX-5, AA capable headunit, firmware 70.00.335 (NA N region)
    Moto Z4 with Android 10.
    AAwireless updated to 1.5.0.

    Even with passthrough mode enabled, I've *never* been able to get AAwireless to work. What settings are you Mazda folks using that it's working for you? What headunit firmware revisions and regions?

    Under non-passthrough mode, it always does the "Enable Android Auto / not responding" dance cycle (even the very first time, it's never worked even once).

    Under passthrough mode, the headunit doesn't seem to think anything is connected at all; no popups or other messages.

    Tried all USB connection modes (saved twice and unplugged/replugged to make sure the setting change took effect; it doesn't always seem to save the change across reboots in my observation). Android's own USB settings are adb ("USB debugging") enabled; default to "No data transfer" (though I suspect these are irrelevant).


    (Sigh, can't update the headunit for the moment. It seems that Mazda nuked the one place I saw that had the 74.xx.xxx update, so for the moment I can't update the thing without paying $$$ to a dealership for the Great Privilege of them plugging in a USB stick and pressing a half dozen buttons. [PMs accepted on this point...])

    **EDIT!** After so much desperation, factory reset the headunit, cleared the AA app's data, reverted to stock version, re-updated to Play Store version, set AA up from scratch again... it finally works. I'll just crawl away and scream into a pillow and hope it stays working :LOL:
    1
    Did you get anywhere with the DPI and the split screen on your Pioneer HU?
    Yes, I've set it to 100 and I have split screen with both wireless and plugged in.
  • 29
    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.
    14
    I've already waited patiently for delivery 3 months more than expected - I ordered In April and was coming in June but now that's looking like October. Now I read on the indiegogo forum that people in the UK are being charged an additional €27 by the Royal mail as the UK is now not in the EU.

    Hi Emil!
    Just received my AAWireless, and will plug in and test tonight. Love the packaging, looks great! However… Since it was shipped from Hong Kong I was forced to pay a rather substantial import fee and duties on this bad boy. I was under the impression that they would be shipped from within the EU? Is it stands now I’m EUR 27,00 poorer :(
    2 2
    https://www.indiegogo.com/individuals/24534862
    Emil Borconi-Szedressy 2 days ago
    PROJECT OWNER
    Looks like you are in the UK which is outside EU and also there is no way to pre-pay taxes with shipping company any more either....


    This is a crazy. An additional $10 was already taken for delivery and it was meant to ship from the EU. I suspect the units have been shipped by Royal Mail / Dutch post. The Royal Mail rips off people in the UK because they add another £11 in admin fees on top of the 20% VAT even though goods up to £135 should be exempt.
    See https://www.gov.uk/government/publi...s-goods-sold-to-customers-from-1-january-2021

    So not only has VAT been charged coming into the EU from China, it has also been charged coming into the UK ON TOP of the VAT already paid in the EU.

    This is just rubbish. What the guys need to do is either ship it from Hong Kong which can cost £0.20 (there are hundreds of chinese ebay and aliexpress sellers doing this already
    See http://www.vatfraud.org/blog/stop-s...ons-universal-postal-union-upu-terminal-dues/
    The $10 postage already taken should then be refunded.

    The other way round it is send the item from Hong Kong and to mark the item as a gift and providing it is below £39 there is NO VAT to pay and NO Royal mail admin fee. Actually as the original product was $57 - roughly £41.25 This wouldn't be a crime seeing as we have had to wait soo long. This could also mean the $10 delivery could be refunded

    The other way is to ship it via fedex and state the ex-vat cost coming from china and then add 20% vat that the developer should be paying to the UK HMRC.

    Sadly if that doesn't take place, EVERYONE IN THE UK will feel ripped off because of the poor delivery and poor choices made by the developers.

    Cheers
    Disgruntled in the UK

    First of all, your item wasn't shipped yet since in the June batch, so you could have not payed anything for shipping. Secondly, UK is outside the EU, there was a vote about this in 2016, so it doesn't matter if the package comes from EU or from HK or from US, it is treated the same, it's an import. If we import it from HK to EU, we will pay import VAT on the product, then when we send it to UK, we claim back that VAT and we should pay VAT in UK, since there is no more free trading between EU and UK.

    Up till recently there was a nice option, to pay VAT and Import duty up-front, when you ship to the UK, but this has been changed and now they requires business outside UK to register with HMRC and do HMRC feeling even if they are residing outside UK, a lot of red tape. Since crowdfunding is not a sale, we can still ship the units to UK, but not sure if we will be able to after the IndieGoGo campaign.

    We are also a EU registered company so we cannot (and will not take advantage) of any loop-holes in systems to sell at ridiculously / unrealistically cheap prices.

    About the user who paid 27 euros, it turned out that user is living in DK, but provided the address as UK so his package traveled the wrong way, hence the extra duties and surcharges.

    Not aware of other users from UK having to pay anything additional when they received the package.