Samsung Moment :: Getting An Excessive Amount Of Force Closes?
Nov 3, 2009Anyone else getting an excessive amount of force closes? I must have had like at least 5 today.
View 14 Replies
Anyone else getting an excessive amount of force closes? I must have had like at least 5 today.
View 14 Replies
I got a samsung fascinate last month and have been doing nothing but soaking up information since then.
Well, My mom has had a Moment for some time now. After looking at it today the first thing I noticed that its really slow and constantly force closes. She doesn't know anything about the phone other than its really slow lol.
It appears to of been rooted (I think my cousin rooted it for her) so I guess I need to know what steps I need to take to speed it up and to get it to stop force closing. LMK if I need to provide any more info,
Think Google Voice was updated a few days ago. Version 0.3.0 on device. Every time on power-off/on it force closes. Uninstalled and reinstalled it, did not help. Reviewed the log file and there are some unhandled exceptions in Google Voice code. Any one else with this problem? Is there a way to reinstall an older version of Google Voice app?
View 11 Replies View RelatedI am running Galaxo 1.6.1. Seems like my phone runs very slow. key presses and app responsiveness is pretty bad especially when i am going between apps like google maps and pandora. at this point it starts to turn into one force close after another)
I'm not an expert on android, but i installed Estrongs task manager and the max memory i get when i kill all apps is about 20mb. i'm often running at about 10-14 at normal use. (i'm sure its much less when the force closes start)
Does anyone have any suggestions for freeing up memory? I saw some tweeks for the previous galaxo roms but those don't seem to apply to 1.6
I have a rooted Fascinate. After a second re-root my SF has been very buggy. My first root was successful. I messed something up trying to install voodoo and had to flash back to stock. Now, after a second buggy root I am faced with many freezes and FC's. (primarily in com.android.settings, but will float to various apps). Battery pulls don't seem to help. After a certain amount of using my phone, hopping WiFi, maps, email, just normal use, something will need to FC.
Within the next few days I plan on un-lagfixing my phone & un-rooting it. Ultimately I'd like to take it back stock and not root. This leads to my question: what is the best way to flash stock. I don't want anything left. I can tell there was something left from my first root because ads still do not show up. I had an ad block program installed on my first root.
Everytime i reboot my phone, I get bunch of problems with my phone. when I try to open the phone dialer I get a force close on com.google.process.acore. Sometimes it completely prevents me from using the phone.
Then on occasion the phone freaks out and shuts the screen off, but leaves the navigation lights on the bottom of the phone. At that point the phone is completely unusable for about 1-2minutes. Sometimes when it comes back on, it starts rerunning the media scanner.
I have a replacement incredible, but over the last week I'm getting more and more force closes than I did with the first one.
View 3 Replies View RelatedI'm working on this new app, and it's force closing before it even opens, why it's force closing? (I've tried this app on my samsung transform and my motorola xoom yesterday, both worked, and them i added the image button inplace of the regular button, and now it won't work. here are my files;
Main.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="fill_parent"
android:orientation="horizontal" >
<EditText
android:id="@+id/editText1"
[code]...
I'm getting reports from users about force closes in my app after the donut OTA. One of them was kind enough to send me a logcat which included these two gems (right after he installed it from market):
10-02 15:56:35.708 D/PackageManager(71): New package installed in / data/app/com.billnapier.android.livebookmarks.apk 10-02 15:56:35.708 W/PackageManager( 71): Unknown permission com.android.browser.permission.READ_HISTORY_BOOKMARKS in package com.billnapier.android.livebookmarks 10-02 15:56:35.708 W/PackageManager( 71): Unknown permission android.permission.READ_HISTORY_BOOKMARKS in package com.billnapier.android.livebookmarks
The second one makes sense, since that name has gone away. But I can't figure out why the first one would show up, since that permission should exist on the phone. anybody got any clues? I can't reproduce this on my phone, so it's kinda hard to debug.
Some of my users are reporting force closes. Does anyone have some ideas about how to track these issues down when I can't reproduce them in the Emulator or on my Hero? This is my app btw if anyone wants to logcat it for me:
http://aliceonandroid.wordpress.com/
I just got my Legend today. Had many problems getting it to work on Tmobile US. Finally got it working, but now I can not personalize it. Everytime I go to Menu-Settings-Personalize- either Scenes, Home wallpaper or Lock screen Wallpaper I get a Force Close. My Sotware information is:
Firmware version
2.1
Baseband version
47.23.35.03U_7.05.35.03
Kernel version
2.6.29-00980ffd
Build number
1.11.997.0 CL128574
Software number
Unknown
Browser version
Webkt 3.1
I've had this phone for about a month now. No problems whatsoever, until the other day. My phone was turned off. Then, it "magically" turn on ans started ringing. I turned my phone back off for a while. Later, I turned it back on and the second the home screen pops up, like 10 force close screens pop up. I can't text, internet, nothing. No settings either. I click the phone tab at the bottom and another force screen pops up, same as everything else. It also shows I have no signal at all, when normally I have almost full bars. A few days prior to this, my phone would phase in and out of service for no reason.
View 7 Replies View RelatedI figured I might try starting something up for those who are having problems with Launcher Pro. It's a great home replacement and has far better functionality than Sense does IMO. The only issue is that it seems like some people are getting a lot of FC's.
I had a good week long run without any FC's, and then after an upgrade it seems like they're back.
If anyone has found any malicious widgets or apps that don't play nicely with LP, can you please post them up here?
I updated my brothers phone from 1.5 to the 2.1 de03 from sdx, now his phone keeps force closing, Sent from my SPH-M900 using Tapatalk
View 6 Replies View RelatedJust installed chomp sms and then sms pop up. When I tried to launch the sms pop up to adjust settings...force close. I do get pop ups though. Slick. Like Chomp also.
View 4 Replies View RelatedAnyone know how to Force Quit a Samsung Moment? About 2 hours ago the network froze. =( I just bought it yesterday.
View 2 Replies View RelatedAnyone noticing a ridiculous amount of force closes on LP+ while running CM6? I originally was on the newest "stable" build, go ta lot of FCs, so updated to the 9/25, still getting the FC's. Then went back to the stable one, updated LP in the market, and still getting the FC's.
View 6 Replies View RelatedA couple days ago I flashed the 2.1 icon pack, used MetaMorph to apply a theme and ended up getting force closures. I did a wipe and restored my last nandroid -- no luck. Then I restored with the RUU and put Fresh 1.1 on my phone. I want to switch to MoDaCo 2.2 but when I do I'm getting those force closes again.
View 1 Replies View RelatedI am new to android development and I have made this using help from a website. The XML files dont have any errors,Here is my Main java code: package com.CFConverter;
import android.app.Activity; import android.app.AlertDialog; import android.content.DialogInterface; import android.os.Bundle; import android.os.Message; import android.view.View; import android.view.View.OnClickListener; import android.widget.EditText; import android.widget.RadioButton; import android.widget.Toast;
public class CFConverter extends Activity {
/** Called when the activity is first created. */ private EditText text;
@Override public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
text = (EditText) findViewById(R.id.EditText01);
} //This Handler is called when we click the button01.
public void myClickHandler(View view) //passing the current view {
if(view.getId()== R.id.Button01) {
RadioButton celsiusButton = (RadioButton)findViewById(R.id.RadioButton01);
RadioButton farhrenheitButton = (RadioButton)findViewById(R.id.RadioButton02);
if(text.getText().length()==0) { Toast.makeText(this, "Please Enter a Valid Number", Toast.LENGTH_LONG);
return; } float inputValue = Float.parseFloat(text.getText().toString());
if(celsiusButton.isChecked()) { text.setText(String.valueOf(convertCToF(inputValue)));
// calling function to convert } else {
text.setText(String.valueOf(convertFToC(inputValue)));
} return; } } private float convertCToF(float fahrenheit) {
return ((fahrenheit - 32) * 5 / 9);
} private float convertFToC(float celsius) {
return ((celsius * 9) / 5) + 32;
} }
We have had a couple users on the myTouch phone have issues in our application. It apparently is force closing on them. I am not sure of why it is, and the 1.6 SDK is not out yet. Has 1.6 been released into the wild? If so, do you know where I can download the image for my G1 dev phone to test w/?
View 7 Replies View RelatedFor the past 2 months, whenever I open the market on my Droid, it always force closes, "(process com.android.vending)". What do I do?
View 1 Replies View RelatedI got the droid about a month or two ago and to date I love it. The ability to customize it and the applications available are amazing. My issue though is the force closures on several applications, the ones I've had issues with are handcent, homerun battle3d, visual voicemail and helix launcher. I may have left one or two out but those are the ones I could remember off the top of my head. I emailed the developer of handcent and they were very fast in responding to my email and we spoke over google talk today at length.
We were unable to figure out the problem for sure but after I did a factory reset, handcent now works again because I love this sms app! I'm not sure about homerun battle and helix cause I no longer use either, but the factory reset fixed visual voicemail as well. After doing the f.r and handcent working again, spoke to the developer again and was asked if I had any other sms apps on my phone. Now I did have chompsms on there at one point and I was advised that this is a possible reason for the f.c issues with handcent. If this is true I would like to ask you guys who are more tech savvy than I if I'm installing certain programs on my phone that are causing the force closes.
My just force closes all the time starting this morning. I updated my phone the first day of the last software release with no issues. Just wanted to see if any one else has a problem as ny return time us coming up. Or if any one know how to reinstall that default app.
View 4 Replies View RelatedAnd I cant find anything in the search that might help. I thought there was some busybox update and now my stoned a$$ cant find it.
View 2 Replies View RelatedI have the Motorola droid. I can see my inbox but when I try and open an email the app force closes. Anyone else had this problem?
View 1 Replies View RelatedEvery time I try to start the Market I get the following error. The application com.android.vending(process com.android.vending) has stopped unexpectedly. Please try again.
I've read lots and tried lots of fixes but nothing works. Cannot download or update any applications as a result.
This is a kind of long process of what I went through to kind of get my phone back up and running after a few small force closes snowballed. My phone is up and running now but still not at 100%, any input would be appreciated.
My phone's previous software information was the following. Virtuous Rom 2.6 with King's BFS #5 kernel not overclocked and the Incredible Revolution Theme.
About a week ago I started noticing some random force closes with some of the HTC services (.com.htc.downloader, or something similar). It would force close but never caused me any problems that I would notice. The only new app I had added in about a month was "Angry Birds Lite"
Then yesterday my phone started acting sluggish all of a sudden so I decided a reboot was in order. I used "quick boot" and selected reboot and my phone started to reboot, and then started to boot loop (it would get all the way to the droid eye animation and sit for a minute then try to boot again). I pulled the battery and attempted to let it boot again and it was still stuck in the boot loop. I then booted into recovery and attempted to restore one of my backups with no luck, now it would just get stuck at the first white HTC incredible screen and sit for half an hour if I let it. Next I did a full data/dalvik cache wipe and tried to restore a couple different nandroids with no luck.
My next step was just to re-download Virtuous and start fresh. I was able to get Virtuous to boot but after going through the set up .com.htc.launcher would go into a force close loop with no way out of it, after another few attempts at loading Virtuous and other Sense based roms and having them all fail with the same .com.htc.launcher force close loop, I tried to go to a senseless Rom and was able to get Sky Raider to boot with no issues. But I wanted my phone back the way I had it.
My last resort was to unroot back to stock(S-off still). I downloaded the stock PB31IMG.zip and flashed it to my phone with complete success. Next I needed to root my phone again. I used the UnrEVOked 3.2 and got my phone rooted, but I couldn't boot into recovery. After much trial and error I was able to get recovery to load by flashing Adrynalyne's version of clockwork mod. I then flashed Virtuous 3.1 with the stock kernel onto my phone, and then I was able to flash back to the standard Clockwork mod recovery.
My phone is up and running now fine when it's on. But my issue now is that I can't do anything through rom manager or manually through clockwork mod to my phone without my phone getting stuck in a boot loop or getting stuck at the first HTC incredible screen after booting out of recovery. Even after just making a nandroid backup of my phone (without loading any apps) it will get stuck at the HTC screen. 95% of the time, clearing the dalvik cache will let my phone boot, but if I had loaded any apps they are all erased and just a placeholder is left on the home-screens. Sometimes I need to do a data
I'm using a newly formatted FAT32 sd card since flashing back to stock and rooting again
I'm running Virtuous 3.0.1, and I have both the stock and extended battery for the phone. My stock battery just ran out of juice, and when I put the extended battery in and started up the phone, I get a series of force closes. Additionally, some apps have magically disappeared - e.g. Handcent. In addition, it has seemingly reverted back to some old settings - e.g. wefi thinks it's just been installed. Weatherbug has a notification that I had previously switched off.
Half my widgets and apps suddenly don't work. And when I try to click on them, I just get a FC error. How can this be caused by switching batteries and how do I ameliorate the issue?
I have a Service with a MediaPlayer which streams audio from the Internet but when I press the Home button and it goes back to the home screen it Force Closes. It's strange though because it works perfectly in the emulator and sometimes it doesn't Force Close on my phone (G1), when I've just turned it on.
This is my code:
CODE:............
Log:
CODE:....................
Would anyone have an idea as to why an app would work on almost every phone that has 2.1 but not the Desire?
One of my apps uses voice input and the Desire is the only phone that force closes when the voice prompt comes up.
The worst part is that I don't know how to test this, I don't have one or know anyone who does.
I finally found out that HTC disabled voice in the Desire and you have to do a work around to install it.
So if you are relying on voice input make sure you use the code in the google example to catch the error:
CODE:......................