Now I just wanna to test with Mali Graphics Debugger, But it seems some wrong happen to me because it shows "No trace data to display" in main window. My target device is Google Nexus 10 and get rooted and host system is Win7.
I did all steps follows "Mali Graphics Debugger v1.2.1 User Guide.pdf".
During my running the commands follows, it seems no special log out, I even can not know if i'm succeed or not from log.
Two lines log out after run mgddaemon: "waiting for an interceptor o connect..." , "waiting for a connection from the host on port 5002".
Then I set the target IP in "Debug->set target IP" to 127.0.0.1 and set the port to 5002. there is only on line log out in Console window: set IP to 127.0.0.1:5002.
Then I launch my game on target device(nexus 10).
After getting in game , I do "Debug->connect to target " or press button "connect to target and start tracing" to connect to target and a new window named "Capturing 127.0.0.1:5002" displayed with a tip "No trace data to display" shown. And one line log shown in console window :"Daemon is version :A006" and one line log shown in cmd.exe :"Host connected." (I noticed someone else have a log "a client connected" in forum but this log never displays in my process.).
Almost nothing else shown in MGD.
Could anyone figure out my problem?
My appreciate for your answer!
Thanks!
Commands attached:
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
adb forward tcp:5002 tcp:5002
mgddaemon
Hi elson,
Sounds like the host is connecting to the daemon but your application is not. Can you let me know what happens when you start the daemon, connect the host to it, and THEN run your app, making sure you first force kill it, or reboot your device? This is to make sure the process really is starting up and not resuming, which ensures the interceptor library is loaded.
Could you also attach the logcat from the application when following these steps?
Thanks,
Chris
Hi Chris:
Thanks for your fast replay.
I just reboot my device and also failed yet.
My steps is:
1. run adb forward tcp:5002 tcp:5002 command in cmd.exe and no log shown in anywhere.
2. run adb shell -> su -> mgddaemon command and logs in cmd.exe are:
Daemon is version :A006
waiting for an interceptor to connect...
waiting for a connection from the host on port 5002...
3. go to Mali Graphics Debugger and select Debug->Set target IP and set 127.0.0.1 to IP Address and 5002 to Port in the dialog pops up. Log "Set IP to 127.0.0.1:5002" shown in Console window. no log shown in cmd.exe window.
4. Run my game on target device .
5. select Debug->connect to target or press a button with tip "connect to target and start tracing" get the same result: a new tap named "Capturing 127.0.0.1:5002" shown in Main window and it displays "No trace data to display". and at the same time ,a log "Host connected." shown in cmd.exe . that's all , nothing else.
Actually I have a question about "5.2.1 Capturing a Live Trace" in "Mali Graphics Debugger v1.2.1 User Guide.pdf".
In "5.2.1" it shows "Select Debug->Set Target IP...and review the target connection details" (actually there is no details for me by "set target IP" except on line log "set IP address to 127.0.0.1:5002".)
Can you let me know if there is any output when you first connect the host to the target, before running your game, after first making sure that the app is force killed using either the task switcher or the settings app, or indeed a reboot? Also can you provide a logcat output showing when you open the game?
As for the question about set target IP, because you see the "Host connected" output from the daemon this is all working fine.
P.S. What version of android is the Nexus 10 running? If it's 4.4.x can you upgrade to MGD 1.2.2, available at Mali Graphics Debugger « Mali Developer Center as this adds support for the new dalvik behavior in KitKat, which might be causing you trouble.
oops , the Android version of my Nexus 10 is 4.2.2 !
But I can't get MGD 1.2.2 by Mali Graphics Debugger « Mali Developer Center , because I just download from this address and get a MGD with version 1.2.1 which full name is Mali_Graphics_debugger_v1.2.1.97319195_Windows_x64.exe. Are you really sure there is a MGD v1.2.2 ? If so, then I will test with MGD v1.2.2 .
Hmm, when I go there its 1.2.2.5b0519ce, which was uploaded on 20th Feb! In any case it really only adds KitKat support so not essential in your case.
Can you provide a logcat from when you start your application? And again please connect the host to the target before running it, to ensure a complete trace.
Hi Chris , thanks for your useful information ,I get the latest version of MGD and fix my problem , Now I can capture frame successful.
Thanks again!
The first part of section 5.2.1 Capturing a Live Trace asks to check if the info provided in Debug->Set Target IP... is correct: IP Address should be set to the valid IP address of the selected target device and Port should be set to 5002.
If the info is invalid you should change it before trying to capture the trace. There are no other details to be checked.
Hope that helps,
Jacek
Hi ,kubacki, I have got it run successful and found there is no much log just as you mentioned.
Thanks for your replay!