yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] whitealien:
I took some time and studied Kaiser and Polaris service manuals (see files attached). If you look closer then differences are obvious. I did not find any part (searching by part number) what can be inter-exchangeable between both devices. For example both video cameras are the same, but part numbers are different, means we cant put video camera from Kaiser into Polaris, even so they are the same. I guess mainly differences are in connectors due different mother boards.

Back to track. The biggest visual difference ofc is main board, what is totally different from Polaris. You can see well that both devices use Qualcomm MS7200 and few more chips that are identical, but not all. Polaris board is a lot smaller what can prove that it have less or different chips from Kaiser. Are you sure Polaris have graphics chip on it?

Resuming what I said. We have two devices with the same chipset, but build differently. Thats why maybe Kaiser ROM out of box wont work on Polaris.

P.S. Here are manuals. Maybe someone can dig out something useful from those.

HTC Kaiser Service Manual

HTC Polaris Service Manual

Cheers, Whitealien
[Touch Cruise ROM Development] bally3:
Thanks for this Whitealien, some more bedtme reading then!

Graphics wise.. I think we can safely say its there! :D

will have to look more closely at the tech specs and see what we can find.. in the mean time I'm back to seeing what I can do to fix the scrolling.. I still think thats the one thing that will give us our answers, it may be that the ddi's just arent going to do the job in which case we look for more compatible ones.
[Touch Cruise ROM Development] imfloflo:
Wooooa Chainfire message in person , good to see you in this topic :)

how can we found this address on our device to help ?
[Touch Cruise ROM Development] radem205:
@Chainfire: Thank you for your explaining message! I think bally3 can give you a list of all the info that he has, because he is working on it from the beginning.
[Touch Cruise ROM Development] whitealien:
I found an answer to my own stupidity:

lol :p

P.S. Chainfire thx for coming here.
[Touch Cruise ROM Development] bally3:
Chainfire, thank you very much for coming back so soon to us and clearing up a lot of confusion.

As it stands, we've had luck with ver 3.28 ddi from kaiser and the July 29 CA drivers (August 19 work also but give us white screen when after sleep mode).

Currently we have all the 3d apps working as you mentioned with the flickering and Pananza's Billboard hack allowing us to show 7,14 fps to the 7,25 fps on the omnio and the 0.6 with the software renderers like htc_d3dm.dll as found on udk's R0 release with Manila 2D.

Currently we are at that Juncture where we know hardware acceleration is initiated on the Polaris but the scrolling issue is our stumbling block.

If we can fix the flickering we believe this may yield better performance.

If you can supply us with the ddi version that worked out of the box for the kaiser or the ddi file from the 2D driver device you are working on please, we can give those a try.

The versions we HAVE tried are:

Ver 3.13 - new wm6.1 Polaris ddl - no HW

Ver 3.14 - kaiser ddl - works but unstable results (freeze etc).

Ver3.29 - worked with net compact 2.0 but not 3.5?

Ver 3.28 - works with 3.5 and 2.0 - most stable version so far.

Much appreciate your input :)
[Touch Cruise ROM Development] NikMel:
<<= The cab from htcclass website is not the reason of blank screen so we can scrap this one bally3 :)

<<== this one run's at avrg 2.1 fps on my latest rom with the files included from htcclass website

<<== 3.5 works too :)
[Touch Cruise ROM Development] bally3:
btw, Chainfire, if this guy can tell us where about he's from maybe one of our many active or even the "silent" members might be able to loan him to work on! ;)
[Touch Cruise ROM Development] whitealien:
If you think that I'm spamming too much, you tell me, but I found this statement interesting. It explains at some point why HTC don't want to provide as with drivers.

P.S. Sony Xperia X1 will use Qualcomm 7200 chip clocked @528Mhz. Maybe Sony will have enough money to buy graphics drivers then we could extract from their ROM.

