I had been using a popular eh09 rom for write some time when suddenly my touch screen stopped responding current. it would stop recognizing input after a random amount of time.
The only way it would work again is by turning off the screen and turning it back on again.
At first I thought it was an issue with the rom I was on so I flashed a different one. The new rom worked fine... For about 3 minutes. I've wiped data to see if starting fresh would help. Same issue.
Help?
Sent from my SCH-I500 using XDA App
Post this kind of stuff in the Q & A forum.
Once there, make sure you include information like rom, kernel, modem, what you did to flash, etc.
the entity said:
I've wiped data to see if starting fresh would help.
Click to expand...
Click to collapse
This may be a silly question but did you do all three wipes?
Factory, cache, and dalvik?
I know when i first went to CM7 a while ago it would do that, i found doing all three wipes fixed it for me.
+1 on FDro's comment. That said, though, you may just have some conductive gunk on your screen, especially if it's persistent across roms and kernels. For example, any dried sweat on there that regains moisture (ambient humidity, rain, more sweat) will instantly become a the equivalent of a hand on your screen; the system will continually register that conductive spot/blob as input until you wipe it off or reset the screen. It may indeed be a bug that requires further troubleshooting, but see if CAREFULLY cleaning off the screen with a lens cloth and some distilled water helps. Do it with the battery out just to be safe though, because the distilled water will become slightly conductive as it pulls material into solution. Use it sparingly, avoid the earpiece, and wait a few minutes to replace the battery and you should be fine.
Edit: I recommend against any solvents like hexane or isopropyl alcohol at the moment since I don't know whether the Gorilla Glass has any sort of coating that they could break down.
Sent from my SCH-I500 using xda premium
Duplicate post
the entity said:
I had been using a popular eh09 rom for write some time when suddenly my touch screen stopped responding current. it would stop recognizing input after a random amount of time.
The only way it would work again is by turning off the screen and turning it back on again.
At first I thought it was an issue with the rom I was on so I flashed a different one. The new rom worked fine... For about 3 minutes. I've wiped data to see if starting fresh would help. Same issue.
Help?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Uh oh. I had the same problem when I moved from eclair to froyo. Screen would freeze and only by locking and unlocking it would it work. The only solution I had was to have Samsung repair my screen. It was done for free, but I was without a phone for a week.
Sent from my SCH-I500 using xda premium
Just to give more detail, I was on Powerwashed 2, did all wipes.
Flashed via Heimdall.
Worked fine for a month.
Suddenly started happening after I installed Seal. I thought that may have taken up too much ram and that android had closed down the touchscreen driver as it managed memory. Uninstall didn't fix the issue. Ruled out the app.
Next I tried changing roms. Went from PW to TSM. Flashed via recovery. Wiped. etc. Worked for about 3 mins, locked up again. Ruled out the rom.
Flashed TKSGB kernal. Issue persisted. Ruled out the kernal.
Now I've just flashed back to ED05 stock. Seems to be working ok.
I'm slowly reinstalling each app to see if it may have been a certain app causing it.
And @ johntinman it may be possible that my phone has the same issue. I'm running off a refurb.
How's the humidity in your neck of the woods? Do you encounter any steep gradients, say, at work or around the house? Example: time spent in air-conditioned areas with movement into "normal" air (ie. Outside). This really sounds hardware-related, but too random to indicate "damage," per se, as opposed to some kind of interference. Was there ANYTHING common to these incidents? Maybe something environmental?
Sent from my SCH-I500 using xda premium
Jazz848 said:
How's the humidity in your neck of the woods? Do you encounter any steep gradients, say, at work or around the house? Example: time spent in air-conditioned areas with movement into "normal" air (ie. Outside). This really sounds hardware-related, but too random to indicate "damage," per se, as opposed to some kind of interference. Was there ANYTHING common to these incidents? Maybe something environmental?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I live in Arizona. No humidity whatsoever.
Interesting... I've never been to AZ (and I need to check whether it's even relevant here), but consistently dry air has me wondering about static.
Also, is the air dusty at all? Have you hit it with some canned air?
Sent from my SCH-I500 using xda premium
Not very dusty here... I'm more concerned with flour from the pizza shop i work at than dust.
Overall, as a quick update the issue is resolved. I repartitioned, flashed back to stock, then followed up with my current rom. All is well.
Related
Hi all.
This has been on for several months now.
After ending calls, or mostly calls being ended, at random times, the streak would seem to be unresponsive and would be very sluggish. I would have to wait for a few minutes or to turn it off and on again for it to start functioning properly once again.
This happens with both streakdroid 1.8.1 and 1.9.0
Could it be an issue with my baseband?21
I have the same problem. I looked everywhere but I didn't find an answer. It happens to me regardless of witch version im using. Currently im using 1.9.0. I would really appreciate some help with this.
Had the same issue despite which rom I was using. Did a screen recalibration from the recovery screen and no problems since. Select it from the stock recoveey screen. One down from "apply update pkg" I think. You don't even have to touch the screen, it does it all itself. Has never been so responsive.
Sent from my Dell Streak using XDA Premium App
brunswick000 said:
Had the same issue despite which rom I was using. Did a screen recalibration from the recovery screen and no problems since. Select it from the stock recoveey screen. One down from "apply update pkg" I think. You don't even have to touch the screen, it does it all itself. Has never been so responsive.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
Thank you so much for sharing. I have re-calibrated my screen and shall report here if the screen becomes unresponsive , and the streak becomes sluggish once a phone conversation is ended. (It happens at random, so may take up some time)
brunswick000 said:
Had the same issue despite which rom I was using. Did a screen recalibration from the recovery screen and no problems since. Select it from the stock recoveey screen. One down from "apply update pkg" I think. You don't even have to touch the screen, it does it all itself. Has never been so responsive.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
I did the calibration but it didn't help:-( .
same here...so slow after calls end
I hope someone has a solution for this because its my biggest issue.
Pretty strange for sure. I dont know what rom you guys are using, but I neglected to mention that I had just finished flashing the 351 official firmware and then performed a factory reset, and then the recalibration. Not telling you to reset, just sharing my experience. Hate having to reset! It completely solved my issues though. Not a screen freeze since.
Sent from my Dell Streak using XDA Premium App
brunswick000 said:
Pretty strange for sure. I dont know what rom you guys are using, but I neglected to mention that I had just finished flashing the 351 official firmware and then performed a factory reset, and then the recalibration. Not telling you to reset, just sharing my experience. Hate having to reset! It completely solved my issues though. Not a screen freeze since.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
how is the 351 version? I'm currently using 1.9.0 and I'm thinking of going back to official but i cant find and decent step by step instructions. Any idea? My phone is a European one.
slekkas said:
I did the calibration but it didn't help:-( .
Click to expand...
Click to collapse
Did not work for me too
It becomes rather sluggish after some calls, where it happens at random.
About factory resets,
What i do before flashing a new rom is to do a factory reset, then enter CWM, and do a factory reset once again, clear the partition cache, dalvik cache , and finally, install the rom. This issue still persist.
arvin2212 said:
Did not work for me too
It becomes rather sluggish after some calls, where it happens at random.
About factory resets,
What i do before flashing a new rom is to do a factory reset, then enter CWM, and do a factory reset once again, clear the partition cache, dalvik cache , and finally, install the rom. This issue still persist.
Click to expand...
Click to collapse
I'm stumped then. Its rather weird that I had the same issues and fixed them so easily. I wish I had somerhing more to offer, but I'm just learning this stuff myself. Hopefully someone with more knowledge will chime in with a suggestion.
As far as the official 351 build is concerned, I'm happy with it. I'm waoting for the gingerstreak rom to get the kinks worked out and then I'm upgrading. To be honest I really liked 1.9.0 and didn't have any issues with it. But, 351 is working fine for me and I'm just not in the mood for another factory reset, reinstall everything morning right now. So it comes down to lazziness more than anything, and I'm not afraid to admit it
Sent from my Dell Streak using XDA Premium App
I had the same issue to with 1.9.0 all I can say that has been fixed on 1.9.1. Don't think Steve is going to release that version though. Just wait for a stable gingerstreak.;-)
Sent from the Almighty Streak!
screen recalibrate
Mine seems to get sluggish after a few weeks of use, then almost down right unresponsive after a phone call, and while on the phone call I do something else with the screen. After a screen calibration, all is well until a few weeks later, then it will do it again.
I'm just wondering...even though the streak has "Gorilla glass", I have a Zagg screen protector on it. Any chance either bare or covered glass is getting some sort of static discharge freaking out the screen?
p51d007 said:
Mine seems to get sluggish after a few weeks of use, then almost down right unresponsive after a phone call, and while on the phone call I do something else with the screen. After a screen calibration, all is well until a few weeks later, then it will do it again.
I'm just wondering...even though the streak has "Gorilla glass", I have a Zagg screen protector on it. Any chance either bare or covered glass is getting some sort of static discharge freaking out the screen?
Click to expand...
Click to collapse
I read an article about capacitive screens and faulty grounding. Basically stated that if there was a ground problem with the screen it wouldn't register touch appropriately. However, the symptoms were more along the lines of touch registering at an alternate place from where you are touching. Doesn't seem to be the case here. Hopefully a definitive solution can be found.
Sent from my Dell Streak using XDA Premium App
Just to share what I experienced. Don't install performance mod. It fixs the problem for me.
RaymondX said:
Just to share what I experienced. Don't install performance mod. It fixs the problem for me.
Click to expand...
Click to collapse
This may very well be the reason as i have perfmod installed.
brunswick000 said:
I read an article about capacitive screens and faulty grounding. Basically stated that if there was a ground problem with the screen it wouldn't register touch appropriately. However, the symptoms were more along the lines of touch registering at an alternate place from where you are touching. Doesn't seem to be the case here. Hopefully a definitive solution can be found.
Sent from my Dell Streak using XDA Premium App
Click to expand...
Click to collapse
If it is a grounding problem, I wonder if there is a common mode problem associated with a difference of potential, between the glass & the casing? The back is metal, and the case front is plastic. I use to use a defender case, but switched to a belt case that is a soft fabric material. I've heard pulling it in and out of your pants pocket could cause an issue, wonder if the case I'm using might be doing it. LOL...if you are old enough to remember curb feelers, maybe I need one of these on my pants to make sure I'm grounded
I had this problem of random freezes and sluggish from the beginning. yes full factory reset n whatnot, ts been always there. from the first couple official builds, over 1.9.0 and even now with the 254 build from dell. I think its connected to the phone module tho, I sometimes have the problem that the complete streak is unresponsive on incoming phone calls. I can see the "pick up" slider, but I cant use it for a couple of seconds, and then its a pain in the *** for a lil bit after the phone call.
-> suspects the phone implementation
I am using 354 rom n its good too....
Sent from my Dell Streak using XDA Premium App
I am running the CM7 with the newest OTB kernal, and I am still getting the keyboard randomly popping up, the back key randomly will work 2 or 3 times in a row. I had the same problem on EF 3.6, com rom and even on the SC roms. Has anyone else had these random key strokes? I heard it was a froyo related issue? Is it hardware related? I had a screen protector that covered the soft keys and removed it, but it is still happening. Any thoughts on how to get rid of it?
FWIW I have odined back to stock, with the atlas pit and even used the ext4 reformatter before I switched to EF3.6.
Any help, advice or thoughts would be great.
I encounter the same issue but it always seems to happen when on the edge of losing cell signal. When going back n forth quickly from service to no service the capacitive buttons (I believe that's what they are called) seem to push themselves. And I have noticed this issue since DJ05 on any rom I have flashed since then and any kernal. I have run just about every rom posted except for miui and cm7. I can not confirm if cm7 has this issue because it is on my other fascinate and not on the cell network. I have terrible signal in the building at work and I have always seen this happen there, at least once a day.
You know am pretty sure I replied to this question before. I guess no one else has really has this issue and the thread died.
Also didn't matter which radio verison I used. I have come to terms that my fassy is just possessed lol
Sent from my SCH-I500 using XDA App
apparently you and I are the only ones that it happens to. I was hoping someone could give me some insight on how to at least find some relevance to a rogue program, bad kernal/rom combo or something. It's very strange and it does it to me more than once a day, and I have good signal most of the time.
Happens to me all the time when I'm at home where I have terrible signal.
I just started having this happen on CM7. The keyboard or the menu would randomly pop up. For me it happened more than just when I had bad signal, but it did seem to happen more often when I had poor signal.
I have this problem too, it would back out of apps I am in too. Quite annoying.
I've been having this problem as well on CommRom 2.1. Seems to be related to poor signal for me. It's pretty annoying to deal with.
Happens on a stock device also
chasmanian said:
Happens on a stock device also
Click to expand...
Click to collapse
Um. No. Not in my experience. Its something that has been well known that is associated with weak/intermittent signal. Didn't start for me until Comm Rom and became more pronounced with CM7…
This happens to me too. Oddly though it only seems to happen during the night when it's plugged in and it doesn't happen all the time. Sometimes I will wake up in the mornings and my screen is on and the keyboard is up.
Do a search for phantom softkey presses. It's pretty common and is a hardware issue.
I as well have this happen. Mostly it happens in low signal area. Recent, my keys just stop working, until I got better signal, or sometimes I am forced to restart the phone.
I just went back to stock ED05 mainly because of this ultra annoying issue and I am completely devastated to find out that it's still #$*%ing happening.
I am so pissed too because I called VZ a week ago and they offered me the Charge replacement, but I couldn't make it to the corporate store until yesterday where I was informed they stopped the replacement policy that day and that I was SOL. Argh. So angry.
420fan said:
I am running the CM7 with the newest OTB kernal, and I am still getting the keyboard randomly popping up, the back key randomly will work 2 or 3 times in a row. I had the same problem on EF 3.6, com rom and even on the SC roms. Has anyone else had these random key strokes? I heard it was a froyo related issue? Is it hardware related? I had a screen protector that covered the soft keys and removed it, but it is still happening. Any thoughts on how to get rid of it?
FWIW I have odined back to stock, with the atlas pit and even used the ext4 reformatter before I switched to EF3.6.
Any help, advice or thoughts would be great.
Click to expand...
Click to collapse
I commented on this a while ago in the CM7 thread. I have it on stock ed04.
What I wanted to know was if you guys have a screen protector on yours or not.
I wondered if my Zagg Invisible Shield was what was "pressing" the capacitive buttons.
Sent from my SCH-I500 using XDA App
lane32x said:
I commented on this a while ago in the CM7 thread. I have it on stock ed04.
What I wanted to know was if you guys have a screen protector on yours or not.
I wondered if my Zagg Invisible Shield was what was "pressing" the capacitive buttons.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You have a shield on gorilla glass???
Sent from my SCH-I500 using XDA App
tyler1234567 said:
You have a shield on gorilla glass???
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Verizon makes a metric **** ton selling screen protectors to those spending $200+ on a smartphone that doesn't need it.
jamesnmandy said:
Um. No. Not in my experience. Its something that has been well known that is associated with weak/intermittent signal. Didn't start for me until Comm Rom and became more pronounced with CM7…
Click to expand...
Click to collapse
Well, just to back this guy up. I had it happen back before and during the time I rooted my phone, and it still happen after I returned to stock (via Factory reset and OTA updates).
EDIT: To the guy who asked about the screen protector, I did have a ZAGG on there, then took off only the section covering the softkeys. Still did it even after I made sure to fully clean it to eliminate any residue. Took the protector fully off, same full cleaning, and it seemed to have gotten worse (if thats possible lol).
I'm about to call tech support, but wonder if it's worth it now that the good trade-in is over.
ElStormChaser said:
Well, just to back this guy up. I had it happen back before and during the time I rooted my phone, and it still happen after I returned to stock (via Factory reset and OTA updates).
EDIT: To the guy who asked about the screen protector, I did have a ZAGG on there, then took off only the section covering the softkeys. Still did it even after I made sure to fully clean it to eliminate any residue. Took the protector fully off, same full cleaning, and it seemed to have gotten worse (if thats possible lol).
I'm about to call tech support, but wonder if it's worth it now that the good trade-in is over.
Click to expand...
Click to collapse
yeah im sure it happens but its fairly rare on a stock phone i would say....
I have it happen semi-regularly. I'm currently on MIUI 1.7.22 / Glich 11.1 / ED05 radio, and never used a screen protector. I also had it happen back before when I was on Super Clean 2.9.2 (don't recall the radio), as well as most any other ROM I've been on.
It's not too uncommon that I would hit the power button to turn off the screen when back on SC2.9.2 and instead it would take a screen shot, because it assumed the back button was being held down!
Gotta love the Fascinate...
jpricesd said:
This happens to me too. Oddly though it only seems to happen during the night when it's plugged in and it doesn't happen all the time. Sometimes I will wake up in the mornings and my screen is on and the keyboard is up.
Click to expand...
Click to collapse
Yup, I got the same issues! Although minor, these things just shouldn't be happening? There's gotta be a fix for this?!?!?!
My wife dropped her phone.....in the toilet.
I tried turning it on today, and it sits at a screen that has a picture of the phone pointing at a laptop. I tried running the Windows Phone Support Tool, and I get this:
Update device 055ec22b - 332fe4fd - a812e651 - 640069c7 Complete with error code: 801812C0, error message: The update failed because your phone started improperly (in the main OS instead of the SLDR, or system loader).
Is there any way to get the phone reloaded with the default OS, or is her phone toast?
The best way to fix it....... Drop it again in the toilet and buy new phone
Sent from my Xperia Arc using XDA App
maybe try a factory reset by using volume up+camera+ power button to boot..if not you can always try flashing one of the stock firmware available in these forums..assuming your hardware isn't toast these things will work
Sent from my SGH-i917 using XDA Windows Phone 7 App
wilcoholic5 said:
maybe try a factory reset by using volume up+camera+ power button to boot..if not you can always try flashing one of the stock firmware available in these forums..assuming your hardware isn't toast these things will work
Sent from my SGH-i917 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Tried a factory reset, as well as trying to flash the stock firmware on the phone. However, I end up at the same spot with the picture of the phone tethered to the laptop. I have a feeling it's a lost cause at this point. Thanks for the advice.
/ignore background noise
Quick questions:
1. Was the phone on when it was dropped?
2. Was the battery removed immediately?
3. How was it dried and for how long?
It could be worse - mine just took a magical trip through the washing machine in my pants pocket. :/ Anyone know of a good parts supplier that stocks the mainboard? That's the one component I can't find for sale, but I want to make sure I CAN get it before I take apart my other Samsung Focus to troubleshoot the broken part(s).
from my experince with a samsung jet,
I dropped it also in water too, i tried t oturn it after few days, strange things happned too me!!! so decided to get a new phone.
I didn't through my jet, and after few months, I charged the phone, and test it found it working without problems
I believe was just a matter of when al lthe electronics inside the phone gets really dry
try it out
I heard pulling out the battery, and putting everything buried underneath dry rice helps. Probably for a couple of days, then see what happens.
Dieabolical said:
I heard pulling out the battery, and putting everything buried underneath dry rice helps. Probably for a couple of days, then see what happens.
Click to expand...
Click to collapse
This is a proven method.
Sent from my LG-P500 using Tapatalk
My Focus is VERY sensitive to any dampness at all. If it gets damp in my pocket (sweating, lawn sprinkler, etc.), it will ding constantly with the sound when you connect the USB cable to it. I have to take a hair dryer to the micro-USB port.
A method I heard, but have never tried, is to wrap the phone in a full sized thick bath towel and bind it closed (duct tape, bungee, whatever) and then put it in the clothes dryer on low heat for an hour.
Thanks for all the info. I will be trying it again tomorrow once I get my USB cable back. I know the cable for my Inspire will work on it as well but I forgot that at work today. Thanks again all.
lekhwani said:
This is a proven method.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
no its not... Its a myth. The liquid evaporates unless you took it all apart and the rice actually touched the liquid and absorbed it. Taking the battery out and leaving the door off and placing the unit in front of a fan will do 1000 times more for the process than rice... Moving air is the perfect evaporator. Plus rice dust gunks up ports... Sorry to burst the experts bubble around here but facts are facts...
First, haha. Yes, vibrator. I didn't know what else to call it. Vibrating unit?
Anywho, it is still "vibrating," but it's so faint that I can't feel it; I can only hear it. I've checked my vibration intensity setting (max) and *#0*#'d it and clicked vibrate, and it does the same thing. It has persisted from EG22 back to EC05. It almost feels like the motor is going but the weight that causes it to vibrate isn't spinning.
I have not flashed back to stock yet, but that will be the next (last) thing I try.
Any ideas? Also, is the vibration unit part of the speakerphone? It doesn't look *too* hard to get to.
Jared
jsheahawk said:
First, haha. Yes, vibrator. I didn't know what else to call it. Vibrating unit?
Anywho, it is still "vibrating," but it's so faint that I can't feel it; I can only hear it. I've checked my vibration intensity setting (max) and *#0*#'d it and clicked vibrate, and it does the same thing. It has persisted from EG22 back to EC05. It almost feels like the motor is going but the weight that causes it to vibrate isn't spinning.
I have not flashed back to stock yet, but that will be the next (last) thing I try.
Any ideas? Also, is the vibration unit part of the speakerphone? It doesn't look *too* hard to get to.
Jared
Click to expand...
Click to collapse
Hmmm, are you sure it's not force closes? Which it's probably not but they tend to do that. And have you ever completely wiped data when going between EC05 and EG22 because it could also be a hardware issue. But I've not seen or heard of this issue. When did it start happening? Like the first time you've experienced it not recently. Have you dropped your phone?
Yes, the vibrator module is in the speaker assembly. Taking apart this is incredibly easy. All you'll need is a Phillips and a thin, sturdy piece of thin plastic (ideally a prying tool) for the back frame (probably the hardest part, the frame's really in tight).
However, if you pay for TEP, just take it in, its a quick fix.
Sent from my SPH-D710 using xda premium
@samaurai: The issue started on EG22, and I did a full wipe and went to EC05. Didn't fix it. Haven't dropped the phone. Force close? Like, single buzz followed by three buzzes? No, it vibrates at the right time, but the vibration is not right. I don't remember anything remarkable about when it started. EG22 was being a ***** and FC'ing, so I was getting ready to go back to EC05, and I noticed it then. Figured it was rom related, but it persisted after the full wipe.
@squishy: I'm not sure if I have TEP (you think I'd know), but I'll look into it. Have a good source for Epic parts if I don't?
jsheahawk said:
@samaurai: The issue started on EG22, and I did a full wipe and went to EC05. Didn't fix it. Haven't dropped the phone. Force close? Like, single buzz followed by three buzzes? No, it vibrates at the right time, but the vibration is not right. I don't remember anything remarkable about when it started. EG22 was being a ***** and FC'ing, so I was getting ready to go back to EC05, and I noticed it then. Figured it was rom related, but it persisted after the full wipe.
@squishy: I'm not sure if I have TEP (you think I'd know), but I'll look into it. Have a good source for Epic parts if I don't?
Click to expand...
Click to collapse
Hmm...I'd be willing to ship you a harvested part. PM me
Sent from my SPH-D710 using xda premium
Are you saying my phone isn't vibrating right because of my battery??? That doesn't make much sense...
I'm having a similar problem except the vibration has ceased altogether. I did recently flash back to SRF 1.2 , but don't think it coincides.
I don't have TEP but I'm still within my year and I have a 2 yr squaretrade warranty. Should I just contact Sammy and see what they say?
I just want to be sure this isn't a software/driver issue. I did try the diagnostics OP mentioned and no dice.
Sent from my SPH-D700 using Tapatalk
Sounds like you have a busted bearing or brushing in the motor that spins the vibration unit (most work by spinning a little assymmetrically weighted rod). The decreased vibration is caused by the motor still spinning, but slower than normal. No fix except replacement of either the whole phone or vibration unit (may be tricky involving soldering, not sure haven't tried it myself). One thought that occurs to me right now is that it could be something physically impeding the spinning, like some hair, you could try opening it up and seeing if it's cleanable.
Sent from my SPH-D700 using xda premium
vitreoush said:
Sounds like you have a busted bearing or brushing in the motor that spins the vibration unit (most work by spinning a little assymmetrically weighted rod). The decreased vibration is caused by the motor still spinning, but slower than normal. No fix except replacement of either the whole phone or vibration unit (may be tricky involving soldering, not sure haven't tried it myself). One thought that occurs to me right now is that it could be something physically impeding the spinning, like some hair, you could try opening it up and seeing if it's cleanable.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
The vibrator module is located within the speaker assembly, so there's no touching the motor. Replacing the entire assembly is super easy, it just requires one screw
Sent from my SPH-D710 using xda premium
SOLVED!
Squshy sent me a couple speaker modules and walked me through replacing it. It was a fifteen minute process, and it was actually pretty easy (eight screws and some plastic popping). I was sure I was going to snap my phone in half a few times, but it finally came apart.
A million, billion thanks to Squshy7!
Anywhere we can pick up spare motors on the cheap...beats waiting for Sammy to commandeer your phone for a week and a half.
...unless it would void my Squaretrade warranty?
Sent from my SPH-D700 using Tapatalk
Here is the first result from a Google search.
http://www.cellulardr.com/sprint-ep...amsung-android-sph-d700-intenna-assembly.html
So i had this issue about a month ago. My phone got submerged in water. I shut it off, took batttery out, blow dried it, and let it sit over night. Next day fired right up with no issues. About 2 weeks later, battery life goes in the toilet. Goes dead in 4 hours with no use. So i bought a new battery thinking that would fix it, but no, it did not. I can understand the phone having issues after getting totally soaked while turned on, but in the past, display used most of the battery, now im getting android os as the culprit. Its strange, what would change from display to android os just by getting wet?. Ive tried multiple roms, its always the same. Any suggestions? Fyi, it dropped in the toilet, nothing worse than seeing your phone screen on while shining up thru the water!
Sent from my ADR6300 using XDA App
You should just be happy it still works at all
...but sorry I can't be of any assistance in this matter. I would probably just try and start from scratch by flashing a stock 2.2 RUU and then rerooting and installing a custom ROM.
Sent from my ADR6300 using XDA App
donnyp1 said:
So i had this issue about a month ago. My phone got submerged in water. I shut it off, took batttery out, blow dried it, and let it sit over night. Next day fired right up with no issues. About 2 weeks later, battery life goes in the toilet. Goes dead in 4 hours with no use. So i bought a new battery thinking that would fix it, but no, it did not. I can understand the phone having issues after getting totally soaked while turned on, but in the past, display used most of the battery, now im getting android os as the culprit. Its strange, what would change from display to android os just by getting wet?. Ive tried multiple roms, its always the same. Any suggestions? Fyi, it dropped in the toilet, nothing worse than seeing your phone screen on while shining up thru the water!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Is everything working such as the sensors, compas, wifi, bluetooth, gps? If one of their chips got fried the os may be constantly trying to load or access something that is not working, therfore killing the battery. FYI the perfered method for drying a soaked phone is to put it in a bag of rice for a couple days. Blow drying just pushes the watter in deeper, and if you do it to much the heat can mess up the circuit board.
Everything works just fine. Im stumped.
Sent from my ADR6300 using XDA App
RamAir02 said:
You should just be happy it still works at all
...but sorry I can't be of any assistance in this matter. I would probably just try and start from scratch by flashing a stock 2.2 RUU and then rerooting and installing a custom ROM.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I guess if I was in your situation, I would try this first to see how that works. If it fixes it then awesome! If not, you know something else is wrong:-(
Sent from my Droid Incredible using XDA App
donnyp1 said:
So i had this issue about a month ago. My phone got submerged in water. I shut it off, took batttery out, blow dried it, and let it sit over night. Next day fired right up with no issues. About 2 weeks later, battery life goes in the toilet. Goes dead in 4 hours with no use. So i bought a new battery thinking that would fix it, but no, it did not. I can understand the phone having issues after getting totally soaked while turned on, but in the past, display used most of the battery, now im getting android os as the culprit. Its strange, what would change from display to android os just by getting wet?. Ive tried multiple roms, its always the same. Any suggestions? Fyi, it dropped in the toilet, nothing worse than seeing your phone screen on while shining up thru the water!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
are you sure all the water is gone? also the minerals in water will stick around long after the water is gone i bet there is something in there that is shorting it out but on a small scale.
i would suggest to take the phone apart and make sure you dont see any white or milky deposits on the MB or any where else. if you see some you can use 91% or higher isopropyl, (rubbing alcohol) i would use 98% but its harder to get, you can find it at a medical supply store though. Clean up the board and let it air dry before putting it all back together.
taking the phone apart is fairly simple you just need to be patient. i used this video when i needed to swap screens.
synisterwolf said:
are you sure all the water is gone? also the minerals in water will stick around long after the water is gone i bet there is something in there that is shorting it out but on a small scale.
i would suggest to take the phone apart and make sure you dont see any white or milky deposits on the MB or any where else. if you see some you can use 91% or higher isopropyl, (rubbing alcohol) i would use 98% but its harder to get, you can find it at a medical supply store though. Clean up the board and let it air dry before putting it all back together.
taking the phone apart is fairly simple you just need to be patient. i used this video when i needed to swap screens.
Click to expand...
Click to collapse
Ill give that a try when i get home, thanks!
Sent from my ADR6300 using XDA App
Took it apart a few days ago, no residue at all, then bam, today phone dead in 3 hours. Put it on xharger, got it fully charged, removed from xharger 5 hours ago, and im at 70% battery! I have no clue, i changed nothing , it just started holding a charge again.
Sent from my ADR6300 using XDA App