title: Android with E-Ink display
body: <p>I'm interested in using Android for a <a href="http://www.eink.com/technology/howitworks.html" rel="noreferrer">E-Ink</a>
   based platform. I know it has been <a href="http://vimeo.com/3162590" rel="noreferrer">demonstrated</a> once by MOTO, but I'm interested in using it for a commercial grade product and not 'just' a technology demo.  I have got a question on the ability to change the platform to cope with specific display effect caused by E-Ink. I'm asking this question from the role of system architect and have no prior experience with Android.</p>
  
  <p>E-ink has several characteristics which are very different than the common LCD displays:</p>
  
  <ul>
  <li>time to update display (50-700ms)</li>
  <li>it costs power to <em>change</em> the display (none to maintain)</li>
  <li>display life time is determined by number of display updates!</li>
  <li>tradeoffs can be made between quality, performance and display lifetime</li>
  <li>grayscale versions available</li>
  </ul>
  
  <p>The great thing: it costs no power to retain display information and they can be read in bright sunlight with no backlight. Also the display can be literally as thin as paper...</p>
  
  <p>This means that the platform software needs to have a degree of control over the number of display updates and the type of display updates to get the best performance. Otherwise, an application which is unaware of the display characteristics could quickly drain the battery, or worse, shorten display life time to months instead of years. Conceptually I'd be interested in replacing a display driver, but I'm not sure if this part is open. I know it is hard to get info on the Qualcomm chipsets.... </p>
  
  <p>My question: can this be done? Can the Android platform be modified to support a drastically different display effect? Any pointers to an android roadmap?</p>
  
  <p>The reason I find Android interesting for this application is because there is a significant overlap in functionality (from cell phone to browser).</p>
  
  <p>Thanks!</p>