HTC Touch Diamond/Pro has multi-touch after all! credit[wmpoweruser.com] - Touch Diamond, MDA Compact IV General

ref: http://wmpoweruser.com/?p=693
Touch Diamond owners will know that the navi-wheel on the front of the device is capacitive, and can measure movement without actually rotating. Like many HTC devices, it seems the Touch Diamond and Pro have hidden features, and pretty tasty ones indeed. Using an application called Nav Debug Tool by HTC, this video shows not only is the navi-wheel capacitive, but that the whole front of the device can track finger movements, and even two fingers independently.
So far there is no know feature on the Touch Diamond/ Pro that exploits this, but once our developers get their hands on the API it wont be too long. This also promises that even current generation devices with resistive screens will be able to take advantage of multi-touch features in WM7.

this has been known for ages and was posted several times before. Its already usable by shapps TouchXperience UI... -.-
just use forumsearch before posting

It's not multitouch. The left and right side are two different "modules". Try, using the utility, to multitouch just one side and see what happens.

kikakeule said:
this has been known for ages and was posted several times before. Its already usable by shapps TouchXperience UI... -.-
just use forumsearch before posting
Click to expand...
Click to collapse
Do you mean to say there is API out there to use this feature? If so, where?

weblance said:
It's not multitouch. The left and right side are two different "modules". Try, using the utility, to multitouch just one side and see what happens.
Click to expand...
Click to collapse
This is a good way for testing I think!

Related

this is cool, future touchflo

