Week 35, 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.3

Status: Released :new:

Release dates : 21 Aug to 28 Aug

Coming with v2.3

Not coming in v2.3

  • S8/ 8+ OTA OS upgrade build release pushed to v2.4 as testing is not complete

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.

  • /e/OS GSI on T or Android 13

  • Development work in progress on /e/OS U or Android 14. List of devices to get the U build will be shared.

  • ETAs for all activities 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 share purchase details here and the team will offer a refund with discount vouchers for future purchases.

  • Back covers are available for purchase on the website 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 Support specific information

  • /e/OS R will be marked as legacy in our supported device list

  • v2.2 will be the last /e/OS R build. The team evaluated and found that there were no major bug fixes in v2.3 for /e/OS R as such no point in making a release of the same code base and only changing the version number.

:point_right: legacy means : No further official / stable / community / dev builds. Users with ROM building skills can build on their own.

:point_right: Legacy /e/OS versions:

  • R - or Android 11

  • Q - or Android 10

  • P - or Android 9

  • O - or Android 8

  • N - or Android 7

  • ASUS devices displaying a warning in the Smartphone Selector mentioning non-availability of official unlock methods.

Devices which will lose support

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

:point_right: Decision on continued support for FP2 pending.

Why /e/OS stops support for an OS

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.

 

:warning: Do not post test build information on the forum :warning:

  • 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

:star: Murena cloud current version : 27.1.8.3

:star: Self Hosting current version v 26.0.8.23

:point_right: Team working on the next version upgrades. Will share more information when we are ready.

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.

:information_source: 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 is on /e/OS Q and v1.17

  • Download available here

  • Sources available here

:point_right: GSI OS version will next move to T or A13 skipping the R and S . Team is working on /e/OS T GSI. Will share release dates once available

 

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)

  • Samsung: S7/7+ : R(A11) S(A12) :new:

:information_source: All OTA OS upgrades are on stable or official builds

Testing
  • Samsung: S8/8+ : R(A11) S(A12)

  • ETA v2.4 :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

 

Documentation updates

:point_right: A guide to understand how to setup Parental Controls

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

12 Likes

Aug 26th is slowly coming to an end, but there is no v2.3 for FP3 yet?
https://images.ecloud.global/stable/FP3/

There is ā€¦ https://images.ecloud.global/dev/FP3/ ā€¦ but not on stable/official yet, which you are using. As usual stable will come a few days later after seeing whether dev/community causes any potentially blocking trouble.

Also ā€¦ Feedback for v2.3 - #22 by MRTN

No Update for my S7 yet. But waiting for it :slight_smile:

Iā€™ve got an S7 too and iā€™m waiting for it to be released. Check out that link, it leads to the gitlab repo of 2.3 for S7 herolte with the validation process. Almost there :crossed_fingers::star_struck:

The last date is now 28th August. Have updated in the initial post.

2 Likes

Thanks ā€“ usually the update for FP3 comes 1-2 days before the end of the release time span, now it is there.

Yesterday I tried twice to install upgrade from my FP5 (from e/OS 2.2), but both attempts failed.
After many many reboots, no message was provided but system continues to be v2.2.
Today Iā€™ve searched for updates, but FP5 says there is no available update.
So I tried to download img file for 2.3 and tried local install: this time my attempt failed with a message ā€œcannot import local updateā€.
Any suggest?

Perhaps this might be useful. A problem with the FP5 update to 2.3 (now solved) was reported in this thread:

Unfortunately, the problem now seems different. In fact, the app now ā€œfeelsā€ the presence of an update, but downloading the update crashes the system. I have already tried twice, the first time it stopped at 70%, the second time at 29%.
Each time I was not able to ā€œrestartā€ the download from where it stopped: it was mandatory to delete partial download.
At the moment Iā€™m downloading the image file via browser and will try local installation.
Iā€™ll keep you up to date.
UPDATE: local update didnā€™t work. Iā€™m locked in 2.2.
UPDATE 2: last attempt. After 3 hours for preparing and finalizing the installation, a reboot and finally I successfully updated to v2.3.

Maybe you could try installing the local update from recovery?

Thanks for your suggest. I red it while I was trying my last attempt, which was successfull.

@Manoj: ā€œkuntaoā€ is not marked as legacy.

The build team shared this list of devices to be marked as legacy. Not all devices currently on R show up in this. Some of these devices will also get the A14 upgrade.

1 Like