yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] bally3:
Rogro, I wouldnt go public with that fix just yet.. tried it on swtos.. didnt work.. tried it on itje's new rom... hard reset required.

Tried a few different ways.. possible its only going to work on a clean rom.. (good news for NikMel though!).

;)
[Touch Cruise ROM Development] bally3:
Neos, nice one mate.. :)

Can you upload the complete set of ddl's from this rom please, I mean disptools.dll, wcr_rex.dll the lot..

and also a regdump if you would please :rolleyes:
[Touch Cruise ROM Development] bally3:
ok..some more light reading.. thought this bit was interesting:

"GDI+ is a library created to add rich drawing and imaging feature to the basic set of Windows APIs. It has been introduced in Windows 2000 timeframe and eventually became a basis of System.Drawing and System.Drawing.Imaging namespaces. GDI+ is a dual API. It has a set of rich objects, such as Graphics, Bitmap, Pen, Brush etc as well, as a flat API suitable for use in legacy C or for P/Invoking. Starting with Windows Mobile 5 (Pocket PC), GDI+ ships on Windows Mobile devices. Despite the fact that the desktop .NET drawing and imaging support is built on top of GDI+, the Compact Framework does not use it. This in part explains somewhat more Spartan selection of graphic features available in Compact framework. Of course one of the main reasons for this was the lack of universal availability of GDI+. E.g it is not present on 2003 and 2003 SE devices, any version of smartphone (including Windows Mobile 6 Standard) or basic Windows CE.

It is also important to understand that Windows Mobile version of GDI+ lacks many features of its desktop counterpart. Although it is 100% API-compatible, a lot of calls is simply not implemented. All it does is returning the corresponding status (NotImplemented) to the caller."

Source: http://community.opennetcf.com/articles/cf/archive/2007/10/31/using-gdi-on-windows-mobile.aspx
[Touch Cruise ROM Development] bally3:
and if you think it might help.. the .lib file you can use a wrapper to make it work apparently.
[Touch Cruise ROM Development] rogro82:
GdiPlus needs to be implemented by a software developer in their software...

http://community.opennetcf.com/articles/cf/archive/2007/10/31/using-gdi-on-windows-mobile.aspx

Alex Feinman already created a wrapper ;)
[Touch Cruise ROM Development] rogro82:
U sure u set all the registry settings? Im using udk's rom now and it works like a charm... Strange :rolleyes:

Ill try it on itjes rom later on... to verify it is/isnt working. wont mind hardreset nr 10000 since the start of this project :D
[Touch Cruise ROM Development] NeoS:
Files uploaded to project webspace.

Wce_rex.dll isn't found in the KS20 rom i have. I did hower find some other files which i put in the zipfile. Maybe we could use those?
[Touch Cruise ROM Development] NuShrike:
While you guys are so willing to hard-reset, can you also test out the touch.dll fix from the S600?

http://xdaforums.com/showthread.php?t=393387

Supposed to help with the huge device slowdown when touching the screen.
[Touch Cruise ROM Development] bally3:
Hi NuShrike :)

File freezes screen cant access.. hard reset time again..! ;)
[Touch Cruise ROM Development] NuShrike:
Wow, thanks for the attempt! I guess the search to fix the HTC touch bug goes on ...
[Touch Cruise ROM Development] bally3:
No problem.. Whats another hard reset tween friends eh? ;)

Do you think theres some validity with rogro's two ddi file method? I havent got it to work myself... but he seems pretty happy with it.
[Touch Cruise ROM Development] NuShrike:
I find it hard to believe that it even works... Maybe it is a new trick.

Has the negative test been tried? Just removing the .dll not named in the registry?

NeoS: do you guys really need a wce_rex.dll from the KS20 or another device? I do have the KS20 wce_rex, but didn't find it useful nor needed. They're also kinda different depending on WM6.0/WM6.1 for instance, and there's three different derivatives. One requires a whole different set of files and supports the ATI drivers (KS20, Diamond, etc), one doesn't support much of anything (WM6.0, Mogul, etc), and one that's a partial hybrid (Kaiser WM6.1). Between KS20 and Diamond, KS20 is using older trstai_extension to call hidden functions, and the Diamond replaces it with ONC RPC to call secret QCT functions.

