application-lifecycle

What I do know is that the current activity get into the onPause() mode, and the home screen activity brought to front. My confusion starts with situation you can re-open the application from the recent tasks menu. so what exactly happening when I'm opening the application from the recent tasks manager? Is the activity that was foreground when the home button pressed is still somewhere in the stack? Is there more then one activity stack on the same time? As far as I understand it, there is no real stack (of applications). Is just that your activity has states, so whenever you are pressing the

Currently in my UWP application, I provide a way to change the app theme. But in order for the change to be effective, the user has to manually close the app and restart it. I'm looking for a way to do it automatically, ie, restart the app programmatically. Is it even possible? thank you. According to a recent blog post , there is a new API for this "from Build 16226 onwards, along with the corresponding SDK." The new static RequestRestartAsync(String) method and overloads on CoreApplication provide the previously unavailable app restart magic, including the ability to pass arguments to the

well most of us familiar with this pattern: public class MySingeltone { public String mSomeReferenceTypeData; public int mSomeValueTypeData; private static MySingeltone mInstance; private MySingeltone() { } public static MySingeltone getInstance() { if (mInstance == null) { mInstance = new MySingeltone(); } return mInstance; } } my problem is that I've found recently that the mInstance don't equal null after activity using him been destroyed, or when the whole application suppose to be clause, for example: public class SomeActivity extends Activity { @Override protected void onCreate(Bundle

I am making my first Socket.io based android application. The socket sends and receives data from a web service. There are a number of screens in the application for different features. How do i use the same socket connection in these different activities. I have tried setting and storing the Socket Object in the Application class and it appears to work well but when the application goes into the background and left there for some time the application is killed and the socket object is then NULL causing the aoo to crash with a null pointer exception. public class MyApplication extends

I have an Android activity which in turn starts a thread. In the thread I open a persistent TCP socket connection. When the socket connects to the server dynamic data is downloaded. The thread sends messages using Handler-class to the activity when data has been received. Now if the user happens to switch from portrait to landscape mode the activity gets an onDestroy call. At this moment I close the socket and stop the thread. When Android has switched landscape mode it calls onCreate yet again and I have to do a socket re-connect. Also, all of the data the activity received needs to be