Database Info

Slowness causing usability hell?

Hi,
Having owned a Qtek 2020/8080 and a 9090, I thought I'd give a windows mobile handset a fourth try by buying the HTC touch pro.
These are my experiences so far:
- the first 2 days I had a hard time not accidentally hang up during phonecalls
- Slow responses lead to usability hell - when a tap on a button does not seem to register, a second tap triggers a second action.
- GPS coordinates do not seem to be attached to pictures' exifdata, while it is enabled using Kaisertweak.
With the previous phone I had (Motorola RZR) I could start a new phonecall within 2 seconds. With my htc touch pro it takes 2 seconds to get to the contacts screen.
My second choice would be an iPhone. Usabilitywise that might have been a good idea, but I really require a hardware keyboard like the htc touch pro has.
Are there any speed-specific tweaks available that could speed up the userinterface? Are there themes that consume less cpu/mem?
(I do love this device because of the amount of features it packs. I'm in some kind of love-hate relationship with my phone, currently ;-)

pitr2 said:
Hi,
Having owned a Qtek 2020/8080 and a 9090, I thought I'd give a windows mobile handset a fourth try by buying the HTC touch pro.
These are my experiences so far:
- the first 2 days I had a hard time not accidentally hang up during phonecalls
- Slow responses lead to usability hell - when a tap on a button does not seem to register, a second tap triggers a second action.
- GPS coordinates do not seem to be attached to pictures' exifdata, while it is enabled using Kaisertweak.
With the previous phone I had (Motorola RZR) I could start a new phonecall within 2 seconds. With my htc touch pro it takes 2 seconds to get to the contacts screen.
My second choice would be an iPhone. Usabilitywise that might have been a good idea, but I really require a hardware keyboard like the htc touch pro has.
Are there any speed-specific tweaks available that could speed up the userinterface? Are there themes that consume less cpu/mem?
(I do love this device because of the amount of features it packs. I'm in some kind of love-hate relationship with my phone, currently ;-)
Click to expand...
Click to collapse
No slowness problems here - but I did make use of the speed tweaks in the 'Raphael Tweaks' thread from the off, so I can only advise doing the same.

dgpurvis said:
No slowness problems here - but I did make use of the speed tweaks in the 'Raphael Tweaks' thread from the off, so I can only advise doing the same.
Click to expand...
Click to collapse
Same here, tweaks do make a difference.

Hrm,
no problems here ROM info in sig and zero tweaks applied.

Once you apply the tweaks, have turned it on and gone through the various touch flo pages once (seemingly to get things cached) then the interface is fast.

kempas said:
Once you apply the tweaks, have turned it on and gone through the various touch flo pages once (seemingly to get things cached) then the interface is fast.
Click to expand...
Click to collapse
I have removed the touchflo application from the today screen, as that was giving me the most headaches. Touching the screen didn't always register, but setting the sensitivity higher helped. I'll give that a try after I have applied the speed tweaks.
Thanks for the replies.

I found that just putting the stylus on the screen doesnt make the device react, but once a tiny bit of pressure is used it reacts flawlessly.

scarecrow2012 said:
I found that just putting the stylus on the screen doesnt make the device react, but once a tiny bit of pressure is used it reacts flawlessly.
Click to expand...
Click to collapse
It's a resistive touch screen, that's how they work. They require at least a modicum of pressure to register a touch/press.

Syphon Filter said:
It's a resistive touch screen, that's how they work. They require at least a modicum of pressure to register a touch/press.
Click to expand...
Click to collapse
Some have regretted that the Touch Pro doesn't have a capacitive screen because of this, but I've noted they have the opposite problem, in that screen presses can register too easily. At least with a resistive screen it is possible to adjust the required pressure.

dgpurvis said:
Some have regretted that the Touch Pro doesn't have a capacitive screen because of this, but I've noted they have the opposite problem, in that screen presses can register too easily. At least with a resistive screen it is possible to adjust the required pressure.
Click to expand...
Click to collapse
One would assume the same applies for capacitive touch screens too.
Capacitive screens work on measuring the distortion of magnetic fields, the distortion threshold before a "touch" is registered could be adjusted.

Syphon Filter said:
One would assume the same applies for capacitive touch screens too.
Capacitive screens work on measuring the distortion of magnetic fields, the distortion threshold before a "touch" is registered could be adjusted.
Click to expand...
Click to collapse
I'm sure that's the case. I was commenting on what can be done with a resistive screen rather than comparing unfavourably with a capacitive screen.

No speed issues here, even without tweaks.
I can agree that screen sensitivity is too low even if set up to high but I taking my time...: )
Regards
B.

touch scrolling setting? (in registry)

Greetings ppl
A while ago I was searching for a way to make finger scrolling in start/programs a bit faster. I found a small registry tweak somewhere (maybe here), but when I entered it nothing happened.
Well sort of. I now see that scrolling in programs folder is normal, however scrolling in other areas, like sms inbox and add/remove programs list is superfast, and in no way useable.
I know, I know, fail.
Problem is, I don't remember the setting which I changed so I can get scrolling speed back to normal (double fail)... any ideas?

sorry to be a pain in the back cover, but any ideas?

Well, turns out that setting both TF3D sensitivity and TF3D finger pressure to Intermediate or High (DiamonTweak 14.1/14.2) caused everything else to scroll at twice the speed!
Setting sensitivity to intermediate and finger pressure to default turned everything back to normal! Weird thing is, I tested those settings on my HD as well, and they didn't seem to have any effect on other apps!

Touch Capacitive Panel (bottom pad)

Hello to all, am going to ask if anybody of you have a problem in TPs Touch Capacitive Pad? I used this app
Nav Debug Tool by HTC
http://forum.xda-developers.com/showthread.php?p=2511016
To check out this multi touch stuff in my TP (though I know before that it has a multi touch feature, I just want to check if it's working properly) but it seems that the pad has a problem. The problem was sometimes, it can register my touch and most of the time, not.. sometimes it can register the multi touch, and most of the time, not .. even the nav wheel has a problem which doesn't register the rotation most of the time. Is this a common problem in TPs or even Diamond??
I even use the signed os WM6.1 but still has a problem.. so I wonder if any of you guys having the same..
thanks!

It's been happening to me for about a year already as well. Seems like it's just defective. It resets thought after sleeping the phone and waking it. I'm not sure if it was because I used to use Sensor scroll or it's a little scratched up.

I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?

R^7Z said:
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
Click to expand...
Click to collapse
that made sense but why would HTC permit a buggy front pad???

You know, it seems many phone brands/cooperations come under fire due to lack of something or another; maybe proof of concept? Perhaps the debug tool is to blame? Or even the sensor degradation over time? One can only speculate so far before it becomes a volatile thought... Again, I point out the idea being good, conceptually. So, I don't know where that exactly puts us as being end users? Then again, I've never really had a decent experience with phones, much less with newer phones; my thoughts and expectations may be slightly on the negative/lesser side of things because of this.

I have the same issue. I used to use GScroll to flip pages in e-books, but finally it got so buggy I had to dump it (other GScroll features were almost impossible to use). I've used NavPad DBug. What I do find is that running the compact heaps command of SK Tools will temporarily fix things, at least most of the time. When I have NavPad DBug running, if it's logging compact heaps will clear out the traces. Somehow or other, it cleans things out when the nav pad gets confused or overloaded with inputs. But even compact heaps doesn't work all the time.
It would be sweet if the capacitative area really worked, but unfortunately it appears to get worn out about the time that you figure out all the things you can do with it. Lol.
Edit: I wonder if the device has problems distinguishing a single touch of your finger vs. several touches. That could really screw up the function of the device.

[Nook HD+] Touchscreen sensitivity experimentation (updated GUI app on 07/13)

Thanks to some testing by @alal690 based on my instructions in the post on how to play with touchscreen sensitivity we have some suggested reduced sensitivity values.
I spent entire day figuring how to do more things in android apps, and here's my next terrible UI attempt: NookTouchscreenSensitivityAdjuster-4.apk (backup link).
It's recommended that you run it with 07/11 cm10.1 release, but it will work with older releases too, just all settings (all but touch sensitivity on 07/06) would reset on screen off.
This minimalistic tool would allow you to change various touchscreen parameters in GUI, so not need to play with adb.
Right now this tool just lets you to play with values, the new values persist until the screen turns off (and the touchscreen resets restoring to default values).
The "save" button only saves the sensitivity and focus settings at this time, and the values persists across reboots (important to grant it root access the first time you run it!), everything else is not saved anywhere (since I am not sure there's any value in that and only included the other settings so you can experiment with them and perhaps get back to me with your awesome finds).
save button only works with 07/06 release, in previous releases save button does not persist anything.
the "reset" button resets values to the "old" values in the touchscreen, meaning pre-sensitivity change (so to 0x11, instead of the new 0x16).
Old post:
Anyway, here's a test zip that you can flash to try the new value. I encourage everybody to try it both if you do and do not feel like you have a touchscreen sensitivity issue.
If there are no downsides (so far I see none on my end), we might make this one to be a standard new default.
touchscreen-test.zip - this is for Nook HD+ (noop on the Nook HD). (Note, this is now included into 6/30 build for ovation)
Do not flash into stock, it'll break it.
I know the raw TS settings is a bit intimidating, so I plan to make an app for that, though that's a bit more effort than what I have time for ATM, so we'll make do with just this topical treatment.

will this work with carbonrom also? i like to switch between them.

What about those of us who felt it wasn't sensitive enough? Is there some sort of weird effect where its so over-sensitive that it feels less sensitive?

Apk07 said:
What about those of us who felt it wasn't sensitive enough? Is there some sort of weird effect where its so over-sensitive that it feels less sensitive?
Click to expand...
Click to collapse
Try it and tell me what you find out.
Feel free to play with other register values as per that other post referenced if you can. No two devices are totally the same. So we'll need a significant amount of testing by all interested parties to come to some middle groumd
Either that, or an app where people would be able to setup volume, touchscreen and other settings for themselves, but we'd still need to have sensible defaults.

bckrupps said:
will this work with carbonrom also? i like to switch between them.
Click to expand...
Click to collapse
It probably will work there too, but I did not test it on anything but my setup.

verygreen said:
It probably will work there too, but I did not test it on anything but my setup.
Click to expand...
Click to collapse
i tried it on both. What a difference already. especially on stock browser. sometimes i wanted to smash the thing lol. you are one hell of a dev. scrolling takes a bit more work but clicking links is so much better now. sometimes i would click a link four or 5 times lol

verygreen said:
Thanks to some testing by @alal690 based on my instructions in the post on how to play with touchscreen sensitivity we have some suggested reduced sensitivity values.
Anyway, here's a test zip that you can flash to try the new value. I encourage everybody to try it both if you do and do not feel like you have a touchscreen sensitivity issue.
Click to expand...
Click to collapse
Can I just flash this zip from CWM... or do I need to do any of the other steps mentioned in the post on playing with touchscreen?

dbrickg said:
Can I just flash this zip from CWM... or do I need to do any of the other steps mentioned in the post on playing with touchscreen?
Click to expand...
Click to collapse
You just flash this one from cwm and you are good to go for just this particular setting change.

verygreen said:
You just flash this one from cwm and you are good to go for just this particular setting change.
Click to expand...
Click to collapse
Thanks. That's what I thought. So I went ahead and did it while I was waiting for your response. So far it seems just fine. I guess I don't notice any great deal of difference. But I'm not sure what the symptoms were that you were trying to cure. I can't figure out how to read any of the context around the link to the post you mention in the OP

dbrickg said:
Thanks. That's what I thought. So I went ahead and did it while I was waiting for your response. So far it seems just fine. I guess I don't notice any great deal of difference. But I'm not sure what the symptoms were that you were trying to cure. I can't figure out how to read any of the context around the link to the post you mention in the OP
Click to expand...
Click to collapse
Basically the problem is: there are multiple complaints about people having too sensitive/too insensitive touchscreens. I don't think I am seeing anything like that, but there is more than one report so perhaps different people have different tolerances and different hardware has it's quirks.
The goal here is to arrive at a different set of defaults that would improve the situation for people that feel there is a problem and at the same time don't make situation worse for everybody else who feels current settings are ok.

verygreen said:
Basically the problem is: there are multiple complaints about people having too sensitive/too insensitive touchscreens. I don't think I am seeing anything like that, but there is more than one report so perhaps different people have different tolerances and different hardware has it's quirks.
The goal here is to arrive at a different set of defaults that would improve the situation for people that feel there is a problem and at the same time don't make situation worse for everybody else who feels current settings are ok.
Click to expand...
Click to collapse
mine personally was very insensitive. when i'm on slickdeals and i know you are also or bleacher report clicking on links such as hot deals and my subscriptions would take multiple tries. i didn't notice much system wide but mostly on the internet clicking smaller links. whatever he did with this zip made mine personally much much better.

verygreen said:
Basically the problem is: there are multiple complaints about people having too sensitive/too insensitive touchscreens. I don't think I am seeing anything like that, but there is more than one report so perhaps different people have different tolerances and different hardware has it's quirks.
Click to expand...
Click to collapse
Aha... then I guess I *did* know about the problem. I noticed it most when reading books. After a few minutes, the page turning touches on the lower right margin would seem to stop. I finally just gave up even trying to use them, and substituted a swiping movement. Anyway, with this zip installed, the sensitivity doesn't seem to be any worse, and might well be better. It hasn't been very long, but I'll keep an eye open for differences.
PS: Just read some of the other people's posts, and see that they were complaining of difficulty in clicking links in web pages. I had certainly noticed that, but hadn't even thought of the possibility of fixing it, so had just ignored it. With this new zip, it does seem like web link sensitivity is much improved.

dbrickg said:
Aha... then I guess I *did* know about the problem. I noticed it most when reading books. After a few minutes, the page turning touches on the lower right margin would seem to stop. I finally just gave up even trying to use them, and substituted a swiping movement. Anyway, with this zip installed, the sensitivity doesn't seem to be any worse, and might well be better. It hasn't been very long, but I'll keep an eye open for differences.
PS: Just read some of the other people's posts, and see that they were complaining of difficulty in clicking links in web pages. I had certainly noticed that, but hadn't even thought of the possibility of fixing it, so had just ignored it. With this new zip, it does seem like web link sensitivity is much improved.
Click to expand...
Click to collapse
mine is much improved. whatever adjustments were made I feel like mine could go even a little more in that direction. I'm at like 85% now lol

Thanks, alal690! I think he deserves to get some "Thanks", too, but he doesn't have any posts! And thanks to verygreen for providing the tools for alal690 to tweak with, of course!

I have noticed more mistypes on the keyboard verygreen if you are still needing input but the positives outweigh that in my book. it really is much better on websites. please thank the other dev that worked on this also alal690.

Big improvement for me, thanks I suspect the issue with pressing ui elements was caused by jitter and phantom touches that may have been caused by oversensitivity even though it seems somewhat counterintuitive... Selecting text was the big issue for me and it's now vastly improved. As has my accuracy on they keyboard - normally I'd have had to retype half of a post this length

BTW, it woul be great if people with some sort of a protective film over the touchscreen will give this a try to make sure it's also ok for them (I know those screen protectors are really popular amongst some people).

I've spent the last week trying to fix this, but it looks like it could be a problem with a driver or the actual hardware itself. If you go to Dev tools, then Pointer Location, you can see the reported values for touch pressure and size. When holding down my finger anywhere on the top 2/3 of my screen, the xy and size values jitter like crazy. If I touch the bottom 1/3 of my screen, there is no jittering and the size value is constant.
I think people that are complaining about low sensitivity are mistaken. I think the touch screen response is actually too sensitive, thus causing the jitter and making it hard to click on hyperlinks.
Reducing the touch sensitivity scale and increasing the touch size in the IDC file has helped a lot, but the jitter is still a problem that I hope someone can figure out how to fix.
Sent from my BN NookHD+ using Tapatalk 4 Beta

phammichael said:
I've spent the last week trying to fix this, but it looks like it could be a problem with a driver or the actual hardware itself. If you go to Dev tools, then Pointer Location, you can see the reported values for touch pressure and size. When holding down my finger anywhere on the top 2/3 of my screen, the xy and size values jitter like crazy. If I touch the bottom 1/3 of my screen, there is no jittering and the size value is constant.
I think people that are complaining about low sensitivity are mistaken. I think the touch screen response is actually too sensitive, thus causing the jitter and making it hard to click on hyperlinks.
Reducing the touch sensitivity scale and increasing the touch size in the IDC file has helped a lot, but the jitter is still a problem that I hope someone can figure out how to fix.
Sent from my BN NookHD+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I agree with phammichael that the real issue here would be jittering, but my symptom is different.
This is what I found so far.
- Pinch out to zoom in something (in gallery or web browser) and hold the 2 fingers on the screen.
- If my fingers are on the right side of the screen surface (portrait mode), the screen jitters. You can see the touch values changing fast and continuously by tiny values.
- If my fingers are on the left side of the screen surface, the screen won't jitter and stay calm.
Am I the only one experiencing this issue?
BTW, this is before I applied verygreen's touch screen patch. I will report back after applying it.

pins2u said:
I agree with phammichael that the real issue here would be jittering, but my symptom is different.
This is what I found so far.
- Pinch out to zoom in something (in gallery or web browser) and hold the 2 fingers on the screen.
- If my fingers are on the right side of the screen surface (portrait mode), the screen jitters. You can see the touch values changing fast and continuously by tiny values.
- If my fingers are on the left side of the screen surface, the screen won't jitter and stay calm.
Am I the only one experiencing this issue?
BTW, this is before I applied verygreen's touch screen patch. I will report back after applying it.
Click to expand...
Click to collapse
The jittery right hand side of the screen in portrait mode is the problem - I have this on my HD+ (which was new) and my Dad has it on his (which was new) as does my friend (again a new unit)
There have also been lots of others reporting the same thing on here.
Put the HD+ into landscape mode and the issue disappears.
I've just applied verygreen's 'fix' zip and I have to say that touch response is loads better - clicking links etc works far more reliably (but right hand side of the screen in portrait mode jitters still exist)
Great work as usual verygreen

Touch screen sensitivity issue

Hi guys, apologies if this has already been discussed elsewhere. I've been using the Mate 9 for a couple of days now and I've noticed the touch screen sensitivity can sometimes be unresponsive. There has been a number of times where I've been on a browser or app and had to click on a link/button at least twice before it responds. It's the same when I click on the Settings button at the top of the notification panel and other areas such as the settings page.
I thought it was just me but I've gone back to my Nexus 6P and iPhone 6s to test, and there is a notable difference.
Has anyone else experienced this? It almost seems like Huawei have intentionally done this as the touch sensitivity elsewhere, i.e. lock screen, seems to work just fine.
Does anyone know if this a known issue and is it likely to be fixed?
Thanks in advance.

Same issue here I believe it has been fixed with a firmware update which has yet to land on my UK model

I sometimes experience some unresponsiveness as well, but told myself maybe it's due to the screen protector? Curious to see if others who took off their screen protector experience this same problem.
It's very minor though, for me.

I know the update was supposed to help and did but I just found a pressure sensitivity setting that allowed me to change the sensitivity which made a big difference IMO. I installed Quick Shortcut Maker and found it under settings. Made the shortcut and pressed it and voila I could decrease the pressure needed to respond.

rndchef said:
I know the update was supposed to help and did but I just found a pressure sensitivity setting that allowed me to change the sensitivity which made a big difference IMO. I installed Quick Shortcut Maker and found it under settings. Made the shortcut and pressed it and voila I could decrease the pressure needed to respond.
Click to expand...
Click to collapse
Are you rooted? Because it tells me that access is denied.

Sammath said:
Are you rooted? Because it tells me that access is denied.
Click to expand...
Click to collapse
No. Stock. I never saw anything similar to that. Installed app. Added shortcut to Pressure Sensitivity and then opened shortcut and moved slider all the way to the left to decrease pressure required.

rndchef said:
No. Stock. I never saw anything similar to that. Installed app. Added shortcut to Pressure Sensitivity and then opened shortcut and moved slider all the way to the left to decrease pressure required.
Click to expand...
Click to collapse
Maybe it's the firmware I'm on MHA-L29C432B158

Yes it does exist AFTER removing screen protector.
Mine is too the point I may return it even thou I think it has a better camera than Samsung and LG