2D Driver Development Project - HTC-CA & Team P3D go 2D!

[bally3]

*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***

The software posted here is for TESTING purposes only, Team P3D or any of the posters of software, or links to software on this thread take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk.

---------------------------------------------------------------------------------------------------------------------------------------------------------------

Project Name: Polaris 2D Driver Project

Driver Name: P3D 2D Driver (Working title)

Development and Testing Team: SEE Post #2 (http://forum.xda-developers.com/showpost.php?p=2759558&postcount=2)

---------------------------------------------------------------------------------------------------------------------------------------------------------------

ANNOUNCEMENT:

The P3D team would like to extend an OPEN INVITATION to all developers and programmers from all forums of EVERY device to come forward and help us create the 2D driver which, as it is being developed from scratch will require much development work with many dll files created from scratch.

If you are interested in helping, please post your interest in this forum and we will add your name to the developers list. If you would like to help but own a different device to which the 3D driver is yet to be ported to, we would also like to hear from you and hopefully assist you with the knowledge we have gained in return for your efforts here. (actually we'll help you anyway but.. we do want your help! :) )

---------------------------------------------------------------------------------------------------------------------------------------------------------------

11/10 - BigKVak successfully dumped the G810 rom and work has started in analyzing its content

---------------------------------------------------------------------------------------------------------------------------------------------------------------

[bally3]

P3D 2D Driver Development Team:

Administration/Testing:

Support and Testing:
Bally3
NikMel
Neos2007
BigKvak
Imfloflo


Developers: (TBC)

Rogro82
NuShrike
Chainfire
Monkeyass
maqui01

[bally3]

It started with a few simple questions:

"Can the Polaris be hardware accelerated?"

"Why doesnt the CA Kaiser 3D driver work on the Polaris?"

That was a month ago..since then, thanks to the help and support of NikMel, NeoS2007, Rogro82 and NuShrike to name a few, we now have a working 3D driver which is currently in a version 1 state and with the release of the cab version through CA last night, we can now concentrate on improving speed and compatibility to make better use of the graphic chips capabilities.

My intention then was never to start a 2D driver or work on a 2D driver until I was satisfied no more could be done to improve it and a "final" release was in the cards, but through my own testing and various posts and conversations, I now find myself wondering whether the improvements with 3D is linked to the 2D driver?

From day 1, before we released the 3d driver and after, users have expressed faster speeds in 2d as well as 3d - though many have explained it to be a "placebo" effect, we naturally attributed this to the gpu sharing the workload with the cpu which makes sense in a common sense way - itje posted a humorous answer on his thread explaining this very thing as worth a read just to put a smile on your face, but on a serious note a question has to be asked - Does improvement on 3D really effect 2D and if that is the case, would a 2D driver help improve the 3D drivers perfornance?

So why start a 2D thread when the 3D driver still needs refining?

Well, apart from the question above, the overwhelming requests for 2D support on both Polaris and Kaiser forums (it should work on both in theory), we now have a dump of the long awaited Toshiba G810 rom to get us started- A BIG THANK YOU TO BIGKVAK - welcome to the team! :)

Originally Posted by BigKvak
I have dumped ROM from Toshiba, here the link http://rapidshare.com/files/152085600/dump.rar.htmlIt is inevitable then that work needs to start on this project. We also need to preserve the 3D thread for future 3D driver developments and defer 2D driver related posts from it, for these reasons, this new thread has been opened for all to start working with the P3D team in bringing 2D greatness to our devices.

Lets share our knowledge and have fun doing it like we did with the 3D driver!

PS: Although I have named the project Polaris 3D driver project, I would like to extend an invitation to users of all devices that could benefit from the 2D drivers creation, after all through CA Kaiser development, we have now ported the 3D driver to the Polaris AND the NIKE and hopefully to many more devices :)

Let our devices not make us divisive - whats is the point?

It is common knowledge that files from newer devices are used to help create the drivers we need for our devices - so why should we gloat and mock other less supported devices, should we not help them and share our knowledge and in the words of a good friend here "Pay it Forward?"

This is not the spirit of XDA Developers and it is certainly not the ethos of Team P3D - We have and pledge tol share all knowledge with users of all devices.

Besides, its so much more fun when we all work together! :)

[bally3]

It appears that HTC-CA were already in the process of

[bally3]

Reserved for p3d 4

[bally3]

Reserved for p3d 5

[bally3]

Reserved for p3d 6

[bally3]

Reserved for p3d 7

[bally3]

Reserved for p3d 8

[bally3]

Reserved for p3d 9

[bally3]

Reserved for p3d 10

[NeoS]

I found this link on microsoft MSDN: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1214862&SiteID=1

It's a guy asking for a 2d driver library. Maybe we can look into that?

[bally3]

I have dumped ROM from Toshiba, here the link http://rapidshare.com/files/152085600/dump.rar.html

To move the discussion of 2d in here.. :)

[NeoS]

I believe this: http://msdn.microsoft.com/en-us/library/aa911096.aspx will be out first place to look. It's mostly there: 2D AND 3D info.
Here's what functions there are:

AlphaBlend API
Provides information about adding support for the AlphaBlend function to your OS design.

Direct3D Mobile
Provide information about adding 3-D graphics support to your OS design and creating applications that use the API.

DirectDraw
Provide information about adding 2-D graphics support to your OS design and creating applications that use the API.

Gradient Fill Support
Provides information about adding support for the GradientFill function to your OS design.

Imaging
Provide information about adding support for compressed still images to your OS design and reference information for the API.

Multiple Screens
Provide information about adding support for multiple displays to your OS design and creating applications to support them.

[bally3]

I believe this: http://msdn.microsoft.com/en-us/library/aa911096.aspx will be out first place to look. It's mostly there: 2D AND 3D info.

reading it now.. some of it we know.. let see what we can learn..

[NeoS]

http://msdn.microsoft.com/en-us/library/aa925824.aspx
Here we go:
"Applications direct output to a specified device by creating a device context for the device. The device context is a GDI-managed structure containing information about the device. An application creates a device context by calling device context functions. GDI returns a device context handle used to identify the device.

