yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] imfloflo:
@itje very small characters ..
[Touch Cruise ROM Development] JAYmasta:
ok here is my result on original clean wm.6.1
[Touch Cruise ROM Development] Fontanini:
official 6.1 rom released!

http://www.htc.com/uk/SupportDownload.aspx?p_id=59&cat=2&dl_id=113

anyone here who can see if there are any drivers in it?

3d drivers should be in it but how about the 2d drivers? is the scrolling in all programs smooth now?
[Touch Cruise ROM Development] Dave_Kjam:
Benchmarking

First of all, sorry if this already been posted.

So, it seems to me that you guys have improved the polaris 3D performance, a LOT. Am I correct?

I think that this thread is already so long and with daily progresses that most of us get lost between the way.

So wouldnt it be nice if someone posted benchmark results for the driver solution(s) you guys have now and compare it, let's say with the omnia drivers. This would be a very good tool, for you guys to see if you still have margin to further improve the driver, and to the rest of us to see the results of you work.

Keep up motivated you all.
[Touch Cruise ROM Development] SuperJMN:
I'll try the official ROM in a few minutes. I'm going to see if benchmarks are better or not.
[Touch Cruise ROM Development] Chainfire:
Someone please mirror this download ASAP!

EDIT: nvm, seems to be the same rom that was leaked a bit ago.
[Touch Cruise ROM Development] SuperJMN:
I'm uploading it at the moment. I flashed it and it appears that it improves nothing... but the splash screen :(

When I was downloading the file I saw this in the HTC website:

"The best possible experience"? Don't laugh at us!
[Touch Cruise ROM Development] JAYmasta:
agree, it might not what you expect, but it works, you will need only a driver

now people can call to me without problem not as before, people call me but phone was like switched off etc...
[Touch Cruise ROM Development] SuperJMN:
The Official 6.1 ROM:

http://www.mediafire.com/?a2mubnmzbzu

I've uploading although they say the one leaked some time ago and this one, are the same.
[Touch Cruise ROM Development] bally3:
try this someone:

regedit:

HKLM\SOFTWARE\HTC\YOUTUBE\ENABLESW = 0

soft reset

try youtube on manila ... :)
[Touch Cruise ROM Development] itje:
I dumped norwegian wm6.1 official

Nothing to salute for regarding drivers.
[Touch Cruise ROM Development] bally3:
whats the version of the ddi?
[Touch Cruise ROM Development] JAYmasta:
bally3 any news, what next, excitation is rising....
[Touch Cruise ROM Development] itje:
3.13..0.0

nothing new
[Touch Cruise ROM Development] bally3:
and you did the regedit to change it to d3dm_ati.dll??
[Touch Cruise ROM Development] itje:
hehe, yeah not after trying the official

but I cooked one on the NOR version
[Touch Cruise ROM Development] NeoS:
So, anyone got the new official wwe rom files ripped? Any differences?
[Touch Cruise ROM Development] bally3:
gwaan.. you're not STILL expecting the miracle 2d driver are you?? :p
[Touch Cruise ROM Development] bally3:
I've made another discovery...

Been testing it all day....

I managed to add a remotehook on a while back and then couldnt remember what I did...

Today I figured it... Add remotehook and the htc_d3dm.dll in d3dm key.

Interestingly enough.. it is being used cos If you try to copy over the dll file it wont let you..

So far benches are exactly the same but heres the twist:

Localhook = software

RemoteHook = hardware

But it doesnt work if you put the files the other way round :confused:
[Touch Cruise ROM Development] gregy74:
The size is exactly same, 84,627.504 b (installer).

So I think that this is exacty same ROM.
[Touch Cruise ROM Development] NeoS:
NuShrike (and some others) told you that the Polaris uses localhook for 2D and 3D. So why use remotehook? and i'm the dense one? lol.
[Touch Cruise ROM Development] bally3:
he did not.. I think... :rolleyes:

