TEST RECORD · OCT 13, 2026, 4:14 AM EASTERN

Progress, real-device testing, and what is still unknown.

This is the full, dated picture behind our status pages. It separates checked code from a person using a real device. It does not mean every path works, and it does not turn an untested path into a pass.

How to read the percentages. “Code checklist” is the share of the listed feature rows where both Built and Automated tests are checked. “Human-device” is the share where the separate Real device check is recorded. These are checklist measures, not a claim of bug-free software. Areas overlap when a feature belongs to both a platform and a named slice. If we have no comparable checklist rows, the page says not measured yet.

CHECKLIST PROGRESS

Progress by area.

Changes compare the public October 11, 7:25 AM Eastern snapshot with the October 12 dated test record. The Android code estimate is separately marked because the overnight review counted code gaps, not device tests.

Area	Code checklist	Human-device	Movement	What the record establishes — and does not
Windows desktop	100%	44%	0 / +13 pointsTwo of 16 desktop rows gained a recorded device check on Oct 12.	About 35 screens were opened on a Windows 0.1.88 test build; a phone backup and two-home library share were also tried. Sign-out, signed-in browser playback, subtitles and keyboard-only use are still not tested in that run.
Android phone	About 97%The published checklist was 94%; an overnight code-gap review estimated about 90% before its merges and about 97% after.	76%	About +3 / +7 code points+3 from the Oct 11 published 94% checkpoint; +7 from the Oct 12 morning estimate. Device coverage was not recomputed by the code merges.	S24 Ultra and S9+ walks, playback, network changes, Campsite, browser and two-home checks were recorded. TalkBack, a fresh install, every route and many exact newest-build retests remain open.
Beebo Auto	100%	100%One checklist row, not every car or route.	No score change	One real-car check covered sign-in, lists, sound and steering-wheel controls. Music, car-screen artwork, away-from-home use, passenger games, Car Party and other cars are not tested.
Campsite games	100%	2%1 of 41 games: Sea Battle.	0 / +2 pointsOne documented two-person game was added on Oct 13; the other games remain scripted-guest coverage only.	An S9+ host and S24 browser guest exercised join, library, music and 41 game rooms on the same-Wi-Fi route on Oct 12. On Oct 13, Nick and a friend completed Sea Battle via DIRECT-BeeboTV Wi-Fi on a Samsung S20—the first real-person result on that route. A phone hotspot and a guest on mobile data, other hand-played games, karaoke, recordings and guest uploads are not tested.
Car Party	100%	100%One checklist row.	No score change	Nick tested it in a real parked car: a guest could follow and send reactions. A passenger could not watch the movie, and a guest had to type a name. Those two fixes are not in the main snapshot used here.
Trip Journal	100%	0%	No measured change	No recorded real trip, recap or video-export device run.
Live TV	100%	0%	No measured change	A real tuner and a real playlist still need a device run.
Away from home / Relay	100%	100%Two related checklist rows.	No score changeOct 12 added a two-home replay.	A phone on 5G played directly and through Beebo Relay; two direct viewers connected at once. Two people on Relay at once remains untested.
Chromecast	100%	100%	No score change	An earlier home-TV cast is recorded. A browser cast to a friend's TV, other receivers and away-from-home casting are not tested.
Jellyfin API	100%	0%	No measured change	More Jellyfin apps still need real-client checks.
Web player / browser	100%	100%Two related checklist rows.	No score change	A signed-in desktop browser run covered 17 pages and playback. Subtitles, audio tracks, Cast, AirPlay, PiP, fullscreen, keyboard-only use and other browsers are still untested.
Photos and backup	100%	100%	0 / +50 pointsThe phone-to-PC backup row gained its real-device check on Oct 12.	Three phone files arrived on a home PC. The removal step and broader photo/video sharing paths were not tested.
Music / Podcasts / Audiobooks	100%	100%Two recorded phone rows.	No score change	Radio and podcast browsing was observed; the October 12 run did not check their playback. Audiobook chapter/restart and screen-off runs remain needed.
Recipes / Family	Not measured yet	Not measured yet	Not measured	Servings and per-person shopping-list work was merged into the code, but this public checklist has no comparable Recipes/Family row and no recorded device acceptance run.
Read It To Me	Not measured yet	Not measured yet	Not measured	Home-computer voice selection and related fixes were merged into the code. A real-device acceptance run is not recorded.
Parental controls	100%	0%	No measured change	Restricted and normal profile behaviour still needs a careful real-PC run.
Accessibility	100%	0%	No score change	Some large-text controls were tried and a clipping issue was found, but the formal accessibility rows do not yet have their recorded device checks. TalkBack, Windows screen reader and high contrast remain untested.
Languages	100%	0%	No measured change	A language picker was merged. Native-speaker review, long text and right-to-left layouts have not been recorded on devices.
Server / accounts	100%	50%	No score change	The own-server row has a recorded device check. Reset and email verification remain switched off and lack a real-email test.
TV platforms: Roku, Samsung/LG, Xbox, Apple, Fire TV	Not measured yet	Not measured yet	Not measured	There is no like-for-like checklist across these platforms. The Android TV / Fire TV row has no recorded real-device check; the other named platforms have no recorded real-hardware run here.
Linux / macOS / Docker	100%	33%Three existing rows.	No measured change	The record includes server and build checks, not a broad hardware run. A real Linux desktop, NAS or Raspberry Pi, and Intel and Apple-Silicon Macs remain untested.

REAL PEOPLE, REAL DEVICES

What was hand tested.

Oct 12 · Two homes and a phone on 5G

