AAWireless - General discussion and support
- Thread starter Emil Borconi
- Start date
-
- Tags
- aawireless
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...
Best Regards,
LPC
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.
True...
But i don´t have wireless pad on my car.
I can only hope the 5000ma that my phone has is enough to not be without battery...
Also its a pitty that my C5 Aircross don´t have an usb plug inside the arm rest...
Best Regards,
LPC
I have a wireless charger pad in my car.
During winter time it is a perfect way to charge the phone on long drives.
During warm temperatures it is a mess.
The phone is already warm through wireless Android Auto. Additionally the temperatures inside the car are high. When I charge my phone in these conditions I reach a battery temperature of 38°C within 10 minutes. With this temperature the charging speed drops a lot. A couple of minutes later I reach 39°C and the phone slows down. For example it needs a lot of time to react. The highest temperature I reached was 41°C with the phone restarting by itself.
Under cold conditions the phone charges with a rate of 7.5% per hour with wireless Android Auto running.
At around March with temperatures rising I reach a charging rate of 1-2% per hour.
With the temperatures we have now I can charge the phone for a maximum time of 15 minutes before the phone slows down.
So generally speaking: during summer time it is impossible to use wireless Android Auto and to charge the phone with a wireless charging pad.
I ordered a charging pad with a cooling fan a couple of days ago to try. But honestly my I don't have much hope as my current wireless charger is pretty efficient and does not heat up much (only the phone heats up a lot).
If it does not work I think I will try a magnetic charging cable instead of the wireless charger.
These high battery temperatures will kill your battery pretty fast.
During winter time it is a perfect way to charge the phone on long drives.
During warm temperatures it is a mess.
The phone is already warm through wireless Android Auto. Additionally the temperatures inside the car are high. When I charge my phone in these conditions I reach a battery temperature of 38°C within 10 minutes. With this temperature the charging speed drops a lot. A couple of minutes later I reach 39°C and the phone slows down. For example it needs a lot of time to react. The highest temperature I reached was 41°C with the phone restarting by itself.
Under cold conditions the phone charges with a rate of 7.5% per hour with wireless Android Auto running.
At around March with temperatures rising I reach a charging rate of 1-2% per hour.
With the temperatures we have now I can charge the phone for a maximum time of 15 minutes before the phone slows down.
So generally speaking: during summer time it is impossible to use wireless Android Auto and to charge the phone with a wireless charging pad.
I ordered a charging pad with a cooling fan a couple of days ago to try. But honestly my I don't have much hope as my current wireless charger is pretty efficient and does not heat up much (only the phone heats up a lot).
If it does not work I think I will try a magnetic charging cable instead of the wireless charger.
These high battery temperatures will kill your battery pretty fast.
I might go the way of the "poor"...
Just plug an 4000ma powerbank on the phone and put both inside the arm rest!
Best Regards,
LPC
Just plug an 4000ma powerbank on the phone and put both inside the arm rest!
Best Regards,
LPC
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.
Car makers are still providing cars with wireless charging and wired AA, and with wireless AA and no wireless charger. We are stuck in the middle and have to provide both, and deal with the situation.
I've had wireless chargers in my cars for a long time, it's the first thing I do, so it was annoying to plug into AA before AAW came along.
I've had wireless chargers in my cars for a long time, it's the first thing I do, so it was annoying to plug into AA before AAW came along.
Just sharing this on a few threads in case anyone wants my opinion:
So I have both Carsifi and AAWireless - just sharing my thoughts here if anyone cares.
I have a Z Fold 3 and a S20 Ultra. The phones have roughly the same load time on either device in a Hyundai Tuscon. In the Hyundai i30, the AAWireless is about 10 seconds faster than the Carsifi.
The AAWireless app is nicer and easier to use than the Carsifi app. It's also got a few more options.
The Carsifi app takes a little longer to update the device when a change is made. There is also an 'experimental' method to boot faster but it made no difference on my phones...
The only benefit to some people (with Carsifi) may be the 'magic button' - you can set it to do 2 things:
1) change paired phone (double click)
2) Play / pause music (triple click) - however on my device, this paused the music but AA froze, and pressing play rebooted the device, so after about 10 seconds it rebooted and started the music again.
I got the AAWireless many months ago, and the Carsifi yesterday (I purposely got both - one for each car, and so I can test both of them too!)
At the end of the day, both do the same thing in the same way. In summary, I like the AAWireless better as it seems to just 'work' better, the app is better and I like the developer and their reputation.
Oh and if anyone has any questions, please let me know and I'll respond.
So I have both Carsifi and AAWireless - just sharing my thoughts here if anyone cares.
I have a Z Fold 3 and a S20 Ultra. The phones have roughly the same load time on either device in a Hyundai Tuscon. In the Hyundai i30, the AAWireless is about 10 seconds faster than the Carsifi.
The AAWireless app is nicer and easier to use than the Carsifi app. It's also got a few more options.
The Carsifi app takes a little longer to update the device when a change is made. There is also an 'experimental' method to boot faster but it made no difference on my phones...
The only benefit to some people (with Carsifi) may be the 'magic button' - you can set it to do 2 things:
1) change paired phone (double click)
2) Play / pause music (triple click) - however on my device, this paused the music but AA froze, and pressing play rebooted the device, so after about 10 seconds it rebooted and started the music again.
I got the AAWireless many months ago, and the Carsifi yesterday (I purposely got both - one for each car, and so I can test both of them too!)
At the end of the day, both do the same thing in the same way. In summary, I like the AAWireless better as it seems to just 'work' better, the app is better and I like the developer and their reputation.
Oh and if anyone has any questions, please let me know and I'll respond.
@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?
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?
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).
But as said, I manually connected phone and AAW via BT and now everything starts connecting and working when I turn on the car
Makes me laugh people complaining about their phone being too hot or their battery life draining faster than desired.
Know the alternative...? Plug your phone in and use android auto
Can't have your cake and eat it too - there will always be a trade-off. Wirelessly charging will ALWAYS make your device hot while charging, it's the nature of the beast. Wirelessly charging, Google maps, GPS, casting via WiFi...
Yep, phones guna go nuclear and melt your car. Is it that hard to charge your device before running AAW? Most phones support a quick charge with 30mins easily getting 50% battery life
Know the alternative...? Plug your phone in and use android auto
Can't have your cake and eat it too - there will always be a trade-off. Wirelessly charging will ALWAYS make your device hot while charging, it's the nature of the beast. Wirelessly charging, Google maps, GPS, casting via WiFi...
Yep, phones guna go nuclear and melt your car. Is it that hard to charge your device before running AAW? Most phones support a quick charge with 30mins easily getting 50% battery life
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.
This should only affect MIUI, but what happens when you try forcing a lower mobile connection on your phone? It might be slightly different for your model, but under Mobile networks > Network mode SIM(x), change to WCDMA or GSM only. Reverse process after testing. Does AAWireless stay connected when you do this? Also, can you try a non Samsung phone in case it's a quirk with your car/head unit?
If you're using v2 hardware and tried everything else you've detailed then it might be a good case study for support, but I would be looking at testing an alternative like MA1 or Carsifi.
Similar threads
Top Liked Posts
-
1
That's interesting, since OnePlus also is based on Oppo...
Did you maybe have or had a systemupdate on your phone?
You also could try these steps: https://themobilequery.com/oppo-find-x3-pro-gps-not-working/
...these also helped the oneplus users I know that have issues with GPS.1I had the same problem with GPS not working (not finding position or not moving on map) after the 2.0.2 update.
Plugging out aawireless from my car's usb, waiting a minute und plugging it back in seems to have helped, at least with the one Google maps journey I had today.
My phone (even if it is a oneplus 8t ;-) ) was definitely not responsible, GPS worked there all the time and I could navigate with the phone without any problem1Great work !
When I fired up the AAW app, it said an update to 2.0.2 was available. When I tapped that, it asked if I wanted to download on a metered connection, & I said yes. It then started to display progress info at the top of the screen, & then almost immediately quit. Repeatable.
Why do I believe that this is a software error? Because the progress info was " % %d %", which means that someone screwed up an 'sprintf' function call.
This used to work correctly.
EDIT:
The above info was from attempting the update while AA was running on the car/AAW/phone.
When I tried again a few hours later, I did not give AA a chance to start, & the update to 2.0.2 worked perfectly, & I did not see the 'sprintf' error.1
I'll check. We've been having some backend issues lately, so that's probably the cause. The sprintf thingy is probably a side effect of that.Great work!
When I fired up the AAW app, it said an update to 2.0.2 was available. When I tapped that, it asked if I wanted to download on a metered connection, & I said yes. It then started to display progress info at the top of the screen, & then almost immediately quit. Repeatable.
Why do I believe that this is a software error? Because the progress info was " % %d %", which means that someone screwed up an 'sprintf' function call.
This used to work correctly.
EDIT:
The above info was from attempting the update while AA was running on the car/AAW/phone.
When I tried again a few hours later, I did not give AA a chance to start, & the update to 2.0.2 worked perfectly, & I did not see the 'sprintf' error. -
7
Haha nice! I'll pass it on to our UI/UX designerI got bored today, so I thought I make a mock up how the AAWireless app could look like When swiping t he car picture could change if you want to connect to annother device/car
View attachment 5645393 View attachment 5645397 We have some UX changes in the pipeline, but it doesn't have the highest prio right now as you can imagine.
We made some changes in firmware 2.1.0 which means we don't need these dreaded USB modes anymore. The plan is to ship devices in passthrough + dongle mode, to make it work natively, like the MA1, by default.
Then we are going to hide away the settings in a sort of advanced settings menu, because all these settings are nice, but people don't read/understand what they do, stuff stops working and then our support has to handle it. Hardly anyone uses these settings, for example, dpi change, the most used feature, is only used on 1 percent of all devices.
Bassicly we are KISS'ing it, but still keep advanced settings for well... You guys5@everyone
For feature requests or issues, please use: https://github.com/cpebit/aawireless-issues/issues/new/choose
I getting really hard to follow this thread. Possibly I already forgot some requests of some people. Need a bit of structure. We will try to fix issues one by one from GitHub.4I had this same problem. Found out it woud be caused to 11.31.1 and upwards. Found the solution on Google Maps Help.
I installed Maps 11.35.0 beta (from apk mirror) and all seems to work well again. My AA is level 7.7.622134 (from play store).
Tried a lot of different variations, but my conclusion is that Maps from 11.33.1 is the culprit.4
Sounds very complex I'll build this feature into the next version of the app, possibly this week. Care to test?3
While I do like these ideas technically. From an UX perspective I don't know.
Right now already we get complaints AAWireless is difficult to setup (while in reality it really isn't), compared to for example the MA1, this would complicate it more. I have seen a lot of support tickets, and for non-tech these things are just very hard to understand. "Why do I need an extra cable?!"
I think for the car's which have an always on USB port (Dodge RAM/Jeep) we seem to have a proper device controlled solution now (in beta).
For other cars which keep their USB port powered for just a while after turn off its trickier, but even then the phone controlled way works for most. What's left is the edge cases, where we have to think about how to handle those. -
40This 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.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!14I'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.
Hi Emil!
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
2 2
https://www.indiegogo.com/individuals/24534862
Emil Borconi-Szedressy 2 days ago
PROJECT OWNER
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.
See https://www.gov.uk/government/publi...s-goods-sold-to-customers-from-1-january-2021
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
See http://www.vatfraud.org/blog/stop-s...ons-universal-postal-union-upu-terminal-dues/
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.
Cheers
Disgruntled in the UK
First of all, your item wasn't shipped yet since in the June batch, so you could have not payed anything for shipping. Secondly, UK is outside the EU, there was a vote about this in 2016, so it doesn't matter if the package comes from EU or from HK or from US, it is treated the same, it's an import. If we import it from HK to EU, we will pay import VAT on the product, then when we send it to UK, we claim back that VAT and we should pay VAT in UK, since there is no more free trading between EU and UK.
Up till recently there was a nice option, to pay VAT and Import duty up-front, when you ship to the UK, but this has been changed and now they requires business outside UK to register with HMRC and do HMRC feeling even if they are residing outside UK, a lot of red tape. Since crowdfunding is not a sale, we can still ship the units to UK, but not sure if we will be able to after the IndieGoGo campaign.
We are also a EU registered company so we cannot (and will not take advantage) of any loop-holes in systems to sell at ridiculously / unrealistically cheap prices.
About the user who paid 27 euros, it turned out that user is living in DK, but provided the address as UK so his package traveled the wrong way, hence the extra duties and surcharges.
Not aware of other users from UK having to pay anything additional when they received the package.
