[LIST] New devices which will be added with AOSP 15 or /e/OS V

It may well be present with the release of e-3.1.x but even in today’s Development Updates post there is uncertainty expressed about exactly when that will be.

1 Like

Looking forward to /e/os for the Motorola edge 30 neo! :grinning:

any ETA on that? when is a community Release planed for the Galaxy Tab S7 ? :slight_smile:

1 Like

JUHU, die Builds sind da :slight_smile:

Where? Give me some link! 🫨

Which device…?

(And I need to put 20 characters))

I wonder how I can find out how the build of tundra is progressing? Can I participate, help?

The A15 builds for devices which did not get it, would be taken up towards the end of the month. The final list would only be available 1-2 days before the release goes out. The builds are automated and made by the systems which pull the latest files from upstream and initiate the builds. There is no manual activity from the team. Except initiating the builds.

1 Like

https://images.ecloud.global/community/diting/
Hallo, leider kann ich die Zip-Datei nicht so entpacken, das ich nachher eine Boot, dtbo und vendor Datei habe. Kann es sein das die Zip Datei nicht korrekt gepackt ist.

Hello, unfortunately, I am unable to unzip the file in such a way that I end up with a boot, dtbo and vendor file. Could it be that the zip file is not packed correctly?

The e-recovery .zip file, characterised by prefix IMG-, is absent so the secondary images seem not available in this way.

e-Recovery.img is there but for the other secondary images please refer to [Walkthrough] Extract eRecovery and boot images using payload-dumper-go.

Thank you,
the path is too difficult for me at the moment. I will wait a few days in the hope that Recorvery.zip will appear as a normal download. Or will that not happen?

Just a guess, if devs become aware of the issue the next build may be packaged to match the install page but republishing of this “first” a15 build, with reported a15 build issues for new devices, might not happen.

That Walkthrough might seem complex, but once you get started with a download of payload-dumper-go is not so hard. Feel free to ask further on that thread, perhaps, if clarification is needed. I see the thread is closed, I guess it could be reopened on request.

Any news on the OnePlus Nord CE 3 Lite 5G schedule? Waiting forward to getting e on this device!

Hello /e/OS community,

I am the owner of a Motorola Moto G84 5G (codename “bangkk”), and I would like to offer it as a donation to the /e/OS project. Since there is only an unofficial build available for this model so far, I want to help accelerate the development and testing process to bring an official stable /e/OS version to users.

The Moto G84 is equipped with a Qualcomm Snapdragon 695, 12GB RAM, 256GB storage, and a 6.5-inch AMOLED display. I believe that having this device at disposal will assist developers in improving compatibility and fixing device-specific issues.

Please let me know how I can best arrange the donation and contribute to advancing /e/OS support for the Moto G84 (bangkk).

Thank you for your amazing work on this privacy-focused open-source OS!

Best regards,
Selune

1 Like

Hi @Selune welcome to the /e/ forum.

A generous offer. You do realise, though that a community build is available Install /e/OS on a Motorola moto g84 5G - “bangkk”.

Just FYI an official build, Different Build Types, is only generated for a device that Murena dot com intend to sell.


Hey
Thanks for the warm welcome!

I totally get that there’s already an unofficial /e/OS build for the Moto G84 (bangkk), and big respect to everyone making that happen. I’m just hoping to chip in by donating my phone, so the devs have direct access to hardware for testing, bugfixing, and maybe speeding up an official build.

I know official builds usually come only for devices Murena sells, which probably makes this tricky. But hey, every little helps, right? I’d love to see /e/OS fully supported on this phone, and if my Moto G84 can make that happen even just a bit faster, count me in!

Let me know what you think or how I can send it your way.

Cheers

I am just a regular user and not involved with development or the organisation. I guess your offer may be seen by someone able to take up the offer. I will just reiterate my use of community as a slightly misleading term here as opposed to unofficial.

No need to send the device @Selune . You can be a part of the testing team and help test out new builds on the device.

2 Likes

Thanks.
I just joined the Testing Telegram group.

Cheers

1 Like