Acquire WakeLock when hosting Swissbit SCUs #86
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FlorianStadlberger
previously approved these changes
Sep 4, 2024
FlorianStadlberger
approved these changes
Sep 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR acquires an Android WakeLock from the Middleware when it's hosting a Swissbit Hardware SCU. While not required in most cases, in some slow-hardware scenarios (on payment terminals) Android seems to switch off parts of the CPU or the device management or the system clock, which resets the Swissbit TSE and enforces constant self-tests.
As these self tests take ~30 seconds, this renders the TSE unusable on these devices. A WakeLock seems to prevent this.