Trezor firmware

This commit is a purely cosmetic UI tweak for the Trezor hardware wallet. It increases the top padding of the home screen label from a theme-defined value to a fixed 38 pixels. There is no security relevance in the change itself.

This is a cosmetic UI alignment change for the Trezor hardware wallet. It makes the default device name shown on the homescreen and in the device menu consistent by using the model's full name (e.g., 'Trezor Safe 5') instead of a hardcoded 'Trezor' fallback. It also tweaks text styling and reorders a translation entry. There is no security-relevant change.

This commit rewrites the on-screen keyboard used to type text into the Trezor Safe 5 (Eckhart layout). It renames the component, removes a separate confirmation screen for empty labels, lets users submit an empty string directly, and allows cancelling even when nothing has been typed. The change is described as a UI/UX cleanup, not a security fix. There is no direct evidence in the commit that it patches an exploitable vulnerability, but removing an extra confirmation step for empty device names slightly changes the safety surface around user input.

This is a minor user-interface cleanup for the Trezor hardware wallet. It changes how a device label is shown on screen so the label text is no longer visually highlighted as a special parameter. There is no security issue or vulnerability here.

This commit is a routine user-interface polish change for the PIN entry screen on Trezor hardware wallets. It renames an internal parameter from 'subprompt' to 'attempts', adds a new flag so the screen can visually highlight the final PIN attempt, and fixes text alignment and spacing. There is no indication this change fixes a security vulnerability or introduces one.

This commit fixes visual layout glitches in the passphrase entry screen on a specific Trezor device model (Eckhart). It adjusts prompt spacing, text alignment, and the placement of the last typed character. There is no indication this changes security behavior or introduces a vulnerability.

This commit is a cosmetic user-interface fix for the Trezor hardware wallet's new 'Eckhart' layout. It adjusts how recovery seed words are displayed on screen—text alignment, prompt placement, and spacing—without changing any security logic, cryptography, or how secrets are handled.

This commit changes how the Trezor hardware wallet's Bluetooth Low Energy (BLE) connection behaves when the device reboots from the bootloader into the main firmware. Previously, the bootloader would shut down BLE entirely during this handoff, forcing the user to reconnect. Now it tries to keep the existing BLE connection alive across the reboot. This is a user-experience and availability fix rather than a security patch, but it slightly alters the attack surface during a sensitive transition.

This commit wires up the on-device settings menu for a new Trezor hardware-wallet UI (the 'Eckhart' layout). It adds menu entries that let the user change or remove their PIN and wipe code, set auto-lock delay, and check their backup. The change is mostly UI plumbing: it connects existing security-management code to new menu items and adds translated labels. There is no obvious security bug in the diff, but it is a partial implementation (other TODOs remain) and the code now exposes sensitive actions through a new menu surface.

This commit adds a Bluetooth on/off menu item to the device settings screen for the upcoming Trezor Safe 7 (Eckhart layout). It is purely a user-interface change: it shows a label and a confirmation prompt, but the actual Bluetooth enable/disable logic is left as a TODO and does nothing. There is no security fix or security-relevant behavior change.

This commit is a routine UI update for the Trezor hardware wallet's device menu. It wires up previously placeholder settings (screen brightness, haptic feedback) and adds a 'Wipe device' option to the menu. There is no security fix or vulnerability visible in the change.

This commit adds new notification entries and warning styles to the device menu on the Trezor hardware wallet. It is a routine user-interface feature patch: it introduces a 'PIN not set' reminder, changes the visual style of a failed-backup warning, and wires the failed-backup menu item to a device-wipe confirmation prompt. There is no evidence of a security vulnerability being fixed.

This commit changes how the Trezor device handles multiple encrypted USB-like communication channels. It lets a new channel on the same connection take over if an existing channel appears stuck for more than one second. The change is described as a feature, not a security fix, and there is no disclosed vulnerability or incident tied to it.

This is a small internal code cleanup in Trezor firmware's message handling loop. It removes an optional 'no message' path and restructures exception handling so the loop continues cleanly after unexpected messages. There is no indication this fixes or introduces a security vulnerability.

This commit simply adds a new firmware version number (2.9.1) to a list of released versions for several Trezor hardware wallet models. It is a routine metadata update with no code changes and no security relevance visible in the diff.

This commit simply updates a timestamp that tells the Trezor device how new its built-in Ethereum network/token list must be. It is a routine data-version bump with no code logic changes and no security relevance visible in the commit.

This commit is purely a documentation update: it compiles the changelog for Trezor firmware version 2.9.1 by deleting individual changelog fragments and adding the final release notes to several CHANGELOG files. No source code, firmware logic, or security behavior is changed.

This commit removes a 'Skip backup' menu option that had accidentally been left on a screen shown during the wallet backup process on the Trezor Safe 5 (Eckhart layout). The change prevents a user from bypassing the backup verification quiz, but it is a UI-only fix and does not by itself create or fix a security vulnerability in the cryptographic backup process.

This commit fixes a bootloader wireless setup workflow so it checks whether Bluetooth pairing actually started before continuing. Previously, the code ignored the return value of the pairing-start function, so if pairing failed to initiate, the setup would proceed anyway. The fix makes the workflow return a pairing-failed status instead. This is a defensive hardening change in the bootloader's BLE pairing path.

This commit removes leftover debug print statements from a Trezor hardware wallet pairing function. The prints could have exposed sensitive cryptographic material (a shared secret and authentication tag) during development or testing, but they were clearly marked as temporary test code and are now removed. There is no evidence this code ever shipped to production firmware.

This commit refactors error handling in the Trezor Python client library and command-line tool. It removes some custom exception types and moves error printing into a shared helper. The changes appear to be a cleanup following an earlier pull request, not a fix for an active security vulnerability. There is no indication in the commit that this addresses a security issue.

This is a straightforward internal code cleanup in Trezor's Python library. It replaces two separate flags that tracked whether a device was paired with a single simpler flag, and adds extra debug logging. There is no indication this fixes or introduces a security vulnerability.

This change fixes a bug in the Trezor hardware wallet's THP (Trezor Host Protocol) communication layer. Previously, if the device was trying to resend a message but the USB host stopped accepting data (for example due to USB flow control), the retransmission loop could get stuck forever, blocking other THP channels. The patch adds a 5-second timeout so the loop can break out and let other communication channels proceed. It is a reliability/availability fix rather than a clear-cut vulnerability patch, though the stuck-loop condition could be abused to deny service to other channels.

This commit only adds a missing period to two changelog entries describing a new Cardano feature. There are no code changes and no security relevance.

This commit only adds or updates translated text strings for the Cardano cryptocurrency feature. It replaces hard-coded English labels like 'Confirm message' and 'Message text' with references to the device's translation system, and updates the translation files, generated code, and a test marker. There is no change to security logic, cryptography, or how user approvals work.