android apps do not start dalvik [released]
i do stop dalvik every night with situations. since a week i have to start dalvik manually, else android apps do not start.
it did occure for the first time on 2.0.0.1, the update to 2.0.1.7 did not fix it. i am aware that there are few similar questions, but they are 1 to 2 years old, concerning version 1.0, 1.1 etc
uodate: 2016-07-39: did not occure.since months, clising it.
android supprtort at boot is enabled
its not an issue after reboot. it s an issue after you stop dalvik manually
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
filipb92 ( 2016-01-24 11:56:35 +0200 )editi 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
pawel ( 2016-01-24 12:49:14 +0200 )editI 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):
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.
ossi1967 ( 2016-01-24 21:00:38 +0200 )edit