fix: support secure capture on One UI 8 - #115
Conversation
|
FLAG_SECURE should not be disabled, as this will break bank app's security detection. |
|
Okay, I’ll try a different approach. And there’s also something specific to Samsung that needs to be tried... |
8fd79da to
e653254
Compare
|
Updated the branch with a Samsung-specific approach.
The implementation was verified against the matching Screen recording is no longer enabled by this PR |
|
Warning: This solution was created with extensive use of AI. I tried to remove unnecessary code and tidy it up, but it most likely still requires the attention of a more experienced developer. |
Please upload the JAR files for Samsung system framework and services. |
|
https://drive.google.com/file/d/1W7u5juRaKsi0IFKuOgd4PdMid1-1IKP6/view?usp=sharing I couldn’t upload it directly here because of the GitHub limit. |
|
I got this working on my s26 ultra (SM-S948N). The PR as-is didn't work for me. It matches methods by name and parameter count, but the screenshot method on the s26u takes 6 parameters, so it never hooks. My fix was to hook the method with a single boolean parameter (the secure-content-policy flag) instead, and that did the trick. I can share my code if anyone's interested, though all of it done with AI help. |
Can this work on temporary root ..(root my galaxy) s24 ultra without bootloop |
Fixes screenshots and built-in screen recording for
FLAG_SECUREapps on Samsung One UI 8 / Android 16.WmScreenshotControllerpolicy and secure-content capture path.falsefromWindowState.isSecureLocked()so secure layers can also be mirrored by Samsung Screen Recorder.Tested on Galaxy S25 (SM-S931B), One UI 8.5 / Android 16: screenshots and screen recordings work.
Related to #93