When I use the default web browser and get finished I can find no where to close it. I just hit the home button to get out of it, but I am sure that leaves it running. So, how do you close out of it and shut it down?
I need to launch the Browser from my application (cannot do the WebView - it has to be browser), and once I'm done with the browser, is there a way to close the Browser and the user back to the application programatically?
The problem is that user will probably press back or home keys to get out of the browser - back key will not work, and home key will put Browser and my app in the background.
I hopped that a button in the HTML displayed would close the browser but it seems like the Android seems to ignore that. Can anyone help?
So I read through the SDK docs and I thought that calling a new activity(browser) as part of a task (myTask) will mean that activity* (browser) will close when a user closes the task (myTask) But I am left with a browser window.
Here is my scenario (in sudo code);
Question 1: What is the cleanest way to ensure that when a user closes my app, any outside activities called will be closed to.
Question 2: Does a callback URl start a new Task, or use one in the stack if available?
Sometimes, after the phone has been in sleep mode for awhile, when I hit the power button to wake it back up and then the menu button (or swipe) to open the screen, I get that circular bar pattern followed by what look like the browser trying to launch. The screen is white, with a white address bar area, too. Then that screen goes back to the circular bar pattern, followed by the white browser screen again, after which it just closes. Very odd. Doesn't do it all the time. Seems to be random. And after a hard reset, sometimes the first time or two I use the browser, it just force closes on me. Again, doesn't do it all the time. (At first I thought I accidentally hit the home button, or something, but I didn't.)
Well I have issues. I always think that my phone isn't running the way it should or could. I have installed many apps and uninstalled a couple. But I have noticed that my browser will force close about every other time I use it.
Ok, I have had a Motorola Droid since they released the phone and my battery has been great. I could charge it overnight and take it off the charger around 6:30 am and when I put it back on the charger around 9 - 10 pm at night I would still have anywhere from 50% to higher battery life and this is after very heavy usage.
Beginning a few days ago I noticed that my Droid battery indicator is showing almost completely drained out by 6 pm and I really used my phone lightly yesterday and today. Today and yesterday both, the red LED was blinking and the battery indicator was showing almost completely dead by 6 pm. I pulled up the battery usage on the phone and it is showing the 'browser' as the biggest battery hog for some reason. Today it was showing 81% of the battery usage was from the browser. I hardly, if at all, used the browser today. I also checked the firmware version and it is showing 2.0.1, which I never updated it myself.
Are there any suggestions about why the browser would be draining the battery down so bad, when the browser has not even been used? Is there a way to close out the browser so it doesn't continue sucking the battery dry, besides using an app killer program?I did search the forum and did not see a specific question/answer to my question. I know I had read that some people were seeing battery issues after upgrading to 2.0.1, but I did not upgrade my phone, it must have done it.
I'm running an application with different activities. When I close my app, all the activities are destroyed but my app still locked in my main thread in: Object.wait(long,int) line: not available [native method] Is there a service still running or something like that ? What can I do in order to close properly my app?
I'm currently writing an application for the Android platform that requires a mounted SD card (or ExternalStorage). I know that it might not be the best way to require something like that, but the application will work with quite a lot of data, and I don't even want to think about storing that on the device storage.Anyway, to ensure that the application wont run without the external storage, I do a quick check in the activities onCreate method. If the card is not mounted, I want to display an error message and then quit the application.When I run the application, and the exception gets raised (I raise it manually to check if everything works), the error message is displayed correctly. However when I press the button, the application closes and I get an Android error, that the application was closed unexpectedly (and I should force exit).I read some topics before on closing an application, and I know that it maybe shouldn't happen like that. But how should I instead prevent the application from continuing to run? How do you close the application correctly when an error occurs?
The ApplicationManager is killing the process of my application when the user presses on "FORCE STOP" on the Aplication Manager.According to the documentation a broadcast action is.The user has restarted a package, and all of its processes have been killed. All runtime state associated with it (processes, alarms, notifications, etc) should be removed. *Note that the restarted package does not receive this broadcast.* The data contains the name of the package.How can I listen that action in my application; I have tried creating a BroadcastReceiver on my package, but the onReceive() is not called.
Can someone tell me how to close all activities running under a tab?My initial activity does not need a tabbed view. Therefore, to initiate a tab for the next (remaining) activities, I call a class that extends TabActivity, from the first tab.All this class does is to assign and call activities based on the tab click.Currently, to close all activities i am using StartActivityforResult.But in this case, while calling activites from the TabHost, setContent does not accept a result code as a parameter.Help me to solve this one. My application is stranded in a blank screen before closing. i.e. in the TabActivity class.
I started to develope an application. When I wanted to close the application I clicked on the home screen, but the app is still playing in the background. Than I tried to click on the "back" key, but nothing happend, so I've created a key event listener for the 'back" key, and inside that method I wrote finish(); Now my app is closing but I think it's still running in the background, because when I go to "manage applications" I can still see it in the "running" tab, and if I press it, I see I can click on the "force close" to actually close the app. What do I need to do in order to really close the app without leaving it open (one way or another)?
I have uploaded application to market and met weird problem which I never received before - when I click "Open" button when the application is installed I receive error dialog and the application is forced to close. I do not have this problem when start application from desktop launcher panel. I have already receive 2 stars for that though the exception even comes not from my cod - very unpleasant surprize from market app.
Application uses vibration and declares corresponding uses-permission "android.permission.VIBRATE" - this is what the exception tells me about, but I can't see such problem with other apps that use vibration on market.
the problem is that this button doesn't exit of my app... it simply closes the current intent ant returns to the previous intent (window) of my app.... how i can do a real exit/close button? i tryed with this:
Intent intent = new Intent(Intent.ACTION_MAIN); intent.addCategory(Intent.CATEGORY_HOME); intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK); startActivity(intent);
but it doesn't works, because when i turn back into my app, the app comes in the last opened window, and not in the first window of the app, how i can do that? i need that when i re-open my app it starts on the first window of my app
I want to close my application, so that it no longer runs in the background.How to do that? Is this good practice on Android platform?If I rely on the "back" button, it closes the app, but it stays in background. There is even application called "TaskKiller" just to kill those apps in the background.
I'm writing a little app that uses GPS coordinates and I have a toast that pops up and displays my current GPS coordinates (and updates them as they change).It works fine but when I close the app the toast remains and covers whatever I do on the homescreen (and continues to update the GPS coordinates).How do I get it to cancel when I close/hide the application?
Is it possible to stop all started services when the user hits the Home Button? I use: startService(new Intent(ClassName.this, ClassName2.class)); stopService(new Intent(ClassName.this, ClassName2.class));
This means I will have to somehow add the 'stopService()' for 7+ of my app classes I've researched this topic and I think there's 'onTerminate' but still not sure how this should be implemented.