This is a port for the Fairphone 3.
Currently only the GSI (Generic System Image) -way is 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
• GSIs:
  • Erfan's GSIs: https://build.lolinet.com/file/halium/GSI/

Status

Working

• Actors: Manual brightness
• Actors: Vibration
• Actors: Notification LED
• Camera: Photo
• Camera: Video
• Camera: Switch between back and front camera
• Cellular: Data connection
• Cellular: Incoming, outgoing calls
• Cellular: PIN unlock
• Cellular: Voice in calls
• 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: Offline charging
• Misc: Online charging
• Misc: Shutdown / Reboot
• Network: Bluetooth
• Network: WiFi
• Network: Flight mode
• Sensors: Fingerprint reader
• Sensors: Proximity
• Sensors: Rotation
• Sensors: Touchscreen
• Sensors: GPS
• Sound: Loudspeaker
• Sound: Microphone
• Sound: Volume control

Working with additional steps

• Camera: Flashlight, with gst-droid patched camera app not needed anymore
• Cellular: Carrier info, signal strength
  • Data-Connection is not displayed, but there
• Misc: SD card detection and access
  • It is there but gets not displayed in Filebrowser
    But one can access it over /media/phablet/<sdcard-name>
• Network: Hotspot
  • also no display feedback, but it is there, after some de-/activation action

Not working

• Actors: Torchlight
• USB: MTP access

Not tested

• Cellular: MMS in, out
• Cellular: SMS in, out
• Cellular: Change audio routings
• Endurance: No reboot needed for 1 week
• Misc: Anbox patches applied to kernel
• Misc: Recovery image
• Misc: Reset to factory defaults
• Misc: RTC time is used after reboot
• Sensors: Automatic brightness
• Sound: Earphones
• USB: ADB access
• USB: External monitor - only for devices that support it

How to build

• 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

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.

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

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.

There you are:
https://forums.ubports.com/topic/4964/fairphone-3-fp3?_=1601277763588

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

@Janez said in Fairphone 3 (FP3):

• SIM card in slot 1 works and phone recognizes it. However to make phone call I need to be connected to some WiFi with internet access
• SIM card in slot 2 works with and without WiFi connection

Ok, it is the same behaviour for me. That's why I did not make this version very official, because I think that is a show-stopper for using it daily.

• Cellular data (2G/3G/4G) does not work for me for halium-boot.img as well as CI boot.img so here I suspect wrong setup of APN. My operator did not provide me too much useful informations. I will try to work it out in next days.

With halium-boot it is working perfectly fine for me (ok, sometimes I have to switch cellular data on and off to make it work).
With CI boot.img, I got a data connection displayed next to the simcard, but it is not making it to the "global" data indicator in the top, which means: no data connection at all.

Other things, that need to be solved for the CI version is Vibration and Notifications in standby mode.

@Janez Thank's for testing.

If I undrestand it right, the combination of halium-boot.img and system.img did not work for you?

And as you are currently using the CI boot.img and system.img, does telephony and cellular data connection work for you?

@ernest I cleaned up everything and reinstalled your version. And now it works.

How were you able to install it ??? on arm64 phone

I built an arm64 version of ubsync... but the contained pre-compiled owncloud libraries were still armhf. And I think the qmake .pro-file did also create armhf path's and so on...

Hi @Janez,
great that it works for you. And thanks for your help.

I can't confirm the telephony and camera bugs as you describe it. For the camera, you could try to change resolution and then switch back again.
Currently I am using another system-build (not GSI).
But I've also had some quirks here and there. Sometimes I could not stop the last phone-call, until I rebooted. Sometimes I was not able to send SMS, they also did not get displayed in history, but after a reboot, the recipient recieved all 3 SMS, I tried to sent.
I think some bugs could also be a result of the dev-build, we are using here.

I must admit that I am also not the one, who knows how to dig deeper into some issues.
I just look around and search for similar issues on similar phones and then try to apply the fix, which someone provided.

As I said above, I am currently testing another system-build, which I am using as daily driver currently. It gets build by the gitlab CI of the ubports repository.
Could you please try if it works for you, when just flash the system.img from here to your FP3?

• download
• boot to fastboot
• then just execute: fastboot flash system system.img
• reboot

What you could test here:

• does it boot successfully?
• does it still boot successfully, if you wipe the data partition (with twrp, or perhaps with fastboot)
  • if not, does it boot again if you flash the boot.img from the gitlab CI link above
  • if yes, that would be interesting

What I try to figure out here is:

If I understand it correctly, the GSI seems to boot the rootfs (ubports) from the data partition.
The CI build packaged the rootfs into the system-partition.

Normally you would either use boot.img together with system.img from the gitlab CI (option1) or use the halium-boot.img together with the GSI (option2, as you do currently).
The CI build also works, but has less working hardware yet. For example telephony only works when wifi is connected (strange thing).

I am not sure if you know how things work with a/b partitions on that/a phone.
I did flash option1 to the a-partitions and option2 to b-partitions.
Then I could switch with fastboot --set-active=a or fastboot --set-active=b between the options and compere them. The data partion is the same for both.
Then I just flashed the halium-boot.img also to option1 and looked how things work out and somehow it seems to work better than option2.
But what I not tested yet, if it perhaps just boots to the rootfs, which is placed on the data partition by the GSI.
I also would not understand why it would work better than the GSI then, because it would be the same, like booting option2.

Hm, I am not sure if it is clear, what I tried to describe...

@Janez Hi, the fastboot error Couldn't parse partition size '0x' seems to be a problem of recent fastboot versions.
To go around it you should adjust the command to:

fastboot flash:raw boot bootimage.img

@ernest Ha, that's it!
In that file the exec was referring to the wron path: ..../arm-linux-gnueabihf/...
I changed it to "aarch64-linux-gnu" and now it works!

Obviously that file is not getting purged, when clearing app data with UT-Tweak-Tool, because it is not part of the app-directory...

Edit:
Hm, but it is still not possible to trigger a sync from within the app.
There is an error that it could not find libowncloudsync.so.0: https://paste.ubuntu.com/p/Wzp55yHnvq/

But I can still trigger the sync with the terminal command.

@ernest thanks.
Interestingly the command works and my folder gets synced: https://paste.ubuntu.com/p/CXf3VWmB3n/
After executing the command, the app also shows a "last-synced" date. The service status still is "Stopped".

So the service just cannot be started by the app. Perhaps it is an AppArmor issue?!

@ernest Yours. I already deleted UBSync multiple times to get sure.

Edit:
Hm, I will check it again... the file creation dates of the lib files, look like the ones I created myself.

Edit2:
Ah no, it is definitely yours, the files where created on the 26th November 2019.

@ernest said in Help creating an UBSync arm64 version:

For the log :
cat .cache/upstart/OwncloudSyncd.log

Hm no, that file does not exist... which is one more indicator for, that owncloudsync daemon could not be started.

@007fred50:
see:

@007fred50 said in Fairphone 3 (FP3):

Can i go back to Farphone OS again? (Android 10)

Yes. "Just" follow this guide: https://support.fairphone.com/hc/en-us/articles/360048050332

if you follow that guide, that I linked above, step by step, you should find the answer:

I will not answer further questions regarding this, sorry, but I am not your personal support.