yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] rogro82:
Still doing some tests... my app still switches on/off but im checking if it affects the drawing of the d3d apps
[Touch Cruise ROM Development] bally3:
NuShrike, I see you're back on again mate.. :)
[Touch Cruise ROM Development] rogro82:
Dont push NuShrike that much.. he still has to read through 10 pages of garbage before he ends up here :D

At least their is no development work in the freezing screen issue... ( something he already thought.. :rolleyes: )
[Touch Cruise ROM Development] bally3:
true.. I'm not sure he should even bother reading through 10 pages of.. lol

but in fairness we have tried to keep this thread constructive bar the odd pointless requests..

I'm running tests on NikMels rom.. maybe its purely placebo.. but I still think this driver cooked-in works smoother.

did you get my post earlier of you guys deciding which tools/apps we should use as you know what you're talking about? I thought it would be better after what NuShrike said about Billboard not being optimised. It sure would have been nice to test this against Hergs No Thrills TouchFlo as it shows the fps constantly but it uses its own libgles and it didnt seem to work for me when I removed it.
[Touch Cruise ROM Development] rogro82:
Im also running tests on the new rom and i havent had my device freeze ones... I think its something rom/registry related that will take too much time to fix.

If everyone is happy with the results so far i wouldnt mind if there would be a beta cab for people to try... Thats just my opinion ill let others decide ;)

Edit:

Remember udk optimized his rom for software acceleration so we dont know what he did to it and we cant rule everything out to keep it working on every rom someone installs on.. Its up to the cookers to make sure everything works like it has to... NikMel's rom shows no problems and thats a "stock" and clean rom besides the needed adjustments

Im sticking to this rom to get it optimized before switching back to anything else that could cause problems and will only take take to figure things out...
[Touch Cruise ROM Development] bally3:
I'm afraid we probably wont find out what differences are if any in the other wm6.1 roms out there. What we learnt is what we posted on here.

I'm also sticking with NikMels rom, its clean and also NikMel has been more than a loyal friend on this development.

With regard to the public beta, are you happy that there is no more we can do to improve the performance then?
[Touch Cruise ROM Development] rogro82:
Nope... ;)

I just think it keeps people off our back... but we shouldnt release it in this thread like i mentioned before.

There should be another thread for the public so they can tell their problems etc and keep this thread clean for development use.

Theres one thing i want for this driver and that is usability... so 3d is nice and ofcourse a real head turner but we should also focus on some other things... if you want to keep this driver alive it should also be of good use in daily life.

Using the Spb benchmarking i noticed the drivers used in the udk rom scored way better on the dib bitblt section. maybe he can contribute to this driver so we can work on better usability.

If he doesnt want to/cant we should look more into the differences...
[Touch Cruise ROM Development] bally3:
I'd still like to be happy that we've covered everything and done all we can with the driver first. Also I want to talk to Neos about adding a disclaimer to the cab and force people to accept the t & c before they install ust be on the safe side.

I'll speak to the others about this and sort it once we decide on the beta release.

Totally agree, but this goes back to the argument of the 2d driver development in terms of every day useability its frame rates on video playback and games (which there arent that many of to take advantage of the driver).

So far my tests show that even though the hardware acceleration now allows me to play movies with direct draw in Coreplayer, the omnio driver is still much smoother and gives better framerates.

I get 8-10fps on Billboard.exe compared to 2.38 - 2.5fps hardware.
[Touch Cruise ROM Development] rogro82:
I had a lil much to drink so dont mind anything i say :D

I was thinking about the following:

We are all after the same thing... make the polaris/other devices work at its best. but instead we all work apart and create groups... If we really want to make this work we need to share our work with people who can make people benefit of it.

NuShrike allready helped us a ALOT.... but i think/hope there are more people out there that can help us achieve our only goal, and thats not just some fancy 3d demo's running.... the actual goal should be to make our devices kick the crap out of every iphone clo(w)n ever made :D

So if they dont come to us maybe we should go to them... lets just ask udk or someone else to implement our findings into their roms if they feel like it. This can only help it grow and will bring more support and a lot more people putting effort into it....

So what im trying to say is.... we dont need to be selfish on this case.. we need more help ( not just people testing and developing, but also people who wants to implement it, what good is it if its never used hey )...

Everyone involved need to think about this and give their opinion so we decide what to do next...

And now im off to bed ;)

