tokbox | Tokbox Server SDK for Google 's Go language | Bot library

As far as I understood, libc++ is a new implementation of the C++ standard library that is coming from LLVM/clang. You then need to add meta-clang layer to your bblayers.conf (after having it cloned obviously) and add libcxx to the RDEPENDS of your recipe.

c.f.: https://layers.openembedded.org/layerindex/recipe/39646/

However, not sure if it wouldn't be better anyway to recompile Tokbox if you have the sources.

I had also faced the same issue and had mailed to tokbox support. This was their response:

The way our screen capture code works is that it recursively traverses the view hierarchy and copies those images to a buffer and then send that buffer over on the webrtc data pipe. Hence once the app is pushed to the background, we could not traverse the view hierarchy and copy the image, so screen sharing works until we are in the application (Android or iOS native app). If you want to share the screen view of Opentok app only, it will work but outside the app won't work. It's just to take care of the privacy and security aspects of the mobile app users.

So according to them you cannot share screen outside the application. It will only work when app is in foreground.

After constantly asking the tokbox support team I got the following reply from them:

To screenshare the content outside of your application on Android and iOS can be achieved. For Android, you need to use the Media Projection API together with Vonage/Tokbox Custom Capturer. For iOS, you need to use the iOS ReplayKit together with Vonage/Tokbox Custom Capturer. Basically, the implementation is to get a frame from Media Project API or Replaykit and then pass it via a custom capturer.

Following their response, I found Accelerator Core Android repo which showed how to integrate Media Projection API with tokbox. More specifically these two files: ScreenSharingFragment.java and ScreenSharingCapturer.java

Using these two files I am now able to share screen outside my application.

Note: Apps that target Android 9 (API level 28) or higher should use Foreground services or else your app will crash due to security reasons.

To stop screen sharing will need to stop the publisher from streaming. To do that you can call:

[OTSession unpublish:error:]

More info is available on the Video API guides

For your case, where you are adding screen sharing to an existing call, you will need to create an additional publisher for the screen sharing rather than editing the existing one. To use the existing publisher it will require the publisher to be reinitialised to switch between publishing a camera feed vs a screen which will stop publishing audio too.

In addition to creating a new publisher, you need to create a new subscriber for the other user, you can do that in the subscriberDidConnect delegate function on the OTSubscriberDelegate.

Additionally, you will need to handle the destruction of both the new publisher and subscriber. This will be done in the delegate functions are you using already on the OTSessionDelegate and OTPublisherDelegate.

I have created a demo app which demonstrates this behaviour.

If you are a beginner then i recommend you disable minifyEnabled in you build.gradle. basically the proguard obfuscates the code and you might not be escaping your model files in the proguard rules

Manik here from the Vonage Client SDK team.

Although this feature does not exist in the Video Client SDK just yet, you can accomplish the sharing of audio with screen by creating a publisher like so:

Sorry, I don't like to give an answer to my own question but I want to do it because it will help other developers.

This line I need to add in after session connected.

html

I need see more of you concrete case code but i hope this can help you.

You need to send the audioSource. Example:

TokBox support confirmed that is is a valid way to go and that the Session Monitoring events are reliable enough. So we will go ahead with the idea of using the StreamDestroyed events.

Unfortunately, this is not equivalent to the subscribed minutes. Calculating those should be possible using the events, but could become quite complex.