On Tue, Dec 25, 2012 at 8:35 PM, TreKing treking...@gmail.com wrote:
I believe it is entirely possible and actually a frequent occurrence that
Activities are destroyed while processes are not. For example, you might
open a second Activity within your own app that causes memory pressure -
your
On Wed, Dec 26, 2012 at 2:35 AM, TreKing treking...@gmail.com wrote:
On Tue, Dec 25, 2012 at 3:04 PM, Latimerius l4t1m3r...@gmail.com wrote:
The thing I don't get is how would that be possible if Android doesn't
collect individual Activity instances, just whole processes.
I believe it is
On Wed, Dec 26, 2012 at 1:38 PM, Mark Murphy mmur...@commonsware.comwrote:
On Tue, Dec 25, 2012 at 8:35 PM, TreKing treking...@gmail.com wrote:
I believe it is entirely possible and actually a frequent occurrence that
Activities are destroyed while processes are not. For example, you might
Have you experimented with Don't keep activities in Settings Developer
options?
On Wednesday, December 26, 2012 4:17:06 PM UTC, latimerius wrote:
On Wed, Dec 26, 2012 at 2:35 AM, TreKing treki...@gmail.com javascript:
wrote:
On Tue, Dec 25, 2012 at 3:04 PM, Latimerius
On Wed, Dec 26, 2012 at 11:30 PM, RichardC
richard.crit...@googlemail.comwrote:
Have you experimented with Don't keep activities in Settings Developer
options?
Nope, I haven't touched that (yet).
--
You received this message because you are subscribed to the Google
Groups Android
On Wed, Dec 26, 2012 at 6:38 AM, Mark Murphy mmur...@commonsware.comwrote:
On Tue, Dec 25, 2012 at 8:35 PM, TreKing treking...@gmail.com wrote:
I believe it is entirely possible and actually a frequent occurrence that
Activities are destroyed while processes are not. For example, you might
On Sun, Dec 23, 2012 at 10:43 PM, Lew lewbl...@gmail.com wrote:
Instances do not initialize static members in Java. The static members are
initialized as part of
class initialization.
Instances can set static values if they're mutable, but that's not
initialization.
I don't know about
On Tue, Dec 25, 2012 at 3:04 PM, Latimerius l4t1m3r...@gmail.com wrote:
The thing I don't get is how would that be possible if Android doesn't
collect individual Activity instances, just whole processes.
I believe it is entirely possible and actually a frequent occurrence that
Activities are
I tried finding it, couldn't. i think it was the video was from around
2008, one of the very early presentations of android memory
management/activity lifecycle videos.
I found a similar one but it only showed a whole process being taken down,
not a single activity instance... so at this
documentation flaw? was android changed to no longer do that? i remember a
presentation done by google mentioning this exact process as part of
android's normal work... but that was years ago... can you point us to
documentation stating otherwise?
regarding onStop and onDestroy, under some
On Sun, Dec 23, 2012 at 4:08 AM, Piren gpi...@gmail.com wrote:
documentation flaw? was android changed to no longer do that?
I am not completely certain what aspect of my email your that is
referring to. If you mean destroying activities to reclaim memory:
thats really pissy... they said the exact opposite in one of their original
android video presentations.
they had a whole part showing how activities are being dropped if the
activity stack gets too big to maintain them all.
On Sunday, December 23, 2012 2:29:15 PM UTC+2, Mark Murphy (a Commons
A lot of Google's Android presentations are online. Can you provide a link
or recall the time period during which that presentation was given?
On Dec 23, 2012 7:00 AM, Piren gpi...@gmail.com wrote:
thats really pissy... they said the exact opposite in one of their
original android video
On Sat, Dec 22, 2012 at 8:06 PM, Mark Murphy mmur...@commonsware.comwrote:
That is a documentation flaw. Android does not destroy this instance
of the activity to save space, except by terminating the entire
process. isFinishing() will distinguish multiple reasons for onPause()
and onStop()
latimerius wrote:
Mark Murphy wrote:
That is a documentation flaw. Android does not destroy this instance
of the activity to save space, except by terminating the entire
process. isFinishing() will distinguish multiple reasons for onPause()
and onStop() being called (e.g., BACK will cause
onDestroy - The final call you receive before your activity is destroyed.
This can happen either because the activity is finishing (someone called *
finish()* on it, or because the system is temporarily destroying this
instance of the activity to save space. You can distinguish between these
On Sat, Dec 22, 2012 at 1:59 PM, Jonathan S xfsuno...@gmail.com wrote:
onDestroy - The final call you receive before your activity is destroyed.
This can happen either because the activity is finishing (someone called
finish() on it, or because the system is temporarily destroying this
Did you look in
http://developer.android.com/guide/components/tasks-and-back-stack.html
when you use singleTop
On Friday, December 21, 2012 2:26:25 AM UTC-5, Amit Dwivedi wrote:
i also have a similar problem... please have a look on my Detailed
i also have a similar problem... please have a look on my Detailed
Questionhttp://stackoverflow.com/questions/13928591/a-strange-behavior-of-android-activities-fragments-and-intent
On Friday, October 15, 2010 5:25:18 PM UTC+5:30, Kumar Bibek wrote:
While starting an Activity, use the
Yep, in normal circumstances. Did you try using the Activity's context and
see if it makes any difference?
On Fri, Oct 15, 2010 at 4:33 PM, mariush mariusz...@gmail.com wrote:
so after invoking finish() onDestroy and onStop must or should be
invoked?
Moreover, it not happens on all kind of
While starting an Activity, use the Activity's context. I am not sure though
what your problem is.
On Fri, Oct 15, 2010 at 4:49 PM, mariush mariusz...@gmail.com wrote:
No,
but how can i finish activity using Context, finish isn`t derived
method and is available only in Activity class.
On 15
If you are finish an activity through code, onStop and onDestroy should be
called. In extreme cases where the system kills your app, these two methods
may or may not be called. I am sure, you are doing something wrong. Or may
be it has got something related to reboot of phone.
On Fri, Oct 15,
22 matches
Mail list logo
