Android :: Activity State On Pressing Back And Home Button On Screen
May 6, 2009
Whenever I press the home button when Im in the root task of my application and when I click on the icon of my app again the state of my task (activity) is retained, but when i press the back button on the emulator and when I open my application its state is not retained. I want the state to be retained in both the scenarios.
In the mnifest I have given the below entries,
android:alwaysRetainTaskState="true" for the root activity
android:launchMode="singleTask" for the application
View 2 Replies
Jul 15, 2010
When i leave my app after pressing home button and then re launch it from menus it behaves in a strange way.Sometimes it launches the same activity on which i pressed home button.But sometimes it launches the first activity of my app. One reason for this could be that whenever system has memory shortage it clears any activities existing in But the strange thing is if i press back button from first activity it takes me back to the same activity on which i pressed home button and all other previous activities are also there(like if i press back button again previous activities also exist.)I haven't set any launching mode for any activity in my app(like single instance etc).What i don't need is that previous activities load on pressing back button on first activity.
View 2 Replies
View Related
Nov 13, 2010
This is difficult for me to diagnose because the Log doesn't provide the offending code line that indicates what caused it.Running the app in the Emulator seems to work OK until I press Home or Back from the Main Activity. Using Back between the activities in the program seems to work OK, it only fails at the Main. I don't have the app finished yet so I haven't loaded it to a device yet.The Log says there was a null pointer exception so I would like to find why.The log points to the android routines (and I don't appear to have the source for those routines in the emulator-most but not all and these are refering to those I can't access). The log gives up at one point and says "11 more".It would be nice to see the remaining 11 in the hopes that one of them points to the line in my code that caused the offense.I'm looking for ideas on ways to find the error and hopefully cure it.
View 2 Replies
View Related
Oct 24, 2009
I am having an issue related to home key . when i press home key all current activity gets hidden. but when i press the executable it again starts from the fisrt screen . I have overidden all methods nsaveInstaceState opPause onStop onResume
but there are still issues what is the right way to handle those conditions. When i am pressing home button i am storing the widgets state in database and when i again click the exectable i am checking the database state and starting the new Intent as saved when user presses the home button .Is it the right way to do that as i am facing the problem when user does the same and again presses the back button , there is already on intent available in stack of activity .
View 2 Replies
View Related
May 2, 2010
I have an Activity with a list that is bound to a ListAdapter reading data into a ArrayList from a database. All is well when the data is first loaded. While the Activity is open and the list is being displayed it is possible and likely that the data in the database will be updated by a service but the list does not reflect the changes because the ArrayList does not know about the changes. If the Activity is no longer in the foreground as would be the case if the user goes to the home screen and then is brought back to the foreground I would like for the Activity to not display what it did prior but rather reload the data using the ListAdapter the view is bound to. I think something needs to call finish() but I am not sure what.
This is what I have in the Activity.
CODE:.......................
View 1 Replies
View Related
Feb 27, 2010
I notice on my eris that when i am on a menu with a black background that if i hit my back (bottom button) a little firmly, right above the button on the lcd kind of changes colors. Like if you press your laptop screen, its only a little bit though. If you could, please try this and report back.
View 10 Replies
View Related
Sep 2, 2010
I have 3 activities in my app: Activity1 -> Activity2 -> Activity3. Inside Activity3, if the user presses Back, I would like to return to Activity2. In Activity3's onPause event, I added a finish() statement. That's probably not even necessary, but I wanted to make sure this Activity gets cleaned up. This works fine.
However, while in Activity3, if the user presses Home or starts a new app (through notification bar or some other means), I want both Activity3 and Activity2 to finish. If the user returns to this app, he should resume with Activity1.
I have figured out how to do one or the other, but I can't figure out how to handle both cases, if it's even possible. Can I trap the "Back" button in Activity3 and send a message back to Activity2 telling it not to finish()? It seems like the Activities follow the same lifecycle flow (Pause, Stop) regardless of what you do to send them to the background. Just to answer the question of why I want this behavior, imagine that Activity1 is a login screen, Activity2 is a selection screen, and Activity3 is a content screen. If I press Back from the content page, I want to be able to make a new selection. If I exit via any other means (Home, notification bar), I want the user to be "logged out".
View 2 Replies
View Related
Mar 30, 2010
I'm new to Android and just starting the very basics. I implement my custom button skin using .9.png images for norma/focus/pressed states. It works fine, but I noticed that after a pressed the focussed button it visually "lost" focus and draws the normal state frame. I planned to use different state images to highloght what button is selected right now, but it seems that it would not work. I noticed also that the same happens with the default LAF button. Is it OK, or it's just emulator issue? What the good workaroud can be used?
View 2 Replies
View Related
Mar 30, 2010
Whenever I am using any app and press the home button, the home screen blacks out for a few secs and it takes around 10 sec to get all the icons back and before I can start using my phone again. I am using a non rooted mytouch 3g.
This problem does not happen if I exit an app by pressing the back button. It becomes very annoying at times.
View 7 Replies
View Related
Mar 3, 2010
example scenario is: from login screen - main screen - then when i clicked a hide button the app will go to home screen, and when im going to click the app again the main screen would be called.
View 2 Replies
View Related
Mar 19, 2010
I created and binded a service in an activity and I would like to know how I can avoiding the android application to stop when I press the back button. When the back button is pressed the onDestroy method is called and I unbinded the service in this method. I try to prevent it by taking care of the back button event and manually call for onStop() method but it always called onDestroy after, why?
View 1 Replies
View Related
May 10, 2010
I've heard that pressing the back button will essentially cause the current Activity to finish(). Is this always the case? Seems like it would be with the way it pops the Activity off the stack.
The one situation I'm not so sure about is when the root Activity in a Task has back pressed. I'm currently experiencing a very weird effect, described as follows:
On loading my application, the first Activity is for initialization, and once it finishes, it calls my main Activity (a TabActivity). This first init activity has android:noHistory="true" set in the Manifest so pressing Back from my main Activity won't go back to that. It goes to the Launcher. When I click on my App in the Launcher a second time, the initialization activity loads again, and loads the main Activity when done. Almost immediately after, it loads a second instance of my main Activity. But ONLY after the Application has already been run once, and was exited by pressing BACK from the main Activity. It does it every subsequent time until I force quit the app or load a new version from the IDE.
Based on this, I am suspecting some kind of Activity instance is lying around and being reused, since it only happens on the second+ time I run the application (and exit with BACK -- using HOME just returns to the last state of the app, no big deal).
View 4 Replies
View Related
Feb 5, 2010
Can you please tell me how can my activity detect user pressing HOME key?
View 2 Replies
View Related
Dec 19, 2009
When I DL'd the GDE app, I accidentally set my stock droid "HOME" screen as the default screen when the popup box came up asking me to choose between stock Home and GDE. Now when I click on GDE and click the home button, it switches back to the stock Home screen. How to I switch the settings now to set the GDE app as the new home screen?
View 15 Replies
View Related
Jul 9, 2013
I upgraded my Galaxy S2 (Straight Talk) to CM10.
Now whenever I press the home button, it brings up CM10's home screen.
How do I bind ADW to the home button?
View 2 Replies
View Related
Mar 29, 2010
I just installed lock 2.0 and i was just adjusting the settings and now every time I'm in my phone and i touch the "Home" button it locks my phone instead of taking me back to my home screen! Is this normal? Did I accidental do it in the settings? HELP its driving me crazy
I'm on the new 2.1 leak if that matters
View 7 Replies
View Related
May 4, 2010
I have just got my hero back from RMA with a new screen. (the old one was fubar). But now the back button is bringing me the homescreen. And not the last screen. So if I browse my settings, and go 4 screens in. I want the back button to bring me to screen 3 (like it used to), and not to the home screen.
View 5 Replies
View Related
Sep 27, 2010
Motorola Droid 2.2 Froyo rooted Bugless Beast 0.5. Randomly (Maybe 2/5) when I press home from the browser, an application, ending a call, etc. All of my icons will disappear for 4-5 seconds. Please tell me if you know of a fix or anything about this problem, I've seen other topics about this but no solutions that worked.
View 9 Replies
View Related
Aug 8, 2010
When you're in the browser long pressing on the back button takes you straight to the history page, very useful.
View 1 Replies
View Related
Oct 9, 2010
I have a pattern unlock on my Samsung Galaxy S 19000. If I want to lock my screen manually I simply press the power button briefly which works fine. I now use a skin on my phone which doesn't allow for easy access to this power button so I'm wondering if there's an app that I can use to lock my phone screen without having to press the power button. I have looked at "lock 2.0", however, it seems to be more for actually unlocking the screen.
View 4 Replies
View Related
Oct 18, 2010
Has anyone seen a a onItemSelected not being called when using a spinner inside a listviewActivity. I have the code below Inside a listViewActivity. The spinner is shown on screen by pressing a button (not the spinner) which in turn calls performClick() on the spinner. When I select an item from the spinner the onItemSelected function is not called. Does anyone know why this might be? Code...
View 5 Replies
View Related
Apr 8, 2010
I am working on my App. in between i pressed the Home button on the device. my app will go to the background tasks. After that i long press the home button it will show my app as a persistent state. i.e where and what i had done in my app. But i click my app in the directory window it restarts my app. i want to do if my app is in the background tasks it will wake up else it will start. how to achieve that?
View 1 Replies
View Related
Mar 1, 2010
on intent when user press back button should exit from the application, how can i track back button and exit from the app?
View 2 Replies
View Related
Sep 20, 2010
I have noticed while working in the emulator that whenever i get out of my app via any method other than pressing the back button, my toggle button (if pressed) will have its state saved and return to that state when i return to the app. im guessing its because its value gets saved in a bundle and reloaded when i return. when i leave the app via the back button, this does not happen and the toggle is always off when i return. is there any way to get the value of the toggle back if the user leaves via the back button, without having to save the value in a db table? alternatively, if my apps notification is in the status bar, i can be confident that the toggle should always be selected, so if there is no way to save the state, is there a way to find out if my apps notification is currently being displayed? then it would be easy to just set the toggle each time via a quick check of the status bar.
View 1 Replies
View Related
Nov 8, 2010
I have an Android app with a splash screen.
This splash screen pre-loads data and when finished starts the application's main activity and finishes (through a finish() call).
This works quite well as long as the application is not totally killed. So, I can usually switch back and forth between different tasks as usual: when I leave the app from a sub activity and return soon after I will be presented with this sub activity.
Now, when I leave this sub activity and do some other stuff for a while inevitably this application process is killed by the OS.
No problem so far. Now I would expect Android, being unaware of my preloading (if the data was not preloaded it would just take longer or not display some fonts, but Android cannot be aware of the fact that I am doing preloading somewhere), to restore the sub activity from a Bundle. However the splash screen activity is started.
So, I say, that's fine then... the splash screen activity is after all the launcher / main activity. Now, the actual mystery I have is as follows.
When I press the back-button from this newly loaded splash screen I will be presented with the sub activity I left the application from before it got killed. I really don't understand this. Apparently Android DID save the sub activity's state (and its history stack) to be reloaded but instead of reloading it chose to start the splash screen instead, with this sub activity (I left the task earlier before it got killed) one step back on the activity stack.
Why does this happen?
When the process is not killed I can switch back to where I left off. When it's killed I cannot (yet still have the whole earlier history of that app restored). I know that Android has to load state etc. in the latter case, but that shouldn't be a problem and is performed automatically by default (according to the docs).
View 1 Replies
View Related
Mar 15, 2010
My question is about restoring complex activity related data when coming back to the activity using the "back" button". Activity A has a ListView which is connected to Array Adapter serving as its data source - this happens in on Create(). By default, if I move to activity B and press "back" to get back to activity A, does my list stay intact with all the data or do I just get visual "copy" of the screen but the data is lost? What can I do when more than activities are involved? Let's say activity A starts activity B which starts activity C and then I press "back" twice to get to A. How do I ensure the integrity of the A's data when it gets back to the foreground? Prefs Manager does not seem to handle complex object very intuitively.
View 2 Replies
View Related
Aug 4, 2010
I just got the vibrant about a week ago, and so far no major issues. Still fumbling around in the apps market for the good stuff. One thing I found annoying was having to press the power/unlock button and then swiping the screen to unlock the phone every time, is there anything in the market or some setting to avoid pressing the button and just swiping the screen or possibly using the touch buttons on the front of the phone then swiping?
View 2 Replies
View Related
Jul 4, 2010
This has been brought up before, but I was unable to find a satisfying answer. And I know it's a newbish question.
What is the difference between exiting an app with the back button compared to the home button? I am not talking about switching to the home screen, I am talking about a scenario when you want to exit an app. For example, you play a game, you're done - do you press home or back? Or, you're in the Facebook app and you want to exit to the homescreen - what do you press - back or home? At first, I thought both buttons do the same with the difference that home brings you to the homescreen instantly while back goes through your previous steps/pages/screens in the current app and then returns you the homescreen.
But later I noticed that 'reactivating' some apps that were exited via the back button cause them to 'reload' (the loading screen shows up - with certain games, grooveshark's loading screen, etc.) while they switch back instantly when "exited" with the home button.
I gather the way to 'leave' an app you don't plan on using for at least a short while (I am not talking about closing the app, I know it's up to Android, or some task-killer) is the back button, while home is more for task switching/starting new apps while old ones are running.
View 8 Replies
View Related
Aug 25, 2010
I was wondering how or if it is possible to exclude activities from the back buttons history list? For example not letting the user back into the Splash Screen?
View 2 Replies
View Related
Nov 2, 2010
on the ui i am having a back button displayed. there are three activities say A,B,C. Activity A is splash screen. Activity B is home screen. Activity C is edit screen. on edit screen only i am having a back button. when the user press that i open the activity B which also contains some sort of http request and response. i want that the previous activity from stack should get displayed? how can i achieve that? i am able to open previous activity on pressing the back button of device? when i press back button on device there doesnt goes any http request? i want to achieve this behaviour when i press the ui back button.
View 2 Replies
View Related
