You can ask it yourself to the surface flinger. There’s nothing wrong in Android and its low level tools, they perfectly know that there’s more than one screen. If the device is closed and you are using the external display, your tool will probably capture the image of the internal screen: I do realize that is not a specific bit flag but a combination of several bit flags for convenience, so it is easy enough to provide the constant value and cast it to WindowManagerFlags, but I would expect, also for convenience, for these convenience constants to be available in the. On a dual screen device, there’s a 50% chance that they will capture the image of the wrong screen…Īs an example, for a device like the Samsung Z Fold 2, the default/primary screen is the beautiful foldable screen inside the device. These tools capture the screenshot of the default screen. If you use a tool to capture a screenshot on a dual screen device, you will soon discover that (probably) it assumes that there’s only a screen. Testing new code, I may encounter some “strange behavior” and capture a screenshot is usually a good way to convey my point to someone else. WindowManagerLayoutParams layoutParams IWindowManager windowManager. I can get the following to work in java but cant figure out the corresponding C code in Xamarin: windowManager (WindowManager) getSystemService(WINDOWSERVICE) WaitingImage new ImageView(this) tImageResource(R.drawable.bgmain) WindowManager.LayoutParams params new WindowManager. I do some work around Jetpack WindowManagerĪnd I talk to developers on how to support this new form factors. What is keeping me busy lately are dual screen and foldable devices. var rotation var matrix new Matrix() var viewRect new RectF(0, 0, viewWidth, viewHeight) var bufferRect new.

Xamarin windowmanager