Database Develop

almost-real keypad on a touchscreen

I heard from a friend that someone is building a phone where the touchscreen keypad is almost as easy to feel as a physical hard-button keypad.
The virtual buttons (0-9, *, #) are spread out in a typical rectangular grid over the whole screen, with large gaps between them. When you (lightly) move your finger across the screen, it vibrates as your finger is passing over any button. If you want to actually press the button, you have to push your finger against the screen harder (this event is acknowledged with a beep).
This sounds like a great interface. Has anyone seen/heard of it? It also seems relatively easy to implement on any PocketPC, unless there are some problems that I'm not aware of.
I'm using one application that uses vibration as a feedback -- Phone_Pad_Vibrate.cab. However, it vibrates only when you actually press a button. I think it's a great app, but obviously its purpose is very different from what I'm talking about (e.g., it won't help you find the right button if you just shift your finger around the screen). Also, I found that it's not reliable -- if I use fast, light touches, I can dial a whole number without any vibration. It may be due to the lag between the button press and the vibration, or due to the different pressure threshold used by this program and the actual phone dialer. If it's the lag, I wonder if it's a technical limitation of the Kaiser.

The screen on the Kaiser (and most other PocketPCs) isn't pressure sensitive, that is, it can tell when you are pressing, but not how hard. You would need a special screen to achieve that.

You are talking about screen technology more advanced than most PocketPCs are currently equipped with. the iPhone has what is generally regarded as the most advanced touch screen in a mass produced product. The software would need to implement it, but the screen's hardware would need to be able to do it in the first place.

D Pad left and right is difficult

Hi All,
Is it my phone or is it a problem with the diamond in that I find it almost impossible to use the d pad to go left and right. Up and down works a treat, but left either makes a call or goes to the home page and when I want to naiviagte right, well it mostly causes the centre dpad to click. Any ideas, send the phone back; it's almost impossible to play worms!

i have the same problem. i think it is not a manufacturing problem, it is designed as is.
i have seen somewhere in the manual, that htc recommends to use the finger nails to press the navigation buttons.

Same behaviour here. It's just bad design. Not a fault of your particular device.

Thats so Cr*p!, don't get me wrong, I love the phone, but that is bad manufacturing, I though HTC were better than that. I am disappointed that they get everything else so nice, but screw up the nav keys, they are pretty damn important. It like saying the that the "T" key on the keyboard sometimes gives you "T" but sometimes it'll give you "R".!! Anyone tries talking to HTC about it?
Oh well, I'll just roll over and take it --- again

Hi there,
just keep in mind that the navigation left/right uses the same (physical) switch as the other buttons. the function called is just determined by the position of your fingers on the capazitive touch element. So you just hav to be quite precise. pressing with the whole of your thumb can cause the problems you state. use your fingertips instead and everything will be fine.

in the beginning I had some trouble but my problem was that I pressed too close to the centre button... I have no problem pressing left or right now. The sweetspot is about the middle between the edge of teh circular button and the home/phone keys

KnOeFz said:
in the beginning I had some trouble but my problem was that I pressed too close to the centre button... I have no problem pressing left or right now. The sweetspot is about the middle between the edge of teh circular button and the home/phone keys
Click to expand...
Click to collapse
I also find it helps to press a little bit lower than you might think (especially on the right button)

slow23 said:
just keep in mind that the navigation left/right uses the same (physical) switch as the other buttons. the function called is just determined by the position of your fingers on the capazitive touch element.
Click to expand...
Click to collapse
Hey, wow. Thanks a lot. That's really the point.
Ever worried about pressing one of the other buttons (Home, Back, Send, End) when pressing to far outside the center. But now that I realised that there are no other buttons to accidently hit, everything works quite fine.

would be great if someone finally finds out how to remap buttons. in that case i am the first to reassign the home button with the left key and back button with right key...

Wish it would be possible to touch the wheel and get LEFT/RIGHT instead of pressing them. Would make it so much easier to use the wheel/pad buttons.

axelpix said:
Hey, wow. Thanks a lot. That's really the point.
Ever worried about pressing one of the other buttons (Home, Back, Send, End) when pressing to far outside the center. But now that I realised that there are no other buttons to accidently hit, everything works quite fine.
Click to expand...
Click to collapse
The hint was also very usefull to me, thank you so much slow23, you made my day
regards,
Daniel

Remap light wheel for up down left right
Now that sounds like a wicked idea. Remap it so that when the touch sensitive circular wheel is not being used for it's whizzy ipod type wheel capability, it is instead used for touch sensitive left, right, up or down!.
Hmm, I'd donate for sure for that to happen!

funny thing about those hardware keys is that they are combined with a capacitive key, eg, try to press the home key with the back of your stylus without touching the button with your finger. it wil respond as dail key pressed.
If you try to press al the buttons at once, there is only one click at either side

[Q] It Anyone Else Having Touch Button Problems?

Is anyone else experiencing the occasional mixup when hitting the back button? As not always, but many times regardless of the application thats open, I'll hit the back button and the search will come up and I wondering whether thats a common problem or a sensor in my phone is defective and I need to exchange it for a new one...
Thanks in advance

im having a different problem with the buttons. a lot of times my first touch wont register and i have to press it multiple times for it to be recognized.

I've noticed that my touch buttons aren't as sensitive as the touchscreen, and that I need to use a lot of pressure to get them to activate on the first try.

not alone there.. same issue here. I have a clear screen protector over them though.. though it shouldn't be a problem.. I've had the issue even before the protector so..

I have a problem with the back button too, not the other ones. However, when I press a spot a little to the left of the back button and not exactly over the button, it seems to register the press correctly.

