AAWireless - General discussion and support

Search This thread

alda.cerny

Senior Member
Dec 29, 2014
147
69
Prerov
Google Pixel 5
Hi, I have such a specific problem with AAWireless

I am using a Skoda Octavia 3 with Columbus unit (MIB2.5), I have the latest available firmware MHI2_ER_SKG13_P4526 in the unit
I am using a Pixel 5 mobile phone with Android 13
AAwireless firmware version is 2.1, the last app version I tried is 3.14.0, today I got an update to 3.15.0

If I connect to AAWireless for the first time (when AAWireless is first connected by cable to the unit in the car) everything works as it should, if I connect for the second/third time (sometimes it works for a longer time) Google Assistant stops working, when I want to start Google Assistant, it is deaf (it does not answer my questions), this is connected with another problem, that the sounds in the navigation do not work in this case, the music I play from the memory card in the car / from the radio seems to be muted, but the navigation instruction is not heard

I did a reset of AAWireless to eliminate possible problems
I have dongle mode on
I tried VAG crash fix on/off

Does anyone have any idea where the problem might be? Thanks for the help

I didn't find the solution to my problem here in the thread, if it is here, I apologize for spamming
 

Magicneng

New member
Feb 1, 2023
1
3
The constant AAWireless disconnection issues with Xiaomi, Redmi or Poco smartphones are due to a problem with the MIUI 13 or MIUI 14 ROM.
I had this problem and after downgrading from MIUI 13 to MIUI 12.5.8 on my POCO X3 NFC everything works fine and never disconnects even if I'm in underground parking or basement with no coverage.
The only thing that in Toyota models with MY22 navigator and connected services, does not restart AAWireless again in case of connection loss, as it happened before with MIUI 13.
Now everything works fine with MIUI 12.5.8.
Sorry for my english, it's spanish translated by google translator.
 

Dangze

Senior Member
Dec 20, 2010
113
47
Hello,
few days ago, my phone received (automaticaly, no AA version change) the Coolwalk option (split screen display). Since then, I have discovered a strange thing :
- if I connect my phone (Galaxy A52 5G) to my car (Citroën C5AC, with NAC head unit) with a cable, the Map picture is displayed on the left half of the screen, and the radio station is displayed on the right part, as explained on the various descriptions of Coolwalk,
- but if I connect my phone through AAW dongle, the Map picture is displayed on the half above part of the screen, and the radio on the below part !
Is there a way to modify this (I prefer the basic display), for example using the DPI setting ? If yes, wich value should I try ?...
For information, I received today the last version (8.7) of AA, but no change !
Thanks for any help or advise !!!
 

Andres.Navas

Senior Member
Hello,
few days ago, my phone received (automaticaly, no AA version change) the Coolwalk option (split screen display). Since then, I have discovered a strange thing :
- if I connect my phone (Galaxy A52 5G) to my car (Citroën C5AC, with NAC head unit) with a cable, the Map picture is displayed on the left half of the screen, and the radio station is displayed on the right part, as explained on the various descriptions of Coolwalk,
- but if I connect my phone through AAW dongle, the Map picture is displayed on the half above part of the screen, and the radio on the below part !
Is there a way to modify this (I prefer the basic display), for example using the DPI setting ? If yes, wich value should I try ?...
For information, I received today the last version (8.7) of AA, but no change !
Thanks for any help or advise !!!
Change the DPI. I have the same car, and I have it configured to 104, and it shows the split display left/right as you want it.
 

knighthw2

Member
Feb 7, 2023
9
0
i got aaw recently
I have a 2018 Cruze with mylink2 and the initial setup went smoothly, and the aaw connects quickly when I get in the car, but on spotify or amazon music, I've been having random stuttering/lag issues.
I already disabled location accuracy, battery optimization, I have the latest version and firmware....does anyone else experience this?
 

SOFO888

Senior Member
Jan 28, 2013
370
69
I have a Chevrolet 2017 with Mylink and no issues at all. Works even better than on our 2018 Renault.
 

italodance

Senior Member
Nov 17, 2008
86
9
@Snirpo can you update AAWireless app with features like making font size bigger? I use dpi for changing new Coolwalk designs and select my preferable style but font is small, it is readable, I just thought if you can add this option to your app.
 

Dangze

Senior Member
Dec 20, 2010
113
47
Change the DPI. I have the same car, and I have it configured to 104, and it shows the split display left/right as you want it.
Hi Andres, i have tried 104 DPI, but it does not change the display for me ! However, I tried other values, for example 103, which change the display, but not completely as I would like : the audio source is displayed on the right part of the screen, but the apps buttons are shown on the left of the screen and not below the screen, as Coolwalk do. Also, these buttons are too small, the time is hardly readable !
I hope @Snirpo (many thanks to him) will read these messages and could find a solution so that the display of Coolwalk through AAW is exactly the same as the display of Coolwalk through USB cable...
 

Andres.Navas

Senior Member
Hi Andres, i have tried 104 DPI, but it does not change the display for me ! However, I tried other values, for example 103, which change the display, but not completely as I would like : the audio source is displayed on the right part of the screen, but the apps buttons are shown on the left of the screen and not below the screen, as Coolwalk do. Also, these buttons are too small, the time is hardly readable !
I hope @Snirpo (many thanks to him) will read these messages and could find a solution so that the display of Coolwalk through AAW is exactly the same as the display of Coolwalk through USB cable...
TBH, I haven't tried Coolwalk with pure USB, but to me the view I got with the DPI set at that value is good to me... You can play with the values, I do remember that to have the "original" you must set it to "0." Did you try it? - Just play a round with different values...
 

Dangze

