every startup fails at filesystem initialising...

[ohgood]

I haven't changed the location of locus or it's directories since several updates ago. now, locus complains my filesystem is read only. the only way to fix this is to go into device administrators section and disallow then allow locus. then it will start normally.

this only started happening with the last two updates.

[Menion]

Hello,
does this happen also with update 3.32.1 (published maybe two hours ago)?

[ohgood]

Hello,
does this happen also with update 3.32.1 (published maybe two hours ago)?

yes in most recent also. I unmounted my sdcard and rebooted a few times to see if it was a sdcard issue. I'll try again this evening.

[Tom]

The same happens to me on a Samsung A3 2017 (Oreo). I'm also using 3.32.1.

[Menion]

Hmm even with the latest version? And checkbox at the bottom with "Don't ask" make no difference, you always see the exactly same screen?

[Tom]

And checkbox at the bottom with "Don't ask" make no difference, you always see the exactly same screen?

Then the message screen is gone. But of course it leaves a bad feeling.

[ohgood]

Hmm even with the latest version? And checkbox at the bottom with "Don't ask" make no difference, you always see the exactly same screen?

I couldn't use my locus database on the sdcard anymore, had to switch to the internal (I'm guessing at this point) before I could select "do not ask again".

I'm guessing it could be related to startup from sdcard ?

[Menion]

You were able to use SD card for point/track database before?? Rooted device? Android 4.1 or 4.2?
Otherwise Locus Map is unable to write into database placed on SD card!

[ohgood]

You were able to use SD card for point/track database before?? Rooted device? Android 4.1 or 4.2?
Otherwise Locus Map is unable to write into database placed on SD card!

this was on a Android 5.1 device. update 3.32.2 send, no more startup errors anymore!

thank you!

[Menion]

Perfect, glad to hear it!