yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] speed_pour:
Just a small thought, but in the interim, wouldn't it be possible to build a custom ddi.dll that exposes all of the necessary methods, then within each method, route the call to the correct ddi (ie. ddi_2d.dll and ddi_3d.dll for the omnia and your drivers respectively).

Maybe I'm off, I'm not sure if some method calls are used by both and dependent on context (might be possible to creatively manage that also, but definitely complicated if this is an issue). Is it required that the DDI be signed?

Obviously this drains a little bit of performance, but it's better than sacrificing 2d for 3d or vice versa. As a bonus, I would expect that this trick would also make it a lot easier to do some testing of new drivers (the 810 for example) as they are released and possibly be useful for some application testing/development.
[Touch Cruise ROM Development] SomethingWicked:
No offense intended, but... Might be a good idea for you to save you a few minutes at flash time, but bad idea for the rest of us who don't use those apps. My two cents worth: PLEASE don't include a lot of extra software that can be added after flashing... :)
[Touch Cruise ROM Development] SomethingWicked:
Ok guys, sorry to report that the gif animator I downloaded blows up when I try to save the new animation. Crap!! And I only have 2 half days off, so I don't have time this weekend to try to fix it.

The animation I was trying to make was a little cheesy :eek:, but it got the point across: it started with a few flashes of a lightning strike, then "Unleash the Power!" flashing from red to white like there was a lightning strike in front of it, reflecting off of it. Then another image would come on a few sec's later and give the title and credits of the rom. You like???

ps. please forgive the cheesiness... the thought is still in rough draft stage... as a matter of fact, the lightning strike isn't even displaying correctly on the beige background... >sigh<
[Touch Cruise ROM Development] bally3:
Hi JesseW, this is just for testing purposes.. for the multiple hard resets that take you back to the beginning again.. very time consuming.. also we need to test whether performance is negated noticeably when fully loaded or not.

With regard to the animation.. Like the idea of the lightning.. definitely would make people sit up and notice.. I'm kind of warm the idea.. especially the text.. could the text be animated?
[Touch Cruise ROM Development] bally3:
If it can work that way, it would be great - but that may require development at a level that we dont have right now I think. I'll let Rogro82 or NuShrike come in on this one as they are more qualified to answer this.
[Touch Cruise ROM Development] NeoS:
I can answer this. The ddi.dll needs to be signed. So you would never be able to do something like that.
[Touch Cruise ROM Development] bally3:
Thanks Neos :)

ps. PM'd you and also updates on group.
[Touch Cruise ROM Development] NeoS:
Did we ever test the cabfile on a wm6.0 device? I'm curious to see it that would work...
[Touch Cruise ROM Development] NeoS:
updated group. Also added the files I have in a zipfile. See if those are the latest.
[Touch Cruise ROM Development] w04g005:
Hey guys,

I'm searching now for 4 days but i can't find a G810 ROM.

NOthing on russian forums, nothing on chinese forums,.....

I called toshiba in said i have deleted a file in the windows folder and they shall send me the firmware. they said i should go to the toshiba support store...arghh

greetz
[Touch Cruise ROM Development] NeoS:
lol. Nice action there. Bummer they didn't fall for that.

Anyway, thanks for your help so far. It's appreciated.
[Touch Cruise ROM Development] itje:
currently testing on my new rom (not released)

Old htc drivers:

getting 2.75 to 3.20 fps with d3ddemo

(no reg edits made, just polaris drivers)

Edit: Allright im cooking the new drivers with a few regchanges, Ill report if any changes are made

edit 2: wow...not mutch more to say then ..wow

In the first test with default drivers, the "cube" in d3ddemo is barly spinning, with the cooked new drivers, its spinning out of control..lol

Edit 3:

All tests passed on hardware accelaration.

added GLBenchmark for those who needs to run benchmarking

edit:

