Repository navigation
Ponko v2.2.0-beta.0
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.1.3
stable-diffusion.cpp is upgraded to upstream master (2026-11-13) - 79 upstream commits,
ggml included.
That brings MiniMax-H3-Image and P-H3-Image (#2324, #2272). H3 video was already
there; what was missing was the Sol-H3 VAE decode path (#2317). CHROMA also gets its own
version id (#2237) instead of borrowing another model's.
Fixes in there that reach features which already worked: hires now honours the step count
you ask for (#2227), diffusers-named SDXL is recognised without the ComfyUI prefix (#2247),
LoRA scalars stay F32 and are merged as F32 when needed (#2263, #2302), and Krea2 Kohya LoRA
names no longer vanish (#2301).
- New family
MiniMax-H3-Image / P-H3-Image: diffusion model + Qwen3-VL encoder +
Sol-H3 VAE. Reference-image editing works from the same checkpoint - New
Text connectorslot, needed when pairing the 4B encoder. Appended at the end of
the slot table rather than next tollm, for the same reason the tokenizer slot was
Verified on a device
512×512, 6 steps, CFG 1.0, Euler + Discrete, shift left empty, on a 15.6 GB phone. 651
tensors loaded, the image comes out clean, no engine warnings.
minimax_h3_image_pruned-Q2_K.gguf- 7.2 GBp-h3-image_text_encoder_int8_convrot.safetensors- 4.8 GBminimax_h3_image_vae_fp16.safetensors- 1.1 GB
Please read before reporting
Expect about 25 minutes for one 512×512 image. 13.4 GB of weights on a 15.6 GB device
means the diffusion steps are read from storage rather than computed - the log shows
available memory falling to 1.2 GB. Slow, not broken.
Two things that waste time if you get them wrong:
- Use the P-H3-Image text encoder, not the 32B one. 4.8 GB instead of 17 GB, and it
handles both text-to-image and reference-image editing - Use the MiniMax-H3-Image VAE. The MiniMax-H3 video VAE and the P-H3-Image VAE are
both incompatible and fail at decode
More steps do not help either; the model is trained on a six-step schedule.
中文说明
Ponko 是一个可离线运行的 Android AI 应用:对话(支持图片、文件、文档输入)+ 绘图 + 打标,
三者都能各自开一个 OpenAI 兼容 API。所有推理都在设备本地完成——除了可选的 App 内 LoRA
下载,任何功能都不需要联网。无遥测,数据留在你手机上。
这是预发布版。 它与正式版并存(包名 com.litertchat.app.beta)。
相对 2.1.3 改了什么
stable-diffusion.cpp 升级到上游 2026-11-13 的 master——79 个上游提交,ggml 一并跟上。
由此带来 MiniMax-H3-Image 和 P-H3-Image(#2324、#2272)。H3 视频本来就有,
缺的是 Sol-H3 VAE 的解码路径(#2317)。CHROMA 也终于有了自己的版本 id(#2237),
不再借用别人的。
其中对已有功能有实质影响的修复:hires 现在遵守你申请的步数(#2227)、
diffusers 命名的 SDXL 不带 ComfyUI 前缀也能识别(#2247)、
LoRA 标量保持 F32 并在需要时按 F32 合并(#2263、#2302)、
Krea2 的 Kohya LoRA 名字不再丢失(#2301)。
- 新家族
MiniMax-H3-Image / P-H3-Image:扩散模型 + Qwen3-VL 编码器 + Sol-H3 VAE。
同一个 checkpoint 也支持参考图编辑 - 新增
Text connector槽位,配 4B 编码器时需要。追加在槽位表末尾而不是放在llm
旁边,理由和当初的 tokenizer 槽位一样
已在设备上验证
512×512、6 步、CFG 1.0、Euler + Discrete、shift 留空,在 15.6 GB 手机上:
651 个张量加载成功,出图正常,引擎零警告。
minimax_h3_image_pruned-Q2_K.gguf— 7.2 GBp-h3-image_text_encoder_int8_convrot.safetensors— 4.8 GBminimax_h3_image_vae_fp16.safetensors— 1.1 GB
报告问题前请看
一张 512×512 预计要 25 分钟。 13.4 GB 权重放在 15.6 GB 内存的设备上,扩散的每一步
都是从存储里读数而不是在算——日志里可用内存掉到 1.2 GB。是慢,不是坏。
两个搞错就白等的地方:
- 文本编码器用 P-H3-Image 那个,不要用 32B 的。 4.8 GB 对 17 GB,且文生图和参考图
编辑都能用 - VAE 必须用 MiniMax-H3-Image 的。 MiniMax-H3 的视频 VAE 和 P-H3-Image 的 VAE
都不兼容,会在解码阶段失败
加步数也没用——这个模型是按六步调度的。