What problem does it solve? When a PlxNative app on a rooted LG webOS television becomes slow, janky, frozen, or consumes unexpected CPU/GPU, developers need a structured way to find the cause on the actual hardware rather than guessing from the simulator. ## Core Features & Use Cases - Live stack sampling: Capture one-shot or statistical stack samples of all threads with plxnative-sample, including a watchdog mode that snapshots heartbeat-stall episodes without killing the process. - Three-layer graphics profiling: Measure production present pacing, passive Mali IRQ rates, and phase-attributable Mali HWCNT counters through the FPS harness, with clear rules about which leg may be quoted as real FPS. - Dead-or-alive triage: Distinguish a crashed process (route to crash-triage) from a stalled or misrendering live one, resolving the correct install via make print-appdir and fuser. - Use Case: A developer notices frame drops in the library scene on their webOS 4.5 set. They take tv-lock, run the FPS harness with --graphics-profile on that scene, compare the baseline and active Mali IRQ legs, then use the framedrop and cpuprof triggers to localize render-thread wall time. ## Quick Start Ask the assistant to profile the running PlxNative app on the TV to find why the UI is stuttering, starting with a stack snapshot and a 30-second graphics profile.
