Yeah, I can see that with Android having lots of devices, it's not optimal, which is why I kinda hedged around it above. But I guess I'm still not convinced that BCD is necessary for normal Android devices.
The nook is technically an Android device, yes, but it's a dedicated ebook reader, and its OS is pretty heavily modified, so as you mention, it does require special consideration. But the vast majority of Android devices don't. You already handle the nook with a custom driver, and not with the Android driver, so you've noticed that as well.
I just don't see that any device which will be handled by this Android driver is going to need any special considerations that might be dependent on BCD. It's a driver for generic Android devices, none of which are dedicated ebook devices with their own special anything, in relation to reading ebooks.
In other words, if it's a Motorola Droid (determined by vendor and product id), it's not gonna matter what custom Android build someone runs on it, it's still gonna interface along the parameters of this driver. Same goes for all other normal Android devices.
|