While driving home I got an idea to remove the lag in Tomtom 7 on the Touch pro by using an optical trick. And I need your advice....
In tomtom you can choose an image as the pointer of your location on the map (by default blue pointer). Some posts in this forum stated that the real position is at the tip of the pointer, where this used to be in the 'center' of the pointer. Still some people have to deal with lag.
Now my idea: what if we change the default icon by a custom made icon of which for example the lower half is transparent, while the upper half is the default pointer. The resolution of the image that represents the icon would be a number of pixels higher (width stays the same) and it would be the questions whether Tomtom allows larger images to be read as icon.
But: assume it works, in your screen the blue pointer would move a but to the top of your screen, like as if it reduces your lag.
Probably there are other complications (like what wil happen during a turn, would it look like your position is outside the road....??), but it is just an idea.
My favorite idea I heard was to have a 5-10 meter pole (or whatever your lag is) mounted to the front of your car with your phone stuck to it and then have a pair of binoculars next to you so you can actually see the screen
But seriously, have you not noticed that when you stop driving the position reported is very close to where you actually are. With your suggestions this would change and IMO not be good.
I resolved my lag issues with my diamond (and I'm sure many others have as well) by using the latest versions of iGO8 and using it in 2D mode. I swear, I have no lag now what so ever. The same can't be said for in Tomtom but TTN7 is rubbish compared to iGO8 anyway IMHO .
GFXboost also apparently improves the visual performance of iGO8, so another point to consider .
Is there any speed-governor app for the Xoom that can be configured to lock the CPU to 1000MHz whenever the soft input area is active (or better yet, whenever Graffiti input is active), and/or a way to increase the digitizer sample rate?
Historically, Graffiti has been totally unusable on my Xoom. Literally, so low of a sample rate, and so many errors, that I just couldn't use it. I finally got around to unlocking and reflashing my Xoom to CM10 last night, and locking the CPU to 1000MHz makes it work a lot better... but the accuracy is still a cruel joke compared to even my creaky, old Hero overclocked to 711MHz.
It's pretty sad, actually. On the Hero, the digitizer seems to be reporting samples at least 4-16 times as often, and I can get nearly 100% accuracy without even trying. On the Xoom locked to max speed, it seems to do a tiny bit better than my S3 gets with stock, but the sample rate still appears to be absurdly low compared to what it was on the Hero, and feedback seems to lag the actual touch by at least 100-200ms. On the Hero, feedback was literally instant... stroke, and see the pixels turn white INSTANTLY under my fingertip. On the Xoom (locked to max), they start turning white a fraction of a second after I touch the screen, and I can see the last bit of the stroke render a fraction of a second after I lift my finger away. With the stock Xoom rom, it was more like, "draw the character, and see a jagged impression of it sputter into existence about a half-second later... maybe, MAYBE even getting recognized correctly about 70% of the time".
I'm guessing that either the Xoom's digitizer has a limited sample rate, or something in the kernel or driver is limiting the sample rate... but I'm still trying to find a straight answer somewhere about whether/how you can build a custom kernel without losing your ability to run paid Market apps. Or whether it's even necessary to go to that extreme, as opposed to something like a setting that tells Android to increase the sample rate, or not throttle the CPU when an input area is active, or maybe a way to let something like SetCPU identify "soft input area active" as a profile-triggering condition. I'm also pretty sure that the Xoom's kernel (if not recent versions of Android itself) try to treat the existence of a soft input area as an excuse to massively throttle the CPU, on the theory that it's just displaying a picture of a keyboard and waiting for a blunt press. HOWEVER, I'm SURE there HAS to be an equally-official way of defeating that behavior, if only because it would also screw up Android's ability to handle east Asian input methods.
Dear guys and gals,
Found a key for touch prediction that when edited showed a marked improvement in keyboard responsiveness and small item manipulation ie classic desktop, file explorer, etc.
The key is: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TouchPrediction
Edit key for latency from 8 to 2.
Edit sample time from 8 to 2
Restart
See attached for a edited registry key to inject. Tested on two surfaces with no ill effects.
edit: to answer a few questions: this increases performance on all touch aspects of the device
The most likely ill effect would be a decrease in battery life as the system must poll the touchscreen more often... just be aware. Otherwise, cool find.
Keyboard does seem faster... Does this also affect swiping? it seems like I can swipe in any way and get the full length of the page / app in one swipe?
Haven't noted in marked increase in battery consumption but I will monitor.
Could this improve the home key button, when my surface is on standby it takes about 6 taps to get the surface to wake up.
possibly, I have not tested the mod for that per say,
Dane Reynolds said:
Could this improve the home key button, when my surface is on standby it takes about 6 taps to get the surface to wake up.
Click to expand...
Click to collapse
I also have not noticed an increase in battery usage on my asus vivo tab. Not a surface, but rt.
What would decreasing the values to 1 due? I am assuming the lower the value, the better. Or did it not test well on Surface?
Originally I choose 2 to test the battery draw. However, now that I haven't seen any significant increase in battery usage the drop to 1 can be done.
Dadstar said:
What would decreasing the values to 1 due? I am assuming the lower the value, the better. Or did it not test well on Surface?
Click to expand...
Click to collapse
Is it that easy for all the values? In other words, can all of the registry values be set to 1 to improve performance? Or are all the values a certain number for a reason? Cuz if latency of 1 works better than the original 8, idk why Microsoft would put it at 8 in the first place. Sorry for all the questions. This stuff is interesting to me!
First off all any values are "safe values". Some screens might be of worse quality then others (different manufacturers of parts). Having that value setup to happy medium means all screens act the same. You lower the value you demand that screen reads the inputs faster and more often. Might not be a good idea on some devices.
Not only talking about surface. Remember win8 (especially pro) will go on many different devices.
Also if you set sampling and refresh to low it might start having ghost touches from minimum input that would normally not be visible (oversensitive).
Best to practice and find perfect for you and your device.
ruscik said:
First off all any values are "safe values". Some screens might be of worse quality then others (different manufacturers of parts). Having that value setup to happy medium means all screens act the same. You lower the value you demand that screen reads the inputs faster and more often. Might not be a good idea on some devices.
Not only talking about surface. Remember win8 (especially pro) will go on many different devices.
Also if you set sampling and refresh to low it might start having ghost touches from minimum input that would normally not be visible (oversensitive).
Best to practice and find perfect for you and your device.
Click to expand...
Click to collapse
How about the other regs that don't really have a highest/lowest rate? For example, Disable Hotmail is defaulted at 2. What would changing that to 1 do?
Dadstar said:
How about the other regs that don't really have a highest/lowest rate? For example, Disable Hotmail is defaulted at 2. What would changing that to 1 do?
Click to expand...
Click to collapse
No there is no general rule where lower value is better. Some of the values displayed are "face values" where 2 is 2 like refresh 2 times a second. Some times 2 and 1 have a meaning off or on (like your hotmail). Remember PC reads numbers. Even more sometimes numbers, text or mix you see like 8 or 4 are actually representations of some kind of code for example hex or binary.
If you do not know what the number represents then changing it is a guess and nothing more. Just have a backup copy as fiddling in registry with drivers can have funny side effects. I did make my hd7 think i am touching it everywhere all the time so it hang seconds after boot
Are we sure this does anything at all? In order to test if the differences were psychological, I set the number to a ridiculously high value and it didn't seem to behave any differently.
Yup I found noticeable differences in fine touch control including in the registry,window control, etc.
Wupideedoo said:
Are we sure this does anything at all? In order to test if the differences were psychological, I set the number to a ridiculously high value and it didn't seem to behave any differently.
Click to expand...
Click to collapse
Thanks a lot!
Is 2 a good value in the case of the surface PRO 1 ?
"touch prediction" did prediction, not pooling!
"Latency" = how much milisecond to look ahead
"SampleTime" = the period in milisecond to average your finger's motion
The effect is thus:
Larger "latency" make the pointer overshoot, smaller "latency" make the pointer lag behind (1 - 100 milisecond depending on your system performance).
There's no penalty on your tablet's battery or digitizer's life for turning TouchPrediction off, and you don't need to restart to see the effect. (try finger drawing in MS Paint to see effect)
If your Surface missed touch, then try to cool the back of your tablet. It might be thermal throttling.
hello! my android 7 device may be called a smartphone but it is incredibly dumb when it comes to interpreting the input that comes to it from the screen when I touch it! I am just wondering if there are any apps or developer projects that seek to address this? no doubt it may be partly a hardware issue, maybe some devices have better sensitivity or let you tweak more settings than just the mysterious 'pointer speed'? but beyond this, are there any attempts to augment whatever module translates physical screen data into logical clicks, drags and so on? for instance, through active or passive training to distinguish drags from clicks, or by examining the screen pixels near where I click so a click in the vicinity of a text label is considered as an attempt to press the label, rather than assuming that I am pressing on an empty area of the background for no apparent reason? thanks in advance for any ideas! — Joseph
Hello! I have a European model Motorola Edge 20. The phone is great, and I love it, however the sensitivity of the display seems to be poorly calibrated (e.g. it sometimes doesn't respond to taps, swipes etc. Not as bad as I've seen some people have it but enough to annoy me). I don't have an issue in games where I turn on the "Touch sensitivity" mode on, which I presume activated the 576Hz touch sampling the phone has, however it doesn't seem to be turned on in normal use.
I have looked online for fixes since the device is rooted, however most of them seem to be old build.prop commands for Samsung or Huawei phones and I'm not sure if they'd work on an android 11 device.
Any help or suggestions would be very appreciated.