/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
emoji.
Release Information
Upcoming Release: v3.2
ETA: 
Next week
- The testing is still in progress. Will have a release date once the QA team gives the go ahead. Expect a release next week.
Tentative list of fixes and optimizing to come as part of v3.2
Coming with v3.2
✅ Google Pixel 8 shiba official A14 to A15
✅ Google Pixel 7 panther official A13 to A15
✅ FP5 A14 to A15 OTA OS upgrade (installation of v3.1.4 required to view this build)
✅ FP4 vendor patch update moved to v3.2 release
✅ FP6 charging limit will be available
✅ October security patches for A13 and above.
✅ FP6 users to get the Fairphone camera app
Android Auto fix for FP6 users pushed to v3.3
Location broken on FP3 fix coming with v3.3
FP6 Random reboot issue
Issue reported on stock ROM as well. /e/OS developers are working with Fairphone developers for a resolution. Team has not been able to reproduce the issue. Request users facing this issue to share logs in the issue on gitlab . We are looking for details like the Service Provider details, information if reboot happened while travelling anything specific. Also wanted to confirm if the reboots started with v3.1.1 or were you experiencing them earlier as well.
Click the arrow on the left for details on the logs we require
We need two logs.
Log 1: Boot Sequence Log
The goal here is to capture the entire boot process, from the very start until the device is fully ready.
Trigger the Boot: Manually reboot the phone. Start the log as soon as the Fairphone splash logo is shown
adb logcat -b all > boot_log.txt
Stop the Log: Wait until you see the homescreen and the device is fully settled.
Log 2: Continuous Log until Issue Occurs
The goal here is to capture a long-running log that will catch the moment the issue happens.
Trigger the Boot: Manually reboot the phone. Start the log as soon as the Fairphone splash logo is shown
adb logcat -b all > continuous_log.txt
Reproduce the Issue: Do not stop the log. Keep it running until the phone automatically reboots on it’s own, ie. reproducing the issue mentioned
/e/OS - A15 - /e/OS V
Status: 
Released - First batch of device builds available
Supported devices to get A15 builds
View the complete list of supported devices
Known Issues:
Some device builds failed during compilation due to last-minute upstream code updates
Team working on releasing all devices planned for A15, as part of v3.2
Important Announcement
A12 - /e/OS S - Support Ending - Effective Immediately:
Support for A12 (/e/OS S) discontinued
Official A12 builds are an exception. They will continue getting A12 builds until we are ready to migrated to A13 or higher
This aligns with our policy of supporting three OS versions simultaneously
All supported devices will be pushed to higher OS versions where possible
Recommendation for Users:
We recommend users on A12 community builds should migrate to the A12 official build
Take a backup before proceeding
Server Outage related
Current Status: RESOLVED
MurenaRecovery Folder
Enabled and visible for all users
Started with premium users, expanded to all impacted users
The folder Will be visible for several months (end date TBD)
Important Actions for Users:
Back up your device data to avoid overwriting older files
Complete guide available here
Notes Sync
Cloud sync possible post v2.9 release
If not syncing after v2.9 upgrade,read the next section. Backup local notes before proceeding
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)
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.
Documentation Updates
Documentation Released
Murena Voice to Text
Murena Vault
Find My Device
Murena Find - replacement for Spot (documentation updated)
Version Naming Convention Updates
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.
Security Information
Security Patch Release Process explaned here
Ongoing Development
🛠️ Active Development Tasks
/e/OS GSI on T (A13)
Team exploring OTA availability
App development for compatibility detection
ETA to be shared
Previous Releases & User Feedback
Feedback Threads
Murena Cloud and Self-Hosting
Murena Cloud
Current Version: 30.0.14.11
Resources:
Self-Hosting
Current Version: v26.0.8.23
Resources:
Status:
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
Note: If MurenaCloud patch number differs from NC patch number, the rating may appear as bad. This is normal - patches are tested before deployment.
GSI (Generic System Image)
Current Version: /e/OS A10 v1.17
Resources:
Next Version: /e/OS T (A13) - skipping A11 and A12
Release dates to be announced
OS OTA Information
✅ Completed
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)
Note: OTA upgrades are for official or stable builds only
Under Development and Testing
- avicii - OnePlus : S (A12) → U (A14)
- FP5 - A13 → A15 (v3.3)
- FP4 - Early 2026
To Be Planned
- FP3
📖 What is OS OTA Upgrade?
Traditional Process:
Download correct OS build from supported device list
Download stock ROM from vendor site (for some devices)
Back up your data
Install stock ROM, then /e/OS ROM
Restore backups if needed
OTA Benefits:
Simplifies the entire process
Requires significant development and testing
Miscellaneous Information
Real-Time Service Status
/e/OS Real-Time Status
🎫 Helpdesk Services
For Paying Murena Customers
Murena device purchasers
Paid Murena cloud account holders
Active donors from the past year
Response Time
5-10 day response wait period due to high volume of requests.
Contact
Murena Helpdesk Contact Form
For Free Users
Warning: Old helpdesk email IDs are no longer monitored.
📱 Device and Vendor Announcements
Gigaset GS290
Sales stopped (vendor ceased production)
Support continues for existing users
Murena One
Sales stopped
Support continues for existing users
Murena Two
Sales stopped
Support continues for existing users
Pre-Flashed Devices
Available in EU, US, Canada, and Australia. Check the complete list on the Murena shop
Purchase via Murena Shop
🌐 /e/OS Website and Social Media Links
Official Websites
Telegram Channels
Social Media
Newsletters
Important Notice
Do Not Post Test Build Information on the Forum
Why this is important:
Test builds are untested and may cause device issues
These builds can potentially soft brick user devices
Such information can confuse other users who don’t see these builds in the updater
Not all forum users are experts in custom ROM installation
For Interested Testers:
If you understand custom ROMs and can perform basic testing
Join the testing team
Share feedback on the dedicated Telegram channel
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
