Tracking alien dalvik crashes

asked 2016-05-10 21:20:50 +0200

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2018-12-03 21:52:10 +0200

Tanghus gravatar image

I've been having crashes of the alien-dalvik runtime since the last 2 updates (both pre-releases)

I can't figure out the reason for the crashes.

Is there any way to trace/track the reason for the crash? Any verbose output of alien-dalvik maybe or something in one of the many journals available on the phone?

I'm a little bit at a loss here. I've got no clue where to look and the normal restart via eventsview shortcut doesn't work.

I can start alien-dalvik again via the settings app or via two commands as root in terminal:

systemctl-user restart alien-pre-start
systemctl start aliendalvik.service

However this is no permanent solution as alien-dalvik will crash again after a while.

I have to restart the runtime each time I take out my phone about 6 times a day.

I'd appreciate any input here. I can't stand this behaviour any longer ;)



edit retag flag offensive close delete


So far I got some help on IRC

checking out:

chroot /opt/alien /system/bin/logcat

as root in terminal or a ssh session could point out if something is broken on the alien-dalvik site or if it's just OOM kicking in.

I haven't really tried to trace it any further by now but I helped myself with another trick:



I edited the file


and changed dalvik.vm.heapgrowthlimit to 128


That helped a little.

Additionally I installed Sailcron from openrepos and set up two cronjobs as root:

systemctl start aliendalvik.service

to restart the alien-dalvik runtime

and an sh command to a dropcache script (bit of a legacy now) I got from here:

to run every 15 minutes, so the windows in which I missed some messages got shorter.

MoritzJT ( 2016-05-29 22:57:08 +0200 )edit