tested my rom with SPB Benchmark:
[Touch Cruise ROM Development] bally3:
Thats great itje! didnt think it would get put through its paces so quickly so thank you very much for this!
[Touch Cruise ROM Development] itje:
no thanks to me, its all you guys :)

Im gonna experiment with ddi and other drivers in the next few days with my rom. I will let you guys know if there is any improvement.

But as I do see great diffrence with the new drivers on many ereas, I belive the performance can be boosted even more.

Im no expert in theese things, but I will see what I can do myself.

thx

cheers
[Touch Cruise ROM Development] bally3:
WOW! itje has already posted up a beta with the new drivers and he's very happy with the performance :)

That was quick.. I only sent the drivers this morning! :eek:
[Touch Cruise ROM Development] itje:
had to see how it was cooking them into a rom.

and yes, this is great stuff for our device.
[Touch Cruise ROM Development] rogro82:
Nice work... now lets see what the response will be :)
[Touch Cruise ROM Development] bally3:
My respects to you Rogro.. soo... what so we do next....? :rolleyes:
[Touch Cruise ROM Development] bally3:
Got this from itje's thread.. Rogro you mentioned this before didnt you?
[Touch Cruise ROM Development] rogro82:
yep and thats what im investigating as we speak ;)

Can anyone confirm the ddi the new roms are using is 3.13?
[Touch Cruise ROM Development] bally3:
I can confirm it is.
[Touch Cruise ROM Development] bally3:
Some light reading agian:

http://msdn.microsoft.com/en-us/library/ms532278(VS.85).aspx
[Touch Cruise ROM Development] NeoS:
Hey guys. So we're public huh? :) Cool.

We need to investigate that slowdown. Might Nikmel's ROM help with this?
[Touch Cruise ROM Development] rogro82:
The performance of the dib bitblt seems/is ddi dependand because running a new blank htc rom gives the same result as say udk ones in spb benchmarking... When you copy 3.28 on it dib bitblt gets slower..

So i took a stock rom and installed our base file.... a no go because of a systemdeviceexception

Strange thing is that i copied the 3.13 ddi and checked to see if it has all the needs for acceleration and it does.

it imports disptools and exports the screenupdatebycopy/flip... NuShrike do you know of anything else that could be wrong? and the screenupdatebycopy is accessing the ddi_disp2d_update, just like the 3.28 does.
[Touch Cruise ROM Development] imfloflo:
The triangle test work but unable to close it with the 0.03 cab
[Touch Cruise ROM Development] itje:
when I added the files from you guys, I noticed that the ddi you supplied was slightly larger then the one in the official wwe rom.

also the one I got from you has fileversion 3.28

and the one in the official is 3.13
[Touch Cruise ROM Development] NeoS:
Correct. This ddi was found most stable and supported our testing applications best.

We might need to find more versions of ddi.dll so we can maybe combine them. Devices like Toshiba's g810 comes to mind. As long as it has the MSM7200 chipset.
[Touch Cruise ROM Development] itje:
allright. can I ask what rom you extracted the ddi.dll v3.28?
[Touch Cruise ROM Development] bally3:
Kaiser stock wm6.1 rom
[Touch Cruise ROM Development] bally3:
have a look at these benchmarks.. taking note that NuShrike said yesterday that the 3mill+ triangles in NikMels test denoted a failure.

See what you think...
[Touch Cruise ROM Development] itje:
nice.

mm, and you have tested with the 3.13 when cooking? Im only asking to see if I might skip a few steps of my own testing
[Touch Cruise ROM Development] bally3:
3.13 doesnt work with the current driver set.

From what Rogro is saying it sounds like its all there in 3.13 - as long as changes to 3.13 dont need to be made - its a signed dll file - changes to other files to take advantage of the routines in 3.13 may show some marked improvement as the ddi was written for the Polaris. But this of course is code level stuff and I wont even pretend to know where to start! ;)
[Touch Cruise ROM Development] NeoS:
updated group post.
[Touch Cruise ROM Development] ouioui01:
but, you're a developer, as you wrote in your first post...;-)

