[NiLuJe]

eInk and Android don't really mix, that's all. Doing it right requires total control, something that is impeded, by design, by a framework like Android, which is designed with pretty much the opposite mindset and goals.

As such, you get an extra layer (or two, or three...) of suckage in the middle killing latency in the vain hope of making most things "mostly" work, instead of the highly specialized and tailored workflow driving eInk properly requires.

(Many of the subtle driver issues I have with this very SoC on Kobo devices can be laid entirely at the feet of the OEM's Android hackery implemented at the display driver level).