New here. Experiencing same issue described above. If you don't mind, how was this fixed?
Not sure what's going on afterwards (are there incompatibilities with different lsec6315updates?), but it looks like it copied config.txt fine.
Emil,Updated HUR to version 5.2 changelog:
- Removed WiFi Direct
- Improved menu UI
- Updated margin setting
- Added option to record audio using BT mic (motorcycle helmets)
- Added button to reconnect WiFi connection ( phone and unit depended won't work on all units, please read app forum for how to connect)
- Option to disable touchscreen
- Removed brightness adjustment (some users experienced problems adjusting brightness after using previous version, sadly they need to do a factory reset of the unit, and update to current version)
How is your phone connected to your HU? USB? How are you charging your phone? Car USB port? Wireless?
I'm looking for a solution for this same issue as well. I've tried using Tasker/MacroDroid to autostart a hotspot and launch HUR at boot, but 1) Tasker doesn't start at boot, and 2) even if I start Tasker manually, it doesn't detect the state context (boot, display on, etc.), however if I manually execute the task (hotspot on + launch HUR), it works fine. I'd just like to automate this. The unit isn't rooted.Good Afternoon,
I'm having a problem using the HUR wireless, I'm using a android headunit and I follow all the setup steps.
Basically when I open the HUR app the head unit Hotspot starts and I can see the connection on my phone but when I try to connect my phone to it I can't it get stuck on Obtaining IP address, the only way it seems to work is if I start the headunit hotspot manually, when I do that everything works fine and I don't have any problems. But it's not that practical.
Could you maybe help figuring out a way to solve this problem? I already tried to set static IP address, when I do that the phone connects to the hotspot but then the wifi launcher doesn't do anything and the android auto doesn't start.
Thank you for your help.
Try to install the beta version, the link can be found on the HUR play store app description. It solve the problem for me, now when I run the app on my headunit the hotspot automatically starts and the phone connects normally.I'm looking for a solution for this same issue as well. I've tried using Tasker/MacroDroid to autostart a hotspot and launch HUR at boot, but 1) Tasker doesn't start at boot, and 2) even if I start Tasker manually, it doesn't detect the state context (boot, display on, etc.), however if I manually execute the task (hotspot on + launch HUR), it works fine. I'd just like to automate this. The unit isn't rooted.
On the phone side, I have to manually start the WiFi Launcher service before it detects the hotspot on the head unit. Would also like to automate this a bit more, but automating the head unit is a higher priority for me.
Thanks and sorry for the late response. I tried this app and it's connecting and disconnecting after a while. Also, I can't turn on internet access on phone or headunit bluetooth options. Any ideas?Not sure what's going on afterwards (are there incompatibilities with different lsec6315updates?), but it looks like it copied config.txt fine.
This is with sys.fyt.bluetooth_type=0? Can you verify it's updated (terminal, file editor or whatever)?
You'll likely need to unpair/repair your phone.
If you launch bluetooth2 with it, you should see that's now the active bluetooth.
It doesn't use the Launcher. You have to start a hotspot on the phone first and tether the head unit by pressing the WiFi button on the home screen.
I've done with beta version (6.3) via this method
Set smaller resolution in HUR settingsThat didn't work for me but I uninstalled bthe beta and the regular version connected right up. It also seems smoother to me for whatever reason. One thing I am wondering is if it is possible to make the active app full screen and not have the sidebar of the second app? On regular android auto it is always full screen besides the small panel on the left. Cheers
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