Database Develop

Capacitive Button Responsiveness?

Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?

I've never had a problem with mine.
I saw a review saying that they got in the way when typing w/ the onscreen keyboard, but I haven't even had that, and I'd like to think that I have pretty normal-sized fingers.

Some people have problems, others don't i personally haven't. I wouldn't consider it to be something important enough to sway me from a sale though.

Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
Click to expand...
Click to collapse
Definitely! That's one of the biggest reasons why I want an N1. It has a good root and dev community and gets android updates first.
I just thought it'd be annoying to have to use a phone with crappy capacitive buttons, but I'm glad to hear that the problem has been fixed.
The only other thing I'm worried about is the dualtouch but it's most definitely going to get fixed in the next update.
Thanks to everyone for their input. I'll definitely be picking up an N1 soon

I have rooted and custom roms etc and I still hate the capacitive buttons with a passion. They are not nearly enough to topple the overall awesome that is the N1 but man I hate those things.

I only hate those buttons, when Nex is in my car mount!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Click to expand...
Click to collapse
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I also haven't noticed any change in the sensitivity with different ROMs or kernels. For me though, sometimes if I hit right on top of the button it won't register. I am used to just tapping it a little above and it works everytime.
As others have said, this is definitely not a deal breaker for me or shouldn't be for any person IMO. This phone's pros far outweigh the cons.

The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
Click to expand...
Click to collapse
When someone is doing that you should just say that it has Finger print authentication technology

absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...

xboomer55 said:
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
Click to expand...
Click to collapse
Did you just buy your N1 from Google brand new?

Those buttons are a pain in the bum, but you get used to them, the bigger problem is if the phone gets too cold it starts mis-registering the touchscreen necessitating a reboot or a bunch of mucking around to fix it. This is the biggest annoyance with the phone for me, hopefully they fix the screen calibration in 2.2!
Almost swapped mine for a Desire, thinking less of doing so now, unless anyone can offer a good reason

I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.

SilentMobius said:
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
Click to expand...
Click to collapse
Just realized that!!
It does not get the upward movement
It gets: right, left & down
So this means, one could set different options for different directions...

hacker01 said:
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
Click to expand...
Click to collapse
I have noticed no issues when holding the phone in my hands but the responsiveness is not that great if the phone is flat on a desk or a similar surface. I wonder what if anything the accelerometer may play a factor.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I dunna man, my 3-year-old daughter figured it out within a minute of getting my phone. I set her up in a game and she decided she wanted something else, so she messed with the capacitive buttons until she got out of the game. Once she had it once or twice (~5-10 seconds for her to figure out each time) it was pretty much instant after that. If a 3-yo can figure it out, I'm pretty sure it's not THAT difficult. Annoying, sure....but not difficult.

hacker01 said:
Did you just buy your N1 from Google brand new?
Click to expand...
Click to collapse
Yes. Direct from Google.

Wow there's definitely a good mix of answers. I thought that the newer batches of N1's fixed the capacitive button problem, but apparently not.
I guess there's not a definite answer. It seems the only conclusion you can make is that some N1's may still have the problem, some may not. Some can be fixed with custom roms and unlocking the bootloader and some cannot. Your results may very.
EDIT: After rereading some of the previous posts (more carefully. excuse my sleep deprived state lol), the capacitive button issue might actually be more of a feature than an issue. I've read similar posts about the capacitive buttons having that sort of "motion detection" thing to prevent accident presses. Hopefully for anyone still having the problem, you can reread some of the posts on this page and give their methods a try

I haven't had a problem with mine but I haven't had the problems most people say they have with the phone so I would recommend this phone to anyone that wants an android phone
-------------------------------------
Sent from my Nexus One

[Q] Touchscreen flakey?

I haven't seen this addressed here, but is anyone else experiencing flakey Nook Color touch screen behavior?
Sometimes it seems like there are random "ghost" touch/taps to the screen. It's very annoying, but power cycling or just locking and unlocking the device (by pressing power and getting back to lock screen) seems to fix it.
Here's a YouTube video which appears pretty close to what I'm experiencing:
http://www.youtube.com/watch?v=LiHH6mdH0WU&feature=related
Any insight would be appreciated. I've only had the Nook Color for 3-4 days, so if it is a problem specifically with my unit, I'm thinking I may need to exchange it.

I seem to be having the same problem, too. I DO hope it's the software and not the digitizer, though.

Oh, look further down this forum section. There's another thread about it and it has a recalibration procedure.

Its definitely the software. I was having issues and recalibrated and it works a lot better now.
I almost think b&n screwed up the edges on purpose to make page turning easier... seemed to be black holes around the screen edges and those seem to be gone now. Tested with a touch test app and it works correctly now (although I didn't test before the calibration so I can't confirm that didnt work fine before the calibration...)
Sent from my NOOKcolor using XDA App

how did u recalabrate it

