yashsingh1/xdaforums huggingface dataset:
[Touch Cruise General] bigduck:
Anyone please help me. I get errors:

D3D Demo - (it shows up with a white frame around my screen)

DLL Checker: msm_clk.dll failed with error 193: %1 is not a valid Win32 application

Lights (D3D): Could not initialize Direct3D. The tutorial will exit.

Text3D (D3D): The sample has run into an error and needs to close: InvalidDeviceException

Triangle (GL): Triangle is not a valid Pocket PC application.

I'm using HTC Cruise with WM6.1:

ROM: 1.28.405.1 WWE

Radio: 1.58.21.23

Thanks in advance
[Touch Cruise General] NeoS:
It seems to me that the files used in the driver are severely outdated or that the DDI.dll isn't compatible anymore.

I hate to say this, but i'm afraid the driver doesn't work on newer roms...
[Touch Cruise General] Svenvdmeer:
to specify the "smootnes". I've use R8 only briefly and i've use R0 before itje 3.5. Manilla on 3.5 feels smoother than on R0 and video playback is better. I don't know enough of this to say that this is because of the drivers but the rom is working fine.
[Touch Cruise General] imfloflo:
and if all works fine mst we remove them too ?
[Touch Cruise General] secoseco:
that is so easy

buy a new Polaris and compare it with the one that you have now

thanks to all XDA developers
[Touch Cruise General] JAYmasta:
why you can't put driver separate ? as *.cab file ?
[Touch Cruise General] NeoS:
Because I already did. And it was a complete disaster. Because of all the different roms, radios and hardware out there, this driver could really BREAK your device. And not just so you have to hard-reset... It BRICKS it. So it needs to be configured and tested properly. That's why we've asked some chefs.

So if you want the drivers: find their roms.

I'm already making a list in the second post of this thread for you guys to find them easily. As stated in the first post, you can also post feedback and issues here.
[Touch Cruise General] bally3:
Because the cab is still in development stage. Remember that chefs will test the rom for stability before release, but cabs can be installed on any rom and, as the user in the earlier post found, can easily upset your device.

Dont worry JayMasta, in a few days, swtos, udk and all the chefs will have updated to the drivers hopefully.

They have all pledged their support which was really good of them. :)
[Touch Cruise General] JAYmasta:
I hope, cuz I use only original rom that's why I ask. and realy thanks a lot

and one more question what about manila 3d after this driver ???
[Touch Cruise General] bally3:
Its down to you imfloflo, you're a seasoned user and able to decide whether its worth risking.. personally I'd wait till the chefs include it in their rom and upgrade to them instead. :)

Itje's already released his and I'm sure epimazzo, udk and swtos wont be far behind.
[Touch Cruise General] imfloflo:
yes but the chefs will not do much that copy the ddi.dll in their own rom that's all the cab do already do that.

and when they release their rom, peoples'll be beta tester.. No .what they can do to increase the stability off the ddi.dll that the cab can't do ?

edit: udK is on the forum :), i hope he 'll see if he can release aR1 version with or without this new ddi.dll

udK Last Activity: Today 12:06 AM :p
[Touch Cruise General] itje:
Is it so hard to understand.

They dont want ppl to permanently brick their device.

Add a warning you might say,add instructions too.

sure..that will help on perhaps 40-50% (obs i skipped that step..)

the rest will install the cab, and then start a flamewar when the device has become a paperweight :p
[Touch Cruise General] imfloflo:
I know lot of people want this new ddi.dll but they don't know they can brick forever their phone. and i know they 'll return theriself to the chefs if it bricks their phone. so you have right to becareful and use a very good disclamer :)

off for today go to bed, dreaming R1's udK ^^
[Touch Cruise General] ouioui01:
where's the cab please!!!

I want to brick my device...and don't want to install an another rom for the moment.....

So please, please....where's the cab!!!

thx!
[Touch Cruise General] iori:
hei imfloflo,

do you really use radio 1.59.42.23?

as far as i know, the latest official radio rom is 1.59.42.15

is there any latest official release or its unofficial?

