yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
Look I am not trying to burst anyones bubble or say this can't be done. All I am saying is that most every option has been tried and unless someone builds drivers from scratch or bases them off something that is known to show an improvment I would get my hopes up to much. M$/HTC has been known to ship "jacked" up devices to beta testers for reviews and and then switch out either hardware or software for the product that they ship hence it being a beta unit they ship to reviewers and testers. the kaiser does not have a dedicated GPU like other devices sold today. I think we need to find a way to make better use of the horse power under the hood be it from better drivers or a better OS. I'm sorry people but this is how the game works! Something better comes aong a few months later and everyone forgets about the device with the issues. I hope and wish just as you that "WE" can fix this but it has been shown not to be an easy fix. Hell there is a $7,000.00 bounty on better drivers I think any person that knows how to code for proper .dll's would have jumped on that! So to me it shows that its just not in writing a better .dll to fix are issue or taking one and modding it a little to run on our kaisers. Don't take this as me knocking this project as I am doing everything as far as cooking and modding OS's and .dll's to see if I can get it to work BUT IT HAS NOT YET!!!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] thimiost:
nevertheless will we ever use these drivers?

If we have them we will have the ultimate piece of hardware
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mrvanx:
@ChocoIncognito Strike 1, your post was not contributing to the thread.

@All please stay on topic if you post a reply.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UKTamo:
Sorry...had to get that out of my system.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Kimma:
I'm getting more and more off track here, but i do believe i started subscribing to this thread because i got here via the Polaris forum.

IF we (read: you) can get the drivers working on the Kaiser, will that mean it will be possible to do the same for the Polaris (is it the same chipset in it as the polaris?)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Pyranwolf:
Just an off the cuff thought... radios have been shown to be responsible for interactions other than strictly phone (take the camera responsiveness example). Sure I read somewhere here that it's more like a mini-os in itself. To get to the point: has anyone tried a cooked up driver with a radio appropriate to the sedna? It's a long shot but maybe that 10 minute thing happened for a reason beyond what we might think.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Macgyvec3:
It may be that these drivers are written only for the p6500 and in the code HTC is specifically rejecting the Kaiser's ID. Maybe it will take emulation or some kind of bypass to get the drivers to believe it's a p6500 and not a kaiser. Qualcomm might require HTC to do this because of people like us. If HTC didn't pay for the drivers for the Kaiser but did for the p6500 then they wouldn't want it to work for the Kaiser.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Devtone:
Wanting 3D acceleration on my Kaiser is one thing but I'm afraid that the todosmartphone benchmarks are fake. Great way to get publicity?! I don't believe HTC is dumb enough to make such a mistake while there are already so many reports about missing drivers, lag and so on.

Other possibility is that all geniuses are working secretly to get the reward ;) lets hope so! make my day!!

(noob)

Isn't there a way to just check if the graphicchip is responding to anything without a driver? just send it some kind of command? to be sure its not hardware disabled?

(/noob)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] surgex0:
Agreed. I honestly hope we're wrong; but since people have purchased the device themselves and are not achieving the same results leads me to believe that the benchmarks are completely false.

Prove us wrong though...I'll add another 200$ to the reward, heh.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Kavalier:
We should figure out what the kaiser is trying to do that makes it crash, Is it using the radio, gps, is it just connecting with the service? We should monitor them right when they crash to figure out specifically what is causing it. what is performance like before the crash?

My guess is the radio because that is the only difference between the two chipsets.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Imsaffor:
If I am to understand some of duttys previous posts, he has gotten the system to run long enough to post some decent benchmarks.

EDIT: Post in question is post #208. If I'm not mistaken, its the closest we've come to actually having the sedna driverson the kaiser amirite?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
Myself Dutty and one other I think has cooked in the drivers and the phone will run for about 10-15 minutes and then freeze up solid with the only way to fix it is by soft reset.

