Is there any way for a process to detect that its being stopped as a result of the user going to Settings->Applications->Manage Applications->My App->Force Stop? I see onDestroy() isnt being called under those circumstances.
View 2 Replies
I see no problem in the code.
CODE:..................
(idk why it's butts but I've gotten used to it now. really just sets up the menu button)
CODE:..........
within DrinkingBuddy.java:
CODE:.....................
That's it. I can press the menu button on the phone and see the menu items I created, but when I click on the "Settings" (r.id.settings) it FC. Do I have to do anything to the manifest/other thing to get this to work?
If I Force Stop an app (via Settings->Applications->Manage Applications->Any App->Force Stop) will the app ever start up automatically again or is the only way to start it up again to have the user start it. I have an app that starts a service. The service registers an alarm I've defined, with the Alarm Manager and this is recieved as expected. In my manifest I've defined a TimerIntentReceiver, to receive that alarm I've defined. If I Force Stop the app then is it possible to have the Alarm Manager "wake" my app up via the TimerIntentReceiver I've defined. I'm not seeing this happen. Once I Force Stop my app it never runs again unless I manually start it. Is there anything I can listen for, apart from BOOT_COMPLETE, to start up my app? Or does the user always have to start all apps.
View 2 Replies View RelatedI've done a search but found nothing. It seems like when I have to force stop an application, it takes me 8-10 button presses to accomplish it (menu-settings-applications-manage applications-sort by size-sort az-find application-scroll down-force stop). It's just not easy. Especially if I'm driving or jogging. Is there a quick and simple way to force stop an application?
View 3 Replies View RelatedI have a service which runs in the background when the user starts using my app. I am using it to do some posts to our server. I always close my service by calling stopSelf as soon as the posts have been made or failed.
But I recently observed two times that my service did not stop. I saw that in the running services in settings on my device that it has been sitting there for over a few hours.
So I was trying to see if I can alternatively set a timer using which I can force the service to stop after a few minutes no matter what.
I just ran into a problem when trying to launch the phone's email app via a button in the options menu because as soon as I click the button in the emulator it causes a force close error.
View 2 Replies View RelatedI've read about how task killers aren't necessarily good because of the way they FC apps, so I'm wondering, is it safe to go into my Running Apps list and Force Stop certain apps? I'm thinking of apps like Amazon MP3, Maps, Peep, Facebook, Fandango, etc. General things like that, nothing system-important.
View 5 Replies View RelatedI'm designing an HTML page for display in Android browsers. Consider this simple example page:
<html>
<head><title>Simple!</title>
</head>
<body>
<p><img src="http://sstatic.net/so/img/logo.png"></p>
</body>
</html>
It looks just fine on the standard HVGA phones (320x480), but on HDPI WVGA sizes (480x800 or 480x854) the built-in browser automatically scales the image up; it looks ugly.
I've read that I should be able to use this tag to force the browser to stop scaling my page:
<meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0; minimum-scale=1.0; user-scalable=0;" />
... but all that does is disable user scaling (the zoom buttons disappear); it doesn't actually prevent the browser from scaling my image. Adjusting the scale factors (setting them all to 2.0 or 0.5) has no effect at all.
How can I force the WVGA browser to stop scaling my images?
A few weeks ago I switched my EVO 4G to the standard Android 2.1 UI through the widely publicized "clear defaults" and "force stop", then pressing "Home" and selecting to default to the Android launcher. This worked very well. Unfortunately for me, I thought this was just going to be a test drive. I wanted to see how it compared to Sense UI, but now I can't figure out how to re-activate Sense. According to the description of the process for other Android phones with Sense, you are supposed to be able to turn Sense back on by doing essentially the same process. Select application "HTC Sense", and do "clear defaults" and "force stop" again. Then press the Home button, and select to default to Sense UI when asked.
This doesn't work on my EVO 4G. When I perform these steps, pressing the Home button has no effect. There is no popup asking which UI to use as default. The standard Android UI remains in effect. I've done a fair amount of google searching, but haven't seen any explanation how to do this so far. I'm hoping that it's possible without wiping the phone back to its initial state. Anyone know how to restore Sense? I'd like to experiment with it, at least until the day Froyo comes out for it.
On both 2.1 & 2.2 I have found that occasionally the browser progress bar will only get 90% before becoming getting stuck. You can try as many times as you like to view the page but it will always get stuck.The only way I have found to cure this is to force stop the internet app, then everything is fine again. Anyone else seen this or know how to stop it occurring?
View 5 Replies View RelatedHas anyone else had the problem with their alarm force closing? It will ring on time but an error message pops up and says it has to close.
View 2 Replies View RelatedI accidently "force stopped" and application. How do I turn the application back on?
View 3 Replies View RelatedSo I just flashed Darchdroid 2.7 and every time I try to open the calendar it says "The process com.android.calendar has stopped unexpectedly. Please try again." Anyone know of a way to help me fix this?
View 3 Replies View RelatedI removed the following and started to get force close errors....any ideas why?
View 1 Replies View RelatedThere are several ways to terminate an app or to "clear cache". What are the differences between them?
Here are some I have been using without deeper understanding:
- Long press middle button and swiping out one app
- App manager: Clear cache, clear data, force stop
- Restart phone
- Use task manager app to kill app in question
Has anyone been having this trouble lately? I've tried clearing out old messages and clearing the cache but yet it still force closes on almost every picture while resizing it.
View 4 Replies View RelatedI'm just wondering if anyone else is having this problem. When I try to open a Facebook contact, the people app keeps force closing and restarting.
View 8 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?
In my application i have several activities and i want to start background music whenever my *Application* is launched and stop music whenever *Application* is paused or stopped.
View 4 Replies View RelatedOkay when user presses log out button what's supposed to happen is:
Code:
stopService(myIntent);
unbindService(mConnection);
mIsBound = false;
I need to shut down the service on background.Except the service restarts itself over and over again! Even if I kill the program from task manager the service restarts itself. Other programs aren't using the service. when I uninstalled the program the foreground program information popped up indicating it was STILL there(albeit this I solved by rebooting phone).
When user says he's finished with the program 'least he can expect is for the program to stay down rather than keep eating battery by acquiring GPS signal and sending them to server. The program is not intended to be "once you log in you need to Uninstall me and reboot phone to get rid of me!" type of program!
I was reading through app suggestions and someone mentioned an app called mp3 Download that basically functions like limewire, letting you search and download mp3's to your phone. Does anyone know anything about this app and whether it is good or not? Or have suggestions for a similiar app? It had mixed reviews at appbrain and when I searched here it came up with a bunch of other threads.
View 4 Replies View RelatedI was told by a few friends that the iphone has an app that allows you to hold your phone up to a song that you dont know and it tells you the name.Does android have anything like that?
View 6 Replies View RelatedI've created a simple android game, based on the Lunar Lander sample, and I'm having a problem with handling key events.When the activity starts, the only keys that onKeyDown or onKeyUp get called for are the dpad up/down/left/right keys.Neither the menu, back, or dpad_center keys trigger onKey methods. However, once I've pushed one of the dpad up/down/left/right buttons, pressing the menu, back, or dpad_center keys do trigger these methods. I'm not getting any errors, or any indication of what's going wrong.It's possible that the focus is set wrong - the activity is started from a button on screen, so it could be in touchscreen mode. If that's the case, shouldn't touching the back button get me in to the right focus mode so that I can catch the event?I'm using the emulator from SDK-1.5r3.I have not been able to try this on a real phone yet.
View 4 Replies View RelatedI saw it on the market but forgot to install it. It displays the number of remaining minutes, texts and data left for the month if your on a monthly mobile phone plan.
View 2 Replies View RelatedI'm working on an application which allocates lot of memory and hence I'm bound to get OutOfMemory. I want a way to get notified when system is running short of memory so that I can stop processing further, notify user and release as much memory as possible.
According to official Android documentation there is a callback onLowMemory from the system. I have a class which extends android.app.Application and I have overridden onLowMemory() method. This class has entry in the in the application tag of AndroidManifest. However it never gets called in my case. Do I need to register for this event using AndroidManifest or any other means?
In one of my applications I programmatically open the context menu when something is clicked in my MapActivity overlay. This works perfectly under 1.x as well as on my 2.0 Milestone. I've used showContextMenuForChild() historically, but openContextMenu() does that same thing.
As expected onCreateContextMenu() is called to build the menu and then onContextItemSelected() is called when something is selected. So far all is well.
The odd thing is that under 1.x the onContextMenuClosed() method is called when I press the back key, but not so under 2.0. This confuses states for my app since I need to know whether menu is shown or not - or maybe there is a way to know this that I have not (yet) figured out...
Is this a deliberate change or should I file it as a bug? Googling comes up pretty dry (stuff that is over a year old).
Anyone with a 2.0.1 Droid that would care to test whether this has already been fixed? (The ETA for Milestone 2.0.1 seems hazy still, but it appears that at least one of my reported bugs has been fixed in 2.0.1 event though it isn't flagged as such.)
Is there a way to make sure onSurfaceCreated is called only once during startup.
Currently in my app it gets called once with say 800x480 then it gets called a second time with 480x800. I guess this is probably due to a call to setRequestedOrientation in onCreate. Is there any way to make sure the app starts in a particular orientation, to prevent orientation changes, and to have onSurfaceCreated get called only once during start up?
I have over-loaded the onFocusChanged() in my classes which inherits from LinearLayout.
CODE:...........................
i use a ScheduledThreadPoolExecutor combined with a ThreadFactory, their all combined should cause an unchaught Exception to be logged so that i can see what happening if any thread is dying in the ThreadPool:
threadPool = new ScheduledThreadPoolExecutor(poolSize, new ThreadFactory());
My ThreadFactory, also sets a UncaughtExceptionHandler :
public Thread newThread(final Runnable r) { final Thread thread = new Thread(r); thread.setUncaughtExceptionHandler(new ThreadLogger()); final int counter = count.getAndIncrement(); final String name = threadName + counter; thread.setName(threadName + counter); if (Logging.isLoggingEnabled()) { Log.d(LOG_TAG, "Thread created :" + name); } return thread; }
The ThreadLogger :................
I have been struggling to get onLocationChanged called, but I'm not sure it does not. Here're my code
criteria = new Criteria(); criteria.setAccuracy(Criteria.ACCURACY_FINE); criteria.setPowerRequirement(Criteria.POWER_LOW); criteria.setAltitudeRequired(false); criteria.setBearingRequired(false); criteria.setSpeedRequired(false); criteria.setCostAllowed(true);
String locationContext = Context.LOCATION_SERVICE; locationManager = (LocationManager)context.getSystemService (locationContext);
String provider = locationManager.getBestProvider(criteria, true);.................