yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] TechNoir:
Any links to the touchscreen performance test you mention?

As for the "deadzone" for touch input, CyanogenMod7 for the SGS has this aswell. Furthermore, it also has a "feature" where if you move your finger slower than a certain speed across the screen, homescreens/browser pages etc will just ignore the touch input. So if you want to minimally correct the framing of a webpage, if maybe the text is just cut off on the side, you need to quickly swipe a very short swipe to get any movement on the screen. Trying to slowly change framing is not possible.

Hardware is fine though, multitouch tests has no filtering like deadzones or speed thresholds.
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
I have this problem to, Its definitely software I think.

I wonder if its easy to mod to get rid of this deadzone/minimum threshold for scrolling. Anyone able to take a look. Its quite annoying in some things and my old android phone didnt do this.
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
Angry birds doesn't bypass the problem. It's quite hard to see underneath your finger but the problem is definitely there in "Angry Birds Rio".

Scrolling in some views don't show the problem so badly, presumably because they use the relative movement of each move event, rather than the absolute distance from the down event.
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Yeah problem is still there in angry birds my mistake.

Its quite annoying in nova hd when you want to move the crosshair a tiny amount. You can't because of this problem :(

Anyone know what file in the source could be edited to maybe stop this ?
[Galaxy S II Q&A, Help & Troubleshooting] RogerPodacter:
my hunch is this source is not available, and somewhere in samsung's closed framework or similar.

i know on cyanogen rom, you can go look at the source code for ADW launcher, and you can locate the touch input source code. and you can find all the algorithms like dX, dY, that are used to register swipes, motion, scrolls, etc. its all pretty complicated and impressive code actually.

i'm sure samsung has equivalent code somewhere.
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
So if we got rid of touchwiz and used ADW launcher would the problem still be there?
[Galaxy S II Q&A, Help & Troubleshooting] drm111:
Good question. I'm curious.
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Still same problem with adw launcher
[Galaxy S II Q&A, Help & Troubleshooting] pulser_g2:
This looks more like a kernel thing to me in the touchscreen driver...
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Are we able to edit/mod/patch the touchscreen driver in the kernel or is this only something samsung can do ?
[Galaxy S II Q&A, Help & Troubleshooting] pulser_g2:
We have the sources. I'm checking out the frameworks first though in case it's obvious.
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Hopefully you can find something thats to do with this :)
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
pulser_g2 did you find anything in the framework about this ? :)
[Galaxy S II Q&A, Help & Troubleshooting] TML1504:
another way to show the treshold, and that it is intentionally:

enter the following two service menus:

*#*#2663#*#* (touch screen version)

shows the set treshold (on my sgs2 it is "70")

BEWARE: DO NOT PRESS THE FW UPDATE BUTTONS!!!

*#*#2664#*#*

shows also that the drawing starts after some specific treshold!

hope somebody will come up with a solution soon :)
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Thats good to now. Hopefully someone finds a way we can reduce this number :)
[Galaxy S II Q&A, Help & Troubleshooting] MaBlo:
Hmm my TSP threshold is 40.. what does that number mean anyway? :p
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Yeah just checked mine now. Says tsp threshold 40.
[Galaxy S II Q&A, Help & Troubleshooting] guyman20:
Solution?

Anybody came up with a solution to this problem?
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
I'm checking the source. According the the kernel config the touchscreen is:

CONFIG_TOUCHSCREEN_QT602240=y

Also useful:

CONFIG_GYRO_K3G=y
CONFIG_OPTICAL_CM3663=y

The QT602240 leads to drivers/input/touchscreen/mxt224_u1.c

Which contains "static int threshold = 70;" so I guess you just need to change that, rebuild the kernel, add it to the boot image and flash it. Simple! /s.

There's also some code which sets it to 30 or 40 in different conditions:

if (ta_status) {
threshold = 70;
calcfg = 112;
noise_threshold = 40;
} else {
if (boot_or_resume==1)
threshold = 70;
else
threshold = 40;
calcfg = 80;
noise_threshold = 30;
}

It gets referred to as noise suppression in lots of places. I still can't see why they'd add it though - the movement after the threshold seems very noise free.

Anyway I found this function which maybe lets you change the threshold:

