Android: don't archive cards on an empty database

[Tialae]

The Android version of Mnemosyne does not work on Samsung Galaxy Tab A (2016) SM-T280, Android 5.1.1.

Mnemosyne only shows the top menu sometimes after loading, sometimes not. It seems to be that minimising it and bringing it back up means the top menu disappears and cannot be restored. Once the glitch occurs, dragging the top bar down just brings down the normal Android menu (wifi, etc.) and it is impossible to bring the top menu down again.

When it does work, it keeps disappearing too quickly to be easily used.

None of the context menu buttons do anything when pressed, except Replay Sound which crashes the app.

It seems like there is no way to add or sync new cards. Overall, the app does not appear to function at all.

[Peter Bienstman (peter-bienstman)]

The menu not showing anymore after you minimise the app is a known issue on my todo list.

That none of the menu buttons work is strange. Can you uninstall the app, delete /sdcard/Mnemosyne and reinstall? This has been know to fix some strange issues.

Adding cards directly on the phone is not supported and not really on my short-term todo list, I'm afraid...

[Tialae (tialae)]

Following your instructions stops the issue from recurring, thank you.

I can reproduce it, however, by pressing the Home button on first start-up, when the "About to archive old logs..." appears. Mnemosyne crashes and then subsequent runs have the behaviour I described above.

That must have been what I did the first time, because I didn't know what to do about the old logs. It does seem a strange thing to show a new user who doesn't have any old logs.

[Peter Bienstman (peter-bienstman)]

Please don't press the home button then. After all, Mnemosyne explicitly tells you leave the app in the foreground :-)

Anyway, I'll try to eliminate that this steps runs for an empty database.

[Tialae (tialae)]

It does say to leave the app in the foreground but it doesn't say it will error if closed. One's assumption is that it will just pause what it is doing. It also has a "proceed" button, indicating that the process has not yet begun so the waiting doesn't apply yet.

Waiting for 10 or more minutes also seems a bit of an unreasonable request for someone who is on-the-go. One might have 3 minutes spare to do some cards, then it asks one to wait for possibily over 10 minutes, so a common reaction would be to decide to do something else for the three minutes, thus pressing the Home button.

I am very thankful for the work done on this so far and I hope my feedback can help further improve the software. In the meantime, I shall try not to commit user error :)

[Peter Bienstman (peter-bienstman)]

10 minutes is worst case estimate on a huge database, for a smaller one / empty one it should be much much quicker.

Thanks for the feedback, I will act on it!