Sometimes, at random, my phone will stop responding. After letting it sit for a little bit, it says that TwLauncher has crashed. This happens when dragging certain widgets to the home screen and trying to use certain apps (Instagram). These crashes do not happen when flashing back to stock via a backup on CWM.
Is there a way to fix this, or am I stuck until an official build comes out?
My current build is IML74K
DrDoctor said:
Sometimes, at random, my phone will stop responding. After letting it sit for a little bit, it says that TwLauncher has crashed. This happens when dragging certain widgets to the home screen and trying to use certain apps (Instagram). These crashes do not happen when flashing back to stock via a backup on CWM.
Is there a way to fix this, or am I stuck until an official build comes out?
My current build is IML74K
Click to expand...
Click to collapse
Try wiping cache and Dalvik in recovery.
Related
Is this the right place to post this?
Inspire 4G Rooted, S-OFF, Clockworked with Bubby's One Click, and attempted to flash CM7.
I can make it past the set up, all the way into the phone. Shortly after, it will just kind of randomly freeze up and go through the boot animation again and then take me to a lock screen. I can unlock it and go back into the phone, but it will almost immediately freeze and go back to the boot animation again.
Flashed 3 times, once on RC2 and twice on RC3, using ROM Manager 3.0.1.0, Clockwork 3.0.0.6, wiping data and cache each time.
Please help!
Did this happen when you were turning on Wifi?
Now that I think about it, the most recent flash I did, yes it did occur when I turned on Wifi...but I am not sure about the other times.
What would wifi have to do with it?
wberry85 said:
Now that I think about it, the most recent flash I did, yes it did occur when I turned on Wifi...but I am not sure about the other times.
What would wifi have to do with it?
Click to expand...
Click to collapse
Its a known niggle with almost every CM build. It doesn't like wifi on the first boot. Let it come to the launcher screen and then reboot the phone. Things should go smoothly after that.
same thing happened to me. I just rebooted it a few times and problem solved. Had no idea that wifi was the problem though.
Awesome! Flashing now...
This works!!
Thanks again guys...
I woke up today to some problems. My S3 would boot up and everything but the touch screen was unresponsive and I was stuck at the lock screen in landscape orientation. I had no idea what was going on so I used odin to flash the stock root66 image to try to fix my phone and now I get stuck at the 4G LTE boot screen. Does this mean that there is some sort of kernel issue? If not, does anyone know what is going on? And how would I fix this problem?
EDIT: I fixed it by odin-ing back to a the stock image but now for some reason my messaging app FCs constantly and I can't use it. I installed Go SMS Pro and it works but it does not display any sort of message. It tells me that I have new texts and whatnot but the conversation is blank. I'm going to try to do a full wipe and restart from there
Having the same issue trying to get SMS to work on the GalaxyMod ROM, it'll boot to the rom, but say I have no service. Bummer. But you can always boot to recovery mode and restore a backup; that always works just fine for me, so that you have a working phone in the meantime.
gseyffert said:
Having the same issue trying to get SMS to work on the GalaxyMod ROM, it'll boot to the rom, but say I have no service. Bummer. But you can always boot to recovery mode and restore a backup; that always works just fine for me, so that you have a working phone in the meantime.
Click to expand...
Click to collapse
I could not get into recovery to do anything of that sort. I used Odin to push the full wipe verison of the stock, un-rooted firmware and now I have a working device. The only problem now, other than losing a lot of data, is the fact that my phone memory is only showing up as 11.8gb.
That isn't a problem as even though your phone says it is 16 GB but like all devices it needs a certain amount of space for the OS files.
I have been trying to fix a recurring force closing of the stock Charge messaging app that happens at random times even after a fresh ODIN install of the stock/factory ep4d + Updates ROM or rooted Deodexed stock or Tweaked lite 1 ROM flash and I use the same ODIN and ZIP files that I've had that always worked b4. I have also had a sporadic (afaik) loss of text messages or sometimes receiving the text but no notification. The force close seems to happen randomly when I am in another app and the screen will freeze for about 2 seconds and then I get a force close usually of the mms app though the same has occurred once or twice from other apps including YouTube. This does not seem to be the problem of other apps that I later install because as the image attached shows, it starts happening even before I have set the phone up after an ODIN flash of the factory image. FWIW, the verizon 411 bloatware app always force closes also when I turn the phone on for the first time after ODIN/Stock flash. Any ideas on what could be causing this or what else I could try to resolve this would be greatly appreciated. Below is 2 of the message that popped up on first boot after this last time I Odin'd back to stock- There were actually 2 mms and 1 411 app force closes within 5 minutes of startup. Thanks in advance for any ideas.
You may want to wait on updating to D80020y. Here's why;
In my experience, the update has corrupted the System UI process causing
*crashes on lockscreen/boot
*crashes to home while attempting to use an app
*apps to restart infinitely and drain battery.
*break lock screen and standby functions (KnockOn and power button) causing you to be unable to wake or enter passwords to your phone without force shutting off phone.
*There is a 50% chance of this bug happening to you on/after boot. If your phone is not experiencing these crashes; do NOT shut it off!
*Safe Mode will NOT prevent these crashes, System UI may still crash.
*My firmware before the update was STOCK rom before I updated on 9/7
TEMPORARY WORKAROUND: If you are able to access home screen, let the phone sit for a few minutes after booting and "warm up" after this period of time; apps will stop restarting and allow the UI to become stable.
I've been using 20y since getting the update, no issue at all.
Were you on stock or custom ROM?
votinh said:
I've been using 20y since getting the update, no issue at all.
Were you on stock or custom ROM?
Click to expand...
Click to collapse
No, I was always on stock AT&T rom. Never rooted either. If I remember correctly, the problems didn't appear until I rebooted the phone a few hours after updating. Maybe it is just me
Try factory reset and see if it gets any better.
Hi all!
My S7 is unrooted, completely stock, running latest 6.0.1 official update
Few days back I updated some apps from the play store and after that, my phone suddenly restarted on its own
This sudden restarting kept on increasing and currently the device boots up for a few seconds, and then freezes and restarts again
I know there's some faulty app that's causing the restarts, because once i managed to turn the UPSM on before the device restarted and it worked fine, with all the apps disabled
I have tried to get a logcat to look for the issue but I can't do that properly as I haven't taken any logcats before and i'm not familiar with the process
I have already tried to flash the stock firmware but that didn't help either
Is there any way or solution to get this fixed? Or can anyone here help me on how to get a logcat so that I can look for the error causing app?
There's a lot of stuff on my phone and I can't risk losing it by factory resetting it
I would boot into safe mode, backup my data first. Then start uninstalling apps I do not need and see removing which one fixes the issue.
munchy_cool said:
I would boot into safe mode, backup my data first. Then start uninstalling apps I do not need and see removing which one fixes the issue.
Click to expand...
Click to collapse
I've booted into safe mode as well, but that isn't helping either
The same keeps happening in same mode as well. The device boots up, and after some 30 seconds it freezes and restarts and gets stuck in a loop