just curious;)
[Touch Cruise General] iseeka:
Congratulations for putting some order in 3d drivers dev
[Touch Cruise General] imfloflo:
@iori yes i use this version this version is integrated in a french operator rom and some people extract it. I use it and all working good. you can find it here http://xdaforums.com/showthread.php?t=430182
[Touch Cruise General] DarkPower:
Thanks for the ad... :D
[Touch Cruise General] NeoS:
Did anyone notice with itjes' 3.5 ROM any programs shutting down unexpectedly?
[Touch Cruise General] radem205:
I have run itje's ROM from the beginning and I haven't found any bugs with the 3D drivers. Everything is working great!
[Touch Cruise General] JAYmasta:
I understand why you have to delay leaving the driver, saying that it will kill every device, it could only restart or make your screen flicker. Others are ignorant but I will sit only in the official firmware, me all sorts of unnecessary problems. The question is how long we'll pull the rubber ?
[Touch Cruise General] dwaradzyn:
I did notice that with Opera. I use it very often and had about 15 crashes since yesterday. We need to keep in mind that opera 9.x is still beta. I used almost every build of Opera 9.5 (nine or ten of them) and I was never satisfied with its stability. The one in this rom is least stable from what I can tell. I'm not sure it is driver related though.

Manila crashed once for me. Again I cannot tell if it is driver related.
[Touch Cruise General] JAYmasta:
you can not tell others, because it might ROM is not working as they should, like all not original (this is not the first device, was not yet firmware without any problems - ever) and can manila for example, or opera and when the original rom then clearly what's what.

variance official firmware is that there are a lot of professionals, but not on the original one in their free time .....

I am not against the non-original rom but for the freedom of choice, availability of a driver inside any rom I am tied to yet unfortunately the problems that the end is not visible
[Touch Cruise General] NeoS:
Relax guys. udK and epimazzo are both working with the driver. That's most probably why their release is postponed, and this thread hasn't had much feedback yet.

Patience is a virtue. ;)
[Touch Cruise General] bally3:
I agree, but the provision of a driver in cab form that overwrites "original" system files then should not be of interest to you either, as in the case of the 3D driver.

There is absolutely no validity to the argument that one should proclaim the right to stay on a original rom and then ask for cab files that install over original system files as this can potentially invalidate your warranty should you 'brick' your system anyway.

I would neither recommend or discourage anyone from a cooked rom - be it a clean one or loaded with applications. To each their own - but if official roms are your personal choice then you should be looking to keep the integrity of the system files and avoid the installation of software that can over-write them.
[Touch Cruise General] NeoS:
Anyone tried itje's OPAL rom?
[Touch Cruise General] radem205:
Yes, it's working excellent. No problem at all with the 3D drivers and the ROM is very responsive. Never had this experience before!!!
[Touch Cruise General] maaafeb05:
Yes, I did, but after one day of use. I found something strange other than the small bugs. The phone turns off itself every about 1-2 hours of not use. Have anyone experienced this problem and if so, how can resolve this? Thanks

Any help is appreciate it
[Touch Cruise General] hejhomer:
Nop. My Polaris on Opal is not turning off at all. Really seem to be quite stable. Probably you must have had problem with installation... By the way video playback in Core Player is definitely improved…. taht's what I’ve been waiting for!
[Touch Cruise General] maaafeb05:
the installation was a success and nothing went wrong. I did reflashed it today with SPL and still the same problem. Anyone has the same, can you tell me how to solve it?

Thanks
[Touch Cruise General] SaBo:
Yes.

Under start -> settings -> connections -> USB to PC do not disable "enable faster data sync" or "enable advanced network"

You won't be able to sync via USB. Sync via BT works fine though.

Sascha
[Touch Cruise General] secoseco:
Hi Neo

yes I test it and it's overall amazing but I think in the next release it will be the best at moment

I test all 3D programs with no bug accept Text3d which I get the text unable to read it's like a blocks and don't know if that normal or don't

I want to ask about something that I know it's not related to 3D driver, what about the performance of shooting video by camera, as you know it's have very low rate frame/sec, and there is a trick to solve it by cover the lens by hand then pres bower bottom and wait for a few seconds and press the power bottom again and waiting for a few seconds and uncover the lens and the performance for camera will be amazing but with a dim picture

is there any way that 3D driver Team can think for solving this problem ??

thanks
[Touch Cruise General] NeoS:
No, sorry. it has something to do with the camera driver made by HTC. It might make a small difference if we manage to get the 2D work better, but for now we focus on 3D.