Sleep well
[Touch Cruise ROM Development] VizagDude:
No one can put it any better than what you just did in words. Thats why XDA is so popular. I am sure there is atleast one member from almost every country of the world and we are all here to contribute our part. Some are good at developing, some are good at design and many more are interested in taking the risk of flashing the ROMs on their devices at their own risk and report bugs for improvement.

I really like the part where you mentioned iPhone clowns... :) No offence though. I myself was a 1st Gen iPhone user (Jailbroke, activated and unlocked on T-Mobile USA).
[Touch Cruise ROM Development] bally3:
yes I do agree with you. Well talk more tomorrow.

Night rogro and thanks again for the help.

I'm off to bed too so night all :)
[Touch Cruise ROM Development] SomethingWicked:
@neos: if its possible, do it this way: open winzip on your pc, then drag the exe to it and drop it in the window. works for me sometimes :)
[Touch Cruise ROM Development] NeoS:
I did a fast review of the pages for tonite.

Here's my thoughts about the development and getting help from others:

it's good to have more people work on it. But they need to have proven themselves in the past (like NuShrike or chainfire in this case) or should be able to put something out there instead of just throwing ideas out. If you get people on your project just so they can be the first to have the drive, you're going to lose your project and all your hard work to some poser.

Again, like rogro said, we need help from the chefs. Once they use our driver, development of nice stuff will come. Manila comes to mind.

But, before we start distributing it we should DEFINITELY make sure everything works for the full 100%. On every Polaris wm 6.1 rom. But i guess y'all know that.

About the 2D driver: Yes, it would be awesome if we could implement it too. But do we have the means to? Wouldn't it be better to start another thread in search for the 2D driver instead of adding it here?

And last but not least: The team consists of 5 people currently. You don't want a team that's too big. You need to coordinate people. And Bally3's doing a great job at that. But if we get too much chatter on the channel, we'll eventually start losing important info. You don't want that.

End of rant. (and time for bed. Look at the time...)
[Touch Cruise ROM Development] NuShrike:
Sorry, I haven't programmed in D3D, but what would you like to do with that code? I'm guessing that we could use it as a sample test 3D app.

I'm currently trying to figure out the problems with my 3D app. I've already confirmed the 2nd texture unit (our OpenGL-ES supports 2) might be broken for Kaiser, Diamond, and Touch Pro. It's kinda important when I want to do dot3 normal mapping.

Broken in GPU/driver, my code, don't know.
[Touch Cruise ROM Development] asa51n:
To extract the NHB file from an exe is easy. Just run it and when the first screen appears saying connect the phone blah blah blah, open explorer and go to your temp folder, usually in your C:\Documents and Settings\"COMP NAME"\Local Settings\Temp.

Hope it helps, Keep up the great wook guys!!!... :D
[Touch Cruise ROM Development] pananza:
I haven't seen anyone else commenting this test of NikMel. It's not just a bit faster, but its 10 times faster on several of the tests.

What exactly did NikMel and Neos test on and with?
[Touch Cruise ROM Development] bally3:
NikMel is runing a clean stock rom with the driver cooked in.

Neos is using UDK R0.

Heres mine with NikMels rom:

Can someone put them by side like NikMel did and put names on the top with roms used please?
[Touch Cruise ROM Development] bally3:
We're all using GLBenchmark Community version - CM version as far as I know.
[Touch Cruise ROM Development] pananza:
I've taken the values and entered into Excel and marked the best scores where there are any difference.
[Touch Cruise ROM Development] bally3:
Thanks Pananza, thats great - just what was needed! :)

interesting.. my rom scored higher on fill rates.. but NikMel scored higher with lights etc.

If I remember correctly, NikMel ran the keep awake program when he ran this.. I'm wondering whether thats where mine slowed down... mm.. I'll test further and post my results.. if its not the case then I'll post my reg settings and ask NikMel to do same and compare them.
[Touch Cruise ROM Development] NikMel:
Hello guys

As I say before I just flashed my rom R5 and run the benchmark and lights.exe without keep awake program
[Touch Cruise ROM Development] bally3:
Hi NikMel ;)

Then the only thing thats different is I've loaded all my proggies back on (Manilla 2D etc) and the reg tweaks.

I've changed BPP: 32

Resolution: 480 x 640

GlyphCache: 32768

