Messages

Hello,

is there more info about this?
We tested
-using on-and offline maps (no difference),
-no wps (no difference)
-no active kml (no difference)
-only points and tracks (no difference)
-all settings default (except screen allways on!)
rollback to 3.54.3 seems to solve the 'crash' problem (bus still a pretty high memory usage).

@balloni55 depending on device:
Developer settings, running services;
you can try to install an older version and see if you experience the same as us. I think vs 4.3 is somthing like our working version

We don't use geocaching

I am also not sure if the problem started with 3.43, i only know that the newer versions give problems to us (3.6X defenitly)

Hello,
the problem for us is the size off the database at the end. We use a lot off tracks and sometimes we load +- 1000 tracks at once. This gives some problem with the size off the  tracks database. Idealy we would like to be able to disable the generation because off the cpu load when generating these tracks and the sql lite db sizes.