After 4.1.0, 4.2.0 and 4.3.0 update aliendalvik no longer starts

REPRODUCIBILITY (% or how often): 100%
BUILD ID = OS VERSION (Settings > About product): 4.3.0.12
HARDWARE (XA2, X10, X10 II, …): Sony 10 Plus - Dual SIM
UI LANGUAGE: English
REGRESSION: (compared to previous public release: Yes, No, ?): 4.0 worked

DESCRIPTION:

After updating to the latest 4.3.0, aliendalvik doesnt start. Before updating phone to latest, the android part was working flawlessly. I didnt test it between the updates so I dont know if this has happened in some previous update or not. Within the GUI both buttons, Start and Stop are grayed out.

This is serious problem, without android app support I will have problems at job :frowning:

I need some solution/workaround to make it work, should I reflash the device? Whatever? Reinstalling Android App Support from Jolla Store (remove and install) didnt help =/

PRECONDITIONS:

/

STEPS TO REPRODUCE:

Updated the phone.

EXPECTED RESULT:

Aliendalvik should start.

ACTUAL RESULT:

Aliendalvik fails.

ADDITIONAL INFORMATION:

● aliendalvik.service - Alien Dalvik
Loaded: loaded (/usr/lib/systemd/system/aliendalvik.service; disabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/aliendalvik.service.d
└─01-prevent-start.conf
Active: failed (Result: exit-code) since Sun 2022-01-16 19:05:05 CET; 13s ago
Process: 11999 ExecStopPost=/usr/sbin/stop-aliendalvik.sh (code=exited, status=0/SUCCESS)
Process: 11997 ExecStopPost=/usr/libexec/lxc/lxc-net stop (code=exited, status=0/SUCCESS)
Process: 11971 ExecStartPost=/usr/sbin/alien-post-startup.sh (code=exited, status=20)
Process: 10135 ExecStart=/usr/sbin/start-aliendalvik.sh (code=killed, signal=TERM)
Process: 10130 ExecStartPre=/usr/libexec/lxc/lxc-net start (code=exited, status=0/SUCCESS)
Process: 10127 ExecStartPre=/usr/sbin/start-aliendalvik-preinit.sh (code=exited, status=0/SUCCESS)
Process: 10123 ExecStartPre=/usr/bin/start-aliendalvik-preinit.sh (code=exited, status=0/SUCCESS)
Main PID: 10135 (code=killed, signal=TERM)

Jan 16 19:05:05 xhal systemd[1]: aliendalvik.service: Service hold-off time over, scheduling restart.
Jan 16 19:05:05 xhal systemd[1]: aliendalvik.service: Start request repeated too quickly.
Jan 16 19:05:05 xhal systemd[1]: aliendalvik.service: Failed with result ‘exit-code’.

Only what I have found relevant in logs:
Jan 16 19:05:18 xhal systemd[1]: selinux: Unknown class service
Jan 16 19:05:26 xhal kernel: /home/abuild/rpmbuild/BUILD/kernel/sony/msm-4.9/kernel/drivers/char/adsprpc.c:1988:error: -512: 0 == (err = interrupted)
Jan 16 19:05:26 xhal kernel: /home/abuild/rpmbuild/BUILD/kernel/sony/msm-4.9/kernel/drivers/char/adsprpc.c:3420:error: -512: 0 == (err = fastrpc_internal_invoke(fl, fl->mode, 0, &p.inv))
interrupted)26 xhal kernel: /home/abuild/rpmbuild/BUILD/kernel/sony/msm-4.9/kernel/drivers/char/adsprpc.c:1988:error: -512: 0 == (err =–More–
Jan 16 19:05:26 xhal kernel: /home/abuild/rpmbuild/BUILD/kernel/sony/msm-4.9/kernel/drivers/char/adsprpc.c:3420:error: -512: 0 == (err = fastrpc_internal_invoke(fl, fl->mode, 0, &p.inv))


Jan 16 19:22:12 xhal healthd: battery l=54 v=3738 t=29.0 h=2 st=3 c=359 chg=
Jan 16 19:22:12 xhal ofonod[2930]: [gbinder] Service manager /dev/hwpuddlejumper has appeared
Jan 16 19:22:12 xhal init: Received control message ‘interface_start’ for ‘android.hardware.camera.provider@2.4::ICameraProvider/legacy/0’ from pid: 55 (/system/bin/hwservicemanager)
Jan 16 19:22:12 xhal init: Could not find ‘android.hardware.camera.provider@2.4::ICameraProvider/legacy/0’ for ctl.interface_start
Jan 16 19:22:12 xhal init: Received control message ‘interface_start’ for ‘android.hardware.camera.provider@2.4::ICameraProvider/legacy/0’ from pid: 55 (/system/bin/hwservicemanager)
Jan 16 19:22:12 xhal init: Could not find ‘android.hardware.camera.provider@2.4::ICameraProvider/legacy/0’ for ctl.interface_start
Jan 16 19:22:12 xhal init: Received control message ‘interface_start’ for ‘android.hardware.audio@5.0::IDevicesFactory/default’ from pid: 55 (/system/bin/hwservicemanager)
Jan 16 19:22:12 xhal init: Could not find ‘android.hardware.audio@5.0::IDevicesFactory/default’ for ctl.interface_start
icemanager)2:12 xhal init: Received control message ‘interface_start’ for ‘android.hardware.audio@4.0::IDevicesFactory/default’ from pid: 55 (/system/bin/hwserv–More–
/hwservicemanager)effect@5.0::IEffectsFactory/default’ from pid: 55 (/system/bin–More–
are.audio.effect@5.0::IEffectsFactory/default’ for ctl.interface_start
/hwservicemanager)effect@4.0::IEffectsFactory/default’ from pid: 55 (/system/bin–More–
are.audio.effect@4.0::IEffectsFactory/default’ for ctl.interface_start

AND

Jan 16 19:22:12 xhal systemd[5335]: selinux: Unknown class service
Jan 16 19:22:12 xhal systemd[5335]: selinux: Unknown class service
Jan 16 19:22:12 xhal systemd[5335]: selinux: Unknown class service
Jan 16 19:22:12 xhal systemd[5335]: selinux: Unknown class service

Had the same problems last update time . Reflashing is surely the fastest way.