Cannot intercept my app with Mali Graphics Debugger

Hi vruiz,

There are no special permissions needed in the manifest because the socket we use is an abstract namespace AF_UNIX socket. This works on every production device we've tested it on because it's not located on the filesystem anywhere and therefore we don't need to ensure any visibility/permissions for it, but this is obviously not the case on your platform. I have seen this before however on a system which implemented a secure launcher. In short, you will need to investigate why there is a permission issue on abstract namespace AF_UNIX sockets, as this is causing the interceptor to be unable to talk to the daemon. If it works with the camera app, then that should provide some clues - what is different about how the permissions are set up for that application?...

Hope this helps,

Chris

Hi vruiz,

There are no special permissions needed in the manifest because the socket we use is an abstract namespace AF_UNIX socket. This works on every production device we've tested it on because it's not located on the filesystem anywhere and therefore we don't need to ensure any visibility/permissions for it, but this is obviously not the case on your platform. I have seen this before however on a system which implemented a secure launcher. In short, you will need to investigate why there is a permission issue on abstract namespace AF_UNIX sockets, as this is causing the interceptor to be unable to talk to the daemon. If it works with the camera app, then that should provide some clues - what is different about how the permissions are set up for that application?...

Hope this helps,

Chris

P.S. over the weekend someone at our end hit the same issue, and solved it by disabling selinux with "setenforce 0", so if your device uses selinux that might solve it!