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.
Related
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.
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Well, maybe you should go back to an unrooted phone so that you can play with your steamy window....
LPChris, I would expect a little more maturity from a "senior member"
I am trying to contribute to make JF the best it can be. Maybe your just having a bad night or something, but theres no need to be so childish.
:ed:
Looking through your posts it seems like your just having a bad night
Back on topic:
While this may be a stupid little problem with one application. Should finger-area sensitive applications continue to be made this could isolate JF1.41 from the market. Naturally I dont care much for steamy window, but I would like to prevent other issues in more... useful... applications
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
sjbayer3 said:
On my unrooted phone the "Steamy Window" application worked fine
If I pressed a little it would make a little line in the "steam", and if I were to push my thumb down on a large area, it would detect that and make a "thumb" sized print.
Now using JF1.41 no matter what I do it only makes a TINY TINY line, about a pixel or two in size.
Did the modification of the screen change an api that the Steamy Window app is using to work different?
Click to expand...
Click to collapse
Ditto about LPChris lol, a lot of his posts sound like that, but yeah I noticed the same thing about the steamy window app before and after using JF 1.41.
Steamy window, LOL! sorry guys. anyway keep up the great work.
Yes, this is a trivial example, but it does identify a real issue.
I was reading through the various google android groups last night and I ran into some info that seems to addresses this issue. From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
your Steamy Window app seems to make use of the size value as it was originally designed. Now with the change, with only one finger input, this value is set to some minimum, producing a thin line.
To test this theory, see if when you touch the screen with two fingers the size of the mark gets bigger.
Why can't a capability bit or other mechanism be defined that could be used to indicate whether or not an application were multi-touch aware, so that the touch handling behavior at the lower levels would revert to "standard" behavior for normal (non-multi-touch) apps? Trying to make the multi-touch hack fully backwards compatible may not be practical.
I tested your idea about multituch possibly fixing steamy window
My only results are really strange.
If I touch with two fingers it will make a line about the width of my 2 fingers, but its located in the top left, no matter where my fingers actually are. Furthermore the line isnt straight its curved.
Now, after my first touch, it seems if I touch it again it just crashes.
ex-MN said:
From what I was able to gather, the JF1.x implementation of multi-touch uses a community hack that reassigns the value that normally keeps track of the size of the touch input. This value is now used to keep track of the distance between two touches. (see: http://groups.google.co.uk/group/android-platform/browse_thread/thread/209b512a9fdf7367?hl=en)
Click to expand...
Click to collapse
Edit: Hmm... the x-y data of the second finger is stored in separate fields. I think the usage of the size field is just as a boolean to tell multitouch capable programs that second finger data is being sent.
themes and JF RC versions. be careful
TheDudeOfLife said:
I've seen some weirdness where my home screen has a jitter. I've also had accuracy issues with clicking menu items and buttons. I'm going to backup my phone and load JF 1.31 back on to see if it is the screen or the img.
Interesting...I just reflashed with 1.41 RC30 and the problem went away. I was using the fade to blue theme .99.
Click to expand...
Click to collapse
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
BhanG
bhang said:
it seems as tho themes have to be matched to the rom, a theme for 1,30 may flake out on 1.41, most of the themes I have seen and used so far were marked as to which rom the were intended to theme...
Click to expand...
Click to collapse
After some more testing I have this same issue on 2 1.41 compatible themes (rusty metal and fade to blue) I am going to go back to themeless 1.41 but I think it is more related to the multitouch 'hack' than the theme themselves. I find it hard to believe that a bunch of icons could mess this up. I watches my screen jitter between the left and right screen for 3 minutes today before I just performed a soft reset on my phone.
Note: I also applied each theme from a fresh flash of 1.41...not on top of each other.
this happens with screen crack also, but it doesnt affect me that much until i start not being able to select stuff. i know it may be important its just not to me... yet *knocks on wood*
Yeah Ive noticed it too..
I thought that it was just the app at first.
I might be switching back to .31 then at least til this gets fixed.
Steamy window def is NOT reading my fingers location or size properly.
I've also seen it affect touch paint found in the API Demos. Doesn't even register touch anymore.
It appears multi-touch is premature at this point and to implement multi-touch throughout the OS and not just the browser like everyone seems to think isnt good. It is definitely is throughout the OS and probably will affect any application that uses the second touch value to register touch size.
My other concern is that dev's won't take this hacked multi-touch into account so they will continue to write programs that won't be compatible since its not the "norm"
Taken from and android forum...this is my biggest concern
"Please think about soft keyboards when considering multi-touch APIs,
where the problem isn't detecting the distance between two finger, but
rather is allowing a 2nd finger (or thumb) to come down on a 2nd key
before the first finger (or thumb) has been released. The proposed
API to provide only a centroid and the distance between fingers won't
work at all for this sort of application.
I think you'd ultimately want to package this as additional
GestureDetector subclasses, depending on whether the type of gesture
detection wanted was pinch/zoom or multiple/overlapping taps.
Keyboards (and maybe games) would use one class, browsers another.
Providing the right information from a touch panel to drive either
detector might be challenging, especially if the panel provides
'unpaired' x and y coordinates rather than individual touch locations,
but I believe it could be done. "
JesusFreke,
Any thoughts on this?
Yeah lets hear what JF's got to say.
I originally thought that the multitouch was embedded in the browser, It's too soon to have it throughout the entire OS...
How about 1.41=with multitouch and 1.42=without
I've installed JF1.41 and I have an unusual bug....sometimes the screen behaves like it isn't calibrated..i press the screen on a button and it is pressed another one....have anyone encoutered this problem?
I invite everyone to do the following to find out how ur touch registers on ur screen. Open anycut. Get it if u don't have it.
Click activity and find raw image viewer. Click ok and then click on the shortcut.
Now start moving your finger around and see the results.
Let's all post our results here so we can figure this out.
Post in the same format as me:
ROM: JF1.41
1 finger - it surpisingly followed my finger perfectly. It only registered the very center point of my finger.
2 fingers - it appears that it made the same point as the 1 finger, however now the point was exactly in between my fingers and stayed there as I moved them around.
Ok so now we need ppl with stock rc30 and 1.31 so we can test this out!
You wanna have some real fun? Try it with 3 or 4 fingers.. It goes nuts..
This is mainly directed towards programs developed right here, by fellow members (I don't see this problem in professional programs).
Of the countless programs from here that I've ran on my phone, just about all of them would screw up/not have any particular handling for when my screen rotates. Generally, the bottom half of the program disappears to some imaginary area off screen, where my keyboard would be. There won't even be any way to scroll down to see what got cut off. Also, as the program is left-justified, the right side of the screen is blank and unused. It looks wholly unprofessional and sometimes a perfectly suitable solution is just to make the program not rotate! I can't imagine such a thing being very hard to implement, yet I very rarely see any program make any effort to deal with this issue.
Honestly I don't understand why I even have to request something like this. I consider it common sense, but I guess not.. >_>
I feel like I'm going to get flamed for this but I hope for the better.
This is the most annoying POS program I have ever seen , whether I have a stock rom or custom rom this annoying program pops up whenever it wants usually while Im doing something , but it also just starts for no reason while sitting on a table ! Yes I turned it off in setting , that doesnt turn it off , that doesnt do sh1t , I mean at least have an on off button for this annoyance , anyone know of a place in the registry to cut this off (gooddaytodie, heathcliff,Jax ???)!!
It's easy enough to remove it from a custom ROM, but if you're getting the app triggering randomly like that, it's probably not a software problem. That sounds like a hardware issue, with either the capacitive buttons being too sensitive (a problem some phones will exhibit, especially while plugged into a charger and then laid on their backs) or with something in the case being messed up. I've had TellMe trigger a few times when I was gripping the phone really hard playing Z0mb1es, but not since then and never while just lying there.
I was hoping Id get your attention and yes I figured it was a hardware issue with the capacitive buttons , but is there any way to disable tell me and yet retain the actions of the capacitive buttons? its really annoying , it may be a hardware issue however after researching this its quite prevalent on the new nokia phones as well I am using a samsung 1st gen focus and I do have a custom rom , if you can point to the right location in the registry to remove this pest I would be appreciative , I will report back to you to let you know how it works out?
Thanks again GDTD , always pleasure hearing from you!
I know of no way to just "disable" it, though that's probably just because I haven't looked. It's part of WebSearch.exe, which if removed or renamed would prevent TellMe from launching (it would also break the other functions of that app, though, such as the barcode scanner and Bing Music).
The Focus is indeed the device I've most commonly heard complaints of having over-sensitive buttons / touchscreen that occasionally push* themselves. I've never tried, but I've heard there's a tool - in the Diagnostics app, I think - that lets you adjust the buttons. Maybe that would help?
* I was going to say "touch", but that... didn't look right.
Thats exactly what I was thinking that there might be some controls in diagnosis that adjust the sensitivity , but, alas I dont know what they would be , if you have the time could you look for me?
I don't have any Samsung phone, and the Diagnostics app is completely different between OEMs. You're better off just doing some searches of the forums, especially the Focus sub-forum.
yep I have been, I used to know all the good codes , but I guess I will have to start searching again, thanks anyway! I think I might be heading back to Android ,after this fone has run its course , just so much you can do with the platform ,unlike windows and crapple ! I am really ticked off how Microsoft keeps sabotaging itself , win 8 phone kills win 7 phone as win 7 phone killed mobile , every two years ,ya have to start all over again ,you will never catch apple and wont even catch a dream of android!
So, I really really wanted to love this tablet. The disappointments have been many, but this focuses on the most severe and frustrating one.
Whenever I am using Dabbler, Skecthbook Pro, ArtFlow, or any other pen-enabled apps, the weirdest things start to happen. It works OK for a while, but then the tablet only starts receiving input from the stylus. Not even UI elements are usable with my fingers. PLEASE NOTE: I do know the tablet has a stylus-only mode, and this is NOT enabled. PLEASE ALSO NOTE: No, the stylus-only mode in the apps is not enabled either.
After a fresh reboot, I open the drawing app and everything works. Palm-rejection is gorgeous, pen accuracy is spot-on, multitouch gestures as pinch to zoom and panning work flawlessly. But after a while, or after I exit the app and return, it starts progressively degrading performance. At first it only accepts pinch to zoom like 50% of the time. Then it gets worse, until I can't do a thing without the stylus - not even the back, home and multitasking buttons.
I spoke with an nvidia tech support rep, and after a back and forth of emails (mostly me giving him info about the proof of purchase, serial number, etc) he told me to contact the seller (Amazon) and ask for a replacement.
I was about to go ahead and replace it, but I wanted to know if any of you are getting the same issues. On the latest official ROM, can everybody use Dabbler, Autodesk Skechbook, etc. for PROLONGED periods of time, and with a high tablet up time, without issues? Is this issue device-specific?
THANKS so much for any help and sorry for long post.