static ssize_t key_threshold_store(struct device *dev, struct device_attribute *attr,
const char *buf, size_t size)
{
/*TO DO IT*/
unsigned int object_register = 7;
u8 value;
u8 val;
int ret;
u16 address = 0;
u16 size_one;
if (sscanf(buf, "%d", &threshold) == 1) {
printk(KERN_ERR "[TSP] threshold value %d\n", threshold);
ret = get_object_info(copy_data, TOUCH_MULTITOUCHSCREEN_T9, &size_one, &address);
size_one = 1;
value = (u8)threshold;
write_mem(copy_data, address+(u16)object_register, size_one, &value);
read_mem(copy_data, address+(u16)object_register, (u8)size_one, &val);

printk(KERN_ERR "[TSP] T%d Byte%d is %d\n", TOUCH_MULTITOUCHSCREEN_T9, object_register, val);
}

return size;
}

Also there's this:

static DEVICE_ATTR(tsp_threshold, S_IRUGO | S_IWUSR | S_IWGRP, key_threshold_show, key_threshold_store); /* touch threshold return, store */

Aha! And after more searching than it should have taken (why don't they use busybox damnit?!) I found this file:

/sys/devices/virtual/sec/sec_touchscreen/tsp_threshold

Sooooo.... if someone has root, and is willing to risk it (your risk etc etc), try running this in adb shell or connectbot:

su
echo "0" > /sys/devices/virtual/sec/sec_touchscreen/tsp_threshold

Let us know if it works!

Cheers
[Galaxy S II Q&A, Help & Troubleshooting] RogerPodacter:
very nice find! you can also just use root explorer, navigate to that folder, and edit the file manually, enter "0", and save the file. these are device attribute files (virtual files in linux used to interact with low level hardware).

curious to hear results.
[Galaxy S II Q&A, Help & Troubleshooting] guyman20:
hmm

Any simple solution for noobs?
[Galaxy S II Q&A, Help & Troubleshooting] Pfeffernuss:
Only checked this one line. Does not work. It renders the whole touchscreen useless. You can touch the screen where you want, nothing gets registered. Only the hardware keys (back, home, etc.) function afterwards. So not even possible to press "reboot", had to resort to long-press-power-off :D

Note: also tried a value of "3" but that makes the phone go completely berzerk. Apps open by themselves, screens wipe, apps FC, etc. So that value ain't "it" as well... :cool:

After a reboot all is well so not a major problem ;)
[Galaxy S II Q&A, Help & Troubleshooting] dinan:
Maybe we should try some values that are above zero but below the current threshold. I'm sure most other phones have to have SOME sort of threshold.
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
Hmm damn. It could be that 0 doesn't work but >0 does... Or maybe that mechanism doesn't work at all.

If you're feeling bored you could try '70' instead of 0 and see if the touch-screen still works. Then maybe go down in 10's: 60, 50, 40 etc.

Another possibility is we have to reset the touchscreen by fiddling with the files in sec_touchscreen/power.

I'll have a proper read through the code in a few hours. How do you do the long-press power off? Just hold down the power button and it turns off?

Also I just noticed /sys/devices/virtual/sec/qt602240_noise_test which contains some interesting stuff, including set_threshould [sic].
[Galaxy S II Q&A, Help & Troubleshooting] Pfeffernuss:
Ah ok... Just edited my previous post that I also tried "3" but that failed miserably. Will try 50 now.

Yes, just keep pressing it until phone switches off. Reboot and all is well.
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
Hmm that leads me to suspect that this threshold isn't actually the move threshold we are looking for, but is a sensitivity threshold.

I hope it isn't set in the (closed source) firmware... Man I wish the original developers left their contact details in the source code.
[Galaxy S II Q&A, Help & Troubleshooting] Pfeffernuss:
You beat me again... Just tried values 50, 30, 30 and there was no difference whatsoever. Then tried 7 and suddenly it was clear what the value does change... Like you said, it's the sensitivity (distance) threshold.

With value 7 I was able to type on the keyboard without even remotely touching the screen. A distance of about 5 mm's already triggered a key-press.

So no, this is not what we're looking for. Interesting and fun nonetheless though :D
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Hopefully you find a way to do it :).

What if you change the value in : drivers/input/touchscreen/mxt224_u1.c and change :

"static int threshold = 70;" to another value
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
That will have the same effect. It's the same thing.
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
So are we stuck here and not able to change this?
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
Well I read through the code. Didn't understand all of it, and to be honest it is full of typos, has few comments and I've never done any kernel development. The only possible thing I found is that it looks like touch is handled differently on the Korean model to the European one, so it would be interesting to know if that model exhibits the same problem. If not then we can probably fix this by compiling a new kernel. Otherwise, we're basically out of luck afaics.

