POS Simulator

Overview

The POS Simulator boots an Android Virtual Device shaped like a specific payment terminal. You pick a vendor, model and variant; the simulator creates the AVD, applies the device’s screen, memory and peripheral profile, spoofs its ro.product.* build identity, and powers it on. Your APK then runs believing it is on that terminal.

It is a development and debugging rig, not a certification tool — but it is the real Android emulator underneath, so the app under test behaves as it would on the device.

Quick Start

1. Create a terminal profile — Open POS Simulator and add a profile in the left rail.
2. Pick the device — On the Device tab choose a manufacturer, a model, and the variant matching the unit you are targeting.
3. Adjust hardware if needed — The Hardware tab carries the model’s defaults; override only what you need.
4. Point at your SDK — On System & Boot confirm the Android SDK, system image and AVD name.
5. Launch — Launch POS Simulator opens the terminal window. Check the green prerequisites list, then Power on — the AVD is created if needed, booted, and given the device identity.
6. Install your app — Install APK… pushes your build onto the running terminal.

Device Tab

The Device tab picks which terminal the emulator will pretend to be. It has four parts: a Vendor filter with a model/variant/SKU search, the Model grid, the Variant chooser, and a Resolved device summary of what the AVD will actually be built from.

Vendors in the catalog

PAX, Ingenico, Kozen, Newland, Sunmi, Verifone, NexGo, Castles Technology, Telpo, plus two generic shapes — a 720×1440 Android terminal and a 480×480 square one.

Variants

Variants of one model differ in screen, memory, peripherals or Android version. Each carries a confidence badge:

Hardware Tab

Every control here writes an actual key into the AVD’s config.ini, driven by the emulator’s own hardware-properties.ini schema — the property name sits under each label so you can see exactly what is being set. Values come from the selected model; anything you change is stored as an override and can be reset. A validation strip at the top of the tab reports problems at edit time rather than as a failed boot ten minutes later.

Peripherals Tab

What the terminal has bolted to it, beyond the Android hardware. The model supplies these; the tab lets you confirm or override them.

System & Boot Tab

Where the Android toolchain lives and how the AVD boots.

Card & Host Tab

Where card data comes from, and where transactions are meant to go.

The Terminal Window

Launch POS Simulator opens the terminal itself. Two tabs are live today; the rest are placeholders that name what they will hold and which milestone brings them.