Why LOUP Is Speakerphone-First Instead of a Small Smartphone
Removing the browser, camera and text stack changes both the product and the firmware architecture.
TOPIC
LOUP Engineering
Lessons, explainers, experiments, and implementation notes.
Parent-Approved Contacts Are an Architecture Rule, Not a UI Filter
Contact approval has to be enforced by backend identity and call routing, not only hidden buttons.
Why the Firmware Has to Stay PBX-Agnostic
Hard-coding one PBX would turn infrastructure choice into a firmware release dependency.
One Device, One SIP Identity
Sharing SIP credentials across devices makes revocation, auditing and fleet diagnosis ambiguous.
The Device State Machine Is Part of the Product Contract
Factory, pairing, active, blocked and retired are operational states with different permissions.
Why the Backend and PBX Need an Adapter Boundary
Identity and parental policy should not be embedded inside SIP routing rules.
Removing Text and Social Features Also Reduces the Security Surface
Product restraint changes threat modeling as much as it changes UX.
Physical Controls Are Part of the Reliability Model
A voice device should remain operable when the display is slow or partially refreshing.
Why Firmware Ownership Stays Separate from the Manufacturer
Hardware development and firmware product logic have different long-term ownership requirements.
Preserve Working Audio Before Adding Product Features
A stable voice path is more valuable than several new features built on a regression.
Reading the ESP32-S3 Memory Map Before Blaming Firmware
Observed flash and PSRAM capacity define what the build and runtime can actually support.
ES8311 and ES7210 Split the Audio Problem in Two
Speaker output and microphone capture travel through different codec responsibilities.
The ES7210 Channel Map Matters More Than the Channel Number in Code
AEC depends on what signal actually lands in each TDM slot.
Unused AXP2101 Rails Should Be Explicitly Disabled
Power rails that are not part of the design should not be left in an accidental state.
VSYS Bulk Capacitance Shows Up as a System Problem
Short current transients can make a stable-looking digital design fail under real audio and radio load.
A WS2812 on a 3.3 V GPIO Needs a Real Logic-Level Decision
A digital LED can still sit on an analog margin problem.
A Service-Replaceable Battery Changes Mechanical and Firmware Assumptions
A screwed back plate makes battery replacement possible but also affects sealing, state retention and service procedure.
USB-C Is Not the Same Thing as a Factory Debug Strategy
One external connector does not remove the need for reliable programming and recovery access.
Pin Maps Belong in the Bring-Up Evidence
One wrong GPIO can imitate a codec, driver or clocking failure.
A Tinny Speaker Is Not Automatically a Codec Bug
Acoustic complaints have to be separated into source, amplifier, transducer and enclosure effects.
I2S Clocking Is the Backbone of the LOUP Audio Path
MCLK, BCLK and LRCK have to agree before higher-level audio debugging means anything.
Upsampling 8 kHz Voice to 16 kHz Can Add Its Own Grit
Sample-rate conversion is audible when the implementation is crude or placed in the wrong part of the pipeline.
A Jitter Buffer Should Absorb Arrival Variation, Not Become a Delay Bucket
More buffering reduces underruns until it starts creating latency and hiding drift.
Clocked Playout Fixed a Class of Problems Packet-Driven Playback Could Not
RTP arrival time should not directly schedule the speaker.
I2S Auto-Clear Prevented Old Samples from Becoming New Noise
DMA behavior after underrun can shape what a user hears during gaps.
Volume Stuck Near 80 Percent Was a Gain-Path Problem, Not a UI Problem
A slider value is meaningless until every digital and analog gain stage is mapped.
Eliminating the Downlink Stall Was More Important Than Tuning Tone
A clean frequency response is irrelevant if the playback path periodically stops feeding samples.
Long Calls Expose Drift That Short Calls Hide
A 30-second audio test can pass while two clocks slowly walk apart over several minutes.
The 80 to 240 Millisecond Bursts Needed Packet and Audio Timelines Together
Short audible failures can be network gaps, scheduling gaps or local conversion artifacts.
Speaker Quality Needs a Reference Signal Before Subjective Listening
Listening tests become more useful when the input and operating point are controlled.
AEC Starts with the Correct Far-End Reference
An echo canceller cannot remove playback it never receives as a reference signal.
Bypassing AEC Was a Diagnostic Tool, Not a Product Direction
Turning processing off can reveal whether the artifact is created before, inside or after the algorithm.
V117 Was Useful Because It Failed Clearly
A bad experimental build can be valuable when it changes a small set of variables and is easy to revert.
Removing the Downlink Suppressor Improved the Stable Build
More signal processing is not automatically better audio.
Echo at High Volume Is Partly an Acoustic Design Problem
AEC has finite cancellation authority when the speaker physically couples strongly into the microphones.
Echo and Feedback Are Not the Same Failure
A delayed copy of far-end speech and an unstable acoustic loop require different diagnosis.
Latency Can Break AEC Even When the Signals Are Correct
A valid reference that arrives at the wrong time can be almost as useless as the wrong reference.
AEC Startup Needs a Defined State
The first seconds of a call should not depend on whatever history remains in DSP buffers.
Raw Multichannel Capture Is the Ground Truth for AEC Debugging
Processed audio alone hides whether the wrong signal entered the algorithm.
AEC Acceptance Should Include Double-Talk
A speakerphone must handle the user talking while the far end is also active.
SIP Registration Is a Device-Identity Checkpoint
A successful REGISTER proves more than network reachability because it joins device credentials to PBX state.
An INVITE Is Only the Start of the Call Contract
Call setup includes dialog state, SDP negotiation and route continuity after the first request.
SDP Is Where Signalling Hands the Call to Media
A SIP call can connect perfectly and still carry no useful audio if the negotiated media description is wrong.
RTP Port Ranges Belong in the Network Design
Media cannot be debugged reliably if the firewall and PBX disagree on where RTP is allowed.
One-Way Audio Is Usually a Directional Problem
If one side hears audio, several parts of the media path are already proven.
Low Packet Loss Does Not Mean Smooth Audio
Burst timing can hurt a speakerphone even when aggregate RTP loss is close to zero.
UDP Was a Deliberate Starting Point for the PBX MVP
Transport choice should match the test objective before adding more complexity.
BYE Handling Is Part of Resource Correctness
A call that starts and carries audio but does not terminate cleanly can leak state across the device and PBX.
A Device SIP Account Should Be Rotatable Without Reflashing Firmware
Telephony credentials are runtime configuration, not compiled product identity.
Two-Device Local Calls Are a Better Milestone Than a Single Loopback Test
A real endpoint pair exposes assumptions hidden by softphones and local echo tests.
Why Asterisk Was the Right PBX for the LOUP MVP
The first PBX needed to be inspectable, scriptable and easy to correlate with packet captures.
Extension 3004 and 3005 Became Reference Endpoints
Named test identities make repeatable call scenarios easier to describe and automate.
Inbound DID Testing Proves a Different Route Than Extension-to-Extension Calls
External ingress adds routing and policy that a local PBX call does not exercise.
PBX Timer Underrun Can Sound Like an Endpoint Bug
Server scheduling can inject media timing problems even when embedded firmware has not changed.
RTP Burst Measurements Need the Network and the Playout Buffer in the Same Report
Packet timing only becomes actionable when it is tied to endpoint tolerance.
Local PBX Testing Removes the Internet Before It Removes Complexity
A LAN test still exercises SIP, RTP, codecs and clocks while excluding WAN variability.
PBX Registration Health Is Not Call Health
A green registration table can coexist with broken dialog routing or media.
The PBX Adapter Keeps Product Identity Out of Dialplan Files
Asterisk should route calls, not become the only database of parent-approved relationships.
Five Devices and Twenty Devices Are Different Tests
Fleet size introduces registration churn, simultaneous calls and operational visibility that a pair cannot show.
A Reference Softphone Is Valuable Because It Is Not the Device Under Test
Linphone provides a known endpoint for separating PBX problems from embedded endpoint problems.
Wi-Fi Provisioning Is the First Real Device-Onboarding Boundary
A factory-fresh device has to join a trusted network before any cloud or PBX workflow can begin.
QR Pairing Should Bind a Physical Device to a Backend Identity
Scanning a code is useful only if the backend can prove which unit and account the ceremony joins.
Backend-Delivered SIP Configuration Keeps Secrets Out of Factory Images
Per-device PBX credentials should be provisioned after identity is established, not cloned into every unit.
Factory and Unpaired Are Different States
A board leaving production and a consumer device waiting for ownership are not the same operational condition.
Blocked Has to Override Normal Device Behaviour
A backend revocation is ineffective if the device keeps registering and calling because local state still says active.
Transfer Pending Prevents Ownership Change from Becoming a Race
Moving a device between accounts needs an intermediate state while old and new authority are resolved.
OTA Required Is a Policy State, Not Just a Notification
Some firmware updates are optional improvements; others must gate service because compatibility or security changed.
Status Heartbeats Need Identity, Version and Health Context
A backend cannot manage a fleet from a last-seen timestamp alone.
Global Factory Credentials Would Turn One Leak into a Fleet Incident
Convenient shared bootstrap secrets create the largest possible blast radius.
Provisioning Failure Needs a Recoverable Path
A device that loses power or Wi-Fi halfway through setup should not become permanently ambiguous.
V115 Stayed Valuable Because It Was Preserved as a Known-Good Artifact
An old build can be more useful than a new branch when a regression removes the reference point.
V132A Became Golden Because It Was Reproducible in Binary and Source
A release is stronger when the exact app image and the source snapshot both survive.
App-Only Flashing at 0x20000 Made Audio Iteration Faster
Updating only the application partition avoids rewriting unrelated state during tight firmware experiments.
Dual OTA Slots Need an Acceptance State
Booting the new partition once is not enough to declare it safe.
ECDSA Signing Makes the Device Verify Who Produced the Firmware
Transport security alone does not prove an artifact should be trusted after download.
Rollback Has to Include Persistent-State Compatibility
Returning to an older binary is unsafe if the newer release already changed data the old code cannot read.
Canary and Stable Are Different Release States
A release that works on one device should not silently become the fleet default.
Sticky Heartbeat Results Must Not Rewrite a New OTA Assignment
Old local status text can outlive the release that originally produced it.
Release Channels Have to Follow Promotion State
Calling a release STABLE while its channel remains canary creates two sources of truth.
Firmware Acceptance Should End in an Observable ACTIVE State
A successful download is not the same thing as a successful deployment.
A 168 by 384 E-Paper Screen Changes the UI Grammar
Portrait monochrome e-paper rewards stable hierarchy and punishes unnecessary redraws.
Partial Refresh Is a Product Resource
A UI transition has a display cost, so redraw scope becomes part of firmware design.
The Rotary Encoder Makes Lists Work Without a Touchscreen
Infinite scroll plus push maps naturally to small menu selection when the display is not interactive.
Call, Volume and Mute Deserve Dedicated Controls
Critical in-call actions should not require navigating back to a menu.
One RGB LED Is Enough When Its States Are Designed
A single status light can become confusing if color, blink and priority are not treated as a protocol.
Incoming Call UI Has a Hard Timing Requirement Even on E-Paper
The user must see caller identity before deciding whether to answer, despite slow display behavior.
Active Call UI Should Show State Without Competing with the Conversation
During a call, the screen is for confirmation and control feedback rather than continuous content.
Volume Feedback Can Be a Small Partial-Refresh Overlay
A physical button needs visible confirmation without forcing a page transition.
Battery and Signal Indicators Need Honest Granularity
Tiny icons can imply precision the underlying measurements do not actually support.
The EVT Toggle Switch Should Not Define the Production Power UX
Prototype hardware can be adapted in firmware without turning the prototype limitation into the final product.
One Microphone or Two Is a System Decision
Microphone count changes acoustics, PCB, enclosure, DSP assumptions and factory test.
IPX4 Has to Be Designed Around Openings, Not Added at Certification
Speaker, microphone, buttons and battery access all create splash-resistance paths.
CAD for Presell and EVT for Engineering Solve Different Problems
A polished render can validate product communication while an ugly prototype answers technical questions.
EVT, DVT and PVT Need Different Acceptance Questions
A prototype phase name is useful only when the team knows what evidence graduates the build.
Factory Programming Should Produce Traceable Device Identity
Flashing firmware is only one step in turning a PCB into a managed product.
Debug Pads Are Insurance for the Units That Do Not Boot
Production fixtures need a recovery path below the application firmware.
Returning the Tinny EVT Unit Is Part of Root-Cause Control
Remote descriptions of sound are not enough when hardware, assembly and enclosure can all differ.
A Two-Device Pass Should Precede the Five- and Twenty-Device Ramp
Fleet growth should happen after the representative call path is stable on real hardware.
Factory Audio Test Needs Objective Signals Before Human Listening
A worker saying a unit sounds fine cannot be the only acoustic acceptance criterion.
Manufacturer Scope and Firmware Scope Need a Written Interface
Teams move faster when hardware decisions and application decisions meet at explicit contracts.