http://www.youtube.com/watch?v=3LRbkHOllLA&eurl=http://msmobiles.com/news.php/6755.html
soo is this available as an update
if that was a real sales pitch count me out - a poor attempt to try and mimic the iPhone, they should innovate like their slogan instead of following behind.
Only new feature is the zoom - but honestly how many use your pda as a camera/picture viewer. Now if they also upgraded the camera so as to be on par with nokia's lens' and the n95's spec then I would agree with the R&D in this area.
forgot about the rotate feature...something tells me it would be easier to press the rotate soft key.....
overall you can tell that I am not happy with this upgrade. Sure it can't do no harm but I think that their time could have been spent researching new features yet to be seen by Windows Mobile.
how about a cube like this on your herald?
http://forum.xda-developers.com/showpost.php?p=1552994&postcount=292
that cube looks pretty nice...lovin the skin. I am actually working on my own cube, trying to make a 6 sided cube (although i'm startin to think it will become quite aggravating to find a side quickly if you are in a rush...whaddya think) with some custom animations. recently inspired to make it into a matrix theme.
not sure if you have seen this thread but it makes it quite simple. YOu should try and implement it into your kaiser port
http://forum.xda-developers.com/showthread.php?t=325424
and btw in regards to the first post the gurus over at pocket cm seemed to have pretty much mimic most of the features from the new touchflo in their pocketcm picture viewer. Give em some time and it will be better than HTC's version, im sure of it.
I know of that link. thats where i got the one i posted
I am folowing that thread to see if there is anything I want to use.
BTW. having more "sides" on the cube is ok idea, but making one that wont kill memory is a tough one my brother in law is a compter programmer, and im talking with him about a multisided cube, maybe there is coming something cool from that part in a while but no promises
about the kaiser port, we will see, first I have to make it work flawless before thinking about what to put in it.
sounds good, keep us all posted on any future developments.
as for the original topic...we all know HTC use Qualcomm chipsets in the past. Maybe with this new deal of AMD liscensing the new graphics technology introduced in the xbox360 (Unified Shader Architecture) to Qualcomm, we should be able to be able to have the memory from the animations use a dedicated graphics card (graphics card in ppc is not new -i think the flame has one)....just imagine OpenGL 2.0 running ported on a pocket pc. Possibilities are unimaginable right now. I think this is where HTC's R&D money should be going....but for all I know its already in the making...one can only hope
yeah that would be a giant step forward.
Im hoping its not so, but im afraid they will take tiny mouse steps forward, just so they can sell more phones.....they know we are addicted, and will buy.....lol
itje said:
yeah that would be a giant step forward.
Im hoping its not so, but im afraid they will take tiny mouse steps forward, just so they can sell more phones.....they know we are addicted, and will buy.....lol
Click to expand...
Click to collapse
yeh for sure, its proven already that they only include one maybe two major upgrades per phone. Much more profitable marketing scheme. Just gotta know which phones to get, the people who purchase the Tytn II are going to be getting a pretty good phone that should b around for long. Where as a phone like the HTC Touch will get outdated pretty quick (Touch Dual already in production.) I'm sure when phones begin to be released with graphics cards built in they will surely only make them w/o keyboards, then another one with keyboard...then some "New and Improved Graphics Card" that doesn't waste as much battery (which they probably had from the begining.)
I guess you just gotta know to wait for the last one...
itje said:
how about a cube like this on your herald?
http://forum.xda-developers.com/showpost.php?p=1552994&postcount=292
Click to expand...
Click to collapse
Guess the whole cube thing is useless. all of these skins mean nothing - when you use your device, and not just flicking this cube back and forth for hours
Sweet looks cool. I would love that for my phone. When will ver 2 be out? I have a problem with touthflo. I can use the cube once then if i try again it wont load. It just flips up then flips away. I have to soft reset the phone to use it again. Is there a fix for this? I have this prob with any touchflo rom. Even my mda with touchflo does this.
eujene said:
Guess the whole cube thing is useless. all of these skins mean nothing - when you use your device, and not just flicking this cube back and forth for hours
Click to expand...
Click to collapse
The cube thing IS useless ... but you know that EVERYONE wants to have the new touchflo 2 the moment its available .... don't ya? haha
duprade said:
The cube thing IS useless ... but you know that EVERYONE wants to have the new touchflo 2 the moment its available .... don't ya? haha
Click to expand...
Click to collapse
as far as i understand, TouchFlo contains not only Сube. As for me - i want only finger scrolling. And it is still imperfect

Anyone noticed using touch screen in games slows down device?

I mean its ridicolous like games like virtual pool which ran on my 300mhz xscale ipaq at full speed slows to a crawl once I start touching the cue stick or ball onscreen. When I am not touching the screen in any game like ffrace or wolfenstein or duke3d or krally it runs pretty well (though not as fast as a 400mhz xscale of samsung device) but once I touch the screen the graphics slow to a halt. It makes awesome games like call of duty 2 virtually unplayable unless you can set the game to just use the hardware buttons or keypad, but not all games have such an option.
Whats the deal? the HTC Trinity had this problem on earlier roms but I am running Dutty's latest rom with the very latest CE build and it still has this problem.
Welcome in the wonderfull world of the Kaiser. You like gaming ? Don't buy a Kaiser !
About COD2, I also tried to play the game without touching the screen, only by pressing the buttons, but it is very slow anyway (unplayable from my point of view).
But I would be glad if I only had problems with COD2 !!!
ive been trying to find a way to fix this problem, i think it can be done, but i would need a rom cooker? someone who is famaliar with a rom (or device) which it's screen does not slow down when pressed. we may be able to get the touchscreen driver from this device. i know theres someone out there that can help.
Are there any HTC devices which doe
n't slow down when using the touchscreen?
jym04 said:
Are there any HTC devices which doe
n't slow down when using the touchscreen?
Click to expand...
Click to collapse
Not really, you wanna games device? buy a PSP.....
OH sugar.. gonna get shouted at now...
jym04 said:
Are there any HTC devices which doe
n't slow down when using the touchscreen?
Click to expand...
Click to collapse
the Universal, for example. that is, non-2.8) models.
(BTW, i my articles, I've thoroughly disussed this problem and was among the first, 2 years ago,to report the problem to HTC. Too bad they still haven't bothered fixing it..)
it is more than just the touch screen drivers its the Direct 3D and other graphics driver that dont exisit on the Kaiser at all if you would read the other threads there is a large pool of money for the first person to make these drivers and get them working on the Kaiser... HTC screwed everyone with there advertising and I have to admit this phone is ****ing slow for what it should be i think all processors should be atleast 900mhz to make it fast enough for me
Menneisyys said:
the Universal, for example. that is, non-2.8) models.
(BTW, i my articles, I've thoroughly disussed this problem and was among the first, 2 years ago,to report the problem to HTC. Too bad they still haven't bothered fixing it..)
Click to expand...
Click to collapse
As you can tell Menneisyys, people do not want to listen....
Menneisyys has said this many times before the d3d issue came out...
There is a touch screen handler problem in ALL HTC devices..
PLEASE...SEARCH THE FORUM...
Menneisyys said:
the Universal, for example. that is, non-2.8) models.
(BTW, i my articles, I've thoroughly disussed this problem and was among the first, 2 years ago,to report the problem to HTC. Too bad they still haven't bothered fixing it..)
Click to expand...
Click to collapse
Menneisyys,
This problem would pretty much cripple the Polaris/Cruise. Do you think this will be a problem for this device as well. I have posted this question several times, but so far all I have gotten is anecdotal replys about the screen being the same as the Touch. The Touch is also 2.8 screen but some people suggest the screen technology is different, so it works better. I have tried a friends Touch, and it does seem to be better, but not dramatiaclly better and from an external standpoint, all I can tell is that it is flush mounted instead of inset.
So from someone who understands the internals, is there any reason why the screens used for the Touch and (assuming) the soon to be relased Cruise perform better?

