I have developed an Android Widget, and it was working fine. I added some extra functionality and pushed an update through the Android Market. Now people are complaining that it doesn't work anymore.
The error I see in the logs is:
I cannot find anywhere what the process is bad error means. Restarting the phone (or emulator) makes the error go away, however, that is not what I want my users to do. explain what the cause of the error is.
Every 5 minutes this error pops up "Sorry! the process android.process.acore has stopped unexpectdly. please try again." It doesnt actually close anything. It pops up even when im not in an app. So it's more annoying than anything.
I have an updated apk - tested successfully on various devices and simulator instances - with the following manifest:
When I post to Android Marketplace as an upgrade to my existing 1.0 app, I get the aforementioned ambiguous message: "The server could not process your apk. Try again."
I just tried to upload the same file again. Now I get a new message:
The new apk's versionCode (2) in AndroidManifest.xml must be higher than the old apk's versionCode (2). The server could not process your apk. Try again.
So Marketplace did get my upgraded apk after all? (The very first accepted apk's versionCode was 1, so this update was of course bumped to 2.) Confused ...
Bumping it up to 3 and trying again. Surprise surprise, I get the original "could not process" error all over again. Going in circles.
If I exit and re-enter the Marketplace page, now it shows that the app has been uploaded! Except there's no app icon. Curiouser and curiouser ... and this is all happening with a cache-cleared (standards-friendly) browser to boot.
Did anybody encounter the RuntimeException with the message "Unknown error"?
java.lang.RuntimeException: Unknown error at android.os.Process.setProcessGroup(Native Method) at android.app.ActivityThread.handleChangeTopApp(ActivityThread.java:3663) at android.app.ActivityThread.access$4100(ActivityThread.java:126) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2039) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:123) at android.app.ActivityThread.main(ActivityThread.java:4595) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:521) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java: 860) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618) at dalvik.system.NativeStart.main(Native Method)
Is anyone getting this error: "The process android.process.media has stopped unexpectedly. PLease try again." It started this morning after I did the prl update. When I hit force quit the error keeps appearing and appearing.
I believe I accidentally (as a dumb noob) deleted the TelephonyProvider.apk and the Sprint_Promotion.apk apps. I got them on my SD card and have been trying unsuccessfully to reinstall them all night on package installer but I keep getting this wonderful "process com.android.phone" force close message. I managed to get my phone into airplane mode thinking if I disconnected it from the internet I could stop the error messages and do the installs off my SD card but to no avail. I'm trying to do it through Package Installer.
I'm un-rooting my phone using OMJ's guide in the everything root related guide, and I'm getting a "Failed Flashing Process" error in RSD Lite.
I am running as admin, I have the correct drivers (I recently rooted...), I have the sbf in C: .... yet it fails.
The error says " Failed Flashing Process. Failed Flashing Process. Interface BP: Error flashing subscriber unit. Device API Error: 0xE0030009 Command: ADDR (0xE0231009); phone connected"
I am going to try flashing SPRecovery to see if I can at least get to a working point.
SPRecovery worked. It boots into 2.1 and has SPRecovery as the recovery. I still want to get it to stock, so I am going to try and download the stock sbf again (it doesn't have a checksum so I have no way of knowing if it is good or not...) .... here goes nothing!
Okay -- so I finally mustered up the courage to root and try a lag fix. I rooted using the unleash the beast files. And then tried the lag fix over at XDA found here: xda-developers - View Single Post - [UTIL] One Click Lag Fix 2.0
I ran the lagfix_ext2, like the forum says -- it took about 10 minutes to do some things ...There was an error message in the middle saying that it had to stop the process. I said okay, but the process kept working, finished, and then rebooted. It booted up, and I downloaded quadrant again (it was gone for some reason), ran it, and only ran an 895 -- this is 16 points less than what i ran just using the unleash the beast. Should I try the lag fix again?
After the update to Android 2.1 on my HTC Eris, like many other people, I had problems syncing my phone contacts to my facebook contacts. The process com.htc.bgp constantly force closed, and no linking could be made or is some cases only a part of the facebook contacts were synced.
Different fixes has been suggested by users online but none of them worked
My wifes account works perfect on my phone but mine does not work on her phone
Obviously its something on my FB account but what?
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 have a bluetooth adapter attached to my car's iPod dock. It acts like a bluetooth headset so I can play music wirelessly from my Droid. My problem is that I have to go through a few menus to connect the paired devises every time I get in the car. Is there a way to have the Droid automatically connect to this device, or is there a widget that can help make this process easier?
At a certain point in my program, when I'm completely done with my service, my activity executes unbindService() and stopService() -- yet the process persists. I can tell that it persists because I run "ps" in "adb -e shell":
"adb logcat", I can show you the sequence of events:
First, my activity calls unbindService(serviceConnection). According to the documentation, unbindService() will "Disconnect from an application service. You will no longer receive calls as the service is restarted, and the service is now allowed to stop at any time." So that is fine, and it is happening.
Appropriately, we see the onUnbind() call happen on the service side. According to the documentation, onUnbind() is called when "all clients have disconnected from a particular interface published by the service." So this confirms the correct service connection is being passed, and that the service is responding accordingly.
Next, my activity calls stopService(serviceIntent), and returns true. According to the documentation, stopService() does the following: "If there is a service matching the given Intent that is already running, then it is stopped and true is returned; else false is returned." Again, this is happening and returning true.
In response, the service's onDestroy() method is called. According to the documentation, onDestroy() is "Called by the system to notify a Service that it is no longer used and is being removed. The service should clean up any resources it holds (threads, registered receivers, etc) at this point. Upon return, there will be no more calls in to this Service object and it is effectively dead."
At this point I expect the process to disappear from the process table. Yet it remains indefinitely. But why?
Also, the process is so persistent that I can bind to it again, and I see that it is the same exact process responding because the PID (process ID) is the same!
So, I decided to give Tridents ROM a try about 10-minutes ago.
I used ROM Manager, backed-up my old ROM, then downloaded Velocity 0.2.
Now, my phone will do nothing, it turns on and shows the red Droid eye, then when it's time to go to the home screen I get pop-up after pop-up saying that "The process com.android.phone has stopped unexpectedly. Please try again."
I have no way of getting on my phone at all, what can I do?
I Just installed a new theme (Live Wire) for my Lithium Mod Rom. Don't know if there is a connection, but when I need to update an app, I get the message something like "process android media process stopped unexpectedly" and it will not allow the update. Everything else works well. I have turned it off for awhile, and have done a battery pull.
I'm using Xperia x10 mini. Whenever I try to add a contact to my phonebook, before clicking save this message appears: "The process android.process.acore has stopped unepectedly. Please try again." And I have no other choice but to click "force close"... Another thing is, even though my contacts' names appears in the messages in my inbox, when I click on the phonebook icon, the phonebook is empty...
So since I got the phone on Thursday, at random, I'll get these popup crash messages, that say "The process com.google.process.gapps has stopped unexpectedly" it has a "Force Close" button, which doesn't seem to change anything other than to acknowlege the message.It will happen at random, sometimes while I'm on the home screen, or sending a text message, but more recently, as I was trying to manage & link contacts. When I searched for this message it seemed to be related to people using Gmail, but I always get this message when I'm doing other things and not even touching my Gmail account.
I've searched around the forums (here and SDX forums) and although it seems the few people that had this issue were able to solve it, my case seems a bit different.
It's different because of the people I've read solving the issue, it was a problem with something they changed / removed with gmail / gmail storage or talk / talk storage. And when they cleared the cache or re-installed the problem went away. Also, it seemed that the same people had a problem with downloading from the market...
Neither of the above apply to me, but yet I'm still getting this FC error all the time!
I was helping a friend with their CL14 Moment out of the box...and went from stock 1.5 CL14 to 2.1 DD03 w/Joey recovery to EclairDD10 and v5 root. I then did the streaming media fix, and then the private app (build.prop) fix (all previously done with my phone no problems). I did all of these update right in a row, and after my last re-boot the FC error (process com.google.process.gapps has stoped unexpectedly) started showing up and won't go away.
The only .apk / odex files I removed were the preloaded Sprint apps
Does anybody have any other ideas on how I can get this FC error to stop? I've tried clearing the cache / data for all the mail / talk apps, rebooted, cleared dalvik cache...
I'm able to successfully use a ScrollView inside the layout xml file for an application. However, when I tried using a ScrollView inside the layout xml file for a widget, I get a "Problem Loading Widget" error as soon as I drop the widget in the emulator. If I comment out the ScrollView, then the widget shows up in the emulator. I've pasted my layout xml file below. Any thoughts on how to get past this error would be much appreciated.
I developed a widget that is a shortcut to the preferences of the android, on my phone it works ok, but I am monitoring it using Crittercism (a capture crash tool) and he is accusing the following error:
I have the widget where you have your appointments on a full screen, so on the top right is the current date, but this doesn't change.only changes when I delete and re-add the widget to the home screen.When I press the widget to go to the agenda itself it does show the date correctly there.Is a problem, forgot a birthday cause of it.(Installed eco birthday now but still)