Week 39. Development and Testing Updates

[Manoj]

/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 emoji.

---

Release Information

Upcoming

• v4.3

  • Releases Notes
  • [Feedback and voting]( Feedback for v4.3 - /e/OS Smartphone Operating System / Build Feedback - /e/OS community)
  • ETA : Initiated
    • Release will be staggered across a week. From 21 Sep to 29 Sep. Every day we release a few devices. We support over 250+ devices and releasing all builds at the same time would impact server resources.

Previous

• v4.2
  • Releases Notes
  • Feedback and voting

Future Release

• Future Releases with approximate dates

Current and Previous Releases and User Feedback

• 4.2
• 4.1.1
• Older Releases

---

Murena Account related issues

• Ensure your Murena Workspace account (e.email or murena.io) has 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

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.

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

Important guides on the Documentation site

• Security Updates Tracking
• Bootloader relocking
• Murena Passwords *
• Murena Sign *
  • Currently compliant with SES only. We are working on AES support.
• Murena Meet *
• Murena Vault *
• Backup *
• Google data migration
• Report issues in /e/OS.
  • If you encounter an issue creating an ID, create or use your Murena Workspace ID as suggested here.

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.

---

Murena Cloud and Self-Hosting

Murena Cloud

• Current Version: 33.0.8.3

• [Release Noted]( v33.0.8.3 · e / infra / ecloud / nextcloud · GitLab)

Self-Hosting

Current Version: v26.0.8.23

Resources:

Release Notes

Upgrade Guide

Status:

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 the Nextcloud scan link
• Enter https://murena.io

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.

---

OS OTA Information

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

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

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

• FP6 – FP6 – A15 → A16
• FP3 – FP3 – A13 → A15
• OnePlus – Nord – avicii – A12 → A16
• Teracube – emerald – A15 → A16
• Teracube – sapphire – A14 → A16
• Teracube – zirconia – A15 → A16
• Teracube – 2e – zirconia – A12 → A15
• FP5 – Fairphone – A13 → A15
• FP5 – Fairphone – A14 → A15
• Galaxy S9* – A12 → A15
• GS290* – A12 → A15
• FP4 – Fairphone – A12 → A13
• S9/9+ – Samsung – A11 → A12
• GS290 – Gigaset – A11 → A12
• GS290 – Gigaset – A10 → A11
• FP3 – Fairphone – A12 → A13
• S7/7+ – Samsung – A11 → A12
• FP4 – Fairphone – A13 → A14
• S8/8+ – Samsung – A11 → A12

🧪 Under Development and Testing

• FP4 – FP4 – A14 → A16 ETA v4.3
• FP5 – FP5 – A15 → A16
• 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	A14	A14 to A16 - v4.3
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.)

Check the section titled A16 Updates below.

📖 What is an OS OTA Upgrade?

Traditional Process:

Download the correct OS build from the supported device list
Download the stock ROM from the vendor site (for some devices)
Back up your data
Install the stock ROM, then the /e/OS ROM
Restore backups if needed

OTA Benefits:

Simplifies the entire process
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

• 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.)

---

Miscellaneous Information

Real-Time Service Status

eCloud Real-Time Status
/e/OS Real-Time Status

---

🎫 Helpdesk Services

For Paying Murena Customers

• Murena device purchasers
• Paid Murena Cloud account holders
• Active donors from the past year

Response Time
2–3 day response wait period due to high volume of requests.

Contact
Murena Helpdesk Contact Form

For Free Users

Forum
GitLab Issues
Telegram Channels

Warning: Old helpdesk email addresses are no longer monitored.

📱 Device and Vendor Announcements

Gigaset GS290
Sales stopped (vendor ceased production)
Support continues for existing users

Murena One
Sales stopped
Support continues for existing users

Murena Two
Sales stopped
Support continues for existing users

Pre-Flashed Devices
Available in the EU, US, Canada, and Australia. Check the complete list on the Murena shop.
Purchase via Murena Shop

