Trezor firmware

This commit fixes how the Trezor hardware wallet reports battery-related warning flags to its internal telemetry system. Previously, the code reported the current state of several battery conditions on every check (for example, 'battery not connected right now'). After the fix, it only reports when the condition actually changes or is newly detected. This is a correctness bug in telemetry logging, not a vulnerability that could let an attacker steal funds or control the device.

This commit adds two new factory-test commands to Trezor's production-test firmware: one that reads battery telemetry (temperature extremes, error flags, cycle count) and one that resets that telemetry. The reset command is blocked on real production hardware unless the device is in manufacturing mode, but it is a no-op in the emulator. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a feature addition for production testing.

This commit fixes a bug in the Trezor hardware wallet where Bluetooth (BLE) communication could get stuck in a 'busy' state after a device restart if BLE was turned off. The fix moves the start of BLE communication outside the 'if BLE is enabled' block, so the BLE subsystem is always initialized even when the user has disabled Bluetooth. The changelog describes this as fixing a 'Connected Trezor is used by another application' bug. There is no direct evidence in the commit that this is a security vulnerability; it appears to be a usability/functional bug fix.

This is a one-line test-reporting fix that adds the bracketed IPv6 form '[::1]' to a list of local hostnames. It only affects an internal UI test tool's button-disabling logic and has no security relevance.

This is a routine automated dependency update by Dependabot. It bumps the urllib3 library used inside a non-production battery-testing tool from version 2.5.0 to 2.6.3. There is no indication in the commit that this fixes a security issue, and the changed file is not part of the Trezor firmware that runs on devices or handles cryptocurrency.

This is a routine dependency update generated by Dependabot. It upgrades the Python imaging library Pillow from version 11.3.0 to 12.1.1 inside a small internal tool used for battery testing. The change is a single line in a requirements file. There is no direct evidence in the commit that this fixes a specific security vulnerability, and the tool is not part of the Trezor firmware that runs on the hardware wallet itself.

This commit only updates the GitHub pull request template, which is a documentation/process file. It contains no firmware code changes and no security-relevant modifications.

This commit improves how Trezor devices display Tron token approval transactions on screen. Previously, only simple transfers were shown clearly; now the device also clearly shows when a user is approving someone else to spend their tokens, including unlimited approvals and revocations. This is a security-hardening change that helps users avoid accidentally signing risky approvals.

This commit adds support for a new Tron blockchain operation called FreezeBalanceV2, which lets users stake TRX tokens to gain Energy or Bandwidth. The change is a feature addition: it adds the contract type to the list of supported transactions, shows the user a confirmation screen with the staking amount and resource type, and handles a protocol quirk where the default resource value must be omitted when serializing the transaction. There is no direct evidence in the commit of a security vulnerability, but any new signing path deserves careful review.

This commit adds support for a new Tron blockchain operation called FreezeBalanceV2, which lets users stake TRX tokens to gain Energy or Bandwidth. The change only updates message definitions, generated code, test fixtures, and translation strings. There is no actual signing or user-interface logic in this commit, and nothing in the diff suggests a security vulnerability.

This commit refactors how the Trezor hardware wallet's graphics chip (DMA2D) waits for image-copying operations to finish. Previously the CPU burned power in a tight loop; now it puts the CPU to sleep and wakes it when the transfer completes. The change introduces new state tracking and error handling, but it also manipulates low-level CPU sleep/interrupt settings and manually clears locks and flags. There is no claim in the commit that this fixes a security bug, and no external advisory is provided. The main concern is whether the new wait logic could, in rare timing situations, leave the driver in an inconsistent state that affects screen rendering or stability, rather than a direct exploit path.

This commit is a small internal cleanup in the Trezor hardware wallet's graphics driver for STM32 microcontrollers. It removes some conditional compilation guards around DMA2D (a graphics accelerator) reset/clock code and deletes one redundant wait call before a copy operation. There is no claim in the commit that this fixes a security bug, and the changes do not obviously create or fix a vulnerability on their own.