I'm sure he said soft/hardware... anyhoo.. I'm testing positive for a bunch of crazy ideas if this works... watch this space! :p
[Touch Cruise ROM Development] bally3:
Its not EXACTLY the same.. I mean they DID change the title to WWE .. :rolleyes:
[Touch Cruise ROM Development] rogro82:
MSDN

You can also put hardware acc in a locally hooked driver
[Touch Cruise ROM Development] rogro82:
So the main reason why u cant override it i think its because its loaded by gwes.... do u have remote process viewer? u can see for ur self ;)
[Touch Cruise ROM Development] bally3:
i dont .. but I shall acquire one and see..

If it is being loaded.. then theres some interesting possibilities here... it doesnt like the omnio driver being remotehooked by the way...
[Touch Cruise ROM Development] bally3:
so if its being loaded by gwes.. and its finicky about what it loads.. is it necessary that its being used?

or more to the point... can we use it ..?
[Touch Cruise ROM Development] NikMel:
The rom that is on htc site and was here available are identical!

It was just to wright something :rolleyes::D:confused:
[Touch Cruise ROM Development] bally3:
Well.. duh! LOL!!

I WAS being sarcastic you know.. :D Its true.. nobody gets British humor!

but seriously.. I do not understand after 1300+ posts in this thread going over this issue of what 6.1 was going to be... why people STILL think it was going to be something special!
[Touch Cruise ROM Development] gregy74:
I understand your humor, and I am not English:)

But I don't understand HTC as a company, the rule of HTC is: If you want drivers just buy some new hitech device:mad:

They will never publish drivers for Polarish and Kaiser. If they will publish drivers, who will buy new device?? This is the rule of HTC. This is shame:mad:

I think that HTC will never have so much costumers, If there was no XDA-develepors forum. I like HTC, but only because of this forum.

And there is really big shame that people must develope drivers by himself. SHAME OF YOU HTC
[Touch Cruise ROM Development] JAYmasta:
better e-mail to them, copy this, and put also (f**k you htc i will never buy device your company and tell same to all my friends)
[Touch Cruise ROM Development] NeoS:
So, back on topic: is it possible we use the omnia as LOCAL and the ati_d3dm as remote? Local is software and omnia kix ass there. But ati is hardware, so... in my head it makes sense. :D
[Touch Cruise ROM Development] bally3:
no.. unfortunately.. it doesnt mind the htc_d3dm.dll

but it complains about the omnio.. but the htc file is just a reference file.
[Touch Cruise ROM Development] bally3:
deleted - ignore this as I've just realised the results are diifferent if you soft reset after each change.
[Touch Cruise ROM Development] bally3:
Latest Benchmarks:

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 : 5955

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

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

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

GLBenchmark HD ES 1.0 : 1526 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 : 110332 Triangles/s

Lights: Omni x 1 : 41885 Triangles/s

Lights: Parallel x 1 : 110332 Triangles/s

Lights: Parallel x 2 : 3598075 Triangles/s

Lights: Parallel x 4 : 3571513 Triangles/s

Lights: Parallel x 8 : 3535757 Triangles/s

Lights: Spot x 1 : 44950 Triangles/s

Swapbuffer speed : 3718

Texture Filter: LINEAR : 3637917 Triangles/s

Texture Filter: LINEAR_MIPMAP_LINEAR : 3653241 Triangles/s

Texture Filter: LINEAR_MIPMAP_NEAREST : 3654263 Triangles/s

Texture Filter: NEAREST : 3650176 Triangles/s

Texture Filter: NEAREST_MIPMAP_LINEAR : 3663457 Triangles/s

Texture Filter: NEAREST_MIPMAP_NEAREST : 3662436 Triangles/s

Texture Size: 1024x1024 : 3663457 Triangles/s

Texture Size: 128x128 : 3659371 Triangles/s

Texture Size: 256x256 : 3638939 Triangles/s

Texture Size: 512x512 : 3646090 Triangles/s

Texture Size: 64x64 : 3649155 Triangles/s

Triangles: Flat Shaded + Color : 3732926 Triangles/s

Triangles: Smooth Shaded + Color : 3725775 Triangles/s

Triangles: Textured : 3642004 Triangles/s

