Glossary
Phones and hardware
Section titled “Phones and hardware”UMS9117
Section titled “UMS9117”The Unisoc chip used by several supported phones, also known by its reference name T117. See UMS9117 features.
SC9820E
Section titled “SC9820E”The Unisoc chip used by the Xiaomi Qin 1s+. See SC9820E features.
Platform
Section titled “Platform”The code shared by phones with the same chip. FPLinux has the ums9117 and sc9820e platforms.
Target
Section titled “Target”The description of one exact phone model, and the name you pass to ./fplinux build and ./fplinux run, such as nokia-ta1618. A target is never used for a different model. See Phones.
Support status
Section titled “Support status”The result for one function on one exact phone, with its tested conditions and remaining limits. See the phone status legend. Hardware presence is a separate fact.
Implementation status
Section titled “Implementation status”Whether FPLinux provides a function on a particular platform. This does not establish a device result or support on every model. See Features.
Stock firmware
Section titled “Stock firmware”The software the phone came with. Starting the phone normally, without the boot key, starts it.
Internal storage
Section titled “Internal storage”The phone’s built-in flash memory, which holds the stock firmware. Targets with a read-only NAND interface can prepare device data and backups. Other targets provide no internal-storage access.
Device data
Section titled “Device data”Radio firmware and calibration, Bluetooth records, FM settings and audio tuning from your own phone. FPLinux does not ship these inputs. Target-owned board initialization and Linux keymaps are separate. See Device data.
Loading the phone
Section titled “Loading the phone”Loader
Section titled “Loader”The PC side of a start: ./fplinux run in a source checkout, or fplinux.py run in a standalone archive. The shared runtime prepares required phone data on first use, sends FPLinux over USB and opens SSH. Targets without required phone data boot directly. Running the same command again reopens an authenticated live session. See Run FPLinux.
Boot key
Section titled “Boot key”The key you hold while connecting USB to a powered-off phone so that it waits for a load instead of starting its stock firmware. Use the exact key listed on your phone page.
BootROM
Section titled “BootROM”Code built into the chip that runs first. With the boot key held, it appears on the PC as USB device 1782:4d00 and accepts a load.
RAM loader (FDL1)
Section titled “RAM loader (FDL1)”A small program that the loader sends first. It prepares the phone’s memory and receives the rest of the system.
USB network link
Section titled “USB network link”The private network over the USB cable that the shell, file copies and the PC keyboard use once Linux runs. The phone then appears as USB device 0525:a4a6. See Connect from a computer.
RAM system
Section titled “RAM system”The default build. It runs entirely from the phone’s RAM and forgets everything at power-off.
microSD system card
Section titled “microSD system card”A build that keeps the Linux system on a microSD card, so packages and files persist. Each cold start still needs the PC loader. UMS9117 uses U-Boot to start Linux from the card; SC9820E loads Linux over USB and mounts the card as its root. See microSD system card.
Builds and packages
Section titled “Builds and packages”Profile
Section titled “Profile”The boot mode a build is made for: the RAM system by default, or a microSD system card with microsd-uboot on supported UMS9117 targets and microsd-root on Qin. Check your phone’s supported profiles and pass the same --profile to every command for that build.
Build type
Section titled “Build type”release by default, or debug, which adds kernel diagnostics. See Debugging.
Optional package
Section titled “Optional package”An application delivered as an APK file and installed on a running phone with apk. See Optional packages.
Standalone archive
Section titled “Standalone archive”A packaged FPLinux for one phone that runs without a source checkout or build tools. See Standalone archive.