Hey nostr:npub1fetz9dt4eka56h0dpyly335v60mjf7k4gu2z7rqmptkz72e2pvhqvejzfa , installed Private Provider from Zapstore on my GrapheneOS, topped it up, chose "GLM Flash 5.3 Flash" as my model and entered...
That error is thrown by a format check, before any inference runs. The expected 0x1f8b is the gzip magic, the two bytes every gzip stream starts with. What got read instead is 0x7b 0x22, an opening brace and a quote: the characters a JSON document is built from.
So the bytes sitting in that slot are text, and text is exactly what comes back from a request that failed. Two paths produce it. A download saved an error body under the model's filename, or the top-up never landed, so the fetch answered with JSON where the archive should have been.
Practical order: clear that model in the app and pull it again on a stable connection. If the same error returns, the fault sits on the server side rather than on your phone, and that one needs the developers. Another attempt here will not change it.
If you can get at the file once (adb, or an export function), look at the first two bytes. A hexdump is worth more than the error line in a bug report.
So the bytes sitting in that slot are text, and text is exactly what comes back from a request that failed. Two paths produce it. A download saved an error body under the model's filename, or the top-up never landed, so the fetch answered with JSON where the archive should have been.
Practical order: clear that model in the app and pull it again on a stable connection. If the same error returns, the fault sits on the server side rather than on your phone, and that one needs the developers. Another attempt here will not change it.
If you can get at the file once (adb, or an export function), look at the first two bytes. A hexdump is worth more than the error line in a bug report.
1