yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] SomethingWicked:
Hello all... Glad to see you're working on 2D now!! You can see my contribution to the 3D project on the group page if you haven't seen it already. I have a couple more ideas I'm going to throw up this weekend. Hope you like them... :D
[Touch Cruise ROM Development] pcarvalho:
i'm always up for testing :P
[Touch Cruise ROM Development] bally3:
Right thanks to BigKvak's excellent efforts, we now have what looks like a working rom dump.

NikMel is looking at the dump and will hopefully post the files to the team when he's done.

Thanks guys.. this could be a defining moment in the 2D driver development, much like NikMel's discovery of the 3.28 ddi file that got the 3D driver project going.

:)
[Touch Cruise ROM Development] monkeyass:
Hello

So where are the programmers then? the assemblers, It's been a while since I touched some assembly code but I can take a look at some if anyone wants an extra pair of eyes, hands and a brain.

I've downloaded a few of these DLL's from various devices and have started decompiling them into assembly code. If anyone can point me in the direction of someone who is already doing this or who can give me a hand then I would be much appreciative.

Monkey,
[Touch Cruise ROM Development] Chainfire:
I'll fully check this out tomorrow.

Vegetable rights and peace!
[Touch Cruise ROM Development] jerpelea:
hy all

i have retested all ddi.dll that i have

performance obtained on nike

0.97 ddi - spb benchmark 1;29;2

3.13 ddi - spb benchmark 1;7;2

3.28 ddi - spb benchmark 1;28;2

3.57 ddi - spb benchmark 1;25;2

till now the best is 3.13 on 2D
[Touch Cruise ROM Development] bally3:
Hey Monkey.. if you give it a day or so.. I'm going to speak to the team and see where we are.. we definitely could do with your help so welcome aboard. I'm thinking about putting together a small dev team to work on this but really, as we did with the 3D driver I would like to see this thread stickied and all the work done openly on here by many people as I'm convinced there are many devs out there who are not seasoned vets of these forums and would like to get involved but wouldnt know where to start or who to ask.

[edit] I'll update the first post to whoever wants to get involved and add your name to the developers list.

Thank you.
[Touch Cruise ROM Development] Chainfire:
-removed post-
[Touch Cruise ROM Development] NikMel:
Guys

its not pissible to use driver from g810 in our polaris in current state of that driver.:confused:

some hacking needed.

Device is not booting after I include it in a rom.
[Touch Cruise ROM Development] bally3:
damn you were fast! :p

did you try the ddi then?

And can you post up the files on the p3d space please?

:)
[Touch Cruise ROM Development] bally3:
:rolleyes:We knew this was going to happen I guess... was hopig also that the ddi would work at least.. would have been easier!

Back to dependency checking and seeing what calls are being made.. I'm getting 3d driver de ja vu.. :rolleyes:
[Touch Cruise ROM Development] rogro82:
Can anyone let me know where i can find the ddi etc or upload it to our snapdrive account? And not the raw files but extracted :)

Thnx
[Touch Cruise ROM Development] NuShrike:
Trying this again: http://xdaforums.com/showthread.php?t=375567
[Touch Cruise ROM Development] NikMel:
uploading...
[Touch Cruise ROM Development] bally3:
All file are there... is this the complete RAW dump of all RAW parts or just part2.raw NiMel?

BigKvak: **** Job Well DONE ****

You've just won the cherished "I was the first person to dump the G810 rom that kick started the Polaris 2D driver project" award.. badge is in the post! ;)
[Touch Cruise ROM Development] NikMel:
we don't need the other parts.

this are only the drivers no SYS or other
[Touch Cruise ROM Development] bally3:
ok.. I've copied an number of files into my windows directory and no crashes.. the ddraw works and menus seem slightly faster - especially when tf3d is running - and its loaded as once you drop it into the windows folder it cant be overwritten after a hard reset so all good there.

