Revision history [back]
 | 1 | initial version | posted 2019-12-13 13:17:52 +0200  |
aliendalvik 3.2.1
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/<my dir=""> but I removed all the files and directories (I hope) which could cause this.
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
| | 2 | No.2 Revision |
aliendalvik 3.2.1
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/<my dir=""> /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
| | 3 | No.3 Revision |
aliendalvik 3.2.1
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
| | 4 | No.4 Revision |
[bug,3.2.1] aliendalvik 3.2.1can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
| | 5 | No.5 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have X.eria XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
| | 6 | No.6 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have X.eria Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
| | 7 | No.7 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
Affter 5 more minutes the service file status looks like this:
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-12-13 14:25:47 CET; 7s ago
Process: 30260 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 28423 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 28790 ExecStart=/usr/bin/start-aliendalvik.sh (code=exited, status=1/FAILURE)
Process: 28787 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 28790 (code=exited, status=1/FAILURE)
Dec 13 14:25:47 Sailfish systemd[1]: Failed to start Alien Dalvik.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Unit entered failed state.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Failed with result 'exit-code'.
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
| | 8 | No.8 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
Affter 5 more minutes the service file status looks like this:
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-12-13 14:25:47 CET; 7s ago
Process: 30260 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 28423 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 28790 ExecStart=/usr/bin/start-aliendalvik.sh (code=exited, status=1/FAILURE)
Process: 28787 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 28790 (code=exited, status=1/FAILURE)
Dec 13 14:25:47 Sailfish systemd[1]: Failed to start Alien Dalvik.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Unit entered failed state.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Failed with result 'exit-code'.
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
EDIT:
Adding log snippet during run of systemctl restart aliendalvik.service.
cat ./journal.log | egrep 'alien|dalvik' > journal-aliendalvik.log
| | 9 | No.9 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
Affter 5 more minutes the service file status looks like this:
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-12-13 14:25:47 CET; 7s ago
Process: 30260 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 28423 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 28790 ExecStart=/usr/bin/start-aliendalvik.sh (code=exited, status=1/FAILURE)
Process: 28787 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 28790 (code=exited, status=1/FAILURE)
Dec 13 14:25:47 Sailfish systemd[1]: Failed to start Alien Dalvik.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Unit entered failed state.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Failed with result 'exit-code'.
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
EDIT:
EDIT 1:
Adding log snippet during run of systemctl restart aliendalvik.service.
cat ./journal.log | egrep 'alien|dalvik' > journal-aliendalvik.log
EDIT 2: I see problem with alienaudio.service in the logs. Again not sure if that is important...
Dec 13 14:55:45 Sailfish alienaudioservice[7448]: [AlienAudioService] ERROR: Failed to add AlienAudioService (1805328)
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Unit entered failed state.
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Failed with result 'exit-code'.
[root@Sailfish nemo]# systemctl status -l alienaudio
● alienaudio.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
| | 10 | No.10 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
Affter 5 more minutes the service file status looks like this:
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-12-13 14:25:47 CET; 7s ago
Process: 30260 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 28423 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 28790 ExecStart=/usr/bin/start-aliendalvik.sh (code=exited, status=1/FAILURE)
Process: 28787 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 28790 (code=exited, status=1/FAILURE)
Dec 13 14:25:47 Sailfish systemd[1]: Failed to start Alien Dalvik.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Unit entered failed state.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Failed with result 'exit-code'.
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
EDIT 1:
Adding log snippet during run of systemctl restart aliendalvik.service.
cat ./journal.log | egrep 'alien|dalvik' > journal-aliendalvik.log
EDIT 2: I see problem with alienaudio.service in the logs. Again not sure if that is important...
Dec 13 14:55:45 Sailfish alienaudioservice[7448]: [AlienAudioService] ERROR: Failed to add AlienAudioService (1805328)
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Unit entered failed state.
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Failed with result 'exit-code'.
[root@Sailfish nemo]# systemctl status -l alienaudio
● alienaudio.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
EDIT 3: Seems like a plenty of information missing in the snippet log. Adding complete log during the android support start by UI:
| | 11 | No.11 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
Affter 5 more minutes the service file status looks like this:
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-12-13 14:25:47 CET; 7s ago
Process: 30260 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 28423 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 28790 ExecStart=/usr/bin/start-aliendalvik.sh (code=exited, status=1/FAILURE)
Process: 28787 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 28790 (code=exited, status=1/FAILURE)
Dec 13 14:25:47 Sailfish systemd[1]: Failed to start Alien Dalvik.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Unit entered failed state.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Failed with result 'exit-code'.
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
EDIT 1:
Adding log snippet during run of systemctl restart aliendalvik.service.
cat ./journal.log | egrep 'alien|dalvik' > journal-aliendalvik.log
EDIT 2: I see problem with alienaudio.service in the logs. Again not sure if that is important...
Dec 13 14:55:45 Sailfish alienaudioservice[7448]: [AlienAudioService] ERROR: Failed to add AlienAudioService (1805328)
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Unit entered failed state.
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Failed with result 'exit-code'.
[root@Sailfish nemo]# systemctl status -l alienaudio
● alienaudio.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
EDIT 3: Seems like a plenty of information missing in the snippet log. Adding complete log during the android support start by UI:
EDIT 4: I found out that I'm not able to connect sdcard for some reason. It seems to me that I will end up with factory reset. :(
| | 12 | No.12 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
Affter 5 more minutes the service file status looks like this:
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-12-13 14:25:47 CET; 7s ago
Process: 30260 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 28423 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 28790 ExecStart=/usr/bin/start-aliendalvik.sh (code=exited, status=1/FAILURE)
Process: 28787 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 28790 (code=exited, status=1/FAILURE)
Dec 13 14:25:47 Sailfish systemd[1]: Failed to start Alien Dalvik.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Unit entered failed state.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Failed with result 'exit-code'.
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
EDIT 1:
Adding log snippet during run of systemctl restart aliendalvik.service.
cat ./journal.log | egrep 'alien|dalvik' > journal-aliendalvik.log
EDIT 2: I see problem with alienaudio.service in the logs. Again not sure if that is important...
Dec 13 14:55:45 Sailfish alienaudioservice[7448]: [AlienAudioService] ERROR: Failed to add AlienAudioService (1805328)
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Unit entered failed state.
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Failed with result 'exit-code'.
[root@Sailfish nemo]# systemctl status -l alienaudio
● alienaudio.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
EDIT 3: Seems like a plenty of information missing in the snippet log. Adding complete log during the android support start by UI:
EDIT 4: I found out that I'm not able to connect sdcard for some reason. It seems to me that I will end up with factory reset. :(
EDIT 5: My SFOS is really broken. My calls are completely silent and the other side don't hear me too. This is not just android problem at all. My internet, browser and SFOS apps seems to be working.
| | 13 | No.13 Revision |
[bug,3.2.1] aliendalvik can't be started
Hello everyone,
I'm not able to start aliendalvik service since the 3.2.1 Nuuksio update. Update seems to went well but I'm getting plenty of errors in journal when I try to start the aliendalvik. Starting it from UI results in the inactive Start and Stop buttons (like it's trying to start but nothing happens). Rebooting phone does not helping. I did bind mount between android layer and /home/nemo/my_dir but I removed all the files and directories (I hope) which could cause this.
I have Xperia XA2 Ultra - Dual SIM
My aliendalvik.service is failing:
[root@Sailfish nemo]# systemctl restart aliendalvik.service
Job for aliendalvik.service failed because the control process exited with error code. See "systemctl status aliendalvik.service" and "journalctl -xe" for details.
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (start) since Fri 2019-12-13 12:06:32 CET; 6s ago
Process: 547 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 9519 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 940 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 944 (start-aliendalv)
Memory: 944.0K
CPU: 955ms
CGroup: /system.slice/aliendalvik.service
├─ 944 /bin/bash /usr/bin/start-aliendalvik.sh
├─ 994 bindfs --chmod-ignore --chown-ignore --chgrp-ignore --map=100000/1023:@100000/@1023 --perms=755 /home/nemo /home/.nemo_bind
├─1231 /bin/sh /bin/systemctl-user start alienkeyboard.service
└─1252 ps -o user= 3739
Dec 13 12:06:32 Sailfish systemd[1]: Starting Alien Dalvik...
Dec 13 12:06:36 Sailfish su[1171]: pam_systemd(su-l:session): Using 600s D-Bus method call timeout
Dec 13 12:06:37 Sailfish start-aliendalvik.sh[944]: Last login: Fri Dec 13 12:05:54 CET 2019
Affter 5 more minutes the service file status looks like this:
[root@Sailfish nemo]# systemctl status -l aliendalvik.service
● aliendalvik.service - Alien Dalvik
Loaded: loaded (/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Fri 2019-12-13 14:25:47 CET; 7s ago
Process: 30260 ExecStopPost=/usr/bin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 28423 ExecStartPost=/bin/systemctl try-restart lxc-net.service (code=exited, status=0/SUCCESS)
Process: 28790 ExecStart=/usr/bin/start-aliendalvik.sh (code=exited, status=1/FAILURE)
Process: 28787 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=203/EXEC)
Main PID: 28790 (code=exited, status=1/FAILURE)
Dec 13 14:25:47 Sailfish systemd[1]: Failed to start Alien Dalvik.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Unit entered failed state.
Dec 13 14:25:47 Sailfish systemd[1]: aliendalvik.service: Failed with result 'exit-code'.
I also found that I don't have aliendalvik preinit not sure if that is expected or not:
[root@Sailfish nemo]# more /usr/bin/start-aliendalvik-preinit.sh
more: stat of /usr/bin/start-aliendalvik-preinit.sh failed: No such file or directory
If you need any more information please ask. I'm missing plenty of functionality without the Android app support.
EDIT 1:
Adding log snippet during run of systemctl restart aliendalvik.service.
cat ./journal.log | egrep 'alien|dalvik' > journal-aliendalvik.log
EDIT 2: I see problem with alienaudio.service in the logs. Again not sure if that is important...
Dec 13 14:55:45 Sailfish alienaudioservice[7448]: [AlienAudioService] ERROR: Failed to add AlienAudioService (1805328)
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Unit entered failed state.
Dec 13 14:55:45 Sailfish systemd[3739]: alienaudio.service: Failed with result 'exit-code'.
[root@Sailfish nemo]# systemctl status -l alienaudio
● alienaudio.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
EDIT 3: Seems like a plenty of information missing in the snippet log. Adding complete log during the android support start by UI:
EDIT 4: I found out that I'm not able to connect sdcard for some reason. It seems to me that I will end up with factory reset. :(
EDIT 5: My SFOS is really broken. My calls are completely silent and the other side don't hear me too. This is not just android problem at all. My internet, browser and SFOS apps seems to be working.
EDIT 6: I did factory reset and update to a new version and everything seems fixed. Even thought I experienced silenced phone calls again but it was resolved by phone reboot. If that will happen again I'll create another issue.
For now, closing this bug because it really seems like something went wrong specifically on my settings/device and I'm not able to reproduce this.