Is there a way to get an instance of the activity that has called the currently running activity from the intent object that has been passed to it? eg. if A has called B, I would like to retrieve A's instance from the intent in B's onCreate method. As Activity is not Serializable i am not able to pass the instance in the extras bundle.
View 1 Replies
I 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 RelatedI'm having difficulties handling multiple instances of my root (main) activity for my application. My app in question has an intent filter in place to launch my application when opening an email attatchment from the "Email" app. My problem is if I launch my application first through the the android applications screen and then launch my application via opening the Email attachment it creates two instances of my root activity. steps: Launch root activity A, press home Open email attachment, intent filter triggers launches root activity A Is it possible when opening the Email attachment that when the OS tries to launch my application it detects there is already an instance of it running and use that or remove/clear that instance?
View 1 Replies View RelatedI have a bunch of tab activities (which I implemented myself, didn't want to use the tabviews with activities inside them), so It's basically 5 activities calling each other every time the user clicks on the tabs displayed as a row of LinearLayouts at the bottom of the screen.
The thing is that the way I do it now, everytime the user jumps from one activity to another, a new activity is created and launched. Of course, I can see I'm wasting resources this way. So what I would like to do is to create every activity only once; and then if the user wants to go back to the previous (or any one that was already created and is probably paused) just check on some kind of list or array to see if the activity can be recovered and only in the case it can't; to lauch a new one.
My question is, how can I check this? should I save the intents? and how to recover the activities afterwards? I'm kind of new with java.
Is there any way to get the instance of a launched activity(or any view in that activity )of a application in another application.
View 1 Replies View RelatedWe all know that hitting the back button on the device doesn't kill the application, it merely finishes (destroys) the activity running on the foreground.
Well I have come across some code which helps me capture the back button signal so that I cannot exit the application. The only way to exit it in such cases is to press the home key.
Now this situation presents me with a unique disadvantage! The inability to kill finish the application on a time of my own choosing allows the application to keep running in the background like nothing has changed.
So in such cases is the task manager my only friend or is there a way for me to otherwise kill this application?
Is it possible to create/push-onto-stack a new Activity of the same main Activity in an Android application with an argument passed to the Activities constructor? Specifically from a Dialog object...
View 1 Replies View RelatedMy app consists of an Activity and a service that runs in the background. The service periodically checks a website for an alarm condition. When the service detects the alarm, it should put a user notification into the status bar. If the user clicks the notification, it should display the app's activity. If the activity is already running, that activity should become visible. If the activity is not currently running, it should be created.
However the notification created by my service *always* creates a new instance of the activity, whether the activity is currently running or not. How do I get the desirable behavior?
Here is my service pseudo-code:
CODE:...............
I'm working to finish a small application, but I'm having problems seeing what combination of activity attributes and intent flags I need to achieve my intended application design. Trying my best not to describe the app in minute detail, here's the basic operation (I've supplied screenshots in the hope it makes sense easily): Users have a garden which contains flowers (GardenActivity).
http://www.tomgibara.com/images/daisy/garden/hut_screen.jpg
They can tap on a garden to see details of flowers (FlowerActivity)
http://www.tomgibara.com/images/daisy/garden/flower_screen.jpg
When flowers are fully grown a notification provided, tapping on the notification displays the garden containing the flower.
http://www.tomgibara.com/images/daisy/garden/notify_screen.jpg
Users can also use the GardenActivity as a picker to choose flowers to "exhibit" (ConfigureActivity)
http://www.tomgibara.com/images/daisy/garden/planting_screen.jpg
I want the app to operate so that if the user already has a GardenActivity somewhere in the stack (whether it's at the top, or underneath a FlowerActivity) the notification will alert the user by bringing that activity to the front (clearing any FlowerActivity that may be above it). I've tried using the FLAG_ACTIVITY_NEW_TASK | FLAG_ACTIVITY_CLEAR_TOP combination (without changing any activity launch modes) on the notification's pending intent, but it still launches a new GardenActivity, even if one is already available.
I've also tried using android:launchMode="singleTask" on GardenActivity. The notifications then seem to work correctly, but it prevents GardenActivity from returning any result back to ConfigureActivity.
I'm writing a bitmap editor and I'm trying to write an autosave feature. When onPause is called, I write the application state to an autosave file. As this takes between 0.1s and 1.5s, I've been advised this IO operation be performed in a background thread.
In the onCreate method of my activity, I check to see if the autosave file exists and, if it does, I open it.
Are there any scenarios I have to consider where the user can somehow leave the activity, the autosave thread starts and the user can return to the activity before the thread has finished? If so, how can I detect this and wait for the thread to finish before I check the state of the autosave file?
I was going to make it that, when the user backs out of my activity, they're asked to wait a second while the data is saved. This seems OK, but I can't do this when my activity is interrupted by something like a phone call.
Also, I'm a bit confused about how multiple versions of the same activity can be started as this makes dealing with autosaving more complex. Is there a way to make sure only one instance of my activity is allowed to run at a time?
Application (non-wanted) behavior - application is started, some text is put into text-box and notification is created through button action. user "clicks" the home button, application is "minimized", notification is available in bar user selects the notification and the application is "maximized"
BUT - instead of the original instance, new instance is started (e.g. in the newest instance is missing the original text; when the latest instance is closed there is still the original instance with original text ) .
The code of the notification method
CODE:.....
I have also in the manifest xml file following tag android:launchMode="singleTask"
But it is still the same...The main problem is double/triple initialization of the application, i know that there are other means to preserve the values in resumed applications. Also it is needed that the applications stays running in background as the main functionality is the streaming of internet radio.
What is missing in the code ? What kind of information from my side is missing for to troubleshoot the issue ?
I've got an android app that pulls a random 20 questions (rows) as a cursor from a SQLite DB and loops through all the questions to ask the user all 20 questions.
Is there some way to save the cursor's state/location when the activity is paused or stopped so that when the activity resumes the cursor is restored and in the same position as it was when the activity was paused/stopped?
Before asking my doubt, let me clarify my understanding of allowTaskReparenting...
Suppose there exists a Task (say Task 1) and this task has an activity (say Activity 1) which wants to call my Activity (say Activity 2). Let my activity (activity 2) set the attribute allowTaskReparenting to true and let my activity have a specific taskAffinity(affinity1). When Activity1 calls my activity (activity2), my activity becomes part of the task1. But suppose another task (task2) is already present/created with the same taskAffinity as mine (affinity1) and an activity in that task (say activity3) tries to start my activity, my activity gets re- parented to task2.
Not sure if i was clear enough. If i were to rephrase my words...
If my activity has allowTaskReparenting set to true and an instance of my activity is already present in task1. If task2 with the same task affinity as my activity tries to start my activity, the EXISTING activity gets re-parented from task1 to task2.
My quesions:
(1) Is my understanding correct ?
(2) If I am correct then a single instance of my activity gets shifted from task1 to task2. So 2 activity objects of my activity are NOT created.
I'm using an intent-filter on URLs for my activity:
CODE:...............
the launchMode attribute is set to "singleTop", but it looks like a new activity is created every time I click a matching url. I thought that if the activity is already alive somewhere, it would simply be brought to the front of my activity stack?
I tried this on the emulator/device, same behavior, a new activity instance is always created.
I have two activities. A and B. A starts B. Both are running in the screen and both are visible. Say now B is visible.
On a special key press, I want to bring the A to the front and make it active. The problem I am facing is when the special key is pressed, another instance of A is launched and the new instance is brought to the front.
But I want the original A to come to the front. I want to make this change in the framework layer rather than application specific by using the singleInstance theme in the launchMode in AndroidManifest file.
Please help me in this regard as this is really urgent for me. Any inputs will be really valuable for me.
I have attached a menu to my TabActivity, and when a menu item is selected, I would like to do something different based on which view is being currently displayed in the TabHost.
int getCurrentTab() returns me the id of the current tab... but from that int how can I get the instance of the activity running?
I also tried getCurrentView(), getCurrentTabView(), but these return things I can't seem to cast to the class of the current activity.
I am using an Application object to store app-wide instance data--data that I need to remain in existence for the entire lifetime of the app, so the Application class seems like the proper place to put it. I have just finished reading this thread http://groups.google.com/group/android-developers/browse_thread/threa... that goes into pretty good detail and receives confirmation from Googler hackbod as to how the Application class performs--and from that info it seems this strange behavior I am receiving should not be happening...
Basically, every once in a while when I resume my app in any of its Activities (it is still running in memory so onCreate is not called) I get NullPointerExceptions because instance variables in my Application class are returning null when I request them from my Activity (via a getter method in my custom Application class). It seems as if sometimes Android saves the states of my Activities but deletes all my instance variable data... This can't be an Android problem--there must be something wrong with my code.
Has anyone else ever ran into an issue of this kind? Any ideas as to what may be causing this? I'm not going to post my code here as that won't help anyone, but hopefully someone can point me in some helpful directions.
1) I dont want to re-create activity once it is created in order to show. How can I do this ? like showing activity from back stack whenver thers a call for it. (It might appear at any index in back stack.)
View 1 Replies View RelatedI have been in problem of the Activity life-cycle. All though i read lots of docs on it put on getting clear picture on it. I have Activity A. In that activity I have menu options. If we click any option it opens the respective activity like if i click on 2nd button it opens Activity B Now again Activity B has same options into it. When user clicks on 1st button then i need to go back to activity A. So using this. Intent intent = new Intent().setClass(context, Articles.class); startActivity(intent); So always it starts new instance of activity and fetch data from DB. I want something like Activity A can be resumed back as it was.
View 6 Replies View RelatedI have a widget that contains 4 buttons to show 4 stock prices, each of them will launch into the same activity Quote.class to show stock details. In onUpdate(), it will set up the pendingIntent with extras with stock symbol. After I hit button A, it goes to Quote activity that shows stock A. Then I hit the BACK button to the homescreen, Quote activity calls onDestroy() and when I hit button B, stock B will show properly. However, when i hit HOME button after it shows stock A, the Quote activity only calls onStop without calling onDestroy(), then as i hit button B, it will call onStart() and it shows the same instance that shows stock A.
CODE:............
Originally I thought adding a flag in the Intent should solve this problem. But I have tried
i.setFlags(Intent.FLAG_ACTIVITY_MULTIPLE_TASK or FLAG_ACTIVITY_NEW_TASK or FLAG_ACTIVITY_NO_HISTORY), none of them makes any difference.
So is there any ways to make it work? How can i remove the history stack from HOME button? How can I call onCreate in Quote activity and get new extras when i hit button B?
I'm trying to figure out the correct way to create an AsyncTask to retrieve some data from the internet and then to take that data and bundle it up in an Intent and pass it to a new activity(A list display). So in the first activity I just have an EditText and Button. In the event of an OnClick the task should be called and when it is finished the data should be bundled inside an Intent and passed to the next Activity. The problem is when I take the results from onPostExecute and set them to an instance variable of the main activity, that instance variable is still null when the task is complete. Here is the barebones version of the code:
CODE:...........
When I debug the application I see onPostExecute does contain a valid PlacesList full of results, so why is the instance variable places set to null after the task is executed? I am going about "returning data" from an AsyncTask incorrectly?
My application has 2 activities. The main activity will create the "child" activity through startActivityForResult((...). When the child activity needs to exit, it calls setResult(..) and finish(). Child activity will start and exit multiple time upon user selection. The activity are start and exit as expected and onAcitivtyResult(..) also got invoked.
However, I found a problem with child activity, when the child activity was created the second time ( Main activity called startActivityForResult(...) upon some user event ), a new instance of child activity was created, but the displayed is the FIRST instance child activity! ( so any state in second instance of child activity was not accessible ). The onKey(...) was always go to first instance of child activity. Make things more interesting, the getInstanceCount () returns 3.
I have checked the code and no where holds the first instance of child activity which should be garbage collected after finish().
Is there a way to prevent the user of opening more than one instance of my application?
For example: User clicks on App and opens it. The user clicks on the home button. (the app is still running in the background) The user clicks on (not the menu button, but the button above it in the homescreen), and then opens the application again. Does it open the same instance, or does it create another one? If it does create another one, how can I prevent it from creating another one, and just opening the existing instance?
I have two activities.A and B. A starts B.Both are running in the screen and both are visible. Say now B is visible.
On a special key press, I want to bring the A to the front and make it active. The problem I am facing is when the special key is pressed, another instance of A is launched and the new instance is brought to the front.
But I want the original A to come to the front. I want to make this change in the framework layer rather than application specific by using the singleInstance theme in the launchMode in AndroidManifest file.
Is there a way to know if there is an instance of your widget currently on the homescreen? I always end up using variables that change state with onUpdate() and onDeleted() calls, but that obviously that isn't effective in every scenario.
View 9 Replies View RelatedI have referred the example given on: http://goo.gl/1uxXv , But it is not showing the exact DatePicker dialog as given in the book example, what i should do to display the same dialog box or Calendar instance in my application ?
View 4 Replies View RelatedIm creating a mail application, where i need to start a service instance for every account, which will check for the new mails for that account. Now my problem is that i want to identify how my service i have created so far (by calling startService()). And also i want to stop a specific instance of service. I know that calling stopService() will stop all the instances of that service. Is there any work around to it.
View 2 Replies View RelatedI am trying to do the following.
I have an Image viewer where in the user picks an Image from within the gallery. The uri to that selected Image is available to me. Now, I want to use this URI information and send it as a file over a socket using FileInputStream. Is this a valid syntax to perform the above action?
CODE:..............
I'm trying to obtain an instance of ServiceState in my Activity. But how am i supposed to do this? There is no static method to obtain an instance or any method on any service that returns an ServiceState instance.
There is the TelephonyManager.listen() call. But i want to get the ServiceState instance when i want, not when android calls my listener because something changed.
The documentation of ServiceState can be found here: http://developer.android.com/reference/android/telephony/ServiceState.html
I need to save some state when the user leaves my game during game play. Saving the state doesn't seem to be an issue, but I can't figure out how to restore it. The onCreate function isn't called when the Activity is resumed (only when it is first created), so I can't get my state back there. Logically, I would use onRestoreInstanceState, but it isn't being called.
CODE:..........
I see log output from onSaveInstanceState, onResume, onCreate, etc, but I never see a log message from onRestoreInstanceState and savedState is always null. Why isn't onRestoreInstanceState being called, and is there another way to get my state back?