Follow mode makes mistakes after a (long) while

Navigation
1

Hello,
I have used Kurviger to just track my holiday route the last weeks. No planning, no routing.
I just started the follow mode the first day and then resume everytime I moved on.

That worked perfect until about 5000kms later.
That means, the logged track was already 5000kms long.
The follow mode started then to not track correctly, but skipped several kilometers, resulting in straight lines.

I think that it is probably a bit of an exceptional case, however maybe it can be fixed.
I stopped the follow mode and saved the route and started a new one, after that it worked again as it should.
If a developer wants the track, I can send via PM
many thanks!

1 Like
2

Can you provide more details (for example share the debug string from the Kurviger settings)? Was the screen locked when the part was skipped?

3

Hello,

what exactly do you mean with the debug string?
Does it still deliver informations, now several weeks after that this has happened?

Screen locked? no. But device was put in standby several times a day. And Kurviger was in background most of the time as I just wanted to track the route.

It was running perfect for about 3 weeks.
Every day I put my device in standby as I put my car off. After device on, Kurviger started and I just resumed the route, just hitting “Fortsetzen”.

One day, I have seen, that the route wasn’t tracked correctly (see screenshot). I then paused follow mode and then restarted follow mode (still same route) and it worked for some kilometers and then it happened again. Tried that some times, but happened again.

After that, I stopped route tracking, saved it and started a new route track which worked then flawlessly the next 3000 kms. Therefore my assumption that the track which was over 5000kms long at this time triggered any errors maybe due to its lengths. I assume 99% of all users won’t create such long tracks.

Screenshot 2025-09-05 101426
Screenshot 2025-09-05 1014261314Ă—604 76 KB

4

Ah ok, yes that is the relevant thing.

If you go into the Kurviger settings at the bottom there is some info about your app and device.

For background usage we added an improvement for iOS with version 3.5.10.

For Android you need to set your system accordingly (don’t stop the app in the background). Knowing more about your device would help to give tipps.

5

ok, I can get that information, next time I’m in my car. The device is an Android device M.I.C Av9v2 with Andoid 13, 6GB RAM. IPS-Display with Multi-Touch-Screen 1280*720 HD (landscape format)

However, I wonder, why its working that way for 4 weeks and then not any more. And after a restart it works flawlessly again?

And the procedure was:
Car starts, Kurviger got started, then just a press at “continue follow mode”, then I navigated with Google Maps, and this on a daily basis, more then once a day.
So I do not think the app could be stopped because of background activity … but who knows, you are the developer.

My Assumption would be more, that Kurviger couldn’t work with such a big data amount without saving.

6

Android can and will stop an app at anytime if Android thinks this is in the best interest of the user or the device.

If the app suddenly stops workin in the background this is usually the reason. You can make this less likely to happen by explicitly remove any battery optimization and similar features from Kurviger.

Unfortunately I can’t help with this particular device. I don’t have any experience with the manufacturer.

This could be possible as we are using resources like the local storage and if this is not available, maybe there was an issue :thinking:.