Week 15, 2025: Development and Testing Updates

Weekly Development and Testing Activities

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


Release

v2.9 :new:

Highlights:

  • Notes app fix to allow sync with the cloud.

  • Release notes

  • OnePlus Nord avicii official build not released as testing is in progress. The build once released will include an A12 build which will upgrade to A14 OTA.


:warning: Server Outage :warning:

Current Status:

  • Email: Working

  • Device Builds: Legacy OS builds like Pie, Q, or R are not available. Users may encounter a file/page not found error. Efforts are underway to add these builds. ETA will be shared.

  • Murena Cloud Services and File Drive Access:

  • Access restored for users.

  • Apps enabled on the Murena Cloud Dashboard. Sync for some apps may not work temporarily.

  • MurenaRecovery folder not visible yet; will be enabled ASAP.

  • Team working on enabling all third-party app access.

  • Access for users with IDs starting from p-z is being restored cautiously to avoid data loss.

  • Notes sync with cloud possible post v2.9. It should start once users update to v2.9. If not syncing after upgrading to v2.9 …Take a backup of your local notes before proceeding… Log in your murena account . In dashboard >> Your profile (top right )>> Settings >> Client Synchronization (left side menu) checkbox is enabled . This should start the sync.

  • Users are advised to back up their device data as full restoration of sync may overwrite or delete local data.

  • Compensation: Details on compensating paying users for service downtime will be shared via email and newsletter.


Upcoming Releases


Your feedback required

:point_right: Thanks to all those who have already shared their comments on these posts.


Ongoing Development Tasks
  • /e/OS V (Android 15) code work in progress. No ETA available.

  • /e/OS GSI on T (Android 13): Team exploring OTA availability and app to detect compatibility. ETA will be shared.


Previous Releases & User Feedback


Murena Cloud and Self-Hosting

Murena Cloud

  • In Progress v29.x.x development work

  • Current Version: 28.0.9.6

  • Changelog

Self-Hosting

  • Current Version: v26.0.8.23

  • Release Notes

  • Upgrade Guide

  • Next release planning in progress. ETA will be shared.

  • Self-hosting guide update is pending.

How to Check NextCloud Version

:information_source: Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad :neutral_face:. This is not an issue; patches are tested before deployment.


GSI

  • Current Version: /e/OS Q v1.17

  • Download

  • Sources

  • Next Version: /e/OS T (Android 13), skipping R and S. Release dates will be shared.


OS OTA Information

Completed
  • Fairphone: FP4: S (A12) → T (A13)

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

  • Gigaset: GS290: Q (A10) → R (A11)

  • OnePlus: avicii: A12

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

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

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

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

:information_source: All OTA upgrades are for stable or official builds.

Testing
  • OnePlus: avicii: S (A12) → U (A14)
To Be Planned
  • FP5

  • FP3

Definition of OS OTA Upgrade
  • Download the correct OS build from the supported device list.

  • For some devices, download the stock ROM from the vendor site.

  • Back up your data.

  • Install the stock ROM, then the /e/OS ROM.

  • Restore backups if needed.

OTA upgrades simplify this process but require significant development and testing.


Miscellaneous Information

Helpdesk Services (For Paying Murena Customers)

:warning: Old helpdesk email IDs are no longer monitored.

Device and Vendor Announcements
  • Gigaset GS290: Sales stopped as the vendor ceased production. Support continues for existing users.

  • Pre-Flashed Devices: Available in EU, US, Canada, and Australia via the Murena Shop.

/e/OS Website and Social Media Links

Websites

Telegram Channels

Social Media

Newsletters


:warning: Do Not Post Test Build Information on the Forum :warning:

  • Test builds are untested and may cause device issues.

  • Interested testers can join the testing team and share feedback on the dedicated Telegram channel.

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

13 Likes

Builds for the following devices have failed

Vendor Device Name CodeName
Samsung Galaxy S20 /S20 5G x1s
Samsung Galaxy s20+/s20+ 5G y2s
Samsung Galaxy S20 Ultra z3s
Samsung Galaxy S10e beyond0lte
Samsung Galaxy S10 beyond1lte
Samsung Galaxy S10+ beyond2lte
Samsung Galaxy S10 5G beyondx
Samsung Galaxy Note10 d1
Samsung Galaxy Note10 5G d1x
Samsung Galaxy Note10+ d2s
Samsung Galaxy Note10+ 5G d2x
Samsung Galaxy f62 f62
Samsung Galaxy Tab S6 Lite gta4xl
Samsung Galaxy Tab S6 Lite gta4xlwifi

We do not have maintainers for these devices and are dependent on upstream code which we had some issues with while compiling. The team will try to get it to build, if that works we will release, else we have to push these builds to the next release which would be v2.10

1 Like

Ohh, that’s strange! Then why is @ronnz98 listed as a maintainer in the /e/documentation?

I never realized that maintainers are listed sometimes :see_no_evil::sweat_smile:

@mihi, keep your eyes open when reading :laughing:
But @ronnz98 is a very special community member anyway, isn’t he?

Yeah he is :grin::grin:. Ronnz the builder

you need to revert this commit:

3 Likes

Hi @ronnz98 you can pass it to the build team members you interact with. They would be able to revert this commit.

Sure. Did create an issue on /e/ gitlab. I also did some unofficial builds for all who wants an 2.9. Just search in the forum

Hi @ronnz98 pl do not post unofficial build urls in this thread. We keep this thread and the information in it for official builds only.

1 Like

avicii community a14 is missing recovery, could you check that?

avicii build now has a script to complete the installation. The recovery will not be displayed separately but is in the zip as a .img file. The install guide has to be updated to reflect this change.

2 Likes

I will tell that to the user on Telegram

The user was able to adopt it from the Fairphone installation guide, thx for your support even on the weekends :bowing_woman:

1 Like

been linking the “how to enable client synchronisation” screenshot alot and it helps most users. Especially those that do not need anything again from the remote and want to just push.

Is there an argument to not mention this at the end of the outage faq yet? it does have a warning and asks for explicit consent. Or I’m missing something said at other places