May not be able to satisfy the use case of probing for peers every few seconds. We would need to pass the intent filters (i.e. register the broadcast receiver) to EVERY activity. This would also imply that it is impossible to do so with upper layer applications (other apps using NFD). For now, this will be commented out and replaced with a single, one-off discovery everytime the user visits the designated activity (e.g. the future NFD fragment/activity that will have the toggle button). This will be ConnectActivity.
Having both probe and discover tasks can greatly reduce streaming performance. At least for my devices, should try to pause them while doing the data transfer.
First point is resolved via starting a service to handle broadcast messages.
Second issue appears to be resolved by fixing a bug where the video app was using NDNController's shared locahost Face. Instead, apps should have their own faces.
May not be able to satisfy the use case of probing for peers every few seconds. We would need to pass the intent filters (i.e. register the broadcast receiver) to EVERY activity. This would also imply that it is impossible to do so with upper layer applications (other apps using NFD). For now, this will be commented out and replaced with a single, one-off discovery everytime the user visits the designated activity (e.g. the future NFD fragment/activity that will have the toggle button). This will be ConnectActivity.
Having both probe and discover tasks can greatly reduce streaming performance. At least for my devices, should try to pause them while doing the data transfer.
interest.setMustBeFresh(true) still does not work