Replies: 2 comments 3 replies
-
It's designed by Android Auto policy, they even check this behavior during manual review. If I'm not mistaken we can't influence that or we need to do some special ui for that. |
Beta Was this translation helpful? Give feedback.
-
I have run into this same issue while going on longer road trips and sometimes even just by filling up the car on shorter trips. My most frustrating experience was when visiting family ~1400km (~875mi). There were many stops and having to go in and make the route recalculate every time was extremely time consuming as it could take around 5min to actually make the route. Only disadvantage is that I don't know how navigation following a track would behave if an unforseen event makes you take a deviation... Will OsmAnd recalculate for the destination or try to get back on track as quickly as possible... Anyway... I thought I'd mention it as I believe it could be a possible way to make the navigation be "resume-able" when making fuel stops and decoupling the phone from the car in the middle of navigation. PS: I'll try to have a look whether it is possible to save the navigation state somehow and check for this navigation state when connecting to android auto. But seeing as I am no developer/programmer (certainly not in java/kotlin) I can't make any promises on whether I can/will make it :( |
Beta Was this translation helpful? Give feedback.
-
If I bring the phone with me, when I stop at a café halfway in a long trip, the current navigation is automatically dismissed.
That is not what I need, I want to continue the current voyage, when I have finished the coffee.
(I think the current navigation continues, if I turn off the ignition, but leave the phone plugged to the car?)
Android Auto 8.2.623924-release
Osmand+ 4.2.7
Beta Was this translation helpful? Give feedback.
All reactions