Related
Can anyone get their hands on the TouchFLO UI CAB so we can give it a try on the Athena? The functionality was released on the HTC Touch in the UK. Maybe someone can get the CAB off of the HTC Touch and we can give it a try on our Athenas.
http://www.htctouch.com
Check out the TouchFLO try me link at the bottom of the page.
ltxda said:
Can anyone get their hands on the TouchFLO UI CAB so we can give it a try on the Athena? The functionality was released on the HTC Touch in the UK. Maybe someone can get the CAB off of the HTC Touch and we can give it a try on our Athenas.
http://www.htctouch.com
Check out the TouchFLO try me link at the bottom of the page.
Click to expand...
Click to collapse
Now that is nice. Especially if it worked in landscape on the Athena.
Indeed. Very interesting.
I'll be looking for it too.
HTC's Touch is QVGA....
From what I've read of the specs, the HTC Touch is a QVGA device without 3G!
If the Cube Touch software is anything like the QVGA HTC Audio Manager I've seen, it will look pathetic on the Athena.
IMHO, it needs to be in a VGA device before it's worth considering installing it to the Athena and preferably a device with similar if not same hardware and software features, in order for all things to be accessible through it's interface.
Having said all that, I read somewhere recently that the Advantage comes with HTC Audio Manager (supposedly no better or worse than WMplayer), but at least natively VGA.
The Touch GUI looks great, but I know one thing for sure, if it lives up to the hype and actually allows better and more intuitive navigation through finger-touch, you can bet your bottom dollar that some big software developers like Spb will be on the bandwagon to produce an even better variant of it.
Great for the rest of the PPC community, whether VGA or QVGA.
May be it has something to do with screen build quality as well....I have a feeling that even though if we install all the interface cabs for "multi touch input method", still Athena screen will not be able to support it.
Does it has anything to do with screen build quality?
few reviews on HTC touch:
http://www.engadgetmobile.com/2007/06/05/htc-touch-hands-on/
http://www.gsmarena.com/htc_touch_with_touchflo_technology-news-274.php
mackaby007 said:
From what I've read of the specs, the HTC Touch is a QVGA device without 3G!
If the Cube Touch software is anything like the QVGA HTC Audio Manager I've seen, it will look pathetic on the Athena.
IMHO, it needs to be in a VGA device before it's worth considering installing it to the Athena and preferably a device with similar if not same hardware and software features, in order for all things to be accessible through it's interface.
Having said all that, I read somewhere recently that the Advantage comes with HTC Audio Manager (supposedly no better or worse than WMplayer), but at least natively VGA.
The Touch GUI looks great, but I know one thing for sure, if it lives up to the hype and actually allows better and more intuitive navigation through finger-touch, you can bet your bottom dollar that some big software developers like Spb will be on the bandwagon to produce an even better variant of it.
Great for the rest of the PPC community, whether VGA or QVGA.
Click to expand...
Click to collapse
I want to give it a try. I see your points but am curious about it working and potentially enhancing the UI. From the demo it looked like a nice new toy to have. I'm thinking it's similar to what they did with the iPhone theme where you had the slider lock, etc. If you can at least swap screens and make custom menus using TouchFLO, that would be great. As for the phone it was released on...shame on HTC for putting something like this on such an inferior device ;-)
Nara-e-Mastana said:
May be it has something to do with screen build quality as well....I have a feeling that even though if we install all the interface cabs for "multi touch input method", still Athena screen will not be able to support it.
Does it has anything to do with screen build quality?
few reviews on HTC touch:
http://www.engadgetmobile.com/2007/06/05/htc-touch-hands-on/
http://www.gsmarena.com/htc_touch_with_touchflo_technology-news-274.php
Click to expand...
Click to collapse
I don't think so but I could be wrong. For example, the iPhone theme uses slider bars, etc and can be loaded onto the Athena, with a little help of third party software. I hope someone posts the CAB so I can test it out. I'll load it and report my findings if someone can get it.
Nara-e-Mastana said:
May be it has something to do with screen build quality as well....I have a feeling that even though if we install all the interface cabs for "multi touch input method", still Athena screen will not be able to support it.
Does it has anything to do with screen build quality?
few reviews on HTC touch:
http://www.engadgetmobile.com/2007/06/05/htc-touch-hands-on/
http://www.gsmarena.com/htc_touch_with_touchflo_technology-news-274.php
Click to expand...
Click to collapse
It isn't multi touch.
Or have I missed something?
ltxda said:
I want to give it a try. I see your points but am curious about it working and potentially enhancing the UI. From the demo it looked like a nice new toy to have. I'm thinking it's similar to what they did with the iPhone theme where you had the slider lock, etc. If you can at least swap screens and make custom menus using TouchFLO, that would be great. As for the phone it was released on...shame on HTC for putting something like this on such an inferior device ;-)
Click to expand...
Click to collapse
Gotta agree with you ltxda. I still want to try it too.
i think it would be great. i know there are other softwares that use this interface. so i think ppc is capable but its all about the software limitation.
If were lucky, alan from the HTC Touch post can investigate this for us as he has just acquired such a device.
http://forum.xda-developers.com/showthread.php?p=1301886&posted=1#post1301886
mackaby007 said:
If were lucky, alan from the HTC Touch post can investigate this for us as he has just acquired such a device.
http://forum.xda-developers.com/showthread.php?p=1301886&posted=1#post1301886
Click to expand...
Click to collapse
That's awesome! Great thinking mackaby007! Can't wait for him to reply and maybe send us a CAB or two.
Bad news so far...
This is what Paul of Modaco has reported so far;
"Random Touch trivia after spending some time today 'digging around'...
- The screen has it’s own new driver version (touch.dll). This means the TouchFLO interface won’t port to other devices. In fact, I tried it - just to be sure - by installing the driver on my Trinity, and the touchscreen stopped working ohmy.gif
- The fancy today screen plugin is just that, and would be easy for HTC to drop onto any device.
- Out of the box I feel the sensitivity of the screen is a little lacking (it occasionally misses clicks or taps from my finger or stylus), however this seems to be configurable in the registry – watch this space
- The Touch has a new version of HTC’s ‘Task Manager’ (close button) application, a new Camera application, and a very nifty network wizard for setting up GPRS settings. These settings are held on the device in a passworded ZIP file!
- NO PHONE PAD T9 ON THE TOUCH! What the hell were they thinking? I had a good moan to our HTC about it, and demo’d what Phone Pad would be like on the Touch... wink.gif
- When you boot the device, it does the email config (you know, the one that connects to the server to get settings?) and then the config of the data connection. Duh! Wrong order!
- All the IR drivers etc. are in ROM despite their being no IR port!
- The fancy UI takes up a lot of memory
- Audio Manager, Comm Manager and the Phone Dialler are all grey-skinned to match the homescreen UI. It looks real nice biggrin.gif
smile.gif
P"
Not looking good at the mo, but let's not give up hope.
mackaby007 said:
This is what Paul of Modaco has reported so far;
"Random Touch trivia after spending some time today 'digging around'...
- The screen has it’s own new driver version (touch.dll). This means the TouchFLO interface won’t port to other devices. In fact, I tried it - just to be sure - by installing the driver on my Trinity, and the touchscreen stopped working ohmy.gif
- The fancy today screen plugin is just that, and would be easy for HTC to drop onto any device.
- Out of the box I feel the sensitivity of the screen is a little lacking (it occasionally misses clicks or taps from my finger or stylus), however this seems to be configurable in the registry – watch this space
- The Touch has a new version of HTC’s ‘Task Manager’ (close button) application, a new Camera application, and a very nifty network wizard for setting up GPRS settings. These settings are held on the device in a passworded ZIP file!
- NO PHONE PAD T9 ON THE TOUCH! What the hell were they thinking? I had a good moan to our HTC about it, and demo’d what Phone Pad would be like on the Touch... wink.gif
- When you boot the device, it does the email config (you know, the one that connects to the server to get settings?) and then the config of the data connection. Duh! Wrong order!
- All the IR drivers etc. are in ROM despite their being no IR port!
- The fancy UI takes up a lot of memory
- Audio Manager, Comm Manager and the Phone Dialler are all grey-skinned to match the homescreen UI. It looks real nice biggrin.gif
smile.gif
P"
Not looking good at the mo, but let's not give up hope.
Click to expand...
Click to collapse
If he wants, have him give us the passworded ZIP file. I'll try to crack it.
I guess we'll have to have someone take a look at the dll mentioned above and see what can be done about that...if there is enough interest.
Maybe we could at least have the today plugin? That looks pretty sweet.
Touch.DLL
I Have a T-Mobile Wing, and I have the Touch.dll file in \Windows . . . (Touch.dll 26.9k 3/21/07 21:21.04)
It came that way, does that mean that TouchFlo may work on my device?
2 things i do not like:
mackaby007 said:
- Out of the box I feel the sensitivity of the screen is a little lacking (it occasionally misses clicks or taps from my finger or stylus), however this seems to be configurable in the registry – watch this space
- The fancy UI takes up a lot of memory
Click to expand...
Click to collapse
pretty dissapointing but to be expected i guess.
Just grab yourself Wisbar, and the graphics file and youll be 2/3rds the way home and hosed to recreating the Interface.
Osir1s said:
Just grab yourself Wisbar, and the graphics file and youll be 2/3rds the way home and hosed to recreating the Interface.
Click to expand...
Click to collapse
Well see, we're not trying to recreate the interface, we're trying to get the actual app from the actual source and see if it works. Please try to contribute to the thread instead of making ambiguous statements!
WarezAppz said:
I Have a T-Mobile Wing, and I have the Touch.dll file in \Windows . . . (Touch.dll 26.9k 3/21/07 21:21.04)
It came that way, does that mean that TouchFlo may work on my device?
Click to expand...
Click to collapse
Just maybe, you never know. I can't remember which post I read, but I do recall it mentioning that the the screen is a new techology and another report that that would not make it a standard WM6 device (I remember now, a discussion at 4winmobile.com about the HTC Touch etc..). Anyway, that makes sense + fellow member neilm also went on to mention that a lot of current WM5 & WM6 wouldn't work on it as it wasn't written with this type of multi-touch screen in mind.
Fair point I think and follows the logik that HTC haven't built a WM6 device that is incompatible with software written for its O/S. No it's more likely that that .dll is all the software needed to make that plug-in (shell or whatever) interface with any WM touch screen.
So, WarezApps, if you have the .dll by default, it could mean that your device is capable of running the plug-in with the screen driver you seem to have, as they may have considered selling it as a default app within your device, but possibly recognized the potential to knock out another new device (for more money), which will appeal to some people just for this particular touch interface!
I think it will work with that Touch.dll screen driver.
Can you upload your file for us all to share and examine.
Anyway bottom line: I think it's all about transferable software now and just want to try it for myself to see.
Okay,
So I am a power user, and that might be putting it lightly. When it comes to deciding between the Mogul and the Touch, I want the Mogul. Well, I DO want the Touch because its thinner, but I couldn't stand using a touch-screen keyboard with my fingers (or even worse, a stylus). I need a separate keyboard that doesn't take up any screen space while browsing.
What I'm curious about is this: Are the touchscreens on the Mogul and the Touch actually different? Forget dimensions etc., but i mean in terms of the technology, are they the same? If they are the same, then all the current hacks to try to turn the Mogul into a Touch-like phone will eventually (who knows how long) mature enough to work almost identically, is that correct?
madador03 said:
If they are the same, then all the current hacks to try to turn the Mogul into a Touch-like phone will eventually (who knows how long) mature enough to work almost identically, is that correct?
Click to expand...
Click to collapse
They are indeed the same, last I checked. There was a rumor that the touch would be multi-touch (ala Iphone), but clearly that wasn't true. The term "touch" merely relates to the suite of touch-centric software that actually sits on top of WM.
That's right, there's nothing fancy about the touch that you can't do with the same software. That software, I'd like to add, has already been extracted as .cab files that can be installed on virtually ANY WM5 or WM6 HTC pocket pc.
So, I don't know what this "maturing" is that you're talking about, or why you think it would be "almost" identical... its the same darned thing!!!
The stuff that's being developed currently is to take it beyond the touch, and more like the finger scrolling iPhone interface.
All of the stuff, I'd like to point out again, sits on TOP of Windows Mobile, meaning its just a program that can sometimes get in the way of how WM was actually designed to work.
Sometimes its convenient to have, but in general, I find any of the touch / finger / iphone add ons to be more trouble than their worth, and that goes for the ACTUAL htc touch as well!!
Dishe said:
They are indeed the same, last I checked. There was a rumor that the touch would be multi-touch (ala Iphone), but clearly that wasn't true. The term "touch" merely relates to the suite of touch-centric software that actually sits on top of WM.
That's right, there's nothing fancy about the touch that you can't do with the same software. That software, I'd like to add, has already been extracted as .cab files that can be installed on virtually ANY WM5 or WM6 HTC pocket pc.
So, I don't know what this "maturing" is that you're talking about, or why you think it would be "almost" identical... its the same darned thing!!!
The stuff that's being developed currently is to take it beyond the touch, and more like the finger scrolling iPhone interface.
All of the stuff, I'd like to point out again, sits on TOP of Windows Mobile, meaning its just a program that can sometimes get in the way of how WM was actually designed to work.
Sometimes its convenient to have, but in general, I find any of the touch / finger / iphone add ons to be more trouble than their worth, and that goes for the ACTUAL htc touch as well!!
Click to expand...
Click to collapse
Um... please show me where I can download the touchflo interface that works exactly like the touch. All the versions I've gotten require the use of buttons instead of touch, and are extremely buggy. If you you know of a cab that gives the mogul all the touchflo features, by all means let me know...
my suggestion, if you have Sprint...wait
Sprint's versio of the HTC Touch is apparently due out in November. It'll be only a matter of time before someone extracts those cabs and/or creates a new touch-based, CDMA-based rom that can be more easily ported to the mogul.
I for one am interested in the new on screen keyboard interfacethe new touch is supposed to have...
I tried using the other method to get the home-brewed (button-based) touch, but I ran into a few problems and uninstalled.
Quick question.
Does or can wm6 support multi touch hardware?
The touch from sprint will have twice the memory (128mb ram) - i don't know about you guys, but I'm constantly filling up the supposed 64mb realistic 47mb really 17mb after cache/etc of memory that this device has...
-mark
Is the iPhone the only one with a multi-touch interface? What is the next phone that will have it?
I'd like to know if you have any problems with Astronavigator on Touch HD.
I have installed it and as soon as go in the menu for changing location, the application freezes
I'd also like to know if there's any similar program, which uses gps to define current location...
Tnx
Andrej
Same for me: app freezes
yep
fine till you change location - then freezzzzz
here the same...no sulotion in the pas half year?
here the same...no solution in the past half year?
I've tried running Atronavigator on both HTC shift and Touch HD, the stuff just freezes.
But... if you de-select all the stuff on the map, once in a while, you can get to the location part, I was even able to get a fix one time and see the soft. as it should be.
On the shift, it's even harder to get it working, one must reboot, kill activesync,kill all the other stuff like GSM/Radio, kill the stars, planets and the rest and..
you might get lucky once in a while...
possibly it's due to the origins of my file...
Same here; just freezes when trying to locate position or even when wanting to input position manually on Touch HD
Hi,
It's Working with WGAFIX.
WGAfix ?
I guess you mean WVGA Fix(.cab) to switch to VGA, I first was confused into downloading WGA fix for XP :-(
This looks like the place to get it.
Incidentally, the freeze happens with the version legitimately downloaded from vitotechnology.com. I sent a request to their support 3 weeks ago, and then by email, haven't heard from them.
The previous version (astronavigatorII 1.2) works fine though...
goulniky said:
I guess you mean WVGA Fix(.cab) to switch to VGA, I first was confused into downloading WGA fix for XP :-(
Where do I get this anyway?
Incidentally, the freeze happens with the version legitimately downloaded from vitotechnology.com. I sent a request to their support 3 weeks ago, and then by email, haven't heard from them.
The previous version (astronavigatorII 1.2) works fine though...
Click to expand...
Click to collapse
Not sure if this is the WVGA fix your talking about
yeah, that's the one. I find that I need to do a soft reset to switch back from VGA to WVGA with that program, but that's fine.
The good news is, once you've set the astroNavigatorII location in VGA mode, you can return to WVGA as everything else works, and it 'cookies' your location. So, as long as you don't move to a distant location, you'll be able to enjoy the app.
Wow, I've been looking for a suitable app that can rival the iPhone's Starmap. Doesn't look like Vitotechnology are too reliable though... No fix for the problem in however many months, and no replies to tech support requests?
More annoying though, I go to their website and find they have an iPhone app themselves called Star Walk 3.0 which has all sorts of goodies like GPS/Digital compass etc, whilst the Astronavigator app for Windows Mobile phones seems to be stuck in a development freeze with a location feature that doesn't even work properly on our phone!
iPhone virtual machine?
from what I can judge, Astronavigator is nowhere as impressive as Starmap, still more expensive, no editing, scant documentation. The navigation / screen gestures are also quite confusing. Haven't used Starmap though.
I guess what we need is an iPhone emulator running under WM6
while the gigantic 4.3" helps in making everything finger (or even foot) friendly, its still a windows mobile device. and many of the apps require some precision are written to be used with a stylus. i cant imagine using "Pocket Artist" or copy and pasting text using my finger on a WM device.
You guys think that this will be a problem with this device.
it's not a problem on the iphone, why should it be a problem on a device with a bigger screen? I don't remember ever using the stylus on my HD...never needed it. I don't expect I'll need it on this device either
twisted-pixel said:
it's not a problem on the iphone, why should it be a problem on a device with a bigger screen?
Click to expand...
Click to collapse
Because iPhone applications are written on the assumption that they are being used on an iPhone without a stylus. Plenty of Windows Mobile apps are written on the assumption that you are using a stylus; this includes a number of utilities built into the operating system.
I used the Leo ROM on my Xperia X1 and can say as long as you stay inside windows (or said different inside the shipped software) you won't get any problems, its very finger friendly and I never went down to an old wm 6 skin. concerns are only there if you want to use some 3rd party software. there might be a problem with finger usage like said above or somewhere else as they don't have to be finger optimized.
Personally - I think it will be fine. Also with later revisions of WM6.5 and then hopefully WM7 I think the phone will get easier IF there are any issues. The issues will only occur when you come out of the HTC Sense layer anyway, which won't be that often.
I thought HTC patented the capacitive stylus?
Lack of stylus will not be a issue at all with that huge screen...I think. We see when its in our hands. Hope it will be very soon
I'm using a TyTN II and almost never dig out the stylus. Over time I moved to apps that were finger friendly. And with the current design trends, I'm guessing even more apps will become available that don't require a stylus.
-Bob-
12aon said:
I thought HTC patented the capacitive stylus?
Click to expand...
Click to collapse
afaik yes but on no pics can you find where it is placed i think and then they will probably release it with a largish price tag like the car dock...
All of you who are using resistive screens with LEO ROM, your impressions are worthless (regarding how the LEO ROM will behave on the real HD2) because resistive screens are more accurate than capacitive screens, even if you use just your finger (not to mention you can still use fingernail with resistive).
HTC said that since the LEO has capacitive screen, it can not operate well without the new MANILA, and for that reason, they said that they didn't give an option to disable MANILA, and went even further to say that if some programer will try to disable it, they did everything they could in order for him to find it "very challenging".
Noam23 said:
All of you who are using resistive screens with LEO ROM, your impressions are worthless (regarding how the LEO ROM will behave on the real HD2) because resistive screens are more accurate than capacitive screens, even if you use just your finger (not to mention you can still use fingernail with resistive).
HTC said that since the LEO has capacitive screen, it can not operate well without the new MANILA, and for that reason, they said that they didn't give an option to disable MANILA, and went even further to say that if some programer will try to disable it, they did everything they could in order for him to find it "very challenging".
Click to expand...
Click to collapse
What makes you say this? There have been plenty off leo roms out that seem to leave that function intact
Noam23 said:
All of you who are using resistive screens with LEO ROM, your impressions are worthless (regarding how the LEO ROM will behave on the real HD2) because resistive screens are more accurate than capacitive screens, even if you use just your finger (not to mention you can still use fingernail with resistive).
HTC said that since the LEO has capacitive screen, it can not operate well without the new MANILA, and for that reason, they said that they didn't give an option to disable MANILA, and went even further to say that if some programer will try to disable it, they did everything they could in order for him to find it "very challenging".
Click to expand...
Click to collapse
I don't use my Touch Diamond's stylus, and the Touch Diamond has a much smaller screen so I think the huge screen of the HD2, coupled with the capacitive touch sensivity, should be fine.
And if that second bit is true, I'm surprised because that means they went to the trouble of making it easy to disable TouchFLO 3D and TouchFLO on older devices...
And if that second bit is true, I'm surprised because that means they went to the trouble of making it easy to disable TouchFLO 3D and TouchFLO on older devices...
Click to expand...
Click to collapse
True, because the TouchFLO 3D and TouchFLO were sold on devices with *resistive* screens, these devices can handle Windows Mobile screens without any trouble. The HD2 on the other hand has the capacitive screen, and HTC knows that operating the WM UI with such device is going to be a problem, such a problem that no one even believe capacitive will reach WM before version 7.0, yet HTC came with the MANILA 2.5 solution, so I can very much understand them when they say they don't want you to defeat MANILA 2.5.
O2 are offering me this phone as an upgrade. I need a decent keyboard and am loathed to part with my TP2!
Does anyone have any experience of using any of the screen "keyboards" for emails etc? If so, can it really replace the hardware keyboard?
May be a silly question, I don`t know much about different screen types but cant you just use another stylus instead of your finger? I always have a pen/stylus in my pocket at work and never use the provided stylus with my HD
kjt57 said:
May be a silly question, I don`t know much about different screen types but cant you just use another stylus instead of your finger? I always have a pen/stylus in my pocket at work and never use the provided stylus with my HD
Click to expand...
Click to collapse
You need a special kind of stylus for capacitive screens.
http://cgi.ebay.co.uk/NEW-CAPACITIV...ries_MobilePhoneBatteries?hash=item2ea897a251
Noam23 said:
All of you who are using resistive screens with LEO ROM, your impressions are worthless (regarding how the LEO ROM will behave on the real HD2) because resistive screens are more accurate than capacitive screens, even if you use just your finger (not to mention you can still use fingernail with resistive).
HTC said that since the LEO has capacitive screen, it can not operate well without the new MANILA, and for that reason, they said that they didn't give an option to disable MANILA, and went even further to say that if some programer will try to disable it, they did everything they could in order for him to find it "very challenging".
Click to expand...
Click to collapse
Very interesting information Noam23. Being able to use a phone effectively with your finger most of the time when you have to use your finger all of the time is not acceptable to me.
I also have the same issue mentioned in your other post where I would want to turn off Manila/HTC-Sense. The fact that they've tried to prevent this proves how unusable WM6.5 is on a capacitive screen.
Oh well, that's just saved me a lot of money!
Can't help but think everyone is being a little binary here
The UI is the launch pad for the device ... It will be possible to disable TouchFlo3D. HTC were probably saying this to detract people from the ever present concerns with exposure to the native OS UI.
All the other apps you use on the device have their own UI. Once launched, it is almost (back to that in a moment) irrelevant what the OS UI is. The concern will be if those desktop class apps we love on WM in spite of WM itself are not easy to use on the HD2.
I don't see many apps I have that will be a problem ... infact, the only ones would be Resco Explorer, utilities like SKtools, data entry tools like Softmaker Office and PhatNotes (although I'll probably be ok with the on screen keyboard given the capacitive touch and size of display ... and for laptop 'replacement' use, I'll use the BT Stowaway keyboard and mouse) and drawing tools .... which some I'm sure want .... I personally (and therefore subjective) have never used them ... so it isn't an issue for me.
It is true to say that PI and Flexmail could do with more focus on touch ... and given the iPhone apps Alex was working on (I'm a little out of date) ... I'm sure that will come soon.
Also .. I'm not sure if it waning enthusiasm or a change of focus ... but having used PI extensively for years ... when using Mobile Shell 3 and things like PocketBreeze, I realised I rarely went to PI any more .... With FlexMail ... it is a superb product ... but it always had problems with storage ... and after the WM client supported HTML ... it was less needed ... with TF3D ... again ... makes it even easier ... so PI will remain for micro text month view and tasks ... FM will remain for when I need to do complex searches of mail (a real weakness of the native clients on all phones), but I will rarely touch them in normal daily use.
So ... although I resisted the 'hype' around capacitive ... and thought a stylus would always be needed .... in practice ... I'd like to get an HTC capacitive stylus if it ever makes it off the drawing board ... but I doubt I'll really need one.
I used to always want the keyboard ... but after having 4 TyTNs and 3 TyTNIIs respectively before I got one that didn't have some keyboard or mech / ribbon issue .... and the TP2 that had the loose mech issue ... I finally decided I wanted to simplify all mechanical bits ... so I'm looking forward to the HD2. I like others think the 5 buttons + the rocker will allow aebutton+ control where needed in older games.
And the benefit to the Capacitive screen for me will be a smoother more responsive touch (I'm not commenting of accuracy ... because no one that hasn't used it can really comment ... and they certainly can't comment on what it maybe like if and when the HTC Stylus comes out ... if it does) .... and it should also be less reflective ... and therefore clearer in different light conditions ... and it will have a harder surface ... which will (to me) feel better.
So in summary ... given TF3D or MS3.5 will cover most of the OS UI requirements ... as well as the front end to native apps which are touch optimised and most of the big apps I will use will be fine with their own UI ... I think the HD2 with it's display and external simplicity has hit the market at the right time and will in practise be more than fine for everyone happy with a device this size that doesn't need drawing apps on day one.
I also suspect that the internal 512M + a good fast 16 or 32 GB MicroSDHC will more than meet the requirements of the WM7 1 chassis .... and in a year or 18 months ... when I have itchy feet .... I will get a ROM from XDA .... that will rejuvinate the machine ... I can't say this for certain ... and no one at present can say it will or won't be a possibility ...
Mine is on order for Clove ... it is genuinely the first time I've been excited about a WM device since the TyTNII was announced ...
Moandal said:
Very interesting information Noam23. Being able to use a phone effectively with your finger most of the time when you have to use your finger all of the time is not acceptable to me.
I also have the same issue mentioned in your other post where I would want to turn off Manila/HTC-Sense. The fact that they've tried to prevent this proves how unusable WM6.5 is on a capacitive screen.
Oh well, that's just saved me a lot of money!
Click to expand...
Click to collapse
Maybe you should try it before drawing any conclusions?
Really interested in seeing how Opera performs on the HD2 and whether or not clicking links is difficult.
It's easy to tap small links on the iphone, why should it be difficult on the HD2? All this "it won't be possible to use because of the capacitive screen" debate is just FUD, IMO.
i've just read about sdk that allow smartphone with windows mobile and resistive screen to have multi-touch.
now the question:
is there a similar project for android device like tattoo?
rossonero92 said:
i've just read about sdk that allow smartphone with windows mobile and resistive screen to have multi-touch.
now the question:
is there a similar project for android device like tattoo?
Click to expand...
Click to collapse
ralle.gade is currently working on including this in his kernel for Kiljacken's ROM
No,
ralle.gade don't work with MT now, becouse we have to wait when Wildfire kernel releases..
i see
i wish it comes fast
it isn't a real MT.. just emulating it thrugh the sw.
a real multi-touch is impossible and I think is very hard dev a software to do it..
we'd need a "hook" (maybe a "+" on the screen) to hang the position of the finger and then do the second move to do something (like rotate images..)
Wikipedia says resisting screens can support multi touch along with this reference
www.umpcportal.com/2009/02/multi-touch-comes-to-resistive-touchscreens/
I've even found that this company 'stantum' is also developing multi touch for resistive screens
i.engadget.com/2009/02/19/stantums-mind-blowing-multitouch-interface-on-video/
It basically requires the device to understand the position of both fingers along the XY coordinates and then process them accordingly.
Sent from my HTC Tattoo using XDA App
any news about MT?
hello man, the problem is that the screen hw tattoo is kind of capability, and is a hardware limitation to not support multitouch,
you could try to emulate it via sw but from what my experience is of counsel to give up, too much work for an outcome that would at most just enough
... and that is why tattoo is so cheap