Hi. Version 5.2 is OK for me. But all versions 6.3 are bad for my radio. The application always crashes.
Oh right the fire HD 8 2020 doesn't have a hotspot function in the settings but can be enabled via a 3rd party app
Could you please details the steps you took to get the connection working. I haven't had any success trying to make Native wireless AA to work.
Hi.I had the same issue of the app crashing. For me it seems that it was related to the gles 2.0 rendering. It stopped crashing when either changing to software decoder or changing the render surface from gles 2.0 to surface view in the graphic settings.
I've just updated to the latest beta on the Play Store. I'm using regular wireless AA (not native) with the WiFi Launcher app. Every time I try to use the voice assistant (tapping on screen, key on steering wheel or "Ok Google", it crashes HUR. Not sure if anyone else experiences this or knows a solution.
Have you enabled the option to disable touch restrictions? That seems to mess up the GPS in some instances.Covid restictions have had me home bound for a while and I haven't had a chance to test HUR on a longer drive. I had a problem today.
I used Google Maps to guide me to a location 1.5 hours away. About 2/3 of the way there I noticed that the vocal instructions and map location on the screen weren't in sync. The vocal instructions were up to date with where I was, but Maps on the car display was behind, around 5 minutes. On the way back I used Garmin on the car deck and had no issues.
I don't know if anyone else has had this happen, or if it has happened if they figured out what it was and a fix.
Not a big problem, as I knew where I was going. But on a trip where directions are needed, this would have been a problem.
You know what, I thought I was in the AA wireless thread. But this may also apply to HUR. The option is called fake speed reporting or something like that in the GPS section. Play with that and the other option called GPS sharing, which I believe means Android auto will use the GPS of the tablet which sometimes is not that good.NO, I hadn't read anything about that. I'll check HUR next time I get in the vehicle. Thanks.
So the head unit is rooted as well, and you installed HUR... What year is it? Are you sure it has WiFi? When you go to settings-> connection in HUR, is the first option you see "use native wireless AA method", or "listen for incoming connection"?Mine is a Honda stock head unit running 4.2.2. HUR I'm running 6.3 B4. The headunit bluetooth card was compatible with native wireless when I installed 6.3, but never did connect. I have tried both types, wireless and via hotspot.
When I get a chance I will try your instructions today. My previous phone, a Pixel 2 stock worked fine when plugged into USB .
The only issue I have with USB, is that the phone will not go through HUR. So in other words, if I ask assistant to call someone the call goes through the phone speaker, with or without audio synced. I have selected and deselected the phone in bluetooth settings. The car deck is awful to make calls through. The bluetooth assistant is terrible and it forces me through several menues before i can connect and make a call.
Native AA works on 5GHz, which that head unit probably doesn't have, and I don't know if there's a fall back for 2.4GHz. What do you see on the screen I mentioned above?Yes, its rooted and that's how I got HUR installed.The first option is for native wireless AA. Its a 2016 Honda Pilot Limited. When I installed HUR 6.3 the phone confirmed that the bluetooth card was suitable for native wireless.
It definitely does have wifi. I have connected to the hotspot on the phone.
The deck must have been archaic in 2016. It is slow, the ui is poorly designed and in general it is subpar to other OEM's. But it did work on USB with 5.2 and a Pixel 2, no problem. The Pixel is gone and I have a Poco X3 NFC, running A11 and ArrowOS.
Connect the phone's audio to the head unit if you can run AA without it and then disable the "sink audio" option which will make the audio go through the phone instead of the tablet, except since it's connected to your radio it will pipe audio hopefully to your speakers.Thanks for the info, I've actually updated to the beta and it is working much better over Wi-Fi and Option 1 is now working as well.
So now my next hurdle is which BT connection do you connect to the BT in the Headunit,
1 - Tablet seems to mean media audio and maps come through Headunit and calls via phone on speaker mode on phone
2 - Phone means calls through Headunit and media via tablet speakers.
I suppose as a last resort I could have phone on BT and and the tablet connected on a long aux plug to stereo but that is another wire to run.
Isn't that exactly what you just joined up to do?
You didn't join to ask a question. You could have started with telling us what device and Android version you are trying to connect with/to, and perhaps someone could help you constructively.
Sent from my ELE-L29 using Tapatalk