yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] bally3:
Wow! thats an interesting turn in events... ok.. I'm testing it myself now .. was trying to avoid another flash if I could help it lol!

Thanks again nikmel.. Did you install the htcclassaction driver or is it cooked into the rom?
[Touch Cruise ROM Development] NikMel:
I just used the CAB file from that site and instelled it
[Touch Cruise ROM Development] dwaradzyn:
Congratulations, i think it's the first time that someone is showing that 3d drivers work on Polaris :) Latest cab from htcclassaction.org does not work on udK Syrius R0. There must be something more for the drivers from CA to work than ddi.dll.
[Touch Cruise ROM Development] NikMel:
If you want to make it work you MUST use the FULL XIP from german rom and I do that.
[Touch Cruise ROM Development] dwaradzyn:
I flashed rom from DDI.zip and installed CA driver. It still does not work. It gives an exception at module coredll.dll at IDirect3DMobile.CreateDevice(). Exactly the same happen on Syrius R0. Running "DLL Checker" app does not help either.
[Touch Cruise ROM Development] bally3:
Nikmel, I'm getting the same.

Do you have any instructions or can you post YOUR cab file for us to try please?
[Touch Cruise ROM Development] NeoS:
I found another interestinf piece of info:

"Gwes.dll

The Graphics, Windowing and Events Subsystem (GWES) is responsible for all graphical output and all interactions with the user.

The drivers that reside in the GWES address space include display drivers, printer drivers, keyboard drivers, mouse drivers, and touch screen drivers."

I guess that's the one responsible. Do we have another GWES.dll different from the one i'm using?
[Touch Cruise ROM Development] NikMel:
There is no gwes.dll for windows mobile:o

its for windows ce platform
[Touch Cruise ROM Development] NeoS:
That must mean that GWES.exe does all the graphics calls?

I feel we're almost there. I just need to find a way to get the screen to stop scrolling.
[Touch Cruise ROM Development] NikMel:
Yes on that.

Screen scrolling is the killing part NeoS2007
[Touch Cruise ROM Development] bally3:
Hi everyone! :)

See we're still picking away at this.. good!

Thanks Neos2007 and NikMel.

I decided to take myself away for the day, get a break from it all.. its been a nice day over here for once!

Ok.. so heres what I've learnt (alongside reading huge amounts of technical pages!)....
[Touch Cruise ROM Development] bally3:
Firstly, I found a Kaiser ddi.dll ver. 3.14 from one of the threads on here.

This file works almost identically to the 3.28 supplied by NikMel, but it doesnt seem to be as stable. Reading some of the info on the threads about this file was known to be buggy

This tells me that we probably need to look at the other versions of this file to see what results we get (one of them might even solve the scrolling).

I say this because - again - I point out that the Kaiser and the Cruise are almost idenctical with only a keyboard and bulkiness to seperate them.
[Touch Cruise ROM Development] bally3:
Secondly, we probably already knew this but, the cruise renderer was software optimised so that it could deliver the CUBE.

Most of the roms we use now dont have cube and with the advent of manilla its likely we're going to drop it altogether.

So my question is: Whats the big difference between the latest Kaiser rom and the polaris roms?

Could we compare them? I'm convinced that the answer lies in looking at the Kaiser registry/files.
[Touch Cruise ROM Development] bally3:
And here comes my biggie... swtos, nikmel and the stock rom are missing DDraw key in the reg altogether.. meaning that without that there is NO direct draw!

(Can anyone confirm that for the stock rom please? just check registry for hklm/system and see if theres a key called DDraw with a key inside it called DeviceEnum)

BUT the udk rom I've recently flashed back to has it in as default (I checked by doing a hard reset and even a reflash).

Now, by just adding the 3.28 ddi.dll file, does nothing different - it still uses the referenced driver happily to do its job.

But following NikMels instructions by adding the Kaiser driver (I still found the prev version from NikMel works better) we suddenly find that the DDraw is populated which to me means that the ddraw file is being used - ie DIRECT DRAW.

Of course ust adding the missing keys will give you the same results, but I now wonder where udk's rom came from or if he did make some reg adjustments, where he got them from?

I'll let that digest as I have a few more interesting revelations... but they can wait! :rolleyes:
[Touch Cruise ROM Development] NikMel:
this registry entry is generated automaticaly when you add d3dm_ati.dll to localhook and reboot your device
[Touch Cruise ROM Development] NeoS:
i found out that gwes.dll seems to control all video output. but like nikmel said, windows mobile doesnt have gwes.dll, just .exe. ive also seen a video by chainfire from the kaiser development, running manila without the scrolling! ive already pm'ed him about or last to solve issue.
[Touch Cruise ROM Development] bally3:
Doh! ok.. so thats not the problem - whew!

