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.
Hi all. Has anyone with a T-Mobile Ameo got Pocket Mechanic working on their device?
It's just that I have downloaded several demo versions (recent ones from Anton's website) and earlier 2.xx versions, and whilst they all install and display fine, I never have the buttons visible at the bottom of the screen to actually activate any of the modules.
It's a right royal pain. I just want to test the defrag options within it, to see if it is worth my while.
Anyone experience this? If not, I got me problem.
Any know of any other freeware or if need be commercial app that will allow me to safely defrag my SD card and Micro drive?
Any help appreciated.
Pocket Mechanic Pro...Incompatible with HTC WM5?
Handango.com reports that there are no WM5 HTC devices compatible with Pocket Mechanic Pro.
Surely this is rubbish. Anyone care to enlighten me/all of us?
http://www.handango.com/PlatformPro... Mechanic&R=92570&productId=92570#compatible1
I use version 2.32.175 without any issues
Doodle said:
I use version 2.32.175 without any issues
Click to expand...
Click to collapse
Well I'm glad to hear that. Thanks for your reply. I noticed you have a HTC X7500, just wondering if this a ROM issue with T-Mobile Ameo or just my device now.
Anyone got this up and running on an Ameo and or Dopod U1000?
Not Working on Ameo....
I'm really stumped on this one....I need help...please!!??!! AAaarrrgg.
OK now I got that out of my system.
Can someone with an Ameo either please test out the evaluation copy (any version from 2.3xx upwards) please to see if they get the same problem or wether it's my device.
Apparently it works without issue on the X7500, but on my Ameo it looks perfect, BUT....the execution buttons at the bottom of the screen are not visible in all Modules except the 'Free RAM' module, where it is clearly visible and working as should.
I have tried 4 different versions all with the same problem. I'm stumped!!
I really need this as I'm constantly transferring large files to and from the MicroDrive and Defragging is something I have learnt is necessary on the PC, so I figured it must equally be important on the PPC with such a large HDD/MicroDrive.
Anyway here are some snapshots, 1 with the execution button (the only one) and 2 without (including all remaining modules). I have tried another app which can do Defragging, but was not at all impressed with it.
Anyway thanks in advance for any help or positive input.
works perfectly on my ameo.. Cache set to 4mb.. ameo seems much quicker. Latest version of the developers site.
Maybe try it without WA3 running? What else have you got running that could affect it?
FWIW defragging the microdrive seems to take an age. I think it was going to take 8 hours...
Thanks for your help.
fards said:
works perfectly on my ameo.. Cache set to 4mb.. ameo seems much quicker. Latest version of the developers site.
Maybe try it without WA3 running? What else have you got running that could affect it?
FWIW defragging the microdrive seems to take an age. I think it was going to take 8 hours...
Click to expand...
Click to collapse
Thanks for the quick reply fards. I already tried it without WA3 but no change there. The only other app I don't trust at the mo is Spb Phonesuite. I'll try that. Thanks for the tip...my mind has gone blank!!
Thanks for your help.
fards said:
works perfectly on my ameo.. Cache set to 4mb.. ameo seems much quicker. Latest version of the developers site.
Maybe try it without WA3 running? What else have you got running that could affect it?
FWIW defragging the microdrive seems to take an age. I think it was going to take 8 hours...
Click to expand...
Click to collapse
Thanks for the quick reply fards. I already tried it without WA3 but no change there. The only other app I don't trust at the mo is Spb Phonesuite. I'll try that. Thanks for the tip...my mind has gone blank!!
Just tried that. It's not Spb Phonesuite.
Eureka!! Got it working..but still no graphical buttons!
Suppose the title said it all. I have had to navigate using the keyboards navigation keys and guess how many clicks downwards to the invisible buttons.
Pathetic I know, but at least I can use the application and it defragmenting after a scandisk as I type. Brill.
Yea, mine works on Htc x7500 with version 2.32.175. It could be your WA3 - What color Font is on your today screen. is it black? I have had some issues with pocket mechanic and wa2, I had to change the font color for it to show...Well that was before I removed WA2
Pocket mechanic's newer version with scandisk is a very good app. Each new release gets better and better. I have used the PM since the beta testing. (even listed in the credits)
Is wa3 really better? I really like the idea and functionality of WA, but it always caused issues with my devices...
eagle 1 said:
Yea, mine works on Htc x7500 with version 2.32.175. It could be your WA3 - What color Font is on your today screen. is it black? I have had some issues with pocket mechanic and wa2, I had to change the font color for it to show...Well that was before I removed WA2
Pocket mechanic's newer version with scandisk is a very good app. Each new release gets better and better. I have used the PM since the beta testing. (even listed in the credits)
Is wa3 really better? I really like the idea and functionality of WA, but it always caused issues with my devices...
Click to expand...
Click to collapse
Hey eaglesteve.
No it's definately not WA3 as I tried it without WA but I will give the colour scheme thing a shot under the native O/S theme.
But somehow I don't think that will resolve it either. You see when I activate/execute a module (via keyboard) it takes me to another screen whereby I get to see the missing buttons which I can then click on. Weird!!
As for WA3 beta2....I love it and can't wait to buy the full product. I bought WA2 near the beginning of last year and loaded it up on at least 4 different WM devices that I went through in the last year. It's a must have for me. I hate the default look of WM and the latest incarnation comes with some much needed new features and is very well implemented. I def recommend it.
Pretty stable too for a beta!
Newest Pocket Mechanic bricked my O2 xda trion
Installed the latest version (2.43) this morning as it is stated as a "critical upgrade". Opened PM and elected to run ScanDisk on my storage card. App responded that it would reboot, open in "Safe Mode" and then proceed to scan my card. The unit rebooted and then hung on the Windows Mobile splash screen. Nothing else happened for 30-min. so I removed the battery for another 30-min. This cycle has been repeated several times with and without the storage card installed but nothing has restored operability to my phone. I have contacted Anton about this but other than his questions regarding which file I downloaded from his site (it was the .cab file for WM5) I have heard nothing further.
Looks as though my phone will need a hard reset - just hope I have a salvageable storage card.
JayBee
sorry to hear that Jaybee, that's messed up. I no longer trust Antons software and will be deleting PM as soon as I have completed this post.
Did you know that a few versions ago he apparently released a version of PM that had malicious code in the app to format or corrupt your memory card? now that was all about striking back at cracked versions of his software. I'm all for developers protecting their investment, but not at the expense of peoples expensive gadgets, especially when weighed up against software which only cost a few measely bucks in comparison!!
This type of action also gave some of his genuine customers problems.
Nah,sorry, i'm done with his software.
PM
I have reported the bug to Anton and he told me the was a major bug in the 2.42 version which only appears in WM5. Now they have released the 2.45 version. Beware, after installing and using scandisk with safe mode my device frooze while booting. I had to hard reset my device to get it working again.
I'm using version 2.30.172 with no problem at all. I have all the buttons that are missing is Mackaby007's unit.
Which Athena do you have?
eaglesteve said:
I'm using version 2.30.172 with no problem at all. I have all the buttons that are missing is Mackaby007's unit.
Click to expand...
Click to collapse
Hi eaglesteve.
What unit do you have? X7500, Dopod or Ameo?
mackaby007 said:
Hi eaglesteve.
What unit do you have? X7500, Dopod or Ameo?
Click to expand...
Click to collapse
Mine is a Dopod.
eaglesteve said:
Mine is a Dopod.
Click to expand...
Click to collapse
That would explain it then. The Dopod ROM seems much better put together than the Ameo ROM.
I'm relieved. Software differences will be resolved in the future.
I just had the infuriating problem of not locating the action/dialog buttons for Pocket Mechanic (and I'm a newbie to WinMobile - just got my HTC TyTNII last Friday).
Turns out it's something to do with the system fonts (and/or font size). One of the FAQs at PocketMechanic website (Wizcode.com) states that:
If the buttons at the bottom of different Pocket Mechanic Professional module dialogs are missing or misplaced you need to adjust the system font properties of your Windows Mobile Device. Symptoms always appear after the default system font settings are changed (most often by a 3rd party application).
Pocket Mechanic Professional missing buttonsThe current implementation of MFC libraries could cause the buttons (and other dialog controls) to be incorrectly positioned on dialogs if the default system font is changed. The MapDialogRect API that is used for mapping controls on a dialog takes into account the system font properties when calculating the positions of the controls but it doesn’t seem to do that correctly on Windows CE. The side effects of that are oddly placed dialog controls when using a non-default system font. Sometimes the controls will be position outside the visible are of the dialogs thus making them unusable.
Click to expand...
Click to collapse
I must've messed around with that earlier (changed to Tahoma 8pt or 9pt) either with Tweaks 2K2.NET or some other tool.
I've now set it to Segoe UI (and 8pt) , and the dialog buttons are back.
Another problem that manifested from the initial changing of fonts was that the tabs to configure Journal Bar (at the bottom of the screen) had disappeared as well.
Now they're back.
Hope this helps.
Well done!
Hi,
I was wondering if any one has tried using a palm emulator on their Shift and if so which program. I tried running a program called styleTap on the Win Mobile side but o luck and the program just freezes up when opened. I am looking to run programs from a treo 680 which is one of the latest Palm software if I am not mistaken. Any help would be greatly appreciated.
Thanks
It's possible
StyleTab (shareware) works on the Shift!
To get it working you need QuickMenu (free) once.
Install QuickMenu
Install StyleTab and YOU CAN'T REACH OK on the nag screen!
Open QuickMenu and turn screen right.
The StyleTab screen is completely displayed.
Goto Optons-display size and choose original.
Restart StyleMenu
Turn screen back to narmal orientation
(Delete QuickMenu)
Install all your palm apps but hacks.
Enjoy your original size IIIc on this big screen.
Start paying after 14 days...
re
Thanks man I am going to try this and post comments.
Turn screen BEFORE installing StyleTab or the WM side freezes...
But after a restart from Vista side you can still turn the page and start StyleTab again.
I like it as most programs work (NO hacks, NO DA files)
re
I tried this and now I can see the OK button but for some reason I cannot click on it?? any thoughts? Also which version are you using?
I use the pocket pc version from http://www.styletap.com/downloads.php
The smartphone version uses keys only!
At the moment I'm reinventing my IIIc on the Shift...
re
Hi,
That is the one I am using, but not able to do anything, for some reason the alignment is off too. If i want to click register I need to click way higher than where the actual button is. What other software do you have installed? any help is appreciated.
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 there!
Could anyone owning a HD2 check how SPB Mobile Shell 3.5 is running on it?
Software Trial:
http://www.spbsoftwarehouse.com/pocketpc-software/mobileshell/download.html
That's an interesting question. I have just put SPB MS 3.5 on my TP and it completely disabled my Touchflo. If that were to happen on the Leo then I would think it might stop the capacitive screen working.
I've had MS on every windows device I've ever owned (5 of them) yet this might be the first time I stick with TF3D....the new 'sense' as it's being called looks so good it might just be the thing that I want.
TF3D was all form and no fucntion, it was far to difficult to perform any real use and just increased the number of presses and swipes needed to actually do anything. The new one doesn't seem to suffer the same thing....but I'll only be able to tell once I get my hands on it
Tomo1340 said:
If that were to happen on the Leo then I would think it might stop the capacitive screen working.
Click to expand...
Click to collapse
Why would it stop the screen working?
vangrieg said:
Why would it stop the screen working?
Click to expand...
Click to collapse
WM 6.5 isn't designed for capacitive screens, I suspect that HTC have programmed it to work in the TouchFlo3.5 Sense UI, as such disabling it could potentially render the screen useless.
Tomo1340 said:
WM 6.5 isn't designed for capacitive screens, I suspect that HTC have programmed it to work in the TouchFlo3.5 Sense UI, as such disabling it could potentially render the screen useless.
Click to expand...
Click to collapse
the start menu works as well as the other native microsoft screens. I doubt sense has anything to do with the screen actually working. IN fact, there are devs ripping sense out of there and making a lite version of the Leo ROM as we speak.
mallman said:
the start menu works as well as the other native microsoft screens. I doubt sense has anything to do with the screen actually working. IN fact, there are devs ripping sense out of there and making a lite version of the Leo ROM as we speak.
Click to expand...
Click to collapse
What would a lite version of the Leo ROM actually include if Sense is ripped out?
Tomo1340 said:
WM 6.5 isn't designed for capacitive screens, I suspect that HTC have programmed it to work in the TouchFlo3.5 Sense UI, as such disabling it could potentially render the screen useless.
Click to expand...
Click to collapse
TouchFlo is ONLY a front screen interface and in no way takes over the control of your device from Windows Mobile. Im sure the correct drivers and everything are in place to make the capacitive screen work perfectly with WM6.5 or you wouldnt be able to run any of the standard Windows Mobile Programs from the Start Menu.
TouchFlo can easily be disabled through the Today screen settings and other front screen interfaces such as Mobile Shell run in its place. The 2 cannot run side by side but as with any other phone you can turn 1 off and start another quite easily.
The only problem with newer Windows Mobile versions such as 6.5.1 is that they have a menubar at the bottom for easy operation of the Start Menu, ok button and other things. From my experience this menubar isnt disabled when Mobile Shell is installed meaning that it overlays the bottom menubar in Mobile Shell, which in turn causes problems. Im sure spb will fix this problem as WM advances and adds more touch friendly functionality.
The things that said capacitive on WM was unsupported are utter rubbish. What it requires is an OEM to write drivers for it. Since HTC have done this, it's supported.
Manila is just a UI enhancement, it's not anything to do with the screen, the drivers etc.
l3v5y said:
The things that said capacitive on WM was unsupported are utter rubbish. What it requires is an OEM to write drivers for it. Since HTC have done this, it's supported.
Manila is just a UI enhancement, it's not anything to do with the screen, the drivers etc.
Click to expand...
Click to collapse
But it's a UI enhancement designed to increase usability on a device with a capacitive screen. Without the new version of Manila you won't necessarily have access to the HTC-skinned versions of WM6.5 utilities, which means you'll be back to using software that is designed to be used with a stylus on a platform that doesn't support stylus use.
I only took a short glimpse into a Leo ROM, and it's different from, say, Topaz/Rhodium ones in that Manila is broken into more packages (Core, Music, Settings, Footprints etc.). So it might theoretically be possible to use just some Manila features if someone bothers to actually investigate the opportunities and do an insane amount work required to materialize them.
Fair comments, I was under the impression that the drivers were part of HTC sense. Also that HTC sense is designed to not be turned off so easy. So from that I drew a natural conclusion that if you were able to turn Sense off, or an application forced it off like SPB MS3.5 does then that would make the drivers not function as they were part of the working Sense UI.
mskip said:
The only problem with newer Windows Mobile versions such as 6.5.1 is that they have a menubar at the bottom for easy operation of the Start Menu, ok button and other things. From my experience this menubar isnt disabled when Mobile Shell is installed meaning that it overlays the bottom menubar in Mobile Shell, which in turn causes problems. Im sure spb will fix this problem as WM advances and adds more touch friendly functionality.
Click to expand...
Click to collapse
On my TYTN2 with WM 6.5.1.23053, there's no overlay with MS3.5. Not sure what build of MS you are using but for me it's just fine.
I have tested MS3.5 on Acer F1 (same CPU as HD2) and it was very smooth. However, when going in landscape, it was slower than my TYTN2 in landscape. It could be a graphic driver issue, which I hope won't be on HD2.
Righto guys - got the SPB Mobile Shell 3.5 trial installed on my MD2 - what do you want me to test?
It has a very Android feel to the OS - kinda parallex scrolling background...
Once installed, it disables the Sense UI.
WildWayz said:
Righto guys - got the SPB Mobile Shell 3.5 trial installed on my MD2 - what do you want me to test?
It has a very Android feel to the OS - kinda parallex scrolling background...
Once installed, it disables the Sense UI.
Click to expand...
Click to collapse
MD2? I think we already sorted out that it will work fine with TouchFLO disabled LOL
mskip said:
MD2? I think we already sorted out that it will work fine with TouchFLO disabled LOL
Click to expand...
Click to collapse
Sorry meant HD2.
I didnt disable TouchFlo - it did it itself.
One thing i've noticed, if you enable hardware acceleration on the SPB, the whole 'carosol' goes slow and unresponsive...
I thought it would be better as the HD2 is meant to use OpenGL?
oh no, not again! no drivers......
WildWayz said:
Sorry meant HD2.
I didnt disable TouchFlo - it did it itself.
One thing i've noticed, if you enable hardware acceleration on the SPB, the whole 'carosol' goes slow and unresponsive...
I thought it would be better as the HD2 is meant to use OpenGL?
Click to expand...
Click to collapse
I guess it depends how spb makes use of hardware acceleration enabled devices. With it turned off it should still run very fast and smooth so not too much to worry about i think. You should install one of my MS3.5 themes (in my sig) and see how it looks I think it would look nice with ProPlus Elegance and all the extra widgets
4pe said:
oh no, not again! no drivers......
Click to expand...
Click to collapse
The HD2 has OpenGL drivers as proved in this stress test against the original HD *HERE*
WildWayz said:
Righto guys - got the SPB Mobile Shell 3.5 trial installed on my MD2 - what do you want me to test?
It has a very Android feel to the OS - kinda parallex scrolling background...
Once installed, it disables the Sense UI.
Click to expand...
Click to collapse
Cool WildWayz! Thanks a lot, I'm just happy that it works and doesn't have quirks of one or the other kind
Yes you should try and mess around with some of mskip's stuff if you like
Maybe you can say how the general feel is? Speed/smoothness -how is it on the capacitive screen? And I don't know if you intend to keep on using it -but it would be very interesting to hear if there is an effect on battery life..
cheers!