cheers, & sorry for my english ;-))
[Touch Cruise ROM Development] bally3:
Hmm.. I suppose its down to your interpretation.. developer often means porgrammer I suppose.. but it should really mean one who develops or helps to develop as part of a team as in this case.. but if it offends we shall remove... :rolleyes:]

[edit] Actually you'll find it says "Development" so I think I'll keep it ;)
[Touch Cruise ROM Development] rogro82:
NuShrike i compared imports and exports of the 2 ddi's ive got ( 3.13 and 3.28 ) only thing that is different is that the 3.13 misses 3 imports from coredll

These are:

SetFilePointer

ReadFile

CreateFileW

Can this be the problem for the driver not running on the 3.13 ddi, which i think is better then the 3.28 we are using at the moment.
[Touch Cruise ROM Development] bally3:
Are you saying the two files are identical but for these 3 imports?
[Touch Cruise ROM Development] NeoS:
I remember NuShrike saying these files are signed. So how are you going to change any code in them? Doesn't that mean you'd have to re-sign them?
[Touch Cruise ROM Development] speed_pour:
If you read through the thread (understandable if you didn't, it grows several pages daily), you'll see that the references of scrolling are related to a bug where the entire screen spins like a slot machine any time the 3d drivers were invoked. It has nothing to do with 2d performance or scrolling in the context of TouchFlo. Assuming the goals remain the same, they are trying to get a hold of a driver that may also improve the 2d performance, but at this time it appears there's been no luck in gaining access to it.

I'm suspect, based on most of what I've read, if you're not going to make use of 3d at all, your best bet should be the omnia driver.
[Touch Cruise ROM Development] SomethingWicked:
What about the Sony Xperia X1? It uses the qualcom msm7200, but at 528 mhz instead of 400 like in our units. Could the driver files in this phone hold our key? There ARE pre-production units out there... :)
[Touch Cruise ROM Development] voxel.:
if i understand, it's the same file (http://xdaforums.com/showthread.php?t=416474) that this link : http://xdaforums.com/showpost.php?p=2651168&postcount=70

i have already put the driver...:o
[Touch Cruise ROM Development] imfloflo:
wait for Android :p

or just install the Syrius R0 from uDK and all 'll be good :)
[Touch Cruise ROM Development] whitealien:
Benchmarks

With syrius driver:

Gxmark 1529 pts

vsbenchmark 2007: 1695 pts

With D3DMXSc50PB.dll:

Gxmark 1558 pts

vsbenchmark 2007: 1684 pts

So in general difference is so small that it can be ignored. Also I did not noticed any visual difference neither under 3D nor 2D. I guess that till we wont have hardware accelerated 3D graphics there wont be any big difference noticeable.

More over with this dll video playback is very slow and PocketMVP hangs device.
[Touch Cruise ROM Development] dwaradzyn:
Do not confuse accelerated ddi/gapi with accelerated d3d/opengl. These benchmarks test gapi speed which is not related to 3d driver. To test 3d speed you should use something like glbenchmark.
[Touch Cruise ROM Development] SomethingWicked:
I just tried the omnia driver with udk r8 and manila 2d. it actually slowed my system down so much it was noticable under touchflo 2d, tcpmp and opera. Am i missing something???

