so i've had this for a few weeks now, it was working great up until last week, when random apps just started shutting down...today has been the far worst, i can't do anything on it right now except make calls,txting is down and all apps are randomly shutting down..."sorry application.... has stopped unexpectedly" has popped up for just about everything from internet to good framework to other things i didn't get to jot down in time. this is my first flash, and as i stated went initially well but i would like to get my phone up and running normal again, please help, thanks
You could try "Fixing Permissions" from ROM Manager.. however, if that doesn't work.. I'd consider reflashing the ROM. Are you on the stock kernel as well?
I've had problems like these with 2.4 but mine actually just started boot looping after all the fcs I got... I would just fresh install 2.4
Sent from my ADR6300 using XDA App
so phone was pretty much a paper weight on sunday...decided to reflash ROM, working great now....but i do have to ask
-is there a way to prevent this from happening again
-still need to figure out how to update google maps and facebook, will not install from market...thanks.
I don't know of a way to prevent it from happening but, to update those apps just remove and then re-install from the market
worked thanks a lot....have u ever encountered service issues when going thru these rom changes...like txts not coming thru?
well spoke to soon....phone crashed out on me again...really no idea what's goin on..HELP!!! please thanks
edit: reflashing phone...tried fixing permissions to stop force closings..didn't work
throwing in the towel...have followed all steps to a T and still phone continues to crash and force close EVERYTHING and at this point have lost all my data in the process...giving CM7 a shot, hopefully that goes better
cm7 is practically flawless. no sense you have more space for apps
Related
On my G2, I've noticed that previously perfectly working apps will suddenly stop working, giving me a force close error whenever I try to launch them after being installed for a period of time. The only way I've been able to fix it is by uninstalling and then reinstalling the application.
Has this occurred to anyone else? And what should I do to fix this problem?
yes, i had this problem a few days ago...i did a factory reset and everything works fine as of now.
are there any solutions that don't require a wipe?
i had to wipe, and i lost all my mileage records i had entered into the mileage app, and my text messages before i backed them up...
its not too bad when its 2 weeks worth of information... but if this is going to occur often, its not going to be pretty
The two times that happened to me a simple power off/power on worked and they stopped Force Closing. I'm taking it that it didn't work in your situation and the uninstall/reinstall was the only fix?
yea i tried rebooting it several times, but after my latest wipe, nothing bad has happened...
still an issue that should be raised if its been replicated more than once
Ive had this problem with the stock browser and twitter, rebooting seemed to fix it.
Ah, one of those times where fix_permissions would be nice.
I've had to uninstall and re-install several of my apps because they've been force closing.
Sent from my T-Mobile G2 using XDA App
I've had this happen and it was acting really weird before it did it. It did like a vicious reboot and just about any app other than stock got a force close upon opening. It's gotta be software issues, god I hate stock roms. Damn TMobile and trying to restricting our joy of root.
Sent from my T-Mobile G2 using XDA App
This is starting to happen to me on my G2 as well now. I have uninstalled the Apps I could (except the preinstalled ones) and still they are force closing on me. I also have Factory Reset the phone several times and it still is happening. I have already exchanged my G2 once at Walmart for a flickering screen but im pretty sure the 14 days are up now with them. At this point I'm sure I have to call Tmobile.
Anyone have any ideas before I call T-Mobile?
I'm not rooted at all just plain stock.
Thanks
Hey fellas,
So I have came upon the dreaded lag of death. I was opening up my messaging app and the phone froze and said "messaging has stopped". So I hit ok which should close the application, instead it sent me into a spiral of issues that amounted to "System Process Failure" which in turn forced the phone into a bootloop and now it has begun to stay at the HTC screen. I flashed the .312 radio a few weeks ago so I am thinking thats the underlying issue but I do not know. I am running the PAC rom safe version due to this same issue I had on kangdemnation v.5.
Appreciate the help in advanced fellas.
I don't have a fix, but here are a few notes. (currently using 320 radio and Evervolv rom, other roms may act differently but I've used Evervolv since it was available)
I always get Lag of Death within 24 hours after I overclock. I have gone weeks or months without any issues then I OC and I get Lag of Death
Whenever I get Lag of Death I reboot into recovery (4ext currently) make a nandroid Backup, SuperDuperWipe, then Restore the nandroid and everything works. Sometimes I will get Lag of Death one more time, but usually it works without a hitch.
I'm now on the 2/23 Evervolv Nightly and it works great and I will not be overclocking
I have no idea how to OC haha I just installed the PAC with aroma tweaks and thats the one I love to use but keep getting this damn issue.
Lol, that endless boot loop ended up killing my DInc2. Hopefully your phone doesn't end up like my DInc2.
Sent from my Xperia Z
Hey guys, I've just updated this fantastic ROM to the latest version, which seems like a huge mistake...
The problem is I keep getting spammed with force closes. Random apps that run in the background get abruptly closed and I get the message about it. It's quite often.
What's worse is that some apps just straight up refuse to run and force close. Game Guides, Dolphin, Titanium Backup, Ebay, FPSe, Opera, just to name a few...
As I'm sure you can imagine this is a pretty BIG problem. Any help figuring this out would be awesome.
I'm using a Sony Ericsson Xperia Play r800i
Update: I use Link2SD and I figured that maybe that had something to do with it. I un-linked a couple of apps, one at a time, and found that after a restart of the device they'd work again. I still get FCs every now and then on the same apps, but it's progress I suppose and a sign of what the problem could be.
Update 2: I think I figured out the problem. In my haste I didn't think about the Dalvik Cache... Cleared it up and now it seems to run smoother and I haven't seen a FC yet (15 minutes in). Apologies for potentially wasting someone's time.
I was running the SGH-i747M with CWM 6.0.4.7 and testing out some 4.4.2 ROMs, I got another phone to play with now and I gave this one to my girlfriend but she doesn't like nightlies so I was trying to install a 4.2.2 or 4.3.1 stable ROM and they won't work. I read online that it might be due to the CWM being too new because it's support is for Android 4.4.x. So I downgraded CWM and that didn't work either. I ended up convincing her that nightlies aren't that bad and shes currently running Carbon but she hates flashing the new nightlies so I do it for her every few days or so. I've noticed though that this phone is acting up really weird since I tried to downgrade CWM and then install the current one again. Sometimes it reboots at random, I gave the phone to her with BAM 2.0 RC2 (I know, shame on me), and that was horrid, so I tried CyanogenMod and that was "okay" but she said it's boring and she wants more features, so I switched it to Carbon because that's what I'm running on my SGH-i317M and she seems to like that, but it's still acting really weird.
When I was using the SGH-i747M while I was waiting for the new display to come in the mail for my SGH-i317M, I was running BAM and the only thing was it was a battery hog, and ocasionally I would get a "blame tyler" error for some things but it was never repeatable, I switched to Carbon and I was running completely stable on the nightlies, I used it for my day to day and not one problem, after switching over to my SGH-i317M now running CarbonROM, still flawless, not a single problem, fast, good battery life, signal strength is always good, but the phone I was on, running the same ROM, is now glitchy as hell and she's talking about getting an iPhone 5S now.. guys you gotta help me here, I just got her to give up her iPhone 4 for this S3 I gave her, I need this phone working, it is a critical situation lol.
The camera app will take one picture, then the screen will freeze and when I close the app, it opens right back up with the same picture, when I completely close the app, it opens up saying can not conect to camera and the only solution is to reboot the phone. It randomly reboots on it's own some times, the battery doesn't last more then a few hours (between 2 to 3 hours depending on use and when I was using it on Carbon, I got 30 hours off of a single charge once, but the average was around 20 hours of use before it would die) and she was telling me while she's on high brightness but never full brightness, the phone gets really hot so there's something wrong from when I flashed an old CWM using Odin, and then flashed it back to the current one.
So how can I do some kind of full wipe everything and make everything better procedure? Does this exist yet? Is it a real thing?
I'm thinking some kind of recovery wipe, completely wipe everything except the boot loader so I can install a fresh copy of CWM using Odin, and then some kind of AOSP ROM that's stable but I think she likes Carbon now so we might just stick with the nightlies as long as these random force closes and random reboots stop, and the camera works, I mean, you can't instagram without a camera, so that makes this phone nearly useless for her. One picture, freezes, reboot the phone, opens picture from gallery, then hipsters it out, then shares it.. not exactly the seamless method she was looking for lol
Please help guys, I really don't want to see another iPhone laying around the house.. ugh..
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?