IssueTracker

Hey Peter, this seems like it could be an issue with connecting to the process.

Peter, I'm in communication with this user on Twitter. They were super friendly and asked if we had enough information here. Can you tell if this is the same issue as the other one you looked at last week?

Hi anugumanoharreddy@gmail.com, based on the log you provided, it looks like the inspector crashed on device. However, it's not possible to tell what caused it to crash. Could you please also provide the logcat collected at the same time?

Hi, we'll need more information to investigate this issue. Could you please follow these steps and reply with the command line outputs? Your help is greatly appreciated.

1. Attempt to use Database Inspector or Layout Inspector on the app once. It's OK if this step is unsuccessful.
2. In Android Studio, close Database Inspector, Layout Inspector, or Profiler tool windows.
3. Disconnect and re-connect the device.
4. In Android Studio, click Run > Run... to launch the app on the device.
5. Clear logcat (e.g., adb logcat -c)
6. In a terminal, run adb shell. In the adb shell, run:
7. $ run-as PACKAGE_NAME
8. $ pwd. What's the output?
9. $ ls code_cache/. What's the output? Three files are expected: libjvmtiagent_x86.so, perfa.jar, transport. Note libjvmtiagent_x86.so may be named libjvmtiagent_arm64.so depending on the device's ISA.
10. $ exit. This will end the run-as session.
11. You should be in the regular adb shell session. Run $ cmd activity attach-agent PACKAGE_NAME /data/data/PACKAGE_NAME/code_cache/libjvmtiagent_x86.so=/data/local/tmp/perfd/agent.config. What's the output?
12. Check logcat. Are there any errors? In particular, if you search for whole word 'avc', are there any hits? They often indicate permission errors.

If you can send back the outputs from Steps 8, 9, 11, 12, that will help us better understand the issue. Your help is appreciated!

Hi anugumanoharreddy@gmail.com, thank you for getting back to us. Step 9 ls code_cache/ shows the libraries and jars that are used to run the underlying pipeline are not present. (the tech that database inspector runs on).

I don't know about the custom rom because it's outside my area of expertise, but it might very well be it. We recently had a user come in with a similar issue and they were running SELinux. They fixed it by disabling SELinux.

I'm CCing shukang@ who knows more about the pipeline.

Indeed Shukang knows the most here. He's OOO so he won't reply today.

However! The fact that you are reporting that JVMTI is not found is probably a pretty severe issue that seems likely due to it being custom ROM, yes.

For background, the Android framework team added JVMTI to Android in O. (JVMTI is a standard, you can read more about it online if you do a quick search, but in Android O we wrote our own implementation).

Note that the framework team added tests to a large suite of OS tests that. Therefore, we verify 1) that JVMTI is available in O+ and 2) for any device to be certified official, they also have to pass these tests. However, if you're using a custom ROM, it sounds like there are no such guarantees there....

My guess is you'll have to do inspection work on an official ROM or device for now.

I'm going to close this bug as infeasible, but please continue to keep adding more information here if you had more questions or wanted to provide more evidence for why we should keep it open.

My code_cache/ directory is also empty, and I'm running on some custom hardware with a custom OS install (based on Android O).

I tried looking for them on my mobile phone (running Android 12) to see if I could copy them, but they were missing there too.

Is there a way to get the missing JVMTI .so and .jar files and side-load them to enable the database inspector?

andy@mx51.io: You need to run the inspector at least once on the Android 12 device to see the files in the code_cache/ directory. Alternatively, is there a directory /data/local/tmp/perfd on the device? If so, you can copy these three files (libjvmtiagent_x86_64.so, perfa.jar, transport) from there to the code_cache/ directory. The _86_64 suffix may change depending on the hardware.

Does google verify, if the OEM firmware supports Database inspector, before certification ?

I copied those three files (libjvmtiagent_arm64.so, perfa.jar, transport) to /data/data/PAKCAGE/code_cache directory, and run that cmd activity attach-agent ... command in adb shell, here's the log in brief: (full log in attachment)

18:42:42.116 PACKAGE_NAME                    W  type=1400 audit(0.0:29): avc: granted { execute } for path="/data/data/PACKAGE_NAME/code_cache/libjvmtiagent_arm64.so" dev="sda17" ino=1426319 scontext=u:r:untrusted_app:s0:c100,c257,c512,c768 tcontext=u:object_r:app_data_file:s0:c100,c257,c512,c768 tclass=file app=PACKAGE_NAME
18:42:42.166 libc                            E  Access denied finding property "ro.serialno"
18:42:42.163 PACKAGE_NAME                   W  type=1400 audit(0.0:30): avc: denied { read } for name="u:object_r:serialno_prop:s0" dev="tmpfs" ino=18827 scontext=u:r:untrusted_app:s0:c100,c257,c512,c768 tcontext=u:object_r:serialno_prop:s0 tclass=file permissive=0 app=PACKAGE_NAME
18:42:42.213 PACKAGE_NAME                    W  DexFile /data/data/PACKAGE_NAME/code_cache/perfa.jar is in boot class path but is not in a known location
18:42:42.767 StudioProfiler                  V  Transformed class: android/app/PendingIntent
                                                .... Transformed class... x 14 lines
18:42:49.489 PACKAGE_NAME                    W  Current dex file has more than one class in it. Calling RetransformClasses on this class might fail if no transformations are applied to it!
                                                .... Current dex file... x 14 lines
18:42:49.490 PACKAGE_NAME                    W  Accessing hidden method Landroid/app/PendingIntent;-><clinit>()V (blacklist, linking, allowed)
                                                .... Accessing hidden method many many lines
18:42:49.635 PACKAGE_NAME                    W  Accessing hidden field Landroid/app/IntentService;->mRedelivery:Z (greylist-max-o, linking, allowed)
18:42:49.674 PACKAGE_NAME                    W  Class android.os.PowerManager$WakeLock failed lock verification and will run slower.
18:42:49.714 StudioProfiler                  V  Profiler initialization complete on agent.
18:42:49.731 StudioProfiler                  V  Acquiring Application for Events

It seems the agent initialization has completed? But the "App Inspection" tab is still empty. How can I do to help investigate further?