yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] NuShrike:
Sorry, it's going through private dev currently. Almost stuck on the dot3 bump lighting (Doom3) that I'm figuring out.

You can try out some other demos I had put out:

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

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

D3DDemo is also a good one, and you've already said it's ripping. :) I'm guessing > 100FPS now.
[Touch Cruise ROM Development] nir36:
Bally, i have to thank you for working on this project and making it as official as it is. considering polaris is a WONDERFUL device i'm so happy one of it's only faults is being taken care of. i'm willing to help with the testing as this is the only thing i'm capable of during this time (very busy with uni)..

CHEERS!
[Touch Cruise ROM Development] Chainfire:
You guys mind if we release it on HTC-CA when it's done (with credits, of course) ?

To do that, we'd have to make a CAB, but to test that, we'd need some folks willing to hard-reset to their 'clean' 6.1 ROMs, installing the CABs, and seeing if it works. Any volunteers there?

Edit: Note that I myself will probably be out of internets for about 4 days starting now, I'll try to read up, but this topic has an insane pages/minute count.
[Touch Cruise ROM Development] soterman:
More than happy to help out!
[Touch Cruise ROM Development] bally3:
Of course not Chainfire.. we'd be more than happy for you to do so.. Never forget that the inspiration to take this on came from the development of the driver you guys did on the Kaiser, well before a Polaris port was considered.

I think with Rogro and NuShrike on board with their dll optimisations, we are about to take the driver further than it was before - which should be good news for both Polaris AND Kaiser users.

off to work .. be back later ;)
[Touch Cruise ROM Development] joergswa:
Yes man, i love to make Hardresets... ;) I think i will flashed the new R1 Rom from udk, today or tomorrow, so HR is nessesary. So i will test the driver, give me the cab!
[Touch Cruise ROM Development] NeoS:
Chainfire, I hope you've read the first post with updates. I've made a cab which I also tested. It works and gives you a few testing tools also (like the kaiser cab) You have to hard reset before use, that's a fact.

I don't know what the others think of a hosted file on HTC CA, but i'm for it. As soon as we have a stable driver, we'll send it out to the public. As for now, we're still in testing and modifiying phase.

Good to see we've got so many good responses from the community.

