Files
Ryan Vogel 8da0cf8291 Align Android typing with iOS and add German and Bokmål layouts and models
Apply R1's English typo and contraction rules before spatial search and
match its language weight, shortlist and valid-spelling margins. A mapped
SCOWL spelling list supplies the validity check missing on Android. Scale
vertical spread and the missing-space cost to real Android row geometry so
"seehkw" still splits into "see how". Keep the existing en/es model bytes.

Build the new German and Bokmål HXTM files with the shared iOS writer.
German uses all Google Books v3 shards; Bokmål uses NB book counts filtered
by the complete 2022 Ordbank snapshot. Pin the new assets, credit their
sources and licences, and ship their real layouts, accents and suggestions.

Replace the post-setup list with the iOS-style Home, local Dictate bar and
four settings pages. Follow the system language by default; make the spoken
language switchable on space, and optionally pin an independent layout.

Verified on the Studio API 35 ARM64 emulator: 1,027 English and 1,374 Spanish
word errors vs R1's 1,163 and 1,387 on the same 2,000 synthetic sentences
per language. Ran all five unit tests in debug and release, inspected the
packaged assets, and checked external-editor suggestions, corrections, undo
and offline microphone insertion, plus Home and settings in both themes.
The Swift reader round-tripped both new models; the identical iOS files
are in the separate local commit 230a437e.
2026-11-20 12:26:13 -05:00
..

Android typing benchmark

On the same iOS R1 word models and synthetic taps, Android now has 136 fewer English word errors and 13 fewer Spanish word errors than iOS. The biggest part of the old 298-error English deficit was a missing step before spatial decoding: porting the English contraction and typo rules alone recovered 231 errors.

Same-model results

Each language has 2,000 held-out synthetic Tatoeba sentences. English has 13,870 reference words; Spanish has 13,301. Errors are word insertions, deletions and substitutions, ignoring case and terminal punctuation. A missing space can change the word count. No user-specific offsets are applied.

Decoder English errors English WER English exact / 2,000 Spanish errors Spanish WER Spanish exact / 2,000
Raw hit keys 4,689 33.8068% 160 5,343 40.1699% 94
Phase 3 Android 1,461 10.5335% 983 1,338 10.0594% 1,086
iOS R1, same HXTM, no offsets 1,163 8.3850% 1,154 1,387 10.4278% 1,064
Phase 4 Android 1,027 7.4045% 1,249 1,374 10.3301% 1,070

The installed APK ran on the Studio’s Android 15/API 35 ARM64 emulator (4 vCPUs, 4 GiB guest RAM). It received the original 402-point iOS key geometry, hit-key sequence, coordinates and separators. Letters request suggestions and spaces request replacements and predictions, exactly as in the Android IME. English and Spanish HXTM files are byte-identical across platforms. The iOS reference is the recorded output-r1-decoder-{en,es}.json output, before calibration. The earlier iOS prototype’s 6.71% English WER used a different model; it is not the comparison target. Phase 3 measurements · historical iOS aggregate, including calibration · Phase 4 replay counts and latency.

Where the 298 English errors came from

We changed one decision rule at a time on the same 2,000 English inputs. The diagnostic runner used scratch copies of the Kotlin classes on Android. Its phase 3 and phase 4 error and agreement counts matched the installed APKs. Deltas below are conditional on the preceding rows; they are not independent effects.

Cumulative change Errors Δ errors Normalized outputs matching iOS / 2,000
Phase 3 1,461 — 1,517
Apply iOS’s English contractions/common typos before search 1,230 −231 1,724
Increase English word/pair weight from 1.25 to 1.5 1,255 +25 1,740
Score only the five best whole-word spatial readings 1,207 −48 1,762
Use R1’s 0.26-row-pitch vertical spread on the recorded layout 1,186 −21 1,832
Use R1’s 6.0 missed-space penalty 1,196 +10 1,864
Protect valid English spellings outside HXTM (phase 4) 1,027 −169 1,773
Diagnostic only: fixed Android 3.9 split penalty even at iOS pitches 1,007 −20 1,751

The R1 scoring and correction order alone closed 265 of the 298 errors. The remaining 33 were a net WER difference, not 33 sentences with one known cause. The intermediate decoders disagreed on 138 alignment spans; in 54, iOS retained a literal absent from HXTM. iOS can ask UITextChecker whether such a spelling is valid. Android had treated every missing spelling as a nonword. It now uses the same valid-literal cost (15 instead of 22) and replacement margin (7 instead of 2), with a bundled public SCOWL list. That list is not Apple’s dictionary. Lower WER is not identical decisions: the final engines produce the same normalized word sequence on 1,773 English and 1,906 Spanish sentences. Spanish made 36 more errors than phase 3 but agreed with iOS on 84 more sentences and still beat the same-model iOS WER.

The production IME scores actual key centres. Android’s rows are shorter than the test layout, so its vertical spread has a floor based on the iOS reference aspect ratio (56 / 39.5). This floor is inactive on the replay geometry. A fixed 6.0 split penalty ranked “seeks” ahead of “see how” for the real centre taps for seehkw. The IME now scales that squared-distance cost with row height, floored at the existing Android 3.9 prior (2% omitted separators). The measured Android pitch was 106.2 × 131 px, giving a cost of about 4.5; the recorded iOS layout uses exactly 6.0. This keeps the iOS behavior on its geometry and fixes the Android regression without a sentence-specific exception. The external editor received we need to do research into this and see how well we can get it from we need tk dk research into this and seehkw well we can get it. Tapping space after we need tk produced we need to ; one backspace restored we need tk.

