Google has selected a new model for the Android User Interface: The Activity, which is tied to User-Interface.
Now, when someone (like me) intends to implement a UI with some networking threads and processing, the two options are:
1) Running the Networking as a Service
2) Spawaning threads from the UI activity.
The two options are not that bad, it is just that using a Service model is an overkill for most applications, and having one activity which manages everything – UI as well as tasks seems like the easier solution.
When I started, I assumed an Activity can be anything, but as clearly stated:
(an activity that is not visible to the user and has been paused) is no longer critical, so the system may safely kill its process to reclaim memory for other foreground or visible processes
Sorry for not posting code, but this project is not an Open Source.