Efforts and knowledge required to help add new devices

I’m wondering getting a Samsung Galaxy Tab or Lenovo Tab of the newer 2024 models. But I see /e/ OS support is completely lacking. And I honestly don’t want any Google infected Android running on my devices.

I’m not unfamiliar with hardware flashing and firmware building (have done that a while back with self-built OpenWRT on routers) and I have some very basic understanding of how the ARM boot process and the flash memory “segmentation” is working. I’ve also been doing Linux setups - including lots of compiling, development and debugging - including some low system-level like kernel and glibc. I don’t consider myself a complete newbie. I have also flashed several mobile phones in the past with LineageOS and /e/ OS and debugged failed flashing and such things. I still haven’t manage to brick or attempted to unbrick any devices, though.

So I wonder what is the base requirements to actually start building the /e/OS images and what is needed to know and understand to add support for a new device? How much effort would be required (days, weeks, months?) If I dive into this, I will contribute back to the /e/ foundation’s work so more users can get a functional device. But I need to get an idea of how difficult it is and how much time I need to expect putting into such an effort. Unfortunately, I don’t have unlimited time available - but I’d be willing to set aside some time to make it happen.

Hi @danzox, great intention !

It is a user forum here, I think best is to ask on xda forum where developpers are.
To build, you need a device where bootloader can be unlocked, a kernel repo, a device tree repo, and a vendor files repo (could be “The Muppets”).