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.
Here is an Enhanced D3D Driver for our Touch Pro2. Before you install driver run the D3DDemo file from your phone. Extract D3DMDemo.exe and copy it anywhere on your phone (Storage Card is good). Run it and see how slow it runs with the default D3D Driver. Then install At0mAng Enhanced D3D Driver.cab, restart and run the D3DMDemo again and see the difference
Enjoy!
Just to make things clear. I did not develop the driver, it was from the Samsung Omnia and the libgles_CL.dll comes from NuShrike. I have been using it since my TyTN II days, gave it a shot on the Rhodium and it worked. I did not see it in this forum so I cabbed it up (was OEM in my kitchen) and posted it.
The cab file contains two dlls both from the D3DM driver and the correct registry settings for d3dm_ati.dll.
To learn more about this driver and to try newer releases please see this thread
http://forum.xda-developers.com/showthread.php?t=496528
There have been a few reports that the drivers from above thread break a couple of things like the G-Sensor with Opera so I am posting back the original file I had up. Strange since I do not have that problem with the latest drivers from the above thread.
It's up to you to decide which drivers you would like to use.
Rocks!
TF3D is realy faster.
walter79 said:
Rocks!
TF3D is realy faster.
Click to expand...
Click to collapse
Cool...glad it is working on other devices.
Been using this driver since the TyTN II then to Raphael and now on to Rhodium Not sure if it is a good or bad thing that the same driver works on the last 3 devices I have...
Wow! It really worked and the M3D really is faster!
Cheers mate!
-ilari
On the Telus (MSM7600) it went from 0.85 ish FPS to a smooth test. Very dramatic change
Same for me here too
is it really faster?
does it mean, that the video-playback is also better?
TF3D is using OpenGL ES or Direct3D? If it's written for OpenGL ES the new drivers should not have any impact over it. It's only my opinion.
Any ideas?
Just to let you know I also went from 0.75 FPS to about 25 FPS.
Crazy change, just don't notice much difference in TF3D.
what's the difference between this and neo's beta 3d driver pack?
snek_one said:
Just to let you know I also went from 0.75 FPS to about 25 FPS.
Crazy change, just don't notice much difference in TF3D.
Click to expand...
Click to collapse
Same opinion. But I cannot see fps in the demo after installing the new driver.
The increase in fps is recognizible high in the demo. The object first is absolutely stuck without the driver. With the driver installed it runs fluidly.
in this demo I have a big boost with this driver !!
Whith games work with that driver? My old quake dont work on my TP2
Will this work on MSM 7201 chipset as well? I don't want to make hardreset again if something will going wrong on my TP1. Thanks.
Edit>
Nevermind,I tried it. Unfortunately no visible change happens on Raphael.
No Change
It made no difference on my Touch Pro 1
I installed it on Touch Pro2 and test runs a lot faster. And also TouchFLO 3D runs more smoothly. I don't know why, but it's really faster. I think TF3D2 uses OpenGL-ES and Direct3D driver can't change it's performance.
TomasNM said:
Will this work on MSM 7201 chipset as well? I don't want to make hardreset again if something will going wrong on my TP1. Thanks.
Edit>
Nevermind,I tried it. Unfortunately no visible change happens on Raphael.
Click to expand...
Click to collapse
Strange I thought it should so I have been using it with my TP1. I never did try the demo though to see if it actually worked.
great great work At0mAng
i have tested in my HD and workly very very well
Difference in the Demo is quite noticeable.
will this driver accelerate need for speed undercover or xtrakt as well?
Seems to work awsome. Thanks.
I asked this elsewhere, but this is a better place to post i think.
Is it possible to have Windows Mobile 6.0 run on the HTC Touch HD? If so, what ROM would I need? I want an English version. I need to run some software on it which doesnt work with WM6.1 and WM6.5
roms have to be 100% custom made with just the correct drivers for it to work on a device
it would be a first if a rom cooker spend too much time cooking an older version then what came with the device be it wm6 or wm5 for that matter
so would not hold my breath
Shame, we needed to get ~80 of these downgraded to WM6.0 for the software to work. I wonder if Orange would accept 80 returned phones
Have sw compatibility problems? I used on WM6.1 all programs from WM5 w/o problems ^^
80 Devices? You could PM directly a cooker and ask him about your problem: you could find a solution
D'rath
avisonjohn said:
Shame, we needed to get ~80 of these downgraded to WM6.0 for the software to work. I wonder if Orange would accept 80 returned phones
Click to expand...
Click to collapse
80!?! Holy crap?? What are those 80 HDs used for??
It could be possible but you would need to find WVGA resolution files for the WM 6.0 SYS build first. I don't think there were any WM6.0 WVGA devices.
Got a load of phones that we issue to satellite engineers for work. We have a bit of software than rubs on the phones and the engineers use it to get customer information, allocate stock to the customer, activate the customers hardware and subscription services ect.
We have never been able to get it to work with WM6.1 or WM6.5
It gives some error about graphics or display or something along those lines.
We currently use the HTC Kaiser (TyTnII) which came with WM6.1 and we had to flash them all to WM6.0 for the software to work.
Without the software, all the staff are unable to work.
Also, is there a way that I can install certain software and configure settings on a windows mobile device, then make a backup of that device and flash it to all the other devices? Its just that having to flash 80+ devices to windows 6.0 and then install framework, then software, then setup messaging and GPRS settings and a few other dependencies can be time consuming (about 30mins per device). When this is done for 80+ devices, well....you get the idea...
Have you tried WVGA fix?
http://forum.xda-developers.com/showthread.php?t=455974
With this you can change the screen to VGA which the program might work with.
avisonjohn said:
Also, is there a way that I can install certain software and configure settings on a windows mobile device, then make a backup of that device and flash it to all the other devices? Its just that having to flash 80+ devices to windows 6.0 and then install framework, then software, then setup messaging and GPRS settings and a few other dependencies can be time consuming (about 30mins per device). When this is done for 80+ devices, well....you get the idea...
Click to expand...
Click to collapse
Yes, you can do this with backup software like Spb Backup.. it backs up the phone's installed software and registry to a file which you can execute on another phone so that it is restored to the exact same way as on the original phone.
Or you can use something free called Sashimi.
Another thing is, if the ROM has User Customization built in, you can have the ROM look for a file called SDConfig.txt on your storage card, which contains a list of CAB/XML files on your SD card to execute automatically after a flash.
rovex said:
Have you tried WVGA fix?
http://forum.xda-developers.com/showthread.php?t=455974
With this you can change the screen to VGA which the program might work with.
Click to expand...
Click to collapse
It will most definitely be the WVGA resolution that is stuffing the software up, all issues with software not running under windows 6.1 on the HD are caused by one of two issues:
1) Software dependencies, ie. Compact Framework version - I have never came across a software dependency issue that cant be fixed
2) WVGA vs VGA resolution, and in this case with it being a graphics issue you will definitely be able to get it running using the WVGA fix quoted by rovex.
All you need to do is install the WVGA fix, do a soft reset and use the program to change it to VGA mode before launching your application which wont work, i can all but guarantee this will fix the problem, of course the only issue is you will have to change the res before launching the app all the time.
I would also suggest you contact the manufacturers of the software (or if its in house contact your in house development department) and tell them to make it work in WVGA resolution, this should only be a minor change, after all they dont need to move all the controls around just ensure it loads even it dosnt use the whole screen.
TheToid said:
It will most definitely be the WVGA resolution that is stuffing the software up, all issues with software not running under windows 6.1 on the HD are caused by one of two issues:
1) Software dependencies, ie. Compact Framework version - I have never came across a software dependency issue that cant be fixed
2) WVGA vs VGA resolution, and in this case with it being a graphics issue you will definitely be able to get it running using the WVGA fix quoted by rovex.
All you need to do is install the WVGA fix, do a soft reset and use the program to change it to VGA mode before launching your application which wont work, i can all but guarantee this will fix the problem, of course the only issue is you will have to change the res before launching the app all the time.
I would also suggest you contact the manufacturers of the software (or if its in house contact your in house development department) and tell them to make it work in WVGA resolution, this should only be a minor change, after all they dont need to move all the controls around just ensure it loads even it dosnt use the whole screen.
Click to expand...
Click to collapse
I tried using that tool, but it still didnt work. Instead I just got a screen saying "We're Sorry" and something about cprog.exe has stopped working.
We have been told that it needs to be run on version 1.81.61.2 on the Kaiser, apparently this is the display or graphics version or whatever that is required for it to run, but im thinking this is the number that shows on the bottom right of the device when powered....
Anyway to find out exactly whats causing this error or any other work around?
avisonjohn said:
I tried using that tool, but it still didnt work. Instead I just got a screen saying "We're Sorry" and something about cprog.exe has stopped working.
We have been told that it needs to be run on version 1.81.61.2 on the Kaiser, apparently this is the display or graphics version or whatever that is required for it to run, but im thinking this is the number that shows on the bottom right of the device when powered....
Anyway to find out exactly whats causing this error or any other work around?
Click to expand...
Click to collapse
I would suggest talking to the developer/manufacturer of the software your trying to get to work to see if they can modify it to work WVGA resolution. This would most likely be your easiest route, especially when all new devices will be on wm6.5 or later and not compatible with wm6.0
Fallen Spartan said:
I would suggest talking to the developer/manufacturer of the software your trying to get to work to see if they can modify it to work WVGA resolution. This would most likely be your easiest route, especially when all new devices will be on wm6.5 or later and not compatible with wm6.0
Click to expand...
Click to collapse
Yes, if the WVGA fix dosnt work then I can only assume that the software has been specifically designed to be locked to only work on the Kaiser phone, the only way you are going to fix this is to contact the manufacturer or employ a software engineer to reverse engineer the software and make it work on the HD, which could be costly and time consuming.
Hi,
in all the Reports about the HD2 they allways say "Multitouch" but i was not able to find out, how many touches at the same time the HD2 can recognize.
Is there anyone who has an answer for me?
greetz
virtually unlimited.
so is there an application around which uses more then two right now?
So far I've only seen dualtouch on HD2. But it might be capable of more than just dualtouch..
LOL
Physically the hardware may be unlimited but WM 6.5 can only support 1 touch!!!
HTC worked around this for the PZ in Sense, but there is no native support for multitouch at all.
WM7 Should do though so keep waiting and hoping..............
i see! thanks for that!
hopefully microsoft and htc will hear our prayers!
That is not entirely true. WM6 might not support multitouch officially. That does not mean HTC does not use it's own extensions. It does.
You must enable multitouch for each application in similar way as rotate (there is white list in registry). Then new events are sent to the window, which allows you to use more 'cursors' at the same time. Of course application must be made to support that. I've seen some demo (which only showed 2 cursors actually), and there was documentation too, unfortunately I can't remember where it was.
i'm using toshiba G810..wm6.5.3
i have a question that is can my phone use sense 1.2/1.5/2.1
how can i use sense?
another qusetion.i crashed when i use xdandroid..
is there any method to help me to use android? i dont' want android kid..
please help me!
From what little information I can find about your device, I doubt you can run Sense on your device. The G180 has a QVGA screen, so it won't be able to run any version of TF3D other than the original QVGA port of TouchFLO 3D. It's probably not going to work though, as TF3D pretty picky about what it runs on, what requirements it has, etc. My advice is that it's not worth it, and you should maybe look of TouchFLO 2D.
XDAndroid is designed for a select few HTC devices, like the Raphael, Blackstone, Diamond, Rhodium, and Topaz. XDAndroid will only work on those devices at this time, as hardware support must be added for each additional device for it to work. Using it on another device, like your Toshiba Portege G180, will not work. The only way for it to work is if developers port XDAndroid to your device, there's nothing you can do to make it work.