This question belongs on the 'android-platform' list. On Wed, Jan 4, 2012 at 4:47 PM, Abhishek Joshi <[email protected]> wrote: > Dear All, > > I am new to this forum and writing first time. We were debating > internally about deciding a OS for our chip. We were contemplating > between Android and custom embedded linux. Before we decide, I wanted > to get answers for following questions: > > • Customization of Android > o Is it possible to remove unwanted libraries and services, how thin > or light weight android can be It is possible, lightweight is something you'll have to decide for yoruself.
> o Customization of libraries e.g is it possible to modify enhance > WebKit to support OpenCV Well of course, this depends how much engineering effort you have behind you, however.. (It's probably not straightforward and immediate.) > • What kind of applications does Android's media framework, > StageFright, support Can't comment too much on that. > • Is there any support in Android for gesture based applications? If > yes, which framework is used for gesture based applications are > supported? > • What are the minimum processor requirements for Android? Guidelines for these sorts of system things are given at: http://source.android.com > • How much is JVM overhead? If you're considering porting Android to run on your system, it sounds like you've got a long way to go :-). Android doesn't run the JVM, it runs a custom vm called Dalvik. The VM perf is pretty good: even the interpreter is written to run fairly well (and lots of time is spent in system native code anyway), and if you use JIT you can go even better. The performance really isn't a big deal, but your usage needs may dictate otherwise (really I'd doubt that anything you would need would suffer too much from using the vm). > • Is android a feasible platform for set-top box platform? Perhaps, you should be aware that designing an Android device is a pretty big venture. You'll need a fair number of really well trained systems people who can hack at the kernel, system, and framework code to do what you want. Though chances are fairly good that your platform is already close to being supported already depending on your architecture. Even so, there's a lot of code there, to first understand, and also modify, the build process itself is fairly time consuming to understand (I don't). Whether or not to use Android really depends on knowledge of your application domain, how extensible (easy to write apps) you need your solution to be, etc.. Keep in mind that being able to *run* Android on <whatever you are making> is not the same thing as being Android compliant! This takes a lot more work! I mean, Android basically *is* Linux (depending on what you call Linux, it's a linux kernel with some stuff on top and minor changes, but it's far from being what you'd call 'GNU/Linux') with a bunch of framework, windowing, vm, etc.. code on top. All in all, not to be insulting, but I think you've got a lot more research to do before you make a serious decision as to which way to go (I would suspect that no company would make a big product decision based on an email response from some random person on a mailing list). So have those engineers of yours do some digging and find out what might work for you :-) Also, like I said initially, these questions *really* belong on the android-platform list, most certainly not android-developers. (which is for people writing apps.) Kris -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
