yashsingh1/xdaforums huggingface dataset:
[Touch Cruise ROM Development] Chainfire:
As I posted before - we can extract the files, but the dump is not complete. It's just missing files and such.

Edit: perhaps the "pdocread" method should be used instead of grabit?

Edit#2: for the "pdocread" method, see this old post of mine: http://xdaforums.com/showpost.php?p=1718401&postcount=51 It has instructions for dumping Part02, but you should be able to figure out how to dump Part00 and Part01 as well if you read the instructions carefully and look at the command. We'd want Part00, Part01 and Part02. Likely either Part00 or Part01 dumping will fail - that's ok, we usually want the 00/01 that _doesnt_ fail :) Unsure if this method works at all for Toshiba, but I think so. If you need further assistance, just post the output of "pdocread -l" here, as well as the commands you used. (Note I will not be checking in much to this forum the next couple of days, so response may not be very fast)
[Touch Cruise ROM Development] bally3:
The only way I know is the pdocread method.. I'll post the link to it when I find it.

[Edit] CF beat me to it lol :D
[Touch Cruise ROM Development] NikMel:
There is no video driver in this file even if someone can fully extract this dump.

We need a dump of pdocread.
[Touch Cruise ROM Development] bally3:
I've started a thread for the 2D driver as this thread is for 3D driver development:

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

Please post in there for the rom.. I'll post the dump link in there too.

Thank you :)
[Touch Cruise ROM Development] spellshaper:
Sorry for bad topic... delete please
[Touch Cruise ROM Development] bally3:
Please kindly move this post to the correct thread - this is a development thread and there is a thread for the 3D driver related issues here:

Team P3D Driver questions and issues thread

Thank you.
[Touch Cruise ROM Development] bally3:
This is "ver 1" release of the cab. It is not beta.

It is also NOT the FINAL version of the driver - (I hope!)

There are no differences to the updated drivers that were sent out to the Chefs recently - seen in Itje's 3.6 and Opal Roms, M-Amine's 2.0 and PharQuangs rom (dont mention it PharmQuang :rolleyes: )

The cab was released as we (Team P3D) had agreed through the CA site in recognition of their work in creating the driver that we ported to the Polaris.
[Touch Cruise ROM Development] NeoS:
I'd like to ask users who ALSO have a Diamond or Touch Pro to check their registry for a key. HKLM\system\d3dm\drivers. What keys are there and what are they?
[Touch Cruise ROM Development] ravest:
i have a diamond with a cooked rom

i don't know if it's of any help, but in that path i only have

LocalHook

D3DMXSc50PB.dll

