Pi Zero Pocket Terminal with a BlackBerry Keyboard

Posted on Mar 5, 2026

I have been sketching a handheld terminal build that feels closer to a BlackBerry than a generic mini cyberdeck: pocketable, keyboard-first, and practical to daily-carry.

The current target is a Raspberry Pi Zero 2 W paired with a BlackBerry Q10 keyboard and a small HDMI display. The planning pass answered three key questions: screen size, missing parts, and what a realistic full BOM looks like.

Design targets

  • Form factor: one-hand/pocket-friendly, keyboard-first.
  • Display sweet spot: 3.7" to 4.0" for a BlackBerry-like feel.
  • Resolution target: at least 480x800 (or 720x720 if panel options make sense).

Below 3.5" gets cramped for terminal work unless fonts are tiny. Above 4.3" starts to feel less “phone-like” and drives enclosure size up quickly.

Keyboard architecture

The Q10 keyboard does not behave like a direct USB keyboard on its own. The practical approach is:

  1. Q10 keyboard module + BBQ10/Q10 breakout.
  2. Small MCU with native USB HID (RP2040 Pro Micro, XIAO RP2040, or ATmega32U4 Pro Micro).
  3. Firmware that scans keys and emits USB HID to the Pi over OTG data.

This keeps keymapping flexible and allows layers/functions for terminal-heavy use.

Core build stack

  • Raspberry Pi Zero 2 W
  • 3.7"-4.0" HDMI LCD
  • BlackBerry Q10 keyboard (+ at least one spare)
  • BBQ10/Q10 breakout board
  • USB-HID capable MCU
  • mini-HDMI -> HDMI path for video
  • USB OTG data path from keyboard MCU to Pi
  • 32-64GB microSD (A1/A2)

Power and reliability notes

  • Use a stable 5V rail sized for Pi + display + MCU startup peaks.
  • If battery-powered, include proper 1S charge/protection and 5V boost.
  • Keep common ground across Pi, display, and keyboard MCU.
  • Add decoupling and at least one bulk cap near display/power input.
  • Plan for thermal headroom inside the enclosure.

Build risks to handle early

  • Q10 connector handling is delicate; buy spare keyboard modules.
  • OTG cable/role mistakes are common; validate data path early.
  • Display inrush and brownouts can look like random boot instability.

Next milestone

I am treating this as a staged build:

  1. Bring up keyboard MCU -> USB HID on bench.
  2. Validate Pi input + display + power stability on bench.
  3. Move to enclosure with buttons, strain relief, and serviceable wiring.

If you are planning a similar build, the two biggest time savers are buying spare Q10 parts up front and proving the power path before any enclosure work.