--- title: "Timing information and power scheduling — PToB research" description: "An awake six-run timing pilot and hypothetical wake/listen energy models, retaining 42 refreshed windows out of 120 and incomplete BLE observation coverage." url: "https://ptob.dev/research/awake-timing-power-scheduling/" language: "en" robots: "index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1" representations: {"application/json":"https://ptob.dev/research/awake-timing-power-scheduling/?format=json","text/markdown":"https://ptob.dev/research/awake-timing-power-scheduling/?format=markdown"} format_description: "https://ptob.dev/agent-formats.json" --- # How Much Timing Information Is Enough? Awake Hardware Evidence and Wake/Listen Energy Models for PToB Research draft 19 October 2026 15 pages · PDF How little new timing information could sustain a useful clock between listens? [Read PDF](https://ptob.dev/papers/preview/?file=%2Fpapers%2Fptob-power-scheduling-preprint.pdf)[Cite this edition](https://ptob.dev/research/awake-timing-power-scheduling/#citation) ## Overview Six randomized awake T096 runs used 125 ms training windows and 5, 10 or 20 second HOLD intervals. Only 42 of 120 windows refreshed the fit; 78 were empty. The study combines that information-budget pilot with explicit guard, drift, wake and reacquisition models. ## What this paper covers - Distinguish a training aperture from physical radio duty and measured energy. - Keep inherited fit history, missing pairs and post-turnover evidence visible. - Define retained-counter sleep and metered-power experiments that could test the proposed savings. ## Research scope Radio reception and the precision counter remained active. Scheduled training fractions are not measured airtime or energy savings. Only one run replaced all acquisition pairs, leaving 10.17 seconds of post-turnover evidence. Physical sleep, wake, power and cold-start qualification remain future work. ## Read it in context Read this earlier awake pilot separately from the 30 October W12 holdover-duration study. They use different targets, estimands and observation populations. [Public pilot data and offline verifier](https://github.com/yantisj2/PToB/tree/main/evidence/power/2026-10-19)[Later W12 holdover study](https://ptob.dev/research/empirical-ble-holdover/) ## Cite this edition Jonathan Yantis. How Much Timing Information Is Enough? Awake Hardware Evidence and Wake/Listen Energy Models for PToB. 19 October 2026. Research draft. [Original PDF](https://ptob.dev/papers/preview/?file=%2Fpapers%2Fptob-power-scheduling-preprint.pdf). Summary permalink: [https://ptob.dev/research/awake-timing-power-scheduling/](https://ptob.dev/research/awake-timing-power-scheduling/) Jonathan Yantis leads protocol design, hardware development and research. GPT 6.1 contributes implementation, analysis and documentation. This page summarizes the linked edition; retain its original evidence dates and measurement references. ## The full paper The original document includes the technical detail and references behind this summary. [Read PDF](https://ptob.dev/papers/preview/?file=%2Fpapers%2Fptob-power-scheduling-preprint.pdf) [Cite this edition](https://ptob.dev/research/awake-timing-power-scheduling/#citation) [Paper sources on GitHub](https://github.com/yantisj2/PToB/blob/main/papers/README.md) ## Continue exploring [Affordable timing from Starlink over WiFi](https://ptob.dev/research/starlink-wifi-timing/)[Trustworthy timing in Zephyr](https://ptob.dev/research/zephyr-hardware-timestamps/)[Low-level timing on ESP32-S3](https://ptob.dev/research/esp32-s3-event-capture/)[BLE timing tails and multipath](https://ptob.dev/research/ble-timing-tails-multipath/)[From BLE to a Pi NTP/PTP gateway](https://ptob.dev/research/pi5-mhat-time-gateway/)[From USB frames to a macOS clock](https://ptob.dev/research/usb-macos-time-transfer/)[Empirical BLE-trained holdover](https://ptob.dev/research/empirical-ble-holdover/)[ESP32-S3 causal clock discipline](https://ptob.dev/research/esp32-s3-causal-clock-discipline/)[All research & evidence](https://ptob.dev/research/) ## Structured data ```json { "@context": "https://schema.org", "@graph": [ { "@type": "WebSite", "@id": "https://ptob.dev/#website", "url": "https://ptob.dev/", "name": "PToB", "alternateName": [ "Precision Time over BLE", "Precision Time over Bluetooth" ], "description": "Bluetooth and USB software clocks: W12 60.3 ns relative-PPS RMS over 522/600 observations, separate 64 s sampled holdover, and CoreSE diagnostics.", "inLanguage": [ "en", "de" ], "publisher": { "@id": "https://ptob.dev/#jonathan-yantis" } }, { "@type": "Person", "@id": "https://ptob.dev/#jonathan-yantis", "name": "Jonathan Yantis", "url": "https://github.com/yantisj2/PToB/blob/main/CREDITS.md" }, { "@type": "Project", "@id": "https://ptob.dev/#project", "name": "PToB", "alternateName": "Precision Time over BLE", "url": "https://ptob.dev/", "description": "An independent protocol project researching precision time transfer across Bluetooth-enabled microcontrollers and USB clients.", "sameAs": "https://github.com/yantisj2/PToB", "member": { "@id": "https://ptob.dev/#jonathan-yantis" }, "knowsAbout": { "@id": "https://ptob.dev/#protocol" } }, { "@type": "Thing", "@id": "https://ptob.dev/#protocol", "name": "Precision Time over BLE", "alternateName": "PToB", "description": "An experimental PTP-inspired protocol proposal for wireless clock synchronization over Bluetooth Low Energy." }, { "@type": "WebPage", "@id": "https://ptob.dev/research/awake-timing-power-scheduling/#webpage", "url": "https://ptob.dev/research/awake-timing-power-scheduling/", "name": "Timing information and power scheduling — PToB research", "description": "An awake six-run timing pilot and hypothetical wake/listen energy models, retaining 42 refreshed windows out of 120 and incomplete BLE observation coverage.", "inLanguage": "en", "keywords": [ "Bluetooth clock synchronization", "Precision Time over BLE", "Implementation & time transfer" ], "isPartOf": { "@id": "https://ptob.dev/#website" }, "author": { "@id": "https://ptob.dev/#jonathan-yantis" }, "about": { "@id": "https://ptob.dev/#protocol" }, "dateModified": "2026-10-30", "image": "https://ptob.dev/social/ptob-timing-v3.jpg", "breadcrumb": { "@id": "https://ptob.dev/research/awake-timing-power-scheduling/#breadcrumbs" }, "mainEntity": { "@id": "https://ptob.dev/papers/ptob-power-scheduling-preprint.pdf#article" } }, { "@type": "BreadcrumbList", "@id": "https://ptob.dev/research/awake-timing-power-scheduling/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "PToB", "item": "https://ptob.dev/" }, { "@type": "ListItem", "position": 2, "name": "Bluetooth and Starlink timing research and results", "item": "https://ptob.dev/research/" }, { "@type": "ListItem", "position": 3, "name": "Timing information and power scheduling", "item": "https://ptob.dev/research/awake-timing-power-scheduling/" } ] }, { "@type": "ScholarlyArticle", "@id": "https://ptob.dev/papers/ptob-power-scheduling-preprint.pdf#article", "url": "https://ptob.dev/research/awake-timing-power-scheduling/", "headline": "How Much Timing Information Is Enough? Awake Hardware Evidence and Wake/Listen Energy Models for PToB", "name": "How Much Timing Information Is Enough? Awake Hardware Evidence and Wake/Listen Energy Models for PToB", "description": "An awake six-run timing pilot and hypothetical wake/listen energy models, retaining 42 refreshed windows out of 120 and incomplete BLE observation coverage.", "author": { "@id": "https://ptob.dev/#jonathan-yantis" }, "datePublished": "2026-10-19", "dateModified": "2026-10-19", "inLanguage": "en", "creativeWorkStatus": "Research draft", "about": { "@id": "https://ptob.dev/#protocol" }, "mainEntityOfPage": { "@id": "https://ptob.dev/research/awake-timing-power-scheduling/#webpage" }, "image": "https://ptob.dev/social/ptob-timing-v3.jpg", "encoding": { "@type": "MediaObject", "contentUrl": "https://ptob.dev/papers/ptob-power-scheduling-preprint.pdf", "encodingFormat": "application/pdf" }, "isPartOf": { "@id": "https://ptob.dev/research/#webpage" } } ] } ```