AAWireless - General discussion and support

Search This thread

b0thunt3r

Member
May 30, 2023
5
0
Yeah, it will be a bit delayed. Saving the settings without changing anything should speed it up. Please report back wether it helped or not :)
Sadly i'm not able to install it - "Update failed". Any suggestions?

Edit: After restoring factory settings it worked, i'll test the next days.
 
Last edited:

milanxx

Member
May 5, 2022
35
1
Finally, Google has modified Android Auto. Wireless is already native. The option is gone and there is no need to have development mode enabled.
Tried and it works
Galaxy Note 20Ultra 5G
AA 9.4.631624
A13 UI5.1
AAW4XOTOtVy sw2.1.0
App 3.23.0
 

Flame Red

Senior Member
Yeah, it will be a bit delayed. Saving the settings without changing anything should speed it up. Please report back wether it helped or not :)

Sorry to ask again, but the above did not help my AAW unit load any firmware. Says up-to-date.

I am also having the stutter issue and interested in the "audio-stutter-fix" firmware.

Id: hf5gcQJG

Thank you!
 

Snirpo

Senior Member
Jan 23, 2007
756
739
Update received. I will test and give feedback.

*** Update: on a trip of about 1 hour, not a single audio glitch. Thank you very much.
Ok, good to know. This is a total hack though, hacking into the AA protocol. I guess we can include it as an option in firmware 3.0... these kinds of issues come and go though with Google tinkering in AA.
 

SOFO888

Senior Member
Jan 28, 2013
398
74
I want to use the AAWireless' Wifi as access point for communication with a camera. The idea is to use the same Wifi like my phone to be able to connect to the camera while using AAWireless.

Unfortunately I was not successful until now.

I tried different IP cameras. Unfortunately all needed internet. Therefore I'm looking for a 5Ghz outdoor offline IP camera. Does anyone have any experience with this?

The second question is about giving fixed IPs to the devices within AAWireless' Wifi. Does the AAWireless device support such a function?

Thanks.
 

festor

Senior Member
Jun 4, 2013
178
119

knighthw2

Member
Feb 7, 2023
11
0
Ok, good to know. This is a total hack though, hacking into the AA protocol. I guess we can include it as an option in firmware 3.0... these kinds of issues come and go though with Google tinkering in AA.
Hi @Snirpo
I also have that firmware, and it has been working very well for about 3 months. I would suggest exactly that, making it available as an option in a future firmware update because it works very well.
 

festor

Senior Member
Jun 4, 2013
178
119
@italodance the first time you didn't reply to the question, I thought you just missed my post, but I noticed you actually read it this time.

You seem to be the only one here that updating to stock MIUI 14 fixed the longstanding Xiaomi disconnection issue. Prior to this, you said enabling AA Developer Options fixed your disconnections. Then you more recently posted that setting Start Android Auto Automatically to "Always" fixes disconnections. Apologies about previously questioning your info, but maybe you can understand why?

I then notice you like to troll people with "buy xiaomi" when they post about issues with other brands so it makes me wonder if this whole thing is another troll?

If it's just some sort of personal grudge then maybe you can swallow that pride and think of the greater good? Instead of incorrectly posting "It has been fixed in n miui 14" you might actually be able to help others running stock MIUI 14 who still get the issue.
 

italodance

Senior Member
Nov 17, 2008
103
10
@italodance the first time you didn't reply to the question, I thought you just missed my post, but I noticed you actually read it this time.

You seem to be the only one here that updating to stock MIUI 14 fixed the longstanding Xiaomi disconnection issue. Prior to this, you said enabling AA Developer Options fixed your disconnections. Then you more recently posted that setting Start Android Auto Automatically to "Always" fixes disconnections. Apologies about previously questioning your info, but maybe you can understand why?

I then notice you like to troll people with "buy xiaomi" when they post about issues with other brands so it makes me wonder if this whole thing is another troll?

If it's just some sort of personal grudge then maybe you can swallow that pride and think of the greater good? Instead of incorrectly posting "It has been fixed in n miui 14" you might actually be able to help others running stock MIUI 14 who still get the issue.
Don’t know why you are acting like this after seeing a proof, regarding switch between networks, yes it is off here.
refer to Automatically to Always, it is for connecting better whenever you start the car so it fixes the problems like no connection to AAWireless or delay in connecting. it fixed issues between car and aaw.
I‘m out of beta, by the way and disabled AA Developer, too. I guess those never have been a solution. Maybe worked on some beta versions, not sure.

if I didn’t reply you cause I did not have time to. It doesn’t mean I don’t care.