Pop Quiz - how many Hard Resets can a Polaris take before it gets fried!?! :rolleyes:
[Touch Cruise ROM Development] bally3:
NikMel, I'm prone to wanting to use your rom - for obvious reasons, I still believe finding the solution is a lot simpler if you can cook in these files.

Are you able to remove the certificate security?

Also can you cook up a version with the kaiser driver, 3d apps, rogro's hookswitcher and total commander in please?

Its a royal pain reloading these apps after every reset and also I'm interested to see what the difference would be when it is cooked in.. maybe it might help?
[Touch Cruise ROM Development] bally3:
something worthy of note... the ddi.dll file that you use should correspond with the disptools.dll due to the calls it makes to the ddi.file.

did you also use the disptools from the nld rom NikMel?
[Touch Cruise ROM Development] bally3:
OK...something wierd...

With the current setup I have 3.28 ddi.dll along with Kaiser drivers (prev version from NikMel).

Everything works as we know with the scrolling.. been playing around looking at different drivers.. and downloaded the Diamond Drivers from the kaiser forum.. it seemed to have a few more files in it than we have so, I copied them to the windows directory, making sure I said no to overwriting my current files.

I rebooted and it froze. Now if files are not being called, simply sticking them into the windows directory should not make any difference!?! (tell me if I'm wrong).

Hard resetting and trying same again to make sure I dont overwrite.. this time I'll use file explorer.. if it freezes.. its an interesting question...!
[Touch Cruise ROM Development] NikMel:
ddi.dll and disptools.dll are from nld rom but the only problem is that camera is not working and blasnk screen after standby:(
[Touch Cruise ROM Development] NikMel:
ddi.dll and disptools.dll from diamond don't work on our polaris

DDI.dll in diamond is loaded at early boottime this file is buildin to xip on diamond so this is the reason that can not be found in oem part of that rom.

Its not a problem to build all this think in a rom I will make it available soon.
[Touch Cruise ROM Development] NikMel:
I need a REAL tflo3d then I can test and make some research on it.
[Touch Cruise ROM Development] bally3:
The non working camera depends on the radio.. I'm sure mine worked with your rom installed. I had the udk r0 radio..

Like I said I cant use it as it contains flash 2.1 and I think it still has the prev net framework .. like the stock rom.. some additions would definately be welcome as it was pretty fast and would make an ideal testing rom - udk r0 is too bloated for testing purposes and swtos was fine but I had problems with the getting the video acceleration to initiate with our fixes.

Ideally if you can update flash and net compact and add the kaiser files, we'd be half way there as a hard reset would not set us back so much.
[Touch Cruise ROM Development] bally3:
The blank screen after standby is also resolved with using the prev version of the kaiser files.. sorry should have updated you guys on that! :p
[Touch Cruise ROM Development] NikMel:
I know what you mean:)
[Touch Cruise ROM Development] bally3:
right just trid that again and it froze. I made sure this time I didnt even copy the known files (ddi.dll, disptools.dll etc)

and it still froze!

any clues?? :confused:

Third time lucky... and I also noticed that the file sizes of the diamond files were mch bigger.. might take a look at what calls are made in them.

Anyone able to get a Diamond registry dump from anyone?
[Touch Cruise ROM Development] NikMel:
what part do you need?
[Touch Cruise ROM Development] bally3:
The whole dump, they're easy to navigate anyway in an editor.

I really want to make sure we're not missing anything.

Just our luck, it would end up being a simple edit.
[Touch Cruise ROM Development] bally3:
Ok.. I might be onto something.. let you know in a minute.. (Darn hard resets!) I might have something for the scrolling.
[Touch Cruise ROM Development] bally3:
Figured out how to test different ddi.dll files without suffering hard resets... rename it and just reference it into hklm/display/Active/Built into LCD/dll

then it only tries to initiate when you click a direct draw app! :D

do you only have to soft reset woo hoo!
[Touch Cruise ROM Development] NikMel:
Yes true!

Then after SR it get back to original state:)
[Touch Cruise ROM Development] bally3:
I've just had an idea... :eek:
[Touch Cruise ROM Development] bally3:
NikMel, can you test this for me please?

Do this, the files in this zip, use file explorer to copy them into your windows directory - make sure you do NOT overwrite existing files, always click no.

