Got it! I never used this functionality and this way to place my waypoints. But this way is also convenient for me Nevertheless, to avoid further user confusion, I would suggest to force all users to this new way and remove this setting.
Hm, I only can change the color but not the transparency…
Had some app crashes when automatic recalculation was active. Unfortunately I can’t say when exactly this happens. I hear the voice telling calculating… then the app quits without any message. Since I was on a 5 day motorcycle trip with other guys, I deactivated the automatic recalculation and then it worked.
Date was 9.6.2020, device was a Samsung S9+ SM-G965F
Routing-Service was Kurviger-BRouter, unfortunately not sure anymore if internet connection was available. Screen was on.
Pretty sure route calculation mode was “next waypoint” as I planned to use this on the normal journey to the hotel and then changed it to strict mode for the rally day trips. The rallies were done with automatic route calculation off which worked ok… no crash any more then.
just came back from a 5 day tour with kurviger 1.13.9 running on an Huawei Mate 9 (Android 9). Routes were fine and most things worked extremely smooth.
One thing though: I made use of the new “Pause” function quite a lot. But unfortunately there seems - at least for me - an issue: What happened is that after the Pause, the fact that I have already passed some of the waypoint was “forgotten” I had manually delete passed waypoint to be “on track” again. This was all with switched off automatic re-routing.
It could be an artifact of the Huawei device. On the bike I have connected the phone to power (which makes is run quite reliable), But the power is switch with ignition. Meaning that when stopping, the Phone runs on battery. Due to the aggressive killing of apps that Huawei does (even though I switched off all of these “features” that I can) it could happen that kurviger would be restarted. Could that be the cause that the fact that I have already passed some wayspoint is forgotten? How is the state of the waypoints (passed/not-passed) persisted? Or is there a general bug which might have cause the issue?