GLBenchmarks show 1000 point drop in swapbuffer speeds though and Billboard FPS drops by a few frames (no that its fast to begin with!).

I think we need to start with a dependency check of the key files first as according to our dev guru:

ahit2dati.dll

ddi.dll

ddraw.dll

and then all other dependencies on files found from them.

We need rogro on this.. he's out erm.. socialising.. you know.. tea and biscuits with the vicar and his wife etc.. :rolleyes:
[Touch Cruise ROM Development] NikMel:
ddi.dll will NOT work:(
[Touch Cruise ROM Development] knownboyofno:
I would love to help but I have a vogue. :( but when yall get this working I would love to know how yall did it so I can try to port it over for others. I want to learn.
[Touch Cruise ROM Development] bally3:
yah.. sorry should have been clearer lol..

I copied a lot of files - NOT including the ddi as you already said it didnt work :)
[Touch Cruise ROM Development] bally3:
We aim to share but you can still help and read up on 2D from some of the MSDN links posted earlier in this thread :)

You never know when you'll come across something everyone else has missed.. of course you could also download the files and run a dependency check on the one listed to find out what files we need to concentrate on.. every little helps.. and you'll learn how we're doing it too! ;)
[Touch Cruise ROM Development] maqui01:
May I ask something? Why are u porting the g810 2d drivers?? Is the GPU the same as the polaris or something like that? Thanks, good luck.
[Touch Cruise ROM Development] bally3:
Yes it is. The Toshiba G810 has a Qualcomm 32 bit 7200 chipset which is same as the Kasier and Polaris so in theory should offer better compatibility - though we seem to have fallen at the first hurdle a little with the ddi which my learned Dev. Guru has just explained to me is due to the newer rev 2 api (thanks dev. guru! :) ) This unfortunately means a lot more low level development for the development team at this early stage.

If you want to see a comparison of these devices:

http://pdadb.net/index.php?m=pdamaster&posted=1&cpu=a7200
[Touch Cruise ROM Development] maqui01:
I see. Are there any benchs that shows g810's 2d performance over polaris's? Is It possible that others pdas with the same chips has better 2d performance? For example LG KS20, I-Mate Ultimate 8502 and the G910?

Maybe there are forums like this for those pdas and could get some dumps from there, or modified version's... who knows... Hehehe...

Wish you the best of luck, thanks for answering all of my annoying questions :P. I just want to learn to get a little bit involved in this, I'm a jr developer.
[Touch Cruise ROM Development] bally3:
No problems friend, Junior Developer eh? what languages may I ask? we sure could use our help as development is where its at - iF you are interested in helping this project - I can add your name to the list of developers?

With regard to testing other roms, the 3d driver base came from kS520, 2 is not so good I believe though I do not know of any 2D benchmarks that have been done apart from what you might find on GLBenchmark.com site under comparisons.

I'll have a look at them today and postmy findings, its possible one of the others may have better 2D, yes,

G910 rom? it took us this long to get a G810 one! :D

But feel froe to scout around for it, if you find it please share it with us :).
[Touch Cruise ROM Development] bally3:
Good effort Jerpelea :)

Our Dev Guru mentioned that 3.13 showed the fastest performance - probably due to being the newer ddi.

Interesting though due to htc's versioning system of each device ddi being independently versioned (nothing wrong with that) I always assumed that they were version by ddi as the kaiser ddi was compatible with the Polaris.

Pity that, because its hard to tell which is the newer ddi apart from looking at the date in an original device - my dates seem to change when I move files to my device so a bit confusing!
[Touch Cruise ROM Development] bally3:
Some good news btw everyone!

Our Dev Guru has confirmed that the G810 is in fact a REV 1 api and not the REV 2 api as previously thought.

In layman terms, what this means is a lot less low level development and we can hope to see a beta working version much sooner than we expected (still a way off though so dont take this as a next week release hint by a long chalk!)

