Week 44 - 2026, 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.


Release Information

Upcoming

  • v4.4.2 :new_button:
  • Build specifically to handle the issues related to the eMudhra certification issues.
  • Build will be for all supported devices - official and community.
    ETA : Post completion of v4.4.1 release next week.

Current :new_button:

  • v4.4.1

  • Release Notes

  • Feedback and voting

    • ETA : 26 Oct to 2 Nov :new_button:
    • Current Status: Initiated
      As usual it will be a staggered release with only a small subset of devices being released every day. This is done to avoid overwhelming our servers as we support 250+ devices.

Future Release

:bar_chart: Current and Previous Releases and User Feedback


Murena Account - Important information

  • Murena Workspace account’s (e.email or murena.io) should have a recovery email.
  • Accounts without a recovery email will face reduced functionality for 30 days, after which they will be deleted.
  • Check if your Murena account has a recovery email, click an log in here.
  • If your account has been disabled or you are facing password reset issues after setting up Murena Password contact me (@Manoj) on this forum and I can assist with re-enabling it. You would be required to verify account ownership by sharing additional details.

Documentation

:backhand_index_pointing_right: Important guides on the Documentation site

:information_source: Guides marked with (*) are features still in beta phase. Additional development, detailed testing, and improvements are in progress. We look forward to your positive comments and feedback which you can post on the forum.


:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

:house: Self-Hosting

:stop_sign:This project is not maintained any more. What that means is no development is in progress or developer assigned to this project. We may take up development at a later stage details of which will be shared.

Last Version: v26.0.8.23

Resources:

:clipboard: Release Notes

:open_book: Upgrade Guide

🔍 How to Check Nextcloud Version

Method 1: Murena Settings

Method 2: Nextcloud Scan

:information_source: Note: If the Murena Cloud patch number differs from the Nextcloud patch number, the rating may appear as “bad”. This is normal — patches are tested before deployment.


:counterclockwise_arrows_button: OS OTA Information

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

:backhand_index_pointing_right: All official builds are candidates for upgrade to A16 or the next OS version for which a build is possible.

:backhand_index_pointing_right: The absence of a device with an official build from this list does not mean the device has been abandoned. We continue efforts to build for all official devices ever sold on the Murena Store. Release dates for these builds will be shared when available.

📢 Completed
  • :mobile_phone: FP4 – FP4 – A14 → A16
  • :mobile_phone: FP6 – FP6 – A15 → A16
  • :mobile_phone: FP3 – FP3 – A13 → A15
  • :mobile_phone: OnePlus – Nord – avicii – A12 → A16
  • :mobile_phone: Teracube – emerald – A15 → A16
  • :mobile_phone: Teracube – sapphire – A14 → A16
  • :mobile_phone: Teracube – zirconia – A15 → A16
  • :mobile_phone: Teracube – 2e – zirconia – A12 → A15
  • :mobile_phone: FP5 – Fairphone – A13 → A15
  • :mobile_phone: FP5 – Fairphone – A14 → A15
  • :mobile_phone: Galaxy S9* – A12 → A15
  • :mobile_phone: GS290* – A12 → A15
  • :mobile_phone: FP4 – Fairphone – A12 → A13
  • :mobile_phone: S9/9+ – Samsung – A11 → A12
  • :mobile_phone: GS290 – Gigaset – A11 → A12
  • :mobile_phone: GS290 – Gigaset – A10 → A11
  • :mobile_phone: FP3 – Fairphone – A12 → A13
  • :mobile_phone: S7/7+ – Samsung – A11 → A12
  • :mobile_phone: FP4 – Fairphone – A13 → A14
  • :mobile_phone: S8/8+ – Samsung – A11 → A12
🧪 Under Development and Testing
  • :mobile_phone: Fairphone – FP5 – A15 → A16
  • :mobile_phone: Murena One – A12 → A16 after release of A15
  • :mobile_phone: Murena One – A12 → A15 (v4.4.1 :crossed_fingers :crossed_fingers:)
  • :mobile_phone: Murena Two – A12 → A15 (v4.4.1 :crossed_finger :crossed_fingers: )
  • :mobile_phone: Google - Pixel 5 – redfin A13 → A16 (v4.4.1 :crossed_finger :crossed_fingers:)
  • :mobile_phone: Nothing – CMF Phone 1 tetris A14 → A16 (v4.5 :crossed_fingers :crossed_fingers:)
📋 To Be Planned

