I can't make any judgment whether systemd would natively support all of this glue logic without knowing the specifics of the logic in question. Further, the maj

I can't make any judgment whether systemd would natively support all of this glue logic without knowing the specifics of the logic in question. Further, the major modifications that would need to be made for an AOSP systemd might invalidate some of them. It's not just adding some unit file options for properties. You have to build ordering, synchronization and whole-scale system integration around it. Besides all other features and minutiae of AOSP. I would think the Android init is intentionally limited, reflecting its use for configure-once embedded devices? It's not a sysadmin's tool by any means. You see fragmentation, I see multiple approaches. Imagine a world where everyone votes for the same one-world government political party. Is reusing a fair chunk of the init system even that major an aspect of developing these devices? It certainly might be with systemd because of how all-encompassing it is, but in principle it shouldn't be.