yashsingh1/xdaforums huggingface dataset:
[Android Auto General] :
I am not a hater. But there is a point reached where i cant support the decisions from @Snirpo anymore.

I was early onboard! I backed that thing up and waited pacietent for shipment because i saw the "vision"

I am owner since the first shipments and its still the same problem that makes aawireless unusable!

@festor Go some pages back and search for my posts before you call someone a karen.

There is no fix yet. Support tickets are not getting the atteion they needed - talking about resetting the device.

I followed every step on this forum there are a lot of Galaxy (S9 /S10 /s20 / s21) Owners who have the same problem. Most of them dont even get a response.

I bought a plasticbrick and all my trials to get support or to resolve this issue end in some nonesense pre-printed answer.

Im happy for all the guys who dont have problems and can say "dont listen to the haters" but there are people who have random disconnects since day one. and then to see an app release just makes me angry, yes.

Resolve the issues first before making new features
[Android Auto General] EViollet:
To be honest, I'm patiently waiting for the new firmware.

The device worked kind of flawlessly for me up to the new app. Now it no longer connects, so I'm back to plugging in the USB cable again, hoping that new firmware solves the issue

I tried deleting app info, Bluetooth pairing, but it currently won't connect.

I also feel that they new app was released too early. It seems to cause more issues then it solves.

Fingers crossed.
[Android Auto General] josefsch:
There also is a recent post by Chiel Prins on Slack:
[Android Auto General] festor:
It was not targeted at an individual, but if people are allowed to have their opinion on the "failings" of the project and its staff then I'm allowed to have my opinion on those who make those claims.

There are "backers" that jumped into this with ridiculous expectations. It probably wouldn't exist without a crowdfunded platform so people have to accept that comes with limitations. In saying that, AAWireless give refunds when not required and even provide a transferable warranty if you sell on your dongle.

You have to understand that with so many combinations of phones/vehicles and software/firmware versions it might be the case that you won't get it to work. The team need to way up the endless requests for additional options and all the other connection issues/bugs and decide a priority list from that aggregate.

You infer that I don't have issues, but I certainly do. I can't make calls at the moment due to the random disconnections using a Poco F3/Skoda Superb, but I'm not making accusatory statements, demanding my particular issue is sorted. My wife has no issues with her S21/VW Golf so your issue certainly doesn't affect all Samsung users.

If AAWireless was genuinely unusable for me, I wouldn't have persevered for over a year. You can still sell it for much more than you paid and maybe someone with a different setup will get some use out of it. You didn't buy anything, you backed a campaign... move on with your life and pick up one of the alternatives.
[Android Auto General] sibesaver:
If you read most of the posts that are complaining the vast majority are just about a lack of communication on the software / firmware side. Constant delays and technical issues are certainly eased with the user community if there's communication. I have 30 plus years of IT experience and that's to me unacceptable, regardless of the state of development and the technological challenges faced.
[Android Auto General] festor:
I think we will have to agree to differ on that. I don't believe most complaints are about lack of general communication. I think they are from users that want very specific communication about their particular issue.

I would prefer the team spent their time on development than providing updates that only end up getting used as leverage and further complaints. Emil has mentioned many times that tickets and emails increase exponentially when he posts an update.

Can I ask, do you believe that posting dev updates here speeds up actual development in any way?
[Android Auto General] gcd:
People are asking for possible solutions/status of their problems. This doesn't make them "haters." I have 2 AAWs, which I paid around 200$, which I can't use because of the disconnection issues. Does it make me a hater to ask about it? I want a status update, except fw 2.0 is coming this week/next week etc. Will it fix the problem?

AAW was a pioneer; now, they're promoting MA1 unintentionally because of the problems AAW has and MA1 doesn't. I switched to MA1 due to the issues I had with AAW. People are demanding a simple thing: Connection stability. Does it make them "Karens"? Meanwhile, AAW continues to sell on Indiegogo with these very well-known problems.

