This is a port for the Fairphone 3.
There are two ways:

1. the GSI (Generic System Image)-way
2. the "native FP3"-way, I call it the Gitlab-CI way. The boot and system images are (currently) getting built by the Gitlab CI.
   In the future, this will be the way, to install it by the ubports-installer and also get ota-updates working.

Sources

• Kernel: https://github.com/luksus42/android_kernel_fairphone_sdm632
• Device: https://github.com/luksus42/android_device_fairphone_FP3
• Vendor: https://github.com/luksus42/proprietary_vendor_fairphone
• Manifest: https://github.com/luksus42/halium-devices/blob/halium-9.0/manifests/fairphone_FP3.xml
• Erfan's GSI: https://build.lolinet.com/file/halium/GSI/
• Gitlab CI Builds: https://gitlab.com/ubports/community-ports/android9/fairphone-3/fairphone-fp3/-/pipelines

Status

	GSI	GITLAB CI
Actors: Manual brightness	Working	Working
Actors: Vibration	Working	Not working
Actors: Notification LED	Not working	Working
Actors: Torchlight	Working with additional steps: use uTorch App	Working with additional steps: use uTorch App
Camera: Photo	Working	Working
Camera: Video**	Working	Working
Camera: Switch between back and front camera	Working	Working
Camera: Flashlight	Working	Working
Cellular: Data connection	Working	Working
Cellular: Carrier info, signal strength	Working	Working
Cellular: Incoming, outgoing calls	Working	Working with additional steps: a data connection must be active (mobile or wifi)
Cellular: PIN unlock	Working	Working
Cellular: Voice in calls	Working	Working
Cellular: MMS in, out	Not tested	Not tested
Cellular: SMS in, out	Working	Working
Cellular: Change audio routings	Working	Working
Endurance: Battery lifetime > 24h from 100%	Working	Working
Endurance: No reboot needed for 1 week	Not tested	Not tested
GPU: Boot into UI**	Working	Working
GPU: Hardware video decoding	Working	Working
Misc: AppArmor patches applied to kernel (Kernel 4.9)	Working	Working
Misc: Battery percentage	Working	Working
Misc: Offline charging	Not tested	Not tested
Misc: Online charging	Working	Working
Misc: Shutdown / Reboot	Working	Working
Misc: SD card detection and access	Working with additional steps: It is there but gets not displayed in Filebrowser. But one can access it over /media/phablet/<sdcard-name>	Working
Misc: Anbox patches applied to kernel	Not tested	Not tested
Misc: Recovery image	Not working	Not working
Misc: Reset to factory defaults	Not tested	Not tested
Misc: RTC time is used after reboot	Not working internet is needed for correct time	Not working internet is needed for correct time
Network: Bluetooth	Working	Working
Network: WiFi	Working	Working
Network: Flight mode	Working	Working
Network: Hotspot	Working	Working
Sensors: Fingerprint reader	Working	Working
Sensors: Proximity	Working	Working
Sensors: Rotation	Working	Working
Sensors: Touchscreen	Working	Working
Sensors: GPS	partly working: the initial location is found but cannot be followed (Activity App)	Not tested
Sensors: Automatic brightness	Not working	Not working
Sound: Loudspeaker	Working	Working
Sound: Microphone	Working	Working
Sound: Volume control	Working	Working
Sound: Earphones	Working	Working
USB: ADB access	Not working	Not working
USB: External monitor - only for devices that support it	Not working	Not working
USB: MTP access	partly working: the ISODrive App works, but switching back to SSH dows not work	partly working: the ISODrive App works, but switching back to SSH dows not work

How to build halium-boot

• create halium folder and cd into it
• initialize the halium 9.0 repo: repo init -u https://github.com/Halium/android -b halium-9.0 --depth=1 (creates a hidden .repo folder, in case if you are wondering)
• do: repo sync -c -j [number of parallel jobs]
  ** make sure that the bionic folder is synced (this somehow missing repo caused builderrors and a headache for me)
• add manifest file fairphone_FP3.xml to halium/devices/manifests
• missing exfat modules: cd into kernel/fairphone/sdm632 and do: git submodule update --init --recursive
• do: ./halium/devices/setup FP3
• modify kernel config: halium/halium-boot/check-kernel-config kernel/fairphone/sdm632/arch/arm64/configs/lineageos_FP3_defconfig -w
  • most of these changes should already be in the kernel source, but there my be changes in the meantime