Since 2d rendering and video playback are the important issues for me, i put it back to htc_d3dm.dll ... :(

Even r8 for some reason doesnt seem to have video playback as fast as r7 did. I'm confused...
[Touch Cruise ROM Development] imfloflo:
Why don't just flash to R0 syrius ? i don't understand .
[Touch Cruise ROM Development] bally3:
Hello everyone!

I see there has been some testing going on with the dll's.

Dwaradzyne's advice about the GLBenchmark is worthy of note seeing as he's knowledgeable on this matter, on that subject can you tell us what specific tests to run on GLBenchmark?

It would help if someone can run these tests and post the results/screenshots.

I take it you're talking about Kishontis GLBenchmark cab?
[Touch Cruise ROM Development] bally3:
A note to all users:

I understand the frustration and impatience everyone feel and wanting to try any new solution. But please be patient and understand that we are only gathering information and testing technologies to better our understanding of the 3D issue. As such, if a user posts a file or submits any information that can assist in this venture you should NOT treat it as a tried and tested solution.

Feel free to help out in testing and post your results but I would appreciate if we do not flood this thread with the usual "why doesnt it work?" posts as - and I repeat again -

THESE ARE NOT TRIED AND TESTED SOLUTIONS.

If a solution is found, I am sure we will be the first to shout it from the rooftops ;)
[Touch Cruise ROM Development] bally3:
To continue then...

As we can see in this thread the software acceleration solution is a divisive one.

On one hand we have the d3dmref.dll used in swtos rom which showed some improvement even to the point of moving the cylinder in lights and the cube in the D3Demo - the first time we actually saw these demos moving - but the frame rate was very low.

UDK's Syrius rom also seems to show some improvement and according to our learned friend Nikmel, the omnio dll was included in both roms. (can anyone run lights on R0 and confirm which dll its using?)

As has been posted here by Dwaradzyne, software acceleration has limited use in practical terms for games and 3D applications unless its specifically designed to utilise it.
[Touch Cruise ROM Development] bally3:
I am STILL a big believer in the hardware acceleration method and seeing the video memory initialising in the files uploaded by NikMel - an earlier release of the htcclassaction driver - was a big confidence boost that it can be done.

Nikmel talks about patching the D3DMXSc50PB.dll file with the htcclassaction driver - if I understood that correctly - so thats one avenue we can explore.

I have been comparing the Kaiser cab files to Nikmels and find that only the files dated 25/07/08 make a difference and when you swap these files into windows folder after installing the newer kaiser cab, the video initialising works without the rest of the files being swapped.

These files are:

ahi2dati.dll

ahi2dati_dm.dll

wce_pmeF.ll

libgles_cm.dll

View attachment dlls.zip

Anyone able to insert these files into the kaiser cab to try out a direct install?
[Touch Cruise ROM Development] w04g005:
One month ago i installed the omnia drivers and then the htcca drivers. i was able to start the cube...3dtext... apps. but there was no hardware acceleration. when i opened the start menu the cube and the triangle moved.

I think we have to wait for the offical HTC rom upgrade.

i hope it contains a the missing dll file (like in the kaiser update)
[Touch Cruise ROM Development] w04g005:
Yes i would be able... if you tell me which kaiser files you mean?

where to download?
[Touch Cruise ROM Development] bally3:
The files are here: View attachment dlls.zip

and the cab here: View attachment HTC-CA-Kaiser-Drivers.cab

Just overwrite the files in the cab with the dlls if you would.

Thanks w04g005 :)
[Touch Cruise ROM Development] w04g005:
i cannot extract the msm_clk.dll this file seems to be corrupted
[Touch Cruise ROM Development] bally3:
hmm.. this is the "BIG" mystery... according to the rom chefs, the WM6.1 IS the official release..

I am still unsure what the difference is going to be.. are we due an improved ddi.dll file which is post version 3.0?

These are the questions nobody seems to have the answers to and what made UDK's rom impending rom release such a fury of speculation from "udk has cracked the hardware acceleration issue" to "maybe he works for htc and has developed a solution". That now seems to be proven to be mythical as most of the improvements we see in the current roms are down to software acceleration from the dll's.. hooked to the ddi.dll file.
[Touch Cruise ROM Development] bally3:
try this one:

View attachment msm_clk.zip
[Touch Cruise ROM Development] NikMel:
the ddi.dll in my testing rom and the ddi.dll in udk's rom are the same and are coming from RUU_Polaris_O2_DE_3.13.207.0_radio_sign_25.85.30.07_1.59.42.15_Ship.

