Week 17, 2022 : Development and Testing Updates

/e/OS Smartphone Operating System Development Updates
1

Builds and Releases

v0.23

Status: :green_circle: Released

  • Release notes

  • Fixes and updates

    • Some issues may be marked confidential by their owners and will not be visible to all.

    :nerd_face: Issues get marked confidential as they contain user logs or user device information. At times when we are working on a new feature and not exactly sure if it will work, we mark it confidential during the development phase.

  • OS versions released

    • R - dev
    • Q - dev
    • Pie - dev

  • OS version Not released

    • Oreo
    • Nougat

  • stable builds released

    • GS290
    • starlte
    • star2lte
    • FP3
    • avicii
    • 2e
    • 2e emerald
    • FP4

OS OTA Upgrade

s7 /s7 edge

Status: :green_circle: Testing

  • We are testing of the OTA OS upgrade for s7 / s7 edge.
  • Volunteers who can help with this testing required

Oreo and Nougat devices

  • We will try to upgrade devices where possible. Builds are failing for devices on these two operating systems. We may eventually have to drop support for devices stuck on Oreo and Nougat unless we get ROM Maintainers willing to build and debug issues for Oreo and Nougat

GSI

  • GSI builds for v0.23 has been released.

  • GSI sources are available here

ROM Builders - Unofficial and Custom

  • A new Docker image has been released
  • Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs
    • You will have to install git-lfs (sudo apt-get install git-lfs)
    • After completing a repo sync, you will have to run repo forall -c 'git lfs pull'

:nerd_face: Reason behind these changes:

Development Activity

Status: :green_circle: In Progress

A summary of issues dev team is investigating or working on

  • v1.0 work in progress. Tentatively looking at a release date of 24th May 2022 for all users :crossed_fingers:
    • There will be updates, optimization and bug fixes coming in as part of v1.0
    • Will share more details in the next couple of updates
    • The v1.0 release will not be available for Nougat and Oreo devices
      :nerd_face: You can track the progress on some of these milestones over here
  • Bliss launcher upgrading and existing issue resolution
  • eDrive code refactoring to optimize the application
  • Updating Applications where forked …ongoing task
  • EasyInstaller to adapt to upgrade OS builds…investigation only

This is a subset of what the team is working on. Most of these tasks are under development and testing phase. Some of the issues will be confidential and not visible to all users.

Announcements

:loudspeaker: Roadmap 2022

:loudspeaker: Teracube 2e and emerald
Teracube users please note there are two different versions of the device now. 2020 released devices are classified as 2e on our site, and those released in 2021 are code named emerald. We have added a warning in the guides to help users. 2e guide and emerald guide.

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

:loudspeaker: /e/OS Pre flashed device sales

  • We sell directly in EU, US, Canada.
  • Find details of what devices are available in which countries here eSolutions Shop.

:loudspeaker: Porting and New Devices

  • Efforts to port new devices continue and details will be shared once we have working builds available :crossed_fingers:

/e/OS Links

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

9 Likes
2

By mistake you have written WeeJ instead of Week in the title.

1 Like
3

:slight_smile: Thanks for pointing that out. Have corrected it.

1 Like
4

Any information does R build for ginkgo be possibly ready at the time when 1.0 will be released?

1 Like
5

Will check with the maintainer and update as to when he is planning the release.

2 Likes
6

Would please any expert like to be the maintainer of Samsung Galaxy Note II (N7100) and debug the build issues? :smiling_face_with_tear:

7

Idem for Galaxy s4 (gt-i9505/jfltexx) ? :sleepy:
Galaxy s4mini (gt-i9195/serranoltexx) ?
Galaxy s5mini (sm-g800/kminilte) ?
following same working device tree as DivestOS ?

1 Like
8

Even Oreo and Nougat ?

9

No not Oreo and Nougat users. Those devices may have to be dropped as mentioned in the initial thread

10

I fully understand the real need for ROM maintainers for these builds. May I introduce the idea of Community maintained builds. In the case of Oneplus One bacon, I have done some experiments but do not have a device, I cannot make conclusions. (However I speculate, that the build process may now disadvantage the older builds aiding their obsolescence.)

With a community effort on this device, we could attempt to give devs sound advice on a direction to move forward. Please would any Oneplus One owners, interested on keeping this flagship device alive test my q build, and report. [Unofficial ROM] Oneplus One 'bacon' MINIMAL_APPS

1 Like
11

Something similar to the model we see on XDA where a maintainer builds as well as debugs issues on the build would be ideal. While it may be easy to find users to install and test a build, the part on finding someone to debug the issues coming up would be difficult.

12

Maybe my question from last week went unnoticed…

Are there any logs available to the public which detail what exactly is failing in the Nougat builds?

I understand that “human resources” have to concentrate on more recent models and that trying to fix the Nougat builds is not on the agenda. However, people (like myself) with technical background but who don’t have the capability of taking over maintainership for a device might still spot something which can be fixed.

Kind regards
Ingolf

1 Like
13

Indeed the XDA model is ideal; however in the case of /e/ and where the knowledge base of this forum can follow the device trees that are alive and well for LineageOS we could conceive of a looser cooperation model of individuals wishing to support /e/ development. We could see if anyone (other than myself) volunteers, [Unofficial ROM] Oneplus One 'bacon' MINIMAL_APPS - #2 by aibd, for such a looser model for Oneplus One.

1 Like
14

I did read the message last week but missed out responding. Will check with the build team if they can collect the logs and can share it.

2 Likes
15

Installed this new version, overwrote my TWRP recovery. I managed to flash it back, but I can’t adb sideload magisk, any clues?

EDIT: Can I get the boot.img of Galaxy S9+ /e/ 0.23 April 6, 2022 so I can patch it and install it with ODIN?

EDIT: Disregard, installed newest TWRP and sideload worked. TWRP 3.6.1-9.0 did the trick.