Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
I think with all the engineers at Google developing Android they could come up with a solution of how to discern whether the act of screenshot was triggered solely by the user, or an app on the phone. They are the ones in power of all the APIs that allow other apps to capture the screen content in the first place. Maybe I am simplifying it too much, but this seems as a bad excuse to me.
Maybe it would be too hard of a solution since there's so many ways third party apps could capture screen content (including for example the Android accessibility service which also allows apps to read content of the screen and even simulate screen touches and gestures which many automation apps make use of) that blocking the screenshot alltogether is by far the most feasible solution.
There is already a solution:
Third-party apps, unless a user specifically go to settings and find that option, don’t have the permission known as “Draw Over Top” that’s required to do screen recordings/screenshots.
So by default, a user is already safe from a malicious app trying to steal info. (That is, unless they just be an idiot and give the app "Draw Over Top" permission)
That's not exactly intuitive. I had no idea that permission would allow an app to take screenshots. The warnings given on the permission screen mention other risks, but not that one.
Some password managers want draw over top.
Bitwarden required it, iirc
Well you are gonna be trusting the password manager anyways, since its literally storing all your passwords. If you trust Bitwarden to store all your passwords, then you can trust it to not abuse the "Draw Over Top" permission.
I just looked at my bitwarden permissions and that's not listed there...
For me and my family, I think the best solution would be to leave it as-is but with a way to lift the restrictions for power users that doesn't involve root access. Something akin to enabling developer mode without having to buy a specific rootable phone