• State Accepted Answer
  • Locked Locked
  • Replies 21 replies
  • Subscribers 136 subscribers
  • Views 17488 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't Trace app with MGD 2.0.1

Phil Lira

Hi,

I'm trying to profile a game with MGD 2.0.1 without success. So far my status is that I successfully managed to connect to target in the MGD GUI but no trace data is displayed.

Logcat is not displaying any information on the intercepted lib. I don't know what I am missing.

ligGLES_mgd.so and mgddaemon are inside /system/lib/egl and there's a symbolic link libGLES_mgd.so pointing to libGLES.so

I tried both with processlist.cfg and without it. egl.cfg contains "0 0 mali" (as per instructions on android 4.4 telling no need to do "0 0 mgd"

Host: Windows 7

Target: Note 4 910H Android 4.4.4 running an APK generated by Unity 4.6

Kind Regards,

Phil Lira.

Parents
  • 0 in reply to Phil Lira

    Hi Philira,

    thank you for feedback. For profiling we have a different tool: DS-5 Streamline. It allows profiling CPU and GPU hardware counters, as well as software events from the Linux kernel and kernel drivers. You cannot do replacements with it yet, but it is something we are thinking about. At the moment setting up Streamline to work with Mali GPUs requires recompiling the Mali driver with the right options (see Using DS-5 Streamline with Mali on Google Nexus 10).

    As a general note, rather than pushing for an experimental approach, like trying 4x4 textures, change states, render to smaller viewport, we usually prefer a more analytical approach. With MGD and Streamline we aim to let the tool show you what is going on in the system, and find the reason of the bottleneck, understanding why something is slowing it down. This allows focusing on the whole system, also taking into account energy efficiency rather than just FPS.

    Still, I acknowledge that what you listed can be very useful features, and some of which are on our 2015 roadmap for Mali tools.

    Thanks,

    Lorenzo

Reply
  • 0 in reply to Phil Lira

    Hi Philira,

    thank you for feedback. For profiling we have a different tool: DS-5 Streamline. It allows profiling CPU and GPU hardware counters, as well as software events from the Linux kernel and kernel drivers. You cannot do replacements with it yet, but it is something we are thinking about. At the moment setting up Streamline to work with Mali GPUs requires recompiling the Mali driver with the right options (see Using DS-5 Streamline with Mali on Google Nexus 10).

    As a general note, rather than pushing for an experimental approach, like trying 4x4 textures, change states, render to smaller viewport, we usually prefer a more analytical approach. With MGD and Streamline we aim to let the tool show you what is going on in the system, and find the reason of the bottleneck, understanding why something is slowing it down. This allows focusing on the whole system, also taking into account energy efficiency rather than just FPS.

    Still, I acknowledge that what you listed can be very useful features, and some of which are on our 2015 roadmap for Mali tools.

    Thanks,

    Lorenzo

Children