This file is an original one
[Touch Cruise ROM Development] NikMel:
yes!

msm_clk.dll is corrupted in the latest cab file from htcclas...
[Touch Cruise ROM Development] bally3:
but just swapping this file for yours didnt make any difference when I tried it - I tried each file individually after resets and only found that the files I mentioned made a difference to the access error from the newer kaiser cab.
[Touch Cruise ROM Development] NeoS:
Ks20 wm 6.1 files

I've found this thread: http://xdaforums.com/showthread.php?t=408280 for the KS20, from which we used some components.

I've extracted the rom and found some files we could use for testing.

You name it, i'll upload it. Found an interesting gdiplus.dll. Did we have that already?

Here are a few files in advance. ;) I've taken the files which seem interesting for Rogro and NuShrike to have a look at.
[Touch Cruise ROM Development] NuShrike:
Please ul a copy of 3.13 DDI and the matching disptools.dll for me, or point to the post where it was previously ul'd.

Was 3.13's DDB BitBlt's 5xxx% improved like 3.28's? Please list the complete numbers for 3.13 and 3.28 for comparison (DDB, DIB, etc), if you can, so I can see.

Rogro btw, the screen blinking on/off when trying to power-off also happens in Opera for Windows Mobile (not the java Opera Mobile). So, power-off issue isn't just a 3D driver problem.

Also, it's more appropriate to say the screen was rolling, than scrolling, as when you had to manually adjust the v-roll in old TVs.

Neither the Omnia driver, nor the ATI 3D drivers have any effect on everyday 2D for ANY app, unfortunately.
[Touch Cruise ROM Development] NeoS:
Thanks for clearing that up for all te readers here.

I will see if i can find the 3.13 somewhere in this thread. I know i've posted it as ddi2.dll. Finding the corresponding disptools poses a bigger problem i guess.
[Touch Cruise ROM Development] rogro82:
Im at work at the moment so if anyone can upload a 3.13 ddi and disptools.dll from the same rom so nushrike can look at it...

It can be taken of the stock new 6.1 wwe rom.

the 3.28 and 3.13 ddb bitblt are almost the same using spb benchmark but the 3.13's dib bitblt takes 8ms compared to the 3.28's 26ms...

3.28 also fails the gapi bitblt on spb benchmark.

The error 3.13 happens in:

coredll.dll

IDirect3DMobile.CreateDevice

This also happened to some roms with the kaiser driver if im not mistaking... Also tried to install an older version of the driver but then it fails on the samething but it says if fails in ahi2dati.dll
[Touch Cruise ROM Development] rogro82:
Indeed, but the ddi does... thats the main reason im trying to get that one to work somehow.. if its even possible :rolleyes:

edit:

added ddi and disptools which should be the right version
[Touch Cruise ROM Development] pcarvalho:
touchflow3D...on qvga...with our drivers :)

step one...first tab and bottom bar...done ;)

bottom bar resized and working (still a formula error but i will work it out, i hope :D)

only problem is its a none stable version of manila 3D, it crashes alot, cant get "under the hood" sort of speak,cant go for instance to the calander when you press the appointments cause manila stays on top of it all... can this be fixed? is this driver related? is there a working manila3D version that isn't part of the ancient beta one? help... please...if there are answers, i'd like to listen to them :)
[Touch Cruise ROM Development] xplode:
so far there is not, and the old one is crappy at best, and it will never be stable even if the graphics and scripts are edited properly (it is not stable on vga also)
[Touch Cruise ROM Development] pcarvalho:
will have to figger out how to make it qvga aware then and apply it to a new build, hope its possible...
[Touch Cruise ROM Development] SuperJMN:
I've tried it too and I can confirm that it's really buggy, but it's a lot faster than before.

