If you have a daemon, you should probably be able to run it as is on Android, provided it is started with the appropriate permissions. (Started by init if real crucial to the platform, or otherwise on demand by something else if needed).
Then, you should provide a Java API that would be implemented through JNI calls that would invoke the native client interface to your daemon (most probably a library). It really depends on how your daemon communicate with its clients though, you may be able to communicate directly from Java through a Unix socket, for example. Can you share a bit more details about your project ? On Mon, Feb 16, 2009 at 9:22 AM, Ashutosh Agrawal <ashuto...@lge.com> wrote: > Hi, > > > > Though I have gone through the available documentation and the source code, > I am somewhat ambiguous about the approach to follow for integrating my > external library (daemon/service which is written in C) in Android > architecture. I think the following main actions needs to be done > > > > 1. Port and Make the service as an external library with Android tool > chain > 2. Write an application framework for connecting application world to > my external library i.e. providing Java API interface and mapping the > corresponding C APIs by JNI > 3. Write a Java application according to the Android analogy and use my > application framework (2). > > > > I would appreciate if somebody from Android team can correct my > understanding on this, and would provide me the piece of advice. > > > > > > Thanks in advance, > > Ashutosh > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
