The app I\'m working on shows some sensitive information that must not be shown on the \"Recent Tasks\" screen when stopping the app by pressing the home button.
I\'
How about implementing a layout overlay on top of your entire activity?
Make it transparent, it's click-through by default, so no negative impact on UX while in use.
In onPause()
set a half-transparent, blurred image as the background of that layout, the data will be scrambled behind it. In onResume()
change the background to fully transparent again. Voila.
It might be faster than other types of overlays. The positive side effect is, if you do the unblurring as a short animation effect when the user goes back (with a proper library that uses C++ instead of Java), it might even look cool and the users wouldnt even mind seeing it.
I haven't tried this myself, but it's something you haven't tried yet.
I looked into this a couple of months ago for the same purpose as you.
Unfortunately, I had to conclude that it is simply not possible. I dug through the android source code and confirmed it.
FLAG_SECURE
, this part of the code does not accept any input or change.SECURE_FLAG
, or any other obstruction of the view). As an aside, these images can be found on an emulator at /data/system_ce/0/recent_images
. FLAG_SECURE
, which will prevent the screenshot from being taken of your application. I experimented with setting this FLAG in onPause
and removing it in onResume
, however as mentioned already these lifecycle methods runs after the screenshot is taken already, and thus had absolutely no effect.As discussed in How to change the snapshot shown by recent apps list? there used to be a callback that you could use to customize the thumbnail: onCreateThumbnail. However, this does not work and it is never called. To be clear, the callback is still there, it is simply never called by the OS. The fact that it stopped working is poorly documented, but apparently was silently deprecated/removed in 4.0.3
As for the thumbnail itself, it is a screenshot taken serverside. It is taken before onPause
is called (or in fact before any callbacks indicating that your activity is about to go into the background is called).
When your app does go into the background, your actual view is animated (to get that zoom-out transition). That animation can be affected through changes you do in onPause
(if you're fast enough that is) (I experimented with setting opacity to 0 on the window among other things). This will however only affect the animation. When the animation is finished, the view is replaced by the screenshot taken earlier.
Also see these questions that discuss this:
There is a way to customize it. You need your Activities with sensitive data to FLAG_SECURE
in onCreate
before you setContentView
. Then you need an empty Activity, which renders whatever you want to have as the customized thumbnail. This usually is some sort of splash screen. This new Activity needs to be the launcher and is the only Activity not FLAG_SECURE
. This Activity is launched and in onResume starts your actual Activity with the sensitive data.
Android OS will take a screenshot of that new Activity at the beginning of your App. Unfortunately the users will also see this Activity for a short moment. Since every other Activity is FLAG_SECURE
, Android OS will use the only available screenshot it made at the beginning.
I think this can only achieve through BroadCastReceiver but there is no receiver present. So therefore you first disable default screenshot functionality in android and then implementing your own functionality to take screenshot and before taking screenshot you should blur your secure information.
Currently (28/10/2020) is impossibile customizing app thumbnail in recent apps screen.
As explained by @Dellkan in the previous answer, the onCreateThumbnail
method is not called anymore by the OS.
Unfortunately, also the suggestion to create a kind of launcher/splash screen without the FLAG_SECURE flag to let the app take a screenshot of that activity is not working, because the screenshot is taken on the activity you see and not at the launch of the app.
You cannot even customize the color of window background when using FLAG_SECURE as reported here.