CAN SOMEONE UPLOAD THE P6500 ROM TO RAPID SHARE PLEASE...

Sorry call me lazy I dont feel like rebuilding the rom if someone has it as an .exe or .nbh
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] petard:
4678 vs 4386? Its not that much of a difference is it? Is it exponential or something? I think this is the thing they promised that will "improve performance" but is not a driver.

What is impressive is the fist post!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Imsaffor:
Yeah, How does the device perform in that time period? Perhaps beyond attempting benchmarks or testing the logevity of the rom we should take that 15 minutes to see how the phone itself operates in real life. I think it would help the cause one way or another if we heard some feedback regarding video playback, Camera, basic functions. If the drivers are worth the effort, this stuff should be noticable within that time.

I should probably clarify how I saw that post, if I understand correctly, Dutty mentions that he has gotten the device to stay on for 15 minutes. But the image he posted showing 4678 is from a rom with the stock drivers, not the ones we are hoping for. Again, I would love to see some benchmarks on this, but AFAIK the benchmarking software doesn't complete in 15 minutes, though I've never ran benchmarking software before so I wouldn't know for certain.

If I'm wrong, please enlighten me, I'm here to learn as much if not more than I am to give advice.

Eagerly, I wait another day. I'm cheering you guys on, I know that the minds at XDA developers can win this battle with our phones!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
i'll upload the rom I cooked the drivers in and also make a new one since i just dumped the p6500 rom be on the look out for it tomorrow afternoon as my internet is slow as **** right now. If someone would like to run benchmarks then please feel free.

also in case anyone was wondering whats in the rom

[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]

"LongPressEndKey"="1_0_31504_1"

"QuickGPS"="1_00_17201130_03"

"aGPSConfirmation"="1_0_1720_2127"

"ConnectionSetup"="1_0_31247_2"

"ConcurrenceMgr"="1_0_622717_0001"

"HTCHome"="2_0_1105723_1"

"FingerPrinter"="1_0_1115721_1"

"StartupAnimationEngine"="1_0_814719_0"

"JbedJava_MIDP"="0_0_20071030_1_1"

"BT_BPP"="1_6_1_0"

"ZIP"="1_21_1720_3930_0"

"TaskManager"="2_0_31249_1"

"SymbolPad"="1_0_28284_1"

"SMART_DIALING"="2_5_28796_2"

"ShareDLL"="2_0_071002_00v2"

"RingtonePlugin"="1_00_070419_0"

"PictureEnhancement"="1_50_1005716_c2"

"PhoneCanvas"="1_0_28766_0"

"mHub"="6_42_070704_E1"

"LockstreamDRM"="1_1_070725_02"

"DShow"="2_00_070911_0"

"CyberonVoiceSpeedDial"="1_2_b071024_0"

"CAMERA"="5_05_29235_00"

"BT_SAP"="3_08_R1"

"BTFtp"="1_2_31247_2"

"AudioManager"="1_2_1031712_q"

"ArcsoftMMS"="4_0_31_36"

"Adobe Reader"="2.00.288

NOTICE A NEW CAMERA BUILD IS OUT!!!

MAYBE SOMEONE WANT TO RIP IT AND MAKE A CAB :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Digitaltigre:
We are still waiting on the ROM from the test unit that performed so well. The purchased P6500s do not have the same performance (crippled by HTC). Why are we even discussing anything until we get hands on the preproduction ROM?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Macgyvec3:
Looking forward to trying your ROM austinsync!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] AllTheWay:
delta-101 posted the two different SEDNA ROM's in post #246 :)

http://xdaforums.com/showpost.php?p=2083480&postcount=246
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
yes thank you I found them sorry to even ask it was late and I missed them the first time around. If anyone wants to benchmark the kaiser rom with the ddi.dll from the p6500 i will be uploading it around 3:00PM NYC time. I have noticed as long as the rom is active it will not freeze so you should be able to get some good benchmarks from it.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] boqonx:
austinsync has pointed out that the device does not freeze upon bootup, could it be freezing when it was trying to enter standby mode?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ray.andy:
When I was running my kaiser on the standard T-Mobile Rom there was something in the Start>Settings>System menu, it;s not clear storage as i didn't have to put a password in. What ever it was it made my kaiser faster but only for a short time !

