Trezor firmware

This commit exposes an existing Bluetooth security pairing/authentication function so it can be called by the main Trezor application (coreapp). It does not appear to fix a vulnerability; rather, it is a feature that lets the coreapp request authentication with the nRF Bluetooth chip. The change removes a compile-time restriction that previously limited the function to secure mode, adds a new system call, and adds a secure-monitor call for validating a pairing secret. Without additional context, this looks like a normal feature enabling secure Bluetooth pairing, not a security patch.

This commit adds a new diagnostic command, 'ble-get-bonds', to Trezor's internal production-test firmware. It lets a factory technician read the list of Bluetooth devices previously paired with the device. The change is purely a feature addition for manufacturing/diagnostics; it does not, by itself, bypass pairing, steal funds, or change security settings. The main concern is that it exposes paired-device addresses (MAC addresses) through the production-test command-line interface, which could be a minor information-leak if the prodtest interface is accessible in the field.

This commit adds a new system call that lets the main Trezor application read the firmware version of the nearby nRF Bluetooth chip. It is a small feature addition that exposes read-only version information; it does not, by itself, change how data is trusted or allow code execution.

This commit adds a new system call that lets the Trezor core application read the list of Bluetooth devices the hardware has bonded with. It is a feature addition, not a fix. The code includes a memory-access check before copying the bond list into the caller's buffer, which is the expected defensive pattern for this firmware's syscall layer. There is no direct evidence in the commit that this is a security patch or that it addresses a known vulnerability.

This commit updates the battery fuel gauge calibration table for a specific Trezor battery model. It tweaks temperature points and the mathematical curves used to estimate charge level. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a hardware calibration/modeling correction. The title says it removes characteristics affected by temperature transition, suggesting an accuracy improvement rather than a security fix.

This commit adjusts internal tuning numbers for the battery fuel gauge in Trezor hardware wallets. It changes how the device estimates remaining battery charge, making the estimate smoother and less reactive. There is no indication this affects security, private keys, user data, or device integrity.

This commit updates the battery fuel gauge calibration table for a specific Trezor battery model. It replaces 4 temperature data points with 8 more detailed temperature profiles and adjusts the mathematical curves used to estimate battery charge level. There is no indication this change affects security, cryptography, user funds, or device integrity.

This commit updates the battery fuel gauge code in Trezor hardware wallets so that it uses separate temperature lookup tables when the battery is charging versus when it is discharging. Previously, the same temperature table was used for both states. This is a routine calibration/modeling improvement, not a security fix.

This commit updates the battery fuel gauge calibration data for a specific Trezor hardware battery model. It changes temperature breakpoints and the mathematical coefficients used to estimate battery charge level from voltage readings. There is no indication this is a security fix; it appears to be a routine hardware characterization update.

This commit adjusts the tuning values for the battery fuel gauge's estimation filter in a Trezor hardware wallet. It changes how aggressively the device trusts its battery sensor measurements versus its internal battery model. There is no indication this is a security fix or introduces a security issue; it appears to be a routine calibration tweak for more accurate battery reporting.

This commit adds a new Trezor feature that lets users derive a special cryptographic key (a SLIP-21 node) for a third-party storage framework called Evolu. The device will show an on-screen confirmation before releasing the key. It is a feature addition, not a fix for a known vulnerability. The main security consideration is that any host application able to send the new message type can request this key, but only after the user confirms on the device. The key is tied to a fixed path ("TREZOR"/"Evolu"), so it cannot be used to steal cryptocurrency directly, but if a user is tricked into approving it, the key could be leaked to a malicious application.

This commit is a purely cosmetic UI tweak for the Trezor hardware wallet. It increases the top padding of the home screen label from a theme-defined value to a fixed 38 pixels. There is no security relevance in the change itself.

This commit only changes the text labels shown on the Trezor Safe 7 (Eckhart) home screen action bar. It replaces 'Tap to connect' with 'Tap to start' on the boot screen and 'Tap to unlock' with 'Unlock' on the lock screen, plus adds the new translation key and updates translation metadata. There is no security-relevant code change.

