Does launching a new activity destroy my networking Service/AsyncTasks?

55 Views Asked by A.Xu At 03 April 2025 at 11:53

I am tinkering and building on Google's own WifiDirect code (https://android.googlesource.com/platform/development/+/master/samples/WiFiDirectDemo/src/com/example/android/wifidirect). I am passing a boolean, and displaying this boolean in a new activity once passed.

I've managed to make a connection, which causes the new activity to be launched, but nothing gets passed.

The demo contains both FileServerAsyncTask (for the GroupOwner), and FileTransferService(client). A few questions:
- A. As a groupOwner/Server, when FileServerAsyncTask gets executed, does it stay active forever?
- B. How would a UI ”know” when it has successfully received something, and should update accordingly? FileServerAsyncTask possesses a OnPostExecute() section – but how should I update the host activity?
- C. Where should I call FileServerAsyncTask? As soon as a contentView is loaded, as its done in the demo? Would it work if tied to a button?
As mentioned before, as soon as I make a connection, I start a new activity, with its own UI. This in itself is probably dumb.
- A. Is this bad practice? Will it interfere with the networking code within WifiDirectActivity & its two fragments. (As it currently doesnt seem to work properly)
- B. Will WifiDirectActivity be destroyed then? Since a new activity is running
- C. If this is bad practice, and I should consider using a new fragment, will replacing the two previous fragments somehow affect functionality as well?