Applications can direct output to a physical device, such as a display or printer, or to a logical device, such as a memory device.

A device context also contains attributes that determine how GDI functions interact with a device. These attributes eliminate the need to specify every piece of information Windows Embedded CE requires to display an object on a device. If you want to change an attribute, you can use attribute functions to change current device settings and operating modes. Operating modes include text and background colors and the mixing mode that specifies how colors in a pen or brush combine with colors already on a display surface."

GDI is the source of 2D on our devices. Maybe we need to look out for GDI tweaks in the registry?

[NeoS]

I also found this blog about the colors used on a mobile device. It's said that if you have a colordepth of 18 instead of the usual 8, 16, 32 bits, it's more cpu intensive. Isn't there a registry key for colordepth?

http://blogs.msdn.com/windowsmobile/archive/2005/09/07/462187.aspx

"The next thing to understand is how the bits turn into colors on the screen. Say you've got a typical PocketPC with a resolution of 240x320 and 65536 colors. That means you've got 320 rows of 240 pixels (dots), each of which has 16 bits of data representing its color. All of that information is stored in a chunk of memory known as the "Frame Buffer." The LCD hardware takes whatever is in the Frame Buffer and converts it directly to what's on the screen. Want to change what's on the screen? Change what's in the Frame Buffer and the screen will update.

Okay, so we need 16 bits for every pixel, and we've got 240 times 320 dots. 16 bits is two bytes, so that's a total of 153600 bytes, or 150K of RAM used to hold what's on the screen."

[NeoS]

Maybe a good thing to mention: we're hoping that the Toshiba g810 Portege has the files we need to develop a 2D driver. We're currently trying to extract a dump we got. Anyone have experience in extracting Toshiba's .Bin files?

[NeoS]

On MSDN:
"The DirectDraw® API provides support for hardware-accelerated 2-D graphics. It offers fast access to display hardware while retaining compatibility with the Windows graphics device interface (GDI). DirectDraw is a specialized memory manager for both system and display device memory and uses hardware acceleration where available. With DirectDraw, you can allocate and manipulate both system and graphics memory, including transfers between the two.

DirectDraw for Windows Embedded CE is adapted from DirectDraw for Windows-based desktop operating systems. Some capabilities from the desktop version have been extended and others have been curtailed to better suit embedded devices.

DirectDraw supports the following effects:

Bit-block transfers (blits)

Page flipping and multiple back buffers

Overlays, which is placing one image surface over another on the video display

Alpha source over destination blending, which is blending two surfaces using the source alpha image component

Video YUV pixel formats and color conversion

Direct video access to the frame buffer

What if we compare our HKLM\system\DDRAW\ keys in the registry with other devices? I see the values in ALL keys there are empty.

[bally3]

Yes.. I've noticed that and played around with them.. no difference.

I've tried the LG KS520, Diamond and HD ddraw.dll files.. none work out of the box. Maybe the G810 one might make a difference?

We need to find out what calls are made and to what other dll files. If you remember the problem we had with the 3.13 ddi? it could be similar situation in that theirs a dependencies issue.

[c3ro]

Maybe a good thing to mention: we're hoping that the Toshiba g810 Portege has the files we need to develop a 2D driver. We're currently trying to extract a dump we got. Anyone have experience in extracting Toshiba's .Bin files?

i registered at http://www.portegeclub.com/forum/

there are several cooked g900 roms. the ppl there must know how to handle the romfiles.

i found a toshiba kitchen here, but dunno if it have all needed tools to extract.
http://www.portegeclub.com/forum/viewtopic.php?t=1143

[NeoS]

Small update: I've found a ddraw.dll from the Toshiba G810. It seems to work with my Polaris!

I'm running a few tests now. :)

[bally3]

Thanks c3ro.. downloading and checking now..

[bally3]

nope.. sorry .. didnt work.. its saying it a needed decompression dll is missing?

Any ideas anyone?

We're running out of ideas here how to extract it.. ust lets hope we can get another dump of it from my g810 friend. :)

[bally3]

Small update: I've found a ddraw.dll from the Toshiba G810. It seems to work with my Polaris!

I'm running a few tests now. :)

Need to do a dependencies check on it.. definitely something going on here.. its faster 2d.. but also some interesting test results!

Could do with the full package to see what we can use.. especially the ddi file and disptools.dll.

If these could work out of the box then we could just use the dependency check to see what we're missing and we're on the right track then.

Right, enough for one night, I'm going to watch tv I think.

Rogro mate, if you come on, if you could check these... or even Pananza.. actually anyone whose good with dependency checking.. you know what to do.. check the ddraw.dll.

[bally3]

I think we might be onto something good here so I'll repeat to all you lurkers and watchers:

IF YOU WANT TO SEE THE DEVELOPMENT OF THE 2D DRIVER THEN PLEASE FIND THE ROM DUMP FOR THE TOSHIBA G810.

I'm hoping BigKvak can dump the rom fully so that we can get to work on it quickly but lets try and get one anyway just in case.

Toshiba G810 or even the G910 rom.

Night all :)

[c3ro]

Thanks c3ro.. downloading and checking now..

hi,

did you already tried this? >> http://forum.xda-developers.com/showpost.php?p=2562972&postcount=164

[FXP]

my findings

i have switched ddraw.dll from diamond to nike but no speed improvement
the files is in /sys/os/
is os core file not releated to the driver
it can be switched only within the same os build or it will not work

i dont think that the 2d accel answer is in here

BR

[NikMel]

c3ro,

Its not possible to make a rom when this dump is not complete.

hi,

did you already tried this? >> http://forum.xda-developers.com/showpost.php?p=2562972&postcount=164

[bally3]

my findings

i have switched ddraw.dll from diamond to nike but no speed improvement
the files is in /sys/os/
is os core file not releated to the driver
it can be switched only within the same os build or it will not work

i dont think that the 2d accel answer is in here

BR

its not the ddraw from diamond.. its the ddraw from g810.

