Search button activated randomly without being pressed - Captivate General

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.

Related

[Q] Froyo problem or water damage maybe?

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

[Q] Possible hardware problem of the back button?

I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
I want to say that I noticed something similar the other day, but it was short-lived, and I'm not 100% sure. It wasn't long enough or bad enough to make me think the phone is defective, but I'm a bit used to funky capacitive button responses from my N1 days.
I can't reproduce the issue right now, though. How much usage are you talking about needing to duplicate?
Does your phone get hot, or feel hotter than normal when this happens?
I'd see if there's some particular pattern or software that seems to trigger it if you're interested in trouble-shooting.
The problem goes away when I don't touch the phone for a while (it seems that 1 hour is enough to reset the problem).
It seems "recharging".
Then with normal usage, nothing in particular, just even browsing in the settings/maps/market/browser etc., in few minutes the problem appears. The button definitely loses his "power".
It's very annoying, and my friends confirmed the same behavior.
EDIT:
Forgot to sat that the phone is not getting hotter, everything else is really normal.
Cheers
Mine definitely can be used for much more than a few minutes without the problem you're describing appearing.
I'd take it back. Factory reset the phone to protect your private data before taking it back. After the factory reset, you might want to test the behavior again, if it went away, the phone's not defective, you just had some software glitch.
Reminder, factory reset erases everything on the phone, so if you do it as troubleshooting step, be prepared to have to set the phone up from scratch again...I'm sure you knew this, but just covering my butt in case you didn't. It's a good trouble shooting step no matter what if you don't mind the hassle of re-setting things up.
I have a similar experience with the back button. Not sure what to think yet.
Sent from my Nexus S using XDA App
I had a similar problem when I had the Vibrant. Just exchanged it and luckily I got a better one without any problems. I did find out though if you are using the screen protector that came with the phone, it can cause this type of problem.
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
michele72 said:
No problem, I will try everything tomorrow. This is not my primary phone (still loving my rooted Nexus One with CyanogenMod 6.1.1 ;-) I can't renounce to the colored trackball for the different notifications), but just a "dev" phone for testing purposes.
Click to expand...
Click to collapse
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
distortedloop said:
The app NOLED from the Market may interest you if you can't live without trackball style color notifications. Seems to work fine when I tested it.
Click to expand...
Click to collapse
Thank you, giving it a try.
Anyway, today I factory-reset my telephone and the problem of the back button is still there. I am returning the device.
Back button non responsive
Hi,
I just got my new nexus S (about an hour ago) that I was really excited about and am faced with a problem with the back button too.
Its got factory settings, so it cannot be a downloaded software issue. Also, I have not yet charged the battery at all, its still running on the same battery power that it shipped with.
The other buttons at the bottom of the phone (home, menu and search) all respond fine, its only the back button that does not seem to work. After going through this thread, I tried long-pressing the button, hard-pressing it, pressing just above it, below it, etc. It just wont respond. I had removed the screen protector it shipped with, so that cannot be the issue either.
If this is a known hardware problem (i.e. others have faced it too), irrespective of whether it is acknowledged by Samsung / Google, I'll return the handset. I do not want to spend a fortune and be landed with a handset that does not work - forget working as desired, but it does not seem to be working as designed !
Thanks & Regards,
Rohan
Yep. Definitely a problem here with the back button. There's also two other threads here about it.
I'm having similar problems. I have to touch the button just right for it to work properly
Sent from my Nexus S using XDA App
I was experiencing the same thing with my Nexus S, wasn't sure if it was the case I was using! Took of case and still had problem. I eventually returned mine cause it seemed like it was getting worse! I have a new one worth no problems, definitely a hardware problem! Return it!
Sent from my Nexus S using XDA App
michele72 said:
I just wanted to share this, since I was able to replicate this issue with three different phones, also asking if other people are having the same issue.
I am using my Samsung Nexus S for three days.
I noticed that the back button (the first capacitive button on the bottom left) appears to have an hardware problem.
Basically normally it works fine, I mean when I'm not using the phone for some hours.
Then if I start to use the phone, after a moderate use (example installing applications from the market, browsing etc) the button gets less and less sensitive.
After some minutes it gets really annoying.
To make it work it is necessary to use a really stronger pressure with the finger, and it is not even always working!
I am planning to return my device, but today talking with some people/colleagues I discovered that two of them have exactly the same problem.
I'm suspecting there is a batch of Nexus S phones with this glitch, I am curious to know how many people have the same problem.
Note:
At first I thought it was a general issue of the capacitive buttons. But I can't replicate the same problem with the other three buttons, they work very smoothly just lighltly skimming the finger over them, even after long usage.
Anyone with the same problem? What is your experience with this button after some usage?
Cheers
Click to expand...
Click to collapse
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
same issue was with Nexus 1. less responsive buttons. thats why there is a bigger gap between the buttons and the screen for galaxy S phones. i dont know why they did such a thing again with the nexus S. its like samsung didnt learn from anything from HTCs mistake.
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
I think this is true ...
I have an HTC Desire with AMOLED screen.
When I play a finger intensive game, like "SkyForce Reloaded", after some times, the touch is not registered.
Then I must stop for a while, or change finger
Try that, you will know what I meant.
But, I don't have issue with the back button on HTC Desire because it is a hardware button. I am just trying to explain about loosing touch registration because finger interaction on (s)amoled screen.
PS: SkyForce Reloaded is an old school shot'em up game where you control a little space ship with your finger, shooting enemies.
ll_l_x_l_ll said:
those buttons work over the heat of your finger. thats why after use it doesnt get as responsive. its because the screen is also heated and the heat of the screen is effecting the buttons. thats why you need harder pressure for the phone to understand this is your finger.
Click to expand...
Click to collapse
The Desire's digitizer is the same Clearpad 2000 which is used in the Nexus One (and quite a few others), the problem there is that it's pants.
Rusty! said:
They work with capacitance, not heat. Hence it being called a capacitive screen with capacitive buttons.
Click to expand...
Click to collapse
lol, isnt called like that because it registers the heat from your fingers. thats why if you try to use a pen, it wont register . and thus. the screen is NOT resistive type "where it will recognize anything since its being pushed by force ? "
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Rusty! said:
Much more too it than that: http://en.wikipedia.org/wiki/Capacitive_touch_screen
Click to expand...
Click to collapse
from your link
"A capacitive touchscreen panel is one which consists of an insulator such as glass, coated with a transparent conductor such as indium tin oxide (ITO).[7][8] As the human body is also a conductor, touching the surface of the screen results in a distortion of the screen's electrostatic field, measurable as a change in capacitance. Different technologies may be used to determine the location of the touch. The location is then sent to the controller for processing.

