I am interested in using Android for the platform based E-Ink . I know that it was demonstrated once by MOTO, but I'm interested in using it for a commercial-class product, and not just a technological demonstration. I have a question about the ability to change the platform to cope with the specific display effect caused by E-Ink . I ask this question from the system architect and I have no previous experience with Android.
E-ink has several characteristics that are very different from conventional LCD displays:
- display update time (50-700 ms)
- power consumption is required to change the display (no support)
- Display lifetime is determined by the number of display updates!
- trade-offs can be made between quality, performance and display lifetime.
- Grayscale versions available.
The great thing: there is no power to save information on the display, and they can be read in bright sunlight without backlighting. Also, the display can be literally as thin as paper ...
This means that the platform software must have some degree of control over the number of display updates and the type of updates displayed in order to get maximum performance. Otherwise, an application that does not know the characteristics of the display can quickly drain the battery or, even worse, shorten the life of the display to several months, not years. Conceptually, I would be interested in replacing the display driver, but I'm not sure if this part is open. I know that it’s difficult to get information about Qualcomm chipsets ....
My question is: can this be done? Can I change the Android platform to support a very different display effect? Any pointers to the Android roadmap?
, Android , , ( ).
!