Quote:
Originally Posted by bast525
SCOTT - I'm hoping... man I hope to God I can get you to take a look at this. One thing I have HATED about the Touch Pro since I got it, and even your ROM didn't fix, is that for whatever reason, the graphics drawing/rendering in Landscape mode is FAR worse than when the phone is in Portrait mode. I had noticed it in Opera Mobile and Mini and a few other apps, and then confirmed it using some benchmarking software (the Bitmap Draw test in SK Tools in particular). The phone renders some 30% slower in Landscape mode! This is noticeable as a drop in frame rate and as Vsync tearing.
At any rate, I ran across a thread on XDA that is about this specific issue, and a few people posted how a new custom ROM from Da_G specifically for the AT&T Fuze, had new drivers that finally fix this problem. Not only is it claimed to fix the Landscape redraw, but it is supposed to be a nice boost in overall graphics performance. I sent him a PM to ask about getting the drivers, but he said the main file which fixes this, ddi.dll (which is from new Diamond official ROMS, and he also apparently uses some Blackstone/Touch HD files), is now part of the XIP and is not a file you can simply post for people to write over their existing driver with. He did say that the file is easily extracted from his XIP for cooking into other custom ROMS.
I wanted to ask... no... BEG... if there is any possible way you can get this ddi.dll (and other graphics drivers such as d3dm_ati.dll and disptools.dll) into your kitchen so that we too can enjoy the increased graphics performance, and, more importantly, no more huge loss in performance in Landscape mode. Is there ANY way you can do this? I would be glad to beta test this... until now I basically treat my TP like a Diamond... I never use the hardware keyboard because the performance in landscape is so bad!
|
Putting it in the XIP won't make it any faster by itself. Turning it into a module will. Currently, the default d3dm.dll is a module. If you install a cab with a new .dll (like d3dm_ati.dll) it probably won't be any faster since that isn't a module. You would need to make it a module, fit it into the virtual memory space, and cook it into the ROM. Assuming the default d3dm.dll, the d3dm_ati.dll and Samsung Omnia driver (d3dmxsc50pb.dll) are all roughly the same size, you should modularize all of them into the same VM space, then in the kitchen select only one.
But correct me if I am wrong - D3D is for 3D rendering only. What we need to speed up is 2D rendering - and that's DDRAW.DLL (again, already a module). We need a faster DDRAW.DLL. Then again, TF3D makes mostly calls to the 3D rendering DLL (as specified in the registry), not the 2D... So really we need both?