and the answer is here.. trust me! :)

[bally3]

NiKMel, Glad to see you on the case my friend :)

Definitely need your insight into this to get it moving.. !

[bally3]

Posted by NIKMEL

Chainfire,

I think part03 is good to go.
Some times dumping disk is causing some problems.

Quote:
Originally Posted by Chainfire
please try the following commands:

Code:
pdocread -w -d DSK1 -b 0x800 -p Part00 0 0x1ff000 Part00.raw
pdocread -w -d DSK1 -b 0x800 -p Part01 0 0x340000 Part01.raw
pdocread -w -d DSK1 -b 0x800 -p Part02 0 0x48e0000 Part02.raw
If those don't work, try replacing -b 0x800 with -b 0x400, -b 0x200 or removing the -b 0x... part altogether.

The values you issues for your command you screenshotted don't see to be correct...

Please continue in this thread - Thank you :)

[NeoS]

I see we're getting places.

After a good read of earlier posted MSDN links, i cme to the conclusion that ddraw + gdi makes the 2D hardware work. I think this is where we should look.

[bally3]

I see we're getting places.

After a good read of earlier posted MSDN links, i cme to the conclusion that ddraw + gdi makes the 2D hardware work. I think this is where we should look.

With NikMel and Chainfire on the case I'm confident we'll get that rom dump soon! :)

btw, Chainfire I hope I can add your name to the team on this one, since we're all working towards a common goal and I dont think anyone can doubt your ability to get a project like this into ultra sonic mode - just look at what yo've done with TF3D! :)

[rogro82]

Most of the work will come from somehow hacking the ddi and coredll if im not mistaking ( cf/ns correct me if im wrong )... i think this will need some hardcore hackers like cf and ns ( and all others that are mentioned on the htcca site ).. Im willing to help and throw in ideas but i think in this case thats about all i can do...

All other things depend on implementations of developers so thats no way to really up the 2d performance.

[bally3]

Most of the work will come from somehow hacking the ddi and coredll if im not mistaking ( cf/ns correct me if im wrong )... i think this will need some hardcore hackers like cf and ns ( and all others that are mentioned on the htcca site ).. Im willing to help and throw in ideas but i think in this case thats about all i can do...

All other things depend on implementations of developers so thats no way to really up the 2d performance.

See.. there you under-estimating yourself again :)

If I remember rightly.. you said something similar on the 3d thread.. and look what you've helped us to achieve.. but yes I take your point on board that there is a lot of hacking and code implementation thats been talked about that may be required.

[imfloflo]

Nice to view another thread with all of you working on this hope we can make this working like 3D porting.
Always here to help ;)

[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

[pcarvalho]

i'm always up for testing :P

[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.

:)

[monkeyass]

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,

[Chainfire]

I'll fully check this out tomorrow.

Vegetable rights and peace!

[FXP]

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

[bally3]

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,

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.

[Chainfire]

-removed post-

[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.

[bally3]

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.

damn you were fast! :p

did you try the ddi then?

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

:)

[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:

[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

[NuShrike]

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 :)Trying this again: http://forum.xda-developers.com/showthread.php?t=375567

[NikMel]

uploading...

[bally3]

uploading...

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! ;)

[NikMel]

we don't need the other parts.
this are only the drivers no SYS or other

[bally3]

we don't need the other parts.
this are only the drivers no SYS or other

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:

[NikMel]

ddi.dll will NOT work:(

[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.

[bally3]

ddi.dll will NOT work:(

yah.. sorry should have been clearer lol..

I copied a lot of files - NOT including the ddi as you already said it didnt work :)

[bally3]

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.

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! ;)

[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.

[bally3]

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.

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

[maqui01]

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

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.

[bally3]

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.

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 :).

[bally3]

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

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!

[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! :)

[NuShrike]

ddi.dll will NOT work:(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.

[NikMel]

NuShrike,

I did include all dependencies of ddi.dll and tryed many combinations.

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.

[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 )?

[killerjohn]

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.

[NikMel]

all of them:)
I need to port coredll.dll then try it again.

did you only check the dependencies of the ddi or also the dependencies of the files the ddi imported ( the dependencies of the dependencies )?

[BigKvak]

Toshiva has: msm7x00_gpio.dll, msm7x00_otg.dll, but I don't find this files on Polaris...

[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??

[BigKvak]

How I can read registry settings from dumped rom?

[NikMel]

this files are in xip part.


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??

[rogro82]

i can confirm that the ddi also accesses disptools and that the screenupdatebycopy uses the ddi_disp2d_update.

[NikMel]

this is a screen dump of ddi.dll

[rogro82]

Where can i find the xip part?

[NikMel]

I'll share it in 15 min's.:D

Where can i find the xip part?

[rogro82]

k thanks :-D

[NuShrike]

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??http://forum.xda-developers.com/showthread.php?p=2014756#post2014756

[NikMel]

Just find them all on http://www.snapdrive.net/myfiles/

[bally3]

How I can read registry settings from dumped rom?

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 :)

[NikMel]

rogro82 check your pm
Where can i find the xip part?

[rogro82]

Got it... just missing one last file its mmtimer.dll :D

[NikMel]

uploading sys part g810 check in 10-15 mins

EDIT: Done upload!!!
Got it... just missing one last file its mmtimer.dll :D

[rogro82]

I really need to learn how to extract it and not be lazy :D

[bally3]

I really need to learn how to extract it and not be lazy :D

More beer rogro,.. thats what you need.. it inspires you :rolleyes:

NikMel you're on fire mate! :D

[bally3]

Got it... just missing one last file its mmtimer.dll :D

here you go!

I'm out visiting folks.. bbl

[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?

[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.

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?

[rogro82]

Which call and from which file? my ddi doenst link to wce_rex only wce_pmem

[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! :) )

[NikMel]

disptools.dll is missing one call from wce_rex

Which call and from which file? my ddi doenst link to wce_rex only wce_pmem

[Chainfire]

Finally home. Lets check this stuff out :)

[Chainfire]

Blergh. Almost got it running on Kaiser, but the Kaiser got to be reflashed - and you guessed it - it gotta charge first :)

[pananza]

Blergh. Almost got it running on Kaiser, but the Kaiser got to be reflashed - and you guessed it - it gotta charge first :)

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.

