@TheVancedGamer
What does the maintainer think? Any idea how that debug kernel got installed?

@wynn1212
Thanks! You might just have kept me from bricking my phone during the next installation attempt.

@Keneda
Thanks a lot for your explanations. So probably I caused any occurring problem myself. However, I'm still curious how that debug kernel came into play.

Are you sure FP4 comes with anti rollback protection ?

From what I read in the /e/OS installation instructions, yes:

Caution: The FP4 comes with an anti-rollback feature. (...) If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device.

But I also read the fairphone support page, and according to it, flashing with fastboot (downgrading included) should be no issue.

(Maybe the /e/OS installation script doesn't use fastboot flashing, but OTA Sideload?)

@arubislander said in Install with ubports installer resulted in having a debug kernel:

So what possibly happened here, is that the kernel was compiled with debug flags set.

OP's best bet is to het in touch with the porter of the FP4.

Ok... How do I find out who this is and how to reach him/her?

Thanks for your replies, all of you!

@Keneda Actually, no... While my FP4 came with Android 12, during installation I noticed that on the device page Android 11 was required; but I thought it might work as well with a later version of Android. (And I wouldn't have known how to downgrade to Android 11.)

How can the version of the former OS, which is erased anyway, affect the installation of Ubuntu Touch? I only know of an Android rollback prevention concerning the security level of Android.

Two weeks ago I installed Ubuntu Touch on FP4 using the ubports installer for MacOS. It didn't go smoothly, because after the first step the installer lost contact to the phone (no device visible in fastboot mode anymore) and only after exchanging the Apple usb cable for one sold by Google it worked again. Later in the process the installer printed an error message saying a logical volume could not be deleted, but ignoring this seemed to go fine. I also tried to relock the bootloader, but it resulted in a bootloop, so I unlocked it again.

Then I had a look around, enjoying the smooth look and feel of Lomiri, but when I used the terminal to look at the dmesg output, I saw this:

NOTICE
trace_printk() being used. Allocating extra memory. This means that this is a DEBUG kernel and it is unsafe for production use. If you see this message and you are not debugging the kernel, report this immediately to your vendor!

Does Ubuntu Touch regularly use a debug kernel? If not, has anyone an idea what happened?