And it will only grow when HTC CA is going to host our driver in an apart Polaris section (because it's obviously different from Kaisers)

I'd like to repeat the request Bally3 made:
[Touch Cruise ROM Development] imfloflo:
How the kaiser member install their HTC-cab, should they hard reset too?

If not ask a chef off thier topic how make a cab without hard reset, but i understand ddi.dll is in use when you boot your phone and when the first screen appear.is that right ?

I'm ok to test the cab, i already test Android SDK 1.0 for vogue on my polaris with dcordes and use udK R0 until the release off R1 maybe this afternoon.
[Touch Cruise ROM Development] Svenvdmeer:
never mind...
[Touch Cruise ROM Development] joergswa:
R1 should release today, so you can read in this thread: http://xdaforums.com/showthread.php?t=425612&page=75
[Touch Cruise ROM Development] bikerg:
I'm currently using a clean install of HTC's latest rom, I'd love to help.
[Touch Cruise ROM Development] rogro82:
I know everyone wants to help get this to the public... but remember there are still issues which have to be adressed before bringing this to the public.

We cant put anything out that isnt working as is shoot be. If more people start testing now this will mean this thread gets flooded with the same calls and it will be impossible to read through them.

My opinion is to stay with same testing team until main issues are resolved and then make another thread for testing the driver... Im not reading through this constantly and have hard time to keep up as it is.

If this thread gets flooded the only way to make sure everyone is reading vital information is using PM's but that will only take time...

So my idea:

Keep this thread clean and not too many involved for now.

@Chainfire:

I dont know if you have read it allready but our main problem is that rendering stalls/demos hang when the phone enters suspend mode and the screen turns off. I dont know if you guys also had this problem on the Kaiser and if you did anything to fix it?

Already tried every PORepaint setting but they arent helping.

I developed an application that pushes my device into Full Power mode ( like when connected to activesync ), to keep the screen alive but this will cause battery drain for sure.
[Touch Cruise ROM Development] NeoS:
Agreed. We might even consider some other forum or whatever. Like you said: we need to get the vital info from each teammember for this to work.

Rogro, could you or NuShrike make a small list of things that should always be done / tested after each update? Like a GLBench, etc. And another thing: if we'd be able to get our hands on a Toshiba 810 rom, what needs to be done to get the 2D capabilities from that device ported?
[Touch Cruise ROM Development] NuShrike:
We've let this go on the Kaiser because it's usually up to the app to handle hibernate/restore.

The better question may be does the stall happen because the app is calling eglSwapBuffers() right into (and during, and after) suspend state, or does the driver stall because the device went into suspend?

1 should be fixed by the app because it lost context and needs to rebuild them, and 2 should be fixed in the driver. We can test 2 by starting up 3D, stop calling swapbuffers, let the device power off and back on, and see if it stalled. If not, then the app just needs to reinit and restore its context state.

Since there's so few 3D apps out there and most of the ones we're testing are samples and not production level code, we should be careful how we judge the suspend behavior.

NeoS: we would probably need to port the DDI.dll from the Toshiba G810, or disassemble both and combine it into a new one. High level work for the latter.
[Touch Cruise ROM Development] rogro82:
Agreed... if it is because its calling eglSwapBuffers i think the only thing we can do is something like a devicepowerstate check but this will drain performance... Is it caused by the updating ExtEscape call or something else? It also happened using the SetPixel method... It can also be that it happens because of the GETDC call....

I think these are our first leads we should investigate...
[Touch Cruise ROM Development] ouioui01:
@ neo

as you're using the same rom as me, Did you test lights.exe while you're using your device to listen FM radio ?

lights won't start (hangs before loading pop-ups....)

test lights.exe before using fm radio -> ok

launch fm radio

lauch lights.exe -> hangs ?

if i try with Triangle, there's an error on InitOGLES (résult : 3, then press ok : 1274 FPS ). I'll hope that you have not the same issue.

cheers!

What's wrong?

As i haven't got your last cab posted to the team, maybe it's due to my lasts files.
[Touch Cruise ROM Development] NeoS:
I'm at work and i don't have a headset to test this. But i will once i get home.
[Touch Cruise ROM Development] boart:
I dont know if this is off-topic, but....

When we use the 3d accleration. Is it also possible to use the GPU of the Polaris for rendering 2d? Are there drivers for it too? More speed in 3d and 2d cause of the use of the gpu would be amazing!!!
[Touch Cruise ROM Development] speed_pour:
i still haven't done my first flash yet, so i'm still on the original stock rom with original SPL. I've already been backing things up to start playing with cooked roms. I'd be happy to do some testing here. Just let me know
[Touch Cruise ROM Development] NeoS:
Ah. Nice followup in this last post: This driver will and can only work on windows mobile 6.1.
[Touch Cruise ROM Development] SP()()KY:
dunno if this is helpful for you but here you can find some toshiba roms for the g900...
[Touch Cruise ROM Development] bally3:
Thanks Spooky.. not sure that its the same chipset but thanks for the effort anyway.. :)

I was looking at the other Qualcomm devices, interestingly enough the imate ultimate 8502 shares the same chipset..

Neos2007 - can you download this rom and disect it to see whats in here please?

http://xdaforums.com/showthread.php?p=2399522

Thanks.
[Touch Cruise ROM Development] bally3:
NuShrike, from a development angle, you and rogro are the most likely to know which tools/apps are reliable and which arent.

We've been using lights/D3Demo etc and BillboardFPS which Pananza kindly updated to send the results to a text file.

Would it be possible for the two of you to recommend what tools you would like us to use so you get accurate results please?

AS we discussed last night. unoptimised apps will only result in innaccurate results and confuse the issue.

Still looking for a decent FREE benchmark program that we can use... I registered with GLBenchmark yesterday but it doesnt seem to work for me.. :rolleyes:
[Touch Cruise ROM Development] pananza:
Like already mentioned here there are very few 3D apps out there. So having optimized D3D drivers is cool, but not really that useful as of today. To check D3D performance I'd recomend running the apps and demos we have today on different machines (that we know have D3D support) and compare.

Compare how BillboardFPS runs on the Diamond to the Polaris with different experimental drivers for example.

