Only few new devices recently

[JoeHardi]

Hey there,

just because I am curious. I recognized that within the last few month only very few new devices where being added as supported devices.

How come?

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

[forart.it]

…maybe lack of maintainers ?

[piero]

Also /e/ list of device depends on Lineage list.

Are there new models from their side ?

[hm8krvg1b]

Hi. I totally agree. I also noticed, only a few devices were added, since 1.11.
I have a poco f3, alioth. I can not update to the newest e/os vetsion.
Still waiting for the released.

Can anyone help me? Does anyone have news?

[Manoj]

We will add newer devices once the /e/OS T builds go out. The idea, in fact my suggestion, was we take one step at a time. Instead of releasing upgrades and new devices in one shot. That way, we upgrade existing devices first and then introduce new ones. The current plan is to release /e/OS T in August along with v1.14 which should come out roughly towards the end of August.

[gchevalier]

I just sadly break the screen of my Oneplus Nord avicii few days ago… Not so simple to find a new supported device, only 3 from 2022
I will try to repair the screen, or get a refurbished FP4

[forart.it]

I still believe that a “build request wizard” that collects proposed devices’ (re)sources and inserts them into a registered-users votable build scheduling list could be a much more efficient/effective strategy for this goal.

Of course a dedicated app/db (such as SpecDevice, for example) would be cool to collect devices’ details to ask for a build or “push” (= vote) its position in the build shedule list.

Last but not least, it would be also extremely cool to have an \e\ autobuild serv-ice/er, but is well known that’s difficult to materially achieve it (a GAN assistance is probably required)…

…anyway here are some scripts that might be inspiring (note: dunno about their state/functionalities achieved, but looks interesting… it would be nice to involve those devs, IMHO !):

• AABS - Handcrafted, automated Android Build Script, written in PHP
• LineageOS + microG for davinci buildscript - Simple script for Debian/Ubuntu-based build servers;
• Script used to build lineage rom on server
• Automated environment to compile android firmware on build servers
• jenkins_bot - Common BASH Script for Automated Android Builds
• AutomatedBuildScript - This python script is designed to simplify the android build process as well do super cool thingz
• Ipython notebook to build the OS inside Google Colab

EDIT:

• build-actions - autobuild your android system!
• ErfanGSIs Tool Workflow - This is a repository for generating GSIs using Erfan GSIs Tool and GitHub Actions
• Experiment of building Android OS on Github Actions server
• Build Your Own Kernel with Github Action - Automaticcaly build android kernel by github actions
• Android Kernel Actions - An action to build an Android kernel with specified toolchains
• android-kernel-builder - Build Android Kernel through github actions
• MikaKernel Builder - Build your kernel with Github Action [Android ARM64 Only]
• Android Kernel Actions - Build kernels with GitHub actions
• Action-Recovery-builder - Github Action to compile various Android Recovery
• recovery-builder - Android Custom Recovery Builder By Github Action Workflows
• android-recovery-action - A Github Action to build android recoveries

Hope that inspires !

[JoeHardi]

Sounds great!

I am still looking for a compact phone and the Asus Zenfone 8 seemed like the perfect option but since they deactivated the bootloader unlock… Its not working anymore.

I am looking forward on the new phones!

[forart.it]

OK, here’s a very basic example (made in Google Forms) of a wizard that \e\ should adopt for device requests:
https://forms.gle/XpjxTCM6cUMvMFWn8

Hope that inspires.