Have anyone got solution for WaterDrop Detection(tab disables touch for 3 sec after a long 10-12 sec touch) feature on galaxy tab 2.pls help its troubling a lot while playing games...
Pls somebody help.no one having this problem?
yes,I also have this problem, I think this sh*tty 'feature' must be disabled, but I have no idea how to do it? maybe some kernel tweaking?
I can't get mine to do this
I think I found where it is in the touchscreen driver, may be increased when I post an updated ROM build for anyone using my ROM.
This would be great! i send my tablet to service center because of this problem
Sent from my GT540 using xda app-developers app
Related
Hello,
my Backbutton activates itself. While I am watching Videos, or whatever I do it stops shining and I am out of every application I'm using. After about half a minute it's shining again and I can use it normally. It's like pushing the button multiple times. Does anyone has an idea how to fix it? I tried different roms but it looks like an hardware failure to me.
Sent from my Nexus S using xda app-developers app
Happened to me as well it is an issue sometimes with samsung but covered under warranty bring it in to sprint
Hit the thanks button if i helped
Sending it back for support is not an option for me. I imported my device from the US to Germany. The support at Samsung Germany told me that they are not responsible for AMOLED devices.
My second problem ist that my IMEI is crashed since I flashed a rom where the dev made a little mistake. So Samsung won't give me any support.
I thought about changing the display but the price for a new one is about 190 Euro. Way too much... I can assemble and disassemble the device but I think that cleaning the device will not solve the problem.
Any suggestions?
Sent from my Nexus S using xda app-developers app
srichter said:
Sending it back for support is not an option for me. I imported my device from the US to Germany. The support at Samsung Germany told me that they are not responsible for AMOLED devices.
My second problem ist that my IMEI is crashed since I flashed a rom where the dev made a little mistake. So Samsung won't give me any support.
I thought about changing the display but the price for a new one is about 190 Euro. Way too much... I can assemble and disassemble the device but I think that cleaning the device will not solve the problem.
Any suggestions?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
It has nothing to do with the display though.
That's likely the part failing:
http://www.globaldirectparts.com/Nexus-S-Navigator-Flex-Ribbon-p/smsng6098595.htm
http://stellatech.com/samsung-gt-i9020-nexus-s-ui-flex,a,en,810423.html
Verify that the one you currently have isn't simply not connected right.
Thank you. I will have a look if the part is not right connected.
Maybe I have to replace it. But in that case 25 Euro are much cheaper than 190.
Sent from my Nexus S using xda app-developers app
This happened to me once. A day later my display completely died. I could turn on my phone, answer calls, etc the touchscreen worked, but I couldnt see anything. I had to get a new one..
I had this problem too.
I flashed a different radio, and boom!! issue resolved
I occasionally get this too. It only comes up when I'm using cm/cm based kernels though, very odd. I'm on matrix right now and it seems to Beowulf, anybody have some tips or suggestions?
Sent from my iPad using Tapatalk HD
I tried a different kernel and it looks like the problem is solved. I know that you should not count your chickens before they are hatched. But I really think that the kernel was the problem.
Anyway, I am just happy that my phone is working properly.
And now I am waiting for jellybean.
Sent from my Nexus S using xda app-developers app
srichter said:
I tried a different kernel and it looks like the problem is solved. I know that you should not count your chickens before they are hatched. But I really think that the kernel was the problem.
Anyway, I am just happy that my phone is working properly.
And now I am waiting for jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
What kernel were you using?
It was not the Kernel!
Changing the radio solved the problem.
Sent from my Nexus S using xda app-developers app
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1277226
I had same problem and fixed it that way.
Sent from my Nexus S 4G using xda premium
It's Alive!
I don't see how the kernel would have anything to do with the backbutton. Although if it worked out then hey that's awesome. Amazing how much I have learned by reading the forums on this site.:victory:
Just clean off the the backbutton, and maybe it will stop or you have a software bug.
Hi all
I'm having this issue where randomly the touch screen stops registering my touch, and the only way to get it to work is to turn the screen on and off.
Hardware buttons work fine, and I have tries different ROMS.
Anyone know anything about this issue? Thanks
Sent from my Nexus S using Tapatalk 2
bump
im not sure how much of an issue this is, i used have that problem sometimes but not since i started using a task killer again. its possible its just a lag issue
Sent from my Nexus S 4G
bringonblink said:
Hi all
I'm having this issue where randomly the touch screen stops registering my touch, and the only way to get it to work is to turn the screen on and off.
Hardware buttons work fine, and I have tries different ROMS.
Anyone know anything about this issue? Thanks
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
As you said randomly, try use clean stock ROM for days to see if it is jammed by applications or not, I have that problem as well sometimes, due to some apps fully occupied CPU and make everything else non responsive...
Sent from my Nexus S using xda premium
the UI might be lagging as well if youre using the noop i/o scheduler.
Sent from my Nexus S 4G
hello, i have samsung captivate i897, it warks good, but sometimes, when i'm using phone, sometimes touchscreen doesn't have any reaction, i should lock and unlock whit power button, and then it's ok. i tryed stock 2.1 2.3.5 roms, and custom aopk 4.0.1 and now i have 4.1.1 but same problem.. when i had 2.1 version this problem was very rarely. what can i do? pls help me.
please someone help me:
Cm9 works really good.
Sent from my PantechP9070 using xda app-developers app
it may just be a lag in response due to busy state. have you tried waiting a minute or two when the screen goes unresponsive? the fact that it is worse with later os suggests it.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Do you have an aftermarket off brand phone case installed? Sometimes the edges of them hang over the screen and can trigger your multiple pressure points.
re
Rexdango said:
Do you have an aftermarket off brand phone case installed? Sometimes the edges of them hang over the screen and can trigger your multiple pressure points.
Click to expand...
Click to collapse
nop i havn't.. maybe it is problem of bootloaders? or kernel? no idea??
I just get my galaxy sl and im facing a really strange problem :
the touchkeys acting really weird sometimes they work fine and some other times i cant use them (the backlight turned off ) but when i lock the screen mostly they return to work fine . i tryied flashing some number of roms but its the same problem.
Im new here by thee way so please answer my question soon and thaks again.
sfndroid said:
I just get my galaxy sl and im facing a really strange problem :
the touchkeys acting really weird sometimes they work fine and some other times i cant use them (the backlight turned off ) but when i lock the screen mostly they return to work fine . i tryied flashing some number of roms but its the same problem.
Im new here by thee way so please answer my question soon and thaks again.
Click to expand...
Click to collapse
+1 heve a same problem too..
its really annoying any suggestions ...?
Try using the qwerty kernel, with this kernel you can adjust the touch sensitivity
I have the same problem from long time ago
Same like me... I think hardware problem.
Sent from my GT-I9300 using xda premium
i've solved mine.. i replaced the keypad cable flex.
Me too it maybe because the touchkey have a problem
Sent from my GT-I9003 using xda app-developers app
Hi, I have a problem with the touch screen of the Nexus: a few days ago I realized that a central band of the screen, more or less half an inch high, no longer responds to touch ... To understand, I attach a picture made with 'Position pointer ' from 'Developer options'.
I wonder if anyone has ever had experiences like this, and what do you advise me to do,namely if trying to change the screen, or maybe other most basic solutions (I've read on the web of people who recommend 'squeeze' the screen). Unfortunately the warranty has expired three months ago ...
Thanks in advance
Exact same problem with my nexus, strange:screwy:
Sent from my Nexus S using xda app-developers app
So, what have you done?
hekomat said:
Exact same problem with my nexus, strange:screwy:
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Nothing yet, living with it for the past two weeks, I don't have the time to bring it to an expert yet
Sent from my Nexus S using xda app-developers app
Bump, anyone?
Sent from my Nexus S using xda app-developers app
Had the exact same problem with my old android phone, it was after a great fall... I assume that it is a hardware problem and you have to replace your touchscreen to fix it...
But its not a big deal as you dont use that part most of the time and also "auto-rotate" is always present to help you... And if still you cant touch some things then use VNC viewer...
http//it.kioskea.net/forum/affich-16636-touch-screen-samsung-s5320-non-funziona-piu
I do not know if it can be somehow help .. The page is in Italian, use google translate .. It is said to 'squeeze' the screen, many people seem to have solved .. Do you say that is our case?
Thanks
MD