Week 19, Development and Testing Updates

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


Release Updates

Upcoming v4.0 :new_button:

  • We are working towards the v4.0 release
  • As the version number indicates it will be a major release
  • As we near its completion, we will share more details of important updates and improvements that would come as part of v4.0
  • We will have a live launch event for the release of v4.0 (date and links will be shared)

ETA: To be shared

Current v3.7


Upcoming Milestones

:information_source: Releases planned in the future are marked as milestones in gitlab

  • Milestones
  • v4.0 will not be showing up there. Based on the QA results we will decide on how to go ahead with v3.8

Murena Account Recovery Email

Ensure your Murena Workspace account (e.email or murena.io ) has a recovery email set. New Accounts without a recovery email will face reduced functionality for 30 days and post that will be marked for deletion. The process will be the same for existing accounts without a recovery email

:backhand_index_pointing_right: To check if your Murena account has a recovery email click here

  • Link will require you to log in to your Murena workspace.
  • In case your account is disabled, you can contact me - @Manoj on this forum and I can assist with getting the account re enabled.

Documentation

:open_book: We are planning on updating our documentation site. Besides making navigation easier the plan is to make user contribution easier. Currently under planning stage, will share details once there is any progress on it.

:cloud: Migrate your data from google cloud to your Murena account. Follow the instructions in this guide.

:bug: Want to report an issue in /e/OS. Create the bug in Gitlab. If you are facing an issue in creating the ID, create or use your Murena workspace ID. Check this suggestion.


:locked: Security Information

:shield: Security Patch Release Process explained here

  • We will be sharing a detailed document about our security policy.

:bar_chart: Previous Releases & User Feedback

3.7 / 3.7.1 / 3.7.2

3.6

3.5


:cloud: Murena Cloud and Self-Hosting

:globe_with_meridians: Murena Cloud

Current Version: 32.0.6.11

Resources:

:clipboard: [Release Notes]( v32.0.6.11 Β· e / infra / ecloud / nextcloud Β· GitLab)

: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

:white_check_mark: Completed

  • :mobile_phone: OnePlus - Nord - avicii - A12 β†’ A16

  • :mobile_phone: Teracube -2e - zirconia - A12 β†’ A15

  • :mobile_phone: FP5 - Fairphone: A13 β†’ A15

  • :mobile_phone: FP5 - Fairphone: A14 β†’ A15

  • :mobile_phone: FP4 - Fairphone : A12 β†’ A13

  • :mobile_phone: S9/9+ - Samsung : A11 β†’ A12

  • :mobile_phone: GS290 - Gigaset : A11 β†’ A12

  • :mobile_phone: GS290 - Gigaset : A10 β†’ A11

  • :mobile_phone: FP3 - Fairphone : A12 β†’ A13

  • :mobile_phone: S7/7+ - Samsung : A11 β†’ A12

  • :mobile_phone: FP4 - Fairphone : A13 β†’ A14

  • :mobile_phone: S8/8+ - Samsung : A11 β†’ A12

:information_source: Note: OTA upgrades are for official or stable builds only

:test_tube: Under Development and Testing

  • :mobile_phone: FP4 - FP4 - A14 β†’ A16
  • :mobile_phone: FP6 - FP6 - A15 β†’ A16
  • :mobile_phone: FP5 - FP5 - A15 β†’ A16
  • :mobile_phone: FP3 - FP3 - A13 β†’ A15 (ETA 1- 2 months)
  • :mobile_phone: OnePlus - nord - avicii - A14 - A16 (v4.0 :crossed_fingers: )
  • :mobile_phone: Galaxy S9* - A12 β†’ A15

:clipboard: To Be Planned :new_button:

  • :mobile_phone: Google Pixel tablet - tangorpro - A14 β†’ A15

  • :mobile_phone: Murena One - A12 β†’ A15

  • :mobile_phone: GS290* - A12 β†’ A15

  • :mobile_phone: Galaxy S8* - A12 β†’ A15

  • :mobile_phone: Galaxy S7* - A12 β†’ A15