Keep up the good work guys.
[Touch Cruise ROM Development] rogro82:
NuShrike do you know why SetPowerRequirement and ReleasePowerRequirement are imported in the Libgles_cm_ks? Maybe they are normally used to keep the device alive while the d3d apps are running?
[Touch Cruise ROM Development] NikMel:
I just have run the triangle, lights and BillboardFPS (at apr. 2,5 fps) for more then 6 minutes on battery and it was running without any slowdown.
[Touch Cruise ROM Development] rogro82:
with or without the keepalive app or using active sync?? Or something else that will keep ur display from going to sleep mode
[Touch Cruise ROM Development] NikMel:
I've included just content of HTC-CA cab and the latest dll's of NuShrike in my rom.
[Touch Cruise ROM Development] bally3:
Hey NikMel, missed ya yesterday :)

I've been playing with a few registry tweaks..

hklm/drivers/GDI/bpp - default is 16 - tried it at 24 and now set at 32.. works fine.. and display looks crispier?

Also added RemoteHook: with omnio and htc_d3dm.dll - lights used to fail when I did it before.. now it doesnt complain.. no differences though.. but still somethings changed.
[Touch Cruise ROM Development] NikMel:
Try my latest rom (PMed) and see if it works for you too
[Touch Cruise ROM Development] bally3:
sleep mode can be turned off in power settings rogro? sorry if thats a stupidly moot observaton..!
[Touch Cruise ROM Development] NeoS:
That ROM isn't in .nbh format. I can't do much with it using my kitchen.
[Touch Cruise ROM Development] bally3:
damn you're right.. its an .exe and I cant extract/view it either..

Anyone care to venture how to extract and executable rom file?
[Touch Cruise ROM Development] rogro82:
yep you can but im too lazy to change the setting everytime ;) and making everyone change there settings because of 3d is a lil bit too much to ask isnt it :D

Im trying to figure out why the apps hang when the device goes to sleep... i dont think its a problem that should be solved in the apps because even glbenchmark will hang when my device enters sleep mode...

Im gonna try the rom now to see if it makes any difference..
[Touch Cruise ROM Development] bally3:
rogro, do you know why 3D text is blocky? its the only app that doesnt work properly but works fine with omnio..
[Touch Cruise ROM Development] NuShrike:
Same bug on any recent HTC/Qualcomm (Diamond/Touch Pro). Omnia is implemented by different people and probably follows the official design spec better. Since OpenGL-ES is the mainstream 3D spec for all mobile devices, maybe that's why D3D Mobile is practically ignored.

The KS20 driver performs a SetPowerRequirement("{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}\ddi", 0, 1, 0, 0) when it creates a video surface. Maybe it doesn't work in keeping the backlight on.
[Touch Cruise ROM Development] bally3:
Hi NuShrike :)

PM'd JesseW about the Polaris if you still want it.

So what do we try tonight? .. I've just installed NikMels rom - Nice work btw, NikMel, running without any problems and running faster which is great! :)
[Touch Cruise ROM Development] bally3:
NuShrike, just been following the CA compatibility thread at kaiser forum...

two things..

Have we tried this?

And...
[Touch Cruise ROM Development] bally3:
You replied to this posting.. I tried 640x480 on mine with 32bpp - it never used to work... not even 24bpp.. but heres the thing.. I can feel the device getting slightly warm when I run 3D apps.. only a little.. near the camera lens.. nothing to worry about.. but since I did this I noticed it was getting warm even when I was using the phone as normal. Its also a little snappier and screen appears crispier.. could be placebo of course.. but the phone is def warmer which points to hardware rendering?
[Touch Cruise ROM Development] rogro82:
Ill go and try it...
[Touch Cruise ROM Development] imfloflo:
that's good tonight we try polaris

heating ^^great new functionnality
[Touch Cruise ROM Development] NeoS:
I noticed that the device was running more smooth too. Less hickups while building the screen, except for the all programs menu.
[Touch Cruise ROM Development] bally3:
nice constructive post imfloflo.. thank you. :rolleyes:
[Touch Cruise ROM Development] imfloflo:
i know it :) if i can help i'm in but without hard reset please :p
[Touch Cruise ROM Development] bally3:
NikMel dont know whether you can use this in your rom creation adventures...

http://xdaforums.com/showthread.php?t=411154
[Touch Cruise ROM Development] whitealien:
/signed for testing
[Touch Cruise ROM Development] rogro82:
Ok tried it... the call is working (the Guid stands for a Power-manageable display), BUT somehow when the device would normally turn off the backlight it does for a moment and switches back on again...

So instead of notifying it not to turn off it turns off and then notices it should come back on again. It will keep doing this so it has nothing to do with the driver but its a flaw elsewhere ( im not running any d3d apps just an app that sends the command ).

