yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] NikMel:
I gues there are some GL function call's made by lights.
[Touch Cruise ROM Development] bally3:
But what we are seeing there with triangles.exe is hardware rendering - correct?
[Touch Cruise ROM Development] NikMel:
Yes this is hardware rendering
[Touch Cruise ROM Development] bally3:
I can confirm, DoomGLES works pretty fast using this dll
[Touch Cruise ROM Development] rogro82:
bally3 can you try this one out? I created a small program so you can switch between the localhook values....

Lemme know if it works or you need some more values ;)
[Touch Cruise ROM Development] bally3:
So we are one step closer - and actually we are now seeing with the Kaiser cab, the omnio driver and the LibGLES you just brought in, that all these things are possible on the Polaris.

I do feel we are making progress NikMel.. what do you think? btw, this libgles_cms file.. where did it come from? the file size is significantly bigger - nearly double to the one in the kaiser cab.
[Touch Cruise ROM Development] bally3:
Thanks I'll give it a go :)
[Touch Cruise ROM Development] rogro82:
Remember that most of the time you have your registry editor open you will need to select the key to see the actual value because the editor isnt updating when keys are changed... ;)

Im using PHM and im seeing that behaviour.
[Touch Cruise ROM Development] bally3:
Thats excellent work rogro82! that will speed up testing times by quite a bit.

Thanks for the help guys, really feels like we're getting to grips with this issue. :)
[Touch Cruise ROM Development] rogro82:
Glad to help... We all have the same goal and thats whats xda is for isnt it :)
[Touch Cruise ROM Development] rhov23:
Hey man! I'm still alive. I just don't have a clue where to start. :eek:
[Touch Cruise ROM Development] iRiKi:
Here you have m8, hope it helps :)
[Touch Cruise ROM Development] fullagon:
Hi Guys

Please dont think this is another will this accelerate my sat nav software question, But i was looking through the files of navigon navigator 7 and i came across a file called libgles_cm_noe.dll now i know these programs aren't usually 3d so to speak but the libgles dll got me wondering didn't some of you guys get cod2 and quake working hardware accelerated by playing with the libgles. I don't know what the noe part means but I just have to ask would there be something in that to maybe make it work hardware accelerated. I mean having some 3d games work is cool but wouldn't it be the ultimate "coolness" to post a utube video of navigon flying along hardware accelerated (thanks to your hard work) to replace the videos of 4 year old devices whipping the polaris's but at redrawing the map? Sorry for my rant but im just curios.
[Touch Cruise ROM Development] NeoS:
I'd say try it out. There's alot of things you could do to test, for example: rename the .dll to just libgles_cm.dll or compare them with a hex editor, etc.
[Touch Cruise ROM Development] fullagon:
Thanks for the reply neos2007, I am not a developer or programmer but I do have the patience to just fiddle around with these things. If I stummble across anything I will let you guys know.
[Touch Cruise ROM Development] fullagon:
Hi guys was looking into the files i mentioned (post #1584) libgles_cm_noe.dll and libEGL.dll found in navigon 7 folder and these files seem to belong to a program called hybrid rasteroid 3.1 which from what i understand is a software implementation of opengl you can even find articles linking that program to qualcom brew. So to me at least there seems to on the surface be some glimmer of hope still that navigon could actually run with hardware acceleration somehow. Would any of the knowledgeable people here just take a quick look at this just to satisfy my curiosity?
[Touch Cruise ROM Development] chavonbravo:
I read a report of someone trying out 3d drivers on and tf3d qvga on lg incite, and it didn't have power down issues. Might be worth looking into, possibly.
[Touch Cruise ROM Development] JASTECH:
What about using the Omnia 3D driver? Would this be easier to work with? I know that Samsung is dropping Qualcom chips in the near future as they have been working on their own chip. Well I can wipe the dust off my Hex Editor and see if I get a head ache.

Thanks, JASTECH ô¿ô
[Touch Cruise ROM Development] chavonbravo:
Well, the lg incite has msm 7201 like diamond/raphael, not 7200 like kaiser/polaris. This is definitely an issue then with some difference in the 7200 and 7201 processor.
[Touch Cruise ROM Development] NeoS:
http://xdaforums.com/showpost.php?p=3226003&postcount=1627

Maybe some new material to test? ;) Latest Diamond ddi.dll.

Edit: Anyone want to help out setting up a wiki page for driver development? Contact me.

