AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
I went for a few trips in the GTI this morning and everything was great again in terms of AAW starting up on the screen, responsiveness and dropout free. I did think stop/start was fixed at the 2.0 FW but will see again maybe in 2.1.
The one issue that has been there for a long time is the Assistant being mute, and it happened again. First drive all good. Go into a store for a few minutes and second drive the Assistant can't be heard.
That's my only issue at the moment.
The one issue that has been there for a long time is the Assistant being mute, and it happened again. First drive all good. Go into a store for a few minutes and second drive the Assistant can't be heard.
That's my only issue at the moment.
One again to everyone with passthrough issues or in general having connection issues... Do the following and it will fix majority of issues.
Step zero: update your AAW to the latest firmware - if you've got issues connecting, there may be bug fixes that help.
Step one: DISABLE passthrough mode in your AAW app settings. Now
reset your AAW device using the small pinhole on the side of the device (hold for approx 5 seconds and you'll see the LED change/stop flashing etc so you'll know when it's reset)
Step two: WIPE YOUR ANDROID AUTO DATA on your device (in settings, search for android auto)
Step three: Clear your headunits Bluetooth connection to your phone.
Step four: Plug in your device to headunit and setup android auto.
Step five: Disconnect your phone and alter the android auto device settings to enable wireless AA (and other desired changes)
Step six: Now plug in your AAW device and set it up and connect (if it doesn't connect, simply open your Bluetooth connections and do it manually)
Step seven: Congrats, you're running AAW without passthrough mode and can now alter the settings within the AAW app.
Step zero: update your AAW to the latest firmware - if you've got issues connecting, there may be bug fixes that help.
Step one: DISABLE passthrough mode in your AAW app settings. Now
reset your AAW device using the small pinhole on the side of the device (hold for approx 5 seconds and you'll see the LED change/stop flashing etc so you'll know when it's reset)
Step two: WIPE YOUR ANDROID AUTO DATA on your device (in settings, search for android auto)
Step three: Clear your headunits Bluetooth connection to your phone.
Step four: Plug in your device to headunit and setup android auto.
Step five: Disconnect your phone and alter the android auto device settings to enable wireless AA (and other desired changes)
Step six: Now plug in your AAW device and set it up and connect (if it doesn't connect, simply open your Bluetooth connections and do it manually)
Step seven: Congrats, you're running AAW without passthrough mode and can now alter the settings within the AAW app.
Yesterday noticed very weird behavior.
Connection worked ~5-10 minutes and then dropped. And then aawireless started "bootlooping". Headunit showed to choose Android Auto or Mirrorlink (it did not restore previously chosen android auto like usual). Stayd ~10-20 sec like so and then lost again the connection. And it did not manage to show android auto even when I clicked to "android auto" on headunit. And this loop remained to the end of my drive. After few hours started another drive. At first it worked some time and after first drop, it started same "bootloop" again.
I don't know if it may be connected with enabling passthrough mode day before (because regular dongle mode still very unstable and trying different settings still...)
Connection worked ~5-10 minutes and then dropped. And then aawireless started "bootlooping". Headunit showed to choose Android Auto or Mirrorlink (it did not restore previously chosen android auto like usual). Stayd ~10-20 sec like so and then lost again the connection. And it did not manage to show android auto even when I clicked to "android auto" on headunit. And this loop remained to the end of my drive. After few hours started another drive. At first it worked some time and after first drop, it started same "bootloop" again.
I don't know if it may be connected with enabling passthrough mode day before (because regular dongle mode still very unstable and trying different settings still...)
Strange indeed, can you send in a bug report via help and support --> bug report? Please inform me if you did, then I can see what's happening
This failure sounds like the boot looping I am seeing. I uploaded a log to support ticket https://cpeb.freshdesk.com/support/tickets/28709 yesterday...maybe of some use.Strange indeed, can you send in a bug report via help and support --> bug report? Please inform me if you did, then I can see what's happening
You can try to update via another power source (laptop/power adapter). Some cars actively repower the device when AA is killed (which we do when starting OTA). In firmware 2.1.0 we removed the killing of AA, which will solve these issues.
I checked. For some reason your phone is disconnecting from wifi 10 seconds after the wifi connection has been setup. Do you have any apps running which may cause this? Like tasker?
Last edited:
no not tht i know of. Pretty much stock android an very little other stuff on top.
As I can understand "bug report" has to be initiated manually, like start driving, then enable bug report, if problem appears, then stop and send right?Strange indeed, can you send in a bug report via help and support --> bug report? Please inform me if you did, then I can see what's happening
Does bug report work when passtrough is enabled (as this problem I described, was when passtrough was enabled).
Today morning disabled passtrough, but still constant connection drops. Should I try to send bug report with passtrough enabled or disabled or both?
Just been back out and tried anything I could find to see if it made a difference.
So far nothing, just same connect then almost instant disconnect.
Tried:
1.Disabling Adaptive Battery
2.Turned off mobile network
3.Forgot my home wifi network incase it was trying to relog into that
4.Turned off "Turn on Wifi automatically" option in wifi preferences.
5.uninstalled the Wifi analyser i did have installed
Happy to try anything anyone else can throw at me.
So far nothing, just same connect then almost instant disconnect.
Tried:
1.Disabling Adaptive Battery
2.Turned off mobile network
3.Forgot my home wifi network incase it was trying to relog into that
4.Turned off "Turn on Wifi automatically" option in wifi preferences.
5.uninstalled the Wifi analyser i did have installed
Happy to try anything anyone else can throw at me.
Yes, passthrough is also fine, but the logging is less detailed. In this case it's probably fine though.
Can you possibly send a phone side log? I'll PM you my email address.
You can generate a log via developer settings of the phone: https://support.wizyemm.com/hc/en-us/articles/360059933253-How-to-generate-an-Android-bug-report
I am having basically the same issue with my 2020 Gladiator and the 8.4 screen, but with an S22. Mine had been working flawlessly since I got it and one morning it just stopped connecting. I am able to get it to connect after factory resets like you, but if I like the truck sit for a few hours and the USB power off, I am back to square one.
These steps worked when connecting for first time in my case, unfortunately. Every subsequent connection it got stuck.
With 1.8 firmware AAW used to work fine without passthrough. Since 2.0.0 the only way to make it work with my headunit is using passthrough.
Checked it, definitly seems like the device is fully rebooting. Like in fully going back to solid green, blinking green, blue. Can you confirm this?
That sounds very odd. Does the device actually not boot anymore in these cases? I mean does the LED stay solid green? If so, it's most likely defective. If not, there's something else going on.
Similar threads
Top Liked Posts
-
3
Sounds very complex I'll build this feature into the next version of the app, possibly this week. Care to test?2
For the latest, please download: https://appdistribution.firebase.dev/i/5196d378c8e122d71
Please enable passthrough mode to verify if it also happens in passthrough mode.1Sounds 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
Haha nice! I'll pass it on to our UI/UX designerI got bored today, so I thought I make a mock up how the AAWireless app could look like When swiping t he car picture could change if you want to connect to annother device/car
View attachment 5645393 View attachment 5645397 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 guys5@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.4I 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
Yes, it's normal, but I'll remove it, because I get a comment about it almost every day3
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. -
40This 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.16I 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!15We 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
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.Hello. What's new in 1.5?
A full changelog for each release would really be appreciated
Thanks for all the hard work!14I'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.
New posts
-
Question No available update for Realme GT Master Edition- Latest: alinajafi19997
