Bug report sent, device is: 0NaI4e4g
Bug report sent, device is: 0NaI4e4g
Ok quite surprising.... Apparently the stale connection detection is triggering for your HU... That means the HU isn't sending any messages for 10+ seconds. Thats normally not really possible at all because the HU should respond to ping messages from the phone. Can you maybe do a run with debug logging on (until it crashes)?
Just to report back, updating to 2.0.1 did not resolve issue. Enabling passthrough mode resolved the issue.I also have (or had) this issue (Samsung Galaxy S20 5G with Android 12). As a workaround I had to press the mute button on the car system two times after accepting a call and then it works correctly for the duration of the call. Also I have had various other sound issues (no sound/no microphone).
I have upgraded to 2.0.1 yesterday, I have yet to try making a phone call but the other sound issues didn't occur again yet.
@rodmoore In a previous post I shared my experiences, also about retrieving the WiFi password: https://forum.xda-developers.com/t/...on-and-support.4247677/page-126#post-86606909How can i get the Wifi password to enable extracion of logs?
I am on my second device after the first repeatedly rebooted, sometime after a few seconds, sometimes it would stay up for 20-30 seconds max, show the map and then reboot.
Well, I updated to the developmental firmware you enabled, but I still can't disable passthrough mode. It just won't connect w/o passthrough (though it did when I first got it, I ASSUME it's the HU update that broke it, but not sure). So I drove home with passthrough on (not sure where debug logging needs to be enabled, but maybe it doesn't matter if I can't disable passthrough?). I did have a disconnect on the way home, light seemed to be blinking green. Then it eventually turns blue and reconnects.Ok quite surprising.... Apparently the stale connection detection is triggering for your HU... That means the HU isn't sending any messages for 10+ seconds. Thats normally not really possible at all because the HU should respond to ping messages from the phone. Can you maybe do a run with debug logging on (until it crashes)?
EDIT: Passthrough mode is enabled of course so I cannot see any messages going through. I'll enable the latest develop firmware for you which should make non-passthrough mode also work again.
MOD Edit: Please help with this issue. I'm tired of pulling the cord after every call. Maybe I should file a bug report? Device #4Hi5S8zxПривет, ребята. Не могу решить последнюю задачу. После телефонного звонка звук больше не воспроизводится устройством. Требуется перезагрузка.
AAБеспроводная версия. 2.0, Ауди А6 С7, ОнеПлюс 7Про
How can we help if we can't read your text? What is it? Russia, Cyrillic? But in the end it does not matter - this is an english spoken forum.Пожалуйста, помогите с этой проблемой. Я устал дергать за шнур после каждого звонка. Может быть, я должен сделать отчет об ошибке? Устройство № 4Hi5S8zx
A'm sorry.How can we help if we can't read your text? What is it? Russia, Cyrillic? But in the end it does not matter - this is an english spoken forum.
Update to 2.0.1A'm sorry.
I can't solve the last problem. After a phone call, the sound can no longer be played by the device. Reboot required.
AAWireless ver. 2.0, Audi A6 C7, OnePlus 7Pro
Please help with this problem. I'm tired of pulling the cord after every call. Maybe I should make a bug report? Device #4Hi5S8zx
Disable your VPN, if you have one. If you're using mobile data, try downloading the update separately over wifi then connect back up to AAWirelss and perform the install. If the download fails on wifi, then switch to mobile data.
FYI, I had the S20+, it's doesn't do the disconnecting thing like those other phones, and I had mobile data on and wifi for my kids devices.this might be the reason why my Galaxy S20+ is disconnecting the WiFi.. but i NEED to have Mobile Data ON while driving
but u dont drive an Audi A6 4GFYI, I had the S20+, it's doesn't do the disconnecting thing like those other phones, and I had mobile data on and wifi for my kids devices.
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)
It's working againAt this moment we have shut down all OTA updates unfortunately. The load on our backend is too high. Too long without maintenance because of other priorities. We have to optimize some stuff to make it work again.
I remember a post from a guy with the classic “I've been in the industry for years” claim. He said that because he had a weekly internal briefing at his workplace, you should be doing the same for us here. If you give an inch, they want a mile.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 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)
Yes, I'll write a full changelog next week from 1.0.0 to 1.5.0 and put it on GitHub + add a link in the app.Hello. What's new in 1.5?
A full changelog for each release would really be appreciated
Thanks for all the hard work!