Suppose there is an activation and at the beginning there is loaded for example an mp3 file for MediaPlayer, it seems to happen quickly, but let's say the file pulls up from the network and loads for a long time. Well, he booted. Now, by clicking on a certain button, I switch to a new activation, and the first one is activated by the system on onPause (as far as I know at this moment all the resources of this activation are cleared). And now, in the second activation, I create a copy of the first activation (or rather, the class) and I want to get access to the file that has long crashed and which I specifically loaded onto the splash screen. If I create an instance of the first class, I will either not have the downloaded file at all, or if its loading is not implemented in the life-cycle methods, it will start loading on a new one. (or even it will not be possible to re-create in such a way that when an instance is created it reloads). Only if I declare a resource as static, can I use it in the future. Correct my mistakes in thinking and tell me how to properly load a heavy resource on the splash screen, so that later it is convenient to refer to it?
There is no answer, I update and clarify the question.
UPD When, when opening the next activation, a heavy file is loaded from the resources into the RAM (for example, the background music file). Surely there will be a delay in the deployment of the activation until the upload is complete. As I understand, such a transfer is transferred to the Splash screen. a separate class is responsible for displaying Splash screen, it has loaded the required file into a variable and we want to receive it, this variable, next activation. But creating an instance of the class Splash screen, we will not get it, it remains to make the variable static. But is it right? Is this approach used when, for example, in a heavy game like World of Tanks, a splash screen hangs for a long time. Hardly they load a bunch of files and make them static. Below in the answers, we suggested not to change the activation, but only to change the display using setContentView (). But then the RAM was crying, variables that are no longer needed will not be killed by the garbage collector .. And on the other hand in the Splash screen there are not many variables .. All files are loaded, the display was replaced with setContentView () and it went .. The question is Is the approach correct and used by professionals?