Debug Halium

Reading kernel logs

To find out what happened during an unsuccessful boot you can check the kernel log files. These can usually be retrieved from /proc/last_kmsg after rebooting the device into another, working system. A precondition for this is that you have a system that you can successfully boot, such as TWRP.

  1. Boot your newly built image
  2. Wait for it to fail
  3. Reboot the device into the working system.
  4. Retrieve the kernel log with adb shell cat /proc/last_kmsg > ~/last_kmsg
  5. Read ~/last_kmsg and find out what went wrong

Add udev rules

Now that you’re logged in, you must create some udev rules to allow some tests to access your hardware. Run the following command, replacing [codename] with your device’s codename.:

cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/etc/udev/rules.d/70-[codename].rules

Now, reboot the device.


The hybris-boot image is based on work from the Sailfish OS and the Sailfish Hardware Adaptation Development Kit porting guide contains valuable tips.