Sick and tired! Where is sky map!

I'm tired of all this andriod talk that you can have sky map or google sky map whatever... I want it for htc touch pro windows.... I don't like the boring ones I got I want to be able to move around and look at all the stars while the phone is being move...i dont want to drag with my hand thats lame and outdated...
more comments
less views please
agreed. i want skymap too.
indeed, if i possessed the knowledge or the will to obtain the knowledge.... this app would have been created long ago
you would need a compass in the device to get that type of movement accuracy.
I know someone that has somthing like that for his android, just need to port it to wm.
t0y0da said:
I know someone that has somthing like that for his android, just need to port it to wm.
Click to expand...
Click to collapse
and his android device also has a compass.
any sort of augmented reality program will not run usably on our devices. the gsensor just isnt enough. we can define y axis and x axis, but no z axis. which is what the compass does, it gives the device a control, a constant, a place that is always going to be the same. it can then use the other relevant info from the accelerometers to always know exactly how the phone is positioned.
run one of the xandroid builds, install skymap, and just try to use it. if youre some how able to get it lined up, and move VERY slowly, you might be able to get it to work. again, one small jerk of the phone, and you will be looking through the screen in a totally different area.
the only wm phone i know of with a compass built in, is the hd2. there might be another one, but i never heard about it.
hartleyshc said:
the only wm phone i know of with a compass built in, is the hd2. there might be another one, but i never heard about it.
Click to expand...
Click to collapse
Sorry to bring up this old topic, but the Omnia II also has a compass.
bobzero said:
Sorry to bring up this old topic, but the Omnia II also has a compass.
Click to expand...
Click to collapse
Thats good to know.
Does the Omnia II have a capacitive touch screen or is that just the Leo?

How many Touch Points on Nook Color and if we can have more?