Checks in an external editor

The Studio sent touch events to Hex’s visible keys and suggestion strip, then read the separate editor’s text. With Wi-Fi off and airplane mode on:

Layout Typed and completed with a model suggestion Space-triggered correction
Español Nos vemos mañan → Nos vemos mañana; ¿ and ¡ inserted from the second symbols page nos vemos mañnaa → nos vemos mañana
Deutsch Bären mögen süße Äpfe → Bären mögen süße Äpfel; held s and slid to ß vielen dnak → vielen dank
Norsk (Bokmål) Jeg lærer norsk på lørda → Jeg lærer norsk på lørdag; next words included kveld, morgen and og tusen takkk → tusen takk

Automatic on a fresh install displayed English, followed the system locale to Español, and returned to English when the system did. With layout pinned to Deutsch and dictation set to Español, the keyboard kept the German letters and showed Español on the space bar.

Models and licences

All four HXTM v3 assets are uncompressed and memory-mapped from the APK; Gradle verifies the pinned hashes. There is no SymSpell data. German and Bokmål have the same binary format as the iOS files; the Studio checked them with the Swift model reader as well as the Android IME. The two new files are also in the iOS checkout’s ios/HEXKeyboard/TypingModel/ folder, local commit 230a437e. The Swift reader round-tripped every spelling and every stored pair cost. This verifies file compatibility, not iOS device behavior.

Language Words Word pairs Source of counts Source of spelling
English 86,133 417,480 Google Books v3, 24 unigram / 589 bigram shards SCOWL 2020.12.07
Spanish 110,000 326,366 Google Books v3, 3 / 73 shards; existing model unchanged RLA-ES Hunspell
German 95,000 368,534 Google Books v3, all 8 / 181 German shards German alphabetic corpus spellings
Bokmål 95,000 370,560 NB N-gram 2026 book unigrams and bigrams, language nob Norsk ordbank, Bokmål full forms

The shared iOS builder, SHA-256 cba009fe227632d9f8d176055f26ca34d5eb6f88a7cbd947955d8f9142878317, sums counts from 1980–2019, selects informative pairs and writes quantized probabilities. The German/Bokmål adapter uses the same writer. For German, it uses the iOS shard reader and filters lowercased words to its alphabet. For Bokmål, it NFC-normalizes and lowercases the words, filters vocabulary to standard Bokmål forms in the 1 February 2022 Ordbank fullformsliste.txt (OPPSLAG, normative and current in that snapshot), and only retains pairs whose two words are in that vocabulary. The September 2026 inflection export alone dropped common uninflected words such as og, på and det; it was not used in the shipped model. The complete snapshot supplied 617,139 distinct forms. Of 20,096,783 observed in-vocabulary pair types, 394,825 met the shared writer’s count and information thresholds; 370,560 fit the model budget.

Reproduce on the Studio

  1. Export only the allowlisted synthetic IDs where the iOS inputs already reside. The exporter accepts test-0…1999 (English) or es-test-0…1999 (Spanish), empty context, no logged flag, and key-aligned finite x/y pairs. It exports only ID, intended text, synthetic hit keys/taps and the matching uncalibrated iOS output. Never transfer the mixed source, labels or personal offsets.

    mkdir -p "$T/bench"
    for lang in en es; do
      python3 benchmark/typing/export_synthetic.py "$IOS_BENCH/input.json" \
        "$IOS_BENCH/output-r1-decoder-$lang.json" "$lang" > "$T/bench/$lang.jsonl"
    done
    
  2. In the synced Android project with JDK 21, Android SDK 35 and the designated emulator:

    ./gradlew assembleDebug test
    adb install --no-incremental -r app/build/outputs/apk/debug/app-debug.apk
    sh benchmark/typing/replay.sh
    

    The Java replay shim executes the installed APK’s Kotlin classes with Android’s app_process. The output is aggregate WER, normalized sentences matching iOS and per-key timing (median/p95/max). Timings exclude loading, JSON parsing, evaluation, editor IPC and screen paint. Phase 3 timed the separate editor’s text-change callback from key-up (letter median/p95: 1.409/2.589 ms; space: 3.161/4.428 ms). The Phase 4 replay measures decoder work, not that end-to-end path or a physical handset.

  3. To rebuild the new typing models, use Python 3.9+, curl, gzip and zstd with scratch storage. German streams each shard and caches its counts. The Bokmål adapter resumes the two large NB archives in validated byte ranges and verifies their SHA-256 alongside the Ordbank snapshot. The SCOWL English validity list has a separate pinned-source generator:

    mkdir -p "$T/models" "$T/source"
    python3 benchmark/typing/build-layout-model.py de "$T/source/de" "$T/models/de.hextm"
    python3 benchmark/typing/build-layout-model.py nb "$T/source/nb" "$T/models/nb.hextm"
    curl -fsSL https://downloads.sourceforge.net/project/wordlist/SCOWL/2020.12.07/scowl-2020.12.07.tar.gz -o "$T/source/scowl.tar.gz"
    python3 benchmark/typing/build-valid-words.py "$T/source/scowl.tar.gz" \
      app/src/main/assets/typing/en.hextm "$T/models/en.valid"