Revision history [back]

Occasionally aliendalvik can not start after being stopped until device reboot. When it happens any attempt to run android app shows an app cover with rotating progress circle which disappears after around a minute.

I tried to track down the issue and it turns out that /lib/systemd/system/aliendalvik.service has ExecStartPre=/system/script/alien_start_guard.sh and the latter script waits until file /run/user/100000/alien_ready_to_start.appears. I don't know why, but occasionally this file disappears during runtime (might be related to to enabling airplane mode). Therefore here is workaround for the issue: touch $XDG_RUNTIME_DIR/alien_ready_to_start After creating missing file aliendalvik starts and works just fine.

I notice this issue at least since 2015-12-21 and is still happens occasionally in 2.0.1.11 (Taalojärvi). And I'm not the only one who have this issue.

P.S.: this looks like an attempt to enforce specific order of running services implemented the wrong way. Systemd has neat way to specify service dependencies, why it is not used?

Occasionally aliendalvik can not start after being stopped until device reboot. When it happens any attempt to run android app shows an app cover with rotating progress circle which disappears after around a minute.

I tried to track down the issue and it turns out that /lib/systemd/system/aliendalvik.service has ExecStartPre=/system/script/alien_start_guard.sh and the latter script waits until file /run/user/100000/alien_ready_to_start.appears. I don't know why, but occasionally this file disappears during runtime (might be related to to enabling airplane mode). Therefore here is workaround for the issue: touch $XDG_RUNTIME_DIR/alien_ready_to_start After creating missing file aliendalvik starts and works just fine.

I notice this issue at least since 2015-12-21 and is still happens occasionally in 2.0.1.11 (Taalojärvi). And I'm not the only one who have this issue.

P.S.: this looks like an attempt to enforce specific order of running services implemented the wrong way. Systemd has neat way to specify service dependencies, why it is not used?

Occasionally aliendalvik can not start after being stopped until device reboot. When it happens any attempt to run android app shows an app cover with rotating progress circle which disappears after around a minute.

I tried to track down the issue and it turns out that /lib/systemd/system/aliendalvik.service has ExecStartPre=/system/script/alien_start_guard.sh and the latter script waits until file /run/user/100000/alien_ready_to_start.appears. appears. I don't know why, but occasionally this file disappears during runtime (might be related to to enabling airplane mode). Therefore here is workaround for the issue: touch $XDG_RUNTIME_DIR/alien_ready_to_start After creating missing file aliendalvik starts and works just fine.

I notice this issue at least since 2015-12-21 and is still happens occasionally in 2.0.1.11 (Taalojärvi). And I'm not the only one who have this issue.

P.S.: this looks like an attempt to enforce specific order of running services implemented the wrong way. Systemd has neat way to specify service dependencies, why it is not used?

Occasionally aliendalvik can not start after being stopped until device reboot. When it happens any attempt to run android app shows an app cover with rotating progress circle which disappears after around a minute.

I tried to track down the issue and it turns out that /lib/systemd/system/aliendalvik.service has ExecStartPre=/system/script/alien_start_guard.sh and the latter script waits until file /run/user/100000/alien_ready_to_start appears. I don't know why, but occasionally this file disappears during runtime (might be related to to enabling airplane mode). Therefore here is workaround for the issue: touch $XDG_RUNTIME_DIR/alien_ready_to_start After creating missing file aliendalvik starts and works just fine.

I notice this issue at least since 2015-12-21 and is still happens occasionally in 2.0.1.11 (Taalojärvi). And I'm not the only one who have this issue.

P.S.: this looks like an attempt to enforce specific order of running services implemented the wrong way. Systemd has neat way to specify service dependencies, why it is not used?

Update 2016-08-08: I tried to narrow down circumstances that leads to disappearing of $XDG_RUNTIME_DIR/alien_ready_to_start file and I don't see any specific triggering factor. Today this file disappeared a couple of hours before my morning wake up time. My Jolla device was in airplane mode, screen off, nobody was interacting with it. I woke for a bit around that time and probably turned screen on for a couple of seconds (without unlocking the device) just to check current time.