BTW, any news on the 2D acceleration?? In fact, everybody use 2D apps for more than 95% of the time.
[Touch Cruise ROM Development] rogro82:
Ok good news... did some testing and tried something we already did before but then in a reversed way...

I set the 3.28 as normal ddi.dll in the windows folder and set the 3.13 ddi as ddi2 in all registry settings and guess what...

3d runs using the 3.28 ddi

and gdi uses the 3.11

BEST OF BOTH WORLDS :D

My spb benchmark shows the normal 3.11 values 1ms/8ms/2ms

Can anyone/bally3 try this and when it works send this procedure to all the chefs notified so they can implement it and give people their gdi performance AND 3D ;)
[Touch Cruise ROM Development] NeoS:
Hey... I did that BEFORE we had the fix and it worked too, but the 3D did the famous stop-n-go, frame by frame animation. So now it works?

is it what i thought before? They "stack" on each other and take instructions from BOTH?
[Touch Cruise ROM Development] rogro82:
yep... im running udk r0 with 3.28 and 3.11 and both are shown in the process viewer under gwes.exe

so both ddi's are loaded and looking at spb benchmark the 3.11 ddi handles the gdi calls. :D
[Touch Cruise ROM Development] imfloflo:
add a ddi3.dll joke :D
[Touch Cruise ROM Development] NeoS:
Well, i'd be able to test very qiuckly, since i still have the ddi2. Which regkeys did you point it to?
[Touch Cruise ROM Development] rogro82:
Actually mine is called ddi3.dll :D

I started with a 3.13 added a 3.28 as ddi2 then overwrote ddi.dll with the 3.28 one because it wasnt working... then added ddi3 :D
[Touch Cruise ROM Development] rogro82:
i used the 3.28 ddi as main ddi in windows folder, then i added the 3.13 ddi as ddi2 (3 :p) and changed:

[HKEY_LOCAL_MACHINE\Drivers\Display\Active\Built In LCD] Dll

[HKEY_LOCAL_MACHINE\Drivers\Display\Primary] DisplayDll

[HKEY_LOCAL_MACHINE\System\DDraw\DeviceEnum\ddi3.dll] (must be ddi2 for you)

[HKEY_LOCAL_MACHINE\System\GDI\Drivers] MainDisplay

I set all these to the 3.13 dll et voila
[Touch Cruise ROM Development] NeoS:
So, you've changed these 4 keys to ddi2.dll? Aren't those ALL regkeys pointing to ddi.dll?

And your screen still goes to sleep mode? Mine doesn't. it sgoes to sleepmode first, but then flashes between sleep and slumber. :/

hey cool. SPB reports 8 ms again instead of 26.

Lemme run GLBenchmark.
[Touch Cruise ROM Development] NeoS:
GLBenchmark was a liiitle faster than my previous benches.

But i'm removing the ddi2.dll regtweak again. I can't seem to get my screen to go into sleep mode anymore, which is pretty annoying.

Reverting back to my old settings.
[Touch Cruise ROM Development] DarkPower:
cf this post on a french offcial rom

http://xdaforums.com/showpost.php?p=2696372&postcount=10
[Touch Cruise ROM Development] pcarvalho:
just a 2D question...

why does the manila2D "All Programs" shortcut in the laucher tab work so fluidly and WM is so crappy in redrawing...could we get the execution path of both, compare them and use it? that would be nice, but i think it not possible :(
[Touch Cruise ROM Development] bally3:
Possibly because it was optimised for the phone.. remember Opal is a much lower spec device. Code optimisation can do wonders to a system.. look at omnio driver.. with all the 3d hard acceleration on the Polaris AND the kaiser.. the software driver still kicks it butt on most benchmarks. Now if we could get ver 3.13 working... <wistful look>
[Touch Cruise ROM Development] rogro82:
I cant force it to go into sleepmode but is does enter sleepmode when it should...

Ill see what i can do about it.

Bally3 u also tested both the ddi's together?