it also means that our dev guys should be able to use similar techniques found in the 3D driver files to create the 2D version.

Chin up people - there's hope yet! :)
[Touch Cruise ROM Development] NuShrike:
You're going to need more files to try the ddi.dll drop in. We need to make this work to test out if G810 has faster 2D.

You'll need from G810: disptools.dll, ahi2dati.dll, and a hybrid wce_rex.dll at least. There's a few other dependencies, and will probably have to be retested/redeveloped from the ground up.
[Touch Cruise ROM Development] NikMel:
NuShrike,

I did include all dependencies of ddi.dll and tryed many combinations.
[Touch Cruise ROM Development] rogro82:
did you only check the dependencies of the ddi or also the dependencies of the files the ddi imported ( the dependencies of the dependencies )?
[Touch Cruise ROM Development] killerjohn:
question

Hi! What programming language can you reverse the dlls - so what is the language do you code 2d/3d drivers?

I have a lot of programming experience in Pascal, Delphi, C#, AutoIt. But almost zero in "real" C or C++ :(

Now I'm running a Diablo II bot project (www.turbotting.net) which is written in AutoIt and based on pixel-based status detection and human interaction simulation.

I also made 5-6 years ago a simple 2D graphic "enigne" in DirectDraw. Plus I know GDI and bitblt operations well, because I developed some nice visual components in Delphi (buttons, form layouts, grids, etc).

Maybe I can help you, but I'm not sure.

Now I'm using Sysrius R1 on my Polaris, and I'm heavily interested in the improvement of the device :)

Sorry for my bad English.
[Touch Cruise ROM Development] NikMel:
all of them:)

I need to port coredll.dll then try it again.
[Touch Cruise ROM Development] BigKvak:
Toshiva has: msm7x00_gpio.dll, msm7x00_otg.dll, but I don't find this files on Polaris...
[Touch Cruise ROM Development] rogro82:
im missing the files like wce_rex wce_pmem and a lot more of which the ddi and disptools are dependent of... arent they in the dump??
[Touch Cruise ROM Development] BigKvak:
How I can read registry settings from dumped rom?
[Touch Cruise ROM Development] NikMel:
this files are in xip part.
[Touch Cruise ROM Development] rogro82:
i can confirm that the ddi also accesses disptools and that the screenupdatebycopy uses the ddi_disp2d_update.
[Touch Cruise ROM Development] NikMel:
this is a screen dump of ddi.dll
[Touch Cruise ROM Development] rogro82:
Where can i find the xip part?
[Touch Cruise ROM Development] NikMel:
I'll share it in 15 min's.:D
[Touch Cruise ROM Development] rogro82:
k thanks :-D
[Touch Cruise ROM Development] NuShrike:
http://xdaforums.com/showthread.php?p=2014756#post2014756
[Touch Cruise ROM Development] NikMel:
Just find them all on http://www.snapdrive.net/myfiles/
[Touch Cruise ROM Development] bally3:
Do you have the original Toshiba G810 rom? if so its easier to reg dump using a registry editor like PHM Registry Editor.

We could do with looking at these and also if you have the g810 could you copy the dll files across from the Windows directory using activeymc please?

The dumped rom files are missing some vital info like version for the ddi and stuff.

Thanks again :)
[Touch Cruise ROM Development] NikMel:
rogro82 check your pm
[Touch Cruise ROM Development] rogro82:
Got it... just missing one last file its mmtimer.dll :D
[Touch Cruise ROM Development] NikMel:
uploading sys part g810 check in 10-15 mins

EDIT: Done upload!!!
[Touch Cruise ROM Development] rogro82:
I really need to learn how to extract it and not be lazy :D
[Touch Cruise ROM Development] bally3:
More beer rogro,.. thats what you need.. it inspires you :rolleyes:

NikMel you're on fire mate! :D
[Touch Cruise ROM Development] bally3:
here you go!