Imageon in Qualcomm 7200
[Touch Cruise ROM Development] NeoS:
Chainfire, thank you for showing interest in our thread and help clearing things up. I can see you know your stuff and i'm confident with your help we'll get there.

I'll lose the idea of using 2 versions of ddi.dll, as it doesn't seem to work. (the system uses either the old or the new version, not both.)

Now, here's something interesting to think about:

How about the msm_clk.dll and other clock settings for the display? It tells the display on which frequency it should show us graphics. It's like the difference between PAL and NTSC.
[Touch Cruise ROM Development] imfloflo:
IS there no any product on the market using this chipset, cause we can find driver on another device different from pda maybe ?
[Touch Cruise ROM Development] NeoS:
Oh and Bally3, would it be an idea to clean up this topic and, like Chainfire suggested, write a lineup of "working" stuff we did?

As far as I can see, we've got 2 basic approaches.

1. Nikmel's rom as a basis, with edited ddi.dll

2. udK's syrius R0, with edited ddi.dll

Both seem to work equally. The only difference is that Nikmel's ROM is cleaner and has (presumably) very few tweaks.

I'm not online very much as of tomorrow, since i'm at work. but i'll be checking this thread.
[Touch Cruise ROM Development] NeoS:
GLBenchmark

So. I decided to run a GLBenchmark. And it worked! 3D graphics! I'll post a small video soon.

The device doesn't seem to like lighting though... lol.

I'm in a VERY good mood right now.

Some results of the test:

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)
[Touch Cruise ROM Development] imfloflo:
@NeoS2007 what have you change and which dll and settings are you using to success this working
[Touch Cruise ROM Development] bally3:
Neos2007: Probably a good idea, though I think as far as threads go we have done quite well to keep it on topic and fruitful.

I'll clear down the first couple of threads but I want to keep the post info for historical purposes.

Interestingly when Chainfire mentioned he'd been on here a couple of weeks ago (I assume he meant the Polaris forum and not just this thread!) I went back to my first post to see when we started this. Amazingly enough my first post on here was only SEVEN days ago!

What a lot we've done in a week! I thought it had been earlier than that.. feels like a few weeks to me! :p
[Touch Cruise ROM Development] NeoS:
Ok, here it is:

http://www.youtube.com/watch?v=DGRZ5HwBbHI

Don't kill me about the quality... I still need to get a better camera.

Enjoy the video.
[Touch Cruise ROM Development] imfloflo:
good news yes a better camera for Neo +1 ;)
[Touch Cruise ROM Development] bally3:
niice... so what did you change?
[Touch Cruise ROM Development] NeoS:
Nothing. I read the HTC CA site again and read they were using GLbenchmark to tune their driver with. So i thought i'd give it a whirl. ;)

This can mean 2 things:

1. the 3D driver works, but misses some minor component. (see GLBenchmark and the Lights.exe Nikmel posted earlier. Both work.)

2. The 3D driver works, but the screen has a different timing than the Kaiser has, thus creating the scrolling effect.

Either way, the driver works. :D

Now we need to straighten out the bumps in the road and with help from Chainfire and other xda-devs, we'll get there.

Again, I really appreciate all the help and ideas we get in here. Keep it coming people.
[Touch Cruise ROM Development] manaaa:
hi,

congrats and respect for the work that has been done so far.

i wasnt following this thread from beginning, but if you could detail some informations i would like to post them as news in the polaris section, updating the driver fix progress thread.

rgds,

mana
[Touch Cruise ROM Development] bally3:
Damn! I thought you hit on something! :p

excepting Chainfires arrival, today has been very disappointing indeed.. nothing gained and lots of interruptions at home :o

Oh well.. tomorrow is a new day as they say...!

(My thanks to JesseW for the logo... it looks niiicee... "ROVERS TILL I DIE")
[Touch Cruise ROM Development] bally3:
Neos2007: are you using ver 3.29 or 3.28? ddi file? and which kaiser cab, new or old?

