I have to admit: I haven't followed your whole discussion because
you've given a very small amount of sample code.  I see that you're
trying to launch with an intent, but don't see why it could include
problems.

So if you want a comprehensive answer, please make up a small sample
project and put it somewhere: I'll try to investigate.

Given what you've said, I can try to shine some light with the
information I know up to this point.

You think that this code is weird:

(in onCreate, or some main thread method..)

    ctx.startActivity(intent);
    Thread.sleep(2000);

     ctx.startActivity(intent);  //!! investigating a weird bug

I would suspect that this would only fire a single intent: intents
will not start until that method has returned (message processing will
happen on that thread), and identical intents will be identified.
However, it *is* strange that if you only call startActivity once you
don't get anything happening.

I don't know if this just a simple mistake, or something going on in
the framework (I want to say a simple mistake, just because as the
platform gets older that code has fewer bugs..).  However, if you can
create a reproducible project, I'd be happy to try to find out what's
going on.

Kris

On Mon, Apr 8, 2013 at 11:28 AM, plnelson <[email protected]> wrote:
> I appreciate everyone's efforts in making suggestions, but this has clearly
> stumped everyone, both here and on Stack Overflow.
>
> Is there a support/bugs forum read by actual Google/Android engineers I can
> ask a question like this on?    Or is there a any documentation on the
> internal steps taken between startActivity and when the target activity Life
> Cycle steps begin?
>
> Right now I feel like launching an activity in Android is like putting a
> message in a bottle and throwing it in the ocean - IF it arrives at the
> other end then great.   But if it doesn't then there's no visibility or
> control over why.  We can try different bottles -  whiskey bottles or
> ketchup bottles -  or low tide or high tide -  but it seems like it's all
> guesswork.
>
>
> --
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to [email protected]
> 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
> ---
> You received this message because you are subscribed to the Google Groups
> "Android Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
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
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to