how about trying: (halium 9) huawei_kiwi.xml: <?xml version="1.0" encoding="UTF-8"?> <manifest> <remote name="LineageOS" fetch="https://github.com/LineageOS" revision="lineage-16.0"/> <remote name="TheMuppets" fetch="https://github.com/TheMuppets" revision="lineage-16.0" /> <project path="device/huawei/kiwi" name="android_device_huawei_kiwi" remote="LineageOS" revision="lineage-16.0" /> <project path="kernel/huawei/kiwi" name="android_kernel_huawei_kiwi" remote="LineageOS" revision="lineage-16.0" /> <project path="vendor/huawei/" name="proprietary_vendor_huawei" remote="TheMuppets" revision="lineage-16.0" /> </manifest>

[image: 1633380136270-nfc_test.jpg]

@nero355 Sorry I have no knowledge about that at all...

I have this same issue. Device I am trying to port is an Honor View 10.

@flohack ah thanks for that, I’ll stick to Halium for now then!

it was my mistake , initially when i run the mka mkbootimg I got this error error: vendor/xiaomi/whyred: MODULE.TARGET.SHARED_LIBRARIES.libsdm-disp-vndapis already defined by vendor/xiaomi/whyred. To resolve this I commented out those modules from vendor/xiaomi/whyred/Android.mk . I accidentally commented out libantradio module too . undoing that resolved the issue .

@aravindor Please mark as solved https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved

After a few days I decided to try another vendor.img and out of nowhere reboots worked just fine. I still have no idea why the vendor messed up apparmor but anyway, if someone happens to have the same problem he could try using different vendor images.

@carlo afaik that command should work, granted my knowledge is mostly LOS 14.1 based porting on a Galaxy Note 4, if that command is not working, double check the documentation your following is for the correct version of your LOS source, as well as your source is complete and not lacking anything.

@yxles Yes.

@flohack thanks a lot, I will do. BR

@carlo I modified the title for you. And I'm glad you figured things out. Best of luck

@nullterminator I have no porting skills at all for what you are doing except for you do need the device to be on android 9 after that nothing. You need someone who knows what is happening.

@luksus Sure, thanks!

@applee I am so relieved to read that. I thought I was the only one here who had no clue about those terms, to which I would add custom ROM, flash, halium, blobs, etc.

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.