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


Releases

Upcoming Release v4.2 :new_button:

  • Tentative list of fixes coming as [part of v4.2]( Milestones · e · GitLab)
    • This is a tentative list and issue can be added or removed from it based on the QA clearing them
  • ETA : Last week of August :crossed_fingers:

Current Release v4.1.1

Upcoming Milestones

:information_source: Releases planned in the future are marked as milestones in gitlab


Roadmap for 2026

:loudspeaker: Check out Gaël’s article on the roadmap for /e/OS and Murena in 2026


Murena Account Recovery Email

Ensure your Murena Workspace account (e.email or murena.io ) has a recovery email set.

  • New Accounts without a recovery email will face reduced functionality for 30 days and post that will be marked for deletion.
  • The process will be the same for existing accounts without a recovery email

:backhand_index_pointing_right: To check if your Murena account has a recovery email click here

  • Link will require you to log in to your Murena workspace.
  • In case your account is disabled, you can contact me - @Manoj on this forum and I can assist with getting the account re enabled.

Documentation

:magnifying_glass_tilted_right: Tips for using the Gitlab or Forum

  • Use the search feature first before raising fresh bugs or creating new posts. If others have already raised similar issues please add your issue details to it.
  • As a rule, when creating new issues on gitlab or creating new posts on the forum share details of your device like its model , build and any additional details that could help others debug the issue.
  • Never share personal details like your email ID when raising issues or creating posts either on the forum or on non confidential issues in Gitlab.

:backhand_index_pointing_right: Check out the new look Documentation site. :new_button:

:backhand_index_pointing_right: Now anyone with a /e/OS Gitlab account can edit the Documentation site.
The process to be able to edit the /e/OS Documentation site is as under:

  • Share your /e/OS gitlab ID with me @Manoj and I shall pass it to the team member who will get you the necessary access to the documentation project
  • Once access is granted your changes will be created as a Merge Request
  • This MR will now be reviewed
  • The MR can be reject or approved. If rejected reasons will be shared in the MR.
  • If approved it will get published and show up on the documentation site.

:backhand_index_pointing_right: Check out the new features that came along with v4.0 release. Some of the features are

:backhand_index_pointing_right: Please note some of these features are in the beta phase. Additional development, detailed testing and improvement are in progress. We look forward to your comments and feedback on these features.

:bug: Want to report an issue in /e/OS.


:locked: Security Information

:shield: Security Patch Release Process explained here

  • We will be sharing a detailed document about our security policy.

:bar_chart: Curent and Previous Releases and User Feedback


:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 32.0.6.11

Resources:

:clipboard: [Release Notes]( v32.0.6.11 · e / infra / ecloud / nextcloud · GitLab)

: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

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

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

:backhand_index_pointing_right: A device with an official build name if not mentioned in this list does not mean the device has been abandoned. We continue efforts to build for all official devices we ever sold on the Murena Store. Dates of release of these builds will be shared when available.

📢 Completed
  • :mobile_phone: FP3 - FP3 - A13 → A15

  • :mobile_phone: OnePlus - Nord - avicii - A12 → A16

  • :mobile_phone: Teracube -2e - zirconia - A12 → A15

  • :mobile_phone: FP5 - Fairphone: A13 → A15

  • :mobile_phone: FP5 - Fairphone: A14 → 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: FP4 - FP4 - A14 → A16
  • :mobile_phone: FP6 - FP6 - A15 → A16
  • :mobile_phone: FP5 - FP5 - A15 → A16
  • :mobile_phone: OnePlus - nord - avicii - A14 - A16
  • :mobile_phone: Galaxy S9* - A12 → A15 :crossed_finger :crossed_fingers:
  • :mobile_phone: GS290* - A12 → A15 (v4.1.1) :crossed_fingers :crossed_fingers:
  • :mobile_phone: Teracube - emerald - A15 → A16
  • :mobile_phone: Teracube - sapphire - A14 → A16
  • :mobile_phone: Teracube - zirconia - A15 → A16
  • :mobile_phone: Murena One - A12 → A16
📋 To Be Planned

This is the consolidated list of all devices which have an official build. The plan is to upgrade all to the latest build possible. This may not work for all devices as some are too old have already hit EOL from vendor and may not work on latest OS versions. Devices with ‘No Update’ come in this category.

Vendor Name CodeName Current OS Upgrade OS
Fairphone FP6 FP6 A15 A15 to A16
Fairphone FP4 FP4 A14 A14 to 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 A12 A12 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
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 A12 to A16
Samsung S9 starlte A15 A12 to A16
Samsung S9+ star2lte A15 A12 to A16
Samsung S7 * herolte A12 No updates
Samsung S7+ * hero2lte A12 No updates
Samsung S8 * dreamlte A12 No updates
Samsung S8+ * dream2lte A12 No updates
SHIFT SHIFTPhone 8 otter A14 A14 to A16
Teracube 2e zirconia A15 A14 to A16
Teracube 2e emerald A15 A14 to A16
Teracube 2e sapphire A14 A14 to A16
Volla volla tablet mimir A14 A14 to A16

(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 upgrade to A16.

    • Official builds get OTA OS upgrades.
    • Community devices require manual upgrade.

    (Ideally in all cases, take backups while upgrading the OS of your device)


: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

:bank: To send in your Donations : Use the email ID 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 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

8 Likes

Do you mean by any chance version 4.2? Version 4.1.2 seems to be close to release.

3 Likes

:slight_smile: Thanks for catching that. Have corrected the next version number. It will be v4.2

1 Like

Reg the FP6 v4.1.1 A16 release.

We await an EU Energy Label test results in order to proceed with roll-out for FP6 v4.1.1 build.

These reports are available here. It has been made mandatory recently by for the newer devices we sell or sold. And should go out with each release - major or minor.

The team is working on getting the reports ASAP so that the rollout may continue and also working on a mechanism by which it would not get delayed in each release.

We await the full report from the EU Energy label site team. As yet it has not been received. The /e/OS team has requested for an update.

Some of the other devices which get this report …

3 Likes

FP6 v4.1.1 A16 rollout Update:

We just got the full EU Energy lab report. The team is working on updating the links and should rollout the build later today or latest by tomorrow.

Also working on a mechanism by which it would not get delayed in future releases.

Update: FP6 v4.1.1 A16 rollout started.

3 Likes

Will Seedvault be back in 4.2? Thanks :slight_smile:

1 Like

will there no 4.x community updates for xiaomi devices ?

Dear @Manoj

Are there any news for Motorola Edge 30 - dubai.

There was no 4.0 release.

THX for your help

dubai was mentioned here regarding failed 4.0 builds …

… but there’s also no visible 4.1.x release for it.

I had all my hopes set on “Fixed calling over Wi-Fi (VoWiFi) and 5G (VoNR) not working on some Fairphone devices and networks.” but alas, the 4.1.1 Fairphone 6 update changed nothing for me.

I upgraded to 4.1.1 earlier today but VoWiFi is still highly unreliable.

I’ve got it set to use WiFi by default, but it keeps defaulting to mobile networks anyway. WiFi is only being attempted shortly after disabling and reenabling VoWiFi.

there’s a concentration of oauth2 failures with Accountmanager / Mail, linked some threads, couldn’t pinpoint a gitlab issue on it. Are you aware?

Unfortunately, some devices have been failing during attempts to build them. I am working with the build team member to get a consolidated list of such device names. Just a heads up, we may have to eventually drop some of these devices from our supported list. Should be able to share the list later during the day today.

Yes and had mentioned in another thread on this forum that the fix should come in as part of v4.2