Week 53, 2025: Development and Testing Updates

:mobile_phone: /e/OS Weekly Development and Testing Activities

  • Summary of weekly development and testing activities by /e/OS developers and volunteers.

  • Updated content is marked with the :new_button: emoji.



Seasons Greetings and A Happy New Year

  • This would be the last update of 2025. As we welcome another year in the middle of the week, here is wishing all our users a happy, healthy and prosperous 2026. :folded_hands:

:rocket: Release Information

Current Release : v3.3

Status: Released

:airplane_arrival: Released with v3.3

:backhand_index_pointing_right: December Android Security patches

:backhand_index_pointing_right: Android Auto fix for A15 users

:backhand_index_pointing_right: Bluetooth connection issue fix for FP6

:backhand_index_pointing_right: Fix for App Lounge not able to show or install common apps


:backhand_index_pointing_right: Issue on Xiaomi devices

A v3.3.1 release specifically for Xiaomi A14 builds has been made. This is as users have reported bugs with the camera and torch apps on these devices with v3.3. The v3.3 build for these devices has been removed.
Will check with the team on the release notes for this build.


:star: /e/OS - A15 - /e/OS V

Status: :white_check_mark: Released

:clipboard: A15 new additions released with v3.3

:clipboard: A15 builds released with v3.2

:clipboard: A15 builds released with v3.1

:clipboard: Supported devices to get A15 builds

:clipboard: View the complete list of supported devices

Known Issues:

:stop_sign: Some device builds fail during compilation due to last-minute upstream code changes. We either try to rebuild these devices during the same release cycle or accommodate them in the next release cycle.


:locked: Security Information

:shield: Security Patch Release Process explained here


:bar_chart: Previous Releases & User Feedback

:memo: Feedback Threads

3.3

v3.2

v3.1.4

v3.1.1

v3.0.4


:stop_sign: Support Dropped

These devices will no longer get /e/OS builds. We are dropping them from our release system. We tried to build v3.3 for them but the builds failed. Efforts to build with the Minimal Apps configuration did not succeed.

Vendor Device Name CodeName
Google Pixel XL 2 taimen
Google Pixel 2 walleye
Motorola Moto G7 Power ocean
Motorola Moto G6 Plus evert

:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 31.0.10.11

Resources:

:clipboard: Release Notes

:house: Self-Hosting

Current Version: v26.0.8.23

Resources:

:clipboard: Release Notes

:open_book: Upgrade Guide

Status:

:memo: Self-hosting guide update pending

🔍 How to Check NextCloud Version

Method 1: Murena Settings

Go to Murena Settings

Look for “NextCloud xx user documentation”

Method 2: NextCloud Scan

Visit NextCloud scan link

Input https://murena.io

:information_source: Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad. This is normal - patches are tested before deployment.


:mobile_phone: GSI (Generic System Image)

Current Version: /e/OS A10 v1.17

Resources:

:inbox_tray: Download

:open_file_folder: Sources

Next Version: /e/OS T (A13) - skipping A11 and A12

:date: Release dates to be announced


:counterclockwise_arrows_button: OS OTA Information

✅ Completed
FP5 -  Fairphone: S (A13) →  V (A15)  

FP5 - Fairphone: U (A14) → V(A15)

FP4 - Fairphone : S (A12) → T (A13)

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

GS290 - Gigaset : R (A11) → S (A12)

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

avicii - OnePlus : A12

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

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

FP4 - Fairphone : T (A13) → U (A14)

S8/8+ - Samsung : R (A11) → S (A12)

:information_source: Note: OTA upgrades are for official or stable builds only

:test_tube: Under Development and Testing

  • :mobile_phone: zirconia - Teracube : S(A12) → V(A15) :new_button: (v3.4)

  • :mobile_phone: emerald - Teracube : S(A12) → V(A15) :new_button: (v3.4)

  • :mobile_phone: avicii - OnePlus : S (A12) → U (A14)

  • :mobile_phone: FP4 - Early 2026

