Fairphone 3 (FP3)

Janez

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.

007fred50

@Luksus Hej

i have installed GSI image V10 now, Fairphone 3 +

GSI:
Updates = Not Working
Vibration = Working
Camera = Not Working
Sound = Not Working
Turn Power Off = Working

GITLAB CI:
Updates = Working
Vibration = Not Working
Camera = Not Working
Sound = Not Working
Turn Power Off = Not Working (restarting)

So they have added new camera and sound modul

Luksus

@007fred50 did you also flash the halium-boot image again, for using it with the GSI?
I ask, because vibration should work here...

@007fred50 & @Janez Does the Notification LED work correctly in the GSI?`

Because it seems that it does for the GITLAB CI BUILT now.

007fred50

@Luksus Yes i flash the halium-boot image

I don't know there to trun the Notification LED on?

FP2andFP3-User

@Luksus
thanks for your support on FP3.
I'm testing both isos, but CI is working better and most of the stuff is running well.
SIM card is running
bluetooth is running
camera is working
sound is working
headset is working

I'm waiting for cellular data connection!
I could download you ISO 20 days ago and flash boot and system. Your last system build from yesterday I can't flash (fastboot flash system ...) . It stops always by 3/5 sending sparse 'system' and do nothing.

Do you know what is the Problem?

thanks

Luksus

@FP2andFP3-User Hi, and thanks for joining

I never encountered such an issue like you described.
Can you confirm that the archive is completely downloaded (~824MB)?
Perhaps, try to download it again.

The extracted size of the system.img, should be around 2.29GB.

Currently there is a new build running, which also should enable Notification LED.

FP2andFP3-User

@Luksus

I did download several times....

But okay i See the New iso running i will try it after work in the evening....

Janez

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

FP2andFP3-User

@luksus

great it works!
I have found the Problem:

Fastboot problem (file data too large) so i change to fastboot -S 300M flash system....

cellular data connection is now working.

LED Notification is also working on my FP3.

next step for me VPN with my own VPN server under lineage and linux it's no problem...but ubuntu touch with the strange VPN app hmm..I will test further

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.