i want debug a game on Samsung GT-N7100 Galaxy Note II (gpu is Mali 400).
Mali Graphics Debugger version is 1.2.2.5b0519ce.
i run the Installation Instructions
adb shell su -c mount -o remount /system
adb push libGLES_mgd.so /sdcard/
adb push mgddaemon /sdcard/
adb shell
# The following commands run on the target
su
cd /sdcard/
cp mgddaemon /system/bin/mgddaemon
chmod 777 /system/bin/mgddaemon
cp libGLES_mgd.so /system/lib/egl/libGLES_mgd.so
chmod 777 /system/lib/egl/libGLES_mgd.so
cp /system/lib/egl/egl.cfg /system/lib/egl/egl.cfg.bak
echo "0 0 mgd" > /system/lib/egl/egl.cfg
but i found every application will crash.
if i revert the egl.cfg file,
cp /system/lib/egl/egl.cfg.bak /system/lib/egl/egl.cfg
every thing will be ok.
do i need some other config?
Could anyone help me on this problem?
Thank you in advance!
Hi Chena,
What version of Android are you running?
Thanks,
Chris
android 4.3, thanks.
Hi chena,
Could you please let us know the original contents of the text file egl.cfg?
This will help us determine what could be the issue you are facing.
Many thanks,
Michael McGeagh
Hi chena, a couple of extra things to check...
Can you let us know the output of adb logcat | grep EGL when egl.cfg is pointing at mgd, and you try and open the android settings application? please clear the log with adb logcat -c first and make sure the application is completely killed. This will show us what the fail looks like in logcat.
Then can you do the following:
mount -o remount /system
cd /system/lib/egl
ln -s libGLES_mgd.so libEGL_mgd.so
ln -s libGLES_mgd.so libGLESv2_mgd.so
ln -s libGLES_mgd.so libGLESv1_CM_mgd.so
chmod 777 *
then please let us know the output of adb shell ls -l /system/lib/egl/, and then the output of adb logcat | grep EGL again following the same steps when you try and open settings? I just hit a similar problem on the S3 and it appears that frameworks/native/opengl/libs/EGL/Loader.cpp has been modified to ignore monolithic (libGLES_<tag>.so) drivers. This isn't a bug in MGD, but is a platform quirk introduced by the vendor that you can easily work around by adding the symlinks. With any luck it's the same problem you're facing and that will fix it for you.
EDIT: We'll add these extra steps in a future version of MGD.