Triangles: Textured + Color : 3653241 Triangles/s
[Touch Cruise ROM Development] benleonheart:
Sad part is,

even if you guys dont buy the high tech devices or something... and tell your friends, HTC still sells a crapload of old devices.

For example, here in Honduras, you'll see many people now carrying Polaris', Kaiser's and Elf's for the simple reason that they're included in the telephone plan, but, do they KNOW how to use the Polaris? up to some level, playing solitaire maybe... Do they even know the potential that a Polaris has? Hell no.

They just buy them here because that's like "oooh, my cell is more expensive than yours", to show it off, and sadly, they do so with WM6.0 lol.

So HTC has not to worry about people not buying their devices since mainstreamers always will.

Now, us, in the other hand, buy the device cuz we've been looking forward to it for so long that... we just have to buy it and get the best out of a pocket pc, this is my 1st HTC device, but I am severely satisfied with it...

Nice jump from motorola, may I say...

But to make my decision on to which model to buy (diamond wasnt available here), i spent like a week on forums and stuff like that (and ended up here)...

After seeing the potential the Polaris has, I said, wtf this is it, the one I will buy... so i bought it...

And let me say something... Diamond has got NOTHING on Polaris ;) ... er... except the drivers xD

Well, cheers!

y pa los ke saben espanol pues, saludo desde honduras razaaaaaas!
[Touch Cruise ROM Development] rogro82:
Bally3 what rom did you use to get this swapbuffer speed? Mine is always around 3000...

The rest is the same except my triangles are all above 3700000 except for lights.
[Touch Cruise ROM Development] NeoS:
Is that benchmark accomplished by adding something to remotehook?
[Touch Cruise ROM Development] bally3:
No remotehook... that I'm leaving for the time being as NuShrike says, its been tried, tested and found wanting.

I'm using itje's v3 - (I kinda like his roms but the rom doesnt matter)

I copied the NEW CA files as my technique before and added v6 of NuShrikes files.

The Benchmarks with this technique came at about 301fps - swapbuffers under 3000.

But I have made a lot of changes in registry - changed all "SW" to 0 to force hardware - changed glyphcache to "32768" and basically anything in the registry I could find that affected performance.

(Changed screen size to "480x640" but it doesnt have made any difference).

With all the tweak though, theres hardly any lag on the device and even the camera is working much faster.

Try the youtube tweak I posted earlier and see what I mean!
[Touch Cruise ROM Development] NeoS:
Yeah, about youtube. I think i said it already has the sw=0 on Syrius. I still have lot of "frameskips" so to speak.

I'm nudging towards flashing itje's OPAL soon, once he fixes the blank screen issue we used to have. Maybe one of use can assist him there?
[Touch Cruise ROM Development] bally3:
He needs to update the files, send him the updated files minus the 3.13 ddi.. that should fix it.
[Touch Cruise ROM Development] NeoS:
Does it? remember i had problems when NOT overwriting ddi.dll 3.13. I'll send them just to be sure.
[Touch Cruise ROM Development] imfloflo:
So itje will release a new rom ?
[Touch Cruise ROM Development] bally3:
yes but your problem was DIF related... remember??
[Touch Cruise ROM Development] bally3:
------------------------Polaris: -------Kaiser: -------Diamond: -----Touch Pro:

Swapbuffer speed: 3718 682 1100 1102

Comparison with GLBenchmark with our latest figures.
[Touch Cruise ROM Development] Svenvdmeer:
Sounds nice but for all the noobs out here... what does the swapbuffer do??
[Touch Cruise ROM Development] rogro82:
Buffer swapping :D
[Touch Cruise ROM Development] bally3:
Its an OpenGL drawing method.

Essentially, it uses two buffers, one on the screen and another one where it draws. When its finished one it "swaps" them. The swapbuffer speed is how fast it draws and swaps.

Hope that helps :)
[Touch Cruise ROM Development] bally3:
ok.. mine was clearer.. yours was better LOL! :p
[Touch Cruise ROM Development] bally3:
What you think of the comparisons rogro?