This is the consolidated list of all devices that have an official build. The plan is to upgrade all of them to the latest possible build. This may not be feasible for every device, as some are too old and have already reached EOL from the vendor and may not work on the latest OS versions. Devices marked “No updates” fall into this category.

Vendor Name CodeName Current OS Upgrade OS
Fairphone FP6 FP6 A16 Already on A16
Fairphone FP4 FP4 A16 Already on A16
Fairphone FP3/3+ FP3/3+ A15 A15 to A16
Fairphone FP5 FP5 A15 A15 to A16
Gigaset GS6/Pro GS6_venus A16 Already on A16
Gigaset GS290 GS290 A15 A15 to A16
Google Pixel 5 redfin A13 A13 to A16 v4.4.1 :crossed_fingers:
Google Pixel 7 panther A15 A15 to A16
Google Pixel 8 shiba A15 A15 to A16 / A17
Google Pixel Tablet tangorpro A14 A14 to A16
Murena One One A12 A15 or A16
Murena Two Two A13 A13 to A16
Nothing CMF Phone 1 tetris A14 A14 to A16 v4.5 :crossed_fingers:
OnePlus Nord avicii A16 A14 to A16 via sideloading possible
Samsung S9 starlte A15 A12 to A16
Samsung S9+ star2lte A15 A12 to A16
Samsung S7 * herolte A12 EOL
Samsung S7+ * hero2lte A12 EOL
Samsung S8 * dreamlte A12 EOL
Samsung S8+ * dream2lte A12 EOL
SHIFT SHIFTPhone 8 otter A14 A14 to A16
Teracube 2e zirconia A16 Already on A16
Teracube 2e emerald A16 Already on A16
Teracube 2e sapphire A16 Already on A16
Volla Volla Tablet mimir A14 A14 to A16

(Devices marked with an * have an issue with FDE encryption that requires a format before the OS can be upgraded. This essentially means data loss. If we are able to build an A15 build for these devices, users will have to install it manually and must first take a full backup of all data.)

:backhand_index_pointing_right: Check the section titled A16 Updates below.

📖 What is an OS OTA Upgrade?

Traditional Process:

:inbox_tray: Download the correct OS build from the supported device list
:inbox_tray: Download the stock ROM from the vendor site (for some devices)
:floppy_disk: Back up your data
:counterclockwise_arrows_button: Install the stock ROM, then the /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


🔊 A17 or A16 Updates 🔊
  • We plan to update all devices currently on A12, A13, A14, and A15 to A16 or A17 once it becomes /e/OS-compatible :speaker_high_volume:

  • If any device is unable to handle A16 or A17 builds, we will share that information.

  • The team expects that A16 will not be buildable or installable on some older-generation devices such as the Samsung S7 or S8. There could be more. While the team will try to OS upgrade these devices, if the attempt fail we will have to drop these devices from the supported list.

  • As you may be aware, A12 no longer receives security patches. This will next affect A13 and subsequent versions. This is standard Google policy for end-of-life (EOL) of older Android versions.

  • All devices we sell in our shop that have official builds are priority candidates for OTA OS upgrades to A16.

    • Official builds receive OTA OS upgrades.
    • Community devices require manual upgrades.

(Ideally, take backups before upgrading the OS on any device.)


:link: Miscellaneous Information

:bar_chart: Real-Time Service Status

:cloud: eCloud Real-Time Status
:mobile_phone: /e/OS Real-Time Status


🎫 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: 2–3 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 addresses 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 the 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

:bank: To send in your donations: Use the email address donation@murena.io


: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 do not 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

12 Likes

Why 4.4.1 or not 4.4??

1 Like

Just installed v4.4.1 official on my FP6. Android System Webview is 153.0.8010.36+e2. Is this what is considered “current”? What is this e2? Does it refer to Elixir? For now I’ll stick to stable google webview 156.0.8078.47

+e2 is a spell check or some other auto correct misunderstood the original text. +e2 probably means to the math exponent 2+.

The development team does not go by the version numbers we publish for all users. To explain this, we would start with a v4.0 once the build is made, new patches may come out, QA might identify some bug, there could be security patch release which needs to be added.
If the addition is important, we increment the build number. The version that the QA finally approves is the one we publish. In this release it was v4.4.1
That does not end the builds for the internal team. The developers at times do make additional build like v4.4.x to test some additional changes for specific devices but these do not get released.
This is normal software development practice. Version numbers are what helps us tracing what goes in each build code. Even in the past we have released v x.x.x builds.