Then reboot and tell me if you see any difference or is it me?
[Touch Cruise ROM Development] bally3:
I'll tell you why.. before I was able to copy over most files INCLUDING the ddi file just by clicking yes to overwrite.

Now most of the Kaiser files are locked - as in use and I cant copy over them and its not for any read only lock either, plus the phone does feel more snappier.. especially when its intensive like accessing the windows directory which is always slow.

Could be placebo.. let me know what you think.. being faster isnt really important at this point.. but the fact that it could mean that the right files are in use when they werent before, could be.
[Touch Cruise ROM Development] NikMel:
I'll do that but now I have to make my polar bootup.:D:rolleyes:
[Touch Cruise ROM Development] bally3:
Ok.. I have some good news.. :)

NikMel, When we first started this, you remember I was playing with the ver 3.29 ddi, and you came with the 3.28?

I did think at the time ver 3.29 seemed to run more smoothly on mine .. but of course it crashed out on Lights and wouldnt initiate the hardware acceleration so I dropped it.

I just found that by renaming the 3.29 to another name.. you can drop it into the windows folder and assign it here.. hklm/display/primary/dll

and reboot.. phone seems to be a lot smoother and this time I'm definately not imagining it!
[Touch Cruise ROM Development] NikMel:
I've included 3.29 in my latest rom but the problem is the blank screen in that rom.

3.29 is the version coming from nld
[Touch Cruise ROM Development] bally3:
the original one you used that works is 3.28?

3,29 is the one I had... are we getting confused? :rolleyes:
[Touch Cruise ROM Development] NikMel:
3.29 come from kaiser NLD
[Touch Cruise ROM Development] bally3:
where does 3.28 come from then?
[Touch Cruise ROM Development] NikMel:
I think kaiser wwe
[Touch Cruise ROM Development] bally3:
hmm.. I seem to have increased my scrolling! I can hardly see the cylinder anymore! does that mean its running faster or just refreshing faster??
[Touch Cruise ROM Development] bally3:
Was the last kaiser ddi then or theres a later? could with seeing what later ones do on here.
[Touch Cruise ROM Development] imfloflo:
lol, too fast to read screen and if you install mymobiler to view your screen on your pc is it the same problem

http://www.mymobiler.com/
[Touch Cruise ROM Development] bally3:
Well I'm currently sat with probably the faster Polaris on the planet me thinks.. I need to do some tests..

Whats the best benchmark program (free!)
[Touch Cruise ROM Development] bally3:
Does anyone know if know if ppc's have snapshot backup programs, like the ones where you get on pc that you can select a recent snaphot to boot on if you crash.

Now that would be sweet! AND very time-saving!!

I might be wisful thinking... but I'd pay for a program like that! :p
[Touch Cruise ROM Development] d_dreamer:
Maybe Spb Backup might helps
[Touch Cruise ROM Development] bally3:
got that already a while back its a lifesaver but still involves a hard reset tho.

Could do with something that can avoid a hard reset and just load a snapshot like my pc does.

Thanks anyhoo! :)
[Touch Cruise ROM Development] NikMel:
to benchmark and be hapy with our device it works good!!!!

download the tools and run them

http://xdaforums.com/showpost.php?p=1733012&postcount=274
[Touch Cruise ROM Development] d_dreamer:
Even in safe mode?
[Touch Cruise ROM Development] bally3:
Thanks NikMel, just about to pm you.. !
[Touch Cruise ROM Development] NikMel:
I will make my other testing available soon and just install htcclass cab and run this **** http://www.glbenchmark.com/GLBenchmark_Community_Full_1_02_WM5_CM.cab it works really good!!:D
[Touch Cruise ROM Development] bally3:
Nice one!

Just to confirm NikMel, I no longer suffer the white screen as I use your previous htc drivers.

Those are the oness to cook in.
[Touch Cruise ROM Development] NikMel:
@bally3: when I include 3.29 driver from kaiser and the disptools.dll from kaiser too then I have that blank screen.

Which rom your arte using there?
[Touch Cruise ROM Development] bally3:
I'm still using udk, but you need to cook 3.28 into it not 3.29.
[Touch Cruise ROM Development] NikMel:
OK tnx!

I'll include it
[Touch Cruise ROM Development] bally3:
hold this info here I need it for reference:

"Does your device have a DDraw driver that supports GetAvailableVidMem?

The Intel XScale D3DM driver doesn't call this particular DDraw API explicitly and neither does the D3DM runtime DLL, so I'm guessing it's something in that particular test or maybe it's being called implicitly by another DDraw routine that the driver does call. "