but if you think I’m a troller, then I will be silence here.

if you judge me for ignoring you, then check out previous pages to find out how many times @Snirpo ignored me.

I just wanted to share my various experiences with you, all. Nothing more than that.

At the end, I don’t care what you think about me.
 

Flame Red

Senior Member
Hi @Snirpo

Wanted to report on the Stutter firmware after about 7 hours of driving.

I experienced several AAW random reboots. Some were just a few minutes apart while others where hours apart. No common cause I could notice

The Stutter still occurs but is a lot less frequent Much improved but not totally gone.

I will continue to test and post anything else I notice.

Thank you!

Galaxy Fold 4 on Volvo XC90
 

festor

Senior Member
Jun 4, 2013
178
119
Don’t know why you are acting like this after seeing a proof, regarding switch between networks, yes it is off here.
refer to Automatically to Always, it is for connecting better whenever you start the car so it fixes the problems like no connection to AAWireless or delay in connecting. it fixed issues between car and aaw.
I‘m out of beta, by the way and disabled AA Developer, too. I guess those never have been a solution. Maybe worked on some beta versions, not sure.

if I didn’t reply you cause I did not have time to. It doesn’t mean I don’t care.

but if you think I’m a troller, then I will be silence here.

if you judge me for ignoring you, then check out previous pages to find out how many times @Snirpo ignored me.

I just wanted to share my various experiences with you, all. Nothing more than that.

At the end, I don’t care what you think about me.
I didn't mention your posts where you harassed @Snirpo as a courtesy to you. You repeatedly asked him to "fix" and "work on" the Xiaomi issue even though it was explained it's not possible. You also repeatedly asked him to fix video lag, an option specifically blocked by Google which would risk the AAWireless app position in the Play Store.

You have made your motives very clear, no further explanation needed.
 

skanadian

Senior Member
Feb 3, 2009
160
61
Ontario
@snipro I wouldn't mind going back to 2.0.2 or trying 3.x. My Kia Stinger was perfect on 2.0.2 when you first fixed the Kia bug, but it's been glitchy since updating to 2.1.x and beyond. I'd prefer 2.0.2 but happy to beta test 3.x. DeviceID: pl2kf12W

Symptoms:
- AA "freezes" every 5-60mins and the audio cuts out for a couple seconds
- The audio delay increases each time, evident by Waze turning down the music to say something. It mostly syncs up before glitches, but gets farther and farther out of sync with each audio glitch.
- May disconnect completely but is way less frequent than the audio glitches

Is the firmware available for download anymore? I vaguely remember instructions on how to connect to the 10.x IP to reload it.
 