That makes me think it's how the kaiser runs programs.

Can someone get screen shots from the original T-Mobile ROM from Start>Settings>System.

I think HTC have had us all fooled and they have set something up wrong !
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] KALSTER:
That was probably cache memory.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fishpony:
I would be able to tell in about 30 seconds if it is working correctly. I have a few movies on my card that do not play worth a crap. that would be proof enough for me that it is enabling the hardware. I will be turning in an insurance claim over lunch and probably getting a new phone. anyone wanna give a quick example of flashing it onto my phone? sprint mogul btw.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] coolVariable:
At this point, I think the benchmarks are fake and that we are not going to get an further with this.

Despite that opinion, I contacted todosmartphone:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ray.andy:
Yep. Thats what it was. it does make a difference when the cache has been cleared.

Screen switches Portrait to Landscape faster, i didn't know of the video issue when I was using the original ROM as I was & AM a newbie LOL
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
here you all go its the 202 build i think with the p6500 ddi.dll driver cooked in and drivers from the new AT-T rom someone please run benchmarks it will freeze if not in use after about 15 minutes

http://rapidshare.com/files/105636194/TEST_DRIVERS.rar
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Rayan:
Hi...

As a Kaiser user I would love to see true drivers for it too.

Just in case the staff at TodoSmartphone don't understand English, I provided a true translation of your text. (Google is not really good with translations you know?) :)

Spanish Translation of Text:

Hola, te estoy enviando este correo por la reciente revisión que hicieron del HTC Sedna. Como sabrás, los resultados de los Benchmarks crearon gran revuelo en la comunidad de Smartphones. Dispositivos anteriores (como el HTC Kaiser o HTC Touch) se cree no estan sacando el rendimiento real debido a la ausencia de drivers de gráficos.

Estos equipos cuentan con el mismo CPU/GPU que la Sedna (MSM7200). Tus resultados han hecho que creamos que la Sedna en tu revisión contenga dichos drivers.

Podrías repetir estos benchmarks (quizas con otro programa distinto)?

Podrías extraer el ROM de tu unidad de demostración y enviarmelo por correo electrónico?

Si necesitas instrucciones al respecto, por favor hazmelo saber.

Gracias!

Let me know if you need my translation assistance in order to communicate better with the TodoSmartphone team.

Cheers!

RayanMX
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] madds:
hi all...

just to leave a link to msdn site about display drivers in windows CE.

might have some info...

http://msdn2.microsoft.com/en-us/library/aa911948.aspx

keep up the good job.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] coolVariable:
why don't you contact them?

http://www.todosmartphone.com/colabora.php?PHPSESSID=21b6b300e175f97eaace6fa644a0bc89

Email: todosmartphone@gmail.com
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fisha21:
Okay, please find attached Spb benchmarks for this ROM.

EDIT: The two ROMs posted above are pre-release Test ROMs. The link below is for the production ROM dumped and reconstructed from my device. Might be useful for comparisons?

http://rapidshare.com/files/105659129/RUU_signed_Sedna_1_10_405_3_radio_1_58_21_34.rar
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] RPG0:
See this:

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

the first post, the part about benchmarks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] FlaTEriC18041983:
When I saw those benchmarks, I reminded the two posted below... first one for a shipped Sedna (am I wright?), second one a Kaiser with shipped ROM or customized?

http://xdaforums.com/showpost.php?p=2082824&postcount=213

http://xdaforums.com/showpost.php?p=2082860&postcount=215

