Week 13, 2025: Development and Testing Updates

/e/OS Smartphone Operating System Development Updates
1

Summary of weekly development and testing activities by /e/OS developers and volunteers. Updated content has the :new: emoji.

:warning: Server outage :warning:

Current status: :new:

  • Email: send and receive working

  • OTA device build download: Legacy OS builds like Pie, Q or R are not available.Users may get a file / page not found error if browsing. We will try to add these builds. ETA of when this would happen will be shared.

  • Murena cloud services and File Drive access :

    • Restoration of access to Murena cloud for premium services and users who made donations
    • Restoration of access to Murena cloud for free user ongoing.
    • All apps enabled on the Murena Cloud Dashboard. The sync for some of these apps may not be working for now.
    • The MurenaRecovery folder will not be visible right now. It will be enabled ASAP.
    • Team is working on enabling third party app access.
    • This week we start work on sharing access to users with IDs with the initial alphabet from p-z. This was the portion of the storage where we had the issues, that triggered the outage.
      -The slow progress is because we are being cautious with the opening up of the drives to avoid unexpected data deletions or data loss.

  • We will share a plan to compensate the loss of service to paying users . The details will be shared by the team over email and through the newsletter linked below.

Read GaĆ«lā€™s explanation and updates for the outage

Release

v2.9

Status: Pending release

ETA: Release starting from 31 Mar to 7 April

  • Notes app fix to allow sync with cloud coming with this release
  • Google pixel 8 shiba install process to be using a script which would be coming in the build. This is more of a documentation change.
  • Once the release is initiated we will share the release notes which will have details of all the changes and fixes coming as part of v2.9

Upcoming releases

/e/OS Installer replaces the EasyInstaller

The /e/OS installer has replaced the Easy Installer. You can check out the /e/OS Installer guide here.

Ongoing development tasks šŸ†•

  • /e/OS V or Android 15 related code work in progress. No ETA available on completion.

  • /e/OS GSI on T or Android 13. The team is working to see if GSI can be made available OTA. An app to detect what works and what does not work with the GSI is also in the works. ETA for release will be shared

 

Previous 5 releases & user feedback

Murena Cloud and Self hosting

:point_right: Upgrade work for v29.xx in progress

:star: Self Hosting current version v 26.0.8.23

  • Release notes

  • Check this guide for help with the upgrade
    :point_right: Next release - team to plan this development activity. ETAā€™s will be shared.

    • The self hosting guide is outdated. We will have that updated ASAP.
How to check the NextCloud version click here

You can find the complete documentation and current NC version under Login ā€“ Murena >> NextCloud xx user documentation. The xx should show the latest version.

  • Another way to check the current version is to check the NextCloud scan link and input https://murena.io this should display the current version number as well as the security level.

:information_source: Please note if MurenaCloud patch number is not the same as the NC patch number, the rating would show up as bad \U0001f610 This is not exactly a problem. We do not immediately jump to the next NC patch as soon as it is released. We first test it and then set out with the deployment.

GSI

  • Current GSI version is on /e/OS Q and v1.17

  • Download available here

  • Sources available here

:point_right: GSI OS version will next move to T or A13 skipping the R and S . Team is working on /e/OS T GSI. Will share release dates once available

 

OS OTA Related information

Completed

  • Fairphone: FP4 : S (A12) to T (A13)

  • Samsung: S9/9+ : R(A11) to S(A12)

  • Gigaset: GS290 : Q (A10) to A 11 (R)

  • Oneplus: avicii : A12

  • OnePlus : avicii : Q ( A10) R (A11)

  • Fairphone: FP4 : R ( A11) to S (A12)

  • Fairphone:FP3 : R (A11) to S (A12)

  • Fairphone:FP3 : Q (A10) to R (A11)

  • Samsung: s7 / s7+ : Nougat (A7) to Q (A10)

  • Samsung: s9 / s9+ : Oreo (A8) to Q (A10)

  • Samsung: Galaxy S9/9+ : Q (A10) to R(A11)

  • Samsung: s8 / s8+ : Pie (A9) to R (A11)

  • Teracube: 2e / zirconia: Q (A10) to R (A11)

  • Teracube: emerald & zirconia : R (A11) to S (A12)

  • Samsung: S7 ā€˜herolteā€™ ā€˜hero2lteā€™: Q ( A10) to R (A11)

  • Google Pixel ā€˜redfinā€™: S(A12) to T(A13)

  • Gigaset: GS290: R(A11) to S (A12)

  • Fairphone: FP3 : S (A12) to T (A13)

  • Samsung: S7/7+ : R(A11) to S(A12)

  • FP4: T (A13) to U (A14) :new:

  • S8/8+ R (A11) to S (A12) :new:

