Same problem with my app, but mine is not a main activity to do your
hack proposed.
The main problem is that when this happens passed parameters from
notification intent are ignored and activity starts with initial
parameters, like it was opened again during usual navigation...
Those intents are making me angry again and again :E
On Jan 12, 3:33 am, Torgny <torgny.bj...@gmail.com> wrote:
> I am trying to create a notification in a service to notify the user
> that the application's data has updated in the background. I want the
> application to resume when they click the notification. When I click
> the notification I get this message in DDMS:
>
> 01-11 16:16:10.574: WARN/ActivityManager(56): startActivity called
> from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for:
> Intent { comp={com.example/com.example.view.ExampleActivity} }
>
> This forces the activity to start even if it is already paused or
> stopped, so it never resumes, it just creates a new instance of it,
> overlapping everything, including service connections. If the
> application is already running, another copy of it starts on top of
> it. How do I make Android just resume the activity?
>
> Thankful for any help!
>
> Warm Regards,
> Torgny
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
