yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] NeoS:
Direct Draw explained

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.
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] 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.

DO NOT USE IT AS IS.

Just wait a rom maker who will include this file in his rom.
[Touch Cruise ROM Development] 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)
[Touch Cruise ROM Development] NikMel:
this driver come from wm6.0 of polaris:o
[Touch Cruise ROM Development] Chainfire:
No go on Kaiser :(
[Touch Cruise ROM Development] SuperJMN:
What use does this driver have? :) Does it fix the high CPU usage when the screen is touched?
[Touch Cruise ROM Development] NikMel:
As I can see from my observations it is making easy on cpu.
[Touch Cruise ROM Development] NeoS:
I'll try. Let you know my findings. What's sopposed to be better?
[Touch Cruise ROM Development] NikMel:
It's not for performance but just to solve the freezing issue of screen.
[Touch Cruise ROM Development] 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...
[Touch Cruise ROM Development] rogro82:
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
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] imfloflo:
why don't making a listing of all function in this driver and what she does.
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] 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..
[Touch Cruise ROM Development] imfloflo:
on which device ?go to irc to talk about it
[Touch Cruise ROM Development] 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...
[Touch Cruise ROM Development] 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..
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] torpie13:
Can u upload a cab with the right value for a speed testing purpose.

thanx
[Touch Cruise ROM Development] NeoS:
The touch.dll made my screen not respond anymore. But, if you feel like you should test, be my guest.
[Touch Cruise ROM Development] HRQ.SLV:
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!
[Touch Cruise ROM Development] Lukecz123:
Screen not responding

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.
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] w04g005:
Is anyone working on the imate 85XX or g810 drivers? It became so silent in here.....;-) Can i help you in any way?
[Touch Cruise ROM Development] NeoS:
The Imate 85xx drivers seem to be the same as the KS20's. So it didn't add anything to our quest. :(
[Touch Cruise ROM Development] 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 ?
[Touch Cruise ROM Development] 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://xdaforums.com/showpost.php?p=2763353&postcount=1503
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] qwasdenn:
edit: sorry, wrong thred ^^
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] NuShrike:
http://xdaforums.com/showthread.php?p=2820868#post2820868
[Touch Cruise ROM Development] secoseco:
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
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] NeoS:
NS, what does that solve?
[Touch Cruise ROM Development] Quilapvd:
So how is the project going so far.

Any updates?
[Touch Cruise ROM Development] paede:
i think all developer change to the android porting project
[Touch Cruise ROM Development] killerjohn:
does it have a topic (Android porting...) ?
[Touch Cruise ROM Development] Petulinek:
Android porting? Its not good message...

2D drivers nothing... 3D drivers are not good, little working, but TF3D freezing on display off... :(
[Touch Cruise ROM Development] 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 :)
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] HRQ.SLV:
Welcome boss!

We've all been missing you around here.

Thank God you're still alive!:D:D:D
[Touch Cruise ROM Development] bally3:
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.
[Touch Cruise ROM Development] secoseco:
Hi bally3

thank you for feeling of responsibility and the answer with easy nice words
[Touch Cruise ROM Development] 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)
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] deechte:
Great to see you back here Bally3. What ugliness are you talking about?
[Touch Cruise ROM Development] NuShrike:
Reanimated test DDI.dll posted (you know where). Looking for a KITL dump of why it doesn't work.
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] NuShrike:
Fixed? version posted.
[Touch Cruise ROM Development] SomethingWicked:
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..
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] NuShrike:
Thanks for the G810 heads up.
[Touch Cruise ROM Development] NuShrike:
rev4 DDI posted.
[Touch Cruise ROM Development] NeoS:
Nice, NS. what's the big change? once i get home i'll have a look
[Touch Cruise ROM Development] bally3:
hi ns.. where was this posted?
[Touch Cruise ROM Development] robertus3d:
Thanks a lot for your hard work guys!:)
[Touch Cruise ROM Development] wooky-:
Good luck guys, and thank you !:)
[Touch Cruise ROM Development] dwaradzyn:
Some users have said that this ROM has incredibly good scrolling. You can check it out here:

http://xdaforums.com/showthread.php?t=447699
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] belabartok:
is it dead?
[Touch Cruise ROM Development] FlaTEriC18041983:
would be very interesting to know indead :confused:
[Touch Cruise ROM Development] imfloflo:
Too bad ... Must buy new device and open a new thread to developpe new driver on it
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] rhov23:
If I knew that I could help in any way I would, but I thought this driver development was happening in the shade...
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] 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
[Touch Cruise ROM Development] retsam88:
Too bad that nice ideas are being dropped..
[Touch Cruise ROM Development] alaamac199:
It's really too bad to kill such a great project ..

and apperently great job was done by alot of people ..

Anyway it worthed a try ..

and I wish I saw the thread earlier so I would 4 sure have helped in someway ..
[Touch Cruise ROM Development] bally3:
If you're a developer we sure could use you on the Android project (see sticky thread). The kernel is booting and we just need a few drivers (wifi, gps etc) doing to make it usable day to day.

We may come back to this project once the Android kernel is finished.. depends how many devs are left to work on it.
[Touch Cruise ROM Development] x_coRe_x:
It's a good news :)
[Touch Cruise ROM Development] norazmi_0673:
Hope hear from u guys VERY SOON....wish your project on android is a successful one!!!
[Touch Cruise ROM Development] alaamac199:
well .. I'm not a developer actualy ..

but I meant sth like testing since I have a kaiser ..

besides there might be other stuff which don't need a developer to do it i.e. searching ...
[Touch Cruise ROM Development] dany547:
it is possible to implement the 2d drivers for Kaiser?
[Touch Cruise ROM Development] c3ro:
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
[Touch Cruise ROM Development] 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. :)
[Touch Cruise ROM Development] bally3:
Thanks c3ro.. downloading and checking now..
[Touch Cruise ROM Development] 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. :)
[Touch Cruise ROM Development] bally3:
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.
[Touch Cruise ROM Development] 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 :)
[Touch Cruise ROM Development] c3ro:
hi,

did you already tried this? >> http://xdaforums.com/showpost.php?p=2562972&postcount=164
[Touch Cruise ROM Development] jerpelea:
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
[Touch Cruise ROM Development] NikMel:
c3ro,

Its not possible to make a rom when this dump is not complete.
[Touch Cruise ROM Development] bally3:
its not the ddraw from diamond.. its the ddraw from g810.

and the answer is here.. trust me! :)
[Touch Cruise ROM Development] bally3:
NiKMel, Glad to see you on the case my friend :)

Definitely need your insight into this to get it moving.. !
[Touch Cruise ROM Development] bally3:
Please continue in this thread - Thank you :)
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] bally3:
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! :)
[Touch Cruise ROM Development] 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.
[Touch Cruise ROM Development] bally3:
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.
[Touch Cruise ROM Development] 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 ;)