Week 47, 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

Next Release : v3.3 :new_button:

:tear_off_calendar: ETA: November last week or early December :crossed_fingers:

Status: Under beta testing

:airplane_arrival: Coming with v3.3

:backhand_index_pointing_right: Android Auto fix for A15 users

:backhand_index_pointing_right: Bluetooth connection issue fix for FP6

:backhand_index_pointing_right: Location broken on FP3 fix

:backhand_index_pointing_right: Builds that failed in v3.2 release

  • Xiaomi Redmi 12C earth will get A15 build

: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 accomodate them in the next release cycle.

:warning: Important Announcement

: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 migrate to A13 or higher

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

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

:white_check_mark: Current Status: RESOLVED

:file_folder: MurenaRecovery Folder

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

:floppy_disk: Back up your device data to avoid overwriting older files

:open_book: Complete guide available here

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

Log into your Murena account

Go to Dashboard → Your Profile (top right)

Navigate to Settings → Client Synchronization (left sidebar)

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

:locked: Security Information

:shield: Security Patch Release Process explained here

:bar_chart: Previous Releases & User Feedback

:memo: Feedback Threads

v3.2

v3.1.4

v3.1.1

v3.0.4

v3.0 / 3.0.1 / 3.0.2

:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 31.0.10.11 :new_button:

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

  • :mobile_phone: FP3
  • :mobile_phone: tangorpro - Google Pixel tablet 7
📖 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

:link: Miscellaneous Information

:bar_chart: Real-Time Service Status

:cloud: eCloud Real-Time Status

:mobile_phone: /e/OS 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

: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

phone
phone427×374 173 KB

15 Likes
2

Will Android Auto work without Google services, or will they be required? In the beta version, I had to install Maps, Google, and Google Voice Control.

3

The changes were specific to make it work on A15. Will check with the developers if google apps requirement was addressed.

Update: The requirement to install google apps first before Android Auto still exists.

The efforts to remove this dependency continue.

7 Likes
4

Hi there, my OnePlus 8T is on e/OS 3.2-a14-20251025540136-community-kebab. Is there a simple way to upgrade to A15? In instructions it says ‘make sure you are on Android 13 or 14. My OS is not stockrom, however it is A14
. Thanks for answering !

1 Like
5

what was stockOS before you install /e/ ?

6

I think OxygenOS a13

7

@TecMar , I was able to get Android Auto working on /e/OS using stubs; I outlined the procedure here, complete with known-working download links:

I hope it helps!!

1 Like
8

Does the Stub Apps are “Dummys”? I think /E/OS will fixed this with the next Version. I think i will be waiting, because the actual Android Update is Higher then the /E/OS because Rollback crack.

9

Does the Stub Apps are “Dummys”? I think /E/OS will fixed this with the next Version. I think i will be waiting, because the actual Android Update is Higher then the /E/OS because Rollback crack.

My understanding of this question is a bit strained
but let’s see what I can tell you


1.) The stub apps are "just enough “app” for Android Auto to pass its initial configuration check, and move on. They’re a few hundred kilobytes each, certainly not enough to include actual Google code.
2.) Far be it for me to put words in the mouths of the /e/ developers, but I’m unaware of any ROM that includes a fully-OSS implementation of Android Auto, and the App Lounge version will always check for Maps and GoogleTTS
so unless /e/OS is going to start shipping with stubs for these apps out of the box (either the linked ones, or their own rewrites), either the stubs or the official apps will be necessary.
3.) No shame in waiting if you so choose, but I’m not familiar with what you’re describing in terms of “rollback crack”
my longer post was about the drama with my assumed API version mismatch; everything I’ve tried works with AA so I don’t think you’ll end up with any sort of versioning issue
though perhaps your workflow requires that your phone remain unrooted, while the described procedure requires root.

I hope it helps you make the best decision for your needs!

1 Like
10

There’s a security issue when switching from a newer security patch to an older one on Android. Apparently, the bootloader gets locked and can’t be unlocked. At least, that’s what I’ve found online.

I think switching from Android to /e/OS won’t be a problem, but to switch back to Android, the security patch needs to be the same as or higher than the previous one.

Thank you for your help, I will first see what /E/OS is doing and whether everything runs stably with version 3.3.

11

Yes, but not only on Android. This is conceptual. If you return any computer device to an older security patch level there will be more security issues which potentially could get exploited because they weren’t fixed yet.

This is not the case universally, but there seem to be circumstances when this can happen, which of course is annoying.
Users can take precautions against this by proceeding manually before trying to relock the bootloader. A forum search for e.g. fastboot flashing get_unlock_ability is advised beforehand.

In my understanding you can go back to an earlier security patch level, but then you shouldn’t try to lock the bootloader again until the security patch level caught up to what was installed before. The locking is the trigger for rollback protection.
It’s worth to keep in mind that locking as well as unlocking the bootloader will force a factory reset for security reasons, so doing it at any point will wipe the phone.

If implemented in the bootloader, Android rollback protection applies regardless of what kind of Android it is. It can apply in both directions. /e/OS install instructions cover this in detail where applicable (example: FP6, note the red Caution under Requirements).

12

:loudspeaker: Murena Cloud has been updated to NextCloud v31.0.10.11 :loudspeaker:

Check out the release notes

5 Likes
13

A note on OS upgrades

we are working on the jump to A15 for Teracube and Murena One device. From A12 to A15

For devices like
GS290
Galaxy S9
Galaxy S8
Galaxy S7

There are issues with FDE encryption. Which would mean no OTA OS upgrades for the old devices. If possible, to build a A15 it would require a format and manual install. Older kernels like 4.9 on the older devices are not going to be upgradable to A16. Older kernel compatibility is blocked by google.

10 Likes
14

As a S9 owner, I would be more than happy to install updates manually, if this makes A15 possible for my device.

2 Likes
15

OTA OS upgrades means upgrading from an older underlying Android version to the new underlying Android version (15 in this case) via the updater without having to install manually (see first post, section OS OTA Information). This would not be possible now, so a manual install of /e/OS based on the new Android version would be needed, a process which by default should wipe the phone.
Once you are running /e/OS based on the new Android version, regular updates within this Android version will arrive as usual via the updater.

1 Like
16

Manoj don’t talk about manual update,
but talk about manual reinstall with format /data

1 Like
17

I’m still okay with that if it still keeps my old warhorse valid.

2 Likes