41–50 of 385 posts
Anyone else noticed that you can't take screenshots on Android when using Chrome Incognito mode? "Can't take screenshot due to security policy". I don't understand the rationale behind it. Why can't I take a screenshot of my own phone?
I had a similar problem when I updated to Android 10 and the MediaStore content provider decided to get stuck in an infinite loop trying to upgrade its database. I couldn't take screenshots, use the camera, or use any functionality in any apps that would rely on the photo gallery. Now, that's me, a long time Android app developer, and it took me an hour to figure out what the hell happened (wiping the data for said c…
While I’m not sure whether it’s true, I think the reasoning behind this is that to the average user, a sensible error message is about as useful as "something failed, good luck".
At least Apple has not done anything as user-hostile as this, yet. On iOS the balance of control is still in the user's favor, not the apps', and increasing with every release (like discrete permissions, limited location sharing, being able to choose which photos each app can see).
How is that user-hostile?
Earlier quoted context omitted.
It’s to prevent you screenshotting snaps / disappearing messages sent to you or to prevent screenshotting licensed content. This is good for 99% of the people.
> prevent screenshotting licensed content. [..] good for 99% of the people Is this a parody, or do you truly think DRM is good?
In principle is DRM bad? Sure, the current implementations are pure cancers, but if they weren't, wouldn't DRM be a rather good thing?
At least Apple has not done anything as user-hostile as this, yet. On iOS the balance of control is still in the user's favor, not the apps', and increasing with every release (like discrete permissions, limited location sharing, being able to choose which photos each app can see).
Earlier quoted context omitted.
> But then again, what choice do I have? Unlock the bootloader, install Xposed and this module: https://repo.xposed.info/module/fi.veetipaananen.android.dis...
Won't unlocking the bootloader make banking apps not work anymore? Had this issue when I tried LineageOS on my old phone, and I really like the convenience of those apps as opposed to using the website, which is extremely bad. Also, how do I do all you said above? (I need a step by step tutorial). Also is it reversible? Are there any other security implications?
Depends on how paranoid your bank is. There's this SafetyNet thing that checks for "system integrity". It's part of Google Services. For now, it's possible to bypass these checks using Magisk, but I've read that Google is testing the new method involving TrustZone — a hardware trusted execution environment within the SoC where you aren't one of the trusted parties.
> Also, how do I do all you said above? (I need a step by step tutorial).
There should be plenty on xda-developers.com
> Also is it reversible?
On Google devices, yes, completely. You can reflash the factory images that Google provides and relock the bootloader. On others... it varies, on Samsung especially.
> Are there any other security implications?
If you leave the bootloader unlocked, anyone with physical access to your device will be able to reboot it into the bootloader and load arbitrary code with OS kernel privileges. From there they'll be able to modify the installed system. They won't be able to read the /data partition [right away] because it's encrypted with your password/pattern.
IMO it's really a shame you can't re-lock the bootloader with your own signing key.
I had a similar problem when I updated to Android 10 and the MediaStore content provider decided to get stuck in an infinite loop trying to upgrade its database. I couldn't take screenshots, use the camera, or use any functionality in any apps that would rely on the photo gallery. Now, that's me, a long time Android app developer, and it took me an hour to figure out what the hell happened (wiping the data for said c…
> at least show a sensible error message so people who haven't spent ridiculous amounts of time reading the source code of your product as part of their job can troubleshoot their systems. Not "something failed, go read logcat, maybe it helps, good luck". While I’m not sure whether it’s true, I think the reasoning behind this is that to the average user, a sensible error message is about as useful as "something faile…
I wont be surprised if iOS screenshots are eventually also altered/prevented in the future using similar levels of control.
Earlier quoted context omitted.
You'd think that a user-initiated screenshot should be distinguishable from a API initiated one, though. In my experience, it mainly seems to be banking and messaging apps that monitor or block screenshot events.
If a user initiated screenshot was distinguishable from an API initiated one, then you could argue third party screenshotting apps aren't first class citizens on the platform
It was a bug - this time. It's not your phone, you're just using it.
It’s to prevent you screenshotting snaps / disappearing messages sent to you or to prevent screenshotting licensed content. This is good for 99% of the people.