Idea
Surface the apps most likely draining the battery — a "top battery hogs" list, and/or naming the likely culprit behind a fast-drain alert (#109). From .claude/FEATURES_IDEAS.md, item 3.
Status: parked — idea only, not yet grilled or researched
The open question is how feasible this is for a normal (non-system) app:
- Exact per-app battery figures (like Settings → Battery shows) need the privileged
BATTERY_STATS permission (signature|privileged) — not grantable to a normal Play/sideloaded app. Blocked.
- A ranked estimate may well be doable via the user-granted "Usage access" permission (
UsageStatsManager / PACKAGE_USAGE_STATS, toggled in Settings → Special access — no root, no ADB). That gives per-app foreground/usage time, from which battery use can be estimated by correlating with the total measured drain. This is the likely way AccuBattery does it out of the box. Unverified — needs research.
Next step (later)
- Research how AccuBattery /
UsageStatsManager actually work; confirm what's really obtainable and how accurate.
- Then grill the design: the accuracy caveats (it's a guess, not a measurement), the "Usage access" permission-grant UX, and whether an estimate is honest/useful enough to show.
Revisit after #108 (rate) and #109 (fast-drain alert). No ADR yet — this is an open question, not a settled "no."
Idea
Surface the apps most likely draining the battery — a "top battery hogs" list, and/or naming the likely culprit behind a fast-drain alert (#109). From
.claude/FEATURES_IDEAS.md, item 3.Status: parked — idea only, not yet grilled or researched
The open question is how feasible this is for a normal (non-system) app:
BATTERY_STATSpermission (signature|privileged) — not grantable to a normal Play/sideloaded app. Blocked.UsageStatsManager/PACKAGE_USAGE_STATS, toggled in Settings → Special access — no root, no ADB). That gives per-app foreground/usage time, from which battery use can be estimated by correlating with the total measured drain. This is the likely way AccuBattery does it out of the box. Unverified — needs research.Next step (later)
UsageStatsManageractually work; confirm what's really obtainable and how accurate.Revisit after #108 (rate) and #109 (fast-drain alert). No ADR yet — this is an open question, not a settled "no."