Phone randomly freezes, requiring hard reboot - AT&T Samsung Galaxy S II SGH-I777

For a while now, my phone has randomly been freezing, becoming completely unresponsive and requiring either a battery pull or a reboot by holding down the power button. It began a couple months ago while running Task's AOKP ICS with ktoonsez's Fluxi XX kernel. The odd thing is that the phone was stable (ie. no freezes) for the first few months under that setup before it started happening once every few days.
When the frequency of freezes went up to about once a day, I did a full wipe (formatted data and system, cleared cache and dalvik) and flashed Slimbean 2.7 with stock kernel, thinking that maybe something had gotten corrupt in my previous setup. That didn't fix anything, so I flashed ktoonsez's Siyah kernel to see if anything would change. Nothing did, so I kept with that setup (currently on Slim 2.9, Siyah 4.3.3).
The freezing is now occurring anywhere between 1-3 times a day, and I can't for the life of me figure out what is causing it. Sometimes it occurs after interacting with the screen, other times it happens while it's charging and the screen is off. Most recently it occurred around a minute after I changed a volume setting and was in the middle of a Scramble with Friends game.
I pulled the last_kmsg (attached) after rebooting the device; I don't know how to go about recording a logcat due to the random timing of freezing. I also don't know how to interpret the last_kmsg, which is what brings me here.
I did take a perfunctory glance at the file and noticed that the log doesn't seem to be very "clean", in the sense that the output is garbled in several places with random capitalizations and incorrect characters (ex. instead of "ignore request by suspending" on line 30 it reads "ignore bequect bY Suspe&ding"). I don't know if this is indicative of anything, and if it is I would be very curious to know what.
Anyways, if anyone has the time to spare to help me look through this to try to find the cause of my problem, I would be very grateful. Thank you in advance.

nitox.n2o said:
For a while now, my phone has randomly been freezing, becoming completely unresponsive and requiring either a battery pull or a reboot by holding down the power button. It began a couple months ago while running Task's AOKP ICS with ktoonsez's Fluxi XX kernel. The odd thing is that the phone was stable (ie. no freezes) for the first few months under that setup before it started happening once every few days.
When the frequency of freezes went up to about once a day, I did a full wipe (formatted data and system, cleared cache and dalvik) and flashed Slimbean 2.7 with stock kernel, thinking that maybe something had gotten corrupt in my previous setup. That didn't fix anything, so I flashed ktoonsez's Siyah kernel to see if anything would change. Nothing did, so I kept with that setup (currently on Slim 2.9, Siyah 4.3.3).
The freezing is now occurring anywhere between 1-3 times a day, and I can't for the life of me figure out what is causing it. Sometimes it occurs after interacting with the screen, other times it happens while it's charging and the screen is off. Most recently it occurred around a minute after I changed a volume setting and was in the middle of a Scramble with Friends game.
I pulled the last_kmsg (attached) after rebooting the device; I don't know how to go about recording a logcat due to the random timing of freezing. I also don't know how to interpret the last_kmsg, which is what brings me here.
I did take a perfunctory glance at the file and noticed that the log doesn't seem to be very "clean", in the sense that the output is garbled in several places with random capitalizations and incorrect characters (ex. instead of "ignore request by suspending" on line 30 it reads "ignore bequect bY Suspe&ding"). I don't know if this is indicative of anything, and if it is I would be very curious to know what.
Anyways, if anyone has the time to spare to help me look through this to try to find the cause of my problem, I would be very grateful. Thank you in advance.
Click to expand...
Click to collapse
Do you have stock kernel settings? I know underclocking GPU can do that
Sent from my GS4 running CM11 Kandy Kane

I tried to keep all stock settings for the purposes of trying to whittle down the list of possible causes, but I did change the following in ExTweaks:
CPU Step Count: 15 -> 6
Load_H0, Load_L1: 25%, 25% (I think originally was 30%, 23% or something)
Mali Touch Boost level: Step3 -> Disabled
Disabled I/O-Tweaks in Cortexbrain

nitox.n2o said:
I tried to keep all stock settings for the purposes of trying to whittle down the list of possible causes, but I did change the following in ExTweaks:
CPU Step Count: 15 -> 6
Load_H0, Load_L1: 25%, 25% (I think originally was 30%, 23% or something)
Mali Touch Boost level: Step3 -> Disabled
Disabled I/O-Tweaks in Cortexbrain
Click to expand...
Click to collapse
Keep it stock then try
Sent from my GS4 running CM11 Kandy Kane

