Does the PC method still work?Hi,
i was wrote form the team to downgrade to Firmware 1.5.
I downloaded it but there is no chance to install it.
It look like the device can't connect to my mobile with Wi-Fi. Bluetooth to connect to phone is established.
Then i delete the cache and data from aa-connect. Big Mistake!!
Now i am unable to download 1.5 again.
I mean it is not so good to question to another download to my perk when i can not connect with Wi-Fi to install it!
What can i do to bring back the Firmware 1.5 without connections?
Interrupt the boot sequence 5 times, How long is the time slice?
Pull the power Cable out, with LED static green or with LED 3 times blink?
To be honest, I don't know at this point. We have over 3800 boards now on 1.7.1 and very few tickets of issues with 1.7.1. Anyway, we're stopping updates for the old boards for now to investigate.
Hi festor,Does the PC method still work?
Download the latest firmware file (1.8.0): First (with firmware from factory 1.0.0): https://drive.google.com/drive/folders/1TcJXyMSc3KsKtwZ5ZpTpW5bgg7ZbVYe9?usp=sharing Second version (with firmware from factory 1.1.0): https://drive.google.c...cpeb.freshdesk.com
+1 problem z połączeniem. AAWireless nigdy nie łączy się z Wifi. Nie ma widocznej sieci Wi-Fi AAWireless-XXXXXX. Połączenie Bluetooth działa dobrze, ustawienia można regulować. Po uruchomieniu dioda LED miga na zielono (ciągle zielony).
Po podłączeniu AAWreless po raz pierwszy, pierwszą rzeczą, którą zrobiłem, była aktualizacja. Działało dobrze od 1.3.0? do 1.7.1
Ale posłowie nigdy nie dostałem niebieskiego światła. Nigdy nie widziałem sieci Wifi AAWreless. Resetowanie, anulowanie parowania, usuwanie pamięci podręcznej i danych itp. nie rozwiązuje problemu. Przejście na wersję 1.5.0 nie jest możliwe, ponieważ aplikacja nie łączy się z urządzeniem.
I think the problem ist not only at a "few" boards of the first batch. Do you see how many customers of this GEN updated to 1.7.0/1.7.1? How much percent of them use this? I think there could be many more with this problem but the most of them have not used this FW, or dont update to any new version or are not interested for searching for the issue and dont report them to you. Not all of this users trying to keep in contact in this board to you or your App.
Yes, we can see exactly how much boards of each model are updated to a certain version.I think the problem ist not only at a "few" boards of the first batch. Do you see how many customers of this GEN updated to 1.7.0/1.7.1? How much percent of them use this? I think there could be many more with this problem but the most of them have not used this FW, or dont update to any new version or are not interested for searching for the issue and dont report them to you. Not all of this users trying to keep in contact in this board to you or your App.
Please contact support at [email protected] and ask for a replacement.Hi festor,
My PC unfortunately does not have Wi-Fi, after borrowing a laptop and struggling with transferring the web link to no avail, I searched for the Wi-Fi AA wireless radio network.
When I print the mail to PDF, the web link no longer works.
The AA-Wireless* network does not show up.
As soon as there is power on the device the green LED goes on permanently and then flashes 3 times each.
A Bluetooth connection is present and I can change the settings.
Neither with or without Force 2.4 Ghz I see the network on the laptop.
The phone is permanently searching for Android Auto.
Translated with www.DeepL.com/Translator (free version)
This notification is from the start/stop mechanism, which means the companion app is in control of starting up AA. I'd disable it if you don't need it.Testing the other day in my Golf when I went to 2.01 showed that I wasn't getting AA projection automatically still.
I reset my AA all through my phone to start using 2.0, which means redoing my shortcuts, background, app arrangement etc, but it doesn't seem to have worked.
I have no trouble with launching AA with the Ottocast in the Polo. Apart from not being able to do Stop/Start stuff for the cars that power the USB before and after the engine is on, it's otherwise pretty reliable and has gotten better with a few FW updates. The Assistant sounds were janky to begin with but are now fine. A newer FW messed up things like dark mode not working with the lights on and sometimes you would get a black screen until you went to another screen and back to AA. I downgraded the FW back to the one that was working good before, I'll keep it handy as I try new ones.
So I had to re-connect to the Ottocast and it's been fine again since but with AAW I am still having to go into the APP, changing the connection method, and upon saving and rebooting it will launch nicely. But not the next time I go into the car, which was four times today. It so far hasn't mattered which connection I try, default, direct, or MTP all work if I change to them but not upon the next try.
The previous time I disabled Dongle Mode but it still wouldn't connect until I changed the connection. When I do drive this car it's nice to have AA so I'm doing this every time but it would be nice if I didn't have to.
Also, recently, probably after 2.0, I get this notification on my phone after using AAW. I have to press the stop button to stop it doing what it's trying to do. Does anyone else get this?
It should normally indeed. Bassiccly every change we do in the start / stop mechanism it breaks for half of the people and fixes stuff for the other half.
It's probably helpful to explain for everyone how the process works So here we go:So I have some updates on my situation and wanted to share for future refference. I managed to get it working in "dongle mode" and also made "stop/start" work. Actually it seems that the only way for "dongle mode" to work was to also have "stop/start" enabled and functioning. It seems that withtout it my phone will not connect to the WiFi created for wireless connection (which is called "AndroidAuto-xxxx" when in dongle mode, different than "AAwireless-xxxx" when in "standard" mode.
The issue was the wifi being turned off by the system. Newer Android OS (11 and above I believe) have this WiFi setting option that turns off the WiFi when you leave a "known location" and turns it back on when you get back to those "known locations" so the issue is that the bluetooth beacon that is sent by the dongle is not enough to trigger WiFi to turn on and connect to the WiFi.
Note that this issue does not manifest itself when I am using a car with proper built-in Wireless AA. I have a Skoda Karoq that has built-in wireless AA and even if my WiFi is turned off, it will turn itself on to connect to AA, just not with this dongle.
Anyway, long story short, because when "Start/Stop" is active I have a constant notification on my phone from the app indicating the status (connected/not connected/etc.) it showed me "wifi is turned off cannot connect" or something simiar. So when I manually turned it on, everything started working. My phone connects imediately to my car with "dongle mode" ON and "start/stop" ON.
What remains an issue is that it will not work with "dongle mode" ON but "Start/Stop" OFF. It seems that without the helper app "helping" the phone to connect to the wifi of the dongle, the phone will not do it on its own. This is not a big deal for me, as I want to have "start/stop" enabled anyway.
So bottom line, everything is working perfectly fine for me now.
Hope this helps others and helps @Snirpo to figure out if they might want to change some stuff for their app.
That's weird, I expected the display to be upside down...
I haven't tried FW 2.0 yet, and I don't know if you're able to set the channel bandwidth in FW2.0, but at least in the US, channel 165 is the only channel that can only do 20Mhz. But that is why I expect channel 165 may end up being the best choice for most people. I would expect less interference, since most people may have chosen other channels on their routers to get more bandwidth.
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.
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
Emil Borconi-Szedressy 2 days ago
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.
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
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.
Disgruntled in the UK