That's the same charger I got. The charger itself is great and if I'm just streaming music via Bluetooth it works awesome. But the combo of aawireless plus wireless charging is just too much. I think a lot of it is just the flip 4 being a less than ideal form factor to keep cool. I know I've seen reports of the flip heating up quite a bit during gaming as well.I use also a wireless charger with cooling fan. It is made by ESR. This works pretty well also during summer.
I modded my case to have a mangetic ring to improve the positioning and also the fixation on the wireless charger.
Yes, this is already kind of possible by enabling start/stop and selecting some random Bluetooth device to start the connection (not the HU handsfree), so it will not actually start based on BT handsfree. You can then start the connection manually with the the "force connect" widget and kill the connection from the notification. If you want we can work together on making these things part of the public API. Please join us at https://join.slack.com/t/aawireless/shared_invite/zt-1rgddavyq-BKI4rW_Lh0tYRVTOaAPU4gHi @Snirpo, any advice about manual connecting?
I (my son literally) have made some simple app with two very very large switches (easy clickable during the driving without losing the look to the road and focussing to hit some miniature text-switch) named "Disable AA" and "Enable AA". This app when launched does nothing untill "Disable" is pressed - it blocks AA service in Android (package hide) so AA connection drops and I can easy use origin car BT features without crazy AA phone service. "Enable" makes AA unhidden and wireless (or wired as well) connection is re-established.Yes, this is already kind of possible by enabling start/stop and selecting some random Bluetooth device to start the connection (not the HU handsfree), so it will not actually start based on BT handsfree. You can then start the connection manually with the the "force connect" widget and kill the connection from the notification. If you want we can work together on making these things part of the public API. Please join us at https://join.slack.com/t/aawireless/shared_invite/zt-1rgddavyq-BKI4rW_Lh0tYRVTOaAPU4g
Maybe try the passthrough mode?Hello, I'm on beta test with firmware 3.0.
(...) Blue light keep blinking and my phone blinking from time to time but nothing had happened. Is there any options I can try? I'm using Samsung Note20 with my Mercedes E300 for your reference.
The Xiaomi issue only happens when mobile data is lost and reconnected. You can reproduce this issue like this:This is on a Motorola MA1 and it will happen with all dongles or native AA Wireless HU's on Xiaomi phones.
Just to clarify, you were on the Global 14.0.1.0.TKBMIXM ROM then received an update to 14.0.2.0 and it has fixed the linked data/wireless issue?New update released for Xiaomi mi 11 lite today, it is the first global miui 14 / Android 13 for my device.
It is MIUI 14.0.2
Connected via AAwireless as usual.
Tried to change mobile data manually from
4G/LTE to 3G = no disconnection
4G to 2G = no disconnection
3G to 2G = no disconnection
3G to 4G = no disconnection
Disabled mobile data toggle = no internet = no disconnection
So what would be the result ?!
Nah I was on the global 13, as I said above this is my first miui 14 upgrade. Yeah no longer this issue.Just to clarify, you were on the Global 14.0.1.0.TKBMIXM ROM then received an update to 14.0.2.0 and it has fixed the linked data/wireless issue?
Or do you mean you upgraded from A12/MIUI13 to EEA 14.0.2.0.TKBEUXM and you no longer have the data/wireless issue?
Can you go into Settings > About phone, and provide details of the MIUI ROM you're on, including the letters within the brackets? It would also be good to know what Android Auto version you're on.Nah I was on the global 13, as I said above this is my first miui 14 upgrade. Yeah no longer this issue.
Took some pics with and without mobile data:
Here you are:Can you go into Settings > About phone, and provide details of the MIUI ROM you're on, including the letters within the brackets? It would also be good to know what Android Auto version you're on.
So it looks like you have a Mi 11 Lite 4G and AA beta.
No, never needed start/stop. I will stick to this update and don’t jump to miui future updates.So it looks like you have a Mi 11 Lite 4G and AA beta.
You're the first person I've seen mention that MIUI14 fixes the data/wifi issue so I wonder if it's an extended AA timeout added to the beta that's stopping the dropout. Have you enabled Start/Stop in the AAWireless app?
@Snirpo is that a Redmi Note 9 you used for the video above? It doesn't look like it will get MIUI 14 unfortunately.
AA over CP is NOT a core feature. In fact even CarPlay is NOT a core feature (yet). Its beta... We dont advertise it anywhere. Its a nice extra, but that's it. Sorry but these "paperweight" comments annoy the heck out of me. Some people expect their issues to be fixed right away. That's just not how it works.I should have come to this thread to begin with, but I, too, am having this issue as well. Also in a Polestar 2.
I submitted a support ticket on January 17 this year, and after providing plenty of information and submitting bug reports, it seems I have been forgotten about. I was even told that "no other Polestar owners have reported this" - rubbish, it seems!
I recently got the 4.0 Beta notification and today updated that in the hope that something had been done, but nada!
I note there are several compatibility options for other manufacturers that exist, including a new one in 4.0 that I haven't noticed before that addresses a Mercedes Benz issue, so surely two people with the exact some car is enough to acknowledge there is an issue for Volvo/Polestar AAOS compatibility?
I'm grateful I didn't buy my AAWireless to use in my Polestar, because I'd be bloody annoyed at having paid the money I did for it and having a shiny, new paperweight as a result.
Blue means working correctly, so you're ok.That sounds good.
While I have your attention, where do I find documentation for the app's multitude of device settings?
Also what color should the device's light be when it is connected and properly working? My device is blue and everything seems OK.
It's not possible right now, we have to implement it. But it's quite some work and it will be pretty wonky with all the screen sizes and stuff.Hey Snirpo,
Thank you very much for the quick response.
I don't like to have Google Maps as start app.
I tried everything to have another app as start app, but did not find a way to change it.
My last hope is to emulate touch inputs on the head unit.
Can you please give me some support how to emulate touch inputs?
Thank you very much.
AA over CP is still very much beta quality. We'll add these issues to our backlog, but right now AA over CP has low prio.Hi all, I have a 2020 Corolla Sedan (USA). This car only supports CarPlay, not Android Android Auto.
We purchased the latest version of AAWireless and enrolled in the beta program to enable AA over CP and it actually loads in the car and looks and works like native AA, which is amazing.
We have 2 problems though which is why I am posting.
1. It takes 1 to 4 "reboots" of the dongle to finally load AA (the light goes through the flashing green and flashing blue before resetting and trying again on its own).
2. Once loaded phone calls through AA are in fast forward and sound like a chipmunk. Occasionally GPS also lags, I'm not using the infinite touch setting.
I've spent hours tweaking the various settings and modes but haven't found a combo that fixes these issues.
Appreciate any guidance!
It is treated correctly. It's on our backlog and does not have priority right now unfortunately. I do agree our support may have given false info though... So in that sense you have been brushed off. I'm sorry for that.Core feature or not, everyone knows it's capable of it.
Nobody is asking for it to be fixed right away, simply acknowledged. @leroy_sunset had no replies to the post back in October and had a support experience that mirrored mine. I was even told "no other Polestar owner has reported this", which was quite clearly not true.
I'm a developer Monday to Friday too, and if I brushed off paying customers with niche requirements, I'd not have a job.
Hell, right now I and about a dozen other developers are working on a feature to be used by 1 customer.
All I'm asking is that this issue, which clearly does exist, is treated correctly.
We can add a feature to disable AAW temporarily. Will probably add it as an "app shortcut" so you can place it on your homescreen.Well that did not work, because the phone, a Pixel 7A, turned both Bluetooth and Wifi back on Tried it numerous times in the car with same results, away from the car both settings remained off as expected. I also want to keep Bluetooth on for hands free phone calls.
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.I used to get the same thing. I believe it is an issue with AA/Google rather than AAW. In any event, I have had to give up on AAW as I can't connect to it/won't update, just sits there with a constant light-blue light. It is a (very expensive) paper weight on my desk now. It is just "too Beta" for my requirements.
I have now got a Carlink 2022 Android box which works flawlessly for me.
MG ZS EV 2022
Galaxy S21 Ultra (not rooted)