I paid 100$ per dongle, and I think I have the right to ask if the issues will be fixed or not. Currently, forget about the extra functionalities; it can't deliver a stable connection with my phone, making it unusable. So first, make it work, then they may deliver the extra functionalities.
[Android Auto General] festor:
If people are simply asking for updates, I totally agree this doesn't make them haters or Karens. We completely agree about that.

Can I ask if AAWireless works for you in passthrough mode? Can I also ask, what percentage of users experience connection issues using AAWireless?
[Android Auto General] Snoogins34:
Re: Chiel's Slack post - in my case, I did indeed choose the BT device that should trigger the Start/Stop functionality in the app. That did not trigger an attempt to save as far as I can tell.

I ended up joining the beta channel for the app yesterday, and I was prompted to install the app again in the Play Store, although the version number did not change so I don't know if it was a slightly newer version or not. After that, I tested both Start/Stop and Auto Video Focus. In the latter case, I got the "Can't save settings" message after enabling it, while Start/Stop was the same as before with no message but no acknowledgement of my changes.
[Android Auto General] gcd:
It's only working in passthrough mode for both my cars. I have an intermediate disconnect - reconnect problem, precisely around the same spots, three times while going to work. MA1 doesn't disconnect on the same route (or any route whatsoever)

The other members also reported the same problem; some said interference, radars, mobile data, etc. No one exactly knows the cause of the issue, and we can't hear anything from the AAW team that they're working on it; they found the reason or even something like we can't fix it. I'll even accept if they can't fix it.
[Android Auto General] 2SR82:
A Tip for all the Mazda Drivers (and perhaps others too).

After Update of Android 11 to 12 on my Pixel Phone and a Update of Mazda Connect Entertainment System at the same time, I was not able to connect my phone with AA Wireless anymore (cable connection was fine all the time).

It always tries to connect and directly interrupts again).

I did countless tries of reset of phone apps, settings and so on. I was in contact with AA wireless support and tried all what they was telling me... Nothing helps.

3 days ago, I tried again and also doing a "factory reset" of Mazda Connect system and after this it started working again. I only need to enable pass through and that's it.

In my tries before I only removed the Bluetooth connection in Mazda connect and after the update I also doing some Option to "delete Cache and Settings" during the update procedure, but as it looks now this was not enough.

So my tip is to not only reset settings on the phone side if you have some problems, also give it a try to really factory reset the car entertainment settings.

I hope this will help some other too.
[Android Auto General] sibesaver:
" I think they are from users that want very specific communication about their particular issue."

I think you're misinterpreting people that come seeking other advice on how to fix an issue. After all that's what XDA forms are all about, helping one another. But to each his own.

EDIT - never said it's sped up development and I'd be naive to think it would. But if you've ever had an IT job you realize you have to report the status at least weekly if not more often. I'm not even asking for that just the same frequency as the shipping updates. If you're going to take the time to write an update make it inclusive.
[Android Auto General] andy o:
I was initially having the same issue with my Pixel 6 Pro working only with Passthrough on my 2016 Mazda 3 but I got it working. Can you try this? Disable Passthrough on AAWireless. Then clear storage (not just cache) for the Android Auto app, and set up Android Auto again, with passthrough disabled, before you set up wired Android Auto. See if it then prompts for AA setup.

If it works, you can then set up wired Android Auto with your phone directly, and after that you shouldn't need to set up AA again with the dongle if you enable Passthrough. Passthrough-disabled and Passthrough-enabled are seen as 2 different cars by AA, and Passthrough-enabled and wired AA are seen as the same car, at least in my setup. I suspect this has something to do with the problem.
[Android Auto General] andy o:
AAWireless and MA1 use different WiFi channels so it's expected that interference won't be the same, but it's also possible for it to happen with the MA1 and I've seen some complaints. It's possible that because there are so many more AAW in the wild, and since it's a more complex product with the extra features, that there are more disconnection complaints about AAW than MA1. Hopefully changing the channel with the 2.0 fw will fix most of these disconnections.
[Android Auto General] jeremyt561:
Thanks for this information. This worked perfectly for me. My device was working in pass-through mode only. After doing this I am now in direct connection mode and it's working perfectly. I have a 2016 CX-9 and a S21 ultra for reference.
[Android Auto General] festor:
Thanks for the info. Hopefully they can resolve your issue. I've seen posts from MA1 users having connection problems with Xiaomi phones which seems similar to my Poco F3/MIUI issues with AAWireless. Also, when I try passthrough on AAWireless it keeps crashing and this seems to be an issue with MA1 and some Technostat head units too. I need the VW fix option which the MA1 doesn't appear to have.