I'm out visiting folks.. bbl
[Touch Cruise ROM Development] rogro82:
ok i collected all files with dependencies to the ddi.dll including all sub-dependencies...

Ill upload the zip-file.

Maybe ns can take a closer look and see if its useful. Should i upload it here or on snapdrive and should i protect it?
[Touch Cruise ROM Development] NikMel:
there one problem:

ddi.dll is missing one call in wce_rex.DLL and at the moment I can't find a suitable wce_rex.DLL file.
[Touch Cruise ROM Development] rogro82:
Which call and from which file? my ddi doenst link to wce_rex only wce_pmem
[Touch Cruise ROM Development] bally3:
Just a reminder that in the 3d driver all dll files with "F" in caps were created by htc-ca.

(isnt typing on your polaris fun! :) )
[Touch Cruise ROM Development] NikMel:
disptools.dll is missing one call from wce_rex
[Touch Cruise ROM Development] Chainfire:
Finally home. Lets check this stuff out :)
[Touch Cruise ROM Development] Chainfire:
Blergh. Almost got it running on Kaiser, but the Kaiser got to be reflashed - and you guessed it - it gotta charge first :)
[Touch Cruise ROM Development] pananza:
Flash using SD card. Don't have that stupid 50% rule. As long as you have enough power to last the flash process (what 3-5 minutes) you are ok.
[Touch Cruise ROM Development] bally3:
Second that. SD card method has never failed me.. and its a good idea to have the POLAIMG.nbh file on your card when things go REAL wrong.. saved my hiney a few times! :rolleyes:
[Touch Cruise ROM Development] bally3:
OK.. interesting news.. the coredll.dll ALSO works fine with the Polaris out-of-the-box.

So thats ddraw.dll AND coredll.dll that work fine.
[Touch Cruise ROM Development] bally3:
Chainfire seems to be moving on the Kaiser rom with this..how are we doing with the dependency checking?
[Touch Cruise ROM Development] itje:
nice stuff

Do you notice any performance diffrence using the new ddraw.dll & coredll.dll?
[Touch Cruise ROM Development] bally3:
yes, to ddraw.dll

no to coredll.clll
[Touch Cruise ROM Development] maqui01:
I worked in many java and .net (in c#) projects, and at college some cpp and c projects, and a few more not worth mentioning. I'd like to help, I don't know how, but I could investigate anything and work out something :D. I'll scout something around about the toshiba rom.
[Touch Cruise ROM Development] bally3:
Thats fine.. in the meantime I have added you to the developers list. Just keep an eye on the threads and see how you can help.
[Touch Cruise ROM Development] w04g005:
Does the ddraw.dll show improvements in scrolling? Any information about the current status of the project?
[Touch Cruise ROM Development] Chainfire:
For the interesting, I have been able to get the 2D drivers running on the Kaiser yesterday, but not very well. Something still amiss there. Same modified files were also tested on Polaris but didn't work. This'll be a while :)
[Touch Cruise ROM Development] akirax:
Good job for all!

Can you explain to us what are the necessary files and how to try it?

I have kaiser ppc.

Thank´s!
[Touch Cruise ROM Development] spocky12:
Hi,

I'm a ks20 owner and I have to say that even if we have hardware acceleration, there are still bugs that prevent some apps from working as they should, and Lg don't seem to care.

Could you please provide me a link to g810 graphic dll folders (or password for those already available here, or method to extract dump.bin available in first post) so that I can see if it's possible to replace some default drivers.

Thanks in advance
[Touch Cruise ROM Development] Chainfire:
There are RAW files posted a few pages back. As you are a chef, you should be able to use your tools to dump the contents...
[Touch Cruise ROM Development] NeoS:
Good to see some people are sreiously working on this.

I tried to add files from the g810 dump but it took me 4 hard resets and it still doesn't work. (on Polaris)

