The phone's queue
What only the phone can prove, taken up by its keeper one change at a time - each with the test that proves it.
Open · 39
Bluetooth s2idle: 20x15 s and 3x120 s way-back cycles bt-on, wakeup ON, with hci_qca dyndbg and geni irq trace; read storm vs crash order
surya-lab proven by bt-no-irq-stormRead-only on the phone apart from trace switches; watchdog armed, no unplug. Decision 2026-11-18-bt-suspend-way step 1.
Standby current measured beside Android's
surya-lab proven by soc-sleeps waits on the author back to unplug, and the Bluetooth suspend fix (ba…r4 SCORED: aborted/partial, unscorable (4 samples, median 120 mA, 63% asleep); aborted by irq 157 + BT SSR at 22:40:48; hang after = sxmo suspend loop on stuck BT SSR, rfkill D-state. Next r5: BT off…
One-shot dtb: CTS pull-down in qup-uart3-sleep like sc7180-trogdor; same cycles as bt-trace-cycles
surya-lab proven by bt-no-controller-crashStep 2. Keep the dtb out of the kept kernel until it measures better.
sxmo autosleep gate: no rtcwake while hci0 is not UP or an rfkill is in D state
surya-lab proven by bt-rfkill-not-stuckStep 4, independent of the others: removes the r4 wedge whatever the controller does.
After one panic try: unlock by the author, then read /data/vendor_ce/0/ramoops as root
google-walleye-lab proven by test walleye-panic-text: a research row quoting the first panic lines (Kernel panic - not syncing: ...) from the ramoops file, or recording that the file is absent for this kind of reboot waits on the author's unlock after the try; Android on a must not be…Ramoops region 0xa1100000 (2 MiB) survives the warm reset; the vendor init encrypts it after unlock. Try may be any existing image that panics (gadget3), no new build.
Sleep hook: unbind 88c000.serial:0 from hci_uart_qca before suspend, bind after (never rfkill); same cycles plus BT audio reconnect
surya-lab proven by bt-hci0-upStep 3, only if steps 1-2 leave controller crashes. Hazard: BT-off s2idle hung twice; run with watchdog and ramoops armed.
FastRPC helpers stopped across suspend; the sensors back
surya-lab proven by motion-and-light2026-11-18 keeper: stop/start around suspend measured 3/3 crash-free with sensors back (research 2026-11-18-sensorspd-stopped-no-adsp-crash). Left: same via sxmo/systemctl suspend, then done. 2026-11…
Waking from deep sleep for calls and messages
surya-lab proven by wakes-for-call waits on the SIM back in surya (the author took it out 2026-11-17) an…On the floor reached above: the modem's IPCRTR glink wakeup enabled (/sys/bus/rpmsg/devices/4080000.remoteproc:glink-edge.IPCRTR.-1.-1/power/wakeup), ModemManager's quick suspend/resume quieting the m…
Proximity blanks the screen at the ear in a call
surya-lab proven by proximity-readsDecided 2026-11-17 (research-sensor-hub, decision 2026-11-17-sensors-registry-kept-current). After sensors-without-crash. The sensor is surya's stk3a5x infrared one (not ultrasonic: nothing in the mic…
Find who holds the SH0 x=1,y=3 sleep vote and drop it
surya-lab proven by soc-sleepsPaused 2026-11-17 by decision 2026-11-17-floor-read-the-entry: read the entry first (floor-entry-trace), then decide whether the SH0 owner hunt resumes.
The phone cannot stay off: shutdown and a charger both boot pmOS
surya-lab waits on the decision of a feature research session: the author has h…Seen 2026-11-09. poweroff in pmOS boots pmOS again. The same shutdown from the EOS recovery on the phone stays off, until a charger is plugged in; then pmOS boots instead of Android-style off-mode cha…
GPS: a component and a failing test, so location can be measured
surya-lab proven by gps-fix waits on the decision of a feature research session: the author has h…The author, 2026-11-17: lp-connected needs the feature gps, but components has no GPS row, so nothing can measure it. Add the component and a failing test first; on SM7150 location comes through the m…
Bluetooth pairs and carries audio: from partial to works
surya-lab proven by bt-pairsThe author, 2026-11-17: bluetooth is partial (controller and powered pass). A works test: pair with a device the lab keeps, carry audio or a file; witnessed where a person must confirm.
VoLTE and emergency calls, to finish calls and messages
surya-lab proven by volte-callThe author, 2026-11-17: confirm first whether today's working calls go over VoLTE (Germany has switched 3G off; read the modem's call and IMS state during the daily echo call). Emergency calls are pro…
Verify headphone, mic and earpiece status directly on hardware instead of relying on the secondhand pmaports note
surya-labThe source only confirms mic/earpiece are broken as a group; headphone output specifically was never separately confirmed one way or the other.
Ask each camera slot what it is
surya-lab proven by image-sensorThe first step of the cameras: a test device tree that only powers a slot (supplies, clock, reset), booted once as the second entry; then the chip's identity register read over its control bus. Turns…
Image sensors: described, then identified, then seen
surya-lab proven by image-sensorKnown (research/cameras.md): the pipeline and all three control buses are bound; no sensor is described, which alone is why the cameras are dark. The vendor's kernel gives the wiring of seven sensor s…
Reach a hung or crashed walleye without a display: warm reset, pstore, UART
google-walleye-lab proven by after a deliberate panic the next boot lets the keeper read the panic log from /sys/fs/pstore (test: walleye-pstore-panic)ramoops at 0xa1810000/0x200000, qcom_wdt.arm_on_probe=1, watchdog.open_timeout=300, reboot=w (porthole); the Pixel debug cable is not in the lab.
Display: Samsung S6E3FA5 command-mode panel through DPU/DSI
google-walleye-lab proven by the DRM connector is connected and a test pattern is seen by a person (test: walleye-display-pattern) waits on walleye-ufs-readonly (not required) / walleye-first-fastboot…No mainline driver; start from the out-of-tree S6E3FA5 driver (OnePlus 5) and porthole's sw43402 cmd-mode work for the DPU side; init sequence from the GPL downstream dtsi; reset gpio94, TE gpio10 (wa…
Read the bootloader's own reason for Load Error over the Android Debug Cable (UART)
google-walleye-lab proven by a captured serial log of one refused control try that names the failing step (LoadImageAndAuth, dtbo, vbmeta or other), attached to a research row waits on the author's debug cableThe bootloader logs the reason to the serial console; the Nura wiki names the Pixel 2 Android Debug Cable. Hands needed; the phone itself is not changed.
dtbo_b stub with overlay id for walleye - only if the control boots and e,f still end in Load Error
google-walleye-lab proven by walleye-dtbo-stub-boot: after the stub, fastboot boot of e or f leaves fastboot; stock dtbo flashed back and its hash equals the one from the zip waits on the author's word (a write to the phone)A write to the phone: needs the author's word and the way back first (stock dtbo from the LineageOS zip read in walleye-loaderror-stock-ids, flashed back with fastboot flash dtbo_b). Overlay id for wa…
Touch: Synaptics RMI4 on blsp1_i2c5 (0x20, irq gpio125, reset gpio89)
google-walleye-lab proven by evtest shows touch events from the RMI4 device when the panel is touched (test: walleye-touch-events)Mainline rmi_i2c driver; supplies pm8998 l6 and l28; xd boards add a pmi8998 power gpio - which board revision the lab phone is, is not known.
UFS probes and the partitions are listed, read-only
google-walleye-lab proven by lsblk in the initramfs lists the UFS LUNs and by-name partitions without a write (test: walleye-ufs-lsblk)Enable ufshc + ufsphy with the vcc/vccq rails from the wahoo dtsi; mount nothing, write nothing; this is also the way to read walleye's own boot.img header.
The audio processor signalling handover every second
surya-labMeasured in the test kernel: 'Handover signaled, but it already happened' once a second from 11 s after boot (54 by 65 s), with or without audio. Also seen in a stock boot's crash memory. Likely an in…
tests/health/base/bt-suspend.sh in the suite, pushed to the phone with the runner
surya-lab proven by bt-hci0-upLanded with the research; the keeper puts it on the phone with lpoco lab suite put now.
Boot the current sm7150-mainline kernel on the phone via lab-agent and record dmesg + audio card list
surya-labThe first real job: proves the whole lab-agent loop end to end on real hardware, and gives a verified baseline instead of secondhand notes.
Why the AOP does not ack QMP sends (qcom_aoss_qmp c300000)
surya-lab proven by soc-sleepsLower rank (research 2026-11-17-sh0-and-aop-research: node equals sm8150/sc7180, serves only the aoss knobs, hypothesis 5). Read only: dump msgram descriptor and mailbox words (magic, version, mcore/u…
Read all power-domain idle_states rows and regulator_summary users across one way-back cycle 15 bt-on (read-only)
surya-lab proven by soc-sleepsSettles why the cluster S2idle column is 0 (wrong row/domain or a path that did not count) and lists the rails that stay on in suspend. Write the output into the cycle log. Watchdog armed.
Silence what wakes the CPUs in suspend, one source per cycle
surya-lab proven by suspend-irq-quietOnly if floor-entry-trace shows interrupts through the cycle (Odin 2 was held by an SD-controller IRQ storm of ~30/s, armada#274). Take the top source from the delta, quiet it by a runtime step (drive…
If SH0 stays: the other TAG_ALWAYS QUP and crypto consumers, one per cycle
surya-lab proven by soc-sleepsOne-shot dtb per change: the serial toward SLAVE_LLCC (sm7150.dtsi ~1259), then the crypto engine (~460), then the rest of the QUP ALWAYS paths; each judged by the sleep-set flush and soc-sleeps. Skip…
Standby current: battery-only suspended cycle of 10 minutes, charge_counter delta over time
surya-lab proven by standby-currentNeeds the cable out for the window (the witness's hands) or the fuel gauge's discharge read while charging is held off; the RTC wakes the phone and the cycle log is read after. Pass: under 15 mA avera…
A debug kernel that dumps held votes in late suspend
surya-lab proven by soc-sleeps waits on floor-read-holders and the subtractions aboveOnly if the reads above leave the holder open: a debug patch (builder) with a pm notifier / syscore op that prints clk enable counts, regulator use counts and icc votes at dpm_suspend_late, out of tre…
Allow USB runtime PM (power/control auto on the HS PHY and the dwc3 controller) for one cycle and read counters and current
surya-lab proven by soc-sleepspmaports#4846: lowers draw slightly and keeps USB from holding CX. Needs the lab link to survive: keep the watchdog armed, one change per cycle.
Under Phosh the PC loses the phone over USB
surya-labAfter switching to Phosh (2026-11-09) the PC showed no USB device for the phone, so no SSH over USB; the user saw the same before, in an earlier Phosh try. Unclear yet: Phosh changing the USB gadget,…
Witnessed: cover the proximity sensor at the ear, see the reading go near
surya-lab waits on the author: hand over the top of the phoneExpect: monitor-sensor --proximity prints near: 1 when a hand covers the top bezel and near: 0 when removed; ask the author for go before running it
A shell-free base for hardware tests
surya-labProposed by the author after a day of faults that a shell's policy turned into loops: test the base - sound, modem, suspend, storage - on a console-only system, with no desktop or shell deciding when…
surya's fastboot serial in its manifest, read from fastboot
surya-labdevlab flash now refuses surya until surya-lab device.toml says [fastboot] serial and writes = true (lab-tools PR 79, decision 2026-11-17-fastboot-by-serial-writes-by-manifest). Next time surya sits i…
Checked by hand
surya-labButtons verified by a person; vibration still to check (the first half-manual test). Settled 2026-11-11: checked by hand once; next: checked by the conveyor as scenes (agent access).
Try every mobile shell with working sound
surya-labSwitched in place with surya-lab ui/switch.sh (postmarketOS UI packages, tinydm for all; no reflash, the sound fixes stay). Phosh: runs, stereo verified by ear 2026-11-09. Next: Plasma Mobile, GNOME M…
In progress · 2
surya's own cluster sleep parameters in its device tree
surya-lab proven by soc-sleeps waits on a deeper decision: WHAT holds CX, AOSS and DDR with an apps…2026-11-17 keeper-7: cycle 15 bt-on on the cp.dtb (0x41002244, 0x4100c244) 8 times: a real 15 s s2idle (RTC alarm wake), cluster S2 entered, cxsd/aosd/ddr 0 (research 2026-11-17-cluster-params-clean-y…
First fastboot boot of the walleye kernel: the phone leaves fastboot and its gadget answers
google-walleye-lab proven by lsusb on the host shows the gadget within 60 s of fastboot boot and ssh/telnet to 172.16.42.1 answers (test: walleye-gadget-up) waits on walleye-boot-refused-why (research), walleye-control-on-slot…Six images and the official LineageOS control all refused with Load Error: the cause is the phone's state or what fastboot boot needs, not our image (walleye-control-e-f-tries). A dtbo/vbmeta write st…
Done · 75
Deep sleep measured once: the SoC's own counters across one suspend
docs proven by soc-sleepsDone 2026-11-17 by surya-keeper: one cycle by hand, soc-sleeps = fail (cxsd 0, aosd 0, adsp never asleep, cluster S2 never entered). Research 2026-11-17-surya-first-s2idle-cycle. The phone woke after…
Read the running Android's full cmdline (skip_initramfs? root=? dm=?) and the ramoops service files, read-only
google-walleye-lab proven by test walleye-boot-cmdline-known: the full /proc/cmdline and chosen/bootargs and /vendor/etc/init/*ramoops* are recorded as a research row; says whether skip_initramfs is presentAnswered by the vendor-gadget4 try (lab PR 25): our idle init RAN (bootreason=reboot at ~120 s, not kernel_panic), so skip_initramfs is not in effect and the ramdisk is used. The cmdline itself was al…
The control boot.img again with slot a active (the state of the very first tries)
google-walleye-lab proven by devlab's before/after slot report and the phone's full fastboot text for the control on slot a; then the phone back to current b, a recoverableproven by devlab's before/after slot report and fastboot text: control refused (Load Error) on slot a; phone back on b
The first shell of our own mainline kernel: read y2 over /dev/ttyACM0 - the whole dmesg first, then the facts
google-walleye-lab proven by A script tests/host/mainline-shell-read.sh (new, in the lab, selftested with a fake tty) opens /dev/ttyACM0 as the lab user the moment it appears, sends commands one at a time with a read timeout, and saves under the lab material path (never into git without redaction): (1) dmesg in full - the first mainline kernel log of this phone; (2) uname -a, /proc/cmdline, /proc/cpuinfo, /proc/iomem, /proc/interrupts, /proc/version; (3) the device list: ls /sys/bus/platform/devices, deferred probes (/sys/kernel/debug/devices_deferred if debugfs is mounted), /sys/class/udc, /sys/class/power_supply, /sys/class/drm, /sys/class/input, /sys/class/regulator; (4) touch /tmp/hold to keep the phone up while reading, then reboot -f. Nothing is written to the phone beyond /tmp. The research row names what the dmesg shows works, what defers or fails (display, touch, UFS, charger, regulators): the real map of the next parts to bring up.proven by reader pass: 13 answers, dmesg 336 lines; fixed reader's end marker matching the phone's echo
Restore the first state: boot Android on slot a to completion, adb reboot bootloader, control once
google-walleye-lab proven by devlab's before/after slot report (a successful yes before the try) and the fastboot text of the control try, accepted (phone leaves fastboot) or refused; the phone back on a bootable slotproven by devlab fastboot state: control accepted from restored first state (walleye-first-state-control-accepted); after the author's power-cycle Android booted on slot a, adb reboot bootloader, fast…
Our images e, then b, by fastboot boot from the first state (Android booted on slot a, then adb reboot bootloader)
google-walleye-lab proven by devlab's before/after slot report and the phone's full fastboot text for each; lsusb polling (by the manifest serial, not VID:PID: surya's gadget 18d1:d001 is on the same host) shows whether a Linux gadget of ours appears (lsusb on the host within 60 s, 172.16.42.1 answering: test walleye-gadget-up)proven by devlab fastboot boot now: e and b accepted from the first state, neither started, slot flags unchanged; see walleye-own-images-e-b-first-state
Try T1: fastboot boot boot-t1.img, wait 90 s, read console-ramoops for the marker
google-walleye-lab proven by tests/host/pstore-t1-read.shran 03:52 slot b: boot-t1.img back as Android after 159 s; battery 4384 mV 100% before; /sys/fs/pstore empty, no ramoops dir; marker absent = cause B
Image T3: init opens /dev/watchdog (kpss-wdt) with a short timeout and never pets it; read console-ramoops after the bite
google-walleye-lab proven by tests/host/pstore-t3-read.sh: pstore holds the T3 marker, last tick under 15, no no-bite line (expected present)Tried once (lab PR 122): back at 42 s, no marker: inconclusive without a witness; the pstore chase is paused by decision 2026-11-18-walleye-vendor-kernel-as-instrument.
Try m1 again now the host runs 7.3.4 (usb_storage loads): read the first text the phone writes
google-walleye-lab proven by massstorage-read.sh (tests/host) prints the init's window text from the phone: uname, cmdline, mounts, dmesg tail of the vendor kernel with our init running, the heartbeat counter growing; kept as material in the lab and recorded as research with what it showsproven by tests/host/massstorage-read.sh pass: gadget 3-2 /dev/sda WALLEYE-LOG m1 beat=4 up=21.34s; research 2026-11-17-walleye-m1-window-read. lpoco-host acceptance: PASS. Next: walleye-ffs-rust-try…
Phone: one image, stock kernel + our dtb with overlay symbols (s3 redone); read the result
google-walleye-lab proven by TESTproven by fastboot boot: left fastboot at 12 s, Android on a at 36 s, flags unchanged; see research walleye-s4-overlay-symbols-try
Phone: boot pk3 once, then pk4, pk5, pk6 twice each from the first state; record the seven return times and read pstore
google-walleye-lab proven by TESTproven by the seven returns in walleye-pk-bisect-returns: our dtb is the fault
Phone: boot x4, x1, x2, x6, x5, x3, x7, xa twice each from the first state; record the sixteen return times
google-walleye-lab proven by TESTproven by 16 boots: x1 dead twice (79,78 s), xa dead (78,76), x2-x7 alive. Next: add gpio-reserved-ranges <0 4>,<81 4> to our dtb and try (alive expected)
Try vendor-gadget5a, 5b, 5c from the first state, in order; stop at the first panic
google-walleye-lab proven by TESTproven by tries: 5a ok (reboot, 156 s), 5b kernel_panic (75 s): culprit is the ncm function/config step; 5c not tried per stop rule. Record 2026-11-17-walleye-vendor-gadget5-bisect
Phone: boot ml1, then ml2, each once from the first state; lsusb tells first light
google-walleye-lab proven by tests/host/mainline-light-up.shTried 2026-11-17: ml1, ml2 and (item walleye-try-ml3-ramoops) ml3 all fail: no USB light, Android on a at ~70 s. pstore read done, empty. Next: UART, the walleye coordinator's call.
Try m1 from the first state, then read the log window on the host for 90 s
google-walleye-lab proven by TEST waits on host: usb_storage for the running kernel (reboot into 7.3.4)m1 tried and its window read as the lab user (lab PR 70: lpoco-host acceptance passed); ml/pk variants superseded.
Phone: boot ml3 once from the first state, then read our kernel's console from the stock Android's pstore
google-walleye-lab proven by tests/host/ml3-ramoops-read.sh (to write: pstore console of our boot read back)Tried 2026-11-17: ml3 no light, Android on a at 72 s, pstore empty (research walleye-ml3-pstore-empty). Proof test tests/host/ml3-ramoops-read.sh fails as the facts stand. The remaining read is UART (…
Phone: boot image ml4 twice from the first state; read the reset time as a score
google-walleye-lab proven by TESTproven by two tries (75 s, 76 s, slot b, nothing flashed, pstore empty): bin table reads score 7 but is not told apart from the safety watchdog (ml1-ml3 back at 69-72 s); see research 2026-11-17-walle…
Phone: boot ml5a twice, then ml5b twice from the first state; record the four return times
google-walleye-lab proven by TESTproven by the phone: ml5a 75 s and 75 s, ml5b 75 s and 78 s (fastboot boot to adb, from slot b, nothing flashed); ml5a ~70 s+ = the kernel never reached init; ml5b equals ml5a within 3 s, so no init r…
Try vendor-gadget5b1, then 5b2, 5b3, 5b4 by fastboot boot from the first state; stop at the first that panics
google-walleye-lab proven by TESTproven by b1 returns, b2 panics at 75 s (research 2026-11-17-walleye-ncm-split-b2-panics); next: the noattr try (n1, n2)
Phone: boot pk3 twice, then ml6a twice from the first state; record the four return times
google-walleye-lab proven by TESTproven by four returns: pk3 63/48 s, ml6a 75/75 s; ml6a no init, pk3 undecided; next: coordinator picks the log channel (ramoops read / UART)
Phone: boot pk1 twice, then pk2 twice from the first state; record the four return times
google-walleye-lab proven by TESTproven by four tries: pk1 75 s, 75 s; pk2 75 s, 75 s - no init ran
Phone: boot g1, g2, g3 (images-g) twice each from the first state, stop at the first that dies; lsusb polled by port every second for 90 s; pstore read after each
google-walleye-lab proven by TESTproven by 6 tries: no gadget enumerates, g2 returns at 138 s; research walleye-pk5-stages-tried
Phone: boot pk5l twice from the first state; read the ACM console and the window, record the first mainline dmesg
google-walleye-lab proven by TESTtried twice: no ACM, Android back at 57/42 s; recorded walleye-pk5l-tried; next walleye-try-dtb-bisect
Phone: boot pk5l2 twice from the first state; after each read /sys/fs/pstore/* and /data/vendor_ce/0/ramoops/*, record the first mainline panic or console text
google-walleye-lab proven by TESTtried twice: no mainline panic text found (research walleye-pk5l2-tried); next: prove the mainline kernel reaches ramoops at all, or return to the dtb diff
Phone: boot wpa twice from the first state, then (if dead) wp1..wp5 twice each; record the return times (<=66 s alive, >=69 s dead)
google-walleye-lab proven by TESTproven by wpa x2: 60 s, 60 s (alive); cause is not a property; next: phandle order / dtb size
Phone: boot wa twice from the first state, then w1..w5 and wr twice each; record the return times (~42 s init ran, ~75 s dead)
google-walleye-lab proven by TESTproven by 12 tries, all alive (research walleye-w1-w5-wr-tried): cause is a property; next a property-level bisect
Try vendor-gadget3.img (vendor-gadget2 plus a 240 s self-reboot) by fastboot boot from the first state
google-walleye-lab proven by walleye-gadget-up (tests/host/gadget-up.sh, GADGET_WAIT=90): a USB device with our strings enumerates and 172.16.43.1 answers ping and telnet; and without hands the phone is back in fastboot or Android within ~300 s of the boot (or kept up with touch /tmp/hold over telnet); else record the bootreasonThird try done, watcher alive: kernel_panic before any gadget strings (research walleye-gadget3-third-try). Next: a kmsg-only init build (builder), then try it.
Controlled repeat: vf2 twice as before, then vf4 twice WITHOUT the poller, to tell the image from the way it was watched
google-walleye-lab proven by four tries from the first state (battery first, Android on a good slot, adb reboot bootloader), each recorded with the time the gadget appeared (plain lsusb by port, no lsusb -v, no reads of the LUN until 70 s after the jump), the time Android is back, and whether the init's beat/step text appears in a single read at ~70 s of /dev/sdX (massstorage-read.sh as in vf2's tries): order vf2, vf2, vf4, vf4; the finding: does vf2 repeat its ~43 s gadget? does vf4 (identical init to vf2 up to the bind) behave like vf2 when watched the same way? if vf4 is alive unwatched and dead with the poller, the poller (lsusb -v or the LUN reads during enumeration) is what breaks the phoneproven by 4 tries: vf2 repeats (gadget ~50 s, empty header), vf4 dead twice unwatched; poller cleared; next: diff vf4 vs vf2 after the bind, bisect the dump
Phone: boot vf1 twice from the first state; the keeper reads the window with tests/host/vendor-facts-read.sh (battery first, phone left in Android afterwards); first run may be partial: say what was missing
google-walleye-lab proven by TEST waits on coordinator: how to make the window show life firstvf1 tried twice (lab PR 125): enumerates, LUN readable, no header: superseded by vf2.
Phone: boot vf2 twice from the first state; read the window with tests/host/vendor-facts-read.sh (step lines print first; battery first; phone left in Android afterwards); say whether the marker, the beat and which step the init reached
google-walleye-lab proven by TESTproven by try 2: marker, beat and init steps seen; blob unread - see walleye-vf2-tried-twice
Phone: start tests/host/vendor-facts-poll.sh FIRST in its own background job (never killed by the keeper's cleanup), then boot vf3 twice from the first state; battery first; phone left in Android afterwards; say how many blocks the poller fetched, whether DONE came, and the beat log
google-walleye-lab proven by TESTtried twice as asked: no gadget, no window, no blocks (poller fail x2); back as Android 78 s each; see walleye-vf3-tried-twice. Next: coordinator decides - vf2's order alive, vf3's reorder dead; diff…
Phone: start tests/host/vendor-facts-poll.sh FIRST in its own background job with VF_MARK=WALLEYE-VF2 VF_HEAD=16 VF_BLOCKS=1040 VF_OUT=$HOME/Projects/walleye-build/material/vf/2026-11-18-vf4 (never killed by the keeper's cleanup), then boot boot-vf4.img twice from the first state; battery first; phone left in Android afterwards; say how many blocks the poller fetched, whether DONE came, the beat log, steps.txt's last lines (where it stopped), and when the phone left USB
google-walleye-lab proven by TESTproven by two tries: 0 blocks fetched, no gadget, back as Android at 78 s both; turning point for the coordinator: vf4 behaves like vf3 (dead), not vf2 - what differs between vf2 and vf4 before the bi…
Try vfa twice, then vfb, vfc, vfd once each (twice if one dies): which single hardware source reads, which kills
google-walleye-lab proven by vfa twice, then vfb, vfc, vfd once each unless one dies (then twice), each recorded with the time the gadget appeared, the time Android is back, and the reader's one line (pass with the parts, or fail saying killed or hung); the finding: which source reads and which kills; /sys/firmware/fdt kept as fdt.dtb and fdt.dts in the lab material path if vfa passesproven by: vfa twice pass (fdt.dtb/dts kept in material path), vfb alive but clk_summary unreadable rc=1, vfc pass, vfd killed twice (research walleye-vfx-tried). Next: give mainline USB its nodes fro…
Phone: boot y1 twice, then y2 twice from the first state; battery first; read return times and the host's lsusb; leave Android on a good slot
google-walleye-lab proven by TESTproven by y1 alive x2 (36 s) and y2 gadget 1d6b:0104 at 18 s x2, research walleye-y-tried
Read the suspend entry: RSC sleep flush, last-CPU idle state, IRQ delta (no kernel change)
surya-lab proven by soc-sleepsDecision 2026-11-17-floor-read-the-entry. One cycle: way-back.sh cycle 15 bt-on, watchdog armed (BT-blocked cycles reset). Before and after: /proc/interrupts, every cpuN/cpuidle/stateN usage+time, pm_…
Phone: boot image n3 once; host sees ttyACM and a shell answers
google-walleye-lab proven by tests/host/ffs-acm-up.sh waits on host: cdc_acm for the running kernel (reboot the lab host in…n3/n3r tried (lab PR 76): cdc_acm refuses a FunctionFS interface without functional descriptors: parked (decision 2026-11-17-walleye-ffs-console-parked).
Phone: boot image n3r (the Rust FunctionFS ACM helper) once; host sees ttyACM and a shell answers
google-walleye-lab proven by tests/host/ffs-acm-up.shTried once (n3r on slot b): the gadget enumerates but the host's cdc_acm refuses it (Zero length descriptor references, -22); f_fs cannot carry the CDC functional descriptors it needs. Parked: decisio…
Measure when the panic happens: T_android from a plain adb reboot against the gap of a panic try
google-walleye-lab proven by test walleye-panic-time: the 1 s watcher log gives T_android (reboot) and the try's gap; panic time = gap - T_android, written as a research rowNot needed now: the panic belongs to the gadget bring-up (gadget4 idle init does not panic); the bisect of the bring-up (walleye-gadget-bisect) is the next measure.
Try n3 (FunctionFS ACM) again now the host runs 7.3.4 (cdc_acm loads): a console on /dev/ttyACM0
google-walleye-lab proven by tests/host/ffs-acm-up.sh passes: /dev/ttyACM0 appears on the host, a shell answers on it (uname -a, cat /proc/cmdline read-only), the phone returns by itself (the init's reboot) waits on the lpoco lab-prepare tool (host access to /dev/ttyACM*); th…Superseded by walleye-ffs-rust-try: the console try uses the Rust helper image n3r (the C n3 is a probe).
Phone: boot pk4 once more, then d1..d6 twice each from the first state; record the thirteen return times and read pstore
google-walleye-lab proven by TEST13 tries, all 75 s (no init); no group of d1..d6 is the cause; recorded walleye-dtb-bisect-tried
Try ncm-noattr n1 then n2 from the first state, stop at the first panic
google-walleye-lab proven by TESTproven by n1/n2 tries: n1 returns, n2 binds without a panic and enumerates with our strings; host cdc_ncm fails on the MAC string (walleye-ncm-noattr-n1-n2). Next: a function the host binds without a…
Try vendor-gadget2.img (the control with an xz gadget ramdisk) by fastboot boot from the first state
google-walleye-lab proven by walleye-gadget-up (tests/host/gadget-up.sh, GADGET_WAIT=90): a USB device with our strings enumerates and 172.16.43.1 answers ping and telnet; else record the bootreasonSuperseded by walleye-try-vendor-gadget3: the same image without the self-reboot timer (decision walleye-try-returns-without-hands). Never tried.
Fallback: hexagonrpcd serves a writable sensor registry
surya-lab proven by motion-and-lightproven by a 150 s run with 0 ADSP crashes and monitor-sensor showing accelerometer, light, proximity and compass; research 2026-11-17-sns-reg-version-served. Lasting install not yet (transient run)
Quiet the Bluetooth UART wake irq 157 so Bluetooth-on standby is representative
surya-lab proven by soc-sleepsproven by 4 bt-on 15 s cycles: no 'nobody cared', hci0 up, soc-sleeps read (cxsd/aosd 0). Cost: ADSP sensor_process crash after every suspend (4 of 4) - needs sensors stopped before suspend; reboot re…
Try vendor-gadget4.img (idle init, no gadget) by fastboot boot from the first state
google-walleye-lab proven by the bootreason and the time the phone is back on Android a after fastboot boot: panic at ~75 s = the panic is independent of our gadget code; a return at ~120 s with bootreason not kernel_panic = our init ran and the gadget bring-up of gadget2/3 is what panics; the init's /dev/kmsg marker is not readable from Android (record that)proven by the try: back on Android a at 156 s, bootreason reboot (not kernel_panic): our idle init ran; the gadget bring-up of gadget2/3 is what panics. Next: bisect the gadget bring-up - the coordina…
Sensors probe: the registry kept current, sensorspd alone unmasked
surya-lab proven by proximity-readsProbe done 2026-11-17 (keeper-8, research 2026-11-17-sensorspd-probe-still-writes): with the configs at mtime 1230768000 the DSP still writes temp.json and sns_reg_version through hexagonrpcd (refused…
Boot with the DSPs never started, then cycle 15 bt-on
docs proven by soc-sleepsDone 2026-11-17 (keeper-9): DSPs never started (remoteproc nodes disabled in a one-shot dtb), cycle 15 bt-on: cxsd/aosd/ddr 0 -> 0, soc-sleeps fails, processors never asleep: none. No DSP vote is the…
Drop clk_ignore_unused / pd_ignore_unused if the cmdline has them
docs proven by soc-sleeps waits on floor-read-holdersClosed 2026-11-17 (keeper-9): the cmdline has no clk_ignore_unused or pd_ignore_unused (floor-read-holders), nothing to drop.
Read what is held before and at a cycle: cmdline, clocks, regulators, icc, genpd
docs proven by soc-sleepsDone 2026-11-17 (keeper-9): read at idle and before way-back.sh cycle 15 bt-on, research/deep-sleep/2026-11-17-floor-holders/README.md; what is held inside late suspend is not known yet (floor-suspend…
Capture through the sound server: a UCM profile for both mics, the headset mic when plugged
docsFirst step of decision 2…
Microphone: check, and make it work
docs proven by mic-hears-speakerTaken up 2026-11-17 by the bring-up session, as the weakest link the data shows: audio-mic and audio-earpiece are both broken and two milestones rest on them (surya-sound, and the calls of…
If refused: cold restart, then the same try on the same slot, with host checks
google-walleye-lab proven by devlab's before/after slot report and the fastboot text of one control try after the cold restart, with the fastboot version and port in the log; the phone back on its start slotNot needed: the Load Error was the slot state after repeated refusals (set-active metadata fixes it); the host restart for the host's own modules was the lab reboot into 7.3.4, done by the author.
Control try: fastboot boot of a public walleye stock-format image (LineageOS recovery or TWRP) with devlab's before/after slot report
google-walleye-lab proven by walleye-fastboot-boot-control: devlab report shows the phone left fastboot (18d1:4ee0 gone for 90 s polls) or Load Error, recorded either way as a research rowproven by research walleye-control-e-f-tries: control, e and f all Load Error, flags unchanged
Try e then f (one at a time) with fastboot boot, after the control, with before/after slot report
google-walleye-lab proven by walleye-fastboot-boot-variants: each image's outcome recorded as research; success is a USB id other than 18d1:4ee0 appearing (our gadget) for e or fproven by research walleye-control-e-f-tries: control, e and f all Load Error, flags unchanged
Try bisect image s0n (stock parts without AVB footer (control of the footer)) by fastboot boot from the first state
google-walleye-lab proven by walleye-gadget-up for s1; for s2, s3, s0n: the phone leaves fastboot (starts) or stays at 'Booting OKAY', recordedproven by s0n: left fastboot after 12 s, then off USB, same as s0; no writes
Try bisect image s1 (ramdisk = ours) by fastboot boot from the first state
google-walleye-lab proven by walleye-gadget-up for s1; for s2, s3, s0n: the phone leaves fastboot (starts) or stays at 'Booting OKAY', recordedno start, fell back to a; see walleye-try-s1-s2-s3
Try bisect image s2 (kernel = ours (lz4 frame)) by fastboot boot from the first state
google-walleye-lab proven by walleye-gadget-up for s1; for s2, s3, s0n: the phone leaves fastboot (starts) or stays at 'Booting OKAY', recordedno start, fell back to a
Try bisect image s3 (dtb = ours) by fastboot boot from the first state
google-walleye-lab proven by walleye-gadget-up for s1; for s2, s3, s0n: the phone leaves fastboot (starts) or stays at 'Booting OKAY', recordedaccepted, not started, stays in fastboot
Try image g (e at 172.16.43.1) by fastboot boot
google-walleye-lab proven by walleye-gadget-up: after devlab fastboot boot now IMAGE the phone leaves fastboot, lsusb shows our gadget (1d6b:0104, walleye-first-boot) within 60 s and 172.16.43.1 answers ping and telnet; devlab's before/after slot report and the fastboot text keptNot needed: the vendor kernel ran with our ramdisk (research walleye-vendor-kernel-facts-s1-panic); mainline images g/h wait until the vendor-kernel gadget (walleye-try-vendor-gadget2) gives a shell a…
Try image h (b at 172.16.43.1) by fastboot boot
google-walleye-lab proven by walleye-gadget-up: after devlab fastboot boot now IMAGE the phone leaves fastboot, lsusb shows our gadget (1d6b:0104, walleye-first-boot) within 60 s and 172.16.43.1 answers ping and telnet; devlab's before/after slot report and the fastboot text keptNot needed: the vendor kernel ran with our ramdisk (research walleye-vendor-kernel-facts-s1-panic); mainline images g/h wait until the vendor-kernel gadget (walleye-try-vendor-gadget2) gives a shell a…
fastboot boot the repacked control from the first state; does the gadget answer?
google-walleye-lab proven by walleye-gadget-up passes (phone enumerates by serial, 172.16.43.1 answers) and the slot report shows what changedSuperseded by the bisect of the bring-up (gadget4 idle init ran, gadget5a ok, 5b panics at the ncm step): see research 2026-11-17-walleye-vendor-gadget5-bisect and walleye-try-ncm-split.
From the running vendor kernel, read the facts our dts guesses (read-only)
google-walleye-lab proven by a research row walleye-vendor-kernel-facts with cmdline, ramoops region and ids, checked against the dts (test: walleye-gadget-up passes during the read)read from the running vendor kernel; see research walleye-vendor-kernel-facts-s1-panic
devlab fastboot boot reads the slot variables before and after a try and says what changed
lab-tools proven by a test that fails when devlab reports a slot change as only refusedDone 2026-11-17 by lab-tools PR 80 (d510232), recorded there as fastboot-slots-told: devlab fastboot boot now reads current-slot and slot-unbootable/successful/retry-count of a and b before and after,…
Write the qcom_aoss prevent_* knobs to off, then cycle
surya-lab proven by soc-sleepsDone 2026-11-17 (keeper-9): knobs written 0 before cycle 15 bt-on: cx/ddr writes time out, 'ucore did not ack channel': the QMP link to the AOP is dead, so the knobs settle nothing; counters 0 -> 0. r…
Cycle with the USB controller unbound
surya-lab proven by soc-sleepsDone 2026-11-17 (keeper-9): UDC a6f8800.usb unbound, cycle 15 bt-on: cxsd/aosd/ddr 0 -> 0. USB is not the holder. The rebind did not bring the lab link back (needed a hard reboot). research/deep-sleep…
Cycle with WLAN unloaded
surya-lab proven by soc-sleepsDone 2026-11-17 (keeper-9): ath10k_snoc/core unloaded, cycle 15 bt-on: cxsd/aosd/ddr 0 -> 0. WLAN is not the holder. research/deep-sleep/2026-11-17-floor-wlan-off/README.md
The modem stays in shutting-down and will not go online
surya-labThe modem stays in shutting-down from boot with the SIM in. tqftpserv 1.1.1 is installed; its read-write base is /tmp/tqftpserv an…
Boots that come up without the sound card
surya-lab proven by sound-cardOn 2026-11-11 one stock boot had no phone sound card: the audio processor ran with no crash, but its service channel (APR) never…
Port the pin fix to the microphone kernel branch
surya-labThe tested tree came from the phone's v7.1-rc3 source plus upstream's WIP; linux-phone-oco/linux's microphone branch has the au…
Sensors kept: hexagonrpcd with a served version marker made lasting, three boots without an ADSP crash
surya-lab proven by motion-and-lightproven by three boots, 0 ADSP crashes, motion-and-light and proximity-reads pass (research 2026-11-17-sensors-lasting-install-three-boots); suspend with the helper left to sensors-across-suspend (1 cr…
Checks that need the SIM skip, not fail, while it is out
surya-labDone 2026-11-17 (lab-tools #73 no_sim helper, surya-lab #123): with the SIM out, modem-registered, mobile-data, call-echo and sms-loopback say 'skip: no SIM card' (before the once-a-day stamp, so a sk…
A way back from a suspend that may not return: the watchdog kept armed through sleep
surya-labDone 2026-11-17 (surya-lab sleep/way-back.sh, build-wdt.sh, patches/qcom-wdt-keep-armed-in-suspend.patch; patched module in updates/ on the phone, acts as stock until 'enable'): idle fuse, probe throu…
Why surya rebooted by itself during standby run r2
surya-lab proven by soc-sleepsproven by research 2026-11-17-r2-reboot-was-the-fuse (pstore console, journal, r2 logs read); r3 waits on decision 2026-11-17-r3-waits-on-the-bluetooth-choice, which the surya coordinator takes
surya unreachable after a real systemctl suspend: the author's power cycle, then the cause
surya-labPhone work is PARKED until it answers. When it does: read pstore/ramoops and journalctl -b -1 first (why it did not return: the 30 s fuse was defused for the try; sxmo autosleep still running?). Rules…
Telephony in the test suite
surya-labdevlab checks: modem registered; mobile data (download a small file over the mobile connection); a call to the number in ~/.…