Week 33, 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.1 :new:

Expected Release Date: Second week of August :crossed_fingers:

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.
    • We would attempt to recover and retry the builds on devices where it fails, but if the A15 is not possible on a particular device, we will share the device details here.

  • :white_check_mark: Various fixes and optimization coming with v3.1.1

    • Final list of fixes and optimization would show up in the Release notes which would appear once v3.1.1 is released

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

: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

13 Likes
2

Please add a ‘Batch’ column to any of the Supoorted List of devices to get A15.

That way we know when a device is expected to get the new release on Batch 1,2, x.

Thanks!

3

We do not target a specific set or batch of devices. We build for all that missed A15 in the previous release. It would only be after a build completes that we know which device builds failed. We release the successful builds. The ones that failed are re run. If they still fail then we would drop that device from our supported list. Just like users, we are also not aware or can make predictions which builds will fail.

4 Likes
4

Hi @Manoj,

I don’t understand, there is no 3.1 version, it will be direct 3.1.1 ?

5

No. There will be no v3.1

6 Likes
6

Thanks for these updates!

For people still on /e/OS S (A12), this is already causing some issues that seem to be related to versions of microG that are too old.
I there a way to update microG in the meantime and somewhere we can track progress for the upgrade towards /e/OS T for devices whose manufacturers have already provided A13 releases?

(Another Teracube 2e user waiting for the update to A13 :wink: )

1 Like
7

:loudspeaker: e/OS installer 0.12.7 is online!

:star: Support added for:

  • Otter(Shiftphone 8)
  • mimir (volla tablet)
11 Likes
8

The closest i’ve seen to this, is by browsing the Milestones on gitlab e.g. in that particular link you can see that depending on the device, test cases are being run for either S(A12), T(A13), A14 or A15. For Zirconia, it looks like test cases are being run on S for the upcoming release.

1 Like
10

I am still on A13 with my FP3. How long will it take for the OTA upgrade to A14 or A15? I’ve been waiting half an eternity for it. Some apps no longer work. I really hope it will be soon.

2 Likes
11

That probably has nothing to do with the fact that you’re still on Android 13.

3 Likes
12

Which ones?

1 Like
13

No mega important apps but still regrettable. For me it’s Payback, LidlPlus and Penny that don’t work.

14

A few apps from f-droid are still not available in App-Lounge with versions as in f-droid. E.g.: Element X

15

Last updated: July 24, 2025
Minimum Android Version: 7.0

Last updated; August 13, 2025
Minimum Android Version: 8.0

Last updated; August 13, 2025
Minimum Android Version: 8.0

(Info given by Aurora Store, an Open Source client for the Google Play Store, so the info is from the Google Play Store.)

This seems to be the case, indeed.

@Atticus81 … any error messages?

2 Likes
17

Error messages:

Payback:

Screenshot_20250813-205627_PAYBACK
Screenshot_20250813-205627_PAYBACK1080×2160 59.8 KB

Lidl Plus:

Screenshot_20250813-205712_Lidl Plus
Screenshot_20250813-205712_Lidl Plus1080×2160 75 KB

When I try to log in to Penny:

Screenshot_20250813-205953_PENNY
Screenshot_20250813-205953_PENNY1080×2160 125 KB

I also have an older version of GMX because the latest versions don’t work. The app cannot be opened.

18

@AnotherElk I just got Lidl Plus working again by disabling the APP Tracker lock. Payback and Penny APP are still not working.

19

Payback will not work because of your unlocked bootloader.

20

Waiting for an OTA upgrade to a new Android version indicates running official /e/OS, and on an FP3 this would indicate a locked bootloader.
But the chance is not zero still … @Atticus81: Is your bootloader unlocked?

But in the end all these Apps are Google-dependent. They might work on /e/OS at a certain point in time thanks to microG … or not :person_shrugging:.

1 Like
21

The bootloader is locked. Banking apps (Consorsbank, Santander, Barclays) work very well. Only Payback, Penny don’t work at all and GMX only the older version.
In any case, I would be very happy if the OTA upgrade for the FP3 hopefully comes soon to A14 or A15. It has been planned since January (Week 5).
Thanks for your support! I don’t have much expertise in this area.

22

I also have the same Problem with the Penny App. I am on Android 13 on a Fairphone 5, the bootloader is locked. I wonder if its a Problem with the Firebase check. I got the same error message.

1 Like