Hello all,
Loving the app, but one issue I have with it using my Android Auto screen, if I stop on my route for fuel or a break etc, when I start to ride again, I have to take my phone out of my backpack/pocket to Continue the route. The main reason I tried this app is because it is one of the few good route planning app that work with Android Auto, so I can keep my phone safe and not on the handelbar. Am i missing something? Is there a button or a setting to let me tap the screen to continue instead of having to access the phone every time?
Hello,
thanks for providing the feedback. Please be aware that Android Auto is still a BETA feature within the App and is under development.
Not everything has been implemented yet and this includes (re)starting the navigation without unlocking the phone. The team is aware of this issue, but the solution apparently requires some not so trivial changes to the app.
On newer phones there is a workaround - you could setup your phone to be able to unlock itself when it is connected to a known bluetooth device. I myself decided not to use this workaround and wait until the issue has been resolved.
Just a quick update, with Version 3.5.2 it is now possible to start the navigation from Android Auto. We are still working on improving this feature. Right now, starting from Android Auto might not work depending on your lock screen settings and Android version.
In my case, there is some functionality now, but still needs some optimizations.
Apparently, the main success criteria is now not if the phone is locked or not, but if the app is in foreground or not.
Here is what happens on my phone/AA:
- If Kurviger is/was in the background (not shown on the phone display), then the navigation will not start, regardless if the screen is locked or not. As soon as the app is called in foreground (requires unlocking the phone), then the navigation will start (assuming “Start now” was pressed on AA before that).
- If Kurviger is in the foreground and the display is unlocked, the navigation starts immediately when the Button “Start now” is pressed on AA. This is of course ok, but not the typical use case.
- If Kurviger was in the foreground and then the display is locked, the navigation starts immediately when the Button “Start now” is pressed and although the the display is switched on an the PIN-Entry screen is shown, it is not required to unlock the phone! HOWEVER, if the PIN-Entry is dismissed by pressing the “Back” button on the phone, the phone display remains on and the navigation is shown on it. If this happens while the phone is in your Backpack, the phone battery may be drained faster than expected and there might be unwanted interference with the navigation by randomly pressed buttons on the phone touchscreen . So - be aware what is happening with your phone while AA is still in the BETA phase.
OSM date stamp: 20/11/2024
Version: 3.5.2
Device: samsung - SM-G970F - Android: 12 - WebView: 130.0.6723.107
App-Version: 3.5.2 - 4125
Screen: 360 x 760 px - 3dppx
Car-Connection: Projection
Car-Model: Google Android Sink (2014)
Car-Screen: 1000x437@1.34375
Interesting, thank you for this. The phone turning on was a big issue when I was using OSMand. The (OSMand) app itself seemed to be a power hog even with the screen off, but it would also turn my screen on and completely drain the phone in under an hour.
Hopefully this is something that can be remedied in future updates.
Might not be the same for everyone - I just tried to describe what is happening in my case and why I see it problematic. The best is to try out and see how it works for you.
We are already looking at fixing turning the screen on, so I believe this should be fixed in the foreseeable future.