[bally3]

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.

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:

[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.

[bally3]

Chainfire seems to be moving on the Kaiser rom with this..how are we doing with the dependency checking?

[itje]

nice stuff

Do you notice any performance diffrence using the new ddraw.dll & coredll.dll?

[bally3]

nice stuff

Do you notice any performance diffrence using the new ddraw.dll & coredll.dll?

yes, to ddraw.dll

no to coredll.clll

[maqui01]

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 :).

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.

[bally3]

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.

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.

[w04g005]

Does the ddraw.dll show improvements in scrolling? Any information about the current status of the project?

[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 :)

[akirax]

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 :)

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!

[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

[Chainfire]

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

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...

[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?

[imfloflo]

i tought the test are making by run a video of bmw spot :p to compare result :p

[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.


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?

[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 :)

[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

[Chainfire]

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.

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)

[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?

[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 ?

[Chainfire]

But what is wrong with our current disptools and ddi's? Can't we compare those with other devices and add the missing dependancies?

Ideally yes, that is easier said than done, though ;)

[Chainfire]

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 ?

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

[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 ?

[Chainfire]

@spocky

Sorry my bad, they were in the 3D thread... http://forum.xda-developers.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?)

[rogro82]

Chainfire:

Here is our disptools.

[bally3]

Anyone tried the ddi in a rom that DOESNT have the 3d driver in it?

[bally3]

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?

Are these ALL the dependencies of the ddi?

and has someone done a dependency check on disptools also?

[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. :)

[maxniper]

Thanks,
you are all doing a great work.

[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? ;)

[Chainfire]

WE HAVE SUCCEEDED
in finding another 200 ways that wont work

However, we are slowly, very slowly, getting closer.

[pcarvalho]

WE HAVE SUCCEEDED
in finding another 200 ways that wont work

However, we are slowly, very slowly, getting closer.

loool...nice update ;)
keep it up :D

[rogro82]

patched libgles_cm_ks for suspend mode

[imfloflo]

Thanks rogro82 good work .

[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.

[NeoS]

It fixes what now?
It's 2D related right?

[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...

[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...

[Chainfire]

Thanks, let's see if we can do anything with that :)

[whitealien]

patched libgles_cm_ks for suspend mode

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.

[monkeyass]

Hi Nikmel,

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

Thanks,
monkey

[rogro82]

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.

Have you tried disabling manila.. softreset and then do the tests again?

I guess it is manilla 3D related as it is not very stable anyway. It hung also when you exit from album.

I think its actually driver related because all the apps are suffering from the same problem.

[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

[Krypto99]

Has anyone checkt the rom from Xpertia X1?
It has the MSM7200A chip, maybey there is someting useful in there!? :)
http://forum.xda-developers.com/showthread.php?t=407148

[bally3]

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

Hi Monkey,

Thanks for doing the tests, the disptools is device specific yes. Thats why we either need to find a suitable disptools to work with the g810 ddi - OR - we need to create files that export out the required calls.

What I'd like to know is what these calls are in the ddi that enable the hardware accelerated 2D - if indeed it is hardware and not software based.

If we can find this out, we can then start looking at all the dependencies that exist for these calls.

At present my understanding is that in theory we can the same as what we did with the 3d driver - using proxy dll files to export these calls - but we probably will need to create a lot more files than with the 3d driver.

But before we can do this, we really need to understand and note what these calls are in the g810 ddi.

[bally3]

Has anyone checkt the rom from Xpertia X1?
It has the MSM7200A chip, maybey there is someting useful in there!? :)
http://forum.xda-developers.com/showthread.php?t=407148

If we can get a rom dump of this, it would be great! :)

So.. A new mission for anyone who wants to help out!

[monkeyass]

Hi Bally3,

From what I remember this morning it is using the ah2dati.dll or something, can't check it at the moment because I'm in work, but most the render functions were called from there. I didn't like that it used Disptools as i don't even have a disptools file on my nike from what I can see. To cut bits out of the one I have just wouldn't work and I really can't tell if removing the call to disptools would work either, most of the code just melts my brain at the moment. I think it will take me some time to read up on the whitepapers for ARM assembly.

Monkey

[NeoS]

ahi2dati.dll? Isn't that used for 3D only?

[monkeyass]

I wouldn't have thought so, as the name suggests.

[Chainfire]

ahi2dati is pretty much the layer between all drivers parts and the hardware... not completely, but you could certainly see it that way.

[NuShrike]

ahi2dati.dll? Isn't that used for 3D only?ATI Handheld Interface 2D ati. It's the core layer to the ATI chip for video memory allocation, PM4 packet commands, some IRQs.

PM4 is somewhat explained in the Radeon docs, but it's very device specific on how to flip the hardware registers, so the Q chip is not documented publically.

[NeoS]

So ahi2dati is also device specific. Like libgles and DDi. Should we make a list of devices we ripped those from? could make life easier.

[knownboyofno]

is this of any help? -->http://forum.xda-developers.com/showthread.php?t=40616

[SuperJMN]

is this of any help? -->http://forum.xda-developers.com/showthread.php?t=40616

I'm afraid this thread no longer exists...

[NuShrike]

So ahi2dati is also device specific. Like libgles and DDi. Should we make a list of devices we ripped those from? could make life easier.Nope, nope, and nope, since we're using the same cpu.

[NeoS]

Ok, then we could just copy the ddi, libgles and ahi2dati from ANY device to ours and it should work? :confused:

[NuShrike]

Ok, then we could just copy the ddi, libgles and ahi2dati from ANY device to ours and it should work? :confused:Yes, unless you're a Kaiser/Polaris. HTC merged DDI and ahi2dati.dll together on Kaiser/Polaris to make it harder. Various tricks were used to even get an usable external ahi2dati for 3D currently.

Best if we can get it all DDI/ahi2dati separated again by porting a proper DDI from another device.

[w04g005]

Best if we can get it all DDI/ahi2dati separated again by porting a proper DDI from another device.
Which one?

[NeoS]

Apparently the Toshiba g810 Portege holds the answer to this.

[w04g005]

so, no need for searching an other ROM dump?

[imfloflo]

NO don't think , some persone already have the g810 dump in their hand and working on it.

[bally3]

Yes, unless you're a Kaiser/Polaris. HTC merged DDI and ahi2dati.dll together on Kaiser/Polaris to make it harder. Various tricks were used to even get an usable external ahi2dati for 3D currently.

Best if we can get it all DDI/ahi2dati separated again by porting a proper DDI from another device.

but this doesnt make sense to me then as in why cant we get the g810 ddi working on our polaris - even with the disptools and modded ddi from chainfire?

Do we have to mod the ddi differently?

[Chainfire]

Laurentius has a lead on that one, we may know the answer to this later today.

[bally3]

Laurentius has a lead on that one, we may know the answer to this later today.

I like hearing this news! :)

On an sub note, a kind xdevver pm'd me to say that the Xperia X1 rom is around .. apparently Sakajati in the kaiser forums has cooked a rom with the x1 files.

Anyone care to speak to Sakajati and see if he will share the files with us?

[bally3]

Whilst we explore these possibilities, c_shekhar has posted a new rom with a new rom here with a new build:

http://forum.xda-developers.com/showthread.php?t=436779

I see from the post that jerepelea shared the sys with him, c_shekhar if you're reading this, can you tell us if the files are newer in this rom? I see its still 3.13 ddi but is there a chance there might be a newer disptools in this or is this from another device?

[Chainfire]

He does mention it has newer HTC drivers... So I guess this is the latest OEMDrivers package, which may definitely help.

[c_shekhar]

Whilst we explore these possibilities, c_shekhar has posted a new rom with a new rom here with a new build:

http://forum.xda-developers.com/showthread.php?t=436779

I see from the post that jerepelea shared the sys with him, c_shekhar if you're reading this, can you tell us if the files are newer in this rom? I see its still 3.13 ddi but is there a chance there might be a newer disptools in this or is this from another device?

It uses 3.13 DDI and the latest 3D drivers you have released. And I confirm the results are wonderful.. Thanks to you and your all the assciates..

[NeoS]

Great progress guys!
What's the progress with the g810 ddi and disptools?

[Chainfire]

Laurentius is working on figuring some XIP and OEM stuff out, so we can learn the secret of why we can get it to work on one specific Kaiser ROM, but not on any other Kaiser ROM or Polaris.

[NeoS]

Great. So that's our first priority. Make the g810 ddi work. :) I'll see if i can assist in any way tomorrow, right now, i'm gonna hit the shower and the sack. ;)

[bally3]

Tried g810 ddi in c_shekkars rom but no luck.

Anyone managed to find the Xperia rom yet?

[bally3]

I've juust pm'd Sakajati - lets hope he will will share the rom with us.

[pdgpereira]

It uses 3.13 DDI and the latest 3D drivers you have released. And I confirm the results are wonderful.. Thanks to you and your all the assciates..

Hello,

I confirm that this rom is very fast. I'm curious to see a bug free qvga converted png M3d coocked rom with this bild. Right now, even the v2 cab instal runs really smooth.

Congrats!

[nir36]

lol i was just thinking how funny it is that after buying a somewhat problematic device graphicswise... (Polaris with official WM6), we now have a very strong device with the 3D drivers, Manila2D or any other shell..(even TF3D runs almost smoothly) and if 2D Drivers come out.. it'll be like ironman switching his dented mohabian's desert suite to a mega gold-titanium one :)

KUDOS :)

[bally3]

Sakajati does not have the Experia rom it seems.. :(

We'll have to keep on searching...

[NeoS]

I'm probably getting the Touch HD in a few weeks. Maybe it has the 2D driver we've been searching for.

[imfloflo]

@Neos2007 noooooooooooo don't let us alone with your new device..
Don't forget Polaris user :p
Or i'll be oblige to sell mine and bought new phone

[NeoS]

hahaha. I'll keep my polaris. Best thing about this is that i won't have to use it in everyday life. So i can mod away with it. :)

[rogro82]

I am using it for every day life... but i just check my missed calls once a day :D

Dont think my phone is usable for more then 5 mins a day... gf is getting pissed off at my phone..

[bally3]

I am using it for every day life... but i just check my missed calls once a day :D

Dont think my phone is usable for more then 5 mins a day... gf is getting pissed off at my phone..

erm.. you DIDNT buy it to make calls did you? :eek:

Thats blasphemy! we may have to oust you from P3D if you did .. its a toy.. not a phone! :p

[chris.dale]

Hi,
I have one question: Will the 2D driver solve the slow performance when the screen is touched (occurs especialy in games)? I remeber I had this issue even with Hermes.

[Chainfire]

No, that is a touch driver issue...

We've been looking into fixing this as well, and for some devices there is a fix (using a different driver) - but so far not for Kaiser or Polaris :(

[knownboyofno]

found somebody wit a X1 they just need to know how to dump the ROM..http://forum.xda-developers.com/showthread.php?t=437784

[w04g005]

found somebody wit a X1 they just need to know how to dump the ROM..http://forum.xda-developers.com/showthread.php?t=437784

In this forum (http://forum.xda-developers.com/showthread.php?t=406168) they made a backup (Sprite and SPB) from the xperia rom. Is this helpful?
Are there any news about the G810 drivers?
greetings

[chris.dale]

No, that is a touch driver issue...

We've been looking into fixing this as well, and for some devices there is a fix (using a different driver) - but so far not for Kaiser or Polaris :(

Ok, so will there be any development of this touch driver?

[NikMel]

Use the attached file for polaris.
This is previous version of driver. I've included it in my rom and I must say I use it for 3 days and with no freezing but without 3D drivers.


No, that is a touch driver issue...

We've been looking into fixing this as well, and for some devices there is a fix (using a different driver) - but so far not for Kaiser or Polaris :(

DO NOT USE IT AS IS.
Just wait a rom maker who will include this file in his rom.

[Chainfire]

Cool, will test this out. Where did it come from? I think I've tried about 16 different touch drivers by now :) (and let some other P3D team members test them too :D)

[NikMel]

this driver come from wm6.0 of polaris:o

[Chainfire]

No go on Kaiser :(

[SuperJMN]

this driver come from wm6.0 of polaris:o

What use does this driver have? :) Does it fix the high CPU usage when the screen is touched?

[NikMel]

As I can see from my observations it is making easy on cpu.

[NeoS]

I'll try. Let you know my findings. What's sopposed to be better?

[NikMel]

It's not for performance but just to solve the freezing issue of screen.

I'll try. Let you know my findings. What's sopposed to be better?

[NeoS]

Well it solved my slowdowns when touching the screen allright. It makes my touchscreen not react to anything anymore. :p

Do you have the old dll for me? So i won't have to hard reset...

[rogro82]

Ok, so will there be any development of this touch driver?

Thats the main problem of this driver... there is way too much development in it ;)

Htc managed to put all touchflo related crap in it so everytime you touch your screen it wonders if has to recognize a gesture or whatever... Biggest development in this driver will be taking all this crap out :D

[rogro82]

k my screen isnt slowing down anymore like it used to :D

just killed all registrykeys the touch dll references... can someone else try this?

i will try to reproduce what i did

[rogro82]

killed:

Software\drivers\touch and all subkeys
Software\HTC\TouchScroll and all subkeys
Software\OEM\TFLOSettings and all subkeys

thats about it i think... im testing it using lights.exe which seemed to suffer a lot when it was spinning while pressing the screen..

For me it renders like not bein pressed

[imfloflo]

why don't making a listing of all function in this driver and what she does.

[rogro82]

main problem is things arent managed in different functions but more global... its like one big spaghetti :rolleyes: one function with 10000 subs to get through...

So i just did what i like to do most... find anything that reference htc and just destroy it :D

[rogro82]

if deleting works for more people i could patch the dll so people wont have to delete the settings but i would like to know if it works before putting work into it..

[imfloflo]

on which device ?go to irc to talk about it

[Chainfire]

Well test this in a bit (flashing right now)... silly never tried that before, lol. Makes sense. If this is the answer I'll just make a CAB that fixes that stuff up... same thing as hacking the DLL, except we dont have to do it for every device...

[rogro82]

a cab can also work but problem will be to get the values back i you kill them in an installer cab.. or arent you going to kill them in it? i can also make a tool that just renames the entries... will be easy to get them back by the push of a button..

[w04g005]

Do you think the problem with the touch.dll is the reason for slow scrolling in "Programs" or other folders? It makes sense for me when i look at the cpu-meter if i (only) touch the screen.

[torpie13]

Can u upload a cab with the right value for a speed testing purpose.

thanx

[NeoS]

Do you think the problem with the touch.dll is the reason for slow scrolling in "Programs" or other folders? It makes sense for me when i look at the cpu-meter if i (only) touch the screen.

The touch.dll made my screen not respond anymore. But, if you feel like you should test, be my guest.

[HRQ.SLV]

killed:
Software\drivers\touch and all subkeys
Software\HTC\TouchScroll and all subkeys
Software\OEM\TFLOSettings and all subkeys
...
For me it renders like not bein pressed


It did not change a thing for me.
I'm using HomeScreen++ to view the CPU usage, and it still robs a big amount of percentage just by pressing any part off the screen.
But in my humble opinion this can be one of the solutions to increase 2D performance.
Keep up the good work!

[Lukecz123]

After I tried to use touch.dll posted here my screen stops responding too. I also tried to erase 3 registry entries - this caused me no touchflo and PDA was very slow - tested with few games too. SO MAKE BACKUP (Sprite backup saved my ass).So I´m looking forward for working 2d drivers.

[NikMel]

The file that I put here will work if you include it in a rom not by just replace it.

DO NOT USE IT AS IS.
Just wait a rom maker who will include this file in his rom.

[w04g005]

Is anyone working on the imate 85XX or g810 drivers? It became so silent in here.....;-) Can i help you in any way?

[NeoS]

The Imate 85xx drivers seem to be the same as the KS20's. So it didn't add anything to our quest. :(

[spocky12]

NeoS2007, if you or someone else managed to split Imate 85xx IMAGEFR.mbn file into xip/imgfs, would you mind telling me how you did (or giving me a dump), please ? I used hex editor to split it but I surely made mistakes as neither imgfs nor xip dumped successfully :)

I'm also trying to use g810 drivers, but I couldn't get them work on my ks20 :
- updating only ahi2dati+libgles_cm didn't work (despite new ones don't lack any reference, imported or exported function, just add new ones)
- I've came to the conclusion that I needed to update ddi/disptools also, but new disptools refers to "memory_barrier" into smem that my smem doesn't have.
- I've tried renaming g810 smem to smef and changing reference from disptool from smem to smef with no success
- To be sure, I tried to duplicate my own smem to smef and change my own disptool smem reference to smef (which is exactly the same, if you've followed me), but it didn't boot either.

I know some people here made 3d drivers for your device, do you have any idea or advice please ?

[NeoS]

If i've read it correctly, NuShrike mentioned the KS20 has the driver natively, which means the 3d should already work. As i recall the Polaris driver is based on some files from the KS20, so yeah... But for 2D we haven't found ANY device who's better yet... We did however find someone who dumped the g810 rom correctly here: http://forum.xda-developers.com/showpost.php?p=2763353&postcount=1503

[spocky12]

Thanks NeoS2007 for your answer.
I'm asking this because it seems that ks20 drivers has some issues (some people complain about a few apps not working as they should or crashing, but working good with samsung software acceleration driver). So I'm trying to fix this.
Moreover, ks20 has some more issues I'd like to address : voip not working (I can hear people I call, but they just hear really choppy sound from my ks20, and thus can't understand a word I'm saying), very low (30Mb) free ram after fresh boot on clean rom, slow memory access (2 to 4 times less than htc devices with spb benchmark)...

As Lg doesn't update their rom, I think to only way to fix this is to try other devices drivers from similar devices (I know there are lots of chances it doesn't work, but I haven't found any other solution so far). Unfortunately, htc has a really specific drivers structure and dependancies, but G810 is really close to what I have on my ks20 (but I had no luck with most of their drivers). I was hoping Imate 85xx could provide some more things for me to test.

[qwasdenn]

edit: sorry, wrong thred ^^

[secoseco]

Hi 2D Driver Development Team

I follow up this thread every day to see the latest news of 2D driver development, and I feel that there is no any progress in that

if you please, can you explain where you are now, and is there hope to see 2D driver for Polaris

thx

[NuShrike]

there is no any progress in that
if you please, can you explain where you are now, and is there hope to see 2D driver for Polarishttp://forum.xda-developers.com/showthread.php?p=2820868#post2820868

[secoseco]

http://forum.xda-developers.com/showthread.php?p=2820868#post2820868

I know that is not Disneyland or you have Alaa Eldin Lamp and know that I talk to developers not magicians and I expect the answer has the responsibility and limited easy, nice words

[NuShrike]

Anybody work with armasm much and linking to coredll?

I can't get some bits of asm to resolve COREDLL_1875, COREDLL_1876, COREDLL_1877, __2_YAPAXI_Z, and __3_YAXPAX_Z which should be in coredll.dll.

one example:
import __2_YAPAXI_Z
MOV R0, R5 LSL #2
BL __2_YAPAXI_Z ; operator new(uint)
error LNK2001: unresolved external symbol __2_YAPAXI_Z

[NuShrike]

Solved some of this, needed:

IMPORT |__imp_??2@YAPAXI@Z|
__2_YAPAXI_Z
LDR R12, =|__imp_??2@YAPAXI@Z|
LDR R12, [R12]
BX R12

[NeoS]

NS, what does that solve?

[Venigo]

So how is the project going so far.

Any updates?

[paede]

i think all developer change to the android porting project

[killerjohn]

i think all developer change to the android porting project

does it have a topic (Android porting...) ?

[Petulinek]

Android porting? Its not good message...
2D drivers nothing... 3D drivers are not good, little working, but TF3D freezing on display off... :(

[bally3]

There has been a lull in the driver development activity for the last few weeks, I've been busy with work and life as I'm sure the others have. I'm sure the development will continue in due course, though we have come across complications with the 2D driver project.

Relax people... We do this in out spare time with no financial gain. And we all have lives outside of xdevs :)

[goldenguy111]

i have been following this thread from post 1 as well, and all those 'rushing' the devs or seemingly 'demanding' results are not doing anything to aid with the project. a lot of these fine people are working behind the scenes, doing what they can. this is not a gimme gimme forum. if and when they get results, they'll post them, as they have for their other projects. have a good day all.

[HRQ.SLV]

There has been a lull in the driver development activity for the last few weeks, I've been busy with work and life as I'm sure the others have. I'm sure the development will continue in due course, though we have come across complications with the 2D driver project.

Relax people... We do this in out spare time with no financial gain. And we all have lives outside of xdevs :)