[Q] Should I use stock when I take this for repair?

For a few months my phone has had a problem where the screen will take control of itself or become unresponsive, it's not the phone being slow, because hardware keys respond perfectly. Scrubbing the screen with a Lysol wipe helps sometimes, but I'd rather just have the problem taken care of (it seems like it's caused by fingerprints on the screen, which isn't a problem on any of my friends' SKs and initially wasn't on mine either).
Anyway, when I take my SK to T-Mo, should I flash a ROM that at least looks stock for warranty purposes or will they not care?
If I do need to go to stock, how would I go about doing that? As far as I remember, I've never taken a backup in recovery and never ODIN'ed (stupid, I know), so I've no idea what to do. I can flash ROMs perfectly fine, but going back to stock is a mind-boggler for me (disabling Voodoo, etc).
Thanks
Mine always does this.
1. The optical trackpad detects the sunlight, strong indoor lights, etc, as movement and causes spurious scrolling.
2. Water on the screen or a finger just outside the boarder of the screen causes the touchscreen to get confused and either not respond or move on its own.
3. The touchscreen driver is prone to crashing. About half the times I want to answer a call or something, I need to toggle the screen off and on with the power button before it'll work.
None of this is because the hardware has broken. 1 is due to a bad design, 2 is inherent to touchscreens of this type, and 3 is just bad programming.
Ha! I have to do #3 all the time. Glad to know it's not just me. Ridiculous.
Also FYI, #1 never happens to me. I see people here curse that damn sensor all the time, but I have never had mine move randomly in sunlight, and it generally works pretty well for me as arrow-keys.
I also do #3 all the time, and have had problems with the optical trackpad in the past (I've since disabled it).
What the problem appeared to be was that my fingers are oily or something, explaining why wiping the screen excessively was useful. I passed on taking it to the T-Mobile store and instead ordered screen protectors from Amazon. No problems since I applied one.
Has anyone else encountered this, or is this a unique problem? I got through nearly a year without having this problem, so maybe something went wonky in the screen. Anyway, problem fixed
DJTiCTAK said:
I also do #3 all the time, and have had problems with the optical trackpad in the past (I've since disabled it).
What the problem appeared to be was that my fingers are oily or something, explaining why wiping the screen excessively was useful. I passed on taking it to the T-Mobile store and instead ordered screen protectors from Amazon. No problems since I applied one.
Has anyone else encountered this, or is this a unique problem? I got through nearly a year without having this problem, so maybe something went wonky in the screen. Anyway, problem fixed
Click to expand...
Click to collapse
Happens all the time to my sidekick. Screen protectors did work tho
Sent from my SGH-T839 using Tapatalk 2

