lifecycle

As far as I can read, Android may kill my process at any time 1 . One might interpret the article [1] such that, at any point, a process must be able to survive a crash. How is that handled? Are there any guarantees of any methods being called if a process is killed this way? The article* doesn't mention it. My question is, how do you guarantee that a force-killed process resumes in some sane way on next start? The only state my process has (assuming no guarantees are made for methods being called when process is killed) is the state in persistent storage (a DB or elsewhere) and this is likely

I'm dealing with .setVisibility() of a view , inside my main fragment at app start. So what I want is that the view is invisible on app start (for this i set INVISIBLE inside onCreateView) and to be visible when I come back to my fragment from other activities while the app is open (and for this I tried to use onRestart() to set view VISIBLE but it cannot resolve onRestart method) is onRestart deprecated or? thanks EDIT: for all the answers below suggesting to use an onResume (and whom gave a -1), onResume doesn't work as onRestart at all, cause is being called right after onCreateView.

Some days ago I have published my application in Android Marketplace and a question came into my mind during designing and developing application. This question is about limitation or unlimitation of number of activities. For example, my application includes 37 activities. Is it so much? I want to know for a game such as "Angry Birds" which has more than 200 levels, it has 200 activities?!! My next question is, assume that I am designing an application which includes 100 activities. User starts application and gos into last activity (such as reading a book). If user wants to close the

I don't understand when I should implement something in viewDidUnload versus viewDidDisappear . What's the difference between the two? For instance, I'd like to send an NSNotification when the view controller is removed from the view hierarchy. Between these two methods, does it matter where I post that notification from? https://developer.apple.com/documentation/uikit/uiviewcontroller Abhishek Singh This is with reference to apple's documentation:- viewDidUnload:- When a low-memory condition occurs and the current view controller’s views are not needed, the system may opt to remove those

I have a "long-running" cleanup operation that I need to perform in onDestroy() of my Activity . What is the best way to do this? If I use a Thread to do this, my onDestroy() will return immediately; but what happens to the Thread reference? I am looking for advice on any implications/gotchas/trip-wires that I need to be aware of here since I assume that the process will still be alive even after the Activity is destroyed. Background: I am using JmDNS in my app. When the user is done with my app, I want to clean up the JmDNS instance. I do this using the close() method of JmDNS class. However,