starting the same activity....

by sdphil » Sat, 24 Apr 2010 05:53:54 GMT

Sponsored Links
 I have a weird issue, and I'll describe it in somewhat abstract terms
in the hopes that someone can see something I'm obviously doing wrong.

I have an activity with some data on it (call it Activity A1).  The
user hits a button and I launch another instance of that same
activity, but with different data (call that Activity A2).  Now, I hit
the "back" button (hardware) and instead of showing the data from A1,
it shows the data from A2.  If I force an orientation change, it shows
the data from A1 correctly.

I am not using static data anywhere and I am using the default onPause
and onResume.  It's almost as if Android is reusing the GUI controls
even though it's a different instance of the activity.




starting the same activity....

by krox » Sun, 25 Apr 2010 04:09:15 GMT


Hmm that sounds weird, I just created a testApp and it worked as
expected (that is it did not update the UI-elements in A1 when I
updated them in A2). Would you mind posting the sourcecode?



Sponsored Links

Other Threads

1. Activity accidentally re-loading with AdMob

I have the following issue, where I load an ad with AdMob on my home screen. 
While it is busy loading the user can navigate away to another activity. If 
the ad didn't finish loading before then, it automatically takes the user 
back to the home screen from it's current activity. 

So how do I either block the user to navigate away while the ad is loading 
(though I don't really want to do that) OR how do I stop the ad from loading 
if the user navigates away?

Basically, how can I improve the user experience and not have them have to 
wait for the ad to finish loading, but still have the ad present at a later 

Much appreciate any advice!


2. check before publish with LVL, the Application Licensing

We have finished implementation with LVL, and about ready to publish.
Previously, we developed the app with separated publish account so
that the whole team can get access to test environment. Now, we have
done that, we created a build with package name and key with our
official publish account info.

I side-loaded the app to device, when app starts, it received the
"ERROR_NOT_MARKET_MANAGED" response. I am bit confused why I receive
this. My package name is the same, my version number is updated, why I
get this response from server?

How could I run a check before publishing on Android Market? What do I
need to in order to get test response? We have already had a paid app
in the market, I am pretty careful doing anything that might mess up
with our published app.

Google documentation isn't that clear. :-(


3. [WTA] remote flash + install custom rom

4. BBM ke android ?

5. (Device or resource busy)

6. Bluetooth external touchpad interaction

7. Android Build dont work on Nexus S