Will look on the internet if there is a solution somewhere that will fix the problem...
[Touch Cruise ROM Development] bally3:
I think Neos and Rogro answered this earlier, we will post a cab up when its finished for the CA site but we are still a long way off for even a public beta.

I wonder if rogro's had any more luck.. NuShrike not online..
[Touch Cruise ROM Development] rogro82:
yep found something... testing as we speak... ;)
[Touch Cruise ROM Development] bally3:
Since its quiet.. I'm going to go out on a limb here for a moment..

Yesterday.. inadvertently, NuShrike made a modest wish.

I think I've made my feelings known about NuShrike's involvement with this project. I'm honestly touched that he's taking an interest in our foray in 3D acceleration and the time he is unselfishly putting into helping us reach our goal because unlike the rest of us, not being a Polaris user himself he is the only one not looking to benefit from the creation of this driver.

So I make this appeal again, if any user knows someone who owns a Toshiba Portege G810, please dump this rom and for those of you who have PM'd me and posted on this thread their desire to help or enquired about the 2D development, please scour the web and ask around to see if you can get this rom.

I myself have pm'd every user on xda-dev who has posted on threads to owning one of these devices.

In the end, the development of the 2D driver will be of benefit to all of us anyway...
[Touch Cruise ROM Development] whitealien:
Ok.

Then I have solution for not flooding thread. How about using chat channel. Make public channel that every one can access, something like #xda_Polaris_3D. Like this anyone can join and say his thoughts as well as info can be exchanged much faster between active users (Nushrike, rogro82, Neos and others), so the development of this project will go faster too. You Bally could do some recap of development progress by posting in this thread 1-3 times a day. What you think?

Also any firefox user have free chat client, chatzilla.
[Touch Cruise ROM Development] bally3:
not a bad idea.. I'll put it to the rest of the dev team - thanks whitealien :)
[Touch Cruise ROM Development] rogro82:
Ok who wants to try out a lot of registry settings to try and make the device not entering sleep mode when it isnt supposed to??

Read this:

http://msdn.microsoft.com/en-us/library/aa910462.aspx

And my previous posts about the power management... you can find a lot of settings under the currentcontrolset...

I have changed so many settings my device has insomnia by now and will never go to sleep :D

Try to find out which settings are wrong and cause the screen not to stay on when it is supposed to...

another google hint:

EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1

Strange thing is my device still has the same turning off/on the display when it wants to enter sleep mode :rolleyes:
[Touch Cruise ROM Development] bally3:
testing purposes
[Touch Cruise ROM Development] imfloflo:
a chat like this chat abot androdi on polaris http://fr.gogloom.com/client2/index2?mainCHAT=1&network=FreeNode&channel=%23htc-linux or example no need client mirc
[Touch Cruise ROM Development] NikMel:
Event if I push the power button on top of the polaris it stays on when running htcca tools:confused:

You don't need to edit registry. The same settings are sett in gui mode of Power tool in Settings->System
[Touch Cruise ROM Development] rogro82:
http://www.eggheadcafe.com/forumarchives/windowsceplatbuilder/Jul2005/post23166881.asp

I did what was told in here and deleted the keys and now gwes is handling power management instead of the power manager... dont think this THE solution but the solution for the screen freezes are caused by this..

my device doesnt go into sleep mode anymore and until now i didnt get any switching on/off screen.

So my d3d apps are running for about 10 mins without any problems... So someone has to investigate the right registry settings so they can be adjusted by the final cab file... if the kaiser is also suffering this problem we can also notify them which setting it is...

If anyone want me to create an application that sets the same powerprofile as the driver does i will create and upload it for testing... It will make the same call NuShrike mentioned and it should make the backlight stay on without turning it off/on...
[Touch Cruise ROM Development] NikMel:
In my roms I have this entry DisableGwesPowerOff set to 1

From Microsoft:

@rogro82: Can you check yours?
[Touch Cruise ROM Development] rogro82:
To make GWES handle it it should be set to 0 but some other keys should be deleted... but this will change the powermanagement....

It will even give you more options in the powermanagement screen :rolleyes:
[Touch Cruise ROM Development] NikMel:
There is one issue!!!

BenchGLES_CE.exe is not running with the latest libgles_cm.dll:confused:
[Touch Cruise ROM Development] bally3:
Tis true.. but i couldnt get it to work before either!
[Touch Cruise ROM Development] pcarvalho:
just wanna say...

