Related
I'm coming to the Evo 4G LTE (stock, not yet rooted) from the OG Evo (rooted, various ROMs, yada yada). I've held off on rooting, just in case I discovered a hardware issue (light leakage, etc.) and needed to swap out the device. So far I've discovered a definite problem, but I don't know whether it's a hardware or software issue, and I'm hoping someone in this forum can help me down the path of figuring out the cause(s).
Specifically, I'm seeing the following things happen, usually all at the same time, but intermittently:
1. Phone heats up, and battery takes a huge hit
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
3. Wi-Fi drops, as does my mobile data connection, so that I appear to lose all connectivity.
4. My app associations get reset. I usually have my URLs set to open with "Dolphin Browser HD", and mail set to open with "Gmail (Compose)", but after this happens they're back to the stock browser and mail app.
5. Can't enter any text. When I enter a text field/control, the keyboard appears (I use Swype, but switching input methods makes no difference), and I can type/Swype away, but no text ever shows up in the field.
This is happening about once a twice a day, on average, and is obviously driving me nuts. I haven't detected a pattern to when/why it happens. And I've been searching the forums, but I haven't seen anyone else reporting this same set of issues. I'm not sure whether it's my device (hardware/lemon), or maybe just a user app behaving very, very badly - I'm not enough of an Android dev to know where to look for clues...?
Any help very much appreciated. I haven't tried a factory reset, but I'm open to that. Also to rooting the phone, and/or contacting Sprint. I just didn't want to blindly do any of those things before asking the Android experts out there for some guidance.
Thanks!!
If it was me, I'd root and flash a new ROM or at least a rooted stock ROM. If that didn't work I'd unroot and exchange it.
I'd say try a factory reset first, but why not root and have it done as a by-product anyway?
Sent from my EVO using xda premium
I agree
If you dont want to root yet just do a factory reset. What is it going to hurt? If you do a factory reset try to just set the phone up with all stock options to see if your problem is fixed.
roachiepoopoo said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
jpbme said:
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
Click to expand...
Click to collapse
The same is with me BEFORE rooting, and after root and ota from xda
Look I want to thank you for posting this. I am NOT CRAZY. This has happenend to me from day 1, I returned the first EVO LTE (for other reasons) and it is still happening on my second EVO LTE
I finally got to the point that I was going to root my EVO LTE to fix this issue. I was going to root and flash and reset EVERYTHING. well surprise surprise nothing changed.
I have all the same problems you described but I lose my 3G about 15 times a day (especially when on calls) I have full bars but the 3G icon is gone and it states that I am disconnected. I can't figure this out. Everyone I appreciate your quick responses to this mans question but none of them work.
I have update profile and prl more times then I can remember. Flashed, wiped , reset everything. Help Me!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any new info on this topic? My 3G disconnecting is really annoying!!
Rooted, wiped, and switched to MeanROM - phone now works GREAT!
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
roachiepoopoo said:
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
Click to expand...
Click to collapse
NO!
So I flashed the Chameleon Rom, was running it for a while and still had issues. This weekend (during a wedding) I flashed MeanRom. And it is still happening. Does anyone know a real fix for this? :crying:
SilverZero said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
stompkins007 said:
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
Click to expand...
Click to collapse
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
slowfncar said:
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The issue I was having was only specific to the blank notifications... everything else has been pretty solid... BUT, there appears to be a light at the end of the tunnel. Last night I saw ClearnROM DE 1.4 was released, and had to give it a try. This time around I was very careful to do a full factory reset, Wipe of everything except storage cards via TWRP, Ran Superwipe script, and installed the latest CleanROM DE 1.4. The one thing I did differently after install was be very careful of what items I restored via Titanium Backup (making double certain it was only restoring app store apps, and no potential artifacts from previous ROMs.
Since doing this the phone has been solid. Haven't experienced the blank notifications, and the phone seems considerably more responsive than it was (which is nice, because it even seemed fast before doing this). Anyway, if anyone else is experiencing this, I recommend they do the same.
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
I don't buy Sprint's insurance and have had issues getting them to do warranty replacements, most recently with my EVO 3D's phantom screen touch problem (also 1st gen hardware). Sprint told me to ship it back to HTC and be without a phone for however long the warranty repair took. Really?
KatanaMan said:
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
Click to expand...
Click to collapse
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
KatanaMan said:
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
Click to expand...
Click to collapse
RE: SuperSU, it lives on the system partition with the ROM so it's protected from a factory reset since that only clears the data and cache partitions (where your user apps are stored).
Sent from my EVO LTE
Just a thought
You cold try ##786# and enter your MSL code for data connection issues. See here to use CDMA Workshop for those that are not rooted (or use MSL Reader from the market for rooted users). Its worth a try at least, before unrooted users decide to root. Keep in mind this will reset your phone to factory so if your going to reset, might as well do this to reset PLI, PRL and other params...
I've been having the overheating/battery drain issue since about a week after first getting the phone. I've tried Meanrom, Viper Rom, and Clean Rom and still come across the same issue with each one. I do complete wipes/factory resets when flashing the new roms and I'm on the latest firmware. When the phone overheats it's pretty much unresponsive. Today, I watched my battery drain from 15% down to 8% in about 10 minutes. I turned the screen off at 8% and went to turn it back on a few minutes later and found that the battery had completely drained by that time. I have no idea why this is happening.
Same here
I've been having this issue as well. It happened while I was stock, it happened after I rooted, unlocked, went S-Off. And it's still happening under MeanROM. Very frustrating!
Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?
Hello,
First off I want to explain what happened exactly. Since April I am using an HTC One, but I gave my S3 to my girlfriend. I gave it to her exactly like I used it: running CM10.1 nightly's, no other mods, no custom kernels, etc. I updated her S3 once every few weeks with a new nightly. It performed normally, like it has been doing for many months.
Since a few weeks, the S3 started to show problems. The camera app would act weird sometimes, but it wasn't anything big. Then the freezes came. Once every few days, the phone would freeze and she needed to reboot. In the past week, the freezes happened many times daily. No matter what you did with the phone, it would freeze very fast. It just got worst and worst, until yesterday the phone wouldn't even turn on anymore. It would stay in the bootup screen.
The problem was, I had only downloaded a CM10.2 nightly update recently, had no Android 4.3 Gapps yet and hadn't succeeded in making a proper Titanium Backup (due to the phone being so unstable, it would freeze at 80% of the backup). Moving to CM10.2 without a wipe wasn't the best idea, but having no TB, I didn't want to wipe data. In the end, desperate measure called for desperate actions. I flashed a nightly build of CM10.2 I had downloaded already on the phone, but still the same. It wouldn't get past bootup animation.
To keep this story as short as I can, I ended up flashing the latest Samsung Touchwiz build (4.1 based) via Odin, but even that wouldn't get past the bootup animation. So I managed to get in some sort of recovery, where a wipe data option was available. Did that, phone started working normally again. Only problem is, this wipe data option apparently was a different kind of beast. I am used to the "wipe data" option that deletes your apps + data, etc, but doesn't touch your photo's, music, etc. This one did.
Is there any known way to recover some of the files that got deleted?
And if anybody is in the mood, any explication on what exactly happened to this S3? I mean, nothing changed, it was working normally for months with CM10.1...
Kind regards
I've never found anyone that recovered any data from the internal sd card, there are pc programs that claim to be able to do this for sd cards and hard disks but doubt they will work on MTP device.
Freezing is common for a minority of phones due to nand block failures, or it could be due to the rom you were using.
boomboomer said:
I've never found anyone that recovered any data from the internal sd card, there are pc programs that claim to be able to do this for sd cards and hard disks but doubt they will work on MTP device.
Freezing is common for a minority of phones due to nand block failures, or it could be due to the rom you were using.
Click to expand...
Click to collapse
Thank you for the quick reply. I suspected this but I though it's worth asking.
I guess my S3 was one of this minority, can't imagine CM10.1 to be the bad guy here. Ah well, at least now she can use the damn thing again. RIP photo's and other important data though. It's near impossible now for Samsung to get me to buy another product from them again in the future.
Unless you have a government grade software/hardware that's being used on digital forensics then it's really quite impossible to recover the files.
For future, look at FolderSync on play. It will sync sdcard data to the cloud or to a computer that is always on.
I set my sdcards syncing over wifi whilst I am asleep. I never lose anything.
[Q] Please Help Me: Rooted Phone & Weirdness After Factory Reset & Failed ROM Flash
So I rooted my SGS4 a few months after getting it from VZW. I was fine with it simply being rooted for over a year and finally decided there was a few things I no longer wanted to live with. I started going down the path of flashing a ROM and after what I felt was enough research settled on the one that would work with my phone. Or so I thought. Short story is it did not and I found out later it wasn't compatible. Prior to flashing said ROM I created a backup and did a factory reset and wipe like a good little boy. Well, I think this is what caused the issues I'm now experiencing. I'll start with the few I can think or right off-hand as being the man annoyances but I reserve the right to add more later as they come up.
So, w/o further adieu, here's the issues I'm having, numbered for our convenience.
1) Whenever I boot up my phone I get the 'Android is Upgrading' after every single reboot with about 62 items 'upgrading' so it takes a while. I use my phone a lot and carry spare batteries that I change out every time it gets low so this can be several times a day and many times the wait of several minutes is quite inconvenient. As I found in a search, I tried using an app called 'Lucky AppManager' to clear the ODEX files and it reboots and I do it again a few times and it still doesn't seem to do any good.
2) for some reason all of my contacts has a little SIM card next to them that I don't recall seeing and it now won't let me edit any of them to add or remove information. This is annoying.
3) This one had been going on for a bit prior to me attempting to flash a ROM so I had hoped at minimum it would be resolved after the reset. Nope. Power down times are very slow. It used to be whenever I powered it down it took only a dozen or so seconds. Even less right when I got it. Then, one day, it took a minute or two to completely power down and has taken that long every since. Annoying.
There was something else but as I type this I'm drawing a blank. Any help that anyone can help me on any of the above would greatly help me.
Thanks!
p.s. This is a duplicate thread since I was so rudely made aware that I had posted to the wrong subforum. Sometimes this forum earns is rep. Sorry to those who genuinely care because a few bad apples ruin it for everyone.
OstrichSak said:
So I rooted my SGS4 a few months after getting it from VZW. I was fine with it simply being rooted for over a year and finally decided there was a few things I no longer wanted to live with. I started going down the path of flashing a ROM and after what I felt was enough research settled on the one that would work with my phone. Or so I thought. Short story is it did not and I found out later it wasn't compatible. Prior to flashing said ROM I created a backup and did a factory reset and wipe like a good little boy. Well, I think this is what caused the issues I'm now experiencing. I'll start with the few I can think or right off-hand as being the man annoyances but I reserve the right to add more later as they come up.
So, w/o further adieu, here's the issues I'm having, numbered for our convenience.
1) Whenever I boot up my phone I get the 'Android is Upgrading' after every single reboot with about 62 items 'upgrading' so it takes a while. I use my phone a lot and carry spare batteries that I change out every time it gets low so this can be several times a day and many times the wait of several minutes is quite inconvenient. As I found in a search, I tried using an app called 'Lucky AppManager' to clear the ODEX files and it reboots and I do it again a few times and it still doesn't seem to do any good.
2) for some reason all of my contacts has a little SIM card next to them that I don't recall seeing and it now won't let me edit any of them to add or remove information. This is annoying.
3) This one had been going on for a bit prior to me attempting to flash a ROM so I had hoped at minimum it would be resolved after the reset. Nope. Power down times are very slow. It used to be whenever I powered it down it took only a dozen or so seconds. Even less right when I got it. Then, one day, it took a minute or two to completely power down and has taken that long every since. Annoying.
There was something else but as I type this I'm drawing a blank. Any help that anyone can help me on any of the above would greatly help me.
Thanks!
p.s. This is a duplicate thread since I was so rudely made aware that I had posted to the wrong subforum. Sometimes this forum earns is rep. Sorry to those who genuinely care because a few bad apples ruin it for everyone.
Click to expand...
Click to collapse
If you're on nk1 or ng6, have you tried going back to nc5 via odin? It sounds like you need to flash the full wipe nc5 and start over from scratch.
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!