Andee lives on your phone or Mac and uses any app like you do—no integrations, no root, any model; memory and passwords never leave your device | Andee 住进你的手机或 Mac,像你一样操作任何 App——无需集成、无需 Root、支持任意模型,记忆和密码绝不离开设备。
docs: no Chinese characters in any English-facing markdown
booboosui4634d2c8e1a7
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 0823782..61c9deb 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -39,7 +39,8 @@ the reader to build one — see *Added* and `docs/releases/v0.3.2.md`.since a dark tablet on a bedside table should not be listening all night, but the screen being off isalso the normal state of a phone in a pocket, so it meant the assistant could not be called from theone place a person actually keeps their phone. The gate now asks `wakeListeningAllowed()` — *the- screen is on, or the user left 锁屏时也听 on* — and that setting **defaults to on**. Its cost is stated+ screen is on, or the user left the "listen while locked" row on* — and that setting **defaults to+ on**. Its cost is statedon the row that flips it rather than left for the status bar to mention: the microphone stays open,and so does the system's recording indicator.Woken with the keyguard up, Andee can hear and answer — `tts.speak` needs nothing from the screen —@@ -65,14 +66,15 @@ the reader to build one — see *Added* and `docs/releases/v0.3.2.md`.Three frames is a click, a tap on the tablet's edge, or the recorder's own first read, so the segmentstarted on the hardware rather than on the person. A segment that starts early comes out long anddirty and, past `MAX_FRAMES`, was **dropped in silence** — the caller's latch never counted down and- the card sat on 听着… for the rest of the window. That is the second and third try. The fix slows the+ the card sat on "listening…" for the rest of the window. That is the second and third try. The fix slows thedecision down without throwing audio away: `START_FRAMES` 3 → 8 (80 ms) so a transient cannot open asegment, and `PREROLL_FRAMES` 15 → 30 (300 ms) so the onset is still in the ring when the decisionlands. Delaying a decision is free; discarding the audio is not — which is why there is deliberatelyno warm-up that drops the first 200 ms. The obvious fix was proposed and withdrawn: a user who tapsand speaks immediately would lose exactly the syllable the ring exists to protect.- **Five of the character's faces now run along the bottom of both cover images**- (`images/cover*.png`, `images/social-preview*.png`), one word under each — 听 看 想 做 说. They are+ (`images/cover*.png`, `images/social-preview*.png`), one word under each — Listen, Look, Think,+ Act, Speak. They arethe app's own illustrations rather than drawings made for the web, and they are the *gesture* moods,the set the web renderer cannot draw because they use props — so this is the first place the covershows the character instead of describing it. The row is confined to the left column by the head's own@@ -102,9 +104,9 @@ the reader to build one — see *Added* and `docs/releases/v0.3.2.md`.### Fixed-- **The enrolment prompt appeared before the microphone existed.** 现在说吧 was set on the tapper's+- **The enrolment prompt appeared before the microphone existed.** The "now speak" prompt was set on the tapper'sthread, before a recorder existed, so the user was invited to speak into a microphone that had not- started. It now moves after `mic.start()` returns: the card reads 正在听… for the 100–300 ms the+ started. It now moves after `mic.start()` returns: the card reads "listening…" for the 100–300 ms therecorder takes to come up, and the prompt appears once something is listening. Nothing is taken fromthe user to pay for it.- **The wake threshold was anchored on the worst take rather than the closest.** `thresholdFor` was@@ -160,11 +162,11 @@ oversight later.the model composes stayed in the night palette. That fix was on the table and was turned down onpurpose — a page's look is the model's business, not ours. Two things stay, and neither is a matterof taste: the `<meta viewport>`, because `HtmlActivity` sets `useWideViewPort` and a page without- one is laid out at desktop width and scaled down, and the ~110×44 px the ✕完成 pill occupies in the+ one is laid out at desktop width and scaled down, and the ~110×44 px the Done pill occupies in thetop-right corner, because that pill is ours. **The cost is on the record**: for the small models thisruns against, that description was the only lever on page quality, and nothing enforces any morethat a generated page reads as part of Andee.-- **The local LLM endpoint and model follow the UI language.** The 本机 tab's two LLM rows already had+- **The local LLM endpoint and model follow the UI language.** The on-device tab's two LLM rows already hada hint that doubled as the value a blank row resolves to, and both were hardcoded to DeepSeek —self-consistent for a Chinese card and wrong for an English one. The cheapest possible fix, changingonly the hint text, is the worst version of it: the box would advertise `https://api.openai.com/v1`@@ -176,14 +178,14 @@ oversight later.because its model belongs to the hosted backend and an English build inventing `gpt-4o-mini` therewould name a model CodeFlying does not serve.- **Errand trips from the check card are handed to the page instead of made by it**, so the list- survives the trip. On the check *page* tapping a row's 处理 sent the user to Settings and coming back+ survives the trip. On the check *page* tapping a row's fix button sent the user to Settings and coming backlanded on the list; from the check *card* the same three taps ended on the desktop with a ball in thecorner, because the card was closed and the assistant folded before the destination launched — whichdoes clear the screen, since an overlay outranks every Activity, but throws the list away: a windowgets no `onResume`, and the destination went out with `FLAG_ACTIVITY_NEW_TASK` into a task of itsown, so back from Settings had nowhere of ours to return to. `SelfCheckUi.onErrand` (was`onYieldScreen`) now hands the host the Intent and lets the host say whether it can carry it.- `Fix.Grant` goes through the same door, so 允许 on 麦克风 / 弹出通知 stops ending on the launcher too.+ `Fix.Grant` goes through the same door, so Allow on the microphone and notification rows stops ending on the launcher too.- **The prop-and-pose layer is on every look now**, not just Andee — stars, a heart, a shield, a sweatbead, the sliced lid, and the idle life that lets a look wear its own expressions and nap whilenothing is happening. The argument for keeping it to one look was that the others had been tuned@@ -211,7 +213,7 @@ oversight later.judgement about when to speak, and limits, all of which happen in the time you did **not** ask foranything.- **The English README no longer contains a single Chinese character** (`\p{Han}` returns nothing): the- language badge, five look names, a dozen `([中文](…))` links, the `(中文)` markers on the CodeFlying+ language badge, five look names, a dozen Chinese-language links, the language markers on the CodeFlyingsites and a button quoted in Chinese. The Chinese README keeps its own language.### Fixed@@ -221,7 +223,7 @@ oversight later.persistent notification that is the way back to it, and every reminder `Scheduler` fires. Thecodebase half knew: `Scheduler` carries a comment blaming this permission for its own failure tonotify, and nothing anywhere tested the claim. The row that looked like it covered this does not —- 通知使用权 is the notification *listener*, which can be granted and green while every notification+ The notification-access row is the notification *listener*, which can be granted and green while every notificationthe app sends disappears. Two things this needed beyond a catalog entry: `Perm.api`, because onAPI 32 and below the permission does not exist and `checkSelfPermission` answers **denied** foranything it does not know, so an ungated row would report a missing permission on every Android 12@@ -317,7 +319,7 @@ matter, because a ROM that revokes accessibility now costs one capability insteaall; the new address resolves outside the mainland and retires that particular trap. It does notretire the other one: a domain still has to resolve *and* serve 443, and a fresh record is noteverywhere at once. Measured while making the move, `1.1.1.1` still answered `NXDOMAIN` while- `223.5.5.5` already had the address — on the wrong resolver that reads as 查不到 on the 版本 row,+ `223.5.5.5` already had the address — on the wrong resolver that reads as "not found" on the version row,which is the intended failure rather than a fault to report. The service itself was checked beforethe switch: the new host answers `GET /api/version` with the same envelope, and the same `data`fields the client parses.@@ -326,7 +328,7 @@ matter, because a ROM that revokes accessibility now costs one capability insteaused to hand the screen to the assistant as soon as it could draw one, which happens on the *first*of those returns, so the list was taken away after row one. On a page whose whole job is to walksomebody down a list, the user is the only one who knows when the list is finished. Closing it with- 完成 puts the assistant back. Two surfaces fighting for the screen was the real bug underneath and+ the Done button puts the assistant back. Two surfaces fighting for the screen was the real bug underneath andit stays fixed by the same move: nothing unfolds a card while the page is up.- **Closing a page puts the assistant back at full size, unconditionally.** The fold that makes roomfor a page is ours — our card is a fullscreen opaque overlay and would cover it — so undoing it is@@ -365,12 +367,12 @@ matter, because a ROM that revokes accessibility now costs one capability insteapainted over it. Two things put it there, both in the body's birth: `window.setCompact(false)`, and`window.show()`, which is subtler — this window is fullscreen *even when the ball is compact* andswallows the touches it does not use, so a page with a ball in the corner is a page whose buttons- cannot be pressed (measured: 完成 did nothing). Telling a fresh launch apart from a return needed+ cannot be pressed (measured: the Done button did nothing). Telling a fresh launch apart from a return needed`SelfCheck.isPageOpen`, written down in the prefs file the startup check already uses. The startupself-check card is skipped while the page is up as well, because that page *is* the list.- **A just-fixed row stops showing as red when the card resumes.** The card's own rows send the userout to a system screen and the only thing that happened on the way back was a language comparison,- so a row the user had just fixed stayed red until they found 重新检查 — and a stale red row reads as+ so a row the user had just fixed stayed red until they found "check again" — and a stale red row reads as"the fix did not take". An Activity gets a resume callback and an overlay does not, which is whythis is a change to one host rather than to the list; it is local-only on purpose, because theprobes hold the card open for seconds. The first resume is skipped (a full pass just ran), the@@ -420,16 +422,16 @@ in the direction that made the model act on a grant nobody had given.`stopEverything()`, reused rather than reimplemented, so the single tap and the triple tap cannotdrift into two different stops and the hub gets its `task.stop` either way. It is guarded on`dispatcher.isTaskActive()`: on an idle ball there is nothing to stop, and the call would still- clear a pending 继续修改, tell the hub to stop, and flash 已停止 ahead of 听着… — three side effects+ clear a pending "keep editing", tell the hub to stop, and flash "stopped" ahead of "listening…" — three side effectsfor a tap that only ever meant "listen". Triple-tap still stops, and is still the *immediate* stop,because a single tap has to wait out the double-tap window before it knows it is not the first oftwo. No gesture moved and no string changed: what a tap *does* depends on what is running, which isnot something a line of text can say. Verified on device (HONOR AMM-AN00) — an idle tap listens- without flashing 已停止.+ without flashing "stopped".- **A device with no conversation is offered ready-made scenes instead of a dead line.** It used to- show 还没有对话 and nothing under it. There is nothing to be helpful *about* yet, and a ball in the+ show "no conversation yet" and nothing under it. There is nothing to be helpful *about* yet, and a ball in thecorner has taught a newcomer nothing about what the thing does, so the one moment this app can be- proactive without being early went unused. The card now shows a hint line — 告诉我,或者选一个 —+ proactive without being early went unused. The card now shows a hint line — "tell me, or pick one" —then a bubble per preset from `ScenePresets`, each labelled with the scene's name and carrying asentence the user could have said: the name is what a person picks between, the sentence is exactlythe part a newcomer cannot invent. Both are fields of one `ScenePresets.Text`, so a bubble cannot@@ -453,7 +455,7 @@ in the direction that made the model act on a grant nobody had given.what the model reasoned, and what each request cost in prompt tokens — was already in`files/brain_trace.jsonl` and reachable only with `run-as`. The new page is built from thoserecords and opened through `HtmlActivity`, which is where folding the card, hanging the ball off- the ledge and the 完成 pill were already solved. Long-press because the other two gestures on a row+ the ledge and the Done pill were already solved. Long-press because the other two gestures on a roware taken — a single tap opens a page row's page, a double tap reads a message fullscreen — and thetwo detectors had to become **one**, because `setOnTouchListener` replaces rather than chains, so asecond one would have silently killed the first. **The row and its log are joined by@@ -503,7 +505,7 @@ in the direction that made the model act on a grant nobody had given.the same reason, so this joins them — and only when `confirm=true`, because the first call is thescript the brain reads back and that one belongs in the card.- **Both READMEs gained a one-click build page and had its likely-reading fixed.** The nav and the- CodeFlying paragraph now point at the `/andee` page — describe the app, tap 立即打包, get a+ CodeFlying paragraph now point at the `/andee` page — describe the app, tap the build button, get apre-configured package with a QR code — and the "any app" feature line was reworded in bothlanguages, because "not a list of integrations" was being read as a claim about integrations thisapp has rather than a claim about aim. The page itself is a separate service with no direct@@ -513,13 +515,13 @@ in the direction that made the model act on a grant nobody had given.- **The prompt's rule about the system permission sheet was wrong, and is now the measured one.** Itsaid a system permission sheet "does not take a tap you inject", and that turned out to be false.- With the card folded, an injected tap on 「始终允许」 really does grant: `READ_CONTACTS` went- false → true, and one tap on 「本次使用允许」 produced an `ACCESS_FINE_LOCATION` carrying `ONE_TIME`,+ With the card folded, an injected tap on "Always allow" really does grant: `READ_CONTACTS` went+ false → true, and one tap on "Allow this time" produced an `ACCESS_FINE_LOCATION` carrying `ONE_TIME`,a flag only that button can set. The earlier four failures had one cause between them and it was ourown card eating the touch, not the sheet refusing it. So the rule changes from "you cannot press it"to **"you cannot read it, so do not aim at it"**: the sheet exposes no accessibility elements atall, so any tap is blind, and the button at the bottom of this particular screen is- 「禁止后不再提示」, which nothing can undo. That is the real reason this step stays the user's, and+ "Deny and don't ask again", which nothing can undo. That is the real reason this step stays the user's, andit is a reason that survives being measured. `LocalPrompt` §0's `type_text`-only rule is stated asthe general one — a tool saying it pressed something is not the thing being done — and §1's list ofgenuine exceptions gains the sheet, which is worth naming because putting it on screen is the whole@@ -535,33 +537,33 @@ in the direction that made the model act on a grant nobody had given.instructions, finds nothing, and concludes the app is broken rather than the text.- `check_detail_brain_key_missing`, `check_detail_brain_hub_missing` and `brain_no_key` all said- **⚙ → 「大脑」 / "Brain"**. The section header is `settings_section_brain`, which reads- **「后端」 / "Backend"** — there is no label containing 大脑 in the settings card at all. The- 火山 tab names use 大脑 only in prose ("the brain lives on a hub you run yourself"), never as a+ **⚙ → "Brain"**. The section header is `settings_section_brain`, which reads+ **"Backend"** — there is no label containing that word in the settings card at all. The+ Volcengine tab names use it only in prose ("the brain lives on a hub you run yourself"), never as adestination.- - `check_detail_voice_key_missing` said **⚙ → 「语音(火山引擎)」 / "Speech (Volcengine)"** — a- section that no longer exists. The Volcengine rows were moved into 后端 → 本机, and+ - `check_detail_voice_key_missing` said **⚙ → "Speech (Volcengine)"** — a+ section that no longer exists. The Volcengine rows were moved into Backend → on-device, and`settings_section_voice` / `settings_section_voice_key` are still in both string files but- referenced by nothing. The path is now the same **后端 → 本机** as the two brain keys, which is+ referenced by nothing. The path is now the same **Backend → on-device** as the two brain keys, which iswhere the field actually is.- - `brain_no_key` also said **"长按小球打开设置" / "long-press the ball, open settings"**.+ - `brain_no_key` also said **"long-press the ball, open settings"**.`onLongPress` does not open settings; it calls `dispatcher.expand()`, which brings the full cardback. Settings is the ⚙ button in that card's control bar. The sentence now names both steps,because the first one is genuinely required — the control bar only exists at full size.- - `check_detail_brain_hub_missing` gained the missing precondition: **「云端」 is hidden unless- 高级 →「显示云端选项」 is on.** `showHub` gates the tab in the picker, but `brainMode` does not+ - `check_detail_brain_hub_missing` gained the missing precondition: **the hub tab is hidden unless+ Advanced → "Show cloud option" is on.** `showHub` gates the tab in the picker, but `brainMode` does notconsult it, so a device can sit in hub mode with the tab that fixes it invisible — turn the- toggle on, pick 云端, turn it off again, and the self-check would have pointed at nothing.+ toggle on, pick the hub, turn it off again, and the self-check would have pointed at nothing.Every label these strings now name was checked against its resource value rather than transcribedfrom the sentence being replaced — which is how the one remaining error was caught: the Englishlabel is **"Show cloud option"**, singular, and the first draft of this fix wrote it plural.- **Both READMEs promised a first-run wizard that no longer exists.** "The first run is a stepped- setup that walks you through both" / 「第一次启动会有一个分步引导」 — `8dac568` deleted the wizard+ setup that walks you through both" — in both languages — `8dac568` deleted the wizard(`ui/FirstRunUi.kt`). A missing setup guide is indistinguishable from a broken install, so thisread as a bug report rather than as stale prose. Both now say what the app does instead: theself-check runs on every start, the card names the missing key, and its button opens settings.-- `README.md` named the Volcengine field as **火山 API key** — the Chinese label — while the English+- `README.md` named the Volcengine field by its Chinese label, while the Englishbuild displays **Volcengine API key** (`settings_voice_api_key`). The Chinese README already hadthis right; only the English file was pointing at a word that never appears on an English screen.- **A picture, a video or a clip now goes into a page, instead of being handed over as a URL.** The@@ -582,7 +584,7 @@ in the direction that made the model act on a grant nobody had given.was attached, so a real `https` image and a real `.mp4` rendering in the page are stillunconfirmed.- **The launcher icon could become a permanent dead end, because the overlay was inferred from a view- object instead of asked for as a grant.** First run, accessibility on, 悬浮球权限 off: the checklist+ object instead of asked for as a grant.** First run, accessibility on, the overlay grant off: the checklistcame up, the user closed it, and from then on the icon did nothing — no screen, no error, no wayback in short of reinstalling. Nothing was removing the ball's window. On HONOR/MagicOS a denied`SYSTEM_ALERT_WINDOW` does not make `addView` throw: it succeeds, and the system hides the window@@ -593,9 +595,9 @@ in the direction that made the model act on a grant nobody had given.`SelfCheckActivity` took its expand-and-finish branch, called `expand()` on a card that cannot bedrawn, finished itself, and left an empty screen; the checklist branch, which is the one that namesthis failure in red, never ran. The grant is now asked **first and directly**, as- `Settings.canDrawOverlays()` — the same predicate `SelfCheck.overlay` uses for the 悬浮窗 row, so the+ `Settings.canDrawOverlays()` — the same predicate `SelfCheck.overlay` uses for the overlay row, so thepage and the door can no longer contradict each other (which is what the user hit: the page said- 没开 while the door said 在屏). It also covers revoking a grant that was already given, when `root`+ "off" while the door said it was on screen). It also covers revoking a grant that was already given, when `root`stays non-null for the life of the process. `showSelfCheckCard()` guarded with the same marker,where its own comment had claimed it already did. Verified on the device (LIO-TL00) on **both**paths, because this edits the working path's entry test too — grant denied now reaches the@@ -604,20 +606,20 @@ in the direction that made the model act on a grant nobody had given.### Changed-- **The 悬浮窗权限 row now leads the self-check list**, ahead of 无障碍服务. Both are hard gates and+- **The overlay-permission row now leads the self-check list**, ahead of accessibility. Both are hard gates andthe order between them was arbitrary; what settles it is that they fail in opposite directions.With the service off the app is visibly inert — nothing to run, and every row below is decoration.With the grant off it *looks* broken instead: the service runs perfectly well, silently cannotdraw, and tapping the icon appears to do nothing at all. That second shape is the one users misreadas "the app is dead", so it goes first.-- 无障碍服务's off-state copy named the row's list position — 「后面几条都不用看」 / *"the rest of this- list does not matter yet"* — which the reorder above invalidated. It is now 「其他都不用看」 /+- The accessibility row's off-state copy named the row's list position — *"the rest of this+ which the reorder above invalidated. It is now *"nothing else here matters"* —*"nothing else here matters either"*: same meaning, no longer positional. Same edit in both stringfiles.### Removed-- **The first-run wizard is gone** (`ui/FirstRunUi.kt`, its wiring in `ScreenBodyService`, the 重新设置+- **The first-run wizard is gone** (`ui/FirstRunUi.kt`, its wiring in `ScreenBodyService`, the re-run-setupbutton on the self-check card, and its strings in both languages). The wizard and the startupself-check both wanted to put a card up on a first start, and when the check found a problem itcovered the wizard, so a new user saw whichever lost the race. The wizard was removed rather than@@ -627,7 +629,7 @@ in the direction that made the model act on a grant nobody had given.the self-check. The two READMEs had promised this wizard — see the *Fixed* entry above.- `check_page_no_overlay` and the `SelfCheckUi.note()` helper it was the only caller of. The noteexplained that the settings sheet is drawn as an overlay — a fact the page does not need to teach,- because the 悬浮窗 row directly below it already carries the fix, in that row's own words and with a+ because the overlay row directly below it already carries the fix, in that row's own words and with abutton. `fixButton()`'s comment used to point at "the note above the list"; it now states the ruleon its own: a button that does nothing is worse than no button.@@ -655,7 +657,7 @@ because a release this size is the norm.GitHub renders a README image through `<img>` and `var(--color-*)` resolves to black there; bothwere rendered at 1:1 and read back to check for overflow, which caught three layout faults thatreading the source alone would not have shown.-- **Both READMEs now ask for your use case (`## Showcase` / `## 好玩的用法`).** The+- **Both READMEs now ask for your use case (`## Showcase`).** TheREADME described what the thing can do and never asked anyone to show what they did with it,which is how a project ends up with no idea whether the odd corners work. The section is aninvitation and three things that make a post useful: the device and ROM (this app talks to Android@@ -709,7 +711,7 @@ because a release this size is the norm.- Both READMEs now carry a warning above the fold and a `## Disclaimer and acceptable use` section;`SECURITY.md` states the triage boundary (steering it is a vulnerability; doing what it was builtto do is documented behaviour).-- **A 版本 row in the self-check list — the first thing this app ever sends anywhere.** It asks a+- **A version row in the self-check list — the first thing this app ever sends anywhere.** It asks aversion service whether a newer build exists and reports the answer as one more row in the same listthe device diagnostics live in: one row, one renderer, no second settings page. The level mapping isthe deliberate part. **Current → OK, newer release available → NOTE, forced update → WARN, and@@ -729,7 +731,7 @@ because a release this size is the norm.- **`res/xml/network_security_config.xml` deliberately did *not* gain the version host, on the secondpass.** Android refuses cleartext HTTP to any host not named there, and what it produces —`CLEARTEXT communication to X not permitted by network security policy` — arrives as a version row- reading 查不到, a message about a policy rather than about anything the user did. So the first cut+ reading "not found", a message about a policy rather than about anything the user did. So the first cutadded the service's IP address to that file, which is the right move *for a `http://` address*. Theaddress then became `https://andee.kuafuai.net`, which needs no exception at all, and the entry wasdeleted rather than left in place: an exception for a host nobody calls only widens what this app@@ -744,7 +746,7 @@ because a release this size is the norm.meaning the constructor's `(String) -> Unit` callback that routes the message to the owner. Kotlinresolves an unqualified call to the nearest scope first, so the line called *itself*: one recognizererror became infinite recursion until the stack ran out (`stack size 1039KB`, thousands of frames of- `AsrController.kt:152`). Any 火山 failure — a dead network, an expired token, a rejected handshake —+ `AsrController.kt:152`). Any Volcengine failure — a dead network, an expired token, a rejected handshake —took the whole process down, which is the opposite of what the callback is for. Now qualified`[email protected](msg)`. The listener's three other callbacks are unaffected: none of themshares a name with an outer member.@@ -852,7 +854,7 @@ because a release this size is the norm.`DISCLAIMER.md` / `DISCLAIMER.zh-CN.md` and `docs/permissions.md` / `docs/permissions.zh-CN.md` alllisted `brain=hub` first in their "data goes where" table's *Default* column, which read as thoughthe hub were the out-of-box mode. It is not: `VoiceConfig.brainConfig` reads- `getString("brain", BRAIN_LOCAL)`, and the `brain` picker lists 本机 leftmost for the same reason.+ `getString("brain", BRAIN_LOCAL)`, and the `brain` picker lists the on-device option leftmost for the same reason.The row now reads `brain=local` (the default) → `api.deepseek.com`, with hub mode as the othercase. Separately, `CLAUDE.md`'s "Existing but not wired up" section claimed there was **no `tts.*`dispatcher namespace** — there is one (`tts.speak`, `CommandDispatcher`); what it lacks is a@@ -868,7 +870,7 @@ because a release this size is the norm.*this* project to). It is now described in its own terms first — **a general platform where youdescribe the app you want and it develops and publishes it** — followed by one plain sentence:**a separate service with no direct relationship to this project**, its own terms, pricing and data- handling. Same treatment in `## Using Andee` / `## 三种使用方式`; the Chinese `## 从哪里开始看`+ handling. Same treatment in `## Using Andee`; the Chinese getting-started sectiontable carried it too, and has since been removed (see *Removed*). The practical guidance isunchanged (still the shortest path; still an APK you have to install; the free token allowance isstill finite and then paid), because none of that was wrong — only the implied ownership was.@@ -880,16 +882,16 @@ because a release this size is the norm.now `WhatsApp`, `Amazon` and `eBay` — WhatsApp rather than a platform-native messenger because thisruns on Android only, and naming an iOS-only one would be a false claim rather than a foreign one.Two of the scene examples needed rewriting rather than substituting: "look after my WeChat" is- 帮我看着微信 carried across word for word, which is not a sentence English builds. Separately, the+ a Chinese scene example carried across word for word, which is not a sentence English builds. Separately, thepanel names were the Chinese labels, so a reader on an English device was being told to look for- **产物** — a word their screen does not have. They now use the labels `values-en/` actually ships:+ **a Chinese label** — a word their screen does not have. They now use the labels `values-en/` actually ships:**Scenes**, **Made for you**, **What it remembers**, **Voice API key**.The **measured** passage keeps every fact. Xiaomi Pad 5, MIUI, WeChat 8.0.78 and the 219-node countare what was observed, and changing the app name there to make the prose consistent would beinventing a measurement. Only its framing moved: it opened on WeChat, which a non-Chinese readerreads as someone else's app having someone else's problem, so it now opens on the generalbehaviour and names WeChat as the one we happened to measure.-- **The blanket "没有任何遥测 / no telemetry at all" claim is gone, because the version row above+- **The blanket "no telemetry at all" claim is gone, because the version row abovemade it false.** It appeared in nine places — `DISCLAIMER.md`, `DISCLAIMER.zh-CN.md`,`docs/permissions.md`, `docs/permissions.zh-CN.md`, both READMEs, and both README badges — and allnine were in the same voice: not "we anonymise it", not "opt out in settings", but a flat statement@@ -900,8 +902,8 @@ because a release this size is the norm.confirmed by the same grep the old text quoted — and then state the single exception field by field,in a row of its own in the data table, next to an explicit list of what that request does *not*carry (conversation, screen, app list, contacts, location, crash log, advertising ID). `docs/permissions.md`- is the canonical copy; the rest point at it. The badge went from `遥测-无` / `telemetry-none` to- `遥测-不含内容` / `telemetry-no content`, because "no content" is the claim that survives.+ is the canonical copy; the rest point at it. The badge went from `telemetry-none` to+ `telemetry-no content`, because "no content" is the claim that survives.Worth recording for whoever edits these next: the old sentence was true of the *repository* on theday it was written and was always going to be false the moment the project shipped anything thatphoned home. This file had already annotated that distinction in the DISCLAIMER's own entry above —@@ -916,7 +918,7 @@ because a release this size is the norm.`git show <rev>:brain/andee-system-prompt.md`.- `dog/NRF24_Dongle/README.md` reference in the README — the dongle firmware is not in thisrepository and never was. The README now says so.-- The `## 从哪里开始看` section in `README.zh-CN.md`, heading included. Its visible content was three+- The Chinese getting-started section in `README.zh-CN.md`, heading included. Its visible content was threerows announcing that the demo video and the screenshots do not exist yet, which tells a readernothing they cannot see for themselves. The heading went too: once the table was gone the sectionheld nothing but an HTML comment, and a heading over nothing renders as exactly that. Everydiff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 5c50794..01b22d7 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -1,6 +1,6 @@<p align="center"><a href="./CONTRIBUTING.md"><img alt="English" src="https://img.shields.io/badge/English-d9d9d9"></a>- <a href="./CONTRIBUTING.zh-CN.md"><img alt="简体中文" src="https://img.shields.io/badge/简体中文-d9d9d9"></a>+ <a href="./CONTRIBUTING.zh-CN.md"><img alt="Chinese" src="https://img.shields.io/badge/Chinese-d9d9d9"></a></p># Contributing@@ -166,4 +166,4 @@ Open an issue and ask, or ask in the PR. Do not sit on it — we would much rath----**Other languages:** [简体中文](CONTRIBUTING.zh-CN.md)+**Other languages:** [Chinese](CONTRIBUTING.zh-CN.md)diff --git a/DISCLAIMER.md b/DISCLAIMER.mdindex dd49aeb..806034a 100644--- a/DISCLAIMER.md+++ b/DISCLAIMER.md@@ -1,6 +1,6 @@<p align="center"><a href="./DISCLAIMER.md"><img alt="English" src="https://img.shields.io/badge/English-d9d9d9"></a>- <a href="./DISCLAIMER.zh-CN.md"><img alt="简体中文" src="https://img.shields.io/badge/简体中文-d9d9d9"></a>+ <a href="./DISCLAIMER.zh-CN.md"><img alt="Chinese" src="https://img.shields.io/badge/Chinese-d9d9d9"></a></p># Disclaimer@@ -94,4 +94,4 @@ Do not install it, do not run it, delete it. Using it means you have read, under----**Other languages:** [简体中文](DISCLAIMER.zh-CN.md)+**Other languages:** [Chinese](DISCLAIMER.zh-CN.md)diff --git a/docs/acceptable-use.md b/docs/acceptable-use.mdindex c07f9ff..bece6e4 100644--- a/docs/acceptable-use.md+++ b/docs/acceptable-use.md@@ -1,6 +1,6 @@<p align="center"><a href="./acceptable-use.md"><img alt="English" src="https://img.shields.io/badge/English-d9d9d9"></a>- <a href="./acceptable-use.zh-CN.md"><img alt="简体中文" src="https://img.shields.io/badge/简体中文-d9d9d9"></a>+ <a href="./acceptable-use.zh-CN.md"><img alt="Chinese" src="https://img.shields.io/badge/Chinese-d9d9d9"></a></p># Acceptable Use Policy@@ -27,7 +27,7 @@ The following are **prohibited without exception**. They are listed because they**(a) Crime, and providing help to crime**- Any criminal or unlawful activity.-- Telecom and network fraud, or **any form of assistance** to it — including transferring funds for others, money laundering ("跑分"), faking transaction flows, receiving and passing on proceeds, promotional referral, bulk account registration or unblocking, and creating or distributing fraud tooling.+- Telecom and network fraud, or **any form of assistance** to it — including transferring funds for others, laundering money by moving it through payment accounts, faking transaction flows, receiving and passing on proceeds, promotional referral, bulk account registration or unblocking, and creating or distributing fraud tooling.This **may constitute "the crime of aiding information network criminal activities" under Article 287-2 of the Criminal Law of the People's Republic of China** — up to three years' imprisonment or detention, plus a fine. Note that in practice, **even without direct profit and even while claiming not to have known, a court may infer knowledge from objective conduct.**- Operating another person's payment account, bank card, or settlement instrument on their behalf.@@ -90,4 +90,4 @@ This document **is not legal advice.** It is a condition of use, not a legal opi----**Other languages:** [简体中文](acceptable-use.zh-CN.md)+**Other languages:** [Chinese](acceptable-use.zh-CN.md)diff --git a/docs/permissions.md b/docs/permissions.mdindex 60489c1..290a56e 100644--- a/docs/permissions.md+++ b/docs/permissions.md@@ -1,6 +1,6 @@<p align="center"><a href="./permissions.md"><img alt="English" src="https://img.shields.io/badge/English-d9d9d9"></a>- <a href="./permissions.zh-CN.md"><img alt="简体中文" src="https://img.shields.io/badge/简体中文-d9d9d9"></a>+ <a href="./permissions.zh-CN.md"><img alt="Chinese" src="https://img.shields.io/badge/Chinese-d9d9d9"></a></p># Permissions@@ -150,4 +150,4 @@ If you want to look deeper, [../SECURITY.md](../SECURITY.md) has the full securi----**Other languages:** [简体中文](permissions.zh-CN.md)+**Other languages:** [Chinese](permissions.zh-CN.md)diff --git a/docs/releases/v0.1.0.md b/docs/releases/v0.1.0.mdindex c427e07..9234ca1 100644--- a/docs/releases/v0.1.0.md+++ b/docs/releases/v0.1.0.md@@ -45,7 +45,7 @@ work. Treat MINOR versions as able to break. See the [versioning policy](../../Cboth READMEs — a turn in, the agent loop, six ways out. Drawing it corrected two claims: there arethree backends rather than two, and an unconfigured device reads as `BRAIN_LOCAL` rather than thehosted one.-- A **版本 row in the self-check list** — the first thing this app ever sends anywhere. It asks a+- A **version row in the self-check list** — the first thing this app ever sends anywhere. It asks aversion service whether a newer build exists: one row, one renderer, no second settings page.- `LICENSE` — Apache-2.0 with additional conditions. GitHub reports it as `NOASSERTION`; that isexpected, not a misconfiguration.@@ -54,7 +54,7 @@ work. Treat MINOR versions as able to break. See the [versioning policy](../../C`docs/permissions.md` + `docs/permissions.zh-CN.md`, `THIRD_PARTY_NOTICES.md`.- A `Signed-off-by:` sign-off is required on every commit, enforced by`.github/workflows/dco.yml`.-- Both READMEs now ask for your use case (`## Showcase` / `## 好玩的用法`).+- Both READMEs now ask for your use case (`## Showcase` and its Chinese counterpart).### Changed@@ -90,7 +90,7 @@ work. Treat MINOR versions as able to break. See the [versioning policy](../../C- `brain/andee-system-prompt.md` — an unused mirror of the cloud brain's prompt with no runtime role.The cloud brain mode itself is not retired.-- The `## 从哪里开始看` section in `README.zh-CN.md`, which held nothing but three rows announcing+- The Chinese getting-started section in `README.zh-CN.md`, which held nothing but three rows announcingthat the demo video and screenshots do not exist yet.## Known issuesdiff --git a/docs/releases/v0.1.1.md b/docs/releases/v0.1.1.mdindex 3ef314b..aace06a 100644--- a/docs/releases/v0.1.1.md+++ b/docs/releases/v0.1.1.md@@ -17,11 +17,11 @@ Still no binary attached — see *Install* below.the window, so the view object stays around and `isShown()` keeps answering true. The entry testtrusted that marker, took the "expand the ball" branch, and finished on an empty screen: the icondid nothing, and did it again every time. The grant is now asked **directly**,- `Settings.canDrawOverlays()`, the same predicate the self-check's own 悬浮窗 row uses — so the page+ `Settings.canDrawOverlays()`, the same predicate the self-check's own overlay row uses — so the pageand the door can no longer disagree.- **Four strings stop pointing at menus that are not there.** The settings card was reorganised twice- since those sentences were written and the sentences stayed behind: they said ⚙ → 「大脑」 / "Brain"- when the section reads 「后端」 / "Backend", one named a 语音(火山引擎) section that no longer+ since those sentences were written and the sentences stayed behind: they said ⚙ → "Brain"+ when the section reads "Backend", one named a "Speech (Volcengine)" section that no longerexists, and one told the user to long-press the ball to open settings — which expands the card, itdoes not open settings.- **A picture, a video or a clip now goes into a page instead of being handed over as a URL.** The@@ -43,18 +43,18 @@ Still no binary attached — see *Install* below.checklist (13 activity records), grant allowed still takes the expand branch (0 records).- **Four strings named menu labels that do not exist, and one a gesture that does not exist either.**`check_detail_brain_key_missing`, `check_detail_brain_hub_missing` and `brain_no_key` said- ⚙ → 「大脑」 / "Brain"; the header is `settings_section_brain` = 「后端」 / "Backend".- `check_detail_voice_key_missing` named a 语音(火山引擎) section whose rows had moved into- 后端 → 本机. `brain_no_key` also said 长按小球打开设置 (*"long-press the ball to open settings"*) —+ ⚙ → "Brain"; the header is `settings_section_brain` = "Backend".+ `check_detail_voice_key_missing` named a "Speech (Volcengine)" section whose rows had moved into+ Backend → on-device. `brain_no_key` also said *"long-press the ball to open settings"* —a long-press calls `dispatcher.expand()`, which brings the card back; settings is the ⚙ button inthat card's control bar, and the sentence now names both steps. `check_detail_brain_hub_missing`- gained the precondition it was missing: **「云端」 is hidden unless 高级 →「显示云端选项」 is on.**+ gained the precondition it was missing: **the hub tab is hidden unless Advanced → "Show cloud option" is on.**- **Both READMEs promised a first-run wizard that no longer exists** — "The first run is a stepped- setup that walks you through both" / 「第一次启动会有一个分步引导」. A missing setup guide is+ setup that walks you through both" — in both languages. A missing setup guide isindistinguishable from a broken install, so this read as a bug report rather than as stale prose.Both now describe what the app actually does: the self-check runs on every start, the card namesthe missing key, and its button opens settings.-- `README.md` named the Volcengine field as **火山 API key** — the Chinese label — while the English+- `README.md` named the Volcengine field by its Chinese label, while the Englishbuild displays **Volcengine API key**. Only the English file was wrong.- **A picture, a video or a clip goes into a page now.** §7 asks for the embedding directly(`<img>`, `<video controls>`, `<audio controls>`, absolute `https://` only) and says outright that@@ -65,18 +65,18 @@ Still no binary attached — see *Install* below.### Changed-- **The 悬浮窗权限 row now leads the self-check list**, ahead of 无障碍服务. Both are hard gates and+- **The overlay-permission row now leads the self-check list**, ahead of accessibility. Both are hard gates andthe order between them was arbitrary; they fail in opposite directions, and that settles it. Withthe service off the app is visibly inert. With the grant off it *looks* broken instead — theservice runs fine, silently cannot draw, and tapping the icon appears to do nothing. That secondshape is the one users misread as "the app is dead", so it goes first.-- 无障碍服务's off-state copy no longer names its own list position — 「后面几条都不用看」 /- "the rest of this list does not matter yet" became 「其他都不用看」 / "nothing else here matters+- The accessibility row's off-state copy no longer names its own list position —+ "the rest of this list does not matter yet" became "nothing else here matterseither". Same meaning, no longer invalidated by the reorder. Both string files.### Removed-- **The first-run wizard** — `ui/FirstRunUi.kt`, its wiring in `ScreenBodyService`, the 重新设置 button+- **The first-run wizard** — `ui/FirstRunUi.kt`, its wiring in `ScreenBodyService`, the re-run-setup buttonon the self-check card, and its strings in both languages. The wizard and the startup self-checkboth wanted to put a card up on a first start, and when the check found a problem it covered thewizard, so a new user saw whichever lost the race; the wizard was removed rather than arbitrate@@ -85,14 +85,14 @@ Still no binary attached — see *Install* below.word is now offered only from settings and as a note row on the self-check.- `check_page_no_overlay` and the `SelfCheckUi.note()` helper it was the only caller of. The noteexplained that the settings sheet is drawn as an overlay — a fact the page does not need to teach,- because the 悬浮窗 row directly below it already carries the fix, in its own words and with a+ because the overlay row directly below it already carries the fix, in its own words and with abutton.## Known issues- **A build with CodeFlying compiled in but no API key can raise the wrong complaint.** Theself-check's availability test looks at `CODEFLYING_ENABLED` and the domain rather than the key, so- such a build reports 大脑 key missing and sends the user to fill in a DeepSeek key — while the real+ such a build reports the brain key missing and sends the user to fill in a DeepSeek key — while the realcause is at build time. Surfaced by reading this release's diff; not fixed by it.- The two issues `v0.1.0` listed are **unchanged and untouched in this release**:`tools/verify_faces_lab.py` still reports 7/16 assertions passing against the committeddiff --git a/docs/releases/v0.2.0.md b/docs/releases/v0.2.0.mdindex 068c031..e6939ab 100644--- a/docs/releases/v0.2.0.md+++ b/docs/releases/v0.2.0.md@@ -23,7 +23,7 @@ the person meant to answer it.- **A single tap on the ball stops what is running and then listens.** Redirecting a busy assistantused to take two gestures and four taps; tapping something busy and having it stop and listen iswhat one person does to another.-- **An empty card now offers ready-made scenes** instead of 还没有对话 and nothing under it — one+- **An empty card now offers ready-made scenes** instead of "no conversation yet" and nothing under it — onebubble per preset, each with a sentence you could have said. Tapping one adopts the scene and thenspeaks it.- **The system permission sheet can actually be seen now.** It was being drawn *underneath* the@@ -47,7 +47,7 @@ the person meant to answer it.on an *abnormal* finish.- **A single tap on the ball stops, then listens.** The stop is `stopEverything()`, reused so thesingle tap and the triple tap cannot drift apart, and guarded on `dispatcher.isTaskActive()` so an- idle tap does not clear a pending 继续修改 or flash 已停止. Triple-tap is still the immediate stop.+ idle tap does not clear a pending "keep editing" or flash "stopped". Triple-tap is still the immediate stop.Verified on device (HONOR AMM-AN00).- **Ready-made scenes on a card with no history.** Tapping a bubble **adopts** the scene before itspeaks — a bubble that only sent its sentence asked the model about a scene nobody had saved. It is@@ -76,18 +76,18 @@ the person meant to answer it.### Changed- **The prompt's claim about the permission sheet was wrong and is now the measured one.** It said- the sheet "does not take a tap you inject". With the card folded, an injected tap on 「始终允许」- really does grant — `READ_CONTACTS` went false → true, and one tap on 「本次使用允许」 produced an+ the sheet "does not take a tap you inject". With the card folded, an injected tap on "Always allow"+ really does grant — `READ_CONTACTS` went false → true, and one tap on "Allow this time" produced an`ACCESS_FINE_LOCATION` carrying `ONE_TIME`, a flag only that button can set. The earlier fourfailures had one cause and it was our own card eating the touch. The rule becomes **"you cannot readit, so do not aim at it"**: the sheet exposes no accessibility elements, so any tap is blind, and- the button at the bottom of this screen is 「禁止后不再提示」, which nothing can undo.+ the button at the bottom of this screen is "Deny and don't ask again", which nothing can undo.## Known issues- **A build with CodeFlying compiled in but no API key can raise the wrong complaint.** Theself-check's availability test looks at `CODEFLYING_ENABLED` and the domain rather than the key, so- such a build reports 大脑 key missing and sends the user to fill in a DeepSeek key — while the real+ such a build reports the brain key missing and sends the user to fill in a DeepSeek key — while the realcause is at build time. Carried over from `v0.1.1`; not fixed by this release.- The two issues `v0.1.0` listed are **unchanged and untouched in this release**:`tools/verify_faces_lab.py` still reports 7/16 assertions passing against the committeddiff --git a/docs/releases/v0.3.0.md b/docs/releases/v0.3.0.mdindex 7c5d4b0..79d6fe8 100644--- a/docs/releases/v0.3.0.md+++ b/docs/releases/v0.3.0.md@@ -60,9 +60,9 @@ that revokes accessibility now costs one capability instead of the whole app.- **The version check moved to `https://api.heyandee.com`** from `https://andee.kuafuai.net`. The oldhost was on the mainland, where an unfiled domain is answered with a 403 block page that arrives in- the app as 查不到. The address is still a hardcoded constant and still the only one the user did not+ the app as "not found". The address is still a hardcoded constant and still the only one the user did notconfigure. A fresh DNS record is not everywhere at once, so on the wrong resolver that row reads- 查不到 until it propagates — intended, not a fault to report.+ "not found" until it propagates — intended, not a fault to report.- **Closing a page puts the assistant back at full size, unconditionally.** The fold that makes roomfor a page is ours, so undoing it is ours too, and it was missing from the model's route.- Both READMEs point their CodeFlying links at the `/andee` one-click landing page.@@ -80,10 +80,10 @@ that revokes accessibility now costs one capability instead of the whole app.two apart.- **The body stays off the screen while the check page is up.** The page was still the resumedActivity with the assistant's fullscreen card painted over it — and that window is fullscreen even- when the ball is compact, so it swallowed touches and 完成 did nothing.+ when the ball is compact, so it swallowed touches and the Done button did nothing.- **A just-fixed row stops showing as red on resume.** Returning from a Settings screen used tocompare languages and nothing else, so a row the user had just fixed stayed red until they found- 重新检查.+ "check again".- **A perch slide dragged the whole card off-screen**, half untouchable, and a voice failure on adevice with no voice set up repeated forever. Both fixed.- **`screen.screenshot`'s schema claimed an aim grid and an element list**, both exactly untrue ondiff --git a/docs/releases/v0.3.1.md b/docs/releases/v0.3.1.mdindex ac53613..948c654 100644--- a/docs/releases/v0.3.1.md+++ b/docs/releases/v0.3.1.md@@ -29,7 +29,7 @@ that reads as an oversight later.- **`POST_NOTIFICATIONS` is actually requested now.** It had been declared in the manifest since thebeginning and mentioned by no Kotlin file, so on Android 13+ everything the app posted was droppedin silence — including the persistent notification that is the way back to it.-- **Tapping 处理 in the check card no longer throws the list away.** The trip to Settings is handed to+- **Tapping the fix button in the check card no longer throws the list away.** The trip to Settings is handed tothe page, which is in the task the destination lands in and gets a resume callback on the way back.## What's Changed@@ -48,7 +48,7 @@ that reads as an oversight later.deliberately *not* switched by language: its model belongs to the hosted backend, and an Englishbuild inventing `gpt-4o-mini` at that endpoint would name a model CodeFlying does not serve.- **Errand trips from the check card are handed to `SelfCheckActivity.showForErrand`** rather than made- by the card. `Fix.Grant` goes through the same door, so 允许 on 麦克风 / 弹出通知 stops ending on the+ by the card. `Fix.Grant` goes through the same door, so Allow on the microphone and notification rows stops ending on thelauncher as well.- **Every look gets the prop-and-pose layer**, not just Andee — stars, a heart, a shield, a sweat bead,the sliced lid, and an idle life that lets a look wear its own expressions and nap while nothing is@@ -68,7 +68,7 @@ that reads as an oversight later.exactly that. The negations are now scoped to a category and the section opens with the axis thatseparates the two.- **The English README no longer contains a single Chinese character** — `\p{Han}` returns nothing. The- language badge, five look names, a dozen `([中文](…))` links and the `(中文)` markers on the+ language badge, five look names, a dozen Chinese-language links and the language markers on theCodeFlying sites were all changed. The Chinese README keeps its own language.### Fixed@@ -77,12 +77,12 @@ that reads as an oversight later.notification this app posts: the persistent notification that is the route back to screen control,and every reminder `Scheduler` fires. The codebase half knew — `Scheduler` carries a comment blamingthis permission for its own failure to notify, and nothing tested the claim. The row that looked like- it covered this (通知使用权) is the notification *listener*, which can be granted and green while+ it covered this (the notification-access row) is the notification *listener*, which can be granted and green whileevery notification the app sends disappears. Two things were needed beyond a catalog entry: on API 32and below the permission does not exist and `checkSelfPermission` answers **denied** for anything itdoes not know, so the entry is skipped rather than answered; and it is named in `SOLO_IDS`, becausethat set is a whitelist whose default would have handed it to `ask_user`.-- **The check card's 处理 no longer ends on the desktop.** The card was closed and the assistant folded+- **The check card's fix button no longer ends on the desktop.** The card was closed and the assistant foldedbefore the destination launched, so a window — which gets no `onResume` — lost the list, and thedestination went out with `FLAG_ACTIVITY_NEW_TASK` into a task of its own, leaving nowhere of ours toreturn to. Verified on the tablet (Mi Pad 5, `.dbg` package).diff --git a/docs/releases/v0.3.2.md b/docs/releases/v0.3.2.mdindex 5d2bcbe..bfa3dba 100644--- a/docs/releases/v0.3.2.md+++ b/docs/releases/v0.3.2.md@@ -14,7 +14,8 @@ telling the reader to build one.## Highlights- **The wake word works with the screen off now**, which is the state a phone is in when it is in your- pocket. **⚙ → wake word → 锁屏时也听** controls it and ships **on**; the microphone stays open while+ pocket. **⚙ → wake word → the "listen while locked" row** controls it and ships **on**; the+ microphone stays open whileit is, and the system's recording indicator shows it.- **It will not pretend it can act while you are locked out.** Woken with the keyguard up it can hearand answer, but screen and app-launch tools refuse outright with a sentence saying why — instead of@@ -30,7 +31,7 @@ telling the reader to build one.### Added- **Wake word with the screen off**, gated by `wakeListeningAllowed()` — *the screen is on, or the- user left 锁屏时也听 on*, defaulting to on. The old rule (screen on only) had a real reason behind it+ user left the "listen while locked" row on*, defaulting to on. The old rule (screen on only) had a real reason behind it— a dark tablet on a bedside table should not listen all night — but it also meant the assistantcould not be called from the one place a person keeps their phone. The cost is stated on the rowthat flips it rather than left for the status bar to mention.@@ -43,7 +44,8 @@ telling the reader to build one.`ui.alert`, `ui.show_html`) go with it. `device.battery`, `device.volume`, `tts.speak` and the whole`note.` namespace stay open, because they work perfectly well locked. Read live rather than mirroredinto a flag: locking the phone mid-answer is a normal thing to do, not a state transition to track.-- **Five gesture faces along the bottom of both cover images**, one word under each — 听 看 想 做 说.+- **Five gesture faces along the bottom of both cover images**, one word under each — Listen, Look,+ Think, Act, Speak.They are the app's own illustrations, and specifically the *gesture* moods the web renderer cannotdraw.@@ -63,11 +65,11 @@ telling the reader to build one.- **The voice segmenter started on the microphone, not on the voice.** `START_FRAMES` 3 → 8 (80 ms) soa transient cannot open a segment, and `PREROLL_FRAMES` 15 → 30 (300 ms) so the onset is still inthe ring when the decision lands. A segment that starts early comes out long and, past `MAX_FRAMES`,- was dropped in silence — the card simply sat on 听着…, which is what "it takes three tries" was.+ was dropped in silence — the card simply sat on "listening…", which is what "it takes three tries" was.Delaying a decision is free; discarding the audio is not, which is why there is deliberately nowarm-up that drops the first 200 ms.-- **The enrolment prompt appeared before the microphone existed.** 现在说吧 was set on the tapper's- thread; it now waits for `mic.start()` to return, so the card reads 正在听… while the recorder comes+- **The enrolment prompt appeared before the microphone existed.** The "now speak" prompt was set on the tapper's+ thread; it now waits for `mic.start()` to return, so the card reads "listening…" while the recorder comesup and invites you to speak only once something is listening.- **The wake threshold was anchored on the worst take rather than the closest.** One dirty take usedto set the door width for the whole system — 2.2755 and 2.1083 against non-wake speech measured at@@ -113,8 +115,8 @@ in, the card the assistant puts up will name what is missing — that is the selfault.> **Would you rather not configure keys at all?** Then this APK is the wrong door. Use the one-click-> page instead — **[codeflying.net/andee](https://www.codeflying.net/andee)** (mainland China) or-> **[codeflying.app/andee](https://www.codeflying.app/andee)** (everywhere else). Describe what you+> page instead — **[codeflying.app/andee](https://www.codeflying.app/andee)**, or+> **[codeflying.net/andee](https://www.codeflying.net/andee)** in mainland China. Describe what you> want, tap the build button, and you get a package with the **tokens already configured** plus a QR> code to scan. Starting is free and the free token allowance is **finite — once it runs out, tokens> must be bought.** It is a separate service with no direct relationship to this project, with its own@@ -177,6 +179,6 @@ README's **Provisioning** section.**Upgrading from v0.3.1:** `versionCode` moves `5 → 6`, so this installs over it normally. **The wakeword now keeps listening with the screen off** — if you have enrolled one, that is a new behaviour and-a new battery cost, and **⚙ → wake word → 锁屏时也听** turns it off.+a new battery cost, and **⚙ → wake word → the "listen while locked" row** turns it off.**Full Changelog**: https://github.com/kuafuai/andee/compare/v0.3.1...v0.3.2