[Q] Froyo problem or water damage maybe? - General Questions and Answers

Hi all,
First post into this forum so be gentle
I've got a Samsung Galaxy S (i9000)
About two months ago I did drop it in a bath (parties eh?) and dried it out for a couple of days in rice, which seemed to have recovered it - bottom buttons did flicker for a bit before I did this (i know, i know, i shouldn't have even switched it on!) Problems seem to have been solved, drying it out seemed to have worked perfectly!
Few weeks ago I got it flashed manually by Samsung Service Centre from Android 2.1 to Froyo 2.2,
However, for about a week now I've been having issues with the same buttons on the bottom of the phone (touch sensitive Back button and Options button) but no problems with the Home button. Odd thing is it isn't persistent, every so often they will work - about 20% of the time - sometimes after hitting the lock button and unlocking the phone.
So.... the ultimate question is, do you think this is a software problem or hardware problem? (Froyo or water damage?!)
I havent done a factory reset just yet, need to spend some time to back stuff up - first thing to try?
Any suggestions would be great, or if you have experienced any similar problems.
Thanks!

Most certainly looks like the water did some damage, but maybe you could try formatting and hard reset but i dont think Froyo has this issue

Ok an update on this, restored the phone back to factory settings. Still having the same issues with the buttons, however they work after a few locks and unlocks of the phone, last about 15-20 presses within the same screen but can go if I switch application.
I'm suspecting there may still be some dampness in the phone so I'm going to try the rice method again and ordered some mini screwdrivers to have a look inside and see what the issue could be.
I just find this odd the problem has only occured within the last week, unless the phone has been exposed to more water (rain) without me noticing.
Do Samsung Galaxy Ss have a water damage indicator?

booya-al said:
Ok an update on this, restored the phone back to factory settings. Still having the same issues with the buttons, however they work after a few locks and unlocks of the phone, last about 15-20 presses within the same screen but can go if I switch application.
I'm suspecting there may still be some dampness in the phone so I'm going to try the rice method again and ordered some mini screwdrivers to have a look inside and see what the issue could be.
I just find this odd the problem has only occured within the last week, unless the phone has been exposed to more water (rain) without me noticing.
Do Samsung Galaxy Ss have a water damage indicator?
Click to expand...
Click to collapse
I think its on the back when you remove the back plate, there is a white sticker

Related

Search button activated randomly without being pressed

Edit: SOLVED
Problem: Water or some liquid mixture with water and other conductive chemicals can leak through the outer edges of the glass screen, causing electrical shorts on any of the navigation buttons. Thus avoid applying direct pressure with damp cloth along the perimeter of the screen.
Solution: Place the phone in a ventilated area as long as needed. In a severe case, this could take a very long time (a blow drier may expedite the process), so you may want to seek instructions on how to dismantle some of the phone components to allow drying, or disable the search key temporarily, or send the phone in for repair(last resort).
---------------Original Post-----------------------
As I type, my Samsung Captivate appears to be possessed with an obsession with clicking the search button all by itself, at random times. I've searched around the forums and have yet to find a solution that works for me.
I'm running Cognition 2.4
The phone is about 1 week old, with the problem starting at about 5 days.
I replaced the phone initially because it would shut down randomly. Now this one seems to have yet another malfunction
EDIT: Also note that the problem began shortly after cleaning my screen with a slight amount of monitor cleaning fluid and microfiber cloth. Whether this is coincedental or not, I don't know.
Does anyone know what might be causing this, or know how I would go about disabling the search button altogether?
i had the same problem, its kinda just went away for me haha
Hmm, I also hope it goes away as mysteriously has it appeared if a solution is not found.
I'm trying to make changes to "system/usr/keylayout/melfas-touchkey.kl" with "droid explorer", but every time I change the file, delete it, or replace it, the file always seems to revert back. Once I figure out how to do this, the problem should be temporarily fixed.
EDIT: My current theory for what causes this is that it occurs due to an electrical short after the screen has been exposed to liquid of some kind. If you look closely, there are thin cracks around the glass of the screen. Whether these cracks are water-permeable or not, I don't know. But due to the nature of this problem coming about randomly, and disappearing randomly for various owners, it would explain the effect of drying. I read someone say that he had this problem on two different phones, so maybe he cleaned both of them in such a way that affected the navigation buttons?
If anyone else can contribute to this theory, please do!
EDIT 2: The frequency of search button activation has increased significantly since the first symptoms appeared. I highly doubt this is software related. There is a apparently an issue with the circuit for that specific button. Considering that my cleaning of the screen was the only possible event that could have impacted the circuit, I am now leaning towards that prospect. There doesn't seem to be an easy way to completely dismantle the Captivate and let it dry.
EDIT 3: I'll focus a fan on the phone over night, then focus a blow dryer on it in the morning.
Had the same problem, it was like that since the first day I got it 07/18. It got worse for a period and now it mysteriously doesn't seem to have the problem anymore. No clue what it is from.
SOLVED
Problem: Water or some liquid mixture with water and other conductive chemicals can leak through the outer edges of the glass screen, causing electrical shorts on any of the navigation buttons. Thus avoid applying direct pressure with damp cloth along the perimeter of the screen.
Solution: Place the phone in a ventilated area as long as needed. In a severe case, this could take a very long time (a blow drier may expedite the process), so you may want to seek instructions on how to dismantle some of the phone components to allow drying, or disable the search key temporarily, or send the phone in for repair(last resort).
you might also try putting it in a ziplock bag with rice in it. (the rice will absorb the water)
Has the proposed solution worked for anyone?
Hi,
I am wondering if the proposed solution worked for anyone? What do you exactly do? Leave the phone in the sun for it to dry out. With combination of blow dryer?
With the battery out? I've had this phone since August and I initally thought it was a software issue. After couple of hard resets, roots and upgrade to 2.2 the problem still persists.
Any suggestions? Should I try all combinations? Rice Ziplock bag?
Just as a note. Used to have a lot of random search loads. Along with the moisture thing...a lot of us right handers contact the corner and it does need a direct tap of button to trigger as touch screen. If you notice the settings button never randomly pop up. Additionally, from wrar and use the plastic can gain some flexibility. Must my two cents to help avoid letting ATT screw up their phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
meadhros said:
Just as a note. Used to have a lot of random search loads. Along with the moisture thing...a lot of us right handers contact the corner and it does need a direct tap of button to trigger as touch screen. If you notice the settings button never randomly pop up. Additionally, from wrar and use the plastic can gain some flexibility. Must my two cents to help avoid letting ATT screw up their phone.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
And in no case...let best but put a screen protector on for you....that will take days to dry...
Sent from my SAMSUNG-SGH-I897 using Tapatalk
I've had that issue in the past, on stock Eclair, and it was an easy fix for me. All I did was flash a custom ROM. I can't say that I tried it on stock 2.2, but an Odin didn't help, so I went custom and it disappeared.
WOW! Thought i was alone.. I also have the phantom button activation problem... but it's not the search button, it's the home button and back button. I know for a fact my phone has not been exposed to moisture. I noticed it after i flashed an OC'd kernel. I tried every OC/UV setting in the voltage control APP thinking it had something to do with the increased MHZ, but the problem didn't go away. I have since flashed a variety of custom roms and regular non OC'd kernels, but the problem still is present. I saw someone post a little while back about the same issue and that they sent their phone in and at&t replaced something having to do with "LIB." The submitter didn't have any idea whether the "LIB" was related to software of hardware. I'm considering sending my phone in, but i hate the idea of being without my phone for 2-3 weeks. If anyone stumbles upon a fix, please do share.
brianray14 said:
WOW! Thought i was alone.. I also have the phantom button activation problem... but it's not the search button, it's the home button and back button. I know for a fact my phone has not been exposed to moisture. I noticed it after i flashed an OC'd kernel. I tried every OC/UV setting in the voltage control APP thinking it had something to do with the increased MHZ, but the problem didn't go away. I have since flashed a variety of custom roms and regular non OC'd kernels, but the problem still is present. I saw someone post a little while back about the same issue and that they sent their phone in and at&t replaced something having to do with "LIB." The submitter didn't have any idea whether the "LIB" was related to software of hardware. I'm considering sending my phone in, but i hate the idea of being without my phone for 2-3 weeks. If anyone stumbles upon a fix, please do share.
Click to expand...
Click to collapse
Try a gingerbread rom.I've had the same problem,back and home key.No matter which froyo rom I run,it would act up randomly at times.I dont spend enough time on eclair to be sure that it does it,but I've been running GR-9 for two days,has not happened once.Coincidence?Maybe....Now running GR-11 for the second day,so far so good.
Sent from my GT-I9000 using XDA App
I agree with the op that the cause is water/moisture in the phone. I have had it on all android versions I have used. And the fact that that it comes and goes is strong evidence in my opinion
Sent from my SAMSUNG-SGH-I897 using XDA App
It might be moisture in some cases, but....
Post getting old, but new to me! My random search problem is definitely not moisture related(unless high humidity outside is considered a problem for a cappy). My phone stays dry, I even clean it with a lint-less cloth, so water isn't the issue(its in a otterbox). I read some post on other sites that show the only fix is either allowing samsung to work on it, or get a refurb from att. I think this problem is also related to all those wrong contact sent messages to, which has happened to me several times with some embarresing happenings . I updated to gb 2.3.5 and problem still exist, plus I use handcent for messaging, and I havn't sent a mis-message yet.
There's another thread on this (search 'crazy back button' and my tests on many roms indicates that it has to with the blk app that mods the buttons. Many roms come packed with versions of it.
No longer sent from my BlackBerry.
Add me to the list with this problem. At first I thought it was an old screen protector. I changed that out last light but I cleaned the screen first by spraying it with LCD cleaner I guess I'll have to wait for it to dry a bit more. I've also been playing with recent Glitch kernels with BLN issues so I can't figure it out!
Well I got the BLN issues sorted. Still can't figure out the search button. There's got to be some way to disable it completely
I get this problem at random times when using Google Maps / Navigate, while the phone is in the car dock. At random times, the search will just pop up. No idea why
While using the phone in the rain one day, the touchscreen pretty much became inoperable once there were multiple droplets on the screen. Luckily I did not have any seepage under the glass, though.
I also concur with meadhros- I've found that when gripping the phone in my right hand, the edge of the pad of my palm at the base of my thumb sometimes sets off the search, since it wraps around the edge of the glass slightly.

Captivate with soft button issues.

Hey guys I'm posting today because I have a little problem or a huge problem I should say at this point. Anyways, I've owned a Captivate since they first came out a couple months ago. I've never had any problems with mine up until about 2 or 3 months ago when the phone started doing something weird. The bottom row of soft buttons on the phone will press themselves. Now only the back button and home button press themselves. The problem started out around the time I flashed Serendipity for the first time (not blaming the rom) I noticed the buttons would press themselves randomly at times and it started out slow, maybe once or twice a day and it didn't really annoy me. Flash forward to today and my phone is practically unusable because of this problem. Any time I wake the device from sleep the home and back buttons will rapidly press themselves over and over and over until I furiously tap either button to get the buttons to stop pressing themselves.
The problem will restart itself about 30 seconds after stopping it and It never stops. I've tried numerous re-flashes with no avail. At first I thought the problem was caused by a bad flash on my part because the problem started after I had just flashed a new rom. But I've known for a while now that wasn't the case. I've never dropped this phone or submerged it in water. This problem just popped up out of the blue one day and never went away.
Do I have a defective phone?
Thanks for the help.
Had the same problem, not to the extent your having more like once an hour they would go crazy. Placed the phone in some rice over night and the problem was gone. Im pretty sure, for me at least, was condensation had worked its way under the glass and was causing contact problems. Worth a shot for you. Never had the problem again after that.
I never even found out how it happened, though I suspect the steam from a hot shower did it.
how is your gps? if it sucks, go for warranty while you can, samsung has a 1 year warranty cross your fingers for a better replacement, or if you go through Att and you get a refurb who knows..... the board inside wont match the date under the battery and who knows how it will work.
whiteguypl said:
Had the same problem, not to the extent your having more like once an hour they would go crazy. Placed the phone in some rice over night and the problem was gone. Im pretty sure, for me at least, was condensation had worked its way under the glass and was causing contact problems. Worth a shot for you. Never had the problem again after that.
I never even found out how it happened, though I suspect the steam from a hot shower did it.
Click to expand...
Click to collapse
I'll try the rice thing, can't believe I've never thought of that. I've never dropped water on the phone but it has been in the bathroom with me when I've taken showers or what not. Thanks for the idea.
TRusselo said:
how is your gps? if it sucks, go for warranty while you can, samsung has a 1 year warranty cross your fingers for a better replacement, or if you go through Att and you get a refurb who knows..... the board inside wont match the date under the battery and who knows how it will work.
Click to expand...
Click to collapse
My GPS does indeed suck, It takes about 5-10 minutes to get a lock on anything sitting outside. My phones still under warranty until this November so I think if I don't solve the problem soon I'll just get a new one.
Does ATT upgrade the phone to a newer version if you replace it with the warranty? I might hold out until ATT releases the Cappy 4g or whatever they're going to call it.

[OPO] Touchscreen issue after foam party

Hello,
So maybe you already laughed a little bit by reading the title of the thread.
I had a foam party yesterday and I was stupid enough to have my oneplus one in my pocket. After about 15 minutes I finally realized that it would be a good idea to put my phone away. When I came back home in the night everything was fine but when I woke up today the touchscreen wasn't responding (only physical buttons worked). So I tried to hard reboot the phone and then everything was working again.
But after some minutes of use, I noticed that a part of the screen was reacting strangely. I went in the setting to activate the "cursor route" and I saw that there is kind of a band in the middle of the screen (about 1 cm) where the tactile is not working.
I removed the back cover and noticed that is was a little bit wet inside .. so I put my phone into some rice.
I tried to see how the screen is responding in my recovery (twrp) and the problem is also there, so I'm pretty sure it's an hardware problem.
Do you have any tips or things I can try to do ? I just want to avoid the Oneplus RMA because I don't want to be without phone for 2 months ..
Thanks in advance !
PS : I'm running CM 11S (latest OTA) and I'm rooted.
Stop using the device at all, you're potentially doing more damage every time you use it while it's wet/damp. Leave it in rice for three days without touching it. After three days is up take it out and inspect the touchscreen again.
okey, so I leave it off in the rice. 3 days without phone will be hard
If I have to replace the tactile screen (without LCD), do you know if I have to use thermal tools ?
pocj30 said:
Hello,
So maybe you already laughed a little bit by reading the title of the thread.
I had a foam party yesterday and I was stupid enough to have my oneplus one in my pocket. After about 15 minutes I finally realized that it would be a good idea to put my phone away. When I came back home in the night everything was fine but when I woke up today the touchscreen wasn't responding (only physical buttons worked). So I tried to hard reboot the phone and then everything was working again.
But after some minutes of use, I noticed that a part of the screen was reacting strangely. I went in the setting to activate the "cursor route" and I saw that there is kind of a band in the middle of the screen (about 1 cm) where the tactile is not working.
I removed the back cover and noticed that is was a little bit wet inside .. so I put my phone into some rice.
I tried to see how the screen is responding in my recovery (twrp) and the problem is also there, so I'm pretty sure it's an hardware problem.
Do you have any tips or things I can try to do ? I just want to avoid the Oneplus RMA because I don't want to be without phone for 2 months ..
Thanks in advance !
PS : I'm running CM 11S (latest OTA) and I'm rooted.
Click to expand...
Click to collapse
Lol, so it's a hardware problem that you soaked your phone ? Sounds more like a user problem.... Good luck trying to pass that on a RMA...Well good luck with trying to get a RMA period... lol
pocj30 said:
okey, so I leave it off in the rice. 3 days without phone will be hard
If I have to replace the tactile screen (without LCD), do you know if I have to use thermal tools ?
Click to expand...
Click to collapse
It'll be much longer without your phone if you don't though. And what @Cholerabob is right, what you've done to your phone isn't covered by warranty, warranty doesn't include damage caused by the owner.
Transmitted via Bacon
Cholerabob said:
Lol, so it's a hardware problem that you soaked your phone ? Sounds more like a user problem.... Good luck trying to pass that on a RMA...Well good luck with trying to get a RMA period... lol
Click to expand...
Click to collapse
If you read my post better, you will understand that I said I don't want to pass it on RMA. Of course I know that I will have to pay about 150e because it's my responsibility and it's not covered by any warranty. That's why I want to change the component myself.
And yes, it's an hardware problem because of a user mistake.
Try to make constructive answers next time at least.

S6 Pressing Back Button By It's self (Capacitive key)

I'm not sure how this is possible, but about once or twice a day, the back button on my S6 is pressed on it's own. It has happened when the device has been on the desk, I see the soft keys light up, the device vibrates like they've been touched and the app I was on went back, all while I was not even touching the device.
It's happened mostly when I'm holding the phone but not even close to touching the buttons, and once it happened and pressed the back button about 10 times in a row while I watched it.
The phone is completely undamaged, perfect condition, never touched water, not dirty at all, buttons are 100% clean. Happens while it's charging or on battery.
Has anyone else experienced this?
(My device was repaired by Samsung for a different issue, motherboard replaced, this only started happening after the repair)
i have, started like yours random. then it started happening more and more so when i was at the store waiting for someone i decided to factory reset ( factory reset twice while at the store) but it got worse. couldn't even get passed initial setup the phone just kept spamming back button so i just kept going back. luckily i already ordered a replacement s6 from tmobile since i was having some other issue with the phone. sadly the replacement s6 took over 7 days to get here. shipped through UPS and got to hawaii then for some reason UPS gave it to USPS for delivery. kinda sad that i ordered screen protectors 2 days after i ordered replacement phone and the screen protectors got here 4 days later through USPS. but other than that my NEW ( we all know its refurbished) galaxy s6 so far has no issues. even the no audio on calls is fixed.
also if you are going to order a replacement, be sure to let them know you have a GALAXY S6 and the date it was released. i say this because the 2 tmobile reps i talked to kept asking questions they say it was for them to determine if my galaxy s6 that was what 2 almost 3 months old at the time was still under warranty
My s6 was showing the same issue with the stuck back button.
It started randomly but than it went crazy and stuck. I wasn't even able to use it.
But 1 factory reset fixed it.
But yesterday the random stuck back button started again when the phone was on my desk and it was really hot (weather was hot as well as the phone). I turned it off for a while and apparently the issue stopped.
I'm not sure it's temperature, firmware, whatever related but I really don't want to factory reset it again.
No solution here, but it is happening to me as well
Solved
Hi i had the same problem aswell , i bought samsung s6 in Pakistan, after the update the back button kept pressing ghostly, i went to local samsung repair shop and the assistant reset something from the setting and then it was fine, i even asked him what you did and how you did? but he said it is secret lol very stupid. i could have post the solution if i know it, but i think it is very easy and something to do with setting. i am sure it is not hard/soft reset. i will post this on other forums to help other people.
thanks
having this problem with my phone too, i cant even get it to stay on the settings screen long enough to back up my stuff
edit: well i think i solved it. i tried clearing the cache, didnt work. then i did a hard reset, didnt work. then i went back and cleared the cache and did a hard reset at the same time and it seems to have worked.
+1 same problem. It happens mainly when the phone is on the move. Funny thing it happened 3-4 times while taking the metro (go figure) with the data on. Usually when I turn off the data, it reduces the amount of back press.
Normal reset doesn't solve the problem. It stops after a while, probably when the phone cools down. I can't seem to reproduce it, but I believe it has something to do with the data on.
I don't really want to factory reset so I'm going to write to samsung directly as the phone is brand new.
i am having same issue too.
---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------
Did anyone try loading a custom rom and got it fixed ?
I've had that issue with my first one. Took it back ASAP as it was DOA. Got a brand new one 3 days later as they didn't have any in stock. This one doesn't have any problems. Don't worry to mutch about it. Get it exchanged.
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
I have the exact same problem...did anyone contact the manufacturer and got a response on the matter?
I believe it may be an app setting messing with the system settings. My device did it once and wouldnt allow me to use my device. After factory reset it made it worse so i used twrp and wiped everything but my modem and flashed my stock firmware and it stopped and hasnt done it since
Sent from my SM-G925P using Tapatalk
faiding said:
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Hum that's interesting, thanks for your precious input on this.
I did contact Samsung who asked me to do a factory reset. It didn't change anything.
They redirected me to a Samsung office in Paris, not for repair but for a deeper factory reset... (not sure what they are talking about), but I haven't been there since due to lack of time.
However, I didn't experience the problem since the last update FXXU3QOKN so I'm keeping an eye on it.
Following "faiding's" comment, I'll probably pay them a visit for a replacement.
working "workaround"
workaround:
lower the speaker volume to ~75% in all settings (Media, ringtone, system, notifications, etc...)
Whats going on? why is it working?
some posts ago someone (user called "faiding") mentioned something about EMC leak, or at least he meant to, by mentioning a faulty insulation.
with that in mind i did some testing and found out that the closes radiating component it the speaker... and once you lower its emissions even thought the faulty insulation, the EMC leak is sufficiently low and the 'capacity short' is avoided.
Note: depending on how 'faulty' is your insulation (it varies from one phone to another depending on production line assembly) lower the volume until the issue stops accruing.
not full-proof but working
What worked for me is turn power saving on
possible fix
might be a coincidence, but this worked for me:
(I am a new user so i cant post a link but here is what you should do)
1. enter YOUTUBE
2. find this video: "Samsung Galaxy S6 Touch Screen Sensitivity Fix"
worked like magic for me
Repair tech
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
dslayer83 said:
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
Click to expand...
Click to collapse
Hi dslayer83,
I've the same problem with my S6
Could you solved the problem replacing the charging port?
It would be very important to me knowing how to repair the phone because I buyed it abroad. In my country Samsung does not cover warranty.
Up with this thread!
I had an S6 since January.. initially the problem was very random, maybe 1 or 2 times per day, sometimes would go crazy for a while
Then i had some time with no defect at all (a couple of weeks?) without doing nothing
This past week, the phone was feeling like the MENU button (what menu as in this phone there isn't any?) and that was very weird!
Today, it simply went completely crazy, and now is completely unusable... i can't actually swtich it off as the back key is pressed so quickly i don't have the chance of doing nothing!
EDIT: Managed to reboot and wipe cache... now it is useable, but still hits the button from time to time
Update... went unuseable again today.... factory resetting now...
If it works, shall we suspect is something software related?
Update: Not working... it started giving the phantom touches just after the factory reset then suddenly stopped
Worked fine for few hours, then started craza again
Now i have done a wipe and factory reset again, and still unuseable

Nexus 5 water damage - screen's all black - motherboard related?

Hello guys,**
Well few days ago I accidentally dropped my Nexus 5 in a glass of water for just 1 sec. So I immediately switched it off and wait a bit to let dry then restarted it, and all seemed to work fine. But just some days later and up to now the phone boots up all fine as usual to the lock screen, and from there I can pull down the notification bar (and navigate through it, activate/deactivate wifi, etc..) but when I unlock it to get to the home screen it becomes all back and nothing appears on the screen even though the phone is still on.*
It's really confusing and weird. When I call the phone it rings (so no signal or sound problem) but I can't still access the screen to take the call as it's all back and unresponsive.
Following some suggestions I disassembled the phone and cleaned it dry but same results again! So now I think the problem is somehow related to the motherboard, coz as you might notice on some of the pictures attached, it seems that some plastic parts have melt down to cover other smaller parts. Anyway guys,*I'm just wondering if some of you guys had experienced something like that and if you were luckier*to find a solution or any directives that could help. Or you even think that's a motherboard problem like, do you know any ways to fix that o buy a new one somewhere??
PLEASE!!
Sorry apparently, I can't publish links until I get like 10 posts or plus..
But anyway guys, I'd really appreciate your help.
Why did you power it on and short circuit it on purpose for??
Bump
@SekouCheikh
Maybe it's a coincidence that you dropped it in water and this happened a few days later. Once in a blue moon mine does something similar to this (although not usually as start up only after lots of use), but I think it's related to an app or xposed. I only notice it after installing a bunch of crap again. Maybe try a factory reset (do it though the computer) just to see if it is somehow not hardware related? That's what I would try first.
Help please
Ttt
Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.
-SmOgER said:
Wait... Are you seriously posting from 2 different accounts??
<...>
First, simply try to factory reset or flash a new rom. There is not enough evidence to be sure it's a hardware problem, it could just as well be a coincidence that it started happening just now.
Click to expand...
Click to collapse
No, I just like to help
Help Op solve the problem please
Ttt

Categories

Resources