Only our GLES replay is done on host.
There is no technical reason that it would be incredibly difficult to handle 32-bit windows applications, but might require quit a bit of work in the build system to get everything working well together.
For the context, we are using this to compare our cloud VR solution with VR content running locally on DayDream so we need the RAW RGBA bytes to compare them
@dsrbecky Thanks for pointing this out.. Our main aim to make sure that latency from our cloud server so we will be comparing the same content playing natively on Android and capture it using GAPID against the frames captured using our solution from remote server and being played on Android
We will be comparing both the captures mainly to analyze the similarity in both the capture to conclude that our sloution has same latency KPIs as content running natively on Android
I'm actually building on Win10 right now... Let me see if I hit this
I can link a binary executable against libgapii.so but it looks like I need to do "installation" stuff manually. Is that right?
FYI, 0.25.0 does not work.
I'm trying to debug a graphics memory leak I suspect is being caused by an OpenGL-using lib I'm using. I wanted to trace the GL lib calls like I would do on a desktop system. The Android environment I'm working in has Java stripped away. So I've got adb but otherwise everything is 100% native.
While I can link in the libgapii libs it appears they need to be initialized in a way that requires the java debug bridge. At least as far as I can gather looking at the go code.
Which version of Android is your project using?
Then I am afraid the debugger + code injection hack is needed. Pascal merged a new approach which only uses GLES layers, but that would only be available in Android Q onwards I think: google/gapid#2700
Good luck with your project, please let us know how you/another tracer manage to trace GLES calls with a different approach!
If you have sufficient control over your application (and its lifecycle) you should in theory be able to LD_PRELOAD libgapii.so, and create the spy (call gapii::Spy::get())
Without Java, we would be unable to understand how the application launches, and connect normally. (OnCreate / ClassLoaders) are what android typically uses, but your application is obviously started in some other way, so would have to do something similar
Without Java, we would be unable to understand how the application launches, and connect normally. (OnCreate / ClassLoaders) are what android typically uses, but your application is obviously started in some other way, so would have to do something similar
LD_PRELOAD is the technique I'm about to try with another lib: https://github.com/apitrace/apitrace.
If I were to do this with gapii where does it send trace data? I thought it blocked on a socket connection? Presumably I need a client also running?
GAPII does not talk to a client directly. The scheme is
client <--> GAPIS <--> GAPII
@ThalmicRevane sorry I'm late to the party. What you are trying to do is entirely possible. Modify your app to load
libgapii.so before doing any EGL/GL work. Then, call the exposed JNI_OnLoad function. You can pass two nullptrs as arguments, as we no longer use Java for anything and ignore them. If you cannot modify your app to call JNI_OnLoad, you can achieve the same by marking the JNI_OnLoad function as a constructor function and removing its arguments, rebuilding, and using LD_PRELOAD to load the library. Calling JNI_OnLoad will initialize the spy and block your app waiting for a connection from host. You should see a GAPII awaiting connection on pipe <pipe> message in logcat. You can then trace using the gapit command line utility. Specify the android device and use a target URL of the form port:<pipename>:<abi>. <pipename> is gapii by default and <abi> is one of armeabi-v7a, arm64-v8a or x86 depending on the ABI of the app you are trying to trace. Let me know if that works for you.
Do gapid works with anbox emulator ?
Hi, unfortunately GAPID does not support the official Android emulator, and it very probably doesn't work either on anbox. GAPID system requirements are detailed here: https://gapid.dev/requirements/