AAWireless - General discussion and support

Search This thread

1enry1

Member
Oct 21, 2015
6
0
hi.... help me on the new GOLF 8 ?

when you tell to the google assistent to call a number in the

address book ... your call the numer that you say ? in my .... NONE !

:-(
 

HofaTheRipper

Senior Member
Apr 26, 2014
250
218
38
St. Veit an der Glan
Well I've upgraded as of yesterday so we'll see!
I checked the change log here and didn't see reference to this issue:

Do you have a source for this info?
I am a beta tester and while testing 2.1.0 we found this issue. As the devs told me this bug was there since 2.0.0, but got worse on 2.1.0.... (no sound at all anymore) so they pushed the bugfix version 2.0.1.
 

HofaTheRipper

Senior Member
Apr 26, 2014
250
218
38
St. Veit an der Glan
this was posted on slack, and after that 2.0.1 was pushed (which was the same as the 2.1.0 dev version at this moment):
 

Attachments

  • Screenshot_2022-05-29-15-22-17-87_abb9c8060a0a12c5ac89e934e52a2f4f.jpg
    Screenshot_2022-05-29-15-22-17-87_abb9c8060a0a12c5ac89e934e52a2f4f.jpg
    172 KB · Views: 44

smirle

Member
Aug 23, 2009
8
6
this was posted on slack, and after that 2.0.1 was pushed (which was the same as the 2.1.0 dev version at this moment):
This is great news - thanks for sharing the detail. My problem with audio dropping did in fact start with v2.0, however I was only on 1.12 for about a week prior (just received my AAWireless unit in late April).

I'm on 2.0.1 now so hopefully I won't see the problem any more!
 
Last edited:

-Loom-

Senior Member
Nov 5, 2010
355
73
Düsseldorf
Using first-gen AAWireless with a Golf 7 MIB 2.5 (Technisat Headunit) and OnePlus 8T Android 11.

After upgrading to 2.0 I had frequent disconnections and some kind of weird bugs like getting a phonecall routed to the phone instead of the car. Sometimes when switching from radio to Spotify, there would be no audio when you hit play etc ..

I'm glad to repot that upgrading to 2.01 fixed all my issues so far. I'm using MPT mode, Wifi 5 Ghz on a channel above 140.

One thing I observed:

I'm using TomTom Amigo on my phone for all kind of warning alerts. It should start automatically when the phone connects to the car and shutdown when connection stops.

I wasn't able to use Amigo because just after connecting it would shut down the app. After digging for a while, I saw that the bluetooth connection to the car couldn't be established once Aawireless is running.

What fixed that for me: On the phone open the bluetooth connection properties from the connected car and disable "Media Audio".
 
Last edited:
  • Like
Reactions: festor

Cipcino81

Member
Aug 26, 2020
13
2
Hello,
after several days of testing, version 1.8 works flawlessly, so the culprit was indeed the new firmware from version 2.0 onward, for some reason. If you need the information my head unit is a Pioneer AVH-Z9200DAB. I will stay with 1.8 if the issue with my head unit will not be resolved.
Thank you.
 

Snirpo

Senior Member
Jan 23, 2007
376
441
Hello,
after several days of testing, version 1.8 works flawlessly, so the culprit was indeed the new firmware from version 2.0 onward, for some reason. If you need the information my head unit is a Pioneer AVH-Z9200DAB. I will stay with 1.8 if the issue with my head unit will not be resolved.
Thank you.
First need to know what the issue is. Are you ok with updating to 2.0.1 again and shooting in a bug report?
 
  • Like
Reactions: hand-filer

Cipcino81

Member
Aug 26, 2020
13
2
First need to know what the issue is. Are you ok with updating to 2.0.1 again and shooting in a bug report?
I had written here and to support about the issue, but anyway it was a problem where randomly video in head unit goes off and displays a black screen with a text indicating "for using android auto please stop the car and check your android phone" phone was normal , and audio infications from navigator still continue to work , and last song finished playing. So it was not a complete disconnection , but a video disconnection.
 

Snirpo

Senior Member
Jan 23, 2007
376
441
I had written here and to support about the issue, but anyway it was a problem where randomly video in head unit goes off and displays a black screen with a text indicating "for using android auto please stop the car and check your android phone" phone was normal , and audio infications from navigator still continue to work , and last song finished playing. So it was not a complete disconnection , but a video disconnection.
I mean I technically need to know what the issue is, bug report might be helpful ;) did this happen in passthrough mode as well?
 