The text3D is correctly displayed. We know it does that and it has to do with the program, not the driver.
[Touch Cruise General] imfloflo:
Just a simple questions: is udK working with you or you just sent the driver and he works alone ?

and When itje release new rom ?

Have you plan to look for 2D driver after 3D working ? :)
[Touch Cruise General] secoseco:
Thanks Neo
[Touch Cruise General] NeoS:
udK is already working with our driver. That why you guys have to wait so long for R1. ;)

itje will make a new Opal rom for Polaris soon, we're testing the latest driver build on his rom.

About 2D: we don't know yet. Maybe we can pull it off just like we did with the 3D driver, but most likely we'll keep working on the 3D for now, since it still isn't fully explored yet.
[Touch Cruise General] frankbalzan:
Viewing 640x480 videos on Polaris?

Hi sorry for the newb question, but i am currently thinking whether to buy an htc diamond or cruise. I would definitly go for a cruise (due to better battery life and sd card) but I would like to know if the 3d drivers the community is developing are currently able to make a user view a divx video 640x480.

I know that 2 ROMs have been posted with these drivers, but I could not read whther these ROMS actually run hardware acceleation or improve dramatically the graphics.

Thanks for you help and development!
[Touch Cruise General] NeoS:
First of all, the screen resolution of the Cruise is 320x240. So it wouldn't make sense to play videos at 640x480.

However, the driver drastically improves the performance of the Cruise to such an extent, that some users even say it's FASTER than the Diamond. I can't really confirm that, because i've never even TOUCHED a Diamond, but the benchmarks on GLBenchmark.com say alot.

I'd just say: if you don't mind the design of the Cruise and just want a device with the best available abilities, go for the Cruise. If you want TouchFlo3D and all those fancy graphics the Cruise doesn't have (yet), go for the Diamond.
[Touch Cruise General] frankbalzan:
Thanks for your quick reply. The truth is that conversion takes to much time... thats why I would natively just copy the videos on the Cruise.

So, if I am understanding well, the hardware acceleration has been enabled? correct?
[Touch Cruise General] frankbalzan:
Sorry again... where can i find the benchmarks you mentioned pls?
[Touch Cruise General] iseeka:
it isnt Ported OPAL rom for polaris, i guess...... itried that and was a bit slow in my machine or didnt i wait long enough to load everything?

......mmmm.mmm

hope it is soon

thanks for your job
[Touch Cruise General] ys222:
3D world ...

I have read most of your writting here regurding the 3D driver as well as amazed from the progress from week to week, also I know that "generaly" in life 3D is better then 2D :-)

So please help me understend over my littel cruise - what different should we all expect once the 3D driver will be use?

only for games? - if so, can you point me to one so I'll be able to compare in time been

Shell ? - what is going to be different? the animation ? TV? Video ?

if the Diamond has 3D driver - I didn't found any special preformance then the polaris aspacialy with the R0 ROM

thanks
[Touch Cruise General] NeoS:
Added news to post #3.
[Touch Cruise General] SaBo:
I'll be damned. The good "old" Touch Cruise beats the Touch Diamond hands down.

Amazing results!

Who would have thought that this would be possible?

Thanks

Sascha
[Touch Cruise General] ouioui01:
where's the release ?:confused:
[Touch Cruise General] benleonheart:
When they consider it proper to be released, stable enough.
[Touch Cruise General] NeoS:
Correct. Here's the situation:

We've asked some chefs to cook in our driver for you to test. If there are any MAJOR problems with the Polaris after flashing the roms (constant reboots, hanging devices, no wake-ups, etc.) we want you to report them here. This way we can see what different roms do and if we need to fix our drivers further.

Team P3D wants to give every Polaris user the joy of 3D on their phone. But we want it stable. There is a big risk of bricking your Polaris, and nobody wants that. That's why we don't release a "free-and-easy-to-install" cabfile yet.

I hope this clears it up somewhat. Again, we need your feedback!
[Touch Cruise General] ouioui01:
Neo,

isn't the risk of bricking the device is higher with rom's updating than installing a cab (a hard reset is easier to recover the device if drivers are not cooked in rom ....i let you imagine if drivers are built in rom, what would happen...hard reset is useless) ? Correct ?

Or maybe, i am too stupid :cool:

Maybe you won't that someone else appropriate your work ...

For now, if i want 3D in my device, i MUST use a cooked rom ??? Of course, im using 3D in my device...thx to XDA and HTC CA !!!