ROM: Swtos V1.6 Full LM WWE
[Touch Cruise ROM Development] bally3:
Thanks ravest... being cooked wouldnt make a difference I dont think.. I wouldnt think swtos would take out the hooks from registry.
[Touch Cruise ROM Development] NeoS:
Thanks to Lexi1986 we have a registry dump of the diamond, so we can compare some keys with our polaris.
[Touch Cruise ROM Development] lexi1986:
I hope this will help. If i can do anything for you guys just ask me. I hope that TF3D will work on the polaris :)
[Touch Cruise ROM Development] BigKvak:
I try pdocread to dump Toshiba rom... But is not working(((
[Touch Cruise ROM Development] NikMel:
BigKvak,

Did you use -p option?

like:

pdocread -p Part03 dump.bin

or

pdocread -p Part02 dump.bin
[Touch Cruise ROM Development] Chainfire:
please try the following commands:

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...
[Touch Cruise ROM Development] NikMel:
Chainfire,

I think part03 is good to go.

Some times dumping disk is causing some problems.
[Touch Cruise ROM Development] bally3:
Hi guys appreciate all the effort thats going into this rom dump but can we continue this 2D quest into this thread please?

Polaris 2D Driver Development : http://xdaforums.com/showthread.php?t=435190

Thanks :)
[Touch Cruise ROM Development] BigKvak:
Yes! I do it!

Here the links:

http://rapidshare.com/files/152983331/part0.rar.html

http://rapidshare.com/files/152983675/part1.rar.html

http://rapidshare.com/files/152985252/part2.rar.html

http://rapidshare.com/files/152987228/part3.rar.html

I install ManilaQVGA (http://xdaforums.com/showthread.php?t=430718) to Toshiba G810... and It's working VERY fast! More faster then Polaris(
[Touch Cruise ROM Development] NikMel:
Thank you!!

This is what we need and now comparing and testing
[Touch Cruise ROM Development] Chainfire:
Well done :)
[Touch Cruise ROM Development] NuShrike:
some credits that need to be named in all of this Not to be Forgotten:

Nikmel for starting this whole thing by making a working rom with the Kaiser DDI 3.28 and current other dumps

Rogro82 for making the ReleaseDC() breakthrough that brought high-FPS back again to the HTC-CA drivers

Bally3 for organizing and keeping things sane
[Touch Cruise ROM Development] NeoS:
So... what happened here?
[Touch Cruise ROM Development] rogro82:
Thanks for the credits ns but most credits go out to you in this case... like is said earlier in another thread.. the best i can do is come up with ideas because the core ( assembly ) stuff isnt a thing i can help with for now. Still have a lot of reading to do since i am about half a year behind...
[Touch Cruise ROM Development] bally3:
Core (assembly) stuff may not be required as much - read said other thread ;)

We still need you Rogro!
[Touch Cruise ROM Development] alperak:
pardon hello bro.. will not we play video 640*480 in Polaris ? or we will play only 240*320 size video ? sorry for my english....
[Touch Cruise ROM Development] bally3:
Wrong thread - please repost here:

Polaris 3D Driver issues and updates
[Touch Cruise ROM Development] NeoS:
Hey guys, check this out:

http://xdaforums.com/showpost.php?p=2800056&postcount=928
[Touch Cruise ROM Development] NeoS:
Can anyone look into this: http://xdaforums.com/attachment.php?attachmentid=123561&d=1224559009 ?

It's supposedly a driver made by a company what's been bought by Nvidia.
[Touch Cruise ROM Development] namaste74:
You guys following the Xperia threads, someone posted some of the video drivers in post 46? Not sure if you have seen them.

http://xdaforums.com/showthread.php?t=431085&page=5
[Touch Cruise ROM Development] Chainfire:
Problem is different resolution :(
[Touch Cruise ROM Development] namaste74:
Ah yes, didn't think about that.
[Touch Cruise ROM Development] imfloflo:
Hye guys have you look manilla.exe with ultraedit i found some thing maybe it's interessant or not
[Touch Cruise ROM Development] rogro82:
These are just some imported functions. A hex-editor wont get you anywhere if you really want to look whats happening...
[Touch Cruise ROM Development] itje:
here is ddi from jade.
[Touch Cruise ROM Development] bally3:
Thread re-opened as we seem to have renewed interest and an interesting lead from iriki :) (Read Neos's updates thread)
[Touch Cruise ROM Development] itje:
Im not sure if this can be the right place, but I have dumped the new Jade rom (touch 3g) and if there is any files in there you guys wanna have a look at I will upload them for you :)
[Touch Cruise ROM Development] amarguli:
Touch 3G dialer

Hi itje,

Is it possible to extract the dialer from this ROM? Does it support video call?
[Touch Cruise ROM Development] NeoS:
Of course itje. I hope rogro or the others of the team are looking at that ddi.dll you posted earlier. That should conclude the files we might or might not need. I don't have the dependancies checker on my lappy. ;)
[Touch Cruise ROM Development] iRiKi:
Wow nice, many thanks :) Hope i won't get crucified here because i don't own a Polaris, but a mere Diamond, tho i think we can all benefit from the joint works of dedicated ppl like you guys.

Q: what 3D games are expected to run on the Polaris?