Problem is we need the WM6.1 release for the KS20 and there isn't an official one as far as I know. Haven't the time yet to attempt a complete port of Diamond's stuff, which involves way too many files, and hard-resets...
[Touch Cruise ROM Development] bally3:
Well.. I've not had any luck that way.. I'll let Rogro try the negative test as it seems to work for him.

There seem to be quite a number of files in the ks520 that dont exist in the Polaris/Kaiser.

GDIPlus.dll

wce_vdec_driver.dll

to name a few..
[Touch Cruise ROM Development] vanvancool:
Yeah... please look at Post Nr. 25

http://xdaforums.com/showpost.php?p=2213146&postcount=25

some benchmark Infos + Tool...
[Touch Cruise ROM Development] NuShrike:
Okay, 3.13 DDI is almost identical to 3.28 when I quickly looked at exports, imports, DisplayInit, MDP overlay, and some other internal functionality. It looks like it has all the right functionality for plugging in the 3D too. I'm checking to see if the 3D driver patches assumed anything that let only 3.28 work.

Okay, try this out for me:

roll back your ROM to the stock state with the 3.13 ddi

install the HTC-CA drivers

install the previous _03 patch (the best IMO)

override the HTC-CA ahi2dati.dll in \Windows with the attached one

Let me know if 3D works or not. This is the first time I've seen a pre-3.28 DDI with ATI code in it. Btw, the HTC-CA ahi2dati.dll specifically loads and uses a file named ddi.dll, so it ignores whatever is set in the registry. Probably could be fixed, if needed.

polaris_ahi2dati_00.zip (4.1 KB, 9 views)
[Touch Cruise ROM Development] NikMel:
NuShrike,

I did that before. Its possible to run the htcca apps but then you have the same thing like running some other procces or tapping on start button to make the htcca apps move.

What I can say is I've compared msm_clk.dll from diferent rom's like diamond and I've found one.

Our problem was that with the latest lib*.dll's you put online the htcca app's are working good but some other opengl apps where just crashing and the msm_clk.dll I've found is the solver of that problem.

I still have to make sure that its true what I say and if I'm sure of it I'll put again my rom online for some testers.
[Touch Cruise ROM Development] rogro82:
Dont know if really is a pre-one. This ddi is the latest release for the polaris so maybe they are screwing up their numbering to make us confused :D

Gonna try somethings with the 3.13 ddi because this is the one that is best on other factors for the polaris.

Did you also noticed the "windows 2d renderer" mentioned in the 3.13 ddi? Havent seen that line in 3.28 or is just overlooked...

I thought i read that somewhere and thats why i tried using the 3.28 as main ddi and i guess thats the reason it works...
[Touch Cruise ROM Development] manaaa:
did you guys looked inside the new official opal rom? - maybe theres some usefull optimization.

http://xdaforums.com/showthread.php?t=430194

good work so far!

**edit**

i forgot, its not using same chipset, so skip that one : )
[Touch Cruise ROM Development] rogro82:
Flashed "clean" udk r0 Rom which has a 3.13 ddi,

added our basefiles ( didnt install the cab because it has 3.28 ddi in it )

and added the latest ahi2dati.dll NuShrike send i can confirm 3d is working on a 3.13 DDI. ;)

Will try to see if its stable... triangle ran at 313 fps.

Edit:

Spb benchmark result are good 1ms/8ms/2ms
[Touch Cruise ROM Development] bally3:
Hi Guys! :)

Just been readig through and decided to have a go..

Downloaded Ije's v3 - 3.13 with out kaiser files.

Copied over NuShrikes ahi2dati file.

Ran dll checker and copied files it required - including libgles.cm

- Video Memory initialised but cylinder static.

Copied the new libgles.cm and the libgles_cm_ks,dll

Ran lights... cylinder spiining again.. seems faster.

Ran triangles .. definitely faster and smoother..

Ran d3demo.exe.. looks faster.. cant make my mind up!

Ran BillboardFPS for 2 mins - still showing 2.380952 fps as before.

Running GLBenchmark.. will post results.. phones faster than it was with the 3.28... cant remember what it was like with stock rom as I havent used one with 3.13 in it for a while.. :)