We've all been missing you around here.
Thank God you're still alive!:D:D:D

[bally3]

We've all been missing you around here.
Thank God you're still alive!:D:D:D

Thank you for the kind words HRQ-SLV :)

I've been reading some of the other forums on current developments and noticed some of the ugliness that haunts xdevs with great sadness.

I'm proud and feel privileged to be a Polaris user and on this forum and still maintain that Polaris users on here are the friendliest people on xdevs, which is why I'm sure I'll be staying here for a long time to come.

[secoseco]

There has been a lull in the driver development activity for the last few weeks, I've been busy with work and life as I'm sure the others have. I'm sure the development will continue in due course, though we have come across complications with the 2D driver project.

Relax people... We do this in out spare time with no financial gain. And we all have lives outside of xdevs :)

Thank you for the kind words HRQ-SLV :)

I've been reading some of the other forums on current developments and noticed some of the ugliness that haunts xdevs with great sadness.

I'm proud and feel privileged to be a Polaris user and on this forum and still maintain that Polaris users on here are the friendliest people on xdevs, which is why I'm sure I'll be staying here for a long time to come.


Hi bally3

thank you for feeling of responsibility and the answer with easy nice words

[NeoS]

AFAIK there's still no better development driver spotted online. I guess the new devices like the Xperia (also MSM7200) could aid in development (if the files in there are better optimised)