Need to look into this.
[Touch Cruise ROM Development] bally3:
Ok... it seems ver 3.28 works fine with net compact 3.5 and older Kaiser cab - http://xdaforums.com/attachment.php?attachmentid=101073&d=1216766158

but ver 3.29 works fine with net compact 2 and new Kaiser cab as it was made to support older versions.

Do these numbers go backwards??? yesterday you told me NikMel that 3.5 was an older ddi.dll file and today I got a Diamond ddi.dll file with file version 1.53!! :confused:
[Touch Cruise ROM Development] NikMel:
there is no call like that
[Touch Cruise ROM Development] NikMel:
I've got even older version of diamond 1.34

I guess htc uses some other logic to number their files?!?!?!
[Touch Cruise ROM Development] bally3:
Polaris 3D acceleration - working apps UPDATE

I'm using udk R0 with net compact 3.5, ddi.dll ver 3.28 and the older Kaiser cab - I have no white screen issues and slowly but surely I'm getting the other apps working.

Currently Mesh, BillBoard, Lights, Lighting and a few other work with the scrolling issue.

I've referenced a new ddi file to the Display registry.

Increased speed and Coreplayer is able to play 180Mb avi file fairly smoothly using DirectDraw (dont know whether thats an improvement or not - havent tried it yet without).
[Touch Cruise ROM Development] NikMel:
I've just added 3.28 to my rom and still have blank screen after standby:o

How about disptools.dll?
[Touch Cruise ROM Development] bally3:
post it up NikMel, I'll give it a go.. I've had some luck today with diamond dlls.

With regard to the white screen, this I took from Kaiser thread:

"Just an intermediairy response...

we're aware the fix for the official ROMs broke some chef's ROMs compatibility. For those interested it has to do with a mutex handle that has to hijacked in runtime. The old cab did it one way that worked with some ROMs, the new cab did it in another way that seemed safer. However, different DDI versions in new cooked ROMs rained on our parade."

There you have it!
[Touch Cruise ROM Development] NikMel:
Here it come http://rapidshare.com/files/147005835/RUU_Signed_R1.rar

Included ddi.dll and disptools.dll from kaiser WWE 3.28

All other files from the latest cab file of htcclass...
[Touch Cruise ROM Development] bally3:
Nice one NikMel, thanks!

Downloading now but I'm off to bed soon so I'll post my findings tomorrow :)

UPDATE: I now have all apps, lights, lighting, fractal, text, mesh working all except the d3D cube ..working on that too.. and the scrolling of course!
[Touch Cruise ROM Development] NikMel:
I don't think its the driver causing that scrolling.

try tools from here http://xdaforums.com/showpost.php?p=1733012&postcount=274 this tools are working really good

The opengl tool runs on more then 15 fps
[Touch Cruise ROM Development] Nils8:
Sorry if I disturb your conversation or anything. Just had a thought about the scrolling which may be totally unrelated but anyway:

Could be caused by wrong number of vertical lines being drawn to screenbuffer and thus the screenbuffer becomes offset a bit which each drawn fps.

Wrong horizontal refresh rate

That's totally guessed but that are things that have caused scrolling for me on some occasions on the pc. Keep up your great treasure hunt!
[Touch Cruise ROM Development] bally3:
No need to be sorry my friend! :)

Anyone offering what could be a vital piece of information is most welcome here. We ourselves have had as much luck with trial and error with some successes.

I'll take a look into the registry, but it would help also if you know a little about these things if you an take a look into the registry yourself. Use PHM Registry - its freeware and does the job more than adequately.

Who knows? when tired eyes get accustomed to looking at the same thing they often miss the darn right obvious - often a fresh pair of eyes does wonders! ;)
[Touch Cruise ROM Development] bally3:
Morning everyone!

I'm going to try and fix the scrolling today mainly as I think we've cracked the acceleration issue. I've even managed to wrap the hardware hook onto a software rendering hook and it looks like its doing what its supposed to but hard to tell with all the scrolling!

I ask everyone whose installed these fixes to do the same as now i think this appears to be our biggest stumbling block - and I dont think it should be.

Chefs, UDK, swtos, and all the others - we could really use your help at this juncture - I think i may even have a 2D fix!

