Trezor firmware

This commit removes two unused Rust import statements (`Insets` and `fonts`) and one unused import group (`text::TextStyle`) from UI source files. It is a routine cleanup triggered by the Clippy linter to eliminate compiler warnings. There is no functional code change and no security relevance.

This is a routine user-interface styling update for the Trezor hardware wallet's newer 'Eckhart' screen layout. It changes how long text (such as cryptocurrency addresses) is broken into chunks and how pagination hints are shown. There is no indication of any security bug or vulnerability being fixed.

This commit adds an automatic page counter hint to a text screen UI component in the Trezor firmware. It is a user-interface feature change, not a security fix or vulnerability. There is no indication it addresses any security issue.

This commit is a routine user-interface layout tweak for the Trezor hardware wallet's Eckhart design. It changes how text is positioned on progress screens (for example, 'Signing transaction...' and 'Please wait') and moves some shared layout constants into a common theme file. There is no security-relevant change here.

This commit removes the on-screen percentage number from loading/progress indicators in the Trezor hardware wallet's user interface. It is a cosmetic UI change only and does not alter security logic, cryptography, or how data is handled.

This commit only rewords user-facing text in the Trezor firmware. It replaces the technical word 'host' with friendlier terms like 'app', 'connected device', or 'connection' across on-screen messages, translations, and test snapshots. There is no change to security logic, permissions, or behavior.

This commit removes Japan from a device menu screen that displays regulatory certification information. It is a routine product compliance change, not a security fix. There are no code changes that affect cryptography, authentication, or how the device protects funds or data.

This is a trivial code cleanup: a single unused import was removed from a Rust source file. It has no functional or security effect on the Trezor firmware.

This commit adds and updates automated user-interface tests for the PIN and wipe-code menus on the Trezor Safe 7 (Eckhart) hardware wallet. It also renames some Spanish translation strings for consistency. There is no change to the firmware's security logic, cryptography, or device behavior—only test code and translations are modified.

This commit is a visual polish fix for the Trezor hardware wallet's newer 'Eckhart' screen layout. It changes how the entered PIN is displayed so the digits are centered and spaced out nicely. There is no security-relevant change here—only the on-screen appearance is adjusted, and the corresponding test snapshots are updated.

This commit changes how the Trezor hardware wallet generates random numbers used to protect PINs, wipe codes, and encrypted storage. It replaces direct calls to a basic random function with a stronger random-number wrapper for sensitive operations, and adds a weaker wrapper for less critical uses. The change suggests the developers want to enforce a stricter random source for security-critical material, but the commit itself does not explain whether the old function was actually weak or exploitable.

This commit adds a build flag that disables a feature called 'tropic' in the legacy Trezor firmware build. On its own, the change is a straightforward build configuration tweak with no visible security bug fix. It may be a defensive hardening step or simply removing an unused feature, but the commit message gives no security context.

This commit adds support for using a second hardware security chip called Tropic to protect the device PIN, alongside the existing Optiga chip. It is a feature addition that strengthens PIN protection by adding another physical barrier against brute-force and chip-level attacks. There is no direct evidence in the commit that it fixes an existing security flaw; it appears to be a defensive hardening change.

This commit refactors how a Trezor hardware wallet establishes a secure communication channel with an optional Tropic cryptographic chip. It removes a 'PRODUCTION-only hotfix' that had been mixing Tropic-sourced randomness into the device's random number generator. It also restructures the pairing-key selection logic so the code tries privileged, then unprivileged, then factory keys in a clearer sequence. The change is described as a feature/refactor with no changelog, not as a security fix. There is no direct evidence in the diff of an exploitable vulnerability, but removing a hotfix and changing secure-channel initialization are security-adjacent changes that warrant review.

This commit changes how many times a device 'stretches' (repeats and strengthens) the user's PIN before checking it. On T3W1 devices, when a build-time flag called STRETCHED_PIN_COUNT is greater than 1, the code now reduces both Optiga hardware stretching and software PBKDF2 stretching to a single iteration. The stated goal is to make PIN verification faster. Reducing stretching weakens the protection against brute-force attacks if an attacker obtains the stored secrets, but the change is conditional on a build flag and does not by itself create a direct remote exploit. It is a security-relevant hardening reduction rather than an obvious vulnerability.