[imfloflo]

Hey Neos2007, i hope new device coming soon with new better driver.
If there are new device they must have develope new driver and don't use the old one, i hope.

for information : with M-Amine we have found the bug of bottom tab bar on tf3d it's propably due to the FRA language files.

[deechte]

[..] noticed some of the ugliness that haunts xdevs with great sadness.[..]

Great to see you back here Bally3. What ugliness are you talking about?

[NuShrike]

Reanimated test DDI.dll posted (you know where). Looking for a KITL dump of why it doesn't work.

[rogro82]

First error seems to happen here:

Data Abort: Thread=8630fa68 Proc=803a8150 'gwes.exe'
AKY=00000021 PC=786049d0(ddi.dll+0x000249d0) RA=786049c8(ddi.dll+0x000249c8) BVA=e59fc004 FSR=00000805

Then a lot of:

Prefetch Abort: Thread=8630fa68 Proc=803a8150 'gwes.exe'
AKY=00000021 PC=e12fff1c(???+0xe12fff1c) RA=80019560(NK.EXE+0x00019560) BVA=e12fff1c FSR=00000805

[NuShrike]

Fixed? version posted.

[SomethingWicked]

Xperia (also MSM7200) could aid in development

Hi neo, I'm considering getting an X1. If I end up with one, I'll let you know, and provide dumps...

