Trezor firmware

This commit adds a new 'battery state of charge' (SoC) field to the device's Features message, which is the information a Trezor reports about itself when asked. It is a straightforward feature addition: the bootloader now reads the battery level from the power manager and includes it in the device description sent to connected computers and phones. There is no indication this change fixes or introduces a security vulnerability.

This commit is a routine build-system change for the Trezor hardware wallet firmware. It prepares the build scripts to include either a development or production Bluetooth (nRF) chip binary depending on whether a development bootloader is being used. No security vulnerability is visible in the code change itself.

This commit adds a numeric model identifier for a specific Trezor hardware board (the T3W1 revision A with Nordic nRF52832 chip) into the firmware signing process as a protected custom TLV field. It is a feature addition that embeds device-model metadata into signed firmware images. There is no indication in the commit that it fixes a security bug or introduces a vulnerability.

This is a routine dependency update for the Nordic chip bootloader component (MCUboot) used in Trezor hardware wallets. The commit only changes one line: it points the build system to a newer commit hash of Trezor's fork of MCUboot. There is no description of any security issue, bug fix, or functional change in the commit message or diff. Without additional information about what changed between the two MCUboot revisions, this single-line manifest update by itself does not demonstrate any security problem.

This commit tidies up debug-related settings in the Nordic chip configuration files for a Trezor hardware wallet variant. It removes Segger RTT debug output and the UART console from the main board default configuration, while explicitly adding a console setting to several dedicated debug-only configuration files. The change appears to be a cleanup to keep debug features out of production board defaults and ensure debug builds still enable the console. There is no direct evidence in the commit that this fixes an active security vulnerability.

This commit widens the preferred Bluetooth Low Energy connection interval range on Trezor's Nordic BLE firmware so that Apple/macOS devices will accept the request instead of ignoring it. It is a compatibility/bug fix rather than a security patch. There is no direct evidence in the commit or supplied references that this change addresses a security vulnerability.

This commit only updates the setup instructions in a README file. It tells users to initialize Git submodules before installing the trezorctl command-line tool. There is no code change and no security issue.

This commit fixes a user-interface timing issue in the Trezor bootloader. Previously, the firmware-installation progress bar could start moving before the user had actually confirmed the update on the device screen. The change makes the progress bar wait until the user explicitly confirms, so the on-screen feedback matches the real installation state. There is no direct evidence this is a security vulnerability, but it removes a small window where UI state could be misleading during a firmware update.

This commit is a routine version bump from 2.9.1 to 2.9.2 for the Trezor firmware. It only changes version numbers in one header file and in translation metadata, plus updates the signed translation package timestamp and hash. There are no code behavior changes, no bug fixes, and no security-related changes visible in the diff.

This commit tweaks how quickly a menu scrolls when the user swipes the touchscreen on a Trezor hardware wallet model, and adds a request to redraw the screen during scrolling. It is a user-interface polish change with no apparent security relevance.

This commit adds four pre-signed binary files called 'vendor headers' for a new Trezor hardware model (T3W1). These files are part of the device's firmware build and boot trust chain, but the commit itself only adds already-signed binaries. There is no code change, no evidence of a vulnerability, and no indication these files are malicious or improperly signed.

This commit removes placeholder/mock Bluetooth device names from the Trezor hardware wallet's on-device menu and makes the 'currently connected' indicator reflect the real Bluetooth state. It is a cleanup of fake test data, not a security fix in the usual sense, though leaving mock data in production could mislead users about which devices are paired.

This commit simply lowers the default screen brightness for the T3W1 hardware model of the Trezor hardware wallet from 150 to 85. It is a product tuning change, not a security fix or vulnerability. The change affects bootloader, production test, and UI theme code, and updates expected test screenshots (UI fixtures) accordingly.

This commit tunes the Bluetooth Low Energy settings on Trezor's Nordic BLE firmware. It asks for a faster connection interval, switches to the 2 Mbps physical layer, and adds suspend/resume functions that slow the connection when the device is idle. There is no direct security bug visible in the diff, but changing connection parameters can affect power, stability, and the attack surface for Bluetooth side-channel or denial-of-service attacks.

This commit is a routine user-interface change for the Trezor hardware wallet. It adds a small connection-status icon and a new 'Disconnected' label to buttons that represent Bluetooth Low Energy (BLE) paired devices. There is no security-relevant behavior change in the code.

This commit adds a new optional subtitle label to a vertical menu screen in the Trezor hardware wallet's user interface. It is a routine UI feature change with no apparent security relevance.

This commit is a routine UI code cleanup for the Trezor hardware wallet's on-screen menu. It splits one type of menu screen into two separate types—one for general submenus and one specifically for device-related options—so the code can use a shorter menu for device screens. There is no security fix or vulnerability here; it is purely a maintainability and layout refinement.

This commit updates the on-screen device menu for a new Trezor hardware wallet design (codename Eckhart). It adds Bluetooth pairing controls such as 'Connect', 'Forget', and 'Forget all', and wires some of those buttons to existing unpair/disconnect routines. The changes are almost entirely user-interface code; there is no obvious security bug, but several TODO comments show the underlying Bluetooth actions are still incomplete or mocked.

This commit is a straightforward feature addition: it exposes the Bluetooth Low Energy (BLE) address of the currently connected host (e.g., a phone or computer) to the Trezor device's application code. It does not change security policies, add authentication bypasses, or fix any vulnerability. It simply makes an already-recorded internal address available through a new API function.

This change makes the Trezor Bluetooth layer disconnect an active Bluetooth connection before erasing a paired-device bond. Without the disconnect, the device could remain connected to a host whose pairing keys have just been deleted, which may allow the host to keep interacting with the wallet after the user thought access was revoked.

This bootloader patch changes the order of operations during a factory reset (wipe). Previously, the device tried to delete Bluetooth pairing information ('bonds') before telling the host computer that the wipe succeeded. Deleting bonds can disconnect the device, so the success message might never reach the host, leaving the user or software unsure whether the wipe completed. The fix sends the success message first, then waits briefly, then deletes the bonds. This is primarily a reliability/UX fix; it does not appear to be a security vulnerability in the sense of theft or unauthorized access.

This commit removes the ability for Trezor's Bluetooth Low Energy (BLE) feature to maintain multiple simultaneous connections. It changes the firmware so the device only allows one BLE connection at a time, and wraps the old multi-connection logic in a compile-time flag that is no longer enabled. The change is described as a feature removal, not a security fix, and no security relevance is disclosed.

This commit increases the Bluetooth Low Energy (BLE) radio transmit power on Trezor's Nordic-based BLE firmware from a lower default level to +4 dBm. This is a one-line configuration change. It is not a code vulnerability in the traditional sense, but it marginally increases the physical range at which a nearby attacker could detect or attempt to interact with the device's BLE signal. The commit itself does not describe any security relevance and no security incident or advisory is supplied.

This commit is a feature addition, not a security fix. It changes how the Trezor hardware wallet's Bluetooth Low Energy (BLE) advertising data is structured so that a new flag can be broadcast when the user intentionally disconnected. This lets a paired computer or phone know not to automatically reconnect. There is no indication in the commit or supplied references that this resolves a vulnerability or security issue.

This commit adds a new diagnostic command, 'ble-get-bonds', to Trezor's internal production-test firmware. It lets a factory technician read the list of Bluetooth devices previously paired with the device. The change is purely a feature addition for manufacturing/diagnostics; it does not, by itself, bypass pairing, steal funds, or change security settings. The main concern is that it exposes paired-device addresses (MAC addresses) through the production-test command-line interface, which could be a minor information-leak if the prodtest interface is accessible in the field.