welshblob

Senior Member
Dec 22, 2013
157
32
Fareham (not in Wales)
Found this thread whilst searching for the MIUI bug but they haven't found a fix. They seem to imply its more related to bluetooth dropping when the mobile data signal goes rather than wifi. No fix and I'm slightly confused by that site in that it appears to be a community effort to build pure Miui roms but are using the xiaomi.eu domain. Dev doesn't seem interested and bat's it off as an AA issue.

 
  • Like
Reactions: festor
May 14, 2022
35
9
Hello!
Well i did spoke too soon saying that everything was working perfectly...

I have sometime a problem where i don´t have BT on the phone and, when starting android auto, i don´t also get the "PowerAMP" icon to have music!

Sometimes happen, sometimes don´t happen... when don´t happen everything works as it should... i have music and i have Waze or Maps.

What could it be?

Im using all the latest versions of the AAWireless APP and the Firmware 2.0.1.

I don´t get any error... simply the "PowerAMP" apps simply vanish from the AA menu on the infotaiment.
Disconnecting the AAWireless unit from the cable and connecting it again seems to fix the issue.

Can you please add a soft reboot button on the APP, please?

Phone: Samsung Galaxy A52 5G latest version 4.1 and Android 12
Car: Citroen C5 Aircross 2019 - Continental NAC Infotaiment

I have allready putted the AAWireless on a hidden place, so its not that easy to keep putting and removing the cable...

Thanks in advance...

LPC
 

festor

Senior Member
Jun 4, 2013
112
50
Found this thread whilst searching for the MIUI bug but they haven't found a fix. They seem to imply its more related to bluetooth dropping when the mobile data signal goes rather than wifi. No fix and I'm slightly confused by that site in that it appears to be a community effort to build pure Miui roms but are using the xiaomi.eu domain. Dev doesn't seem interested and bat's it off as an AA issue.

I wanted to confirm it was MIUI cutting wifi/BT, but I tried to register there (a few times) without any luck. Keeps getting flagged as spam behaviour?

Either way, the dev who posted in the thread seems adamant it’s down to AAWireless (without evidence) and says to contact Google for help. This is after complaining about the initial edited log attached, demanding a full unaltered log, then complaining the full log is too big to go through.

If this is typical behaviour, it doesn’t look like there will be a fix any time soon.
 
  • Like
Reactions: welshblob

welshblob

Senior Member
Dec 22, 2013
157
32
Fareham (not in Wales)
I wanted to confirm it was MIUI cutting wifi/BT, but I tried to register there (a few times) without any luck. Keeps getting flagged as spam behaviour?

Either way, the dev who posted in the thread seems adamant it’s down to AAWireless (without evidence) and says to contact Google for help. This is after complaining about the initial edited log attached, demanding a full unaltered log, then complaining the full log is too big to go through.

If this is typical behaviour, it doesn’t look like there will be a fix any time soon.
Yeah it's unfortunate that some devs appear to have that attitude. I have had a response from my feedback submission which was to state what router I'm using and to enable WiFi logging, record the time it happens and then submit the logs. Proving a bit challenging to get the timing right on that one. So I've replied with the link above for the moment. I'm getting closer to replacing the ROM on my phone due to this.
 
  • Like
Reactions: festor

festor

Senior Member
Jun 4, 2013
112
50
Yeah it's unfortunate that some devs appear to have that attitude. I have had a response from my feedback submission which was to state what router I'm using and to enable WiFi logging, record the time it happens and then submit the logs. Proving a bit challenging to get the timing right on that one. So I've replied with the link above for the moment. I'm getting closer to replacing the ROM on my phone due to this.
I’ve seen a few people mention that PixelExperience fixes the issue, but I decided against changing. I would probably end up with a few other issues that are just as annoying, to me anyway.

Swapping to a Vodafone based carrier recently which has better coverage in my area and 2.0.1 firmware (5GHz, Ch 153) has dramatically cut my disconnections over the past week. A 40 min drive yesterday (typical route) had no dropouts where a few weeks ago I could easily have 3 or 4.

