@fhendrikx
I haven't seen much movement on this, though I would like to. I too have a p3 I'd like to use UT on.

Well Android 11 will be a problem, we currently do not have the support layer "Halium 11" up and working. We are currently struggling with 9 and 10. Of course @edenmutt you are invited to help doing groundbreaking works here, but it might not what you have expected for porting. A lot of low-level bugs, and you need to familiarize yourself with the architecture changes between 9 and 11 at least.

@actuday6418 soooo what happened?

@arubislander

This thread I started was aimed to get insight in the possible porting of the OnePlus Nord. As such I hadn't planned to discuss the differences between Pinephone and Librem 5.

And I shouldn't have posted my earlier comment, reading back I was wrong as I was referring to the binary blob for the Wi-Fi/Bluetooth issue still in the back of my mind. I'm sorry about that, the last thing I want is to keep any misconceptions alive. The last sentence has been striked through and apologies to @PINE64 are in place.

I remember that someone was working on support for the FP3 but all information was in the Halium Telegram group.
Does anyone know if things are still going on (I left Telegram for good and don't intend to return)?

@synnyg_r
If you flashed via script halium-install-standalone.sh dont forget to add argument with -p ut
halium-install-standalone.sh -p ut path/to/rootfs.tar.gz path/to/system.img

New day, new error ... 😕

[ 0.265849] i2c-msm-v2 75b7000.i2c: probing driver i2c-msm-v2
[ 0.265999] i2c-msm-v2 75b7000.i2c: error on clk_get(core_clk):-517
[ 0.266016] i2c-msm-v2 75b7000.i2c: error probe() failed with err:-517

https://paste.ubuntu.com/p/sv9dwMntH5/

@JCLemme Ok but then smth is really broken, I would suggest to start building a LineageOS tree from scratch, and get their recovery working. Or, use TWRP as recovery, try to boot boot.img from your build, let it crash and then go into TWRP, use adb and get /proc/last_kmsg if possible