If the Android container is not running, many parts of Ubuntu Touch will not work. Run this command to check on the container’s status:

sudolxc-info-nandroid

If you get output similar to the following, the Android container is running and you can move on to the next troubleshooting step:

Name:androidState:RUNNINGPID:1194IP:10.15.19.82

If you do not get State:RUNNING, the container is stopped. You can run sudostartlxc-android-config to attempt to start it. If the container does not start after that, you can run sudolxc-start-nandroid-F to get a more detailed log of why it has failed.

If some partitions used for Android drivers are not mounted, the container may start but not work correctly.

To check the mounted Android partitions, run ls/android. At least the following folders should be contained within:

datasystemfirmwarepersist

If any of these are missing, run dmesg to get the kernel log. Mounting Android partitions will start after the following line:

initrd:checkingfstab[...]foradditionalmountpoints

Try to diagnose and fix any mounting errors that you find in the log for the partitions listed above.

Note

Some devices have a vendor partition that contains proprietary libraries and executables required to run Android. If your device has this partition, make sure that it is mounted in addition to the others listed above.

Use scp or a similar program to copy the usc.log, usc-gdb.log, and usc-logcat.log files from phablet’s home folder to your computer. Then, post the content of these files to paste.ubuntu.com, Pastebin, GitHub Gists, or a similar service so the people helping you can view them easily.

Sometimes processes will hang for a very long time and then abort or segfault. The reason for the hang is apport, which attempts to collect useful information about the crash before allowing the program to stop.

If you don’t need apport’s information and would rather have the programs crash faster while troubleshooting, issue the following commands: