更新日志

各版本的对外更新内容(与 GitHub Releases 同步)

按版本记录每次对外发布的更新内容(与 GitHub Releases 的说明保持同步)。


zako3.17 更新日志#

修掉一个会打到所有「同时装了官方 Shizuku」的用户的启动问题,以及通知栏配对时端口可能丢失的隐患。versionCode 抬到 317 —— 这是为了进 F-Droid(它只比 versionCode),也顺带把版本名按惯例对回 3.17。

🔧 修复与优化#

  • 与官方 Shizuku 并存时启动失败、甚至互杀:本应用的服务进程原本也叫 shizuku_server,而 starter 在启动前会按进程名杀掉所有同名进程。官方 Shizuku 的服务进程正好同名,于是两种坏法都会出现 —— 对方以 root 运行时杀不动,starter 直接 fatal: can't kill … 退出;两边身份相同时,则会把对方的 server 悄悄杀掉。现在服务进程改名为 shizako_server,清理逻辑也改为只杀「cmdline 里同时包含本应用包名与服务类名」的进程,从旧版本升级上来的旧名字进程同样能被认出。README 承诺的「可与官方 Shizuku 共存」从这一版起才真正成立
  • 通知栏配对可能带着错误的端口去连接:端口和配对码以前共用同一个 extra key(paring_code),PendingIntent 又是先按 -1 建好、再靠 FLAG_UPDATE_CURRENT 就地改 extra。现在端口改用独立 key(pairing_port),每个端口各建一个 PendingIntent;收到的端口先校验 1..65535,不合法就不发起连接并直接说明原因,不会再出现「明明发现了 46499,却去连 0 号端口」
  • 连接前先确认配对服务还活着:系统「使用配对码配对设备」对话框一关,adbd 就把配对端口收回去,那之后再连只会得到 ECONNREFUSED。通知栏与分屏对话框两条路径现在都会在连接前探测端口,命中就明确提示「配对服务已停止监听(端口 N)」,并告诉你重开对话框,而不是笼统地报一句「连不上」
  • 配对流程补了现场日志:pairing reply received: port=…(端口有没有传到、传成了几)、pairing start: hosts=[…] port=…、resolved type=_adb-tls-pairing._tcp … listening=…,再遇到「配对连不上」时一眼就能定位是发现、端口传递还是连接环节的问题

🌍 English#

Fixes a start-up problem that hits everyone who also has the official Shizuku installed, plus a port hand-off flaw in notification-based pairing. versionCode is now 317 — required by F-Droid, which only compares version codes; the version name goes back to the numeric convention as 3.17.

  • Start-up failed — and could kill the other manager — when the official Shizuku was installed: our server process was also called shizuku_server, and the starter kills every process with that name before starting. With the upstream server running as root the kill fails and the starter exits with fatal: can't kill …; with both running under the same identity it silently killed Shizuku's server instead. The process is now shizako_server, and the starter only kills processes whose cmdline contains both our application id and our server class — which also recognises an old-name server left over from an upgrade
  • Notification-based pairing could connect with the wrong port: the port shared one extra key with the pairing code (paring_code), and the PendingIntent was created once with -1 and then "updated" via FLAG_UPDATE_CURRENT. The port now has its own key (pairing_port), each port gets its own PendingIntent, and a port outside 1..65535 aborts before any socket is opened instead of dialling port 0
  • The pairing port is probed before connecting: once the system "Pair device with pairing code" dialog closes, adbd releases that port and any later connect can only return ECONNREFUSED. Both the notification and the split-screen dialog now probe it first and say "the pairing service has stopped listening (port N) — reopen that dialog" instead of a bare "can't connect"
  • Better logs for pairing: pairing reply received: port=…, pairing start: hosts=[…] port=…, resolved type=_adb-tls-pairing._tcp … listening=…

zako3.16hp 更新日志#

修复 zako3.16 留下的问题:Root 激活广播必崩、配对在个别设备上连不上、配对每次尝试都会泄漏一个 socket 与一块原生密钥内存,以及低频恢复会永远空转而通知还在宣称「正在重试」;另外新增「简单 / 进阶」双模式,把大部分人用不到的功能收起来。 versionCode 仍为 316,只是 versionName 加 hp 后缀,可直接覆盖安装 zako3.16。

✨ 新增#

  • 简单 / 进阶双模式:有人反馈功能太多、一眼不知道该点哪儿。现在分两档,开关在首页服务器状态卡下面那张卡片上(整张卡可点)。简单模式下收起:底栏的日志 / 模块 / 控制台,工具箱的模块整组 / 控制台整组 / 实验室,以及设置里的底部栏、稳定性与自动化、API 日志;无障碍、激活、应用管理这些常用入口保留。选择会被记住 —— 这次开了进阶,下次打开还在进阶
  • 档位不是散在界面里 if 判断的:每个入口自带 FeatureLevel,由一处统一裁决。以后加功能只要标一下档位,不会出现「简单模式下还能点到」的破漏

🔧 修复与优化#

  • 实时磨砂现在拨了开关立刻生效:以前它只在 Activity 创建时读一次,所以必须在设置里拨完、退出 App、再重进才看得到效果。现在开关状态是运行时可观察的,拨完当帧就把快照层接上/关掉并同步底栏可见性,不用重建 Activity。顺带收紧了代价:非玻璃风格下不再开着整屏快照录制(那层离屏 RenderNode 每帧都会把内容重录一遍)
  • Root 激活不再崩溃(真机必现):用 Tasker / MacroDroid 发 START_ROOT(或 START 且上次是 Root 模式)时,App 必定崩溃 —— 回调跑在没有 Looper 的线程上却直接弹 Toast,抛出 Can't toast on a thread that has not called Looper.prepare()。更别扭的是崩溃发生在服务已经起来之后,所以现象是「服务起来了,App 却没了」。已改为切主线程弹提示。这条是公开的广播接口,已 root 的设备最容易踩到
  • 配对增加局域网地址兜底:此前只连 127.0.0.1;个别设备/ROM 上应用连不上自己的回环地址(有用户反馈:同一台设备上 Termux 与电脑都能配对,本应用却连接被拒)。现在先试回环,只有在连接立刻失败时才改用本机局域网 IPv4 重试;配对码错误、协议层失败仍然立刻报错,不会让你白等两轮
  • 配对不再泄漏资源:AdbPairingClient 实现了可关闭接口,但配对服务与配对对话框两处都从不关闭它——每次配对尝试(包括失败后的重试)都会泄漏两个文件描述符(原始 socket 与 TLS socket)以及一块原生内存,而那块内存里存着 SPAKE2 密钥的拷贝。现在配对流程自身负责清理,无论成功、失败还是中途异常都会回收
  • 建连阶段失败也会清理:此前若在建立 TLS 连接时就失败(端口不通、握手失败、读取超时),清理逻辑会被整段跳过;现在这类失败同样会销毁原生上下文
  • 重复销毁不再有风险:原生销毁入口补上空指针与重复调用两道防线,销毁后清空指针并抹掉密钥材料;「本端配对消息」为空的极端情况改抛具名错误,而不是崩溃
  • 低频恢复现在有出口:此前若上次是无线调试激活、但固定端口 5555 不通、又拿不到自动开启无线调试所需的权限,恢复逻辑会什么都不做却每 5 分钟唤醒一次,永远等不到成功,而常驻通知仍在显示「正在重试」。现在这种情况会停止重试,并把通知改为如实的「自动重连已放弃——请手动启动服务(或重新授权限 / 改用 Root)」;另外增加了约 1 小时的尝试上限,避免无限唤醒耗电
  • 更正 zako3.16 的措辞:下面 zako3.16 一节写的「每 5 分钟探测并拉起一次,直到成功」不再准确——现在低频恢复有明确出口。正常使用(能拉起的情况)行为不变
  • 配对日志可诊断:握手成功时会打印 Handshake succeeded via <host>:<port>,遇到「配对连不上」时看一眼日志就知道是否走了局域网兜底
  • 配对端口文案不再有歧义:无线调试页面顶部那个「IP 地址和端口」是连接端口,配对要用的是「使用配对码配对设备」对话框里显示的端口。此前输入框只写「端口号」、提示又说「按无线调试页面显示的配对端口填写」,很容易填成顶部那个;而填错的表现是握手阶段报证书校验失败(adbd 的连接服务会校验客户端证书,配对服务则不校验)。现在标签改为「配对端口」,提示与错误文案都明确指出两者的区别
  • 配对填错端口会当场拦下并自动纠正:配对时会同时探一遍连接端口;如果你填的正是它,会直接提示「这是连接端口,不是配对端口」,并在已知配对端口时自动换上去。另加一层恢复:若握手阶段失败、而 mDNS 另外探到了配对端口,会自动用那个端口重试一次 —— 这种情况多半就是填成了连接端口
  • 配对失败现在能看到原因:错误提示里附上「端口 · 异常类型」,截图就能说明问题;AdbPairClient 同时记录 pairing start、TLS handshake -> host:port、失败阶段与异常,不用再靠猜是「连不上」「握手失败」还是「协议层失败」

🌍 English#

Fixes problems left in zako3.16: every pairing attempt leaked a socket and a chunk of native memory holding key material, and low-frequency recovery could spin forever on some devices while the notification kept claiming it was retrying. Also adds a Simple / Advanced split so the features most people never touch get out of the way. versionCode stays 316 with an hp suffix on versionName, so it installs over zako3.16 directly.

  • Simple / Advanced modes: people said there were simply too many features. There are now two levels, switched from a card on the home screen (right under the server status card). Simple mode hides the log / modules / console tabs, the module, console and lab groups in the toolbox, and the nav-bar, stability and API-log entries in settings; accessibility, activation and app management stay. The choice is remembered — leave it on Advanced and it is still Advanced next time
  • The level is not decided by scattered if checks: every entry carries a FeatureLevel and one place decides. Adding a feature later means tagging it, and there is no way to accidentally leave it reachable in Simple mode
  • Live blur now applies the moment you flip the switch: it used to be read once when the activity was created, so you had to back out of the app and reopen it to see any effect. The switch is runtime-observable now: flipping it wires up (or tears down) the snapshot layer and the bar's visibility in the same frame, with no activity recreation. Also tightened the cost — snapshot recording no longer stays on when the style is not Glass
  • Root activation no longer crashes (reproducible on device): sending START_ROOT via Tasker / MacroDroid (or START in root mode) crashed the app every time — the callback ran on a thread without a Looper and called Toast directly, raising Can't toast on a thread that has not called Looper.prepare(). Worse, the crash happened after the server had already started, so the symptom was "the service came up, but the app vanished". The toast now runs on the main thread. This is a public broadcast interface, and rooted devices are the most likely to hit it
  • Pairing now falls back to the LAN address: previously it only connected to 127.0.0.1; on some devices/ROMs an app cannot reach its own loopback address (reported: on the same device Termux and a PC pair fine, while this app gets connection refused). It now tries loopback first and only retries with the device's LAN IPv4 when the connection fails immediately; a wrong pairing code or a protocol failure still fails right away rather than making you wait through a second attempt
  • Pairing no longer leaks: AdbPairingClient is closeable, but neither the pairing service nor the pairing dialog ever closed it — every attempt, including every failed retry, leaked two file descriptors (raw socket and TLS socket) plus native memory holding a copy of the SPAKE2 key. The pairing flow now cleans up after itself on success, failure and mid-flight exceptions alike
  • Cleanup also happens when the connection phase fails: previously a failure while establishing TLS (unreachable port, handshake failure, read timeout) skipped cleanup entirely; the native context is now destroyed on those paths too
  • Repeated destruction is safe: the native destroy entry point now guards against null and repeated calls, clears the pointer and wipes the key material afterwards; an empty local pairing message raises a named error instead of crashing
  • Low-frequency recovery now has an exit: if the last activation was wireless debugging, the fixed port 5555 is gone and the permission needed to re-enable wireless debugging automatically is missing, the recovery loop used to do nothing while still waking every 5 minutes — never succeeding, while the persistent notification kept saying it was retrying. It now stops and reports honestly: "Can't auto-reconnect — please start the service yourself (or re-grant permission / use root)". A cap of roughly one hour of attempts prevents endless wake-ups
  • Correction to the zako3.16 wording below: the "every 5 minutes until it succeeds" phrasing in the zako3.16 section is no longer accurate — recovery now has a defined exit. Behaviour is unchanged in the normal case where a relaunch can succeed
  • Diagnosable pairing log: on a successful handshake it logs Handshake succeeded via <host>:<port>, so a "pairing won't connect" report immediately shows whether the LAN fallback was used
  • A wrong pairing port is now caught and corrected on the spot: pairing also probes the connect port; if the port you entered is that one, it says so directly and switches to the pairing port when known. There is also a recovery path: if the handshake fails and mDNS had already found a different pairing port, it retries with that one automatically — which is almost always the connect-port case
  • Pairing failures now tell you why: the error message carries port · exception type, so a screenshot is enough; AdbPairClient logs pairing start, TLS handshake -> host:port, the failing stage and the exception, so "cannot connect", "handshake failed" and "protocol failure" are no longer indistinguishable