I think its 3.29 we SHOULD be using but or life of me I cant get it to work with the new kaiser cab.. therein lies a clue..
[Touch Cruise ROM Development] NeoS:
I think we should ask amod to edit the threadtitle. In my opinion "Polaris 3D driver project" should sound better and attract more developers.

Also, a small list of things we've accomplished so far in the first post should sum things up.

Again, great work people. I'll see you again in the morning. (i have a girlfriend who needs my attention now ;))

edit: @Bally3: I'm using the 3.28 ddi.dll with the latest HTC-CA cab (19-08-08)
[Touch Cruise ROM Development] SomethingWicked:
I've been mostly quiet, just watching... but I stumbled across something interesting, probably not relevant to this thread, but just in case:

When I'm in camera mode, if I'm looking at something dark, the frame rates are insufferably low and basically renders the dang thing useless. But... if I'm looking at something bright, especially a light source like a TV or laptop screen, the display is as fluid as a movie when moving the camera.

I hope this observation helps in some way... :rolleyes:
[Touch Cruise ROM Development] ianl8888:
Off 3D topic, but I believe that the Polaris has a heat problem.

Why ?

Recently, I had occasion to run a GPS trace of two long vehicle trips (both >4 hours). The program I was using to record these traces is a fairly simple one (not TomTom etc) that recorded x,y,z points each 100m and continually "joined the dots" to form a continous trace. I needed these traces as records for a professional report.

The Polaris was plugged in to the relevant vehicle power socket with a car adaptor to ensure the battery didn't clag in these separate long trips. Power charge LED turned green after about the first 20 minutes (quite normal)

On each occasion, the top edge section of the Polaris (power button edge) became very obviously hot after about 3 hours and the charger LED started flashing amber, indicating that the Polaris had stopped re-charging. I had to remove the charger and suspend the trace for about 20 minutes to recover.

Perhaps it was the charge adaptor (since this happened in two separate vehicles) but it is the same adaptor that works without problem when there is no GPS trace for similar periods.
[Touch Cruise ROM Development] SomethingWicked:
As a truck driver, I use gps with google maps every day, leaving the phone plugged into the car charger for hours at a time, and mine has never gotten hot. :confused: But I do keep mine completely out of direct sunlight...
[Touch Cruise ROM Development] bally3:
This is where we need the developer(s) to come in.. lets hope chainfire will be able to help.

heres a list of files that we need to check:

21/05/2008 10:07 12,800 adsprtossvccore.dll

20/05/2008 18:31 89.088 ahi2dati.dll​

20/05/2008 18:31 89,088 ahi2dati.dll

23/11/2005 11:11 53.248 cereg400.dll​

23/11/2005 11:11 53,248 cereg400.dll

20/05/2008 18:31 31.232 clkregim.dll​

20/05/2008 18:31 31,232 clkregim.dll

20/05/2008 18:31 71.168 d3dm_ati.dll​

20/05/2008 18:31 71,168 d3dm_ati.dll

20/05/2008 22:03 230.912 ddi.dll​

20/05/2008 22:03 230,912 ddi.dll

20/05/2008 18:31 414.208 disptools.dll​

20/05/2008 18:31 414,208 disptools.dll

15/04/2008 10:58 18.680 dsm.dll​

15/04/2008 10:58 18,680 dsm.dll

21/05/2008 03:24 4.608 gxdma.dll​

21/05/2008 03:24 4608 gxdma.dll

20/05/2008 18:31 323.072 libgles_cm.dll​

20/05/2008 18:31 323,072 libgles_cm.dll

21/05/2008 03:17 5.632 mmmap.dll​

21/05/2008 03:17 5632 mmmap.dll

20/05/2008 18:30 7.168 mmtimer.dll​

20/05/2008 18:30 7,168 mmtimer.dll

20/05/2008 18:31 5.120 msm_clk.dll​

