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-86606909
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
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.
Known issue, you can track it here: https://github.com/cpebit/aawireless-issues/issues/124Hi All,
Recently I've changed cars recently and bought a VW Passat B8 from 2016 with MIB2 (previously a VW Tiguan Allspace from 2020).
Since this car change my AAWireless doesn't want to function correctly. I have random disconnections happening (could be once every 10 minutes or once every minute). When the disconnection happens it seems that it's the AAWireless device which is crashing somehow as the little status light goes off and then starts the boot sequence again (nothing > green > blue).
In the past the VW Tiguan Allspace worked fine (even though it took more than 1 minute from start of the car to full working).
What I've tried :
1. New cables : doesn't change anything (the cables work for Android Auto if I connect my phone directly to it)
2. Reset : doesn't change anything
3. Updates from v1.8 to v2.0 to v2.0.1 : doesn't change anything
4. Several USB modes / connection modes / VAG crash fixes / Start Stop fixes etc. : doesn't change the disconnects
Additional info :
* Device : AAWireless-ezvXL6z3
* Samsung S10e on Android 12
* The USB interface on the Passat seems to stay on for a very long time despite the car being off. I happens that when I near my car in the morning I automatically connect to AAWireless even though I'm just passing next to it (not opening it, nor entering it).
Is this something that anyone experienced before?
Regarding the broken day / nightmode cycle:
I also have this problem, and I read a few days ago that it was due to a combination of updated Google Maps and Android Auto.
The combination which should work:
Android Auto: 7.5.621344
Google Maps: 11.31.1
You finde all these old versions on apkmirror.com, or similar sites.
Didn't have the time to check this out myself.
While I do like these ideas technically. From an UX perspective I don't know.@Snirpo
Why don't you use a Y-cable? Data plugs into the USB and electric power from the cigarette lighter plug.
By this you can check the voltage on the cigarette lighter plug. Is it 12.x Volts, you know the engine is off. Then you wait for a timeout of 2 minutes after the phone disconnected and turn off AAWireless. As soon as the voltage is 14.x Volts, you know that the engine is running and turn AAWireless on. You could sell this as an addon cable for people who need this.
Another solution is to make it based on vibrations/accelerations. The early bluetooth handsfree sets used a similar way to check if the door was opened. I don't know if there is a sensor on the board.
Another idea is to carefully check how stable the 5V from USB is during engine start as the ICs have to control the output voltage based on the input voltage (input voltage should drop during engine cranking). I guess you will see a voltage control behavior. I think it will drop for a short time and then go over 5V until the controller sets the 5V stable. And here you can start AAWireless. As soon as the phone disconnects keep a long enough timeout of 5 minutes or so to make sure that noone tries to reconnect. Then you can turn off AAWireless. You could sell this as an addon cable for people who need this.
These are just some ideas...
Yes rebooting is a band-aid solution for sure. But I think it would be a good thing to add in any case. Most devices I own have an option somewhere in the menu for a reboot. Hopefully it's not too difficult to implement.
We're still testing the new start/stop mechanism. It seems promising for cars which keep USB port always or very long enabled (Mainly Dodge RAM)
I've already waited patiently for delivery 3 months more than expected - I ordered In April and was coming in June but now that's looking like October. Now I read on the indiegogo forum that people in the UK are being charged an additional €27 by the Royal mail as the UK is now not in the EU.
Just received my AAWireless, and will plug in and test tonight. Love the packaging, looks great! However… Since it was shipped from Hong Kong I was forced to pay a rather substantial import fee and duties on this bad boy. I was under the impression that they would be shipped from within the EU? Is it stands now I’m EUR 27,00 poorer
Emil Borconi-Szedressy 2 days ago
Looks like you are in the UK which is outside EU and also there is no way to pre-pay taxes with shipping company any more either....
This is a crazy. An additional $10 was already taken for delivery and it was meant to ship from the EU. I suspect the units have been shipped by Royal Mail / Dutch post. The Royal Mail rips off people in the UK because they add another £11 in admin fees on top of the 20% VAT even though goods up to £135 should be exempt.
So not only has VAT been charged coming into the EU from China, it has also been charged coming into the UK ON TOP of the VAT already paid in the EU.
This is just rubbish. What the guys need to do is either ship it from Hong Kong which can cost £0.20 (there are hundreds of chinese ebay and aliexpress sellers doing this already
The $10 postage already taken should then be refunded.
The other way round it is send the item from Hong Kong and to mark the item as a gift and providing it is below £39 there is NO VAT to pay and NO Royal mail admin fee. Actually as the original product was $57 - roughly £41.25 This wouldn't be a crime seeing as we have had to wait soo long. This could also mean the $10 delivery could be refunded
The other way is to ship it via fedex and state the ex-vat cost coming from china and then add 20% vat that the developer should be paying to the UK HMRC.
Sadly if that doesn't take place, EVERYONE IN THE UK will feel ripped off because of the poor delivery and poor choices made by the developers.
Disgruntled in the UK