Week 40, 2025: Development and Testing Updates

/e/OS Smartphone Operating System Development Updates
1

: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

:crystal_ball: Current Release: v3.1.4 :new_button:

Status: Released

Key Features:

  • :white_check_mark: September security patch

  • :white_check_mark: Browser updated to latest upstream Android patches

  • :white_check_mark: FP3 vendor patch updated

    • FP4 vendor patch update moved to v3.2 release

:nerd_face: The A15 builds for certain devices failed due to last-minute changes made by upstream device maintainers. These changes, which are pulled to our servers, are critical for addressing bugs and improving device performance. However, their late integration can occasionally cause build failures. We understand that these failures may cause inconvenience, and we appreciate your patience. As users, you’ll recognize the importance of incorporating these updates to ensure stable and functional ROMs.

:backhand_index_pointing_right: Team has been requested to come with a plan to prevent this failure in future releases. Also team would be working on sharing these builds along with v3.2

List of devices for which the A15 build failed
Vendor Device Name CodeName
ASUS ZenFone 8 sake
Essential Essential PH-1 mata
F(x)tec Pro¹ pro1
Fairphone FP3/3+ FP3
Fairphone FP4 FP4
Google Pixel 4a 5G bramble
Google Pixel 4a sunfish
Google Pixel 8a akita
Google Pixel 5a barbet
Google Pixel 3 blueline
Google Pixel 3a XL bonito
Google Pixel 9 Pro Fold comet
Google Pixel 4 XL coral
Google Pixel 3 XL crosshatch
Google Pixel XL marlin
Google Pixel 5 redfin
Google Pixel 3a sargo
Lenovo Z5 Pro GT heart
Lenovo Z6 Pro zippo
LG G7 ThinQ g710ulm
Motorola Moto G7 river
Motorola edge 40 pro rtwo
Motorola moto g84 5G bangkk
Motorola Moto Z3 Play beckham
Motorola edge 20 berlin
Motorola edge 2021 berlna
Motorola moto g power 2021 borneo
Motorola moto g10 capri
Motorola moto g30 caprip
Motorola moto g9 power cebu
Motorola moto g32 devon
Motorola edge 30 dubai
Motorola Moto G6 Plus evert
Motorola moto g 5G - 2024 fogo
Motorola moto g34 5G fogos
Motorola moto e7 plus guam
Motorola moto g9 guamp
Motorola moto g42 hawao
Motorola Moto G 5G / Motorola One 5G Ace kiev
Motorola Moto G7 Plus lake
Motorola moto z3 messi
Motorola edge 30 neo miami
Motorola Moto G 5G Plus / Motorola One 5G nairo
Motorola Moto Z2 Force nash
Motorola Edge S / Moto G100 nio
Motorola Moto X4 payton
Motorola edge 20 pro pstar
Motorola moto g52 rhode
Motorola moto g82 5G rhodep
Motorola moto g200 5G xpeng
Nubia Mini 5G TP1803
OnePlus 7 guacamoleb
OnePlus 7T hotdogb
OnePlus 9 lemonade
OnePlus 9 Pro lemonadep
OnePlus Nord N200 dre
OnePlus 5T dumpling
OnePlus 7 Pro guacamole
OnePlus 7T Pro hotdog
OnePlus 8 instantnoodle
OnePlus 8 Pro instantnoodlep
OnePlus 8T kebab
OnePlus 9R lemonades
OnePlus 9RT martini
OnePlus 11 5G salami
Razer Phone 2 aura
Realme 10 Pro 5G luigi
Realme 9 Pro 5G oscar
Samsung Galaxy A52 4G a52q
Samsung Galaxy S10 5G beyondx
Samsung Galaxy Tab S5e gts4lv
Samsung Galaxy Tab S7 gts7lwifi
SHIFT SHIFT6mq axolotl
Sony Xperia XA2 Ultra discovery
Sony Xperia 10 kirin
Sony Xperia 10 Plus mermaid
Sony Xperia 1 II pdx203
Sony Xperia 5 II pdx206
Sony Xperia 5 III pdx214
Sony Xperia 1 III pdx215
Sony Xperia 1 V pdx234
Sony Xperia XA2 pioneer
Sony Xperia XA2 Plus voyager
Xiaomi Poco F1 beryllium
Xiaomi Mi 6 sagit
Xiaomi POCO F3 / Redmi K40 / Mi 11X alioth
Xiaomi Mi 10T / Mi 10T Pro / Redmi K30S Ultra apollon
Xiaomi Mi MIX 2 chiron
Xiaomi Redmi K20 / Mi 9T davinci
Xiaomi Mi 8 dipper
Xiaomi Mi 8 Pro equuleus
Xiaomi Redmi Note 8 / 8T ginkgo
Xiaomi Redmi 7A / 8 / 8A / 8A Dual Mi439
Xiaomi Redmi 4A / 5A / [Note 5A / Y1 - Lite] Mi8917
Xiaomi Redmi 3S Mi8937
Xiaomi Mi A3 laurel_sprout
Xiaomi Mi MIX 3 perseus
Xiaomi Mi MIX 2S polaris
Xiaomi Redmi Note 10 Pro sweet
Xiaomi Mi 8 Explorer Edition ursa
Xiaomi Redmi Note 7 Pro violet

: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

  • :counterclockwise_arrows_button: These builds will be released in v3.2

:warning: Important Announcements

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

Effective Immediately:

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

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

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

Recommendation for Users:

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

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

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

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.

:locked: Security Information

:shield: Security Patch Release Process

:open_book: Complete explanation available here

:date: Upcoming Releases

A15 Device Lists

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

