foreground app name

[samer]

Hello
In split screen mode, when two applications are used to work on the screen, the name of the foreground application can only be known (magic text: name of the foreground application) and the other cannot be known even if it is being worked on (the name of the first application remains).
Is it possible to know the name of the other front-end application while we work on it?

 

[Endercraft]

For me on MIUI 14 when in split screen the foreground app is the app which you haven't interacted with (if I interact with app1 it shows app2 as foreground and if I interact with app2 it shows app1 as foreground).

 

[sampleuserhere]

Run the following command with Shell Script action dumpsys activity activities | grep "mResumedActivity"


or use TouchTask plugin to grab "application" window type with Read Screen action. the app names are stored in separate output called app name.

I remember I had pointed this one out somewhere in the beta feedback thread, the dev haven't mentioned this particular case either iirc.

 

[samer]

For me on MIUI 14 when in split screen the foreground app is the app which you haven't interacted with (if I interact with app1 it shows app2 as foreground and if I interact with app2 it shows app1 as foreground).

That is right .
when using MacroDroid or TouchTask, the foreground name appears reversed.

When using Android 7, only one application name appears.

 

[samer]

Run the following command with Shell Script action dumpsys activity activities | grep "mResumedActivity"

This requires root access.

 

[samer]

or use TouchTask plugin to grab "application" window type with Read Screen action. the app names are stored in separate output called app name.

Yes, it displays the names of the two applications together, which is useful.
But it (TouchTask) requires a long period of time to analyze this (it may take up to 2 seconds).

 

[Endercraft]

This requires root access.

It does not..

 

[sampleuserhere]

This requires root access.

We have to grant "android.permission.DUMP" for MD via ADB first before executing dumpsys.

Don't forget to toggle the non-rooted option in the action.