Anyway, the results of the second seemed almost identical to those posted now... means the drivers don't function correctly, or are no different to originals?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
Well please remember I made NO tweaks to the rom just replaced the ddi.dll and he ran the benchmarks I am sure we could sqeeze a little more out of it but I think the point has been made! thanks for running the bench marks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UKTamo:
Well I've run SPB benchmark on my Kaiser, running Dutty's WM6.1 Hybrid RTM ROM and I get:

Overall 2483

ddb bitbit 202.4

dib bitbit 29.86

gapi 586.5

So compare that to the one with the drivers.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ericmcintire:
I'm sure someone else noticed this and it may be irrelivant.. but the "d3dm.dll" in the original 6500 dump is slightly larger than the one currently on my kaiser.. could someone with some more know how put the larger driver on their kaiser and see if it does anything?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] UKTamo:
How long did the device last idle before it died?

How did the device perform in usage, not just benchmarking?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] duttythroy:
:(drivers will not work on kaiser for now, sorry to blow the bubble as austinsync already said it increase the graphis but thats as much it will do as far as my testing goes.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Chainfire:
As far as I can see this driver

may

be a slightly more optimized version of the DDI we have on our Kaisers, but it still doesn't use ATI hardware...

As for the d3dm.dll , that's just an MS driver. Again, it

may

be slightly more optimized but it doesn't provide HWA.

EDIT: Still hoping we will some day see the ROM from todosmartphone.com ... though they are not responding to my e-mails and never did contact me on MSN like they said they would ...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] the_passenger:
another day, another failed hope. Great efforts from the guys here but nothing from HTC.

Cheers up.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] the_passenger:
HTC would probably contacted them right before your appointment, so .................
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johnny13oi:
This business with HTC seems very shady. I mean not providing us with the drivers is one thing but trying to stop people from doing the work themselves and getting the drivers (probably contacted todosmartphone.com first and preventing things from happening) is another thing. Geniuses here are trying to do their work and HTC trying to stop that is really disappointing. What they are doing will cause many to lose their trust in the HTC brand.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Rumball:
Keep in mind that this is pure speculation.

[All: Sorry for jumping in to this thread and not really contributing to this investigation...I just think it is a bit premature to be claiming HTC is actively trying to prevent the forum from accessing the drivers claimed to be in the P6500 ROM...]
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] SouthernLuke:
Are we even positive that this was even somebody from todosmartphone? I'm not being negative, but we do have things to consider.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Digitaltigre:
I for one believe the benchmark they achieved. todosmartphone.com seems at first glance to know what they are doing. I looked at the review and know enough Spanish to see they were surprised by the benchmarks and believe the magical ATI drivers are in there. I doubt they made a mistake on the benchmark and don't see a reason for them to make it up. The production P6500s don't perform the same. Given HTC's stance and track record I think it's more believable that HTC is pulling a bait and switch. HTC may not think they will get called out for this. I doubt many reviewers are actually benchmarking devices they receive. Instead they just write wonderful reviews unknowingly helping to fool the public into buying. If what I'm thinking is true this is the worst case of despicable behavior. I keep thinking what if another manufacturer did this with another piece of equipment? A car, a computer, hell even a refrigerator. Grrrr:mad:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Chainfire:
Yes. I contacted them on their site and got a reply from them last thursday.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] fisha21:
That's the same ROM I was running when I did the benchmarks in post #215.

Slow, slow, slow. Massive redraw lags. Lasted for about 3 minutes, then froze - I think it is when the screen tries to switch off. To be honest, best performance so far (including release Sedna ROM) is from Dutty's latest Hybrid ROM. Just keep coming back to that one. (Dutty, we'll settle the advertising bill later ;))

@Chainfire and Dutty:

What do you think about RPG0's comments about the driver issue? I'll look for any comments you have over on that thread - can at least try and keep this one OT!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
I think our hope still is to take apart disptools.dll from your previous effort. There's a lot of hardware specific stuff in there yet to be mined.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Chainfire:
I'm not going to go there and invest time in the discussion (not in this thread either, btw). You ask for my opinion, here it is: most of that post is mostly wrong.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] drownage:
Hmm... so maybe its just that 7200 OEM doesnt really have the ATI chip enabled... only version of it such as 7201, etc...