Nice wotk NuShrike!
[Touch Cruise ROM Development] rogro82:
My gl benchmark running udk r0:

3D Rendering Quality: Bilinear Filter : 95% (Success)

3D Rendering Quality: Perspective Correction : 100% (Success)

3D Rendering Quality: Sub Pixel Precision : 95% (Success)

3D Rendering Quality: Trilinear Filter : 89% (Fail)

3D Rendering Quality: Z-buffer Precision : 99.1% (Success)

CPU Performance: Float : 565

CPU Performance: Integer : 5954

Fill Rate: Multi-Textured, 2x2 : 16005 kTexels/s

Fill Rate: Multi-textured, 4x2 : 18125 kTexels/s

Fill Rate: Single-textured, 4x1 : 27034 kTexels/s

GLBenchmark HD ES 1.0 : 1528 Frames

GLBenchmark HD ES 1.1 : Failed / Not supported

GLBenchmark Pro ES 1.0 : 80 Frames

GLBenchmark Pro ES 1.1 : Failed / Not supported

Lights: Ambient x 1 : 117484 Triangles/s

Lights: Omni x 1 : 43928 Triangles/s

Lights: Parallel x 1 : 119527 Triangles/s

Lights: Parallel x 2 : 3639960 Triangles/s

Lights: Parallel x 4 : 3619528 Triangles/s

Lights: Parallel x 8 : 3590924 Triangles/s

Lights: Spot x 1 : 45972 Triangles/s

Swapbuffer speed : 2987

Texture Filter: LINEAR : 3722710 Triangles/s

Texture Filter: LINEAR_MIPMAP_LINEAR : 3686954 Triangles/s

Texture Filter: LINEAR_MIPMAP_NEAREST : 3718624 Triangles/s

Texture Filter: NEAREST : 3713516 Triangles/s

Texture Filter: NEAREST_MIPMAP_LINEAR : 3727818 Triangles/s

Texture Filter: NEAREST_MIPMAP_NEAREST : 3724753 Triangles/s

Texture Size: 1024x1024 : 3721688 Triangles/s

Texture Size: 128x128 : 3711472 Triangles/s

Texture Size: 256x256 : 3714537 Triangles/s

Texture Size: 512x512 : 3721688 Triangles/s

Texture Size: 64x64 : 3718624 Triangles/s

Triangles: Flat Shaded + Color : 3782984 Triangles/s

Triangles: Smooth Shaded + Color : 3794222 Triangles/s

Triangles: Textured : 3715559 Triangles/s

Triangles: Textured + Color : 3699213 Triangles/s
[Touch Cruise ROM Development] NikMel:
the only problem is that the app's are running not as smooth as with 3.28 but it runs and it means that we have an original file that was made for polaris
[Touch Cruise ROM Development] bally3:
Itjes Rom and GLBenchmarks:

3D Rendering Quality: Bilinear Filter : 96% (Success)

3D Rendering Quality: Perspective Correction : 100% (Success)

3D Rendering Quality: Sub Pixel Precision : 95% (Success)

3D Rendering Quality: Trilinear Filter : 89% (Fail)

3D Rendering Quality: Z-buffer Precision : 99.1% (Success)

CPU Performance: Float : 562

CPU Performance: Integer : 5963

Fill Rate: Multi-Textured, 2x2 : 15974 kTexels/s

Fill Rate: Multi-textured, 4x2 : 18186 kTexels/s

Fill Rate: Single-textured, 4x1 : 27034 kTexels/s

GLBenchmark HD ES 1.0 : 1531 Frames

GLBenchmark HD ES 1.1 : Failed / Not supported

GLBenchmark Pro ES 1.0 : 80 Frames

GLBenchmark Pro ES 1.1 : Failed / Not supported

Lights: Ambient x 1 : 117484 Triangles/s

Lights: Omni x 1 : 44950 Triangles/s

Lights: Parallel x 1 : 119527 Triangles/s

Lights: Parallel x 2 : 3887188 Triangles/s

Lights: Parallel x 4 : 3887188 Triangles/s

Lights: Parallel x 8 : 3884123 Triangles/s

Lights: Spot x 1 : 45972 Triangles/s

Swapbuffer speed : 3400

Texture Filter: LINEAR : 3891274 Triangles/s

