You may need to give more information on what you are doing. If the flicker you are seeing is happening when you launch your app from the home screen, this is not atually your app but a preview of it based on its theme and such in the manifest. If you can't make this match what will ultimately run, you can set the theme to be something like a dialog so the system won't show it (since without the content a dialog won't look anything like what the user sees). But if you do that, it will feel like the app takes slower to launch. Best is to have the manifest set up so that the preview looks close to what they see so the user can see this while the app is launching.
On Oct 13, 6:31 am, Anm <[EMAIL PROTECTED]> wrote: > Hmmm.. I tested it again and the startActivity()/finish() seems to be > working now. > > It may have been an issue with an exception that was thrown in the > child activity during initialization. I would launch the app, briefly > see the entry-point activity, get a first draw of the child, and then > a error dialog. When I clicked past the error dialog, I would see the > entry-point activity again, then the child activity, then another > error dialog that would close the app. I didn't commit my code at > that point and don't remember specifics. > > But slightly related... > Is there anyway to prevent the brief view of the redirecting > activity's UI? It seems silly to push through start/resume/pause/stop > when the app has already requested a new startActivity() or finish() > from onCreate(). --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
