Revision history [back]

Step to reproduce on my Jolla C:

1. Press the power button to power off the display (I have no device lock code set)
2. SSH into the phone, as root.
3. Type systemctl restart aliendalvik.
4. The command stalls indefinitely (does nothing and does not terminate).
5. Press the power button once more to wake up the phone
6. Now the command terminates and I get the command prompt again.

This seems unusual. If I restart some other service, for instance bluetooth, the command completes immediately.

Step to reproduce on my Jolla C:

1. Press the power button to power off the display (I have no device lock code set)
2. SSH into the phone, as root.
3. Type systemctl restart aliendalvik.

Expected: 4. The command completes almost immediately and restarts the Android layer.

Observed: 4. The command stalls indefinitely (does nothing and does not terminate).

This seems unusual. If I restart some other service, for instance bluetooth, the command completes immediately.

Step to reproduce on my Jolla C:

1. Press the power button to power off the display (I have no device lock code set)
2. SSH into the phone, as root.
3. Type systemctl restart aliendalvik.

Expected: 4. Expected:

1. The command completes almost immediately and restarts the Android layer.

Observed:

Step to reproduce on my Jolla C:

1. Press the power button to power off the display (I have no device lock code set)
2. SSH into the phone, as root.
3. Type systemctl restart aliendalvik.

Expected:

Observed:

This seems unusual. If I restart some other service, for instance bluetooth, the command completes immediately.

I stumbled upon this behavior while looking for workarounds for Whatsapp messages arriving late and the web client web.whatsapp.com not working -- it seems that restarting the Android layer "wakes up" the Whatsapp app.