Software Update: 8901.4.A.0016.6

Discuss The Products
, ,
25

Yes, this works around the issue, but is not a fix.

Bugs in version n-1 that were fixed in version n, but re-occur in version n+1 are a symtom of poor engineering and even poorer quality control. Each new version becomes a Pandora's box ("What is going to be broken (again) when I install this patch?"), which is definitely not the way it should be.

I also strongly detest the (very common) ‘but we have a workaround’ attitude, because it puts the workload to get the system to function properly on the customer (and forum members) instead of the developer where it should be.

7 Likes
26

A thought … how feasible, I don’t know, but a thought nonetheless :slight_smile: …

The Fairphone 3 is an A/B device. It holds two OS installations at a time, after an update the old version is still there. User data is shared (not doubled).

The cool thing is … users should be able to switch the OS slots and thus boot the old version (by disrupting the boot process into the new version a few times intentionally, if more convenient methods are unavailable with a locked bootloader?).

The “uncool” thing is … rollback protection. With obvious good intentions, this mechanism breaks the possibility to simply fall back to the old OS version in case of obvious trouble after updating, because if the old version is on an older security patch level (which it usually is), a factory reset will be needed to boot the old version, user data as well as user-installed Apps and their data will be deleted.

This kind of bugs me, conceptionally.
The result of this protection is that a quick and practical fix for users in case of serious issues after an update is disabled for a gain many affected users would legitimately consider much less important, if given a choice.

What if OS updates could be split into updates which do substantial changes while keeping the same security patch level date as before … and later updates which only raise the security patch level date?

This way, after a feature update the possibility to fall back to the old OS version in case of obvious trouble would be left intact, because rollback protection wouldn’t kick in?
And a later update ideally just raising the patch level date wouldn’t break stuff and could be started by users once they are sure they don’t need to fall back?

I don’t know whether the deed of only raising the date is left to the discretion of the OS vendor, or if raising the date would have to be bundled with actual security patches. In the latter case, leaving 1 patch undone until the date-raising update should do the trick.

Wouldn’t this be possible?

6 Likes
27

New problem seemingly related to this update

28

@formerFP.Com.Manager WPA3(SAE) networks are not shown anymore and no (auto)connection possible since update.

29

@Cookie WPA3 was already not supported on Android 10 and the previous Android 11 releases (only some Android 11 beta versions had WPA3 support enabled, which was a mistake). FP3 is not certified for WPA3, therefore we cannot enable it.

30

WPA3 was already possible with Android 10 release versions on the FP3 and was disabled with update 8901.3.A.0077.20201221.
See: Is WPA3 officially supported? As it does no longer work

31

Facing the same issue with Bluetooth earphones with the FP3 after this update. Is there any fix for it?

32

The only things we can do are:

  • wait for an update
  • downgrade
  • switch to /e/OS or that other one
  • get a new phone without that update installed

No workarounds or fixes are known. We’re stuck with this issue for now. Devs apparently are aware of it but there’s no timeframe when we get an update solving it.

2 Likes
33

I noticed another issue:

I’m using Tasker to do various little things for me. For instance, Tasker sets the audio-level for media to the highest value and sets the ringer volume to zero, activating vibration mode. Tasker has done that when I connected the phone to a bluetooth device (box, headphones, car).

Now, after the update, Tasker no longer sets the media-volume to max.

Maybe someone could try and verify/falsify.

Thanks in advance

34

In addition: I have made some tests on Tasker and the bt-functuonality.

I let Tasker get the weatherforcat and read it aloud when connecting to my car via bt. I do the same for calender entries. The phone connects to the car bluetooth and both things work. I get the weatherforcast and the calender is read.

Then music should start either via FolderPlayer or via VLC. But… nothing. Not only is the external bluetooth communication down when it comes to media control, but there is something broken internally, too, because music wont start automatically.

Maybe this helps to narrow down what happend.

35

Issue with diminished audio volume on Bluetooth devices after updating to 8901.4.A.0016.6

36

Same here! I was wondering now since two weeks until thought of checking the forum. :unamused:
It seems to be a general problem, before this update everything worked fine…

37

I can report a couple of other problems with Bluetooth.

  1. most of times the phone doesn’t connect with the Bluetooth car system by itself, I must go in the car settings, select the Fairphone and click on “connect”;

  2. always in the car, the “recent call” list is no longer sent to the car system. I can only make calls by selecting a number in the contact list, I don’t have any list of recent calls to choose from.

This is annoying.

I’ve quickly checked the forum and I can’t find any information from Fairphone about when a fix will be made available.

This is really annoying.

Ciao,
Max

38

That’s not unusual as they don’t predict when they can fix an issue and they are no doubt responding to support complaints, of maybe of a more pressing nature, and are not ‘readers’ of this forum.

39

If I were Fairphone I’d just write something like “We read about the issue you reported, we made an analysis and we find there is a problem in the last update we released. We’re sorry for that, we’re working to solve it. You’ll get an update by end of this month”.

It doesn’t cost much time, it’s not a contractual agreement to solve the problem by 30th Sep 12:00PM, it makes you feel there is someone working on your problem, it would probably prevent tens of people to open support tickets that cost time to manage that they could better use in solving the problem, and gives you that feeling of “community” that I’d expect from a company such as Fairphone (and that I’ve already found many times in these two years as a FP user).

It’s just about paying little attention to those little things that can make a difference in your relation with customer.

Ciao,
Max

3 Likes
40

Why would they read about your issue? Surely a user would contact them and not rely on the forum.

I doubt they have made an analyisis to pin the problem to the last update, especially if they have to red the forum to know some users do have > how many > all the variables

So they are not working on it most likely so why say they are. They probably haven’t found the ‘problem’ software wise

When you say update do you mean a software update or just an indication that analysis is gathering momentum. ?

41

there is a way more important issue with broken NFC preventing people to measure their bloodsugar and this was picked up directly by Fairphone and a patch created and all this is communicated here in the forum. They cant comment on each an every annoying bug and yes its annoying but really nothing important like the health related NFC issue.

2 Likes
42

The update broke bluetooth control completely. The Fairphone is not usable for me like that as I’m using those broken features extensively.

This is not the first time an update broke important features of the phone. Meaning that there is a clear quality issue. This would not be a problem if we need to wait a month for a fix. It probably takes months though (as experience suggests).

I can’t recommend the phone like that to anyone. It’s clearly broken repeatably.

1 Like
43

I understand, you can still use the BT devices, you can just not use the devices control buttons and you can still control the device with the Fairphone, correct? Thats annoying yes, in my eyes not unusable. Not everyone is hit by this bug, btw.
Funny off topic thought that come to my mind: when it was announced the FP4 would come without a headphone jack, reading the forum one could get the impression BT devices are only rarely used. now that BT is partially broken, reading in the forum gives the impression BT is the most important feature of a phone.

Back to the topic: reading this, I’m wondering what settings the broken devices use?

44

It’s clearly more than a little annoying to have such software failings and almost insulting to get an update, which by accounts implies some improvements, only to find a ‘new’ failing.

I acknowledge your stress and likewise wouldn’t recommend the Fairphone on that basis.

I would draw anyone’s attention to these repeated failures and point out that’s the cost of a small company investing in fair trade for those that source the minerals and manufacture the phone.

So far I am prepared to pay that cost. However I don’t use bluetooth in the ways described and haven’t had this issue.

So you say it “The update broke bluetooth control completely” and does that refer only to a particular bluetooth headset you have? Maybe you would like to name the device and I hope you have contacted support offcially so they understand the range of devices that are not functioning as expected.