Enable AIDL events to get information on binder transaction [341852305]

Fixed

Feature Request

Status Update

No update yet.

Description

ml...@google.com

created issue #1

May 21, 2024 07:35AM

Component used: Macrobench 1.3.0-alpha05

By default binder transaction calls are very enigmatic not providing info on what's going on. This can be improved by enabling AIDL atrace tag that would give some information in the binder reply

https://screenshot.googleplex.com/5rsikWYi3gU6N2J

What do you think we add this tag as default in the macrobenchmark perfetto config?

Reference trace file:

https://ui.perfetto.dev/#!/?s=14a24102de992c35566c55a94d14a9e29117f981072d17c6696778ea4efc96fa

Comments

ml...@google.com <ml...@google.com> #2May 21, 2024 10:03AM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android build

Which Android build are you using? (e.g. OPP1.170223.012)

Device used - Device Make, Model, Android OS Version

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report capturing

After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.

Alternate method

Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen record of the issue, for clarity

Please capture screen record or video of the issue using following steps:

adb shell screenrecord /sdcard/video.mp4

Subsequently use following command to pull the recorded file:

adb pull /sdcard/video.mp4

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

cc...@google.com <cc...@google.com> #3May 21, 2024 08:14PM

android 9, 10, 11, 12
Devices: samsung, realme, xiaomi, OPPO, motorola, LGE,

I don't know how to write code reproducing issues in Android framework, unless you explain what does "no event down from INITIALIZED" mean. Then maybe I can prepare a piece of code that doesn't "event down from INITIALIZED". Until then - sorry.

Also - this error doesn't ever show on the device it is just logged to crashlytics, so there's now way to capture anything "after reproducing the issue".

ap...@google.com <ap...@google.com> #4May 21, 2024 08:56PM

Marked as fixed.

That particular error means that you are attempting to move the Lifecycle to DESTROYED before it was actually ever moved to CREATED. It was never actually supposed to be supported, but there was a bug in Lifecycle that made it so it only failed if there was an Observer on the Lifecycle, but it was fixed in https://issuetracker.google.com/177924329.

ca...@google.com <ca...@google.com> #5May 21, 2024 08:59PM

Glad to hear it was fixed. I'm experiencing it with lifecycle 2.5.1.

pr...@google.com <pr...@google.com> #6Jun 12, 2024 10:45PM

I mean it was fixed to throw the error in Lifecycle 2.5. It was always supposed to be an error.

Issue 341852305