Week 37, 2025: Development and Testing Updates

: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: Current Release: v3.1.1 :new:

Status: Ongoing

  • Release Notes
  • The release is staggered across a week as usual. We stagger the releases to avoid loads on the server as there are more than 200 devices, with up to 3 OS versions being released for most of the devices.
  • ETA : 2 September (started)
    • :warning: Date got pushed forward from last week as A15 builds failed on multiple devices. We continue running the builds and expect to be able to release them this coming week.

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

  • :white_check_mark: Various issues and fixes


  • :white_check_mark: Devices getting the A15 build along with v3.1.1
  • :no_entry_sign: Devices not getting A15 builds in v3.1.1 as the builds failed. The builds would be released in v3.2 :crossed_fingers:
  • :no_entry_sign: Devices which were on A14 but builds failed and not getting v3.1 A14 builds in v3.1.1 . They will get the A14 build along with v3.2

:crossed_fingers: Tentative release of v3.2 would be towards end of September :crossed_fingers:


  • :warning: FP6 official users on A15 should pick up v3.1.3 release dated September 5
  • There was a fix missing in v3.1.2 which required another emergency release.
  • We will remove the v3.1.2 FP 6 official release from the updater in case it is still showing up.
  • We are working on streamlining the release process. The quick releases for the FP6 official A15 builds were to resolve issues that were reported at the last minute.

:loudspeaker: FP5 A14 to A15 OTA OS upgrade is being released along with v3.1.1 - the current release. :new:

:loudspeaker: FP5 A13 to A15 OTA OS upgrade will come along with v3.3 - that is expected in 2 months time. :new:


: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 released in v3.2 :new:


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

:clipboard: Version Naming Convention Update

New Standard: Using OS version numbers instead of letters

  • /e/OS VA15

  • /e/OS UA14

  • /e/OS TA13

  • /e/OS SA12

  • /e/OS RA11

  • /e/OS QA10

  • /e/OS PA9

  • /e/OS OA8

  • /e/OS NA7

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

🧪 Testing Phase
  • avicii - OnePlus : S (A12) → U (A14)
📋 To Be Planned
  • :iphone: FP5 - A13 → A15 (v3.3)

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

13 Likes
  • :warning: FP6 official users on A15 should pick up v3.1.3 release dated September 5
  • There was a fix missing in v3.1.2 which required another emergency release.
  • We will remove the v3.1.2 FP 6 official release from the updater in case it is still showing up.
  • We are working on streamlining the release process. The quick releases for the FP6 official A15 builds were to resolve issues that were reported at the last minute.
3 Likes

FP6 community builds for v3.1.3 are also being built. We will release them once they are complete. May be later today or by tomorrow.

2 Likes

The explanation behind these quick releases is that with v3.1.1 on FP6 we detected the IMEI related issue where a hardcoded value was being passed. This resulted in v3.1.2 which resolved the issue but still had issues with some SIM cards.Which necessitated a v3.1.3 release.
We are discussing how to mitigate such hotfix releases.
While we test all builds before release at times some features break on select SIM card or networks.
We sincerely regret the confusion around the FP6 official release and will work on streamlining the process in future.

11 Likes

It would be nice to have a open source device tree, then others could spot issues or help fixing things. It would be possible to create merge request to e.g. enable double tap to wake support or similar.

BoardConfig needs:

# Screen tap-to-wake
TARGET_TAP_TO_WAKE_NODE := /sys/bus/spi/devices/spi0.0/gesture_wakeup

Then we need

    <!-- Whether device supports double tap to wake -->
    <bool name="config_supportDoubleTapWake">true</bool>

in the right overlay. Not sure which one it is now. And maybe selinux needs to be adapted. But it is pretty simple to add that.

2 Likes

Latest update on FP6 3.1.3-a15 (two updates over this weekend) broke hotspot over WiFi
When connected to 5G, hotspot works as expected
When connected to Wifi, hotspot turns off the minute you try to turn it on.
before the update this worked as expected, after updates not anymore.
No message, the toggle just turns off immediately.

We have been unable to reproduce this issue when tested.

@Manoj

Hello,

Android 15 is available for FP4 community version. When Android 15 will be available for FP4 official version ? FP4 is compatible with Android 15. I see information for FP6,FP5 et FP3, but nothing for FP4. It seems that FP5 received A15 (official), why not FP4 ?

Thanks.

Let me check. The last I heard it was being tested.

Update: Early 2026 . Official builds require OTA OS upgrades. That will take some additional time for development. The community builds are on A15 but those are manual upgrades.

2 Likes

These A15 builds have been published.

  • These builds are community builds and will require to be manually installed.
  • You can follow the installation instructions from the guides in our documentation site. Find the device based on the device name in the table. Follow the link to view the guide and download the builds.
1 Like

I just performed the upgrade to 3.1.3 and I get unexpected device reboots randomly with a very brief message that I can’t read until the end as it flashes too fast. But it says something like “region changed to US, rebooting in 5s…”. And it seems everytime the region changes, sometimes I have seen it be EU.

1 Like

I disabled the position masking feature in the advanced privacy settings and it seems to help with stability for a while. But as soon as I launched another app that requires my position, I see the little blue location icon on the top right and the same message occurred again and it reboots too.

I am on FP6 with 3.1.3 OTA from sept 5

Is there anything I can provide you that would possibly give some insight?
Like a log or something?
I can make a screen video capture to show, but it wouldn’t be something you can work with I think.

I’ve had a few random reboots too so far. I haven’t noticed any messages like that, though that doesn’t mean they weren’t there.

EDIT: I do see that message. It now reboots as soon as I unlock it every time. Which means the phone is effectively boot looping just with the added step of unlocking it on each boot. It is unusable. I don’t even think an OTA update would work because it can’t stay unlocked long enough to update it. It seems to switch between US and EU on every boot. I’ll take my SIM out and see if that helps maybe?

1 Like

Talking about reboot, in my first post I spoke about 2 updates, but seeing these mentions about reboots I am inclined to think that what I thought to be a second update was probably in fact a reboot.
Hard to say but just a thought. Do what you want with my two cents

Okay taking the SIM card out stops the boot loop. But here is a screenshot of the error.

I guess taking the SIM out will be necessary for an OTA to fix this. My phone is no longer a phone but it will

I’ll also note the wifi has been very unstable. Not sure if that’s related or not.

Welp… Even without the SIM card it’s doing it now too. :frowning:

1 Like

Thanks IMEI looks again like it is suppose to :ok_hand:

1 Like

As an update, I’ve been running stable for several hours now, even with my SIM card installed. The one thing that I’ve done is turned location services off for the entire phone.

My rationale was given it seemed to be a region change thing, maybe it’s using that to determine the region. It seems to be helping. Or maybe it’s a coincidence.

EDIT: I must have jinxed it. It rebooted…

Same thing: disabling the location service altogether at the phone level seems to have fixed the random reboots.

Hopefully this gets fixed soon because having to disable GPS pretty makes the phone useless imo.