And how do we test for performance increase? Any tools for that?
[Touch Cruise ROM Development] imfloflo:
i tought the test are making by run a video of bmw spot :p to compare result :p
[Touch Cruise ROM Development] NikMel:
Guys,

You can add ddraw.dll to polaris and it will work with no notable performance gain.

If you try to add video driver (ddi.dll) with all or partial dependencies it will not boot and there is no difference buildin to rom or just by cab install.
[Touch Cruise ROM Development] spocky12:
Hi Chainfire and thanks for your answer.

Well, if by chefs you mean people that develop tools, kitchen and roms, indeed I'm a chef. Problem is, I'm not htc chef. I had to build my own tools to work with lg file format (I've never worked with raw files, I made tools to extract/uncrypt lg flash.bin file in order to obtain xip.bin/imgfs.bin). I assume this raw file was created with pdocread, but the only time I used it, I made separated dumps, one for each partition, so I'm not sure on how I could get xip.bin/imgfs.bin from it. When I have time, I'll surely find out how to do it, but you'll save my time telling me how I could achieve it :)
[Touch Cruise ROM Development] Chainfire:
K, first I'm using the tools that came with the Raphael Kitchen (see Raphael forum).

This is pretty much it, may be some mistakes made of course, guess you'll figure it out

ren Part1.raw xip.bin
ren Part2.raw imgfs.bin

imgfstodump imgfs.bin
ren dump imgfs

mkdir xip
dumprom xip.bin -5 -d xip

pkgtool imgfs

note that pkgtool returns immediately but runs in the background, and many of the resulting files will be hidden/system :)

HTH
[Touch Cruise ROM Development] Chainfire:
Just copying all the dependancies _usually_ will not work for driver stuff at all. In my case I found a disptools in one of the latest Kaiser ROMs that had the required functions that matched the DDI, and modified the references in DDI to some other DLLs to use 3D-driver DLLs instead. At least in that way it boots. But needs more research, as _something_ is still incompatible that way too. (it's really slow, and KITL logs fill up with some memory alloc problem)

(generally you'd want to use as few device specific DLLs from other devices as possible)
[Touch Cruise ROM Development] NeoS:
But what is wrong with our current disptools and ddi's? Can't we compare those with other devices and add the missing dependancies?
[Touch Cruise ROM Development] spocky12:
Thanks Chainfire, I didn't see those dump files, I thought you talked about dump.bin in first post, it'll be ok, I'm familiar with imgfstodump and dumprom.

While I'm here, may I ask how you "modified the references in DDI (or in any dll I assume) to some other DLLs". I confirm copying all dependancies from a driver not made for my device didn't work at all (it was diamond stuff, as I saw it was using same drivers than mine, just more up to date. I just hope using drivers from device with same resolution will give better results). What kind of tools do you use ?
[Touch Cruise ROM Development] Chainfire:
Ideally yes, that is easier said than done, though ;)
[Touch Cruise ROM Development] Chainfire:
IDA 5 disasm'r and a hex editor (xvi32). The 3D drivers already have some patched/proxy DLLs that provide some missing functionality, so I used those. They don't work on the KS20 I think, though :D
[Touch Cruise ROM Development] spocky12:
Sorry, I must be blind, but I can't find dump files, only NikMel saying "uploading them" and a link to http://www.snapdrive.net/myfiles/ which takes me to my snapdrive account :)

Btw, Chainfire, thanks again for your explanations. If I understood correctly, in new dll you want to replace, you just change a referenced dll name say, foo.dll to bar.dll, and develop a bar.dll which acts as a proxy to original device driver where functions exist, and provides additional missing functions ?
[Touch Cruise ROM Development] Chainfire:
@spocky

Sorry my bad, they were in the 3D thread... http://xdaforums.com/showpost.php?p=2763353&postcount=1503

@all

Doh, tests on Polaris not being signed.... gonna try that now with rogro... maybe it'll load now and be just as bad as on Kaiser :D (or perhaps it will work right instead?)
[Touch Cruise ROM Development] rogro82:
Chainfire:

Here is our disptools.
[Touch Cruise ROM Development] bally3:
Anyone tried the ddi in a rom that DOESNT have the 3d driver in it?
[Touch Cruise ROM Development] bally3:
Are these ALL the dependencies of the ddi?

and has someone done a dependency check on disptools also?
[Touch Cruise ROM Development] bally3:
Just a quick update folks.. Seems like a quiet night on here tonight but actually a lot of the low level stuff that we mentioned is being worked on by Chainfire, Rogro and the other developers and a bit of brain-storming by the rest of us.. (and many hard resets!)

We will hope to update you with some news soon. :)
[Touch Cruise ROM Development] maxniper:
Thanks,