20/05/2008 18:31 5,120 msm_clk.dll

21/05/2008 10:06 22.016 msm_time.dll​

21/05/2008 10:06 22,016 msm_time.dll

21/05/2008 10:04 52.736 oncrpc.dll​

21/05/2008 10:04 52,736 oncrpc.dll

21/05/2008 10:02 736.256 remote_apis_clnt.dll​

21/05/2008 10:02 736,256 remote_apis_clnt.dll

21/05/2008 10:02 18.432 remote_apis_svc.dll​

21/05/2008 10:02 18,432 remote_apis_svc.dll

21/05/2008 02:38 11.776 smem.dll​

21/05/2008 02:38 11,776 smem.dll

20/05/2008 18:31 15.360 TrsTai_extension.dll​

20/05/2008 18:31 15,360 TrsTai_extension.dll

20/05/2008 18:31 22.016 wce_pmem.dll​

20/05/2008 18:31 22,016 wce_pmem.dll

21/05/2008 02:36 17.920 wce_rex.dll​

21/05/2008 02:36 17,920 wce_rex.dll

20/05/2008 18:31 5.632 wce_tramp.dll​

20/05/2008 18:31 5,632 wce_tramp.dll

off to bed now... goodnight all :)
[Touch Cruise ROM Development] NeoS:
I don't know if we have all those .dll's... Are these ONLY for graphics?
[Touch Cruise ROM Development] NikMel:
He combined all dll's from kaiser and diamond that are graphics related:)
[Touch Cruise ROM Development] imfloflo:
For information if ti can help

personnaly on my polaris with the R0 rom i haven't this files :

20/05/2008 18:31 89.088 ahi2dati.dll

23/11/2005 11:11 53,248 cereg400.dll

20/05/2008 18:31 31,232 clkregim.dll

20/05/2008 18:31 71.168 d3dm_ati.dll ----------> only d3dmdll and default_d3dem.dll

15/04/2008 10:58 18.680 dsm.dll

21/05/2008 03:24 4.608 gxdma.dll ----------> only gx.dll don't know if it's the same things

20/05/2008 18:31 323.072 libgles_cm.dll

21/05/2008 03:17 5.632 mmmap.dll

20/05/2008 18:31 5.120 msm_clk.dll

21/05/2008 10:04 52.736 oncrpc.dll

21/05/2008 10:02 736.256 remote_apis_clnt.dll

21/05/2008 10:02 18.432 remote_apis_svc.dll

21/05/2008 02:36 17.920 wce_rex.dll
[Touch Cruise ROM Development] polum:
It´s really working?

Stupid post...

Sorry !!!!
[Touch Cruise ROM Development] radem205:
This video is made by NeoS2007, so everyone who follows this thread have seen this video already.
[Touch Cruise ROM Development] bally3:
Evening all :)

Looks like Chainfire's arrival put a stop to the mad frenzy!

Ok.. back to work.. so what do we know:

ROMS:

WM6.1 Roms - udk R0, swtos light ddi, stock rom - all these roms do exactly the same and show no difference less the use of (or not use of) software renderers. No tweaks have been made other than the standard ones to speed up the device (glyphcache etc). I.m not counting NikMels rom which has the kaiser and the correct ddl files to initiate hardware acceleration as this is at best a development rom at this stage and needs further testing and tweaking before release.
[Touch Cruise ROM Development] NeoS:
Welcome back Bally3.

i've started downing some roms from Kaiser and Diamond. I'll see if i can dump them and pull some of those missing .dll's out of there. (I know i can dump kaiser roms, but Diamond could be a problem)

Secondly, I won't be around much tonight (my GF is having her birthday, so i'll have alot of folks over) but i'll try to take a sneak-peak once in a while.

bally3, is that list you made the complete listed USED by the ddi.dll and all their dependancies?
[Touch Cruise ROM Development] NikMel:
You can dump diamond rom the same way as kaiser.