And maybe this is not driver, but just the patch that us kaiser users will be getting sooner or later... maybe...

Well installing the TEST_DRIVER rom right now... will let u know if i find anything different

Edit: Definitely not drivers... Programs seem to launch faster, but thats about it. Rendering is stil slow when screen flip, scrolling, website rendering, IE is still slow at loading though... the only programs that acutally started up faster than Dutty's were the built in ones like File Explorer/Solitaire :), etc... Camera didnt wokr :-/... But then again this is just a test... But I think we're getting closer... Not with driver, but just to get Kaiser atleast clsoe to competing with its predecessors..
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] scm2ejm:
I still want to know what the deal is with the Core Player team. How did they get hardware acceleration for the media player they created? Did they licence the technlogy off ATi or Qualcomm or are there some whitepapers/API documentation out there that we dont know about. The battery lasts so much longer when using Core Player for MP3s than WMP10 or whatevers cooked in to Duttys Hybrid.

BTW, I dropped my kaiser a few days ago and cracked the casing. I'll probably make an insurance claim at some point so if someone wants me to test any ROMs the let me know as I dont care if I brick it :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Devtone:
The latest 1.2.2 plays a desktop XviD movie just fine on Dutty's Hybrid if I don't mind the outrageous screen buildup lag. no problem for static images and websites but for games and movies?! :mad:

Some benchmark result..

(349MB, 23fps 146kbps XviD 624x352, 128kbps MP3)

Qtv - 81.94%

Raw - 75.09%

DDRAW - 85.91% No video, black screen but does finish.

GDI - 71.09%

Nothing special about the Qtv itself?

And that CorePlayer uses less power for MP3 playback is nothing special, almost all other players use less then WMP ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Chainfire:
I have found that CorePlayer QTV performance on Kaiser differs greatly over different ROMs. I hadn't actually noticed this until a few weeks ago, but QTV performed a lot better on my original HTC ROM than it does with the Dutty I'm running (I think it's the latest, but it may be the one before that). Strange, as Dutty's beats that ROM in all other aspects ...

Note that I say it performed better as many video's that played damned smooth back then are choppy now. IIRC I average around 120% in the benchmarks for normal 350mb TV rips, while I'm only reaching 85-90% now. Also, IIRC it was a 20% to 100% improvement over the best other score I could get in CorePlayer. I don't have those benchmarks stored anywhere though, so I don't have 'evidence' to back it up. I might be having a brainfart. Anyway, I am quite sure that 350mb TV rips played completely flawless before and 700mb TV rips played slightly choppy now and then. Right now I can hardly get a 350mb TV rip to play even somewhat smooth. Another thing I had when it performed 'great' though was, it only played great on the high quality setting. Medium or low made it choppy.

As for how CoreCodec does it,

as far as I know

they are simply using the QTV overlay for which all (or at least most) of the files were already available at least on my original HTC ROM.

QTV itself seems to be nothing more than a specially optimized MP4 decoder and blitter for the MSM7x00 platform, but as far as I can tell it doesn't use hardware.

Note that I have only glanced at QTV internals, I have not 'taken them apart' like the CoreCodec guys so all of the above should be taken with a grain of salt (and some Tequila if you have it!)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] livefastdiefun87:
Im getting so bored of this escapade. Ive just sat in work and read through all 38 pages of this thread (i work for a mobile company) I think with the way HTC are going we are all going to end up with palm treo's lol. Considering it uses the same chipset as the 6500 there should be no reason why slightly modifying the drivers will not work but HTC will not allow this. Surely someone must have come across something in the .dll's that can be extracted and modified to create even a slight boost even if it is not a full kick up the ass for the kaiser