Edit2: Bally, I shamelessly copied the disclaimer from this thread over to the Blackstone dev thread. Hope you don't mind.
[Touch Cruise ROM Development] bally3:
For all the help you gave this thread Neo, I sure would find it hard to to muster up any indignation lol (thats for telling me to keep the language simple remember you rotter! ;) hehe!)
[Touch Cruise ROM Development] imfloflo:
Inreseting thing: when i install the M2D iolite test version on my udk R4 with M2D installed, after installing the M2D , footprint and audio package my camera becomes very fast and no freeze anymore.

Don't know where it comes from but maybe there is something interestant in there.

To test: have udK R4 install

download the M2D version 22

install first M2D cab, then footprint, then audio cab don't forget to reboot when it's needed that's all.

link here http://xdaforums.com/showthread.php?t=398173
[Touch Cruise ROM Development] Quilapvd:
Can you include the needed cabs at your post, else the community users need to search all over it (like me ;)) to find it.

Sound's interresting.

Edit:

Damn, the camera is indeed very fast! Nice found imflo.
[Touch Cruise ROM Development] NeoS:
Ghehehe. Yeah well, you mustn't try to deliberately increase difficulty in your already lingual complicated forum posts. ;)

Btw, Android's coming along nicely on Polaris. Good work.
[Touch Cruise ROM Development] bally3:
Did you get anywhere with the m2d camera trick imfloflo?

Would be interesting to try it with other roms if its working.
[Touch Cruise ROM Development] imfloflo:
I reinstall the package but unable to success to have this performance gain again.

Don't know what i had down but the camera was to speed :s
[Touch Cruise ROM Development] Kiiv:
I've tried with ROM WM6.1 Manilla 2D (Core 21109) by TranMinhMan but I've seen no difference...

But I don't know if I've installed things correctly. After downloading the file "IOLITE M2D.zip", I've installed the cab in this order :

TEST IOLITE M2D TAKE 3.cab

TEST IOLITE FOOTPRINTS.cab

TEST IOLITE AUDIO MANAGER.cab

TEST IOLITE ALBUM.cab

TEST IOLITE Streaming Media.cab

TEST IOLITE YOUTUBE.cab

Have you do something else?
[Touch Cruise ROM Development] Quilapvd:
I've installed the cabs on the M-Anime rom,

And I got also some perfomance at the camera.

The quality of the pictures is worser than normaly, but video's are smooth filming etc.

Kind weird.
[Touch Cruise ROM Development] imfloflo:
It works only one time don't know what i have done and unable to success again :s

i only installed :

TEST IOLITE M2D TAKE 3.cab

TEST IOLITE FOOTPRINTS.cab

TEST IOLITE AUDIO MANAGER.cab

but camera was smooth

maybe something in the M2D or footprint cab i though
[Touch Cruise ROM Development] pcarvalho:
hummm...did this happen imediatly after install or did you reboot 1st?
[Touch Cruise ROM Development] imfloflo:
I reboot jsut when the installation ask me.

Just desactivate M2D, install first cab,then reboot, then install footprints, I seem to remember.

Very disappointed to not success again. :s but i see i'm not the only one to have this so maybe we can find something.

I can't hardreset so often cause it's my every day phone.
[Touch Cruise ROM Development] Quilapvd:
The difference what I dide, is that I didn't reboot when it was asked. I installed directly the 2 other cabs and then rebooted.

Maybe is that the difference.
[Touch Cruise ROM Development] pcarvalho:
seems to me that something wasn't properly loaded or something like that and so it made the camera "become" smoother...what was the camera version...before install and after?
[Touch Cruise ROM Development] norazmi_0673:
i've been reading your post since 3 days ago (page by page). VERY interesting stuff, can't wait for the final release. Viewed test TF3D on polaris(youtube)...wow! Any working TF3D (test drive) on Polaris so far??
[Touch Cruise ROM Development] Alex-V:
What`s with tf3d...????

What`s whith it....?

I pursue tf3d qvga polaris long time since ..., however, why thus nothing at all more does itself ...?? I find tf2d is complete, however, tf3d .... driver ...? further development to known problem black screen issue .?? Excuse ...., however, it simply interests me...

