Week 50, 2025: 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.

:rocket: Release Information

Next Release : v3.3 :new_button:

Status: QA in progress

:tear_off_calendar: ETA: December 2nd week :crossed_fingers:

:airplane_arrival: Coming with v3.3

:clipboard: Tentative list of issues and optimization coming with v3.3

:backhand_index_pointing_right: December Android Security patches

:backhand_index_pointing_right: Android Auto fix for A15 users

:backhand_index_pointing_right: Bluetooth connection issue fix for FP6

:backhand_index_pointing_right: Location broken on FP3 fix

:backhand_index_pointing_right: Fix for App Lounge not able to show or install common apps

:backhand_index_pointing_right: Builds that failed in v3.2 release

  • A15 build for Xiaomi Redmi 12C earth

:star: /e/OS - A15 - /e/OS V

Status: :white_check_mark: Released

:clipboard: Supported devices to get A15 builds

:clipboard: A15 builds released with v3.1

:clipboard: A15 builds released with v3.2

:clipboard: View the complete list of supported devices

Known Issues:

:stop_sign: Some device builds fail during compilation due to last-minute upstream code changes. We either try to rebuild these devices during the same release cycle or accommodate them in the next release cycle.


:locked: Security Information

:shield: Security Patch Release Process explained here


:bar_chart: Previous Releases & User Feedback

:memo: Feedback Threads

v3.2

v3.1.4

v3.1.1

v3.0.4

v3.0 / 3.0.1 / 3.0.2

:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 31.0.10.11

Resources:

:clipboard: Release Notes

: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
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: zirconia - Teracube : S(A12) → V(A15) :new_button: (v3.4)

  • :mobile_phone: emerald - Teracube : S(A12) → V(A15) :new_button: (v3.4)

  • :mobile_phone: avicii - OnePlus : S (A12) → U (A14)

  • :mobile_phone: FP4 - Early 2026

:clipboard: To Be Planned :new_button:

  • :mobile_phone: FP3
  • :mobile_phone: tangorpro - Google Pixel tablet 7
  • :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.
  • In case any device is not capable 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 S7 or S8.
    • 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.
  • 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


: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

17 Likes

We might push the v3.3 release to early next week as we are getting too close to the weekend. Usually, we do not release a build during the weekend. We will start the builds today. That takes about 2-3 days to complete. After that a sanity test happens and then, after the QA green lights it, we publish the release. So most probably early next week.

15 Likes

Thanks for letting us know. This will make a nice xmas présent :christmas_tree::snowflake::wrapped_gift:

Good job - as always quality over quantity. BTW there are a lot of impatient guys here - so practical tip: always add two weeks to first announced release date - you will get rid of many complaints :wink:

3 Likes

Or learn to be patient and ignore the ETA…

8 Likes

Amen. Being in the custom rom space for over a decade the golden rule is “never ask ETA”.

5 Likes

I understand that its important to test these kind of things and its plausibel that a release before a weekend is not really clever.
But I would set the ETA’s around 2-3 weeks later than the original, since many people will ask, why it doesnt come out at the mentioned time stated by the ETA. For me, its not really relevant, but I have seen people asking here alot. Or dont release an ETA at all.
And for the argument, that it is an ESTIMATED time frame, then, in my opinion, it should be around 50% of the time BE the time frame, and not only 10%, since there are builds that WILL fail, depending on the devices.

Sorry for my rant, the team is doing a really good point, just thought I could let out some critism here, since its my opinion.

i first understood the tip as Intended to users, not to Manoj or to the team !

now i read it differently, but it is too late, i cannot remove the :heart: i gave to you.
ah ah…

It’s ok - we can have different opinions. But you are right: it was tip for Manoj and /e/OS team. I am patiently waiting for 3.3 whenever it will came out.

P.S. - I am terribly sorry for stealing your heart :wink:

Personally I would not like it to be delayed but I understand the situation. Two weeks ago my bank app has blocked access on my phone due to issues introduced with 3.2 (if I understand correctly because of an issue with App Lounge). So I personally would love to see the update sooner than later as I’m not able to pay with my phone, confirm online payments that require approval through app or do wire transfers. I can work around this with cash money and a card reader but not for everything or everywhere. But with the end of year festivities and need to pay for stuff in new locations, this is even more challenging.

On the other hand, I finally updated from a way older update to 3.2 as this seemed (!) to finally be an update that didn’t introduce more issues for my phone model than it tried to fix. I desire 3.3 to be “critical bug free” but at this point seeing the more complex issues only becoming known much later and a fix often also taking a long time, I’m not holding my breath it’ll happen even with 2 weeks of extra testing.

I have a question.

I have installed /e/ OS 3.2 on my Fairphone 6. It had the security patch from the 5th of October prior to installing /e/ OS. Therefore, i have not relocked my phone yet, as I don’t want to brick it due to rollback protection.

Now my question is: Can I just install /e/ OS 3.3 with December security updates via the phone ui and then relock my phone? Or do I need to flash my phone with /e/ OS 3.3 from scratch and then relock my phone?

Thank you in advance,

Mikk

1 Like

Hello @Mikk, Welcome to the /e/ users forum.

You can apply OTA updates through the → settings → updater
And then reboot to bootloader mode to relock_ critical and finaly relock

Thank you very much. That makes it very clear.

Ok, I’m in the same place, waiting for the v3.3 after which I can proceed and lock the bootloader on my FP6. However, even though the upgrade itself may be possible without flashing and wiping data, I’m afraid we can´t really escape from wiping the data, since that is what happens when locking the bootloader, as described in https://doc.e.foundation/devices/FP6/install:

Locking the Bootloader

After you have completed the installation and verified it starts up successfully, you can lock the bootloader on your FP6.
Warning: Running the below commands will factory reset your device and wipe all data.

Or am I overseeing some possibility to escape wiping?

2 Likes

Or instead of announcing a date, leave it as “date to be announced” and then give the exact date two or three weeks later.

I don’t mind if the date is pushed back once, or even twice, but it happens every time. It’s not about being impatient, it’s just about announcing things properly.

Just because the project is wonderful and, thankfully, exists, doesn’t mean we have to say amen to everything.

3 Likes