[4.0.1.45] - Alien Dalvik Not Starting

Bug Reports
,
#1

REPRODUCIBILITY (% or how often): 100%
BUILD ID = OS VERSION (Settings > About product): 4.0.1.45
HARDWARE (Jolla1, Tablet, XA2,…): XA2 Single Sim
UI LANGUAGE: English
REGRESSION: (compared to previous public release: Yes, No, ?):

DESCRIPTION:

Similar issue to this post Android Support/Alien Dalvik no longer working [3.4.0.22]
After updating to 4.0.1.45, Android Support stopped working. All buttons greyed out.

PRECONDITIONS:

STEPS TO REPRODUCE:

EXPECTED RESULT:

ACTUAL RESULT:

ADDITIONAL INFORMATION:

(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

[4.0.1.15] AlienDalvik stop working and doesn't start (Solved removing Android Data)
#2

Did you try this:

devel-su
systemctl stop aliendalvik
rm -rf /home/.android/data/system/package_cache/1/Alien*
systemctl start aliendalvik
exit

That was proposed as solution for 3.4 by @jovirkku, for me it worked.

#3

Try waiting a while. The upgrade to Android 9 is probably requiring applications upgrade by ART (i. e. recompilation).

After upgrading 4.x, no more Android Support
#4

Tried that but it does not help at least in my case.
journalctl -xe
https://pastebin.com/d6KNJUD7

Edit:
Finally figured out what was the problem. I had theme pack support installed (not in use) which caused aliendalvik to fail.

devel-su
pkcon remove harbour-themepacksupport
systemctl start aliendalvik

fixed my issue

I found issue by looking systemctl status aliendalvik output which showed failed ExexStartPost script Process: 22161 ExecStartPost=/usr/share/harbour-themepacksupport/service/apkicons.sh (code=exited, status=2)

4 Likes
#5

I removed busybox-symlinks-bash and made sure gnu-bash is installed.

The aliendalvik systemd startup script pukes on some bashism when ash is used…

#6

I had this same problem and your solution worked for me! Thank you!

#7

Yes, multiple times. I tried everything in that thread.

#8

That was it. That solved it immediately. Thank you!

#9

Had same issue with Alien Dalvil not starting after upgrade to 4.0.1.45 and
pkcon remove harbour-themepacksupport
fixed it for me thanks!