So, any Koreans here?
[Galaxy S II Q&A, Help & Troubleshooting] bcam117:
Any progress on this?
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
No, and it makes playing Baldur's Gate tricky. :-/
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
I'm afraid I managed to build a kernel with DRIVER_FILTER disabled, but it made no difference. I guess this is a firmware thing.

I looked at the firmware but it just looks like random bytes to me. I have no idea how to disassemble it, or even what kind of code it is (I guess atmel? given the chip is an atmel chip?)
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
I actually got a response from the developers! Unfortunately it is not a good one. They don't have the firmware source, and they think this bug is a feature:
[Galaxy S II Q&A, Help & Troubleshooting] XpLoDWilD:
Maybe we could ask them to reduce this "move" threshold as it's a bit large compared to other devices, and prevent smooth scrolling/browsing
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
I sent them a reply saying that other phones don't have the threshold and there are no problems, and it also messes up apps that require small moves.

But if they don't have the firmware source I doubt they'll change much...
[Galaxy S II Q&A, Help & Troubleshooting] qwerty warrior:
reminds me of the Iphone's bugs .... i mean features
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
Any devs got any updates? Know a way to reduce/stop this?
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
?????????????????
[Galaxy S II Q&A, Help & Troubleshooting] xiga:
This is the only thing that actually bothers me about my beloved SII. I don't notice it while browsing or moving from screen to screen, but try playing a game and it becomes apparent immediately. I tried playing 'Pool Break Pro', and sweet Jesus how annoying is it trying to make the tiny adjustments needed to line up a shot properly! I really hope this is something that can be fixed, and we're not stuck with this forever.

ps - Separate issue: I'm not a big mobile gamer, but I also tried playing Pac-Man Championship and my God the number of times he wouldn't go in the direction i wanted him to go in. I was getting REALLY frustrated playing the game, and that's from someone who finished all 360 levels in the iphone version (not the same game). After this, i booted up my old 3gs and after 4 weeks of non-use, i could immediately tell the screen is more sensitive & responsive compated to the SII.
[Galaxy S II Q&A, Help & Troubleshooting] mariosergio2112:
This is very annoying. Im getting mad with samsung. If they dont fix this, my next phone will be an htc.
[Galaxy S II Q&A, Help & Troubleshooting] zmirburger:
this problem didnt annoy me at first,

but using tweetdeck a motion is needed to make the menu popup:

slight swipe to the left/right > hold (If u swipe too much it will change tabs, needs to be a small swipe)

with this problem this motion cannot be done!! had no issues with my old sgs1

not very happy with this but i could live with it if there is really no fix. but if there really is a fix it would be awesome
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
I've had no further replies from Samsung. I will send another email soon. I may also try to contact Atmel, but I doubt that will go anywhere.
[Galaxy S II Q&A, Help & Troubleshooting] vitalij:
Hi, I actually have found the way to lower or remove this threshold, and even created an app for this. Obviously you will need root for this. App allows to both test touchscreen and manually set and apply threshold - try setting it to 0, then press apply. The only limitation is, that it will be restored to default after screen will turn off.
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
Fantastic! How does it work?

Edit: I strings'd it, something like this?

echo "9 11 ??A" > /sys/devices/platform/s3c2410-i2c.3/i2c-3/3-004a/object_write

How on earth did you work that out?

Edit 2: Unfortunately it doesn't seem quite right. While the initial move threshold is removed, subsequent movement becomes very jittery.
[Galaxy S II Q&A, Help & Troubleshooting] vitalij:
By reading kernel sources ofc. Actually for me setting the threshold to 0 works perfectly without any consequences - and do just this: removes that initial threshold. So maybe you have changed anything else? or you screen is calibrated somehow differently. It would be nice to hear other people experience on this.

Edit: BTW I'm on stock firmware KE7
[Galaxy S II Q&A, Help & Troubleshooting] Timmmmmm:
Ah ok. Where is bit where the kernel driver sets the threshold...? I can't find it. :-/

Hmm weird. It's a subtle effect, maybe I will make a video later. I could do with an app that plots x & y vs time, then it would be obvious.

