My impression is that the app doesn’t switch to brouter calculation even if it takes much too long to calculate a valid result, then finally the app quits in a calculation subroutine.
would it be a solution to force offline calculation when an online calculation cannot be finished in a certain time (15 seconds or so) even if there is internet connection on the device? Or is it possible to read the actual internet band width on the device and switch based on a low bandwidth? Don’t know how a smooth solution would be, but I guess all is better than a crash.
When internet is available with enough band width all is working fine.
Google Play console collects reports (after submit). Ι don’t see anything for Kurviger 1.13.11 (Beta) yet. So what really happened can only be theories now.
Regarding combined routing services, we had discussed all that:
Internet is checked on route request, if it does not work an offline routing happens.
That’s the simplest process and will remain so. Or select offline routing in settings.
Thanks. I think it was with 1.13.10. Before last tour yesterday I had updated to 1.13.11 and had no crash on the route (also with automatic calculation active). But it is a good hint, when such things happen, I can change the route option in settings and change it back later again.
Many thanks for the option to change the font size! I hope that soon we will see the option to change the size of several UI elements, although it’s probably harder to implement
I noticed that the speed panel is not refreshing when following. It invariably shows one value that corresponds to the speed when activating the following function (i.e. usually 0 km/h).
During navigation is OK.
Edit: Sorry, I did not notice that @Nico_Krause has already pointed out this problem…