yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] [kab]:
new released (right now only beta available) spb mobile shell 3.0 have feature to draw some things in OpenGL (they have option - activate 3D acceleration).

this option not available, when driver not installed.

but when you install it - you have crash of this program.

is there any way to fix that?

i can tell which functions working wrong...
[Touch Cruise ROM Development] NeoS:
The OpenVG driver's been updated and seems to improve somewhat. Try it out. :)
[Touch Cruise ROM Development] mutant92:
Are the driver for the power issue problem?

Were can I download them?
[Touch Cruise ROM Development] whitealien:
With what ROMs these drivers are working now?

I tried with new Win 6.5 and it gives me error when I try Lights.exe and others 3D testing progs are not working either. Its not working with c_shekars 6.1 ROM too as soon as there are some "new" default drivers from HTC.

I wanted to try TF3D as I saw that guys have found solution for power management. What ROM you can recommend me?

cheers, whitealien
[Touch Cruise ROM Development] bally3:
Where did you hear that the power management issue had been fixed?

btw, I recommend maxnipers omnio for trouble free driver use.. I've gone back to it myself. :)
[Touch Cruise ROM Development] whitealien:
By fixed I mean they found reliable solution. http://xdaforums.com/showthread.php?t=460621
[Touch Cruise ROM Development] bally3:
Very clear and concise test results Drakh.. nice :)

I very much agree with you on your findings, I myself have stuck with my good friend Maxnipers Omnia rom for this very reason, the 3d driver works well and although some users have claimed its a placebo effect, I have consistently found that the driver makes the os feel much smoother and less laggy - especially when multiple programs are opened simultaneously.

Nice heads up on the GFxboost though, that I didnt know I've installed it and will post my results after a few days of testing.

One more thing I have found which I hope someone can shed light on, after installing the 3d driver, spb mobile shell 3 which is what I am currently using, shows a 3d driver accelerator mode that can be invoked, but when you do this and soft reset the phone, the 3d carousel stops working :confused:

Would have loved to see some iprovement with this, although I do admiit its smooth enough as it is.
[Touch Cruise ROM Development] bally3:
Currently there is one rom, DeadlinkV1 from Rukako that has the new OEM and sys which gives the added memory and storage space and uses the 3.13 ddi that works with the 3d driver but because of the wce_pmem.dll file incompatibility that pcarvalho mentioned, it hasnt worked as yet (could just need some code changes, maybe we can get rogro82 back to take a look..?)

I'm currently thinking that the best of both worlds will be a 6.1 and 6.5 variant of roms that use the 3.13/3.19 ddi and the 3d driver cooked in if its at all possible so I may tale some time to look into this and see if we can get someone to make the needed changes for us.

In the meantime, if anyone's code savvy enough to tell us why it doesnt work, what calls are required/missing etc, maybe we can entice someone to help us out.
[Touch Cruise ROM Development] Drakh:
Bally3, well, I can say it's not a placebo effect when Gfxboost does run fine, as I told you I use Coreplayer in directdraw mode to test if Gfxboost is doing it's work (playing a sample video that has lots of movements), if not, video will be choppy as usual, if it does, will be the same as when you use Qtv mode, so the same in whatever other app that uses directdraw.

I guess the ones who state about the placebo effect don't have a functional environment for Gfxboost, as it just doesn't work there, you know, it's a bit tricky to get it work properly, but once done, it works without a glitch.

About Mobile Shell 3, I sometimes have the same problem when using carrousel with 3D accelerator mode where it show a black background, but there, I see no difference in performance with or without 3D accelerator mode so I disabled it in MS3 config (the latest MS3.x Betas hide 3D accelerator mode in our Polaris anyway).

You don't need to reset the device to apply changes to MS3, it applies changes on-the-fly, if not, just exit the program and start it again.
[Touch Cruise ROM Development] Drakh:
Indeed, tried DeadlinkV1(1.1) and it won't run HTC-CA 3D driver... I'm back to M-Anime 2.0.

It's been done (all patches, added memory, etc) with working 3D drivers in Kaisser forums, sad I'm not a cooker nor coder, yes, some talent is needed here.
[Touch Cruise ROM Development] bally3:
pcarvalho is our mainchef at the mo who could has offered to have a go if we can find out wha needs to be done when cooking a rom.

So the logical step forward would be to find one of those cooks who will kindly liaise with pcarvalho and hopefully help him fill in the missing blanks so that we can have a a decent memory/storage rom with 3d drivers.

