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

Latest Builds (Download):

• stable (OTA-18)
• release candidate
• devel

Status

Working:

Actors: Manual brightness
Actors: Notification LED
Actors: Torchlight (with uTorch app)
Actors: Vibration (partly, not working on chat-messengers for example)
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: MMS 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
Misc: Anbox patches applied to kernel
Network: Bluetooth
Network: WiFi
Network: Flight mode
Network: Hotspot
Sensors: Fingerprint reader
Sensors: Proximity
Sensors: Rotation
Sensors: Touchscreen
Sensors: GPS
Sensors: Automatic brightness
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:

USB: ADB access
USB: External monitor - only for devices that support it
Misc: Offline charging

Not tested:

Endurance: No reboot needed for 1 week
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 one of the the latest "flashable" artifacts zip, which contains boot.img and system.img (stable is recommended):
  • stable
  • release candidate
  • devel

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)
• OTA Updates do currently work only, if they are "incremental" updates. If not (update size > 500MB) the phone will not boot after updating. I encountered, that is the case after ~4 days not upgrading (devel channel).
  To solve a not booting phone after OTA update:
  1. Flash the android 9 system image first.
  2. Flash the latest system image built from gitlab CI again.

@adlinux Hi, I am the "porter" of the FP3/+ and I (sadly) have to say that the FP3+ (on Android 10 base) is definitely not ready for daily usage.
The FP3 with older camera modules maybe. But there are some quirks with mobile-data/cellular network for some users still.
So the older FP3 would be an option, if it has to be a "fair" phone.
If the "fair" is not your first priority, you currently will have a better experience with Volla or Experia.

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

This is a first experimental port, which should work for FP3 and FP3+ with Android 10 base.
It is not as matured as the Halium 9 port, so it will not work better for FP3 owners with "old" camera and top modules.

First a short overview what is working and what not (yet)

Not working:

• media cannot be played with system integrated mediaplayer
• videos cannot be recorded and cannot be played by the mediaplayer
• fingerprint-reader

Working

• phone calls
• SMS
• vibration
• cameras (just tested the new modules yet)
• WiFi
• Audio/Video works in browser
• System sounds work
• Anbox

Sources

Kernel: https://github.com/luksus42/android_kernel_fairphone_sdm632/tree/halium-10.0
Build Toolchain: https://gitlab.com/luksus42/fairphone_fp3/-/tree/halium-10.0

Flash

You need to have an Android 10 base flashed on your phone first. The latest eOS did not work for me. I used the Fairphone Open OS version 77. I assume the latest update will also work.
If you have not already Android 10 on your phone look here:
https://support.fairphone.com/hc/en-us/articles/360048050332-Manually-install-Fairphone-OS-on-FP3-FP3-

Then download latest Halium 10 build for FP3:
https://gitlab.com/luksus42/fairphone_fp3/-/jobs/artifacts/halium-10.0/download?job=devel-flashable

And flash the boot.img and system.img images with fastboot.
If you need step by step instructions just adapt the flashing instructions from this post:
https://forums.ubports.com/post/44184

Troubleshooting

• It is likely to be needed, to format the data partition if you flash ubports the first time, which will delete all your personal files on the phone.
  I am not sure if a fastboot -w will be enough, or if it is needed to format the data partition using TWRP.

• Some users report, that an initial boot to recovery is needed to boot system successfully. Otherwise the device hangs on boot-logo.
  However, actually there is no recovery in this build, for me it was enough to "cold" boot the device (very long press on the power button until it reboots) after the first start, when it hangs on boot-logo.

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.

Manufacturing date of my device is 2020-10-23.
I bought it as "used".

I use Linux btw., perhaps that makes a difference for spflashtool...

@FP2andFP3-User & @marek_python
I just flashed the TB-X606F_S100015_191127_BMP Images with the SPFlashTool on my X606XA Tablet.

• tablet was turned off
• no cable connected
• download started in flashtool
• connected usb cable without pressing any button
• flashing started
• "Downlod Ok"
• red light is on
• I disconnected the cable and hit the power button.
  It boots... but with some errors. Could be caused by not matching tablet version. Anyway.

Now I wanted to flash TB-X606F_USR_S100168_200828_BMP:

• tablet was turned off (I turned it off by long power button press until the display turns off, if it not vibrates again, I can be sure that it is really turned off)
• no cable connected
• download started in flashtool
• connected usb cable without pressing any button -> red light on but else nothing happened
• unplugged cable
• connected usb cable with pressing volume down button -> red light on but else nothing happened
• unplugged cable
• connected usb cable without pressing any button -> red light on
• a short press on the power button
• after ~2 seconds flash-tool did start to download images
• "Downlod Ok"
• red light is on
• I disconnected the cable and hit the power button
  Device boots this time without errors...

No Idea, if this is helpful.

I just can't believe, that there is no way ...

@marek_python so perhaps plug it in and let it alone for some hours, to let it charge a bit....

What was important for my device, that I also choose the right "Download-Agent" (MTK_AllInOne_blalba.bin) from the image folder, which I wanted to flash.

---

I had the impression that it starts to flash more reliable without error, if I press (only) the volume down button, while plugging the usb cable.

---

Then I have had an issue, which is described here together with a solution:
https://www.programmersought.com/article/74183233522/

But as you already did a successful flash, I don't think that you need this.

---

I am still not sure if you tried to boot your devices, without any plug in it... For me it was a solution sometimes.

---

It is also worth to try different long-press combinations with volume up/down or all together...

---

And did you try to enter fastboot mode? ah, you did

@marek_python mh, I think that is an expected error, if the device is not turned off, when trying to start the flash procedure...

So what happens, if you start the flashing process, then connect the usb at the turned off device without pushing any button?

@koens mh, did you re-format your sdcard before using it?
And did you set the option to save to sdcard in your camera app?
Does it still complain, when you set the option back to "internal"?
What is the FAIRPHONE directory for?

@FP2andFP3-User
Is the red light on, even if no cable is plugged?
When flashing, did you leave the preloader checked, as kugiigi suggested?
Which device do you got exactly: X606X, X606F, X606XA, X606FA ?
Which image did you flash?
Can you enter fastboot mode: long press power + volume down together?

I was in similar situations multiple times, so I think there should be a way out.

Can you try to reflash it with SPFlashtool, maybe with the next newer image version?
Normally the device is off, you start the download-process in flash-tool and then you connect it the usb-cable, but sometimes I needed to push the power button, if nothing happened after connecting usb (I did experiment with preloaders from different versions, what did not went very well and I ended up in the same situation like you).

@fp2andfp3-user did you try to unplug the cable and just push the power button?

@mighty I have a matrix bridge running on my home-server... If you are interested, I probably could invite you in the bridged matrix room.