Building LineageOS for FP4

I hope my question is appropriate here:

I have tried to build it by myself. But it failed, because I cannot follow the guideline 100% precisely I think.

I use a Linux system, which is good. However, my system directory is on an SSD. It has not enough space (~100GB) left. So I need to adjust it to work from another harddrive.

Maybe you can review my steps and tell me if I do something wrong regarding my adjustments:

I followed the steps here with the following changes.

You see that I always try to refer to the respective drive:

  1. Create the directories:
    As in the guide:

mkdir -p ~/bin

My change:

mkdir -p ~HARDDRIVE/directory/android/lineage

  1. Initialize the LineageOS source repository
    My change:
cd ~HARDDRIVE/android/lineage
/HOME/bin/repo init -u https://github.com/LineageOS/android.git -b lineage-18.1
  1. Download the source code
/HOME/bin/repo sync

The issue I experience then I explain here ^

Is my approach totally wrong?

I don’t see an issue in your steps. Have you tried what Aaanze recommended to recover from this error? Or try starting with a fresh lineageos folder.

I will try to delete everything and do the steps again. But thanks for confirming it is possible my way.

FYI, I can confirm: Using both PRs from poshul did the trick. FPCamera is operational now. :slight_smile:

2 Likes

Is it working properly? I can’t open the app normally, it closes right away.

There’s another PR to solve the backlight issue. :clap:

As far as I can tell, it works properly. However, I did not test everything. That PR is for LOS 19.0.

EDIT: The slow motion effect crashes the application.

I didn’t noticed that i can built LOS 19.0 yet, thanks.

Why is there no official Los version for fp4?
After that long time?
I think /e/OS and iode base on them and there are out for long now

Because people need the time to do this volunteer work in their freetime. And having no idea about the work to be done, I will not judge if it takes long or not

5 Likes

Yvonne, I didn’t want it to take too long.
I’m just surprised that there is no LOS version yet, although there are /e/OS and iodé based on LOS. Since it should be theoretically feasible to bring out a pure LOS.
For me, it’s purely about the technical aspect. Because I don’t understand it.
Not that it takes too long or that I want to question the work of the developers, or make any demands. Keep, that’s far from my mind…

The current state of development does not meet LinegeOS port requirements for official roms: charter/device-support-requirements.md at master · LineageOS/charter · GitHub

Until the “quality” of the rom is good enough only unoffical builds can be made.

/e/ or Iode probably don’t have such strict requirements. Unofficial LOS can be built of course, but the los-18 branch from wearefairphone seems unmaintained. I think they are working on los-19.1

7 Likes

thx for sharing this informamtions…

Hi there. Sorry if it as already been answered, but I have difficulties findind this information : where can I follow the project developement and its updated compliance to Lineage criteria? I also would like to be able to download the release to test it as sson as it is usable. Many thanks!

There is no single source of truth at the moment since there is no official Lineage Rom.
Best is probably to follow

development happening on the staging/lineage-19.1 branch.

But there are also FP4 Repos from /e/, Iode, CalyxOS for their Roms. There might be some fixes / improvements that are only in one Repo but not yet in the other …

If you want to test something you probably need to piece it together yourself and make a custom build for now.

3 Likes

One question again:

At what stages do I need to be careful or would you warn me to continue when it comes to rooting and flashing the FP4?

My plan it to unlock (i already did) and root the phone (I want an Adblocker etc). I was told that rooting can brick the phone. Is that correct? Or do I have a misunderstanding?

To root the FP4 you will find information here

1 Like

At the moment, re-locking the bootloader can brick the phone. Several users had to send it back because of that.

My advices:

  • if you want root, don’t flash the patched boot image but “fastboot boot” on it (see the guide for the details)
  • if you install an alternative OS don’t relock the bootloader (or be really careful)
2 Likes

@oli.sax many thanks.

On "don’t flash the patched boot image but “fastboot boot”: So this guide is wrong? Could you perhaps advice a bit more what step to do in stead of this. This is not so clear to me. I don’t understand the difference between “patched boot image” and “fastboot boot” :confused:

No the guide is correct, that’s exactly what is writen :slight_smile:

The difference I wanted to highlight is between

  • “fastboot boot”
    and
  • “fastboot flash”
1 Like

fastboot boot patched_boot.img

will temporarly boot the system with the provided patched_boot.img meaning you’ll boot rooted but the image will not be copied on your boot partition, it is merely injected and will not persist until next reboot. This is what you’re supposed to do.

fastboot flash boot patched_boot.img

will write the patched boot image on your boot partition meaning it can result in harming the device should there be anything wrong/incompatible with the patched image