🌐 /e/OS Website and Social Media Links

Official Websites

Murena
/e/OS Website
Documentation
Report Bugs
How to Report Bugs

Telegram Channels
Available Channels

Social Media
XDA
X
Mastodon
LinkedIn
Medium

Newsletters
eFoundation News
Murena Promotions

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

---

Important Notice

Do Not Post Test Build Information on the Forum

Why this is important:

Test builds are untested and may cause device issues
These builds can potentially soft-brick user devices
Such information can confuse other users who do not see these builds in the updater
Not all forum users are experts in custom ROM installation

For Interested Testers:

If you understand custom ROMs and can perform basic testing
Join the testing team
Share feedback on the dedicated Telegram channel

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[GabrielT]

Hello,

Thanks for the clear information on latest developments.

In the /e/OS gitlab, I get the error “429 too many requests” whenever I want to access to a commit content, even if I try only once in a week.

I guess this gitlab instance is configured to block such access depending on the account level (I am not tagged as a developer) . Is there a way to change this or is it simply not allowed by policy and I should simply clone the repository locally to get all the information (commits, code etc) ?

Thanks

[Manoj]

At present access is restricted to anyone except admins. We are monitoring spammers and unauthorized attempts to access the systems. Normal access would be restored at a later time.

[levin]

I’m a little confused regarding Seedvault. I was under the impression that being able to make local backups’ supposed to be coming back with v4.3. However, in the backup documentation it states that backups are impossible w/o Murena login and in the release notes it says that “If you were already using Seedvault, you can choose to keep using it instead of moving to /e/OS Backup”.
I wanted to start using Seedvault with 4.2, which was impossible. Does that mean I’m now stuck and forced to use Murena Workspace if I want to make a backup?

[zoidberg]

I was awaiting this release to install e/os on my new phone but I am still getting a security patch error when trying to use the e/os web installer. Followed all the guides instructions so not sure what to do now.

[urs_lesse]

Welcome to the Community. – The rollout of 4.3 only started today, so depending on your device, it might not be available yet and/or not have made it yet into the installer.

[zoidberg]

Gotcha, yeah I think it just hasn’t been added to the installer yet because it seemingly should be supported (it’s the Fairphone 6+). Thanks, happy to finally be here!

[urs_lesse]

Yes, I actually just checked for the FP6 as well, and the official version (that comes with the Installer) is still on the previous 4.2 level: https://ota.ecloud.global/api/v1/FP6/official/

[zoidberg]

What’s the best way for me to monitor when it does become available?

[urs_lesse]

For my part, I just check the link up there from time to time. The 4.3 community version for the FP6 is already available, and typically official comes 2-3 days later (Murena usually only releases new versions between monday and friday).

You can also have an eye on Feedback for v4.3

[naillig59]

@Manoj Manoj

A private DM please

[Manoj]

Hi @naillig59 you can send a DM by clicking on the profile image and then on the message button that comes up for that person.

[levin]

@Manoj would you mind clarifying if I’ll be able to make local backups with Seedvault after updating to 4.3, please?

[Manoj]

@levin

to make local backups with Seedvault

Yes, seedvault should work as expected. Just check you have space in your storage to keep all these backups.

[ieder1]

Google Pixel 5 ‘redfin’ and Murena One + Two are the last Official supported devices which are still on Android 12/13. When will they move up to the stage of developing an OTA update to A16?

[obacht]

Nope, add at least Samsung S7(+) and S8(+)

[hakunamatata]

The upgrade for Pixel 5 redfin is planned for v4.4 in October.

[ieder1]

Thanks! Could I have looked this up myself somewhere, or is this inside information?

[ieder1]

Well, at least there was communication about these devices that they were building an update but that these builds failed.

[hakunamatata]

You can always use the search function and search for “redfin” or “Pixel 5”, that way you can for example check how the latest update worked on this phone. The info about the upgrade coming with v4.4 can be found and the end of this thread: Week 37, Development and Testing Updates - #4 by Manoj