Trezor firmware

This commit changes the Trezor firmware's embedded MicroPython configuration so that detailed error tracebacks are no longer stored in optimized (PYOPT=1) builds. The stated goal is to avoid allocating traceback data in release builds, which can save memory and reduce information exposure if an error occurs. There is no direct evidence in the commit that this fixes an active security vulnerability, but it is a defensive hardening measure.

This commit fixes a bug in the Trezor hardware wallet's Bluetooth handling. When the device went to sleep and woke back up, two internal flags that control whether Bluetooth advertising should restart were not saved and restored. As a result, after suspend/resume the device might not resume broadcasting its Bluetooth signal correctly, which could break wireless pairing/reconnection. The patch simply saves and restores those two flags across sleep/wake cycles.

This bootloader patch makes the device explicitly turn off its Bluetooth Low Energy (BLE) radio when the hardware receives a power-off command. Without this fix, the BLE chip might stay on during shutdown, which could waste battery, cause unexpected radio behavior, or keep the device discoverable longer than intended. The change is defensive and improves shutdown hygiene rather than fixing an obvious remote attack.

This commit fixes a timing issue during startup of the Trezor hardware wallet's Bluetooth (BLE) subsystem. Previously, the firmware might decide whether to start broadcasting Bluetooth advertisements before the wireless chip (nRF) had finished booting. The fix adds a new check that waits up to 5 seconds for the BLE subsystem to report it is fully started before making that decision. If the subsystem is not ready, the device may skip advertising for bonded peers. This is a defensive fix that could prevent Bluetooth pairing/connectivity problems or unexpected behavior at boot, but the commit itself does not describe a security vulnerability.

This commit only updates expected screenshot fingerprints (hashes) in a test fixture file. It does not change any actual device code, cryptographic logic, or user-facing behavior. It is a test-maintenance follow-up with no security relevance.

This commit only re-enables an existing automated test for the T3W1 hardware model and records the expected screen snapshots for that test. It does not change any firmware code that runs on the device, so it cannot introduce a security vulnerability or fix one.

This change lets non-production firmware builds accept translation files signed with development keys, not just official production keys. It is meant to help QA test translations on unsigned builds. Production builds still require official signatures, so an end-user running official firmware is not directly affected. The main risk is that a misconfigured build could accidentally ship with the relaxed setting enabled.

This commit only adds a new Python library called 'bleak' to the project's dependency list and lock file. Bleak is a popular, legitimate library used for Bluetooth Low Energy communication. There is no actual code change, no vulnerability fix, and no indication of malicious intent in the commit itself. It is a routine build/dependency update.

This commit changes the Trezor Python library so that Bluetooth Low Energy (BLE) device support is only enabled when the user explicitly sets an environment variable or passes a command-line flag. Previously, BLE transport was always included in device discovery. The change is a defensive hardening measure, not a fix for a known exploit.

This commit adds Bluetooth Low Energy (BLE) support to the Trezor Python library so it can discover and connect to Trezor hardware wallets over Bluetooth. It is a feature addition, not a security fix. The new code runs BLE operations in a separate process and communicates with it through a pipe. There are no obvious severe vulnerabilities in the diff, but the code introduces new attack surface: it trusts nearby BLE devices advertising a specific service UUID, performs Bluetooth pairing, and forwards raw USB-like protocol chunks over BLE. Because this is brand-new code, its security posture is unproven and partial (for example, chunk-size validation is only logged, not enforced).

This commit refreshes the on-device settings menu for the Trezor Safe 7 (Eckhart layout). It lets the menu restart on a specific submenu after actions like disconnecting a Bluetooth device or toggling haptics/LED, and removes the confirmation prompt for some toggle buttons. The changes are almost entirely user-interface plumbing; there is no obvious security bug, but the new loop and direct hardware calls deserve a quick sanity check.

This commit is a routine internal code cleanup for the Trezor firmware's on-device menu screen. It changes some internal number types from usize to u8, adds helper functions for building menu items, and makes the code more readable. There is no indication of a security fix or vulnerability being addressed.

This commit replaces hard-coded English text strings in the Bluetooth pairing user interface with references to the device's translation system. It does not change what the device does, only how the text is loaded, so it can be translated into other languages later. There is no security bug being fixed here.

This change simply turns the device's LED red while the user is confirming a factory wipe, then turns it off afterward. It is a user-experience/visual indicator change in the bootloader and does not alter security logic, data handling, or access controls.

This commit adds colored LED lighting effects during the Bluetooth pairing process in the Trezor bootloader. It is purely a user-interface change to give visual feedback when the device is in pairing mode. There is no indication it fixes or introduces any security vulnerability.

This commit adds a new function that lets the firmware ask the RGB LED driver what lighting effect is currently running (for example, pairing or charging). It also adds a special 'none' value returned when no effect is active and tightens a bounds check so invalid negative effect IDs are rejected. There is no security-relevant change here; it is a straightforward feature addition.

This is a tiny code cleanup in Trezor's firmware emulator for Unix. It renames one internal function and adds a stub function that always reports 'no LED effect active.' It does not change behavior on real Trezor hardware and does not fix or introduce any security issue.

This commit changes the visual pattern of the RGB LED charging indicator on Trezor hardware wallets. It swaps the order of the charging animation phases so the LED stays off for the first 800 milliseconds, then fades to yellow, holds yellow, fades off, and repeats. There is no security-relevant change here—only the timing and visual appearance of a status light.

This commit changes the Trezor bootloader's hibernation charging indicator from a solid blue LED to a pulsing 'charging' LED effect. There is no security-relevant change visible in the diff. It is a user-experience/visual feature.

This commit replaces hard-coded English text in Trezor's on-screen pairing and connection prompts with proper translation keys. The visible messages stay the same in English, but the firmware can now display them in other languages. There is no security bug being fixed here; it is a routine internationalization cleanup.

This commit adds a small cache that remembers recently paired Bluetooth-like device names and MAC addresses for Trezor's experimental Trezor Host Protocol (THP). It only stores entries whose MAC address is already bonded in the device's secure BLE storage. The change is purely additive and gated behind the USE_THP build flag. There is no direct evidence in the commit of a security vulnerability; it appears to be a feature implementation with a filtering safeguard.

This commit is a user-experience improvement for Trezor hardware wallets that connect over Bluetooth. It makes the device menu show a friendly computer name (like "Alice's MacBook") instead of a raw Bluetooth MAC address for recently paired devices. The change also stores that friendly name in device flash memory the first time pairing happens. There is no direct security bug visible in the diff, but it slightly increases the amount of untrusted data (the host name supplied by the connecting computer) that is saved and later displayed on the device screen.

This commit adds a safety check that ensures two specific hardware features (THP and BLE) are enabled before a device menu function can run on the T3W1 hardware model. It is a defensive assertion to prevent the menu from operating in an unsupported configuration, not a fix for an active security vulnerability.

This commit only adds new data structure definitions (protobuf messages) for a future feature that will cache recently paired host names and MAC addresses in Trezor's Trusted Host Protocol (THP). It does not change any runtime logic, parsing behavior, or security checks. There is no indication of a vulnerability or security fix.

This commit is a user-interface feature change for the Trezor hardware wallet's Eckhart design. It replaces a static text truncation behavior with a scrolling marquee animation for long subtext labels in menu items. There is no security-relevant change visible in the code.