Trezor firmware

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 is a user-interface polish change for the Trezor hardware wallet's battery indicator. It adds finer battery-level icons (splitting one 'mid' icon into 'mid-plus' and 'mid-minus') and adjusts the percentage thresholds at which each icon appears. It also includes automated tests to verify the new thresholds. There is no security-relevant change here.

This commit fixes a bug in how the Trezor hardware wallet disables Bluetooth (BLE). Previously, when BLE was turned off, the function returned early and never updated the internal 'enabled' state flag. That could leave the system believing BLE is still on, potentially causing unexpected behavior, power drain, or confusion about whether the wireless radio is active. The fix removes the early return so the state flag is always set correctly.

This commit fixes a visual text-rendering bug in the Trezor hardware wallet's user interface. Specifically, when long cryptocurrency addresses are split into small chunks for easier reading, the last chunk on a screen line was sometimes displayed incorrectly or with a missing '...' ellipsis. The fix changes how the layout code decides when a chunk is the final one and how much space to reserve for the trailing ellipsis. There is no evidence this bug could be exploited to steal funds, bypass security, or alter transaction data.

This commit adds a new Python command and library function that lets a user ask a Trezor device for its hardware serial number. The device already had a way to provide this number; the change only exposes it through the PC-side tools and adds tests. There is no obvious security bug in the code shown, though making serial numbers easier to read could slightly help someone track or fingerprint a specific device.

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.

This commit simply deletes an unused Python helper function from a Trezor hardware wallet UI layout file. The function was not being called anywhere, and removing it does not change any runtime behavior or introduce any security risk.

This commit is almost entirely a test-suite expansion for the Trezor Safe 7 device menu. It adds automated click tests for settings like auto-lock, device label, LED, haptic feedback, brightness, backup checks, notifications, menu traversal, and device wipe. A small amount of production code changed: a new 'led' field was added to the Features protobuf message so the device can report RGB LED support, and a few UI debug-trace strings were improved to make automated testing easier. There is no obvious security vulnerability in the diff.

This commit simply exposes a new device setting in the information message the hardware wallet reports to connected computers. It adds a field called auto_lock_delay_battery_ms to the Features message across the protocol definition and generated code for Python, Rust, and the device firmware. There is no change to security logic, no bug fix, and no behavior change beyond reporting the value.

This commit replaces two pre-compiled binary files used for Bluetooth Low Energy (BLE) testing on the Trezor T3W1 hardware model. The change is described as a routine update to test binaries, with no source code changes and no changelog entry. There is no information in the commit or supplied references indicating a security fix or vulnerability.

This commit removes a 'virtual lock button' from the Trezor hardware wallet's home screen on the Eckhart layout. Previously, holding a finger anywhere on the home screen (except the bottom action bar) for a set duration could lock the device. Now that gesture is gone. The change is described as a feature tweak, not a security fix, and no security relevance is disclosed in the commit or supplied references.

This commit is a code cleanup and hardware-support refactor. It splits the touch-screen driver for the FT3168 controller out of the older FT6x36 driver, updates the T3W1 device build files to use the new driver, and removes an unused wake-up workaround. There is no obvious security vulnerability introduced, but any driver refactor carries a small risk of functional regressions in touch handling on the T3W1 hardware.

This commit only increases version numbers across Trezor firmware components and translation files. There are no code changes that fix or introduce any security behavior, so it has no direct security relevance on its own.

This commit adds a new software switch that lets the device turn its Bluetooth Low Energy (BLE) radio on or off from the driver level. It is a feature addition, not a fix for an existing bug. The change introduces guards so that when BLE is disabled, the driver refuses to process incoming BLE data, send data, enter pairing, or switch the radio on. There is no evidence in the commit that this is a security patch or that it addresses a known vulnerability.

This commit only reformats and expands the documentation comments in a single Bluetooth header file. No actual code logic, function behavior, or security properties changed.

This commit is a code cleanup that rewrites how the Trezor firmware talks to its Bluetooth chip. Instead of sending one big generic 'command' packet that could describe many different actions, the code now uses a separate, specific function for each Bluetooth action (such as turn on, pair, disconnect, erase bonds). The change also tightens the security boundary between the app and the kernel by validating the pairing name and pairing code directly, rather than trusting a caller-built command structure. There is no direct evidence in the commit that this fixes an active security bug, but the old design made it easier for a caller to request unintended operations by crafting command data, and the new design removes that entire class of mistakes.

This is a small bug-fix change in the Trezor Python command-line tools. It fixes a situation where the tool would keep using an old cached connection to the device while waiting for the device to reboot into bootloader mode. Now it clears that cached connection and tries to reconnect. There is no direct evidence this is a security vulnerability; it appears to be a reliability/usability fix for firmware updates.

This commit adds a new internal interface that lets trusted and less-trusted software running on the Trezor device read the device's serial number. The code checks that the caller is allowed to write to the memory it provides, then copies the serial number there. There is no direct evidence in the commit that this is a security fix or that it introduces a vulnerability; it appears to be a feature exposing information that was already available elsewhere in firmware.

This commit adds a one-time 'rework' feature to the Trezor production-test tool, allowing a factory worker to overwrite a device's variant (color, Bitcoin-only flag, packaging) if it was originally written incorrectly. The change is intended for manufacturing repair, not normal user operation. It does not appear to be a security patch; it is a production-process feature.

This commit only rewrites code comments in a header file to use a more formal documentation style. No actual program logic, function behavior, or security checks were changed. It is not a security fix and does not introduce any security issue.

This is a simple code cleanup change that renames a function from get_device_sn to unit_properties_get_sn across four files. It does not change what the function does, how it is called, or any security behavior. It is not a security fix.

This commit updates the production-test configuration for a Trezor hardware model (T3W1 revC) to use a newer revision of an external secure-element firmware file and a matching compile-time identifier. It is a build-configuration change, not a patch to cryptographic or wallet code. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a routine hardware bring-up or compatibility update.

This commit adds a visual LED effect and a short 'finalized' animation to the hold-to-confirm action on Trezor's newer Eckhart-style user interface. It changes when the device reports a confirmation: instead of confirming the instant the user releases the button, the device now waits for a brief 500 ms animation to finish. During that animation it ignores further button input and lights the RGB LED in a color matching the on-screen confirmation. There is no indication this fixes a security bug; it appears to be a user-experience and visual-feedback feature.

This commit adds a new device state flag so the Trezor hardware wallet can tell a connected computer: 'this session replaced an existing channel, so the user does not need to confirm again.' The host-side library is updated to recognize the new state. It is a feature change, not an obvious vulnerability fix, but it touches the authentication/authorization boundary between device and host.