zako3.16 更新日志#

彻底治理仿冒风险,并大幅加固后台保活与断线重连。如果你在任何第三方站点见过 "Shizako+" 之类的改名重打包版,请务必用本版校验你手里的安装包。

🛡️ 仿冒治理三件套#

  • GitHub 版不再携带上游身份占位包:此前 GitHub 版 APK 内嵌一个占用上游包名 moe.shizuku.privileged.api、应用名为 "Shizuku" 的空壳子包——它逐字违反上游 Apache-2.0 §6 的附加条款,而且任何人解包 APK 跑一次 aapt2 dump badging,都会把这份官方构建看成一份「重打包改名的仿冒品」。该子包、构建任务与相关界面入口现已全部移除
  • 应用内签名自检(只警告、不阻断):启动时读取当前安装包的签名证书 SHA-256,与官方发布指纹 515BAF0C…9F9C8A 比对;不符会弹警告并引导打开官方发布页核对、一键复制自己的指纹。仿冒品能抄界面、抄包名,但抄不走发布私钥
  • 签名指纹公示:「设置 → 关于」新增签名指纹卡,展示当前安装包自己的完整证书指纹与校验状态(官方签名 / F-Droid 签名 / 无法确认),点按复制;F-Droid 版由 F-Droid 重签,指纹不同属正常,应用内会如实标注

🔁 稳定性:保活与断线重连三级策略#

  • 快重试 → 低频恢复:服务 binder 死亡后 3 秒快重试 ×3;仍失败则进入低频恢复模式,每 5 分钟探测并拉起一次,直到成功——旧版重试 3 次失败后就永久放弃,只剩干等
  • 冷恢复:手机重启 / 看门狗被闹钟或 shell 小看门拉回时,binder 从未上报、死亡回调不会来——新版会主动探测并按上次激活方式(root / adb)尝试拉起服务
  • 手动停止受尊重:修复「开着保活点停止服务,3 秒后服务又被拉起来」——现在所有停止入口(首页状态卡、快捷开关、Tasker)都会通知看门狗,自动重连压制 30 分钟,常驻通知如实显示「服务已被手动停止」
  • 通知状态更透明:新增「低频重试第 N 次」状态,随时知道她在抢救还是在岗

🌍 English#

