AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
Hi Snirpo,
thanks for the quick answer. I needed some time for the test, but finally made another extensive test. First with the settings I had (+passtrough mode), later with different modifications.
The reason it took long was the first try. I changed to passtrough and I believe that time I had no (or maybe 1) disconnetcion.
Later there was one more case with only 1 disconnection.
But the complete picture has not changed.
I usually drive 2x 40-50 min per day on the motorway. There were in avg 5-8 disconnections.
If I go to the city, the frequency of disconnections are even getting higher.
How could I test weather it is the HU or the dongle?
In the weekend I might have the chance to test it in another car for 2-3 hours.
Dev is the new one, the other will not be updated anymore. Firebase app is a bit buggy, you first need to accept the invite, should be in your mailbox.
If the same happens in another car, I'd say send an a support request at [email protected] for a replacement.
I think the problem is the car turning on the USB port when you walk to the car. Device (AA) will start up too soon and will time out because there's no reaction from the HU yet.
In normal (non-passthrough) mode we keep the wireless side alive by pinging to the phone. So AA will not time out.
This has changed in 2.1.0, we don't ping anymore in both normal and passthrough mode. If this has negative side effects, please tell me
However... dongle mode should also fix this, because it makes AA wait for the handsfree connection of the car to the phone.
Oh me too if i can AAWireless-SUsVhcKV
Also I have one behaviour now, for exemple I like switch between poweramp, deezer and also smart audiobook, and I use waze as gps
But now for exemple if I use deezer, it go at the bottom bar with the control button, and if I switch on android auto to poweramp, deezer still stay at the bottom bar, so if I want to switch song with the "next" button on my car wheel , it stop poweramp and next the song on deezer
I hope I was clear, so now I disabled deezer and I only use poweramp but I can't understand why it do this
Thanks in advance for the help, or informations
Also I have one behaviour now, for exemple I like switch between poweramp, deezer and also smart audiobook, and I use waze as gps
But now for exemple if I use deezer, it go at the bottom bar with the control button, and if I switch on android auto to poweramp, deezer still stay at the bottom bar, so if I want to switch song with the "next" button on my car wheel , it stop poweramp and next the song on deezer
I hope I was clear, so now I disabled deezer and I only use poweramp but I can't understand why it do this
Thanks in advance for the help, or informations
I've noticed that connection takes far longer in 2.0.2 than 2.0.1. It will take up to 50 seconds whereas previously would take about 10.
AAWireless would double blink blue, then change to red. This would happen a few times then it would connect.
Will the 2.1.0 beta fix this, or is it possible to rollback to 2.0.1.
AAWireless would double blink blue, then change to red. This would happen a few times then it would connect.
Will the 2.1.0 beta fix this, or is it possible to rollback to 2.0.1.
D
Deleted member 10362463
Guest
When will 2.1.0 firmware will be released i don't want to use aawireless in non passthrough on my hyundai. So eagerly waiting for 2.1.0 update to stable channel. @Snirpo @Emil Borconi
Last edited by a moderator:
Despite the request, I did not receive the 2.1 beta. Maybe I don't know how to get to her? Should it appear as a standard system update?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
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.87
Maybe in the future. We're looking into it, but it's not trivial because the CarPlay protocol is completely different from Android Auto.
We might also need an MFI chip to be able to do it, we're looking into ways around it, because we cannot get an MFI license (we tried). All the Chinese dongles just put an MFI chip on without having license.
IF we can do it we will provide it as a free update. For now I'd buy this other device if you want both. -
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!