BTW... where did you get your blackstone? I'm considering one of those as well... thanx..

[w04g005]

Hey guys,

this goes to anyone out there who is still working on the 2d drivers. I received an e-mail from toshiba support team. they said tomorrow there will be a new update for the g810!
maybe it's useful. http://www.toshiba.co.jp/product/etsg/cmt/english/asian/g810/g810_rom.htm

Is there still development?

greetings

[NuShrike]

Thanks for the G810 heads up.

[NuShrike]

rev4 DDI posted.

[NeoS]

Nice, NS. what's the big change? once i get home i'll have a look

[bally3]

rev4 DDI posted.

hi ns.. where was this posted?

[robertus3d]

Thanks a lot for your hard work guys!:)

[wooky-]

Good luck guys, and thank you !:)

[dwaradzyn]

Some users have said that this ROM has incredibly good scrolling. You can check it out here:
http://forum.xda-developers.com/showthread.php?t=447699

[NeoS]

That's a rom based on older ddi. What the team's trying to do is fix stuff inside the new ddi or bypass certain code.

[belabartok]

is it dead?

[FlaTEriC18041983]

is it dead?

would be very interesting to know indead :confused:

[bally3]

Yes this project is dead.

Unfortunately the development work required to create a 2D driver was too great for any single developer on xdev to tackle on their own. Due to the nature of xdevs, talented developers move onto newer devices as they purchase them and that leaves older devices with less and less development potential.

