Software update: 3.A.0107.20210513

@Mark_Jaroski @mmik922

Which network are you using, it may help someone to know ?

Finally the flash activation bug in the camera has been fixed, it was very annoying to me even if labeled as a minor bug.

1 Like

I’m not. I have an Fairphone3 with no symlock. I get updates directly from Fairphone.

I presume that that’s the same for everybody, no?

In any case the speed of this security update is cause for celebration.

Fairphone updates are provided OTA (Over The Air) via the network used unless a user downloads and installs the newer version manually. So some people/networks get it earlier than others and for some there is a along delay

1 Like

OK, So I’m on Swisscom.

I’ve had Pixel and Essential phones before the Fairphone, and have always received updates on release day.

1 Like

Not only Fairphone has released the update before Google:


Hi @Mic57 and @Antoine,

This should now be available. :slight_smile:


Obviously it is not clear to everybody, otherwise the question of why a patch level date was in the future would not come up. I don’t find your answer to my posting adequate.

I think @ontheair was only seconding your explanation, not criticizing it at all. :slight_smile:

1 Like

It may be common but clearly not common knowledge that an update can be over a month old and yet have a future date and I consider an odd way of dating.

So it means there will be no more until June 5th and that this update covers security patches up to 5th May.

For most users this is not a problem as they hardly take note of updates, if they even get them. But when interested people do note the updates clearer information would be helpful. Calling a May 5th update June 5th isn’t and there may never be a real June 5th update if there’s a delay.

1 Like

Indeed, it looks like “old”, but it’s not. Google releases monthly patches and distributes the stable ones for the next month patch cycle earlier to all the official Android phone vendors to have them ideally implement them until next official patch level date.

So if you search for Android security fixes e.g. at Android Security Bulletins  |  Android Open Source Project you’ll find the fixes for security patch level June not even released yet, because we’re still before the official date. From June 5th on, you’ll get to know which security patches were delivered in the Android source.

Oh and I note that the patch is pushed to the vendors at least a month before it is published in the bulletin, which means Fairphone had this patch probably late April ~ so it doesn’t address security issues in May ~ it’s an April 5th patch at best

to note . . .

Android framework issues disclosed in the May 2019 security bulletin, for example, were provided to Android partners at least as early as March 20th, 2019

Hmm… I don’t understand exactly what you mean. Now, Fairphone 3 states security patch level June 5th, so it includes all security patches until that particular security patch level announcement, even when it was delivered earlier than June 5th.

1 Like

I’m sure you got it wrong there.

What we got is something that is labelled “Security patch level 2021-06-05” because that’s what Google thinks everyone should call it.
The meaning of this label is “Security patch level of both android system and vendor software that gets announced by Google in June 2021”. Which I think is too long for normal communication :wink:

What we got a couple of days ago is “the full June update”.

The next thing we will get will be “the full July update”. It will have the label “2021-07-05”.

We may get it again early. Or we may not.

But in any case: Fairphone provided 2021-06-05 on May 29th. Google is likely to povide it on June 1st, or 3rd or 5th (these were the release dates of the last three bulletins according to Pixel Update Bulletins  |  Android Open Source Project). The “typical cheap” Android phone model will likely get it after May 5th.
But they all will get the same fixes (with exceptions in the vendor part; Qualcomm devices won’t get Mediatek fixes and vice versa for example).



True, that’s why I explained it and also gave the additional information that not only Fairphone did it, but also other companies (in this case: Samsung; including a link with more informations).

Ok, if you have further questions additional to my explanation or details that are not mentioned in the link I provided: Feel free to ask. If I know the answer, I will be happy to share it.

That bit I agree with, what I find odd, as @Amber has said, is that it is misleading.

It’s stated that Fairphone and other vendors get the update at least 30 day before it is publicly released.

So Fairphone were provided with this 30 days before they pushed it to the networks, which was 28/29th May.

This means the security issues that were addressed were from 30 days before that i.e. the end of April.

Am I missing something in thinking calling it a June update is a bit misleading if it only has security updates from April 28th at the latest.

You have two ways to date such an update : you use the date you created it or you use the estimated date it will be published. Google chose the second one for the security patch.

1 Like

That could make sense but it doesn’t as
a) in the first case it is created in April (given it is at least 30 days old when Fairphone get it (28th May) So that’s an April release.

b) there’s no estimated date Android always release on the same date the 5th of the month. However the published date is usually just before the patch update ???

So why not call it the may 5th Update and then the vendors have to verify it.

Not all vendors have the same capacity so some will release it before others but the update is the April security patch and some vendors may release it way down the line so 5th June is a bit random if your second option was the likely reasoning.

Still baffled ??

Hmm, I just said a german IT magazin said they get it about (=approximately) one month in advance to clarify why the release we got is an official release from Fairphone and nothing hacked as it was believed e.g. by @soeren_h before.

Maybe it is not exactly month in case, despite the magazine told, maybe it varies from month to month according to release fixing of Google and other contributors. At least it seems that it is not exactly 30 days or something fixed as @Ingo showed.

Google releases something labeled as FULL patch (as indicated by yyyy-mm-05) and mm means the official release month and 05 is the day some time in advance to the phone vendors to let them implement it.

1 Like

Maybe it helps to just think of it as a release number (that by chance looks like a date)?

Imagine it would be something like “10.21.0” and “10.21.1” where the “10” is Android 10, “21” is the 21st monthly update of Android 10. And “0” means “without” and “1” means “with” vendor patches.

And “2021-06-01” happens to be “10.21.0” and “2021-06-05” would be “10.21.1”.

What is so important about when the version is created as long as there is a clear scheme to identify the monthly updates? These labels are meant to have the level of “updatedness” be comparable among all manufacturers of Android smartphones. Would it really help if Fairphone called it “2021-05-30” and some cheap phone has their “2021-06-04” today which turns out only contains the fixes Fairphone got in their “2021-04-28”? And how would you know which of those version was released without vendor patches?