Works for both:)
[Touch Cruise ROM Development] bally3:
The list of ddi files I placed in the response to Chainfire show that we are missing a number of ddi versions - of most interest to me are the versions BEFORE 3.28 and after 3.14 - as they may show better compatibility.

For those of you technically limited but would like to help, why not find different rom version - stock rom preferred of the kaiser and list/link them here?

For those of you with a little experience in this area, I would ask to extract some of these and see if we can find ddi's that match the versions we need (even if they are newer we would still be interested in testing them).

I've had a few people apologising for not being able to contribute as its way over their heads. I say there is plenty to be done and every little helps even if all you are able to do is paste a link to something that might be of relevance that you come across from typing and searching through search engines.

For example, we need to find out what versions of these ddi.ddl files were released, what the latest version is, if anyone knows someone with a kaiser or any other device that uses the qualcomm msm 7200 chipset let us know. for a list of these devices can be found here:

http://www.pdadb.net/index.php?m=pdamaster&posted=1&cpu=a7200
[Touch Cruise ROM Development] bally3:
nope, as NikMel said its a list of ALL the graphic dependant files, we need to start looking at what each does to help us understand the issues we have.

I was thinking about starting a new thread just for dependencies and listing what each does as we research it and adding to it but I fear that it would just end up me and one or two of researching the lot - I'm time-limited to how much I can time I can spend on this after next week so I am now looking at what to prioritise.

Chainfire's suggestion about the ddi file matches my own thinking so any help there would be gratefully accepted, especially as I have little desire to learn about rom dumping/extracting at this stage due to my time limits.

I'm sure chainfire will come through for us with the clock issue and the Polaris specific support issue so the one we should concentrate on now is the ddi file search and listing dependencies and file versions of other devices running the same chipset.
[Touch Cruise ROM Development] NikMel:
I've just included the latest ddi.dll of kaiser in to my rom and there is still that scrolling thing

The version of dll is 3.57
[Touch Cruise ROM Development] bally3:
Try cooking this ddi into the older drivers... they had better compatibility with the newer ddi.dll and post the ddi file up here man, I wanna play too! ;)
[Touch Cruise ROM Development] namaste74:
wiki has a nice post on this:

http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
[Touch Cruise ROM Development] NikMel:
Me too I'm using the at&t 3.57 rom
[Touch Cruise ROM Development] rogro82:
Does anyone have an original libgles_cm.dll? Not the one that came with the HTC class action driver but one that was originally on the device...

Im currently useing some tools to disassemble some dlls to see / try to find out what has been changed.

For now i see a few functions in the libgles_cm.dll that I think are altered and could possibly be the reason why the scrolling happens.

One of the changed functions i found in the libgles_cm.dll is eglSwapBuffers()... the reason i think this one is altered is because there are about 9 functions that also reside in the dll having a _ prefix or are renamed like _wglSwapBuffers().

Also functions like

eglGetDisplay()

eglChoosePixelFormat()

eglCreateContext()

eglDeleteContext()

eglDescibePixelFormat()

eglGetPixelFormat()

eglGetProcAddress()

eglSetPixelFormat()

have duplicates in the dll and have a prefix and the for most the e(gl) is changed in w(gl)....

Hopefully my english isnt too bad and you guys understand what im sayin :D

Could also be that these functions are altered by HTC or someone else, but somehow i have a feeling that these were altered to make/get the hardware acceleration going....

Im also looking at all the other files to see if there are some noticable changes made.

Maybe someone from the original project can tell anything about it..

I hope i am not ruining / spoiling anyones work... else just let me know and i will edit this post, because i dont want to spoil anyones hard work...
[Touch Cruise ROM Development] NikMel:
First install that cab file then extract attached file to somwhere and run the exe file from the extracted map.