NuShrike and Rogro82 both pledged to help on this project (I believe Rogro82 is still tinkering with the touch screen issue) but both devs requested that more developers come on board as they would be unable to take on the workload involved by themselves (fair comment - we all have lives). After many requests for more developers to come on board with little interest the project has been abandoned. There was some success with the Kaiser and te G810 ddi file but I believe has also been abandoned.

There are lessons to be learnt from this project and I hope xdev users will take them on board:

Firstly, Programmers are not the only DEVELOPERS who work hard on projects. There are many developers like myself and Neos2007 who work hard in the background, researching, testing and a huge amount of support and administration work which is as time-consuming if not more than the actual programming development work that is done. This should be recognised and appreciated as development work and if donations links are added to signatures, consider a donation - dont insult them and then wonder why projects are abandoned because developers leave in disgust - That lesson should have been learnt by Polaris users just by reading the Kaiser threads - we can and should be better than that. The Polaris forum has been the envy of xdevs - this is from the many pm's I've had from users on other forums wishing they had the development activity we have enjoyed - dont let a few rotten apples spoil it for everyone else - If you like what we do - tell us, if you dont - keep it to yourself.

Secondly, I have a great amount of respect for xda developers as a forum, but I have noticed over the last few months that more and more development is shifting to irc with xdev used for notification only. I think irc has its place and its a great tool for communicating faster when required but my personal opinion is a successful xdevs project is better kept on xdevs where it belongs with irc used for communication as required. The issues with irc are well known for project control issues, as seen with the Android project recently which cause projects to collapse. This was also partly the case with the 2D driver project apart from the lack of devs issue. Keeping a project on xdevs allows for more user interaction, its historical and easy to pick up from and as we proved with the 3D driver project has a much higher rate of success as theres less chance of arguments of project control.

A successful project requires a well constructed project team and also developers who are willing to commit the time and energy required to see it through. There are plenty of talented developers in the Polaris forum, but they are either unwilling or unable to commit the time required to undertake projects.

I hope more developers will take the time to contribute to our projects and I hope more users will also donate to developers as well as to rom cookers to keep projects like these going.

Regards

Bally3

[imfloflo]

Too bad ... Must buy new device and open a new thread to developpe new driver on it

[NuShrike]

I haven't given up. Just taking a vacation since driver work has taken 8 months of life and wasn't the goal ... :P

Problem was there was no dev device to go around for a-hard-reset-per-change for 2D driver tests. Too painful on one phone, and it's not like people actually donated much to the effort.

That bounty was all hot air.

So far, QVGA is still the way to go if you want speed. Tests on the new Raphael have been disappointing even if the UI is more responsive.

[NeoS]

What Bally3 just said pretty much sums it up. We've put alot of time and effort in the 3D (and 2D) projects and a after a while (especially with all these new devices from HTC) people started to lose interest.

I'm still working with these people to get better results out of most HTC devices, so i've not completely abandoned this project. I just don't have a Polaris to test it on anymore.

[rhov23]

What Bally3 just said pretty much sums it up. We've put alot of time and effort in the 3D (and 2D) projects and a after a while (especially with all these new devices from HTC) people started to lose interest.

I'm still working with these people to get better results out of most HTC devices, so i've not completely abandoned this project. I just don't have a Polaris to test it on anymore.


If I knew that I could help in any way I would, but I thought this driver development was happening in the shade...

[boart]

I really appreciate to all people that work on the 2d and 3d project. I hope, that we will see a nice rom with a smooth 2d and a manila 3d :) If we get this, we will have to raise a monument for all your work!!!!!

by the way.. for the work, all you guys have done so far, we also have to be very thankful.
THX for ur work :D

[FlaTEriC18041983]

Hi, sorry for answering that late, wasn't sent a mail that there has been a response :confused:

@bally3, nushrike and neos2007
The problem with HTC's new devices is clear to me, but what I cannot understand is that rush on those, after all HTC did in the past. I personally can't afford buying a new device every year. And as my Polaris just got 10 months old (back then, it was brand new), I don't want to buy a new one by now.
The point is, I think there are still many people like me still wanting their Polaris-performance to be improved, because they don't plan to buy another 500EUR-device hoping its performance will be better.
I really estimate your work, and if you would continue working on the 2D-project resulting in a real improvement of the usability of the Polaris, I would donate 50EUR.
I know the donation-principle works the other way around: donations have to be made to cover the costs of the developers. But I hope you can understand that I don't want to invest in such a project, not knowing if there will ever be a result.
So not to be misunderstood, once again, I really appreciate what some persons here at xdevs are doing, and I would never insult somebody working on such a project (bally3 mentionned something like that).

Well, that's what I wanted to say,
now I wish Merry Christmas and a good start into 2009

best regards,
eric