Lets all have go then... cant be that hard.. most kaiser devs I've come across have been top notch dudes.. I'm sure if we ask nicely enough they will help us ;)
[Touch Cruise ROM Development] pcarvalho:
where can i see that? if there is a kaiser one with working 3d and 101MB then its possible 4 polaris 2 ;)

i need links please :)
[Touch Cruise ROM Development] Drakh:
gimme a sec...

[PDACorner] Ultimate-X.V6 -21048|D3D|M2D|P|L|N|Enhanced Version

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

(biggest thread by far, he also added Chainfire's Gfxboost to his ROM)

6.1 WWE ROM shifu V08 M2D|RAM 101|LZX|D3D|Full ~ Light ~ Naked| [21048]

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

(claims 3D tested and working)

TPCExtremeV6 Loaded[101 RAM][WM 6.1--21051][D3D][M2D]

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

(claims 3D tested and working)

TyTN II WWE D3D M2D Mobile Vista 4.00 SeaDragon 5.2.21109, by ansar.

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

(claims 3D tested and working, seems not enhanced memory)

All 6.1 ROMs, I haven't see that for 6.5 yet.

what I see they share in common is that they use CE210?? for 3D and 101Megs; Seadragon use a more recent ROM, have achieved to run 3D, but not enhanced memory (and I see no CE211?? can do both).

Through my walk in Kaisse forums is also important to notice they don't pursuit to have the latest CE in cooked ROMs, but to have the best performing one, so they are these days centered on CE210?? (and their releases).

Hope this helps.
[Touch Cruise ROM Development] pcarvalho:
ok, thanks...gonna crack those open and see whats in them...

will report as soon as i get a chance to test...

cheers
[Touch Cruise ROM Development] bally3:
Good to see some positive movements in this direction. :)

The 3D driver, though it needs improvement is capable of significant performance gains and with the effort that Chainfire and P3D made to bring it to our devices, it would be a shame if it wasnt utilised. Lets hope pcarvalho can work his magic and then share his knowledge with our other cooks so we can have 3d driver based roms with more storage and memory as this would be the closest to a perfect rom we can hope for at the moment.
[Touch Cruise ROM Development] bally3:
Ok, I've made a wierd discovery, hope some users will try this out and let me know if its any good.

I was after changing the paths in my registry so that the default paths for all programs that access any media (win mo player, coreplayer, pictures and videos, htc album etc) would go to my Storage Card\My Documents\My Pictures etc.. to keep everything nice and clean as I like it.

I looked for '\My Documents' in registry and changed all references to this to '\Storage Card\My Documents' then copied my entire My Documents to my storage card then rebooted my device.

Dont know why but my device now feels.. 'snappier' all of a sudden.

I havent had a chance to run any tests but I dont have anything to test 2D with anyway but it does seem that navigating my phone is a bit smoother than before. I tried accessing the Windows folder in file explorer which usually takes a few seconds and that also appeared to be faster.

I'll let others have a try and come forward with their opinions but it doesnt feel like placebo - especially since I wasnt looking for this result :p
[Touch Cruise ROM Development] bally3:
Another interesting discovery.. (wheww.. slow down man!) ;)

On Drakh's findings, I installed GFXBoost as a service and noticed that the 3D now works even when the 3D mode is invoked in SPB3. No noticiable gains and I cant see any way of determining that its even using the 3D driver, but it works anyway.
[Touch Cruise ROM Development] Drakh:
Bally, Gfxboost will do 2D rendering so you will see no improvemente in 3D programs, it's easy to check if it is working or no (run a video with lots of movement in Coreplayer (directdraw mode)) it must run as smooth as with Qtv mode, you know what I mean, also MS3 feels the change, scrolling becomes smooth (scrolling up/down).

It's weird, btw, how does lights3D run in your device? completely smooth? of it does skip some frames? I ask you that because, in other ROMs it runs 3D drivers, but someway lights 3D skip frames meaning something is going wrong and there Gfboost won't run (even M-Anime 2.0 light version does that and Gfxboost is useless).

Please, someone test my claims, it's: first Install M-Anime 2.0 Full ROM (I mean Full, no lite), second install HTC-CA 3D drivers located at the begining of this thread, third install Gfxboost) that's all (if you want also want dialer to improve, install Opal dialer found in M-Anime 2.0 thread), you will feel the change; I've tried this combination with every newer ROM than M-Anime with no success (less the last german one ;)).

