Fairphone 3 (FP3) Port

Luksus

@purplecroc89
Uh, perhaps I did forget to merge my last changes?!
Did you take the artifacts from anbox branch or master?

Purplecroc89

@luksus
The artifacts from the master branch. I will retry to download and flash the last one from the master branch and see what happen.

Luksus

@purplecroc89 please try the anbox branch if you did not yet. Perhaps I need to trigger a new build first for the master branch...

Edit @Purplecroc89 :

So I just took a look and encountered, that theoretically the master branch should have worked. On the anbox branch my latest fixes were missing.
Now I updated it and did a new build and for me the recovery is (still) working.

Please try this boot-image (system should not matter, regarding recovery):
https://gitlab.com/ubports/community-ports/android9/fairphone-3/fairphone-fp3/-/jobs/968159027/artifacts/raw/out/boot.img

anditor

Hi!

I flashed the newest build and system image of the anbox branch. But the kernel is still from December 30.

Linux ubuntu-phablet 4.9.112-perf+ #1 SMP PREEMPT Wed Dec 30 13:19:35 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux

My hope was, with the newest images of the anbox branch, I can try out anbox. But the status tell me:

$ anbox-tool status
Kernel: NOT OK
System: NOT FOUND
Enabled: NO
Running: NO

So, am I doing sth wrong or does the kernel still do not support anbox?

Kind regards,
Andreas

Luksus

@anditor Hm no, that seems not right:
If this kernel would be able to run anbox, there would be displayed "Kernel: OK".

BUT: Even if it was "OK", it is currently not possible to do anbox-tool install, because it says, that the installation is not supported on arm64 devices yet. So this is no priority now, I just prepared the kernel, in case we will be ableto install anbox some time in the future.

Back to the current build: I also installed the latest one and I have the same issues as you described. It seems that I messed something up.
I first need to take a look and will inform you, if a new build is testable.

Luksus

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

Purplecroc89

@luksus Ok, thanks, i will try this

anditor

Thanks for feedback @luksus . The build from last night was still the December Kernel. Well, I will wait until you tell me/us there is a fixed one.

because it says, that the installation is not supported on arm64 devices yet

Ok thats not what I expected to hear. But thanks for clarify it. And of course, I can understand. There are still more important issues have to fix first.

Thanks for you work and time to port UbuntuTouch to FP3.

louisoquinn

Hello Luksus, hello everyone
I tried to flash Ubuntu Touch many times, using different artifacts, but it's not working. Maybe I missed something. Here is the steps I did :

Fairphone 3 unlocked
Fastboot OK
Flashing Android 9 stock image successful (I boot Android 9 to check, and it's working)
Then, I went to fastboot again, and flashed both boot.img and system.img from different artifacts
When I reboot, there is Fairphone bootscreen with "powered by android" on the bottom, and nothing happen.
I hope you can help me. It's been years I follow Ubports and I'm so thankfull you work on Fairphone 3 port Luksus Many thanks for that.

Luksus

@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... :crossed_fingers:
Because I cannot reproduce it on my Fairphone.

louisoquinn

@luksus Alright, yeah I saw that post
Even with older artifacts it seems that it's not working.
Let me know if I can do anything to help you by doing some tests (I'm not a dev, just a fan), and I hope these issues will be fixed soon

Altor

Hello,
Thank you for your port.
I succeed to install the last version of the port without difficulty (master artifact from 4 days ago).

I have one issue, the sound doesn't work when calling or when looking at a youtube video. I know that at the top of the installation there is a warning : " audio-module do currently not work with this port" but in the working section, the sound seems to work (Cellular: Incoming, outgoing calls is working, Sound : microphone/volume control work…)

When I press the volume up and down, nothing happen.

So, does the sound work on this port ?

If necessary, I could open a new post.

Luksus

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

Altor

@luksus hello,
Indeed, I have the fp3+... So everything is normal.

Luksus

Small Update:

Since today's update, automatic display brightness should work.

Either install latest OTA Update (only if it is smaller than 500MB) or flash one of the lates builds, see first post in this topic.

rd440

I am trying to build for FP3 using the instructions at
https://forums.ubports.com/topic/4964/fairphone-3-fp3
I am stuck at this line, as the directory fairphone/sdm632 does not exist.
"missing exfat modules: cd into kernel/fairphone/sdm632 and do: git submodule update --init --recursive"
Under ~/halium/kernel, I only have configs and test.
Did I miss any prerequisite?

Luksus

@rd440 Hi, looks like I forgot to mention, that you have to do another repo sync after adding the manifest file. Then the sources, given in the manifest, will be downloaded.
For further questions regarding building, please start a new topic, thanks.

Luksus

Hi,
I just created an initial post for my FP3+ Port.
Look here: https://forums.ubports.com/post/48578.

Janez

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

@janez Thanks. I updated the builds and now the links are working again.