[FP6] upgrade to 4.1.1. not available

[rlucassen]

Hello list,

2 questions:

1. I read Fairphone 6 (4.1.1) is now available on AOSP 16, but there is no A16 image available. The built-in updater says “No new updates found” (of course). OTOH, my other FP5 has the latest A15-4.1.1. Is this an error or did I miss something crucial somewhere?

2. When I used LineageOS there was no possibility to upgrade from one Android version to a newer version using the built-in updater. Is that still the case with /e/OS?

Richard.

[Lightning]

Hi @rlucassen,
it will officially released for FP6 tomorrow.
If you can’t wait: Builds – Django REST framework

[cad-forge]

Wondering the same, seeing people with updates talking about, no ota update available,

[rlucassen]

OK, thnx, and does:

“is_upgrade_supported”: false

mean that it is not upgradable using the built-in upgrade utility?

Richard

[piero]

@rlucassen

“is_upgrade_supported”: false

But previous one have “true”, that is important point.

[rlucassen]

As e/OS/ is based on LineageOS I think that’s the case. But I cannot find any docs on upgrading to a newer Android version. While for LineageOS there is a special page, although it is not mentionned anymore. I had OnePlus devices before and a newer Android version was pushed with adb.

R.

[dave]

See the OS OTA Information section in each week’s Development Updates thread, this week’s here:

@Manoj

Official builds get OTA OS upgrades.

[rlucassen]

Ok, it might depend on which device you have. On the OnePlus5T page it is mentiond “Upgrade to a higher version of LineageOS (e.g. lineage-20 → lineage-22.2)”

[piero]

@rlucassen

But I cannot find any docs on upgrading to a newer Android version

[HOWTO] Upgrade my /e/OS to major Android version without loosing /data

. [e] . since android T (13), lineageOS builds on witch /e/OS are based are expected to include the needed updated firmware partitions to make the build compatible without having to go back reinstalling the Stock OS (usefull for first install, AND even more for upgrading custom android version) for most of the supported devices.. In order to be sure it is really possible in your case, you must answer those 4 questions : . What was the android version of the StockOS installed before /e/ …

[rlucassen]

Yes, I found that page, but I’m not able to answer Q1: I received the FP6 and immediately I put /e/OS on the device. Anyway, I’ll wait what will happen today I read somewhere that new releases are not released at the same moment otherwise the servers would explode.

Richard

[aibd]

@rlucassen

I read somewhere that new releases are not released at the same moment otherwise the servers would explode.

There you go … and OTA Upgrade (yes /e/ does rejig the Lineage updater to handle Android version upgrade for official devices only) is probably further limited by device, geographically and OTA Upgrade seems always to come last.

Do you have official or community?

• An earlier link you questioned was offocial

[rlucassen]

I run official version 4.0-a15. I never had a look at the community version. Are there some advantages compared to the official one?

R.

[aibd]

@rlucassen

Are there some advantages compared to the official one?

I suggest it is well worth subscribing to the weekly Development Updates - /e/OS community (previously linked already).

@Manoj

Devices with official builds will not have community builds showing up in the installation guides.

• The community versions of the devices we sell or sold has been removed from the documentation.
• We would prefer users to eventually shift to the official builds. That way the maintenance of the devices is easier and more efficient.

[rlucassen]

Well, I’ll stay with the official builds, I need the device for my work…

R.

[rlucassen]

Still no new version. There is a post in which someone says “clear the cache of the updater” but that does not change anything. Perhaps they discovered some issues in 4.1.1 or maybe the “is_upgrade_supported”: false is not correct, the “is_upgrade_supported”: true still points to the 4.0 version.

Anyway, I’ll wait, 4.0 works well over here for the moment.

R.

[aibd]

@rlucassen

Still no new version

Still valid:

@aibd

I suggest it is well worth subscribing to the weekly Development Updates - /e/OS community (previously linked already).

Week 31, Development and Testing Updates

FP6 A16 rollout may be delayed as we await some testing results. Will update on the rollout once we get the results.

[rlucassen]

I could’nt find a subscription button but apparently I overlooked it. I’m subscribed now.

And I’ll just wait, like I said, 4.0-a15 works well. And the

“is_upgrade_supported”: false

means the version will not be released?

R.

[aibd]

@rlucassen

I’m subscribed now.

Good to hear I did not recognise your familiar voice even with the non sequitur to OnePlus 5T.

[YeOldHinnerk]

Still no update available.

A bit more information than “we are looking into something “ would be nice. Can we expect android 16 before 4.2? is there a serious issue or something very specific? can FP6 users help somehow…?

[AnotherElk]

@YeOldHinnerk

A bit more information than “we are looking into something “ would be nice.

Was given here …

Week 31, Development and Testing Updates

Unfortunately, no. We await an EU Energy Label test results in order to proceed with roll-out for FP6 v4.1.1 build. These reports are available here. It has been made mandatory recently by for the newer devices we sell or sold. And should go out with each release - major or minor. The team is working on getting the reports ASAP so that the rollout may continue and also working on a mechanism by which it would not get delayed in each release. We expect to publish the FP6 v4.1.1 build by tomor…

… and renewed now …

Week 32, Development and Testing Updates

Reg the FP6 v4.1.1 A16 release. We await an EU Energy Label test results in order to proceed with roll-out for FP6 v4.1.1 build. These reports are available here. It has been made mandatory recently by for the newer devices we sell or sold. And should go out with each release - major or minor. The team is working on getting the reports ASAP so that the rollout may continue and also working on a mechanism by which it would not get delayed in each release. We await the full report from the EU …