Mali Graphics Debugger and Unity

I'm trying to make this debug tool work with Unity game on a non-rooted Android device.

Could anyone give a hint on how do I do that?

I followed all the steps from MGD's user guide with no success.
There are several things that I need to do with a source Android files (like adding some lines to an "Android.mk" file and manually load a .so file). And these steps need to be done slightly different way in case of Unity's app.

So, I placed libMGD.so to the "Assets/Plugins/Android/libs/armeabi-v7a" folder in Unity project, installed the provided MGDDaemon.apk and enabled it on the device.
But in the MGD tool itself I don't get any trace data. I'm facing exactly the same issue as discussed here, but unlike that guy, I'm not building a VR app. In fact, VR is even disabled in player settings.

So if anyone was able to debug Unity's build with the Mali Graphics Debugger on an unrooted device, I'd really appreciate some help.

As far as I can see, some people was able to make MGD work. So could you tell the secret, how you did that, please?

 

I spent hours getting the non-rooted version working. Here's how: https://community.arm.com/message/33498#33498.

 

Argh. I just had time to work on it today and just got it working. It kinda feels frustating that someone already posted the solution before me.

To add my two cents.

1) In build settings you can select "Google Android Project" and Export. This will create an android project for you in which you can load in Eclipse or Android Studio.

2) Derive your class from UnityNativePlayerActivity instead.

3) On Eclipse select File > Export -> Java -> Jar

4) Place libMGD.so from non-root/armeabi-v7a into Plugins/Android/libs/armeabi-v7a

5) manifest and jar files into Plugins/Android

 

Thanks guys!. You both really helped a lot.

 

Call me stupid, but I guess I need an even more detailed step by step process to get this working on a non-rooted device. @Jodon or @Phil Lira any help would be much appreciated.

 

Unzip the attach .zip file into your Assets/Plugins/Android folder. Rename the AndroidManifest.MaliDebug.xml to simply AndroidManifest.xml. Then make sure you're running the MGDaemon on your device. Launch via the MGDaemon while your Mali Debugging app (running on your PC) is connected. I should warn you, the info I got from MGD was pretty much nothing. The built-in Unity tools are much better.

Cheers.

 

Thanks I will try it out.

Why was it not helpful? It should show you a complete breakdown of shaders and draw calls and actual performance on device.

 

That's what I thought too. I'm on mobile, but here's the relevant thread where I discuss the issues I have. In short, you're better off using their other tools to figure it out plus the Unity Frame Debugger and profiling tools. If you need shader times, their shader compiler is what you need.

https://community.arm.com/message/34065#34065

 

Hey guys,

I needed this as a plugin that can be called at any time, so no need to modify AndroidManifest.xml or anything, just a simple C# call.

You can get it here:
https://github.com/mihailogazda/Unity3d-Mali-Profiler-Plugin

 

That was my first implementation. Unfortunately it disn't work for me when testing with the Gear VR. Those libraries grab function pointers on startup and if Mali isn't active by then it won't function.

 

How to Connect device?
via Device Manager, according to doc, but I can't find it in UI
https://developer.arm.com/docs/dui0...ger/android-devices/connecting-to-your-device
the instruction on the site is very poor