I'm running the test again activesynced... which is nearly finished...
[Touch Cruise ROM Development] NeoS:
Wow. Nikmel's score is way better. If you look at my video for GLBenchmark, you'll see that the device has a hard time to display lighting. How was it on your bench Nikmel?
[Touch Cruise ROM Development] NikMel:
This is test I made just now and I'll put video online soon
[Touch Cruise ROM Development] NeoS:
The Imate rom Bally posted can be extracted, but it will take me a hell of a long time, since i don't know what i'm doing. It's in mbn format.

And Nikmel, what the hell did you do to get such high results? Give your Polaris Red Bull or something?
[Touch Cruise ROM Development] NikMel:
Just flash R5 rom and you will see it :rolleyes:
[Touch Cruise ROM Development] NeoS:
Err.. I could. But i still use my device in normal day life and i love the manila 2d interface... Oh well. Good way to test out my cab. Or did you already put those files in?
[Touch Cruise ROM Development] NikMel:
It's a rom with some htc stock apps
[Touch Cruise ROM Development] NeoS:
If you've changed any files or registry settings i'd like to know. I can put them in the driver cab. The point is, we want everyone to use their own roms with these drivers. So flashing your rom would give me the results, but not everyone wants a stock rom these days if you know what i mean. ;)
[Touch Cruise ROM Development] bally3:
NikMel, are you able to add apps into your rom? I wanted a few apps that I have to reload at every hard reset to be cooked in.. :

Total Commander

feexplorer

SJ 3D Apps (Billboard etc)

HTCorg apps (lights d3demo etc)

PHMregedit

GLBenchmark CM

psShutXP

Manila 2D with Full youtube player

Would you be able to do this? I can provide you with all the cabs. I was going to do an SDAutorun but theres another thing worth testing.. how benchmarks are affected by a clean rom and a fully loaded one.

Neos: Manilla 2D is in cab form with all the trimmings and works perfectly as far as I can see (its also in yummy black!)

Any chance of being able to do this NikMel? (prettty pplllleaaase!) :p
[Touch Cruise ROM Development] bally3:
It aint stock no more Neos.. its on steroids.. ! :D
[Touch Cruise ROM Development] NeoS:
Yeah. It's like dragonball Z, it has hidden potential. (And spikey gold hair in the process.)

We're reaching a stage where we can't improve much on speed i guess. Like NuShrike stated earlier: MY benchmarks were faster than the Diamond in some places. Now look what you did Nikmel! Shame on you for killing the Diamond and it's "glorious" 3D! Makes all the Diamond users feel ****ty now... aw.
[Touch Cruise ROM Development] bally3:
I've posted some thoughts to the group.. have a read and tell me what you think - thanks.
[Touch Cruise ROM Development] NikMel:
This is my glbenchmark http://nl.youtube.com/watch?v=8_DsX-aGYYA

It's on precessing so will take some time...
[Touch Cruise ROM Development] rogro82:
NikMel the 2nd movies seams a lot faster using your rom... im gonna stick with it because it also solved the suspend issue for me.

Maybe an idea to get registry dumps of both your rom and udk's and compare the [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power] and all sub settings..

Especialy the keys under State and check if the subkeys "{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}" are the same and existing where they should and also check the bkl1: setting for each state...
[Touch Cruise ROM Development] NeoS:
I'm still curious though. Could it be possible that cooking the drivers in a ROM will significantly improve performance? Is that what happened in your benchmark Nikmel? Because if that's the case, making a cabfile doesn't seem logical. You'd rather flash a custom ROM with the drivers.