Texture Filter: LINEAR_MIPMAP_LINEAR : 3886166 Triangles/s

Texture Filter: LINEAR_MIPMAP_NEAREST : 3883101 Triangles/s

Texture Filter: NEAREST : 3883101 Triangles/s

Texture Filter: NEAREST_MIPMAP_LINEAR : 3880036 Triangles/s

Texture Filter: NEAREST_MIPMAP_NEAREST : 3884123 Triangles/s

Texture Size: 1024x1024 : 3886166 Triangles/s

Texture Size: 128x128 : 3884123 Triangles/s

Texture Size: 256x256 : 3889231 Triangles/s

Texture Size: 512x512 : 3892296 Triangles/s

Texture Size: 64x64 : 3889231 Triangles/s

Triangles: Flat Shaded + Color : 3891274 Triangles/s

Triangles: Smooth Shaded + Color : 3894339 Triangles/s

Triangles: Textured : 3886166 Triangles/s

Triangles: Textured + Color : 3883101 Triangles/s
[Touch Cruise ROM Development] JAYmasta:
ati3d_drivers-dll from touch-it rom. maybe we start test on official rom also ?
[Touch Cruise ROM Development] NeoS:
So, we're using the stock 3.13 from now on? I fiure 3.13 is older than 3.28, so there must be something "improved" right? otherwise you wouldn't update your files. (if i were the programmer that is)
[Touch Cruise ROM Development] NeoS:
What do you mean "maybe we start test on official rom"?
[Touch Cruise ROM Development] imfloflo:
So Itjes rom seems to be a little better than udK R0 wait the R1 release to see which ddi.dll udK choose to integrate in his release
[Touch Cruise ROM Development] NeoS:
Weel, we haven't heard anything from other chefs except itje. So I do hope they react and start using our driver. We need more testing material.
[Touch Cruise ROM Development] imfloflo:
udK read this thread lot of time as we can see when he is online :)

He knows all progress you have made and if he juges the driver are stable he 'll incorporate them in his rom.
[Touch Cruise ROM Development] JAYmasta:
I mean you are testing the driver only at certain ROM, when it will start to like RUU_Polaris_HTC_WWE_3.13.405.0_radio_sign_25.85.30.07_1.59.42.15_Ship??
[Touch Cruise ROM Development] bally3:
Soon JayMasta.. if the 3.13 driver appears to be stable we may consider a release of the cab to a few testers. As you can see from the posts, there is a lot to do and a lot of changes being made from day to day.
[Touch Cruise ROM Development] bally3:
My fault Neos, I've been busy with .. well normal life! :rolleyes:

Epimazzo has been messaging me and he is currently putting the driver through its paces and comparing the resullts to his rom.

udk has also been in contact also and is testing the drivers at this time - still waiting to hear from him but I'm sure it'll be a thorough analysis of the drivers, if I know anything about him!

Patience is a virtue here.. the chefs have their own roms and their own threads to maintain and although the driver could be a major boost to the roms, its only application is to 3D and therefore to a larger extent an addition to what the roms cater for which is stability, speed (2D as well as 3D if not more so).

We gave the files to the chefs on Sunday.. its Tuesday.. hardly enogh time for a chef to put the driver through its paces. Itje's method was different - he incorporated the driver and made sure it was working then let it out to his users to see how they went with it. Every chef has his own approach to testing new software - its good that these different methods are being adopted as it allows us to get a fuller picture of the drivers capablilities and its stability.
[Touch Cruise ROM Development] JAYmasta:
Yes, I understand the lack of patience, want to test, and sit only on the official firmware

can explain the difference between????

GLBenchmark_Community_Full_1_02_WM5_CM

GLBenchmark_Community_Full_1_02_WM5_CL
[Touch Cruise ROM Development] bally3:
This is probably more to do with the driver file versions than any particular rom - the only rom that I have seen that has consistently provided improved results is NikMels stock rom with the driver cooked in - and I presume its because its a clean rom (No Manila 2D etc.)

NikMel: I take it you're already cooking these in? if you think its stable enough, seeing that its no longer using an alien ddi file, would you consider releasing a clean rom version once you're happy with the results please?

