Week 30 2024: Development and Testing Updates

Summary of weekly development and testing activities by /e/OS developers and volunteers. Updated content has the :new: emoji.

Release

v2.2 :new:

Status: Release due on Monday 22 July

Coming with 2.2
:star: Parental controls
:star: OTA OS upgrade for s7
:star: Ability to see last couple of updates in updater
and much moreā€¦

:point_right: Get a preview of the Release notes here

:point_right: Release timeline: 22 July to 29 July 2024

Not coming in v2.2

  • S8/ 8+ OTA OS upgrade build release likely with v 2.3 in August ( date to be confirmed later)

Upcoming releases

Ongoing development tasks
  • A web based version of Easy Installer to be released replacing the existing desktop version. At present the team is working on the development and testing of this tool. Will share ETA for release.
  • /e/OS GSI on T or Android 13
  • Development work in progress working on /e/OS U or Android 14. List of devices to get the U build will be shared.
Murena 2 specific information
  • The camera out of focus issue reported by some users, has been identified as a hardware issue. We do not have spare parts for replacements. Request you to send in your invoice details to the helpdesk@e.email ID and the team will offer a refund with discount vouchers for future purchases.
  • Back covers have been sent to users who had pre ordered. The website will be updated for those who want to order.
  • The Murena 2 is now sold out. We are working on plans to create a new and even better model in our Murena line for our users.
 

Previous 5 releases & user feedback

Device specific

  • ASUS devices will have a warning in the Smartphone Selector mentioning non availability of official unlock methods. Changes expected along with v2.2 release
  • EasyInstaller v0.21 released
To be marked as legacy

X00P , X01AD , X01BD , YTX703F , YTX703L , a5y17lte , a7y17lte , addison , ahannah , albus ,cedric , d800 ,d801 ,d802 , d803, d850 , d851, d852 , d855, ether , f400 , ginkgo , hannah , hlte , hltechn , hltekor , hltetmo , jactivelte , jasmine_sprout , jason ,jflteatt, jfltespr , jfltevzw , jfltexx , jfvelte , klte ,klteactivexx , klteaio, kltechn , kltechnduo , klteduos, kltedv , kltekdi , kltekor , lavender ,lithium , ls990 , montana , obiwan ,oneplus3, platina , rhannah , s3ve3gds , s3ve3gjv , s3ve3gxx ,scorpio ,shamu, sirius ,suzuran ,twolip ,victara ,vs985 , wayne ,whyred ,x2, z3, z3c , zl1

What legacy would mean

  • No further official builds. Users with ROM building skills can build on their own.

  • Legacy /e/OS versions:

  • R - or Android 11

  • Q - or Android 10

  • P - or Android 9

  • O - or Android 8

  • N - or Android 7

:point_right: Decision on continued support for FP2 pending.

/e/OS R or previous OS support drop reasons Google has stopped security patches. LineageOS has also dropping support. For most of the older devices vendors would also have stopped vendor patches.We would not be able to continue support as it would require backporting security patches which will require dedicated resources and is not a viable long term solution. Users are advised to upgrade to newer OS and builds where available.

 

Posting information on test builds

  • Please do not post information or links to /e/OS test builds on the forum.
  • These builds are as yet untested and under development and may in some cases cause user devices to soft brick.
  • Such information can confuse other users who do not see these builds in the updater.
  • Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds
  • If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team
  • As part of the testing team you can share your comments on the dedicated testing telegram channel.

 

Murena Cloud and Self hosting

Murena cloud NextCloud version upgraded

Murena cloud current version

Murena cloud Next Cloud 27.1.8.3

Self Hosting current version

Self hosting Murena cloud v 26.0.8

How to check the NextCloud version click here

You can find the complete documentation and current NC version under Login ā€“ Murena >> NextCloud xx user documentation. The xx should show the latest version.

  • Another way to check the current version is to check the NextCloud scan link and input https://murena.io this should display the current version number as well as the security level.

Please note if MurenaCloud patch number is not the same as the NC patch number, the rating would show up as bad \U0001f610 This is not exactly a problem. We do not immediately jump to the next NC patch as soon as it is released. We first test it and then set out with the deployment.

GSI

Current GSI version click here
  • Download available here

    • Sources available here
    • version is /e/OS Q (A10)

    :point_right: The v1.17 GSI build is the last build and is on /e/OS Q
    :point_right: GSI OS version will next move to T or A13 skipping the R and S . Release dates to be shared

 

OS OTA Related information

