Fairphone 3 (FP3)

Luksus

@fp2andfp3-user OpenVpn to my home synology server worked for me so far.

Janez

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)

AppLee

@janez said in Fairphone 3 (FP3):

Do we have any reliable tools to measure data traffic?

You can try this app: https://open-store.io/app/datamonitor.matteobellei
See if it fits your need.

Janez

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

Luksus

@applee I tested this app already, but currently it seems not to work for mobile data. WiFi data is counted.

@Janez no I don't think, that using cellular features (telephone and sms) is using any mobile data.
I still don't know why it is needed to have a data-connection to use this features. I think it is just a bug of this port, which I need to figure out.

KoenS

@Luksus
Many thanks for the instructions and information you offer her

I bought myself a FP3+ yesterday and started trying to install Ubuntu Touch on this device.

For the moment, the OS is running, but I can't use my hardware (only the screen).
No sound, no camera, no mic,... I can make a phonecall but can't hear anything. On the other side also no sound.

Do you (or anybody else) can inform me what i did wrong, or what i can do to make the hardware operational?

Many thanks!

Janez

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?

KoenS

@janez
I had the same error, but i managed to solve it with adding this parameter at the end.
-S 522239K
Maybe it can help you.

Luksus

@janez you also can try this:
https://forums.ubports.com/post/43419

Luksus

@koens the issues on FP3+ seem to be caused by the newer sound and camera modules.
Do you know if they work with android 9? @007fred50 ?

KoenS

@luksus Dont know, I will install android 9 again and give it a try.

007fred50

@luksus No it does not work

I installd Android 9 and then ubuntu touch

Sound camera and more does not work

KoenS

@luksus Damn, I installed Android 9, same problem, no camera, no audio :-(.

So i suppose Ubuntu Touch is based on Android9? Any idea if and when an update will be available?

Janez

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

KoenS

Damn it, i'm tired of seeing the FAIRPHONE (powered by android) screen.

Yesterday i've got Ubuntu Touch working after installing Android 9, but nothing of the harware worked.
So today i reinstalled Android 10. Then i tried with /e/ which worked fine.

But i am a Linux user and the reason i purchasted the Fairphone 3+ was the capability of using Ubuntu. (I'm a iphone user since the iPhone 3 came out).

So I installed Android 10 again, then I tried both options from the first thread multiple times - allways preceded with installing Android 10 , but i allways get stuck on the FAIRPHONE logo.

I'ts time to go to bed now, wonder what i will do tommorow...

Luksus

Hi @koens ,
Yes, current ubports images for the FP3 are based on Halium 9 (Android 9).
Therefor you will have no luck, trying to install it on a Android 10 based FP3.

So we either have to wait for Halium 10, or somehow manage to get the drivers for the new modules into the Halium 9 port...

flohack

FP3 probably has a vendor partition that needs to be flashed with the Android 9 version. So either goback to stock ROM or LOS for Android 9 and then try again.

Janez

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

@janez I think it is better trackable, when you open issues at the gitlab repository.

About the call issue: does it happen, regardless how long the call is, or only if the call is longer than the time to auto-lock/display turning off?
About WiFi: I also encountered this issue from time to time, but not only on the FP3... I also got the impression, that it happens more often on specific WiFi-networks, for example at work, while it works without issues at home. But of course, that could be caused by the signal-strength, like you assume it. Naturally, the WiFi-radius at home is much smaller than at work.

I have another two issues:

From time to time (maybe every two days) it happens, that the phone will not wake up again. The display stays black.
I need to hard reboot (long press on the power button until it reboots), to make it work again.
Sometimes (it happened two times in the last 14 days) my sim-card "vanishes". That means, that there is only WiFi option in the Settings and all cellular functions are not available.
Even a reboot does not help always. Last time, I needed to switch to the B Partition (where I have the GSI installed), booted it and then switched back to the A Partition with Gitlab version.

Fla

@janez said in Fairphone 3 (FP3):

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.

This is a know problem with certain Access Point, probably not related to this port.