Andor's Trail

Now I have the described behavior also with English version.

I just realized that I have two Android 11 devices available so I did some testing:

Device 1: Stock Samsung Galaxy A40 (unfortunately no A50 that could be used to try and duplicate Lupo's issues)

Device 2: Samsung Galaxy S5 running LineagOS 18.1


Device 1:

AT hasn't been installed before, so it is a clean first install of the apk, no old savegames.
I could start a new game, save, load and continue it after restart, no observerd issues during ~20min playing.

I could not access the folder with the savegames using the Samsung supplied file manager nor using ghost commander.
So I tried total commander and could at least read and copy the savegames to another folder but could *not* write files *to* the savegames folder.
So no possibility to restore savegame backups...

I tried accessing the phone via USB from my PC but with no luck. (PC didn't even recognize it, although file transfer had been selected as standard USB configuration in developer settings).

So I tried to transfer a savegame from my normally used phone (still running android 9) over Bluetooth.
This failed and gave a "memory error" message on the device 1.
So tried to rename the savegame to "savegame1.bak" - and this actually worked... (no problems in the other direction 11->9, so maybe a new annoying android 11 "feature")


Device 2:

AT has already been installed on this device before (but not from google playstore but from fdroid).
Trying to install the beta-apk did *not* work. (First I got the "Are you sure to update"-message, but installation afterwards broke off with "App has not been installed")
Is the supplied beta-apk only applicable to update playstore-installs, or may the install problem be connected with the latest fdroid version still being 0.7.13.1 instead of 0.7.13.2?

I also tried to transmit a savegame from my old android 9 device to device 2, but using the unmodified filename would also not transmit.

And for this device it did not work to rename the savegame to "savegame1.bak". I got a "The content is not supported" error-message on the sender side.

What finally did work was adding a .zip file extension.
It seems that Android 11 does some weird stuff based on guessed file content type. I really don't like that, transmission protocolls should be transparent...

I deleted AT an also all related files. Afterwords I installed the beta again. Same behavior as described before. After a while it crashed and I have to start from last save. Thre is no warning or anything special that happened before crash. Smartphone asked to set AT to sleep because of crashes it seems to use to much accu.

Schnatterfleck wrote: ↑Sun Sep 26, 2021 12:41 pm Is the supplied beta-apk only applicable to update playstore-installs, or may the install problem be connected with the latest fdroid version still being 0.7.13.1 instead of 0.7.13.2?

All Android apks have a unique signature. If the signature matches, you can install a new version to replace an old version. However, the fdroid signature will not match the Playstore signature, so to go from one to the other you must uninstall the current copy of AT. That will not delete any of the savegame data, it will just uninstall the app.

Thanks to everyone for their work testing this. It is extremely valuable to us.