I'm also trying to gauge how common these issues are. I see people posting that these problems are widespread, but what are they basing this on? Over 63 thousand backers with plenty (like you and me) ordering 2 perks so is this just assumption or are there figures available somewhere?

I'm talking about the comments such as "perhaps they are just trying to rake in as much money as they can before closing the doors."

Are you suggesting internal status reports should be posted publicly or do you mean other dev teams

post public weekly updates? Maybe you have some examples? We actually seem to agree that posting these updates won't actually speed up development so I don't understand your logic. If you believe the team, it certainly doesn't cut down on emails or tickets either so there seems to be no upside.
[Android Auto General] gcd:
I don't know the percentage of the disconnection problem. But even in this thread, I think it's not that rare to omit this problem. MIUI has a different problem with the phone. It looks like it's not compatible with any of the AAW solutions. I don't use MIUI

Here is a search result in this thread: https://xdaforums.com/search/39916687/?q=disconnect&t=post&c[thread]=4247677&o=relevance

Some random posts:

https://xdaforums.com/t/aawireless-general-discussion-and-support.4247677/page-130#post-86692459

https://xdaforums.com/t/aawireless-general-discussion-and-support.4247677/page-97#post-85923807

https://xdaforums.com/t/aawireless-general-discussion-and-support.4247677/page-122#post-86568703

https://xdaforums.com/t/aawireless-general-discussion-and-support.4247677/page-130#post-86690067
[Android Auto General] maisonmdsgreen:
Thanks replay, I've tested it on other phones, same thing.
[Android Auto General] sibesaver:
Okay from the questions you're asking you apparently not reading my post fully. I said I don't expect weekly or even monthly updates but if you're going to report shipping updates you can include software in the same update. Not that hard to comprehend.
[Android Auto General] LM1970:
The product is fine, but it disconnects during some journeys always in the same place along the road. You can reconnect manually after a few hundred meters. S22
[Android Auto General] festor:
I fully comprehend what you're requesting, you want news, regardless of how it affects development. I just didn't accept your analogy of having to "report the status at least weekly if not more often" in an "IT job" correlates to this situation or even why you mentioned it. Maybe you can elaborate or provide some examples?

I think it might actually hinder progress. It generates more enquires (i.e. work) from those that don't feel the news catered to their issue and makes it harder to change direction if required. It also adds pressure to rush updates because some expectant users take an estimate as a promise.

Emil posted an update on March 2nd about the app/firmware over at indiegogo and you said you "don't expect weekly or even monthly updates", but you go on to suggest we should get dev updates with every shipping update now? We know they are working on the firmware and the app so I'm happy with that. I personally don't need to know the minutia, especially if it might actually slow down development.
[Android Auto General] -Loom-:
I have one of the very first AAWireless units from the first perks shipped.

I'm using it with a OnePlus 8T with Android 11 and a VW MIB 2.5 headunit - Unfortunately it's one of those problematic Technisat headunits. It's running in USB direct mode, and since the VAG Fix was implemented, it was smooth sailing for about half a year. Speaking: no headunit reboots anymore.

About one month ago, I enabled passthrough mode - just out of curiousity. I quickly realized that it will disable the VAG fix so I disabled passthrough again.

And ever since that I get those frequent disconnects every now and then. It's not a headunit reboot, just loss of connection to AAWireless followed by a reconnect 10 seconds later. Basically the same things many other users reported here.

Things I've tried:

- Upgraded to the latest firmware (was using 1.6 before)

- Factory reset of AAWireless

- removed and cleaned everything AAwireless and Android Auto related stuff on the smartphone, including bluetooth

