Week 51, 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.

:rocket: Release Information

Next Release : v3.3 :new_button:

Status: Release initiated :new_button:

( we do not release builds over the weekend, which is why the release was pushed to this week.)

:tear_off_calendar: ETA: December 15 to 22 :new_button:

:airplane_arrival: Coming with v3.3

:clipboard: Tentative list of issues and optimization coming 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: Builds that failed in v3.2 release

  • A15 build for Xiaomi Redmi 12C earth

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

Status: :white_check_mark: Released

:clipboard: Supported devices to get A15 builds

:clipboard: A15 builds released with v3.1

:clipboard: A15 builds released with v3.2

: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

v3.2

v3.1.4

v3.1.1

v3.0.4

v3.0 / 3.0.1 / 3.0.2

: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

22 Likes

Thanks for 3.3 release.

May we please access the release note?

1 Like

Will ask the team members to make it public. It should have happened in sync with the release. Apparently, we missed that. My apologies. Should be made public during the EU working hours today.

4 Likes

The v3.3 Release notes should be visible now. Apologies for not syncing the publish along with the builds.

7 Likes

is this the Community or Offizial 3.3v?

Releases combined both community and official builds. This release, v3.3, like all our releases will be staggered over a week. The release started on 15th Dec and will go up to 22 Dec. Every day we will release a few devices. We stagger releases to avoid stressing out the build servers. Usually, official builds will go out a couple of days after the community build goes out.

4 Likes

Hopefully distrowatch will pick it and write about it on their website. Murena went out of their TOP100 last week so it would need this announcements to get back on their list and have better visibility to possible new users.

1 Like

Will the v3.3 also be released for the FP6 till December 22?

Yes. By 22 Dec all devices builds, community and official will be released.

2 Likes

The following device builds failed during compilation for v3.3. Some failed due to lack of space on their partitions to load the /e/OS build.

Vendor Device Name CodeName OS version
Asus Zenfone 5Z Z01R A15
F(x)tec Pro¹ X pro1x A14
Google Pixel XL 2 taimen A14
Google Pixel 2 walleye A14
Motorola Moto G7 Power ocean A15
Motorola Moto G6 Plus evert A15
Motorola Moto G7 river A14
Motorola Moto G7 Plus lake A14
Motorola Moto G7 Power ocean A15,A14
Nubia Mini 5G TP1803 A14
OnePlus 6 enchilada A15
Xiaomi Redmi Note 10S Rosemary A15
Xiaomi Redmi Note 10 Pro sweet A14
Xiaomi Redmi K20 / Mi 9T davinci A14
Xiaomi Mi A1 tissot A13

We will try to make the builds again. One option is to try with a minimal set of applications. If even that fails, we may have to drop support for these devices from the /e/OS supported list.

5 Likes

What can I do to help with testing those Motorola G7 phones. If I buy them and test, and enable telemetry, would it help?

Hi!

I’m not sure, if this is the correct topic but I think there was a mistake linking the new 3.3 Build for the Fairphone 4. Install /e/OS on a Fairphone FP4 - “FP4” lists A14 official (Security patch: 2025-12-01), but there is no zip file available with this security patch date. Thanks!

Sorry for beeing totally off topic, but this :

Firefox_Screenshot_2025-12-16T16-58-51.710Z

was way too priceless not to mention !

6 Likes

Like written here, official comes bit later. Unfortunately on the installation page it is already changed…

Hi @Manoj,

Thanks for the passed year and you’re amazing daily work within Murena :hugs: .

According to the release note v3.3-t, the issue for the GPS problem on FP3 seems not to have been resolved. Can you clarify for me this with your dev team ?

Thanks a lot

3 Likes

I had this problem on FP3 v3.0 to v3.2-a15 . With v3.3-a15, it seems to work very well now. It seems that the issue has been addressed.

1 Like

question …..can i flash my FP6 with IMG-e-3.2-a15-20251022539003-official-FP6 to

IMG-e-3.3-a15-20251213556761-community-FP6 …..via recovery (sideload)?

No you can’t. Changing build types is a new install

1 Like

Yes, you can update from “e-3.2-a15-official” to “e-3.3-a15-community” via recovery and adb sideload under certain conditions :

ONLY, if the bootloader is unlocked and you will have to confirm :
→ “install anyway despite signature mismatch”.

ALSO, you will need to use the OTA file, not the IMG one
https://ota.ecloud.global/community/FP6/e-3.3-a15-20251213556761-community-FP6.zip
.

1 Like

You cannot sideload any ROM with leading IMG-; these are install only ROMs and include format data when used for an install.

1 Like