AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
How 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.
Requested and received a replacement device but this is also showing the same behaviour.
Regardless of passthrough mode/dongle mode/resetting up/clearing caches ........
Ticket is open for issue https://cpeb.freshdesk.com/support/tickets/28709 but i thought I would also ask here.
Phone is a Motorola G200 running android 12 head unit is a SEAT (VW MIB) PN 7N035200C (H/W H31 S/W 0363)
Happy to extract logs and assist with debug as I really want this working. Just need some instructions.
Thanks
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.
Requested and received a replacement device but this is also showing the same behaviour.
Regardless of passthrough mode/dongle mode/resetting up/clearing caches ........
Ticket is open for issue https://cpeb.freshdesk.com/support/tickets/28709 but i thought I would also ask here.
Phone is a Motorola G200 running android 12 head unit is a SEAT (VW MIB) PN 7N035200C (H/W H31 S/W 0363)
Happy to extract logs and assist with debug as I really want this working. Just need some instructions.
Thanks
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.
Last edited:
Just to report back, updating to 2.0.1 did not resolve issue. Enabling passthrough mode resolved the issue.
@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-86606909
I've been getting more frequent disconnections even while stopped at a light, even after latest firmware and trying a bunch of different wifi channels. What I've noticed though is that it's been getting warmer in the past month or so with the more frequent disconnections.
Has anyone faced heat issues? I keep it away from the sun and it is only about 27C here so it isn't extreme climate by any means.
I also read earlier in the thread that someone claimed to have fixed their issues with a v2, but I don't know if that is just a one time coincidence.
Has anyone faced heat issues? I keep it away from the sun and it is only about 27C here so it isn't extreme climate by any means.
I also read earlier in the thread that someone claimed to have fixed their issues with a v2, but I don't know if that is just a one time coincidence.
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.
I have had an issue since I received the unit but I've delt with it "Device Not Supported" it will launch Android Auto sometimes. Once it throws this error a couple times I am unable to even connect with direct USB to my phone. I have to pull fuses to reset my radio or wait until the next day. I've tried all the different modes and different USB cables. I've updated from 18 to 2.0.0 to 2.0.1 with the same issue. Definitely frustrated and I've sent tickets to support. I am starting to wonder if it's a heat issue as it seems worse the longer I run it or the hotter the day. Can only uninstall and factory reset so many times. Car is 18 Challenger with 8.4 Nav. Phone is pixel 3a xl.
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
Пожалуйста, помогите с этой проблемой. Я устал дергать за шнур после каждого звонка. Может быть, я должен сделать отчет об ошибке? Устройство № 4Hi5S8zx
Last edited by a moderator:
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.
A'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.
If you still have problems, post info about what stage it's failing and the error you're getting.
Hello,
Im the guy of the Vodafone SmartX9 (that didn´t work on the AAWireless).
Since then i updated to a Realme 8, and after managed to update the AAWireless to 2.0.0 and then 2.0.1 i can say with that phone i didn´t have any problem at all.
But the phone stopped working, battery faulty it seems. And i was forced to send it back.
Yesterday i got a brand new Samsung Galaxy A52s, and i was worried about some problems reported by some collegues of forum here.
But im happy to report that i have tested and AAWireless is running like a champ.
Here how i did it...
After updating the phone to the latests versions of software and apps, i went to Android Auto App or option inside Android 12.
And activated the developer menu (go to version number and press until it says so...).
then i went there and activate the Wireless Projection.
Went back and checked if Android Auto Wireless was selected (if not, select it).
I then exited and went to the car, and plugged the phone to usb with cable, it detected android auto and i configure all the options on the phone and on the infotaiment.
I let AA runn and open some apps inside the infotaiment (waze, phone, Maps), then i unplug the phone.
I then plug the AAWireless unit and start the AAW App on the phone.
I follow the steps but on my case the app didin´t detected the unit on BT.
I went manually to Bluetooth and selected the unit.
After connected, i went back to the app and finished the procedure.
After going to the main menu i waited 20 secs and the Android Auto app started runing as expected.
I didn´t alter any option on the options menu.
And the AAW is using 5G connection for better speed and stability.
I since then, have disconnected BT on my phone, reconected, removed the unit, inserted the unit back.
And so far, flawless function... everything works, audio works, music works, steering controls works, phone works (using Mic and Speakers of the car), Waze works.
No disconnect so far...
Im using now:
AAWireless on 2.0.1
Samsung Galaxy A52s 5G (Running Android 12 and latest versions)
Citroen C5 Aircross 1.2 from 2019 with latest version of NAC infotaiment.
I hope i can help with my report.
Best Regards,
LPC
Im the guy of the Vodafone SmartX9 (that didn´t work on the AAWireless).
Since then i updated to a Realme 8, and after managed to update the AAWireless to 2.0.0 and then 2.0.1 i can say with that phone i didn´t have any problem at all.
But the phone stopped working, battery faulty it seems. And i was forced to send it back.
Yesterday i got a brand new Samsung Galaxy A52s, and i was worried about some problems reported by some collegues of forum here.
But im happy to report that i have tested and AAWireless is running like a champ.
Here how i did it...
After updating the phone to the latests versions of software and apps, i went to Android Auto App or option inside Android 12.
And activated the developer menu (go to version number and press until it says so...).
then i went there and activate the Wireless Projection.
Went back and checked if Android Auto Wireless was selected (if not, select it).
I then exited and went to the car, and plugged the phone to usb with cable, it detected android auto and i configure all the options on the phone and on the infotaiment.
I let AA runn and open some apps inside the infotaiment (waze, phone, Maps), then i unplug the phone.
I then plug the AAWireless unit and start the AAW App on the phone.
I follow the steps but on my case the app didin´t detected the unit on BT.
I went manually to Bluetooth and selected the unit.
After connected, i went back to the app and finished the procedure.
After going to the main menu i waited 20 secs and the Android Auto app started runing as expected.
I didn´t alter any option on the options menu.
And the AAW is using 5G connection for better speed and stability.
I since then, have disconnected BT on my phone, reconected, removed the unit, inserted the unit back.
And so far, flawless function... everything works, audio works, music works, steering controls works, phone works (using Mic and Speakers of the car), Waze works.
No disconnect so far...
Im using now:
AAWireless on 2.0.1
Samsung Galaxy A52s 5G (Running Android 12 and latest versions)
Citroen C5 Aircross 1.2 from 2019 with latest version of NAC infotaiment.
I hope i can help with my report.
Best Regards,
LPC
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.
Similar threads
Top Liked Posts
-
5
In dev app yes. Production app no. We'll start rollout of 2.1.0 this evening.1AAWireless will not start up, car shows "Searching for phone"
This is a bug in Android Auto, we are looking...support.aawireless.io
2.1.0 will also have a firmware based workaround/hack coming up.
This is not a problem in AAWireless, but in Android Auto/HU. MA1 has the same issue, confirmed with @psmedley .
Kinda odd AAGateway works, have to check what's different over there. Did you ever use The AAGateway solution before on this car?
EDIT: Actually think I might know why AAGateway works. Do you by any chance have the "Non ROOT mode" option enabled in AAGateway? When "Non ROOT mode" is enabled, AAGateway does the same "hack" as AAWireless does with firmware 2.1.0. -
19
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.10
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.
Then you have all the narcissistic Karens with zero patience that say whatever they think will get your attention so they can jump the queue. Even when you (quite rightly) post that firmware will now be staggered with no release announcement, you have an immediate request from someone with “faulty” units asking you to announce when the release will start!?!
It must be incredibly frustrating and every rational user will understand. Even if you decide against stepping back permanently, please take a lengthy break.8I wanted to add my thanks to @Snirpo and his team. They've been working tirelessly to get everything working for everyone. When you think about all of the combinations of phones, Android versions (including non-standard ROMs), Android Auto updates, head units (not just an auto manufacturer but the changes those manufacturers make to their own systems year after year, and updates) plus aftermarket systems - it's staggering how many different things have to all "just work."
I know forums are often the place people come to report their problems and ask for help, and having been on the receiving side of it myself it can sometimes be overwhelming and disheartening.
So kudos to the AAW team for everything they've done!8 -
41This 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.19
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.16I 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!15We 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.14
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!
