This project is about rebuilding the touch.dll coude from the original dll assembly.
Latest package:
touch.cab
For adding the "developers certificate" ( read side node on update 21/11/08 ) you can use the following tool:
Microsoft Security Configuration Manager
--------------------------------------------------------------------------------------------------
Update 21/11/08:
Ive finally managed to rebuild the touch.dll from assembly and recompiled it and im able to boot the new touch.dll
Ive cleared some of the calls made to some old features implemented in the original file like the touch cube etc.
Be aware that this isnt for daily use and only for testing purposes. But I really need some input on speed and reliability because i cant test everything on my own ( i flash my device every 4 hours or so so not really long testing times ). If you are not affraid of hard resetting your device and are willing to participate in testing current work please do but dont keep me responsible for freezes etc
I have only tested it on udk R4 because its easy for me to test speed on manilla 2d and it gives me a good impression of daily usability. And because i removed almost all calls to the original cube code it wont be any good for cube lovers as and original HTC roms.
Keep in mind that all ive done now has been done during work in a few hours and although ive tried to be on the safe side i cant tell you all is working as its suppose to and I think i havent done more then remove about 20% of garbage out of it.
I know not all is as fast as its supposed to be but like i said im better safe then sorry and i dont wanna hardreset every 2 mins or so... Some good testing can be done in Manila2d like scrolling through images fast and scrolling through the bottom bar. Also ive noticed that scrolling through the normal "All programs" is still on the slow side ( still need to resolve a lot of scrolling issues... HTC has included a lot of codes for all sorts of winmo controls like listviews etc ) but if you open up the all programs in manila from the programs menu u will see what kind of speed it can work at minimum....
As for the priorities mentioned earlier in this thread im going to set both the priority256 and the priorityhigh256 at 109 ( original microsoft value that can be found at msdn ) in the cab file so we can test the touch interface as it was suppose to be set up... you can easily change these values as you like ( read earlier posts ). Setting it lower then 109 will give it an higher priority which will make the device suffer more from touch input... Setting it higher ( upto 255 ) will give the touch input less priority and will make rendering faster but can also come of the cost of reliability.
Side node:
Make sure your rom has the "Sample Privileged Developer" Certificate installed because i signed both the file as the cab with this certificate ( files need to be signed because of being system file and they dont get any trust at boot without a certificate ).
--------------------------------------------------------------------------------------------------
Start 15/11/08:
Ok so because i didnt had much to do this week i started digging into the touch.dll to see if there can be some solutions to the slow scrolling/stuttering etc when touching the screen.
I already found out that the graphics stuttering mostly happens due to the fact that the touch.dll is set to real-time process priority.
WinMo uses priority values from 255 (low) to 0 (real-time).. Normally touch should be set at 109 ( according to msdn ), but because htc put so much garbage in it ( touchflo related ) and it got slow as #@% they put the priority to 0 as a default and deleted the registry entries
Using IDA i found out that those registry values are still being accessed but since they are not there the default of 0 is used.
Just create the following key
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch
And create the following values in it
Name value (DWORD)
Priority256 255
HighPriority256 255
This will not speed up the actual scrolling but it will also not make the device freeze when pressing the screen... So scrolling seems more natural. ( especially in programs folder and file explorer )
So this is not a fix but a good start for now.
Already found out a few things looking at the code that can be dropped out so im going to try to rebuild the touch.dll from asm without most time expensive calls ( hopefully shrike will help me out on this one ).
Let me be the first to say thank you. I am not sure I did the things right, but my Polaris seems more alive than ever. I will post an exported regkey, please confirm that I've done it correctlly.
I have noticed an improvement in sliding in S2U2 and on everything that involves touching the screen. This indeed is a great step forward for Polaris.
Thanks for trying... As soon as development will progress ill create a cab file which will include the registry keys.
Big difference... great job,
I've noticed though that in icontact, when you scroll contacts, the animation has to finish so that it can accept new gesture, so i set it to 109, scrolling is still good and icontact work propertly..
Great find Rogro! Was irritating me how the graphic stutters whenever I scroll in programs and phonebook..
Just wondering though, if it was such a simple fix, why did they remove the reg key to begin with? as far as i can see, the impact on the processor speed seems really minimal..
I look forward to more of your discoveries..
Nice job! Performance is much better... but in the all programs list the icons all still flashing when scrolling, although its much less.
Thank you
Great job in all programme speed seems little better.
nice
thanx
Hey Rog,
Nice to see you're trying different things.
I looked at my HD but it didn't have the slowdown the Polaris has. But it also doesn't have the registry keys... so i added them and soft reset. Now, my HD's TFLO3D is really unresponsive and stutters... So maybe it's only for non-TF3D devices?
Thank's
It's working well in my M-Amine 2.0 Final Rom.
Here is the little Cab.
EDIT: If you install this cab or change the register by hand (Is the same) , the scrolling work well but maybe you will have problems with Igo, TomTom or destinator.
Please take that in your mind.
Thanks a lot Rogro!! It's wonderful for every application that uses touch scrolling.
Why do HTC engineers leave us alone with those awful bugs? Is it so difficult to add those 2 DWORD values?
Actually it fixes the screen response AND the All Programs scrolling in Manilla 2D
thanks for sharing rogro82.
cheers
Thanks rogro82.
It's working
BTW i've notice something,,maybe wrong.
When you scroll (very fast) in file explorer or program folder, stoping it(the scrolling) with a sigle tap it's not so easy. Or when you tap to stoping it ,then turning to another direction(up or down).
Also the icontact scrolling isn't good enough.
I use the "cbolumar" cab.
BTW i've notice something,,maybe wrong.
When you scroll (very fast) in file explorer or program folder, stoping it(the scrolling) with a sigle tap it's not so easy. Or when you tap to stoping it ,then turning to another direction(up or down).
Click to expand...
Click to collapse
Thats because the scrolling is still way off in terms of speed... the only thing that happens when you change the registry settings is that it will not allow touch.dll to eat all resources and hang all other processes..
Maybe you could try to set it to 109 ( what it should be on a normal driver )..
I never use any gestures or whatever so setting it to 255 works for me for now until i can start cleaning code.
TomTom7 with these settings
Nice find. But in Tomtom7 something strange happens. I have to press the screen much harder then without these reg keys. I Use M-Amine's RTM rom.
Anyone else have this or is it just me having this bug?
ViNZ! said:
Nice find. But in Tomtom7 something strange happens. I have to press the screen much harder then without these reg keys. I Use M-Amine's RTM rom.
Anyone else have this or is it just me having this bug?
Click to expand...
Click to collapse
The same bug for me with Navigon Mobile Navigator 7
kr.,
Frepke
Bug with IGO 8
The same for me , i have a lot of problems with the screen in Igo , the problem disappear after delete the register changes.
To delete this, you must go to the register and delete the new values by hand, not the touch entry but the priority entries.
Only uninstalling the cab is not valid because the driver is in use.
Thanks a lot!
It's like early Christmas!
It´s because of people like you that my Polaris is an increasingly awesome machine. Continuing like this in the near future it will teleport me from one place to the other!
Keep up the good work.
Don't ever leave us Rogro!
TT6 don't work
The screen is no usable.
I have delete all the key and now work well
ROM M-Amine 2.0 Final ITA
Related
Guys, I have a question.
I used to have an iPaq 6300 running WiMo 2003, when selecting input methods there is an arrow beside the input method you click on to bring up the menu that lets you choose between Keyboard, Block Recognizer, Transcriber or Letter Recognizer. This was instantaneous! The moment you press the arrow, the menu pops up and you can switch input methods instantly.
On my new Atom Exec though this is not the case. You have to press the input method icon first, which brings up the arrow, then click on the arrow, then wait like a minute before the menu pops up. What gives? Is this really how all WiMo5 devices work? Is this a problem with WiMo5 or with the Atom Exec in particular?
It is annoying because it makes it harder to switch between input methods. Could someone tell me the score on this?
Thanks,
My bad, I fiddled around with the Atom a bit more and fixed the problem by doing a Hard Reset. Now I set the PPC back up to how I like it and it's working flawlessly.
Hmm after some time the problem seems to be back. It looks like the phone bogs down with stuff after a while, causing this problem. I don't feel like reformatting, does anyone have a fix, or a program that cleans up and optimizes your PPC?
this is an issue of WM5.
It also happens to WM6. The more applications you installed, the slower it will get (not sure what kind of application though). Well, Atom Life has 1GB of ROM. Of course people will start installing a lot of applications.
Anyway, I read somewhere in the forum stating that if you have more than 10 today plugin installed, the SIP will take a some time to appear. The plugins don't necessary be active. I mean, the ones not active are also counted. I have not confirmed this yet though.
I have more than 40 programs installed in my atom. It didn't slow down that much (only 5 to 10%) but what I usually do is to backup everything first before I install anything. At the first sign of speed reduction or bugs, I just do a restore. I have more than 15 today plug-ins both active and inactive. However, one thing I noticed is that it is better if you install your non-essentials to your sd card. It doesn't matter if you do a hard reset, they will still be there and if you use a tray launcher or clauncher, you can configure the icons to reappear even if you do not re-install them. This way, you reduce the clutter in your main memory and at the same time save you the trouble of re-installing. The reconfiguration of the executable icon will take some time but it is still faster than re-installing 30+ programs. It is important though to maintain a storage of no less than 17MB. Once you go below this, you will really see the reduction in speed and will be pissed off with your PPC. By the way, do not use Opera or any modified IE (tab browsing and downloading. by the way, Opera is good with downloading but sucks in handling your PPC's memory) while doing something else with your PPC. It will really really slow down your PPC.
i posted this same thread sometime ago, but there was no solution. At last i discover the culprit. I see the difference in speed when i install Embedded Windows VB Runtimes. regardless whether i install it in the memory card or the main memory.
Got this info from another site, it really works.
--------------------------------------------------------------------
make WM5 SIP faster (加快輸入法) (not a joke)
X51V ENG A12 + Ce-Star 2.8R2A + Monster SIP + MS IME for JAP works well.
But I am not very sure "every WM5 PPC" works well, too.
After installing a lot of softwares, WM5 SIP becomes slow.
You can make it fast again.
1. install resco explorer 5.42 and resco registry at \Device
2. use resco registry to export the registry of
HKEY_CLASSES_ROOT\CLSID
to a file (like CLSID.reg) at PPC, or SD, or CF
donnot edit or modify CLSID.reg
3. use resco registry to delete CLSID
4. use resco explorer to execute CLSID.reg to import the registry CLSID back
5. turn off PPC, soft reset
It is amazing like magic.
--------------------------------------------------------------------
Weird... it really works. Everything back to normal. Menu is displayed instantly after tapping on the list button.
I'm using Atom Life WM6, so this mean that it also works for WM6.
Urk Double Post
Aha! O2's proprietary software is a bunch of Today plugins! That may be the culprit. I noticed the a while later though after the O2 software was installed.
I have no perceptible slowdown on the Exec other than the input method switching. I just need to fix that!
My main memory is about 85% free (83.6MB) and yes I do install all the non-essentials to the SD card.
MightyOx I'll try your method hopefully this fixes this issue. While "upgrading" to WM5 I thought it would be a completely better experience, but I'm finding WM5 has issues and that quite a few things were done better in WM2K3 (like the SIP switching speed) or how about creating a new SMS message in WM2K3 you only needed 2 taps here in WM5 you need 3. *roll eyes* sometimes I wonder what developers are thinking when they take steps backwards like this.
On the other hand I love being able to rotate the screen, and Voice Command 1.6 was totally worth it.
Mochan said:
Aha! O2's proprietary software is a bunch of Today plugins! That may be the culprit. I noticed the a while later though after the O2 software was installed.
Click to expand...
Click to collapse
It's not O2's software. It just happen to be the next software you've installed before the problem show itself. It can be any software. As I said in my previous post, it will happen after you've installed a certain number of software. I think it is WM5 and WM6 related.
Anyway, the workaround is already posted. So, I have no more complain about this problem.
Yeah, looks like it's not. I tried Mightyox's method, THANK YOU SIR my Atom is running fine again. It's like once you pile over some registry entries over the CLSID directory, it takes time to get it. So the solution is to delete the registry key and "re-enter" it so it goes back on top. Very strange but if it works then more power.
Tried it on my flame...Wow...works like a charm
THERE IS A NEW THREAD WHERE YOU CAN FIND NEW VERSIONS. PLEASE, USE FTOUCHFLO 1.4.1 INSTEAD OF THESE ALPHAS.
Update 2007-10-16:
Hello!
Here you have new release which is much more stable than all previous!
Mostly I was working on solving problems, increasing performance and reliability, so:
1. Horizontal scrolling in Programs, Settings, Office etc. solved.
2. Problem with excluded applications list solved.
3. Many improvements had been done in scrolling together with bugs fixing.
4. Problem with a few instances of FTouchFlo running at the same time solved. You'll not start more than one instance now.
5. Problem with forwarding stylus events to gwes in scrolling mode solved. It was the reason of a unstable scrolling.
6. Problem with memory leaks when starting applications solved.
What's new:
1. Possibility to set up initial mode: "Scrolling" or "Launching".
There is additional parameter int the config file:
;Initial mode (S - scroll, L - launch)
InitialMode:S
2. Now you'll see small icon at top of your screen showing current FTouchFlo mode.
S - scrolling, L - launching and D - disabled (application is in excluded apps list).
You can now switch between modes by tapping at the icon.
3. A few more or less bugs found and killed (of course some new bugs introduced )
Thank you all for good ideas, unfortunately it's just impossible to implement them all in reasonable period of time + I was really concentrated on reliability and performance.
I hope that A4 is a last Alpha version!
P.S. Don't forget to uninstall all previously installed FTouchFlo versions! Calibration.dat file you shouldn't delete.
Update 2007-10-15:
Friends, I really didn't feel good yesterday when I was writing description to Alpha 3.
Error is in description how to toggle between scrolling and launching modes. You should use DOWN->UP->DOWN gesture to toggle. E.g. from the bottom of the screen, move your finger to the top and then back to the bottom.
Thank you!
Update 2007-10-15: Alpha 3 available now!
Thanks to all donators!
Changes in alpha 3:
1. Solved problem with iContact and other applications without name of window. Just put name of exe file into excluded programs list.
2. Delay function added to configuration: delay time in milliseconds before "standard windows behavior".
3. Launch applications function added.
FTouchFlo now has 2 operation modes: scrolling and launching.
To toggle between operation modes you should use up-down gesture. If mode has been toggled you'll hear a beep.
You can use GestureWaitingDelay parameter in the config file to set up how much time FTouchFlo will be waiting for gesture. So, for example, if you'll set up there 1000 ms, FTouchFlo in the scrolling mode will be waiting 1000ms before start scrolling. As less GuestureWaitingDelay, as fast you should move your finger. Try to find suitable value for you.
Once you're in the launching mode you can use 4 gestures:
down-up, up-down, left-right, right-left to start 4 different applications.
There are 8 parameters in the config file for this:
UpDownApp:
UpDownAppCmdLine:
DownUpApp:
DownUpAppCmdLine:
LeftRightApp:
LeftRightAppCmdLine:
RightLeftApp:
RightLeftAppCmdLine:
You can guess what they mean by their names, actually...
As an example I can show how to start .swf files by Down-Up gesture:
DownUpApp:/Windows/saplaywm.exe
DownUpAppCmdLine:/Cube Launcher 0-03.swf
Installation:
Before installing alpha 3 it is necessary to uninstall previous versions. Calibration.dat file you shouldn't delete because it is the same for alpha, alpha2 and alpha3.
P.S. Application becomes more and more complicated and it is harder and harder to introduce new features. I've spent 2 days near the computer and I'm going to calm down for a while. Also I've got flu, so alpha 3 might be affected by this fact.
Thank you!
Update 2007-10-14: more info about Alpha 2
1. Before installing alpha 2 it is necessary to uninstall previous version. Calibration.dat file you shouldn't delete because it is the same for alpha and alpha2.
2. FTouchFlo reloads configuration file (with excluded programs list) each time you're opening new application, so after you add new application to exclusion list, keep in mind that FTouchFlo will start ignoring it after you switch to other application and then switch back.
Update 2007-10-14:
First of all I want to say Thank You to all donators!
Alpha-2 version is now available!
Changes:
1. Improved calibration routine.
2. Excluded applications list added.
3. FTouchFlo doesn't work if SIP is working.
4. Delay before "standard windows behavior" function decreased to 100ms.
5. Improved speed and reliability.
Still not solved:
1. Horizontal scrolling in Programs, Settings etc.
2. Transcriber doesn't works.
3. No sound on screen taps.
4. Strange issue: "In Spanish, it's installed in "Menu Inicio\Programas\Programs" and uninstall doesn't work.".
5. Possible to start more then one instance of MouseEvent.exe and possible to start Callibration.exe. Just now I remembered about these problems.
How to configure programs which shouldn't be affected by FTouchFlo:
There is a file FTouchFloConfig.txt in the program directory.
Contents of the file after installation:
; FTouchFlo configuration file
; Exclude applications
ExcludeocketCM.exe
Exclude:TomTom Navigator
Exclude:Flash lite
; end of configuration
You can use application exe file name or application's window name. So, to put, for example, Calculator application to the list you should add there:
Exclude:Calculator
or
Exclude:MobileCalculator.exe
Program will re-read contents of config file automatically.
---------------------------------------------------------------------
P.S. Don't forget about donations ... It is really hard to find free time.
P.P.S. In advance I want you to excuse me for my English and probably not so clear explanations. It is 3:10 a.m. now...
P.P.P.S. You may use this software on your risk. I'll not take responsibility for possible problems... and so on and all stuff like this.
---------------------------------------------------------------------
Update: Scroll function videos: scroll 1 and scroll 2
Hi to all owners of HTC PDAs who wants to use TouchFlo but their PDAs doesn't support it!
After a deep research how touch screen works and communicates with gwes I've made an application which is able to intercept all stylus movements and process it or forward to gwes.
It is still necessary to do a lot of things like calibration and other stuff, but in fact it works!
I'll continue working but I really don't have much free time, so your donations will speed up development.
-=<Here>=- and -=<Here>=- you can see how it works now. It can recognize movements in four directions and start selected programs: Internet Explorer, Calculator, TMail and File Explorer.
Also I am looking for your ideas how to use this software... there are few possibilities I noticed and going to implement:
1. Start programs depending on direction (like it works now).
2. Use it for scrolling with finger.
3. Create a library so any developer can use it to implement their ideas.
Thanks a lot for my friends (Pavel and Sergey) who are working on this software. Without their help such progress wouldn't be possible.
EDIT: I forgot to mention that I've tested it on HTC Trinity, but I'm sure it will work on any HTC PDAs with touch.dll written according to Microsoft specification.
wow.. that looks awesome
I just saw your other video.. and wow.. I'm even more amazed
DVS_WiNdz said:
I just saw your other video.. and wow.. I'm even more amazed
Click to expand...
Click to collapse
Thank you! I've just added link to the second video.
Is there a cab for us to download?
HTC CUBE works in our ATOM
http://forum.xda-developers.com/showthread.php?t=333513
HTC Touch Cube working on O2 ATOM(WM6 AKU0.7.0)!
THIS PROGRAM DOES NOT REQUIRE FLASH - ITS THE REAL TOUCH FLO!!!
PART 1 - Install your Touch Cube onto your Atom!
Hi guys,
I've managed to get the HTC Touch Cube working with jiggs's WM6 AKU 0.7.0. Not sure if anyone was previously successful in doing this. But unfortunately, at the moment, it is using the ButtonFlo method of turning the cube.
I dont have the expertise to get this thing working using the Finger or stylus to get the touchscreen to turn the cube yet.
Maybe one of you geniuses out there will be able to take this one step further and get it working fully! (I'm hoping)
Here are the files I used and hope it works for you guys on jiggs WM6 AKU070.
INSTALLATION STEPS -
1) Install jiggs's WM6 AKU070 (make sure HTC HomePlugin is activated - dunno if you really need it).
2) Install HTC Audio Manager.
3) Install HTC Audio Mgr Today Plug-in.
4) Install Touch flo(Alpha).cab
5) Install JT ButtonFlo.cab
6) Map Touch Flo pgm to one of the buttons - I chose the O2 Media Plus button.
7) Soft-reset.
PART 2 - Customizing Your Cube using Touch Settings!
Step 1: Install Touch settings V1.22.cab, then soft reset.
Step 2: Go to windows\startup and delete entry "Mediahubmini"
Step 3: Soft reset (I don't think it's neccesary though, but i do perform
this step.
Step 4: OH YES! Also install the missing ICON files for the APLauncher - AL_xx_Touch.zip into a separate directory (eg. \Touch).
Step 5: Copy the same ICON files(from Step4) into \Windows. (these files were missing in Part1).
Step6 - Soft-reset and you should see everything working!
steveecourt said:
Is there a cab for us to download?
Click to expand...
Click to collapse
Hi! Not yet. It is really not ready for publishing yet.
I am working on calibration now and after it will be done I'll publish first alpha.
P.S. Now calibration data gathered from my Trinity and hardcoded.
generalriden said:
http://forum.xda-developers.com/showthread.php?t=333513
HTC Touch Cube working on O2 ATOM(WM6 AKU0.7.0)!
THIS PROGRAM DOES NOT REQUIRE FLASH - ITS THE REAL TOUCH FLO!!!
PART 1 - Install your Touch Cube onto your Atom!
Hi guys,
I've managed to get the HTC Touch Cube working with jiggs's WM6 AKU 0.7.0. Not sure if anyone was previously successful in doing this. But unfortunately, at the moment, it is using the ButtonFlo method of turning the cube.
I dont have the expertise to get this thing working using the Finger or stylus to get the touchscreen to turn the cube yet.
Maybe one of you geniuses out there will be able to take this one step further and get it working fully! (I'm hoping)
Here are the files I used and hope it works for you guys on jiggs WM6 AKU070.
INSTALLATION STEPS -
1) Install jiggs's WM6 AKU070 (make sure HTC HomePlugin is activated - dunno if you really need it).
2) Install HTC Audio Manager.
3) Install HTC Audio Mgr Today Plug-in.
4) Install Touch flo(Alpha).cab
5) Install JT ButtonFlo.cab
6) Map Touch Flo pgm to one of the buttons - I chose the O2 Media Plus button.
7) Soft-reset.
PART 2 - Customizing Your Cube using Touch Settings!
Step 1: Install Touch settings V1.22.cab, then soft reset.
Step 2: Go to windows\startup and delete entry "Mediahubmini"
Step 3: Soft reset (I don't think it's neccesary though, but i do perform
this step.
Step 4: OH YES! Also install the missing ICON files for the APLauncher - AL_xx_Touch.zip into a separate directory (eg. \Touch).
Step 5: Copy the same ICON files(from Step4) into \Windows. (these files were missing in Part1).
Step6 - Soft-reset and you should see everything working!
Click to expand...
Click to collapse
Hi!
I promise that I'll inform you personally when I'll be able to release a cab, so you'll be able not to map your Cube to some button, but use your finger to start it.
BTW, Cube still doesn't work on my Trinity. All the time just black screen.
Thank you!
When you get the black screen, press the power button to put the device in standby mode, wait 15 sec and hit the soft reset, this helped me with the black screen problem in the past
efrost said:
Hi!
I promise that I'll inform you personally when I'll be able to release a cab, so you'll be able not to map your Cube to some button, but use your finger to start it.
BTW, Cube still doesn't work on my Trinity. All the time just black screen.
Thank you!
Click to expand...
Click to collapse
Sounds very awesome do you think it work on kaiser and do you need help testing it, i have been trying on hermes since beginining and I dont mind been a beta tester for the kaiser model, just pm me if you think thts a good idea. anyways great work
efrost said:
Hi!
I promise that I'll inform you personally when I'll be able to release a cab, so you'll be able not to map your Cube to some button, but use your finger to start it.
BTW, Cube still doesn't work on my Trinity. All the time just black screen.
Thank you!
Click to expand...
Click to collapse
thanks..hope you will PM me.. i need to activate the finger touch on this HTC CUBE & i think ur the man to help us.
efrost said:
Hi!
I promise that I'll inform you personally when I'll be able to release a cab, so you'll be able not to map your Cube to some button, but use your finger to start it.
BTW, Cube still doesn't work on my Trinity. All the time just black screen.
Thank you!
Click to expand...
Click to collapse
follow the procedure #2. YOU NEED THIS
PART 2 - Customizing Your Cube using Touch Settings!
Step 1: Install Touch settings V1.22.cab, then soft reset.
Step 2: Go to windows\startup and delete file called "Mediahubmini"
Step 3: Soft reset (I don't think it's neccesary though, but i do perform
this step.
Step 4: OH YES! Also install the missing ICON files for the APLauncher - AL_xx_Touch.zip into a separate directory (eg. \Touch).
Step 5: Copy the same ICON files(from Step4) into \Windows. (these files were missing in Part1).
Step6 - Soft-reset and you should see everything working!
------------------
if still BLANK SCREEN
http://forum.xda-developers.com/attachment.php?attachmentid=48659&d=1188479012
<----download this .brn files (replace if needed old files)
(read this forum also CLICK --HERE--)
put it in ur /windows..THEN softreset
EVERYTHING WORKS TO ME NOW...i tried to install this program so many times, many times also i GOT THE BLANK SCREEN.
NOW I REALIZED MY MISTAKE, I did not copy & replace .brn & png file on my /windows...thats the key to work & no blank screen. Co'z no source of image after running the touchflo program and this files is the source
I can test also for blueangel device
Another keen Hermes volunteer here! I hope you're going to dish out some source code as I'm keen to learn how you have managed to hook mouse events!
Keep up the good work!
xplode said:
I can test also for blueangel device
Click to expand...
Click to collapse
@xplode,
did you try it yet? If so, does it work on the BA? Thanks.
egzthunder1 said:
@xplode,
did you try it yet? If so, does it work on the BA? Thanks.
Click to expand...
Click to collapse
Hi!
Friends, take it easy! I'm really not going to release something that for sure will not work. I already posted above that calibration data taken from my personal Trinity and hardcoded in the program, so I would create calibration procedure and then I'll publish version for alpha testing.
For example, at the upper left corner my Trinity touch screen driver reports me X = 97 and at the lower left corner I have X = 90. On your devices I am sure it will be different.
So, it is necessary to have precise calibration procedure so your devices will work properly!
BTW, if you have implemented precise enough procedure for calibration, it would be great if you share it with me.
efrost said:
Hi!
Friends, take it easy! I'm really not going to release something that for sure will not work. I already posted above that calibration data taken from my personal Trinity and hardcoded in the program, so I would create calibration procedure and then I'll publish version for alpha testing.
For example, at the upper left corner my Trinity touch screen driver reports me X = 97 and at the lower left corner I have X = 90. On your devices I am sure it will be different.
So, it is necessary to have precise calibration procedure so your devices will work properly!
BTW, if you have implemented precise enough procedure for calibration, it would be great if you share it with me.
Click to expand...
Click to collapse
@efrost
Didn't mean to sound too overexcited, but... truth of the matter is that I am. I am as happy as a crackhead on payday
I saw the videos on Youtube and I liked the way it worked. It was blazing fast! In either case, keep it up!!!!
Umm.. I have a question. Do most of your phones run as fast as the one in the video? Mine is so slow.
Hi! I've found a few free minutes (at work) and implemented scrolling.
It scrolls standard contacts, e-mails, word, internet explorer etc. In other words, every window which has scroll bars.
I don't have possibility to create video and share it for now, but today evening you'll get it!
What mechanism are you using to hook the mouse events? Care to share any code?
Ta,
Chris.
Summary:
I'm starting this thread as a dedicated effort to enhancing the integration of the HTC TouchFLO Cube onto non-"HTC Touch" devices, without requiring a different version of touch.dll to be installed on the device via a new ROM.
Current Status:
WHAT'S DONE
Much research in learning how the cube works
Development of some theories
Development of a testing app to test theories
Proof of concept app built to prove the theories
Using FTouchFlo, I have all 4 motions assigned to the correct cube task ... and it's all working!
Slide up - open
Slide down - close
Slide right - spin right
Slide left - spin left
Added new feature, where LR, RL, and UD finger swipes can execute other tasks if you perform them when you're not on one of the cube faces. Read Project Status 11-12 entry for details
Added an option to allow LR, RL gestures to open & spin the cube even when biotouch is not running. Not sure if this is actually the way the Elf works, but some people want it
Conversations have been started with efrost about integrating our work here directly into FTouchFlo. Talk about a speed enhancement!
Raven_coda has cracked the final piece of the puzzle!
I have implemented Raven_coda's changes, and my C# version works great ... StartUp items are sorted out now!
C++ version created ... speed is definitely improved
A few bugs fixed, a few issues addressed, and a few new features added
Beta release v1.1.0 available here:
http://rapidshare.com/files/72589345/TFloCubeCtrl_-_v1.1.0.zip -or-
Use the attachment at the bottom of this post
NOTE: This file is a zip archive, suitable for situations where you already have the HTC TouchFLO cube installed. If you have never installed TFloCubeCtrl before, then follow the TFloCubeCtrl - Installation instructions. If you're upgrading from v1.0.4, then use the TFloCubeCtrl - Upgrade instructions. You do *not* need to uninstall TFloCubeCtrl or the HTC TouchFLO cube in order to upgrade. For a complete cube installation, please check with duttythroy on his thread here: http://forum.xda-developers.com/showthread.php?t=336482.
Newer cab built by xplode available here:
http://rapidshare.com/files/75947199/HTCCube_FTouchFlo_TFloCubeCtrlv110_Config-xplode.cab
Includes HTCCube + FTouchFlo v1.4.1 + TFloCubeCtrl v1.1.0 + TouchSettings v1.22 + FTouchFloConfig. This should also include all of the patches and fixes from the attachment list. However, if you installed the previous version of xplode's cab and are experiencing issues, try the following:
If you experience 2 apps launching from the MediaHubMini using Xplode's latest cab ... then replace the MediaHubMini.exe with the "patched" version below in the attachments. Either terminate the MediaHubMini process first then overwrite, or delete the MediaHubMini (preload) link from Windows\Startup, soft reset, then overwrite the file.
If you are having issues with QuickDial not functioning properly ... then replace the QD_Bar_NoBar_HL.png image file with the replacement version in the attachments. Also you can try replacing the version of QuickDial with the patched version in attachments below. Either terminate the QuickDial process first then overwrite, or delete the QuickDial (preload) link from Windows\Startup, soft reset, then overwrite the file.
WHAT'S LEFT
The black screen issues seemed to have all but disappeared. I believe we have determined the reason they were occurring, and have solved at least a vast majority of them.
Solve any remaining beta release bugs/issues
Once the beta seems good to people, get the code to efrost for him to integrate into FTouchFlo!
Rules:
For now, this thread is intended for people who already have a working version of the TouchFLO Cube on their system.
I'd prefer to keep this thread research & development oriented. I don't want this to turn into another thread of a million posts by people who are getting cube black screens and want help.
The cube still has a few unknown nuances/dependencies ... so this thread will be most suited for people familiar with alpha version software.
This thread is about integrating the original HTC TouchFLO Cube. I don't think we need a bunch of posts about how some 3rd party app is better, or how a Flash cube turns faster. There are other alternatives, yes ... this thread is about just one of those alternatives.
More as I think of them
Structure:
Post #1 is for general info
Post #2 will be project updates
Post #3 will be announcements / additional updates
Post #4 is some project background info
Post #5 we'll reserve for a hint/tips section
The rest is up to you guys
Donations
Thank you to all who have donated! Every donation makes me realize that other people are also interested in this project, and helps keep me motivated to continue expanding the functionality, and answering questions!
Props
JasonStern for his tireless research as to why QuickDial was failing on certain devices (see QD replacement image an new version attachments)
Musicman247 for providing me with files and sharing the work he has done with a true 6-sided cube
Zyphlin for pointing me to the work that Musicman247 was doing
Raven_coda, who despite being my mortal enemy at first , ended up discovering the key to breaking our dependency on the original biolauncher app!
duttythroy for creating his cab installer that started me down this path
efrost for creating FTouchFlo which makes the cube work with finger control
xplode for creating cab installers for me (even though he "hates" the cube )
techmonkie for responding to my RFI, and straightening me out re: launching/exiting
funman and Biffert for also helping me out with reference information from an actual HTC Touch users
jasjamming & Bepe for the original work on Touchflo Alpha
others ... I'm sure
Project Status
11-10-2007: Proof of concept app in C# is completed, and the four finger control functions are working! One major issue, is how to get back into the cube when biotouch is still running, but no cube app is in the foreground (like after you launch and close an app). So far, I can only get the startup animation when I start biotouch from scratch ... so the downswipe action runs the close animation, and then closes biotouch. It really seems like I should be able to call something to get a running instance of biotouch to re-execute the startup animation ... but I'll be darned if I can find it as of yet.
I'd like to get some input from users of an actual Elf or Touch Dual device. Ideally, someone who can run a process viewer app to see the processes behind the screen ... and even better if they have a tool like Remote Spy that comes with Visual Studio 2005. I think it would help me ... because right now I'm just guessing at what should be happening.
I need to figure out what pieces need to be in startup for my app to work. Basically, I've written my own version of BioLauncher ... which doesn't require biotouch to be running at all (it starts it on an upswipe). But so far, removing the ns script call from startup (bio.lnk) didn't seem to allow the biotouch animations to run. Need to do more research in this area. Everything works fine if I use my normal Touchflo Alpha install ... use the hardware button to loop through things (pre-loads all the cube apps probably), and then use my new app mapped to FTouchFlo. If none of this makes any sense to you ... read "How the TouchFLO Cube works" in Post #4.
11-10-2007 (after some sleep): I posted a message over on the Elf forum asking for some information about the behavior of the cube in certain situations. We'll see if I get any help. If anyone reading this knows of anyone with an Elf or Touch Dual (are they out?) ... then send them over to that forum, or check it out yourself and borrow their device for a bit
11-11-2007: I actually got an answer from the Elf forum techmonkie is indicating that biotouch doesn't really terminate on cube close, thereby indicating that there *has* to be a way to trigger the startup animation from a running biotouch instance. I was really starting to suspect that this was the case ... but this was the evidence I needed. Figuring this out will solve my startup woes ... and that should complete the interactivity with the cube. At that point ... I may consider a controlled alpha release, just to confirm that things are working as design on other devices. We'll have to see how things go. I'm going to refocus my investigation on triggering the open animation from a running biotouch ... but I may need some detailed analysis from an Elf ... we'll see.
11-11-2007 (update): Did I mention how much sleep this thing is causing me to lose?! Anyways, OK ... must have been the inspiration of knowing how it was actually working on an HTC Touch device, because with the info in techmonkie's response, and a little more digging into the assembly code of touch.dll to confirm, I've got the startup issues sorted out. In fact, biotouch.exe does indeed remain memory resident. There is a way to get the startup anim to run ... although I swear I tried this before, and it didn't work. The open and close animations even do a little screen fade-in. It's working quite well for me in fact! This is so sweet ... I went and downloaded a few other animations from the Elf Cube customization thread ... just to see then animate in my new fully-functional cube!
There's a few cleanup things to do for tomorrow ... and then it's on to sorting out the correct startup sequence. I'm still considering the controlled alpha release. Right now, you need to add it on top of a working cube ... which may not be bad for those that have working cubes!
11-12-2007: I had this thought earlier today ... I never really want a RL or LR swipe to bring up the cube and spin it, if the cube wasn't open before. You don't really know what page you'll land on ... unless you know where you left off last. I'm not exactly sure of the Elf's behavior on this point ... but I decided to add the ability for my cube interface to execute cube functions when the cube is open, or execute other apps if the cube is not open. For instance, I can have a RL swipe spin the cube when the cube is open, but the same gesture will launch Total Commander when I'm on the home screen I think it's pretty cool ... retains the cube interaction abilities, and still retains the "quick launch" nature of FTouchFlo gestures! Doesn't appear to slow it down much ... I'm hoping the C++ version is better anyways.
11-16-2007 (Announcement): New Announcements ... see Post #3 below.
11-20-2007: Hints, Bugs, & Issues section updated to include at least a start (prompted after yet another post about missing contacts tab in HTC Home . Development work on fixing the screen lock bug continues.
11-21-2007: Version 1.1 is under way with a few new commands available. Detect for screen lock and rotation seems to be working, and I'm hoping to fix a few of the other bugs. Also, use of link files for <App_2> parameter now work!
11-24-2007: Version 1.1 development continues. I removed the error message when using the openSpin<Direction> command and running in landscape mode. Also, I think I've fixed the "rainbow effect". Finally, I've adding another new command option: lock, which will execute the standard device lock. So some of the new commands are: minimizeAll, lock, lock-home, and somehow I'm going to work in a command to lock and suspend. Tossing around the idea of allowing screen rotation through gestures as well. So I think bugs 1 & 2, & possibly 3 are fixed, and issues 1 & 2 are adressed. A release is probably due, maybe by the end of this weekend.
11-25-2007: Version 1.1 seems complete. I've added screen rotation as well ... so the final list of new options is: lock (sub options of "home" and "suspend"), rotateDisplay (left and right), minimizeAll. I'll try to package it up in a new archive by tomorrow, after a bit more testing.
12-05-2007: Remaining issues still seem mostly centered around some devices having issues with QuickDial. I've gotten my hands on some new versions of the required apps, and am currently evaluating them. For the most part ... it looks promising that these will extend our cube functionality!
Announcements
11-12-2007: Limited Alpha Release
With this latest feature added ... and everything seeming to work perfectly on my device, I've decided to go ahead with a limited release alpha. It's just so cool ... and I know there are "Cube People" out there that wanted this just as much as me Basically, here's how it works.
You are not eligible for the alpha unless you already have the TouchFLO cube software installed and spinning to the right via FTouchFlo. Reason is that I was focused on rewriting the biotouch interface app first ... as that's the key component. There are lingering nuances to getting the TouchFLO cube apps themselves working ... but I'll be addressing that once I get past this phase. Don't worry ... I have plans on making this a simple cab installation for the whole enchilada ...
If you're interested in trying out the alpha version ... PM me, because I'd rather not have a bunch of one-line posts for people asking to test.
I'll give you the location of the zip file to download. This is alpha-ware ... so not fancy installers yet, but I guess I'll throw in a readme.txt file or something. It's pretty simple really ... assuming that you have a working cube.
Once you get things installed ... try it out. If you're having problems that seem like they might be installation/configuration issues ... then PM me about them first. I'd rather keep the posts as relevant to "general design/development" as possible.
Along the sames lines ... no need to post messages saying it works and whatnot, just PM me. Since it's not publicly available ... we don't really need pages of posts from people saying it works.
11-14-2007: Limited Alpha Release - ON HOLD
Alpha is on hold until I work through some issues ... and clear out some PM's Thank you all for your interest and feedback.
11-15-2007: Startup items are sorted out ... first beta version is on its way ... although apparently no luck in finishing that night
11-16-2007: First revision ported to C++. Need to do some testing and tweaking ... hopefully will finish tonight!
11-16-2007 (Update): Beta release v1.0.4 available here: http://rapidshare.com/files/70299288/TFloCubeCtrl_-_v1.0.4.zip. Currently just a zip archive, I may build a cab installer over the weekend, just for my app (for you that already have the cube installed). For a complete cube installation, please check with duttythroy on his thread here: http://forum.xda-developers.com/showthread.php?t=336482
11-27-2007: Beta release v1.1.0 available here: http://rapidshare.com/files/72589345/TFloCubeCtrl_-_v1.1.0.zip. This file is a zip archive, suitable for situations where you already have the HTC TouchFLO cube installed. If you have never installed TFloCubeCtrl before, then follow the TFloCubeCtrl - Installation instructions. If you're upgrading from v1.0.4, then use the TFloCubeCtrl - Upgrade instructions. You do *not* need to uninstall TFloCubeCtrl or the HTC TouchFLO cube in order to upgrade.
Background
Background:
A few weeks back, I was inspired by the work of a couple of fellows who were working on a project to get the HTC TouchFLO Cube working on other HTC devices. You've probably seen the installation cab floating around in a couple of different threads. Like many of you, I quickly became enamored with the cube ... and jumped through all of the hoops to get it working (and I was one of the lucky ones who got it working).
The original work by jasjamming and bepe provided a cube that could spin to the right via a hardware button. Then, with the release of efrost's FTouchFlo ... you could get the cube to spin right with a finger motion. It was all great, but I wanted more! Two things bothered me greatly ... you could not spin the cube left, and once you launched a program ... the only way to return to the cube would be to spin it again.
So began a intensive week-long, late-night effort to learn as much as I could about the TouchFLO Cube, and if/how we could get it do more. I am very happy to report that much progress has been made ... and it is definitely feasible that we can have finger controlled spin left, right, open, and close.
How the HTC TouchFLO Cube works
The HTC TouchFLO Cube is really the collaboration of four separate executables, and an "interface". The four executables consist of one app per each each face of the cube (ApLauncher.exe = App Launcher; MediaHubMini.exe = Music, Photos, Video; QuickDial.exe = Contacts), and an application that facilitates the animation sequences for the cube (Biotouch.exe). Now, at this point I guess I'll point out that "cube" is really a bit of a misnomer. Since there are only 3 faces to this object + top and bottom, it's really more of a pentahedron, or a triangular prism if you like the sound of that better. The "interface" part is where things get interesting. On an HTC Touch (Elf) or Touch Dual ... the "interface" that detects finger swipes and translates them into calls to the biotouch application is the main touchscreen library: touch.dll. This is where we start running into problems trying to run the cube on other devices. Without modifying the touch.dll on a given device ... there will be nothing to interpret finger swipes and communicate to biotouch. This is the point the original work by jasjamming and bepe went down the path of attempting to map a hardware button to be used to spin the cube. An executable needed to be created that would interact with biotouch in the same manner that the touch.dll file would, and trigger it to run the spin right animation. I'm not exactly sure what process these guys went through to figure this out ... but they did. From there ... it was efrosts creation of FTouchFlo that brought the next revolution. FTouchFlo is an app that allows you to map a file to be called when it detects one of the four finger swipe motions (up-down, down-up, left-right, right-left). With this, you could now map that same executable that was assigned to the hardware button to the left-right swipe action in FTouchFlo ... and now your cube spins with a finger swipe.
That's pretty much where the development stopped. I did a lot of research on this ... but pretty much all I could find from that point on was various people's input about it not working on this device, sort of working on another, etc. I simply couldn't believe that no one was pushing to enable the other cube interactions! It frustrated me to no end to know that I had a cube that was capable of spinning left, but no way to tell it to do so. So I rolled up my sleeves, read through countless pages of posts about what had been done so far, downloaded a disassembler, performed a lot analysis and theorizing ... and here we are today.
Hints, Bugs, and Issues
Hints
Problem: I installed the cube, and now my Contacts tab in HTC Home is gone!
Resolution: Delete the registry key: HKLM\Software\OEM\MASD\QuickDial
Problem: I installed the latest cab, and now I have trouble completing a gesture
Resolution: Try changing the GestureWaitingDelay in FTouchFloConfig.txt to a higher value (i.e. 50000)
Problem: I can't figure out what/how to map the cube to my hardware buttons
Resolution: Download my zip archive from post #1, and read the TFloCubeCtrl - Readme.txt file
Problem: I don't know/understand the TFloCubeCtrl options in the FTouchFloConfig.txt file
Resolution: Download the TFloCubeCtrl - Readme.txt file from the attachments in this post
Problem: I'm not very technical, and I don't know what to do
Resolution: Be patient and wait for there to be a final release. This is a beta, and is therefore not polished to the point of a one-click install
Problem: I end up activating the cube when I try to unlock in Slide2Unlock
Resolution: Add s2u2.exe to the exclude list in FTouchFloConfig.txt
Problem: My Touch Settings application has no icons for the APLauncher
Resolution: Be sure to add the AL_xxx.png icons to your Windows directory
Problem: Editing the FTouchFloConfig.txt file is confusing/difficult
Resolution: Check out the FTouchFlo Configuration Tool by schaps here: http://forum.xda-developers.com/showthread.php?t=345568
Problem: I installed the latest Xplode cab, and MediaHubMini is launching multiple apps
Resolution: It's a known issue ... try replacing your MediaHubMini.exe file with the one from the attachments in Post #1. Be sure to terminate the MediaHubMini process first, or remove the MediaHubMini (preload) link from Windows\Startup and soft-reset
Problem: I installed the latest Xplode cab, and QuickDial is not working
Resolution: It's a known issue ... try replacing your QuickDial.exe file with the "DeviceCheckPatched" one from the attachments in Post #1. Be sure to terminate the QuickDial process first, or remove the QuickDial (preload) link from Windows\Startup and soft-reset
More to follow ...
Bugs (for TFloCubeCtrl only)
When the device is locked, but the screen is still "active", an up-down gesture in FTouchFlo will still bring up the cube ... although you then can't do anything with it. (Fixed in v1.1.0)
Link files (.lnk) do not appear to work when specified as the <Command_2> parameter. (Fixed in v1.1.0)
In some non-HTC devices (Eten M600), TFloCubeCtrl is unable to detect that the QuickDial cube app is running (related to QuickDial issue listed below)
A DeviceLock issue detailed here: http://forum.xda-developers.com/showpost.php?p=1730847&postcount=453
ICE (Infinite Cube Effect) issue as detailed here: http://forum.xda-developers.com/showpost.php?p=1732668&postcount=460
PM me to report other items you think are bugs
Other Issues
When launching the cube using a RL or LR gesture, and the cube isn't already in the foreground (aka using the openSpin<Direction> command), exiting the cube using the close command causes some interesting "rainbow" effects on the today screen as the cube app closes. The rainbow colors then disappear ... but it's very strange for a split second. (Seems better to some in v1.1.0, but not solved completely)
When you have openSpin<Direction> set up in FTouchFlo and you perform a RL/LR gesture when in Landscape mode, you receive an error message indicating that Biotouch is not running. (Fixed in v1.1.0)
QuickDial app is running slow on some devices, sometimes taking 3-4 seconds to display the actual contact name/photos. Although it was never that slow for me, v2.0 of QuickDial loads even faster. Xplode's cab installer linked to on Post #1 has QuickDial v2.0
On non-HTC devices, the QuickDial app does not seem to load. For QuickDial v2.0, this is due in part to validation that the program is running on an HTC device (I'm not sure if QD v1.0 does this). JasonStern has made some progress on the QuickDial issues ... see Problem/Resolution above
Great job!
this looks great, cant wait to see the results.
Hope this helps...
Hey Kona...that darn cube is addicting!! Im one of the few also that has the cube running flawlessly on my 8525..buttonflow that is! After alot of trial and error and lots of hard resets...i got it working. First thing to do is get the cube running after a hard reset. Second I installed gullum activate cube cab..View attachment activate_cube.CAB. Not sure what it did but the only time I have to launch biotouch is after opening keyboard....not even after a SR!!! I guess it keeps biotouch running or somehow launches it automatically. Just my 2cents...
niterdr said:
Second I installed gullum activate cube cab..View attachment 57648. Not sure what it did but the only time I have to launch biotouch is after opening keyboard....not even after a SR!!! I guess it keeps biotouch running or somehow launches it automatically. Just my 2cents...
Click to expand...
Click to collapse
Just so you know ... typically a Windows Mobile cab file contains a _setup.xml file. This file is what tells the OS what steps to perform in order to install the cab file. This particular cab file puts four shortcuts into the Windows/StartUp folder. It also inputs the typical TFLOSettings into the registry ... most of which don't really apply to us, because it's touch.dll that's looking at these registry entries, and unless you've got an HTC Touch version of touch.dll, nothing is looking at those. The exception would be the Kaiser, where it does use some of those entries for the integrated TouchFlo scrolling.
I can't say specifically why this works for you ... it's a little counter to my experience, where I was finding that links to pre-load the cube apps in the startup folder were actually contributing to my black screens.
Regardless ... I can say a couple of things about this: 1) this also seems to support the fact that biotouch normally remains in memory. I wasn't sure that was the case, because the only way I could see the startup animation was running biotouch from scratch. I got response from my RFI in the Elf forums that confirms this. 2) I suspected also that the Elf pre-loads all of the cube apps, so they don't lag on the first cube rotation. I'm not really sure why this didn't seem to work on my device ... and I'll definitely be revisiting this concept when I do the analysis to determine the correct configuration for loading the cube with my new software.
Thanks for the input!
hey, i dont understand, AJE has ported the whole Biotouch on the HTC P3300..
Then what do you want to reinvent ?
Can't you see with him directly ?
Kona, you're not the only one who wants this working on a Kaiser.
My girlfriend got herself a touch and now I'm all jealous about her cube
I'm a programmer myself and I've been looking at the touch.dll from the kaiser. But I can't find the dll from the HTC Touch. Could you maybe attach it here so I can have a look at that one too. (Or link to it) I don't have the biotouch cube installed yet.
Do you have any idea if the cube should run in windows mobile emulator in visual studio ? I think i'm going to try that... less messing with my kaiser.
cAnArdtichAud said:
hey, i dont understand, AJE has ported the whole Biotouch on the HTC P3300..
Then what do you want to reinvent ?
Can't you see with him directly ?
Click to expand...
Click to collapse
To the best of my knowledge ... some people have indeed successfully created ROMs with a functioning Biotouch Cube interface (Artemis, Charmer, Wizard to name a few). But to do this, they actually replace the version of touch.dll that normally comes on the device with the version that comes with the Elf. While this is obviously a viable and functioning approach ... it can only be done through flashing a new ROM.
I wanted to pursue an option that could be installed via a cab. I also heard that trying to flash the Elf touch.dll on a Hermes was not working. Finally ... I haven't seen/heard of anyone trying to put an Elf touch.dll on a Kaiser, and writing my own biotouch interface application seemed a lot easier than learning how to cook my own ROMs.
Damn..it could be grat !!! xD
Denhomer said:
Kona, you're not the only one who wants this working on a Kaiser.
My girlfriend got herself a touch and now I'm all jealous about her cube
I'm a programmer myself and I've been looking at the touch.dll from the kaiser. But I can't find the dll from the HTC Touch. Could you maybe attach it here so I can have a look at that one too. (Or link to it) I don't have the biotouch cube installed yet.
Do you have any idea if the cube should run in windows mobile emulator in visual studio ? I think i'm going to try that... less messing with my kaiser.
Click to expand...
Click to collapse
No need to be jealous ... if you've already got the cube running, then try out my alpha release! Will run just as good as the Touch!
I sent you a PM re: the touch.dll
As for running the cube in the Windows Mobile 5 emulator ... I'm not sure. I never really tried ... and I'm not exactly sure how it works. I guess you'd have to able to install apps into the emulator environment (4 TouchFLO cube apps plus their graphics and registry entries). Anyone care to chime in about trying to do something like this in the Visual Studio device emulator?
I think i'm lucky !
i've just download your alpha and tested it.
it works great on my french kaiser .
no bug till now.i've tested it till 30 minutes.
perhaps a bit slow at the first seconds and then everythings went smoothly !!!
i don't see what could be improved !
btw, just wanted to point that i've duttythroy alpha2 installed at first and it worked on my kaiser with some modification :
i deldted apl - biotouch - hub fom windows\start up
and deleted a key in registry: quickdial
nice work !
one more question : why the time limit ?
Kona, just one suggestion. Would be great if the Cube can be rotated L-R and R-F using the D-Pad as well. I think that is far more reliable and quicker than using the finger.
Thanks for continue to work on the TouchCube as I thought it was an unfinished business.
Kona_Mtbkr said:
No need to be jealous ... if you've already got the cube running, then try out my alpha release! Will run just as good as the Touch!
I sent you a PM re: the touch.dll
As for running the cube in the Windows Mobile 5 emulator ... I'm not sure. I never really tried ... and I'm not exactly sure how it works. I guess you'd have to able to install apps into the emulator environment (4 TouchFLO cube apps plus their graphics and registry entries). Anyone care to chime in about trying to do something like this in the Visual Studio device emulator?
Click to expand...
Click to collapse
@Kona,
Do you think that this would work in the Blue Angel running WM6? I am asking simply because I do not feel like re-flashing my device.... again
Thanks!!!
megaman said:
I think i'm lucky !
i've just download your alpha and tested it.
it works great on my french kaiser .
no bug till now.i've tested it till 30 minutes.
perhaps a bit slow at the first seconds and then everythings went smoothly !!!
i don't see what could be improved !
btw, just wanted to point that i've duttythroy alpha2 installed at first and it worked on my kaiser with some modification :
i deldted apl - biotouch - hub fom windows\start up
and deleted a key in registry: quickdial
nice work !
one more question : why the time limit ?
Click to expand...
Click to collapse
Good to hear ... I hope you mean that even after the 30 mins, you still haven't had any problems.
The slowness in the first few spins of the cube is likely due to the fact that the individual apps for each cube face are not yet running, so they have to start up on the first spin. After that, it's much quicker to redisplay the cube face because those app stay memory-resident. In the installations that I've seen that use the ns script and Touchflo in the startup do not respond well when you try to "pre-init" the cube face apps in startup as well. I'm suspicious that it has something to do with this touchflo app, because in my mind, outside of preloading the cube apps, I don't know why anything other than FTouchFlo should need to be in startup. We'll see though ... I'll be working on getting a solid install from scratch soon.
And I agree ... I think dutty's alpha 2 install is a good base for me to start from (pending his approval). I'm hoping that I'll be able to rip the old parts out, and sub in my new app, and everything will work out great.
bchau said:
Kona, just one suggestion. Would be great if the Cube can be rotated L-R and R-F using the D-Pad as well. I think that is far more reliable and quicker than using the finger.
Thanks for continue to work on the TouchCube as I thought it was an unfinished business.
Click to expand...
Click to collapse
I was just thinking about what else I could try to add to my cube controller ... and spinning via dpad did cross my mind. This doesn't end up being exactly trivial, because I haven't made any mods to the actual biotouch.exe or any of the cube apps. When you're on a given face of an app ... it's that HTC app that is the foreground window. But I'm wondering if I can't register a listener for dpad events, and trigger the cube based on that. I'll put it on the wish list.
What can be done even sooner though ... is you will be able to assign any of the cube functions (open, close, left, right) to any hardware button you can assign a shortcut to. Actually, if you're familiar with link files, you can do it now ... but I'll be adding them in my next release probably too.
megaman said:
one more question : why the time limit ?
Click to expand...
Click to collapse
Oops, forgot to answer this. I added an expiration date simply because this is a very early alpha release. It hadn't yet been tested on anything other than my device ... and I didn't want someone to go crazy and burn it into their ROM.
Fear not ... I will remove the expiration date when I feel that the software is ready for a prime-time release. Although, I could be using this alpha just to get people hooked, and then complain about the vast amount of effort I put into the project and lack of donations received ... and threaten to never release a new version
Nah ... I wouldn't do that
PROGRAM IS NOT WORKING AT 100%! AT THIS MOMENT ONLY FUCTIONS LISTED BELOW ARE WORKING. OTHER FUNCTIONS UNDER DEVELOPMENT.
Current Version
- [NEW] Birthdays button/indicator works
- [NEW] A little bit more comfortable clock setting
- [NEW] Fade-in effect now depends on your device speed
- Clock Settings
- Clocks, Indicators
- Balance update
- BlueTooth, GPRS/EDGE, WiFi, GSM on/off
- Support for all resolutions (hope so )
- Support for scale components of main window (may be useful for big resolutions)
Install: unpack to Program Files to your device.
Scale factor and balance setting are in HKCU\Software\MaxHome
Day's period to search birthdays in the same regestry.
To Do Next: sort birthdays in order of days, alarm settings, maybe screenlock
Hmmmm. so i'l be the first one
I'me more into icons and launchers but nice icons
I'm sure that a lot of people will like this
Very nice...can't wait to take it for a spin
It's amazing ! I really want this ! Good job !
Thos application seems to be verry good.
nice!!! quite tired of the normal todays screens..too much cluttered plugins...
hope you could share with us soon very much interested to try out...
nice work keep it up =) hope it is also support VGA..coz many developers develop QVGA soft huhu
looks good, keep it up!
I'm begginer in programming. So dont promise a VGA version. I wrote it with Windows Mobile 6 SDK. I think it will work with 5.0 and 6.0 of coarse.
Actually I doing it for my personal using (QTek S200, WM6).
Will be glad if some one else will can to use it
hi MaxKysh, im a beginner too. Is possible to use grafic libs like XFlib in your project?
Don't know I use only API functions.
Please, try it
Here it is if somebody want to try Please report of your try.
Tested on QTEK S200 - works well.
Tested on Asusu p525 - don't work BlueTooth swith (will try to fix it).
WiFi switch don't realised yet.
Place into Program Files on your device.
The balance USSD request message stored in HKCU\Software\MaxHome\Balance\Message.
http://forum.xda-developers.com/attachment.php?attachmentid=72766&stc=1&d=1204001375
I've got an normal htc elf p3450
And the program doesn't work correct, the background doesn't load therefore the transparant icons doesn't show.
I can enter the settings tab but i don't think any of the settings work.
I know you are a starting programmer (and i can't program anything so i have deep respect for you) but could you concider something like total customization
Greetz
Did you extract it to Program Files? (I meen Program Files\MaxHome\, and not to Storage Card (!)). Don't promise full customize but will work on it
MaxKysh said:
Did you extract it to Program Files? (I meen Program Files\MaxHome\, and not to Storage Card (!)). Don't promise full customize but will work on it
Click to expand...
Click to collapse
As i have a dutch elf i don't have the program files folder but i made one by hand and copied the whole MaxHome folder to that directory but it still didn't work.
Greetz,
Hmm... That is my big mistake Will try to fix it
hi, just tried it, unzipped to device/Program Files/Max Home
tried running MaxHome01b.exe and comes up with error:
"the file 'MaxHome01b' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. You might need to reinstall or restore this file."
I clicked on accept when it said it wasnt signed...
Not working for Wizard
Date and time displayed correctly, the "Comm Manager" displays correctly but the Bluetooth button is the only one functioning, the rest do not have any effect.
Icons at the bottom do not work at all.
Anyhow, good idea, keep the good work!
Forget to say:
realized at this moment only:
- Clocks
- BlueToot, GSM, GRRS switch (WiFi - not yet)
- Balance Update
The bottom icons just for full view They are not working.
Please tell me, which Software to programm do you use??
Can you post the source code, so that we can help you to make a realy realy good home screen?
Thanks
Eg, when using Task Manager on PC, i go to the CPU prosess tab and now im able to change the CPU priority of any program to: very high/high/medium/low/very low.
Can we do this with WM?
Rn
You can set the priority level of a thread, not of a process.
The system scheduler works quite different from desktop Windows. A thread with a priority level above normal can lock the entire system. An application must be designed very well if it want to change the priority level of one of its threads.
...
id like to 'trial and error'.
i understand the risk of locking the system = my own fault if it does.
but id still like to know your info about the system scheduler and changing the priorties please.
even if i cant get it to do what i want, ill still learn something new
Rn
ps, thanks for your reply
raving_nanza said:
but id still like to know your info about the system scheduler and changing the priorties please.
Click to expand...
Click to collapse
Here you find to both subjects a very good answer.
Just install dotfred's task manager, and set the priorities with it. If you screw up, it doesn't matter. A soft reset restores them to the stock configuration.
...
cheers dude, ill download and try it now.
Rn
update
i tried dot fred TM, but didnt like it though :/
cant i just add a .reg for each specific program that i want to have a higher cpu priority?
eg, something like this:
Dword="priority256", Value="XXX"
("XXX" = eg: "255" is normal priority)
???
Rn
raving_nanza said:
i tried dot fred TM, but didnt like it though :/
cant i just add a .reg for each specific program that i want to have a higher cpu priority?
eg, something like this:
Dword="priority256", Value="XXX"
("XXX" = eg: "255" is normal priority)
???
Rn
Click to expand...
Click to collapse
Not that I'm aware of; this stuff isn't set in the registry, except for a few thread priorities for the file system that are in the boot.rgu, and aren't user accessible. You can get a program called Speedbooster that will automatically watch for specific processes opening, and will then adjust thread priorities to however you want them. Wait, I'll save you the time and money, because it sucks. It changes all thread priorities for a given process, and most of the time makes things worse instead of better. You're better off just doing it with a task manager manually for a while, and then giving up and realizing it's a waste of time. Lol.
...
Farmer Ted said:
Wait, I'll save you the time and money, because it sucks. It changes all thread priorities for a given process, and most of the time makes things worse instead of better.
Click to expand...
Click to collapse
Yeah i already found SpeedBooster on google but its not freeware, which cant be cooked into roms
I suppose it would be cool if someone develops an app dedicated to do this = no task manager, no nonsense, no nothing, just a simple small app which lets you select a program and set its priority.. Simples!
Farmer Ted said:
and then giving up and realizing it's a waste of time. Lol.
Click to expand...
Click to collapse
Basicly i wanted to increase the priority of Total Commander and Opera10 because their the main two programs i use. (probably the main two programs everyone uses.)
I think your right though dude, ill take your advice and give up now before i do waste my time, my precious ORD time! lol
Cheers dude!
Rn
I tried increasing the priorities of PIE and UCWEB with sppedbooster, and the problem is that it slows down finger-scrolling dramatically, to the point that the browsers were unusable. You can make a sppedbooster package, but just not distribute it. I cooked it in for a while, when I was determined to convince myself I hadn't blown twenty bucks on a piece of crap.
Why do you need to speed up total commander? I use it all the time, too, and it's pretty snappy. I'd suggest limiting the number of processes and not using manila to optimize speed.
...
Farmer Ted said:
I tried increasing the priorities of PIE and UCWEB with sppedbooster, and the problem is that it slows down finger-scrolling dramatically, to the point that the browsers were unusable. You can make a sppedbooster package, but just not distribute it. I cooked it in for a while, when I was determined to convince myself I hadn't blown twenty bucks on a piece of crap. Why do you need to speed up total commander? I use it all the time, too, and it's pretty snappy. I'd suggest limiting the number of processes and not using manila to optimize speed.
Click to expand...
Click to collapse
i wanted to speed up total commander because its slow at accessing some folders eg, accessing the windows folder, there is a lag i dont like waiting for and increasing the cpu priorities for TC would reduce this lag
ive deleted the manila package, it eats up way too much storage/ram, so iv made my own skin for a today screen, which is aprox 1mb.
obviously manila is eye candy but im prepared to loose it for the increase in storage/ram.
i also didnt want manila in my rom due to the fact i dont actually like it, ok some stuff is cool eg, album and audio manager the way they rotate and the slide effect but its so gdam popular so most roms look the same, i wanted my rom to be differant. (i didnt want to be a sheep )
you gave me an idea for increasing the touch velocity of the finger scrolling, could anyone tell me whats the highest velocity were able to use?
(both up and down velocities? )
is there one for left and right?
(obviously there must be, but do you know whats it called so i can find it?)
thanks again dude!
Rn
The easiest way to speed up access to the windows folder is just to select 'hide files in rom' in the settings. Then you can get into it quickly. Looking at rom files is pretty useless most of the time, anyway. The downside is that TC then doesn't show the plugins folder in the device root. You can also set shortcuts on the hotlist to folders you might want to access, like startup or the start menu. Finally, you can just limit the number of rom files during cooking to speed things up; the fewer the better, obviously.
...
Farmer Ted said:
The easiest way to speed up access to the windows folder is just to select 'hide files in rom' in the settings. Then you can get into it quickly. Looking at rom files is pretty useless most of the time, anyway.
The downside is that TC then doesn't show the plugins folder in the device root. You can also set shortcuts on the hotlist to folders you might want to access, like startup or the start menu. Finally, you can just limit the number of rom files during cooking to speed things up; the fewer the better, obviously.
Click to expand...
Click to collapse
id rather have everything viewable in the rom rather than to hide files, useless or not. im sure everyone else would probably do the same, that way you can see exactly what you have got.
i also like to have hidden files always viewable on my pc too. eg, in my kitchen nothing is hidden, ive went through every folder and almost every file has had its hidden properties removed, including the files that dont un-hide when using the hidden files toggle on pc, which was weird
the plugin folder is one of the main functions i use TC for as i dont use regedit.exe or any other registry viewer other than TC. so i wouldnt want to be dissabling that function, if i dissable it i may as well add fexplore.exe back into the rom and use that instead
yeah, thats one of the good things about TC = the ability to create shortcuts with the >>>, however i always make them myself with a good old .txt file with the link wrote inside
agreed, the less files the better, obviously lol
at the moment my rom for blackstone is 103mb ... storage is aprox (18 - 20mb) ... ram is aprox (40 - 50mb) in use after the initial first boot and customisation.
ill search my kitchen for the finger velocity up/down scroll tonight.
if i can improve the scroll ill be nbecause the scroll is really crap!
Rn
btw:
if anyone wants to Alpha test my rom then private message me because i wont be uploading it for public use untill its Beta.
im just finishing the today screen skin but ill start letting people Alpha test it after that.
(basicly to find bugs, recomendations bla bla bla.)
I totally forgot this, but the process manager in sk tools has an option to create shortcuts with a command line that will change priorities. You could create one for total commander, and then use a mortscript that would launch TC, maybe wait a few seconds, then run the shortcut to bump up the priority.