ARAMTwo runtime modes
Application mode
Loads KTF WIPI, SKT SKVM, and LGT Raptor-family apps or games directly and emulates services such as display, audio, input, storage, and timing. Results vary because titles depend on different carrier and handset services.
System mode
Researches booting a complete Samsung handset from user-supplied firmware. A full cold boot and a bootloader handoff are distinct verification milestones.
v0.2.0 system-mode verification
ARAM version: v0.2.0 · core: e624402 · verified: September 2, 2026
| Handset and build | Verified milestone | Not generalized |
|---|---|---|
| SCH-W830 DL21 and DA18 | Fresh-media provisioning, power-cycle cold boot, home screen, verified keys, and a built-in app | Camera, cellular, Bluetooth, and arbitrary built-in or downloaded apps |
| SCH-W770 DA05 | Fresh-media provisioning, power-cycle cold boot, physical HOLD input, and the SKT home screen | Remaining controls and arbitrary apps |
| SCH-W860 DA06 | Fresh-media provisioning, power-cycle cold boot, and the home screen | Its model-specific keypad and arbitrary apps |
| SCH-W210, W240, W270, W290, W300, W330, W390, W420, and W460 | QCSBL-to-OEMSBL entry for an exact firmware set | Cold boot, display, input, filesystem, and app compatibility |
The evidence is the system firmware progress record included with v0.2.0. It publishes no firmware bytes or private paths.
Compatibility milestones
| Milestone | What it proves | What it does not prove |
|---|---|---|
| Recognized | The format and base metadata are identified | Loading or execution |
| Loads | Code and required regions are placed safely in memory | Entry-point execution |
| Executes | Guest code starts running | A rendered frame |
| First frame | The guest renders its first visible frame | Input, audio, saves, or a full playthrough |
| Playable | Core interaction and progression were exercised | Every part of the title |
| Complete | The defined verification scope was completed | A different carrier or build |
Application compatibility record boundary
- Hosts: Windows, macOS, Linux, Android, and web browsers
- Inputs: WIPI, SKVM, and Raptor-family application packages plus JAR or DAT inputs
- CPU baseline: a portable Go core covering ARMv5TE and Thumb execution
- Product tools: state, rewind, input mapping, debugger, cheats and patches, and compatibility reporting boundaries
Required fields for a public game record
| Field | Recorded value |
|---|---|
| Identity | Game or app name, carrier or runtime, input format, and privacy-safe image SHA-256 |
| Environment | ARAM version, test date, operating system, and selected device or carrier profile |
| Result | The reached recognized → loads → executes → first frame → playable → complete milestone |
| Evidence | Reproduction steps, known issues, and a related release, test, or GitHub issue |
ARAM does not create a title page from an unverified name alone. A searchable HTML record is added only after an exact version, hash, and reproduction procedure are available.
Write a reproducible report
Include the ARAM version, platform, input image SHA-256, reached milestone, and visible error instead of relying on a title name alone. Never attach the original game or firmware bytes.