After long running the Media|Player (audio mode) the app I'm developing often crashes w/ the following error: > Process android.process.media (pid 14795) has died. > Killing <my app> because provider com.android.providers.media.MediaProvider is in dying process android.process.media
View 3 Replies
I will try to be as brief as possible... I have published a very simple android application it's name is "Vib-e-rator PRO". It's purpose is obvious, it can be used as a masssage vibrator or as an erotic stimulator...
My Problem is don't have an Android Phone to test my app in real time.
I have been recieving mixed comments from people. A few users say its working fine. But majority of them complained that the Phone would n quit vibrating even after the closing application.
Later i speculated that when ever the user switched off the vibrator and quit the app it would work as expected. If any user (most of em) directly closed the application ( either through the close option provided in the app itself or by pressing the END button in the phone ) without switching off the vibrator then it would not stop vibrating.
So i added myvib.Cancel() (myvib is the context for Phone Vibrator) in the exit block the close option provided in my app. For the other scenario, when it is closed by pressing the END button in phone, i have no idea how to solve it... So friends please advice me what is necessary to do... The comments i have been receiving from many users of my app is really embarassing....
like many others, I want to kill my Android application on "exit" button. Really kill, not just move to background and stop all active code. (I know very well that Android does not like it.) I found Process.killProcess(Process.myPid()); and System.exit(0) which both work fine (I have no problem with activity stack, the "exit" button is in my base Activity.). But there is a problem. When I kill my process and I am back in the shell, I press [Home] button. It shows list of applications that are on the background including my application which has been killed.
Is there a way how to do both: 1) kill the process and 2) remove it from the Android application list that is shown after user presses [Home] button? Thanks for all replays (with the exception of that stupid "you should not exit applications explicitly on Android"
Do static variables of an ApplicationContext subclass left untouched when the process is killed?
View 4 Replies View RelatedWhenever the memory needs to be reclaimed, the process is being killed by Activity Manager Service in killPidsForProcess. I have a back button in my activity window on right corner of the title bar.
I want to kill the activity completely on clicking the close button. Can I reuse the same function and will it have any major effect? Please help me out in this.
I just started to get "The process com.htc.provider has stopped unexpectedly. Please try again. FORCE CLOSE" error. I think I've narrowed it down to my HTC Weather widget, because I noticed that it now states "Current City" instead of the city name, such as Pittsburgh. So, when I open the weather apps and hit the refresh button, I get the error everytime I hit the refresh button.
The only apps I've installed since this started to happen are MyApps, Lookout (Update), MyVerizon (Update) and CNN News (Update).I've only had the ERIS for about two weeks and this is the first time I've encounter this error.
I have an app with multiple activities and a local service.
if I finish() all the activities and stop the service, the process still exists (if I go into adb shell and type ps, I still see it).
is there a way to make sure the process is killed when I "quit"?
I keep getting this message, "The process com.htc.provider has stopped unexpectedly. Please try again." followed by a box to 'force close.'
I seem to remember it wanted to update about a week ago, so I hit ok and then the update failed. It has not asked to try and update again since then....
The phone will display this message upon start up and also will occur at other seemingly random times.
The phone works fine after pressing force close but does anyone know how to stop this annoyance?
I created application with name Test, and has a class that extends broadcastreceiver that listen for PACKAGE_RESTARTED. I use Advanced Task Killer, and killed the Test application. But when I kill another application, for example gmail, the Test's broadcastreceiver got the intent (I logged it). Does it means that broadcastreceiver will never died?
View 4 Replies View RelatedI have an application with many forms implemented as separate activities. The form variables are dynamically built based on a database, and there are a ton of variables in the C++ side of the application (accessed via JNI). I don't see how saving out all of this data to persistent storage each time the onPause() or the onSaveInstanceState() of one of these many activities goes into the background is a smart use of processor time. And I don't see how even if I save the local variables for each activity during that time I'd be able to restore a single activity within the context of all the others.
I have set up a service that auto saves the files when I detect that the app has gone into the background. (I set a time stamp when onPause() is called in any activity and then clear the time stamp when onResume() is called on any other activity. If the time elapsed is more than a few seconds, I know I'm not the top activity any longer and the service saves the files).
What I'd like to do is continue on as normal unless the OS kills one of my activities. Since we don't always get notified of this, I thought it would be nice if there were a way to tell the OS that I'd rather you kill the whole app than just one activity.
On Froyo, we found that some new "Task Manager" apps are now using the ActivityManager.killBackgroundProcesses() to kill apps. When this happens, Intent.ACTION_PACKAGE_RESTARTED is no longer fired. How can I find out that my application has been killed? I tried to start a service, and I do see this message printed in logcat:
W/ActivityManager( 2426): Scheduling restart of crashed service com.example.android.apis/.app.RemoteService in 20000ms
However, the service is never restarted as advertised, if the app is killed using the killBackgroundProcesses API. (If I go into adb shell and kill the service process, the service will indeed be restarted ...) This looks like a bug anyway, because the notification created by the app is no longer removed like in eclair (the StatusBarService, and a bunch of other system services, depend on the Intent.ACTION_PACKAGE_RESTARTED broadcast).
I can see on OMAP zoom2 platform, the moment screen timeout happens my application is getting terminated. I have a Google map based LBS application which is running on Zoom. I have implemented the interfaces given in gps.h to libhardware_legacy/gps.cpp .
GPS application talks to android framework and Framework talks to libhardware to get the GPS info. Now I can see that the moment screen timeout happens and the display goes off, my application killed. Actually from the framework the stop interface (hgps_stop() ) gets called on screen timeout.
I am wondring why this is happening, as I am not sending any stop request form my GPS application to the libhardware.
Is it something related to Android power manager, that android Power manager does not know about my application is running?
Currently my application is configured to always receive the CONNECTIVITY_CHANGED action to force an update if the previous update failed because there was no connectivity. What I don't like about this is that the broadcast receiver gets to be called too many times although it is not needed. I was thinking to register my broadcast receiver only if an update failed using the Context.registerReceiver(BroadcastReceiver receiver, IntentFilter filter) method. But I'm not so sure if this is a good idea. I'm concerned that if my application is evicted from memory the broadcast receiver will be unregistered or lost and my application will not be notified about the future CONNECTIVITY_CHANGED actions. The update is done in a short lived service. So if the update fails, the service will register the broadcast receiver just before it ends its execution time. Can somebody explain what happens to my broadcast receiver after the application is evicted from memory?
View 4 Replies View RelatedI have two BroadcastReceiver registered. When the app is closed they both fire at the appropriate times and do the appropriate things. If the app is closed then killed (say with an AppKiller), the receivers never receive their broadcasts, and nothing happens. Presumably the same thing happens if the parent app is killed due to low memory, so how do I ensure those broadcasts are fired/received. The API states that even if the app is killed it should fire, does anyone else have experience with this situation? If it helps my manifest is:
<!-- receivers for AlarmManager -->
<receiver android:exported="true" android:label="Shift roster updating calendar."
android:name="com.skooter.shiftroster.backend.service.UpdateCalendar" >
</receiver> <receiver android:exported="true" android:label="Shift roster checking alarm."
android:name="com.skooter.shiftroster.backend.service.SetWakeup" >
</receiver>
and nothing esoteric is going on in the AlarmManager/BroadcastReceivers
I need to create 3 things:
Content Provider
Service
Application
I'm wondering if these all three will be in one single project, or they will be three different projects?
Also how can I limit my Content Provider to my services and my applications?
Look what Im doing. Im getting a SMS message and breaking word by word using the StringTokenizer class.I've done this, but when I try to insert the word in the content provider, the application stops, and the emulator says the application stoped unexpectadly.
I don't know what to do anymore, I've tryied everything you can think about, but i didn't found the answer.
Please Help Me! Check my two classes.
SMS.java Class:
CODE:.....
I am a newbie to android programming. I want to search the name of contact member by taking phonenumber from the user. I dont know whats the issue and when run it just displays error .. "Application has stopped unexpectedly !".
My code is like this ...
CODE:.........................
I am working on Gps based application which runs all the time in background. But in extreme low memory case(or when i open many apps) my app is killed by the android system. I want to relaunch my app when it is killed by android system.I goggle it for this but don't get any solution.Any help would be appreciated.
View 5 Replies View RelatedI am trying to retrieve all applications that are running on the android phone. Following is the code I have wrote, but how do I get the application name into my Array items?
Context context = getApplicationContext(); Resources appR = context.getResources();
ActivityManager actmgr=(ActivityManager)context.getSystemService (Context.ACTIVITY_SERVICE);
List<RunningAppProcessInfo> appList = actmgr.getRunningAppProcesses();
CharSequence[] items = new CharSequence[appList.size()];
Vector <Process>allProcesses = new Vector <Process>();
for (int i=0;i<appList.size();i++) {
RunningAppProcessInfo rti = (RunningAppProcessInfo)appList.get (i);
Process p = new Process (rti.pid,rti.processName,rti.pkgList);
allProcesses.add(p); items[i] = p.getProcessName(); } : : :
If an application begins a Service via bindService or startService, will this Service object ever run from a process different from that of the application? I ask because many Android example projects begin a service and communicate to them using IPC which seems wholly unnecessary considering that, according to the Android Service documentation, "... services, like other application objects, run in the main thread of their hosting process." IPC, AIDL, and the IBinder interface only seem useful if connecting to a Service started by an application other than your own. Is this a correct or fair understanding?
View 1 Replies View RelatedAs an exercise I attempted to add an AppWidgetProvider-derived class to one of our existing Android applications. When the widget is created and appears on the home screen, the output from adb logcat notes: W/ActivityManager(58): Unable to launch app com.mycompany.myapp/ 10042 for broadcast Intent { action=android.appwidget.action.APPWIDGET_ENABLED comp= {com.mycompany.myapp/com.mycompany.myapp.MyAppWidgetProvider} }: process is bad
This output comes from around line 10814 in ActivityManagerService (looking at cupcake on git). This is running on an ADP 1.5, FWIW. The same AppWidget code, once separated from the main application's project and put into its own simple project, runs as expected, so I know my manifest entries/XML/Java are all as they should be. Has anyone else run into this, or perhaps can the Android team comment on what aspect of my application might be preventing the AM from starting up the process when the widget is added to the home screen?
For some reason I can't explain, when my app runs, I will on occasion get the following error message: "The application xxxxxxxx (process xxxxxx) has stopped unexpectedly. Please try again". When I debug my code, it seems to break at random places that doesn't make sense. On top of that I tried to surround the entire code with a try/catch block just to try to catch the exception, but it doesn't work either. I'm suspecting it's the OS that is producing this error message but I don't know why. As far as my code goes, if there were exceptions caused by it, it would've been caught by the try/catch block. Can someone shed some light here?
View 13 Replies View RelatedI am seeing a curious behaviour in my app. I have a widget that gets updated by a service every # hours, when the service finishes I stop it, using "stopService(new Intent(this, MyService.class));", the widget if pressed launches an Activity. Now it gets interesting, while im on the activity everyting works fine, then when I exit the app(by the back key or a button I designed which simply calls this.finish() ) the ActivityManager would tell me that my process has died, I do not see any error of any kind, just that the process has died.
Why I am seeing that message and what does it mean exactly? That is having a side effect on my service regarding static variables getting set to default. Could my code be the cause of this? Is there any way to know that your process has died? I have tested my app on a HTC Hero running 1.5, it always works well on the emulator and I never get that message. I know android kills processes to reclaim memory but Im always careful to close apps heavy on resources.
Is android's memory 16MB limit per Process or Application? If the limit is by process, I can make some services remote. That means the service will be in different processes, and the limit will be 16 x N.
View 3 Replies View RelatedBeing interested in Android development and still in the experimentation phase - there's something I haven't been able to grasp. As far as I've been able to understand, the process lifecycle and application lifecycles are separate and as such, it would be possible for the application to still to exist, even if it's process has been killed. So I guess my question would be, in what scenario could this occur and how is the application accessible if the containing process has been killed?
View 5 Replies View RelatedIn a comment on an epic StackOverflow question-and-answer, a gentleman who I will call Tim has outlined a scenario he says he is running into, one I have some difficulty believing. Reading somewhat between the lines, the flow would appear to be this:
1. User taps on an activity icon in the launcher 2. Process starts up 3. Application object is put in that process -- and a custom Application object loads an NDK library which initializes some statics/singletons 4. User uses application 5. User abandons application (e.g., HOME) 6. Later, user returns to application, before the first process is killed or recycled for use with another app 7. A second Application object is created, in the same process, before the first Application object is called with onTerminate()
This screws things up for Tim's app -- apparently, it does not deal with pre-initialized statics/singletons well. They were presumably counting on onTerminate() to let them clean up the NDK space. As a result, they are relying upon killProcess() (somehow...unclear under what conditions they might call this) to force their own process to go away, so their statics get cleaned up. Step #7 is what confuses me. I can see a new Application object being created, but only if the first Application object were terminated. I don't see any NDK-related bugs out on b.android.com that seem to match this complaint, though in principle it might cause problems for non-NDK apps as well. Has anyone encountered a new Application object being created in a process before the old one is terminated?
One of the winners of the Google app contest was Jigsaw by Mikhail Ksenzov, an app to capture and process whiteboard data. The app isn't in the market, and I can't find anything via Google about it's status. Is it still beta, or what?
View 1 Replies View RelatedI have been struggling with uploading my application to android market. I keep getting the same old "The server could not process your apk. Try again.". I tried for hours to change and modify my AndroidManifest.xml file but no luck.
Here is my my AndroidManifest.xml:
CODE:............
When a try to deploy my android App in the emulator, after the application(.apk) gets loaded in to the emulator, when I tap on the menu button in emulator for loading my application's initial screen, its is raising me a alert message with this information:
<pre>Sorry Application Keyboard in Process (Force Quit / Wait)..</pre>
and some other similar messages too..
How can I avoid this issue that is happening at all time, When this happens, unless I tap on Wait button, I can't able to proceed.
I have develop some application using sending sms" when I try sending sms show up " The Application xxx(Process com. Bhn.xxx)has stoped unexpectedly
Any body knows , about that error ?