Top Liked Posts

  • 1
    I've been trying to find a new or easier way to switch between two devices that use the same dongle in a shared vehicle. I found a two-year-old YouTube video that demonstrates disabling Wi-Fi and Bluetooth on the last paired phone so that the next phone will go into the connection queue, or to keep the other phone away. But after reading about "dongle mode", it seems that the dongle looks at the connected device that the head unit connects to and then launches Android Auto wireless on that device that vehicle connected to. Is this correct?

    Is there maybe a post that someone can link me to, or can you provide me with the most reliable method to switch between connected/paired phones on one dongle without having to disable Wi-Fi/Bluetooth? I tried using the thread searcher for keywords and found a lot of posts that briefly touch on the topic, but nothing definitive. I want the process to be simple for my wife when she gets into the vehicle and i'm nearby.
    The easiest way, with dongle mode enabled (so native mode, how Google designed it), is to turn on airplane mode on the phone you want to disconnect to make sure both Bluetooth and Wi-Fi are off. Then the car should connect it's handsfree to the other phone, and AAWireless will also connect to the other phone. If both are connected, AA will start up. So no, by default, natively, there is no proper way to switch between phones.

    Another way is to disable dongle mode and re-pair AAWireless. Then AAWireless works in a emulated wireless HU mode. In this mode it doesn't matter to which phone the handsfree of the car is connected, you can switch phones with either the home screen of the companion app or the widget. However, non-dongle mode uses a dummy handsfree profile to make AA think AAW is a real HU. This can cause issues with handsfree audio routing during phone calls on some (dumb) phones. This is also why this mode is not default.

    In the AA code there is actually a setting to make the "needs to be connected to handsfree of car" optional. I really really wish they made this available for the end user. It would make our lives alot easier and solves alot of these "blinking greens". Half of our support tickets is about blinking greens, and there's not much we can do about it apart from suggesting people to disable dongle mode, which brings other issues like mentioned above. It just sucks a bit...
  • 3
    HI, I have old AA wirelles version and using it on Mercedes W213. All is nice, except that Android auto does not use full screen, as mercedes did not allow it. But Carplay can use full screen. Tried buying dongle with Android Auto via Carplay, and it used full screen, but quality was low. So returned it.
    If I buy gen 2 AA wireless dongle, can I use Android Auto via Carplay full screen and will it have same quality as non full screen Android Auto? When this option should move from beta to stable?
    It works, and is quite smooth on the develop firmware atm. However, it's still beta and will probably stay like that for a few weeks / months. Right now the biggest thing missing is support for phonecalls. On some cars (Subaru for example) bluetooth handsfree stays enabled when using CarPlay, then phonecalls will work right now already. Other cars shut down Bluetooth handsfree when using CarPlay. Android Auto by default uses bluetooth for phone calls. So we need to proxy bluetooth handsfree to CarPlay. This is quite some work and not quite trivial, because it's realtime, so you don't want to introduce too much delay.
    3
    @Snirpo since 3.0.0 was pulled, do you expect to release 3.0.X next or expedite the 3.1.0 release?
    Will the 3.1 release include video hardware acceleration?
    3.0 is only pulled for the old devices (cs307). I'm waiting for one of these affected devices to arrive, so I can figure out what's happening. 3.1 will include video hardware acceleration for AA over CP.
    2
    How to check my device version (AAW7c4dd2f9), generation 1 or generation 2? I'd like to try the Carplay function with AA wireless if my device is generation 2.
    if not, any plan to make the generation 1 compatible with Carplay?
    That's an old one. There is a slight possibility possibly we can make CarPlay work on the gen1 devices, but I wouldn't give it too much hope.
    @Snirpo are you able to fix this for me?
    After reading through a couple of pages, I also have the stutter problem that toddfla1018 and many other users are encountering. Any chance I would give this audio stutter fix a try @Snirpo ?

    My device is AAWb3818cc9

    Thanks
    Done
    2
    As im having the same issues with my Toyota Rav4 I'm assuming there is a compatibility issue with all new Toyota models with the MY21MM units ( wireless airplay / wired AA ) and AAWireless.. it seems like the audio unit can't connect to Bluetooth if it was selected to run android auto and visa versa which causes handshake problems.. friend of mine works at Toyota and they tried the unit on the current corolla, rav4 and corolla cross and had the same issue.. but worked perfect with the older style Audio units that do NOT have the wireless applecarplay...if you need me to assist with a beta firmware to try resolve please let me know as it seems this issue will be affecting all Toyota owners moving forward.
    Yeah, it's becoming a problem indeed. Not only for us, but all native AA dongles have the same issue. It's especially annoying in Japan where Toyota is obviously huge. It seems to be a recent issue though, seems to be related to a HU firmware update. Also the Denso HU's seem to act differently than Panasonic. I kinda need a HU on my desk to resolve this issue though. If we can even resolve it... Can you somehow arrange one through your friend? We'd obviously pay for it.

    The problem seems to be twofold.
    - One problem is these headunits having some weird switch to either use AA OR handsfree. I have no clue why, it's a super odd design decision. This will break dongle mode, because AA expect the handsfree of the car to be connected, otherwise it will not start up the AA session. So first thing to try is to disable dongle mode, clear data of AA and re-pair AAW.
    - for Denso HU's, once it does start up AA (solid blue LED), it hangs and after a while the session will timeout. When you press the "connect" button on the HU in time, it will start up AA.
    - for Panasonic HU's what seems to help is to clear all phones on the HU side. Plug in AAW and let AA start up. Then do not connect the phone wired, because it will screw up the wireless connection. If you connect the phone wired, you have to clear all phones on the car again to make AAW work again.

    Please join us in Slack for easier comms. https://join.slack.com/t/aawireless/shared_invite/zt-22rn00y78-rGCaGgop26o1b5Jjkc4DoQ
    2
    @Snirpo Could I be part of the 3.0.0 beta? I would love to try out Carplay :)

    • App Version: 3.29.0
    • Firmware: 2.2.0
    • Hardware revision: Gen2
    • Serial number: AAW5e3e88a5
    • Car: Peugot E-208 50kWh

    @Snirpo can u try the beta too ?? app version 3.29.0 firm.2.2.0 gen 2, AAW87cf4226, car:merc gla my2022
    3.0 will be available from next week for everyone. The firmware itself isn't beta btw. Only the CarPlay functionality is.
  • 43
    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.
    20
    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.
    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!
    15
    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.
    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.