Skip to content

Ponko v2.1.2

Choose a tag to compare

@visitor257 visitor257 released this 08 Nov 08:27

中文说明  ·  跳到末尾  ·  Jump to end

Ponko 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.

Installs over 2.1.1. Models, settings and LoRA selections carry across.

What's new

More than one LoRA at a time, each with its own weight

Requested in #4. The app applied exactly one
LoRA: you could keep any number of .safetensors in the list and switch between them, but
only the selected one was loaded, and the strength was a single value shared by whatever was
loaded.

The LoRA list is now multi-select, and each ticked entry shows its own weight. The txt2img and
img2img parameter cards grow one weight field per selected LoRA, labelled with the file
name - so three LoRAs means three rows, not one global slider that can only mean one thing.
Both pages edit the same values and re-sync when you switch between them.

Nothing in the engine had to change. sd.cpp already takes a list of LoRAs with a multiplier
each; the bridge from Kotlin to native was passing one. The work was plumbing, but with two
places worth being careful: paths and weights are collected in pairs so a skipped entry cannot
shift a weight onto its neighbour, and the path strings are materialised before any pointer
into them is taken.

Three details that are decisions rather than mechanics:

A weight of 0 drops that LoRA before it reaches the engine. sd.cpp would otherwise load the
entire file and multiply the result by zero.

Turning the LoRA switch on with nothing selected selects the first file, which is what the
old single-slot code did implicitly. "On but doing nothing" would have read as a regression.

An existing user's global strength is migrated onto the LoRA they had selected, so a tuned
0.8 does not silently become 1.0.

One expectation to set: two LoRAs at 1.0 usually fight rather than stack - styles cancel,
fine detail goes muddy. 0.5-0.8 each is the usual starting point. Every extra file also costs
memory and load time.

Known limits

Unchanged from 2.1.0 — see that release's notes. The two configurations still untested are
PixArt Alpha (the 512 variant) and MOSS-Image at its recommended CFG.

中文说明

Ponko 是一个可离线运行的 Android AI 应用:对话(支持图片、文件、文档输入)+ 绘图 + 打标,
三者都能各自开一个 OpenAI 兼容 API。所有推理都在设备本地完成——除了可选的 App 内 LoRA
下载,任何功能都不需要联网。无遥测,数据留在你手机上。

可直接覆盖 2.1.1 安装。模型、设置和 LoRA 选择都会保留。

新增:可同时挂多份 LoRA,各自独立权重

来自 #4 的请求。原来只挂一份:列表里可以放任意多个
.safetensors 并切换,但同时只有一个会加载,强度是全局一个值。

现在列表是多选,选中的条目各自显示自己的权重。文生图与图生图的参数卡里,每选中一份就多一行
对应的权重输入框
,标签是文件名——选三份就是三行,而不是一个只能表达一个值的全局滑杆。
两页编辑同一份数据,切页时自动同步。

引擎完全没改。sd.cpp 本来就接受「一组 LoRA、各自带 multiplier」,是我们的 Kotlin 到 native
那层只传了一个。所以这是接线工作,但有两处要小心:路径与权重必须成对收集(否则跳过的条目会让
权重错位到别人身上),以及字符串要先全部落地再取指针(vector 扩容会让指针失效)。

三处属于判断而非机械的部分:

权重填 0 会在下发引擎前就丢掉这一份。否则 sd.cpp 会把整个文件加载完再乘 0。

打开 LoRA 开关但一份都没选时,自动选第一个——老的单槽代码隐式就是这么做的,
改成"开着却没反应"会被当成功能坏了。

老用户那个全局强度会迁移到他当时选中的那一份上,调好的 0.8 不会悄悄变回 1.0。

一点预期要提前说:两份都设 1.0 通常是互相打架而不是叠加——画风互相抵消、细节变糊。
一般各自 0.5~0.8 起步。每多挂一份,内存和加载时间都会增加。

已知限制

与 2.1.0 相同,见那一版的说明。仍未验证的两项是 PixArt Alpha(512 变体)和 MOSS-Image
在其推荐 CFG 下的表现。