I got my S3 last year, a week or two past the release. I had rooted and flashed a stock debloated ROM, though I couldn't say which as it's been so long. Worked fine for a little bit, but then overnight, it stopped producing sound, and it wasn't just that it got ticked to silent mode. I changed volumes, tried keypad noises, nothing. Also, upon receiving or making a call, it would send out, and crash the phone, causing a reboot. I pulled the battery, and noticed a faint bit of moisture inside the device, but my water damage indicator was not ticked.
I had given up on it until recently, now that I'm a tad bit more knowledgeable about these sorts of things, and I used Odin to flash back to bone stock with no problems. Sadly, the problems I have with sound and calling are still present.
I assume this is a hardware issue due to the moisture I had found present in the device, but I'd like to know how I could further troubleshoot this to know for sure.
Any suggestions would be grand, thanks.
WTFsandwich said:
I got my S3 last year, a week or two past the release. I had rooted and flashed a stock debloated ROM, though I couldn't say which as it's been so long. Worked fine for a little bit, but then overnight, it stopped producing sound, and it wasn't just that it got ticked to silent mode. I changed volumes, tried keypad noises, nothing. Also, upon receiving or making a call, it would send out, and crash the phone, causing a reboot. I pulled the battery, and noticed a faint bit of moisture inside the device, but my water damage indicator was not ticked.
I had given up on it until recently, now that I'm a tad bit more knowledgeable about these sorts of things, and I used Odin to flash back to bone stock with no problems. Sadly, the problems I have with sound and calling are still present.
I assume this is a hardware issue due to the moisture I had found present in the device, but I'd like to know how I could further troubleshoot this to know for sure.
Any suggestions would be grand, thanks.
Click to expand...
Click to collapse
If flashing back to stock/factory reset didn't fix it, chances are that it's from the moisture. You can clean it off with some can air and put it in a bag of rice for a day or two to see if it will help.
Related
Hey guys,
My mom's GSM S2 has been randomly rebooting, and she insists that its when she 'bumps' the phone in her pocket while walking around listening to music.
I suggested it may be a problem with the music player, but after fiddling with it, I noticed it sometimes rebooted without music playing either.
She said she felt like a change anyway, and asked me to root her phone, and I suggested installing an ICS ROM as well.
I rooted the phone and loaded Resurrection Remix for her, but the problem persists.
She says she has never seen the phone reboot 'on its own' (i.e. sitting on the table untouched). Its usually after taking it out of her bag, or while its in her pocket.. etc
I thought it may be a rogue app, but the problem seems too related to physical movement, which made me suspect the battery. I have checked it, and it seems to be seated pretty securely to me, but who knows..
Any thoughts?
Sometimes a faulty or old battery can cause such issues by not maintaining a constant flow of energy at the correct voltage (usually too low).
Try replacing the battery and see if the problems persist. If they do then perform an RUU to get everything 100% stock and then send it to Samsung for repair (assuming its under warrenty still?)
Edit: sorry I did somewhat forget what you said about it being related to movement. If that is definitely the case it could be a loose connection inside the phone. In which case a new battery would be unlikely to help and you would probably be better just sending it to Samsung for repair.
Sent from my Nexus One using Tapatalk 2 Beta-4
Just did a quick test.. tried forcing a reboot by bumping and shaking the phone.. no luck. Maybe the problem isn't as related to movement as I thought.
Perhaps you're on to something with the faulty battery hypothesis, will try test with a different battery!
edit: just managed to cause the phone to reboot by removing the back cover
My GSM Galaxy Nexus has been experiencing random shut-downs, especially when it is in my pocket. I haven't noticed any problem with overheating and I tried rooting it and installing the latest version of ICS 4.0.4 directly from Google's source.
I also have Lightflow installed, but I doubt that it causes shut-downs, since I've only heard of reboot problems.
I suspect it could be a problem with the battery because, whenever this happens, the charge level goes down by at least 5% or more.
So, does anybody know how to remedy this? Or will I have to exchange the phone?
This has happened to me a couple times. I never know how long it's been off. I'll take it out of my pocket, and it's just totally off. I hold the power button and it starts up. Very frustrating bug though... as rare as it may be.
I'm still stock, unrooted 4.0.2 using the extended battery on VZW. Holding out for the first update, then we'll see...
Just so you know next time that happens grab a log and post it. Also, if you battery is down, try wiping stats, that usually brings it back.
obsanity said:
Just so you know next time that happens grab a log and post it. Also, if you battery is down, try wiping stats, that usually brings it back.
Click to expand...
Click to collapse
Sorry for being such an ignorant and a noob but by log you mean a crash log right? Which is the best way to obtain them?
This happens to me about once a day. I'll come back to the phone and it will just be off. I aslo have root and lightflow installed. What's the best log to get?
It was the battery for me...
This was happening to me too, almost every time I took my phone out of my pocket, it was turned off.
After a couple weeks of troubleshooting and googling, I figured out what it was. It was the phone getting "twisted" in my pocket from sitting and standing. If you twist your phone like your're trying to wring water out of it (not too hard), the battery loosens just enough to cause the phone to lose power. I fixed this by taping a thin piece of foam to the inside of the battery cover to keep the battery in place. Makes the back of phone feel firmer too.
Hello !
I'm experiencing the same kind of power off.
Very often it's in my pocket, but sometimes not.
I've leave the debug mode on for the day, so last time it happens to me i've save a "abd bugreport" to a file.
Is there any clue that can be found in this file to know why the phone shutdown ?
Regards,
Antoine
EDIT : I have YAKJU 4.1 stock ROM, no root, no unlock.
I noticed a while ago before seeing the videos that if I banged my GN against the table a certain way against its bottom left corner that it would shut down. I solved that like the poster above by putting an extra something in between the battery and the cover (paper). That solved lots of the problems I had with my phone shutting down when I put it down on hard surfaces. There is though, I believe, a second software caused issue for some of the shutdowns. I still pick it up once every couple days to find that it's off. I've banged it, tapped it, twisted it, and I can't get it to shut down physically like that anymore.
I'd like to know more about how to pull the logs and find out what's going on.
I've had my Nexus for three days now, and I've had several shutdowns. Two of them were during a phone call, and the other two were during a workout using micoach app. The twisting/pocket option doesn't apply to me, because during the calls I was holding it in my hand, and during the workout it was strapped to my arm. I also have lightflow, and will uninstall to see if there is any difference. Running totally stock unrooted 4.1.1. This is making the phone totally unreliable, and I will return it if I can't get this fixed soon.
Every would have had that problem due to how poorly Samsung constructed the battery slot for the battery to fit it. What I did to fix that problem was take out the battery. Even from time to time rage quit and rip the battery out while the phone was on. And put it in, and push it a bit up toward the camera. That fixed my battery issues. Others have put a foam thing (sorry I don't know the name) where the battery slot golden things were so the battery wouldn't move. You can also try that.
Galaxy Nexus-codenameandroid rom
I uninstalled Lightflow after posting my previous message, and since then have not had any random shutdowns. All calls are performed flawlessly, and I've used micoach several times again (this was when the problem was most obvious) without any problem. I haven't changed anything else, so I'm pointing my finger at Lightflow. I'm installing it again to make sure it was the cause, will report back.
Regarding the battery problem, I've been looking at it and can't see how it can become loose. It is really tight, and there is no spare room to add any kind foam. Maybe thye have tweaked the design on later batches? My GN was built March 2012.
I had the same issue and it was caused by an app. The app "Boid", a twitter client still in beta, was causing the reboots. The reboots occurred once or twice a week, they happened on 100% stock ICS, 100% stock JB, custom roms also.
Like the above poster, I uninstalled LightFlow and am no longer having any issues. I'll try and get in touch with the developer and see if there are any logs I can get to help.
Sent from my Galaxy Nexus using Tapatalk 2
Hi guys, recently I've been having quite an issue with my Wildfire S. It worked fine, rooted S-ON with CM7.2RC from alquez, until one day.
It all started two weeks ago when I was on one open air party where a thunderstorm overwhelmed me and left me completely wet. I've been terrified of that day before cause WFS is my first smartphone and I've been wondering how would it react on water. Maybe there is no causality between this, idk.
But since then, everytime somebody called me, the display shut off and after the call has ended, I couldn't awake my phone by normal means - the on/off button didn't work, so I started using quite dumb solution - a hard reset with taking off battery and putting it on.
(then I figured out that it could be awaken by plugging it to USB)
quite stange issue, isn't it?
I did a factory reset and flashed the CM again on clean. The frequency of a dead display has lowered down to every two calls appr. but it was still happening. Today, finally, I took off and on the battery again and that somehow did a factory reset... that's it, I have to solve it.
I'm quite worried it has something to do with HW (after becoming wet). However, if I'm not calling, it WORKS FINE!
Anybody can say anything about this?
Crusheer said:
Hi guys, recently I've been having quite an issue with my Wildfire S. It worked fine, rooted S-ON with CM7.2RC from alquez, until one day.
It all started two weeks ago when I was on one open air party where a thunderstorm overwhelmed me and left me completely wet. I've been terrified of that day before cause WFS is my first smartphone and I've been wondering how would it react on water. Maybe there is no causality between this, idk.
But since then, everytime somebody called me, the display shut off and after the call has ended, I couldn't awake my phone by normal means - the on/off button didn't work, so I started using quite dumb solution - a hard reset with taking off battery and putting it on.
(then I figured out that it could be awaken by plugging it to USB)
quite stange issue, isn't it?
I did a factory reset and flashed the CM again on clean. The frequency of a dead display has lowered down to every two calls appr. but it was still happening. Today, finally, I took off and on the battery again and that somehow did a factory reset... that's it, I have to solve it.
I'm quite worried it has something to do with HW (after becoming wet). However, if I'm not calling, it WORKS FINE!
Anybody can say anything about this?
Click to expand...
Click to collapse
It sounds like the proximity sensor got wet. Normally, i'd tell you to take the case and battery out and leave it all in a bucket of uncooked rice for a day to pull out the moisture. But beings that this has been awhile, idk if it will help
BigChillin said:
It sounds like the proximity sensor got wet. Normally, i'd tell you to take the case and battery out and leave it all in a bucket of uncooked rice for a day to pull out the moisture. But beings that this has been awhile, idk if it will help
Click to expand...
Click to collapse
I was thinking about something like that too (since I have very little expertise at smartphones). Could I disable it for calls somehow? (what would it do to normal use?)
As far as I know there is no actual setting to disable it. If you were a code ninja (or knew one) i'm sure they could. And it would just mean that you would have to manually turn it off to talk on the phone. But, we're not sure that's the problem. So, I personally would try the rice and hope for the best.
BigChillin said:
As far as I know there is no actual setting to disable it. If you were a code ninja (or knew one) i'm sure they could. And it would just mean that you would have to manually turn it off to talk on the phone. But, we're not sure that's the problem. So, I personally would try the rice and hope for the best.
Click to expand...
Click to collapse
Thanks for your help mate. You told me about the proximity sensor - which I googled and this popped out - http://forum.xda-developers.com/showthread.php?t=951858
"Screen does turn off when holding to face on a call, but fails to come back on, requiring taking out the battery"
I may have found a solution. Thanks again!
I hope so. If not, just come back and light this topic up again
Well, it seems my enthusiasm was premature as the app doesn't work on WFS. I tried a factory reset & flash once again, called from my gfs phone to mine and it happened again:
Even though I didn't put the phone to my ear, the display went black and after the call has ended, it hasn't awaken.
I'll try the rice, but damn, I don't understand it at all.
Crusheer said:
Well, it seems my enthusiasm was premature as the app doesn't work on WFS. I tried a factory reset & flash once again, called from my gfs phone to mine and it happened again:
Even though I didn't put the phone to my ear, the display went black and after the call has ended, it hasn't awaken.
I'll try the rice, but damn, I don't understand it at all.
Click to expand...
Click to collapse
I don't get it either. The only thing besides it being dead that i can think of is that there's still moisture in the lens or something causing the sensor to trip (or not in this case).
I may have found another solution, but I don't understand it at all. http://forum.gsmhosting.com/vbb/f634/solved-wildfire-s-proximity-sensor-problem-1413248/#post8066168 Could you translate it to normal language, if you think it could be the fix?
That actually seems good. It basically says to get JTAG manager, and rewrite the broken nand files with the working ones at the bottom of the post. It IS a pretty advanced operation though, and it seems you would have a pretty good chance to brick your phone if you don't follow it to the letter.
I guess CM has an option to turn proximity off. Try that maybe?
Try a different rom.
Sent from my HTC_A510c using XDA App
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
a_p3rson said:
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
Click to expand...
Click to collapse
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
lorddavid said:
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
Click to expand...
Click to collapse
Superoneclick? That's the closest I found, and it doesn't say that it supports the Glide. And, I am running a fully stock version of 4.0.4, unrooted and everything. I might need a little more help here, haha.
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
lorddavid said:
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
Click to expand...
Click to collapse
Isn't that a different version though? The build number on that is UCLG9, not UCKJ3 (which is what I have right now).
I am not sure, but, if with that your problem persist, maybe is hardware, but I only do that. When I did it, that was the latest version, now there is another version but not sure what is it
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
davidpartay said:
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
Click to expand...
Click to collapse
I really was hoping it was a OS issue, as it hadn't ever done this on GB. If I flash a new rom then, it would be fixed?
Also, I too noticed that my phone is abnormally warm when it does this. I do have a cover on my phone, but I noticed that it seems to be centered about on the horizontal center of the phone, about a half-inch below the camera. If this is related, what do you think it is?
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Exxon02 said:
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Click to expand...
Click to collapse
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
a_p3rson said:
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
Click to expand...
Click to collapse
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Exxon02 said:
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Click to expand...
Click to collapse
Your issue sounds similar, but slightly different. Mine only happens while I am charging it, and it has only done it since a while after I made the upgrade to 4.0.4. Although, they sound similar, and my phone also gets concerningly warm, so I have no idea if it is the same thing or not...
If it's out of warranty, then you have nothing to lose by doing a backup and a clean ROM installation, which is what I would do. I guess if you do it when fully charged and while the phone is cold you should be fairly safe, especially if you use a small ROM. I've found the latest M3 10.1 ROM installs fairly quickly, so that might be worth a shot even just to see if it fixes the problem.
The only risk you're taking is that the phone might die and get bricked in the process if it's a hardware fault, so I guess it's really your call.
EDIT: On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
davidpartay said:
On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
Click to expand...
Click to collapse
I like that idea, as it should fix the overheating issue. However, the times that it actually has this malady aren't regular - it seems to happen more at night, but not every night. I could try putting it in the freezer when it does it though, and see if it works. If it is overheating, could it be a hardware issue then? I also noticed that my battery that I have in my phone does appear to have a slight dent near the bottom, and it is only happening when it is charging, so I am wondering if it could be a problem with the battery? When I pull the battery out after it has done this, the battery itself isn't that warm, but the phone is, so I'm thinking it isn't the battery, but does anyone else have any ideas?
Hopefully someone here can help. I've tried researching the problem and I can't seem to find any answers.
I recently damaged the LCD on my Note II. The replacement assembly arrived today and I just finished the repair. All seemed well. The phone booted up properly and everything seemed to work fine. About 20 seconds after boot the loudspeaker started making an extremely loud buzzing noise. This lasted for about 5-10 seconds and then would continue to come and go, each time lasting for approximately the same amount of time. After a bit of troubleshooting I noticed this would also occur anytime I tried playing anything at all from the loudspeaker though was not limited to this alone as it continues to come and go seemingly at random. Music, notifications and the like will not play.
Prior to the damage the phone was in 100% working condition. I am also 100% sure that the repair was done correctly. Taking this into account I have no idea whatsoever what the issue could be.
Other than this, everything else on the device seems to work fine. I should also note (no pun intended) that I am fairly certain no other components where damaged along with the LCD.