:information_source: All OTA OS upgrades are on stable or official builds

Testing
  • OnePlus : avicii : S ( A12) to U (A14)
To be planned
  • FP5
  • FP3
    (This means activity will be taken up once the team has the bandwidth.)
Our definition of an OS OTA upgrade

Usually for /e/OS ROMs to upgrade the OS you have to do the following

  • If available download the correct OS build from the supported device list

  • For some devices you also need to download the stock ROM from the vendor site.

  • Take a back up of your data

  • First install the Stock ROM

  • Next install the /e/OS ROM. Here you can take help of the install guides available on our documentation site.

  • If required apply the backups you downloaded before starting the whole process

An alternate to this tedious process is where we offer the user the option to upgrade the OS OTA. This option is available for stable device builds only.

This process is easy for the user but requires a lot of development and testing effort.

Different /e/OS build types

Misc information

Helpdesk services - Exclusively for paying Murena customers

:point_right: Murena helpdesk services will be exclusively for

  • Customers who purchased Murena devices
  • Paid for a Murena cloud account
  • Active donors from past year

Paying customers can write in here with issue details

:point_right: Users who use the /e/OS or Murena cloud for free will have the following modes for issue resolution:

Free services users will also get assistance on this forum for issues such as:

  • Gitlab Account opening related issues
  • Murena Workflow / cloud account issues

:warning: Please note, the old helpdesk emails IDā€™s are not monitored any more :warning:

Device and Vendor specific Announcements

Gigaset GS290

  • We have stopped the sales of the Gigaset GS290 on the eSolutionsShop as the vendor has stopped production of the device. We will continue support for existing users.

:loudspeaker: Message being shared on the request of our vendor partners

  • Vendors whose phones we sell on our eSolutions Store do not directly sell /e/OS flashed devices.

  • The vendors only sell their devices with their own stock ROM.

  • To get pre flashed /e/OS phones, you have to purchase them from the eSolutions Shop.

/e/OS Pre flashed device sales

  • We sell directly in EU, US, Canada and Australia

  • Find details of what devices are available in which countries here Murena Shop.

/e/OS website and social media Links and Support

Websites

Telegram Channel

Social Media

Newsletters

:warning: Do not post test build information on the forum :warning:

  • Please do not post information or links to /e/OS test builds on the forum.

  • These builds are as yet untested and under development and may in some cases cause user devices to soft brick.

  • Such information can confuse other users who do not see these builds in the updater.

  • Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds

  • If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team

  • As part of the testing team you can share your comments on the dedicated testing telegram channel.

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

13 Likes
2

Again no activity towards OTA for Murena FP5 :unamused:

2 Likes
3

Again activity towards security updates :partying_face: .

9 Likes
4

I agree with you. People get so anxious to get OS upgrades, that they forget how lucky we are to have a degoogled ROM with security updates.

Cheers

16 Likes
5

I donā€™t like being the booh-man but timely updates are still crucual. /e/ takes 6 Weeks for a security update while other roms take a couple of days or a week. Of course, this does not have to be the goal but 2 weeks should be the intention imo.

2 Likes
6

Seems to be a mistake there, S isnā€™t A10 but A12.

2 Likes
7

Thanks for pointing that out. Have corrected in initial post.

2 Likes
8

Hello Manoj,
I see youā€™re planning to release version 2.9 sometime next week.
Will the stable version of the OnePlus Nord have this update?
Because youā€™ve apparently fixed the update issues on 2.8, but havenā€™t made it available for this phone.
Thank you.

1 Like
9

Let me check and get back.

2 Likes
10

I just noticed that there are now ā€“ in addition to the most recent versions ā€“ official / stable versions of /e/OS Android 10, 11, 12 and 13 available for the Fairphone 3 and the Fairphone 4, all with March 2025 dates. Will these now allow incremental OTA upgrades to A13 for those stuck on A10, 11 and 12?

4 Likes
11

I would be really surprised if thatā€™s not the intention behind it, but I would be very interested in anybody actually trying whether it works.

1 Like
12

Still usefull for some old devices :

Released for all devices dropped with
e-2.2-r (android 11),

not yet accomplished for devices dropped in
e-1.17-q (android 10)
e-0.23-p (android 9)
e-0.21-o (android 8)
e-0.21-n (android 7)

13

The installation documentation now contains a note that the bootloader can only be relocked for official builds, if supported of course.
What does this information mean for devices such as the Shift6mq (axolotl), which only ever had a dev/community build, but you were able to close the bootloader thanks to your maintainer for this device? Will the Shift6mq get a closable bootloader again, as it was with the Android 13 version?
The documentation also has an section for relocking the bootloader.

14

Thanks for pointing that out. Will confirm with the device maintainer. If it can be locked will have the warning removed.

1 Like