In an earlier post I told that one program can use Gfxboost at one time, but I never had a problem with that, except when I used AudioManager TouchFlo2D that doesn't release it, but since I use MS3, it's not a problem for me, you can see what program is currently using Gfxboost going to Control Panel, System, Gfxboost, btw you can enable/disable Gfxboost there and see how 2D rendering is affected... inmediately noticeable.
[Touch Cruise ROM Development] pcarvalho:
those findings were on what rom's? every finding should be a little bit more explicit, else one has to guess ;)

its seems that its possible to run 3d driver...when i have more info i'll post it...cheers
[Touch Cruise ROM Development] bally3:
Drakh: Lights runs silky smooth on my device.

pcarvalho: I'm using Maxnipers Omnia rom.. went back to it because of the 3D driver working great with it, but I dont think this thing I found would be rom, or even device specific.
[Touch Cruise ROM Development] Drakh:
Weird, it should run fine, maybe Gfxboost is working now for you? (also weird because improvement is noticeable since the 1st second), try using Coreplayer the way I told before, what does Gfxboost says? (it must say Enabled(Active)).

Bally3, hand me the link of your ROM to test, so I'll tell you if I can get Gfxboost run in that ROM.
[Touch Cruise ROM Development] bally3:
Somewhere in the darkest recesses of my infinitely tiny brain a light bulb went off.. of course maxnipers rom was made in m-amines kitchen and probably based on his rom - doh! :rolleyes:
[Touch Cruise ROM Development] Drakh:
haha, so you were "assembled" in the times of Eniac, when computing was run with vacuum tubes:p (I imagine little creatures in hurry inside your brain, yelling 'run! run! change that bulb!').
[Touch Cruise ROM Development] bally3:
yes except the little creatures were in m-amines kitchen cooking roms ... we need to find out what version the rom was. In any case it was a6.1 with the lower memory.

I read in one the threads by SuperJMN that there has been some 2D activity today using 3dD drivers and GFXBoost and on 6.5 roms.. any info on this?
[Touch Cruise ROM Development] Drakh:
Well, he states that he succeeded running 3D applying a self-made patch, so I have no more info, some windows 6.5 ROMs come with 3D drivers that reads "MS Reference driver" but in fact just captures calls and does software rendering (lights3D gives, mmm?, 3fps), maybe he's refering that driver? dunno.

I tried installing HTC-CA 3D drivers in latest pcarvalho's 6.5 ROM with no success (expected, I haven't seen 6.5 ROM with HTC-CA 3D drivers in Kaisser forums), so no funcitonal Gfxboost.

Bally3, again, don't have the link of your Maxniper ROM? I want to test there.
[Touch Cruise ROM Development] bally3:
Here you go, my good friend Maxnipers Omnia rom - released in December just after my good friend M-Amine posted his entire kitchen and tutorial to build roms that helped spark up some of the newer chefs we see today on the Polaris. (Not forgetting to thank udk, whose Polaris kitchen started it all and bepe whose tools made the all the kitchens possible etc..) you get the general gist ;)

I found a registry entry that had M-Amines name in it so I think we can safely concur that this was one of his base roms.
[Touch Cruise ROM Development] Drakh:
I'll check right now...

Sorry, I can't get Gfxboost to work in Maxnipers Omnia rom, it happens the same when I install M-Anime 2.0 lite, 3D drivers seems not to work properly, I reinstalled 3D drivers three times, lights3D is not completely smooth (almost) and when backlight dims, lights3D losses about half frames (that doesn't happens to me on the other ROM, lights3D is the same smooth when screen is full bright or dimmed).

Btw, this ROM comes with 3D drivers, but it reads "Xscale Optimized 3D drivers"... weird.

I'll try to reinstall drivers a couple of times more, but I tried the same in other ROMs without success :(.
[Touch Cruise ROM Development] smaaland:
How well does this run with SPB Mobile Shell 3? Does it improve the performance?

I've heard about crashes and such problems before with these two combined. How is it now?
[Touch Cruise ROM Development] Drakh:
If Gfxboost is working OK, MS3 works completely smooth (highly noticeable when you fast scroll up/down).

Problems with MS3 are related to enablig 3D mode in spb config, never had a single crash but sometimes I get a black background when I use carrousel and enable it, I see no performance gain with spb 3D mode so I disabled it anyway.
[Touch Cruise ROM Development] minyominev:
I have 3D drivers and Gfxboost working on PDAVIET ROM WM6.5 (Core 21234) by TranMinhMan with help of the package released by SuperJMN here 2D acceleration for Polaris under WM 6.5 (package inside)