• check again without -w parameter
• add fixup mountpoints for FP3, I am not sure if this is really needed:

    "FP3")
        sed -i \
            -e 's block/mmcblk0p30 mmcblk0p30 ' \
            -e 's block/mmcblk0p31 mmcblk0p31 ' \
            -e 's block/bootdevice/by-name/vendor_a mmcblk0p32 ' \
            -e 's block/bootdevice/by-name/product_a mmcblk0p60 ' \
            -e 's block/bootdevice/by-name/vendor_b mmcblk0p33 ' \
            -e 's block/bootdevice/by-name/product_b mmcblk0p61' \
            -e 's block/mmcblk0p62 mmcblk0p62 ' \
            -e 's block/mmcblk0p34 mmcblk0p34 ' \
            "$@"
        ;;

• apply hybris patches: hybris-patches/apply-patches.sh --mb
• build:
  I used a little bash script, you can also execute each command individually in the terminal

  #!/bin/sh
  
  # prepare 
  # using python 3 caused builderrors, perhaps there is an environment variable for this??
  sudo ln -sf python2 /usr/bin/python
  
  # when using zsh shell you will likely need this two commands
  setopt shwordsplit
  export LC_ALL=C 
  
  # build
  export USE_HOST_LEX=yes
  source build/envsetup.sh
  breakfast FP3
  mka halium-boot
  #mka systemimage
  
  # revert python 
  sudo ln -sf python3 /usr/bin/python
  

  Of course, you could also build the systemimage, but I could not get it to work/boot yet.
  It takes ~1h on an Intel i7 9750H (@45W) ;-).

How to flash

GSI

Prepare

Build or download the halium-boot image.
Get TWRP for Fairphone 3.
Get a ubports GSI.
Unlock your phone, see: https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone-3/
You will need the android tools "fastboot" and "adb".

Flash

• Boot the phone into bootloader/fastboot by pressing power + volume-down buttons until it reboots. Or just reboot and click a volume button within 5 seconds and select the bootloader.
• Flash halium-boot image: $ fastboot flash boot halium-boot.img
  • if fastboot throws the error: Couldn't parse partition size '0x' try the following command: $ fastboot flash:raw boot halium-boot.img
• Boot your downloaded TWRP image temporarly: $ fastboot boot [twrp-image.img]
• In TWRP go to ADVANCED and Select "ADB Sideload". Activate sideload.
• in Terminal: adb sideload [ubports_gsi.zip]
• Wait until it finished, then reboot system.

Gitlab CI

Prepare

Download the latest flashable artifacts zip, which contains boot.img and system.img.
Unlock your phone, see: https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone-3/
Get TWRP for Fairphone 3.
You will need the android tools "fastboot" and "adb".

Flash

