I downloaded mali graphics debugger v2.0 for win7 32bit, but i can't capture any data after setting up host and target following the MGD user guide, what should i do?

Hi, Chris! I have tried new Mali Graphics Debugger v2.0.1 and has the same issue (Samsung Galaxy Note (Mali-400) + Android 4.2.2 (Cyanogenmod)).

I've also tried to make symlink from /system/lib/egl to /vendor/lib/egl. The problem is /system/lib/egl doesn't contain any libGLES_mali.so but contains libEGL_mali.so, libGLES_android.so, libGLESv1_CM_mali.so and libGLESv2_mali.so. I've tried to map all available *.so to /vendor/lib/egl/libGLES_mali.so, but the result the same (black screen and huge log with functions which are not discovered). Best result was achieved with libGLES_android.so (corrupted picture and only one function not found). Is there any possibilities to make it work for my configuration.

Hi, Chris! I have tried new Mali Graphics Debugger v2.0.1 and has the same issue (Samsung Galaxy Note (Mali-400) + Android 4.2.2 (Cyanogenmod)).

I've also tried to make symlink from /system/lib/egl to /vendor/lib/egl. The problem is /system/lib/egl doesn't contain any libGLES_mali.so but contains libEGL_mali.so, libGLES_android.so, libGLESv1_CM_mali.so and libGLESv2_mali.so. I've tried to map all available *.so to /vendor/lib/egl/libGLES_mali.so, but the result the same (black screen and huge log with functions which are not discovered). Best result was achieved with libGLES_android.so (corrupted picture and only one function not found). Is there any possibilities to make it work for my configuration.

I was going to suggest making 3 separate symlinks, from /vendor/lib/egl to /system/lib/egl, but due to the above bug there's no way to support fragmented builds at present (EGL will only look for /vendor/lib/egl/libGLES_mali.so, and symlinking that to libEGL.so would break GLESv1 and v2). There is a fix incoming though which will resolve this, and it should "just work" by following the install guide.