cheers!
[Touch Cruise General] imfloflo:
Waiting R1 to give my feedback :p ( joke )
[Touch Cruise General] NeoS:
We asked the chefs to test them before release, so it's pretty safe to use the roms. Cabs however can be installed on ANY windows mobile device and thus is more risky.
[Touch Cruise General] imfloflo:
And can we install this cab on other devica than polaris ? PP3D_v003.cab ?? in which version are you now ? is there really difference between 003 and the actually version ?
[Touch Cruise General] dwaradzyn:
Is there really any risk of bricking (which is not recoverable even by hard reset)? Do you really mean Polaris can be bricked by installing 3d drivers? Did that happen to any of 3d team?
[Touch Cruise General] imfloflo:
yes they semi brick their device, if you say to the driver to jump in another memory adress yes you can brick your phone.
[Touch Cruise General] ouioui01:
curious that HTC CA cab for kaiser did not brick a lot of devices :D:D.

did you count how many people ask for installing some polaris roms for other devices!!!!!!

for now, i have not seen a rom without bugs....

I really don't uderstand....oh, i've forgotten .... do you want donations ?:cool:

cheers!
[Touch Cruise General] ouioui01:
i'm using HTC CA cab for Kaiser...and my device is ok! LOL
[Touch Cruise General] udK:
This is a joke right?! :eek:

There is any risk to brick a device installing a cab.
[Touch Cruise General] imfloflo:
Installing new driver, which aren't good for our device,can brick or broke your device yes.

Don't panic they'll not release a bad driver and they wait to have a full working driver before release it :)
[Touch Cruise General] NeoS:
That's why we say it's on your own risk. But if rom chefs test and release roms that work, there is a slim change it will brick the device. See it as a small insurance policy. ;)
[Touch Cruise General] NikMel:
There is NO cab or any installation software that can brick any pda!

The negative think could be is that your device will not startup and you must do a HARD RESETE!
[Touch Cruise General] ouioui01:
neo,

my friend, i'm not an idiot...if cabs brick devices, why HTC CA drivers for KAISER did not brick our polaris before :D:D ?

I think there's an another reason...which i don't see...

I repeat : ROM upgrade risks more than installing a cab....A HARD RESET deletes cab's files.

@ imfloflo, don't talk for nothing, my friend!

cheers!
[Touch Cruise General] imfloflo:
ok, but if the cab change the chipset jump by asm command , a hardreset can do anything, it's in the chipset code and it's too late.

I don't speak anymore :), i success to make udK speaking woooaaa to proud :)
[Touch Cruise General] NeoS:
I'm not saying it WILL brick your device. Flashing CAN brick your device.

We just want to sit on the safe side for now.

Be patient you guys. :p
[Touch Cruise General] secoseco:
Hi Neo

what is this ????

I do compare Cruise with HTC Touch Pro & Touch Diamond !!!!!!!!

is this April flam, I mean October flam ????????

I am joking, did it mean that we will get TouchFLO 3D if we can convert it to QVGA ???

and which rom now have the last 3D driver from the amazing team

thanks
[Touch Cruise General] rogro82:
Ok let me clear this one up... ( dont call me if it will :D but ) these drivers can/will ( as in want to ) NOT brick your device.

All codes are based on the kaiser drivers which are updated based on a few changes we made when were porting the drivers for the Polaris..

There were somethings found that speeded up the drivers a bit and these changes are now also implemented in the Kaiser drivers.

The only really difference between our driver and the polaris driver are some specific addresses that are different between kaiser and polaris and we are using a different DDI because the one the kaiser was using didnt work well for bitblt on a polaris. ( For what i know they still use/support ddi 3.28 and dont include one in their cab file ).

Our implementation is based on ddi 3.13 which has given the best result in both 2d as 3d on a polaris.

The biggest risk involved in installing this cab will be the risk of a needed hardreset although this risk is small because the final release cab

will not include a ddi

.

This way the risk of needed hardresets is reduced by a lot, but it will mean u need a rom that has the 3.13 ddi or make a 3.13 work on your own rom. Most if not all chefs are using this ddi at the moment so this wouldnt be a problem for most people.

Thats also the reason the chefs are implementing it as we speak.. this way we can test if the drivers work on all roms using this ddi without any problems..