Passed: direct and Relay playback, network switching, two direct viewers, library sharing from invite through stopping access, phone backup, browse, favourites, playlists, radio, podcasts, Campsite host/guest setup, landscape and restart.

Not tested: two people on Relay, a friend's Chromecast, Beebo Auto in a car, a real TV pairing code, TalkBack and the newest fixes on real devices.

Oct 12 · Windows desktop walk

Passed: about 35 screens were opened and looked right on the unpublished 0.1.88 test build, including media areas, admin screens and all eight Settings pages.

Found: settings search missed the intro/skip section, and the window did not stay maximized when brought forward. Not tested: sign-out, signed-in browser player, subtitles, track switching, PiP, keyboard-only use, high contrast and 150% scaling.

Oct 12 · Signed-in browser

Passed: sign-in and reload, 17 pages, clip and film playback, seeking, pause/resume and switching quality.

Found: old browser pages chose the wrong automatic quality, lacked a reconnect action after idle, had a nearly blank Suggestions page and showed empty-image icons. Not tested: subtitles, audio tracks, Cast, AirPlay, PiP, fullscreen, touch layout, keyboard-only use and Firefox, Edge or Safari.

Oct 12 · Campsite

Passed: S9+ host and S24 browser guest join, guest library, music controls, 41 game rooms entered and started or correctly refused, a complete scripted-guest Drop Four game and guest data pages, on the same-Wi-Fi route.

Found: abandoned rooms did not clear, the host sheet button was under the navigation bar, and a stopped host needs a watched unattended run. Not tested: a phone hotspot, a guest on mobile data, a real two-phone board-game touch run, synced audio, karaoke, recordings, guest uploads and a screen-off host.

Oct 13 · Campsite Sea Battle, two people

Passed: Nick hosted while a friend on a Samsung S20 created Sea Battle; Nick joined, they played a full game to the end, the friend won, and it worked well. They used DIRECT-BeeboTV Wi-Fi (BeeboDirect), the Wi-Fi Beebo creates for Campsite without internet: the first real-person result on that route.

Scope: this is human testing for Sea Battle only. The other 40 Campsite games still have scripted-guest coverage only. Nick's phone, browsers, game length, sound and graphics observations were not recorded. A phone hotspot and a guest on mobile data are still not tested.

Earlier two-phone checks

Passed: S24 and S9+ Watch Together joins and sync, and Campsite host/guest checks on the documented routes. The October 11–12 phone walks reported no crashes for the paths they opened.

Not tested: Watch Together rejoin after app closure, every connection route, every game and every device size.

Nick's real-car Car Party check

Passed: a guest could follow along and send reactions in a real parked car.

Failed or missing: a passenger could not watch the playing movie, and a guest could not continue with a blank name. Both fixes are still in development, not in the source snapshot used for this page. This was not a driving-safety validation.

CODE CHANGELOG · OCTOBER 12–13

What changed — and what did not make the cut.

These entries describe code merged into the source snapshot used for this record. They are not a promise that a change is in a published download or has been re-tested on a real device.

Guest video requests with host approval and phone video upload were merged.
Family Recipes gained servings and per-person shopping-list work.
Read It To Me gained home-computer voice selection and related cleanup.
Language picker work and landscape / Back-navigation fixes were merged.
Security-header policy code was added and tested; the server deployment is still pending, so the public hosts are not claimed to have those headers yet.

Still not in the source snapshot used here: the abandoned Campsite-game-room cleanup, the Car Party passenger-watch and automatic-guest-name changes, and Campsite guest downloads. They are not listed as shipped or human-tested.

AUTOMATED TEST COUNTS

Latest recorded test totals.

These counts describe automated checks, not real-device coverage and not a combined release result: Worker 1,675; home server 1,103 own tests plus 1,669 worker-suite tests; desktop 1,303 test files; Android web flavour about 7,189 tests. Different runs can use different source snapshots, so the counts are not added together.

Older history (2 entries)

Oct 11 · Published Android build walk

The published tester22 build was opened on the S9+ and S24. Tabs, search, playback controls, picture-in-picture, quality picker, screen-off audio when enabled, progress after a force-close and no crash log were recorded for the named paths. Rotation, fresh-install behaviour, car, TV and mobile-data routes were not covered in that run.

Oct 6 · First Beebo Auto car check

One car and one drive covered the listed sign-in, list, sound and steering-wheel paths. It did not cover music, car-screen titles or artwork, away-from-home use, passenger games, Car Party or another car.

PLAINLY UNTESTED

What remains untested.

Two people watching through Beebo Relay at once; broad browser-to-TV casting; and a fresh-install Android run.
TalkBack, Windows screen-reader and high-contrast journeys, native-speaker review of translations, and long or right-to-left layouts.
Real tuner and playlist use for Live TV; broad Jellyfin-client testing; a real trip and export; and a careful parental-controls device run.
Real Roku, Samsung/LG TV, Xbox, Apple hardware, a real Linux desktop or NAS/Raspberry Pi, and Intel or Apple-Silicon Macs.
The phone's own hotspot and a Campsite guest on mobile data; hand-played Campsite games other than Sea Battle; synced music, karaoke, recordings and guest uploads.

SOURCES AND LIMITS

Where this record comes from.

Our October 11 published progress checkpoint and the October 12 dated real-device record.
The dated two-home, desktop, browser, Campsite and phone test reports, the Oct 13 Sea Battle two-person record, plus the recorded Android code-gap review.
The source change history through the October 13 snapshot, checked so unfinished work is not described as merged.
Self-hosted Google Fonts remain pending approval to obtain font packages; no font package was added for this update.

The machine-readable version of the public progress data is in testing-status.json. For feature-by-feature five-check status, see release evidence. For versioned notes, see updates.