Hello everyone. Please tell me what the differences are, I don’t see any difference, there is also a guide but it doesn’t match the data written opposite the ROM, I see Official, Community, Test, Unofficial, Custom. For example:
/e/OS Recovery for community build ???
/e/OS build : R community ???
Are these two community builds?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
in your case, please have a look at the adress bar…
If you want the stable release you may want to have the stable/s3v3gds. If you want the dev, then the /dev /s3v3gds. Community builds are dev versions. Ye not intuitive i know.
it is not your first fake comment…
Then please let me know.
stable builds only exist for devices that have been sold by Murena…
Murena proudly present: Stable builds for FP2, a device never sold by Murena 
… /e/OS stable FP2 download
Let’s say stable builds originally were intended for devices sold by Murena (or the e foundation back then), but it didn’t stay this clear-cut over time.
Side-topic :
Also in the past there were stable builds for some devices intenting to work with the “easy-installer”
Guys, sorry, but I still don’t understand the logic of whoever wrote this)) Here’s how it could look (I’m giving away advice for free))
/e/OS build = > Stable
/e/OS build = > Dev
/e/OS build = > Community
/e/OS build => Unofficial
/e/OS build => Custom
/e/OS build => Test
The links and pages are the same! Where is stable and where is Dev, etc.?
There’s a renaming process going on currently. Dev is becoming “community”, stable is becoming “official”.
While dev/community and stable/official are out there in general, stable/official is not available for every /e/OS device. For the majority of /e/OS devices there’s only dev/community.
So …
For s3ve3gds there’s only community as per install guide … https://doc.e.foundation/devices/s3ve3gds/install … and only dev as per download page … https://images.ecloud.global/dev/s3ve3gds/ … which are two names (currently) for the same thing.
Both are on the download page:
Yes, apparently the build system and download pages didn’t get to changing the names from dev to community yet.
Thank you very much for your answer. If I understood you correctly, these links are the same, right?
Let’s look at another phone, for example, OnePlus 6 - “enchilada”. Install /e/OS on a OnePlus 6 - “enchilada”
Here, too, I do not see the difference, I open the links and the files are the same, where should I look to distinguish them?
Yes, obviously …
There’s no difference, and there needs to be no difference because OS install file and matching recovery are on the same download page.
Here’s an example with everything available … dev/community, stable/official, and respective recovery images (if applicable) … Install /e/OS on a Gigaset GS290 - “GS290”
If no recovery image is given and the OS install filename starts with “IMG-”, then it gets installed in a different way without involving the recovery.
You can find more examples by browser-searching official install doc (as opposed to community install doc) on the device selector page … https://doc.e.foundation/devices
I think at this point you are asking about
Imho, this duplication derives from old templates, but maybe not totally out of use for some devices.
I agree, it does add an extra layer of confusion as both the ROM and e-recovery are now packaged and displayed “on one line” as already well explained.
I guess, disregard the top arrowed line (for most devices) and you won’t experience the duplication. 
Not necessarily. I think the distinction is needed in the template at this point.
Not every device needs the recovery to install, so the recovery link doesn’t appear in every device’s install guide.
And if it appears, it is listed as a necessary download for the install, and as such it needs a link to where it can be downloaded, as the side-by-side listing on the download page hides the recovery image a little too much for some.
You can’t omit the mention of the recovery, and you can’t omit the link without risking more confusion. The duplicate link just comes from the same download page serving both files.
You make my point very well @AnotherElk.
The templates are adjustable, in the case of FP3 the three lines
appear to work nicely, the third line explains the lines above.
The image in my post which you quote, the inclusion of “to understand the difference” (as said by our OP) is not helpful in understanding
This topic was automatically closed after 90 days. New replies are no longer allowed.
