Hello @hehip,
for helping we would need to know more information. How long have you been waiting for installer before you decided to turn it off? In some steps there is need to watch your phone and confirm actions the installer made in fastboot. For example you need to confirm "Reboot to recovery" manually on your phone. I think installer claims it is "flashing firmware" but in reality it is waiting for recovery to boot up.

Today I successfully flashed FP3 from Linux using installer 0.10.0, maybe you can try Appimage if snap version is older one. You can read my latest experience here:
https://forums.ubports.com/post/79146

I managed to take some time and verify my findings.

It looks like I made mistake on first installation because today I managed to flash Focal directly over FPOS. So right now my flashing procedure was like this:

1. Download and Fairphone OS based on Android 10
2. Flash Fairphone OS without locking bootloader
3. Boot into Fairphone recovery and erase user data as requested
4. Reboot to Fairphone OS welcome screen
5. Reboot to Fastboot mode
6. Use Ubports installer and let it do its job with Focal/stable branch

Hello,
I noticed strange bug where some apps draw their windows one pixel smaller than they should on Fairphone 3.
Cinny is rendering with gap on top:

Morph is rendering with gap on right side:

My question is whether this is device specific or not and if it is mistake on app side or system side of things?

Edit:
After rotating the screen Morph fixes itself until being closed and Cinny stays with consistent gap along the top side (or to be precise, side near to earpiece) all the time.

So after trying some alternative android based OSes I decided to give Ubports a try once again. Almost perfectly after a year, what coincidence
Installation process is more-less not as painful as I expected, but I think it would be nice to fill some additional information.
First of all in install instructions there is link to non-existent Fairphone support article for FPOS download. I did find new article with all FPOS versions available here.
Before install I did flash Android 10 version of FPOS and verified it is working. After that I flashed Ubports 20.04 stable and ended up in bootloop. Reflash directly to Ubports 16.04 did not help. I had to flash FPOS again, then flash 16.04 and upgrade that to 20.04. But that can by caused just by some fault on my side.
Also in the mean time I forgot it is bad to lock bootloader for Ubports. It would be nice if installer mentioned this too (maybe I just missed it).

I don't think this is Pixel specific problem. I am experiencing this on Fairphone 3 as well. In random pattern there are 3 things that happen:

• camera app starts normally
• camera app complains about not having permissions
  • can be solved by simply restarting app and everything works then
• camera app hangs on black screen after ending splash screen and needs to be ended
  • after that whenever I try to start camera app it hangs on splash screen with it forever loading

@luksus I don't think I enabled adb while in developer settings. So this part was probably my mistake

Hello,
Today I used installer in order to migrate from /e/ OS to UbPorts and would like to refer (I do not want to flood category with duplicate topics).

Android ROMs
I had to migrate back from /e/ OS Android 11, which was easy thanks to link for old FPOS in installer. /e/ OS version Q (1.4) did not work for me and phone got only to boot loop.

Some notes
I used AppImage installer from device card on ubports.com on Gentoo stable:

• Installer did not notice I do not have android-tools installed and just hanged on "waiting for device"
• Even with stock FPOS the installer (appimage) did not recognize connected phone. I had to reboot it manually to bootloader.
• After manually selecting device there are several channels marked as android9 (stable, rc and devel). Nothing terrible but it is a bit confusing, because device card on website refers to gitlab.../android10/...
• Rest of installation worked as expected. Last step (sending feedback) failed due to some random error after clicking send button.

Hey @Luksus, I'm affraid links in first post are broken. Download links give error 404. I managed to navigate through GitLab and download needed files manually from CI but it would be nice to have links working

@Luksus I will try to report them there next time.

• Call issue: It happens more often when someone is calling me, phone just stays locked after accepting call. When I call someone, it looks like the issue is related to auto-lock time.
• wake up problem: I noticed this problem a while ago but for the last build and data wipe with TWRP the phone looks more stable. I run it 4 to 5 days now without the need of reboot.
• sim-card vanish: This happened to me only once, while signal was so weak it could not handle even 2G data. But after a while of no cellular the phone "repaired" itself.

@dblake76 as luksus said, everything in first post is valid. Even possible errors you could encounter during flashing are covered there.

So after few days of using Gitlab CI I am experiencing few minor issues:

• when calling, it gets minimized and I have to unlock the phone to control call
• when WiFi has weak signal and phone disconnects, it sometimes requires password again. I learned to confirm blank password (about 50% cases WiFi catches up again) or hit cancel and then connect to it from drop down menu. In very rare occasions the phone behaves like it forgot password and I have to write it down again even though I see that specific WiFi in saved networks.

