What the developer wrote
Authored by obrusvit
test(core): disable suspend in emulator
- this should be temporary until there's a better way to continue tests
after emulator suspend
[no changelog]
What changed, and why it matters
This is a test-only change that prevents the Trezor emulator (a software version of the hardware wallet used for testing) from entering a low-power suspend state during automated tests. It does not affect real Trezor devices and is not a security fix.
No security action needed. Treat as a normal test-infrastructure change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies lock_manager.py so that the suspend-and-resume logic, gated by USE_POWER_MANAGER, is additionally skipped when running in the emulator (utils.EMULATOR). The commit message explicitly frames this as a temporary test workaround: ‘disable suspend in emulator … until there’s a better way to continue tests after emulator suspend.’ No production behavior on hardware is changed.
Changed components
core/src/apps/common/lock_manager.pyInspect captured patch +1 / −1
diff --git a/core/src/apps/common/lock_manager.py b/core/src/apps/common/lock_manager.py
index ed660b937..ea06e27f5 100644
--- a/core/src/apps/common/lock_manager.py
+++ b/core/src/apps/common/lock_manager.py
@@ -157,7 +157,7 @@ def lock_device_if_unlocked() -> None:
elif config.is_unlocked():
lock_device(interrupt_workflow=workflow.autolock_interrupts_workflow)
- if utils.USE_POWER_MANAGER:
+ if utils.USE_POWER_MANAGER and not utils.EMULATOR:
if workflow.autolock_interrupts_workflow:
# suspend immediately
suspend_and_resume()
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.