android-service

I coded an IntentService where I send a command line. Is related to an activity where I'm trying to program a Console. The activity's purpose is to do a 'command prompt' where I can send and receive to/from the server. The Service's action is: COnnect to the server Send command line Get response Retrieve response to user The main problem is that every time I send a command line, the Service has to reconnect to the server. (Cause every time I'm starting the whole Service) How can I avoid this step? I would like to "keep alive" the service waiting for a command line to send, without the need of

Are there any drawbacks to using intents as a form of message passing between two apps that I control? I have two apks which will always exist on the device together. And, I'd like to use explicit intents to pass messages back and forth as opposed to creating and managing two separate services. Using explicit intents just seems like an easier to manage approach than services. Communication between applications can expose certain rich, but if you really need to do this way, you can only customizing permissions that your applications will have knowledge. Then you can use BroadcasrReceiver to

I have a service in Android that encapsulates a framework that has a start method. The service boils down to something like this, many things omitted: public class MyService extends Service { private IBinder thisBinder; public MyService(){ thisBinder = new LocalBinder(); } @Override public IBinder onBind(Intent intent) { return thisBinder; } public void start(Map<String, Object> options) { getDriverManager().start(options); } } I also have a bridging class that makes calls to the service: public class MyServiceBridge implements ServiceConnection { private boolean started = false; private