I'm using stock KE2. I expect the mxt224e firmware is the same though..
[Galaxy S II Q&A, Help & Troubleshooting] gusoldier:
Great fix! It even fixed the choppyness when you touch and hold the screen very light.

Anyway to make this permanent?
[Galaxy S II Q&A, Help & Troubleshooting] kramerty88:
Many thanks bro! This really makes my day, since it was one of the few things that annoyed me...
[Galaxy S II Q&A, Help & Troubleshooting] MaBlo:
Thanks I've been waiting for a fix. You should make a thread in the dev section though, it's easily missed here.
[Galaxy S II Q&A, Help & Troubleshooting] zmirburger:
Nice it works!! Should get a way to make it permanent and incorporate it into all future custom roms! And yeah should make a new thread about this app. Link us when u do, great job!
[Galaxy S II Q&A, Help & Troubleshooting] angelomaldito:
...........
[Galaxy S II Q&A, Help & Troubleshooting] angelomaldito:
Thanks for the tip. The *#*#2663#*#* test for me shows a TSP threshold = 40. Actually I happy with my touchscreen settings, and I think there's a reason for that to be the way it is. Nevertheless, I don't understand why the discrepancy between the threshold values of my SGS2 and yours.
[Galaxy S II Q&A, Help & Troubleshooting] vitalij:
Hmm interesting actually every time it shows different value - just try it many times and you'll see.
[Galaxy S II Q&A, Help & Troubleshooting] vitalij:
Yeah I'll make a nice app which will let keep the settings at all times and also let adjust other touchscreen driver settings :) When I'll finish I'll create a thread - in a day or two.
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
vitalij that sounds great. So it is possible to keep the change permanent ?

How would it work? Would something need to be running in the background constantly and always writing a value to this location when the screen wakes up. Or is there a way to make the change and then nothing needs to run again and the value stays?

Thanks so much for this :)
[Galaxy S II Q&A, Help & Troubleshooting] EleCtrOx666:
I always get "TSP treshold = 40".

The values below, however, change everytime.
[Galaxy S II Q&A, Help & Troubleshooting] angelomaldito:
It seems that my threshold doesn't change, as I repeated the test a couple of times and it's always = 40. I'll try again later just to confirm that.

[edit] Confirmed, always TSP = 40 all the time
[Galaxy S II Q&A, Help & Troubleshooting] zmirburger:
My treshold is always 70 :o
[Galaxy S II Q&A, Help & Troubleshooting] dinan:
Just tried this app out and while it does seem to work, it might have introduced another problem that I'm not sure was there before or not.

If you use any multitouch test app and try using 2 fingers and crossing an axis of the other.. it seems like the screen loses one of the fingers. Anyone else seeing this? It was similar to the Nexus 1 before and I thought this screen didn't suffer from this problem but I never checked.

Edit: BTW this issue only happens after you use this app. If you turn off the screen and turn it back on, the issue isn't there anymore. So for stock phones without this app, there is no problem with the touchscreen and multitouch points crossing each other's axes but after setting a different move threshold with this app, other problems seem to pop up.
[Galaxy S II Q&A, Help & Troubleshooting] soyef:
Try other touch testing apps
[Galaxy S II Q&A, Help & Troubleshooting] zmirburger:
Hmmm I don't seem to have that problem after changing the treshold. Same before and after. I used yaamt to test this
[Galaxy S II Q&A, Help & Troubleshooting] soyef:
Yeah multi touch tester has a bug

Used to happen to me before using the app

yamtt always worked fine though
[Galaxy S II Q&A, Help & Troubleshooting] sorrowuk:
There is no side effects when changing the threshold. It just works the same as before except there is no deadzone/move threshold anymore. For me anyway.

Just hope it can be made permanent. vitalij hows it going with that?
[Galaxy S II Q&A, Help & Troubleshooting] vitalij:
done: link
[Galaxy S II Q&A, Help & Troubleshooting] LocutusEstBorg:
Is there any way to make the value stick after the screen is turned off?
[General Questions and Answers] ianshmian:
The signal dies on me everytime I lock the screen, it also happens to the Froyo stock build. I have a Rhod400. I used kernel 1253 so that the service bug wont happen but now everytime I charge my phone it just stops totally.
[Galaxy S I9000 General] Mossat:
I updated to gingerbread xwjvh and no problems there. I installed the modem file for my signal no problem there.

So i decided to root for the first time using CF-Root-XW_XEE_JVB-v3.1-cwm3rfs