So far the phone is a bit more stable than with GSI build.
Speaking of issues/bugs, is it better for you @Luksus to write them down here or should I open them in GitLab?

@Luksus thanks, that worked. Gitlab CI build is so much smoother!

About FP3+: To use upgraded modules you need to install Android 10 and as far as I know nothing based on Android 9 works.

So I had some time to try flashing again and I did not manage to flash Gitlab-CI build.
I am constantly receiving error with partition size (probably):

fastboot flash system ./ubports-ci/system.img
Sending sparse 'system' 1/5 (520932 KB)            OKAY [ 14.473s]
Writing 'system'                                   OKAY [  9.115s]
Sending sparse 'system' 2/5 (499041 KB)            OKAY [ 13.816s]
Writing 'system'                                   OKAY [  2.879s]
Sending sparse 'system' 3/5 (521678 KB)            OKAY [ 14.446s]
Writing 'system'                                   OKAY [  4.476s]
Sending sparse 'system' 4/5 (522239 KB)            FAILED (remote: 'data too large')
fastboot: error: Command failed

Android tools are latest version:

adb version
Android Debug Bridge version 1.0.41
Version 30.0.5
Installed as /usr/bin/adb

I tried to look through internet and found that this can be caused by old version of android tools (but package manager does not know any newer and it is happening on x86 machine as well as on arm64) or wrong partition size. Does anybody have the same problem?

@applee thanks, that app looks good but not working for GSI build. I will try Gitlab-CI build as soon as possible if I will be more lucky there.

Finally I managed to setup propperly cellular data for my operator (O2 CZ). Trivial problem - fill the name of APN (on default it's empty). It would be great if there could be some default APN config file we could edit to have it set up.
@luksus do you have any idea if taking calls and sending/receiving SMS on Gitlab-CI build consumes any cellular data? Do we have any reliable tools to measure data traffic? I guess now that my Internet connection works even without WiFi I am ready to switch builds but I do have limited data (around 1.5GB per month).

Side note - during weekend I tried to flash Gitlab-CI build using Pinebook Pro but it seems like android-tools for ARM have some limitations as I was stuck on pretty old problem - system.img was too large to flash. (stopped on step 3/5)

@Luksus no, notification LED seems to not work at all. However it did not work well on default system as well so I overlooked that.

Hello @Luksus,
Regarding sudo upgrade: vibration feedback works for me but is a bit laggy now. I guess it takes around 0,2 - 0,5s to vibrate after tap on icon but it can be caused by slow loading of an app. Keyboard vibrations work but I have them usually off. However while typing I can't change sound volume of the keyboard. It just sits at its level even though phone is in silent mode.

Regarding time-bug: while describing my issue I rebooted phone this morning. It took around an 1hr to set right time, I guess I need to be more patient next time.

In the mean time I noticed an error with missing _apt user (command apt could not get rid of permissions) so I tried to add it manually. For now error is gone but I have no idea if I did it right or if this user has to be in specific group.

As soon as the Gitlab CI build will be able to make calls and sms, will hop on it and try but for now phone calls are important to me and I do not always have access to internet connection.

I had some time to play around with the phone. I did fresh install of halium-boot.img from your build and sideloaded ubports_gsi.zip

I found very annoying bug - System time is set to 1st January 1970 and does not matter if I have set auto or manual time set. After reboot the phone still counts since 1970.
I tried to fix that by running sudo mount -o rw,remount / and after that performing time change but without success. On next boot I have yet again year 1970.

I also tried to perform sudo apt update and sudo apt upgrade. Web browser seems to improve in performance but the time issue is still there. I also noticed the phone does not respect change of timezone and just sits with that picked on first boot during settings.

BTW, I noticed there is LineageOS build for FP3. Not sure if this could help but AFAIK SailfishOS build by default relies on Lineage so it might be helpful for UBports as well.

@Luksus yes, you understand right.

• halium-boot.img and CI system.img does not boot from fresh
• CI boot.img and system.img boot successfully

So far I found strange combination which works for me:

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

Hi @Luksus,
I tried to boot system.img and it worked on first try, no issues. In the meantime I executed sudo apt update && sudo apt upgrade so some package versions might have been different for me on previous build.
So far I was able to send and receive few SMS messages without need of reboot.

Here are some points:

• after fastboot flash system system.img phone successfully booted.
• post TWRP:
  • after TWRP phone did not boot
  • tried to flash system.img again, did not boot
  • flashed boot.img and system.img and successfully booted

After newly flashed system wifi did not appear to be working. However after reboot everything seems working. I also so far did not apply switching between two options you suggested.
Also issues I have been describing in previous post seem to be solved, in the next days I will be using this build and will refer how system works.