http://rapidshare.com/files/145828245/htcorg.rar
[Touch Cruise ROM Development] dwaradzyn:
OK, this time Lights.exe shows that there is hardware acceleration. There is no screen update until I force something to draw on the screen (ie start menu or volume change).
[Touch Cruise ROM Development] NikMel:
You need to wait for max. 1 min.
[Touch Cruise ROM Development] dwaradzyn:
I launched Lights.exe and waited for 9 minutes now. It produced 7 frames by itself. When I touch start menu it does show some new frames but still no fluent animation. I'm so close to see 3d working on Polaris, please give me another hint how to make it work.

Thanks in advance
[Touch Cruise ROM Development] bally3:
ok we have:

HARDWARE RASTERISATION: TRUE

HARDWARE T & L: TRUE

USING VIDEO MEMORY

but lights flashes constantly with very few frame movements. Further more, having examined the files in the .rar, they seem to be the same as the ones in the cab?

Can anyone confirm this? ... Running further tests.

Good work Nikmel does seem like you've made some progress!
[Touch Cruise ROM Development] bally3:
UPDATE: These files are older than the ones in the cab???
[Touch Cruise ROM Development] NikMel:
they are one version older yes!

Yes this files are coming from that cab file.

It seems to me that the lights file and other exe files too are not looking in to windows directory
[Touch Cruise ROM Development] bally3:
Ok copied all files into the Windows directory over-writing previous files, made note of older files.

Ran lights again.. this time no flashing.

Still no frames.

D3D demo runs same as before - no frames?

Looks like its reporting hardware acceleration but theres absolutely no evidence of it.

Trying a different approach.

NIKMEL: If your results are different to ours please report.
[Touch Cruise ROM Development] NikMel:
you need to just push the Start button let the start window to popup and close.
[Touch Cruise ROM Development] bally3:
Erm.. thats not hardware acceleration Nikmel.. it has always moved when buttons were pressed or screen clicked.

The cylinder should spin freely without any intervention.

The cab file with swtos driver did that at least, albeit only a few frames per second (fps).
[Touch Cruise ROM Development] NikMel:
there is no full hardware acceleration on our device this is the reason

I think swtos uses software acceleration from omnia
[Touch Cruise ROM Development] SuperJMN:
Oops, I spent all the day out and now that I'm home I find that there was a false alarm. I felt excited for some minutes, but it seems that we don't have the key for the moment :(

Sorry for not being able to help, guys. I don't have any ROM that could make things easier.
[Touch Cruise ROM Development] bally3:
I'm confused, it shows hardware acceleration but theres no hardware acceleration?? :confused:
[Touch Cruise ROM Development] bally3:
Its ok SuperJMN - ya didnt miss much, except a brief glimmer of hope!
[Touch Cruise ROM Development] bally3:
Well for once my sceptism was well founded!

Nikmel, you claim that you have these Benchmarks we have been unable to reproduce.

You show us images of the Video Memory initialising saying it works, and now say there is no hardware acceleration for the Polaris.

What is the meaning of this?
[Touch Cruise ROM Development] NikMel:
well!

install the spb Benchmark and you will see!
[Touch Cruise ROM Development] ridli:
with my cruise
[Touch Cruise ROM Development] NikMel:
whos rom you are using?
[Touch Cruise ROM Development] NikMel:
In the appis from htcclassaction.org use your volume up for 2-3 seconds then it will run for some seconds
[Touch Cruise ROM Development] bally3:
I'm currently doing some research on this. Will report my findings later.
[Touch Cruise ROM Development] NikMel:
Here you go

With the libgles_cm.dll file in dll.zip triangle.exe run smoothly but only triangle.exe runs
[Touch Cruise ROM Development] bally3:
nice find namaste74! .. thats what we want to see more of.

Does anyone know whether the version number corresponds with the ddi version number? just grasping at straws here I'm afraid..
[Touch Cruise ROM Development] NikMel:
Yes on you question.