Please follow these instructions: https://cpeb.freshdesk.com/support/...evice-never-connects-and-keeps-blinking-green to make sure everything is reset to initial state.Hi to all of you! I have Nissan Qashqai and car was manufactured in this March. I've tried everything to use AAwireless in my car but without any success.
One of the members also have Nissan Qashqai and he have managed to get thing going. I also used his method but without result. He have connected some USB hub to the car and than AAWireless to that hub, that's the only thing that I didn't do. Maybe that could be the problem? I'm really trying everything to try to bring AAWireless to life in my car.
I have recorded a video and maybe some of you can tell me what else should I try to do:
My phone is Samsung Note 9. I also tried with LG G7.
At the one point in the middle of video while I was trying to use Android auto from car screen I forgot that because of cleared cache I need to click on my phone to accept everything. Also day before recording video I did the same thing but first I connected phone with cable to enable everything in Android Auto and delete cache etc.
It looks quite similar as a problem that TheTen described.
I did everything as you told me to do. And still no result. :/Please follow these instructions: https://cpeb.freshdesk.com/support/...evice-never-connects-and-keeps-blinking-green to make sure everything is reset to initial state.
Make sure you're on the newest firmware, and make sure USB mode is on "default". Then it should work.
The USB hub "workaround" was not really a solution. "Default" USB mode is the key for (some) Nissan's.
I get this if I move the device. In my case, the USB c cable connection to the aaw device is not perfect. I have to gently move the cable near the device, until I find the corect position and it connects. Maybe try this.
Yeah I think it's a bad USB connection. We can swap the device, please contact support at https://cpeb.freshdesk.com and ask for a replacement.
Ah, here we go!
Anyone?Could use some input…
Received my unit a good few weeks ago. I’m running a SEAT Alhambra UK late 2015 with FULLLINK. Head unit device p/n is 7N5035680A with hardware H20 software 0240 and nav database 6P0919866.
I can pair Samsung NOTE 10+ to the AAwireless and connect through app, updated firmware, can change settings and initiate reboot.
On connecting to the AAwireless the phone attempts to open AndroidAuto which pops up as a notification ‘scanning’ for a connection that never gets made. The AAwireless just never seems to connect to the head unit.
I’ve tried three usb c cables that all work direct with the phone. I just get constantly flashing blue LED. Out of hundreds of reconnection, wipe data and re-pair, reset button, usb config changes just TWICE did I get a brief acknowledgement of USB device on the head unit and that was ’device not recognised.’
Nothing gets the thing working.
To be fair, I know support are busy… but…
I reached out to email support and just got several rounds of ‘in theory it should work’, lots of ‘try resets/delete cache and data/re-pair/usb modes but nothing works….and then support just left me there at ‘if it isn’t going to work I’ll just have to sell it on eBay with the caveat that it doesn’t work on an Alhambra 2015…’ with a virtual shrug and absolutely zero emphatic help to get it working or even test for a faulty unit.
So I’m less than impressed.
Does anyone have it working on a similar late 2015 VAG system?
Yes, we can see exactly how much boards of each model are updated to a certain version.I think the problem ist not only at a "few" boards of the first batch. Do you see how many customers of this GEN updated to 1.7.0/1.7.1? How much percent of them use this? I think there could be many more with this problem but the most of them have not used this FW, or dont update to any new version or are not interested for searching for the issue and dont report them to you. Not all of this users trying to keep in contact in this board to you or your App.
Yes, that's also what I think. If you have problems from the get go, it's different, because yes, then people might give up at a certain point. But when you have a working device and it suddenly stops working (seemingly) because of an update, people will report it. Especially with the number of devices in use now. To give a number, out of about 10k batch 3 (e2w3) devices, 2k are on 1.7.1, so about 20 percent. Maybe not everyone will report issues, but even if if only 5 percent reports it, it will immediately be visible in ticket count (or messages on XDA/Reddit). With 1.7.0 there was an (intermittent) general issue, and it was reported pretty quickly indeedNew issues would be getting reported.. that's human nature to get upset/annoyed/frustrated when something breaks..
1.7.1 is still rock solid here and using Start/Stop full time without issue. Best firmware release to date! I think they just need to iron out the 1.10.x app issues in the internal beta and push a new stable app release and we're good.
1.7.0 was of course the worst since it broke many devices booting up most of the time, and you better believe I reported on that promptly, then tested the sh*t out of it, and so it got fixed in 1.7.1.
Hello. This is MY big problem, too.I have received the unit and was very satisfied with its operation, but I was very disappointed when I discovered that my phone has stopped recording calls when connected to the aawirelless, this for me is very important to have this recording function the calls, before putting the aawirelless if it had the function of recording calls having connected by bluetooth to the car radio.
My phone is a xiaomi Mi 10T Pro, with android 11 system, room xiaomi.eu, with native dialer and active call recording.
Please, it is very important for me to be able to record the calls for my work, I need to know if this bug has any solution, thank you very much for the help.
View attachment 5434719
Thanks for commenting on your experience, I really imagined something like that, I hope a solution is finally discovered, I have stopped using aawirelles for this and it makes me very angry.Hello. This is MY big problem, too.
But The issue is from Android auto, not from AA Wireless. Even when I used the cable the issue was present.
This is because AA uses his own dialer that bypasses stock dialer... So internal call recording (made from stock dialer) does not work anymore...
Only once, and only for few days, Samsung stock dialer worked fine with AA with call recordings on... no idea why,
And no idea why this is not working anymore after I had to delete cache and data from Google app and Google play services...
I think this is the usual Google's stuff...
Boot limit is set to 5 failed boots before reverting to the previous version, so I think you experienced this. I'm glad we built in this failsafe... Didn't think we ever needed it... Thanks for the info guys!
I'm glad the no led is issue is fixed now This was a nasty issue. I'll give out testers a day or two to double check if it's completely solved, so I'll probably release 1.7.1 on Tuesday.
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