Sorry for the english i`m from german and the english is from Abacho.de

whith kind regards...:)
[Touch Cruise ROM Development] Alex-V:
English training....??!!

Where I can find good in English training....??!!

Whith kind regards form germany...:)
[Touch Cruise ROM Development] bbezja1:
isn't this normal with other phones? you can make photos with 2 or 3 (or so) mpix quality but when you switch to camera it drops to 360x128 (or so)? not just phones, even cameras do that just not such a big difference
[Touch Cruise ROM Development] bally3:
New version of Panels SDK available with open GL ES support

LIONS AND TIGERS AND SONY XPERIA PANELS WITH OPENGL ES SUPPORT ON MY POLARIS? (OH MY!)

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

Now this is something I want to see running with the drivers! :)

The SDK can be downloaded here:

http://developer.sonyericsson.com/getDocument.do?docId=100379

And just when you were thinking the 3D drivers were going their grave... ;)
[Touch Cruise ROM Development] imfloflo:
Good news to hear :)
[Touch Cruise ROM Development] SuperJMN:
What does this mean? :O Are we going to get the so called 3D acceleration properly? And what about 2D?
[Touch Cruise ROM Development] bally3:
It means that if a decent dev decides to put some effort into bringing the panels to the Polaris device, in theory we should finally see the benefits of the 3D drivers.

The 2D driver project is dead - unless someones working on it in the background silently, but I very much doubt it. The only thing that could revive it now it seems is if a device using similar chipset to the Polaris is released (again unlikely) that has a 2D driver we can adapt for our device.The probabability that someone would be willing or have the expertise) to create a 2D driver from scratch is unlikely given that as with the Android project, the only dev doing any significant amount of developing outside of cooking new roms at the moment seems to be Rogro82. This has become painfully obvious this last week since Rogro has been tied up with work with the lack of support on that project.

One can only assume that the other devs left the Polaris scene and onto newer devices.

To be honest, we're looking at an end-of-shelf-life device at the moment with some of the newer devices already in their maturity. Unless the attraction of a decent device, now available at a sub £200 price tag that does pretty much everything these newer devices do can attract potential developers to purchase these devices, I would not bank on large projects like the 2D driver to be a realistic expectation.

We can of course go the route of the kaiser and just send a willing developer a device or pay them toward the purchase of one in return for developement work but this can only be realised by users donating. As class-action.org proved with the 3D driver, pledging means little if its not backed up by hard cash.

In the meantime I'm eternally optimistic that someone will get the panels working - if only to finally get some use out of and showcase the 3D drivers, which have recently started to feel like wasted effort since TF3D hasnt materialised.
[Touch Cruise ROM Development] Lord Meshadieme:
I have just two things to ask, First Can someone upload the tools you guyz use to test opengl and D3D because i can only find one for opengl around the internet. Second questions does this provide an advantage over the drivers provided in HTC's WM6.1 Update?

I love the effort you guyz put in here, its amazing how good the freelance development continues around here. I honestly would love to get into it myself but im very tied up with other projects, it'd be interesting to code for a new platform for a change.

Keep up the great work guyz!
[Touch Cruise ROM Development] bally3:
Sorry for the late reply my friend, busy with the Android project so didnt see the post.

Its a bit late for me to check the names but the 3d driver comes with some d3d and opengl samples to test with and we used GLBenchmark CM version. As far as the differences are concerned - I'd say yes the 3d driver is much faster but needs tweaking to get it working with games etc (see previous posts - sorry - again quite late 12.20am here in uk).
[Touch Cruise ROM Development] Lord Meshadieme:
Hmm i can't seem to close the apps once it starts, sp do i have to installa task manager to do it or is there something to configure. I was planning on doing some benchmarking before and after the driver and tweaks (so ill have to rip the apps to a seperate cab), how will i get the frame rate to show would also be helpful.

Thanks in advance, ill post up the cab and benchmark once im done maybe we can start a benchmark collection here.
[Touch Cruise ROM Development] NeoS:
Anyone interested in testing some new files / ideas?

Firstly, when we started this project, we only had the Diamond as a reference. Now, we have ALOT more devices to steal files from :P.

I've been thinking: what if some newer device has some better files, anyone interested in ressurrecting this project?
[Touch Cruise ROM Development] imfloflo:
Good to see people come back here.

Are the new files and new devices more responsive ?
[Touch Cruise ROM Development] NeoS:
I'm not sure. But that isn't the issue. The issue is one last fix AFAIK, the sleep-bug. Once that's fixed, you guys can start using manila3D. :)
[Touch Cruise ROM Development] w04g005:
Let me be a part of it!! Ok i'm no programmer but I'm a great tester :-)

If only the stupid standby bug could be solved!! There are so much ports even for TF3D from Diamond 2 (look into kaiser/software forum). But noone can use it!!

greetings
[Touch Cruise ROM Development] bally3:
For the time being I'm going to have to bow out of it as I really want to see the Android project through before I commit to anything else.

I love seeing the dedication in these forums but I have to reiterate what I've said before:

WE NEED MORE DEVS.

The work required to finish this project can be developer led only, and even that at dll level programming which very few users have on the Polaris thread and even less so now that we've lost almost all our developers to newer devices.

We have the Will but lack the Skill.

Lord Meshadieme seems to be more than capable and I'm sure there are others especially in the other forums who may want to join forces and thats the only way I can see any progression, but you'll have to get some dedicated developers to commit some time and as Neos mentioned above - thats not so easy to do.

When the Android project is completed, I hope to return these projects. In the mean time I wish you the best of luck - its a hard task to do, but not impossible if the right devs come on board. ;)

Edit: W004, please edit and delete the un-necessary profanity. This is a family-friendly forum used by many young users and I wish to keep it that way - thank you.
[Touch Cruise ROM Development] NeoS:
Thanks for your info on your current occupation Bally. Good to still see you lurking around here. ;)

I'd like to call out to the users interested to gather a few files from me, from different devices.

Let me list what i'm looking for:

- Libgles_cm.dll from either MSM7200 or MSM7201A devices. MSM7225 devices don't seem to have the file, therefore I don't think they have a 3D chip built in...

- I think we have most chance with devices NOT built by HTC. We know HTC/Qualcomm cheated us out of the files, so hopefully some other OEM is willing to pay for the files.

- Last but not least, we need someone to set up a small database of some sort. We need to make a list of all libgles_cm.dll files and what's in them, together with a device's name, date, and version. Is there someone willing to do that in a way so everyone can contribute?

I'll post this in the Blackstone forum as well, since most MSM based devices benefit from a better driver. ;)

Good luck and good hunting guys.
[Touch Cruise ROM Development] w04g005:
What do we have to get these files? Do we have to search in dumped roms?

greetings
[Touch Cruise ROM Development] NeoS:
Yes. They If you look here: http://wiki.xda-developers.com/index.php?pagename=Developing a graphics driver for Windows Mobile You can see a list of files needed for the graphics driver to work.

Most files are already in our posession, but the libgles_cm.dll is the one that holds the most secrets.
[Touch Cruise ROM Development] w04g005:
Ok i found the libgles from xperia
[Touch Cruise ROM Development] NeoS:
So far, I have libgles_cm.dll from: Blackstone, Xperia, Rhodium, LG Incite.

To name a few, I need: Kaiser, Polaris, Diamond, Raphael.
[Touch Cruise ROM Development] w04g005:
For diamond there is a version uploaded here:

http://rapidshare.com/files/116479458/ATI_Beta2.rar
[Touch Cruise ROM Development] Lord Meshadieme:
Hate to go out of topic but its seems my previous post was misunderstood, id like some help with the tools for OGL and D3D, i can't seem to close them once started. I'd also like to know how i can enable viewing the frame rate or recording it with these tools.

Thanks in advance.
[Touch Cruise ROM Development] P3PeCZ:
Hi

please WORKS 3D DRIVERS FOR POLARIS IN ORIGINAL HTC ROM WITH WM6.1???

newest htc rom is:

HTC Touch Cruise_RUU_Polaris_HTC_WWE_3.13.405.0_radio_sign_25.85.30.07_1.59.42.15_Ship
[Touch Cruise ROM Development] mutant92:
Hallo,

I've flashed official HTC WM6.1 ROM and installes TF3D with all important Addons. I'm afraid, I've the problem that my display doesn't go into standby mode. When I push the power button only the backlight turns off. When I repush the Power-Button, the display goes off, on, off and on. Then my Polaris reboot! Is there any fix for this avaible?

When yes, could I have it, please ?
[Touch Cruise ROM Development] belabartok:
When you listen music with the app pocketplayer even having the 3d drivers installed, you can put polaris to standby and still listen music.Maybe there`s something that can help with the development there
[Touch Cruise ROM Development] bally3:
Please read the thread before posting, this has been covered countless times and no there is not a fix for the power issue at this tiime.
[Touch Cruise ROM Development] P3PeCZ:
Works 3D Drivers in oficial htc rom(wm6.1) ???

