Linux PhonesEnglish·Русский
Linux PhonesEssenceThe ideaHow close we areThe phone in the labFeaturesDevicesSoC familiesTestsResearchDecisionsBacklogLandscapeMade by work

The phone in the lab

✓ Why it exists✓ What it must reach✓ How each step is delivered and proven✓ What is happening now

Why it exists

This is one particular phone - a Xiaomi POCO X3 NFC, known by its codename surya - kept on a desk and plugged into a lab machine, so that making Linux work on it can be done carefully, the same way each time, and without ever leaving it broken.

What it must reach

Working
4/6Boots, shows, touches, connects
3/4Sound
3/3A real phone: calls, messages, data
Perfection
12/21Every part works
Ongoing perfection
0/1Tested every day
1/4Its fixes upstream
Readinesslevel 0 of 9

1 / 6 milestones done

How each step is delivered and proven

Boots, shows, touches, connectsin progress
devlab flashtoollab-tools

Writes the pristine image with the device's known fixes baked in, and fingerprints its device tree first.

Any flash gives the same known phone - found out the hard way.

devlab healthchecklab-tools

Twenty-two checks on the phone itself - the sound card, the amplifiers, the modem, Wi-Fi, storage - compared with everything that passed before.

The phone is the reference: it must not quietly get worse.

Soundin progress
devlab heartestlab-tools

Plays a tone on each speaker and hears it through a microphone in the lab, measured against the silent room. It waits for a microphone fixed in place: its first results, from a microphone that moved, were withdrawn.

A driver that loads proves nothing about sound. A machine should hear it.

The device's manifesttoolsurya-lab

The stereo profile, the corrected amplifier driver and two masked services, written down once and baked into every flash.

A fix made by hand is lost at the next flash.

A real phone: calls, messages, datadone
The modem checkschecklab-tools

Whether the modem is seen and ready for calls, messages and data - not yet whether a call goes through.

Seen is not the same as working; this is the first rung only.

Every part worksin progress
The parts tablepractice

Each part of the phone with its state, taken from the checks and the records of the work.

So what is left to do is a list, not a guess.

Tested every daynot known yet
A part's status is derived (derive/support-status.sql, run t…
devlab watchgathererlab-tools

The checks after every start, by themselves, written down.

Tested once is not tested.

Its fixes upstreamin progress
The upstream queuepractice

The amplifier fixes and the Sxmo profile prepared as patches with their maintainers named.

So every phone on this chip gets them.

What is happening now

Made by work

920 commits in the last 90 days latest release lpoco-v0.14.1 · 2026-11-18

✓ device-template: check✓ device-template: gather✓ device-template: tad✓ docs: ci✓ docs: feeds✓ docs: gather◐ docs: pages✓ docs: release✓ lab-tools: Packages✓ lab-tools: Release✓ lab-tools: ci✓ lab-tools: gather✓ surya-lab: check✓ surya-lab: gather✓ surya-lab: tad✓ sxmo-deviceprofiles: check✓ sxmo-deviceprofiles: gather

2026-08-21: 0 commits2026-08-22: 0 commits2026-08-23: 0 commits2026-08-24: 0 commits2026-08-25: 0 commits2026-08-26: 0 commits2026-08-27: 0 commits2026-08-28: 0 commits2026-08-29: 0 commits2026-08-30: 0 commits2026-08-31: 0 commits2026-09-01: 0 commits2026-09-02: 0 commits2026-09-03: 0 commits2026-09-04: 0 commits2026-09-05: 0 commits2026-09-06: 0 commits2026-09-07: 0 commits2026-09-08: 0 commits2026-09-09: 0 commits2026-09-10: 0 commits2026-09-11: 0 commits2026-09-12: 0 commits2026-09-13: 0 commits2026-09-14: 0 commits2026-09-15: 0 commits2026-09-16: 0 commits2026-09-17: 0 commits2026-09-18: 0 commits2026-09-19: 0 commits2026-09-20: 0 commits2026-09-21: 0 commits2026-09-22: 0 commits2026-09-23: 0 commits2026-09-24: 0 commits2026-09-25: 0 commits2026-09-26: 0 commits2026-09-27: 0 commits2026-09-28: 0 commits2026-09-29: 0 commits2026-09-30: 0 commits2026-10-01: 0 commits2026-10-02: 0 commits2026-10-03: 0 commits2026-10-04: 0 commits2026-10-05: 0 commits2026-10-06: 0 commits2026-10-07: 0 commits2026-10-08: 0 commits2026-10-09: 0 commits2026-10-10: 0 commits2026-10-11: 0 commits2026-10-12: 0 commits2026-10-13: 0 commits2026-10-14: 0 commits2026-10-15: 0 commits2026-10-16: 0 commits2026-10-17: 0 commits2026-10-18: 0 commits2026-10-19: 0 commits2026-10-20: 0 commits2026-10-21: 0 commits2026-10-22: 0 commits2026-10-23: 0 commits2026-10-24: 0 commits2026-10-25: 0 commits2026-10-26: 0 commits2026-10-27: 0 commits2026-10-28: 0 commits2026-10-29: 0 commits2026-10-30: 0 commits2026-10-31: 0 commits2026-11-01: 0 commits2026-11-02: 0 commits2026-11-03: 0 commits2026-11-04: 1 commits2026-11-05: 7 commits2026-11-06: 0 commits2026-11-07: 0 commits2026-11-08: 0 commits2026-11-09: 24 commits2026-11-10: 100 commits2026-11-11: 51 commits2026-11-12: 6 commits2026-11-13: 0 commits2026-11-14: 1 commits2026-11-15: 0 commits2026-11-16: 20 commits2026-11-17: 453 commits2026-11-18: 257 commits
docs holds only what helps every device; each device has its own open base; docs derives progress from themin progress

Both lanes record only in their own base (google-walleye-lab #15, surya-lab #136; docs #353, #360); docs pulls their parts daily (feed-device-bases, #355; surya's base named #361)…

How a device repository takes later changes of device-template beyond idealkb's generic filesin progress

Decided 2026-11-17 (idealkb decision 2026-11-17-chain-follow-by-slice): the same pin-and-follow slice as idealkb, not a fork, subtree or Copier. Done: device-template lists what it…

The audio DSP sleeps when nothing playsin progress

2026-11-17 keeper-6: two floor tests (adsp stopped; adsp+cdsp+modem stopped) still gave cxsd 0, aosd 0, ddr 0 - the DSP is not what holds the SoC (research 2026-11-17-adsp-stopped-…

Our own forks of each upstream we patch: fixes worked and proven there, carried until upstream takes them, mailed as working patches by the authorin progress

Decision 2026-11-18-upstream-forks. Forks live under grenudi (grenudi/sxmo-utils, grenudi/linux; transferred from the org); three fixes written on topic branches (sxmo series of 3,…

Upstream work is kept as records: upstreams and upstream_items (idealkb 0.8), the upstream-* items headed in themin progress

Seeded 2026-11-17: six upstreams, nine items (sxmo profile sent; tas2562 x2, WCD series, UCM, pd-mapper, tqftpserv, PR 60 comment as drafts); patches and messages copied into upstr…

Start the upstreams lane: one lane coordinator for the forks and every outgoing seriesin progress

Lane coordinator upstreams-coordinator started 2026-11-18. Forks: grenudi/sxmo-utils (mirror of sr.ht ~mil/sxmo-utils), grenudi/linux (fork of sm7150-mainline/linux). Where each se…