Week 34, 2025: Development and Testing Updates

/e/OS Smartphone Operating System Development Updates
1

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

:rocket: Release Information

:crystal_ball: Upcoming Release: v3.1.x :crossed_fingers:

Expected Release Date: To be shared

:information_source: Testing detected some issues in the code which required more time to debug and resolve. The code release will be published if the issues are resolved this week. Will update on the progress. Accordingly the build number may also increment.

Key Features:

  • :white_check_mark: Revolut fix (for devices with locked bootloader only)

  • :white_check_mark: Second batch of devices on A15 to be released

    • The final list would only be available once we complete the builds as the builds fail on some devices for various reasons. While we would attempt to recover and retry the process, if the A15 is not possible on a particular device, we will share the device details here.

  • :white_check_mark: Various issues and fixes

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

Status: :white_check_mark: Released - First batch of device builds available

Highlights:

Known Issues:

  • :warning: Some device builds failed during compilation due to last-minute upstream code updates

  • :arrows_counterclockwise: These builds will be incorporated with upstream changes and released in v3.1.x

:warning: Important Announcements

:iphone: A12 - /e/OS S - Support Ending

Effective Immediately:

  • :no_entry_sign: Support for A12 (/e/OS S) discontinued

  • :arrows_counterclockwise: Official A12 builds are an exception. They will continue getting A12 builds until we are ready to migrated to A13 or higher

  • :clipboard: This aligns with our policy of supporting three OS versions simultaneously

  • :arrow_up: All supported devices will be pushed to higher OS versions where possible

Recommendation for Users:

  • :arrows_counterclockwise: We recommend users on A12 community builds should migrate to the A12 official build
  • :floppy_disk: Take a backup before proceeding

:wrench: Server Outage Status

:white_check_mark: Current Status: RESOLVED

:globe_with_meridians: Murena Cloud Services and File Drive Access

  • :white_check_mark: Access restored for all users

  • :white_check_mark: Apps enabled on the Murena Cloud Dashboard

  • :warning: Sync for some apps may not work - see details here

  • :white_check_mark: NextCloud Desktop client works with client synchronization enabled

:file_folder: MurenaRecovery Folder

  • :arrows_counterclockwise: Being enabled and made visible for all users

  • :crown: Started with premium users, expanded to all impacted users

  • :alarm_clock: The folder Will be visible for several months (end date TBD)

Important Actions for Users:

:memo: Notes Sync

  • :white_check_mark: Cloud sync possible post v2.9 release

  • :warning: If not syncing after v2.9 upgrade,read the next section. Backup local notes before proceeding

:wrench: Client Synchronization Setup

To enable data sync between device and cloud:

  1. Log into your Murena account

  2. Go to Dashboard → Your Profile (top right)

  3. Navigate to Settings → Client Synchronization (left sidebar)

  4. :white_check_mark: Enable the checkbox

Note: Only enable if you want device and cloud data to be in sync. Keep unchecked if you prefer separate data storage.

:books: Documentation Updates

:new: New Documentation Released

:clipboard: Version Naming Convention Update

New Standard: Using OS version numbers instead of letters

  • /e/OS V → A15

  • /e/OS U → A14

  • /e/OS T → A13

  • /e/OS S → A12

  • /e/OS R → A11

  • /e/OS Q → A10

  • /e/OS P → A9

  • /e/OS O → A8

  • /e/OS N → A7

This change eliminates confusion in version tracking.

:lock: Security Information

:shield: Security Patch Release Process

:open_book: Complete explanation available here

:date: Upcoming Releases

:new: A15 Device Lists (Draft)

Existing Devices:

New Devices:

:warning: Note: These are initial lists. Some devices may not support A15. Lists will be updated based on user and build team feedback.

:date: Release Schedule

:arrows_counterclockwise: Ongoing Development

🛠️ Active Development Tasks

:iphone: /e/OS GSI on T (A13)

  • :mag: Team exploring OTA availability

  • :iphone: App development for compatibility detection

  • :alarm_clock: ETA to be shared

:bar_chart: Previous Releases & User Feedback

:memo: Feedback Threads

:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 29.0.16.4

Resources:

:warning: Note: Some users may see “server software is end of life” messages. This is NextCloud’s upgrade reminder. We’re working on the upgrade - release date to be announced.

:house: Self-Hosting

Current Version: v26.0.8.23

Resources:

Status:

  • :arrows_counterclockwise: Next release planning in progress

  • :memo: Self-hosting guide update pending

🔍 How to Check NextCloud Version

Method 1: Murena Settings

Method 2: NextCloud Scan

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

:iphone: GSI (Generic System Image)

Current Version: /e/OS A10 v1.17