AND PLEASE thet are 3d drivers is better for Polaris? this 3ddrivers htc-ca OR 3ddrivers Omnia??
[Touch Cruise ROM Development] bbezja1:
directX 10.1 ftw
[Touch Cruise ROM Development] webbdn:
Hi NeoS2007.

This is the libgles_cm.dll from Toshiba G810 ROM.

Hope this helps.
[Touch Cruise ROM Development] hUmpL:
HTC-CA-Polaris-Drivers

Installed HTC-CA-Polaris-Drivers and when I rebooted the phone it just stops at "Smart Mobility". Nothing happends. Might have missed something in the installation but I guess thats too late now. My question is, what can I do now?

** Edit** Found a solution
[Touch Cruise ROM Development] bally3:
I'm not over excited about the 6.5 roms as yet - still very buggy and the 3D driver wont work, Android boots fail, no Opera etc..

So I decided to go back to my trusty Maxniper Omnio rom which I managed a 371fps with the 3D driver before and Android boots 100% of the time for me, but I didnt want all the bloat of the rom - mainly as I'm ow in love with the PointUI home2 interface.

At the customisation part of the first boot I reset to stop it loading and found I had nearly 50Mb of ram to play with without most of the Omnia widgets configured. It seems pretty fast so I loaded the 3D driver and WHAM! I had a super-fast rom which when I tested gave me an impressive score 364fps on GLBenchmarks. Moreover I still had 49Mb of ram when PointUI was loaded and that sucker rocks on this rom.