This commit adds an optional text argument to the Trezor production-test firmware's 'ping' command. Previously, 'ping' always replied with just 'OK'. Now, if you type 'ping ABC', the device replies 'OK ABC'. It is a small feature change in a diagnostic/testing tool, not a security fix or vulnerability.

This commit changes how the Trezor hardware wallet displays and clears its PIN-entry keyboard during the boot screen. The title says it 'clears PIN keyboard in bootscreen,' suggesting the previous code may have left PIN-keyboard graphics or state visible when the device went to sleep or resumed. The patch adds a notification channel so the boot screen can be told when a suspend is happening, and it re-creates the lockscreen after suspend instead of continuing straight to PIN entry. There is no direct evidence in the diff of a security vulnerability such as PIN leakage, but a leftover PIN keyboard on screen could theoretically expose partial PIN-entry state or confuse the user interface.

This patch fixes a UI state issue in Trezor hardware wallets. If the device auto-locks while the user is in the middle of typing their PIN, the on-screen PIN keyboard could remain visible even though the device is now locked. The fix detects this situation and clears/restarts the workflow so the keyboard doesn't linger. It is primarily a user-interface consistency bug, but leaving an active PIN entry screen on a locked device could confuse users or create a minor information-leak signal (that a PIN was being entered).

This is a user-interface styling change for the Trezor hardware wallet's action bar. It adjusts how pagination buttons are sized and positioned on the new 'Eckhart' device layout, and updates the corresponding visual test snapshots. There is no indication this affects security, cryptography, or how transactions are approved.

This commit adds a user-facing Bluetooth on/off toggle in the device menu for the Trezor Safe 7 (T3W1). It stores the user's preference and only starts Bluetooth at boot if it was previously enabled. There is no direct evidence of a security vulnerability in the change, but it touches Bluetooth state management and storage, which are security-relevant areas.

This commit changes how a Trezor device handles its initial secure connection (THP handshake) when the device is PIN-locked. Previously, the handshake simply failed if the device was locked. Now, the host can send a new 'try to unlock' flag in the very first handshake message. If that flag is set and the device is locked, the device shows the PIN keyboard so the user can unlock it, and then the handshake continues. If the flag is not set, the device still fails the handshake when locked, preserving the old behavior. The change is described by the vendor as backward-incompatible, meaning companion software (Suite) must be updated to match the new message format.

This is a small user-interface change for the Trezor hardware wallet's homescreen. It removes the battery percentage number (state-of-charge, or 'SoC') from the homescreen and instead shows only a battery icon. The code renames an internal mode from 'OnChargingChangeOrAttach' to 'HomescreenBar' and adjusts how the battery icon is drawn. There is no security-relevant behavior change visible in the diff.

This commit is a purely cosmetic UI fix for the Trezor hardware wallet's new 'Eckhart' layout. It adjusts where the page counter (for example, '1/3') is drawn on screen by giving it its own smaller padding values instead of reusing the larger padding used for instructional text. The change only affects visual spacing; it does not touch cryptography, transaction signing, backup/recovery logic, or any security-sensitive code. The large number of changed test hashes is expected because any screen-pixel change alters the recorded screenshots used for automated UI regression tests.

This commit adds a new optional feature that lets a connected computer ask a Trezor device for its hardware serial number. The device shows the request on its screen and requires the user to tap 'Allow' before sending the number. It is a deliberate product feature, not a hidden backdoor or bug, and only works on models that explicitly support it (currently the T3W1 / Trezor Safe 7 line).

This commit adds a new device message that lets a connected computer ask a Trezor hardware wallet for its unit serial number. The change only defines the message format across several programming languages and build files; it does not include the actual firmware code that reads or returns the serial number. Because the serial number is a low-sensitivity identifier and the real behavior is not shown, the direct security risk is small, but it slightly expands what an untrusted host can learn about the device without user approval.