It seems to be what a number of people want and might be interesting to see what the feedback is.
[Touch Cruise ROM Development] itje:
I have made a rom that has been cleaned out (very little apps/files etc) with the new drivers. And Its really working well. But im on very tight schedule right now, but I will post the results later. I might try with another build aswell.
[Touch Cruise ROM Development] bally3:
Thats great itje - will be interesting to compare the results and see whether its the clean rom or other factors that affect benchmark figures.

Can you do me a teeny weeny favour itje? I had to flash to your v3 without the 3d drivers for my testing and my spb backup has messed up the theme. Could you post up your latest touch-it tsk file pllease? :)
[Touch Cruise ROM Development] itje:
sure :) no problem
[Touch Cruise ROM Development] bally3:
Thanks my firend :)

Tried to use the black panther theme but it just didnt look right!
[Touch Cruise ROM Development] itje:
Just cooked and flashed with dd1 3.13 and the other new files. works very well at first impression
[Touch Cruise ROM Development] itje:
here is result with 3.13

Ill try do one with previous in a while
[Touch Cruise ROM Development] radem205:
It's a huge difference against this one: http://xdaforums.com/showpost.php?p=2703565&postcount=116

Edit: With Itje 3.5 beta (clean), I have these results:

Especcialy the DIB Bitblt is a huge difference!
[Touch Cruise ROM Development] NuShrike:
Cool, it all works, and maybe just corrupted msm_clk.dll left to check... :D
[Touch Cruise ROM Development] rogro82:
Yep finally getting somewhere :D

Im glad we can use an official polaris ddi now... NuShrike have you tested this ddi on a kaiser already? could be interesting since it makes so much difference for a polaris...
[Touch Cruise ROM Development] NeoS:
Great. I'll bake us a new cab for testing once I get home. I'll post the results in the group post.
[Touch Cruise ROM Development] NikMel:
Here you go a working msm_clk.dll!
[Touch Cruise ROM Development] NeoS:
Ok, i'm home ;)

I made a v0.04 cab and posted it "you know where".

- added NuShrike's ahi2dati wrapper

- added Nikmel's msm_clk.dll

Lights won't work. Another cool thing: i'm getting a Dutch Error :D

System error.

I guess the msm_clk doesn't like the ddi.dll too much, or there's something wrong with the combination of the two. I'll remove either one of them and create seperate cabs.
[Touch Cruise ROM Development] NikMel:
I have done it with 3.28 and 3.13+ahi2dati

We should make sure about the compatibility of ahi2dati with either of ddi.dll versions

Wath we know is that ahi2dati works with 3.13 but we should see if it works with 3.28 too:confused:

:rolleyes:
[Touch Cruise ROM Development] NeoS:
Hmm. This is weird.

I made a cab for both files. Didn't change ddi.dll so it's still 3.13, stock udK R0.

First tested the ahi2dati wrapper. didn't work.

Then i tried the msm_clk.dll, didn't work either. :confused:

What else did change that this won't work?
[Touch Cruise ROM Development] NuShrike:
The new ahi2dati.dll version 1.0.0.26914 (wrapper) won't work with 3.28.

This is a newly made one for Polaris simply because a certain data segment in the 3.13 ddi ends up at a different location in memory than the 3.28+ DDIs.

NeoS: so you followed my steps of stock rom, + latest HTC-CA drivers, + _03 (or _04) libgles_cm.dll (version 1.0.0.26909) and libgles_cm_ks.dll (version 1.0.0.26709), + (version 1.0.0.26914) ahi2dati.dll and 3D stops working?
[Touch Cruise ROM Development] bally3:
both mine and rogro's tests were down without the new clk file so it looks like thats your culprit.
[Touch Cruise ROM Development] bally3:
NikMel: link updated check pm. :)
[Touch Cruise ROM Development] NeoS:
That's what i'm missing. With the 26709, it won't work, giving me an error message in Dutch.

By the way, could we upload all the files to our shared webspace? Makes it easier to track differences. (and for me to put them in a cabfile)

p.s. read the team page
[Touch Cruise ROM Development] rogro82:
Dont remember if i did the test using the new msm_clk but i am running it at the moment without any problems...
[Touch Cruise ROM Development] NeoS:
I'll just wait for you guys to tell me: "Hey, put this into a cab and run it!"

