View Single Post
Old 12-08-2015, 09:53 PM   #301
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by geertm View Post
Android started using MTP in 2011. Since then ADE 2.x, 3.x and 4.x were released by Abobe. Surely MTP support could have been added by now?
And still, no ereader used an Android that used MTP.
Which is basically because B&N didn't update the Nook.

When I said "no device", I didn't secretly mean "no Android OS". I meant ereaders.


Why add support for something that doesn't exist?
And isn't assumed to someday exist? -- At least, wait until it exists before devoting resources to supporting it.

Quote:
Looking at B&N's website and software do you really want them to write their own custom firmware
Now, I was wondering about that myself, but I eventually decided it is better for B&N to lay all their cards down at once. Rather than baiting us with illusions of competency in their hardware and proof of inadequacy in their website.
eschwartz is offline   Reply With Quote