Resources:

Next Version: /e/OS T (A13) - skipping A11 and A12

  • :date: Release dates to be announced

:arrows_counterclockwise: OS OTA Information

✅ Completed Upgrades

  • FP4 - Fairphone : S (A12) → T (A13)

  • S9/9+ - Samsung : 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: All OTA upgrades are for stable or official builds.

🧪 Testing Phase
  • avicii - OnePlus : S (A12) → U (A14)
📋 To Be Planned

  • :iphone: FP5

  • :iphone: FP3

📖 What is OS OTA Upgrade?

Traditional Process:

  1. :inbox_tray: Download correct OS build from supported device list

  2. :inbox_tray: Download stock ROM from vendor site (for some devices)

  3. :floppy_disk: Back up your data

  4. :arrows_counterclockwise: Install stock ROM, then /e/OS ROM

  5. :arrows_counterclockwise: Restore backups if needed

OTA Benefits:

  • :white_check_mark: Simplifies the entire process

  • :warning: Requires significant development and testing

:link: Miscellaneous Information

:bar_chart: Real-Time Status

🎫 Helpdesk Services

:white_check_mark: For Paying Murena Customers

  • :iphone: Murena device purchasers

  • :cloud: Paid Murena cloud account holders

  • :gift_heart: Active donors from the past year

:alarm_clock: Response Time

  • :hourglass_flowing_sand: 5-10 day response wait period due to high volume of requests.

:telephone_receiver: Contact

:free: For Free Users

:warning: Warning: Old helpdesk email IDs are no longer monitored.

📱 Device and Vendor Announcements

:iphone: Gigaset GS290

  • :stop_sign: Sales stopped (vendor ceased production)

  • :white_check_mark: Support continues for existing users

:iphone: Murena One

  • :stop_sign: Sales stopped

  • :white_check_mark: Support continues for existing users

:iphone: Murena Two

  • :stop_sign: Sales stopped

  • :white_check_mark: Support continues for existing users

:shopping_cart: Pre-Flashed Devices

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

:iphone: Telegram Channels

:iphone: Social Media

:e-mail: Newsletters

:warning: Important Notice

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

15 Likes
2

Thanks for the updated info. I’m not sure to understand this point. You mean the update may be made available this week even if some issues remain, or the release date will be pushed forward until issues are resolved?

4 Likes
3

:slight_smile: Thanks for pointing out the error. Have corrected it in the initial post.

1 Like
4

Hoping you guys meet the target this week with the release.

1 Like
5

I think that it is much better to release next week than to release as soon as possible with bugs. Dear devs you are doing great work - nobody will be disappointed with one or two more weeks delay - quality is better than quantity.

12 Likes
6

I am also in the team “It is ready when it is ready”.

However, I can totally understand the desiere for an update. It is always great to see the new features and often an update means for some a fix for an anying bug.

7

Revolut for many I suppose.

2 Likes
8

For me an issue not receiving SMS which LOS claim to have finally fixed on ver 22 (A15)

9

Well for some FP6 users (like me), this update means more than that. It will allow to actually relock the bootloader and start configuring the phone thanks to a post-June 5, 2025 sevurity patch. Can’t do this on v3.0
4 due to the antirollback protection. Of course I’m already on v3.0.4 to try things out but I won’t configure the phone on v3.0.4 since relocking the bootloader will erase all data and I’ll have to restart all. So looking forward to v3.1.x!

4 Likes
10

The bug zoom on FP6, the full charge of 50Mpx on FP6, the bug of folders on FP6.

3 Likes
11

For me it is not beeing able to send a SMS.

12

I am in the same boat :wink: Staying with my old one until most of it is resolved

13

Actually, not for that one particular update but as a general question: would it be possible to decouple security patches (and webview updates) from other updates?

1 Like
14

I’m excited for this update because it includes the latest MicroG, which finally fixes a several year old issue preventing Microsoft Intune from working. Intune is super helpful for work and I miss it from my old phone. I’m new to /e/OS and it seems my timing is very good here! XD

But yes I’d also rather wait a little longer for a polished release. Not a huge deal.

5 Likes
15

Looking forward to the new A15 Official. Please don’t rush it, but make it right. We all are better off that way. Question: When one is currently running the Community A15, can one then do an OTA to the Official A15, once available?

1 Like
16

Pl can you share the device name.

17

The device is a Pixel 8.

18

I have the same question for the Pixel 7a

19

Switches from Community to official builds are not possible without a clean install. This would mean downloading the official build, formatting your device and doing a clean install. The reason is the builds are made using different keys. Taking a backup of your data before the process is recommended.

1 Like
20

Thanks Manoj. I will do so once the Official A15 is available.