I should have mentioned that I made these changes a few days after flashing Siyah. During the time that it was stock, freezing still occurred.

My suspicion is that there is some sort of hardware malfunction causing this to happen, considering that it has occurred across both ICS and JB platforms running on different kernels. I would actually be mildly surprised if it is due to ROM or kernel. Still hoping an interpretation of the last_kmsg will reveal more information about this.

nitox.n2o said:
My suspicion is that there is some sort of hardware malfunction causing this to happen, considering that it has occurred across both ICS and JB platforms running on different kernels. I would actually be mildly surprised if it is due to ROM or kernel. Still hoping an interpretation of the last_kmsg will reveal more information about this.
Click to expand...
Click to collapse
Flash stock and factory reset within the ROM after booting up with stock. Just make sure you backup you SDCARD to your PC as it will format your SDCARD. Go from there and see if it happens stock.

Related

[Q] phone shuts off please help

samsung fascinate frimware 2.2.1 its the super freakin clean rom ebo1 for baseband and build number ....the phone just shuts off randomly and i either have to do a battery pull or reboot with the poweer and volume buttons held in originally i thought it was a hardware issue so i got a new fascinate and this one is doing the same thing someone please help me
This typically stems from not wiping data as well as cache prior to flash...
Sounds like you have a rogue app locking the phone up while it's sleeping. I would do a factory reset, then install your apps one at a time until you figure out what's causing it. Allow the phone to sit idle, and maybe even reboot between installs. Allow the phone to settle down and enter sleep between each install and then try to wake the phone after it has been idle for a minute or two.
The other way would be to try looking at logcat with your phone connected to your computer when the screen is on, then when the display turns off and the phone sleeps. Odds are, whatever is causing the problem will be the last thing displayed if logcat stops giving you output. Otherwise, it should just repeat the same thing over and over (I'd assume so anyway) when it's trying to wake up from sleep.
My friend was having a similar problem so he flashed from SC 2.9 to the Deoxed eb01, wiped all the data on his SD card, and reflashed to SC 2.9, he hasn't had that problem since.

EC10 Kernel Problem?

So I can't post in the developer section yet but, I have noticed a problem since flashing to the EC10 kernel. If I have messaging open and in a message if I hit the power button to put the phone e to sleep it crashes and reboots.
I was running, Super Clean 2.9, DL09, EB16, no voodoo
I wiped all data, cache and dalvik cache, then using clockwork flashed the kernel then super clean again.
Now I'm running SuperClean 2.9, DL09, EC10, no voodoo and have the problem?
I'm going to try and reflash everything tonight, just wondering if anyone else expierenced this? I can repeat the problem over and over so its not just a random fluke.
*edit*
So I can crash the phone about 75% of the time, sometimes usually by trying to put the phone to sleep with a program open.
*edit*
So after deleting that particular conversation the problem no longer occurs. Not sure what the deal was.
Im thinking it had something to do with a mms file you recieved or sent
Sent from my SCH-I500 using XDA App
So I spoke to soon, the problem occurs in other things besides messaging.
My phone crashed 20+ times today. I can pretty much cause it crash on purpose at this point. It will almost always crash if I try and put it to sleep without returning to the home screen before putting it to sleep, or before it puts itself to sleep. If I return to the home screen first it really doesn't do it. When it goes to sleep the menu, home, back, search buttons all light up, but the screen is off, if I'm on the phone or have music playing, that continues for 10-15 seconds, then the boot animation appears, and it has restarted.
I do have the log files to if that would help anyone?
I'm so relieved I'm not the only one experiencing this! I was beginning to think that my phone was physically broken or something.
Like Ohio I'm experiencing lots and lots of crashes and restarts when I hit the power button to turn the screen off and even sometimes when the screen goes off on its own, and this happens on SC2.9.2 for me, but I also think it was happening on AOSP with an EC10 kernel, though I'd written it off at the time as a fluke before it started happening every few minutes on SC.
I can make it crash very frequently by pressing the power button while I'm watching a Youtube video or if I am at the glass swipe lockscreen and I press the power button while holding the phone upside down to turn the screen off. Very strange. In addition, it also does it seemingly randomly throughout the day, and it actually did it again not 3 minutes ago for no reason at all as it was just on the homescreen.
I have no recollection of this ever happening before EC10, and I've tried multiple EC10 kernels with UV and standard voltage as well as multiple ROM installs after complete wipes, all of which produce similar results.
I don't know if it's related, but I've also been experiencing freezes where the screen stays on but becomes completely unresponsive, save for the touch keys which will still flash but not make the haptic feedback work. I have to do a battery pull to get it to work again. I can make THIS happen merely by browsing the Reddit Is Fun app for about five minutes, which it has never, ever done before, but I've also had it freeze up on me at other times as well, including two minutes after a SC install where I was just signing into the Market.
I'm going to go back to an EB kernel and see if things go a little better. Are there others out there having these issues with EC10?
I went back to Superclean 2.9.0 with its stock EB01 kernel, and I've had no more issues with the crashes and resets at screen off.
Follow the how to fix all problems in this link. Everything works flawless on mine
http://forum.xda-developers.com/showthread.php?t=1017817
Sent from my SCH-I500 using XDA App
I'm not having these issues. Try to fix permissions and wipe the dalvik cache (under advanced in CWM).
drose6102 said:
Follow the how to fix all problems in this link. Everything works flawless on mine
http://forum.xda-developers.com/showthread.php?t=1017817
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
^^^ this.
Champion thread to remove the issues you've got - especially ones that are tough to track down.
Swyped on my Fascinate - please excuse any swypo's...
This doesn't really address the issue at all.
That link doesn't address this issue at all.

i9300 lock up problems - seemingly at random

Hey guys,
I'm hoping somebody here might have an idea for where I can start to look for this problem, I have had the SGS3 for around a year now, I put CM10 on it initially (from memory), upgraded to CM10.1 when that was released via the nightly releases and I have been running those since.
Recently I updated from a Feb / early March release (cant recall specifically which one) to the next latest (mid to late March I believe) to move from 4.2.1 to 4.2.2. I believe a little after that ( if not that day) I began to very occasionally have small lock up problems with the phone. It would lag out for a short amount of time, or would just completely lock up on the screen its on for a while (if I leave it, it can be between 30 minutes to an hour before it becomes responsive again)
Often I would need to use it so I just end up having to hold the power button in to force a reboot to clear it.
Initially I thought "ok just a bug in a nightly, that's cool, it'll be patched out soon enough", a few days later a nightly came down that fixed a notification bar drop down loop problem I was getting but this other thing has stuck around, depending on how my phone feels its occurring a lot or a little each day, generally seconds / a minute after I start to use it.
I have since jumped around on a few more CM10.1 roms and I have even reverted to the 4.2.1 roms I was using ( I still have them on the phone so I know they are the right ones) to test if its that, but now they are encountering this problem as well.
The phone is completely clear now of user data, I have done a full data clear via CWM and even the original Google "welcome" setup section has locked up more than once in my attempts to set the initial configuration of the phone....
Any thoughts? CWM etc has never had a problem so while it seems to lean toward hardware i'm still thinking its software, maybe a CM10.1 release has updated something else in the phone that's now causing problems, something more firmware related etc?
EDIT: to give some examples, just before I readded my exchange details and started to sync contacts etc, I went into contacts, opened the menu and selected "Settings" to change the first name last name sorting and it just stopped on the settings button, settings was still lit up etc but it was not responsive.
Just now (about 30 minutes later) I have pressed to turn the screen on and its on the lockscreen. Great its back I think, i'll grab the baseband / kernel etc to put in here, I slide it to the unlock and bam, frozen on that now.
more info
I had a play this morning and activated the CPU overlay etc as well as strict mode.
The phone has just done it again in the play store, however the CPU overlay shows nothing out of the ordinary and there was no screen flash to indicate a long run causing a problem.
Interestingly the cursor in the search bar for google play is still blinking, so the phone is still "alive" however i cant control it via the touchscreen or the hardware buttons.
I am trying to dump the log via ADB now however its gotten as far as finding the phone and seems to have stopped (though maybe its still going, i'll see soon hopefully)
Anybody got any ideas? This is driving me crazy and i'm not sure where to go with it now, i guess back to stock is the next option then maybe a warranty claim if thats still possible....
Log collected
Either it was still collecting or it collected after the last event in the log but i've uploaded the log to pastebin here:
http://pastebin.com/Cc20CYZH
The main thing seems to be this:
Code:
W/SQLiteConnectionPool( 6385): Requests in progress:
W/SQLiteConnectionPool( 6385): execute started 646409ms ago - running, sql="COMMIT;"
W/SQLiteConnectionPool( 6385): The connection pool for database '/data/data/com.android.email/databases/EmailProvider.db' has been unable to grant a connection to thread 237 (AsyncTask #2) with flags 0x1 for 646.44104 seconds.
W/SQLiteConnectionPool( 6385): Connections: 1 active, 0 idle, 0 available.
And also this:
Code:
W/InputEventReceiver( 3327): Attempted to finish an input event but the input event receiver has already been disposed.
FYI - that bit at the bottom of the paste about the screen turning off with timeout, the screen has now turned off but i still cant turn it back on etc, soon enough it'll probably reboot (which seems to be what it ends up doing) then it'll be ok again until a problem occurs again.
I'm currently trying a new baseband as recommended here:
http://forum.xda-developers.com/showthread.php?t=2133401
Will post the results after a few days, fingers crossed.
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
BHARGAV33 said:
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
Click to expand...
Click to collapse
I actually never ended up changing back, i flashed the new baseband as above, ran the dumm file generator app a few times (letting it lock up as it went), flashed a new rom a few times as well and after all of that it seems to have worked out all the bad sectors.
Definitely seemed like I was a victim of the beginning of the SDS problem, all due to the fact i had flashed this almost immediately after receiving it and had never updated the baseband.
For those with lock up problems, go to http://forum.xda-developers.com/showthread.php?t=2133401 and follow that for installing the baseband, then do the dummy file generator etc, i'm back to a phone that works properly
PS - It took a few weeks after for it to find and remove all the problems, remember your actual ROM install could be written to bad sectors so i would definitely recommend after you run the dummy file generator a few times to update your ROM at least once, it was after 2-3 updates mine had completely settled down.
PPS - If the dummy file gen fills up your storage then crashes, just go to app info (drag from launcher is the easiest way to get here) and clear the data, that'll delete all the dummy data
PPPS - The dummy file gen can make your phone run terribly as it gets close to full, be patient, its not necessarily the lock up problem but even if it is you need to let it sort it out itself, restarting will make it worse not better.

[Q] Android gets into a hotboot looping state for unknown reason

Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug

[XP][HELP] Phone restarts very often

Hiyas, I think I need some help with fixing my phone to functionalo state.
It started to restart very often (without user interaction and freshly booted).5 to 10 minute intervals approximately. I can't say exactly what might be wrong the phone doesnot otherwise expose any kind of visual problems (poor performance, apps crashing or nonfunctionality).
Is there any common diagnostics for that situation...to get known what's wrong and remove the culprit. Certainly this can be hw fault also (the worst variant).
The phone uses stock ICS, custom kernel, UBL, rooted.//also in the past I encounter freezes and reboots occassionally but not so often as during last two days. May this be a poorly written application? In most recent time I only installed two new apps (Solo Launcher not default and XPrivacy)
bflmpsvz said:
Hiyas, I think I need some help with fixing my phone to functionalo state.
It started to restart very often (without user interaction and freshly booted).5 to 10 minute intervals approximately. I can't say exactly what might be wrong the phone doesnot otherwise expose any kind of visual problems (poor performance, apps crashing or nonfunctionality).
Is there any common diagnostics for that situation...to get known what's wrong and remove the culprit. Certainly this can be hw fault also (the worst variant).
The phone uses stock ICS, custom kernel, UBL, rooted.//also in the past I encounter freezes and reboots occassionally but not so often as during last two days. May this be a poorly written application? In most recent time I only installed two new apps (Solo Launcher not default and XPrivacy)
Click to expand...
Click to collapse
i have this problem with custom kernel A.1.100 FW Release by @DeathZeroFx
No this is not custom kernel but stock. However it is happening too. Today the phone lasted whole day without a restart however at morning it had restarted about 6 or 7 times in a row, being on charger. This points like the restarts happen under some circumstances only.
Sent from LT22i using Tapatalk 2

Categories

Resources