Teaser: An ATAK Button Case for My Galaxy S9 EUDs

The OpenMANET radio carries the data, but the thing you actually look at is the phone running ATAK. I’ve got a few Galaxy S9s set aside as the end-user devices (EUDs), and poking a touchscreen with gloves on while it’s strapped to your chest gets old fast. So there’s a side build going: an ATAK button case with real buttons you can find by feel. Here’s a first look before the full write-up.

Render of the v4 ATAK button case for a Galaxy S9: one-piece body, screw-down front lid, full-width screen window and three shaped buttons on each end

v4: one-piece body, screw-down lid, and three buttons per side with different hole shapes so you can find them by feel.

The idea

  • Landscape, on the chest. The phone rides screen-up in landscape with a raised “wing” at each end.
  • Three buttons per wing. Each hole is a different shape (round, square, oval, counterbored), so you know which one you’re on without looking down.
  • The phone plugs into the case. This idea comes from my RAM Mount GDS tablet cases. The S9 slides onto a USB-C plug inside the case, and charging and data come in through ports on the outside. Nothing dangles off the phone itself.
  • The buttons are just a keyboard. A small controller in the case shows up to the phone as a USB keyboard, so each button sends a keystroke. Mapping those keystrokes to ATAK functions (drop a marker, center on me, and so on) comes later.
ATAK button case v4 with the lid off: the hub board and button board sit in the end wings around the phone, with the drop-in wedge at the phone's top end

Lid off: the hub board in one wing, the button board in the other, and the drop-in wedge holding the phone onto its USB-C plug.

Two custom boards

All of the electronics live on two boards I designed in KiCad. Both are finished, pass every design check, and are sitting in a folder ready to order from JLCPCB.

  • Hub board (right wing): the USB hub, the button controller, power for the phone, a data port out to the radio, and three buttons. It’s a 6-layer board only 0.8 mm thick. The USB-C plug that goes into the phone straddles the board edge with pins on both faces, and that one part only fits a 0.8 mm board.
  • Button board (left wing): three more buttons and the USB-C charge port. A 14-wire cable runs under the phone to tie the two together.
KiCad layout of the ATAK button case hub board, top and bottom, with three button switches, USB hub and controller chips

The hub board, top and bottom: a 6-layer, 0.8 mm board that plugs straight into the phone.

Where the print is

v3 got printed and strapped on. The overall shape and size sit well on the chest, so that stays. But the separate left-end piece felt fragile, and the slots for the phone’s own side buttons were a little off. So v4 changes how it goes together:

  • One-piece body with a screw-down front lid. Ten M3 cap screws into heat-set inserts, all outside the seal.
  • An o-ring cord seal around the lid joint. The ports and screen still need plugs and a film before I’d call it splash resistant.
  • A drop-in wedge that holds the phone onto its USB-C plug. The phone drops in, slides onto the plug, the wedge goes in behind it, and the lid goes on.
  • A bolt-on mount pod with the AMPS hole pattern, so the mount can be swapped.
  • The phone’s side-button slots moved to match the test print.

It grew a bit for all that: about 215 × 78 mm, roughly 30 mm thick with the pod. v4 is printing tonight on two printers at once, so I’ll have a usable one in hand either way.

Back of the ATAK button case v4 showing the camera cutout and the bolt-on mount pod with AMPS hole pattern

Back side: a bolt-on pod with the AMPS hole pattern for the chest mount.

Coming up

  • How v4 prints and fits.
  • Ordering the boards, then the full build write-up with all the details.
  • Soft TPU button caps captured in the rigid print. That’s my own R&D project once the boards are in hand.
  • Mapping the buttons to ATAK functions.

This is a side build of the OpenMANET radio project. The latest radio work is in part 7: 5 GHz on the mesh.

My OpenMANET Dual-Band Plan: HaLow + 5 GHz, a CM4 Carrier and a Handheld

In part 1 I got the basics of OpenMANET straight. This one is the plan, and the headline is the OpenMANET dual-band idea: a mesh that runs fast 5 GHz links when nodes are close together and falls back to long-reach 915 MHz HaLow when they drift apart, without the network ever dropping. Plus a handful of other things I want bolted on. Writing it down now so I can see later how far off I was.

Ground rule: stay compatible with stock nodes

I want my radios to join anyone else’s OpenMANET mesh, and theirs to join mine. So everything custom is an add-on on top of the stock firmware, never a fork of the core. For a node to join a mesh, these have to match:

  1. HaLow mesh ID, encryption key, channel and channel width
  2. Country/regulatory settings (the radio’s BCF file), so channels and power line up
  3. A compatible batman-adv version
  4. The stock network model: 10.41.0.0/16, a DHCP scope per node, one mesh gate

Anything I add has to be invisible or harmless to a node that doesn’t know about it. Before I call any custom feature done, it gets tested against an untouched stock node.

How OpenMANET dual-band works: let batman-adv do it

This turned out to be the easy part, because the mesh stack already supports it. batman-adv can bond several radio interfaces into one mesh. Add a 5 GHz 802.11s interface next to the HaLow one, attach both to the same bat0, and BATMAN_V picks routes by measured throughput.

  • Close together: the 5 GHz hop is way faster, so traffic moves onto it automatically. Clearer voice, video and file pushes.
  • Far apart: 5 GHz falls out of range and traffic falls back to HaLow. The network slows down; it doesn’t drop.
  • Stock nodes without a 5 GHz radio just see a normal HaLow mesh.