[Completed] Weird behavior after dropping my Moto X

I was rushing down the stairs when my Moto X 2014 slipped out of my hand.
It bounced down the stairs, one step at a time, then bounced off the last step, across the hallway, into the wall and then face down on the wood floor.
I'm using a cheap case with small bumpers around the screen, which may have prevented the glass from breaking.
But when I picked it up, it was frozen on the lock screen. Every time I tried to unlock it, it went blank, then showed the main screen quickly and went back to the lock screen. After a few attempts, I quickly concluded something must have gone wrong with the hardware. A fall like this can't affect the software, obviously. I was ready to kiss my $500 toy goodbye but gave it one last shot. I held the power button, tapped "power off", then restarted. It seemed to take a lot longer to restart, but it did, and now everything is totally back to normal.
What do you think caused the software to behave like that, if there is no hardware damage? Was it confusion by the rapid accelerometer changes or something?
Is there probably some subtle hardware damage I'm unaware of now? Is there an app that can diagnose this?
Did the fall cause the battery to dislodge temporarily or something, and the power fluctuation corrupted something in the memory? Would that explain the software malfunctioning, and then going back to normal after clearing the memory?
Sent from my XT1095 using XDA Free mobile app
Hi
Thanks for writing to us at XDA Assist. There's just no way to know exactly what happened and what caused the device to act like that, there are too many possibilities and variables. As long as the phone is back to normal that's the main thing.
No response in two days, thread closed.

S7 Water Damage

