Feedback for v4.3

Fairphone 4 user here.

Since updating from /e/OS 4.2 to 4.3, WhatsApp audio calls have become unusable: incoming speech is heavily distorted/high-pitched (“Mickey Mouse” effect).

This was working normally before the update, so for me this is a clear regression introduced by the 4.3 stable OTA.

I understand that the issue is known and that a fix is currently planned for 4.4 in mid-October. From a user perspective, though, waiting several weeks for the next regular release is really not a good experience for a regression that breaks a basic phone function across apps such as WhatsApp and Signal.

I would strongly encourage a 4.3.x hotfix for the FP4 rather than waiting for 4.4.

3 Likes

Same for me, but on e-4.2-a16-20260814662908-community-lemonade (OnePlus 9). Turns out I had enabled that option “shortcut to prevent ringing” like @AnotherElk said, and I was pressing it without knowing (it’s not explained in Settings what the key combination actually is that you’re enabling). Stopped happening once I turned that off.

Take a peek at the post above yours, SVP. :wink:

1 Like
  1. Vendor Name: Fairphone
  2. Device name: The Fairphone FP6
  3. Version of /e/OS or Stock which existed previously: 4.0
  4. Is the device Rooted / Not rooted: Not rooted

The update was a bit confusing at the beginning: push message announced an available update. However, no update was found when klicking on that message. After 2 days, the update went trough.

I’m happy, that one of the issues I listed here ( Feedback for v4.1.1 - #82 by regenrinne ) seemns to be solved: the extrem high latency when accessing internet via Wifi disappeared. All apps running smoothly again. Thanks to the developers for fixing this. <3

If you just tap the enable/disable toggle there, no, but if you tap the “shortcut to prevent ringing” text (note the slim spacer dividing the text from the toggle, showing that text and toggle are different actions), then it is explained :wink: .

Official v4.3.1 build for FP4 will roll out tomorrow.

14 Likes

Great ! Thank you for taking into account the urgent nature of the Mickey Mouse issue.

3 Likes

Vendor Name: Google
Device Name: Pixel 5
Device CodeName: Redfin
Version of /e/OS which existed previously: 4.2 T Official
Is the device Rooted / Not Root

It was updated yesterday, and everything seems to be running smoothly since then.
Thanks for the great work!

Murena

Murena Two

eOS 4.2

not rooted

Ever since I installed 4.3, all functionality with the print reader is simply gone. It is not even in the device settings anymore.

Consequently, all the apps with which I used the print reader do not show said feature anymore as well.

Device: Fairphone 6 (FP6)
OS: /e/OS 4.3
Previous version: /e/OS 4.2
Not rooted

I haven’t noticed a lot of issues (not as many as listed here. I was very happy that the WiFi issue was fixed. However….

  • The Seedvault App has been added again but it often fails to create the local backup. I’ve already generated a support ticket for this. However, I was told it’s not officially supported :confused:
  • One thing I noticed tonight, the Advanced Privacy app doesn’t seem to be blocking the same trackers as before. Specifically, I have Business Calendar installed, and since the license doesn’t transfer without Google Play, I can only use the ad supported version. Prior to 4.2, it blocked the ads in the app, showing 5 or 6 trackers blocked. Now it only blocks 3, all Google trackers… so imagine my surprise tonight when I opened the Calendar and an advert started playing. It seems Advanced Tracking has a different block list. I’ve gone back to RethinkDNS, which I was using during the 4.2 wifi issue.

Other than these two issues, I’ve not had that many problems.

On my part as well big thanks and thumbs up! :+1:t2::+1:t2:

Good Morning.

Updated to 4.4-beta-a16-20260930683167-official-FP4

right now on FP4 => Voip calls on Signal sound normal.

:smiling_face_with_sunglasses:

(20 characters added)

3 Likes

Same notification on my Pixel 8 w/ official 4.3, though it’s much less annoying than the previous account manager and sync issue notifications which were coming in several times an hour

I have a new problem on my FP4. FritzBox VPN makes my device restart after a couple of seconds. I have tried the website of my teslalogger and my smarthome (iOBroker). At home they work, via VPN the device reboots.

How can I fetch a protocol to give you more hints?

Try tailscale its works very good

Thank you for the tip. But this might be a new symptom since the problem occurs since 4.3. 4.2 has worked perfectly via IPSec.

  • Vendor Name: Fairphone
  • Device Name: Fairphone 4
  • Device CodeName: FP4
  • Version of /e/OS which existed previously: 4.3-a16 official → 4.3.1-a16 official
  • Is the device Rooted / Not Root: Not rooted
  • Is the Bootloadeer locked / unlocked: Locked

After update to 4.3.1 everything works as expected:

:white_check_mark: Cellular calls
:white_check_mark: VoIP calls (no chipmong anymore)
:white_check_mark: Miracast / screen mirroring

Thanks to the dev-team :birthday_cake:

2 Likes

Official v4.3.1 build for FP4 on A16 has been released.

  • Build was required to resolve the audio distortion issue reported in the build.
  • Releases Notes

It may not be visible in all locations and may take 1-2 days before being available for all FP4 users.

13 Likes

Same difference. That’s bad design. The toggle literally just turns on a key combination, yet it doesn’t tell you straight up what that key combination is, it makes you dig deeper to find that out. And once I went in I could understand why there’s a need for a submenu (you actually have options as to what the key combination should do), but at the parent level of display there’s no visual indication that tapping the toggle does something different from tapping the rest of the row the option is displayed on, i.e. that there even exists a submenu to go into (a simple vertical bar separator doesn’t tell me there’s a submenu, there’s no such metaphor in all the UIs I’ve used in my life).

Maybe I’m complaining in the wrong place, and this is just Google’s stupidity about their rules for Material-Shmaterial-yadda-yadda bad design concept (still very strongly influenced by the “flat(-brain) design” principles of not making all control and layout elements look distinct from eachother based on function, and distinct from the background they’re being displayed on).