Related
Couldn't see anything about a general jerky S2 here - hope I'm not duplicating something...
I have a T-Mobile UK Galaxy S2. I've had it a week and its my first Android phone so I'm not super experienced with it. I am rooted running:
Android version 2.3.3
Kernel KF3
Build Number BOKF3
About once per day the phone becomes very jerky and unresponsive. If I am navigating the menus or flicking up a long menu screen the motion isn't smooth. Similarly if I am using Swype my swipes often get interrupted by this freezing motion. The phone just doesn't keep up with my finger and in end up with an incomplete word. In the web browser it takes a while to register my finger on the screen and often when I try to scroll, I end up clicking.
The problem goes away if I turn off the phone and restart but I have not been able to find a way to resolve it without doing this.
I have tried: ending all apps; clearing ram; using advanced task killer.
Only a reset seems to make a difference. I can then be OK for the next few hours, but I think I've had this problem at least once per day since I've had the phone.
I've not notice it being triggered by any specific app.
Can anyone help me fix this? Is there anything I can install to see what might be going on? Anyone else had the problem?
Any help really appreciated
Backup all data and factory reset as first step ..
jje
Can you advise what my best way is to do that given my current situation.
I didn't make a backup pre-root. Is this a problem? Is it just a matter of connecting to Kies to do the factory reset? Or do I need to use other tools/locate the original kernel.
There is nothing on the phone that I need to back up (other than a few paid apps which I believe I can use Titanium (free) to backup right?
Thanks
Update: Backed up my apps with "file expert", did the factory reset, downloaded fresh copies of only the apps I really wants and so-far-so-good. Thanks again.
Problem seems to have reappeared. Was using the phone this morning and it became all jerky again. Can anyone suggest other things I can look at?
thanks
If you are still on old KF3 ROM, consider upgrading to KG3 or wait few days KG6 will be released.
I see signs of kg6 in the other forums. is the version I need out now?
Im really keen to gert this shorted as the jerk is driving mr madit seemslike a pylsetjayfreezes the phone. If I am in my contacts list i can flick the screen and make the list scroll fast down.but it stops for a second then continues on its way.normally when it happens it happens s second time just when the scroll is slowed right down. Its like there is something running on the phone causing it every 1.5 seconds.
Im worried my phone is defective as none else seems to have this problem.
Any pointers to three correct kg6 our other solutions much appreciated.
Cheers
Sent from my GT-I9100 using XDA App
Well a couple of months later I still have the same problem. I'm now running KH3 and the problem is persisting. I've also noticed that the 'jerk' interrupts the filming of video so anything recorded while it is happening ends up with little skips in the video and out of sync audio.
I've also tried an app from the market "fast reboot" but that doesn't solve the problem. I still only get a temporary fix by turning the phone completely off and then back on again.
Does anyone know the process for returning a phone to T-Mobile UK? Am I going to be without a phone for ages? A friend who also has a SGS2 on the T-Mobile network but purchased from Carphone Warehouse is convinced it that it is the fact it is a T-Mobile direct phone that causes the problem... but they can't all be like this???
Otherwise, is there anything else I can try to troubleshoot what might be happening. There must be *something* that starts running on the phone that causes this jerky behavior but I just don't know how to identify it.
Any help much appreciated - thanks!
Well, that's definitely not normal. Sounds like an hardware issue to me. A friend of mine got his SGS2 from T-Mobile Shop Austria (with branding) and he doesn't have this issue.
- Maybe your homescreen is overloaded with widgets. Try to remove some Widgets, like Program Monitor (caused me some jerking).
- Do a factory reset (settings/privacy/factory data reset). don't forget to backup your data.
- Try to flash a different Rom (full wipe) with Odin, like KI3 (2.3.5) or a Custom Rom . I'm personally using CheckRom Revolution and I'm really happy with this Rom. However you'll lose your T- Mobile branding and your warranty, if you root your phone. Don't forget to backup your current Rom and buy / use a USB JIG to get the warranty back, if it doesn't solve your problem.
Well, I personally doubt that any of these methods will help your problem.
If nothing helps, then talk with T-mobile ... maybe they'll instantly replace your GS2 with a new one, if you explain the situation in detail. Try to put some pressure on them^^ Otherwise you have a couple of weeks to wait, because T-Mobile will most likely send your damaged phone to Samsung.
good luck.
My SGS3 works just fine for 2 weeks, until now.
Suddenly, it keeps randomly crashing and reboot into samsung s3 logo screen.
Oh, I have tried different roms (and stock rom also) but the crash still happen.
I also have tried wiping cache, dalvik, clean install, removing external sdcard, and restore factory setting. But none was effective.
Any ideas?
I had a similar issue with my Atrix and it turned out to be the SIM Card. Had it replaced and no more random reboots. I figured this out by checking the panic dumps...maybe there is a similar way to check this on the SGS3
jiggytom said:
I had a similar issue with my Atrix and it turned out to be the SIM Card. Had it replaced and no more random reboots. I figured this out by checking the panic dumps...maybe there is a similar way to check this on the SGS3
Click to expand...
Click to collapse
Thanks for the response.. I tried it just a moment ago without sim card, and it still got the random reboot..
Any other people who got the same problem?
Is the phone unusually warm? The phone will automatically reboot if it overheats, but that wouldn't normally happen unless it's been left in the sun or overclocked.
I can get mine to go into a reboot loop if I play Asphalt 6 while outdoors, but the problem goes away as soon as I let it cool off for a minute or two.
devonck said:
Is the phone unusually warm? The phone will automatically reboot if it overheats, but that wouldn't normally happen unless it's been left in the sun or overclocked.
I can get mine to go into a reboot loop if I play Asphalt 6 while outdoors, but the problem goes away as soon as I let it cool off for a minute or two.
Click to expand...
Click to collapse
yes, the phone (when i use it) is usually warm, but my phone also crashed while not in warm state.
but this crashing-reboot problem just show up after 2 weeks of normal (and not any crash experience) usage.
this crashing problem show up after i played temple run btw (not sure is relevant)
aquavalanche said:
My SGS3 works just fine for 2 weeks, until now.
Suddenly, it keeps randomly crashing and reboot into samsung s3 logo screen.
Oh, I have tried different roms (and stock rom also) but the crash still happen.
I also have tried wiping cache, dalvik, clean install, removing external sdcard, and restore factory setting. But none was effective.
Any ideas?
Click to expand...
Click to collapse
Sorry to hear that man. Had a SGS with same issues. maybe Samsung has hurried releasing galaxy S3
I'd factory reset and only put on the important apps you use. Depending how long it takes for you to normally get a reboot you can slowly add new apps back to narrow it down. I had the same problem last year and thought I had a bad sgs2. But it turned out to be dolphin hd browser at the time that caused it and haven't had a reboot in a year. It could be something similar in your case. Hopefully its software related and not hardware
Sent from my GT-I9100 using XDA
blue265 said:
I'd factory reset and only put on the important apps you use. Depending how long it takes for you to normally get a reboot you can slowly add new apps back to narrow it down. I had the same problem last year and thought I had a bad sgs2. But it turned out to be dolphin hd browser at the time that caused it and haven't had a reboot in a year. It could be something similar in your case. Hopefully its software related and not hardware
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
i just tried flashing normal ROM, after booting to "get started" page, approximately 3~10 seconds, my sgs just rebooted over and over again, until it show only black screen with battery icon on it (i think it may be charging animation while the phone is turned off).
ahhhh this is driving me insane!!
update : i just flashed hypergalaxy ROM and currently it is stable and not experienced crashing (yet ).
i'll give further report later today
Sent from my GT-I9300 using XDA
Have you tried reinstalling FW with Odin? If yes does it still reboot after a factory reset with nothing installed?
yes, i have tried flashing stock rom using odin a few hours ago, but the crashing still happen.
my sgs3 now stuck at boot-standby5sec-crash-reboot loop.
so, i decided to bring my sgs3 to samsung service center tomorrow. hope they will replace it with a new unit
UPDATE : Samsung replaced my new SGS3 with a new hardware (not sure new device though, the flash counter reset to zero )
the problem seems to be hardware related
thanks for all your reply to my problem
aquavalanche said:
My SGS3 works just fine for 2 weeks, until now.
Suddenly, it keeps randomly crashing and reboot into samsung s3 logo screen.
Oh, I have tried different roms (and stock rom also) but the crash still happen.
I also have tried wiping cache, dalvik, clean install, removing external sdcard, and restore factory setting. But none was effective.
Any ideas?
Click to expand...
Click to collapse
I am having the same issue, I've had my phone since Saturday (6/23/12) and it crashes, reboots, apps crash, internet crashes, email crashes, etc. I can udnerstand a lot of apps may not be updated to ICS.. but no matter what I do.. everything crashes.. It's a bit ridiculous. I am a prior iPhone 4S user and am probably going to return this phone. I can't do much without it crashing or the screen freezing.. not being able to do anything for 2-3 minutes, etc. And they couldn't port any of my numbers from my prior phone because they didn't have the software update to do so yet. So overall, bad experience with the Galaxy.. and maybe I should have waited longer before buying this phone to work all the problems.
Krayjee said:
I am having the same issue, I've had my phone since Saturday (6/23/12) and it crashes, reboots, apps crash, internet crashes, email crashes, etc. I can udnerstand a lot of apps may not be updated to ICS.. but no matter what I do.. everything crashes.. It's a bit ridiculous. I am a prior iPhone 4S user and am probably going to return this phone. I can't do much without it crashing or the screen freezing.. not being able to do anything for 2-3 minutes, etc. And they couldn't port any of my numbers from my prior phone because they didn't have the software update to do so yet. So overall, bad experience with the Galaxy.. and maybe I should have waited longer before buying this phone to work all the problems.
Click to expand...
Click to collapse
I'm very sorry that u have these problems.but there will always manufacturing faults when making so many units.only one thing to do,return it and get a replacement.when u get a fully functional galaxy u won't regreat it,it's a awesome phone.Samsung usually replaces the phone,so I think they will do the same in your case.anyway best of luck
After all the problem I've been through, finally I send my phone back to samsung service center.. they tried to reinstall stock rom several times, and in the end, they change the IC board to a new one.. and it does solve my probs..
SGS3 tebooting
Hi guys here is a peace of my experience
Bought the phone last year in November .2 weeks everything fine then it starts rebooting itself.retun it to the mobile provider and get it back in 3 weeks with conclusion that they experience the reboots as well and that the phone had some kind of software issue.in 3 hours i was back in the shop with my phone rebooting again.they send it again to service got it back yesterday with 4.1.1 android and they sad it may be caused with wrong customizing or not supported sd card,turned on the phone and had few reboots manage to update to 4.1.2 and today heavy gaming internet etc and no reboots so far.will test it till wendsday and see what happens.if it will reboots again then its going back to service and this time it is the 3 time so i will get a new phone.
Hi all,
My Galaxy S II keeps crashing. The phone will just power off and the battery will drain right out and the only way to turn it back on is take the battery out then charge it again. Sometimes if I am quick and realised it has crashed I can take the battery out and turn it back on and the battery will have drained 30% in an hour.
Does anybody know why the phone might do this or is there a way I can track whether something in particular is crashing the phone via a log or something like that?
Thanks
Yes there are apps that can do that.
So whats the score.......are you on latest o2 or latest unbranded.
Post the about phone details lol.
Hi,
It is on the latest H3G UK firmware and is unlocked via the Galaxy S Unlock app by Helroz (so via nv_data.bin)
4.0.4
I91000NELP4
Build: IMM76D.XWLPY
Any ideas and what is the app called?
Thanks
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
zetsuboumeow said:
Hello,
Just thought I would take this opportunity to join this thread since I have been suffering from a very similar (if not identical) problem on my S2 too. It's quite lengthy, apologise for that - hope to give as clear a picture as possible:
- S2 originally from vodafone contract, am now with giffgaff
- 1 year and 6 months old
- not rooted, have always used Samsung official firmware
- updated to ICS 4.0.4 about a month ago(?)
- Kernel version 3.0.15-1056084, build number: IMM76D.BULPG
I must say I can't be certain if the random crashes started (it would sometimes heat up really hot, or sometimes not warmed up at all), phone will just turn off. Can't turn back on without taking battery out and re-inserting.
Similarly, the battery level will drop by 30+% once the battery is re-inserted.
Glad to know it is not just me. I'm hoping I can get an app that will log what is going on right up until crash time!
Have experienced once where it started up in "safe mode" and although everything was still there, the apps I have put in folders were all listed cos the folders were gone. Restarted and it wasn't in safe mode anymore, but had to create new folders and sort my apps again.
The random turn offs can happen every few days, or twice a day. Don't know why it happens.
I haven't installed many new apps (some are by japanese developers but worked fine before and after I updated firmware), asked at a Vodafone store and they suggested it could be a battery problem. (offered to send it off for repair, but will take 7-10days and factory reset, which I want to avoid...)
So bought and changed a new battery (from Samsung website) which looked good (no random shut downs for a week) but it all started again last night. So it's not the battery.
Suspected it's most probably software problems.
After upgrading to 4.0.4 firmware, the phone cannot display phone serial number/network etc etc under the "legal information" in settings.
The battery log seems funny too, I would re-insert battery and restart, the battery log will still show it's been on battery for 20+hours.
I've also spotted that there're 2 OS running when looking at the battery log - when I upgraded from gingerbread to ICS, I did not do a factory reset (is that absolutely necessary?) but phone has been working perfectly for a few months after the upgrade so I thought nothing of it....
I wanted to post a screenshot but not allowed cos I'm new to forum... =(
Is it because there're 2 OS so it's clashing...?
Since I haven't rooted, I'm not sure what I can do - last resort is to wait until JellyBean rolls out from Samsung and factory reset when I upgrade?!
Hope I've given enough info to get help easier.
PS: Kies is testing my temper. Tried to solve the "this device is not supported by KIES" problem by reinstalling whilst not connected to internet, kind of worked, allowed me to backup small files (such as call logs) but when it comes to big bits e.g. photos, it will show the "unexpected error" message again.....
also got "wssyncmlnps has stopped" on my phone...
ARGH!!! just wana backup my stuff before it completely turns into a brick!
Click to expand...
Click to collapse
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Rackers said:
So glad it is not just me. I'm hoping I can use an app to log what is going on when crash time happens. Can someone tell me what the app is called please?
Click to expand...
Click to collapse
Me too facing above all,unfortunately riding in same boat.
I installed jellybam 7.4 the day it was released and since then I had an issue where the phone would regularly freeze with the only way of fixing it to restart the phone (holding in the power button).
I had originally just upgraded without wiping the phone, so figured last night I'd do a complete wipe (zoots megawipe) and start again. However today I am still getting the same freezes (in fact twice in the last 10 mins!).
Any ideas what might be causing this? Is there any diagnosis app that i can run to see what's causing the freezing?
I wiped again today and installed 7.5 and still the same issue.
Thanks in advance!
I'm having the sort of the problem so I thought I could borrow this thread since our problems seems to be similar.
Can boot the device without any problems, but it freezes randomly.
Tried:
* Different roms (want to use Slim Bean and are currently using it)
* Full wipe / Factory reset
* Wipe cache / Dalvik cache
* Not allowing Android to restore my apps after factory reset (in case some app was causing this)
* Tried latest Perseus kernel (but got a bootloop so reflashed everything)
http://forum.xda-developers.com/showthread.php?t=2133401
the solution...
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Very bad Samsung After Sale Services
I'm very unhappy with Samsung
I got the same problem. Cannot use it because the screen freezes all the time so I need to unplug the battery for restart each time.
Then I decided to sent my phone to Samsung repair services. After 2 weeks, they sent it back to me.
Back to home, I turned on my phone and made a reset for the first installation but when I tried to connect into my google account, the screen has been frozen once again !!!. Then after and after ...
So the screen touch issue has not been solved even if my phone just came back from Samsung repair services. !
According to the repair document, they has just reinstalled the firmware but did not take care of the hardware.
So if this problem is well known why Samsung did not take care of this problem correctly ?
Now, They keep my phone for more than 4 weeks and did not give me a decent replacement phone with 3G at least.
For those who has got this problem, I recommand you to write clearly the problem with a letter joined to your request for the repair services before you send your phone.
Thanks.
nhariamine said:
http://forum.xda-developers.com/showthread.php?t=2133401
the solution...
Sent from my Supercharged V12 Samsung Galaxy S3 using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer
Really hope this is the cause and fix for our collective problems.
Update:
After doing what I was told to do in that post the freezing was significaly lower. They still occur but not as much, from 40 times yesterday to 1 today so far.
Unfortunately I came across that thread a couple days ago, have tried the DFG method lots of times and I still get freezes. Now arguably they aren't now as frequent, but I've had days where it doesn't freeze at all, so that may just be luck.
Possibly stupid question... Are you able to flash a new firmware whilst keeping your custom ROM?
I have as SM-G991U (256 GB S21 US version, stock everything but using Nova Launcher) that is randomly freezing/crashing then rebooting on me 1-2 times/day. Does android have any kind of crash log I could look at to try and figure out what's causing the problem? On the samsung forums, their support reps suggest running in Safe Mode, which I have, but it's not very useful because I can't reproduce the problem on demand and it usually happens 1-2/day, but sometimes less, so unless I just ran in safe mode all the time, that wouldn't tell me much. Plus, it would only tell me it's an issue caused by one of a hundred or so apps which, again, is not helpful.
So I'm hoping there is a crash log or something somewhere because I have no idea what triggers the crashes. The other night, it was sitting on a wireless charger, the screen wasn't on, then all the sudden it rebooted. It's not specific to any app or anything I'm doing. If there are no crash logs (which would be frustrating and disappointing), any other troubleshooting ideas are welcome!
Look for a memory leak. Typically a poorly written 3rd party apk.
Try clearing system cache.
Make sure auto restart isn't enabled...
dougleto said:
I have as SM-G991U (256 GB S21 US version, stock everything but using Nova Launcher) that is randomly freezing/crashing then rebooting on me 1-2 times/day. Does android have any kind of crash log I could look at to try and figure out what's causing the problem? On the samsung forums, their support reps suggest running in Safe Mode, which I have, but it's not very useful because I can't reproduce the problem on demand and it usually happens 1-2/day, but sometimes less, so unless I just ran in safe mode all the time, that wouldn't tell me much. Plus, it would only tell me it's an issue caused by one of a hundred or so apps which, again, is not helpful.
So I'm hoping there is a crash log or something somewhere because I have no idea what triggers the crashes. The other night, it was sitting on a wireless charger, the screen wasn't on, then all the sudden it rebooted. It's not specific to any app or anything I'm doing. If there are no crash logs (which would be frustrating and disappointing), any other troubleshooting ideas are welcome!
Click to expand...
Click to collapse
Hi mate
For logs info check here and here
You can always flash firmware , using home_csc , to avoid factory reset the phone , if the problem is system related it will help
If is app related
Try booting in safe mode to see if problem goes away...
MAX 404 said:
Hi mate
For logs info check here and here
You can always flash firmware , using home_csc , to avoid factory reset the phone , if the problem is system related it will help
If is app related
Try booting in safe mode to see if problem goes away...
Click to expand...
Click to collapse
Thanks! I'll definitely try these out. I tried safe mode, the trouble is it's not really great as a diagnostic because the phone will go from 4-24 hrs between resets during normal operation, and since a phone in safe mode isn't terribly useful, it's hard to keep it in safe mode for long enough to see if that fixed the issue, if that makes sense. And then, if it did fix the issue, it just narrows it down to 1 out of a hundred apps! But maybe I'm missing something. Is there additional information I can find if I run in safe mode that would help suss out the problem?
blackhawk said:
Look for a memory leak. Typically a poorly written 3rd party apk.
Try clearing system cache.
Make sure auto restart isn't enabled...
Click to expand...
Click to collapse
Thanks! I know how to clear cache but not how to check for memory leaks. Do you have a tool you'd recommend to do that? And I had never heard of auto restart before, so thanks for that. I confirmed that it is NOT enabled (that would have been a face palm moment!).
dougleto said:
Thanks! I'll definitely try these out. I tried safe mode, the trouble is it's not really great as a diagnostic because the phone will go from 4-24 hrs between resets during normal operation, and since a phone in safe mode isn't terribly useful, it's hard to keep it in safe mode for long enough to see if that fixed the issue, if that makes sense. And then, if it did fix the issue, it just narrows it down to 1 out of a hundred apps! But maybe I'm missing something. Is there additional information I can find if I run in safe mode that would help suss out the problem?
Click to expand...
Click to collapse
Is not easy , you just need to be methodic
See if you can find anything useful in the logs first
Reflash firmware , use home-csc , see if it help
Have you notice if the phone fails under any specific circumstances?
If that does not help and if you can really relate the problem with any specific app you may try to freeze or uninstall suspicious app and let it run for a day , Package disabler app is a good option , it is easy to enable or disable app but is not free, you could try this one , is a debloater tool , it allow you to disable app... may be easy that having to uninstall / install by hand
I'm also having the same problem. Had the phone since June, it didn't start to occur until late August, which leads me to suspect it is an update related issue.
GillBates21 said:
I'm also having the same problem. Had the phone since June, it didn't start to occur until late August, which leads me to suspect it is an update related issue.
Click to expand...
Click to collapse
I'm glad you posted today, I've been meaning to post again here because I tried troubleshooting and am still having issues. In fact, it crashed twice today when I was trying to send a text message.
I installed one of the log applications (can't remember which one at the moment) but it wasn't really helpful. They didn't seem to catch any information related to a crash even though they were logging data at least twice when it crashed.
Then I tried reflashing using home-csc using ODIN and that ended up soft-bricking my phone (and yes, I followed all the instructions and used home-csc) so I had to reflash everything and do a full factory reset. That seemed to help, reducing the crashes from once/day to once/2-3 days for a few weeks, but now it's back to ~once a day (sometimes more, sometimes less).
So if anyone has any other idea, I'm all ears. When I was reflashing and stuff, I noticed in the recovery mode (or whatever it's called) options that you can look at logs. Does anyone know if one of those logs would have crash-related data or any other ideas of what to try? This is incredibly frustrating, especially that it's persisting after a factory reset. Argh!
dougleto said:
I'm glad you posted today, I've been meaning to post again here because I tried troubleshooting and am still having issues. In fact, it crashed twice today when I was trying to send a text message.
I installed one of the log applications (can't remember which one at the moment) but it wasn't really helpful. They didn't seem to catch any information related to a crash even though they were logging data at least twice when it crashed.
Then I tried reflashing using home-csc using ODIN and that ended up soft-bricking my phone (and yes, I followed all the instructions and used home-csc) so I had to reflash everything and do a full factory reset. That seemed to help, reducing the crashes from once/day to once/2-3 days for a few weeks, but now it's back to ~once a day (sometimes more, sometimes less).
So if anyone has any other idea, I'm all ears. When I was reflashing and stuff, I noticed in the recovery mode (or whatever it's called) options that you can look at logs. Does anyone know if one of those logs would have crash-related data or any other ideas of what to try? This is incredibly frustrating, especially that it's persisting after a factory reset. Argh!
Click to expand...
Click to collapse
So what I tried to do is roll back all the default google app updates. Ex: Android system webview, Google app itself, etc etc. I factory reset it without backing up any apps (but pictures and messages etc), It was working for a few days and then it happened again. Which further reinforces my thinking that my problem is software based.
GillBates21 said:
So what I tried to do is roll back all the default google app updates. Ex: Android system webview, Google app itself, etc etc. I factory reset it without backing up any apps (but pictures and messages etc), It was working for a few days and then it happened again. Which further reinforces my thinking that my problem is software based.
Click to expand...
Click to collapse
So I'm curious why you think that means it's a software issue. If this isn't a widespread issue with the S21 and after we've both done a factory reset and still have the issue, that makes me think it could be a hardware issue. Of course, there could be some software incompatibility with an app that most people don't have installed or a bluetooth connection or something, which is why I really want to find a useful crash log (and find it rather absurb how hard it is to find a useful crash log on android, come on guys, it's a mature OS, some kind of crash log seems pretty basic!), because otherwise, it could be a ton of issues and I can't reproduce it. Ugh.
The reason is that the "few days" after the reset and restoring pictures, messages (but not apps) from backup, where there were no crashes at all (where previously it would happen at least 2 times per day).
GillBates21 said:
The reason is that the "few days" after the reset and restoring pictures, messages (but not apps) from backup, where there were no crashes at all (where previously it would happen at least 2 times per day).
Click to expand...
Click to collapse
Got it, that makes sense. I'm on t-mobile and just got an update this morning. We'll see if that improves anything because my device restarted 4 times yesterday
I havent had a crash like this since i disabled chrome and other google stuff, and downgrading google apps lol.
GillBates21 said:
I havent had a crash like this since i disabled chrome and other google stuff, and downgrading google apps lol.
Click to expand...
Click to collapse
How did you disable chrome and what other google stuff did you disable? (There's obviously quite a lot of google services that can't be disabled)
After the most recent monthly update, my phone has gone from rebooting multiple times/day to once every 2-3 days, which is more manageable but still super annoying. It is incredibly frustrating to me that there are no good tools to troubleshoot a crash (at least that I've ben able to find). Honestly, it's driven me to consider an iPhone for the first time in my life .
My trouble is back... I will be scheduling a fix with samsung soon so I can RMA it
Check the below link. This seems to be a hardware problem which got solved after Samsung replaced the motherboard.
Samsung Restart problem
So I bought this phone for my wife. Since I received the phone, after a day the phone started crashing whatever app she was on and then take you back to lock screen without having to go through a full restart process but it was definitely a restart as you would need to enter your pin again as opposed to fingerprints.
Since it was within 15 days of purchase I returned and reordered another one from Samsung, and to my surprise exact same issue. What are the odds of having two brand new phones having exact same issues.
This leads me to believe it must be a software issue. I just received this 2nd new phone last Friday.
Yeah, I think what I was experiencing was a hardware issue (it definitely went through the full restart process, not what is described in the previous post). And from the link posted by sandystays above, it looks pretty common. I contacted Samsung support and was not impressed at all. They walked me through a number of troubleshooting steps that weren't helpful then had me take my phone to UBreakIFix. I did, they ran a diagnostic and their tools couldn't find anything wrong so they said Samsung should replace it.
Contacted Samsung, told them I had taken it in. They said I needed to take it to a technician (again, right after telling them I just had). They then said, oh, you'll have to mail it to us and you'll get your phone back in 7-10 business days. Their suggestion for what to do for a phone in the meantime? Buy a prepaid phone then return it when I get my phone back (which a) is unethical and b) wouldn't work anyways since they're locked). Ridiculous. They also admitted that this is a very common problem, so I asked why they just won't send me a replacement device if it's so common to which they had no real answer, just "that's our policy".
Eventually, I contacted T-mobile (my carrier) and was very pleasantly surprised. After me telling them the issue and the steps I'd taken to troubleshoot it, they sent me a replacement phone (recertified, but still) that arrived in 2 days. WAAAYYYY better than Samsung. The entire process made me a bit jealous of my wife's iPhone. If she had had a similar issue, we could have taken it to an apple store and not had the whole "our policy is that you have no phone for 7-10 business days" nonsense from Samsung AND the backup and restore process is still way better on iPhones than on any android I've ever owned. How there is no easy and reliable backup/restore mechanism on android after so long is beyond me.
Bottome line: if you have a similar issue, it's very likely a hardware problem (my replacement phone has been fine for 3 days now). And avoid Samsung support if you can!
dougleto said:
Yeah, I think what I was experiencing was a hardware issue (it definitely went through the full restart process, not what is described in the previous post). And from the link posted by sandystays above, it looks pretty common. I contacted Samsung support and was not impressed at all. They walked me through a number of troubleshooting steps that weren't helpful then had me take my phone to UBreakIFix. I did, they ran a diagnostic and their tools couldn't find anything wrong so they said Samsung should replace it.
Contacted Samsung, told them I had taken it in. They said I needed to take it to a technician (again, right after telling them I just had). They then said, oh, you'll have to mail it to us and you'll get your phone back in 7-10 business days. Their suggestion for what to do for a phone in the meantime? Buy a prepaid phone then return it when I get my phone back (which a) is unethical and b) wouldn't work anyways since they're locked). Ridiculous. They also admitted that this is a very common problem, so I asked why they just won't send me a replacement device if it's so common to which they had no real answer, just "that's our policy".
Eventually, I contacted T-mobile (my carrier) and was very pleasantly surprised. After me telling them the issue and the steps I'd taken to troubleshoot it, they sent me a replacement phone (recertified, but still) that arrived in 2 days. WAAAYYYY better than Samsung. The entire process made me a bit jealous of my wife's iPhone. If she had had a similar issue, we could have taken it to an apple store and not had the whole "our policy is that you have no phone for 7-10 business days" nonsense from Samsung AND the backup and restore process is still way better on iPhones than on any android I've ever owned. How there is no easy and reliable backup/restore mechanism on android after so long is beyond me.
Bottome line: if you have a similar issue, it's very likely a hardware problem (my replacement phone has been fine for 3 days now). And avoid Samsung support if you can!
Click to expand...
Click to collapse
On the second phone I still have the 2wk window to return. I am contemplating if I should just return altogether. I had bought an s21 Ultra as well and that seem to be working OK.
Two s21+ phones with same issue, what are the odds of hardware problem? But what if it is the entire batch that is bad.
isiddiqi said:
On the second phone I still have the 2wk window to return. I am contemplating if I should just return altogether. I had bought an s21 Ultra as well and that seem to be working OK.
Two s21+ phones with same issue, what are the odds of hardware problem? But what if it is the entire batch that is bad.
Click to expand...
Click to collapse
Your issue sounds different to me. Mine definitely fully rebooted, I have no idea what is going on with yours, it sounds like your crashes are locking the phone or something, that could definitely be software. Good luck!