Of course I can only assume that the others are without hardax..
[Touch Cruise ROM Development] NeoS:
AKA Backbuffering? If so, this roccks. ;) (see how i wrote that with double c? That means HOW MUCH!)
[Touch Cruise ROM Development] NikMel:
bally3,

your benchmark is so good b/c of files your are using not registry settings.

my first benchmark was also that good.:) that was with the original version of libgles.dll from htcca site/cab
[Touch Cruise ROM Development] NuShrike:
Just how fast the device is at switching between the two screen buffers (visible front, hidden back) without doing any other work such as AI, math, calculations, any drawing, etc. All the drawing happens on the back so you get smooth graphics without tearing, etc. How fast you can swap is one of the major limitations to FPS.

So divide the score by 10.. that's how much time it need to swap. So:

Polaris, as fast as it can -- 300 times a second

Kaiser (~60 fps): so limited to speed the LCD hardware update speed LCD is running @ some pseudo-60Hz power)

Diamond/Raphael (~100 times a second): not limited to LCD speed, but limited by other (HTC) issues

Nikmel: So which FPS you were getting originally, since you were here before everybody else? :) It should have been closer to the Kaiser speed, but it seems like the Polaris is just faster anyways. :)
[Touch Cruise ROM Development] NeoS:
GLBecnhmark.com finally noticed our Polaris drivers. Check this link and compare the Touch Cruise with the Touch pro or Iphone. You'll have a good laugh. ;)

http://www.glbenchmark.com/compare.jsp?benchmark=glpro&D1=Polaris
[Touch Cruise ROM Development] imfloflo:
Comparing Cruise and Kaiser and we have better result with polaris :)

http://www.glbenchmark.com/compare.jsp?benchmark=glpro&showhide=true&D1=HTC P4550 TyTN II (Kaiser)&D2=HTC P3650 Touch Cruise (Polaris)
[Touch Cruise ROM Development] bally3:
the results are good but lets not forget the kaiser driver will improve soon too.
[Touch Cruise ROM Development] imfloflo:
With your help and the polaris driver, or it's another team working on it ?
[Touch Cruise ROM Development] bally3:
We aim to share what we've learnt with everyone as is the spirit of xda-devs which will become apparent soon.

The improvements made to the 3D driver shold be transferable and I have heard its already being looked at, but if the Kaiser developers need our assistance - not that I think they'd need it - I'm sure I speak for the whole team that we would be happy to help.

We should not forget its the Kaiser developers that created the driver - we merely ported it to the Polaris - no small achievement - But we should also be thankful to Chainfire and the Kaiser crew. :)
[Touch Cruise ROM Development] SuperJMN:
As a user, I totally agree. Everyone counts.

My personal thanks to the Kaiser Team.
[Touch Cruise ROM Development] Chainfire:
Latest Kaiser driver set outperforms the Cruise again :D
[Touch Cruise ROM Development] rogro82:
Built on the same files? :rolleyes:

When are u going to release it? :D Wanna see whats inside ;)
[Touch Cruise ROM Development] Chainfire:
It'll be released in an hour or so.

Yeah should be mostly the same files, barring some Polaris and Kaiser specific stuff.
[Touch Cruise ROM Development] rogro82:
k... are you also using the 3.13 ddi or sticking with the 3.28?
[Touch Cruise ROM Development] Chainfire:
TBH, I'm not 100% sure, but I think 3.28.
[Touch Cruise ROM Development] rogro82:
k so the major change will be the brute force screen updating using the extescape then i guess
[Touch Cruise ROM Development] Chainfire:
You know who to ask for the details. However, something else has changed, as we used ExtEscape before though the performance now is higher than it was then.
[Touch Cruise ROM Development] rogro82:
i know a releasedc was added.. but i dont know if it was there in the past.. that was causing the slow down while running 3d apps a bit longer