you are all doing a great work.
[Touch Cruise ROM Development] NeoS:
Im really sorry that i'm not there right now guys. I'm on the road for a couple of days, so i won't be able to join your chat sessions. But i will check the forums from time to time.

I see collaboration is the way to go eh? ;)
[Touch Cruise ROM Development] Chainfire:
Update of the day

WE HAVE SUCCEEDED

in finding another 200 ways that wont work

However, we are slowly, very slowly, getting closer.
[Touch Cruise ROM Development] pcarvalho:
loool...nice update ;)

keep it up :D
[Touch Cruise ROM Development] rogro82:
patched libgles_cm_ks for suspend mode
[Touch Cruise ROM Development] imfloflo:
Thanks rogro82 good work .
[Touch Cruise ROM Development] rogro82:
It will not fix the stalling of manila after a suspend but thats a different story... been looking into that also...

Somehow something is destroyed when device enter suspendmode/or comes back out of suspend mode. Used remote spy and the window is loosing name and proc address changes.
[Touch Cruise ROM Development] NeoS:
It fixes what now?

It's 2D related right?
[Touch Cruise ROM Development] rogro82:
Its common driver related... the libgles is used by the 3d driver but too not have people search for it in 1000 threads it seemed better to post it in here.

It fixes the possibility to turn the screen off.. manila still crashes but thats a different story.

Im not thinking 2d/3d :D eventually all is related to each other...
[Touch Cruise ROM Development] BigKvak:
Here links to ToshibaG810 Reg:

http://rapidshare.com/files/153926912/toshibaG810REG_ToCom.rar

http://rapidshare.com/files/153927055/toshibaG810REG_PHMBackUp.rbk

May be it will help...
[Touch Cruise ROM Development] Chainfire:
Thanks, let's see if we can do anything with that :)
[Touch Cruise ROM Development] whitealien:
I tested it and I can confirm that phone goes sleep mode with running TF3D, but when you turn in on, it hung. I guess it is manilla 3D related as it is not very stable anyway. It hung also when you exit from album.

Great work m8 ;)

edit: I did few 3d tests. lights.exe seems to be slower and triangle just does not start. Glbenchmark does not run either - stays on white screen.
[Touch Cruise ROM Development] monkeyass:
Hi Nikmel,

Do you have the coredll.dll from the g810 i can take a look at please?

Thanks,

monkey
[Touch Cruise ROM Development] rogro82:
Have you tried disabling manila.. softreset and then do the tests again?

I think its actually driver related because all the apps are suffering from the same problem.
[Touch Cruise ROM Development] monkeyass:
Hi,

Are you guys noticing big differences from your ddi.dll compared to the g810's? I have a nike and there are alot of differences held within the files, I've noticed that disptools has tv-out functions in there aswell which i'm sure this should be hardware specific should it not?

Monkey
[Touch Cruise ROM Development] Krypto99:
Sonyericsson Xpertia X1 Rom

Has anyone checkt the rom from Xpertia X1?

It has the MSM7200A chip, maybey there is someting useful in there!? :)

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