Synology, je réevaluerait, a priori désormais on est obligé d'acheter des disques dur syno.

Merci crcr et turold pour ces éléments très intéressants. Mais pourquoi a-t-on besoin de faire évoluer ces drivers et composants logiciels d'une version Android à l'autre? Ne peut-on pas conserver les anciens drivers tout simplement?

Leon.

Drivers are modules files like xxx.ko
Modules are saved at /vendor/lib/modules.
If you mean you want to use modules from kernel 4.4 with kernel 5.0 that doesn't work. Every kernel comes with its modules, its opensource, isn't windows. You need to recompile the modules or find them compiled for the new kernel.

To expand: not only is the driver a different for every version, it is often different for specific hardware (not just chip or chipset) and of course for every CPU family. A module/driver for the same chipset on an android phone running on a Snapdragon series will be totally different from that driving the SAME CHIPSET on an AMD-64 CPU, which will be different from the one on an AARCH64 CPU. On two cell phones running the same version of Android with the same chipset devices, but a different configuration, the drivers may have to be different. There are a LOT of variables and potential incompatibilities involved.

IF they were all the same, then there could only be a single Android image that would work on every cell phone made to run Android in the world. It would only have to detect and load the right drivers on install. They are NOT all the same, and that does not work.

(Actually we may be able to make something ALMOST like that work, once we are all running Linux phones. At least for certain kinds of devices.)

Great fun, yes?

Also a lot of smartphone chip manufacturers never even try to get their driver into mainline linux, they're fine just providing a blob to a vendor that only works with their one specific kernel....