There are some process manage application that allows user stop any running aplication by a button pressing. I want to know, in these situations, the onStop and onDestroy methods will always get executed?
View 6 Replies
Each time I switch the orientation of the device, onStop() and onDestroy() are called. They are also called when I close the Avtivity (dismiss()), and when I press 'back' key. In onStop() or onDestroy() methods : how can I know how I can here ? I'd like to run some code when I close the Activity (back button), but not if I change screen orientation
View 7 Replies View Relatedi`ve got some problems with finish() method. I expect what after calling on my Activity finish() method onStop and onDestroy must be triggered(or am wrong??), in majority of examples they are, but Scenario: - reboot phone - launch activity - invoke finish() onPause is triggered but afterwards they are no calls to onStop() and onDestroy()I`ve noticed, that those calls are triggered after launching any other activity.
View 7 Replies View RelatedI wonder if I could save a value (in my program its an index) so I could call it back when the program launches back again (even if the program destroyed) and the user could start from where finish.
View 2 Replies View RelatedI need be able to tell if Activity.onStop() was called because my application is moving to a new activity, or if it was closed because the user pressed the "Home" key or hit the back button from the bottom of the activity stack.The reason is because I need to know when it is appropriate to shut off music that is playing in my application (A game). There is nothing more annoying than hitting home and having something playing music in the background.However, Activity.OnStop() is called for each activity change, and I don't want to suspend music when moving between multiple activities in my app. I just can't find a way to differentiate between going home and going to a internal activity.Am I perhaps hooking into the wrong events?
View 3 Replies View RelatedI'm saving the state of my activities for orientation change support, it works well. Sometimes I have a dialog open though and need to save its state as well. My dialog's onStop() method doesn't seem to get called when I change orientation. Where would get notified inside the Dialog that we're being destroyed, so I can save its state?
View 3 Replies View RelatedThe docs say "The onStart() and onStop() methods can be called multiple times, as the activity alternates between being visible and hidden to the user"When I press the back button an it will go back to the previous activity which totally covers the old one.What is going on here?
View 1 Replies View RelatedI have a problem with the activity lifecycle specifically on Nexus One (2.1 running on emulator works fine). If I just create a simple empty Activity with no special launchModes that logs the calls on the onStart and onStop methods, this is what I see: - launch app: onStart called; - home button: onStop NOT called; - launch app: onStart NOT called; - home button: onStop NOT called: and so on. Sometimes if I press the back button then the onStop is not called, but the when i launch the activity again the onStart is called and right after the onStop is called. Similar results with different launchModes. What is going on? Can anyone confirm this?
i found an android issue for the problem here: http://code.google.com/p/android/issues/detail?id=6094 and a similar thread here http://groups.google.com/group/android-developers/browse_thread/threa.
Every once in a while my activity gets restarted after it's destroyed instead of being created again. I.e. I see:
CODE:..........
instead of:
CODE:............
Looking back in my log I can see this happening periodically, but no apparent pattern to it. This certainly isn't in the state diagram, and needless to say this doesn't make for a happy app.
I added TextToSpeech to my app, following the guidelines in the following post:
http://android-developers.blogspot.com/2009/09/introduction-to-text-to-speech-in.html
and now my onDestroy is no longer called when the back button is pressed.
I filed a bug report regarding this: http://code.google.com/p/android/issues/detail?id=7674
Figured i should also ask here if someone else has seen this, and found a solution?
It seems that it is the intent that causes the problem, i.e. the following:
CODE:................
If I skip this intent, and just go ahead and create a tts-instance, it works fine.
Any clues to what is wrong with this intent?
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:................................
why onDestroy is being logged twice for the fragment class in the the following code when the orientation of the device changes. Its logged once for the activity class, but twice for the fragment.
Code:
public class ExampleActivity extends Activity {
protected String LOG_TAG = ExampleActivity.class.getSimpleName();
private FrameLayout mFragmentHolder;[code].....
I am seeing an issue where when I hit the "back" button, I get the onPause call, but it isn't followed by onStop and on Destroy. On most phones, I see this, but on one particular phone (Droid-X),
View 7 Replies View RelatedI have a mediaplayer object inside an activity that plays from mp3 files situated in the res/raw folder. The MediaPlayer.create(Context context, int resid) method is used to create and return a mediaPlayer object to play this track. What I have noticed is that when the activity is obscured by another activity and hence the "onStop()" method is called , the music continues to play. Can anyone explain why this occurs? I though that onStop would essentially freeze any actions taking place by objects associated with the activity, except for services etc
View 1 Replies View RelatedI have two activities. One loads all rows from a database, and the other saves to the database. When I have the second save in onStop and the first repull the data in onResume, they do it out of order (the first resumes and then the second saves). I managed to fix this by putting the saving data in onPause, but why was this happening? Was this the cleanest way to do it?
View 1 Replies View RelatedIn the Android Application Fundamentals it says that after the call to the onStart()-method of the activity lifecycle either the callback method Resume() or onStop() is called. In case of an "normal" Start of an activity the system calls onCreate(), onStart(), onResume().But does somebody know an example where onStart() - onStop() are executed one after another?
View 2 Replies View RelatedI have an application that is silencing the ringer while it is open, then when it closes it unsilences it. Currently I am doing these two things in OnStart and OnStop. The only problem (and it's a big one) is that when a phone call comes in, it stops my application (calling OnStop), then rings at its normal volume. Is there any way to get around this? I tried using onCreate and onDestroy, but I want to restore the original volume setting as soon as the program is closed, which onDestroy doesn't seem to do. 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 android-developers+unsubscribe@ googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
View 8 Replies View RelatedI'm having this strange issue where upon exiting a subactivity that is translucent (android:theme="@android: style/Theme.Translucent" ) the onStop() method doesn't appear to be called. have a TimerTask that runs and is supposed to be terminated when the subactivity ends in the onStop() method, but I'm instead left with an orphaned thread running in the background. It go particularly bad when I ran the subactivity several times. When I revert to no theme, the onStop() method is called and the activity behaves properly. Is there something I missed about how Translucent activities'lifecycles differ from standard activities?
View 4 Replies View RelatedJust like the title says, Is there a simple line of code I could add to onStop()that will simply stop any gps activity currently going on with my application?
View 1 Replies View RelatedI am running into an issue with the way my asynctasks are executed. Here's the problem code:
firstTask = new background().new FirstTask(context);
if(firstTask.execute().get().toString().equals("1"))
secondTask = new background().new SecondTask(context);
What I'm doing here is creating a new asynctask object, assigning it to firstTask and then executing it. I then want to fire off a separate asynctask when the first one is done and making sure it returns a success value (1 in this case). This works perfectly on Android 2.0 and up. However, I am testing with Android 1.5 and problems start popping up. The code above will run the first asynctask but doInBackground() is never called despite onPreExecute() being called. If I am to execute the first task without the get() method, doInBackground() is called and everything works as expected. Except now I do not have a way to determine if the first task completed successfully so that I can tell the second task to execute. Is it safe to assume that this is a bug with asynctask on Android 1.5? Especially since the API says that the get method has been implemented since API 3. Is there any way to fix this? Or another way to determine that the first task has finished?
I understand that the system may kill the activity without calling onDestroy(). Say I have a MediaPlayer that runs even when it's not visible, I would be releasing the player in onDestroy() method.Now, if the system decides to kill the activity after calling onPause() and never called onDestroy(), what does it mean for my MediaPlayer? Is it ever released? This is bigger problem for Camera since I think it requires to be released for other activities to use it.
View 1 Replies View RelatedI use AlarmManager to restart my service, code is:
CODE:........................
After 5 seconds, BootCompleteReceiver will startServcie(), but only see onStart() not onCreate() calls.
Is the way of destroying the service wrong? BootCompleteReceiver is written in AndroidManifest.xml
Testing onDestroy.
Q: does using a lot of RAM in one application always lead to onDestroy being called on Activities in other applications?
To try and figure this out I created two separately installed applications. The first just logs its lifecycle transitions and the second allocates a chunk of memory each time you press a button.
What I saw was the second application eventually suffered a fatal Out Of Memory Error force close. The onDestroy method was not called on the first logging application and when I switched back to it onResume was called.
My conclusion is that using a lot of memory in a single application will lead to a fatal Out Of Memory Error without onDestroy first being called on Activities in other applications. The documentation left me expecting an onDestroy on the logging application since the foreground application was trying to allocate more memory.
Does the above sound right? What's a good way to test the onCreate/ onDestroy lifecycle methods as they relate to low memory?
when writing a ContentProvider I have to implement the onCreate()-method, in which I establish my database connection. But to write the changes I made to the database I have to close the database on some point. Does something like a onDestroy()-method exist for ContentProviders or is there some intent I have to listen to, which is fired before killing my process?
View 5 Replies View RelatedWhen user presses BACK key, my activity's onDestroy is called and then it is killed. Is there a way (by overridding Activity.onKeyDown??) to simply put the activity into background without killing it? I want the BACK key to act like the HOME key (which doesn't kill my app), except I want to show the activity immediately below my activity.
View 7 Replies View RelatedA service is setup by an activity with startService(service_intent). This service is meant to run 24 hours a day. After some amount of time, 5 or 6 hours sometimes but its not predictable, the service is killed.In the database log, the destroyed message does not show up and the notification #1 is not cancelled. Android makes no attempt to restart the service. The database log will show the startup of the replacement service if I trigger it by visiting the activity. What can I do to keep this service running or at least get it restarted by android automatically?
View 6 Replies View RelatedI have an application with a single Activity implemented as a singleton (in the AndroidManifest). It implements a Listener I wrote. When the application is first run the Listener works fine. When I use the "home" button to minimize it, then open it again it's still fine.
But when I press the back button then run it again from the application icon, the Listener doesn't work fully. The code runs and the Listening methods are called as usual but none of the UI elements that are listening update. It requires a restart of the phone to get the listener working again after this point.
I know the "back" button doesn't really close the application, per se. But resetting the phone sure does! Is there a way to use the onDestroy() or similar method to call a function that actually closes the application? I'm asking because restarting the phone is the only way to get the listener back so I was hoping I could do that programmatic ally.
For example, my progress bar is a member variable of my Activity, but onCreate() I do "progressBar = (ProgressBar) findViewById(R.id.progress_bar);" Is this perhaps creating a separate instance of it or something?
If I override my main Activity's onDestroy() method in order to recycle a bitmap when the screen is rotated, should I call super.onDestroy() before or after myBitmap.recycle()? Does it matter?
View 1 Replies View RelatedI am working on a MVC implementation for Android (to be subsequently hosted on SF and/or GC).
It works like this:
Activity (View) <=> Application (Controller) <=> Data (Model) <=> Persistence (DB/Network etc)
The scenario is:
1. Activity launch (main/launcher)
2. Notifies Application about performing a data transaction
3. Upon receipt of data response, controller devices which Activity to launch (or update existing)
4. Application has overridden the method onConfigurationChange
Problem: When the orientation is changed, the Application is notified about onConfigurationChange but:
a) The "current" activity is Destroyed and recreated -- which is fine to some extent b) The new instance which is created is automatically => onCreate, onPause, onStop, onDestroy.... now that's catastrophic.
With following simple code (on clean, new android project):
CODE:..............................