Oh and team, go to first post and go to the dev group link there. Join the group so we can discuss development and all related stuff there without posts from other people in between. (not that we don't appreciate any feedback from the community)
[Touch Cruise ROM Development] NeoS:
Again: requet to all users: We still need a dump from either the imate 8502 or the toshiba protege 810. Both seem to use the msm7200 chipset.

Portégé G810 Features

Platform: Windows Mobile 6.1 Professional

Processor : Qualcomm MSM7200 (400 MHz)

Band : 850/900/1800/1900 for GSM/GPRS/EDGE 850/1900/2100

UMTS/HSDPA (3.6 Mbps)/HSUPA (2 Mbps)

Navigation : Built-in GPS & A-GPS

Interface : Bluetooth v2.0, USB v2.0, WiFi 802.11 b/g, FM Radio with RDS

Size : 58 x110 x 14 mm

Weight : 120 g

Display : QVGA (320 x 240), 65K colors, TFT, 2.83"

Camera : 3 megapixel, autofocus

Memory : 256 MB ROM / 128 MB RAM, micro SD slot up to 4 GB

Battery : 1,530 mAh

Standby: up to 200 hours

Talktjme: up to 4hours

So please, if anyone can find roms from those phones, let us know. I have found one for the imte 8502, but i can't seem to extract it. If anyone can, again, let us know.
[Touch Cruise ROM Development] bally3:
(Gets the feeling he's banged on about this for a while now and no-one seemed to listen.. wheres the headbanging smilie..?)
[Touch Cruise ROM Development] NeoS:
lol. I know. But it's not confirmed though. So don't slam your chest just yet. ;)
[Touch Cruise ROM Development] NikMel:
NeoS2007 I don't have udk's rom and you do. Can you compare the content of my rom to that of udk?

I'm sure there will be some differences.
[Touch Cruise ROM Development] NeoS:
No, i can't. Simply because udK locked his rom. I can't properly compare the differences without a full dump of the rom. I could try to find some differences manually.

However, if you'd be able to add the packages like Bally3 requested, we'd be able to see if that has any impact on the performance.

Another thing: I noticed that my device doesn't clear it's memory properly. After a soft reset the device uses about 50%. I ran DooM, closed it and it was stuck at 69%! I wonder if it's the same with other applications.
[Touch Cruise ROM Development] w04g005:
There is an 6.1 update for imate 8502!! it's in this forum:

http://xdaforums.com/showpost.php?p=2395252&postcount=1

greetz
[Touch Cruise ROM Development] NeoS:
I know. But it needs to be extracted. We need those files in the rom itself. So if anyone is able to extract those system files, we'd might be able to improve overall graphics in stead of only 3D.
[Touch Cruise ROM Development] NuShrike:
Nikmel's 10x performance is normal and par with the Kaiser (high 2 million to low 3 million tris/sec) when the devices aren't running in low-power mode.

Also, anything with a few million triangles in the GLBenchmark usually means failed tests. Not that the MSM7500 platform can't do a few million triangles per sec (the specification says closer to 4 million), it's just that here, GLBenchmark is failing faster. :D

I can understand it failing the lights tests, but it's failing the color/textured triangles tests too because the display stays black. I think GLBenchmark is bugged here and never got fixed.
[Touch Cruise ROM Development] NeoS:
Aha. Well, i'll try some 3D games from the microsoft windows mobile site. See what those do on my device.

Sweet! Guitar Hero Mobile works like a charm. Don't realy know if it's 3D though, so i'm gonna test some more. (and having fun at that ;))
[Touch Cruise ROM Development] pananza:
Guitar Hero works fine on a stock VM rom without any accelleration too :(
[Touch Cruise ROM Development] NeoS:
Crap. Oh well. as long as i've enjoyed myself. lol
[Touch Cruise ROM Development] bally3:
Been testing the new rom from NikMel.. I've had a few thoughts from what NuShrike said about the d3d usage and the 2D if we get it going...

Now it seems to me that the 3D driver is good in certain areas and doesnt make much difference for 2D apps and re every day phone use.

What NuShrike said about when we get the 2D ddi file we'll have to merge it with the existing ddi etc..

That got me thinking about the two ddi scenario... and also the current situation.. my thoughts are this.. and they're only thoughts remember..

What if we isolate the ver 3.28 ddi to only get called when its needed and invoke the omnio driver for the rest of the time?

It would probably mean having a renamed ddi file as well as the stock one.. would that work? I'm also thinking about the heat issue which I'm still looking at, but it seems that a better solution would be only to use the hardware acceleration (from now I'll call it "HardAx" for short.. )

when its needed... any thoughts?
[Touch Cruise ROM Development] bally3:
We;ve seen that one w04g005, Neos and I both downloaded it.. I think Neos managed to extract the file as well but its not an nbh... I cant even extract it on pissta.. I mean vista.. :o
[Touch Cruise ROM Development] NeoS:
Interesting idea. But i think the system can only handle one ddi at a time. We should relay this to rogro or NuShrike. If ddi.dll is used for both 2D and 3D graphics, we should be able to get something if we get the ddi.dll from the omnia, right?
[Touch Cruise ROM Development] NeoS:
It's an mbn file. So if you know how to extract that, we're gold.
[Touch Cruise ROM Development] bally3:
I'm googling it now.. must be able to extract it...how exactly did you extract it? did you do the install method or winzip - winzip method didnt work for me and the .exe isnt vista compatible.
[Touch Cruise ROM Development] NeoS:
The install trick. It makes perfect sense, windows needs to have the files in a temporary folder to be able to access it. Problem is: I've got it on my desktop computer (winXP) and i'm on my laptop now. (Vista x64) And i'm not home for about... 6 hours or so.

But someone else must be able to extract it. it's not that hard. Just go to c:\temp once you've started the .exe and it asks you to connect your device. The mbn file is there. ;)
[Touch Cruise ROM Development] bally3:
durn it.. I'll have to wait until someone extracts it or you get home.. meantime... I'll see what this mbn file needs for extraction :confused:

[edit] - you might just get away with renaming it to .nbh it looks like.. have a go.. extract.. dont flash! lol

ps. ...we've been stickied! :)
[Touch Cruise ROM Development] pananza:
Havent tested since I dont have the mbn file. But here's a promising tool: http://forums.se-nse.net/index.php?showtopic=6229
[Touch Cruise ROM Development] bally3:
Looks good.. neos get back soon so we can try it mate :)

.. Found these apps on NuShrike's thread, they show over 100 fps.. !!

If you're still running without the hardax 3d.. can you test and tell me what you get Pananza?

thanks
[Touch Cruise ROM Development] pananza:
Cannot run program: "Either is not signed or a required component is missing". I have signing off in Advanced Config. Any ideas?
[Touch Cruise ROM Development] NeoS:
Could someone look into that tool? It might work.

I've been looking at some videos from the toshiba g810. The scrolling in 2D is phenomenal. I'd say it's as smooth as the iphone. So... we need that!
[Touch Cruise ROM Development] bally3:
All I did was extract the resources folder and the .exe into a folder and placed in Device (root). Should work..?

.exe should sit in the folder but outside of the resources folder - so in the same folder as resources.
[Touch Cruise ROM Development] pananza:
Copied libgles_cm.dll and some other files to \windows

The the app starts, but has the same bug as the others (don't update unless menu is touched, this causes the program to exit).

Running with the app that draws to small blue pixels to force a redraw I get 106 fps.

- Stock udK Syrius R0

- Omnia driver (LocalHook points to omnia dll file)

- Just copied libgles files to Windows

- Hangs after about 30 seconds
[Touch Cruise ROM Development] sepahewe:
Sorry, but I googled them yesterday and tried to unpack the mbh, but it complains on wrong header, even with the header checks turned off. My guess is that you have different types of mbh-files and the extractor for SE doesn't work in this.

Also if you check the heades hex-bytes it doesn't say BA BE :(

The SE Extractor tool was specifically designed for a few SE models. If I understood the discussions around the mbh format correctly, it seems that mbh is a format that is raw to the flash it is going to be programmed into, and I guess the SE phones use a different type flash the the HTC phones. I even followed a few leads thad landed me in a Russion group that claimed to have tools, but theirs too only worked for SE.

After have followed this thread from the start I thought I should try to help out with something, too bad it was in vain....
[Touch Cruise ROM Development] bally3:
Dont be sorry friend! Its good that you put so much effort into it.. thank you! :)

mmm.. maybe that mbh isnt the way to go then.. strange.. the imate is a WM phone though.. might be the reason why there arent any cooked roms available for it.. oh well.. lets carry on looking for the Toshiba g810. Incidently there are a number of other phones we can try..

http://pdadb.net/index.php?m=pdamaster&posted=1&cpu=a7200

granted some of these are just rebranded kaisers..
[Touch Cruise ROM Development] bally3:
.

Well that at least points to the fact that the 3d hardware is working as it should.. the testapp here works flawlessly.

hmm.. just had cause to hard reset.. (again) and decided to try the tests again and noticed the frame rate drops without my tweaks.. I'm getting 89-90fps ... where I was getting 100+.

Interesting...
[Touch Cruise ROM Development] NikMel:
Screen dump of that tool
[Touch Cruise ROM Development] bally3:
hey nikmel.. have you started on that rom yet? not rushing you mate.. just wanted to know whether we could get net compact 3.5 in there please.. ?

btw.. Jesse is working on some artwork for you.. ;)

http://rapidshare.com/files/74438597/NETCFv35.zip
[Touch Cruise ROM Development] bally3:
Just testing with nc 3.5 according to the thread post:

This may yiield even better performances.. though I think it will be even better if 2.0 is replaced with 3.5 and cooked in.