Four Low-Power GUI Techniques
Each technique addresses a different power consumer in the display subsystem. Apply them in combination for maximum battery life improvement.
Dirty-Region Rendering: CPU Wakes Only When Content Changes
A full-screen redraw renderer activates the CPU and DMA for a complete frame computation at every display refresh cycle — even if the screen shows a static clock face with only the seconds hand moving. At 60 fps this is 60 full render passes per second regardless of content change rate, burning energy continuously on pixels that have not changed.
Sparklet's dirty-region renderer marks only changed widget bounding rectangles. On a mostly static screen — an idle health monitor displaying heart rate that updates once per second — the dirty region is typically less than 3% of total display pixels. CPU and DMA are active for a few microseconds per second rather than continuously. The processor returns to sleep between dirty events, entering RTOS tickless idle or platform deep-sleep mode.
- Default behaviour in Sparklet — no power management configuration required
- Sleep current for Cortex-M4: ~1 µA; active render: ~10 mA — 10,000× difference
- On a 1 update/sec wearable UI, CPU is active for ~50–200 µs per second of operation
- Compatible with RTOS tickless idle for zero MCU power between dirty events
Display Backlight and Sleep API: 50–80% Power Saving From Backlight Management
In a typical TFT LCD display module, the LED backlight consumes 50–80% of total display subsystem power. At full brightness a 3.5-inch TFT backlight draws 40–80 mA at 3.3 V — 130–260 mW — from a battery that may supply only 500 mWh total. A wearable that dims after 5 seconds of inactivity and blanks after 15 seconds reduces average display power by 60–80% compared to always-on operation at full brightness.
Sparklet exposes a display sleep API accepting a brightness level (0–100%) and a transition duration in milliseconds for smooth fade. A hard on/off switch creates a visible flash on LCD backlights — the fade API eliminates this. Waking on touch or button input requires one API call — the display returns to the last active screen state without reloading the widget tree, as the tree is preserved in RAM during sleep.
- API: set brightness percentage + fade duration in milliseconds
- Inactivity timer configurable in application — Sparklet manages the backlight transition
- Instant wake: widget tree preserved in RAM, no screen reload on resume
- Typical power saving: 40–80% of total display subsystem power on TFT LCD products
Partial Refresh for OLED and E-Ink: Power Proportional to Changed Pixels Only
OLED displays consume power proportional to the number of illuminated pixels and their brightness — a black pixel on OLED consumes near zero power. Sparklet's dirty-region renderer naturally minimises OLED power by updating only changed pixels per frame. An always-on OLED watch face that updates only the seconds digit illuminates approximately 1,200 new pixels per second rather than refreshing all 240×240 = 57,600 pixels at 60 fps — a 2,880× reduction in pixels processed.
E-ink displays have a unique constraint: a full waveform refresh takes 0.5–2 seconds and consumes significant energy, while a partial refresh updates only changed pixels in 100–300 ms with 70–90% lower energy. Sparklet supports partial refresh mode for e-ink compatible display controllers — the dirty-region map is passed directly to the HAL display driver as the partial refresh region, eliminating full-screen waveform updates for all incremental content changes.
- OLED: dirty-region renderer limits powered pixels per frame automatically
- E-ink: partial refresh completes in 100–300 ms vs 1–2 s for a full waveform update
- E-ink partial update energy: 70–90% lower than full waveform update per event
- Compatible e-ink controllers: SSD1683, IL3897, and equivalents via HAL abstraction
Always-On Watch Face Mode: Sub-Milliwatt MCU Render Power
Smartwatches and fitness trackers require an always-on display mode where a minimal watch face — time, date, step count — remains visible continuously on OLED or Memory-in-Pixel (MIP) displays at the lowest possible power. Sparklet supports an always-on mode where the render task updates only the specific widgets carrying time-sensitive data on each RTC wake.
In always-on mode, the MCU wakes from deep sleep on a 1-second RTC tick, updates the time widget's dirty region (approximately 40×60 pixels for a seconds digit), renders and flushes only that region to the display, then returns to deep sleep. Total MCU active time per second: 100–500 µs. Average MCU power contribution: under 0.1 mW. The display panel itself consumes 0.5–2 mW in always-on mode depending on lit pixel count. See the full architecture at Wearable Display GUI.
- RTC-driven wake triggers dirty-region update of time widget only — no full screen redraw
- MCU active for 100–500 µs per 1-second update cycle
- Widget tree preserved in RAM throughout deep sleep — no reload on each RTC wake
- Compatible with all RTOS and bare-metal deep sleep implementations