Closes the clone/impostor risk for good and hardens keep-alive & reconnect. If you ever saw a renamed repack like "Shizako+" on third-party sites, use this build to verify what you actually installed.

  • No more upstream-identity stub in the GitHub build: the APK used to embed a placeholder sub-package occupying the upstream package name moe.shizuku.privileged.api with the app name "Shizuku" — a verbatim violation of the upstream Apache-2.0 §6 additional terms, and, to anyone running aapt2 dump badging on the APK, indistinguishable from a repackaged, renamed counterfeit. The module, its build tasks and all UI entries are removed
  • In-app signature self-check (warn-only): on launch the app reads its own signing certificate SHA-256 and compares it with the official release fingerprint 515BAF0C…9F9C8A. A mismatch shows a warning that points to the official release page and lets you copy your own fingerprint. A clone can copy the UI and the package name, but not the release private key
  • Fingerprint disclosure: Settings → About now shows the full certificate fingerprint of the APK you actually installed, with its verification status (official / F-Droid / unverified); tap to copy. F-Droid builds are re-signed by F-Droid, so a different fingerprint is expected and labeled as such
  • Three-tier reconnect: 3-second quick retries ×3 on binder death, then a low-frequency recovery mode (probe and relaunch every 5 minutes until it succeeds) — the old build gave up for good after 3 attempts
  • Cold recovery: after a reboot or when the watchdog itself is pulled back by the alarm or the shell daemon, the binder never reports and no death callback fires — the new build probes on its own and relaunches via the last activation method (root / adb)
  • Intentional stops are respected: fixes "stop the service and the watchdog pulls it back 3 seconds later" — every stop entry (home status card, quick settings tile, Tasker) now notifies the watchdog, suppressing auto-reconnect for 30 minutes; the persistent notification honestly shows "stopped by you"
  • More transparent notification state: a new "low-frequency retry #N" status tells you whether she is rescuing or on duty

zako3.15 更新日志#

修复「配对明明失败,界面却显示已配对」,以及配对失败时没有任何提示的问题。

🔧 修复与优化#

  • 配对状态不再谎报:此前只要点过一次配对(配对码输错、端口不通、中途取消都算),本地就会留下一把无线调试密钥,激活页据此显示「已配对」——而设备根本不认识这把密钥。现在密钥只在配对真正成功时才落盘,并单独记录一条成功记录,「已配对」以这份记录为准
  • 配对失败会说明原因:此前配对失败时客户端只回一个 false,界面什么也不显示,用户看到的就是「转一下圈,然后什么都没有」。现在区分配对码错误或已失效、无法建立加密连接(端口或配对码已过期)、配对被设备中断三种情况,并在对话框与通知栏给出对应的下一步动作
  • 密钥生成失败不再卡住通知:通知栏配对路径遇到密钥生成失败会直接退出,通知永远停在「配对中」;现在会明确提示失败
  • 状态自动恢复:从旧版本升级、本地已有可用密钥的用户,服务成功启动后会自动补上配对记录,不必重新配对;「忘记配对」现在会把成功记录一并清除

🌍 English#

Fixes "pairing failed but the app says it is paired", and the total lack of feedback when pairing fails.

  • Pairing state no longer lies: previously a single pairing attempt — wrong code, unreachable port, cancelled halfway — left a key on the device, and the activation page reported "paired" based on that key alone, even though the device had never seen it. The key is now persisted only when pairing actually succeeds, and "paired" is based on that success record
  • Pairing failures now explain themselves: the client used to report failures as a bare false, so the UI showed nothing at all. A wrong or expired pairing code, an expired port or pairing code (secure connection refused) and an interrupted pairing are now distinguished, with the matching next step shown in both the dialog and the notification
  • Key generation failure no longer jams the notification: the notification-based pairing path used to return silently, leaving the notification stuck on "pairing"; it now reports the failure
  • Automatic recovery: users upgrading from an older version who already hold a working key get the pairing record written automatically once the service starts successfully, so re-pairing is not needed; "Forget pairing" now clears the success record too

zako3.14 更新日志#

针对「搜不到配对服务」的场景修复,GrapheneOS / 华为 / 鸿蒙用户请务必升级。

