Energy findings
Every detected battery anti-pattern, ordered by severity. Expand a row for the offending source and its trace hint.
| Expand | Severity | Rule | Finding | Category | Location |
|---|
Run log
Analysis progress and reasoning stream, newest entry last.
Every detected battery anti-pattern, ordered by severity. Expand a row for the offending source and its trace hint.
| Expand | Severity | Rule | Finding | Category | Location |
|---|
Analysis progress and reasoning stream, newest entry last.
EcoTrace runs 23 energy detectors over a Java or Kotlin project, then traces every critical finding backwards through the call graph to the architectural decision that caused it. Static analysis is local and instant; cross-file causal tracing is handed to IBM Bob 2.0.
Wakefulness, network, location and architecture rules evaluated in process, with no network round-trip.
Up to six hops backwards from the anti-pattern to the entry point that put it on the path.
A remediation for every rule, written against WorkManager, coroutines and modern lifecycle APIs.
ADB dumpsys batterystats snapshots turn the static
result into a measured mAh/min rate and an A+–F grade.
Stored locally in %APPDATA%\ecotrace\settings.json
Issued from bob.ibm.com under Account → API Keys. Sent only to the Bob endpoint, never written to a log.
Run before committing an AI fix. Leave empty to skip verification.
Static analysis runs either way; the model only affects how deep cross-file causal tracing goes.
Needed only for live drain profiling. Static analysis works without
it. If adb is not on your PATH, give the full path.
EcoTrace is built on the IBM Carbon Design System, which ships the three themes this selector offers — Gray 100, Gray 90 and white — over one shared token set. Switching is instant and affects the whole application.
Every graded scan recorded for this machine.