v1.4.1-beta2

简体中文

测试版，改动集中在实验性监测功能。未启用该功能的话与 v1.4.0 行为一致。
先挂个两三天，没出奇奇怪怪的Bug就推正式版

需要注意的行为变化

• 计数含义改为「通报次数」，默认每次访问都会通报，不再自动合并。定位这类会持续高频上报的权限，不设通报间隔的话通知会在几秒内被刷满。请在「监测设置 → 监测点设置」里给这类监测点设一个间隔。

新增

• 监测点级配置：「应用 + 权限」构成一个监测点，每个监测点可单独设置通报间隔、提醒方式（跟随全局／静默／弹窗）、通报内容（全部／仅被拒绝／仅被允许）。
• 新增「仅在应用不在屏幕上时通报」。判定依据是系统为该应用记录的进程状态，只有应用正显示在屏幕上才算前台，前台服务算作不在屏幕上。读不到该状态时照常通报，不会静默。
• 可监测的权限从 10 个扩展到全部 147 个，首次开启会说明噪音与 ROM 适配性两项风险。
• 新增「配置示例」页，列出常见场景对应的配置建议。
• 取消勾选某个权限后，它的监测点配置会保留，重新勾选时继续生效。

修复

• 监听的注册与停止没有串行化，可能造成重复订阅，或关闭后仍有监听残留在系统中。
• 旧版 Parcel 布局的回退解析判别条件不可靠，可能把「被拒绝」读成「被允许」。
• 事件只按包名匹配，其他用户空间（如私密空间）中同名应用的访问会混入同一条记录。
• 只注册到 started 监听时，被允许的长时访问会被整体丢弃。
• 常驻通知不再在不同通知渠道之间来回切换。
• 通知中过长的应用名不再把后面的权限名和计数挤掉。
• 系统服务重启后的恢复流程此前无法真正重新注册，现已可用。

AppOps 的读写方式没有改动，已保存的模板、历史和设置不受影响。已选择的监测应用与权限会保留。

English

A test build. The changes are confined to the experimental monitor; with that feature off it behaves like v1.4.0.

Behaviour change to be aware of

• Counts now mean "times reported", and every access is reported by default instead of being folded together. A permission that reports constantly, such as location, will fill the notification within seconds if no interval is set. Give those monitoring points a reporting interval under Monitor settings → Monitoring points.

New

• Per-point settings: an app and a permission together form a monitoring point, each with its own reporting interval, notification behaviour (follow monitor / silent / pop up), and outcome filter (everything / refused only / allowed only).
• New "only when off screen" option. It reads the process state the system keeps for the app; only the app being on screen counts as foreground, so a foreground service is still reported. If the state cannot be read, the access is reported rather than dropped.
• The list of watchable permissions goes from 10 to all 147. Turning that on explains the noise and ROM-compatibility risks first.
• New "Example setups" page describing common situations and what to set for them.
• Unpicking a permission keeps its monitoring point settings for when it is picked again.

Fixed

• Watch registration and teardown were not serialised, which could leave duplicate subscriptions or watches still registered after the monitor was switched off.
• The fallback for the older Parcel layout could not tell the two layouts apart reliably and could read a refusal as an allowed access.
• Events matched on package name alone, so an app with the same name in another profile, such as a private space, was folded into the same entry.
• Allowed long-running accesses were dropped entirely when only the started watch was registered.
• The ongoing notification no longer moves between notification channels.
• A long app name no longer pushes the permission and the count off the end of a notification line.
• Recovery after a system service restart could not actually re-register; it now can.

AppOps reads and writes are unchanged, and saved templates, history, and settings are unaffected. Selected monitoring targets are kept.

SHA-256 (AppOpsNext-v1.4.1-beta2.apk): 87a93079a2d635fc0916b2357f15ae4b1b0c00e85984de8835f99024f840d318