A: all 3D games that are compatible with the OpenGLES CM specification, like CoD2 or Quake3.

for CoD2 just follow the instructions on this thread: http://xdaforums.com/showthread.php?t=428703, copy the libgles_cl.dll from the polaris drivers (which sits in \Windows) and run the cod2_goforce.exe.

For Quake3 it's way easier if we skip the instructions on my Diamond thread and just download this full package: http://rapidshare.com/files/151627147/q3ce-1.1a-release-armv4-diamond.zip.html. Again, like Cod2, copy the libgles_cm.dll from the polaris drivers to that q3 folder. sometimes q3 crash after a few minutes, sometimes it crashes after a few seconds, so make sure you have the maximum memory available and the least processes running.

Ow, and you can also try the ChopperFight.ARM.CAB, after installing the cab copy the libgles_cm.dll to the install dir, rename the libgles_cm.dll to libgles_cl.dll (that's an "L" in bold) and enjoy the app in fully 3D mode.

The important part related to the development of the libgles_cl driver is posted on the other thread.. should i re-post it here, or if some friendly mod can move it to here, feel free to do it.

Thanks again to reading all of this \o/
[Touch Cruise ROM Development] NeoS:
Well, this is the development thread, so all relevant info on developing is welcome. feel free to repost.

Update on my side: I've done something terrible. I've bought a Blackstone. I still have my Polaris though. Don't know how long that will last...
[Touch Cruise ROM Development] deechte:
:eek: Oh no! Everybody's leaving! Is there still anyone out there? Anyone?
[Touch Cruise ROM Development] imfloflo:
NOoooooo why you bought this, all cooker and chef with polaris go to diamond or blackstone :( I think i 'll buy soon it too.
[Touch Cruise ROM Development] maxniper:
yap i think i will buy one too
[Touch Cruise ROM Development] NeoS:
Well, i ran GLbenchmark on my Blackstone. Results are... kind of depressing. lol. I expected it though. Anyone interested in developing a driver upgrade for it? :P

edit: here's the result: http://xdaforums.com/showthread.php?p=2867901#post2867901
[Touch Cruise ROM Development] maqui01:
is it a huge different talking about the screen?? I mean, watching a movie or something is totally different or it's kinda the same?

pd: I posted in the blackstone forum the same message but i wanted to do it here... I misplaced the post :P sorry.
[Touch Cruise ROM Development] belabartok:
I hope at least they don`t leave without developing the 2d drivers
[Touch Cruise ROM Development] NeoS:
I have to say, after a few hours of working with the device, i've never had any faster and smoother device before. In terms of benchmarks it isn't really fast, but who cares? I can scroll my menus really fast, watch video without any stutter or hicks and the screen is SO much better than my Polaris.

But that doesn't mean i'll abandon the project. ;)
[Touch Cruise ROM Development] maxniper:
noooooo, please don't abandon us
[Touch Cruise ROM Development] NeoS:
As i said before, i won't abandon this project just because i bought a new device.

I've dug up some info on the thing we're trying to get working on our devices. OpenGLES CL/CM.

I figured, as long as we know what the technique needs for it to work, it would be easier to fix those things that are needed. Right? ;)
[Touch Cruise ROM Development] iRiKi:
common = OpenGL|ES CM

common lite = OpenGL|ES CL

so if CL only supports fixed-point but CM supports both floating point data type and fixed-point, i don't see great difficulties in coding a libgles_cl.dll (that is, if you're the coder of libgles_cm.dll heh)

:D
[Touch Cruise ROM Development] NeoS:
Let me get this straight, libgles_cl.dll is practically only a part of libgles_cm.dll then?
[Touch Cruise ROM Development] Quilapvd:
That should it be.

Check this out >

Click and Click

Both going about Opengl ES and maybe you could get some information from that pages.
[Touch Cruise ROM Development] gregy74:
New ROM 3.18, with new DDI 3.18

http://rapidshare.com/files/162700070/DDI.rar.html
[Touch Cruise ROM Development] NuShrike:
You can probably just redistribute _cm as _cl.

The problem is some Axim programs (aka Intel 2700G) have the DLL ordinals hardcoded (Virtual Pool for instance), so unless the _cm's ordinals match up with whatever the Axim program thinks it is, it's not going to work.

You may be would need the .lib link file the i2700G file used and reproxy, or reexport, the _cm .dll with the ordinals in the right order.
[Touch Cruise ROM Development] iRiKi:
without the libgles_cl file all are nothing but assumptions. what do we need to compile it ?
[Touch Cruise ROM Development] NeoS:
As far as i know, no other msm7200 device has the libgles_cl.dll. Maybe someone can look into their device and see if libgles_cl.dll is there? We could at least look at it, right?

Oh and what's that about DDI.dll 3.18? Any new stuff? :)
[Touch Cruise ROM Development] adrenalynik:
In 3.18 there isn't DDI.dll....:(
[Touch Cruise ROM Development] NuShrike:
We might be able to reverse the ordinals from the _cl version of GLBenchmark actually, assuming it didn't strip the import names.
[Touch Cruise ROM Development] w04g005:
Where did you search the ddi? It has to be in the Windows folder!

But gregy74 posted the ddi 3.18 from this ROM

http://xdaforums.com/showpost.php?p=2887739&postcount=4

greetings
[Touch Cruise ROM Development] c_shekhar:
here is ddi.dll 3.18

find it here..............
[Touch Cruise ROM Development] NuShrike:
How's the SPB Benchmark?
[Touch Cruise ROM Development] NeoS:
Won't run on M-Amine's 2.0. So anyone else without a custom rom want to try it?
[Touch Cruise ROM Development] gregy74:
Graphic test: DDB BitBlt: 1ms

DIB : 8ms

GAPI : 2ms

Arkaball frames per sec: 6ms

That was tested with offical 3.18 ROM
[Touch Cruise ROM Development] NuShrike:
Wow, that's really fast. As fast or faster than the previous one, and blows away the Kaiser's.
[Touch Cruise ROM Development] NeoS:
What's the course of action in this? Checking the dependancies on ddi 3.18 to see if it works with out current driver, or reverse engineer the CL stuff in GLBench?

EDIT: Could any rom chef do me a small favour and make a development rom for this? It would be great of we'd have a rom without the drivers cooked in, but with some tools like Total Commander or any registry editor and the 3d testing-applications like Lights.exe and others. And disabling error reporting and all those other annoying stuff. It would make hard-resetting WAY easier, because i've hard-reset my device more than 20 times already.
[Touch Cruise ROM Development] bally3:
Tested 3.18 with current 3D drivers - works with the drivers - havent noticed any hiccups - still stable with c-shekkars rom I'm using. I actually thought it felt slower in use so I ran GLBenchmark - swapbuffers have dropped by a stonking 130+ frames to 224.9 fps!

Going back to old ddi for the time being until shekkar updates his rom.
[Touch Cruise ROM Development] bally3:
The file size of 3.13 and 3.18 is exactly the same.. can someone else confirm this?
[Touch Cruise ROM Development] w04g005:
Hey Bally,

Petulinek mentioned it

http://xdaforums.com/showpost.php?p=2888252&postcount=6

What does this mean?
[Touch Cruise ROM Development] NeoS:
It could mean that this new ddi doesn't improve much. Maybe even nothing.
[Touch Cruise ROM Development] c_shekhar:
yes both sizes are same (286720 bytes). And according to the tests by bally3 the frame rate falls down. Does it means two things..

1. Either we abandon the ddi.dll_3.18 and get back to ddi.dll_3.13 or

2. need to make changes in the 3D set of drivers developed by the great team.
[Touch Cruise ROM Development] Quilapvd:
But if it doesn't improve nothing why should they release a new version?

It must have some new improvements/fixes, else it won't be released.

I think there is some updating is needed for the 3d set of drivers what c_shekhar already said.

1. Strip the new ddi searching what's the difference.

2. If there are some changes at functions we need to update the drivers.
[Touch Cruise ROM Development] gregy74:
I am using this latest 3.18 ROM last few days.

I tested few movies with Coreplayer-qtv:

Kate and Leopold 101%

Taken, xvid, alliance 75%

National Security 90%

I don't know, but I thionk that video playing is better.

I also tested light.exe with this ROM. Lights work, about 2 frames per second.
[Touch Cruise ROM Development] NeoS:
Now this is great news. If this really happens, it would mean that (if reverse engineered) Qtv should be accessable for all Qualcomm devices. Which means high quality video playback. ;)

Here's hoping they make it that way.
[Touch Cruise ROM Development] imfloflo:
Really great news, more work todo,for Poalris 3D TEAM but finally we can have a full working polaris at 100%.
[Touch Cruise ROM Development] iRiKi:
that would be a great achievement. however, once it's done for the polaris, what chances are to "port" libgles_cm.dll from the Diamond ? what can i do more to help you ?
[Touch Cruise ROM Development] NeoS:
Anyone tried this application for testing?

http://service.futuremark.com/orbmobile/spmarkjavaweb/index.jsp
[Touch Cruise ROM Development] kolibrik:
Just skipped from page 1-3 to 150

Hi,

I am sorry that I did not follow on the whole post, since I am just plain lazy ;). I wondered if you guys have a suggestion on the stock ROM which has the best video drivers. I am not looking for cooked ROM, because I learned on my Kaiser that something always gives on those ROMs. I was using 6.0 ROM and it worked much better for me than 6.1 ROM (faster, more responsive). I am just getting the Orbit II because I do not like the keyboard on the Kaiser. So I need to catch up to the whole ROM development on Orbit/Polaris. Sorry if it really does not beling here, but my maijn concern is the video drivers, so I felt that it is good forum for other to see what is the most current ROM in terms of video drivers. Thanks
[Touch Cruise ROM Development] iRiKi:
That's a java app, so almost sure it doesn't test OpenGL|ES, however it may be a nice tool to test 2D graphic performance against other java-enables phones.
[Touch Cruise ROM Development] w04g005:
Hey guys, if i had understodd it correctly, the S2P v0.56 for VGA devices also needs open gl. Tested it and it worked!
[Touch Cruise ROM Development] imfloflo:
Polaris is QVGA why test vga version ?There is an directdraw/GDI option in S2U2 but very slow the s2u2 screen
[Touch Cruise ROM Development] w04g005:
because AC said the VGA version is for devices with hardware 3d !! i thought I HAVE such a device. Maybe coverflow is a little bit faster with hardware rendering.....try it yourself it's working without problems!
[Touch Cruise ROM Development] imfloflo:
It's working but the screen resolution is good too for our polaris in 320*240 ???
[Touch Cruise ROM Development] w04g005:
Yes! You have to install the v0.55 and put the v.56 s2p.exe into the s2p folder!

try it. But there is not much (none) decrese in graphics
[Touch Cruise ROM Development] smaaland:
Hi everyone.

I'm sorry if this is not the correct place to ask, but i'll try: I dont really get this. This cab that you download from the first page in this thread is just the driver, and not the TouchFlo plugin for the today-screen, right? I get the driver to work with the lights program, and i downloaded the TouchFlo 3D cab from some other place i found using google (seems i couldn't find it in more than one place). Very well, i tried to install it, and it seemed like it worked, and after tweaking the registry, aven the labels became right. But when i try to use the music tab or the photo tab, i just get error messages about some errors in the files "audiomanager_eng", and "albumsearcher" (or something similar, i don't remember exactly). Is there enyone else who have managed them to work, and where do you find the correct installation files? I have the official swedish ROM from HTC with WM6.1.

Thanks, and great job to all of you!
[Touch Cruise ROM Development] eggroe:
If i'm not mistakened, you need to have the diamond audio manager and diamond album to run both tabs.. I might be wrong though
[Touch Cruise ROM Development] smaaland:
Okay. I see. And where can i find them for my Cruise?
[Touch Cruise ROM Development] Petulinek:
In the right corner is button SEARCH!!!!!
[Touch Cruise ROM Development] NeoS:
If anyone is still with this: I've got a few files from Blackstone. ddi.dll, disptools,dll, gxdma.dll and HTCmpd.dll. Just holler if you need them.
[Touch Cruise ROM Development] rhov23:
If there is any way I can help on this project, please let me know.

I have 1 Polaris, time and effort to offer :)
[Touch Cruise ROM Development] bally3:
hi RHOV, sorry for the late reply, at the moment the issue with getting the driver working with 3d games because of the CL and CM issue mentioned in the earlier posts here: http://xdaforums.com/showthread.php?t=426314&page=154

Thats pretty much all there is to do with the 3D driver to really make it shine.
[Touch Cruise ROM Development] iRiKi:
The new 2.03 ROM for the Diamond features an updated libgles_cm.dll (before 317k, now it's 322k), and some really speed improvements over the "old" dll included in 1.93.

Just check this out:

http://xdaforums.com/showthread.php?t=464497
[Touch Cruise ROM Development] NuShrike:
Nice! Any diff in GLBenchmark?
[Touch Cruise ROM Development] iRiKi:
sorry, i don't have any old GLBenchmark results to compare with. But i've also noticed Coreplayer improvements, tho this is off the topic of this thread i guess ;)
[Touch Cruise ROM Development] bally3:
Any chance of getting this extracted and posted up to look at please?

Thanks :)
[Touch Cruise ROM Development] SuperJMN:
*JMN's sobbing all night long, losing the hope to see lightning fast graphics. Polaris, poor device, you forgotten piece of technology!!
[Touch Cruise ROM Development] bally3:
no point sobbing JMN lol :p

You could try and get more involved or try and attract more people to the project. its not completely dead, just not as alive as we'd like it to be!
[Touch Cruise ROM Development] bally3:
NikMel, any chance you can cook the omnio into your rom and see if it works better or worse?

My 3D Demos are crazy and so are the fps. the only bit I'm trying to get my head round is GLES and I assume thats something that will be a stumbling block.

In the mean time is there any regswitch we can embed that we can use to easily switch from the ati dll hook that initiates the video memory to the omnio dll?

It would really help to speed up some of this stuff and may be the best we have right now until the all elusive ddi.dll surfaces - if it does.
[Touch Cruise ROM Development] imfloflo:
Why trying t use this driver , i tought the udk R0 rom was ok for the news 3D drivers ?
[Touch Cruise ROM Development] bally3:
I didnt see any significant improvement with udk's rom - same as swtos rom, there were slight improvements and thats it.

Tell me if your experiences are different and I'll flash back and take a look.
[Touch Cruise ROM Development] rogro82:
You can easily create a new registry entry and name it "LocalHook2" or something like that... That way you can rename the key everytime you want to change the d3d driver.
[Touch Cruise ROM Development] bally3:
yeah thats what I've been doing but I thought it would be better to have some kind of switch that can do it in one click.
[Touch Cruise ROM Development] rogro82:
Can you post the localhook entries you want to switch between? Maybe i can create something for you...
[Touch Cruise ROM Development] NikMel:
Wel try this one

Just extract and replace the current one

http://rapidshare.com/files/146147916/libGLES_CM.rar

This is an OpenGL renderer so only triangle.exe works
[Touch Cruise ROM Development] imfloflo:
@bally3 have you try the R0 version ? i found this version more responsive.
[Touch Cruise ROM Development] bally3:
Thanks NikMel, now thats interesting because thats the one thing we didnt have.. now why isnt the lights working anymore?
[Touch Cruise ROM Development] bally3:
I also have GL manila.exe file that I'm going to give a try.. great find NikMel!