In Developer Settings? I had it at 800x480 only. What should I set it to? I'll try the first setting and see how it is when I go to my car, thanks.
Last edited:
In Developer Settings? I had it at 800x480 only. What should I set it to? I'll try the first setting and see how it is when I go to my car, thanks.
In HUR - -> Settings - - > graphics ——> pixel densityIn Developer Settings? I had it at 800x480 only. What should I set it to? I'll try the first setting and see how it is when I go to my car, thanks.
I'm using in portrait on note 9. My screen is set to 1920x1080 and 170 on the pixel density. It's not perfect in that the icons are a bit ugly and few buttons are cropped but it's still very usable.I can't get this to work in Portrait for Self Mode.
I'm trying to get a set up working on a rugged tablet for my motorcycle, any ideas?
No diceI'm using in portrait on note 9. My screen is set to 1920x1080 and 170 on the pixel density. It's not perfect in that the icons are a bit ugly and few buttons are cropped but it's still very usable.
I can confirm the same happens on my Moto phone running Android 13. I tried several things like changing the AA resolution both in HUR and in AA developer settings directly, but nothing makes a difference. It's like the full screen mode that HUR is using reports a larger viewing area to the AA server than what there actually is. HUR on my actual old Android 8 head unit works correctly and does not cut off the ends of the screen, even with the new AA layout Coolwalk.At the risk of being lost in the noise: Using Self Mode on my Pixel 6a, it looks like HUR cuts off the top section (with the selfie camera "hole punch"), which cuts off the extreme left and right sides of the AA display. I've fiddled with DPI, resolution, and the margin settings and none of them help with this. Has anyone been able to use Self Mode with a hole-punch camera without cutting off the ends of the display?
Start at 400, which I'm guessing will make the buttons very small, but from there you can increase or decrease the value to your liking. Depending on the value, AA will change the layout as well.Question, i have a 1080x2340 resolution 6.47 inch screen (huawei p30 pro). What dpi do i need to put in the settings of this app so i can have AA normal on my phone screen?
i ment the pixel density, when i do 400 everything is super huge. How lower it goes how better, but i can not seem to find the best pixel density...Start at 400, which I'm guessing will make the buttons very small, but from there you can increase or decrease the value to your liking. Depending on the value, AA will change the layout as well.
Start at around 250, seems to work best for me on my phone.i ment the pixel density, when i do 400 everything is super huge. How lower it goes how better, but i can not seem to find the best pixel density...
Hey, I just tried something that worked here. I went to the Android settings, under Display. There's a submenu called Full screen. This is to allow apps to show content around the punchout camera. I selected this for HUR and then the AA icons were no longer cut off. I did have to adjust the left margin by 50 pixels to avoid the punchout camera.At the risk of being lost in the noise: Using Self Mode on my Pixel 6a, it looks like HUR cuts off the top section (with the selfie camera "hole punch"), which cuts off the extreme left and right sides of the AA display. I've fiddled with DPI, resolution, and the margin settings and none of them help with this. Has anyone been able to use Self Mode with a hole-punch camera without cutting off the ends of the display?
It's a personal taste; but I like the big buttons since they are easier to hit while driving. It also doesn't do the split screen, which to me makes sense for a screen of that size.i ment the pixel density, when i do 400 everything is super huge. How lower it goes how better, but i can not seem to find the best pixel density...
Thank you for this. Unfortunately my Pixel 6a doesn't allow this natively, and apps require special permissions to control it. I'll have to look into this.Hey, I just tried something that worked here. I went to the Android settings, under Display. There's a submenu called Full screen. This is to allow apps to show content around the punchout camera. I selected this for HUR and then the AA icons were no longer cut off. I did have to adjust the left margin by 50 pixels to avoid the punchout camera.
No, the project still works even up to the coolwalk update. The Dev will add things or fixes if needed but is focusing on other projects since this one still works.Hi guys, considering the project is unfortunately abandoned , is there any alternative?
that's not an error that's a feature by Google, it opens the keyboard on your phone for easier typing instead of the head unit. It should open both the on screen keyboard and phone keyboard. Self mode isn't ideal, wifi launcher is pretty solid.Im using the paid version of HUR with beta tester. I'm using self mode and I'm hit by the error of "Your phone's keyboard is active" when ever I want to search in the Google Maps or Waze. What is the possible solution to this?
The 2nd question is about the start self mode automatically does not work here. It will gives me blank screen and halted. Anyone had any idea how to get it work?
Hi not sure if others have mentioned this but the issue is primarly with google opening the keyboard causing the annoying loop of hur and the android auto app moving back and forth.Im using the paid version of HUR with beta tester. I'm using self mode and I'm hit by the error of "Your phone's keyboard is active" when ever I want to search in the Google Maps or Waze. What is the possible solution to this?
The 2nd question is about the start self mode automatically does not work here. It will gives me blank screen and halted. Anyone had any idea how to get it work?
Hi, Thank you for your reply. I am listed as a beta tester and a paid customer thru the Google app store. How do I confirm that I am on the beta version and if not, how do I get it?Make sure to use the beta on the paid version (the stable and trial versions are quiet buggy)
Follow the method and fixed the situation. Thank you very much for this tutorial.Hi not sure if others have mentioned this but the issue is primarly with google opening the keyboard causing the annoying loop of hur and the android auto app moving back and forth.
If you have another android phone say from a friend try temporarily downloading head unit reloaded on their phone (the trail version works if they don't have the paid version) and launch usb mode. Once android auto is launched open the keyboard by clicking on the search bar in google maps or waze (etc). Once their click on the phone keyboard button (circled in red). At this point you can disconnect from hur on the other android phone and uninstall it if not needed. This will prevent the anroid auto app from launching the key board on subsequent hur launches allowing you to use the keyboard properly.
View attachment 5859977
Hope this helps![]()
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