So far so 'smooth':)
[Touch Cruise ROM Development] smaaland:
Nice!

Right now I'm running an official HTC WM6.1 ROM, with no 3D driver and no Gfxboost, and I feel like it's a little laggy sometimes. Do you think the driver would increase the performance, even if 3D mode in SPB Mobile Shell is not used?
[Touch Cruise ROM Development] Drakh:
Good everybody now is aware of Gfxboost ;), the program was available since several weeks ago, say thanks to Chainfire for this great work.

There are others thing we can add to our device to improve user experience further.

I'll keep an eye on them and tell what I find.
[Touch Cruise ROM Development] mutant92:
nice tool :)
[Touch Cruise ROM Development] SuperJMN:
Thanks! But I've checked it and it doesn't have the required function eglBindAPI :(
[Touch Cruise ROM Development] bally3:
So are we getting anywhere on this project? seems like we're a bit in limbo since the 6.5 / 3d driver discovery which btw works very fluidly on pcarvalhos's 85Mb build - just wish e would create a clean one of this rom that would have nailed it for me.
[Touch Cruise ROM Development] SuperJMN:
People are too focused on Qualcomm MSM7201A devices. Polaris is not receiving the support of the community :(

No devvers, no progress. What about OpenVG for Polaris? we need a valid libgles_cm.dll, but we have needed it for weeks... what's up?

It's a pity that a device that is well capable, would have to be tied to this undesirable situation.
[Touch Cruise ROM Development] Drakh:
Greetings Bally3!

Well, what I can share now is that I see qcamera live in imate 9502 & 8502 (seems Imate licenced it) so hardware acceleration for their cam app, maybe also qdecoder and qtv inside ROM?, read my post about it:

http://xdaforums.com/showpost.php?p=4051339&postcount=1476

Ask a developers to take a look at that attachment and the ROM file.

The latest Neo2007 beta OpenVG drivers also improves software rendering so much that it makes me wonder if I should move to a pure software rendering ROM and accept the 15Megs where video shared memory resides. :p. (I must look apps that use renders with GDI/GAPI in this scenario).

Well coded programs also do wonderful when using renderers other than directdraw in our qualcomm devices.

*rant on*

I knew qualcomm was evil, but not this level, I'll never buy a device with a qualcomm CPU inside again, they earn their beans only licencing technology, even in incomplete pieces trying to get the most money from manufacturers not caring about final customer.

*rant off*

Cheers.
[Touch Cruise ROM Development] whitealien:
Well, what I understood is that Qualcomm is only a chip maker, but it was HTC who decide not to pay full licence to use that chip. Am I wrong?

The problem now with Polaris (and Kaiser) is that many good devs moved over to another devices or are just busy with another things. Where are Chainfire, rogro82, NuShrike, NikMel? At the moment there are no devs for Polaris, sorry. :( We can just wait and hope that someone will apear some day or just move on like them. Anyway, smartphone life is 2-3 years no more, and Polaris is already 1.5 years old.

For those who are looking for good 3D ROM should check pcarvalho's latest cook. Its really fast even so you must sacrifice 16Mb of RAM for that.
[Touch Cruise ROM Development] bally3:
Agree with you on the pcarvalho rom - runs lightning fast but you cant really blame the devs you mentioned, they didnt even have Polaris devices to begin with so we were lucky to get the dev they brought to our devices - especially Chainfire whose contribution to all devices is widely known and appreciated.

There have been many opinions about why the Polaris lost its development so fast but I actually think this is the way its going to be as device life cycles seem to be getting shorter as new devices are released faster.

The legacy for our devices are a good number of decent roms, a 3d driver and not to forget the large number of software thats out there that works quite well on qvga devces and is still supported.
[Touch Cruise ROM Development] Drakh:
Agree, the invaluable help of developers/contributors gave us a functional device we now enjoy, sad they are more focused to more recent devices, now but still I thank all them and a warmer hug to 'alive' developers/contributors for our devices like pcarvallo, chavonbravo you :p and so on, we know there are still more work to do, basically in graphics performance, I guess the rest is mature.

Bally3, did you contact any developer to take a look to that dll file or to look inside the imate ROM to see if some interesting graphics files can be found? if they licenced qcamera, I think they also licenced qtv also and that means 3D dlls, if not, at least we might en with a hardware accelerated camera app :p

greetings.
[Touch Cruise ROM Development] bally3:
Nope. I'm taking on more of a supportive role with the 3D driver now, Neos2007 is your man to take things forward. I'm really time-constrained these days and need to concentrate my efforts on the Android project which I really do think has massive potential and realistically has a much better chance of completion than the 3D driver project at the moment as I've mentioned before, its all programming and debugging thats required now and not a matter of trying different files from newer devices and releases.
[Touch Cruise ROM Development] NeoS:
And still, without your initial post, we wouldn't have 3D on Polaris at all.

That said, sadly the original P3D team is gone. Most devvers are doing other stuff (like Bally3 does Android devving) and aren't interested in the old MSM7200 chip anymore.

I'm still interested in getting this show on the road though, so i've started a thread in dev&hack in the general forums, hoping to get some more knowledge and support from various device-users.

Needless to say, most users went on and bought newer devices (Diamond, Pro, HD, etc) and these babies have OpenGL acceleration out of the box, without the bugs. However, these drivers leave much to be desired, so they need constant tinkering when new devices and files pop up.

I'm on the verge of getting a Polaris, just to get this project running again...
[Touch Cruise ROM Development] imfloflo:
Very sad to see all dev getting new device instead of concentrate effort in this device which has the capacity of running correctly the driver.

As we can see with the progress made in the android thread.

I'm still here to test if needed.

I hope others polaris user will post in this thread to see how many we are to really want this for our polaris

.
[Touch Cruise ROM Development] peredenoel:
have a try.....
[Touch Cruise ROM Development] Drakh:
We are many for sure imfloflo, our device is cute and 400Mhz ain't any slow, so cute that Iolite kept the shape :), well, I want to point again if someone took a peek at imate 9502 ROM, their camera app uses hardware acceleration, there's a dll that shows that (qcamera), and more likely video hardware drivers (qtv), maybe we can end with better video drivers and if not with a better camera app ;).

In another topic, why the huge difference to enable more free memory but breaks video acceleration (15MB)?, the device uses 320x240x2 = 150Kbytes plus some Kbytes to hold 3D, it'd be interesting to find in what address the video buffer is mapped so we can tweak more nk.exe to a lower/higher limit without conflicting with that region so the tradeoff of free memory in a hardware accelerated ROM and a non-hardware accelerated ROM lowers.

According to chavonbravo this part of code is responsible of that:

38459FE530559FE5A13EA0E38224A0E3 (original)

38459FE530559FE5A13EA0E38324A0E3 (tweaked)

Sadly in my life I didn't choose to be a programmer, but a support guy.

I'll try to be more active in forum and help in whatever I can, Android is doing huge leaps thanks to bally3 and his gang :p

Let's keep it up.

Cheers.
[Touch Cruise ROM Development] NeoS:
Hey, I'm a support guy too. But that didn't stop me from trying to better these devices. ;)

I have already assembled a dev & test team for general driver devving, but i could always have a few MSM7200 users on board.
[Touch Cruise ROM Development] saayinla:
Am screwed up...I have just installed this graphics driver on my HTC TOUCH HD. I dont know what i was thinking and now my phone is stuck on the boot screen.
[Touch Cruise ROM Development] SuperJMN:
Try to reflash you device using your Hard SPL. You just have to press the camera button and then reset withouth releasing it. When you are in Hard SPL, connect it via USB and start the program to flash.
[Touch Cruise ROM Development] NeoS:
I got my Polaris. Flashed pcarvalho's 6.5 rom, but the htc-ca drivers aren't working? :S could anyone get me up to speed on this?
[Touch Cruise ROM Development] bally3:
you using the 3d one? that should work ootb.
[Touch Cruise ROM Development] NeoS:
I wasn't. Now i am. But installing the P3D driver didn't work on the non3D version, why is that? The new 6.5 kernel?
[Touch Cruise ROM Development] w04g005:
As far as i know it depends on the OEM Drivers. In the 3d ROM it should be 3.13 and in the NON 3d ROM it should be 3.19!

I know in the ROM description of pcarvalho it is always 3.19 but i assume it isn't correct! (You may ask pcarvalho)
[Touch Cruise ROM Development] pcarvalho:
no 6.5 kernel, i wish :D

non3D is kernel patched to get 101mb of ram on newer drivers (3.13, 3.18 or 3.19 - all the same drivers i guess)...

3D drivers also will not work on non3D cause DDI is from 1.XX drivers...

cheers