• Locked Locked
  • Replies 3 replies
  • Subscribers 136 subscribers
  • Views 4670 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

Getting Mali Graphics Debugger to run with Samsung S2

Bodo Pfeifer
Note: This was originally posted on 6th June 2013 at http://forums.arm.com

Hi,

we like to use the Mali Graphics Debugger with a Samsung S2.

There is a problem:

According to the readme we have to copy 2 files to the device.

* Pushing them to /sdcard/ works fine

but
* cp mgddaemon /system/bin/mgddaemon fails

Message: "cp: can't create '/system/bin/mgddaemon': Read-only file system

FYI: I am super user. Tried to chmod the directory but this gives me the same message.

Can anyone help me here?


Thanks in advance,
Bodo
  • Note: This was originally posted on 7th June 2013 at http://forums.arm.com

    Hi Bodo,

    it might be that the partition on which the "bin" directory resides is mounted read-only, in which case even root (superuser) can't write until it is remounted read-write.

    If you did something like

    adb shell

    to open a shell on the device, and then

    mount

    you can see what partitions are mounted. If there is one listed for "system" then you could try something like this (once you have become superuser):

    mount -o remount, rw /system

    If "system" isn't listed in the mounted partitions then you may need to remount the whole root filesystem read-write instead:

    mount -o remount, rw /

    HTH, Pete
  • Note: This was originally posted on 7th June 2013 at http://forums.arm.com

    Hi Pete,

    thanks for this tip. It worked! Got those files copied and could continue with the readme.

    Now I get a connection.

    The Log of the Debugger says "[INFO]: PROCESS_STARTED" when I start the game.

    The main window keeps showing "No trace data to display". Not sure if this is normal.

    If I push the button to capture a frame, the log states: "[INFO]: FRAME_CAPTURE_WAITING".

    And instantly a dialogue pops up, telling me that "An internal error occured during: "Capturing frame"."
    The more-details button then shows an java.lang.NullPointerException.

    I  have no idea what might be wrong here. The app is a release build,  might this be a problem? Does the app need to be debuggable?
    Or is this truly an internal error from the Debugger?

    Can you / anyone help me here?


    Thanks in advance,
    Bodo
  • Note: This was originally posted on 10th June 2013 at http://forums.arm.com

    Hi Bodo,

    Sorry to hear you're having trouble with the tool. Can you let me know which version of Android you are using? Also which application are you attempting to trace, and are you sure it's a GLES application?

    Thanks,
    Chris