:counterclockwise_arrows_button: Ongoing Development

🛠️ Active Development Tasks

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

  • :magnifying_glass_tilted_left: Team exploring OTA availability

  • :mobile_phone: 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: 30.0.14.11 :new:

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:

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

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

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

  • :mobile_phone: FP5 - A13 → A15 (v3.3)

  • :mobile_phone: 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. :counterclockwise_arrows_button: Install stock ROM, then /e/OS ROM

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

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

:free_button: For Free Users

: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

:mobile_phone: Telegram Channels

:mobile_phone: Social Media

:e_mail: Newsletters

: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

phone
phone427×374 173 KB

15 Likes
Feedback for v3.1.1
IRRÉSOLU - Fairphone 5 - Official - J'attendais la version 14, mais je n'ai que la 13
2

Thanks for the hard work on the 3.1.4 release. Got my FP6 as daily driver again after the random reboots were fixed!

2 Likes
4

Absolutely loving this!

2 Likes
5

fyi - microG development has kind of come out of extended summer vacation (August, half of Sept) and commits are happening again. I see bugfixes (Google sign-in, Playintegrity, Splitinstall) but also major new api surface (Blockstore) - so next microg repo sync will have more than during summer

6 Likes
6

My device is marble, and I flashed this rom. I have a problem. I set the pattern unlock, but no matter how I operate it, it can only be unlocked by sliding.

7

:new: Google Pixel 7 ‘panther’ will not be getting the official A13 build as part of v3.1.4 release. The reason is team is working on the A15 release for this device. We expect to release it with v3.2 next month (Oct).

1 Like
8

Very quiet week of developments and uptades!

1 Like
9

The 3.1.4 release notes for all Android versions (12 to 15) state that “We are proud to deliver the /e/OS 3.1.4 version for supported devices whether they are on an Official or a Community build.”

3.1.4-t-official for FP3 is there , but 3.1.4-t-community is not (as of now).
Will 3.1.4-t-community for FP3 still arrive?

Also, while 3.1.4-a14-community is there, 3.1.4-a15-community is not. But as official is still on Android 13 (T), this doesn’t contradict the release notes at least.

10

image

A15 failed for the FP3

1 Like
11

Hi Manoj, I see that the Motorola Moto G6 Plus has many problems compiling and I see that there are details with its system memory partition size which is 2.65GB. Would support be withdrawn? Some time ago I saw that the Derpfest project developed a recovery and a patch to give Evert dynamic partition support since it does not support it by default, could the same methodology be applied? Another solution that I also found was that in the Evolution X ROM, the developer resized the size of other partitions that had space left to increase the system partition, like a repartition, could any of these solutions be applied to evert?

12

I have passed on the details to the build team. Will share their response.

1 Like
13

was interested how this works (to dynamic), not fully sure if that is all, but some pointers:

longterm it’s better to just use an online-installer after initial setup for some parts to make the image smaller again - couple it to that long wish of /e/OS users being able to remove default apps

1 Like
14

Interesting to hear from @LineangelCM that evert has system partition size 2.65G. ocean has 2.6G and a build was created by the team and published containing no Maps, 3.1.4-a15-20250916526794-community-ocean.

This build runs well (there is free space on system of 27M). It would be great to hear that the team would consider to implement this MINIMAL_APPS approach.

If this were to be considered (in case the team does not have access to some of the 5 Moto and Pixel devices listed in bad news for … would it be useful for other owners of these devices to share system partition size?

1 Like
15

Indeed, the MINIMAL_APPS flag is what is set, while building for such devices. Will share if the build succeeded.

1 Like
16

Ah thanks, I forgot it was in the list, but …

… or was 3.0.4-t-community the last Android 13 (T) community version for FP3 and users should upgrade?

Week 41, 2025: Development and Testing Updates
17

Of course it seems like a good idea, to share the size of the system partition of our devices, although it seems fine to me to try with the state of minimal apps, even so I will see if I can communicate with the maintainer of the moto g6 plus with evolution x to see if a flashable script can be made and increase the partition without having to modify it much.

18

Hi Manoj, from what I’ve seen, what the Evolution X maintainer did was adapt the OEM partition as system_ext to free up space on the system partition. I imagine something similar can be done with version A15 of the /e/ ROM. Given that the OEM has approximately 0.5GB unused, leaving that free.

19

How is this technically achieved?

  1. Edit the device’s fstab (mount file in the device tree).
  • In the evert device tree, the /oem entry is changed to mount that partition as /system_ext.
  • Simplified example:
    bash /dev/block/bootdevice/by-name/oem /system_ext ext4 ro,barrier=1 wait
  1. Modify BoardConfig.mk and device tree to declare that the device has system_ext.
  • Add flags such as:
    makefile BOARDUSESSYSTEM_EXT := true
  1. Move packages and libraries that were previously in /system to /system_ext.
  • This is done in the ROM makefiles (e.g., device.mk), indicating that certain modules should be installed in system_ext.
  • You even have to update the /e/ recovery for it to work and be detected when updates are released.
    I don’t know if this solution allows adapting the evert builds to work like this, it is what was applied with Evolution X, which seems to me to be somewhat simpler than implementing what Derpfest did, it could even work with Ocean and others.
1 Like
20

is that a comment by a evo-x dev? I can only find a BOARD_USES_SYSTEM_EXTIMAGE build flag referenced in evolution-x sources.

21

Do we know when microG will update on /e/OS? Will this be in the next monthly update from Murena OTA (on FP6, latest eOS version) or will this form part of an update in the background in MicoG app?

Curious because it’s causing issues with my Garmin Connect app (see this thread)