On Mon, Nov 8, 2010 at 1:37 AM, Mathias Lin m...@mathiaslin.com wrote:
That's what I thought. But why is the UI state then not entirely
cleared?
AFAIK, applications do not hold the saved instance state -- the
operating system does, in its own process.
--
Mark Murphy (a Commons Guy)
Hi Mark,
thanks for your reply. Yes, it's probably managed by the system, yet
I'm still wondering:
Below you can see that the browser activity runs in different
processes (#2307, #5536) before and after I killed/restarted it, and
yet it's displaying / restoring the same UI input values entered
On Mon, Nov 8, 2010 at 11:38 AM, Mathias Lin m...@mathiaslin.com wrote:
thanks for your reply. Yes, it's probably managed by the system, yet
I'm still wondering:
Below you can see that the browser activity runs in different
processes (#2307, #5536) before and after I killed/restarted it, and
They don't have the same instance state. You can use adb shell dumpsys
activity to see the system's activity stack; each of those entries is an
instance of an activity as far as the system is concerned.
Killing a process while its UI is in the background is a normal situation on
the system -- it
Not too scary if you look at my scenario ;-)
I have devices that I rent out to end-users through a hotel/concierge.
These devices hold 1) my app, 2) browser, 3) facebook app.
End-users (hotel guests) can rent the devices and return it to the
hotel. The non-technical hotel concierge needs to be
Please leave the lifecycle documentation. Processes are just transient
entities used to hold running processes; killing a process is not the same
as stopping an application. You are treating this like a Unix system,
when it is not.
Resetting an application back to its initial state is done with
Ok. In my case, I cannot call finish() myself since it's a third party
app (Facebook) and the native browser. Therefore I do a kill. Wouldn't
that also end the lifecycle as well, with same effect as a finish() ?
On Nov 8, 12:55 pm, Dianne Hackborn hack...@android.com wrote:
It isn't stored
On a rooted phone, you ought to be able to kill the Linux process. Just
finish or force close may not be secure since the Android OS lazily reclaims
processes that are no longer in use. Although on a non-rooted phone this is
not an issue, since the Android OS relies on Linux process security.
--
That's what I thought. But why is the UI state then not entirely
cleared?
But I found the following difference though doing some more testing -
I found there's a difference whether the activity is in the foreground
or not when I do the kill:
Case 1)
I start the facebook app, I am on the login
9 matches
Mail list logo
