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

For Fairphone 3+ please use the installer or follow this thread!

This is a port for the Fairphone 3.

It is required that the device is using Android 9, otherwise it must be downgraded first: see Troubleshooting section.
Downgrading seems not to be necessary. Only the vendor partition should be replaced with the stock Android 9 vendor image.

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

0. 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.
1. If your phone is running with android 10, flash the android 9 vendor image with: $ fastboot flash vendor vendor.img
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.

• Stockimage (prepared to not wipe your data while flashing): https://www.androidfilehost.com/?fid=7161016148664802137

@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.

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

The X605 is now available in the ubports-installer.

Hey @all,
it seems that I have solved the issue with always starting in desktop mode...
Turns out that it were some kernel configs, which leads to unity8 thinking, that there is some kind of input device connected... how @kugiigi suggested.
So there is no need anymore for creating an upstart script in this regard.

I am not sure if the boot-image is being updated by the OTA update, so maybe I need to adjust the installer configuration first and you have to reinstall the bootimage with the installer afterwards. I will inform you here, how to proceed.

I additionally got usb-mtp mode working. Which should be available with tomorrows devel-update.

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.

This port works for FP3 and FP3+ with Android 10 base.

Status

Working:

Actors: Manual brightness
Actors: Notification LED
Actors: Torchlight
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/WayDroid patches applied to kernel
Network: Bluetooth
Network: WiFi
Network: Flight mode
Network: Hotspot
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:

Sensors: Fingerprint reader
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

Sources

https://gitlab.com/ubports/community-ports/android10/fairphone

Install

You need to have an Android 10 base flashed on your phone first. I assume the latest update should work.

If you need to upgrade to Android 10 first (for example, if you already have installed the Halium 9 Ubuntu Touch build) and don't want loose your user-data, I prepared the 3.A.0129 stock rom, which does not touch your userdata, when flashing:
https://www.androidfilehost.com/?fid=7161016148664802137

If your device is upgraded or already running Android 10 just use the ubports installer, which you can download on this site:
https://devices.ubuntu-touch.io/device/fp3/

WayDroid (anbox-halium)

Since everything changed again in the waydroid source, I removed the instructions.
We should just wait until it is ready...

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, if that happens, 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.

I have just added the kodimote app to the openstore.

Hi,

I've created a new build for the Oneplus5/T, which is based on the nowadays for android9+ devices recommended build method (Standalone kernel method).
I am running it myself for some months now and also just fixed the last issue, the not working fingerprint, that I think it's time to let it test by you owners for regressions, compared to the current full-system-image version.

Why a new build method at all, since the current build is working fine?

1. Reduce CI-load
   The full-system-image method is very "ressource-hungry". For every device with full-system-image, our jenkins-CI needs to build a (devel) build every day. For the OP5/T it takes about 7 minutes. That doesn't sound much, but the build-server seems to be very powerful, since a system-image build on my local machine takes about half an hour (Ryzen 5700U Processor). Also, these CI-Pipelines need to be maintained by someone.
   So, for the standalone-kernel-method, the CI only needs to build one generic_arm64 image (for every Halium version), which will be used by many devices, and the build of that image only takes about 2 minutes.

2. Better maintainability
   The kernel-standalone-method in combination with the generic halium image is more future-proof, regarding maintainability, and also new features or system-upgrades. The general needed updates for newer Halium-versions are centralized and the same for every device.
   A device maintainer only needs to take care for the kernel and the relatively small device-config tree with device-specific overlays.

Other improvements of the new build

1. It already contains the fix for the microphone not working after a call. It survives system-image upgrades.
2. It contains an initially disabled user-service, that, when enabled, is switching mobile-data to 2G when the screen is off, to save battery.
   You can activate it by executing in the terminal on the phone: systemctl --user enable lte-battery-saver.service
   It will be started on next boot or you start it manually by executing: systemctl --user start lte-battery-saver.service.
   It survives system-image upgrades.
3. For device-specific needed system-changes, it is using the overlaystore method. Compared to the current method, it is more reliable when doing system-upgrades. The overlays of the current build, may be overwritten by an OTA update, which can lead to device not booting and you would need to use the ubports-installer to reinstall the system-image. With the overlaystore method, such things should not happen.

Flashing and Testing

You can just flash the boot and system image with fastboot, without loosing any data.
At least flashing the system image should be enough, since we are using the same kernel source for both build-methods.

HINT
For me, my local distributions fastboot version does not work for flashing the system image. Therefor I am using mfastboot, a motorola implementation, which works for me.

Get the latest images here:
https://gitlab.com/ubports/porting/community-ports/android9/oneplus-5/oneplus-cheeseburger-dumpling/-/jobs/artifacts/master/download?job=devel-flashable-focal

Extract it, boot the device in bootloader mode, connect it to your pc and flash the ubuntu.img to system partition: fastboot flash system ubuntu.img.
Then reboot.

Snaps

The rootfs/system-image size of the OP5/T is very limited. That's why it is hard to install anything additional on the rootfs, for example the snap-dependencies.
But it is possible to expand it a little bit. For that:

• reboot to recovery
• connect through adb
• execute: e2fsck -f /dev/block/by-name/system
• execute: resize2fs /dev/block/by-name/system
  Output should be something like:

  Resizing the filesystem on /dev/block/sde21 to 786432 (4k) blocks.
  The filesystem on /dev/block/sde21 is now 786432 (4k) blocks long.
  

• reboot

Now it should be possible to install snap-dependencies, using the app Snapz0r.

Finally

Please share your experience here.
Especially, I am interested in feedback for the OnePlus5 (without T), since I don't have this device to test it myself.

@pe3noATo2DOTpl
First: please dont be so wasteful with praises and smileys. The praises make me feel uncomfortable and lots of smileys make your text hard to read.

I already have another x605f tablet for developing.

The 2GB version can run UT, but will never be able to do OTA updates, since we cannot get the recovery working for it. If I remember correctly, even TWRP is not working on this version.

Same applies, when using TWRP recovery on the 3GB version, you won't be able to do UT OTA updates.

So, whatever you do, don't go for the 2GB version.

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...

@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.

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

I think it is better to keep this thread clean...
So please just open a new thread for specific issues. Thanks.

I started work on FP2 kernel for focal, multiple times, but never got it to a usable state. Iirc, I got it booting one time, but in this state, it was missing lots of needed configs, for getting UT up with UI and other needed stuff.

I like the way, how ubtouch has implemented the "horizontal os functions", switching the app from the right and opening the app drawer from the left.
Apps could still implement horizontal swipes for own functionality, when swiping from the middle of the screen. Like it works here in the forum, when swiping to the right, it opens the topics overview and when swiping to the left it opens the profile-overview.

@peat_psuwit , @Emphrath : wooow, the flash works with the camera app ... I am speechless
This is with Halium and latest gst-droid patch.

An FP2 with new camera module and working flash... I still can't believe it.
Thank you so much @peat_psuwit .