Simon Fels

@Fuseteam I've added another new version of the snap to the edge channel (revision 108) which adds additional logging functionality at early container startup. Please try again and collect log...

@Fuseteam Can you me the favor and also attach the kernel log the collect-bug-info scripts generates?

@Fuseteam Thanks! The invalid PID for SGICHLD is not a problem. The actual problem here is ``` lxc 20180612041921.140 DEBUG lxc_start - start.c:signal_handler:326 - Container init process 30354 exited. lxc...

Looked into your kernel log now and it looks like you have a pretty old CPU (from 2011) `AMD A8-3520M`. We had problems with older CPUs not supporting all features...

@Fuseteam Can you give me the output of `$ cat /proc/cpuinfo`?

Created https://github.com/anbox/anbox/pull/765 to easier detect these situations which will be followed by a more explicit check when we start the container to prevent people from running into this situation.

@Fuseteam As I feared, you miss support for SSE 4.1/4.2 and SSSE 3 which are mandatory for Android (see https://developer.android.com/ndk/guides/abis).

@Fuseteam One of the next versions. Still need to write the code for that but we will show the user a proper error message.

@Fuseteam The term `Intel Core Duo 2` covers quite a few different models and they don't support all the same set of instructions. Check https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors

> This too indicates that there is some sort of problem with processes/IPC/thread scheduling. The issues you outlined above about thread/scheduler issues are because the container used for the Android...