Repository navigation
Ponko v2.2.0-beta.1
Pre-releasePonko is an offline-capable AI app for Android: chat (image, file and document input) +
drawing + tagging, each of which can be served over its own OpenAI-compatible API.
All inference runs on-device: apart from the optional in-app LoRA download, no feature
needs the network. No telemetry; your data stays on your phone.
See the README.
This is a pre-release. It installs alongside the stable app (package
com.litertchat.app.beta).
What changed since 2.2.0-beta.0
Sampling cache (EasyCache / UCache)
Two new rows in the parameter card of the drawing and image-to-image pages: a cache mode
dropdown and a threshold field. Both are passed per image, so switching them does not
reload the model.
- EasyCache targets DiT models (SD3.5, Flux, Qwen-Image, H3-Image...)
- UCache targets UNet models (SD1.5, SDXL)
- Picking the wrong one for the architecture is not fatal: sd.cpp logs that the cache is
not supported for that model type and then behaves as if it were off - Threshold left empty means the mode's own default (EasyCache 0.2, UCache 1.0)
Reading the result: max_warmup_steps defaults to 8, so a run with fewer than ~20 steps
cannot skip anything by design. The engine states what it actually did in the log
(EasyCache skipped N/M steps (x.xx speedup)); a skipped step also reports progress, so
the bar keeps moving normally.
CLIP skip
A third new row. Empty means "use the architecture default": 1 for SD1, 2 for SD2 / SDXL /
SD3 / Flux. On SD1.5, an empty field and an explicit 1 must produce a pixel-identical
image with the same seed. Values are clamped to 1..12. It only affects encoders that have
layers to skip - the T5 and LLM encoders (SD3, Flux, Qwen, H3) ignore it.
Remaining time
The progress line used to count up ("· 1234 s"), which says nothing about how much longer
you are waiting. It now ends with an estimate extrapolated from the average time per step.
- The unit is a setting: About → Settings → Remaining time, seconds or minutes,
seconds by default - It appears from the first completed step; the text encoding before it is not
proportional to steps and is excluded from the timing - Switching the unit takes effect immediately on a running job, without interrupting it
Load failures now carry the reason
"Load failed: could not create inference context. The file may be unsupported..." was all
the app said when sd.cpp refused a file - which cannot be acted on. sd.cpp does log the
real reason (a tensor it could not find, a shape that did not match, a header it could not
read), but that only reached the log file. The most informative line is now appended to
the message itself, so a screenshot carries the cause. When no such line exists the
message is unchanged.
Fixed: loading progress was reported as sampling steps
The bar could sit at "step 528/528", full and frozen, with no estimate. 528 was never a
step count - it is how many tensors the text encoder loads. The engine latches "sampling
started" the first time it reports a step count equal to the one requested, and a small
component inside the H3-Image text encoder happens to report exactly 6 tensors, which was
the requested step count. Every tensor batch after that was drawn as a sampling step, and
because total == current the estimate was suppressed.
The guard now also requires the reported total to equal the requested steps. A tensor
batch never matches; real sampling always does.
Fixed: the elapsed time and the estimate kept disappearing
The progress line is written from two places - a one-second ticker, and the preview-frame
callback that fires once per sampling step. The ticker wrote the full line; the preview
callback wrote only "Denoising… step N/M" and knew nothing about the start time.
Whoever wrote last won. On H3-Image, which emits a preview frame on every step, the
elapsed time and the estimate vanished a moment after each tick and came back a second
later. Both paths now build the line through the same function.
Verified on a device
512×512, 6 steps, CFG 1.0, Euler + Discrete, minimax_h3_image_pruned-Q2_K on a 15.6 GB
phone:
- the line starts at
step 0/6with an empty bar - not528/528 - after the first step:
step 1/6 · 273 s · ~1201 s left - switching the unit to minutes turns the same line into
~23 minwhile the job keeps
running - at step 2/6 it still reads
574 s · ~1083 s left, and 25 seconds later
600 s · ~1135 s left- the preview frames no longer wipe it
中文说明
Ponko 是一个可离线运行的 Android AI 应用:对话(支持图片、文件、文档输入)+ 绘图 + 打标,
三者都能各自开一个 OpenAI 兼容 API。所有推理都在设备本地完成——除了可选的 App 内 LoRA
下载,任何功能都不需要联网。无遥测,数据留在你手机上。
这是预发布版。 它与正式版并存(包名 com.litertchat.app.beta)。
相对 2.2.0-beta.0 改了什么
采样缓存(EasyCache / UCache)
绘图页和重绘页的参数卡里多了两行:缓存模式下拉框 + 阈值输入框。两个都是每张图现传的,
切换不会重载模型。
- EasyCache 面向 DiT 模型(SD3.5、Flux、Qwen-Image、H3-Image 等)
- UCache 面向 UNet 模型(SD1.5、SDXL)
- 选错不致命:sd.cpp 会记一句「该模型类型不支持此缓存」,然后当作没开
- 阈值留空 = 按模式取默认值(EasyCache 0.2,UCache 1.0)
怎么看有没有生效:max_warmup_steps 默认 8,所以 20 步以下的运行本来就不会跳步。
引擎会把实际做了什么写进日志(EasyCache skipped N/M steps (x.xx speedup));被跳过的步
同样会上报进度,进度条照常走。
CLIP skip
第三行。留空表示「用架构默认值」:SD1 是 1,SD2 / SDXL / SD3 / Flux 是 2。在 SD1.5 上,
留空和显式填 1 必须出一张同 seed 完全一致的图。取值夹在 1~12。它只对有层可跳的编码器
起作用——T5 和 LLM 类编码器(SD3、Flux、Qwen、H3)会忽略它。
剩余时间
进度行以前是往上涨的(「已 1234 秒」),读不出还要等多久。现在末尾会给出一个按「平均每步
耗时」外推的估算。
- 单位是设置项:关于 → 设置 → 剩余时间单位,秒或分钟,默认秒
- 从第一步完成起出现;首步之前的文本编码和步数不成比例,不计入计时
- 出图途中切单位立刻生效,不会打断正在跑的任务
加载失败会带上原因
sd.cpp 拒绝一个文件时,以前只显示「加载失败:无法创建推理上下文。文件可能不受支持…」,
这种话没法照着做。sd.cpp 其实会打出真正的原因(哪个张量没找到、哪个形状不对、哪个头读不
出来),但那几行只进日志文件。现在最有信息量的那一行会拼进提示本身,截个图就够。没有这类
日志时,提示与以前完全一致。
修复:加载进度被当成采样步显示
进度条可能停在第 528/528 步、满格不动,而且一直不显示剩余时间。528 从来不是步数——那是
文本编码器加载的张量个数。引擎在「上报的步数 == 请求步数」时会锁存「已经开始采样」,而
H3-Image 文本编码器里有个小组件恰好上报 6 个张量,正好等于请求的步数。锁存之后,后面每一批
张量都被画成一步采样,又因为总数等于当前值,估算就整个被压掉了。
现在判据多了一条:上报的总数还必须等于请求的步数。张量批次永远对不上,真正的采样永远对
得上。
修复:耗时和剩余时间会突然消失
进度行是从两个地方写的——每秒一次的 ticker,和每步一次的预览帧回调。ticker 写完整的一行;
预览帧回调只写「正在去噪采样… 第 X/Y 步」,而且它拿不到开始时刻。
谁后写谁赢。H3-Image 每一步都出预览帧,于是耗时和剩余时间在每次 tick 后一闪就没了,一秒后又
回来。现在两条路径都走同一个函数生成那行字。
已在设备上验证
512×512、6 步、CFG 1.0、Euler + Discrete、minimax_h3_image_pruned-Q2_K,15.6 GB 手机:
- 开跑是
第 0/6 步,进度条从空开始——不再是528/528 - 第一步完成后:
第 1/6 步 · 已 273 秒 · 剩余约 1201 秒 - 把单位切成分钟,同一行变成
剩余约 23 分钟,任务照常跑 - 第 2 步时仍是完整的
已 574 秒 · 剩余约 1083 秒,25 秒后变成已 600 秒 · 剩余约 1135 秒
——预览帧不再把它擦掉