Completed
  • Fairphone: FP4 : S (A12) T (A13)

  • Samsung: S9/9+ : R(A11) S(A12)

  • Gigaset: GS290 : Q (A10) Android 11 (R)

  • Oneplus: avicii : A12

  • OnePlus : avicii : Q ( A10) R (A11)

  • Fairphone: FP4 : R ( A11) S (A12)

  • Fairphone:FP3 : R (A11) S (A12)

  • Fairphone:FP3 : Q (A10) R (A11)

  • Samsung: s7 / s7+ : Nougat (A7) Q (A10)

  • Samsung: s9 / s9+ : Oreo (A8) Q (A10)

  • Samsung: Galaxy S9/9+ : Q (A10) R(A11)

  • Samsung: s8 / s8+ : Pie (A9) R (A11)

  • Teracube: 2e / zirconia: Q (A10) to R (A11)

  • Teracube: emerald & zirconia : R (A11) to S (A12)

  • Samsung: S7 ā€˜herolteā€™ ā€˜hero2lteā€™: Q ( A10) R (A11)

  • Google Pixel ā€˜redfinā€™: S(A12) T(A13)

  • Gigaset: GS290: R(A11) S (A12)

  • Fairphone: FP3 : S (A12) T (A13)

    • All OTA OS upgrades are on stable builds
Testing
  • Samsung: S7/7+ : R(A11) S(A12)
    • ETA v2.2
  • Samsung: S8/8+ : R(A11) S(A12)
    • ETA v2.3 :crossed_fingers:
Our definition of an OS OTA upgrade

Usually for /e/OS ROMs to upgrade the OS you have to do the following

  • If available download the correct OS build from the supported device list
  • For some devices you also need to download the stock ROM from the vendor site.
  • Take a back up of your data
  • First install the Stock ROM
  • Next install the /e/OS ROM. Here you can take help of the install guides available on our documentation site.
  • If required apply the backups you downloaded before starting the whole process

An alternate to this tedious process is where we offer the user the option to upgrade the OS OTA. This option is available for stable device builds only.
This process is easy for the user but requires a lot of development and testing effort.

Different /e/OS build types

 

 

Misc information

Read Gael 's roadmap for 2024

Device and Vendor specific Announcements

Gigaset GS290

  • We have stopped the sales of the Gigaset GS290 on the eSolutionsShop as the vendor has stopped production of the device. We will continue support for existing users.

:loudspeaker: Message being shared on the request of our vendor partners

  • Vendors whose phones we sell on our eSolutions Store do not directly sell /e/OS flashed devices.
  • The vendors only sell their devices with their own stock ROM.
  • To get pre flashed /e/OS phones, you have to purchase them from the eSolutions Shop.

/e/OS Pre flashed device sales

  • We sell directly in EU, US, Canada and Australia
  • Find details of what devices are available in which countries here Murena Shop.
/e/OS website and social media Links and Support

Support

  • Facing issues with devices you purchased from us ? For issues you would want support on from the /e/OS support team, send in the details using the contact form

Websites

Telegram Channel

Social Media

Newsletters

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

15 Likes

Updated my Moto G5s (Montana) to 2.2. Fixed my WiFi problems :slight_smile:

2 Likes

Hello /e/dev-team,

thank you for this information.
Iā€™m afraid, this decision would mean the end of live for my redme note 7 (levander). Because the phone is used for banking and other ā€œofficial stuffā€, security patches are mandatory.

Thank you again, for keeping this old device usable for years!
Kind regards

Great project for both !
A web based version would be something like web installer for stock rom of pixel or grapheneOS ?

1 Like

The problem is R doesnā€™t get any security updates anymore. It has been dicussed in the past on the forum.

The web based installer will be like an installer for /e/OS. It will install the latest /e/OS build for a particular device. Only difference with the current installer is there would be no need to download and install. Not sure how the web installers for other ROMs work, but the concept would be the same if they are web browser based.

I donā€™t find it,
so i understand it is not implemented into the ā€œRā€ based versionā€¦

R support has being dropped. This is mentioned in the initial post as well. We will be supporting only S or Android 12 and T or Android 13 OS versions. U or Android 14 is under development.

Will it be possible to update from T to U when U is ready?

I know that the 2.2 is a staggered build, but are there any news of when the stable versions of 2.2 will be ready? Are there anything that one can do to help make the stable version ready?

And thanks for your great work!

Once your device gets U, of course you can upgrade with a new install.

If you mean OTA upgrading via the updater, as usual this will depend on your device. Just follow these weekly announcements, see the first post now for example, section ā€œOS OTA Related informationā€.


Of course there is ā€¦ Use community/dev instead of official/stable, update it timely, and hopefully donā€™t encounter blocking issues to report after updating to help the matching stable update to proceed as planned some time later.

You are running stable in order to get it when it is ā€¦ stable (or letā€™s say deemed as stable). Thereā€™s no rush on stable, or you chose the wrong build type/release channel :wink: .

@AnotherElk thanks for your answers :slight_smile:

Ok, actual e-2.2-r was announced as the final release,
But i was not expected that it will be in fact an e-1.21-r builded in july