The order is:
A: startActivityForResult( B ) B: <dostuff>, call finish() A: onCreate <---- what's this all about A: onActivityResult
This happens for a tiny minority of users. I havn't been able to reproduce or find any common elements. A is the launch activity.
CODE:..............
View 7 Replies
I have an application, which (for the sake of simplicity) has two types of activities - Overview and DetailView. The Overview activity shows a list of steps and allows the user to start a DetailView activity corresponding to the step chosen.
In the DetailView activity, the user can start another Overview, which shows different steps than the ones in the parent of the current DetailView.
In the Overview, DetailView is started by using startActivityForResult (). In the DetailView, when the user decides to start a second Overview, I call setResult () and finish () and then start the new Overview. In this scenario, onActivityResult () and finishFromChild () do not fire. Instead, they fire when the parent finishes (?).
Code from Overview:
CODE:....
Code from DetailView:
CODE:..........................
I have a flow A->B->C->D where A desires some information that is obtained by D. B, C, and D propagate the data back through the flow using setResult(RESULT_OK, data) and finish(). All intents in A, B, and C are started with startActivityForResult. However, if B is reclaimed by Android and forced to call onCreate again after C finishes onActivityResult in B is never called and the data never makes it back to A. Is there a way I can be sure that onActivityResult will be called?
View 5 Replies View RelatedI have a parent activity, and a child activity that extends the parent activity. When the parent starts the child activity,
Which onCreate gets executed first? The child's or parent's?
There is a particular variable I am setting in the Child activity's onCreate method, and right now, it looks like it takes a while to get to the Child activity's onCreate, and so the methods in the Parent are reporting an empty variable. Whereas when I make the Parent sleep for a while, it reports the correct variable.
CODE:............
So, basically, even after the Parent starts the Child, it still returns "Parent Value", but when I have the thread sleep, it return "Child Value".
I have faced with issue about startActivityForResult() and onActivityResult(). If child activity started by the startActivityForResult() exit by unexpected exception the onActivityResult() is not called and I have no any ideas how can I handle this to get application working in a fail-safe manner ?
When my code runs child activity with startActivityForResult() it awaits until onActivityResult() will be invoked to get working further, but onActivityResult() is not calling and my code is "hang- up" (logically).
So the question is how can I handle all possible ways the child activity is finished (normally and by unexpected exception) to get fail-safe code ?
I have check the documentation for this issue but have found nothing relating issue.
I launch my TestWebView activity. After my web page is loaded, I put the app in the background by pressing the Home key. Then I bring the TestWebActivity back to the foreground. Unexpectedly, TestWebView's onCreate() is called when I bring the activity to the foreground. But onDestroy is never called. This same thing happens every time I tested. It appears the old TestWebView was not completely killed so there are possibly duplicate web clients running.
My code: .....
In my android app I call the voice recognition in my onCreate method of my startup activity. I have made it a preference to start up with the voice control or not. However, the app takes about 5-7 seconds to load when voice recognition is on. When it is off, the app starts almost instantly. Below is sample code, I have added Free_Form, max_results 1, and a custom prompt to mine.Why would calling the normal android speech recognition take sooo long to load in my OnCreate method?
View 1 Replies View RelatedI have a problem with the method "onActivityResult".
I create a new Activity from my main activity:
CODE:.........
The new Activity is ended like this:
CODE:.............
But the Method onActivityResult seem to be not called
CODE:................
I'll be brief. I have an application with the following Activities Schema:
A (ActivityGroup) | |__
B (Activity Group) | | | |__
C (Activity) | |__ ... (Other Activities) | |__
D (ListActivity) | | | |__
ListView with a custom adapter with two buttons per row
All the Activities shown on the "diagram" are displayed and visible in real time while the application is being executed.
I'm pushing new list elements from C to the ListView in D. And by clicking each row's buttons I'm trying to edit the data of the row by means of a dialog. The problem is when, in the dialog activity, I perform the setResult() and finish(); the D's onActivityResult() is never called, and I do not know why.
I am updating some code from 1.1 to run with the new SDK 1.5. I noticed that onActivityResult is being called before OnRestart.
If Activity A calls activity B. Activity A goes to onPause(), then onStop(). Activity B goes on... finishes and returns.
Activity A starts at onActivityResultf(). So if you try to make a clean exit with onStop(), it will cause nullPointers when it comes back.
OnActivityResult is giving me major headaches. My little game has a title / menu screen. Upon clicking "new game" an Activity is launched which creates a SurfaceView for my game world.
When playing, the player can enter buildings in the game world. Upon entering a building I launch the activity for that particular building from my SurfaveView.
Here is an example:
CODE:............
mMap is the SurfaceView. I'm passing a bundle containing the state of the player. In onActivityResult I grab the bundle returned by the store activity and update the player state.
CODE:................
mSavedPlayer is later used to set the new player state.
All the above works generally
I can enter stores, buy stuff, leave and the player is updated correctly.
The problem manifests when I press the Home button (or someyimes back button) and onDestroy gets called. My onDestroy method does nothing besides call super.onDestroy();
After onDestroy() gets called onActivityResult no longer gets called.
So:
1) I play the game, everthing works great.
2) I press home and ondestroy is called
3) relaunch my game via launcher icon
4) Resume game. I can still enter and leave stores but onActivityResult is no longer called.
Here is some logcat output. I'm logging each time I enter a relevant method.
CODE:................................
I have the following issue. I am starting a recognizer intent activity in order to detect speech using the "startActivityForResult" method. I have also an "onActivityResult" method listening for results from the recognizer activity. It works and it detects my speech. The problem is that it is only called when everything is ok or when i cancel the operation, but it is not called if it doesn't find a matching text "RecognizerIntent.RESULT_NO_MATCH" or in the rest of wrong cases "RecognizerIntent.RESULT_........" What is happening? Application is Android 2.1 and I have tested on a Android 2.2 device.
View 1 Replies View RelatedI have a TabActivity with 3 tabs, each tab started an activity and I realise when a tab is clicked onResume is call. If I have onCreate, when app start it will launch onCreate and then onResume immediately.So, I can just get ride of onCreate in this case?
View 2 Replies View RelatedI make 'hello world' app :-) and wrote a Log code in onCreate. and then give "android.intent.category.DEFAULT" and "android.intent.category.HOME"
This situation appears emulator(1.5, 2.0, 2.1). but HTC hero(1.5, original htc rom) didn't! it just call one time! Which is normal? and If calling twice is normal, why are they call twice?
Following is the example of tabs with intent data.
While debugging i found that always when first tab we add in tab host in our case following tab
CODE:................
oncreate method of "List1" intent get called regardless it is our current tab or not even if if i define tab2 as a current tab how to fix this ?
CODE:..........................
I have some code in the onCreate method an Activity and noticed that it is being called three times. Is it normal behaviour?
View 1 Replies View RelatedI got my hands on Android which is really fun. But at some point I don't seem to understand the concept. I've got a Main class which reads like this:
CODE:....
In the onCreate(...) I set the layout to setContentView(R.layout.main); and add an OnTouchEvent Listener to the sole View in main.xml: myView.setOnTouchListener(new OnTouchListener() {@Override public boolean onTouch(View v, MotionEvent event){...
As you can see I also implemented a SensorEventListener which is used if required. All works fine so far.
But my problem is this (at this point my misunderstanding kicks in): whenever I rotate the device the onCreate(), onStart() etc. methods are called, causing my app to act as if it just started. Furthermore, I feel unable to implement an onSizeChanged(int w, int h, int oldw, int oldh) { ... } Listener.
Can anyone please explain where my error in reasoning is? I am working on a tiny app which is more or less done, except for the just mentioned bug(s). Maybe I got it all wrong but it does what it is supposed to do (i.e. sending touch positions and accelerometer data over the network via UDP).
I have a main screen with buttons to launch other subactivities. I have to press back button each time to go back to the main screen of my application. How do I finish a child activity and automatically return from the caller?
View 5 Replies View RelatedCan someone tell if why when starting an activity with startActivity(intent) , calling getParent() in onCreate() of the new created activity returns a nul ?
Also how could I obtain the parent of an activity created in such a way ? Can a reference of the activity below the current activity in the activity stack be obtained ?
Can you please tell me if you know how to get the Andorid unit test instrementation to call my activity's onActivityResult()?
I can't find anything here: http://code.google.com/android/reference/android/app/Instrumentation.
How can I make sure I only retain one copy of an activity on the stack when called from non-activity? When called from an activity I can just add the FLAG_ACTIVITY_REORDER_TO_FRONT flag to the Intent, but how can I do this from e.g. a widget or a notification?
View 1 Replies View RelatedI have a Contact Activity which is derived from ListActivity, which displays list of contacts, and on click of item, a new Activity Message Activity derived from ListActivity is initialized.Now I know, I can pack some information in Bundle and pass it before creating activity, but is there a way I can get instance of "ContactActivity" in onCreate method of "MessageActivity"?
View 1 Replies View RelatedAs we know, startActivityForResult() used to get a result for a task from parent activity. Here when we click the setResult(). It returns the result to the parent Activity.
Child Activity means it should maintain the persistent state. That is when the users clicks a button on the child activity. It do not finishes that activity and show the Parent Activity. And again i may go to the child activity from parent activity. If the child does not exists it starts a new child activity else it should show the existing child activity with persistent content.
Simply said, my parent Activity starts a new Child Activity. Now both Activities should be alive. How to call the Parent Activity without finishing the child Activity(in other words, How to BringtoFront the parent Activity)? For this scenario,
you can not use startActivity(). Because it creates a new Activity Instance. Not Existing Parent Activity
you can not use startActivityForResult(). Because it finishes the child Activity Instance.
I'm opening an Activity using this:
startActivity(new Intent(Parent.this, Child.class)); And on the child, I have this code on the onCreate function (the if contains more than just true, of course): public void onCreate(Bundle savedInstanceState) {super.onCreate(savedInstanceState); if (true) { AlertDialog.Builder builder = new AlertDialog.Builder(this); builder.setPositiveButton("OK", null); builder.setTitle("Error"); builder.setMessage("Connection error, please try later.") .show(); finishActivity(0); return;}}
Why is the activity not closing? I get the alert box, but then I have to tap the "back" button to go back.
I understand that Android Activities have specific lifecycles and that onCreate should be overridden and used for initialization, but what exactly happens in the constructor? Are there any cases when you could/should override the Activity constructor as well, or should you never touch it?
I'm assuming that the constructor should never be used because references to Activities aren't cleaned up entirely (thus hampering the garbage collector) and that onDestroy is there for that purpose. Is this correct?
I know that network activity and expensive operations should not be done on the ui thread, but what about database activity?
I have an activity that, when started, I query an sqlite database and dynamically populate rows in a tablelayout with an inflator. I do this all in the oncreate() method. Should this be done in a separate thread?
My child activity X is called from Parent activity P through startActivity(intent). I want to close P when X called its finish() method. I override a method finishFromChild(Activity child) in P and called finish() in it. But this functions (finishFromChild(Activity child)) is not being called after X finish() Is it a known bug or I am missing some thing? I googled and also searched the groups but no help.
An alternative could be... using StartActivityForResult() and a "fake" onActivityResult, where I can finish the parent activity, but this way is quite bad, i think...
I prefer the first one, if it would work....
Any idea why this doesn't create an activity that looks like a popup instead of an activity that completely fills the screen?
CODE:.............
I assumed that I only needed to set the layout height and layout width to something other than "fill_parent", but it still shows up as a black screen that completely fills the screen.
Ultimately, I simply want to create a popup, but I do not want to use an AlertDialog. Is this possible?
When we want to pass data from an activity to a sub activity we use the is there any event handler that handles this?
View 1 Replies View RelatedAndroid will call onCreate() of my activity whenever it is launched.
In the onCreate() of my activity can I tell what intent launches my activity?