drksilenc said:
how did u recalabrate it
Click to expand...
Click to collapse
http://www.nookdevs.com/Recalibrate_the_NookColor_touch_screen
Additionally, I went ahead and sent back to factory defaults for the 1.0.1 update and I tested the screen before recalibrating.
Exactly as I thought, the edges of the screen are calibrated so that when you get near the edge of the screen, it essentially "rolls" all the way to the edge... so there's a very strong "gravity effect" near the edges of the screen until you run the reconfiguration steps as posted above.

[Q] Touch Screen Responsiveness

Device: Nook Color rooted to 1.1
I had my Nook Color in the car today (40 degrees or so), pulled it out to show her what it looked like rooted. While standing in the driveway showing her different things, I found the touch screen was overly sensitive. As I was scrolling through different things (the app list, twitter, facebook), the slightest touch would select/open an item. It normally doesn't do this. It was incredibly frustrating and almost unusable. I pulled it out later and it seems to be behaving like it normally does.
Does temperature affect the NC screen? Where they any touch screen changes in 1.1? Is there a setting to calibrate the touch screen? I can't seem to find one. Any other suggestions?
I tried doing a search on the forum, but the search crashed.
Thanks.

horsemom said:
Is there a setting to calibrate the touch screen? I can't seem to find one.
Click to expand...
Click to collapse
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
I don't know if it's placebo or not, but I feel like this app improved my screen response.
http://forum.xda-developers.com/showthread.php?t=934500
As for the other question, I would expect the screen to be less responsive in cold weather, but I don't have anything to base that on.

Guessing what you experienced was due to condensation on the screen. Doesn't take much and can be 'invisible' to you but the screen is sensitive to 'stuff' on the screen and will become overly sensitive if there is anything on it, like moisture, skin oils, etc .. a screen protector may help but unless it continues that is probably the cause.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
What you experience is probably temperature related, but another thing to try is to increase the LCD screen density to around 190, 200, or a little more. For me, I get improved sensitivity, especially near the corners.

My daughter accidentally got a little water on the screen and it was a little erratic. I put it in a ziplock with a handful of rice for about 6 hours and it was like new.

I have owned 3 nook colors, the first one I owned freaked out when I used a damp cloth to wipe the screen. It exhibited some strange behavior and emitted some loud static from the speaker. It would not power down or anything... finally it just went back to normal, so I took it back to B&N and then went and bought one at walmart. I took it back because I thought I wanted the Viewsonic G Tablet. But after trying it I finally bought a Nook Color at Best Buy, bought a screen protector too so that I don't have a repeat of my first NC. The screens on these things are, I believe, rather sensitive and the cold or the moisture may have played a part in your unit's behavior.
migrax

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
Same here. My screen also seems very inaccurate.
Have you found a fix?
Sent from a NookColor using the xda app

I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).

tenderidol said:
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
Click to expand...
Click to collapse
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook

It's funny, actually... The cold makes your skin less detectable because of vasoconstriction in your fingers as a physiological response to the cold temperature, but a hint of moisture by means of condensation has the opposite effect.
For me, condensation is rarely a problem, but the decreased capillary blood flow effect is quite noticeable.
Sent from my Nexus S using XDA Premium App

One thing that's been mentioned before (and the B&N salesman told me while buying a screenprotector) is that if the screen has a lot of fingerprints, it'll make the nook act weird.
Try wiping the screen of fingerprints.

don_ernesto said:
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
Click to expand...
Click to collapse
Thanks for the reply. Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!

tenderidol said:
Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
Click to expand...
Click to collapse
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply

don_ernesto said:
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
Click to expand...
Click to collapse
Thanks again for the reply.
Yes, I'd love to take care of it ASAP, since I'm sick of trying to hit a small button on the screen and going somewhere else instead.
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!

tenderidol said:
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
Click to expand...
Click to collapse
go ahead! you won't loose any app or any data (not even your progress in Angry Birds)
Of course, before applying this changes i always make a backup. good to have a way back in case something goes wrong

Good test tool
I ran GoJimi's tool, and since then my screen has been flipping out. Typing anything is a good test...I enter one key like "z", and get 2 - "zm". Utterly maddening.
A good tool to see what's going on is "Mutitouch Test" from JerryW in the market.
When I press with one finger, I see a "phantom" 2nd point jumping around. Very quick way to see 1) how good tracking is and 2) if there's any random inintended multitouch action happening.

[Q] Does HBOOT 0.35.0017 fix or improve the touchscreen miscalibration issue?

