there is a black area when screen captured, what's going on?

[weizai]

as the following picture:

this is my option LD_LIBRARY_PATH=/data/local/tmp /data/local/tmp/minicap -P 2160x3840@2160x3840/0 -s > /mnt/sdcard/screenshot.jpg

[sorccu]

It can mean that you set the resolution slightly wrong.

What device is that anyway? Can you do adb devices -l and paste the line here? Feel free to remove the serial number if you like, though.

[weizai]

oh sorry, my option is: LD_LIBRARY_PATH=/data/local/tmp /data/local/tmp/minicap -P 3840x2160@3840x2160/0 -Q 100 -s > /mnt/sdcard/screenshot.jpg

and this is adb devices -l info: 192.168.10.133:5555 device product:rk3288 model:rk3288 device:rk3288

[rahul0698]

I am trying to capture the screenshot with Samsung galaxy GT_I9082. The image that I am getting is the black area. With another device, i am getting a good result. what can be the problem?

ABI- ameabi-v7a, sdk-17 screen resolution 480x800 and this is ADB

devices -l info : device product:baffinxx model:GT_I9082 device:baffin

[sorccu]

Is the physical screen on?

[rahul0698]

yaa it is on

[rahul0698]

I am getting this on running this command- adb shell LD_LIBRARY_PATH=/data/local/tmp /data/local/tmp/minicap -P 480x800@480x800/0 PID: 14077 INFO: Using projection 480x800@480x800/0 INFO: (external/MY_minicap/src/minicap_17.cpp:239) Creating SurfaceComposerClient INFO: (external/MY_minicap/src/minicap_17.cpp:242) Performing SurfaceComposerClient init check INFO: (external/MY_minicap/src/minicap_17.cpp:249) Creating virtual display INFO: (external/MY_minicap/src/minicap_17.cpp:255) Creating CPU consumer INFO: (external/MY_minicap/src/minicap_17.cpp:261) Creating buffer queue INFO: (external/MY_minicap/src/minicap_17.cpp:267) Creating frame waiter INFO: (external/MY_minicap/src/minicap_17.cpp:271) Publishing virtual display INFO: (jni/minicap/JpgEncoder.cpp:64) Allocating 1154052 bytes for JPG encoder INFO: (jni/minicap/minicap.cpp:448) New client connection vc_dnfo = open("/dev/vc-dnfo", O_RDONLY, 0): Invalid argument ioctl_failed = ioctl(vc_dnfo, VC_DNFO_IOC_DISPLAY_INFO, &vc_dnfo_info): Invalid argument vc_dnfo = open("/dev/vc-dnfo", O_RDONLY, 0): Invalid argument ioctl_failed = ioctl(vc_dnfo, VC_DNFO_IOC_DISPLAY_INFO, &vc_dnfo_info): Invalid argument vc_dnfo = open("/dev/vc-dnfo", O_RDONLY, 0): Invalid argument ioctl_failed = ioctl(vc_dnfo, VC_DNFO_IOC_DISPLAY_INFO, &vc_dnfo_info): Invalid argument vc_dnfo = open("/dev/vc-dnfo", O_RDONLY, 0): Invalid argument ioctl_failed = ioctl(vc_dnfo, VC_DNFO_IOC_DISPLAY_INFO, &vc_dnfo_info): Invalid argument

[dkw72n]

Two different issues here. I have seen the Samsung one before.

[rahul0698]

And exactly what are those issues. Can you please let me know how to fix those issues? And if there are more than one device how to get the particular device to respond to minicap.

[sorccu]

It's not so easy. Please consider asking your company to donate one of those devices to the project so that we can check for ourselves. Otherwise it's unlikely that the issue can be solved.

On Mon, Apr 17, 2017 at 22:19 RAHUL RAJ CHAKRAVORTY < [email protected]> wrote:

And exactly what are those issues. Can you please let me know how to fix those issues? And if there are more than one device how to get the particular device to respond to minicap.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/openstf/minicap/issues/60#issuecomment-294484146, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB-_dntA6beMwmdlxCrtSBT8VzJxuUVks5rw2bhgaJpZM4Ma4cI .

[nosiyBUGS]

I knew the reason。some apps background prevent this capture，please clear the background and try again。