Trezor firmware

This commit fixes a typo in the code that manages the Optiga secure chip's metadata. The code was writing a value to the wrong variable name (`metadata_locked` instead of `metadata`). Because the intended `metadata` structure was not fully initialized, the device might have compared stored secure-chip settings against an incomplete or incorrect expected value. In the worst case this could affect whether the device correctly detects that the Optiga chip is configured, which is part of the hardware-security boundary protecting secrets. The change is a one-line variable-name correction and is marked [no changelog], so the vendor does not describe it as a security fix.

This commit removes a 'Go to bootloader' menu option from normal user builds of the Trezor hardware wallet, keeping it only in debug/developer builds. The change prevents an ordinary user from intentionally or accidentally rebooting the device into bootloader mode through the on-device menu. While entering bootloader mode is a normal part of firmware updates, exposing it in production builds could let a local attacker with brief physical access force the device into a state where they could attempt to install modified firmware or interfere with an update. The patch is narrow: it only hides the menu item behind a debug-only compile flag, so the underlying bootloader entry mechanism still exists for legitimate update workflows.

This commit fixes a UI flow bug in the Trezor hardware wallet's 'Eckhart' layout. Previously, when a user opened a menu during a confirmation screen and chose an item, the wrong internal signal could be sent: the first menu item was always treated as 'Info' and the second as 'Cancel', even if the menu only contained a cancel option. The fix tracks which menu items actually exist and maps the user's selection to the correct result (Info or Cancel).

This commit fixes a build configuration issue for the Trezor T3W1 hardware wallet. The device supports reading a unique serial number, but the build system was not correctly advertising that capability. As a result, the Python module that handles the 'get serial number' command was accidentally excluded from the firmware image, so the feature would not work at runtime. The patch adds the missing capability flag for the T3W1 (emulator and three hardware revisions) and fixes a related list-concatenation bug in the build script that could have caused other feature exclusions to behave incorrectly. There is no direct evidence in the commit of a security vulnerability; it reads as a functionality/availability fix.

This commit simply shortens the on-screen label for a device menu item from 'Regulatory certification' to 'Regulatory' (or translated equivalents) and updates the internal translation key from regulatory_certification__title to regulatory__title. It is a cosmetic UI text change with no security relevance.

This commit adds a user-facing warning message on Trezor devices when the connected computer or phone is slow to respond during a button-confirmation step. It is a usability improvement to prevent users from seeing a confusing blank screen; it does not fix a vulnerability and does not introduce a new attack path.

This commit simply reverts a previous internal renaming of a user-interface text label. It changes the translation key for a Bluetooth 'Waiting for connection...' message from 'words__waiting_for_host' back to 'ble__waiting_for_host' and updates the generated translation files accordingly. There is no security relevance.

This is a visual layout tweak for the Trezor T3W1 hardware wallet. It slightly shrinks the plus/minus buttons on a settings screen so that translated text (like the word "seconds") does not get cut off. There is no indication of a security vulnerability or exploit.

This commit fixes a single spelling mistake in a code comment, changing 'then' to 'than'. It does not change any executable code, behavior, or security properties of the Trezor firmware.

This commit adds a single header include to a battery fuel gauge source file in preparation for supporting different battery types. There is no functional code change, no security fix, and no security-relevant behavior introduced.

This commit updates the Trezor firmware's battery fuel gauge to support a second battery model (HCF343837NCZ) alongside the existing one. It renames constants to avoid naming conflicts, adds a new compile-time selection case, and includes the new battery data header. There is no indication this is a security fix or introduces a security vulnerability.

This commit simply removes an unused header file include from a battery fuel gauge source file. There is no functional code change, no bug fix, and no security relevance visible in the diff.

This commit adds a new data file describing a specific battery model (HCF343837NCZ) used by the device's power/fuel gauge. It contains calibration tables for temperature, voltage, capacity, and internal resistance. There is no code that processes user input, no network activity, no cryptographic operations, and no change to existing logic. It is purely a hardware-support data addition.

This commit changes the bootloader menu on a Trezor hardware wallet so that the 'Pair new device' Bluetooth option is grayed out when Bluetooth Low Energy (BLE) is disabled. It is a UI consistency fix rather than a fix for an exploitable vulnerability. There is no evidence in the commit or supplied references that this resolves a security issue.

This bootloader patch makes the device erase a special protected memory region (backup RAM) when the user enters a 'wipe code' to factory-reset the device. Without this cleanup, sensitive leftovers could remain in that protected memory after a wipe. The change is small and defensive, but the commit message does not explain what specific risk it fixes.

This commit fixes a Bluetooth behavior on the Trezor T3W1 hardware wallet: after a user turns Bluetooth back on, the device now resumes advertising itself so it can be found and reconnected. Previously it might stay silent, causing connection problems. There is no direct evidence this is a security vulnerability rather than a usability bug.

This commit changes the Trezor bootloader so that Bluetooth Low Energy (BLE) settings are remembered across reboots. Previously, the bootloader would turn BLE back on even if the user had turned it off. Now the bootloader reads a saved 'BLE enabled' flag from backup memory and only enables BLE if the user had left it on. The pairing/setup workflows still force BLE on because they need it. This is a privacy/usability fix rather than a critical security patch, but it prevents an unwanted BLE radio from being active when the user expects it to be off.

This commit adds a new GitHub Actions workflow that lets maintainers manually upload English translation source files to the Crowdin translation service. It is a routine CI/infrastructure change with no apparent security relevance.

This commit is a routine code cleanup that renames battery-related constants and arrays in a Trezor firmware header file to include the specific battery model name (JYHPFL333838). No values were changed, no new functionality was added, and there is no indication of any security issue being fixed.

This commit moves a function call (unit_properties_init) so it runs earlier during the startup of a special factory-testing program called prodtest, instead of only when Bluetooth support is enabled. The change is in a low-level embedded file used during hardware production testing, not the normal wallet firmware users run. The commit message says it is a fix but gives no details about any security impact, and no independent security references were provided.

This commit refactors the Trezor firmware's battery fuel-gauge code so it can support multiple battery types in the future. It replaces hard-coded battery model constants with a runtime-selected structure based on a battery_type value read from device OTP memory. There is no obvious security bug in the diff, but the change introduces a new hardware-derived input (battery_type) into power-management calculations. Currently only battery type 0 is handled, and any unknown type falls back to the same default model.

This commit adds a way for the Trezor device to tell the connected computer or phone when its power source changes (for example, when USB is plugged in or a wireless charger is placed nearby). It also exposes two new status flags, usb_connected and wireless_connected, in the device's feature report. There is no direct security fix here; it is a feature that improves real-time status reporting.

This commit adds a new developer/testing tool that creates a fake Bluetooth (BlueZ) interface on a developer's computer. It lets software talk to a Trezor emulator as if the emulator were a real Bluetooth device. It is not a fix for a security issue and does not change any production firmware, wallet, or device code. It is purely a testing/development helper.

This commit is a code cleanup that moves emulator-only UDP socket handling for the Trezor hardware wallet emulator into a shared helper module. It affects only the Unix emulator build, not real Trezor devices. The change does not appear to fix or introduce a security vulnerability; it is a refactoring to reduce duplicated code between USB and BLE emulation layers.

This commit adds a software-only Bluetooth Low Energy (BLE) emulator for Trezor hardware wallets. It is a testing/development feature that lets a desktop emulator simulate BLE connections over local UDP network sockets. It does not change real hardware behavior and is not a security fix or a disclosed vulnerability. The main risk is that any emulator-only code could, in theory, contain bugs that affect testing environments, but there is no direct evidence this introduces an exploitable flaw in production devices.