Hi
My S7 got damaged as back and recent apps capacitive buttons have started malfunctioning and phone behaves as if both are constantly pressed...
This happened after i tried to record a video under water (1 foot depth, 15s duration), while it had front/back protectors and full body protection through a cover which had audio jack and usb port plugs as well. I can safely say the pressure and time were both within limits of IP68 but the phone still couldn't handle it.
Can you suggest possible rectifications steps or suggestions to make phone usable again
Thanks
Let it completely dry out and don't use it whilst doing so!
Samsung has used internal coating of parts to prevent lasting water damage rather than seals.
Your problem likely occurred by using the hard buttons whilst the phone was still wet.
My guess is it should be fine if you are patient enough.
drummerman said:
Let it completely dry out and don't use it whilst doing so!
Samsung has used internal coating of parts to prevent lasting water damage rather than seals.
Your problem likely occurred by using the hard buttons whilst the phone was still wet.
My guess is it should be fine if you are patient enough.
Click to expand...
Click to collapse
thanks, i have tried to dry it as much as possible and now put in a bowl of rice as per internet wisdom waiting for a positive outcome...
secondly, would you know of any option to disable these capacitive buttons and enable android navigation bar without root?
Lieutenantdaan said:
thanks, i have tried to dry it as much as possible and now put in a bowl of rice as per internet wisdom waiting for a positive outcome...
secondly, would you know of any option to disable these capacitive buttons and enable android navigation bar without root?
Click to expand...
Click to collapse
Sorry no but others may do.
Good luck
Water Damage
I also have the same problem. My Galaxy S7 starts to behave like the Recent Apps capacitive button is pressed constantly. It's very frustrating because my phone was barely dipped in the water for just a few seconds trying to take an underwater selfie.
I had a Galaxy S5 before and I always had no issues taking my phone into the pool. I think Samsung had a better job making the S5 water-resistant than the S7. Very frustrating because S5 performs well having only IP67 rating than the S7's rating of IP68.
I tried heating the capacitive buttons hoping the moisture would dry up and putting it inside a closed container full of rice, but no luck. My phone is just 4 months old. Job well done Samsung! Really!!
iRavenX said:
I also have the same problem. My Galaxy S7 starts to behave like the Recent Apps capacitive button is pressed constantly. It's very frustrating because my phone was barely dipped in the water for just a few seconds trying to take an underwater selfie.
I had a Galaxy S5 before and I always had no issues taking my phone into the pool. I think Samsung had a better job making the S5 water-resistant than the S7. Very frustrating because S5 performs well having only IP67 rating than the S7's rating of IP68.
I tried heating the capacitive buttons hoping the moisture would dry up and putting it inside a closed container full of rice, but no luck. My phone is just 4 months old. Job well done Samsung! Really!!
Click to expand...
Click to collapse
wow, seems like this is a common problem then, how are u managing to use the phone?
i will share update tonight as the phone would be in rice for 48hrs which should be enough to dry out any moisture, but seeing your comment i no longer have high hopes
My phone is unusable as the Recent Apps will always pop-out rapidly. I don't want to get my phone repaired as opening the phone would void its "water-resistance." Yeah, it's not even water-resistant tho.
Is there a way to deactivate the capacitive buttons? If there is, are there any mods for this?
Give me some updates bro after 48 hours. Thanks!
iRavenX said:
My phone is unusable as the Recent Apps will always pop-out rapidly. I don't want to get my phone repaired as opening the phone would void its "water-resistance." Yeah, it's not even water-resistant tho.
Is there a way to deactivate the capacitive buttons? If there is, are there any mods for this?
Give me some updates bro after 48 hours. Thanks!
Click to expand...
Click to collapse
there's another thread where people have posted solutions to this problem, though its mostly for people having this issue out of the blue without anything to do with water...
one is to factory reset/install updates
second is install an app to disable button lights
http://forum.xda-developers.com/showpost.php?p=66129442&postcount=90
third is to install another app and change button actions
http://forum.xda-developers.com/showpost.php?p=66123403&postcount=89
i am going to try above solutions one by one in case phone doesn't recover, you should try and check as well
Problem persists [emoji20]
Sent from my SM-G930F using Tapatalk
I have this problem too: after brief water exposure both capacitive buttons stopped lighting and responding. Tried rice, heat, time - nothing worked. Everything else about the phone works fantastically. So going to attempt a repair next. Have looked at the ifixit teardown, having a hard time figuring out if I need to replace the screen\digitizer (meaning, the capacitive functions are built into the glass there), or the modules with the LEDs underneath (which don't seem to be readily available parts online anywhere), or something else. Anyone have any knowledge on how these two buttons interface and work and what the potential issue might be?
fredless said:
I have this problem too: after brief water exposure both capacitive buttons stopped lighting and responding. Tried rice, heat, time - nothing worked. Everything else about the phone works fantastically. So going to attempt a repair next. Have looked at the ifixit teardown, having a hard time figuring out if I need to replace the screen\digitizer (meaning, the capacitive functions are built into the glass there), or the modules with the LEDs underneath (which don't seem to be readily available parts online anywhere), or something else. Anyone have any knowledge on how these two buttons interface and work and what the potential issue might be?
Click to expand...
Click to collapse
Well your problem is different from mine as my phone's recent apps button was continuously pressed and I had to disable it
Maybe you can try root+xposed+good lock to have on screen navigation bar...?
Hope someone here can help you with the hardware fix. Do share update whatever the outcome
Sent from my iPhone using Tapatalk
like others have said, just put it in a bowl of rice and hope

Categories

Resources