Hi,
some weeks ago I run into the same old thing: sqlite db error when saving a track.
I tried the usual things: delete old db file, renamed backup ... no change - copied my OM directories, deleted the app and installed for new ... no change, tried to copy elder backups in ... no change...
Then I had the idea to look into the system directories, whether OM has data here and alas ... there is a /Android/data/com.orux.oruxmapsDonate with 2 subdirs and some files in them. I deleted all files - not the directory and the subdirs! - started OM again and no sql error any more! Don't understand at least, why, as the files were named something with "cache" (which I emptied as a first try) and a few of them were just empty, size 0... but now it runs and I can add saved gpx tracks and can do track logging, delete tracks... as it should...
just my 2 ct
some weeks ago I run into the same old thing: sqlite db error when saving a track.
I tried the usual things: delete old db file, renamed backup ... no change - copied my OM directories, deleted the app and installed for new ... no change, tried to copy elder backups in ... no change...
Then I had the idea to look into the system directories, whether OM has data here and alas ... there is a /Android/data/com.orux.oruxmapsDonate with 2 subdirs and some files in them. I deleted all files - not the directory and the subdirs! - started OM again and no sql error any more! Don't understand at least, why, as the files were named something with "cache" (which I emptied as a first try) and a few of them were just empty, size 0... but now it runs and I can add saved gpx tracks and can do track logging, delete tracks... as it should...
just my 2 ct