keep up the good work...

cause i'm already working in the port of touchflo3D to QVGA ;)

without your work it wouldn't be happening on my cruise :D

lets make magic happen :cool:
[Touch Cruise ROM Development] rogro82:
Ok this application makes the same call the libgles does when it creates a new video surface... It should make the backlight stay on but somehow it turns the screen off/on when it should go off...

Easiest way to try things is to set the turn backlight off to 10secs and run the app... if the backlight stays on your on the right track...

More info in previous posts... This is an issue that has nothing to do with the driver but since the d3d apps hang because of this issue it should be looked after...

In short:

The problem with the device hanging while running the 3d apps is not a driver issue... its something that always been wrong but comes up running the 3d apps because they cant go into sleep mode...

Thats why this call is in the libgles but it isnt working properly...

This is one of the main issues before we can even think about releasing this driver... Its not "our" problem but making sure the d3d apps run normally is so no way people will like it when we tell them their device got stuck because of a faulty registry setting ;)

Edit:

The names of my apps keep getting better as we progress :D
[Touch Cruise ROM Development] NikMel:
If I replace that dll it works!:)
[Touch Cruise ROM Development] NikMel:
@rogro82: as I say in my latest rom R5 the screen stays ON and there no is off/on think

@bally3: You've flashed my latest rom can you confirm the above sentence? Can you run the htcca tool on your polaris on battery for 10 minutes?
[Touch Cruise ROM Development] rogro82:
@nikmel ill give it a try... still didnt havent had any time to test it because of this issue. is your glbenchmark running faster then before??

I think we should compare your registry settings of the currentcontrolset power settings with the ones udk r0 uses...

There should be a difference i think.

You can test it running my app and setting the turn backlight off to about 10 secs.... if it doesnt turn off and doesnt turn on/off when it should turn off ur ok...
[Touch Cruise ROM Development] NikMel:
I thing glbenchmark is faster that by Neo

Left is my test and right is Neos
[Touch Cruise ROM Development] rogro82:
NikMel im just a plain old c# dev.... how can i install a nbh file :D

Need to do some more research on windows mobile things.... Been to busy at work to really focus on my phone..

Most of the the time i just run an executable with nice screens :D now i know how our customers feel like...
[Touch Cruise ROM Development] imfloflo:
you can install nbh files with the Polaris Custom RUU from udk http://xdaforums.com/showthread.php?t=376119

i just use it to install the new radio from the lastest french rom which increase the performance , maybe take a look to this rom http://xdaforums.com/showpost.php?p=2696372&postcount=10
[Touch Cruise ROM Development] bally3:
Thats great news pcarvalho! :)
[Touch Cruise ROM Development] bally3:
Rename it to POLAIMG.nbh

stick it in the root of your SDCARD

Soft reset and hold camera button to get to flash screen

Press power button to flash.

Thats it.. and its a good way of ensuring you can get your Polaris back from a semi-brick! :D
[Touch Cruise ROM Development] NikMel:
BTW: now I'm running Lights.exe for 23 minutes on battery and it still runs!

The only think is that the power button just dims and do not turn the screen off :rolleyes:
[Touch Cruise ROM Development] rogro82:
Thnx... got it to work ;)

Can anyone export the complete registry settings of the HKLM\SYSTEM\CurrentControlSet\Control\Power\ of a rom like udk or another cooked rom... The best would be Udk because thats the one which got me in to trouble ( no offence udk )... I think something is wrong with the states, but i guess they werent touched...
[Touch Cruise ROM Development] bally3:
sure can.. it works fine.. apart from d3demo.. it worked on my old rom but not on here.. which version of the libgles you use?
[Touch Cruise ROM Development] NikMel:
bally3 d3demo works here very well and fast!

I use polaris20080925_04 version.

Make sure that the directory of d3ddemo is empty:D:rolleyes:
[Touch Cruise ROM Development] rogro82:
Trying my app as we speak... will let u know if its working as its supposed to... ;)
[Touch Cruise ROM Development] NikMel:
You've flashed it ?

Thats fast :D:cool:
[Touch Cruise ROM Development] NikMel:
Well I'm off to find my bed :D.

Nice job you've done guys!!!
[Touch Cruise ROM Development] bally3:
Night NikMel :)

I'm up for a little while longer so I'll keep rogro company for the time being !