:clipboard: To Be Planned :new_button:

  • :mobile_phone: FP3
  • :mobile_phone: tangorpro - Google Pixel tablet 7
  • :mobile_phone: Murena One - A12 - A15
  • :mobile_phone: GS290* - A12 - A15
  • :mobile_phone: Galaxy S9* - A12 - A15
  • :mobile_phone: Galaxy S8* - A12 - A15
  • :mobile_phone: Galaxy S7* - A12 - A15

(Devices marked with an ‘*’ have an issue with FDE encryption which requires format before the OS can be upgraded. This essential means there would be data loss. If we are able to build a A15 build for these devices, the user will have to manual install it and that would require first taking a backup of all data.)

:backhand_index_pointing_right: Check the section titled A16 Updates below

📖 What is OS OTA Upgrade?

Traditional Process:

:inbox_tray: Download correct OS build from supported device list

:inbox_tray: Download stock ROM from vendor site (for some devices)

:floppy_disk: Back up your data

:counterclockwise_arrows_button: Install stock ROM, then /e/OS ROM

:counterclockwise_arrows_button: Restore backups if needed

OTA Benefits:

:white_check_mark: Simplifies the entire process

:warning: Requires significant development and testing


:speaker_high_volume: A16 Updates :speaker_high_volume: :new_button:

  • We plan to update all devices currently on A12, A13, A14 and A15 to A16 :speaker_high_volume:
  • In case any device is not able of handling the A16 builds we will share that information.
  • The team expects that A16 would not be buildable or installable on some of the older gen devices like the Samsung S7 or S8. There could be more.
    • For such devices we we will work on getting them to the highest OS version possible.
  • As you may be aware A12 does not receive security patches anymore. This will next impact A13 and so on. This is a standard Google policy to end of life (EOL) older Android versions.
  • All devices we sell in our shop, with official builds are priority candidates for OTA OS upgrades. The difference is the official builds get OTA OS upgrades. Community devices will require manual upgrade.
  • Will share dates and ETA once I get them from the team.

:link: Miscellaneous Information

:bar_chart: Real-Time Service Status

:cloud: eCloud Real-Time Status

:mobile_phone: /e/OS Real-Time Status

New Gitlab account creation

  • If you are trying to create a new /e/OS Gitlab ID and facing issues with the email ID, you can try and create a Murena Workspace ID and use it to log into Gitlab. Check the updated documentation here

🎫 Helpdesk Services

:white_check_mark: For Paying Murena Customers

:mobile_phone: Murena device purchasers

:cloud: Paid Murena cloud account holders

:heart_with_ribbon: Active donors from the past year

:alarm_clock: Response Time

:hourglass_not_done: 5-10 day response wait period due to high volume of requests.

:telephone_receiver: Contact

:ticket: Murena Helpdesk Contact Form

:free_button: For Free Users

:speech_balloon: Forum

:bug: GitLab Issues

:mobile_phone: Telegram Channels

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

📱 Device and Vendor Announcements

:mobile_phone: Gigaset GS290

:stop_sign: Sales stopped (vendor ceased production)

:white_check_mark: Support continues for existing users

:mobile_phone: Murena One

:stop_sign: Sales stopped

:white_check_mark: Support continues for existing users

:mobile_phone: Murena Two

:stop_sign: Sales stopped

:white_check_mark: Support continues for existing users

:shopping_cart: Pre-Flashed Devices

:globe_showing_europe_africa: Available in EU, US, Canada, and Australia. Check the complete list on the Murena shop

:shopping_cart: Purchase via Murena Shop

🌐 /e/OS Website and Social Media Links

:globe_with_meridians: Official Websites

:house: Murena

:mobile_phone: /e/OS Website

:books: Documentation

:bug: Report Bugs

:open_book: How to Report Bugs

:mobile_phone: Telegram Channels

:speech_balloon: Available Channels

:mobile_phone: Social Media

:mobile_phone: XDA

:bird: X