Everyone else, if you know these people, please spred the word - I dont know any of the chefs and I dont want to beg for help on each thread either.
[Touch Cruise ROM Development] bally3:
This thread has been at the top of the Polaris forum for two weeks at least - with over 19,000 views and 445 postings - I'm a bit suprised and slightly disappointed at the lack of support from more experienced members - either they think this is a complete waste of time and effort as its been done in the Kaiser forums, or that 3D acceleration is not as important, as has been mentioned by a number of users on here, as 2D acceleration - - I'd be suprised if the latter was true as what made me start this thread was down to the excitement around the 3D acceleration issue and udk's R0 rom which was rumoured to fix this.

Oh well.. whatever it is, hope someone decides to help - it would be nice to take this to the next level just as NikMel did when he cooked in the kaiser ddl last week.
[Touch Cruise ROM Development] kulhous:
I think that I'm not only one "silent watcher" who visits this thread many times a day and I fully support your efforts and look forward to any succes that all off you will surely soon achieve. I think there are tens users like me, and hundreds of users who would celebrate such improvement as functioning 3d or 2d drivers.

I am personally looking forward to DirectDraw with HW acceleration at most, because of fluent video playback and acceleration of some 3d games.

Thank you;)!
[Touch Cruise ROM Development] namaste74:
Second that. Been following the thread since you started, wish I could help but this is beyond me.
[Touch Cruise ROM Development] radem205:
I agree with Kulhous! Your guys are doing a very good job!

I view this topic 100 times per day to stay informed about your project.

Unfortunately, I have no experience in developing some drivers. I hope there is someone else who want to help you.

Keep up the good work!
[Touch Cruise ROM Development] bally3:
Thanks guys, at this point even doing some googling about scrolling and screen refresh/update would help.

I'm going to speak to NikMel about making a out of the box production version later today with the fixes we have found. At least that will allow users to flash the rom and take a look at it themselves.

But even installing the registry editor from the link above and going through the registry for screen, refresh,framebuffer, type of keywords and posting them here would be useful - after all, thats how we all started - tinkering!
[Touch Cruise ROM Development] NeoS:
Morning Guys.

I've been thinking. This scrolling thing:

It has to be a frame issue. The Kaiser worked out of the box with the drivers. With a little customisation, so did out Polaris. But, our screen is TOTALLY different from the Kaiser.

There's our problem. Now, we need a way to fix it. We need specs from Kaiser screens and specs from Polaris and look for significant differences in refreshrate, or whatever.
[Touch Cruise ROM Development] NatronCH:
may be this is a related problem:

http://www.youtube.com/watch?v=QJaGaTy-Pmw

it shows android on polaris with some sort of scrolling problem.

if i remember right, the video driver was the same that worked on the kaiser.

they where able to resolve it, but don't ask me how.

may be a glance in the htc-android source might help.
[Touch Cruise ROM Development] NeoS:
Yep, that's the problem alright. This is the only problem we face. I've pm'ed some of the people who worked on the kaiserdrivers, maybe they have a clue towards a non-scrolling display.

by the way, screen specs on Kaiser:

Screen size: 2.8 in (71 mm)

Screen resolution: 240×320 pixels at 143 ppi, 4:3 aspect ratio

Screen colors: 65,536 (16-bit)
[Touch Cruise ROM Development] NeoS:
Bally3, could you upload your ddi files? I think i might have found something.
[Touch Cruise ROM Development] CyberCSK:
Here is the post of the diff of android driver for polaris from kaiser.

But I don't get a clue on it how to apply this kind of solution to windows mobile instead of hexedit/deasm the driver. Does anyone know a person who is capable to do this?
[Touch Cruise ROM Development] NeoS:
Looks like a pixel alignment problem.

Let's try this. If anyone reading this thread has a Kaiser, i'd like to know the values of the following registry keys:

HKLM\drivers\active\display\gpe\logicalpixelsx=96

HKLM\drivers\active\display\gpe\logicalpixelsy=96
[Touch Cruise ROM Development] bally3:
Will do as soon as I've finished tweaking NikMels latest rom.. performance is looking much more impressive..but I've got a few differences still between udk's R0 and NikMels to iron out.

Will post once I've done what I need to do... currently looking at the ddraw file in a hex editor.. anyone know a better way?
[Touch Cruise ROM Development] radem205:
You have to set the values at 192 (see http://www.mobilitysite.com/boards/...ing-vga-related.html?highlight=logicalpixelsx)
[Touch Cruise ROM Development] NeoS:
lol. doing the same for ddi.dll.

I'm comparing ddi.dll (3.13) to ddi.dll (3.28).
[Touch Cruise ROM Development] NeoS:
Great find! I'm going to try that right away!