AAWireless - General discussion and support

Search This thread

TheUntouchable

Senior Member
Jul 14, 2010
1,198
286
Germany
Huawei P30 Pro
Any thoughts on GA for 2.1.0? (another Hyundai / Kia owner that has just upgraded to get widescreen Android Auto on the headunit)
I can tell that switching to pass through is currently a good workaround :) But I have the problem that the connection sometimes takes longer then my driving time.. sometimes it connects instantly.. The WiFi timeout is already set to 5 seconds :( Have the feeling this started after upgrading to one of the 2.X firmwares.
 
Last edited:

shadwell_lad

Member
Oct 20, 2010
45
8
London
I can tell that switching to pass through is currently a good workaround :) But I have the problem that the connection sometimes takes longer then my driving time.. sometimes it connects instantly.. The WiFi timeout is already set to 5 seconds :( Have the feeling this started after upgrading to one of the 2.X firmwares.
Thx. I'll go on pass through. Long drive planned today so let's see how that goes
 
  • Like
Reactions: TheUntouchable

WestHej

Member
Apr 17, 2012
24
7
Thx. I'll go on pass through. Long drive planned today so let's see how that goes
I'm on a Hyundai. So far passthough is a workaround since I upgraded the infotainment for AA widescreen but it does take a variable amount of time to connect. I'm also keen to get the DPI higher (I set it at 180 on an ioniq 5). Makes the AA interface look so much smarter rather than a kids toy! Hope we can get an update soon to fix it.
 

amirage

Senior Member
Hi all, I just get the phone to download 2.0.2 firmware. My device firmware is 1.8.0 and app won't download the update whatsoever. I click download and then nothing...again the start download comes up...I hit it again..still nada...any suggestions? I deleted the data and cache in the app and even forced stopped it..still no use...
 

bertsmelik

Senior Member
Jan 12, 2014
124
45
Ridderkerk
Reboot phone to connect
I would like to share my experience. Just found this morning that AA does not connect to my phone. Restarted AAW a few times: no joy.
Only after I rebooted my phone, it connected without a problem.
Inspecting the phone revealed that Maps had been updated last night (to version 11.36.2). I recall that I had to reboot the phone a few weeks earlier in order to connect.
Would the update of Maps cause this?
Anyone else saw this on his/her phone?

My AAwireless: 2.0.2
My phone: Poco X3 NFC (rom: Pixel Experience Android 12.1)
My car: MG EHS PHEV 2021
 
Last edited:

sick6

New member
Dec 3, 2012
4
0
Maybe I'm not doing it right, but I don't see 1.8 as an available option when I go to System Update.
On the dev app, it says the same thing for current and latest: 2.1.0-202206240850-develop-516470d-develop-6803c38f.
In the regular app, it just says no update available. What is the correct way to rollback to 1.8? Thanks.
 

zepatko

Member
Nov 9, 2021
13
1
Yup, this is fixed on 2.1.0, which is in beta. You can use passthrough mode in the meantime.
What is actually the difference with or without the passthrough mode ?
I've been using it since the beginning because I had some diconnections problems in normal mode, and never tried again without it.
Is it better without it ? and, if yes, why ?
 

TheUntouchable

Senior Member
Jul 14, 2010
1,198
286
Germany
Huawei P30 Pro
What is actually the difference with or without the passthrough mode ?
I've been using it since the beginning because I had some diconnections problems in normal mode, and never tried again without it.
Is it better without it ? and, if yes, why ?
When using passthrough mode most settings in the app like DPI, the sink stuff and co will not work as everything is directly routed to the phone.
 

x10isrooted

Senior Member
Jun 23, 2010
259
33
Does anyone know if on 2.0.2 the SSL fix was applied? I'm still on the dev aawireless app + firmware update "channel" where everything works fine but I do not need daily updates and if it's on the stable I would revert back to stable "channel"
 

DroidShift79

Senior Member
Sep 11, 2012
1,517
612
Frankfurt am Main
OnePlus 9 Pro
What is actually the difference with or without the passthrough mode ?
I've been using it since the beginning because I had some diconnections problems in normal mode, and never tried again without it.
Is it better without it ? and, if yes, why?
Passthrough mode will send all data unmodified to the dongle. This should work all the time, everywhere. Using it in combination with dongle mode should be fine for everyone. Downside is, you can't use any advanced features like DPI settings with it

Without passthrough mode, you could use the extra features in the app. And for me connection without passthrough, is much faster.
 

zepatko

Member
Nov 9, 2021
13
1
When using passthrough mode most settings in the app like DPI, the sink stuff and co will not work as everything is directly routed to the phone.

Passthrough mode will send all data unmodified to the dongle. This should work all the time, everywhere. Using it in combination with dongle mode should be fine for everyone. Downside is, you can't use any advanced features like DPI settings with it

Without passthrough mode, you could use the extra features in the app. And for me connection without passthrough, is much faster.

Ok, thanks for your answers. I'll try it when 2.1 firmware will be available (I'm KIA user, and apparently version 2.02 doesn't work properly with last unit update)
 

psmedley

Senior Member
May 5, 2011
124
29
Adelaide
Does anyone know if on 2.0.2 the SSL fix was applied? I'm still on the dev aawireless app + firmware update "channel" where everything works fine but I do not need daily updates and if it's on the stable I would revert back to stable "channel"
AFAIK the SSL fix is only in 2.1.0, but I also understand that using Passthrough on 2.0.2 works as well.
 

Snirpo

Senior Member
Jan 23, 2007
431
520
Maybe I'm not doing it right, but I don't see 1.8 as an available option when I go to System Update.
On the dev app, it says the same thing for current and latest: 2.1.0-202206240850-develop-516470d-develop-6803c38f.
In the regular app, it just says no update available. What is the correct way to rollback to 1.8? Thanks.
Sorry, accidentally enabled develop instead of 1.8, 1.8 should be enabled now.
 
  • Like
Reactions: sick6

Top Liked Posts

  • 9
    Very close to release of 2.1.0 now. We fixed the UConnect issue, except for some cases where you still have to re-plug the device, but this is also the case on the MA1.
    5
    @Snirpo
    I just want to say thank you to you and your team for your hard work and the device.
    I have it now since end of October 2021. I use it nearly every day.
    The successful connection rate is at around 98-99% in my case. For the other 1-2% there is always support from your side. Thanks for this.

    Don't listen to inpatient people. Everybody wants to have everything right away. Waiting is something people don't know any more today in the globalised world. Don't listen to these guys.
    3
    ... They will not work perfectly for all, there are just too many variables clueless people.
    There. I've fixed it for you! :)

    Mine works perfectly 99% of the time, & when it doesn't seem to work, rebooting the HU or phone fixes it. That tells me where the problem is.

    Too many people have unrealistic expectations of wireless communications (that includes Bluetooth). As a Amateur Radio licensee for fifty years, I understand the frustration. However, it's the nature of radio communications.
  • 16
    I used to get the same thing. I believe it is an issue with AA/Google rather than AAW. In any event, I have had to give up on AAW as I can't connect to it/won't update, just sits there with a constant light-blue light. It is a (very expensive) paper weight on my desk now. It is just "too Beta" for my requirements.

    I have now got a Carlink 2022 Android box which works flawlessly for me.
    MG ZS EV 2022
    Galaxy S21 Ultra (not rooted)
    I know I should ignore these posts, but these are the comments why I'm honestly considering completely dropping out any forum / reddit / social media. What's the point? We have support, we have warranty, we have a refund policy. It might be "beta" for you, but we shipped over 100k devices and believe me or not, for most, it just works. It's the same thing for all of these dongles. They will not work perfectly for all, there are just too many variables.
    9
    I know I should ignore these posts, but these are the comments why I'm honestly considering completely dropping out any forum / reddit / social media. What's the point? We have support, we have warranty, we have a refund policy. It might be "beta" for you, but we shipped over 100k devices and believe me or not, for most, it just works. It's the same thing for all of these dongles. They will not work perfectly for all, there are just too many variables.
    I remember a post from a guy with the classic “I've been in the industry for years” claim. He said that because he had a weekly internal briefing at his workplace, you should be doing the same for us here. If you give an inch, they want a mile.

    Then you have all the narcissistic Karens with zero patience that say whatever they think will get your attention so they can jump the queue. Even when you (quite rightly) post that firmware will now be staggered with no release announcement, you have an immediate request from someone with “faulty” units asking you to announce when the release will start!?!

    It must be incredibly frustrating and every rational user will understand. Even if you decide against stepping back permanently, please take a lengthy break.
    9
    At this moment we have shut down all OTA updates unfortunately. The load on our backend is too high. Too long without maintenance because of other priorities. We have to optimize some stuff to make it work again.
    It's working again :)
    8
    @[email protected]:
    Please stop spamming this thread !
    9
    Very close to release of 2.1.0 now. We fixed the UConnect issue, except for some cases where you still have to re-plug the device, but this is also the case on the MA1.
  • 41
    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!
    16
    I used to get the same thing. I believe it is an issue with AA/Google rather than AAW. In any event, I have had to give up on AAW as I can't connect to it/won't update, just sits there with a constant light-blue light. It is a (very expensive) paper weight on my desk now. It is just "too Beta" for my requirements.

    I have now got a Carlink 2022 Android box which works flawlessly for me.
    MG ZS EV 2022
    Galaxy S21 Ultra (not rooted)
    I know I should ignore these posts, but these are the comments why I'm honestly considering completely dropping out any forum / reddit / social media. What's the point? We have support, we have warranty, we have a refund policy. It might be "beta" for you, but we shipped over 100k devices and believe me or not, for most, it just works. It's the same thing for all of these dongles. They will not work perfectly for all, there are just too many variables.
    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.