yashsingh1/xdaforums huggingface dataset:
[Android Auto General] Mother_Teresa:
Hi @Emil Borconi . if this is not the place to ask, please direct me to the proper place.

Will (is) it be available only through the funding page or can I (and others?) opt in via other routes.

I am located in The Netherlands.

cheers

edit to also add something useful, the following app (root) may help enhance the experience (XDA link);

[ROOT ONLY] AA AIO TWEAKER - The ultimate Android Auto Utility
[Android Auto General] HofaTheRipper:
Hopefully there will be a fix for that! Everything else works so perfect and i dont want to mess with the cables anymore. I am sure @Emil Borconi and his team will find a solution.
[Android Auto General] Emil Borconi:
For Huawei internet problem please see the second faq post as well. Forget the AAWireless wifi and when you get promoted if you want to use the WiFi without internet make sure you ignore the question
[Android Auto General] Mips81:
Hello, I received mine.

I had problems.

i use phone Mi9 with latest update and car HYUNDAI i20 2019

My startup process to fix is:

I have reset the Android automatic app.

I reset the AAWireless Config app

Reset the AA hardware

Configure Android Auto

Android auto connect to my 2019 Hyundai i20 car

Disconnect from the car

Exit Android auto

Connect AAWireless

Launch the AAWireless Config app as a guest (no internet car wifi AAWireless detected)

Wait for the automatic opening invitation from Android on the car in your phone's task list

Launch Android Auto from the car

Ready to go

i20 2019

Logiciel: GB.EUR.SOP.V093.181122.DAU_A

Micrologiciel: GB.EUR.281.181123.MICOM.DL
[Android Auto General] InnocentSmith:
Waiting for mine to be shipped in the next month or two (if the factory picks up)! In the meantime, any Subaru owners out there have tried it yet?
[Android Auto General] voigtkampff:
Today I received my AAWireles, so far very bad experience. I tried reporting the ticket but got no confirmation that it was received so I decided to post here hoping for some help.

Phone: Sony Xperia XZ1 Compact G8441

Car: Mazda 6 2016

AAWireless when connected to car USB port shows green LED for 5-10sec, this switches to red for some 2-3 secs and restarts to green.

