Add runtime control to Android ETDump profiling

[psiddh]

Enhances existing EXECUTORCH_ANDROID_PROFILING with runtime control API.
Replaces hardcoded profiling with flexible, production-ready implementation.

New Capabilities:

• Runtime profiling control via ETDump.enableProfiling()/disableProfiling()
• Configurable output paths (no root access required)
• Programmatic data access with getETDumpData()
• Zero performance overhead when profiling is disabled
• Single APK deployment (enable/disable at runtime)

Implementation:

• Add ETDump.java: Public Java API for profiling control
• Add executorch_jni_etdump.cpp: JNI implementation with global ETDumpManager
• Modify jni_layer.cpp: Integrate ETDump with Module loading
• Modify CMakeLists.txt: Enhance EXECUTORCH_ANDROID_PROFILING flag

Backward Compatible:

• Same build flag (EXECUTORCH_ANDROID_PROFILING)
• Default behavior: profiling disabled (zero overhead)
• Users who already enable profiling get new features automatically

Usage:
// Build with: -DEXECUTORCH_ANDROID_PROFILING=ON

ETDump.enableProfiling("/sdcard/profile.etdump"); Module module = Module.load("model.pte"); module.forward(inputs); ETDump.writeETDump(); ETDump.disableProfiling();

Summary

[PLEASE REMOVE] See CONTRIBUTING.md's Pull Requests for ExecuTorch PR guidelines.

[PLEASE REMOVE] If this PR closes an issue, please add a Fixes #<issue-id> line.

[PLEASE REMOVE] If this PR introduces a fix or feature that should be the upcoming release notes, please add a "Release notes: " label. For a list of available release notes labels, check out CONTRIBUTING.md's Pull Requests.

Test plan

Test Command: EXECUTORCH_ANDROID_PROFILING=ON sh scripts/build_android_library.sh

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/16359

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 7 New Failures, 5 Unrelated Failures

As of commit 24ee8a9 with merge base 479791d ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  The process '/usr/bin/git' failed with exit code 128
• Build Presets / linux (linux, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build (gh)
  The process '/usr/bin/git' failed with exit code 128
• Build Presets / linux (pybind, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build (gh)
  The process '/usr/bin/git' failed with exit code 128
• Build Presets / windows (pybind) / build (gh)
• Lint / lintrunner / linux-job (gh)
  >>> Lint for extension/android/CMakeLists.txt:
• pull / android / build-llm-demo / linux-job (gh)
  /pytorch/executorch/extension/android/jni/jni_layer.cpp:285:33: error: 'etdump' is not a class, namespace, or enumeration
• pull / unittest-buck / macos / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• pull / test-llama-runner-linux (fp32, xnnpack+custom+qe, linux.arm64.2xlarge, executorch-ubuntu-22.04-gc... / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• pull / test-models-linux (w2l, portable, linux.4xlarge.memory) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• pull / test-models-linux-basic (vit, portable, cmake, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11... / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• pull / test-setup-linux-gcc / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• Test CUDA Builds / test-models-cuda (linear) / linux-job (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[Gasoonjia]

Mind hint me about the relationship between Android ETDump and devtool one? Basically it is our ETDump + an Android Wrapper if I understand corrent?

[psiddh]

Mind hint me about the relationship between Android ETDump and devtool one? Basically it is our ETDump + an Android Wrapper if I understand corrent?

Yes Android ET Dump is simply a wrapper , Core ETDump + High level Android Dump helper APIs , making it very flexible for Android apps to profile dynamically