Week 40, 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

Current

  • v4.3 :new_button:

    • Releases Notes
    • Feedback for v4.3 and voting
    • Security Patches: as of September 1st, 2026
      • ETA: Release dates from 21 Sep to 28 Sep.
        • Staggered release. Every day we would release builds for a few devices. We support over 250+ devices and releasing all builds at the same time would impact server resources.

Future Release

:bar_chart: Current and Previous Releases and User Feedback


Murena Account related issues

  • 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

:magnifying_glass_tilted_right: Always use the search feature first before raising new bugs on or creating new posts. Add details to existing issues. Share as much details about the phone as possible.

:backhand_index_pointing_right: Anyone with a /e/OS GitLab account can now edit the Documentation site. The site now uses Hugo and is being upgraded on a continuous basis. The idea is any user with an /e/OS Gitlab ID should be able to edit the site.

A brief explanation of how users can edit the Documentation site
  • Share your /e/OS GitLab ID with me (@Manoj). I will pass it to the team member who will grant you the necessary access to the documentation project.
  • Once access is granted, your changes will be created as a Merge Request (MR).
  • The MR must then be reviewed.
  • The MR can be rejected or approved. If rejected, reasons will be shared.
  • Once approved, the content is published and appears on the documentation site :bouquet:

: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

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

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: FP5 – FP5 – A15 → A16
  • :mobile_phone: Murena One – A12 → A16
📋 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
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
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 No OS upgrade (to be decided)
Samsung S7+ * hero2lte A12 No OS upgrade (to be decided)
Samsung S8 * dreamlte A12 No OS upgrade (to be decided)
Samsung S8+ * dream2lte A12 No OS upgrade (to be decided)
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

5 Likes

The fix for the voice on FP4 being distorted post release of v4.3, will come along with v4.4 which would be released in mid-October.
Checking with the team if it would be possible to release a fix earlier. Will update team response.

10 Likes

The FP6 official and community v4.3 build has been rolled back.
We have received a random reboot issue reported by one of our testers. Developers have been asked to check the logs and identify the issue. Will update progress.

3 Likes

I just remind the dev-team, that the FP4 and FP6 are official devices. Waiting until mid of october is not an option.

3 Likes

Just be realistic - difficult bugs sometimes happen. Give the Team chance to resolve problems. I also have FP6, updated to 4.3 - and luckily for me no bugs so far.

1 Like

The FP4 v4.3 community and official builds have been rolled back. This is following the complaints of audio distortion in the release. Will update on the developer updates for this issue.

4 Likes

Team is actively looking at rolling out an interim release specific to these devices. Will update on the progress.

9 Likes

https://community.e.foundation/t/week-39-development-and-testing-updates/84902/37

There’s still no A16 upgrade to /e/-4.3 for the Oneplus 8T ( /e/OS community kebab download ) (and for the Oneplus 9R as well ( /e/OS community lemonades download ), while there is one for the Oneplus 7T ( /e/OS community hotdogb download ))???

@Manoj , do you’ve got any new info about this from the team?

Just got an update. The builds for kebab and lemonades both failed.

Will share the complete list of builds that failed. We will try to re run those builds. Will update if any of those builds succeed.

The following builds failed. Some failed due to updates coming in from upstream at the last minute.

Vendor Name Codename OS version
Asus Zenfone 5Z (ZS620KL) Z01R A14
Essential Essential PH-1 mata A14
Google Pixel Fold felix A15
Lenovo Z6 Pro zippo A14
Motorola edge 20 pro pstar A14
Motorola moto g52 rhode A14
Motorola Moto G7 river A15
Motorola Moto Z3 Play beckham A15
OnePlus 11 5G salami A14
OnePlus 8T kebab A16
OnePlus 9R lemonades A16
Razer Phone 2 aura A14
Razer Phone cheryl A14
Samsung Galaxy S10+ beyond2lte A15
Xiaomi Mi MIX 2S polaris A14
Xiaomi Redmi K60 Pro socrates A14
Xiaomi Redmi Note 10 Pro sweet A14
Xiaomi Redmi Note 10S rosemary A15

We will work on restarting these builds.

2 Likes

Hi @Manoj,

I have some feedback for the development updates and overall visibility of the project’s evolution:

I find that copy-pasting the content of last-week’s development update makes it hard to find what informations are actually new this week. Since I read those every week, most of the content inside of it is basically noise to me.

For example, here’s what the a git diff of the content of last week’s update and this week’s update looks like :

I think it would be much more usefull to have concise posts highlighting what has been done since last week, and what is currently happening. The rest of the information would be better served on a dedicated post linked via a URL on each week’s update.

I see that the gitlab issue board has been cleanup up and clarified. That was a major problem I had to keep track of what was happening on the project :slight_smile:

3 Likes

I just noticed v4.3.1 for Sept. 30 in the milestones here Milestones · e · GitLab and it (/e/OS v4.3.1 · e · GitLab) has a FP4 issue: [FP4] No audio at all in cellular calls after OTA update to 4.3 (Android 16) (#9694) · Issues · e / Backlog · GitLab
Thx!

1 Like

Thank Your for trying to release 4.3.1 for FP4 to fix audio.

Would it be possible/realistic to separate security updates (i.e Android SPL, firmware patch, webview updates) from e/OS specific feature updates (e.g. bug fixes in e/OS apps, new e/OS features etc)? Although this would mean providing 2 OTA updates per month instead of one, it could help with getting security patches quicker without holding them back due to bugs in features. This is the model CalyxOS seem to have adopted. Could that make sense for e/OS as well?

1 Like

What about the devices below? The latest status was that a decision still had to be made. Does this mean they’re discontinued for good? Then I’ll know whether I should start looking for a replacement for my Edge 30…"

Issue is still under discussion. Will confirm if the decision to remove them is final.

Vendor Name Code
Motorola moto g200 5G xpeng
Motorola edge 20 berlin
Motorola edge 2021 berlna
Motorola edge 30 dubai

this map tile overlay contribution to microg by a murena developer is notable - feat(maps): implement addTileOverlay via MapLibre raster source by jonathanklee · Pull Request #3685 · microg/GmsCore · GitHub - over the years there were half a dozen of threads on missing custom tile layer support. Looks like to be in v4.4

Hi, news on the FP5 A16 upgrade? @Manoj

Unfortunately, these devices have been failing consistently. Will check with the build team during office hours today and get back. The chances are some of these devices may be dropped.

This is possible and the team is working on sending out all system apps as upgrades from the App Lounge. This is slightly complicated so no ETAs at the moment.

1 Like

Great news, thanks! This would definitely help.