Yesterday I updated to the latest version of the beta in the play store and so far have not experienced the issue. Activating the assistant via tapping, physical button or catch phrase seems to work as expected.Did you find a solution?
I am having the same issue with the beta.
You are right, it is on the play store now. Thank you.the version that are in playstore beta is already RC3.. I believe it is the latest one..
I dont know if its the latest version or not but the one available to me in the play store is V6.3 RC3.Are we sure the latest beta on the play store is definitely the latest? It doesnt seem to be any different to the previous beta, and I have no AA wireless settings in HUR. USB works occasionally, and wireless doesnt work at all.
Very confused here lol, as I thought the latest couple of beta's improved the native wireless compatibility.
Go into settings and graphics and change the pixel density. For me split screen is 160 and below, full screen is 170 and above. Your situation will likely be different vales than mine.Hi Guys, so today I ditched the dongle and loaded HUR. Love it... It also enabled the new split screen feature in AA.. Trouble is I don't need split screen and I cant seem to disable the feature. Does anyone have a suggestion how to turn off this new AA feature?
I dont know if its the latest version or not but the one available to me in the play store is V6.3 RC3.
I have gone back to stable 5.2 because it broke too many things for me as above. Notably;
- USB doesn't work at all
- Steering wheel controls no longer work and aren't mapable
- Native wireless AA still needs wifi launcher (isn't a show stopper)
That's a difference we have then, i have full voice functionality in 5.2 stable. Hey google, responding to msgs etc all works flawlessly in 5.2 and 6.3 RC.The RC version voice command does work eg I say "Hey Google ... read message" and it will read out all the new messages or I say Call Kelvin and it starts calling the person. I don't get this to work in Stable 5.2 though. I switch to using USB connection method now and it worked every single time where as using Wifi Launcher method, sometimes I need to repeat steps to get the Waze map showing on my Car HU. Another good reason for me to use USB method is it charge my phone at the same time.
Car salesmen will do anything to get you in the showroom to unload a new vehicle on you. That said, this is a pretty clever ploy.Hi anyone using the native WiFi method, mine is working great accept when I go past a local car showroom AA disconnects and then hur closes down. Its the only place that this happens really strange
Just to expand on what Clarkie49 said, because this is getting tiresome..One question about wifi...do I have to enable the hotspot in the phone settings when wifi launcher is installed, or do I just leave it off and wifi launcher sets up the wifi?
Thanks for your patience.
am start-foreground-service -W com.google.android.projection.gearhead/com.google.android.projection.gearhead.companion.DeveloperHeadUnitNetworkService
am stopservice -W com.google.android.projection.gearhead/com.google.android.projection.gearhead.companion.DeveloperHeadUnitNetworkService
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.
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