Week 52, 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: Release initiated :new_button:

:tear_off_calendar: ETA: December 15 to 19 Dec, 22 Dec to 24 Dec :new_button:

:stop_sign: Release was stopped over the weekend ( 20 Dec,21 Dec) to check for issues in the build. Issues were reported by Xiaomi and Motorola device users. An issue has been created to track these issues. The team will take a decision to continue with the release based on a go ahead from the QA team.

  • On the issue with the camera and torch not working in Xiaomi devices the team has identified the cause for issue and is working on a plan how to release the fix. Will update if there are any inputs from the team.

: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: Fix for App Lounge not able to show or install common apps


: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

3.3

v3.2

v3.1.4

v3.1.1

v3.0.4

: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 :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


: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

The team is checking as to when the roll out will resume. We had stopped the roll out after inputs from users of Xiaomi and Moto devices of issues in their builds. The development team is evaluation any possible impact on official builds.
Will have more clarity on when the builds will be resumed for community and official later today. Will update.

6 Likes

Hello Manoj,

I don’t find the information. Is the update available for FP6 official. I’m still in 3.2.1. I suppose it will coming in this week.

Have a nice day.

The Update of v3.3 rollout is as under:

  • Xiaomi and Motorola device builds of v3.3 will be on hold and removed if already showing up on the server
  • A fix specific for Xiaomi devices will be rolled out as v3.3.1
  • For the issue on Motorola devices we are still investigating.
  • The release of v3.3 will continue for all other devices - Official and community as we these issues were device specific.
8 Likes

Thanks for keeping us up to date, Manoj! Excited for the update.

Any update on MiA1 (tissot)? Will this device receive the update or is being discontinued?

1 Like

May be discontinued. We are checking on the possibility of getting builds made for the device. Final decision is yet to be made.

1 Like

:studio_microphone::cloud:Users can now migrate their calendar, contacts and files from Google to Murena Workspace https://murena.io/settings/user/migration

There are a few minor bugs related to files migration detected during QA runs that we will resolve in coming months. Calendar/contacts migration is not known to be buggy and works well. We have a guide that explains the basics of what is possible with this feature.

6 Likes

3.3 update for FP6 now availlable, downloading is slow as everybody wants to download right away…:wink:

2 Likes

I just installed the new 3.3V official on my FP6 over the normal update function of /e/ 3.2V which I had already installed. I waited for the update to lock the bootloader again. Now, I have the newest Android Security Patch level installed (the one that comes with 3.3V), and the Phone did not recieve any updates since beginning of November. Now: when I do a “fastboot flashing get_unlock_ability” it returns “0”. It it still save for me to try to relock the bootloader or why do I not get a return of “1”, as some forum post suggest I need to get?

@Helight here is a thread asking, I think, very much the same question as you. Installed 3.0.2 official and tried to lock bootloader.

In brief the command

fastboot flashing get_unlock_ability

does ask about unlock ability. Not lock ability, it does not check or query any SPL dates.

It does however check device state. Install pages tell us to lock directly after install. Now it could be somewhat uncertain what might have changed the device state.

The linked thread poster opted to go back to Fairphone OS, then reinstall /e/OS.

There are a number of similar cases in this :magnifying_glass_tilted_left: forum search.

1 Like

When 3.3 Will be available for FP5?

2 Likes

woah if that is not burying the lede! That is great to see!!

All v3.3 Xiaomi devices builds on A14 have been removed from the image’s server. This is as we detected an issue with the build impacting the camera and torch app. A v3.3.1 specific to Xiaomi on A14 will be released ASAP.

Now available. :grin::grin::grin::grin::grin:

For those having an issue while creating an account on Gitlab, pl follow the instructions given here

1 Like

FP6 Tap to wake up is targeted for v3.5 which would be coming around Feb mid :crossed_fingers:

2 Likes

I see for Android Auto a stub app is installed, do I then only have to install Maps/TTS package and Google so that it runs or are there already stub apps available?

Successfully updated to 3.3 from previous version of official /e/OS on:

  1. “herolte” Galaxy S7, not rooted, official /e/OS
  2. “redfin” Pixel 5, official, still updating after 4 hours “finishing installation” but % are going up.

Hopefully after 10 hours it will finish on Pixel 5. I can only click “hang”, but can wait, because system is usable while “Ending Installing …”.

***Update.

After 15 hours, it finished “Ending Installing…” and allowed me to just click “update”.

Everything went smooth after that, and it installed an update and restarted the phone.

Revolut is working now fine. Before that, it complained, not allowing to login.

2 Likes

Hello @Manoj , do you know whether there will be an /e/OS A15 build of version 3.3 for the OnePlus 6 (enchilada)? The first build for version 3.3 failed so that a new attempt was necessary.

Thank you for keeping us updated!
Happy holidays everyone :slight_smile: