Software update: FP4.FP44.A.149.20220722

Hi everyone :hibiscus:,

Our latest software update for Fairphone 4 users is now available.

Software Version: FP4.FP44.A.149.20220722
Security Patch Level: 5th of July, 2022
Update Size: 90.96 MB

List of changes:

  • The camera’s auto-focus and white balance features have been improved.
  • The network compatibility for some carriers has been enhanced.

Please note:

Together with our partners, we test the software before its release, and in some instances where a software update might result in some problems for users on a specific network or in a specific country, we prefer to delay the software release for that specific customer base and fix all the potential issues before making the software available to everyone.

That means that depending on your network provider, some Fairphone 4 users may receive this update later. Once the update is available you’ll receive a push notification to automatically update.

16 Likes

Installed without issues, can’t wait to try out the new camera tweaks :tada:

4 Likes

Updating here. Also looking forward to the update.
Where can we deposit requests? I noticed that the phone’s display comes on when new notifications arrive, when the phone is in grey-screen/bedtime mode. That defeats the purpose, I’d think, and it can be a bit annoying/distracting too.

Update went smoothly. Unfortunately selfies are still mirrored. Request is on hold for months.

7 Likes

Update is 100% fine. :slight_smile:
Thank you for keeping us and our devices up to date.

Link to the ota.zip, as usual.

3 Likes

Make sure you configure your phone to your preferences :slight_smile: Check “keep the screen dark”. Battery saver does the trick as well.

2 Likes

Will this update make Fairphone 4 work better on US networks?

Updates are sent to networks for checking so the roll out is bit by bit, but I imagine there is no roll out to any US networks so you can only try and hope the basics work and work a bit better.

After the update, I lost the 5G connection exactly every ten seconds. I am using o2 Germany with a physical SIM card. Restoring the default APN settings fixed the problem.

boring terminal output
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=108 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=39.4 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=150 ms
From 192.168.29.89 icmp_seq=4 Destination Net Unreachable
64 bytes from 1.1.1.1: icmp_seq=5 ttl=52 time=34.3 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=52 time=34.1 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=52 time=32.9 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=52 time=32.5 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=52 time=32.3 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=52 time=34.5 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=52 time=34.5 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=52 time=40.5 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=52 time=36.0 ms
From 192.168.29.89 icmp_seq=14 Destination Net Unreachable
64 bytes from 1.1.1.1: icmp_seq=15 ttl=52 time=32.9 ms
64 bytes from 1.1.1.1: icmp_seq=16 ttl=52 time=38.1 ms
64 bytes from 1.1.1.1: icmp_seq=17 ttl=52 time=43.0 ms
64 bytes from 1.1.1.1: icmp_seq=18 ttl=52 time=34.8 ms
64 bytes from 1.1.1.1: icmp_seq=19 ttl=52 time=36.6 ms
64 bytes from 1.1.1.1: icmp_seq=20 ttl=52 time=34.8 ms
64 bytes from 1.1.1.1: icmp_seq=21 ttl=52 time=34.4 ms
64 bytes from 1.1.1.1: icmp_seq=22 ttl=52 time=33.1 ms
64 bytes from 1.1.1.1: icmp_seq=23 ttl=52 time=38.2 ms
From 192.168.29.89 icmp_seq=24 Destination Net Unreachable
64 bytes from 1.1.1.1: icmp_seq=25 ttl=52 time=33.2 ms
64 bytes from 1.1.1.1: icmp_seq=26 ttl=52 time=31.8 ms
64 bytes from 1.1.1.1: icmp_seq=27 ttl=52 time=32.8 ms
64 bytes from 1.1.1.1: icmp_seq=28 ttl=52 time=29.9 ms
64 bytes from 1.1.1.1: icmp_seq=29 ttl=52 time=34.7 ms
64 bytes from 1.1.1.1: icmp_seq=30 ttl=52 time=33.0 ms
64 bytes from 1.1.1.1: icmp_seq=31 ttl=52 time=33.8 ms
64 bytes from 1.1.1.1: icmp_seq=32 ttl=52 time=32.8 ms
64 bytes from 1.1.1.1: icmp_seq=33 ttl=52 time=33.8 ms
From 192.168.29.89 icmp_seq=34 Destination Net Unreachable
64 bytes from 1.1.1.1: icmp_seq=35 ttl=52 time=32.0 ms
64 bytes from 1.1.1.1: icmp_seq=36 ttl=52 time=35.6 ms
64 bytes from 1.1.1.1: icmp_seq=37 ttl=52 time=46.0 ms
64 bytes from 1.1.1.1: icmp_seq=38 ttl=52 time=51.1 ms
64 bytes from 1.1.1.1: icmp_seq=39 ttl=52 time=50.6 ms
64 bytes from 1.1.1.1: icmp_seq=40 ttl=52 time=39.5 ms
64 bytes from 1.1.1.1: icmp_seq=41 ttl=52 time=32.7 ms
64 bytes from 1.1.1.1: icmp_seq=42 ttl=52 time=37.9 ms
64 bytes from 1.1.1.1: icmp_seq=43 ttl=52 time=31.9 ms
From 192.168.29.89 icmp_seq=44 Destination Net Unreachable```
3 Likes

Thank you for that. I had completely missed that option.
It’s perfect. :slight_smile:

2 Likes

Installed without issues, thank you. Where can I find a A.149 boot.img?

The kernel page should usually get updated in the not too distant future.

If you need it quicker, you can extract it from your running system after you updated (needs root):

  • Note down the slot you are currently in adb shell getprop ro.boot.slot_suffix
  • Copy the corresponding boot partition adb shell su -c dd if=/dev/block/by-name/boot_a of=/sdcard/boot.A.149.img
  • And pull it to your PC adb pull /sdcard/boot.A.149.img
2 Likes

Thank you @hirnsushi !

When will the new boot.img be uploaded to Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation?

Depends, sometimes it takes hours, sometimes days, no idea how that process works :man_shrugging:
I’ve uploaded you one here. Nope, that’s a Magisk patched one, I’ll upload another one in a second.
Here’s a stock boot.img.

Oh, and welcome to the community :wave:

3 Likes



What is happening with the image processing?? Stock camera put a very agresive noice cancelling filter over it
Gcam has way more details?

5 Likes

Wow, that’s terrible. I really hope that we get access to all cameras through the API as soon as possible.