Yes I saw that as well on some devices, will try to look into it.@Emil Borconi Thanks, the latest update fixes the problem of hotspot not starting.
However, it seems to have introduced a new one: The first time the phone connects to the car screen everything seems ok, but if you get outside the car and back in again, then they can't reconnect again, until you manually press "force stop" on the HUR service from the car screen's android settings, and then it can connect again once.
My suspicion is that the connection is not properly terminated at the HUR side after disconnect when the screen hibernates, because before the phone tries to reconnect you can sometimes still see the previous AA session on the car screen, and after the phone tries to connect the screen goes black.
Some more testing if I goto the setup menu and back it turns on the hotspot, if I repeat this process it toggles the hotspot off.Still no hotspot I'm afraid, goto settings and back again and hot spot appears.
Hi EmilSome more testing if I goto the setup menu and back it turns on the hotspot, if I repeat this process it toggles the hotspot off.
In your code is it possible to just turn on the hotspot and not toggle it?
My Pixel 2 - ran perfectly on Android 11 via USB on HUR 5.2. I'm curious if users of the new 6 beta are seeing any issues with it b4 I update. No takers so far, so I'll probably give it a shot.Hi all,
Been a long time user of HUR , I did have it setup to use usb for a long time but that now seems to of stopped working with HUR since I installed the android 11 beta on my S10 (is that normal or anyone had that issue?). I have now managed to get wireless mode working in the meantime, however is there anyway to stop HUR freaking out when I connect the usb cable? I'd still like to use the USB for charging and wireless mode to connect to HUR.
I just installed the beta. The first time I tried wireless, it worked perfectly, as far as I could tell - no video artifacts, no issues with next track, etc. However, after restarting the car and letting HUR auto-launch, my phone blinked a couple of times as if connecting AA and the WiFi Launcher widget went from 'Running' (blue) to 'Connected' (green), but HUR on the head unit continued to show the 'listening for connection' screen. I tried this several times, but I never got AA to come up on my head unit again. Either I would get the 'listening for connection' screen or I would get a black screen, but I never got AA after that first time.
For background, on the previous version (5.?), everything worked great, except it usually would require one or more attempts to get AA to connect wirelessly and stay connected. It might crash or disconnect the first time or first couple of times. It would usually take 1-3 times to get it to connect and stay connected. After connected, it would continue to work perfectly indefinitely (I've seen it work flawlessly for multiple hours straight).
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