I have found that the buttons just do not like any other finger than the index finger try to use the thumb and it will go to search or do nothing.I also returned my first phone as the buttons were terrible 80 percent of the time they would not work.So there maybe be a flaw in some of the phones as this one works fine even with the phantom skins on.The first phone would not even register a response with the skin on.

The buttons on the Captivate suck.
Buttons, as a construct, are well known.
The functional priority of the button is not a mystery and hasn't been for 100 years.
It has to click or otherwise give the user an indication the button has been pressed far enough to take effect.
It has to be tacticle. You have to have some way of knowing that your finger is on the button before you press it.
You have to have some leverage to put enough force on the button to make it move.
It has to be about the size of a finger tip.
It has to be visible. If you can't see it you can't press it.
It has to be different than other buttons that are millimeters from it.
It has to react the first time you press it, or you will naturally press it again, achieving unwanted results.
In all of the above, the Captivate fails.
The T-Mobile Galaxy has more a lot more real estate below the buttons to allow your fingers to get on to them, and a raised ridge on the rear surface of the phone exactly to give your other fingers something to grip against to increase aim and pressure.
But the Captivate has a nice lot of space at the top OH YEAH!

The only problem I have with the buttons is that I can't see them in a dark room
Sent from my SAMSUNG-SGH-I897 using XDA App

I'm getting something similar. Sometimes when I hit the home button the search button blinks as if I had pressed it, then brings up the search screen. On my first captivate (mfg. date 7/16) sometimes it would happen once out of every hundred presses and sometimes it would happen 3 out of 5, very inconsistent. I traded that one in for one with a later manufacturing date (8/10), and my new one does it too but maybe only 1 out of every 100-200 presses. The fact that the search button blinks makes me think it's some kind of short/hardware issue. The back button has only triggered a search for me once, and that was on my first phone.

So this is a hardware issue or a software issue?
My back button on my phone must be pressed 4-5 times sometimes before it will register. The phone did not have the issue when I got it, and a friend of mine who has the Captivate as well does not have this issue.
It may be my imagination, but the phone seems to register touches better after I run a task killer or after restarting the phone, but tends to have issues when multiple apps are up and running.

I was having a button problem as well but fixed it by upgrading to JH3. h t t p://forum.xda-developers.com/showthread.php?t=767666
Your mileage may vary but it worked for me.

May be my imagination, but it seemed to be more isolated to back button on JH3 than JF6 on my machine. My perception is that if I take an additional half-second pause before pushing back button it registers more often. Do not believe it is hardware though. I believe that your home page(button), settings (button), and search(button) all reference something that resides in permanent memory(ROM) whereas the back(button) is trying to recall something that is in temporary memory (RAM) and possibly similar to lag issues may be related to Samsungs somewhat proprietary file allocation system. I am by no means computer literate enough to ponder concept any deeper than just mentioned.

I was having a problem with pushing the home button and the search would come up. I took it to a AT&T store and because I was still in the first 30 days they swapped it out for me.

i'm having a completely different issue with my touch buttons. my back button will register multiple button presses even when i'm nowhere near it. it's quite frustrating to be in the middle of an app and all of a sudden the back button goes off 3 or 4 times and gets you back to the home screen. i've tried searching the forums for some resolution or to see if someone else has had this, but not yet.
Edit: I must not have searched thoroughly enough, found another thread on this issue. http://forum.xda-developers.com/showthread.php?t=858873&highlight=back+button+issue&page=2

Bad spen behaviour

Hi,
The SPen of my n7000 is not working properly. After a few seconds "writing", it stops writing. Some seconds later it begins again. Then stops.... intermitently. It seems like there is a problem in the pressure sensitivity or something. The problem began some months ago, first failing once in a while only, then more and more frequently, to the point of not being usable today.
Funny thing is that the cursor is shown correctly, it never stops moving. The spen only stops "writing".
Ok, so I bought a new SPen. The new one writes only when I press the button (and I have to press hard). When I don't, it does not write, unless I use the pen almost parallel to the phone. Cursor is shown fine too. Still, it seems it works OK only when I keep pressing the button. But then there's other problem: the pen writes even if not touching the screen, so writing decently is impossible. Quite similarly like here: https://www.youtube.com/watch?v=viDDKGPj2FI. I took off the pen's button, but then there is no potentiometer inside (as opposed to the original spen).
Any idea how to fix this? How to tell the spen to keep the button pressed by default, or to rever behaviour? Which system file does control this?
Thanks!
L.

unusable on windows tablet: touchscreen mouse mapping incorrect

I am using a Samsung TabPro S and I cannot navigate within RemixOS because the mapping of my touchscreen input to the curser within Remix is totally wrong. The mouse pointer is always some few cm away from the point where I touch the screen.
Impossible to correctly navigate.
I could use the trackpad though, but I don't want to.

I'm having the same problem...
I'm on a surface pro 4 and if I try to change orientation the screen gets confused.

Same problem on a Windows 10 Asus N550LF Touchscreen Notebook, i.e. mouse cursor basically stays where it was when I touch the screen, and just clicks. I can only use the trackpad, but then, what's the point of having the touchscreen to run android apps?
Also, when I tap and hold, mouse cursor goes into select mode or drag and drop, but with no accuracy on mapping position.
Also, trackpad scrolling (with two fingers) is jumpy, inaccurate.

jide is jeremy, ben and david: "and we're here to take it to the next level"
boys,
just try to focus on the basics first, get it done, then talk about the "next level"

same here on surface pro 4. I tried everything without success.