My unsupported devices todo list and non-successful devices overview list

Pardon, typo on my part. I have updated to the official /e/OS-R (Red Velvet Cake).

My question refers to a possible /e/OS-T (Tiramisu)

Hi @ronnz98
I see you are now also building ROMs based on /e/OS 7 Nougart (LOS 14.1) and 9-Pie (LOS 16.0). Can you please try to build a ROM for the Samsung Galaxy S5 Plus (kccat6) SM-G901F?

1 Like

Samsung Galaxy S5 Plus ready for testing:

e-0.23-p-20240428-UNOFFICIAL-kccat6.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-0.23-p-20240428-UNOFFICIAL-kccat6.zip/download

1 Like

@ronnz98 You are simply the best!

My first installation on SM-G903F was successful.

The system can be set up, but - there are some inconsistencies that I will try to reprod and verify and share my experiences shortly.

Apropos inconsistencies

I was able to reproduce the glitches mentioned above and eventually work around them, so your /e/ROM now works fine.

@ronnz98, if you open your own thread something like

UNOFFICIAL BUILD] Samsung Galaxy S5 Plus (kccat6) for /e/OS-Pie

I will share my experiences.

Unihertz Atom L

Hi @ronnz98, fancy a new device manufacturer? I could test your ROM …

1 Like

https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL/blob/master/docs/HOW-TO-BUILD.md

I would need the vendor files first…

vendor files searched for a long time, but found nothing useful :unamused:


[UNOFFICIAL] TWRP 3.7.0_11-0 for Unihertz Atom L

@forart.it, can you please help?

Did you notice the contents of https://github.com/ADeadTrousers/android_device_Unihertz_Atom_LXL/blob/master/docs/HOW-TO-EXTRACT_SEPOLICY.md et al including scripts and links to Unihertz ROMs.

1 Like

Well, as always, I can only recommend you to search for needed resources (= aka device tree, kernel sources, vendor blobs) at GitHub.

Here’s my quick method to probe it:
https://github.com/search?q=<device_brand>+<device_codename>+device&type=repositories&s=updated
https://github.com/search?q=<device_brand>+<device_codename>+kernel&type=repositories&s=updated
https://github.com/search?q=<device_brand>+<device_codename>+vendor&type=repositories&s=updated

Then, of course, you have to seek for ones that fit builder needs…

Hope that helps.

Hi @ronnz98,
one more time, Thank you for all your /e/OS builds !

can you please give a try to upgrade our OS for the legendary Samsung Galaxy s4 international LTE ?
optimized LineageOS 20.0 seems to be available…

https://github.com/JDCTeam
.
https://github.com/JDCTeam/manifests/blob/opt-cm-20.0/default.xml
.
https://github.com/JDCTeam/android_device_samsung_jflte
.
https://github.com/JDCTeam/android_kernel_samsung_jf

I still not giving up building for the Samsung A21s, but get this error:

clang-r353983c/bin/llvm-ar: error: unknown option P.

e-2.0-r-20240519-UNOFFICIAL-jflte.zip
https://sourceforge.net/projects/eosbuildsronnz98/files/SamsungSmartphones/e-2.0-r-20240519-UNOFFICIAL-jflte.zip/download

For R I could build, for S and Q not… please try if it works…

I will be abble to test tomorow at the end of the day.
Even if official DEV build is already e-2.0-r.

But my question was about the JDCTeam called
“opt-cm-20.0” branch…

ah ok… tried now for LOS20 brunch but got same kernel errors as for LOS19

Signature verification failed → install anyway ? → YES

it boots and seems working !

looks very complicate

The manifest is not for device, its for a certain lineage version I suppose

Can anyone help, I tried for Samsung J8 j8y18lte again but go this error. I already have minimal apps builds and strangely the max. image size seems to be sufficient (>3GB)

Out of space? Out of inodes? The tree size of /home/ronnz/eOS_R/out/soong/.temp/tmp9mRygj is 1660874752 bytes (1583 MB), with reserved space of 0 bytes (0 MB).
The max image size for filesystem files is 3397386240 bytes (3240 MB), out of a total partition size of 3397386240 bytes (3240 MB).
11:58:37 ninja failed with: exit status 1