I haven't seen any one discussing this with the T-Mobile Galaxy S3 (SGH-T999) yet, so I'm guessing its just an issue with my phone but I thought I'd ask first..
My phone is a brand new T-Mobile Galaxy S3 (SGH-T999) 16gig Blue, fresh out of box. Not rooted. Running stock rom.
Searching, I've a seen similar issue mentioned for other (older) phones, the fix seemed to be disable auto-rotation and auto-brightness. I've turned both off, and still have the problem.
If I let my T-Mo S3 sit, and the screen has been off for a few minutes (usually two or so will do it), I can't get the screen to turn back on.
The LED will blink, and if I hold the power button long enough, the phone will restart (and the screen will turn on).
I've tried a factory reset via the settings menu, going into stock recovery and doing a wipe cache, as well as a factory reset and wipe cache in the stock recovery. I still have the issue.
Have others experienced this? Is there a fix, or is it time for me to get with T-Mobile about a replacement?
Note: My VZW S3 (SGH-i535) doesn't have this problem).
Replacement
Sent from my SGH-T999 using xda premium
KidJoe said:
I haven't seen any one discussing this with the T-Mobile Galaxy S3 (SGH-T999) yet, so I'm guessing its just an issue with my phone but I thought I'd ask first..
My phone is a brand new T-Mobile Galaxy S3 (SGH-T999) 16gig Blue, fresh out of box. Not rooted. Running stock rom.
Searching, I've a seen similar issue mentioned for other (older) phones, the fix seemed to be disable auto-rotation and auto-brightness. I've turned both off, and still have the problem.
If I let my T-Mo S3 sit, and the screen has been off for a few minutes (usually two or so will do it), I can't get the screen to turn back on.
The LED will blink, and if I hold the power button long enough, the phone will restart (and the screen will turn on).
I've tried a factory reset via the settings menu, going into stock recovery and doing a wipe cache, as well as a factory reset and wipe cache in the stock recovery. I still have the issue.
Have others experienced this? Is there a fix, or is it time for me to get with T-Mobile about a replacement?
Note: My VZW S3 (SGH-i535) doesn't have this problem).
Click to expand...
Click to collapse
Exact same issue here ... Do you have power saving enabled? The only other option I play with is NFC ... although not sure why this would affect it. I have now disabled power saving and NFC to see if problem persists.
I did get a replacement phone. The replacement works fine.
Did a factory reset and haven't had an issue since. Definitely an app causing it ... just not sure which one!
Sent from my MZ601 using xda app-developers app
gellofish said:
Did a factory reset and haven't had an issue since. Definitely an app causing it ... just not sure which one!
Sent from my MZ601 using xda app-developers app
Click to expand...
Click to collapse
I had tried several factory resets. Didn't fix. I even tried re-flashing via Odin.
Mine even "stayed alseep" at the "welcome" screen pre-setup (after factory reset).
newbie with the same problem..
My GTI9300 is doing the same thing. If I leave it idle for a while, then press the power button, the phone is unresponsive. Pressing the home or vol buttons does nothing. if I call it, the phone recieves the call, but no ringtone is played and the screen stays off.
It started doing it since I updated to the official 4.3 rom. Its been happy and dandy on 4.1.2
I have a sneaky suspicion it's a samsung service app causing problems. Once (still on 4.3) the screen wouldn't turn back on after a Skype call. I had to call it to unlock the phone, when it did come back it said "samsung push service stopped working." Today while browsing, the hyperlinks became disabled for a short while until an app update notification showed up. Then it was normal again. It may be unrelated, but could it be the push service interfering with wake from deep sleep?
Could be, kinda hard to say. But if you haven't already you should factory reset. If some data from your previous build is not being read correctly it could cause any number of issues. (You could try clearing data on and disabling the service app first if you like)
Beyond this though, you should probably post in the international forum. Our devices are very different and I for one know very little about yours.
Good luck!
Sent from my SGH-T999 using Tapatalk
replace
factory reset and if thta doesnt work replace it.
Related
Hi,
I got my SGS T999 right after release. It's been running fine up until recently when a number of things started failing progressively right after the Jelly Bean update, and now it's hardbricked. This is a non-rooted phone. No apps installed from sources other than Play Store and Amazon.
Just prior to the Jelly Bean OTA:
1. All the sensors stopped working - gyro, proximity, etc. They all stopped working. They wouldn't come back on a restart either. I was getting ready to try a factory reset when the Jelly Bean OTA came.
2. Updated to Jelly Bean, sensors started working again, but the phone would randomly restart, in my pocket, just sitting there on the table...
3. On Saturday I used the phone a little, just like normal. About 45 minutes after making a call and not using the phone again, I noticed that the phone was dead. I plugged it in thinking something had drained the battery.
4. When trying to power it up, it would vibrate once, sometimes twice but the screen stayed black.
5. I tried taking the battery out for a while, replaced it and turned it on - it started booting up, but before fully initializing, rebooted again and then went black.
6. Once i got a charging screen when i plugged it in, but could never replicate.
7. Became totally hardbricked. Can't get into download mode, can't factory reset, nothing at all. No vibrate, nothing. I fully charged the battery to make sure, and nothing. It's totally dead and unresponsive.
Is there anything I can do besides request a warranty replacement? What could have happened?
Thanks.
With all those issues you were having prior to updating it sounds like a malicious app... which can be installed from the play store there are plenty (porn apps and fart apps, many many more) yes issue for a replacement.
Sent from my SGH-T999 using xda premium
mt3g said:
With all those issues you were having prior to updating it sounds like a malicious app... which can be installed from the play store there are plenty
Click to expand...
Click to collapse
I hadn't installed anything that was sketchy though...
Probably a bad phone.
Sent from my SGH-T999 using xda app-developers app
Meant malicious app or broken sensors. Wither way return it.
Sent from my SGH-T999 using xda premium
mt3g said:
With all those issues you were having prior to updating it sounds like a malicious app... which can be installed from the play store there are plenty (porn apps and fart apps, many many more) yes issue for a replacement.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Gotta love those fart apps..lol
Sent from my Inspire 4G using xda app-developers app
Can you get it in download mode?
Volume down + home + power
If so just Odin the stock rom again.
Powered by the SGSIII
ThC23 said:
Can you get it in download mode?
Volume down + home + power
If so just Odin the stock rom again.
Powered by the SGSIII
Click to expand...
Click to collapse
Nope, no response of any kind to anything at all anymore.
msbmsb said:
Nope, no response of any kind to anything at all anymore.
Click to expand...
Click to collapse
Sounds alot like an hardware failure warranty exchange is the way to go..
Sent from my SGH-T999 using xda premium
I would definitely take it in to get it replaced. Your still under manufacturer warranty if tmobile will put up a fight.
Sent from my SGH-T999 using xda app-developers app
Thanks for the confirmation. I've requested a replacement under warranty, hoping it's a new one and not a refurb.
Thanks!
For informational purposes, here's the conclusion (so far):
On receiving the warranty replacement SG3, I tried turning on the original once more, as a test. To my surprise, after several days of being powered off, it came back up and seemed to be working fine. It ran normally for a day and a half, at which point it then began to reboot, after turning on the GPS for the first time (whether that's actually related or not is unknown, just a note). It would either reboot immediately on the first screen unlock, or it would reboot while booting up.
Fortunately, this did give me an opportunity to factory reset. For anyone suspecting it had something to do with a rogue app, the phone would reboot on the very first initialization screen, where you enter your gmail account info.
So I restored to the warranty phone, which seems to be working fine except for the hands-free speaker which has some constant background static.
I have a perplexing problem with two phones that I have. The issues is, when the phones go to sleep (either by timing out while on battery or when I hit the power button on the phone to turn off the screen), the CDMA radio will shut off after a while and won't turn back on until I perform one of the following:
1. Reboot
2. Make a phone call
3. Send a text message
4. Switch in and out of airplane mode.
I know when it's off because I will suddenly get a flood of text messages when I perform any of the above tasks.
I thought originally this was something wrong with my phone (maybe too much flashing), so I got another Galaxy Nexus (Sprint). Unfortunately, it does the same thing. If I keep it on a charger and do not turn the screen off, everything works fine.
The phones are a Galaxy Nexus that works with Sprint. Since I don't know when it happens, I captured a logcat of the phone overnight after I turned the screen off. The next morning, I had to dial out to "wake" the phone.
I have factory reset the phone, flashed another rom (it seems to happen to anything that was based on CM), All these have happened multiple times trying to fix the issue. I have wiped dalvik and cache with no avail. Is there something I'm not trying?
I tried looking around to see if anyone else had this problem, but came up empty.
Perhaps someone had had this problem as well and can direct me to a fix.
Logcat: http://www.darktremor.info/logs/logcat.txt
Thanks.
Has anyone else had an issue where the lock screen is unresponsive after you turn it back on? Here's the scenario:
1. Using tablet.
2. Let the screen time out normally or press the power button to turn off the screen.
3. Wake the tablet either with power or home buttons.
4. Screen is completely non responsive. Doesn't register any of my touches on the screen. Have to power off and on the screen multiple times before it allows me to unlock the screen. Orientation doesn't seem to matter.
I have a brand new WiFi only edition, model P600. I immediately did the three small OTA updates Samsung pushed to me as soon as I first turned the tablet on, but I'm pretty sure it was happening before, as well.
Anyone else? Haven't seen mention of this issue here so far.
Sent from my SM-P600 using xda app-developers app
SportingChap said:
Has anyone else had an issue where the lock screen is unresponsive after you turn it back on? Here's the scenario:
1. Using tablet.
2. Let the screen time out normally or press the power button to turn off the screen.
3. Wake the tablet either with power or home buttons.
4. Screen is completely non responsive. Doesn't register any of my touches on the screen. Have to power off and on the screen multiple times before it allows me to unlock the screen. Orientation doesn't seem to matter.
I have a brand new WiFi only edition, model P600. I immediately did the three small OTA updates Samsung pushed to me as soon as I first turned the tablet on, but I'm pretty sure it was happening before, as well.
Anyone else? Haven't seen mention of this issue here so far.
Sent from my SM-P600 using xda app-developers app
Click to expand...
Click to collapse
Never had this problem on my Note 10.1
Yours could be a just a software issue - Try doing a factory reset and see if its anyway better if not then go back and get it exchanged.
P.S I have had this issue just recently on my S3 and this was after doing a recent update (which then got cancelled due to it causing lag and errors on peoples S3's) so I just need to find the time to factory reset it and all should be good (in theory)
Geordie Affy said:
Never had this problem on my Note 10.1
Yours could be a just a software issue - Try doing a factory reset and see if its anyway better if not then go back and get it exchanged.
P.S I have had this issue just recently on my S3 and this was after doing a recent update (which then got cancelled due to it causing lag and errors on peoples S3's) so I just need to find the time to factory reset it and all should be good (in theory)
Click to expand...
Click to collapse
Yeah, I was afraid of that. No joy on the factory reset. I'm rooted and so the Knox stuff is tripped and shows "modified." Hope that doesn't come back to bite me. (Btw, issue was apparent from first boot - before I rooted.) I'm about to go find the factory firmware and ODIN it back on here so at least there's no trace of SuperSU and all the bloatware is back. I think my parents got the Note from Amazon, so hopefully they won't look too closely anyway.
Thanks for the reply.
FWIW, I've tried factory reset, flashing firmware straight from Kies (UEUBMK1), turning off Smart Stay, Palm motion, Reading mode, and I'm the only user registered on the device. No joy on anything. Just going to have to send it back to Amazon for replacement.
Have you tried disabling Daynote?
I've found that when I freeze Daynote the magnetic sensor from eg the book cover case don't work anymore.
My train of thought is that maybe your magnet sensor is defective and Daynote ends up in an endless loop?
meks007 said:
Have you tried disabling Daynote?
I've found that when I freeze Daynote the magnetic sensor from eg the book cover case don't work anymore.
My train of thought is that maybe your magnet sensor is defective and Daynote ends up in an endless loop?
Click to expand...
Click to collapse
Have not tried this, but now it's too late as we've boxed it for shipping back to Amazon. Thanks for the response, though!
So I had my Galaxy S3 since it came out. A few months ago I noticed it shut off and wouldn't turn back on. (it would vibrate when the battery was inserted, goto samsung boot screen and never go anywhere from there) I noticed this site and a lot of others having the same problem so I began to trouble shoot.
I cleared my cache by getting into the boot screen and that seemed to fix my problem.
Now about 2-3 months later it started doing the same thing! This time clearing the cache did nothing, heck sometimes I can't even get a chance to clear the cache without it restarting on me again. Sometimes (if I'm lucky) i'll get it to boot up and it will go to home screen without a problem. Little to know it shuts off without warning and I'm stuck at the beginning.
This phone has never been rooted. Please help! I'm using a mytouch 4g now and this thing is slow as molasses! Do I have any chance to recover my s3 or is it sudden death syndrome?
Also I had alot of pictures/videos on the internal hard drive of this phone, is there anyway to retrieve those since my phone can't even boot up?
nexus24 said:
So I had my Galaxy S3 since it came out. A few months ago I noticed it shut off and wouldn't turn back on. (it would vibrate when the battery was inserted, goto samsung boot screen and never go anywhere from there) I noticed this site and a lot of others having the same problem so I began to trouble shoot.
I cleared my cache by getting into the boot screen and that seemed to fix my problem.
Now about 2-3 months later it started doing the same thing! This time clearing the cache did nothing, heck sometimes I can't even get a chance to clear the cache without it restarting on me again. Sometimes (if I'm lucky) i'll get it to boot up and it will go to home screen without a problem. Little to know it shuts off without warning and I'm stuck at the beginning.
This phone has never been rooted. Please help! I'm using a mytouch 4g now and this thing is slow as molasses! Do I have any chance to recover my s3 or is it sudden death syndrome?
Also I had alot of pictures/videos on the internal hard drive of this phone, is there anyway to retrieve those since my phone can't even boot up?
Click to expand...
Click to collapse
I am currently having the same exact issue. I suspect it is a faulty power switch. I will be replacing it, if it works i will update and let you know
had tisesr
mentisimperium said:
I am currently having the same exact issue. I suspect it is a faulty power switch. I will be replacing it, if it works i will update and let you know
Click to expand...
Click to collapse
I've heard of that too, I took apart my s3 and removed the power button as well as blew some compressed air through it. Still didnt work but yes keep me updated!
I ripped my power switch from the motherboard. To turn it on you plug it in and hold home and volume down to go to the odin screen. click volume down to reboot the phone. I am waiting for a new switch to come in the mail which I will attempt to solder onto the board.
My note 4 randomly freezes and goes to black. It also randomly restarts, gets stuck, and then restarts again. It's very annoying, if I want to check something, I hit the home button and the phone is frozen on the lock screen. Random apps are also crashing but instead if just closing the app my phone's screen just shuts off and I can't get into the phone for at least a minute. I don't know what the problem is and I really don't want to factory reset my phone.
I would pull the battery and take out the SD card (if you have one) and sim card and boot it up and see if that helps.
If u r using de-bloatware app then try restoring all the apps.
Factory reset, don't install anything and see if it continues. Then start installing a couple of apps till it happens again, try to identify the offending
App.
Same here.. Just started happening 2 weeks ago.. I have yet to find the offending app. ****ing ATT and their ****ty note 4 ughhhh
Happening to me too. Even after factory reset, and in Safe mode. I think it is from the June 16, update. I plan on taking it in to the att store and having them flash the new update to the phone. Thinking maybe my over the air update got screwed up somehow.
I put mine on ultimate power saving mode at night to keep it from dying since I forgot my charger. When I woke up, I tried to turn off ultimate power saving mode, but the option was gone. I rebooted and it got stuck at the att boot logo. I took it to the att store and they said I'd have to file a claim on insurance and that they can't fix it.
I cane home and connected it to adb to see if I could back up my files. Without sending a command to it, it wiped itself and factory reset. I lost everything, but since then I have had no issues.
Mine started doing this a couple of weeks ago. Factory reset twice, sd card out. Still doing it. Had to go back to note 3. With sd card and sim card out it seems to work ok on WiFi only.. No stuttering or force closes since?
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Mine was doing the same thing. Turns out the battery was taking a crap. New battery and no more issues. For myself at least.
Mine is unusable. It boots into download mode half the time after factory reset. When I get it to boot up it only lasts for 15 minutes then resets again and gets stuck
Sent from my SM-N920I using XDA-Developers mobile app
Black89 said:
Mine is unusable. It boots into download mode half the time after factory reset. When I get it to boot up it only lasts for 15 minutes then resets again and gets stuck
Sent from my SM-N920I using XDA-Developers mobile app
Click to expand...
Click to collapse
Try what I did accidently. Connect to your pc. Boot into recovery lode and see if you can connect with adb. Then connect to with adb sideload and let it sit there. Maybe send a few commands and see if it will do like mine. It might get it to unhang. You might lose everything if it restores, but it might do like mine.
insanoshaman said:
Mine was doing the same thing. Turns out the battery was taking a crap. New battery and no more issues. For myself at least.
Click to expand...
Click to collapse
Mine mostly ok, albeit chained to at&t FIRMWARE, but I do get an odd eeror: when in a call the phone will make a a keypad tone,as though I'm leaning on the keypad [not], often mid-Bluetooth handsfree calls. It last 2-4 seconds, long enough to interrupt the flow of a call. anyone ?
I have had tons of apps update as of late. I too am experiencing lag, lock ups, black screen. I thought I was alone.
Had a friend's Note 4 do the same only he was on Sprints network. He was not rooted and on MM. I tried a factory reset and it helped for an hour or two then it went back to random rebooting or apps freezing. I tried flashing factory software through ODIN. It was good for an hour then went back to random reboots and apps freezing. I tried another ODIN flash without restoring any of his apps and the same thing happened. I tried changing the battery and that wasn't it, I removed the SD card and that wasn't it either.
He had to take it to Sprint and they ended up just giving him an S7.
Sent from my SM-G925P using XDA-Developers mobile app
I started having this problem just after the update. I tried to switch the battery out and tried to take SD card out. I factory reset it about 3 times now. Nothing has solved it.
I took it into AT&T, and even though I'm not under warranty anymore (had phone for almost 2 years now), they worked with me and ended up giving me a new s7.
I suggest you go talk to AT&T because this is a problem with all AT&T Note 4's. Tell them you want it fixed and talk to the managers and get them to contact the corporate help desk. Don't leave without them fixing it. You paid $900 for this phone.
Gave you a new S7? Or swapped it out on a next contract?
dave30534 said:
Gave you a new S7? Or swapped it out on a next contract?
Click to expand...
Click to collapse
I did not pay a dime. But you have to show them that it freezes and crashes even after they factory reset it
Just left an [email protected] store. He looked at me like I had 3 heads. He had never heard of such. Will call corporate and work my way down.
I did hold a S7 edge.... it was a thing of beauty and speed. No ir though... it's why I like note 4
Works without sim
I've had the exact same issues, (Galaxy Note 4 on AT&T). Tried factory reset, wiping cache, re-flashing with odin, removing SD card, removing apps, multiple batteries, etc.... the only thing that has worked so far is removing the SIM card. It runs flawless without it. Currently using my S3 for calls and text and use the note 4 like a giant iPod touch on wifi only. Hoping this is a software issue AT&T will correct but knowing them..... best bet is probably to wait until August and get the new Note 7.
Why not try the MM update that is out right now, it´s not an OTA but by just renaiming the file to update.zip, putting it in your ds card and applying it through recovery you will have a practically new phone, it´s worth the try.
I´m ruuning it and it´s been great so far, no bugs, no errors.