Ive tried to brick my device so many times without success installing these drivers.... i wished it had so i could have send it back to HTC so they would finally have a working 3D driver :D

The reason that bricking is mentioned is because we dont want to take ANY responsibility and dont want to get a class action lawsuite against us for misinforming people :D ;)

And now im getting me a beer....
[Touch Cruise General] imfloflo:
for the moment chef have receive the lastest version of the driver they 'll cook new rom soon after testing stability. if we can convert it yes we can have it :)

looooooooooooooooool :):)
[Touch Cruise General] NeoS:
Thanks rog. But you should definitely reduce your drinking. :p
[Touch Cruise General] rogro82:
No man it makes me type so much crap... cant help myself ;)

AA is for quiters :D

Edit:

Oh crap out of beer... getting me a wodka instead :) ...
[Touch Cruise General] whitealien:
mixing beer with wodka ... :)

I think we are going to loose rogro tonight
[Touch Cruise General] imfloflo:
correct : i think we are going to have a new driver with new capability and a flur screen :p
[Touch Cruise General] whitealien:
hahah

I think rogro found solution how to get 3D experience on Polaris - you must drink half bottle vodka and 2 beers :D
[Touch Cruise General] rogro82:
Thats why it was scrolling at first :D Now i see clear

Vision set to 2d mode as we speak no need for 3d anymore... making me throw up :p

Also mixing in some red bull to keep me awake..
[Touch Cruise General] itje:
im sure he will enter 4d mode anytime now
[Touch Cruise General] rogro82:
when im off to bed ill enter double d mode :D

and now no more talk about my addictions... :)

@itje:

How are the latest drivers holding up?
[Touch Cruise General] itje:
fast and furious my friend :)
[Touch Cruise General] epimazzo:
Confirmed:D

And...no major issues at the moment I'm writing this post...but tests have to be in place and ensure all conditions has been covered up...:)

As a famous drink slogan used to say....let's keep walking...;)
[Touch Cruise General] NeoS:
Thanks Epimazzo.

And rog... if Buckler was still in business, i'd donate a crate to you. ;)
[Touch Cruise General] imfloflo:
So you are release soon the next version of your rom? :)
[Touch Cruise General] secoseco:
Hi Neo

I just test M-Amine 2.0 RC3 rom and found that all 3D test app not working as other rom, in other words I fell that this rom not included the 3D driver, I do hard reset and test the rom again and get the same, not supported 3D, I don't know if there is something wrong with me or not and I hope that any one test this rom can confirm this problem

the best rom I test untill now using 3D driver it's itje's Opal Beta 2

thanks
[Touch Cruise General] NeoS:
M-amine's rom doesn't currently have the 3d drivers built in. Just wait for RC4.
[Touch Cruise General] timmymarsh:
Hi all,

excuse me for my ignorance but i have been watching the 3d driver dev since it started. Now that official 6.1 is here, has anyone tested/benchmrked this? HTC did say that there would be an "improvement" ....? When the cab is finally released will this work on the official 6.1 rom, are the necc dll's on it (3.13 i think??)

Apols for my stupid question, i am trying to keep up with guys and your amazing developments :D I am patiently and excitedly waiting....:)
[Touch Cruise General] secoseco:
thanks Neo, I hope that you modify this post because I thought that all this roms included 3D driver
[Touch Cruise General] NeoS:
Whoops. You're right. I forgot to add the "SOON... In theatres near you...." line.
[Touch Cruise General] ouioui01:
i uderstand now why you still don't release the cab....it's not for bricking devices...or law suite problems....

NICE signature Neo!!!!

Cheers!
[Touch Cruise General] NeoS:
You're accusing me of wanting money for it?

Let's make one thing clear: If it was me, the cabfiles was already online for you guys to toy with. Team P3D agreed on a release plan and i stick by the decision.

I'm not in this for profits.

Ah to hell with it. Think what you want. I'll just stick with the project. See how you get your answers.
[Touch Cruise General] rogro82:
Hopefully it wasnt meant that way... ignorance happens all around you... If people think you or me or anyone else having a donation link in their signature are in it for the money then they shouldnt download the cab and do all work themselves ;)

If I should have made all ours i invested in this project for a boss i would have enough beer for a month ;) :D

Thats why no money is asked and things arent licensed... we offer our services for free... if someone likes what i do they can donate something... nothing more than that to it

Cheers! :cool: