Well,As the topic battery drain came up again: yes, it is normal that the phone needs a lot of energy with wireless Android Auto. This leads to a fast battery drain and heat.
You have to remember that WiFi, Bluetooth and GPS are running. Especially WiFi and GPS need a lot of energy.
Moreover the phone is online as Google Maps downloads all information in real time. By this the phone uses also the internet connection all the time, which also needs energy.
I lose about 12.5% of my battery level per hour with wireless Android Auto running.
It's more than having just the radios turned on it's them being active with data. GPS especially if you're not navigating doesn't go through the constant data updates.Well,
I too have in home Wifi (all the time) BT, on my stereo speakers and headphones and the phone don´t heat like this...
I have GPS allways on also.
I use Waze for Driving.
But it heats up pretty bad.. (very warm to touch)...
Tomorrow im doing a 200km drive so i will infer the power drain and heating of the device...
True...Yeah I don't understand the battery drain complaints. If your phone did this much work on your home Wi-Fi with GPS and streaming music the results would be basically the same. Whether it's OEM wireless Android auto or using a dongle like AAW you really should have some sort of wireless charging setup to make it effective.
Thanks, something to consider I suppose. I was hoping that there might be a way within the settings, either of AAW app, or phone settings, as AAW unit is sat hidden away in the central armrest.
No, I don't use the pass through mode. Just the initial configuration.thanks for the feedback. It seems that it happens after I go to the car infotainment and go back to Android Auto, I updated today to 2.0.1, I will try again tomorrow, I have been using it for a week I may have messed something up. It worked today. Do you use Passthrought mode? I have not made any changes to the initial configuration and everything is fine, no drops, just this thing to clarify
Thanks for the suggestion but in my Redmi A3 Android 11 "avoid bad connection" is not present (I know that this option exists for others android phones).
At this point I would try everything and you absolutely need to be using the companion app. Anyone suffering disconnections needs to be on their regions 5GHz wifi using a high channel (153 or above) which is set and confirmed in the app.@festor yesterday did new factory reset (after updating to 2.0.1), cleared data from phone, from car. Did new pairing for phone and car (via bt, via cable) and then connected AAWireless with car. After pairing phone with AAwireless bt, AA appeared on headunit (without using companion app).
Drove ~30km and it had 3-4 drops (two were semi urban, other two were on country roads)
Today morning added few layers of tinfoil over AAwireless device. Looks like connection was more unstable than yesterday.
Should I try to setup via companion app?
Sounds very complex I'll build this feature into the next version of the app, possibly this week. Care to test?I've been happily using AAwirelsss in my Kia Stinger, but I do have a few notes on my specific installation that others might find helpful.
Instead of using the built in start / stop detection, I made a Y cable that hooks up the USB data lines and ground to my head unit, but power is pulled from a cigarette lighter USB adapter. I don't know if this is safe on all cars, but it worked on mine.
I have quite a few devices in my car I need to share internet with, and I do not want to buy an extra hotspot., so I had to make a few tweaks on my phone to make my phone's hot spot play nice with AAwireless. In the past I simply had a macrodroid script set up so that when my bluetooth connects to the car, it started my phone's hot spot.
Unfortunately, the limited wifi connection to AAwireless seems to confuse my phone's hotspot, and it won't share any internet once connected to AAwireless.
I found the trick was to to have Macrodroid enable my hotspot, then disable wifi, forcing the hot spot to share my cellular data connection, then reenable wifi, and script connecting to AAwireless manually.
The AAwireless password is the SHA-1 of the device name in upper case.
Note: AAwireless does currently support connecting through a hot spot, but only a hot spot that isn't also your AAwireless phone. Support for connecting via your phone's built in hot spot is eventually coming, but for now the method I use above has worked well for me.
Haha nice! I'll pass it on to our UI/UX designer We have some UX changes in the pipeline, but it doesn't have the highest prio right now as you can imagine.
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.
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.
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