Mali Graphics Debugger: Not getting trace data in GUI

Hello,

I've been working on this all day and I can't quite get the last mile done.

I've followed the Help documentation to a T, as well as, looked around this site for relevant info.  Specifically, Re: Re: Mali Graphics Debugger : libGLES_mgd.so makes crash application  Though, no applications are crashing in my case, I'm just not getting trace data.  Similarly, I'm working on a Samsung Note 8.0 GT-N5110 with a Mali-400 GPU.  I think, for some reason that mgddaemon isn't able to send traces, and I'm trying to track down why.

I'll answer the first few questions in the above post by default.

• Firstly /vendor/lib/egl doesn't exist
• Here's /system/lib/egl

shell@konawifi:/system/lib/egl $ ls -al

-rwxrwxrwx root     root            8 2015-07-22 14:42 egl.cfg

-rwxrwxrwx root     root          416 2015-07-22 14:42 egl.cfg.bak

-rwxrwxrwx root     root        13344 2014-08-04 07:15 libEGL_mali.so

lrwxrwxrwx root     root              2015-07-22 14:46 libEGL_mgd.so -> /system/lib/egl/libGLES_mgd.so

lrwxrwxrwx root     root              2015-07-22 14:42 libGLES.so -> /system/lib/egl/libGLES_mgd.so

-rwxrwxrwx root     root        79116 2014-08-04 07:14 libGLES_android.so

-rwxrwxrwx root     root      3724781 2015-07-22 16:21 libGLES_mgd.so

-rwxrwxrwx root     root        25640 2014-08-04 07:15 libGLESv1_CM_mali.so

lrwxrwxrwx root     root              2015-07-22 14:46 libGLESv1_CM_mgd.so -> /system/lib/egl/libGLES_mgd.so

-rwxrwxrwx root     root        21540 2014-08-04 07:15 libGLESv2_mali.so

lrwxrwxrwx root     root              2015-07-22 14:46 libGLESv2_mgd.so -> /system/lib/egl/libGLES_mgd.so

• • Here's egl.cfg
    0 0 mgd
  • egl.cfg.bak, what's the difference between 0 0 and 0 1? 
    0 1 mali
    
  • Looking at the walk through on YouTube (ARM Mali Graphics Debugger Tutorial 2 – Target setup and first connection - YouTube), I see some differences
    • when I run mgddaemon after rebooting the device I get:

Macintosh:arm_android snovak$ adb shell mgddaemon

1437602372514: mgd_daemon[6520]: INFO: Main: The MGD daemon is starting

Daemon is version: B002

Socket is: \0mgddaemon

1437602372519: mgd_daemon[6520]: INFO: HostConnection: Initializing host connection

1437602372522: mgd_daemon[6520]: INFO: InterceptorListener: Initializing interceptor listener

1437602372523: mgd_daemon[6520]: INFO: Daemon: Daemon initializing

1437602372527: mgd_daemon[6520]: INFO: Daemon: Daemon running

1437602372529: mgd_daemon[6520]: INFO: InterceptorListener: Interceptor Listener waiting for connections

1437602372531: mgd_daemon[6520]: INFO: HostConnection: Host connection listening

• • Firstly, this sort of indicates that the daemon isn't started on boot.  I think that's bad.
    
  • I don't see anything saying that it's on port 5002.... as you see @~2:40 on the video
  • I see Socket is: \0mgddaemon, but I don't see anything about a port, so is \0mgddaemon local TCP/IP, or something else?
  • I do forward the port as outlined in the Help documentation via `adb forward tcp:5002 tcp:5002`
  • The GUI connects to the port, but again, I see no traces.  If the calls are being intercepted, I don't think they're going down the right pipe.