I've been reading bits on this forum for ages, mainly for research purposes, and I've seen a few anti-android posts. I've avoided posting in the past but now I'm signing up to find out just what is so wrong with it.
Windows projects, and some work in web front-ends. I've worked on various mobile platforms, though not Android, yet. I am not associated with Google or the Open Handset Alliance and currently have no published Android work. I do have an Android based phone and have spent a lot of time playing with the SDK and researching it as a potential platform for a Car entertainment system. I haven't decided whether to use it yet.
The Android framework/API provides a lot of facilities that are highly relevant to in car entertainment systems. Media playback, touch interfacing, graphics (2D and 3D), bluetooth, storage, image display and manipulation, GPS interfacing... the list goes on. It also provides a relatively quick and simple platform to develop applications on, and is very focussed on touch based UI design.
So, assuming someone takes the trouble to design an appropriate user interface that runs on Android for use in a vehicle, what exactly makes it so unsuitable for use in this way?
As for giving nothing back to FOSS.... you what!? It is an open project in itself, the source is available for download, and changes to the kernel have been provided even if they are currently excluded from the trunk. Grab the source and have a look, you may surprise yourself and find something useful!
No doubt there are people out there that think Android is great for an in-car system for all the wrong reasons; but there are a lot of good reasons for considering it.
So, as software developers, what are the practical reasons that make Android so unsuitable for ICE?