-
-
Notifications
You must be signed in to change notification settings - Fork 186
Functionalities explained
Launcher opens to a main menu. The exact layout changes by screen size and device capabilities, but the current menu can include SD, OTA, WUI, USB, PMan, CFG, and installed app shortcuts.
SD opens the SD card browser.
From the file browser you can:
- enter folders
- install
.binfirmware files - create folders
- rename files and folders
- copy files
- paste copied files into another folder
- delete files and folders
The file list can show only binaries or all files, depending on the See All Files setting. Dotfiles can also be hidden or shown.
OTA opens the online installer. Launcher connects to WiFi and queries LauncherHub for firmware metadata.
The OTA menu supports:
- firmware list browsing
- pagination
- ordering by downloads, name, or latest update
- starred firmware filtering
- text search
- version selection
- direct online install
- download to SD card
- adding firmware to Favorites
If Favorites are configured, the OTA entry first lets you choose between the normal OTA list and the Favorite list. Favorites can point to LauncherHub firmware IDs or direct firmware links.
WUI starts the Web User Interface. Connect with a browser to the IP address shown on the device.
The WebUI can:
- browse SD card files
- upload one or more files
- upload folders through supported browsers
- download files from the SD card
- delete files and folders
- create folders
- rename files and folders
- install a firmware file already on the SD card
- upload and install firmware directly from the computer or phone
- split merged firmware when app and SPIFFS sections are detected
- edit text-like files such as
.txt,.ini,.conf,.c,.cpp,.h,.hpp,.js,.css,.htm, and.html - view and edit NVS fields, except protected internal keys
Default WebUI credentials are admin / launcher.
USB appears on devices with USB OTG support. It exposes the SD card as a USB mass storage device, so the SD card can be managed from a computer without removing it from the device.
The option requires a mounted SD card. If no SD card is present, Launcher will ask you to insert one.
PMan is the Partition Manager.
Use it to inspect and modify the device partition table. It shows system, app, data, and free regions. Protected partitions are marked with *.
For existing partitions, available actions can include:
- Details
- Backup
- Restore data
- Edit Size
- Remove
- Format
For free space, available actions can include:
- Add OTA
- Add FAT
- Add SPIFFS
Changes are staged first. Use Apply Changes to write the new table or Discard Changes to reload the current table.
Partition changes can erase or move data. Back up important FAT or SPIFFS partitions before editing layouts.
CFG opens Launcher settings.
Current settings can include:
- Charge Mode
- Brightness
- Dim time
- UI Color
- Orientation
- See All Files
- Show Dotfiles
- Boot to Launcher
- Ask to copy SPIFFS
- Partition Manager
- Backup SPIFFS
- Restore SPIFFS
- Boot Animation, when developer mode is enabled
- Calibrate Touch, on resistive touch devices
- Restart
- Turn-off, on supported devices
Boot to Launcher controls whether the device always stays in Launcher or automatically boots an installed app. The label is shown as a checkbox-style toggle.
Ask to copy SPIFFS controls whether Launcher asks before installing SPIFFS/LittleFS data when the firmware includes or declares one.
Installed firmware can appear directly on the main menu. Selecting an installed app opens actions:
- Launch the app
- Rename the app
- Delete the app
- Cancel
Deleting an app removes its OTA app partition entry. If the app has linked FAT data partitions, Launcher can remove those too, then compact the partition table and restart.
Headless ESP32 and ESP32-S3 builds are intended for devices without the normal display/button UI. SD card pins can be configured and stored, and the WebUI is the primary management path.
For the best compatibility:
- use SDHC, not SDXC
- use 32 GB or smaller cards
- format as FAT32
- use MBR partitioning, not GPT
- prefer 8 GB or 16 GB cards when possible
Some devices share SPI between the display, touch controller, LoRa hardware, and SD card. Launcher includes board-specific setup to reduce bus conflicts, but SD card quality and formatting still matter.