This is a cosmetic UI alignment change for the Trezor hardware wallet. It makes the default device name shown on the homescreen and in the device menu consistent by using the model's full name (e.g., 'Trezor Safe 5') instead of a hardcoded 'Trezor' fallback. It also tweaks text styling and reorders a translation entry. There is no security-relevant change.

This commit rewrites the on-screen keyboard used to type text into the Trezor Safe 5 (Eckhart layout). It renames the component, removes a separate confirmation screen for empty labels, lets users submit an empty string directly, and allows cancelling even when nothing has been typed. The change is described as a UI/UX cleanup, not a security fix. There is no direct evidence in the commit that it patches an exploitable vulnerability, but removing an extra confirmation step for empty device names slightly changes the safety surface around user input.

This commit only updates a test data file (tests/ui_tests/fixtures.json) used to verify that the device's on-screen user interface matches expected screenshots. It adds new test cases for setting a device label to empty or maximum length, and refreshes many pre-computed visual hashes for an internal test model. There are no changes to the actual firmware code that runs on Trezor devices, so this commit cannot directly introduce a security vulnerability in shipped products.

This is a minor user-interface cleanup for the Trezor hardware wallet. It changes how a device label is shown on screen so the label text is no longer visually highlighted as a special parameter. There is no security issue or vulnerability here.

This commit is a routine user-interface polish change for the PIN entry screen on Trezor hardware wallets. It renames an internal parameter from 'subprompt' to 'attempts', adds a new flag so the screen can visually highlight the final PIN attempt, and fixes text alignment and spacing. There is no indication this change fixes a security vulnerability or introduces one.

This commit is a cosmetic user-interface fix for the Trezor hardware wallet's new 'Eckhart' layout. It adjusts how recovery seed words are displayed on screen—text alignment, prompt placement, and spacing—without changing any security logic, cryptography, or how secrets are handled.

This commit fixes visual layout glitches in the passphrase entry screen on a specific Trezor device model (Eckhart). It adjusts prompt spacing, text alignment, and the placement of the last typed character. There is no indication this changes security behavior or introduces a vulnerability.

This commit changes how the Trezor hardware wallet's Bluetooth Low Energy (BLE) connection behaves when the device reboots from the bootloader into the main firmware. Previously, the bootloader would shut down BLE entirely during this handoff, forcing the user to reconnect. Now it tries to keep the existing BLE connection alive across the reboot. This is a user-experience and availability fix rather than a security patch, but it slightly alters the attack surface during a sensitive transition.

This commit wires up the on-device settings menu for a new Trezor hardware-wallet UI (the 'Eckhart' layout). It adds menu entries that let the user change or remove their PIN and wipe code, set auto-lock delay, and check their backup. The change is mostly UI plumbing: it connects existing security-management code to new menu items and adds translated labels. There is no obvious security bug in the diff, but it is a partial implementation (other TODOs remain) and the code now exposes sensitive actions through a new menu surface.

This commit adds new notification entries and warning styles to the device menu on the Trezor hardware wallet. It is a routine user-interface feature patch: it introduces a 'PIN not set' reminder, changes the visual style of a failed-backup warning, and wires the failed-backup menu item to a device-wipe confirmation prompt. There is no evidence of a security vulnerability being fixed.

This commit adds a Bluetooth on/off menu item to the device settings screen for the upcoming Trezor Safe 7 (Eckhart layout). It is purely a user-interface change: it shows a label and a confirmation prompt, but the actual Bluetooth enable/disable logic is left as a TODO and does nothing. There is no security fix or security-relevant behavior change.

This commit is a routine UI update for the Trezor hardware wallet's device menu. It wires up previously placeholder settings (screen brightness, haptic feedback) and adds a 'Wipe device' option to the menu. There is no security fix or vulnerability visible in the change.