Trezor firmware

This is a small internal code cleanup in the Trezor firmware's user-interface code. It changes how a scrolling text effect (marquee) clips its drawing to the screen, removing a manual vertical offset workaround. There is no indication this change fixes a security vulnerability or affects device security.

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.

This commit adds a new helper function that shortens text strings so they do not exceed a specified byte size. It is a routine feature addition with no obvious security bug, and there is no disclosed security issue tied to it.

This commit simply updates a Python helper library called 'munch' from version 2.x to version 4.x in the project's dependency files. The stated reason is to remove a harmless user warning. There is no indication this change fixes or introduces a security problem.

This commit fixes a bookkeeping bug in the Bluetooth pairing code of Trezor hardware wallets. The device now correctly increments its count of bonded peers immediately when it receives confirmation that pairing completed. Previously, the count may have been updated late or missed, which could cause the wallet to incorrectly think it had no bonded Bluetooth devices or to allow more pairings than intended. The change is small and defensive, but the exact security consequences depend on how the stale count was used elsewhere in the firmware.

This commit increases a timeout in the Trezor bootloader from 100 to 300 ticks while wiping Bluetooth pairing information ('bonds'). A too-short timeout could cause the wipe operation to fail or behave inconsistently if the Bluetooth chip takes longer to respond. The change is a hardening fix, not a clear-cut vulnerability patch, and the commit message does not describe any security impact.

This commit removes a special 'suspended charging' mode from the Trezor hardware wallet's power manager. Previously, if the device was suspended while plugged into USB or wireless power, it would wake up periodically to update the battery fuel gauge using actual charging current. Now it always uses a fixed self-discharge estimate instead. This is a feature simplification, not a clear security fix. It could make the displayed battery percentage slightly less accurate when charging while suspended, but there is no direct evidence it creates a security vulnerability.

This commit changes how the Trezor hardware wallet's RGB LED behaves when the device is suspended while charging. Previously the LED driver was fully shut down; now it stays partially active to show a charging light effect. There is no obvious security bug in the change itself, but it slightly increases the amount of code that runs before the device enters its deepest sleep state.

This commit adds a new helper function that reports whether the Trezor device is currently charging. It also refactors one existing suspend/resume check to use that helper. There is no indication of a security bug being fixed; it appears to be a routine feature/refactoring change.

This commit simply deletes one unused macro named PM_SUSPENDED_CHARGING_TIMEOUT_S from a header file in the Trezor firmware's power management code for the STM32U5 chip. A macro is a named constant used by programmers; 'unused' means no code referenced it anymore. There is no functional change, no bug fix, and no security relevance visible in the change.

This commit adds a single CPU instruction called __WFI (Wait For Interrupt) inside the charging loop of a Trezor hardware wallet's suspend routine. It tells the processor to idle until an interrupt occurs, which is a normal power-saving measure. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a power-management or stability improvement.

This commit adds new power-management functions to the RGB LED driver in Trezor's hardware wallet firmware. It lets the device remember what LED effect was running before sleep, then restore it after waking up. There is no obvious security bug in the change itself.

This commit changes the order in which a Trezor hardware wallet decides whether its battery is charging, discharging, or idle. It now asks a dedicated helper function first instead of relying only on raw current readings. There is no indication in the commit that this fixes a security problem; it appears to be a routine improvement to charging-state detection.

This commit changes two fixed text strings inside the ChaCha20 code from C string literals to explicit character arrays. The strings are public constants used by the ChaCha20 algorithm ('expand 32-byte k' and 'expand 16-byte k'). The commit title says it fixes a CI build error, and there is no evidence in the diff or commit message of any security bug, memory issue, or behavior change beyond how the compiler stores these constants.

This commit updates a bundled cryptographic library (secp256k1-zkp) from one version to another. No actual code changes are shown, and the commit message does not describe any security fix. On its own, this looks like a routine dependency maintenance update.

This commit adds a new piece of information—battery charge percentage (SoC, State of Charge)—to the device's public 'Features' response. It only reads a value from the power manager and exposes it. There is no security-sensitive change: no new permissions, no bypass of protections, no handling of secrets, and no memory-safety issue visible in the diff.

This commit simply adds a new function that lets the device's Python-based software read the battery percentage from the power manager. It is a straightforward feature addition with no apparent security implications.

This commit swaps in newer pre-built binary files for the T3W1 hardware model's bootloader and Bluetooth firmware, plus updates the recorded cryptographic hashes that the build system expects. The change log says '[no changelog]' and the title calls it a routine chore. There is no visible source-code change, no description of a security fix, and no independent evidence that this update addresses a vulnerability.

This commit fixes a tiny user-interface wording mistake. After successfully unpairing a Bluetooth device, the Trezor screen was accidentally showing the message intended for the confirmation prompt ('forget this device?') instead of the success message ('device forgotten'). There is no security issue—just the wrong label on the success screen.

This commit only adds a new automated test that checks the Bluetooth 'unpair all' feature on one Trezor model. It does not change any production firmware code, so it cannot introduce a security vulnerability by itself.

This is a small bug fix in the Trezor hardware wallet firmware. After a user unpairs a Bluetooth device, the device was trying to send a button-press request over the now-disconnected Bluetooth link, which would fail. The fix stops sending that request during the success screen shown right after unpairing. It is a robustness fix, not a security vulnerability fix.

This commit fixes a small mismatch in how the Trezor device tells its Bluetooth subsystem to forget a paired device. The underlying Rust function now requires an address argument (or None), and the Python caller was updated to always pass one. The change is a code-cleanup/fix rather than a clear security vulnerability, but the previous default-argument path could have hidden caller mistakes.

This bootloader-only change adds a short wait and a temporary logo screen when a Trezor device has no firmware installed and Bluetooth (BLE) is enabled. The goal is to give the wireless nRF chip time to finish starting up before the user sees the 'Start' setup button. Without this delay, the device could briefly show the start button while the Bluetooth state is still unknown, which might lead to a confusing or inconsistent setup experience. There is no direct evidence in the commit that this fixes an exploitable security vulnerability.

This commit changes how a Trezor Bluetooth device broadcasts its presence to Apple devices. It makes the device advertise more frequently at first, then slow down after 30 seconds, and adds a lock to prevent simultaneous changes. There is no clear security bug being fixed; it appears to be a compatibility/stability improvement for iPhones and iPads.

This commit removes a short 0.1-second delay from an automated test script. It does not change the actual Trezor firmware or any code that runs on user devices. There is no security issue here.