Related
Has anyone made a haptic touch plugin for wm6 devices?
Would love the phone to slightly vibrate when I use the touch keyboard.
I'm on a htc diamond btw.
I think it would be cool too, but I think one of the biggest problems is the time delay between hitting the key and feeling the vibration. I also wonder about the effect on battery life... anyways I would still like to try it!
You might want to do a search because I remember reading about something like this but think it was for the dialer.
I will post here if I find the thread.
-bridic-
Yea I am pretty certain one of the Iphone dialers is haptic or something...perhaps it's a dailer you have to pay for.
I have a couple kinda sorta solutions..
I'm at work so I don't have them here.. But I have one .cab that will vibrate when you press the number buttons on your dial screen, and it work's perfectly. And then I have an .exe that make's every screen tap vibrate, and it kinda sorta work's. I've looked for feedback programs for months, and have found nothing. The best thing i've determined which took me forever, is enabling screen tap sounds, and going into the registry and changing the default sound to vibrate instead.. I can also look up how to do this for you when I get home.. But really there's no good solution out there. On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Raven1467 said:
I'm at work so I don't have them here.. But I have one .cab that will vibrate when you press the number buttons on your dial screen, and it work's perfectly. And then I have an .exe that make's every screen tap vibrate, and it kinda sorta work's. I've looked for feedback programs for months, and have found nothing. The best thing i've determined which took me forever, is enabling screen tap sounds, and going into the registry and changing the default sound to vibrate instead.. I can also look up how to do this for you when I get home.. But really there's no good solution out there. On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Click to expand...
Click to collapse
Tnx a lot walter, and thanks for explaining the difference between haptic and tactile
Posting a guide on changing the registry or giving me a link to the two programs mentioned over would be great.
Raven1467 said:
On another note this would be almost considered tactile feedback.. Haptic feedback is crazy technology that deals with detecting the electrical current from your touch. That's why current PPC's are awful with this stuff, cause it doesn't have that technology, and most phones that say they do, don't, they just mimic it.
- Walter
Click to expand...
Click to collapse
uh, not quite sure what "haptic" technology you're talking about, but any feedback of mechanical vibration would definitely be considered "haptic feedback". From wikipeida: "Haptic technology refers to technology which interfaces the user via the sense of touch by applying forces, vibrations and/or motions to the user."
Also, to address concerns a little further up the thread: If implemented correctly, there is no perceptible delay between screen contact and vibration feedback. Me and a couple friends whipped up a little test application based on the WM6 SDK's application template, wherein if you tap anywhere in the application window, the vibration motor is toggled for ~50ms (this can be adjusted based on preference, but 50ms was a nice barely perceptible 'thud' with each tap). The feedback is, for all intents and purposes, instantaneous. Also, since the vibrator is only active for 50ms, you'd need to tap 20 times before you've drained the same battery as a 1 second text message alert, or 40 times for 2 seconds, and so on... really, I think the battery drain would be negligible. Anyway, proof of principle for using the vibration motor for haptic feedback is there, and the affect is quite nice, but we never got much further because of a lack of time and programming knowledge. By the way, if anyone has any information on how to hook into touch.dll (which would be the proper way of implementing a system-wide haptic response), I'd be very interested in hearing about it.
This sounds a very interesting idea! Not every program visually responds to touch when operated with finger, so sometimes I was just left wondering did I make the touch? Did the touch go through? Then one or two seconds later (yes my phone is that slow) something happens. This should help if not eliminate that problem.
Here is the cab for the haptic-esque dialpad if anyone was interested
i've noticed that when haptics is on, it tends to vibrate only every other press
such intensive vibration is probably bad for your phone
a_lazy_dude said:
Also, to address concerns a little further up the thread: If implemented correctly, there is no perceptible delay between screen contact and vibration feedback. Me and a couple friends whipped up a little test application based on the WM6 SDK's application template, wherein if you tap anywhere in the application window, the vibration motor is toggled for ~50ms (this can be adjusted based on preference, but 50ms was a nice barely perceptible 'thud' with each tap). The feedback is, for all intents and purposes, instantaneous. Also, since the vibrator is only active for 50ms, you'd need to tap 20 times before you've drained the same battery as a 1 second text message alert, or 40 times for 2 seconds, and so on... really, I think the battery drain would be negligible. Anyway, proof of principle for using the vibration motor for haptic feedback is there, and the affect is quite nice, but we never got much further because of a lack of time and programming knowledge. By the way, if anyone has any information on how to hook into touch.dll (which would be the proper way of implementing a system-wide haptic response), I'd be very interested in hearing about it.
Click to expand...
Click to collapse
That sounds pretty perfect. Would be nice if someone finished your project.
DiemetriX said:
That sounds pretty perfect. Would be nice if someone finished your project.
Click to expand...
Click to collapse
I've installed this but can't find it anywhere. Looked in programs, personal and settings. I've even looked in the windows folder. I have an HTC Raphael.
Any pointers please...?
As I was driving yesterday, I was frantically (and dangerously) trying to type a text message on my Vogue. As you people with phones that have no hard kb, you know how frustrating it can be to type a message, let alone while one is driving. Now I know that it's not safe to text while driving period, but there are certain times when it is necessary. I came across the idea of a D-pad keyboard. You would use the directional pad on the phone to select letters from a keyboard, and then use the center button to select that letter for input. While this would not be fast or efficient typing, this would help greatly to type messages when only one hand is free for driving, or some other activity, as it would give the user an actual button to press. Sadly, I have no programming experience whatsoever. I also don't have a steady source of income, so I cannot guarantee any donations if someone developed this. But maybe if enough people caught on to the idea and liked it, a bounty could be started for someone who developed something like this. I've uploaded some rough mockups of what it might look like.
drewden123 said:
As I was driving yesterday, I was frantically (and dangerously) trying to type a text message on my Vogue. As you people with phones that have no hard kb, you know how frustrating it can be to type a message, let alone while one is driving. Now I know that it's not safe to text while driving period, but there are certain times when it is necessary. I came across the idea of a D-pad keyboard. You would use the directional pad on the phone to select letters from a keyboard, and then use the center button to select that letter for input. While this would not be fast or efficient typing, this would help greatly to type messages when only one hand is free for driving, or some other activity, as it would give the user an actual button to press. Sadly, I have no programming experience whatsoever. I also don't have a steady source of income, so I cannot guarantee any donations if someone developed this. But maybe if enough people caught on to the idea and liked it, a bounty could be started for someone who developed something like this. I've uploaded some rough mockups of what it might look like.
Click to expand...
Click to collapse
DONT. TEXT. WHILE. DRIVING. Especially on a touchscreen only phone. Not to mention your mockup would take extremely long to type out one word let alone a message. what you want would be to have multiple slides, first slide you can go either L or R with the full keyboard split in half. pressing L will give you a slide with the letters of q-t, a-g, z-v; R will give you y-p, h-l, b-m. from these slides you can go U, D, and R. U will give you top row of letters, D will give you bottom row of letters, just select will give you middle row and R will give you either number pad or symbol pad. minimum key presses is the key.
You should try the phone keypad, I find it alot easier when driving. Of course I still don't recommend typing while driving . But why I think would be even better is voice feedback. As you press a letter or key on whatever keyboard you're using it would voice the key you pressed then enter the character with a confirmation click sound when you release the keypress.
First off, please stop texting while you're driving. Why can't you just pull over and do it? Why risk your life and other innocent people because you're texting? NOTHING is that important for you that you can't just pull over to the side of the road and do all your texting there. Your idea is unique but pretty useless for your situation as well. It seems it will take a lot longer to move the directional pad and hit enter after the right selection with the middle button on that button decal. At the end, you'll still have to look at your phone while texting. How would you find the defendant if you were one of the juror in a jury, listening to some guy who seriously injured or killed someone because he was texting?
Actually, with an SIP such as TenGO this is an excellent idea.
one day i really needed to text while driving, i started typing.
suddenly i realized that the traffic stopped and i was so close, luckly my breaks could stop me on time.
other wise, i would never be here i guess.
since then, i never touch the phone while driving, the max is picking up the phone using BT Headset.
scary. be carefull, driving is not a game, you cannot load life back if mission failed.
anaadoul said:
one day i really needed to text while driving, i started typing.
suddenly i realized that the traffic stopped and i was so close, luckly my breaks could stop me on time.
other wise, i would never be here i guess.
since then, i never touch the phone while driving, the max is picking up the phone using BT Headset.
scary. be carefull, driving is not a game, you cannot load life back if mission failed.
Click to expand...
Click to collapse
Yes, I understand your experience. And thank you all for all your replies. I'm glad a lot of people are concerned about the safety of all the drivers. However, I also stated that this could primarily be used in OTHER activities in which you only have one hand free or cannot/should not be fully focusing on your phone. I realize the risks of texting while driving, which is why I don't when in any type of traffic. I live in rural Indiana, where most of the times it's a wide open road with fields to the left and right and not a car in sight. I just thought this would be a simple solution if the urgency was presented where someone needed to send a quick text. I also think voice feedback would be helpful. Even better would be speech-to-text + BT headset. That would be the ultimate program for this situation, but I have yet to see anything close developed. Once again, thanks for all the input.
flyboy009 said:
You should try the phone keypad, I find it alot easier when driving. Of course I still don't recommend typing while driving . But why I think would be even better is voice feedback. As you press a letter or key on whatever keyboard you're using it would voice the key you pressed then enter the character with a confirmation click sound when you release the keypress.
Click to expand...
Click to collapse
Phone keypad would be your best bet.
anaadoul said:
one day i really needed to text while driving, i started typing.
suddenly i realized that the traffic stopped and i was so close, luckly my breaks could stop me on time.
other wise, i would never be here i guess.
since then, i never touch the phone while driving, the max is picking up the phone using BT Headset.
scary. be carefull, driving is not a game, you cannot load life back if mission failed.
Click to expand...
Click to collapse
lol.
wouldn't be cool if there was a giant reset button.
haha.
I agree with everyone though, don't text while driving.
In most of the states in the US it is actually illegal to do so,
and has quite the hefty fine associated with it.
There was this girl about 6 months to a year ago that was driving down the US 60 (in arizona) and was in the left lane of the highway, and ended up swerving all the way accross every lane of traffic and tboned a parked van on the side of the road that had overheated.
Inside that van were 2 adults, and their 4 children
(2 young teens and 10 and 5 yr old I believe, something around those ages).
All 6, and the girl texting, were killed upon impact.
They found the girl texting gripping her phone (with keyboard slid out) in her hands.
Moral of story, Population control.
JKJKJKJKJKJKJKJKJKJKJK!! I'm goin to h*ll for that one.
But seriously, I don't recommend texting while driving.
TEXTING WHILE DRIVING is good if you have set your vehicle in AUTO PILOT! XDDD
Ahh well, guess the idea is shot down by the community. I really meant it for more purposes other than driving, just thought driving would be one of them even though it's not recommended. I guess I'm just unsuccessfully trying to find some way for efficient, easier input on a touch screen like the Vogue. I have small fingers myself and I have yet to find a quality keyboard that I can get up to speed on. And yes the phonepad is the next best thing if the need arises. Has anyone seen anything close to being capable of speech-to-text? I'm probably dreaming here but that would be an amazing app that could probably make a lot of money
What could surely be possible would be for the 9 buttons available on the d-pad to correspond to a t9 keypad. Press up for abc, up-right for def and so on.
Definetly would like a d-pad keyboard! The more options the better. Check out a psp for reference.
jez83uk said:
What could surely be possible would be for the 9 buttons available on the d-pad to correspond to a t9 keypad. Press up for abc, up-right for def and so on.
Click to expand...
Click to collapse
that idea sounds pretty good, except I'm pretty sure on the Vogue, or any other d-pad on a phone, there aren't diagonals (up-right, down-left, etc.) are there? Just up,down.left,right.
VLingo
A better solution to your texting while driving would be a speech to text software, have a look here. I have not tested it myself yet but it looks interesting and safer than the alternatives. Please don't risk other peoples lives.
And please vote in my poll.
Thanks for the link! I also voted on your topic.
Wow....
I was so looking forward to this device after my Kaiser/XperiaX1/Rhodium. My biggest gripe was always the speed, then the screen size, after all.
But this thing is next to useless. The capacitive touch screen is HORRIBLE, and the lack of a stylus so annoying that words cannot describe. I find that I constantly end up with apps closing when I try to press buttons near the top, etc.
Its impossible to type with, its so inaccurate. Maybe its unfair of me, coming from devices with keyboards but even so, I could type on the screen of my rhodium soo much better.
I guess that boils down to "capacitive screen" too, I guess I'll be going back to my Rhodium and waiting for a snapdragon or tegra powered system with a resistive screen.... Calibrating this thing makes no useful difference.
Sorry for the rant, more than a little frustrated with my £500 paperweight atm.
Nemeth782 said:
Wow....
I was so looking forward to this device after my Kaiser/XperiaX1/Rhodium. My biggest gripe was always the speed, then the screen size, after all.
But this thing is next to useless. The capacitive touch screen is HORRIBLE, and the lack of a stylus so annoying that words cannot describe. I find that I constantly end up with apps closing when I try to press buttons near the top, etc.
Its impossible to type with, its so inaccurate. Maybe its unfair of me, coming from devices with keyboards but even so, I could type on the screen of my rhodium soo much better.
I guess that boils down to "capacitive screen" too, I guess I'll be going back to my Rhodium and waiting for a snapdragon or tegra powered system with a resistive screen.... Calibrating this thing makes no useful difference.
Sorry for the rant, more than a little frustrated with my £500 paperweight atm.
Click to expand...
Click to collapse
All I can think is you must have really FAT fingers becuase the screen on this baby is amazing and typing on it is amazing. It's a million times better than the iPhone.
I haven't ever used an iphone for more than a few mins.
I don't think the issue is finger size as I can type better on the screen of my rhodium which is smaller, but resistive. Its more the fact that I touch a button and something happens over the other side of the screen (maybe a slight exaggeration) and apps like Resco file explorer leave me trying to press the same button 20 times before I get it due to lack of Stylus.
Its not usable, its just frustrating.
Nemeth782 said:
I haven't ever used an iphone for more than a few mins.
I don't think the issue is finger size as I can type better on the screen of my rhodium which is smaller, but resistive. Its more the fact that I touch a button and something happens over the other side of the screen (maybe a slight exaggeration) and apps like Resco file explorer leave me trying to press the same button 20 times before I get it due to lack of Stylus.
Its not usable, its just frustrating.
Click to expand...
Click to collapse
Just give it a day or two. You'll never want to have an other device...
I really disagree with you on this. I think the screen and the responsiveness is superb to type on. Top of marked for sure. Beats iPhone and Hero imo.
The touch screen on HD2 just like a sexy girl - soooo sensitive.
beating the iPhone and Hero doesn't mean much to me as I haven't done much with either beyond a quick fiddle, but we are all held to believe that capacitive is better, so I was expecting an improvement on my old phones which have all been Resistive.
Maybe mine is broken I guess...
Still, I eventually managed to make a link to the task manager on the start menu. It feels like I fight with it for 30 mins and if I am lucky, I happen to get something done along the way.
If only it was like just about every other HTC phone I have used and had the little drop down task manager on the home screen where the X would usually be...
Its all down to
Calibration.
Ensure you calibrate the screen and calibrate the screen how you tend to use it.
I calibrated the screen with my thumb while holding it in the same hand. Scary but for its size and sensitivity it works great.
Be careful about calibrating with your finger then expect to type great with your thumb. Works okay but you will need some patience. You will get better results with calibrating with your thumb in my situation.
^Agree, re-calibrate your screen & see the differents. If you still want to sell, then put it in the Marketplace...
Try this fix.. For me it was a 100% improvement.
http://forum.xda-developers.com/showthread.php?t=585511
If only it was like just about every other HTC phone I have used and had the little drop down task manager on the home screen where the X would usually be...
Click to expand...
Click to collapse
There's a tweak for that already [that puts it back there] - think it's a Dutty job - have a look in the other forum on apps
And BTW - I've owned an iPhone and many HTC touhscreens and I feel your pain - I too have issues with this one typing is pretty inaccurate (typically it seems to trigger the key blelow that which I'm typing on) and sometimes it seems to just not recognise a press at all....I end up jabbing it so hard with my finger sometimes in frustration! I'm becoming more used to it but it is a little dissapointing, given the iPhones screen (for accuracy and responsiveness) is certainly thus far better than this one
Guys, remember, this screen is going to take time to get used to. Capacitive is a totally different beast to resistive.
And one day is not long enough to fully get used to a device. I am having a few small problems with typing (mostly because it's so sensitive and I'm not used to it!).
Once I get used to it, I don't think there will be any problems. I can already type faster on the HD2 on screen keyboard than I could on the X1 hardware keyboard!
Nemeth782 said:
If only it was like just about every other HTC phone I have used and had the little drop down task manager on the home screen where the X would usually be...
Click to expand...
Click to collapse
The Dutty's fix for this didn't work for me, but this alternative did, and there's a few other tasty treats on the post too...
http://forum.xda-developers.com/showpost.php?p=4947950&postcount=1
Original Poster's phone could be faulty. I had a demo of an HD2 the other day, and the keyboard was going completely mad: touching the backspace key, for example, resulted in a flurry of detected key-presses not just of the backspace key itself but of all keys around it in all directions. I mentioned this to the guy in the shop and he said that the reason why they had put that one aside for demo purposes was precisely that they couldn't get the screen properly aligned/calibrated on it, and that the other models they had didn't have the same problem. He might have been lying, of course....
Whenever I try to start/respond to a sms, it takes about 10 tries of me tapping on the textbox at the bottom of the screen for it to recognize I'm tapping it and to make the keyboard come up.
My buddy, who will use my phone, can do it almost every time though... I'm coming from an iPhone so I'm used to touchscreens. I've tried with/without my nail, using my entire THUMB, using just the tip of my thumb.
I dunno what to do... Any ideas? Thanks
I noticed that this will happen to me on occasion. In my experience with it, if I tap towards the top of the box it will work the first time, but if I tap towards the lower bottom then it doesn't work so often.
actually, this used to happen to me alot.
then I noticed that every time i was trying to touch the text box, my thumb, or another finger from my other hand, was also touching the screen.
And since the stock keyboard doesn't have a detected multi-touch input, when there are two touched, the input value is returned as null.
So, once i figured that out, i never had a problem. But, there has also been complaints about the touch screen calibration being off, so...you can never know unless you mess around
Ill give those tips a shot! Maybe adding the multi touch hack will help too...
It also helps if you don't just tap really quick, but press it instead(well not really press, but leave your thumb or finger on it for a second).
I'm sure there are weird calibration issues near the bottoms of our screens. When I first got the phone, I really thought it was broken or there was a huge bug trying to get the virtual keyboard to come up while writing SMSes. Like david said, try touching a little higher than where the text box is to bring up the VK. Usually, I aim at the top border of the box. Now I rarely have to touch more than once to bring it up, but it's still an issue that should be addressed by HTC (or maybe Google).
heroskyy said:
actually, this used to happen to me alot.
then I noticed that every time i was trying to touch the text box, my thumb, or another finger from my other hand, was also touching the screen.
And since the stock keyboard doesn't have a detected multi-touch input, when there are two touched, the input value is returned as null.
Click to expand...
Click to collapse
This is exactly what I determined. My keyboard pops up every time when press near the top of the input box.
Is this a hardware issue - or something a future update is able to correct?
You can long-press the "Menu" softkey to open the keyboard at (almost) any time.
When this happens to me i just push in the trackball and the keyboard pops up.
tiltman71 said:
When this happens to me i just push in the trackball and the keyboard pops up.
Click to expand...
Click to collapse
x2
I also noticed if you get a lot of texts or have a lot of texts the problem gets worse.
Hello!
I have been having a small issue with the touchscreen. This all started when I noticed I could type faster on my iPod touch than I can on my Incredible (no, not another Apple fanboy lol). So I started to look into what was causing this. Quite quickly I noticed that some keyboard presses did not register, but I saw the icon pop up (to show which key I was pressing)! This only happened if I typed fast... so then I started to look deeper into why the icon popped up but it didn't type the key. I figured out that if you touch two points too quickly, the screen registers it as a "drag" event. As a side note, I've been using Smart Keyboard Pro for it's multitouch capability. I've tested this by tapping twice quickly in Swype, and sure enough, it drew a line between two keys.
Has anyone else experienced anything like this?
Thanks,
x.v_
I made a video to demonstrate what I'm talking about!
http://www.youtube.com/watch?v=fsln2yas1p0
Someone reply? >.<
100 views + 40 YT views
it has nothing to do with multitouch. do the same thing but hold a finger on a and a finger on l at the same time, then let go of a and the same thing happens. you're just touching it fast enough that that's how it's registering. it's not the screen, it's the apps. swype isn't multitouch so that's what happens when you try.
it has nothing to do with multitouch. do the same thing but hold a finger on a and a finger on l at the same time, then let go of a and the same thing happens. you're just touching it fast enough that that's how it's registering. it's not the screen, it's the apps. swype isn't multitouch so that's what happens when you try.
Click to expand...
Click to collapse
...I didn't say it had to do with multitouch? It is a global problem, not just apparent in some apps. This seems to be a bug in how the phone handles two points being touched too quickly. This should not happen.
Sent from my ADR6300 using Tapatalk