Senior Member
Dec 20, 2010
113
47
DPI at "0" is what I don't want (and on my car identical to DPI 104): the map is displayed at the above part of the screen, and the audio programm is displayed below, the apps button on the left of the screen with too small characters...
I will continue to play with various values and I will take some pictures of the various screens !
For your information, you can also try with USB connection...
 

Andres.Navas

Senior Member
DPI at "0" is what I don't want (and on my car identical to DPI 104): the map is displayed at the above part of the screen, and the audio programm is displayed below, the apps button on the left of the screen with too small characters...
I will continue to play with various values and I will take some pictures of the various screens !
For your information, you can also try with USB connection...
Here my view... For me is good enough, the hour and left bar are readable... I do really enjoy this interface!
IMG_20230209_184637.jpg
 
Last edited:

Snirpo

Senior Member
Jan 23, 2007
613
679
Hi Andres, i have tried 104 DPI, but it does not change the display for me ! However, I tried other values, for example 103, which change the display, but not completely as I would like : the audio source is displayed on the right part of the screen, but the apps buttons are shown on the left of the screen and not below the screen, as Coolwalk do. Also, these buttons are too small, the time is hardly readable !
I hope @Snirpo (many thanks to him) will read these messages and could find a solution so that the display of Coolwalk through AAW is exactly the same as the display of Coolwalk through USB cable...
There shouldn't be any difference. Can you try to enable passthrough mode in AAW settings? If it's still not the same in passthrough mode then it's AA itself which somehow makes the dpi different wired vs wireless. If it's fine in passthrough mode, but not in non-passthrough mode, it could be a bug in the firmware.
 

Dangze

Senior Member
Dec 20, 2010
113
47
@Snirpo
I didn't make the test yet, but I remember that 2 days ago I drove my wife's new car (Kia Picanto last model), and my phone has wiressly connected to Android Auto, and the display was exactly the same than wired AA ! That tends to prove that there is no different dpi setting in AA itself...
 

chrisstavrou

Inactive Recognized Developer
Mar 4, 2005
476
28
Nicosia
Hi all, I have been using AAwireless without any problem from the device itself for which am very happy.

However, my car is a Volvo XC40 running the Sensus Headunit (not the Google Automotive one) which has a portrait screen. The current implementation of AA in this unit results in displaying AA in the bottom half of the screen in a kind of widescreen mode making AA (wired or wireless) disappointing to use. Build in navigation app, can switch to full screen which is nice but not AA.

I have also received Coolwalk on my S21 but it still displayed at the bottom 1/2 of the screen in widescreen.

I am wondering if it is possible to make AAwireless to request a portrait orientation/resolution from the headunit to test if the headunit behaves differently (or any other idea that might trigger the use of the whole screen).

Thanks
Chris
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I tried everything you said, clearing caches, storage, unpairing, uninstalling, debug, etc. I tried it all a million ways for two hours in my car. This device was fine a week ago when we went from a Samsung Note 10+ to the S23 Ultra on the same Nissan Rogue. I couldn't even do the debug as when I would try it would say could not get debugging status is it powered on? Then sometimes debug started (i think) but when I would go back it would say unable to get debug log or similar. And my device would always disconnect and reconnect from Bluetooth like crazy.

    I tried using a phone Sim tool to hard reset the device. I used the app to do the same thing. Using setup it would always look like it was going to work till the end where it would timeout "Looking for Android Auto" in the notification garage door. Then it would send me through troubleshooting. During troubleshooting my device would flash green forever and then sometimes it would stay solid red. I have no clue what is happening here as it was fine a week ago? Please help me out here. We backed you when you were still working on the devices but this is a little much. I thank you for your time and effort though. Let's try round two please.

    Sincerely,

    5th
    I'm trying to help. But at some point I have honestly no idea what to do or try.
    Every time Samsung releases a new flagship phone, Android Auto starts breaking and our support ticket count explodes. It happened with the S20, 21, 22, Fold 3 and now also the S23 and Fold 4. And this "cheap" dongle always gets the blame, because it cannot be the 1000+ dollar phone.
    Anyway, maybe the dongle is broken and it's pure coincidence. So let's try to replace it. Please contact [email protected]. You can mention this post and support will replace it for you.
    2
    In my case, I think it was a coincidental carrier/network update that's helped me. I still disconnect when manually disabling data etc, but I've had 2 dropouts over the past few weeks when I would normally have several every day.

    The only report that MIUI 14/A13 fixes the Xiaomi issue is from a Mi 11 Lite 4G (Global) user on this forum and there was no video. It could also be the AA beta they are using.
    I recorded a special video for you, I updated AA this morning as well and all fine:
    1
    @Snirpo:
    One question besides...did you guys find a solution to connect a second phone by bluetooth to the head unit with AAWireless?

    See this thread here:
    What they are talking about in this topic indeed possible by enabling "disable media sink", it will remove media audio channel from AA. So the phone will route the audio through bluetooth, when connected.
    1
    it does not work for me (v.3.18)
    Hmm, for your device the latest certificate is installed on the device. Is there any possiblity to reset / clear devices on the head unit side? Otherwise please try to clear cache and data of Android Auto. Another possibility is to try to enable to "GM fix". I'm pretty sure actually it needs the GM fix.
    1
    BIngo! It works with GM fix!
    Yeah I remembered from testing in a Citroen C3 this was nessecarry. Without getting into too much technical detail, the main problem is a wired connection vs wireless in non-passthrough mode is detected as a different "car" by AA. And this Citroen head unit (+ GM and some other brands) need a wired connection first to get through the initial AA setup. In passthrough mode wired vs wireless is detected as the same car, so it's not an issue. The "GM fix" hacks into the AA protocol to bypass this weirdness.

    We should probably rename the GM fix.
  • 42
    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.