Normally when the Nemo rootFS is extracted to device partition, all the files needed to boot it up (including the most recent kernel at the time of package creation) are set to correct locations. This is why ubiboot refers to the Nemo kernel as "/boot/Nemo/boot/bzImage", which in turn is the symlink inside Nemo to the vmlinuz-2.6.32.xxxxxxxx in the same directory. It just works, out-of-the-box. One thing, when you say the device "turns off after Nemo boot", did you check that it did not actually start Nemo, but without GUI? If you plug the device in USB, if the IP interface appears on your computer, you can configure, for example 192.168.0.100 as the IP address there and SSH as root to your Nemo in 192.168.2.15 If that happens, rebooting the device should get you GUI on the next boot. BTW, can you check the ubiboot logs on Harmattan side /var/log/ubiboot.log and /var/log/ubiboot.dmesg. From there you can see if there was some problem in the kernel selection.
Another oddity report: I already mentioned about missing UI bug when device is charging in actdead mode and an alarm is triggered. No chance to stop/snooze Today I did not get any alarm at all. Reason (confirmed) was that I did shut down device from Nemo. Like: Nemo booted, shut down, device off > no alarm With Nidroid it was a bit different (not yet confirmed): boot nit shut down, device off, 2s alarm rin and then device did shut down on its own again This would need a lot of testing. Just wanted to inform you to take care that you boot to jarmattan when you have the need for reliable alarm (wake ups)! Maybe we can add a section to wiki to list all that stuff?