How do you know that’s not done further with the v4.0 ?
I think you should think about that there is not only one team.
I would imagine that one team or more are responsible for the differents tools, one for the os, one or more for the cloud stuff.
For me it would mean that we wouldn’t set the whole devs for the issue in a phone, even if that is a big issue.
Some guys have no glue how it works on the FP6.
Only the team and some experts are organized for it.
And I’m pretty sure that all who knows about FP6 and are organized for it, are working further on it.
And maybe they need some more alpha tester.
Then I’ll suggest you to propose yourself as tester.
How do you think about it? if it’s so urgent for you. 
1 Like
Where do I sign up for the alpha testing?
you can enable it into the " → settings → developer options " menu.
1 Like
@Manoj the feedback thread for 4.0 is still missing, whilst 4.0 already rolling 
FP3 have a major upgrade to Android 15!!!
FP3 is now available on AOSP 15
I’m so happy. Thanks team for your work!!
Now i must wait the update’s notification.
8 Likes
Great launch!
When is the deployment of 4.0 happening!
1 Like
Ah oui merci 
@Leap follow the instruction of piero in the developer options there is a section /e/os options for developers where you could activate the connection to the test channel and the /e/os telemetrie.
seems that you could make a shortcut to the bug report, and have some options about some debug info and type of reports…
We have started the rollout of v4.0. Please note this is a major release and includes multiple new features.
Staggered Release: 11 June to 22 June
4 Likes
Was waiting for the formal internal announcement from the build team about the release of builds being started. Have created the feedback thread here
3 Likes
Is CMF completely abandoned?
No A16 planned update
No 4.0
No bug fixes
I don’t want to sound ungrateful for all the hard work you guys are doing.
It’s awesome and I’m so happy I can use a privacy focused phone, but had I known that a device with an official build and that was being sold on the store was not going to get worked on I wouldn’t have bought it
No device is abandoned. For the Nothing CMF Phone 1 tetris the plan is to jump to A16. I guess I had mentioned this earlier in another post.
The only case in which a device would not get a A16 would be if the device does not support A16 for whatever reason. For example, very old devices may not work with latest OS versions.
CMF should also receive v4.0. It is a staggered release, and the entire release process will take a week to complete.
3 Likes
Understood, thank you for the reply
Sorry if I sounded ungrateful, was just a bit frustrated when I saw all other devices were getting v4.0
You guys really are doing awesome work
Thank you to everyone working on this project
Users with S9 and GS290 when flashing the A15 builds when it is released will need to format their phone before the install to avoid the FDE encryption issue.
The following device builds on A16 failed during the compile process of v4.0
| Vendor | DeviceName | CodeName | OS |
|---|---|---|---|
| Lenovo | Z6 Pro | zippo | A16 |
| Motorola | edge 20 | berlin | A16 |
| Motorola | edge 2021 | berlna | A16 |
| Motorola | edge 30 | dubai | A16 |
| Motorola | moto g200 5G | xpeng | A16 |
| Sony | Xperia XA2 Ultra | discovery | A16 |
| Sony | Xperia 10 | kirin | A16 |
| Sony | Xperia 10 Plus | mermaid | A16 |
| Sony | Xperia XA2 | pioneer | A16 |
| Sony | Xperia XA2 Plus | voyager | A16 |
We will attempt to retry these device builds and release with v4.0 else they will be added to the next build release which would be v4.1 in a months’ time.
please, S9 means only S9 or S9 and S9+ ?
thanks.
An update I have from the development team is that v4.0 A16 is currently on lineage-23.0. The team may not move to 16.2 but directly go to A17 once it comes out.
2 Likes
on fp4 here (community a15 3.7.3, 4.0 already listed under a16).
will 4.0 become part of an ota-update anytime soon for current a15-users? if yes, will this update a15>a16 ota?
or is a manually update a15>a16 with the 4.0-image the only way to get 4.0 / a16? if this is there a way to preserve current userland? or would this flash everything?
thanks for your help.
/e/OS updates are not bothered if they ascend point updates or to a new whole number.
community build users should expect to do Android version upgrades manually. The official advice is to treat this as a new install because it is known to be a major amount of work to provide OTA Ugrade of Android version in official builds which expect to be performed error free and without loss of data.
With murenacloud plus seedvault plus one’s own backup of essentials then
- Fresh install or
- a dirty upgrade, [HOWTO] Upgrade my /e/OS to major Android version without loosing /data
just depends on user preference for a little risk or “Fresh and clean”.
Search the forum for other user stories fp4 for more reassurance for your phone.
Unknown till published, but maybe not.
1 Like
Thank you for the informations! dirty upgrade does not work, all described cases tried. the 4.0 image seems to lack basic information this upgrade-process needs (stopping in all cases untouched).
any alternative then? beside a fresh install or waiting for ota, hopefully with an option going a15>a16 with 3.7.3-4.0?
The ROM you are using must not contain IMG- in the name. If it does you need to delete those four characters from the url and / or read the approiate part of the guide.
If you are using the OTA_PACKAGE please try to describe the method / error.