I was able to pair the device with phone after a few attempts. Car doesn't recognize AAWireless. When first connected there was a question box on head unit asking whether I agree to accessing contacts information or sth (don't remember exact text), this happened several times but now doesn't happen anymore (I chose agree). I was able to have "settings" usable for a brief period of time in the app, I tried enabling direct mode, then passthrough, but I don't know if the settings were stored in the device because my guess is that it's bootlooping. Also tried enabling debugging mode and send the bug report/logs (you got to be very quick for this because the button becomes active for like 0,5sec). My guess is that sending didn't succeed. Also tried resetting the device with a pin (I don't know if this does anything). I spent like 2hrs today trying combinations of direct mode/passthrough. It happened once that the device connected for a brief period of time (LED was blue and AA seemed to work). The interesting thins I noticed: clearing AAWireless Config data/caches doesn't delete the configuration that was previously stored, there seems to be no way of removing it. The phone connected with the same USB cable works (AA is connected), so probably not a cable issue. Please advise, thanks.
[Android Auto General] Notor1ouS-:
anyone tried it already in a Honda Civic 2017 (Sport Plus with its Android 4.2 Headunit)?
[Android Auto General] Mirkob77:
Hi good evening Emil Borconi. I would like to know if I receive an email notification when new AA wireless will be ready for pre-order. I have already an account indiegogo.

Thank you very much
[Android Auto General] Emil Borconi:
Sadly no. Keep an eye on indiegogo
[Android Auto General] seppbrandy:
Thanks Emil, I got it right at the end, now I have connection and Internet. Thanks again and great job.
[Android Auto General] tomballpkrxda:
I also have a 2020 Palisade. Did you come up with a creative way to mount or store this or is it just dangling in the cup holder area? If you have something creative, a photo would be nice. Thanks!
[Android Auto General] DevAuto:
Can you run the cable through the pass through hole in the center console and then use velcro to hold it underneath and out of sight on the bottom of the center console, right above the little storage area?
[Android Auto General] jasalta387:
Same experience here (Pixel 4 / Nissan Qashqai). I was asked to try with various cables to rule out a problem with the cable (cables are b*tch sometimes). I'm in contact with support. I'm hoping I can send some logs or something to have them look at the issue more closely.

I also get the dongle into that "boot loop" when using Pass-through on. The only way to unstuck is to get settings to allow you to set Pass-through off. I cannot find a reproducible pattern but what seems to help me is to take Android Auto app off the loop (turning off Bluetooth or clearing data of Android Auto) and try navigating back and forth into the setting of the companion app. If I use a normal charger (not the car plug) the bootloop seems to be slower and hence I can get a chance to change the setting.
[Android Auto General] Genebaby:
I'm waiting to receive my two devices, not sure when they will be in Australia.

I am pretty confident it will work ok on my 2020 Golf GTI, and I hope it works on the wife's 2018 Mitsubishi Triton Exceed.

Looking forward to OTA updates in the future, and maybe Apple Carplay support for when my daughter starts driving next year. I'd rather buy from you guys than the others.
[Android Auto General] goran_oh:
Someone with hyundai i30 2015/2016 to confirm if is working,tnx.
[Android Auto General] DevAuto:
This isn't my post, but it was posted yesterday in the comments on the AAWireless page on Indiegogo "Received my AAWireless today, works flawlessly in my Hyundai i30N. Can finally use the wireless charging pad as it was meant to be."
[Android Auto General] Genebaby:
In the 2020 GTI I have:

Device: 5NA035045F

Hardware: H55

Software: 1367

This is the 9.2" screen

In the 2019 Polo:

Device: 3Q0035824C

Hardware: 724

Software: 0890

This is the 8" screen

The GTI was at VW recently and I did ask them to check for updates on the infotainment and they said it was up to date.

Would be great to find out if that's true and if I can do it myself like the maps.

Also, I checked the other AAW device again and this time it got the 1.20 update. Haven't used the car in over a week so only checked now.
[Android Auto General] Marshy33:
I'm pretty sure your GTI has a mib2 High Harmin, which I didn't think had an issue with the headunit fully rebooting? I don't really know about these as they are different to the mib2 standard I have.

Your polo has a Delphi mib2 standard which again I wasn't aware had an issue. I thought it was just technisat (sometimes known as preh)

If you could get me the train versions for both as stated in my last post I can see if there's any updates.
[Android Auto General] speedyg0nz:
Device part number: 5K7035200L

Hardware: H41

Software: 0478

Train Version: MST2_EU_VW_PQ_P0478T

Just to provide the device information for my situation as well. Recall that my unit doesn't reboot, but constantly drops connection (does not appear to be related to audio or cable used) and the AA session usually disconnects as soon as it starts, and never lasts more than a minute. This is on a 2017 Sharan.
[Android Auto General] Marshy33:
What version is your AAwireless board? I was having some disconnection issues with V1.0.0, now on v1.2.0 or higher these seem to have gone for the short time I have been using it since the update.

Good to hear you haven't had any reboots on 478, I'm on 475 now its a far more stable than my previous versions. From what I'm aware 475 - 478 is just a minor update to the headunit's bluetooth.

You are on the most up to date software.
[Android Auto General] speedyg0nz:
I'm on the first batch of the boards, Backer ID below 200. Updated to V1.2.0 but still having the same issues despite trying different combinations of MTP/Direct, Passthrough, Audio Sink. Also, I got the technicians to update the HU software at the dealership last month, which explains the latest software.
[Android Auto General] Marshy33:
I have 2 boards the beta version and the production version (Which was also from the first batch). The beta version has been pretty solid for me, but my production board was playing up.

I manually did the DRAM fix on my production board and its far more stable. Even though it may not need it, it wont hurt doing the fix to see if it helps.

GitHub - Snirpo/aawireless-dram-fix

Contribute to Snirpo/aawireless-dram-fix development by creating an account on GitHub.

github.com

To add... I use MTP with passthrough turned off and only Auto Video Focus turned on.
[Android Auto General] Genebaby:
I am pretty sure my headunits do not actually reboot, it's AAW that resets at times, when it's asked to do some stuff, and possibly in a certain area. I was driving along there and tried to get an SMS, it all froze and AA was gone, and I have never recalled seeing the VW logo for a full reboot. I'm pretty sure the Mitsubishi unit in the wife's car did do full reboots, but I'm using both our units for now and she can join back in when the third one arrives and maybe things will be better for her.

Here is my full info:

GTI

Device: 5NA035045F

Hardware: H55

Software: 1367

SW Train Version: MHI2_ER_VWG13_P4521_2

Polo:

Device: 3Q0035824C

Hardware: 724

Software: 0890

Software Train Version:MST2_EU_VW_P0890D
[Android Auto General] Demondim:
Received my unit a few days ago, plugged in for the 1st time & performed the OTA update today.

Works perfectly.

Car : Seat Ibiza 2018

Thank you AAWireless :D
[Android Auto General] Marshy33:
That's good to hear they don't fully reboot, adds further confirmation this issue is just with the Technisat / Preh headunits.

Your GTI does have latest software. The polo's latest is 891, which I wouldn't think would be worth the upgrade.
[Android Auto General] Genebaby:
Thanks, how do we do the upgrade when it's available?
[Android Auto General] Marshy33:
I've been speaking to a person that helped me update my unit from 2xx to 4xx, who seems to have all the information. I'll PM you some details now.
[Android Auto General] wainy54:
Upgraded to 1.2.3, after I had applied the patch.

All worked mostly fine.

Firstly the patch worked, had to be spot on 10s holding the button. (This was done prior to the 1.2.3 release)

Update to 1.2.3 took two attempts, first one stopped at 90%. My phone seemed to connect back to my home WiFi. I tried again and it upgraded successfully.

Everything still working fine with the Audi A5 (B9). Audio timestamp and touch limit options applied.

The only thing of note is that sometimes, everything connects then disconnects briefly before reconnecting. Only happens at the start.
[Android Auto General] George234:
Hi Charlie, I also haven't been able to get my AAwireless to work since day 1 from the first batch. I have a Mazda CX5 Maxx Sport 2016 using a Samsung Note 20 Ultra.

I haven't applied the DRAM patch to mine. I have been through with support troubleshooting the connection without any luck. I've tried about a half dozen cables that all work with wired AA.

The behaviour of the notifications on your phone are the same as mine, 2 notifications where one states connected and the other searching and continuously loops.

One additional thing to add, I noticed on the head unit that under Entertainment the available connections list USB1 (for AA). This remains greyed/inactive the whole process. Under normal wired AA the connection would be shown as highlighted/active. Seems the AAwireless isn't even being recognised by the head unit (you would suspect the cable, but I have tried many).
[Android Auto General] Snirpo:
For some reason the CX5 is very problematic. Odd thing is one of our testers has an Mazda 6 with seemingly the same Headunit (model + version) and it works just fine.
[Android Auto General] sm753:
Got the OTA for 1.2.3 yesterday. Fixed my issues and so far from testing everything works without issue. Prior to the OTA, it would only connect with passthrough enable and would constantly disconnect and reconnect every couple of minutes. Now just trying to dial in the DPI settings for optimal split screen mode. Thanks to the project team!

2019 Mazda CX-5

Pixel 3a XL
[Android Auto General] Dion.Dube:
I have a 2017 Camaro SS as well and the USB in my car only stays powered for a minute or two after I exit the vehicle, does your behave differently?
[Android Auto General] xxBrun0xx:
Nope that's pretty much it. But it keeps trying to reconnect several times before it gives up. Annoying if you're trying to use your phone right away, but definitely not a deal breaker.

Do you also have to use Pass-through mode on yours to get it to connect reliably? MTP seems to never actually connect in my car.
[Android Auto General] 88fingerslukee:
Anybody have issues flashing the OTA? For whatever reason my app will not update my device. It keep saying update failed.
[Android Auto General] dablessing:
I had these same issues. Scroll up to my last post, I provided instructions I followed and it worked. It may have also been that my work outlook email account required administrator access, so the security policy wouldn't allow unsecured wifi networks. I turned off the admin access too and did those steps as mentioned and I got it to install to 1.2.3.
[Android Auto General] vizzze:
Yes it does have the navigation system:

Train version: MST2_EU_VW_ZR_P0359T
[Android Auto General] milanxx:
Yes, when they are turned off or on, but in the BT profile without the call function, the native connection works

And I thought, update the SW in the dongle. I have 3.0 so probably only 3.1. Update 3.0 will probably not work on 3.0

I did the reset several times during the experiments.
[Android Auto General] 1Epitaph:
I have a hotspot in my Explorer that a dashcam connects to and I have been using it with aawireless with no issues. Not sure what has changed but it is no longer functioning when connected through the hotspot. The interesting thing is that when I switch it to connect to the hotspot, It is still accessible. I mean that the app can see it and I am able to change settings on it.... but it wont connect AA. Any Ideas?
[Android Auto General] Snirpo:
What the name of your device? (AAWireless-xxx or AndroidAuto-AAWxxxx)
[Android Auto General] 1Epitaph:
AAWireless-JvO9k8xp
[Android Auto General] Snirpo:
Please update the companion app to 3.35. Wi-Fi client mode was broken.
[Android Auto General] mealzonwillz:
Hi,

I have a device AAWireless-zMFHxDsR.

What the latest firmware it can upgrade to? At the moment it's on 1.80 and the app tells me there are no updates for it. Most of the features on the app is unavailable because it needs a newer firmware.

Reason is I have a Hyundai Tucson 2023 and connects only if Passthrough is enabled. Wanting to know if there's any other way around this, and if there are any firmware versions suitable for this dongle that I can upgrade to.

Thanks.
[Android Auto General] hako612:
Hey @Snirpo,

I wanted to use AAWireless (fw 3.0.0) for CarPlay with my iPhone mini 13 and iOS 17.0.1 in my Opel Astra K, but CarPlay doesn't start after following the article on the AAWireless website.

Could it work with a newer version of the firmware? If so, please let me receive the newest firmware.

Thanks in advance!

Device ID: AAWcc149aa0
[Android Auto General] kbwang75:
@Snirpo

I just purchased a AAWireless on firmware 3.0. My car is a Mercedes on Mbux. My phone is is Samsung S21 5G on ANDROID 13.

I noticed that it's Unable to reconnect after the next drive. I Need to delete car in android auto app and then AAwireless will reconnect and Android Auto app will create previously connected car. My infortainment screen will be connected to android auto.

The unable to reconnect issue will reoccur when I turn off my car.. ..restart the car.. then unable to reconnect again..as per what I explained earlier . I Need to delete car in android auto app and then AAwireless will reconnect and Android Auto app will create previously connected car. My infortainment screen will be connected to android auto.

This cycle kept continuing. I tried resetting the AAwireless and clear cache/Data in the phone but it's useless.

I have enabled pass through

Is there any members here that can shed some lights on what's the problem ?
[Android Auto General] milanxx:
And the mobile does not protest with a red screen?

Either way, try the start stop directed at the BT car.
[Android Auto General] Snirpo:
Disable dongle mode in AAW settings. Unpair AAW device, clear AA cache data, and re-pair. That should do the trick.

To confirm, on second connect you're getting the dreaded "looking for Android Auto" notification but AA won't start? This means AA is waiting for the handsfree of the car to connect. Are you also using a smartwatch by any chance?
[Android Auto General] milanxx:
@Snirpo

The contagion is spreading. A colleague with S23 today the same as me.

He also got the PrivateComputingService update today, that's the only system update that came.
[Android Auto General] boshi24:
I think I have the same problem, it worked without issues for weeks/months (last time on Wednesday) but today AA stopped working. AAW keeps on flashing green then flashing blue and green again. My phone loses the wifi connection every 10-20sek. AA keeps on "looking for AA" and AAW is "synchronising" but AA does not start on my car. I can start the AAW app but it looses the connection every 10sek. No settings were changed and no watch connected.

Not sure if the "PrivateComputingService" caused this because the last update was on Tuesday (new update available now but not installed yet) but AA still worked on Wednesday. I'll try a few of the tips from here tomorrow.

Edit: I've installed AAW version 3.0 today but nothing changed. App version is 3.35 since Tuesday.
[Android Auto General] kbwang75:
@Snirpo

I will proceed to unpair/delete all current AAW pairing, clear all data and cache and re-pair everything and will report back the situation.

You right, During the second connection, I am getting the"looking for android auto" and I think also noticed a "AAW Synchronizing" notification and AA is not starting. The S21 phone don't have a smartwatch paired..

What do you meant by waiting for hands free of the car to connect? Do I need to do anything for this ?

Thank you so much for responding
[Android Auto General] kbwang75:
No red screen. Disable start stop directed at car ?
[Android Auto General] DBrice:
How do i get the update to 3.1 so that I can have full screen carplay android auto in my subaru ? AAW1ee7eb6d

currently on 3.0.0 with a tiny car play screen
[Android Auto General] Snirpo:
When you're getting the "looking for AA" notification. Is the Bluetooth handsfree connection of the car connected to the phone? If not, AA won't start with dongle mode (the native mode) enabled.
[Android Auto General] kbwang75:
If it's not connected to the car BT, AAW will not start in dongle enabled mode?
[Android Auto General] kbwang75:
0

@Snirpo

When I disable dongle mode. It's seems to be working , reconnected in the next/subsequent drive without any manual intervention.

Do you mind explaining what is the root cause ? Is there something to do with my s21 phone not connected to my BT car hands free ? I think I did noticed my s21 phone not connecting my car BT hands free.
[Android Auto General] J_E_F_F:
My multiple phone connection problems started in combination with both enabling dongle mode and upgrading to fw 3.0

probably need to go back and disable dongle mode.

One phone would connect, and if that person left the car, the next phone would never connect, green blinking light, reboot, aaw/and phone, no chnage. Finally reset aaw and it connected after a few minutes.
[Android Auto General] ktamm0:
Just looking to confirm if my current device is a generation 1 or 2 device and might be capable of CarPlay. The sticker on the bottom says

Model: CS307-e2w1s2

Date: 2021-12-10

AAWireless App shows AndroidAuto-AAW6b5ce566.

Was trying to get things connected with my 2017 Audi A4 and the gfs iphone 14 pro but it wasn't able to connect. I was able to get to the ip through a browser while connected to the aawireless hotspot though. I noticed other people are having issues connecting so not sure if its a gen1 vs gen2 issue, or possibly with VAG not quite being supported yet.

Looking through posts here and the firmware docs looks like cs317 is the gen2 device..... I updated to the 3.0.0 firmware without the lockup that others have experienced which seems promising. Looking back through my Indiegogo / kickstarter emails there was traffic around the time of my purchase of the switch from gen1 to gen2 hardware and the timing almost suggests it could be a gen2 device. Guess I'm almost hoping the sticker might be misleading me. Alternatively I figured I'd post here in case the developers are looking for more people with the gen1 device

My friend had also bought a device (cs317-e1w3) so I might be able to borrow his to see if it is my aawireless device or the A4 causing the issues.
[Android Auto General] Saggy2121:
So I have a Vauxhall Combo 2020

Set it all up as prompted

Autostart on AA doesnt seem to work and have to do it manually and the light starts flashing blue then goes to solid.

Everything seems to work though.

Need to be worried on the solid blue light?
[Android Auto General] Snirpo:
Very likely your car's hands free is not connecting to the other phone, when the person with the first phone steps out of the car. So AAWireless will try to connect to the other phone, "looking for AA" notification will show up, but AA won't start.

Bassicly if you want to have multiple phones working correctly, switch off "dongle mode". This is also mentioned in the app on the "phones" screen. Phone priority from the AAWireless side will simply not work with dongle mode turned on, because the car's handsfree connection to a phone determines which phone will start the AA connection. Works as designed by Google. This is the native way of doing stuff.
[Android Auto General] Snirpo:
Yup, that's what I expected. The root cause is mentioned in the post above. If the phone wasn't connected to the handsfree of the car, AA will never ever start. There's nothing we can do about this, except doing it the non-native way by disabling dongle mode.

It's unfortunate, but that's how Google designed it. I do get why they did it though... A lot of (especially factory) head units suck balls and my might go haywire when AA (tries to) connects too early. If you wait for the hands free of the car to connect to the phone, then you at least know the head unit has been fully booted up. It sucks, but that's what it is.
[Android Auto General] HairyMilkshakes:
My AAWireless device keeps spamming synchronization notifications on my phone. Until I restart the service or my phone it won't go away.
[Android Auto General] kbwang75:
Thank you so much
[Android Auto General] floofyfloof:
Is there a place to read the dev build change log? Like an auto generated commit log that exists somewhere
[Android Auto General] Snirpo:
Hmm, that might be a bug, is AAWireless still powered when this happens? (Like in a car with always powered USB?)
[Android Auto General] Snirpo:
Yes, when you are part of the internal beta program.
[Android Auto General] HairyMilkshakes:
That may be the case. Quite honestly I am not sure as AA stays on for a bit then disconnects after the car powers off after a min or so. But this issue happens after I am already away from my vehicle for an extended period of time as well.
[Android Auto General] Snirpo:
Does the "looking for AA" notification also show up?
[Android Auto General] milanxx:
I did that with AAW in the office. Connected to PC and set start stop. And then an endless carousel of notifications even though the plug was no longer powered. It ended when I put AAW stop in the annotation.