Skip to content

Comments

Add a toggle to disable FLAG SECURE#313

Open
BasedJellyfish11 wants to merge 1 commit intoGrapheneOS:16-qpr2from
BasedJellyfish11:16-qpr2
Open

Add a toggle to disable FLAG SECURE#313
BasedJellyfish11 wants to merge 1 commit intoGrapheneOS:16-qpr2from
BasedJellyfish11:16-qpr2

Conversation

@BasedJellyfish11
Copy link

@BasedJellyfish11 BasedJellyfish11 commented Feb 20, 2026

issue: GrapheneOS/os-issue-tracker#664

Adds a setting to developer options to disable flag secure globally. Actual setting is implemented in GrapheneOS/platform_packages_apps_Settings#411

image image

@thestinger
Copy link
Member

We only want to override disabling screenshots instead of the other parts of it.

@BasedJellyfish11
Copy link
Author

AFAIK flag secure is only used for screenshots (and casting, which seems like the same use case)

https://developer.android.com/security/fraud-prevention/activities

FLAG_SECURE

FLAG_SECURE is a Window flag that tells Android not to allow screenshots or to display the window view on a non-secure display (such as Casting the screen). This is useful for applications that need to protect sensitive information, like banking apps or password managers. When a window is flagged with FLAG_SECURE, Android prevents screenshots from being taken and prevents the window from being displayed on a non-secure display, such as a TV or projector. This helps to protect the information that is being displayed in the window from being accessed by unauthorized people.

Is the ask to decouple the setting from the casting functionality? Or just a double check

@thestinger
Copy link
Member

It does change other things including it not generating thumbnails for recent apps.

@BasedJellyfish11
Copy link
Author

Sounds good, let me look into what needs to change

@BasedJellyfish11
Copy link
Author

Should be good now

2026-02-20 19-08-59

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants