[Touch Cruise ROM Development] rogro82:
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 :rolleyes:

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 ).