:elephant: Mastodon

:briefcase: LinkedIn

:memo: Medium

:e_mail: Newsletters

:newspaper: eFoundation News

:tada: Murena Promotions


:warning: Important Notice

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

Why this is important:

:warning: Test builds are untested and may cause device issues

:fire: These builds can potentially soft brick user devices

:thinking: Such information can confuse other users who don’t see these builds in the updater

:busts_in_silhouette: Not all forum users are experts in custom ROM installation

For Interested Testers:

:test_tube: If you understand custom ROMs and can perform basic testing

:busts_in_silhouette: Join the testing team

:speech_balloon: Share feedback on the dedicated Telegram channel

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

20 Likes

Just to confirm is MiA1 (Tissot) still in supported device list?

Checking. Will update

Hello Manoj,

first of all, thank you very much for your great work and that of your team.
Now to my question: I bought a Samsung S9+ in the Murena shop and am not sure how to interpret your information in “To Be Planned”: Will the smartphone receive an OTA update to a higher version? At least version 13 would be great, so that Seedvault backups are possible. Thanks for the info and best wishes for the new year!

bruni

When did you buy the phone from the shop? The team is working on upgrading all devices where possible. Some of the older models may no longer support the newer OS versions. While the devices we sell are on the first list of devices to be upgraded it will also mean that the device should support an upgrade. The upgrade is planned for version A16 where possible if not then the highest OS level which it supports.

Hallo Manoj,

I bought

the phone

in Oktober 2019. It is a Samsung S9+ (SM-G965F, star2lte).

Thanks
Bruni

S9/S9+ upgrades to A15 are planned. Will share ETA when available.

1 Like

Thank you very much!
I wish you all the best for the new year.

2 Likes

Hi,

Still no sign of 3.3.1 release note?

Checking if a release note will be published for v3.3.1

Hi,

My FP6 allows me to download and install /e/OS 3.4-beta.2 via the testing channel.

Where can I see the release note or what will change with 3.3 ?

Releases · e / os / 🚀 Releases · GitLab

what could change from 3.3 with 3.4 ?

Milestones · e · GitLab

Hey @Manoj

…so sorry to be ‘that guy’…but figured I’d ask…to my knowledge, aside from one forum post of yours a few weeks ago indicating that self-hosted /e/Cloud is still intended to be supported…I haven’t seen any updates on anything about it - progress, intended feature sets, intended Nextcloud target.

Figured I’d ask if there was any good news that could be shared before the end of the year =)

Thanks!!

2 Likes

The last update I had from the team member was that self-hosting is still supported. We do have plans to publish the next release of it. The dates or when it would be available are still not available. Let me check again today during EU office hours and get back.

Update: To be planned. No dates available as yet. Will share once I have an ETA.

2 Likes

Wishing all users a happy, safe and prosperous 2026 on behalf of the team’s behind /e/OS and Murena.

Looking forward to another year of improvement and optimization of the OS and associated services.

Keep sharing your positive comments and feedback. :folded_hands:

28 Likes

thanks Manoj for looking after the forum the 7th to 8th year

12 Likes

Adding to my question about UP-implementation in last weeks thread it would be very nice being able to read about UP-implementation somewhere within the reach of https://doc.e.foundation/ also simply because users might want to use UP with all sorts of other apps if working fully functional and some bugfixing might always be necessary thus better understanding what happens in the background will definitely be helpful.

And maybe it’s a good idea to deliver the status of the service in https://status.murena.io/ as well?

I would have appreciated that, because I had to temporarily move away from the integrated UP and extra install ntfy in order to receive needed notifications. Which made me end up with two instances of ntfy, one hardcoded + dysfunctional that I could not switch off anymore thus running in the background and one functional but eating extra battery…
(Note: built-in UP is up and running again in the meantime, least for me on pixel4a sunfish 3.3 A15)

5 Likes

Have requested the team to share an updated document about UP implementation as part of the documentation site. Will notify when it is released.

3 Likes