✨ 新功能#

  • 激活页补回「手动连接端口」入口:跳过配对与服务发现,直接连本机上的 ADB 端口(适用于搜不到配对服务、或 adbd 已经监听在固定端口的设备)

🔧 修复与优化#

  • 无线调试配对:配对对话框的端口输入框现在始终可见可手输。此前端口/配对码输入框只在 mDNS 发现到端口之后才渲染,而 mDNS 走组播——GrapheneOS 开启 VPN 时组播不会送进应用,华为 / 鸿蒙部分机型也会拦截,这些设备上对话框会一直转圈、连输入框都没有,用户无路可走。现在自动发现只负责预填端口,6 秒无结果即转为手动输入引导(并解释原因)
  • 启动服务:mDNS 拿不到无线调试端口时,回退到本机已经存活的 ADB TCP 端口,不再静默返回(此前这类设备上点「启动服务」没有任何反应)
  • 兼容性占位包:安装 / 卸载失败时列出全部三条通道(Shizako server、root、ADB)各自的失败原因。此前只上报最后一条通道的错误——root 可用而 server 通道失败时,界面上会显示与自己无关的 ADB 报错,排查方向完全被带偏

🌍 English#

Fixes for devices where the pairing service cannot be discovered — GrapheneOS / Huawei / HarmonyOS users should upgrade.

  • New: a "connect to a port manually" entry on the activation page — skips pairing and service discovery and connects straight to an ADB port on the device
  • Fixed: the port field in the pairing dialog is now always visible and editable. Previously the port / pairing-code fields were only rendered after mDNS had discovered a port; mDNS multicast is blocked on GrapheneOS with a VPN enabled and on some Huawei / HarmonyOS devices, so the dialog spun forever with no input fields at all. Discovery now only pre-fills the port, and after 6 seconds it falls back to a manual-entry prompt that explains why
  • Fixed: when mDNS yields no wireless-debugging port, starting the service now falls back to a live ADB TCP port on the device instead of returning silently
  • Fixed: the compatibility stub now reports the failure reason of all three channels (Shizako server / root / ADB) instead of only the last one, which used to show an unrelated ADB error while root was actually working

zako3.13 更新日志#

授权稳定性修复 + F-Droid 版本上线。

✨ 新功能#

  • 新增 F-Droid 专用版本(版本名带 -f 后缀),已提交 F-Droid 上架:该版本关闭自动更新与更新检查、只走官方 GitHub API(不含第三方反代)、隐藏「一键注入」与 AI 解释入口、不打包兼容性占位包

🔧 修复与优化#

  • 应用管理:修复用 root 激活服务后,给某个应用授权再刷新,该应用从已授权列表里消失(服务端授权记录漏写了包名;旧配置文件里已经写坏的记录也会一并治好,不需要重新授权)
  • 权限授予:修复用官方 dev.rikka.shizuku:api 构建的应用(只声明上游权限名的那种)授权 / 撤销时会出错的问题
  • 启动服务:修复在服务起来后 3 秒自动关窗之前手动返回时崩溃(Fragment not associated with a fragment manager)
  • 关于页:去掉「二次开发」措辞,并修掉「基于 Shizako」这个自指文案

🌍 English#

Authorization stability fixes, plus the F-Droid build.

  • New: a dedicated F-Droid variant (-f version suffix), submitted to F-Droid: self-update and the update check are turned off, only the official GitHub API is used (no third-party mirrors), the one-click injection and AI explain entries are hidden, and the compatibility stub is not packaged
  • Fixed: after activating the service with root, granting an app permission and refreshing the list made that app disappear from the granted list (the server wrote the authorization record without a package name; records already broken in the old config file are healed too, no re-grant needed)
  • Fixed: granting / revoking permissions for apps built against the official dev.rikka.shizuku:api (which declare only the upstream permission name)
  • Fixed: a crash when leaving the "start service" page within the 3-second auto-close window (Fragment not associated with a fragment manager)
  • About: wording cleanup

zako3.12 更新日志#

激活可靠性大修 + 全面性能优化,强烈建议所有用户升级。

