Hi everyone,
i don't know if someone already encountered this but sometimes my GS3 does not respond when i try to wake him up. (it's not turned off just standby). The screen stays black en nothing works. One time the screen did woke up but i couldn't unlock it because the touchscreen didnt work. It could not be turned off and the buttons didn't do anything! The only way for me to get out of this was a battery pull!
I did not root or modify anything on this phone because i like the stock samsung TW for the first time .
Did anyone else have this problem? And how did u solve this? Thank u.
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
dnlgee said:
Possibly due to an app you have installed.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thank u i didn't thought of that. Is their an easy way to find out wich app this could cause? I still find it very weird. If an app is not compatible than it just shouldnt install intead of breakin the phone right? XD
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
if you are not sure about the root cause of the problem better factory reset your mobile
bala_gamer said:
if you are not sure about the root cause of the problem better factory reset your mobile
Click to expand...
Click to collapse
Yes, if it happens again than i will try that. But i already sent the unit back from were i ordered it. They will send me a new one because its their policy to send a new one if something happens in 2 weeks.
So i will see if it still occurs with the new one otherwise its one of my apps. Than i will install only a few apps and see what causes it. If it doesnt occur one more thime than the unit was faulty. Ill keep u guys updated.
chicoelnino said:
This happened me last night as well. Couldn't do anything other than turn the phone off, and when it came back on it was fine again.
Unrooted as well. Would like to find out how I can prevent this from happening again?
Click to expand...
Click to collapse
Did it happen once? My phone had it like 3 times so thats why i sent it back. But if it still occurs with my new phone than it must be one of the apps i got Luckily they got DOA policy. I asked if it includes ''the phone does not work as it should" and they said yes send it back u will get a new one yaay but now i have no phone
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
sama said:
I had this. After a hard reset, multiple times, and configuring with no accounts (no samsaung account, no google, nothing), it still happened. I ended up returning the phone and I've not had a single problem since.
I think it was either faulty memory or a dodgy firmware flash (more likely). Either way, I didn't care to find out and now it's all good.
Click to expand...
Click to collapse
Yes lucky i found this out early too.. Because after another week i wouldnt get a new one and now i get
Factory reset your phone.
Hope everything turns out alright.
Related
Just trying to build some statistics as to how common this turning off problem is.
--------------------
PLEASE READ THIS BEFORE ANSWERING:
1) Obviously this is regarding the phone turning off on its own when its not due an empty battery.
2) Only answer with "no" if you've been using the phone for at least a week. If you've been using it for less and it hasnt turned off, answer with "No - but had it for less than a week".
--------------------
I just want to know before I send my phone to Amazon for replacement.
I've had it 8 days, so I clicked the 2nd "no". If I saw any hardware fault in a new device I'd immediately get onto the supplier for a replacement. Unless there's software at fault here (unlikely, but obviously possible) then I can't see the problem simply going away.
Hope you get it sorted mate.
Nope. Had the phone since may 6.
Sent from my GT-P1000 using XDA Premium App
Thx for the replies guys.
Keep the answers coming
No. Never unless the battrey is empty.
Sent from my GT-I9100 using XDA App
Touchwood, never and I've had the phone a few weeks now.
Had this problem last year with my new Desire, but returned it to HTC and they replaced the mobo without any problems.
Yep had it nearly 4 weeks and its went twice. Not in the last week or so though.
Sent from my GT-I9100 using XDA App
Everyone runs different apps and settings on their phones. Unless there's a specific hardware problem there's going be tons of variables to consider for those having reboot issues. I've had mine for six weeks and its never done anything wonky.
I returned my 1st one as it turned off a few times a day. Replacement has been fine.
Sent from my GT-I9100 using XDA App
Does reboot count as a yes?
I clicked yes but I am not 100% sure if this happened to me or not. Allow me to explain...
I was carrying it in my hand walking and I happened to look at the screen and it was showing the Samsung GT-i9100 splash screen seemingly for no apparent reason. When it went away it just went right back to where it was (no media card reading or anything).
It was strange to say the least but I have not seen it happen again since then and that was about a week ago and I have had the device for approx. 3 weeks now.
Does this sound like the same issue?
BarryH_GEG said:
Everyone runs different apps and settings on their phones. Unless there's a specific hardware problem there's going be tons of variables to consider for those having reboot issues. I've had mine for six weeks and its never done anything wonky.
Click to expand...
Click to collapse
Lightfunkyone said:
Does reboot count as a yes?
Click to expand...
Click to collapse
Oh sorry i forgot to mention this. No, reboots don't count as they're probably a software problem which can be fixed maybe with a new ROM or update or wtvr (i'm probably going to install another ROM eventually). And i'm not sure how a replacement will help with that, since I already have the KE7 firmware installed.
Just complete turn offs, cuz it might be a hardware problem, which can be solved by a replacement.
Thanks for the responses guys. Keep it up
Hmm, well i'm not really sure of anything, but that looks like a reboot to me. It might be that it turned off and you accidentally held the power button and turned it on, but since there was no card reading or anything, i think it's the "fast reboot" problem i've seen some people with on the forums. I hope it doesn't happen again
Hey guys.
I've noticed that occasionally Vlingo/Voice control pops up after a single-click of the home button. This happens a couple of times a day.
I was wondering if this could be a hardware or software error. My guess is that it has to be a software error because it happens so rarely and the button itself has quite the travel (I just don't feel it being pressed twice).
My question is has this problem happened to anyone else before? It's kind of driving me crazy.
I'm on stock rooted (with insecure kernel) BOKE3 (Android 2.3.3).
Thank you!
I think it's hardware related. I noticed it in CWM Recovery. Sometimes when i pushed Home once, phone acted like I was pushing it twice.
I have my GS2 for 2 months. It happened to me only twice.
Thanks for the reply. I don't have CWM recovery installed and the couple of times I've been in the stock one I haven't noticed anything. I guess time will tell if it's a hardware or software bug when ICS is finally (officially) released for SGS2.
Happen to me in cwm a couple times too...
Now i use POWER button...just to be sure i dont mess up the Sg2
can somebody fix this problem? it is annoying when I want my phone back to homescreen but the vlingo comes out...
I have the same problem, and it's definetly a hardware issue. My home button have gotten progressively worse, it have now reached a point where it now double clicks several times a day.
Sent from my GT-I9100 using xda premium
You know, I remembered that it all started when I had the "bright" idea to format the /cache from the stock recovery. I just formatted it to see if it will fix itself. Already the stock launcher's animations are back (I never realized they were gone), hopefully this fixed the problem, otherwise off it goes to Samsung for service.
This happens to me all the time and it drives me crazy... I hate that goddamned thing... `what would you like to do` how about shut the hell up.
I suppose if you root it can be uninstalled
i think i have the solution , will post a video on youtube in few hours.
I had same issue with LPB ICS, then i flashed again, wipe data, cache etc, even deleted battery log/stats, and now everything is perfect..
This is not HW issue afaik..
Same for me. It's especially annoying if you're sitting in a course and the media sound isn't muted.
For me it seems to be a hardware problem, too. Because after I had replaced my S2 it just happend once in 2 month. Before it happend several times a day.
LG WortPixel
I have the same problem too. I used CWM. I think this is software things.
toi1em said:
I have the same problem too. I used CWM. I think this is software things.
Click to expand...
Click to collapse
How many times have you encountered it and have you disabled/use Rom without home button double click?
Sent from my GT-I9100 using xda premium
Factory reset did not do the trick, I still occationally get the damn Vlingo. Maybe I should try installing another factory firmware.
I'm really tempted to just send it in for service.
andreasS2 said:
Factory reset did not do the trick, I still occationally get the damn Vlingo. Maybe I should try installing another factory firmware.
I'm really tempted to just send it in for service.
Click to expand...
Click to collapse
It won't help, I'm confident it's a hardware problem. The best you can do is to flash a rom without the double click feature.
Sent from my GT-I9100 using xda premium
Do you know if the stock ICS (leaked) roms come with Vlingo or a double-click feature in general?
brar.arsh said:
I had same issue with LPB ICS, then i flashed again, wipe data, cache etc, even deleted battery log/stats, and now everything is perfect..
This is not HW issue afaik..
Click to expand...
Click to collapse
It happens on every Rom I've used.
Sent from my GT-I9100 using xda premium
Can't we just make a warranty claim? Or are they just going to come back with "could not reproduce problem" since it only occurs 2-3 times a day?
Edit: I've contacted Samsung and they've told me to update to the latest firmware. Lol.
andreasS2 said:
Do you know if the stock ICS (leaked) roms come with Vlingo or a double-click feature in general?
Click to expand...
Click to collapse
Yup they do, and I had the same problem on the latest ICS leak. It also double clicked in CM7, but it's harder to notice there as it dont have Vlingo.
I guess you can make a warranty claim. I dont know your countries rules regarding this, but in Norway they must fix stuff like this even though the warranty dont apply/is expired.
Sent from my GT-I9100 using xda premium
The phone's warranty runs until the end of September 2013.
I just installed another original rom and it already popped up Vlingo once, I'm going to test it some more and report back.
Edit: Same problem, it's definitely hardware related.
Okay people, I just got my S3 last night, and after about 3hrs of use, my problems developed. My problem is intermittent, but nonetheless, very aggrivating. When I press the power or home button, screen wakes, but touch is unresponsive. I thought it might have been a lockscreen issue, but I've tried all variants including no lockscreen and have the same problem. Is there any updates or fixes that anyone knows of or do I have a defective phone? Any thoughts are welcomed. For what its worth, I also rooted my device, and it installed supersu. I don't know if that could be related, but I'm going to give a full unroot reset a try as well.
Sent from my aokp_tenderloin using xda premium
Are you connected to charger, that can cause pro lems when getting unstable current
Sent from my GT-I9300 using xda app-developers app
On or off the charger, makes no difference. I Fully factory restored, pulled root, triangle counter reset, and everything else in between, and the issue still remains. Even tried another rom and kernel, sames results. Seems like I have a fancy light up paperweight for the most part. First samsung phone in over 10 years, and this is what I end up with. Great job samsung.
For how long is there no response.anyway try disable s-voice in settings.that is directly related to home button.power button hmm, don't know..
So, factory reset the phone, reflashed stock rom, even booted phone up with no sim or memory card, fresh from a reset. On the main setup screen, if I lock the phone, then wake it up, touch is dead. Definitely a hardware problem. Called samsung uk because anyone who used DAILYSTEALS.COM will find out if their phone ever needs service, that the phones sold via them came from the UK. Not really happy this wasn't explained on their website prior to purchase, as I would have held off. Now my 3 day old phone with not even 24hrs of use on it is off to a UK service center.
Word to the wise when buying online, check the origin of your phone if the retailer isn't an official seller. now my money saved is going right back.
zodiaxe66 said:
For how long is there no response.anyway try disable s-voice in settings.that is directly related to home button.power button hmm, don't know..
Click to expand...
Click to collapse
As stupid as it may be, I want s-voice to work, shouldn't have to disable something to make the phone work properly out the box.
LG-P760 stock Android 4.1.2
Only basic apps, FB, gmail etc.
1. Factory/hard reset
2. Works around 3-4 days perfectly, then starts to crash.
By crash I mean black screen, nothing helps, only battery pull.
3. After first crash, starts crashing more frequently. Happens only in standby.
Worst was today: If I start phone, log in, then it wont crash before I put it in standby. First time in standby, within 30 second, it had crashed.
twice crashed when someone tried to call me. Vibrated once, then crashed.
I would like to avoid replacing my phone.
Any ideas how to find the source of this problem? Any recommendations?
lamui said:
LG-P760 stock Android 4.1.2
Only basic apps, FB, gmail etc.
1. Factory/hard reset
2. Works around 3-4 days perfectly, then starts to crash.
By crash I mean black screen, nothing helps, only battery pull.
3. After first crash, starts crashing more frequently. Happens only in standby.
Worst was today: If I start phone, log in, then it wont crash before I put it in standby. First time in standby, within 30 second, it had crashed.
twice crashed when someone tried to call me. Vibrated once, then crashed.
I would like to avoid replacing my phone.
Any ideas how to find the source of this problem? Any recommendations?
Click to expand...
Click to collapse
I had the same problem with Vietnam Rom and it was the baseband. I changed to the baseband from ICS from a Rom of my country so I have Vietnam Rom+Original ICS baseband and everything works well.
Thanks.
Although, I understand it mostly is problem when you have unlocked bootloader.
I am running stock everything.
And they have problem with rebooting phone, mine crashes and freezes.
Weird is that it starts around third day of normal use.
I think I have to take on a quest with a warranty. Does anyone know, can I contact LG straight without the provider, where I bought the phone?
lamui said:
Thanks.
Although, I understand it mostly is problem when you have unlocked bootloader.
I am running stock everything.
And they have problem with rebooting phone, mine crashes and freezes.
Weird is that it starts around third day of normal use.
I think I have to take on a quest with a warranty. Does anyone know, can I contact LG straight without the provider, where I bought the phone?
Click to expand...
Click to collapse
You can.
lamui said:
Thanks.
Although, I understand it mostly is problem when you have unlocked bootloader.
I am running stock everything.
And they have problem with rebooting phone, mine crashes and freezes.
Weird is that it starts around third day of normal use.
I think I have to take on a quest with a warranty. Does anyone know, can I contact LG straight without the provider, where I bought the phone?
Click to expand...
Click to collapse
I haven't unlocked it. The problem was the same: SOD sleep of death, when the screen goes off you can't do anything but pull the battery.
But if you can use the warranty use it. You should find the warranty info in the box to know where send it in your city.
Sent from my LG-P768 using xda app-developers app
Thanks. I will search into it. Sleep of death is new expression for me.
I only have phone, it came from relatives who threw away receipt + box.
Luckily I managed to get new receipt from provider yesterday (I dont think they usually give out receipts twice), so now I can use local warranty.
Thanks everyone for replying. I will post update when I have final solution.
Since you are stock you might want to consider flashing the kdz to see if that helps. Good luck!
Sent from my LG-P769(20d) using the xda-developers app. If I helped you please hit the "thank you" button.
I'm having the exact same issue with mine. I've heard everything from "try a different SD card" to "factory reset," and nothing seems to permanently fix the issue. What I've found kind of sort of works is just reboot it a whole bunch until it finally comes up and doesn't do it any more. From there, I'm good to go until the battery runs out or I need to reboot it because all the bloatware is causing it to glitch. This usually means that I have to reboot my device 10+ times in a row every few days. Hopefully, you found a more viable fix than this.
neo1piv014 said:
I'm having the exact same issue with mine. I've heard everything from "try a different SD card" to "factory reset," and nothing seems to permanently fix the issue. What I've found kind of sort of works is just reboot it a whole bunch until it finally comes up and doesn't do it any more. From there, I'm good to go until the battery runs out or I need to reboot it because all the bloatware is causing it to glitch. This usually means that I have to reboot my device 10+ times in a row every few days. Hopefully, you found a more viable fix than this.
Click to expand...
Click to collapse
Hi
I managed to kind of solve this issue. Because I am not sure how, I haven't closed thread yet.
Anyway, I warranted device, they re-installed soft. Came back, same thing. After around weeks use, SOD. Factory reset. After that, things went interesting.
I tried not to leave it idle. Always had something running. I also had noticed by the time it never occurred when it was plugged in or music was playing.
One day it did it again, but I was in a hurry and just disregarded it. I did something(I was busy, maybe just plugged it in automatically?) and it came back up. It took like 10 sec for screen to start, but it did just wake up. And it haven't had crash ever since. I have no idea is this solution or is this just some coincidence and I am not keen to factory reset again, to see will it reoccur. It's my only phone
TLDR: Managed to get out of sleep of death, haven't reoccurred since.
My stock, never-rooted GT-I9300 (4.1.2, I9300BWELK1, JZO54K.I9300XXEMC2) is plagued by boot loop problems. It first started about 3 months ago, where the blue charge LED would suddenly come on and the phone would not wake from sleep. I pulled the battery, then when it was turned on it showed the initial S III logo, then the O2 logo followed by the glowing Samsung logo. Then repeated from the O2 logo endlessly. I pulled the battery again, then the next morning restarted it without the SIM or SD card in, and it had done a partial factory reset - i.e. lots of phone contacts were there with the texts, but all the settings had reverted to default. Later that day while on charge the same thing happened again, and I sent it away to O2 for repair.
When it returned, the same thing happened 6 weeks later although this time it was on when it froze and went straight to the O2/blue LED stage. Another repair (I'm fairly sure these 'repairs' were just factory resets...), and 6 weeks later exactly the same. Back to the O2 shop for another repair.
This time they replaced the 'main board' and when it came back it had a different Wi-Fi MAC address. This time only 6 days elapsed before the same fault arose again, and finally I was eligible for a replacement handset. This lasted 2 days before a boot loop condition occurred again! This time, being sure it couldn't be a hardware fault I tried my own /data and /cache wipe, which worked. I skipped all but the must-have apps, and I thought this was going to be stable but once more this past weekend the boot loop happened again (I've got my restoration procedure down to about 15 minutes thanks to the practice!)
I don't know what could be causing this and I'm fed up with resetting my phone. Are all S IIIs this unstable? I've never had a phone that required a factory reset within 18 months! When it is in the boot loop, I can access recovery and download modes, but safe-mode start-up has no effect.
The last remaining candidates I can think of are a problem with my SIM card, or a defect with my SD card... or an app. Can anyone suggest the best way to troubleshoot this? I'd really really rather not have to skip importing my settings as I have among other things many SSIDs I don't easily have access to re-create.
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
kernalk said:
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
Click to expand...
Click to collapse
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Skander1998 said:
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Click to expand...
Click to collapse
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
kernalk said:
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Everything to carries is "news".
I can't help with logs and whatnot, so I'll leave that to someone else.
You can always flash and downgrade to the older firmware that didn't give you a problem, if the problem persists, it is indeed an app.
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
That doesn't fill me with confidence!
Thanks again for the replies. I'm not wild about downgrading. I liked the improvements! Is it possible to downgrade in a carrier supported way? Retaining warranty compliant has been rather useful in the past few months!
Sent from my GT-I9300 using xda app-developers app
You can flash any official via odin.
Sent from my GT-I9300 using Tapatalk 4
Well late Friday night it did it again. Not sure when exactly as I was asleep. Woke up in the middle of the night and went to check the time, Looked at my phone to find the blue LED on when it should have been red for charging or green for fully charged, and it was very hot - wouldn't turn on either. Pulled the battery but it kust went into the loop. I was away from home so I couldn't do any troubleshooting and had no choice but to wipe.
This time I didn't restore settings and the only apps I installed were SMS Backup & Restore and Puzzle Alarm (I know this isn't the culprit as I only started using it this week!). Gone are all my precious wifi SSIDs but otherwise I'm not sure I've noticed the difference.
So I'm now not connected to my work wifi, nor have I set up my work email or Lync - two of the things I use my phone for must after Facebook which I've also not reinstalled. Facebook mobile web is really hard to use by comparison.
By chance I popped into the O2 shop later that day and had the fortune to bump into a Samsung rep who had never heard of this and agreed that I was unfortunate to have these problems (how touching!) and suggested I speak directly to Samsung support rather than O2 which I will do this week. I will also contact O2 about a replacement SIM and look into replacing the SD too.
This is really silly. I'm not keen on downgrading the software because the first thing either Samsung or O2 will do is upgrade it again. Frankly at this point I'm fed up with the whole thing but I've got a year left on the contract and even a pretty much new handset like mine won't fetch enough.