Ill go and stalk ns to see if he has come up with some more improvements :)
[Touch Cruise ROM Development] Chainfire:
Package updated.
[Touch Cruise ROM Development] rogro82:
Thanks for the polaris info mentioned ;) im dll the package as we speak :D
[Touch Cruise ROM Development] NeoS:
oooh, progress... I love progress. Both Kaiser and Polaris now working almost the way they should.
[Touch Cruise ROM Development] c3ro:
Great progress so far! Keep the work : )
[Touch Cruise ROM Development] bally3:
Can someone post up a working QuickGPS.exe file for me please? its the only bug on itje's and I'm loathe to get rid of it for the time being while I'm testing..

Reached a new high... 384fps.. :)

Also might have resolved our backlight issue.
[Touch Cruise ROM Development] NeoS:
All by just regtweaks?
[Touch Cruise ROM Development] bally3:
btw, does anyone have d3d demo with the fps showing? mine doesnt show when its the ati drivers running but does with all the others :confused:

ps. Chainfire, love to see some benchmarks on here or the kaiser thread :)
[Touch Cruise ROM Development] bally3:
lol.. yeah.. and some tinkering ;)
[Touch Cruise ROM Development] radem205:
Here you go....
[Touch Cruise ROM Development] rogro82:
Bally did u use the maxbackbuffers or something else to achieve it?
[Touch Cruise ROM Development] bally3:
Thanks radem - worked a treat! :)
[Touch Cruise ROM Development] imfloflo:
New package, long time without news video or new cab for the most courageous people :)
[Touch Cruise ROM Development] whitealien:
OMFG !!!!

working QuikGPS hahahahahahaha :D

I was looking for this ages :D

Many, many, thanks m8
[Touch Cruise ROM Development] radem205:
Haha, your welcome.

@Bally3: What has QuickGPS to do with the 3D driver progress? :)
[Touch Cruise ROM Development] bally3:
Amazing how simple issues seem to have dogged so many :confused:

Why didnt anyone think of it before???
[Touch Cruise ROM Development] bally3:
Maxbackbuffers are still being tested - so far putting it above 1 give lower fps.

Whats yours set at?
[Touch Cruise ROM Development] NeoS:
You know what would be really cool to test with our new driver? Google Streetview.
[Touch Cruise ROM Development] bally3:
Go for it ;)
[Touch Cruise ROM Development] psicobra@hotmail.com:
where can i get the lights program i want to test it
[Touch Cruise ROM Development] imfloflo:
Don't forget to record it :p
[Touch Cruise ROM Development] cbandarrinha:
Hi,

I'd love to test it with Google Streetview but I don't know where to get it to use on my Polaris. Anyone??

Thank you
[Touch Cruise ROM Development] itje:
I found this in oemdrivers from opal rom

it say core 3d engine, im not sure if this is relevant, but id rather put it up then not :)

cheers
[Touch Cruise ROM Development] NeoS:
Thanks, i'll run a dependancy test.
[Touch Cruise ROM Development] rogro82:
looking at the name i think its the omap 3d software driver...
[Touch Cruise ROM Development] NeoS:
these are the functions:

ti3dAmbientMaterialSource

ti3dBlendParameters

ti3dClearBackBuffer

ti3dClearDepthStencil

ti3dCullMode

ti3dDeInit

ti3dDeleteTexture

ti3dDiffuseMaterialSource

ti3dDrawIndexPrimitive

ti3dDrawIndexProcessedPrimitive

ti3dDrawLastPixel

ti3dDrawPrimitive

ti3dDrawProcessedPrimitive

ti3dEnableAlphaBlend

ti3dEnableAlphaTest

ti3dEnableColorVertex

ti3dEnableDepthTest

ti3dEnableFog

ti3dEnableLight

ti3dEnableLighting

ti3dEnableNormalRescale

ti3dEnableStencil

ti3dEnableTexturePerspectiveCorrection

ti3dEnableTextureProjected

ti3dEnableTextureTransform

ti3dEnableTextures

ti3dInit

ti3dMaterial

ti3dPerfDrvEscape

ti3dPerfQueryEsc

ti3dProcessVertex

ti3dRegisterImage

ti3dSetAlphaCompareFunction

ti3dSetAmbient

ti3dSetBackFrameBuffer

