Skip to content

MODULE_PERFORMANCE.md

Latest commit

 

History

History
78 lines (59 loc) · 2.15 KB

MODULE_PERFORMANCE.md

File metadata and controls

78 lines (59 loc) · 2.15 KB
Raw

Xposed Module Performance & Impact

Measuring how Xposed modules affect device performance.

Impact factors

  • Scoped modules (target single app) — minimal impact
  • System-wide modules — higher overhead, especially with hooks in frequently-called methods
  • Callback count — each hook/callback adds latency

Benchmark tools

Built-in Xposed logging

# View Xposed module load time
adb shell dumpsys | grep -i xposed

# Check Zygisk timing
adb logcat | grep -i "zygisk\|lsposed"

Android Profiler

  1. Open Android Studio → Profiler
  2. Select device and process
  3. Monitor CPU, memory during app launch
  4. Compare with modules enabled vs disabled

Custom profiling in module

Java.perform(function() {
    var start = Java.use("java.lang.System").nanoTime();
    
    // Your hook
    var target = Java.use("com.example.Class");
    target.method.implementation = function() {
        console.log("[Perf] Method called");
        return this.method.call(this);
    };
    
    var elapsed = (Java.use("java.lang.System").nanoTime() - start) / 1000000;
    console.log("[Perf] Hook setup took: " + elapsed + "ms");
});

Performance checklist

  • ✅ Scope module to specific apps if possible
  • ✅ Avoid hooking frequently-called methods (onCreate, onDraw, etc.)
  • ✅ Use reflection sparingly — cache references
  • ✅ Test on low-end devices (if targeting them)
  • ✅ Monitor battery impact (logcat + Battery Historian)
  • ✅ Profile memory leaks (if holding references)

Slowest modules (typical impact)

  • Clipboard monitors — +2-5% CPU
  • Animation tweaks — +1-3% depending on hook depth
  • Permission overrides — minimal if scoped
  • Inline encryption logging — +5-15% for crypto ops

Optimal hook targets

❌ Avoid:

  • onCreate, onResume, onDraw (called frequently)
  • View.inflate, Thread constructors
  • System.loadLibrary (affects startup)

✅ Better:

  • Lifecycle callbacks (onStart, onPause)
  • Specific UI update methods
  • User-triggered methods

Test with trace

adb shell perfetto -c perfetto_config.pb -o /tmp/trace.pb

# Analyze in Perfetto UI: https://ui.perfetto.dev