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
Related
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
I have been experiencing some extreme wake-up lag on my R800a running DoomKernel v11 after installing a theme. It's so bad that it takes a solid 3 seconds for the screen to light up and during those seconds, the music is choppy as hell. I wouldn't mind it if it wasn't ruining the music. I first installed this custom ROM http://forum.xda-developers.com/showthread.php?t=1321314 and I noticed the intense lag right away. I thought it was just a glitch in the ROM so I just went back to stock. Then I tried installing this theme http://forum.xda-developers.com/showthread.php?t=1464375 and I got the same problem again. I completely wiped all the user data and started from scratch twice and am still faced with the same problem. The phone runs perfectly when it's awake. There's absolutely no lag anywhere, just on the initial wake-up. I even used an app called Soft Locker so it wouldn't go into deep sleep and set my minimum CPU clock to 1.5ghz and I still got the lag. The theme is way too sexy to just give up so I was just wondering if anyone has encountered this before.
So I tried using the stock kernel with the theme and the wake up lag went away so I guess the DooMKernel was causing the problem, which is unfortunate because I love that kernel. Has anyone else had a similar problem while using the DooMKernel?
Actually SE.Tweaked isn't working well right now.
I have R800a as well, I installed it, and it wouldn't even boot. R800i users seem to have no problems, but R800a and at users seem to be having problems.
As well all ICS roms are in BETA. So things not working properly with all phones/kernels should be expected.
So it's not doomkernel, it's the ROM.
I've got a Verizon G'NEX and I flashed DroidViscious's 4.1.1v1 rom with Franco's kernel about a month ago and everything was smooth sailing up until last week. I've been experiencing random instances of my screen freezing for about 10 seconds followed by my device rebooting. Upon startup right after a reboot I can enter my pattern lock and then it freezes immediately after and reboots (I can tell it's responsive during the unlocking of the pattern because of the haptic feedback). This will happen several times before I'm able to get back to the homescreen without it freezing.
I thought there was a problem with the rom since it was an older build Jelly Bean so I wiped the device and flashed the latest build of Pete's BuglessBeast using his default kernel hoping that would solve the problem. Unfortunately it didn't. I'm still experiencing these random freezes and reboots and the only way I can get it to boot without freezing is to pull the battery out for a couple of minutes and try again.
I'm wondering if the device is thinking it's getting too hot so it shuts down but I don't really have any way of knowing (it happens a lot when I'm in the car or when the phone is charging). Anyone have any ideas on what the problem is and how to resolve it? Or any ideas on how I can debug the problem myself? It's happening fairly often now when I need my phone the most.
The phone isn't even a year old so if relock the bootloader and return it to stock it should be covered under warranty still if there's a hardware issue.
Well, this problem seems to be exclusive to Jelly Bean. I reverted back to ICS and everything seems to be fine. Is anyone else having this problem with Jelly Bean roms?
yeah I get alot of random reboots and some freezes here and there. not sure what it is. but i have to gsm version gnex.
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?