Software Update: 3.A.0129.20210805 (unknown caller and zero brightness bugs)

[Incanus]

@Lilly-3

Habe nun mein altes S5 im August durch ein FP3+ ausgetauscht

Reichlich spät, da war das S5 dank fehlender Sicherheitsupdates schon seit Jahren unsicher. Ein Telefon aber als unbrauchbar zu bezeichnen, wegen eines Fehlers bei einem Provider, den man zudem noch umgehen kann ist dagegen schon ein wenig harsch.

[Lilly-3]

@formerFP.Com.Manager

We realize that the situation for those affected by the Caller ID and Adaptive Brightness issues has been quite frustrating. So, we’d like to share some updates and a bit more information in this post.

We can now confirm that our next software update will be released early November. This update will include a fix for the Caller ID issue and we’ll reverse the recent changes made to Adaptive Brightness.

Some of you have asked why we could not release the fix earlier. We found the root cause, but it is modem related, so the release process is more complex. We needed to do more tests and do the full cycle certification process (not only the Google Certification, but also the Operators Approvals process). Rolling back to the last working version, including the security update(s) means that we would still have to do the full cycle of tests and approvals.

Testing a new release means proceeding with some internal tests, running internal CTS (Compatibility Test Suite [image]), and doing field testing in some specific countries to run non-regressions test cases. We haven’t done external beta testing for the Fairphone 3 (other than network compliance), but taking into account our own research and feedback from the community, our plan is to implement a beta testing program when we roll out Android 11. We are also aiming to do a staged roll out for Android 11.

To shed some light on how to go about applying new security patches for a new release, these are the steps involved:

1. We get the source from Qualcomm/Android Open Source Project
2. When a new security patch comes, it is based on the original Qualcomm/Android Open Source Project source, so we cannot directly apply all the changes in a simple manner.
3. After resolving the conflicts, we have to test that it should not have any regression compared to the previous version.

Splitting security updates from application updates is technically doable but the cost would be significantly more, so for now we are combining both.

Hopefully this clarifies the process up a bit more. Once again, thank you very much for your feedback and sincere apologies to all Vodafone Germany users who have been affected by these issues.

And this answer comes after two months ?? In my time as a software developer, customers were treated differently. The FP3 + was my first and last model from Fairphone.

[Lilly-3]

Leider kann ich den Work-a-round nicht nutzen, da wie geschrieben hier in weiten Bereichen das 3G schon abgeschaltet ist. Wenn ich mit 2G telefonieren möchte, hole ich mein altes Nokia wieder raus. Sicherheitsupdates hin oder her, es muss ganz einfach zum telefonieren geeignet sein.

[anon9989719]

As above and implied before, it would be comforting at least if this info

@formerFP.Com.Manager

We needed to do more tests and do the full cycle certification process (not only the Google Certification, but also the Operators Approvals process). Rolling back to the last working version, including the security update(s) means that we would still have to do the full cycle of tests and approvals.

was published earlier or was this the earliest that such knowledge was available,???

[Incanus]

@Lilly-3

Wenn ich mit 2G telefonieren möchte, hole ich mein altes Nokia wieder raus.

Und wo ist der Unterschied beim Telefonieren zwischen 3G und 2G?

@Lilly-3

Sicherheitsupdates hin oder her, es muss ganz einfach zum telefonieren geeignet sein.

Das ist heute bei Smartphone allerdings in der Regel die am wenigsten genutzte Funktion. Außerdem funktionert es doch auch.

@Lilly-3

And this answer comes after two months ??

Ja, mit der zu einem Termin angekündigten Lösung. Die Nachricht, dass das Problem erkannt wurde und an einer Lösung gearbeitet wird kam schon früher.

[anon9989719]

I’m wondering if any of the concerned authors, above, have seen this?

@formerFP.Com.Manager

Splitting security updates from application updates is technically doable but the cost would be significantly more, so for now we are combining both.

@formerFP.Com.Manager

Some of you have asked why we could not release the fix earlier. We found the root cause, but it is modem related, so the release process is more complex. We needed to do more tests and do the full cycle certification process (not only the Google Certification, but also the Operators Approvals process). Rolling back to the last working version, including the security update(s) means that we would still have to do the full cycle of tests and approvals.

[urs_lesse]

First report of an FP3 update A.0130 (1.3 GB):

Nouvelle mise à jour – 3.A.0130.20211029

Bonjour, Après des mois d’attente, une mise à jour (3.A.0130.20211029) est enfin arrivée sur mon fairphone 3 et j’ai été surpris par son poids aux environs des 1.3 Go… Dans la description, il n’était question que de mise à jour de sécurité, ce qui m’étonne un peu… Y a t il une façon d’accéder à la liste complète des modifications apportées par cette mise à jour ? J’ai cherché mais je n’ai pas trouvé… Merci

[ontheair]

Had to use a translator, but: Very interesting!

I am surprised that there is an update, without an anouncement here. But nice, let’s see when it will pop up on other people’s phones!

[anon9989719]

Not here in the UK on EE as of 10:54 GMT

[Martin_Mattausch-Wie]

Amazing… lets roll out the update in france first. Not in the country wich is heavyly affected by the unknown caller bug since two months… lets do exactly that!

[anon9989719]

The roll outs have to be checked by the networks and carriers. Maybe they did Germany first but the networks are not happy and won’t push it.

It’s not just a Fairphone process

[anon93683458]

Hey, I haven’t got a Fairphone yet… but I can fully understand how frustrating this issue is. I hope the the update comes in the next week or so.

[Thomas23879]

Hi,
you said: This update will include a fix for the Caller ID issue …
I`m still very disapointed!
There ist still no update and no solution.
Did I miss it?
regards
Thomas

[anon9989719]

Hi Thomas.

You haven’t missed a thing

The next update, a cure for this one, hasn’t gone wild yet, although there is some notion it is imminent.

[Alain_Guillet]

Usually, people add a print screen of the update. You can see that it is not the case here so I find strange this information especially because nobody else said the same, not even in France

[OldRoutard]

Well, for that to happen, you need to have a FP3, be using the standard OS, have Sosh as your operator (OK maybe Orange as well, who knows?), be interested in Android updates, be familiar with the Forum and know enough of the etiquette to leave a screenshot. What’s the probability?
And yes, two people in the other thread have notified having received the update.

[Mic57]

Hi, just to confirm it , I could manually find the update. As you can see , security patch level from October the 5th. The original update of this thread was not available for me ( Sosh is my provider). So I had no unknown caller issue and I do not have it after updating at least I had only calls from my contacts but no issue so far

[Alain_Guillet]

It seems my expectations are too high…

@Mic57 Thanks for the print screen

[anon9989719]

No such thing as too high, just need to balance it

I have seriously high expectations but even greater disillusionment, so it can’t get worse.

[StevenHachel]

@formerFP.Com.Manager

early November

early November, middle or end november?