I even managed to get Xtraxt - a game from the Sony Experia to run on it (640x480 so unplayable but it still booted!). Quake, Doom ran fast, videos were smoother (dont hold me to that though) and overall performance was to my liking,. I've asked Maxniper if he would be kind enough to release a bare-ass naked rom with probably Office on it (I need it to read my default.txt file for Android and its a sucker to cab install correctly). I hope he comes back to me so I can release that and my set up details for people to try.
[Touch Cruise ROM Development] bally3:
Now whilst being smug and happy about my triumph, I backed up my install and then loaded TF3D to see whether it would be any different (for a laugh of course! :rolleyes:). - Again TF3D was so much faster than I remembered it to be, and this time I was sure of it, just from seeing the speed of the tab animations.

I think TF3D could be veery usable if the power issue could be resolved. Notice I say resolved and not fixed as I'm pretty sure thats not going to happen anytime soon!

So heres my suggestions for an alternative way round the problem:

1. The screen freezes when the device tries to sleep, it seems that TF3D is waking up the device incorrectly - but if you unload or toggle off TF3D, its fine. So why dont we just write a script to unload TF3D when it tries to sleep and reload when you hit the power button?

OR

2. Write a script to make TF3D unload if the device has been inactive for a while - maybe tie it with a screensaver to run after unloading TF3D? again it would have reload TF3D when the screen saver stops when the device is activated. This way the system would only sleep in screen saver mode and not when TF3D was running.

Dont know how you would go about it (MortScript?) but it would be good to see if this could be workable alongside the Omnia rom - especially if MaxNiper will make the naked rom for us to add it to.
[Touch Cruise ROM Development] NeoS:
Doesn't such a mortscript already exsist? I know in the early TF3D tests there was one.

On a sidenote: the issue CAN be fixed, but it needs to adressed in a new wrapper for perhaps libgles_cm.dll. I'm not sure though, maybe the real devs can point that out.

This sreen-off issue is only consistent on the MSM7200 chipset. So the fix would only apply to the Kaiser, Polaris and probably Nike.

By the way: the OpenVG driver is said to enable hardware 2D acceleration in the Xperia and Diamond. Look it up in dev&hacking to try it out.
[Touch Cruise ROM Development] w04g005:
There exists a script and even an exe (i think by worstenbrood) which deactivates TF3D when you want to send your device to sleep but this isn't a real solution. Who wants to wait a half minute or even longer till the device (TF3D) can be used.

Tried the OpenVG driver. without any noticeable change!

greetings and thanks
[Touch Cruise ROM Development] chavonbravo:
Has anyone tried the libgles_cm files from topaz/rhodium? They have the msm7200a chipset, instead of msm7201a like diam/raph. Haven't tried tf3d for a while, but maybe it'd work?
[Touch Cruise ROM Development] NeoS:
Libgles_cm.dll for all these devices are the same. I did a comparison for HD/cruise/raph/rhodium/topaz/Xperia/etc.

The problem is: the file needs MORE calls, but they can't be added just by adding them in with a texteditor. That's why there needs to be a wrapper.

I hope I explained it right. ;)
[Touch Cruise ROM Development] kyryl:
I have the same problem. Tell me your solution pls.