and now it's constantly rebooting non stop...please help very urgent
[Galaxy S I9000 General] devonblue4u:
Did you do a factory reset and clear cache yet?
[Galaxy S I9000 General] Mossat:
I think i fixed it...not sure if i did it right but all i did is put the phone back in download and used the recently released cf root for jvh....and it seemed to have calmed down...what i don't understand is what is the difference between the kernel and rom??
[Galaxy S I9000 General] devonblue4u:
When I flashed JVB, I got a few FC's as I forgot to wipe data. Afterwards, no probs at all.
[Dell Streak 7] tech5:
I have figured out it is the ext partition of the internal card is been switched to read only

Unformatable and unaccessable from adb

If we can get this to be writable again it should help....but my adb know how sux.....but in learning
[Dell Streak 7] tech5:
Ok....well I contacted someone an they said that the internal SD card could be replaced cause it was a micro SD........2 hours later its been stripped apart no micro SD found and reasymbled .....its a sandisk 16 gig nand and not replaceable.......good thing for full insurance........now to decide what kind of horable death it shall receive before I cough up the 150 deductable ........I'm thinking chuck it out the window while driving down the interstate ......then throw it in the dishwasher for awhile ........I'm open for suggestion
[Dell Streak 7] killahbeatz:
put it back together and call dell to get it repaired for free or replaced
[Dell Streak 7] luchoster:
yup! that's exactly what I'm doing, sending it tomorrow to freaking Mexico to be repaired!

weird how the DS7 repair "department" is in Mexico! oh well they said that if they can't repair it, they'll send me a new one, No charges!
[Desire HD General] sathyaac:
Guys -

i am newbie in these rooting stuffs, i tried to root my DHD, but now stuck in the very first step... :(

I installed VISIOnary+ in DHD and set USB debuggin ON.

checked "set system r/w after root" and selected temproot now.

it says rooting your device and after 2min, only black screen..nothing happens.

I waited for 10min, but the same black screen.

So, rebooted and everything was normal(as a un-rooted device).

any help what wrong i did or how to rectify this problem.

Thanks

Satya
[Desire HD General] comio:
Hi,

you need to downgrade to 1.32 before to gain root.

ciao

luigi
[Desire HD General] vassilyk:
Hi!

Read this tutorial, it explains everything you need to permanently root your DHD

How To Permanently Root HTC Desire HD [Complete Guide]

addictivetips.com/mobile/how-to-root-telus-htc-desire-hd

That's the one I've used and it worked like a charm.
[Desire HD General] sathyaac:
thx guys..

i have successfully rooted and Eng S-off.

Now i want to flash the custom rom, should i need to flash the radio also seperately?

Do u have any procedure to flash the customer rom.

-Satya
[Desire HD General] Mr_JMM:
Yes. You will need Radio S-OFF.

Place on SD Card and use recovery or ROM Manager to install ROM.

Wipe data (factory wipe) before each ROM.
[Desire HD General] sathyaac:
I have flashed the custom Rom, but the volume seems to be muted. The other person in the call s not able to hear me. Neither does the voice recorder picks up any sound. S there any setting to turn on?
[Eee Pad Transformer Themes and Apps] DoManOfFuture:
MOD EDIT: No warez allowed - this also includes linking to warez websites
[Eee Pad Transformer Themes and Apps] stuntdouble:
You're not allowed to post warez here btw.
[Eee Pad Transformer Themes and Apps] DoManOfFuture:
Woops, and now fixed.
[Eee Pad Transformer Themes and Apps] the_scotsman:
Forum Rule #6
[Vibrant General] Djapatos:
so as many of us here i had the gps problem, and i started to not care anymore. The other day after i flashed Trigger 3.2, i also flashed some useful apps like SGS tool, spare parts etc. As i was going over those apps, i went to SGS tools, and noticed GPS fix all the way at the bottom. I decided to give it a try but didnt think it would work. I clicked and then select north-america.... and apply.

And surprisingly my GPS has been working perfectly fine since then.

So those of you who still have gps problem, try that

Hope this help;)
[Vibrant General] mugenfiji0327:
This has been posted before, it works for some people and it doesn't for others. Just like every other GPS fix out there. Not trying to be rude and I'm sure everyone appreciates you trying to help, but duplicate threads just create clutter. Once again I am not trying to be rude so please do not take it that way.
[Vibrant General] Emama:
flashing the S.gps is the easiest way as I know