Does upgrading the HBOOT help with the wonky touchscreen heat-related miscalibration issues that every Nexus owner knows about?
I raised this question on a different thread:
http://forum.xda-developers.com/showthread.php?t=903975&page=9
but wanted to throw this question out to a larger audience.
This week I finally got tired of having intermittent but definitive touchscreen miscalibrations, usually associated with charging and/or heavy usage. HTC shipped a swap for me to use.
The new one works pretty well, except the camera takes pinkish tinged images, so it unfortunately will be going back. However, I noticed that the HBOOT is the newer 0.35.0017 (though the date displayed by the bootloader screen is Jun 14, 2010).
So I upgraded the HBOOT on my original N1, and have been trying hard to reproduce the touchscreen craziness. So far I've been unable to do it.
It's difficult for me to make it happen on demand. I "stress tested" it essentially by doing the things that normally bring it on, GPS with charger, and graphics intensive games. But I'm getting really tired of beating angry birds again and again =P
So, if you're still experiencing touchscreen wonkiness that is fixed by turning on and off the screen, which HBOOT do you have?
There are of course many other potential mitigating factors I've thought about. Custom ROMS. Kernels. Touchscreen protector. Radio version.
Just for completeness, there are different part numbers on the two:
Original N1 part # 99hke002-00 F
Replacement N1 part # 99hke002-01
Who knows what the significance of that is.

No it doesn't.

Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?

You know, as strange as it sounds, since I upgraded to the 0.35 HBOOT about a month ago, I have had zero issue with the digitizer. Call it coincidence, but that is what's happening so far.

We will call it coincidence for now =)
A happy coincidence.

waylo said:
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
Click to expand...
Click to collapse
Not very often, in fact think it hadn't done it over the past week. I've been using the crap out of it customizing CM7 over this weekend and no hiccups.

our touch screen is always a hardware problem..

That's not the question. The question is if you're still having a lot of problems with your touch screen, which hboot do you have?

I was actually kinda wondering the same thing. I finally got around to putting on CM7 (build 39) on Friday (coming from CM 6.1). I right away had the impression that the screen was more responsive (the notification drop-down bar tipped me off) and I have not had a single episode of wonkiness with the screen since. CM 6.1 was a little weird for me and I had screen issues (especially the drop-down).
Oh well, even if it isn't the HBOOT, something has changed for the better for now

Another thing I learned recently is that on the native google navigation app, there seems to be a touchscreen dead zone directly vertical in the center of the screen (in landscape mode at least). It basically corresponds to the current street you're on if your navigation is active and your path is straight ahead.
So if you touch there and try to shift the screen around, you might mistakenly think the whole screen is awry. I think this is by design.
I'm not sure why it's there but it reliably is unresponsive to drags. So I'm not using that center area to gauge if my screens gone wonky.
Now if you hit the menu button, the buttons centrally do respond to taps.

Just had my first case of misregistering digitizer in a while. But instead of the whole bottom 1/3 of the screen going stupid it was just the bottom right corner, around the enter button/backspace if you have a portrait keyboard.
Oh well, it still works better than stock eclair!

So just as an update, the HBOOT definitely does not rid the digitizer issues plaguing everyone. It seems actually that my kernel had more of say in when/how often the issue surfaces.
I found that on Enom's Froyo ROM, problems arose more often with stock Enom than Pershoot or Wildmonks. However, each kernel has its own benefits.

Is anyone working on a fix for the appalling 8.9 touchscreen sensitivity?

I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.

jeremy89632 said:
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
Click to expand...
Click to collapse
i sent him a mail. here are the responses:
it seems unlikely:
- I don't have the device
- it uses different touch controller than 10.1
- kernel doesn't support configurable parameters for 8.9
Click to expand...
Click to collapse
I'm speaking about driver provided for controller used in 8.9, it has
no possibility to change configuration. And the firmware of the
controller is a binary blob with no documentation.
Click to expand...
Click to collapse
looks like we are unlucky

being very upset with this problem i started poking around the build.prop
it might be placebo but i feel that when this is added:
Code:
windowsmgr.max_events_per_sec=300
it gets a little more responsive. still not what i want it to be but better than before.

Try Touchscreen booster
It seems to have helped mine.

thanks. seems a little more responsive.
here is the apk if anybody else was wondering:
http://forum.xda-developers.com/showthread.php?t=1261237

My 8.9 LTE is super sensative, probbly the most I have seen on any android tab.
I can just barely graze my screen with rhe back of my fingernail and it even picks that up.
Compared to my roomates ASUS Transformer Prime, wo cant even use his fingernail unless he really jams it down.

iinteresting but im on the tegra version which aparently has completely different hardware

hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.

MatteAce said:
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
Click to expand...
Click to collapse
Try TouchScreen Booster?

the_hatrix said:
Try TouchScreen Booster?
Click to expand...
Click to collapse
that's been the first thing I did, but the improvements it brings are very light.

Does the tablet really have different hardware between the wifi and the LTE version? (at least regarding the screen digitizer)

Loccy said:
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Click to expand...
Click to collapse
Hmm, is it really a sensitivity issue? If I swipe first then wiggle like you mention, the screen will wiggle slightly. It sounds like there is a threshold to switch from holding the finger down motionless, to scrolling from left to right.
Perhaps a threshold setting (if available) is sufficient to overcome this?

I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.

Kasracer said:
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Click to expand...
Click to collapse
I have Samsung 3.2 OTA update and it really changes nothing.
Btw no answer yet from Samsung, and yes, the problem is just about some sort of accidental touch filter