title: Google Drive Custom Thumbnail for Standard MIME Type
body: <p>I have yet another pesky question for people who understand how Google Drive SDK works. On Android platform, I am creating my own custom thumbnails for JPEG image files ( thumbnail is a reduced JPG of the most important detail of the parent image ), The size is a bit non-standard - 384 x 128px, but well within limits stated in the <a href="https://developers.google.com/drive/file" rel="nofollow">documentation</a>. So, the code goes like this:</p>
  
  <pre><code>// thumbnail 
  String myThumb = "test.tnl";
  Thumbnail tn = new Thumbnail();
  tn.setMimeType("image/jpeg");
  tn.setImage(Base64.encodeBase64String(myThumb.getBytes()));
   // define meta-data
  File body = new File();
  body.setTitle("test.jpg");
  body.setDescription("bla bla");        
  body.setMimeType("image/jpeg");
  body.setThumbnail(tn);
  File gooFl  = drvSvc.files()
    .insert(body, new FileContent("image/jpeg", new java.io.File(test.jpg)))
    .execute();
  </code></pre>
  
  <p>and executes flawlessly (there are more 'body' elements I don't list here) and everything works like a charm. But when I download the image, my thumbnail is gone, replaced by standard Google thumbnail - s220 type.</p>
  
  <p>I did notice the documentation statement:</p>
  
  <blockquote>
    <p>As with indexable text, Drive automatically generates thumbnails for many common file types. For shortcuts and other file types Drive can not render, you can provide a thumbnail image generated by your application. </p>
  </blockquote>
  
  <p>Reading it ambiguously, I was hoping that by supplying my own thumbnail to a known MIME type, I will keep Google Drive from generating its standard one, but it probably is not the case. So the question remains. Is there a solution to my problem?  Having custom thumbnails for standard "image/jpeg" MIME types? Or is there a work-around, perhaps another custom field I can stick some 10Kb of binary data in? I need the thumbnails in my Android viewer - another app.</p>
  
  <p>Thank you, sean</p>