(Devices marked with an β€˜*’ have an issue with FDE encryption which requires format before the OS can be upgraded. This essential means there would be data loss. If we are able to build a A15 build for these devices, the user will have to manual install it and that would require first taking a backup of all data.)

:backhand_index_pointing_right: Check the section titled A16 Updates below

πŸ“– 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


:speaker_high_volume: A16 Updates :speaker_high_volume: :new_button:

  • We plan to update all devices currently on A12, A13, A14 and A15 to A16 :speaker_high_volume:
  • In case any device is not able of handling the A16 builds we will share that information.
  • The team expects that A16 would not be buildable or installable on some of the older gen devices like the Samsung S7 or S8. There could be more.
    • For such devices we we will work on getting them to the highest OS version possible.
  • As you may be aware A12 does not receive security patches anymore. This will next impact A13 and so on. This is a standard Google policy to end of life (EOL) older Android versions.
  • All devices we sell in our shop, with official builds are priority candidates for OTA OS upgrades. The difference is the official builds get OTA OS upgrades. Community devices will require manual upgrade.
  • Will share dates and ETA once I get them from the team.

:link: Miscellaneous Information

:bar_chart: Real-Time Service Status

:cloud: eCloud Real-Time Status

:mobile_phone: /e/OS Real-Time Status

New Gitlab account creation

  • If you are trying to create a new /e/OS Gitlab ID and facing issues with the email ID, you can try and create a Murena Workspace ID and use it to log into Gitlab. Check the updated documentation here

🎫 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

:bank: To send in your Donations : Use the email ID donation@murena.io


: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

16 Likes

Hi @Manoj, thanks for the update!
Did you get any info from the team regarding A14->A16 for avicii? (cf. previous post)

Testing for avicii is still in progress. Will update once they are ready to release it for all.

@piero @Manoj the OP mentions the issue for A16 in v3.7 which is for the A12->A16 change, I was asking about the OTA for A14->A16 that you mentioned you’d ask the team about in a previous post

The upgrade is A12 to A16. Checking on the options available for A14 user.

1 Like

The team is checking if they would be able to trigger an OTA OS upgrade A14 > A16 build for the avicii in the next release.

3 Likes

that would be awesome, thanks for checking!
fingers crossed!

Great news about upcoming v4.0 major release.

Would be amazing if you could include

Thanks you devs and everyone @ e/os

1 Like

@Manoj Hi, any progress for starlte please?

Hi @Manoj,

Any news at this point if the FP4 low call volume issue will be tackled in 4.0?

Thanks

1 Like

The A15 jump for S9/9+ is planned with v4.0 release :crossed_fingers:
Awaiting QA clearance

2 Likes

Hello how is it on the plan for the pixel 8 pro husky for the A16 in general?

when would it be planed to bring it on A16?

it has been released already since a month : /e/OS community husky download

2 Likes

:open_mouth: what !

Ive observed all the weeklies and the device list here Smartphone Selector

But not here where you’ve given the link :sweat_smile:

Thought that if it will done then the smartphone list with Variant will be updated …:sweat_smile:

@piero Many Thanks for your answer :+1:

@Manoj that’s possible that the smartphone list here Smartphone Selector is not up to date?

Thanks for pointing that out. It should be updated now.

3 Likes

@manoj Do you know if this issue will be fix with v4.0 ? Thanks

Community build for Oneplus Nord avici is unavailabe via install instructions. It only points to 3.7.1 A16 official.

Hi @Ahappo community build users with a device supported by official have to get used to a new documentation idea.

These community builds will not be documented.

But we find what we need by taking the official url … then change official to community … as:

https://images.ecloud.global/official/avicii

to

https://images.ecloud.global/community/avicii
2 Likes