Skip to content

Apple's open-source XNU kernel on Android phones: its own loader and drivers, Metal on the Adreno. Runs from RAM; a reboot gives the phone back to Android.

C

Docs: fb_beam and wallpaper_freeze=1 are in the tree; the numbers of the last run; what MORE cannot turn off

yehorkaa261f2ce0b57b
diff --git a/CHANGELOG.md b/CHANGELOG.md
index fc84447..e48d8cf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -21,9 +21,11 @@ changes to it; the scripts named fetch the release and put the changes on.
## 2026-11-04
-- metal: 120 frames a second is not reached: hakios-metal 100 to 104 in page swipes, about 90 in Settings' scroll and in opening an app, 28 at the home button with `wallpaper_cache=1`; after the finger lifts, 185 of a swipe's 205 frames take 8.3 ms, while it drags 75 to 80 a second; `docs/reference/metal-measurements.md`
+- metal: 120 frames a second is not reached: hakios-metal 101 in page swipes, 109 in Settings' scroll, 92 at the home button, 4% of frames over 16.7 ms; after the finger lifts, 185 of a swipe's 205 frames take 8.3 ms, while it drags 75 to 80 a second; `docs/reference/metal-measurements.md`
+- springboard: `wallpaper_freeze=1` makes the wallpaper one picture, from the IOSurface on the panel (`kern.hakios.fb_surface`): home button 92 frames a second, against 28 with `wallpaper_cache=1` and 50 without either; the icons blink once, the wallpaper does not change until the next boot, and the lock screen shows the same picture
+- windows: `tools/metal-run.sh` sets `wallpaper_freeze=1` and `metal_defer=1`; `MORE` cannot turn them off
- metal: 250 touch samples a second instead of 125 change nothing (100 to 102); `touch_poll_us` stays 4000 in `tools/metal-run.sh`
-- display: (PENDING, its commit is being tuned) `fb_beam=1`, the default: each thread's rows are written behind the panel's scan line (2433 lines, 8338 us), and the moving bands are gone; `kern.hakios.fb_surface` is the IOSurface on the panel
+- display: `fb_beam=1`, the default: each thread's rows are written behind the panel's scan line (2433 lines, 8338 us), and to the eye the moving bands are gone; it costs no frames (Settings' scroll 109 against 89, home button 92 against 81, swipes 101 against 99)
- docs: a short README and a front page by what you came to do; `docs/reference/metal.md` and its measurements; every boot-argument of both Metal paths in the catalogue (`tools/boot-args.py` reads `hm_boot_arg_set`)
- licenses: Turnip, AdrenoMetal, metal2vulkan and the plug-in's origin in `THIRD_PARTY_LICENSES.md`; a binary built with `M2V=1` has obligations and is **to verify** before any distribution
diff --git a/README.md b/README.md
index 32da096..c554bec 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@ Android.
**Documentation:** [docs/](docs/index.md), and the site, [hackios-web.vercel.app](https://hackios-web.vercel.app).
**News, 4 November 2026:** on the POCO X5 Pro 5G the window server draws through Metal on the Adreno 642L, two ways. hakios-metal: page
-swipes 100 to 104 frames a second, Settings' scroll about 90. UniXNU's Metal on Vulkan: swipes 50 to 57, scroll 41. The panel is 120 Hz,
+swipes 100 to 104 frames a second, Settings' scroll 109, the home button 92. UniXNU's Metal on Vulkan: swipes 50 to 57, scroll 41. The panel is 120 Hz,
and **120 frames a second has not been reached**. [Metal on the Adreno](docs/reference/metal.md),
[the measurements](docs/reference/metal-measurements.md). <!-- FINAL-NUMBERS -->
diff --git a/README.uk.md b/README.uk.md
index 59c4cdd..132df64 100644
--- a/README.uk.md
+++ b/README.uk.md
@@ -10,7 +10,7 @@
**Документація:** [docs/](docs/index.md) (англійською) і сайт [hackios-web.vercel.app](https://hackios-web.vercel.app).
**Новини, 4 листопада 2026:** на POCO X5 Pro 5G віконний сервер малює через Metal на Adreno 642L, двома шляхами. hakios-metal: гортання
-сторінок 100–104 кадри на секунду, прокручування в Settings близько 90. Metal поверх Vulkan від UniXNU: гортання 50–57, прокручування 41.
+сторінок 100–104 кадри на секунду, прокручування в Settings 109, кнопка «додому» 92. Metal поверх Vulkan від UniXNU: гортання 50–57, прокручування 41.
Панель працює на 120 Гц, і **120 кадрів на секунду не досягнуто**. [Metal на Adreno](docs/reference/metal.md),
[вимірювання](docs/reference/metal-measurements.md). <!-- FINAL-NUMBERS -->
diff --git a/README.zh.md b/README.zh.md
index 835477e..68db6d5 100644
--- a/README.zh.md
+++ b/README.zh.md
@@ -6,7 +6,7 @@
**文档:** [docs/](docs/index.md)(英文),以及网站 [hackios-web.vercel.app](https://hackios-web.vercel.app)。
-**动态,2026 年 11 月 4 日:** 在 POCO X5 Pro 5G 上,窗口服务器通过 Metal 在 Adreno 642L 上绘制,有两条路径。hakios-metal:翻页每秒 100 至 104 帧,Settings 滚动约 90 帧。UniXNU 的 Metal on Vulkan:翻页 50 至 57 帧,滚动 41 帧。屏幕是 120 Hz,**尚未达到每秒 120 帧**。[Adreno 上的 Metal](docs/reference/metal.md),[测量结果](docs/reference/metal-measurements.md)。<!-- FINAL-NUMBERS -->
+**动态,2026 年 11 月 4 日:** 在 POCO X5 Pro 5G 上,窗口服务器通过 Metal 在 Adreno 642L 上绘制,有两条路径。hakios-metal:翻页每秒 100 至 104 帧,Settings 滚动 109 帧,主屏幕按钮 92 帧。UniXNU 的 Metal on Vulkan:翻页 50 至 57 帧,滚动 41 帧。屏幕是 120 Hz,**尚未达到每秒 120 帧**。[Adreno 上的 Metal](docs/reference/metal.md),[测量结果](docs/reference/metal-measurements.md)。<!-- FINAL-NUMBERS -->
从 [Getting started](docs/getting-started/index.md)、[On the phone](docs/getting-started/phone.md) 或 [Port a device](docs/porting/index.md) 开始。各部分的工作情况:[文档首页](docs/index.md#what-works)。
diff --git a/configs/boot-args.lst b/configs/boot-args.lst
index 1c81983..4e8de58 100644
--- a/configs/boot-args.lst
+++ b/configs/boot-args.lst
@@ -89,6 +89,7 @@ ddr_rest k
ddr_vote k
display_probe k
epoch k
+fb_beam k
fb_beat k
fb_ca_hz k
fb_diff k
diff --git a/configs/common_defconfig b/configs/common_defconfig
index 6f43afa..8e3ef99 100644
--- a/configs/common_defconfig
+++ b/configs/common_defconfig
@@ -2,7 +2,7 @@
# HakiOS common defconfig: every setting there is, with what it does.
# Made by tools/hakios-config.py listing common -o <this file>; the values are the ones that file sets, and tests/CI check that it names every symbol.
#
-# 370 symbols in 18 groups; 34 are set, 25 of them drivers built in.
+# 371 symbols in 18 groups; 34 are set, 25 of them drivers built in.
#
#
@@ -335,7 +335,7 @@ CONFIG_TOUCHSCREEN=y
# CONFIG_VIRTIO_INPUT is not set
#
-# GPU and display (75)
+# GPU and display (76)
#
# rendering on Adreno (an image built with GL=1; the GPU's firmware from your phone) [needs fw-gpu/ from the phone]
@@ -380,6 +380,9 @@ CONFIG_GPU=y
# before any step: read what the firmware left the display controller doing (display_probe() below; two clocks are ...
# CONFIG_DISPLAY_PROBE is not set
+# frames written to the panel's memory whenever their beat comes, as before
+# CONFIG_FB_BEAM is not set
+
# read by MiniIOMobileFramebuffer.cpp (kernel)
# CONFIG_FB_BEAT is not set
diff --git a/configs/symbols.tsv b/configs/symbols.tsv
index ddb6040..7de0cd7 100644
--- a/configs/symbols.tsv
+++ b/configs/symbols.tsv
@@ -80,6 +80,7 @@ DDR arg ddr CPU, memory and boot k hakios.cpufreq.c the memory's bus clock manag
DDR_REST arg ddr_rest CPU, memory and boot k hakios.cpufreq.c
DDR_VOTE arg ddr_vote CPU, memory and boot k hakios.cpufreq.c
DISPLAY_PROBE arg display_probe GPU and display k hakios.adreno.c before any step: read what the firmware left the display controller doing (display_probe() below; two clocks are turned on, nothing else written)
+FB_BEAM arg fb_beam GPU and display k MiniIOMobileFramebuffer.cpp frames written to the panel's memory whenever their beat comes, as before
FB_BEAT arg fb_beat GPU and display k MiniIOMobileFramebuffer.cpp
FB_CA_HZ arg fb_ca_hz GPU and display k MiniIOMobileFramebuffer.cpp the refresh rate told to CoreAnimation (IOMFBDisplayRefresh) when it is not to be fb_hz's
FB_DIFF arg fb_diff GPU and display k MiniIOMobileFramebuffer.cpp which pixels of the panel each frame changed (it costs: the panel's memory is slow to read)
diff --git a/docs/boot-args.md b/docs/boot-args.md
index e02e75c..2b9ae1f 100644
--- a/docs/boot-args.md
+++ b/docs/boot-args.md
@@ -2,13 +2,13 @@
Made by `tools/boot-args.py --markdown`; CI fails if it is out of date with the source (`tools/boot-args.py --check`).
-Every argument that the kernel, the loader or user space of this port reads, and which file reads it. **348 arguments**: 277 read by the kernel, 14 by the loader, 67 by user space (one is read in more than one place).
+Every argument that the kernel, the loader or user space of this port reads, and which file reads it. **349 arguments**: 278 read by the kernel, 14 by the loader, 67 by user space (one is read in more than one place).
This is a catalogue of what exists and who reads it, not a manual. What an argument means is in the head of the file that reads it. The stable switches have a symbol in the configuration (`tools/hakios-config.py help SYMBOL`, `docs/configs.md`); the rest are the knobs of bring-up (a driver's steps, pauses, traces, test modes) and can change with the driver. Any of them can be given in a configuration with `CONFIG_BOOTARGS="name=value ..."`, which checks that each name is in this list. What the arguments of the two Metal paths do: [Metal on the Adreno](reference/metal.md#boot-arguments).
Layers: **K** the kernel, **L** the loader, **U** user space (through `sysctl kern.bootargs`).
-## GPU and display (75)
+## GPU and display (76)
| Argument | Layer | Read by | Configuration | Set by |
|---|---|---|---|---|
@@ -25,6 +25,7 @@ Layers: **K** the kernel, **L** the loader, **U** user space (through `sysctl ke
| `adreno_stream1` | K | `hakios.adreno.c` | `CONFIG_ADRENO_STREAM1` | |
| `adreno_watch` | K | `hakios.adreno.c` | `CONFIG_ADRENO_WATCH` | |
| `display_probe` | K | `hakios.adreno.c` | `CONFIG_DISPLAY_PROBE` | |
+| `fb_beam` | K | `MiniIOMobileFramebuffer.cpp` | `CONFIG_FB_BEAM` | |
| `fb_beat` | K | `MiniIOMobileFramebuffer.cpp` | `CONFIG_FB_BEAT` | |
| `fb_ca_hz` | K | `MiniIOMobileFramebuffer.cpp` | `CONFIG_FB_CA_HZ` | |
| `fb_diff` | K | `MiniIOMobileFramebuffer.cpp` | `CONFIG_FB_DIFF` | |
diff --git a/docs/metal-plan.md b/docs/metal-plan.md
index 46b7aec..ecd3136 100644
--- a/docs/metal-plan.md
+++ b/docs/metal-plan.md
@@ -1,7 +1,7 @@
# Metal on the Adreno: the plan, and where it stands
**Where it stands, 4 November 2026.** The window server draws through Metal on the phone, on two paths, and the plan below is done as far
-as that: hakios-metal at 100 to 104 frames a second in page swipes, UniXNU's Metal on Vulkan at 50 to 57, on a 120 Hz panel. 120 has not
+as that: hakios-metal at 100 to 104 frames a second in page swipes (109 in Settings' scroll), UniXNU's Metal on Vulkan at 50 to 57, on a 120 Hz panel. 120 has not
been reached. What to read now: [Metal on the Adreno](reference/metal.md) and [the measurements](reference/metal-measurements.md).
Everything below the next section is the record of how it went, with the dates, and says what was known then. <!-- FINAL-NUMBERS -->
diff --git a/docs/reference/metal-measurements.md b/docs/reference/metal-measurements.md
index bef1e8f..2fabd7e 100644
--- a/docs/reference/metal-measurements.md
+++ b/docs/reference/metal-measurements.md
@@ -12,23 +12,25 @@ been reached**: not on hakios-metal, not on metal2vulkan, and not on OpenGL ES.
| User space | the Darwin 16.5 user space, laid out from your own IPSW |
| Panel | 1080 x 2400 at 120 Hz |
| Rendered | 1125 x 2436, scaled onto the panel by the driver |
-| The run | `tools/metal-run.sh`: eight cores, `fb_hz=120 fb_threads=6 touch_poll_us=4000`, the round of `rc.jobs.bench` four times |
+| The run | `tools/metal-run.sh`: eight cores, `fb_hz=120 fb_threads=6 touch_poll_us=4000 wallpaper_freeze=1 metal_defer=1`, the round of `rc.jobs.bench` four times |
## The results
-Frames a second, 3 and 4 November 2026.
+Frames a second, 3 and 4 November 2026. hakios-metal as the last run of 4 November had it: `wallpaper_freeze=1 metal_defer=1 fb_beam=1`.
+metal2vulkan as measured on 3 November, before those.
<!-- FINAL-NUMBERS -->
| Motion | hakios-metal | metal2vulkan |
|---|---|---|
-| Page swipe | 100 to 104 | 50 to 57 |
-| Settings' scroll | about 90 | 41 |
+| Page swipe | 101 (100 to 104 over the runs) | 50 to 57 |
+| Settings' scroll | 109 | 41 |
| Opening an app | about 90 | not recorded |
-| Home button | 28 with `wallpaper_cache=1`; 78 with the wallpaper hidden | 41 to 57 |
-| GPU time a frame | about 10 ms at the home screen | 14 to 21 ms |
+| Home button | 92 | 41 to 57 |
+| Frames over 16.7 ms | 4% | not recorded |
+| GPU time a frame | about 10 ms at the home screen, 3 November | 14 to 21 ms |
-Both draw the system correctly.
+Both draw the system correctly. Not one of these is 120.
**hakios-metal, inside a swipe.** Once the finger has lifted, 185 of the animation's 205 frames take 8.3 ms, one refresh of the panel.
While the finger drags, frames come at 75 to 80 a second, and the window server waits 8 to 14 ms on GPU fences. The 100 to 104 in the
@@ -47,14 +49,16 @@ off and no texture was shadowed.
| Surfaces let go of as soon as their pixels are on the panel, not when the next frame comes | in `MiniIOMobileFramebuffer` | unchanged |
| The iPhone XR's screen class, 1.85 times fewer pixels | `fbwidth=828 fbheight=1792 fbscale=2 fbsubtype=1792` | idle GPU time 2.2 ms, not 6.8; gestures not faster; the wallpaper black |
| The iPhone 12 mini's screen class | `fbwidth=`, `fbheight=`, `fbscale=`, `fbsubtype=` | 103 to 107, with the red rdar://45025538 status bar |
-| The wallpaper hidden, for swipes | `wallpaper_freeze=2` | 101 to 103, as with it: the wallpaper is not what holds swipes under 120. It is what holds the home button |
+| The wallpaper hidden, for swipes | `wallpaper_freeze=2` | 101 to 103, as with it: the wallpaper is not what holds swipes under 120. It is what held the home button: 78 hidden, against 28 with `wallpaper_cache=1` |
+| The wallpaper's picture through `-drawViewHierarchyInRect:` | `wallpaper_freeze=1`, first version | one colour; with all of SpringBoard's windows hidden the screen itself was black. It now reads the IOSurface on the panel |
## What did help
-On hakios-metal, each as the commit that made the change measured it, in the order they were found.
+On hakios-metal, each as the commit that made the change measured it, newest first.
| Change | Before | After |
|---|---|---|
+| `wallpaper_freeze=1 metal_defer=1` | home button 50 (28 with `wallpaper_cache=1`); Settings' scroll 90; frames over 16.7 ms 9% | home button 92; scroll 109; 4%; swipes 101 |
| Eight cores, not one, for the first boot | first frame at 159 s | 86 s |
| `fb_threads=6`, not 3 | Settings' scroll 75 | 84 |
| `wallpaper_cache=1` | swipes 85 to 91; an app's close 40 | swipes 97 to 103; an app's close 22 to 30, slower: the poster changes under its zoom |
@@ -85,16 +89,20 @@ The panel reads the very buffer the driver writes. It takes the scan 8.3 ms to r
written across the line being read came out torn: a piece of the last frame and a piece of this one, moving bands with doubled icons and
text wherever something moved. Seen on the phone.
-PENDING: `fb_beam`, the default once its commit lands, writes each thread's rows behind the scan line, read from the interface's own
-`INTF_LINE_COUNT`, so that the next scan reads all of the new frame. The scan measured 2433 lines, 8338 us. The bands were gone. If the
-counter does not count as a line counter should, frames stay on their beat, and the log says so.
+`fb_beam=1`, the default, writes each thread's rows behind the scan line, read from the interface's own `INTF_LINE_COUNT`, so that the next
+scan reads all of the new frame. The scan measured 2433 lines, 8338 us. It is looked at a minute after the driver starts; if the counter
+does not count as a line counter should, frames stay on their beat, and the log says so. 2 to 16 frames in 5 s miss their scan.
-The frame rates with `fb_beam` are still being tuned, and the table at the top is without it.
+The bands were gone to the eye. That is the only evidence: `xl screenshot` cannot tell, because it sends live memory in pieces of 1 MiB, and
+the bands in its pictures are 243 rows apart.
+
+It costs no frames. The same run otherwise, 4 November:
<!-- FINAL-NUMBERS -->
-| With `fb_beam` | hakios-metal |
-|---|---|
-| Page swipe | being tuned |
-| Settings' scroll | being tuned |
-| Home button | being tuned |
+| | `fb_beam=1` | `fb_beam=0` |
+|---|---|---|
+| Page swipe | 101 | 99 |
+| Settings' scroll | 109 | 89 |
+| Home button | 92 | 81 |
+| Frames over 16.7 ms | 4% | 6% |
diff --git a/docs/reference/metal.md b/docs/reference/metal.md
index c51e53c..71d2f2f 100644
--- a/docs/reference/metal.md
+++ b/docs/reference/metal.md
@@ -5,7 +5,7 @@ measure it, and what is not known. The numbers: [Metal measurements](metal-measu
[the plan](../metal-plan.md).
**Status, POCO X5 Pro 5G, 3 and 4 November 2026.** Both paths draw the system correctly. hakios-metal is the faster: page swipes 100
-to 104 frames a second, Settings' scroll about 90. metal2vulkan: swipes 50 to 57, scroll 41. **120 frames a second has not been
+to 104 frames a second, Settings' scroll 109, the home button 92. metal2vulkan: swipes 50 to 57, scroll 41. **120 frames a second has not been
reached on either.** Neither is on by default: without `metal=1` the window server draws through OpenGL ES, as it always has.
<!-- FINAL-NUMBERS -->
@@ -119,25 +119,25 @@ Every argument is in [the catalogue](../boot-args.md), which is made from the so
| `metal_fps=passes` | plug-in | also every pass of one slow command buffer in 200, with its attached and touched colour attachments |
| `metal_fps=mainpass` | plug-in | also the draws of a pass of 40 draws or more over 4 ms (in sysmem, where draws are timed) |
| `metal_fps=draws` | plug-in | also each draw of a sysmem pass timed alone, and the time counted by program |
-| `metal_defer=1` | plug-in | the window server's command buffers recorded on a thread of hakios-metal's own: a draw costs its render thread about 5 us instead of about 40 |
+| `metal_defer=1` | plug-in | the window server's command buffers recorded on a thread of hakios-metal's own: a draw costs its render thread about 5 us instead of about 40. `tools/metal-run.sh` sets it |
| `metal_luma_boost=1` | plug-in | draws `luma_boost`, which is otherwise left out where the library has its own |
| `wallpaper_cache=1` | SpringBoard | the wallpaper's window rasterized by the window server |
+| `wallpaper_freeze=1` | SpringBoard | the wallpaper as one still picture: at the home screen the window of the icons is hidden for a moment (they blink once a boot), the pixels of the IOSurface on the panel (`kern.hakios.fb_surface`) become one opaque view in the wallpaper's window, and its layers are hidden. It gives up: the wallpaper does not change until the next boot, and the lock screen shows the same picture. `tools/metal-run.sh` sets it |
| `wallpaper_freeze=2` | SpringBoard | the wallpaper hidden: what it costs, measured |
-| `wallpaper_freeze=1` | SpringBoard | the wallpaper's window as one still picture. In this tree the picture comes out one colour and is not used. PENDING: taken from the IOSurface on the panel (`kern.hakios.fb_surface`) |
| `ui_lite=1`, `ui_lite=0` | SpringBoard | Reduce Transparency and Reduce Motion on, off again. Without it the settings are left alone |
| `fbwidth=`, `fbheight=`, `fbscale=`, `fbsubtype=` | framebuffer | another iPhone's screen class: `fbwidth=828 fbheight=1792 fbscale=2 fbsubtype=1792` is the XR's |
| `touch_poll_us=N` | touch driver | the touch screen read every N microseconds. The driver's default is 8000; `tools/metal-run.sh` sets 4000 |
| `fb_hz=120`, `fb_threads=6`, `fb_measure=1` | framebuffer | the driver's beat at the panel's rate, six processors scaling a frame onto the panel, the panel's own rate measured once |
-| `fb_beam=1` | framebuffer | PENDING, not in this tree's kernel until that commit lands. The default: each thread's rows are written behind the panel's scan line. `fb_beam=0`: whenever the beat comes, as before. [Tearing](metal-measurements.md#tearing) |
+| `fb_beam=1` | framebuffer | the default: each thread's rows are written behind the panel's scan line. `fb_beam=0`: whenever the beat comes, as before. [Tearing](metal-measurements.md#tearing) |
-PENDING also: the sysctl `kern.hakios.fb_surface`, the IOSurface last put on the panel.
+And one sysctl: `kern.hakios.fb_surface`, the IOSurface last put on the panel.
## Measure
```sh
tools/metal-run.sh # 180 s, hakios-metal; the summary in logs/<time>-metal.txt
MORE="metal_m2v=1" tools/metal-run.sh # the same on metal2vulkan
-MORE="wallpaper_cache=1" tools/metal-run.sh # any argument beside the defaults; a later one of a name wins
+MORE="wallpaper_cache=1" tools/metal-run.sh # any argument beside the defaults
```
An image built with `RC_JOBS=rc.jobs.bench` unlocks, waits a minute for the start-up work to end, and does the same round four times:
@@ -147,9 +147,13 @@ four times in the same state of the system, and runs can be compared.
`tools/metal-run.sh` takes the phone from Android, its bootloader or the loader, uploads the system image, runs, and writes a summary:
`tools/frames.py`'s frames per gesture, the plug-in's `fps:` lines, what was refused, the frames on the panel, the shader cache and any
crash. It sets `gpu=1 metal=1 metal_fps=1 touch_lat=1 touchscreen=1 gpu_recover=1 anim_max=1 bootcpu=7 cpus=8 cpufreq=1 fb_hz=120
-fb_measure=1 fb_threads=6 touch_poll_us=4000`, the path of QuartzCore's library, and (unless `PERSIST=0`) `ufs=2 ufs_write=1
+fb_measure=1 fb_threads=6 touch_poll_us=4000 wallpaper_freeze=1 metal_defer=1`, the path of QuartzCore's library, and (unless `PERSIST=0`) `ufs=2 ufs_write=1
var_store=1`, which keeps `/private/var` in your `darwin` partition so that shader stages are compiled once.
+`MORE=` adds arguments at the end. The kernel's are its own to resolve, but the plug-in's and SpringBoard's are found with `strstr`, which
+takes the first of a name: `MORE` cannot turn off the script's `wallpaper_freeze=1` or `metal_defer=1`, and to run without them, change
+`ARGS` in the script.
+
`tools/frames.py RUN.log [MORE.log ...]` on its own reads the `tl:` lines of `touch_lat=1`. For each gesture it gives the frames a
second while frames came, the share of frame steps over 16.7 ms, 33 ms and 8.3 ms, and where a slow frame's time went. A window server
drawing through Metal says no `tl: g`: its frames are counted by the swap that handed each over, so `draw` and `idle` are 0 there,
@@ -159,11 +163,13 @@ meaning unknown.
- **Under 120.** While a finger drags, the window server waits 8 to 14 ms on GPU fences and frames come at 75 to 80 a second; after
the finger lifts, 185 of 205 frames of a swipe take 8.3 ms. The cause of the wait is not established.
-- **The home button** takes 28 frames a second with `wallpaper_cache=1` and 78 with the wallpaper hidden. The wallpaper is many
- full-screen layers from another process, and rasterizing its window does not stop them being composed again.
+- **The wallpaper is frozen to get the home button's rate.** 92 frames a second with `wallpaper_freeze=1`, 50 without it or
+ `wallpaper_cache=1`, 28 with `wallpaper_cache=1`. It is many full-screen layers from another process, and rasterizing its window does
+ not stop them being composed again. A wallpaper that moves or changes costs that, and it is not solved.
- **metal2vulkan renders each frame to a tiled image and merges it back with a compute pass.** The linear attachment path stays unused
because a second, non-linear attachment is in the pass, and the extension wants every colour attachment linear.
-- **Tearing.** The panel reads the one buffer the driver writes. `fb_beam` is the answer being tuned; it is not in this tree yet.
+- **Tearing.** The panel reads the one buffer the driver writes. `fb_beam` writes behind the scan; 2 to 16 frames in 5 s still miss
+ their scan, and whether the panel tears less is so far for the eye: [Tearing](metal-measurements.md#tearing).
- **Not the same stack as UniXNU's.** Theirs runs on the Adreno 740 with its own kernel driver, [Adreno740](https://github.com/UniXNU/UniXNU/blob/main/docs/drivers/adreno740.md),
and a newer system. Only the part above that driver was taken. What is measured here says nothing about theirs.
- **hakios-metal is not pinned.** `userland/build.sh` takes whatever is beside the tree; `metal_defer=1` needs its
diff --git a/docs/ru/metal.md b/docs/ru/metal.md
index eb9bcd8..c7b6262 100644
--- a/docs/ru/metal.md
+++ b/docs/ru/metal.md
@@ -2,7 +2,7 @@
> **Обновление, 4 ноября 2026.** Этот разбор написан в октябре, и вывода раздела 4 («(В): ни то, ни другое») больше нет: теперь оконный
> сервер рисует через Metal на Adreno 642L телефона, двумя путями, и оба рисуют правильно. **hakios-metal** (близко к пути (А) раздела 4,
-> без Vulkan: AIR через NIR в ir3, собственные пакеты PM4): перелистывание страниц 100–104 кадра в секунду, прокрутка Settings около 90.
+> без Vulkan: AIR через NIR в ir3, собственные пакеты PM4): перелистывание страниц 100–104 кадра в секунду, прокрутка Settings 109, кнопка «домой» 92.
> **metal2vulkan** (стек UniXNU: фронтенд AdrenoMetal, metal2vulkan, Turnip — пути, которого в разделе 4 не было): перелистывание 50–57,
> прокрутка 41. Панель 120 Гц; **120 кадров в секунду не достигнуто**. Без `metal=1` система по-прежнему рисует через OpenGL ES. Стена с
> `default.metallib` снята не плагином: `tools/ca-metallib.py` делает эту библиотеку на вашей машине из того, что вы даёте сами. Что
diff --git a/docs/windows.md b/docs/windows.md
index 8a39546..49409fa 100644
--- a/docs/windows.md
+++ b/docs/windows.md
@@ -85,7 +85,7 @@ cp userland/root.apfs userland/system.apfs /mnt/d/.../hakios/userland/
# Git Bash, in the Windows checkout (the phone in Android is fine: the script takes it into the loader):
tools/metal-run.sh # 180 s; the summary in logs/<time>-metal.txt
MORE="metal_gmem=1" tools/metal-run.sh # with tiled rendering (each pass left in sysmem says why)
-MORE="wallpaper_cache=1" tools/metal-run.sh # any boot-argument beside the defaults; a later one of a name wins
+MORE="wallpaper_cache=1" tools/metal-run.sh # any boot-argument beside the defaults
SHOTS=20 tools/metal-run.sh # and a screenshot every 20 s, logs/<time>-shots/
```