brackenhill_mob
Senior Member
You're right I did mean AA - my badI guess you mean force close Android Auto? Force closing the AAWireless companion app won't do much (unless you're using start/stop).
You're right I did mean AA - my badI guess you mean force close Android Auto? Force closing the AAWireless companion app won't do much (unless you're using start/stop).
Sadly i'm not able to install it - "Update failed". Any suggestions?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![]()
I had already asked to include me, if possible, thank you.I am also interested in the "audio-stutter-fix" firmware.
I have a Samsung Galaxy S21 and GM Tracker 2021 and at times it stutters a lot.
My device ID is AAWf7667875
Thank you!
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![]()
Update received. I will test and give feedback.I had already asked to include me, if possible, thank you.
AAWf7667875
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.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.
As a follow up to the thread below, do you have a Network Acceleration section in settings with a "Switch between networks" option?
Hi @SnirpoOk, 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.
Don’t know why you are acting like this after seeing a proof, regarding switch between networks, yes it is off here.@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.
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.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.
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.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.
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.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?
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.@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?
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.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?
DoneAfter 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
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.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.
@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
3.0 will be available from next week for everyone. The firmware itself isn't beta btw. Only the CarPlay functionality is.@Snirpo can u try the beta too ?? app version 3.29.0 firm.2.2.0 gen 2, AAW87cf4226, car:merc gla my2022
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.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)