android apps do not start dalvik [released]

This also happens with my jolla, on 2.0.0.10 (Saimaa), can't even manually switch on aliendalvik, just have to reboot, seems at aliendalvik a startup flag is missing as alien_start_guard.sh is waiting for that, haven't found an answer yet.Trying "sudo systemctl stop aliendalvik.service" as command in situations, you do need sudo installed see here for more on that. Or use Alien dalvik stop from Schutlrman, in Warehous, and have that run by situations, still testing here

i am using schturmans app to stop dalvik overnight. the issue is: i need to start dalvik manually again. it wont get started by an Android app anymore as it did untill recently

I tried the following to make sure that at least in general, starting an Android app does start Alien Dalvik once it has been shut down manually (on 2.0.1.7):

1. Stop Alien Dalvik from system settings (Sailfish Utilities)
2. (Wait a bit. I know this is a very Star Trek TOS way of dealing with computers, but it makes me feel more secure.)
3. Start any Android app. The startup animation appears instantly on the home screen.
4. The startup animation disappears again and you stare at the screen.
5. After a while, the application appears.

I think that with 2.0.1.7, the time I spend on step 4 has increased. But it still works.

The only thing I do differently from pawel is that I stop Alien Dalvik manually once in a while and do not use Situations or a similar application. Maybe those who experience this issue can check if it also appears when they stop Android support via system settings? It might be something with the tools you use, not that Sailfish doesn't start Alien Dalvik any more in general.