Problem with MediaProjection and permission dialog

Thank you for sharing this information!!!

I was very excited to learn these things because I have been trying to get a non-null MediaProjection and I wasn't having any success.  I was about to give up when I found your post.  This fills me with hope.

I am lacking in my Android and Java knowledge with primarily a Windows (C++/C#) background; that combined with a multi-minute inner dev loop for just testing out any of these Android specific changes to my project means my process has been a very slow iterative one.  I am determined to get this to work, and expect to be working on it for at least a few more days if not a week as I figure out all of the additional pieces.

There are a few visible hurdles that I need to get past next, which I believe you have already solved.  

First, I'm dumbfounded about how to even import ComponentActivity.  "import androidx.activity.ComponentActivity;" gives me the package not found error.  And a little searching seems to indicate that this is because of the "androidx" part, and that I need enable this for my project using UPL.  For which I found this article:

How to force the Unreal Engine Android project to use AndroidX? | by Taras Leskiv | nineva | Medium

https://medium.com/nineva/how-to-force-the-unreal-engine-android-project-to-use-androidx-f7060abd56ac

But turns out I have already done everything in that article, because I'm using a solution for calling java that already does that:

Sovahero/PluginMobileNativeCode (github.com)

https://github.com/Sovahero/PluginMobileNativeCode

I'm putting my java files in with the plugin's java to simplify my tests.  Still can't figure out I'm still getting this error.

But once I figure that out, the next problem is how to get my android manifest to have the activity changes you showed above.  Since the manifest is generated each time, simply changing the one in the intermediate folder does not look like a path forward.  I believe I need to figure out how to use my own UPL for adding that.  

Thanks for pointing that out. 🙂

I'm still working to get to the point where an exception is the only problem I have.  The problem I am having now is the app process crashes, or hangs and is then closed automatically?  UE4 Launcher logs don't have a callstack; and my logging indicates that the call to startActivity didn't cause an exception.  I don't know this space well and so I have just been researching and trying various things to try and make progress on it; maybe while the update did break it, there is still a way to get it to work given the right setup.  

From other attempts to capture audio, I tried MediaRecorder (only works for capturing Mic I now believe) and I can get a permissions dialog prompt to appear using Activity's requestPermissions.  I would have thought that they would be using similar mechanisms and so if that one still works perhaps there is still a way.

The exception message I get when I do this call:

resultLauncher.launch(mediaProjectionManager.createScreenCaptureIntent());

is:

"unable to find explicit activity class com.android.systemui/com.android.systemui.media.MediaProjectionPermissionActivity"

Is that the same exception you are getting vit?

eusebium, the way I found that got the ScreenCaptureActivity to be created was like this:

public static String start(Activity activity)
{
	try
	{
		Intent intent = new Intent(activity, ScreenCaptureActivity.class);
		intent.setAction("SCREEN_CAPTURE");
		activity.startActivity(intent);

		return "start: no exception";
	}
	catch (Exception e)
	{
		return "EXCEPTION: " + e.getMessage();
	}
}

 Please ignore my String return that I'm leveraging for logging.  The activity passed to this function is FJavaWrapper::GameActivityThis that the MobileNativeCode passes in with this call:

FString TestResult = AndroidUtils::CallJavaCode<FString>(
		"com/Plugins/MobileNativeCode/ScreenCaptureActivity",
		"start",
		"",
		true);

My activity in my manifest looks like this:

      <activity
          android:name="com.Plugins.MobileNativeCode.ScreenCaptureActivity"
          android:configChanges="density|keyboard|keyboardHidden|navigation|orientation|screenLayout|screenSize|uiMode"
          android:launchMode="singleTask"
          android:resizeableActivity="false"
          android:screenOrientation="landscape"
          android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen"
          android:noHistory="false" >
        <intent-filter>
          <action android:name="SCREEN_CAPTURE" />
          <category android:name="com.oculus.intent.category.VR" />
        </intent-filter>
        <meta-data android:name="com.samsung.android.vr.application.mode" android:value="vr_only"/>
      </activity>

I've been taking a few days of vacation this week; so my replies may be delayed.  The exception I mentioned is related to the more recent other thread that vit created.  Sounds like a bug may have been introduced.