✨ 新功能#

  • 每次打开 App 自动检查更新,发现新版本就地弹出可下载的对话框(不再只依赖通知栏)
  • 更新检查自动挑选可用源:GitHub API 被网络拦截时自动切换镜像,国内网络同样能收到更新

🔧 修复与优化#

  • 激活:
  • 修复「电脑 ADB」激活必失败(启动命令缺少 APK 路径参数)
  • 修复 Dhizuku 一键激活必失败(命令带了电脑端前缀,却在设备上执行)
  • 修复看门狗 / 开机自启 / 快捷磁贴重启服务时用错启动方式
  • 修复无线调试配对可能永久卡在「配对中」(补连接与读取超时)
  • 修复服务端一处空指针:同一进程二次连接时应用会永久收不到服务,且界面看不出异常
  • 修复共享 uid 下只有第一个包能收到服务的漏推问题
  • 首次引导:修复 Android 7.x 闪退、Android 11/12 点激活无反应、倒计时被转屏重置等 17 处问题
  • 更新检查:改为按版本号逐段比较,只认「确实更新」,避免把旧版本当作新版本推送
  • 问题反馈:修复 #5(Dhizuku 缺少开关)、#6(深色模式黑字)、#7(模块搜索不到)
  • 性能与耗电:
  • 启用 Baseline Profile:冷启动实测提升约 15% ~ 20%
  • 后台保活轮询 12 秒 → 45 秒,去掉无用的周期性唤醒,明显降低耗电与闪存写入
  • 应用列表图标改为真正命中缓存(此前每次新建项都走主线程加载)
  • 界面噪点纹理全应用共用,窗口底图内存减半

🌍 English#

Activation reliability overhaul + broad performance work — strongly recommended for all users.

  • New: check for updates on every app launch, with an in-app download dialog; automatic mirror fallback when the GitHub API is blocked by your network
  • Fixed: "Computer ADB" and one-tap Dhizuku activation never worked; watchdog / boot / quick-tile restarting the service with the wrong launch method; wireless pairing could hang forever; a server-side NPE that left an app permanently without the service; shared-UID binder push skipping all but the first package
  • Fixed 17 issues in the first-run setup wizard (Android 7.x crash, no-op activation on Android 11/12, countdown reset on rotation)
  • Update check now compares version numbers instead of string inequality (no more downgrade prompts)
  • Fixed issues #5 / #6 / #7
  • Performance: Baseline Profile enabled (~15–20% faster cold start), background keep-alive polling 12s → 45s, real icon-cache hits, shared noise texture, half the background bitmap memory

zako3.01-hp 更新日志#

紧急修复版,强烈建议所有用户升级。

  • 修复「激活」可能一直转圈、卡住无反应的问题:新增超时保护,未完成配对时会明确提示
  • 修复启动失败时误关「无线调试」开关的问题(失败后可立即重试)
  • 修复控制台列表弹窗偶发闪退
  • 一并加强:「分屏配对」对话框(不用电脑也能走完配对流程)+ 持久 TCP 模式(默认开启,断网也能一键启动)

zako3.01 更新日志#

玻璃 / Material 3 双风格领衔:zako3 系列首个版本,整套系统全面重做,外加一整套新玩具。更新后建议先逛逛「工具箱」和「设置」~

✨ 新功能#

  • 玻璃 / Material 3 双风格全新界面:KernelSU 风格重做,一键切换、深浅色与动态取色全适配
  • 一站式激活:Root / 无线调试 / 电脑 ADB / Dhizuku 一页搞定;已配对可一键启动
  • 全新工具箱:模块 / 控制台 / 无障碍管理器 / 实验室 / 推荐应用
  • 首次引导全面重构:七页五步,内嵌配对指引
  • 更新欢迎页:老用户升级后首次打开可见

🔧 修复与优化#

  • 修复动态取色下部分按钮 / 图标颜色不同步
  • 修复主页与激活页状态显示不一致
  • 滚动、切页等性能与动画细节优化