ti3dSetColorMask

ti3dSetDepthCompareFunction

ti3dSetDepthStencilBuffer

ti3dSetFillMode

ti3dSetFogColor

ti3dSetFogDensity

ti3dSetFogEnd

ti3dSetFogMode

ti3dSetFogStart

ti3dSetLight

ti3dSetShadeMode

ti3dSetStencilCompareFunction

ti3dSetStencilOperation

ti3dSetStencilWriteMask

ti3dSetTexStageWrapMode

ti3dSetTextureAddressMode

ti3dSetTextureArgument

ti3dSetTextureColorOp

ti3dSetTextureCoordinateFlags

ti3dSetTextureFactorColor

ti3dSetTextureFilter

ti3dSetWindowExtents

ti3dSetZWriteEnable

ti3dSpecularMaterialSource

ti3dTransform

ti3dUnsetDepthStencilBuffer

ti3dViewport
[Touch Cruise ROM Development] itje:
guess there is no use for it then :)
[Touch Cruise ROM Development] NuShrike:
Looks like opengl but missing many standard calls. Seems to be CPU based, but maybe something can be learned from it eventually.
[Touch Cruise ROM Development] itje:
eerrr..

guess there is use for it then :D:rolleyes:
[Touch Cruise ROM Development] rogro82:
It is indeed mentioned at msdn and some other sources as being the (TI Texas Instruments) Omap CPU based D3DM driver.
[Touch Cruise ROM Development] maqui01:
Did you finally test google streets with the latest 3d drivers?? it would be interesting to see some results from some apps.

I'd like to thank to the whole 3d team for doing this job, it's amazing to see how this pda can be improved that much. I can't wait for a final release :D
[Touch Cruise ROM Development] NeoS:
I can't test it since i'm not in the US. Maybe someone with itje's Opal rom can?
[Touch Cruise ROM Development] imfloflo:
How can have streetview on our google cause on internet i can use it but in google maps 2.2.... i haven't any option.

Is there a soft or only with internet in opera?
[Touch Cruise ROM Development] maqui01:
Just being curious cause I work as a developer, did you decompile the ddi.dll and changing code or doing fixes on the rom to make It work? Which were the main changes you all did during the porting??
[Touch Cruise ROM Development] imfloflo:
@maqui01 in another post they say they will not release ddi.dll in their cab so i think they don"t touch this dll, http://xdaforums.com/showpost.php?p=2732881&postcount=84

but they use it in another dll and modify the jumping adresses by disassembling files (reflector ?? )
[Touch Cruise ROM Development] rogro82:
reflector wont get you anywhere it only handles managed code ;)
[Touch Cruise ROM Development] imfloflo:
yes i know it , so which soft do you use to read dll from our pda?
[Touch Cruise ROM Development] rogro82:
I use PE Explorer / Depency walker / IDA Pro, but these i use mainly for checking files and checking if ddis are capable / making the right calls to support 3d.

Besides that im mainly a c# dev and have written apps to invoke updating of remote dc's and using p/invokes to try to to make the backlight stay on and influence the way power management behaves when a 3d app is running.

This way i dont have to hack my way through all driver dlls but still let me find / try to find the answers to some problems ;)

The actual implementation of most code in the drivers has been done by someone else... not taking any credits as he deserves them the most.
[Touch Cruise ROM Development] dwaradzyn:
The results are indeed very impressive. I ran glbenchmark and I noticed that a significant number of tests did not produce any output on screen. What worries me is that tests with outstanding results were the "blank screen" tests. I'm suspecting that high result are caused by testing unimplemented (no operation) calls to 3d api.
[Touch Cruise ROM Development] NeoS:
Could you name a few?

Btw: rogro, any progress in that lighting thing? Or isn't it being looked at?
[Touch Cruise ROM Development] bally3:
The results you see mentioned are the swapbuffers which do show, we are aware of the failing tests but i do not mention these in my comparisons as we have not yet looked into these though nushrike did mention that any figure over 3m for the triangles was a failure.

Appreciate any light shed on this issue..