Week 16, 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 Updates

Upcoming v3.7 :new_button:

Status: Release initiated

ETA: 14 April - 21 April :new_button:

What to look out for in this build:

:rocket: A16 OS Release

Status: Released

  • List of Supported devices that got the A16 community build

  • New devices joining the supported devices list and come with A16 community build.

    • These builds are community builds. Will require a manual download and install. Installation guides have been updated and share instructions on how to do a fresh install of the A16 builds. Take a backup before installation of a higher level OS.
    • Official A16 builds will take some time. Will share information as to when they will be released.
    • There will be further addtions to the list of devices we will release on A16.
    • The plan is to update all devices where possible to the latest OS version.

Upcoming Milestones

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


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

:open_book: We are planning on updating our documentation site. Besides making navigation easier the plan is to make user contribution easier. Currently under planning stage, will share details once there is any progress on it.

:cloud: Migrate your data from google cloud to your Murena account. Follow the instructions in this guide.

:bug: Want to report an issue in /e/OS. Create the bug in Gitlab. If you are facing an issue in creating the ID, create or use your Murena workspace ID. Check this suggestion.


:locked: Security Information

:shield: Security Patch Release Process explained here

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

:bar_chart: Previous Releases & User Feedback

3.6

3.5

3.4

3.3

v3.2


:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

:loudspeaker: Murena Cloud just got an update

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

✅ Completed
Teracube -zirconia -  S(A12) → V(A15) 🆕

Teracube : S(A12) → V(A15) 🆕 

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: OnePlus nord avicii - A12 → A16 - v3.7 :crossed_fingers:

  • :mobile_phone: FP4 - FP4 - A14 → A16

  • :mobile_phone: FP6 - FP6 - A15 → A16

:clipboard: To Be Planned :new_button:

  • :mobile_phone: FP3 - FP3 - A13 → A15
  • :mobile_phone: Google Pixel tablet - tangorpro - A14 → A15
  • :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

: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

12 Likes

We are planning on updating our documentation site. Besides making navigation easier the plan is to make user contribution easier.

great to read - on both accounts - but esp. the backflow of documentation.

2 Likes

Hi @Manoj,

I took a quick look here Milestones · e · GitLab but wasn’t able to understand if the FP4 low call volume issue reported here Issues reported on v3.6 (#9277) · Issues · e / Backlog · GitLab and the FP6 fast vs. slow charging tags issue reported here Issues reported on v3.6 (#9277) · Issues · e / Backlog · GitLab have been addressed in 3.7.

Would it be possible to have details?

Thank you

Nedo

2 Likes

Reg the charging tag on the FP6 it is just a visual issue and has not been addressed in this release. The team clarified that irrespective of the tag the charging will be as per the setting the user has set. That is if the setting was for slow charging it would charge slow. The error in the tag will be addressed in one of the future releases.

Yet to get an update on the FP4 low volume issue

3 Likes

Hi Manoj,
thanks for the update!
Regards

The v3.7 release has been initiated. It will be staggered release as usual and spread over a week.

Please note the following devices will not be receiving the v3.7 build

Vendor Name CodeName OS Version
Lenovo Z6 Pro zippo A16
Xiaomi Redmi Note 10S rosemary A15
Xiaomi Mi MIX 2 chiron A15
Nubia Mini 5G TP1803 A14
Xiaomi Xiaomi Pad 5 nabu A14,A13
  • These device builds failed on these OS versions. We will try to rebuild them if that works it will be released as part of v3.7 else they will be accommodated in v3.8 which should come out by May.
  • These builds failed due to changes coming in from the upstream code base.
3 Likes

Hi.
What’s up with the official OTA update from A15 to A16 for the FP5?
Can’t find any informations on this.
Greetings.

1 Like

Official OS upgrade builds are all WIP. The release going out with v3.7 is for OnePlus nord avicii A12 to A16. All other official builds are still WIP with no ETAs to share.

2 Likes

I see on the ota api that the e-3.7-a15 for shiba is already available (not yet listed on the pages nor on the updater).
https://ota.ecloud.global/api/v1/shiba/stable/
Is there the a16 upgrade available as part of the v3.7 ? so it will have a later e-3.7-a16 build ?
Thanks

e-3.7-a16 is out :

1 Like

Thanks, but I was talking about the official build.
But on the OTA server, I can see both e-3.7-a15 and e-3.7-a16 builds for the community edition, so I suppose that it will be the same for the official one (if there is no issues on the build of course)

As this post explains official builds do not just follow on from community.

2 Likes

What I’m a bit surprised of is that FP4 has been marked eligible for A14→A15 OTA upgrade in early 2026 but there is no update on this milestone while, if I get it right, it seems that FP4 will get directly A16 but without any clear milestone. Matteo

1 Like

Hi Manoj,
as of today 13 FP4 users reported the low call volume issue with 3.6 and also 3.7 (probably also with previous versions).
Any news if this could be addressed at some point?
Do you think there is a need to open a similar “Issues reported on v3.7” gitlab issue or the above “Issues reported on v3.6” one will be enough?
Thx

1 Like

I discussed with development team and the response was that there was an issue with the volume, if set too high it would sound distorted. To resolve this the sound was set low.
The team will be raising it higher in one of the next releases while testing against the distortion.

2 Likes

Thanks for the very useful level of details!
Imho better low than distorted, very good to know that devs will try to test the best threshold (if what we have now is not already that best threshold).

I agree, thanks for the information and feedback! If its any contribution to the issue, I used to run FPOS on my FP4 before and can’the recall having this issue then. I’m so curious as to whether this issue is also present in Lineage?

But it was louder without noticeable distortion in old versions.
So a solution for no problem …?