/e/OS ships in several flavours. The build type tells you who built it, which keys signed it, and whether it receives updates. It is also part of the file name.

TypeBuilt bySigned withOTA updatesOTA upgradesPublic downloadRelease frequency
official/e/OS infrastructureOfficial keysYesYesYesMonthly
community/e/OS infrastructureDevelopment keysYesNoYesMonthly
test/e/OS infrastructureAndroid test keysNoNoNoOn demand
UNOFFICIALExternal contributorsTheir own keysNoNoNoSet by each contributor
custom/e/OS or external usersTheir own keysNoNoNoSet by the ROM builder
Monthly

Official

Murena smartphones, built from a released and tested community branch.

  • Available for Murena smartphones.
  • Go through additional and longer testing cycles.
  • Built on the /e/OS infrastructure and signed with /e/OS official keys.
  • Have a maintainer and receive regular OTA updates.
  • Users can also download the files and install them manually.
  • Device flash packages use the IMG-e- prefix and include images plus a flashing script.
  • Previously called stable builds.
Example
IMG-e-4.2-a15-20260816-official-FP4.zip
Naming format
IMG-e-<version>-<android-version>-<yyyymmdd>-official-<device>.zip
Monthly

Community

The latest /e/OS development code for your device.

  • Built on the /e/OS infrastructure and signed with /e/OS development keys.
  • Released after testing, but may still contain non-critical bugs.
  • Receive regular OTA updates.
  • Available for download on /e/OS websites.
  • Previously called dev builds.
Example
e-4.3-a16-20260918677977-community-tegu.zip
Naming format
e-<version>-<android-version>-<yyyymmdd><build-number>-community-<device>.zip

Version support policy

/e/OS produces community builds for a device on the 3 most recent AOSP versions available for it. Within a given AOSP version, devices keep receiving the regular OTA updates mentioned above (security patches and /e/OS feature updates). Moving to a newer AOSP version is an upgrade, not an update: it is never delivered over the air, and requires manually flashing the new build.

AOSP stops providing security patches for a given version after about 3 years — past that point, continuing to publish /e/OS updates on top of it brings no security benefit, which is why community builds are not maintained indefinitely on older AOSP versions.

App Lounge will soon be able to check for and install updates to system apps (for example the Browser) independently of the AOSP version, so devices keep receiving the latest updates for those apps even without a full AOSP upgrade.

On demand

Test

For developers who test and debug applications or platform changes.

  • Built on the /e/OS infrastructure and signed with Android test keys.
  • Use the default Android test keys and enable full ADB access at boot.
  • Do not receive OTA updates.
  • Not publicly available on /e/OS websites.
  • Release frequency depends on development and testing requirements.
Example
IMG-e-4.2-a15-20260816-test-FP4.zip
Naming format
IMG-e-<version>-<android-version>-<yyyymmdd>-test-<device>.zip
Set by the contributor

Unofficial

Made by external contributors. Install at your own risk.

  • Made from /e/OS source code without additional source modifications.
  • Not supported by /e/OS, and may not have a maintainer.
  • Do not receive OTA updates.
  • Not published by Murena and tagged as UNOFFICIAL.
Example
e-4.2-a15-20260816-UNOFFICIAL-FP3.zip
Naming format
e-<version>-<android-version>-<yyyymmdd>-UNOFFICIAL-<device>.zip
Set by the ROM builder

Custom

Made by /e/OS or external users. Install at your own risk.

  • May include changes to /e/OS sources or device-specific code.
  • Not supported by /e/OS.
  • Not publicly available on /e/OS websites.
  • Release frequency depends on the client or ROM builder.
Naming format
Defined by the custom ROM builder.