3 Likes

Response from the developer:

Its our revision on top of a particular chromium version. You can follow the tags for browser here.
This was done on request from our internal QA team to distinguish between builds.

3 Likes

Hi @Manoj

Tha /e/OS maps App disappeared after upgrade to 4.4.1 a16. I don’t find any information about maps App deletion from /e/. It’s a bug?

Device : OP8T - kebab. Upgraded from 4.2-a16 into 4.4.1-a16

The maps app has been dropped from community devices which had space constrains.

As you may remember previous couple of builds for kebab failed.

We have a MINIMAL_APPS flag which is executed for such devices with sever internal space constrains and which would remove some apps as mentioned in the link.

4 Likes

This is mainly a problem caused by eOS itself due to the early made decision, to place all the apps it delivers into system space, in violation to the rule to use system space sparingly. While this placement must be done for apps like “microg” and “advanced privacy” it is completely unnecessary for apps like web-browser, mail-client, contacts, calculator … and maybe even an app installer (think of “aurora store” to which eOS users regularly revert, when “app lounge” refuses to work).

The OP8T has an overall storage of at minimum 128G. This should absolutely be sufficient. Have a look at lineage4microg: Concerning “kebab” they are currently at lineageOS V23.2 (A16 second version) without ever having had any trouble of that kind (lineageOS for “kebab” is even at V24.0 (A17))!

It would be nice, to get a comment on this from the development team.

5 Likes

@Manoj What about /e/OS v4.4.2 ? Will this be released for all devices?

We will be coming out with a v4.4.2 specifically to address the emudhra certification issue. The release will address the certification updates across the OS and browser. We will share more details in the days to come. This build will go out for all supported devices.

9 Likes

is there some major block to getting A16 on FP5? It has been under development & testing for a while now

4 Likes

I think several users will be confused by the fact that suddenly some apps are missing (happened to me too: OnePlus 6T (fajita) has got no Maps app on /e/OS 3.7.1) or are not available at all.

My suggestions:

  • It would be nice if the information about MINIMAL_APPS builds is published in the devices list (or in the device description and/or the installation description)

  • Furthermore it should be published in the release notes when it was necessary to apply MINIMALS_APPS to a device

  • If a device uses MINIMAL_APPS then a list of all affected apps should be available with links to download them when needed

3 Likes

Dear @Manoj , what about a comment on this?:

(It´s got 4 Likes meanwhile)

Kind regards

Have passed it to the developers. Will get back if there is a comment.

MINIMAL_APPS and the list of apps it removes is mentioned in the documentation.

Had shared a comment with the build team to mention it in the release notes.

Passing the feedback again along with the other comments in the post.

1 Like

The developer response was that when we made our first release and adopted this approach it was way back in 2019 and we were on A7 or Nougat. The approach did not change over the OS versions. Devices which started on older OS versions will still have system as product partition.

Yes we can change. But we might break devices which don’t have much in product for example mostly older phones before 2020. Newer devices don’t have this issue as they use super partitions and all partitions sit inside it, so there’s no space allocated per partition per se.
As lots of legacy devices were dropped after a15.

3 Likes

Hello @Manoj ,

the OP8T is such a newer (A/B) device, where the system partitions live in logical partitions in a super partition, and it obviously has this problem!!! (while its user partition usually has enough of free space for all the apps which don’t need to live in system space) ???

Hi @RdLr, on a running device and adb shell one can check

df -h /

Typical OK result

Filesystem            Size Used Avail Use% 
/dev/block/mmcblk0p62 2.6G 2.4G  134M  96%

As Android itself and the /e/ ROM gets larger the spare space gets smaller. This is illustrated in ocean /e/OS builds where a15 killed off /e/OS at e-3.2 but a14 runs on with marginal spare space.

I never did check the calculations for super

No need to check anything!

eOS blows up the system partitions in super unnecessarily so that they finally don’t fit together into the fixed size super partition by stuffing them with apps which can as well live in the (huge) user space partition.

Lineage4microg and LineageOS itself don’t have this problem because they don’t do that!

PS

Maybe a build of eOS 4.4.1 A15 for the moto g7 power (ocean) would still succeed if apps like Browser, Mail, Kalendar, Calculator, … were apps to be installed by the user as normal user apps (instead of their delivery as system apps somewhere located in a logical partition of the super partition)?!

1 Like