When engineers talk about latency in the field, they rarely mean a single number from a datasheet. They mean the distribution of delays between a physical event, software observation, and actuation — shaped by interrupt handling, kernel scheduling, driver quality, and how much unrelated work shares the CPU. On Android, that story includes a large userspace, aggressive power management, background services, and a Linux scheduler tuned for throughput and interactive fairness across many applications. The result is often excellent for smartphones; it is not always what you want when you are prototyping high-rate sensor pipelines or validating control ideas on constrained hardware.
QNX Neutrino is built as a microkernel-style real-time operating system: most drivers and services run in user space, with explicit message-passing and a scheduler designed around priority-based preemption. On a legacy BlackBerry 10 class device (QNX 8.0-era userland on ARM32), the overall software context — installed services, memory footprint, and typical runnable threads — can be dramatically smaller than on a modern Android handset. Smaller working sets improve cache locality; fewer daemons reduce contention; and predictable priority semantics make it easier to reason about worst-case response for a sensor callback or a tight control loop in the lab.
This is not a claim that every BB10 device is a substitute for a certified safety PLC or a formally verified RTOS deployment. It is a useful reminder that platform choice shapes jitter. For teaching, reverse-engineering, and open-source tooling on QNX-class systems, a lean stack can make the difference between “the demo stutters” and “the demo is trustworthy enough to iterate on.”
SW7FT’s public QNX work — including BerryCore, Chromium and Node.js ports, and toolchain experiments — sits in that spirit: preserving capable hardware as a developer platform, documenting quirks (alignment, libc, networking), and sharing reproducible builds so the community can push real software on real silicon instead of slides.
Disclaimer: SW7FT is not affiliated with or endorsed by BlackBerry Limited. References to BlackBerry, BB10, and QNX are for technical context only.