Feature request: let the user pick which language packs get flashed
Problem
Every build ships all 33 languages, but a user only ever reads one or two. The translation tables are a fixed cost in an app partition that is already close to full, and that space is what new features have to fit into. They are also paid twice, once in each OTA slot.
Proposed solution
Add a Language Options block to the flasher UI: a checkbox list of the available languages, defaulted to English plus the browser locale. The user ticks the ones they want and the flasher writes an image containing only those.
The reference model is the Betaflight Configurator flasher, where the user picks features before the image is written to their board.
User flow
- User connects the device to the flasher.
- The flasher shows a Language Options section.
- User ticks one or more languages (English always on — it is the fallback for missing keys).
- The flasher flashes the firmware plus the selected locales.
- Settings → Language then lists exactly those entries.
Feature request: let the user pick which language packs get flashed
Problem
Every build ships all 33 languages, but a user only ever reads one or two. The translation tables are a fixed cost in an app partition that is already close to full, and that space is what new features have to fit into. They are also paid twice, once in each OTA slot.
Proposed solution
Add a Language Options block to the flasher UI: a checkbox list of the available languages, defaulted to English plus the browser locale. The user ticks the ones they want and the flasher writes an image containing only those.
The reference model is the Betaflight Configurator flasher, where the user picks features before the image is written to their board.
User flow