With the Xiaomi Android 13 beta released for more devices, I hope we get some feedback soon if the issue carries over.
 
  • Like
Reactions: welshblob

zoemas

Member
Jun 26, 2013
12
1
I use AA wireless for about a month now. So far I don't have any major issue. It connect's within 8 sec after it receives power. No disconnects wile driving. But....
- When playing spotify and using maps to navigate, the music stotters real bad when I receive a spoken navigation instruction and keeps stuttering a few secconds afterwards. This was on 5Ghz, strangely when I put it on 2,4Ghz this doensn't happen , only the map voice stotters sometimes , but not as bad as the music.
-My major anoiance is that Google Assisant doen't understand a word I'm saying , I say one thing and she understands something completly different. This doesn't happen when using AA wired.
 

Top Liked Posts

  • 3
    I've been happily using AAwirelsss in my Kia Stinger, but I do have a few notes on my specific installation that others might find helpful.

    Instead of using the built in start / stop detection, I made a Y cable that hooks up the USB data lines and ground to my head unit, but power is pulled from a cigarette lighter USB adapter. I don't know if this is safe on all cars, but it worked on mine.

    I have quite a few devices in my car I need to share internet with, and I do not want to buy an extra hotspot., so I had to make a few tweaks on my phone to make my phone's hot spot play nice with AAwireless. In the past I simply had a macrodroid script set up so that when my bluetooth connects to the car, it started my phone's hot spot.

    Unfortunately, the limited wifi connection to AAwireless seems to confuse my phone's hotspot, and it won't share any internet once connected to AAwireless.

    I found the trick was to to have Macrodroid enable my hotspot, then disable wifi, forcing the hot spot to share my cellular data connection, then reenable wifi, and script connecting to AAwireless manually.

    The AAwireless password is the SHA-1 of the device name in upper case.

    Note: AAwireless does currently support connecting through a hot spot, but only a hot spot that isn't also your AAwireless phone. Support for connecting via your phone's built in hot spot is eventually coming, but for now the method I use above has worked well for me.
    Sounds very complex :) I'll build this feature into the next version of the app, possibly this week. Care to test?
    2
    Always ready to test. I'm already part of the google play beta group, will the test version show up there?
    For the latest, please download: https://appdistribution.firebase.dev/i/5196d378c8e122d7
    1
    No way
    It happens right after the firmware update to 2.0.2 from aawireless
    Please enable passthrough mode to verify if it also happens in passthrough mode.
    1
    Sounds very complex :) I'll build this feature into the next version of the app, possibly this week. Care to test?

    Always ready to test. I'm already part of the google play beta group, will the test version show up there?
  • 7
    I got bored today, so I thought I make a mock up how the AAWireless app could look like :D When swiping t he car picture could change if you want to connect to annother device/car :D

    View attachment 5645393 View attachment 5645397
    Haha nice! I'll pass it on to our UI/UX designer :) We have some UX changes in the pipeline, but it doesn't have the highest prio right now as you can imagine.
    We made some changes in firmware 2.1.0 which means we don't need these dreaded USB modes anymore. The plan is to ship devices in passthrough + dongle mode, to make it work natively, like the MA1, by default.
    Then we are going to hide away the settings in a sort of advanced settings menu, because all these settings are nice, but people don't read/understand what they do, stuff stops working and then our support has to handle it. Hardly anyone uses these settings, for example, dpi change, the most used feature, is only used on 1 percent of all devices.
    Bassicly we are KISS'ing it, but still keep advanced settings for well... You guys :)
    5
    @everyone

    For feature requests or issues, please use: https://github.com/cpebit/aawireless-issues/issues/new/choose

    I getting really hard to follow this thread. Possibly I already forgot some requests of some people. Need a bit of structure. We will try to fix issues one by one from GitHub.
    4
    Regarding the broken day / nightmode cycle:

    I also have this problem, and I read a few days ago that it was due to a combination of updated Google Maps and Android Auto.

    The combination which should work:

    Android Auto: 7.5.621344
    Google Maps: 11.31.1

    You finde all these old versions on apkmirror.com, or similar sites.

    Didn't have the time to check this out myself.

    I had this same problem. Found out it woud be caused to 11.31.1 and upwards. Found the solution on Google Maps Help.

    I installed Maps 11.35.0 beta (from apk mirror) and all seems to work well again. My AA is level 7.7.622134 (from play store).​

    Tried a lot of different variations, but my conclusion is that Maps from 11.33.1 is the culprit.
    3
    @Snirpo

    Why don't you use a Y-cable? Data plugs into the USB and electric power from the cigarette lighter plug.
    By this you can check the voltage on the cigarette lighter plug. Is it 12.x Volts, you know the engine is off. Then you wait for a timeout of 2 minutes after the phone disconnected and turn off AAWireless. As soon as the voltage is 14.x Volts, you know that the engine is running and turn AAWireless on. You could sell this as an addon cable for people who need this.

    Another solution is to make it based on vibrations/accelerations. The early bluetooth handsfree sets used a similar way to check if the door was opened. I don't know if there is a sensor on the board.

    Another idea is to carefully check how stable the 5V from USB is during engine start as the ICs have to control the output voltage based on the input voltage (input voltage should drop during engine cranking). I guess you will see a voltage control behavior. I think it will drop for a short time and then go over 5V until the controller sets the 5V stable. And here you can start AAWireless. As soon as the phone disconnects keep a long enough timeout of 5 minutes or so to make sure that noone tries to reconnect. Then you can turn off AAWireless. You could sell this as an addon cable for people who need this.

    These are just some ideas...
    While I do like these ideas technically. From an UX perspective I don't know.

    Right now already we get complaints AAWireless is difficult to setup (while in reality it really isn't), compared to for example the MA1, this would complicate it more. I have seen a lot of support tickets, and for non-tech these things are just very hard to understand. "Why do I need an extra cable?!"

    I think for the car's which have an always on USB port (Dodge RAM/Jeep) we seem to have a proper device controlled solution now (in beta).
    For other cars which keep their USB port powered for just a while after turn off its trickier, but even then the phone controlled way works for most. What's left is the edge cases, where we have to think about how to handle those.
    3
    I can, but it feels more like a bandaid solution. What kind of problems do you have?
    Yes rebooting is a band-aid solution for sure. But I think it would be a good thing to add in any case. Most devices I own have an option somewhere in the menu for a reboot. Hopefully it's not too difficult to implement.

    As for the issue, here's the description:

    Setup
    Car - Kia Stinger 2019 GT AWD
    AAWireless - Firmware 2.0, factory reset a few weeks ago. Enabled dongle mode and passthrough mode. Everything else is default
    Phone - Pixel 5

    Issue
    Once in a rare while (like every 20-30 trips) the audio from AAWireless connection just stops working. Happened with multiple different apps (Spotify, Pocketcasts, etc.). The app keeps playing the content (I can see the play time advancing) but no sound. There is never an interruption with the AA connection - it's rock solid, stays on my car display and is navigable. it's just the audio that stops working.

    Troubleshooting steps
    Tried factory reset in non-dongle mode (fail)
    Tried factory reset with dongle mode (fail)
    Tried dongle mode + pass through (fail)
    Upgraded to AAWireless firmware 2.0.1 (did that this morning, too early to tell)

    When this happens (again it's rare) the only way that I can resolve this is to leave the car for a few minutes and let the AAWireless unit power down with the car, or power cycle the AAWireless unit by unplugging and plugging back in. If I turn off the car and turn it back on immediately, the problem remains as the AAWIreless device stays powered on. If I switch to radio on the car the sound works fine but when I go back to AAWIreless the sound is still gone.

    In either situation, rebooting the AAWireless seems to fix the issue.

    Hope this helps. Like I said this is fairly rare occurence that can occur at the beginning of a trip or after 30 mins of driving. That's why I'd be happy with a device reboot option in the app as I know the permutations of cars + phones + AAWireless settings makes this hard to diagnose.
  • 40
    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.
    16
    I just want to leave a big THANK YOU for the developers! You invented a great product and do a great job here.

    Anyone who has ordered the product knows that it is a crowdfunding project, which may also have teething problems. I find it cheeky to get upset about problems, even though they are dealt with promptly here. What more should the distributors do than react to the problems here and offer solutions?

    I also have problems with the device, but I was helped quickly. Even if it takes a few days.

    Dear team: Keep up the good work!
    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.