I have read in the manual: Tutorial - Using CallSubDelayed to interact between activities and services
CallSubDelayed makes it much simpler. It allows you to call a sub in a different service or activity. If the target module is not active, then it will be started automatically. When the target module is ready, the sub will be called.
CallSubDelayed doesn't immediately call the target sub. It sends a message to the message queue. The internal framework manages this message and passes it to the target module when it is ready.
----------
But my experments showed, that CallSubDelayed called from service doesn't force the activity, which is not active, to be started automatically. Is it correct behavior ?
CallSubDelayed makes it much simpler. It allows you to call a sub in a different service or activity. If the target module is not active, then it will be started automatically. When the target module is ready, the sub will be called.
CallSubDelayed doesn't immediately call the target sub. It sends a message to the message queue. The internal framework manages this message and passes it to the target module when it is ready.
----------
But my experments showed, that CallSubDelayed called from service doesn't force the activity, which is not active, to be started automatically. Is it correct behavior ?