From 36513cf059ed52c28018fe687135bc33b5690318 Mon Sep 17 00:00:00 2001 From: Karol Kulesza Date: Sun, 23 Aug 2026 11:55:42 +0200 Subject: [PATCH] =?UTF-8?q?chore:=20one=20number=20for=20the=20model=20siz?= =?UTF-8?q?e=20=E2=80=94=202.59GB,=20not=202.4GB=20in=20five=20comments?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Five comments described the shipped artifact as "2.4GB" while the README and every deep dive say 2.59GB. Both were right — 2.59e9 bytes is 2.41 GiB — but nothing in the repo said so, so a reader comparing pubspec.yaml to the README had two sizes for one file and no way to reconcile them. Normalized on the decimal figure: it is what litert-community publishes, and what the docs already use fifteen times. The two Android backup-rule files carried a range rather than a stale single value. It spans the Gemma 3 1B fallback to Gemma 4 E2B, so it is now the two sizes those models are documented at — 0.58GB in model-provisioning.md, 2.59GB in on-device-inference.md — rather than a band rounded off both ends. Comments only; no executable line changed. `dart format` reports 0 changed and `flutter analyze` no issues. --- android/app/src/main/res/xml/backup_rules.xml | 2 +- android/app/src/main/res/xml/data_extraction_rules.xml | 2 +- integration_test/model_provisioning_test.dart | 2 +- lib/services/models/model_downloader.dart | 2 +- pubspec.yaml | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/android/app/src/main/res/xml/backup_rules.xml b/android/app/src/main/res/xml/backup_rules.xml index 7b7e3ad..8dd9cf1 100644 --- a/android/app/src/main/res/xml/backup_rules.xml +++ b/android/app/src/main/res/xml/backup_rules.xml @@ -2,7 +2,7 @@