• Boot the phone into bootloader/fastboot by pressing power + volume-down buttons until it reboots. Or just reboot and click a volume button within 5 seconds and select the bootloader.
• Flash boot image: `$ fastboot flash boot boot.img
  • if fastboot throws the error: Couldn't parse partition size '0x' try the following command: $ fastboot flash:raw boot boot.img
• Flash system image: $ fastboot flash system system.img
  • if flashing of system image does break before finished (file data too large), try: fastboot -S 300M flash system system.img
• Boot your downloaded TWRP image temporarly: $ fastboot boot [twrp-image.img]
• In TWRP format your data-partition (perhaps that could be done with fastboot too...)
• reboot the system.
  Default password is phablet.

Troubleshooting

In case something wents wrong, you should be prepared to be able to flash a working android image. I used the /e/ OS images for this case.
Look here: https://community.e.foundation/t/how-to-flash-e-os-on-fairphone-3-using-debian-based-gnu-linux/15498

Known Issues

• There are some graphics-glitches (black bars flashing up here and there).
  • Much less with latest GSI v10
• Inititally the scaling is very small, this leads to some unwanted effects. Morph Browser, websites are always in Desktop Mode
  • Fix: Make the system writable sudo mount -o rw,remount / and change/add following properties in /etc/ubuntu-touch-session.d/android.conf:
    GRID_UNIT_PX=21
QTWEBKIT_DPR=2.0
FORM_FACTOR=handset
• In the app overview (swipe from the left) it is hard to grab the app, to close it by swiping it up or down. fixed with GSI v10
• The settings app crashs, when opening the memory-overview in the Info-area.
• With Erfan's GSI (v9) webapps crash on start fixed with GSI v10

This is a port for the Fairphone 3.

On Fairphone 3+, camera and audio-module do currently not work with this port.
It is required that the device is using Android 9, otherwise it must be downgraded first: see Troubleshooting section.

Sources

Kernel: https://github.com/luksus42/android_kernel_fairphone_sdm632
Build Toolchain: https://gitlab.com/ubports/community-ports/android9/fairphone-3/fairphone-fp3

Status

Working:

Actors: Manual brightness
Actors: Notification LED
Actors: Torchlight (with uTorch app)
Camera: Photo
Camera: Video
Camera: Switch between back and front camera
Camera: Flashlight
Cellular: Incoming, outgoing calls
Cellular: Data connection
Cellular: Carrier info, signal strength
Cellular: PIN unlock
Cellular: Voice in calls
Cellular: SMS in, out
Cellular: Change audio routings
Endurance: Battery lifetime > 24h from 100%
GPU: Boot into UI
GPU: Hardware video decoding
Misc: AppArmor patches applied to kernel (Kernel 4.9)
Misc: Battery percentage
Misc: Online charging
Misc: Shutdown / Reboot
Misc: SD card detection and access
Misc: RTC time is used after reboot
Misc: Recovery image + OTA Updates
Network: Bluetooth
Network: WiFi
Network: Flight mode
Network: Hotspot
Sensors: Fingerprint reader
Sensors: Proximity
Sensors: Rotation
Sensors: Touchscreen
Sensors: GPS
Sound: Loudspeaker
Sound: Microphone
Sound: Volume control
Sound: Earphones

Working with additional steps:

USB: MTP access (partly working: the ISODrive App works, but switching back to SSH dows not work)

Not working:

Actors: Vibration
Misc: Anbox patches applied to kernel
Sensors: Automatic brightness
USB: ADB access
USB: External monitor - only for devices that support it

Not tested:

Cellular: MMS in, out
Endurance: No reboot needed for 1 week
Misc: Offline charging
Misc: Anbox patches applied to kernel
Misc: Reset to factory defaults

How to flash

Prepare

• Unlock your phone, see: https://www.fairphone.com/en/bootloader-unlocking-code-for-fairphone-3/
• You will need the android tools "fastboot" and "adb".
• Download the latest "flashable" artifacts zip, which contains boot.img and system.img:
  https://gitlab.com/ubports/community-ports/android9/fairphone-3/fairphone-fp3/-/pipelines

Flash

1. Boot the phone into bootloader/fastboot by pressing power + volume-down buttons until it reboots. Or just reboot and click a volume button within 5 seconds and select the bootloader.
2. Flash boot image: $ fastboot flash boot boot.img
   • if fastboot throws the error: Couldn't parse partition size '0x' try the following command: $ fastboot flash:raw boot boot.img
3. Flash system image: $ fastboot flash system system.img
   • if flashing of system image does break before finished (file data too large), try: $ fastboot -S 300M flash system system.img
4. Wipe your data partition with command: $ fastboot -w
5. reboot the system.

Troubleshooting

In case something wents wrong, you should be prepared to flash back a working android image.

• /e/ OS: https://community.e.foundation/t/how-to-flash-e-os-on-fairphone-3-using-debian-based-gnu-linux/15498
• Stockimage (also for downgrade): https://github.com/p1gp1g/fp3_flash_stock (use A.0111)

Yes, do a fast release.
Currently (before last OTA) there are so much fixes, that the stable users have to wait for one or two months.
I think it's better to get fixes to stable channel quick.

I updated the start-post.
With the latest GSI v10 from Erfan, the phone gets very usable. I don't know of a real issue so far.

Somehow I managed to build a more recent working GSI zip for arm64:
https://drive.google.com/file/d/1L_fA1W1D9xWO2OqmnimvHdLWEdRN1api/view?usp=sharing

Camera does not work in this version, so far...

FP2, findings and differences to legacy version:

• camera does work with gstreamer-droid patch and is superfast
• after turning flightmode off, it is not needed to enter SIM-pin again
• waking up from sleep is delayed by some (5?) seconds, what makes it hard sometimes to answer a call, because you have to wait until the swipe is working
• I can't get a MTP USB connection, when I unplug the device, my pc informs me about using another network connection, lsusb identifies the device as:

Bus 003 Device 007: ID 0fce:7169 Sony Ericsson Mobile Communications AB FP2

Is that gstreamer-droid based camera only a Halium-thing or will it also come to current ports?

@jezek :

please try the following command in the terminal (on the phone):

rm -rf .cache/mediascanner-2.0/ .cache/unity-thumbnailer/ .cache/gstreamer*/*

Then reboot.

This always fixed it for me, whenever this issue appeared again.

I have just added the kodimote app to the openstore.

@Flohack : oh you got me wrong a little bit. I did not create my own port.
I just wanted to host the images I built out of Ratchanan´s port, since no prebuilt images are served yet.
It is for the users, who are not able to download all sources or can't build it by themselves, but like to test the halium port.

@altor it is not working for the new FP3+ modules.
The working section therefor depends on the "older" FP3 model.

Do you have an FP3+ or FP3 with newer modules?

@keneda oh, ok

@flohack I think kenedas answer was at least as ironic as yours.

@louisoquinn Great, that you give it a try.
But I fear you are hitting the same dead end like there:
https://forums.ubports.com/topic/5662/bug-two-sim-cards-only-one-is-working-perfect/53
(the thread-title does not fit anymore though).

And I have no solution yet.
Honestly my hope is, that some android/flashing-experienced user, who has the same issue could investigate this further...
Because I cannot reproduce it on my Fairphone.

@purplecroc89 Ok, then it is a full update and currently expected not to work until I solved this issue:
https://forums.ubports.com/topic/5553/bringing-fp3-to-the-ubports-installer/19

@Purplecroc89 I rebuild the system image, that you can flash the current ubports dev version:
https://gitlab.com/ubports/community-ports/android9/fairphone-3/fairphone-fp3/-/jobs/1051808201/artifacts/download?file_type=archive

Then you could try another OTA Update tomorrow.

If you want to keep a working OS on your phone, just flash both slots:

• fastboot flash system_a system.img
• fastboot flash system_b system.img
• do the same for the bootimage

Then on a failed OTA, the system should boot after automatically switching to the other slot.

And for Reference:
Switching the active slot:

• fastboot --set-active=a

Checking, which slot is active:

• fastboot getvar slot-active:a

@purplecroc89 ok, that sounds like the error I encountered, when doing a full update.

What is happening here, is that the updater script formats the system partition and then reinstalls ubports on it. But that formatting somehow breaks something on the partition so, that the next reboot in the current slot fails, and the phone immediately reboots to the other slot, hoping there would be a bootable os...

Can you tell me, which size the downloaded update has? If it is something abourt 500MB it is a full update.
If it is lower, 100-250MB, it is an incremental update.

Perhaps there is triggered a fullupdate even without channel-switch.

@purplecroc89 Does not sound wrong to me.
What exactly is happening?

Does it automatically reboot to the recovery, when you hit "reboot & install" and do you see the the ubports mascot with a text "installing update"?
Or does it immediately fail to install the update?
What is displayed on the screen?

@keneda you have to consider the context.
We are in a development environment and afaik there is no way to lock/unlock it without wiping the data partition.
I am even not sure if one needs to do the oem unlock with some code again. Where would you enter the code on ubports?

But I also have to clarify, that I did not experiment a lot with locking and unlocking the bootloader.
So I would be more than happy, If another person could do this for me .

I also think, that this is a general ubports/halium(?) issue/discussion.

@purplecroc89 uhhh, I never relocked my bootloader, because I wan't to be able to flash the device again, in case something went wrong.
And without a working android, we are not able to unlock the bootloader again, as far as I know... Please corect me if I am wrong.

So I would not recommend to lock the bootloader to you either.

So if you got the time:
Please unlock it again.
Flash the images I linked above.
Do not lock the bootloader.
Try an OTA update.

And if that works, perhaps try to lock the bootaloader again and give the OTA another try...