You need to re-read the life-cycle documentation. After pressing
[home] your app may be killed at any time, it just hasn't been killed
yet.
If you need a background process read up on services.
--
RichardC
On Oct 28, 7:26 am, tomei.ninge...@gmail.com
tomei.ninge...@gmail.com wrote:
When user
I can handle may be killed. I just don't want killed for sure.
Anyone got an answer for this?
On Oct 28, 12:37 am, RichardC richard.crit...@googlemail.com wrote:
You need to re-read the life-cycle documentation. After pressing
[home] your app may be killed at any time, it just hasn't been
If you think how to get around application lifecycle, then you
project design is TOTALLY BAD. Really.
Redesign project.
On 28 Paź, 08:26, tomei.ninge...@gmail.com
tomei.ninge...@gmail.com wrote:
When user presses BACK key, my activity's onDestroy is called and then
it is killed. Is there a
I agree with Piotr.
Tomei,
We may be able to help you with the *how*, if you told us *what* you
are trying to accomplish. I am almost 100% it could be done without
trying to circumvent Android's lifecycle management.
On Oct 28, 4:42 am, Piotr piotr.zag...@gmail.com wrote:
If you think how to
My activities's first screen shows a bunch of images. When I hit HOME
and then launch the app again, my app's first screen is displayed
instaneously.
You are not launching the app in this case. Pressing HOME is roughly
equivalent to minimizing a window in a windowed operating system. Choosing
My activities's first screen shows a bunch of images. When I hit HOME
and then launch the app again, my app's first screen is displayed
instaneously.
If I hit BACK and launch the app again, the images are decoded again
and it takes about 200ms to show.
Is there anyway to reduce this 200ms time?
6 matches
Mail list logo