I can't keep track...:(

off for a smoke.

We need ftp space. Works WAY better. And at least we can organize.
[Touch Cruise ROM Development] rogro82:
If you can put all the latest files in a new zip called basefiles_v2 that would be helpful...
[Touch Cruise ROM Development] NuShrike:
Pack _05 to consolidate my changes. This obsoletes all previous packs, and so I'm removing them.

rogro: I think the "windows 2d renderer" string is in all the DDI's I've looked at.

polaris20080930_05.zip (122.5 KB, 35 views)
[Touch Cruise ROM Development] bally3:
Thanks NuShrike.. will try this when I've recovered from my semi-brick.. again .. :o

Note to self: wce_pmem.dll is not to be touched :rolleyes:
[Touch Cruise ROM Development] rogro82:
funny overlooked it i think... most of the time first thing i check is the ScreenUpdateByCopy
[Touch Cruise ROM Development] Chainfire:
So, where are we?

As I'm not able to check in much I'm hardly following what is going on.

Do we have anything working yet? Good enough to build a CAB? :)
[Touch Cruise ROM Development] bally3:
Hi Chainfire :)

Unfortunately not, is the short answer.

We now have a poliaris specific driver - Thanks to NuShrike and Rogro82 - that should eventually work out-of-the box with the polaris ddi file - so less chances of stability problems and hopefully more scope to develop on.

A cab is way off at this point, as we've only just proven that the polaris ddi ver 3.13 is capable of hardware acceleration and we are testing to see how stable it is.
[Touch Cruise ROM Development] Chainfire:
All I can say is, the Kaiser drivers were not very stable at the time of first release either :)

My ultra-awesome CAB skills are at your disposal whenever, let me know and I'll roll it all up (and "have it released" *cough* on HTC-CA). Guess NuShrike will nudge me whenever it's alpha.

EDIT: By the way, why don't you guys drop in on IRC ? The way this topic goes makes me think that'd work a lot easier :P
[Touch Cruise ROM Development] bally3:
Time.. time time... I'm ill in bed at mo so the compy is my closest friend but I'll be struggling to fit things around in the following weeks.. same as everyone else I guess.. is there an easy way to get onto your irc without registering and downloading software etc?
[Touch Cruise ROM Development] rogro82:
Nah we are trying to flood google indexing with polaris 3d using xda :D

Im building a cab for myself at the moment so i dont have to grab the right files everytime i need to reflash ( every hour or so ;) )
[Touch Cruise ROM Development] SuperJMN:
It's really easy to get into IRC! You only have to follow the link that Chainfire has in his sign.

Also, if you have Opera for Windows, you can creat a chat account and select "Freenode" as the server, then enter the room #xda-devs

I'm there, with all the people, but Chainfire seems to be sleeping, hehe :P
[Touch Cruise ROM Development] SuperJMN:
Somebody talked about "flooding"

Yeah, flooding is what they call to what is happening in the IRC channel #xda-devs ;)

Bally3, Rogro, NeoS2007, Chainfire, NuShrike, imfloflo, cmonex, Olipro... some of the great ones there!

NuShrike, Chainfire, Bally3, NeoS2007, Rogro, are talking about the drivers together and I can't believe it :)

O_O
[Touch Cruise ROM Development] NuShrike:
My original copy of msm_clk.dll (properly modified for wce_reF.dll of course). Includes sha256 checksum.
[Touch Cruise ROM Development] NeoS:
Ghehe... I'm the exception ofcourse. NuShrike, the method you told me: it's not working. I still get a device exception. (and in Dutch) What files are copied from a dutch device?

I'm starting to think my device is the culprit, since my device was originally dutch...
[Touch Cruise ROM Development] JAYmasta:
can you test in this program -Vsbenchmark 2007- and put here results ?

on clean wm6.1 i got 1480 score total
[Touch Cruise ROM Development] itje:
Here is results from my Ported OPAL rom with 3d drivers (latest available package)
[Touch Cruise ROM Development] NuShrike:
All files wrapped up together again. :P Properly versioned to avoid confusion and with checksums.
[Touch Cruise ROM Development] SuperJMN:
The competent voices here say this benchmark is not good for 3D benchmarking :P