This commit adds a new secure-monotonic version counter (SECMON_MONOTONIC_VERSION) to the Trezor Model Safe 3 (D002) hardware wallet's secret storage layout. Monotonic counters are used to prevent rollback attacks, where an attacker tries to downgrade the device to older, vulnerable firmware or bootloader. The change itself is a defensive hardening patch, not an exploitable vulnerability. However, because the commit is marked [no changelog] and provides minimal context, we cannot fully assess whether it fixes an incomplete earlier implementation or responds to a known security issue.

This commit adds new UI helper functions across four Trezor device themes to let users confirm long pieces of data (like transaction details or messages) in chunks, showing a prefix of bytes and asking whether to continue or confirm all at once. It is a user-interface feature, not a fix for a known security bug. There is no direct evidence in the commit or supplied references that it addresses a vulnerability.

This is a small user-interface cleanup for the Trezor hardware wallet. On one device style (Bolt), it hides an extra 'info' button when there is no label text for it, so users don't see a confusing blank button. The change also adjusts internal Rust return types so the different device layouts can return the same kind of object. There is no direct security fix here.

This is a small user-interface feature patch that adds support for displaying an optional subtitle in a Trezor hardware wallet screen flow. It does not change security logic, cryptography, memory handling, or user confirmation behavior. There is no indication this commit fixes or introduces a security issue.

This is a one-line visual styling fix in the Trezor hardware wallet's user interface. It changes which font style is used when displaying data values in a specific confirmation screen (confirm_with_info) on the Delizia layout. The old style was the general monospace font; the new style is a monospace font variant intended specifically for data. There is no direct evidence this change fixes a security vulnerability, but using the wrong font style could theoretically make important data harder to read or distinguish from labels, slightly weakening the user's ability to verify what they are approving.

This is a minor user-interface polish change for the Trezor hardware wallet's 'Caesar' screen layout. It simply hides an empty or placeholder 'info' button so users don't see a blank or confusing button during confirmations. There is no security-relevant behavior change.

This commit fixes a bug in the Trezor firmware's code that reads BIP32 extended keys (the xpub/xprv strings used by wallets). Previously, if the function encountered an invalid key string, it returned an error immediately without wiping a temporary 78-byte buffer that held decoded key material. That leftover data could remain on the device stack and potentially leak small pieces of secret key information to later code. The fix ensures the buffer is always cleared before the function returns, even on error paths.

This commit updates two GitHub Actions workflow files that manage translation files with Crowdin. It bumps the versions of some reusable actions (checkout, create GitHub app token, create pull request), adds input fields so the workflow caller can choose who is assigned and who reviews the resulting pull request, and reorders a couple of lines. There is no change to the Trezor firmware code that runs on the device, no change to cryptographic handling, and no indication of a security fix or vulnerability.

This commit changes only test-reporting helper code used to generate HTML pages and animated GIFs for UI test results. It preloads the first screenshot so the displayed image does not visibly jump when the page loads. There is no change to the Trezor firmware, wallet logic, cryptography, or any code that runs on the device.

This commit disables an 'update' button in a test report web page when the page is not loaded from the user's own computer (localhost). The change is a hardening measure to prevent someone from accidentally or maliciously triggering test-result updates from a publicly hosted copy of the report. It is not a fix for a known exploit in shipped Trezor firmware.

This commit adds keyboard shortcuts to a Trezor internal test-reporting web page used by developers during UI testing. It lets reviewers press 'a', 's', or 'd' to mark a test result as OK, OK & UPDATE, or BAD, and improves the visual styling of the buttons. There is no security relevance: the tool is not shipped to end users, does not handle secrets, and does not change device firmware or wallet behavior.

This commit fixes a display clock configuration for three Trezor hardware screen variants. The clock divider value was hard-coded to 62, but the formula shows it should be calculated from the external crystal frequency. On the DISC2 board the crystal runs at a different speed, so the hard-coded value produced the wrong DSI display clock. This is a hardware initialization bug that could cause display corruption or failure to light up the screen on DISC2; it is not a software vulnerability that an attacker can exploit.

This commit only adds explanatory comments to two generated/mocked source files describing the history and future plans for two internal type aliases (`PropertyType` and `StrPropertyType`). No code behavior changes, no bug fixes, and no security-related modifications are present.