About the only thing I didn't do yet is to factory reset the headunit itself.

This really puzzles me since it was working without a single disconnect for half a year, and after this switch to passthrough and back again it's disconnecting up to 3 times in 20 minutes of drive. And it really happend immediatly after using passthrough. So, it doesn't look like a coincidence.
[Android Auto General] mobileman88:
Likewise, I paid for 2 AAW (1 as a backup) of which both aren't working for the past few months. Not that I am a hater. I have spent another $100 on a MA1 which works reliably for now.
[Android Auto General] mobileman88:
For my case, passthru mode is worse, when it disconnects (the screen simply doesn't update for 10-20 mins till the time I disconnect AAW and reconnect it back). At least for MTP/Direct mode, it reconnects after about 60 seconds (only problem is that my Waze might have lost its destination by then which is very annoying) although my Spotify can resume where it left off.
[Android Auto General] :
@Snirpo

Yes even in passtroughmode. (Sorry did not saw your post before)

The Problem accurs allways in the same spots.

I tried every mode and every option that the old app provides. (Switching ghz etc)

Im happy to help out with data or anything that helps.

Just hit me up.

I work in the IT for 10 years and have a ground knowledge of technology so you dont have to explain a lot to me - when we work things out.
[Android Auto General] ddiehl:
I recently purchased one of these and so far it works great and not experiencing any of the disconnect issues. My only problem is that anytime I'm in range of a WiFi hotspot I may have previously connected to the music will start cutting out, as I think it's toggling between WiFi and 5G. I already turned off WiFi scanning in location services but that didn't help. It's just a minor annoyance and not a dealbreaker but annoying none the less. Is there any solution for this? Overall a great product and I'm very pleased.

Phone Pixel 6 Pro

Car MK7 VW Golf Alltrack with MIB
[Android Auto General] festor:
I'm not sure if it's the same issue, but music skips and cuts out intermittently for me when I use the 2.4 GHz option. It greatly reduces disconnections, but I don't think it has enough bandwidth to cope with everything. Hopefully the upcoming new firmware with extra 5 GHz options will solve both of these issues.

I just got an update for the app btw:

WHAT’S NEW

- Fix start / stop settings

- Bring back the save button

- Improve bluetooth connection stability

This is an intermediate release, we will further improve the bluetooth connection stability in further versions.
[Android Auto General] Snirpo:
Yeah, not sure what I'm looking at anymore though cause according to some of our testers 2.1.0 didn't have any connectivity issues for them. Also 2.2.0 is way and way more stable connection wise on an Xiaomi Mi 10 (surprisingly) vs my Pixel 6 Pro. So confused... On the Pixel it seems you sometimes need to retry connections up to 5 times before it actually connects.
[Android Auto General] sibesaver:
My pixel 5A is connecting reliably 100% of the time with no disconnects so far. I do have an audio issue when I'm near my home Wi-Fi, the YT music sound will leave the head unit and play through the phone speakers before reverting back. Using the latest 2.2 app.
[Android Auto General] Dangze:
Have a look here :

Motorola MA1 for Android Auto Wireless Review: The 'easy' way isn't always best

The Motorola MA1 dongle promises to deliver wireless Android Auto, and it does, but bugs paired with no future support isn't a great formula.

9to5google.com

Enjoy...
[Android Auto General] SOFO888:
Hello together,

In general my AAWireless devices are running fine now.

I just have the following issue from time to time: sometimes my phone connects to AAWireless WiFi, but Android Auto does not start.

What I tried so far:

- Reconnecting to the Wifi (turn Wifi and Bluetooth off and on again on the phone) --> did not help

- Disconnecting AAWireless device from the USB port and plug it back in --> did not help

- Disconnecting Bluetooth from the infotainment system and reconnecting --> did not help

- Starting the Android Auto on the phone helped only one time, all other times it did not help

Only one solution works: restarting the phone.

Based on my tries it is not related to the AAWireless device in my opinion. It seems to be a Google bug.

As I read through the thread I found out that there is a certain amount of people having similar issues, but no real solution so far.

My question is now: does anyone have any idea why I have to restart my phone to get it to work? Is there any cache to be deleted? Is there an app that has to be force stopped and restarted?
[Android Auto General] dzeidzei:
I've had this also. Starting AAWireless app usually has fixed this and if not then going to aawireless settings page and saving settings has worked always.

On the other note, latest beta update finally fixed settings for me and I was able to enable start/stop. Still not tested enough but it might be that if I access setings page in app too quickly, the app does not correctly connect to device and settings can't be adjusted.
[Android Auto General] SOFO888:
Thanks.

I will try next time when I have this behavior.

It happens right now every 2 weeks.

Moreover I would like to understand what the reason is...
[Android Auto General] Genebaby:
Amazed that MA1 has no update ability, that's seems a bit crazy if backed by Google, who are always changing things here and there.

Sometimes issues are related to your phone, or an AA bug in general. I remember a few weeks ago I got in my oldest car that has a wireless AA/Carplay box and I need to press to talk to the Assistant. I couldn't press, it wasn't working at all to do that function. Thought something was wrong in that car but it was the same in the other cars, and then it went away. Strange stuff.

Other devices are just trying to work as simple pass-through and not always that great at it, but at least they have FW updates, save the MA1.

The best thing about AAW is it has the app and you can acheive other functions as the thing we are all doing here is introducing a wireless AA connection to cars that were not designed for it, so behaviour before and after connection can be strange as it was never intended to work that way.

The Start/Stop funcion is a great example of overcoming issues with the USB ports that you were only meant to plug your phone into.

In a VAG car I like that the port powers up when I do something to the car, anticipating me getting in, so it starts booting up and connecting AAW. The downside is turning off the car and the port still being active for a little while and your phone being tied to it.

So thanks to the AAW team for all their hard work, and I'm sure many people are blaming the device when there are so many other things that can get in the way at times. Hopefully it's smooth sailing as much as possible.
[Android Auto General] antman68:
I still have the 15 April update and Play Store says it's up to date. I am a beta tester so I'm not sure why I can't see the new update.

My connection time has been really slow since the 15 April update - sometimes 5 minutes or more (I have tried different cables and changing conection mode). The app only works properly in passthrough. Hoping that the new update fixes up hte connection time and lets me enable the Start/Stop function again.

I've noticed that the unit is getting very sensitive to bumps (e.g. pot holes or speed humps) or just being slightly knocked by my hand or anything else, causing it to disconnect. It's mounted on the roof of the cubby next to the USB port.

Edit: Play Store says that I have version 2.2.0 but the change log mentions an added Korean translation, fallback to manual device pairing, auto save of settings but nothing about fixing the Start/Stop settings, reinstating the save button, etc.
[Android Auto General] antman68:
But it seems like most people, including me, can only get AAW to work properly in passthrough mode. You get the Start/Stop function (when it is working - currently not - but there are otherways to skin that cat, e.g. Bixby routines, IfTTT, Macrodroid, etc.) but none of the other extra functions, so it's barely different from the other devices.

For clarity, I can get AAW to work with passthrough disbaled but it is always losing media volume control (hijacked by Assistant volume control) and Assistant goes mute after receiving any notifications, making/receiving calls, dictating texts or other instructions to the assistant. This is on a VAG MIB2 head unit (2016 Golf). I'd love to be able to change the DPI, remove the tap restriction, etc. AS ADVERTISED but the problems noted are too significant to accept just to get the extra features.
[Android Auto General] bjevers:
Media control bug happens to me wired in 2 completely different vehicles so it has to be an Android Auto bug in general. The way I quickly fix that is to cycle the head unit power off and on quick.
[Android Auto General] antman68:
I've never had the problem with a wired connection and I never have the problem in passthrough. I can usually fix it by changing the headunit to Phone and back to AA, but it's not always succesful. The loss of Assistant is a bigger issue because it cannot be easily fixed and it means that you can no longer receive any information from the Assistant, can't listen to or send texts, etc., which are some of the main reasons for having AA in the first place.