Yes I had this kind of problem with Eclipse until a few days.
But now I changed my manifest and the intent flags in my notification
intents:
My main activity is still singleTop to avoid multiple instances when
relaunching from Home, onNewIntent is called.
In notifications intents I use both the fl
Look at the discussion under the topic "Activity Question" couple days
ago
webmonkey wrote: 27. August 2008 20:25
---
there is no need to use singleTask, singleTop or any
other special flags. It has something to do with the way Eclipse re-
installs your application. If y
about onRestoreSavedInstanceState: I misunderstood the doc, I now
understand why it was not called in my case. Sorry.
about onNewIntent:
In fact there is a very strange problem: if I launch my application
from Eclipse, the mechanism will not work, but if I shutdown my
emulator then relauch emulat
On Aug 28, 3:42 pm, hackbod <[EMAIL PROTECTED]> wrote:
> In addition, you can use "adb dumpsys activity" to see the current
> state of the activity stack to try to diagnose what is going on in
> your application.
Sorry this should be "adb shell dumpsys activity"
--~--~-~--~~-
Hi Guillaume, there is really not enough information here to help
you. The onNewIntent() and onRestoreInstanceState() methods do
generally work, they are used in many places. You'll need to be more
specific about what you are doing to be able to get help. It also can
be useful to include the ou
Another lifecycle problem: onRestoreInstanteState is never called when
I relaunch my activity after pressing HOME (and the onCreate is not
called so the activity hasn't been recreated).
On Aug 28, 1:38 pm, Guillaume Perrot <[EMAIL PROTECTED]> wrote:
> In M5 I used notifications with intents (with
6 matches
Mail list logo