RTSP video, ATAK and file transfers get the benefit without knowing anything about it. They ride whichever link batman-adv picks.

OpenMANET dual-band diagram: close together, traffic rides a fast 5 GHz 802.11s link; far apart, batman-adv falls back to 915 MHz HaLow without dropping the mesh

Close in, batman-adv moves traffic onto 5 GHz. Far apart, it falls back to HaLow.

Not every 5 GHz radio can mesh

The radio has to support 802.11s mesh point mode, and a lot of popular cards don’t. Per the OpenMANET docs: the MT7916AED and MT7915DAN work (stability varies with kernel and driver), the QCA6174 works but only one network at a time, and the Intel AX200/AX210 and MT7921 are access-point only.

The Pi 4 only has USB for a second radio, so testing will use a MediaTek mt76-family USB adapter (MT7612U or MT7610U chips). Rule of thumb: shop by chip, not brand. Avoid MT7921-based Wi-Fi 6 sticks and Realtek RTL88xx adapters for mesh work. The final hardware gets a PCIe M.2 card (MT7916) on the CM4 board.

Voice that gets better when you’re close

Here’s the part I haven’t seen anyone else do. OpenMANET’s push-to-talk already uses Opus audio and adapts its error correction when packets drop. My add-on would go the other way: when every listener in a talk group is on a fast link, bump the Opus bitrate up for clearer audio, and drop back the moment anyone isn’t. Opus decoders follow bitrate changes on their own, so stock nodes still hear it fine.

Is anyone else doing this?

Multi-band mesh isn’t a new idea, to be fair:

  • OpenMANET upstream says work is underway to bond HaLow with 2.4 GHz using BATMAN_V. Same mechanism, different band, so I should talk to them before I start rather than duplicate their work.
  • Doodle Labs sells 900 MHz + 2.4 GHz Mesh Rider radios, but the whole mesh switches bands together to dodge interference. One band at a time, not a different band per link.
  • Silvus has a dual-band StreamCaster with a dual-frequency link feature. Proprietary, and military money.

What’s less common in mine is HaLow plus 5 GHz picked per link, voice that improves when nodes are close, and staying fully open and compatible with stock nodes. The adaptive voice piece is a good candidate to contribute back.

The other add-ons

  • 5G mesh gate. One node NATs the whole mesh onto the internet through the Quectel RM520N-GL 5G modem I pulled out of a swap-meet box. Its GNSS can supply that node’s position. On a Pi 4 it needs a USB 3 sled, since the PCIe HAT I was eyeing is Pi 5-only and OpenMANET targets the Pi 4 and CM4.
  • Drone DF link. My drone detection stations would plug into a node’s Ethernet port and publish bearings as Cursor-on-Target, so they show up on every ATAK screen on the mesh. Two stations could share bearings for triangulation over the same mesh. It’s all just IP, so the radio core doesn’t change.

The hardware end state: a CM4 handheld

I’ll admit it: I want it to look like a real tactical radio. The inspiration is something like the Silvus SC4200EP handheld, with a vehicle unit later once the hardware and software settle. I know it’s tacticool. I think they look cool. Moving on.

The CM4 is the same silicon as the Pi 4, so OpenMANET support and power draw carry over, but it exposes a PCIe lane the Pi 4 board doesn’t. A custom carrier board in KiCad could put all of this on one board:

  • CM4 with onboard eMMC (no SD card to shake loose in the field)
  • The HaLow card and a PCIe 5 GHz card on M.2 slots
  • GPS, power management and SMA connectors laid out the way I want
  • A removable battery pack that clips onto the bottom, so I can swap and keep going, plus a small onboard backup cell to stay alive during the swap
  • A PRC-148/152-style battery interface. Plan is to buy one adapter kit to learn the geometry, then 3D-print the radio and battery sides and only buy the metal contacts after that.

No 5G modem in the handheld. Too many antennas, too much heat and power for something you carry. That lives in the mesh gate and maybe the vehicle unit.

The roadmap

  1. Two stock Pi 4 nodes. Learn the system, bench test, range test.
  2. Add 5 GHz. Prove dual-band switching on USB adapters.
  3. 5G mesh gate with the RM520N-GL.
  4. CM4 carrier board in KiCad.
  5. Handheld enclosure in FreeCAD, then the battery packs.
  6. Drone DF link once that project is far enough along.
OpenMANET build roadmap in six steps: stock Pi 4 nodes, 5 GHz, 5G mesh gate, CM4 carrier board, handheld enclosure and drone DF link, with the stay-compatible ground rule

Six phases, one rule: every node has to join anyone’s stock OpenMANET mesh.

Everything in this stack is unlicensed: HaLow and 5 GHz Wi-Fi are Part 15, and the 5G modem rides a carrier’s license. Next up: the phase 1 parts list.

References

—
TL;DR: Bond a 5 GHz radio and the HaLow radio into one batman-adv mesh and routing picks the fast link automatically. Add adaptive voice, a 5G gate and a DF port, then shrink it all onto a CM4 board in a handheld, while staying compatible with stock OpenMANET.