darken 2356726417 fix(overview): Call an empty case not enough on older models ...

AirPods Gen 1 and Gen 2 publish their case capacity as a lower bound, and
the adequacy check let that guard run before any zero-reading check. At a
0% case those two models rendered the definite "no charges left" text in
the neutral uncertainty colour while the screen reader hedged with "may
not be enough", contradicting the same node three ways.

The empty reading is now handled before the lower-bound guard. It sits
after the "enough" branch, which a zero reading can never satisfy, so it
cannot mask a positive claim. The lower-bound rule exists to avoid
underselling a case whose published capacity is only a floor, and an
empty case has nothing to undersell.

Fixes review finding F4

2026-08-25 22:33:42 +02:00

..

proguard

Fix release builds failing on a missing Play Core annotation

2026-08-07 19:30:15 +02:00

src

fix(overview): Call an empty case not enough on older models

2026-08-25 22:33:42 +02:00

.gitignore

Refactoring

2022-09-14 18:00:18 +02:00

build.gradle.kts

fix(upgrade): Add a persistent acknowledgement safety net for Play purchases

2026-08-18 17:55:19 +02:00

proguard-rules-debug.pro

Refactoring

2022-09-14 18:00:18 +02:00