So I just downloaded and tested this app called MultiTouch and realize that our Nook Color just has 2 touch points instead of an Apple IPad, which has 10 touch points. If you do not know what touch points are, it's the number of fingers you can register on a multi-touch device all at one time. For 2 touch point, the Nook Color can only detect 2 fingers at once on it's screen. Well my question here is, is there going to be a way later on to modify the hardware/software to allow more than 2 touch points? Or are we stuck with 2 touch points forever because of Nook Color hardware limitations?
what do you need more than 2 touch points for? I am honestly curious.
For 250 a piece this tablet isn't going to survive for too long. At least among us rooters.
devis said:
For 250 a piece this tablet isn't going to survive for too long. At least among us rooters.
Click to expand...
Click to collapse
Can you clarify that?
Anyway, I see that once you touch more than 2 points it blanks out all the touch..
I discovered that when using an emulator and needing the third touch point..
bruceleroyjr said:
So I just downloaded and tested this app called MultiTouch and realize that our Nook Color just has 2 touch points instead of an Apple IPad, which has 10 touch points. If you do not know what touch points are, it's the number of fingers you can register on a multi-touch device all at one time. For 2 touch point, the Nook Color can only detect 2 fingers at once on it's screen. Well my question here is, is there going to be a way later on to modify the hardware/software to allow more than 2 touch points? Or are we stuck with 2 touch points forever because of Nook Color hardware limitations?
Click to expand...
Click to collapse
The iPad is designed for finger typing like a full QWERTY keyboard.The Nook Color is not. So really any more than two points is not necessary or even usable on this device.
deitiphobia said:
The iPad is designed for finger typing like a full QWERTY keyboard.The Nook Color is not. So really any more than two points is not necessary or even usable on this device.
Click to expand...
Click to collapse
Not necessarily true. My Droid Incredible, up until about two weeks, ago, at least that's when I saw it it on the forums, only had two point multi touch. It now has 10 point multitouch thanks to a custom kernel. I think it has more to do with the kernel than the actual digitizer, or whatever capacitive screens use to detect touches. it would make sense that since the nook can detect a point anywhere on the screen that software could be written in the form on a custom kernel to detect more than one at once. Of course this is all pure speculation about the nook as I know pretty much nothing about capacitive screen technology. If anyone else can shed some light or reeducate me, fell free.
http://forum.xda-developers.com/showpost.php?p=9736804&postcount=7
Already a thread on this here...
http://forum.xda-developers.com/showthread.php?t=868826
spikey911 said:
Can you clarify that?
Anyway, I see that once you touch more than 2 points it blanks out all the touch..
I discovered that when using an emulator and needing the third touch point..
Click to expand...
Click to collapse
I mean this is a cheap tablet. Lots of potential, yes, but unless it can do Gingerbread I don't see it being used for too long.
deitiphobia said:
The iPad is designed for finger typing like a full QWERTY keyboard.The Nook Color is not. So really any more than two points is not necessary or even usable on this device.
Click to expand...
Click to collapse
two words:
Gingerbread Keyboard
devis said:
I mean this is a cheap tablet. Lots of potential, yes, but unless it can do Gingerbread I don't see it being used for too long.
Click to expand...
Click to collapse
i actually see it being used for quite some time by "normal" users.
now for us xda'ers i definitely agree.
cal3thousand said:
two words:
Gingerbread Keyboard
Click to expand...
Click to collapse
I didn't find the GB Keyboard better than any others...
Hi everybody. Are there any new developments on enabling this feature?
I'm also interested in more than 2 touch points for certain applications.
My Nook running CM7 detects 2 point touch.
madfatter said:
it would make sense that since the nook can detect a point anywhere on the screen that software could be written in the form on a custom kernel to detect more than one at once
Click to expand...
Click to collapse
... what?
califrag said:
http://forum.xda-developers.com/showpost.php?p=9736804&postcount=7
Already a thread on this here...
http://forum.xda-developers.com/showthread.php?t=868826
Click to expand...
Click to collapse
According to that post, it's a software limitation and not hardware. Does anyone know if it could be added or does no one care? I love my $250 tablet and the only thing that sucks is the 2 point touch. Like the OP said, after two fingers it just blanks the touch to nothing. Seems like even that could stand some work. The NC seems to freak out if you put too many fingers on it. I've been annoyed with this for a long time.
Any updates on this?
Will the Nook Tablet or the Kindle Fire also have these limits?
Bootstrap Bill said:
Any updates on this?
Will the Nook Tablet or the Kindle Fire also have these limits?
Click to expand...
Click to collapse
Kindle fire has this limit as well. I don't know about Nook Tablet
---------------------------------
Sent from my LG Optimus V using Tapatalk

N1 dual touch screen

Anyone here that has the 2.3.3 firmware could report if the multitouch problem of the N1 has been removed ?
It's not removed. It's a hardware problem.
not the kind of news i wanted to hear. i was really thinking of ordering a nexus one tomorrow , but considering the multitouch problem it turns me off.
what is the N1 multi touch problem? I have N1 but didn't notice any problem there. Firmware: 2.3.3
The problem is that it doesn't have true multi touch. It only registers two points, and can't handle it when the axis is crossed with the two points.
Google maps has some clever work arounds for it, though. Since axis crossing makes the standard rotate on Google maps almost impossible, to rotate the maps you have to move two fingers horizontally to rotate (instead of actually rotating the two fingers)...
Sent from my Nexus One using XDA Premium App
Danger-rat, autocorrect didn't act too well on your message
Jack_R1 said:
Danger-rat, autocorrect didn't act too well on your message
Click to expand...
Click to collapse
Thanks Jack - I just cleaned it up...
Sent from my Nexus One using XDA Premium App
i notice this problem, mainly in games where the controls are on the bottom. Many games allow you to shift the dpads and this helps immensely. what specific needs do you have with multitouch?
I tested the problem you're mentioning with a pointer visualizer
it actually detects when the pointers cross the axis, but it seems that there's a software snap that glues the two pointers axis for a while. does not seem to be hardware, but it's most likely a software error correction thing.
siavash79 said:
I tested the problem you're mentioning with a pointer visualizer
it actually detects when the pointers cross the axis, but it seems that there's a software snap that glues the two pointers axis for a while. does not seem to be hardware, but it's most likely a software error correction thing.
Click to expand...
Click to collapse
It has been discussed many times before, this is a hardware limitation caused by HTC using the ****ty clearpad 2000 digitizer. Software no matter how well it is written will only be able to solve so much because the fault lies in the hardware.

Categories

Resources