P6500 ROM DUMPED (ATi Drivers Inside)

[hidavi]

Or at least I think the drivers are in there. Props to hdubli for dumping it.

http://rapidshare.com/files/103706855/Part02.rar.htm

So, XDA Masters, can you guys please play with this and see what you get in terms of Qualcomm MSM7200 drivers? Apparently, the Sedna has the same chips as the Kaiser but it actually has the drivers that the Kaiser lacks.

EDIT: I suggest no one here brags to the online press yet so that Qualcomm doesn't get mad too soon :(

http://img402.imageshack.us/img402/4231/htcsednagraphddbbt3.gif

http://img241.imageshack.us/img241/1917/30937000uv2.jpg

5100 vs 400. Speaks for itself.

Please, don't post if you aren't going to be helpful. There are 30 pages already & suffice to say that the vast majority are worthless crap.

Let's save some pages for development. The more crap that get's posted the less continuity there is in the information.

[mikeeey]

or better yet, if someone was able to locate the files in this rom and create a working cab! that would be great!

[sswalia]

If you would like to see all of the spb benchmark tests for the HTC SEDNA 6500; visit this site- make up your own mind on what this means. To me it is pretty conclusive.

These are the benchmark tests for the Sedna-
http://www.google.com/translate?u=http%3A%2F%2Fwww.todosmartphone.com%2F Revisin-de-la-HTC-P6500-Sedna-Fotos-Videos-y-Tests-Benchmark-notice-87P4.html&langpair=es%7Cen&hl=en&ie=UTF8

Even the reviewers on the site commented on the unique graphical benchmarks as compared to other msm7200 chipsets


UPDATE: If there are any more p6500 users at this forum, we need you to dump your rom so we can analyze it for drivers; Also it would be helpful if you could run spb benchmark tests on your device to confirm the results of todosmartphone.com.

[hakushox]

SWEET find bro! hopefully a lot of good will come out of this.

[AllTheWay]

Also noticed this from the site.



Emphasizes the graphics performance of the PDA which seems to include, for firn, ATI drivers that we take in the absence TyTn II and Cruise. Or it or have improved quite graphics performance of the PDA. In the rest of comparative speed does not stand out especially being in most cases almost tied with her cousin the HTC Pitt.

[sswalia]

that was translated by google from spanish---- so if you want the actual words and not the butchered translation just go to the site and check it out....


Does look super promising though! :eek::D:cool:

[cuboosh]

so ...this means what

[hidavi]

Alright guys, shhh. Nothin more us n00bs can really do so lets sit and wait patiently till a pro takes a look at this...

[fb.knight]

could this be what we have been wating for? calling the best of xda! we need like a bat signal or something :D ill be checking back ever half hour till this thing is confirmed one way or the other.

[herg62123]

nice find props to those who pulled it

[xmoo]

Let the hacking begin xD!

[neilson]

Let the hacking begin xD!
We need to keep a quiet and steady approach to all this. When it's accomplished, I soon hope to see enhanced performance on my Sprint Mogul and across all devices with MSM7200 and MSM7500 chipsets.

[tvachev]

Hope it works!!!!
Thank you !

[_Alex_]

default_d3m.dll and htc_d3dm.dll are identical to Kaiser's AT&T 1.62 ROM (WM 6.0 OS 5.2.1622). DDI.dll is different, with the P6500 version being ~2K larger.

I've discovered it's not as simple as just replacing DDI.dll on a Kaiser. I just tried and it hung at the splash screen, so I had to hard reset.(If you want to try too, install the attached cab at your own risk. I'm just happy I didn't try to cook this in :p) This isn't unusual, as I seem to recall reading about Chainfire having similar experiences with the LG KS20 DDI.dll.

It looks like we'll need someone like cmonex, Olipro, Pof, jwocky2001, Nushrike, Chainfire or anyone else blessed with ASM skills or device driver hacking to make this work. If any of you need more files to work with and don't feel like dumping imgfs, shoot me a PM and I'll send you any files you require.

Good luck!

[herg62123]

i downloaded file just in case qualcomm wants us to pull this from xda.

i have it stored to my pc if we need this file again uploaded.

[NFRCER]

Thanks alex,
this shall help speed up the proccess of fixing the drivers, if possible of course.

[the_passenger]

DDI.dll is version 0.92, isn't it pretty old ?

[_Alex_]

DDI.dll is version 0.92, isn't it pretty old ?


It's stamped with whatever build version it was (e.g., AT&T 1.62 has version 1.62, AT&T 3.14 = 3.14), so I'd guess that this is ROM 0.92 for the Sirius. It's missing the XML file found in Kaisers that indicate the version in the OEMVERSION directory. (It could be somewhere else, but I haven't looked.)

FWIW, all the files in the OEM directory are dated 09-09-07 or 09-10-07. Not sure if that matters or not, especially if the benchmarks are valid...

[herg62123]

i tried to install it with total commander.....got through boot screen but now the black screen of death....have to hard reset now......dam it......still working on solution

[the_passenger]

IMHO, HTC could NOT make it to work on the KAISER/TOUCH... and so on, so they said, screw it, and move on w/o the driver.

[mikeeey]

how many people think this is gonna be the whole LG KS20 thing all over again? chainfire or something tries to get the drivers to work but it just wont. that would suck..

[ray.andy]

You gotta think positive ! Something is different with the P6500 (Said to be faster video etc) if its not a driver then maybe a piece of software.

[mikeeey]

yea i know, im normally an optimistic person, but it just worried me when people said they were needing to hard reset, and getting similar results that chainfire was.

[herg62123]

i am just curious....has anyone ripped the new test AT&T rom to see if the ati driver is in it....may not be the p6500 driver but it may be the one for kaisers a like.

[Azrael Masters]

default_d3m.dll and htc_d3dm.dll are identical to Kaiser's AT&T 1.62 ROM (WM 6.0 OS 5.2.1622). DDI.dll is different, with the P6500 version being ~2K larger.

I've discovered it's not as simple as just replacing DDI.dll on a Kaiser. I just tried and it hung at the splash screen, so I had to hard reset.(If you want to try too, install the attached cab at your own risk. I'm just happy I didn't try to cook this in :p) This isn't unusual, as I seem to recall reading about Chainfire having similar experiences with the LG KS20 DDI.dll.

It looks like we'll need someone like cmonex, Olipro, Pof, jwocky2001, Nushrike, Chainfire or anyone else blessed with ASM skills or device driver hacking to make this work. If any of you need more files to work with and don't feel like dumping imgfs, shoot me a PM and I'll send you any files you require.

Good luck!

Could this behavior because of this: http://blogs.msdn.com/windowsmobile/archive/2005/11/03/488934.aspx ?
I mean that KAISER isn't booting up after your driver update.

Hope it helps.

Good Luck! :)

[_Alex_]

i am just curious....has anyone ripped the new test AT&T rom to see if the ati driver is in it....may not be the p6500 driver but it may be the one for kaisers a like.

Wouldn't it be easier just to flash and benchmark the ROM? :D

[_Alex_]

Could this behavior because of this: http://blogs.msdn.com/windowsmobile/archive/2005/11/03/488934.aspx ?
I mean that KAISER isn't booting up after your driver update.

Hope it helps.

Good Luck! :)

I have SDKCerts.cab cooked in along with Security Policy 0101a set to disabled.

The problem could be simply that the P6500 has a 3.5" screen, while the Kaiser has a 2.8" screen. Or one of a thousand possible other issues. I'm going to leave it to the ASM/driver gal/guy (s) to figure that one out :D

[Mikulec]

I have SDKCerts.cab cooked in along with Security Policy 0101a set to disabled.

The problem could be simply that the P6500 has a 3.5" screen, while the Kaiser has a 2.8" screen. Or one of a thousand possible other issues. I'm going to leave it to the ASM/driver gal/guy (s) to figure that one out :D

Do u know if some "gal/guy" is working on this issue?

[herg62123]

here is the one date 9-10-07 is from new at&t rom

the other is the one alex posted

[_Alex_]

Do u know if some "gal/guy" is working on this issue?


According to the stickied thread in the Kaiser general forum, I believe a gal and a guy are waiting on donations for devices. I haven't really read through the entire 600+ post thread :rolleyes:

[Mikulec]

According to the stickied thread in the Kaiser forums, I believe a gal and a guy are waiting on donations for devices. I haven't really read through the entire 600+ post thread :rolleyes:

They were waiting for the device two months ago. I thought you are in contact with them.
Ok, thanks for the info.

[Akya]

here is the one date 9-10-07 is from new at&t rom

the other is the one alex posted

so wait are you saying that the new ddi is actually in the new rom? i wonder what the benchmarks will say...

[mccune]

I hope this is 'just' a software thing. Then I'm sure someone will break this. If it's a hardware issue then I think we're screwed :(

[rev3nant]

Anyone tried DDI from previous page? Or is it same as before?

[_Alex_]

i am just curious....has anyone ripped the new test AT&T rom to see if the ati driver is in it....may not be the p6500 driver but it may be the one for kaisers a like.

Wouldn't it be easier just to flash and benchmark the ROM? :D

here is the one date 9-10-07 is from new at&t rom

the other is the one alex posted


Anyone tried DDI from previous page? Or is it same as before?

See this post (http://forum.xda-developers.com/showpost.php?p=2071731&postcount=623) for AT&T WM6.0 1.62 tweaked results.

See this post (http://forum.xda-developers.com/showpost.php?p=2071803&postcount=114) for AT&T WM6.1 3.14 stock results.

As far as I'm concerned, this pretty much means that the WM6.1 3.14 DDI.DLL tweaked would probably would perform at the same rate as the tweaked WM 6.0 1.62 DDI.DLL.

So, let's all get back on topic and think good thoughts for the P6500 DDI.DLL :D

[paulobrien]

Just a heads up on this, I used dependency walker to find the dependent DLLs and put them all into a CAB.

Sure enough, on reboot, hang at the HTC logo :(

P

[Meos]

Well if it was that easy tot make the driver compatible with the Cruise, HTC would have made the changes and released the whole thing themselves. So my guess is that it gonna take a whole lot more hacking/fidling to make this work.

[draxredd]

@meos : HTC is trying to artificially fragment a market in order to increase earnings. they are perfectly technically able to fix the kaiser situation, but it wouldn't make sense from a marketing standpoint. Of course they won't put it that straight, but their latest and greatest PR answer is anything but clear regarding that :"you want video acceleration ? buy another of our products".


ps:So you see, HTC released drivers for msm7200 acceleration before end of march.

warning: post may contain minute traces of irony.

[ceevee369]

According to the stickied thread in the Kaiser general forum, I believe a gal and a guy are waiting on donations for devices. I haven't really read through the entire 600+ post thread :rolleyes:

if one of the Pro's would leave a message that they see a 75% success possible, I am more than willing to provide them 100 US $ support fee to purchase a piece to test.

Some others who would like to join?

This tech talk about DDI.dll goes above my flashing capabilities, so I put my believe in the best of the best here @XDA :)

[hidavi]

Erm, I can give $5...

And yes, I also believe that HTC left out the drivers on purpose, not because they couldnt put them in.

[hidavi]

Those getting hanging screens, are you using WM6 or 6.1? You should probably try with 6.0 if you aren't already.

[ChumleyEX]

It's my understanding that someone did indeed get the blacklisted kaiser. Geez I really hope this comes through, I just hate to see my phone tip toe when it can run.

[johnburgelin]

what's this blacklisted kaiser?....i think ill run a search...
~j

[johnburgelin]

i have much to learn in my searching skills....got to filter through all the junk
~j

[rvdgeer]

i have much to learn in my searching skills....got to filter through all the junk
~j

Thanks for keeping us informed on your progress! :D
I'm a n00b at this and I'm sure I can't do anything to help besides keeping spirits up and some occasional testing...

[URPREY]

what's this blacklisted kaiser?....i think ill run a search...
~j

I was curious too. I believe this is the answer:
http://forum.xda-developers.com/showpost.php?p=1910883&postcount=23

[hidavi]

that kaiser is no different than any other Kaiser. Its just not accepted by AT&T (stolen?)

[URPREY]

that kaiser is no different than any other Kaiser. Its just not accepted by AT&T (stolen?)
Summary: someone donated a blacklisted Kaiser to a developer who was willing to work on making the drivers work. The drivers appear to be here, so the developer who received the blacklisted Kaiser now has a device and drivers to work with.

[hidavi]

Oh, hehehe, ok :D

[SCSweeps]

How does a phone get blacklisted exactly? I thought all the data the cell network read is from the sim card.

[wiebenik]

any suggestions i install the cab in this thread on my tytn2 installation works fine but te phone stuck on vodafone screen someone help me please. i only got a backup on my sd card

[flushbeer]

you should have read before... the DDI.dll doesn't work out of the box.

I would suggest: hard reset ;-)

[Qlphn]

I may be wrong, but when vox ddi.dll was ported to tornado without proper certificate effect was identical (device 'dead' on startup screen). Maybe it's similar case?

http://forum.xda-developers.com/showpost.php?p=1734553&postcount=4

[_Alex_]

any suggestions i install the cab in this thread on my tytn2 installation works fine but te phone stuck on vodafone screen someone help me please. i only got a backup on my sd card


Did you not read the post where the cab was attached? Even if you read only the bolded text, it clearly informs you what can occur and what you need to do to recover.

I've quoted myself for your ease of reference.


I've discovered it's not as simple as just replacing DDI.dll on a Kaiser. I just tried and it hung at the splash screen, so I had to hard reset.(If you want to try too, install the attached cab at your own risk. I'm just happy I didn't try to cook this in :p) This isn't unusual, as I seem to recall reading about Chainfire having similar experiences with the LG KS20 DDI.dll.

[fishes234]

How does a phone get blacklisted exactly? I thought all the data the cell network read is from the sim card.

They blacklist the imei number in the phone, which is supplied to the network when you connect. The tech's been there for years but it's only comparatively recently that network operators have actually started doing it, hence it now being illegal to change your phone's imei number.

[_Alex_]

I may be wrong, but when vox ddi.dll was ported to tornado without proper certificate effect was identical (device 'dead' on startup screen). Maybe it's similar case?

http://forum.xda-developers.com/showpost.php?p=1734553&postcount=4


Question already answered, read: http://forum.xda-developers.com/showpost.php?p=2071693&postcount=27. I also assume that modaco (Paul@modaco perhaps?) also had sdkcerts installed when he used dependency walker to include other DLLs within his unreleased cab, when replied here: http://forum.xda-developers.com/showpost.php?p=2071998&postcount=36.

I'm pretty much done with this. It's time to help the heavier hitters to take a wack at it :D

[jug6ernaut]

^^^ lol whats up with ppl installing any ol cab these days :S

[swtaltima]

^^^ lol whats up with ppl installing any ol cab these days :S


I did! but I always back up my phone so a hard reset isn't the end of the world. I am hopeful that this will work some day.

[jug6ernaut]

I did! but I always back up my phone so a hard reset isn't the end of the world. I am hopeful that this will work some day.

me2! this is very exciting!

[Qlphn]

Question already answered, read: http://forum.xda-developers.com/showpost.php?p=2071693&postcount=27. I also assume that modaco (Paul@modaco perhaps?) also had sdkcerts installed when he used dependency walker to include other DLLs within his unreleased cab, when replied here: http://forum.xda-developers.com/showpost.php?p=2071998&postcount=36.

As far as i know it's diffrent security level (Privileged Execution Trust Authorities) and it can't be disabled - so security policy 0101a will not help here. Everyone's Tornado was uncertertified, yet still there was few victims ;) I'll try if sdkcerts are enough (my poor tornado will be guinea pig...)

[dubbeld00]

http://forum.xda-developers.com/showpost.php?p=2072587&postcount=364

From what i understand he seems to have it working on a Polaris... If that's true... well... that would be great.

[fb401]

^^^ lol whats up with ppl installing any ol cab these days :S
Haha, everybody wants to "beta test".

[GSLEON3]

I have a quick ????

Can anyone tell me if any of the posts with attachments have just the dynamic libraries, unedited & without anyof the sdk certs?

I have an idea on this, but I'm on my device today, no pc till later, & I want to have a look in the clean dll's.

I see lot's of attachments from Alex, etc... But none of them tell me what's what. If anyone's compiled just the DLL's, not as cab, please let me know.

[jug6ernaut]

Haha, everybody wants to "beta test".


haha your right... now im not gonna claim to be an expert...or to really knowing anything at all lol. but when something does come from this(notice i said when, bc i think something will) it will be some time in the future... Things like this are not just thrown together..it will take some time... but as always i have trust in the community :) lol.

[swtaltima]

haha your right... now im not gonna claim to be an expert...or to really knowing anything at all lol. but when something does come from this(notice i said when, bc i think something will) it will be some time in the future... Things like this are not just thrown together..it will take some time... but as always i have trust in the community :) lol.

I did load the cab alex provided on my 8525 and it reset just fine. Its my extra phone so I kinda throw caution to the wind.

[wiebenik]

any suggestions i install the cab in this thread on my tytn2 installation works fine but te phone stuck on vodafone screen someone help me please. i only got a backup on my sd card


problem fixed hard reset and replace backup thankx

[_Alex_]

I did load the cab alex provided on my 8525 and it reset just fine. Its my extra phone so I kinda throw caution to the wind.


Just speculating (again), but we know that the Hermes has an ATI Imageon chipset. Maybe this just proves that the Kaiser doesn't?

Remember folks, if we could get better video performance on the Kaiser by porting over drivers from the Hermes, it probably would have been done awhile ago, especially since alot of the Kaiser chefs were formerly Hermes chefs.

I further speculate that being able to install it on another hardware device doesn't mean that it'll work on the Kaiser. :(

I'm waiting for Olipro, cmonex, Pof or someone else to come along and blow us all out of the water with their findings :D

[hidavi]

This is different, though. The P6500 has the same chipset as the Kaiser. The Hermes does not.

[RacerII]

Same here no boot with the ddi.dll
Time to restore my backup.

[_Alex_]

This is different, though. The P6500 has the same chipset as the Kaiser. The Hermes does not.


*SHRUG* Maybe the Hermes doesn't even use DDI.DLL :) Anywhoo, I've had enough fun for the day with this. I'm out :D

[NuShrike]

This isn't unusual, as I seem to recall reading about Chainfire having similar experiences with the LG KS20 DDI.dll.

It looks like we'll need someone like cmonex, Olipro, Pof, jwocky2001, Nushrike, Chainfire or anyone else blessed with ASM skills or device driver hacking to make this work. If any of you need more files to work with and don't feel like dumping imgfs, shoot me a PM and I'll send you any files you require. Good luck!Sure - I've just downloaded it. I'm guaranteeing nothing, since I'm still busy chewing through AhiInit() from the KS20's stuff. Almost done, and then I can chew through AhiDevOpen(). Walking all the memory setup and allocation paths has been "fun".

It's been annoying every time I update to some new ROM, it's a day lost restoring settings... :P

edit: wtf, there's a qtv_mp4_decoder.dll that I've never seen before.

[Johannus]

i am so hoping you could make this work!

[SCSweeps]

Sure - I've just downloaded it. I'm guaranteeing nothing, since I'm still busy chewing through AhiInit() from the KS20's stuff. Almost done, and then I can chew through AhiDevOpen(). Walking all the memory setup and allocation paths has been "fun".

It's been annoying every time I update to some new ROM, it's a day lost restoring settings... :P

edit: wtf, there's a qtv_mp4_decoder.dll that I've never seen before.

WE LOVE YOU NUSHRIKE! <3

[Jonathan1683]

Didn't HTC's official statement say that it can't be fixed because it doesn't have the ATI chip?

[merten3000]

Whoohooo..... we are on the edge of a big breakthrough!

Maybe I can build a hdmi connecter into my kaiser and watch HD on my LCD-TV with this new driver coming......just dreaming and making jokes....

I hope the clever guys in here (not me for sure!) will find a way to boost the graphics performance on our beloved kaiser.

Good luck!!

Greetz Merten

[hidavi]

Didn't HTC's official statement say that it can't be fixed because it doesn't have the ATI chip?

Lies. It is well-known that the MSM7200 chipset has a modified version of the ATi Imageon chip in it. The P6500 confirms this.

[Jonathan1683]

hmm, that's a pretty bold official lie to their customers. Hopefully it works. I would buy that P6500 if it wasn't ugly as shit.

[muthaflaco]

I'd get one too....if it had a KB. (I'm a text whore)

Edit: Thanks for looking into this guys. I have no idea how to do any of the tecnical stuff, or I'd help you.
Your expertise is appreciated. If any of you live near me, I'll buy you an 'adult beverage.'

[littlerain]

hmm, that's a pretty bold official lie to their customers. Hopefully it works. I would buy that P6500 if it wasn't ugly as shit.

LOL!"ugly as shit" That 's so funny !!!

[Laurentius26]

Very nice to here this ;)

Lies. It is well-known that the MSM7200 chipset has a modified version of the ATi Imageon chip in it. The P6500 confirms this.

[jockyw2001]

hidavi: can u pls also post part0 and part1 Thx!

[hidavi]

I don't have it. Ask the member hdubli (I gave him props in the first post) for it seeing as how he's the originator of this.

[mackaby007]

Sure - I've just downloaded it. I'm guaranteeing nothing, since I'm still busy chewing through AhiInit() from the KS20's stuff. Almost done, and then I can chew through AhiDevOpen(). Walking all the memory setup and allocation paths has been "fun".

It's been annoying every time I update to some new ROM, it's a day lost restoring settings... :P

edit: wtf, there's a qtv_mp4_decoder.dll that I've never seen before.

That must have been what Corecodec tapped into to give us such a videoplayback boost in version 1.2.1 of their player and also the reason why WMplayer natively supports MPEG 4 playback in seemingly hardware accelerated mode.

Shame nothing has turned up yet for D3D or any 3D graphics processing at all.:(

I can't say who right now, as they can't afford to be inundated with questions at the moment, but at least 2 of xda's top developers/hackers are looking into the P6500 ROM and potentially transferable or re-cookable drivers for the Kaiser and other Qualcomm based 7200 chipset devices (7500 too).

Let's just wait a little longer to see if they have any success. If they do, they will let us all know in due time.

Meanwhile might I suggest that we simply try to assist them in testing when they ask for assistance and remember to honor our pledges for the bounty, if they should be successful.

[NuShrike]

Well:

there's no easily visible "ati*" driver that I can see
htc_d3dm.dll is just a stub to import default_d3dm.dll localhook just like the Kaiser's
somebody at least compiled some of the .dlls to target a CPU higher than ARMV4I (meaning the newer ARMv6 in the Qualcomm)
DDI.dll (still using ancient ARMv4I asm such as "bx lr") is almost identical to the Kaiser's for at least 90% of the file from diffing just the asm. There are changes, and maybe this new DDI has improvements, or it's just tweaks for the kernel/userland/device.

SetKMode() isn't being used anymore, (or it became an internal function), but using ChangeDisplaySettingsEx() from coredll.dll is new


Can we have somebody independently verify the SPB benchmarks just to be sure?

[dcd1182]

Meanwhile might I suggest that we simply try to assist them in testing when they ask for assistance and remember to honor our pledges for the bounty, if they should be successful.
agreed, if i can help with msm7500 testing let me know.
you can also sign me up as a donator if a driver is made for us.

[jockyw2001]

As far as I can see we need the P6500 AMSS.
In other words I should finish my radio dumper.

[mackaby007]

Can we have somebody independently verify the SPB benchmarks just to be sure?

Agreed 100%!! ...was thinking the same thing all day. There doesn't seem to be a forum for the P6500 as yet, so no obvious place to find owners of this device.

If anyone here is a P6500 owner, can you please run this benchmark to verify the results. It would at least confirm if our efforts in hacking the Sedna ROM are justified. Much appreciated.

[MDA-Fan]

Can we have somebody independently verify the SPB benchmarks just to be sure?

I would recommend that too. I´ve tested Vbenchmark on the magician and the kaiser today and the magician had on test 3 18000 points (Kaiser: 2300) and that only because it couldn´t handle the JPEG test (errors)!
(overal result: Kaiser=1471, Magician=4700)

[hidavi]

It should be stickied on every subforum here that we need a P6500 owner's help.

[sswalia]

All we have right now for the p6500 is the dumped rom from a preproduction model that hdubli got his hands on. Apparently he no longer the unit and therefore can not go through and do benchmark tests.

IF THERE ARE ANYMORE P6500 OWNERS AROUND, please i beg you, could you please, DO A BENCHMARK TEST AND DUMP YOUR ROM.

I know for a fact that there are a few people rocking the HTC Sedna here at xda.


The benchmark tests done by todosmartphone are undeniable, however the rom from this preproduction phone from (from december i believe... i.e note the date of the OEM directory, and the version - .92- of the rom build. ) may not be far enough up to date.

WHAT THIS MEANS IS WE NEED TO SPREAD THE NET.... and FIND MORE P6500 users who can benchmark their device and dump a rom for us..

Even us NOOB end-users can HELP with this one :D




SPREAD THE WORD!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[DarkDvr]

I fully agree.

MODERATORS please help us out and sticky this. Help us find Sedna owners.

[jockyw2001]

All we have right now for the p6500 is the dumped rom from a preproduction model that hdubli got his hands on. Apparently he no longer the unit and therefore can not go through and do benchmark tests.

Such a shame he didn't dump part01 and smi so that I could reconstruct radio.
The rom I just cooked with a Kaiser part01 doesn't boot as could be expected.
Well I guess we must wait for the next owner(s).

[sswalia]

one sec, i think he has the spl dump, would that work... i'll ask anyway

[jug6ernaut]

wouldn't it suck if some1 got the driver to work...then we tried to use it in our kaisers and since we have been running them so long without the graphics card that it wouldn't work from just sitting there...lol...that would suck...

[Crypter]

Why wouldn't HTC release the drivers for the cruise and kaiser WITH the release of the p6500? i think... even when u find the driver... it wouldnt work ....

[the_passenger]

wouldn't it suck if some1 got the driver to work...then we tried to use it in our kaisers and since we have been running them so long without the graphics card that it wouldn't work from just sitting there...lol...that would suck...

aahhh, you meant it got rusted? lol

[jug6ernaut]

aahhh, you meant it got rusted? lol


lol i can see the panic in the streets now :P

(sorry i know this is in no way contributing to the cause)

[atkdabomb]

Why wouldn't HTC release the drivers for the cruise and kaiser WITH the release of the p6500? i think... even when u find the driver... it wouldnt work ....

Licensing.

[Imsaffor]

The pricing on the two devices. Kaiser/Sedna that I can find seem to be too far apart to merit just the additions that the Sedna has. Perhaps the reason the device costs so much more is because they have paid for the proper licencing?

[NoThrills]

Well:

there's no easily visible "ati*" driver that I can see
htc_d3dm.dll is just a stub to import default_d3dm.dll localhook just like the Kaiser's
somebody at least compiled some of the .dlls to target a CPU higher than ARMV4I (meaning the newer ARMv6 in the Qualcomm)
DDI.dll (still using ancient ARMv4I asm such as "bx lr") is almost identical to the Kaiser's for at least 90% of the file from diffing just the asm. There are changes, and maybe this new DDI has improvements, or it's just tweaks for the kernel/userland/device.

SetKMode() isn't being used anymore, (or it became an internal function), but using ChangeDisplaySettingsEx() from coredll.dll is new


Can we have somebody independently verify the SPB benchmarks just to be sure?

I find it very strange that everyone is so focused on the ddi.dll.

Yes, it's the display driver, but does anyone really believe this is 'the key'? I have been digging around this display crap a little bit myself, and, believe it or not, I've managed to get my Kaiser booting with this new ddi.dll.

It's not displaying alot (it's acting very, very weird), but still. It's showing something.

But then again, what did we expect. Compare the file to any recent 3.02/3.02/3.08/3.14 ddi.dll, and you'll see only 1-2kB difference. Those 2kB are not going to give you H/W acceleration.

It is compiled into something else, and we'll going to need to find that. I'm going to try and find it, anyway :)

[NuShrike]

I find it very strange that everyone is so focused on the ddi.dll.For me, it's a known point to start searching for "what's different?". Where's the external hooks for the magic hardware acceleration? Otherwise, there's a lot of subsystems check ...

Since you got it booting, mind doing some benchmarks to see if there's anything to find? :)

[NoThrills]

For me, it's a known point to start searching for "what's different?". Where's the external hooks for the magic hardware acceleration? Otherwise, there's a lot of subsystems check ...

Since you got it booting, mind doing some benchmarks to see if there's anything to find? :)

That's the problem, it's booting, but that's about it. Not much functional you can do with it, it's extremely, extremely slow. But that might be because of everything else I'm breaking to get the ddi.dll running :)

My guess is the 'magic' H/W acceleration is in parts of the ROM we do not have yet.

But then again, it's 1:20 AM now, and I need to get up in 5 hours :) So, more fiddling tommorrow.. If there's anything usefull I'll let you know...

[jug6ernaut]

That's the problem, it's booting, but that's about it. Not much functional you can do with it, it's extremely, extremely slow. But that might be because of everything else I'm breaking to get the ddi.dll running :)

My guess is the 'magic' H/W acceleration is in parts of the ROM we do not have yet.

But then again, it's 1:20 AM now, and I need to get up in 5 hours :) So, more fiddling tommorrow.. If there's anything usefull I'll let you know...

ok first idk what im talking about first of all....and this probable makes no sense at all...

but...back on my wizard i would always run roms ported from other phones..ones that for sure did not have the same chipsets...if we were able to port the rom to our kaiser would that work? though im pretty sure getting the .dll's to work is apart of that right?

again sorry for my stupid unhelpful post :S

[Doug2873]

wow seeing those benchmarks have made me a believer...PM chainfire about this ASAP!!!

[Bronx31]

Meanwhile might I suggest that we simply try to assist them in testing when they ask for assistance and remember to honor our pledges for the bounty, if they should be successful.


:) Can't agree more!! I'll Beta Test it, and pay my donation quickly

[Devtone]

Interesting...

Display Driver Development Concepts

Application
The application can be simple, such as a Hello World application, or complex, such as a three-dimensional engineering application.

Whichever it is, the application calls GDI functions. Coredll.dll exposes these functions.

Coredll.dll
The major set of functions is exposed through a single DLL, called Coredll.dll.

In most cases, this library does not perform the work. Instead, the library packages the parameters for the function call and then triggers a Local Procedure Call (LPC) to another process.

The specific process depends on the function call. All drawing and windowing calls are sent to Gwes.exe.

Gwes.exe
The Graphics, Windowing and Events Subsystem (GWES) is responsible for all graphical output and all interactions with the user.

The drivers that reside in the GWES address space include display drivers, printer drivers, keyboard drivers, mouse drivers, and touch screen drivers.

Ddi.dll
The default name for the display driver is Ddi.dll. As with most DLLs, Ddi.dll communicates through exported functions.

Ddi.dll exports only the DrvEnableDriver function, which returns a pointer to an array of 27 function pointers to the caller. When GWES requires a display driver, it calls one of these 27 functions.

Writing a device driver involves writing the code for these 27 functions.

Three of these functions are specific to printer drivers, which leaves 24 for the display driver developer.

Hardware
The graphic pipeline ends at the hardware. The display driver communicates to the hardware using the mechanism required by the hardware.

This process typically involves a combination of memory-mapped video buffers and I/O registers.

http://msdn2.microsoft.com/en-us/library/Aa447495.displayarch(en-us,MSDN.10).gif

*SOURCE (http://msdn2.microsoft.com/en-us/library/aa447495.aspx)

[hidavi]

The pricing on the two devices. Kaiser/Sedna that I can find seem to be too far apart to merit just the additions that the Sedna has. Perhaps the reason the device costs so much more is because they have paid for the proper licencing?

It would have to be. the only extra things the Sedna has are a fingerprint reader and 0.7" more screen space.

[dcd1182]

i barely have the knowledge to obtain a kernel log so heres hoping someone else can decipher it :)

this is from msm7500 titan with DDI.dll, QTV*.dll, htc_d3dm and default_d3dm from P6500 cooked in


CertVerify: DDI.DLL trust = 2
ERROR: function @ Ordinal 259162 missing in Module 'wce_rex.dll'
!!! Please Check your SYSGEN variable !!!
Data Abort: Thread=82d30d80 Proc=8033c2b0 'gwes.exe'
AKY=00000021 PC=0005fb20(gwes.exe+0x0004fb20) RA=0006984c(gwes.exe+0x0005984c) BVA=0c000008 FSR=00000007
Data Abort: Thread=82d30d80 Proc=8033c2b0 'gwes.exe'
AKY=00000021 PC=03e2f978(wce_rex.dll+0x00001978) RA=03e2f96c(wce_rex.dll+0x0000196c) BVA=0c000004 FSR=00000007

it seems my wce_rex.dll needs to be replaced as well? too bad its in xip part
or i could be completely on the wrong track... thought id give it a shot

i noticed another thing as well:
Someone mentioned that they had not seen qtv_mp4_decoder.dll before. It is also contained in the new wm6.1 Kaiser 3.14 test ATT rom. (http://forum.xda-developers.com/showthread.php?t=380913)

edit: this was probably a pointless post - after further reading in the ks20 thread it looks like nushrike had already played with wce_rex.

[NuShrike]

i barely have the knowledge to obtain a kernel log so heres hoping someone else can decipher it :)

this is from msm7500 titan with DDI.dll, QTV*.dll, htc_d3dm and default_d3dm from P6500 cooked in


CertVerify: DDI.DLL trust = 2
ERROR: function @ Ordinal 259162 missing in Module 'wce_rex.dll'
!!! Please Check your SYSGEN variable !!!
Data Abort: Thread=82d30d80 Proc=8033c2b0 'gwes.exe'
AKY=00000021 PC=0005fb20(gwes.exe+0x0004fb20) RA=0006984c(gwes.exe+0x0005984c) BVA=0c000008 FSR=00000007
Data Abort: Thread=82d30d80 Proc=8033c2b0 'gwes.exe'
AKY=00000021 PC=03e2f978(wce_rex.dll+0x00001978) RA=03e2f96c(wce_rex.dll+0x0000196c) BVA=0c000004 FSR=00000007

it seems my wce_rex.dll needs to be replaced as well? too bad its in xip part
or i could be completely on the wrong track... thought id give it a shot

i noticed another thing as well:
Someone mentioned that they had not seen qtv_mp4_decoder.dll before. It is also contained in the new wm6.1 Kaiser 3.14 test ATT rom. (http://forum.xda-developers.com/showthread.php?t=380913)Could be the RexGetVirtualAddress() (Kaiser,p6500) vs get_virtual_address() (KS20) memory allocation problem I saw before. But wce_rex.dll seems to vary a bit depending on device ...

If what you said about the qtv driver is true, then that may be the "fix" that coming "from" HTC.

How do you guys get into the kernel log? It would help me a lot to know.

[WorldIRC]

I have a personal friend who works for ATI for his internship and works in driver development for mobile devices. I am asking him for some favours for us ;)

[dcd1182]

How do you guys get into the kernel log? It would help me a lot to know.

go to bootloader, then task 37 in mtty. drop me a line on freenode if you need more help there.

[punkcell]

Kool.

Also it is very hard to find a person with a P6500, I can't even find a forum for, but i also notice that other ppl are looking for one also to dump the rom, just like we are all trying to do.

[RustyGrom]

WorldIRC, that's awesome. Hopefully he can help but I'd edit your post as we wouldn't want to get him in trouble. There can't be very many people in his position so he may be easy to identify as the leaker. Call me paranoid I guess.

[rcm_rx7]

i can just see all the april fools drivers threads coming already

[umvagia0]

sorry if this is a n00b question....just curious, if you guys can extract the drivers...will this improve the functionality of the camera in low-light situations? I thought I read a while back that it would.

keep up the awesome work! i have no doubt you guys will solve the driver issue.

thanx

[WorldIRC]

WorldIRC, that's awesome. Hopefully he can help but I'd edit your post as we wouldn't want to get him in trouble. There can't be very many people in his position so he may be easy to identify as the leaker. Call me paranoid I guess.

No worries. He may be under NDA...but I'm not ;)

[Edvard_Greig]

No worries. He may be under NDA...but I'm not ;)

Right.....but his talking to you would be a violation of the NDA if they found out it was him.....

[rovanesyan]

sorry if this is a n00b question....just curious, if you guys can extract the drivers...will this improve the functionality of the camera in low-light situations? I thought I read a while back that it would.

yes it most likely would fix the camera issues, however im more interested in the tytn ii's ability to potentially run emulators with the sound on

[mlcohen]

sorry if this is a n00b question....just curious, if you guys can extract the drivers...will this improve the functionality of the camera in low-light situations? I thought I read a while back that it would.

keep up the awesome work! i have no doubt you guys will solve the driver issue.

thanx

the low-light 'functionality' is strictly controlled by the shutter speed / aperture combination ie. not a software issue. The larger the aperture the more light can be accepted in less time.

[maati]

One more idea: As on the Polaris, it makes a huge difference in TFlo scrolling speed if the programs folder is launched from HTC Home or from start menu, there must be something in the software/programming that went totally wrong.
See here: http://forum.xda-developers.com/showthread.php?t=381389

Perhaps it has something to do with the ARM9/ARM11 thing or something like this, which means, even if we don't get the video drivers to work or if there are none, perhaps a change in some DLL files related with all softwares and the processor is the key.

Would you think it is worth to have a look into this, too?

[hidavi]

Doesn't happen on my Tilt. Scrolling is always fast regardless.

[Isaygarcia]

Maybe that thing is what HTC was referring when they said "software fix", its not a driver, but is a whole structural change from arm9 to arm11. With the new instructions and functions of the arm11 the kaiser will be the BEST (no phone but PC) ever.
but anyways... the driver is essential now..
imagine : Driver + ARM11 Architecture =? POWER!!

[ceevee369]

edit: wtf, there's a qtv_mp4_decoder.dll that I've never seen before.


Do you mean that the QTV decoder from corecodec is embedded in the Sedna stock Rom as on-top dll aside the DDI?
that would be funny (and rather expected) that HTC would liase with CoreCodec.
Which also prooves that the original main video dll are not goood enough?

QTV could explain a better performance indeed, but never the benchmark values the SEDNA reported (it is availble on Spanish site i saw somewhee)

I know that some people are ven trying to unlock the Wifi functionality on the 7200 chipset as it IS all there. There is enough proof that there are no MSM7200 a-b-c chipsets, only 1 version with disabled functionalities no?

[hidavi]

Do you mean that the QTV decoder from corecodec is embedded in the Sedna stock Rom as on-top dll aside the DDI?
that would be funny (and rather expected) that HTC would liase with CoreCodec.
Which also prooves that the original main video dll are not goood enough?

QTV could explain a better performance indeed, but never the benchmark values the SEDNA reported (it is availble on Spanish site i saw somewhee)

I know that some people are ven trying to unlock the Wifi functionality on the 7200 chipset as it IS all there. There is enough proof that there are no MSM7200 a-b-c chipsets, only 1 version with disabled functionalities no?

CorePlayer QTV mode blows ass in my Tilt. GDI is what I'm forced to use.

Maybe that thing is what HTC was referring when they said "software fix", its not a driver, but is a whole structural change from arm9 to arm11. With the new instructions and functions of the arm11 the kaiser will be the BEST (no phone but PC) ever.
but anyways... the driver is essential now..
imagine : Driver + ARM11 Architecture =? POWER!!

Erm, to change the architecture, you'd have to change the whole chip, you can't "update" it...

[dumpydooby]

No worries. He may be under NDA...but I'm not ;)
With all due respect, I think you didn't get his point.

If HTC has decided that the redistribution of this driver would put a damper on their income, then they might be inclined to monitor some of the online discussions to see how close everyone is to succeeding. Should they find this particular discussion, they might get an urge to call up ATI and inquire about interns on the mobile driver development team. Considering that it's unlikely that there are very many interns on the mobile driver development team, I suspect that it might be rather easy to narrow down any individuals that could potentially pose a threat.


Yes, it is quite possible that HTC will go after individuals that could potentially be aiding in the redistribution of their drivers. Creative Labs just issued a cease and desist to an individual that was redistributing drivers for their sound cards. The situation was very similar to this one, actually. The drivers in question offered more functionality that was built into the hardware of the sound cards, but had not been enabled by the default drivers. So an individual took updated drivers from other Creative Labs sound cards and modified them to work with unsupported cards. This is precisely what our situation is like. We have HTC releasing updated drivers with newer products, and we have individuals that are trying to port those drivers to unsupported devices.


That said, I think you should refrain from exposing your friend. He could lose his job if stuff hits the fan.

[hidavi]

Don't expose him but DO get the info and files we need.

[sswalia]

what all can we do on the front of finding more p6500 users... I've already pmed everyone that has posted that they have had one on the forum..... does anyone know of any coorporate business that have bought this item in bulk... it seems like that is the target demographic.

Also, is it completely off the wall to just ask HTC for a copy of the sedna rom? You could pretend like you are a confused coorporate partner? or some bs like that...

Finally, does anybody here speak spanish fluently? Why dont we contact that todosmartphone.com website and see if they still have the rom and phone that they did review on... They obviously know of our plight, and they might just be sitting around waiting for someone to ask them for the rom and phone info, lol. The review was only done on 3-27-08, so they must still have the phone- its not even been a week.

Please, someone who speaks spanish fluently, ask this site very nicely if it would be at all possible for them to dump the rom from their reviewed p6500 Sedna Rom.... This might be the quickest most direct way to get our drivers.

[hidavi]

Spanish is my first language. I'll hit them up tomorrow when I'm awake :D

[neilson]

Spanish is my first language. I'll hit them up tomorrow when I'm awake :D
Make it happen man. We gonna have bottles poppin' by the time we're finished here.

[Imsaffor]

Well, I've already backed up my data, I'm planning on reflashing my phone anyway. I'll hold off on it a bit so I can test out any cabs you guys have. I'll help in any way I can.

[_DrG_]

my bruv is getting his p6500 later today, i have asked him to run the d3d test found here: omikr0n D3D "Lights" Test (http://forum.xda-developers.com/showpost.php?p=1621811&postcount=13) for starters as soon as he gets it out the box, then ill work on him to see if we can get a rom dump :)

[cmonex]

could someone please upload the sedna part01.raw too, i need files from XIP too

thanks

and yeah i think the chance for success is bigger now :D

EDIT: i see part01 still hasn't been posted. :(

[cmonex]

As far as i know it's diffrent security level (Privileged Execution Trust Authorities) and it can't be disabled - so security policy 0101a will not help here. Everyone's Tornado was uncertertified, yet still there was few victims ;) I'll try if sdkcerts are enough (my poor tornado will be guinea pig...)


you can disable it by editing the kernel. which i have done

[kwikky]

- never mind -

[bouaroudj]

my bruv is getting his p6500 later today, i have asked him to run the d3d test found here: omikr0n D3D "Lights" Test (http://forum.xda-developers.com/showpost.php?p=1621811&postcount=13) for starters as soon as he gets it out the box, then ill work on him to see if we can get a rom dump :)
can't wait for that

[MickyMax]

you can disable it by editing the kernel. which i have done

Can you explain how have you made this please ? :confused:

[slovoflud]

at last some hope! :)

at least 6 people here at work with TyTN II are waiting for those miracle drivers! :)

[Radeon123]

This might be a little of topic but while search for P6500 videos on youtube I came across this one which shows smooth scrolling of the programs menu unlike the stuttering scrolling most phones with the 7200 chipset have :).

The clip is at about 55 secs.

http://www.youtube.com/watch?v=yTgJ08_tQzM&feature=related

[cmonex]

Can you explain how have you made this please ? :confused:

sure, but a prerequisite, you need a disassembler handy.


anyway i still see no XIP from sedna posted... oh well, working on getting it.

[tenticle56]

could someone please upload the sedna part01.raw too, i need files from XIP too

thanks

and yeah i think the chance for success is bigger now :D(

The cavalry have arrived :) :)

[kwill]

Man!!! you guys at xda never cease to amaze me:) getting these drivers to work would be the next coming of our devices and can't wait, as I know you all will get it done!! sorry, as this is definitely where my small amount of technical knowledge stops. but, will be here for any help that I can offer. GOOD LUCK!!!! (as if you all will need it :))

[Dredd67]

http://www.engadgetmobile.com/2008/04/01/microsoft-announces-windows-mobile-6-1-device-upgrades/

Could this be what HTC was waiting for? Should'nt we wait also until we have the official TyTn II 6.1 ROM?

[brrrt]

http://www.engadgetmobile.com/2008/04/01/microsoft-announces-windows-mobile-6-1-device-upgrades/

Could this be what HTC was waiting for? Should'nt we wait also until we have the official TyTn II 6.1 ROM?
Strange that the HTC Touch Cruise isn't in the list...

[Mr. Zach]

this whole driver issue has me second guessing my purchase here. it's quite unfortunate.back to my wizard i go for a while.

[hidavi]

Your Wizard is faster than your TyTN II?

Anyway, I've been trying to register for todosmartphones forum all day and their forums have been down all day :(

Maybe I should try emailing them? Problem with that is that I doubt that they're willing to jeoparodize their relationship with HTC (who provided the reviewing unit). I'm figuring we'd have a much greater chance if we ask a forum member or through the forums since it would be more of an unofficial colab.

[Kimma]

This video has a comparison between the Sedna and the Cruise when playing a video:
http://www.youtube.com/watch?v=hSzGUvlT3x4
It seems to go smoother on the sedna than on the Cruise.

Edit: forgot to add, the comparison is in the very end of the movie

[Mr. Zach]

the wizard actually plays movies/videos as it has adequate drivers. the video prforms pretty well. not perfectly (195mhz processor) but it actually works. blackberry has an awesome new phone in the works, i may be converting.

[Pawel062]

sure, but a prerequisite, you need a disassembler handy.


anyway i still see no XIP from sedna posted... oh well, working on getting it.

everyone please give cmonex some time on this and keep posting technical info only. this will help keep the thread slow. once i am done with my athena rom i will also pop in and help cmonex. will be using the touch cruise for testing :)

[mackaby007]

hehe with Cmonex and PK backing this exploration of possibilities, my faith in a potential resolution to this driver issue has been renewed. Great to see you guys here.

If you need me to test anything......PM me.;)

[mackaby007]

This video has a comparison between the Sedna and the Cruise when playing a video:
http://www.youtube.com/watch?v=hSzGUvlT3x4
It seems to go smoother on the sedna than on the Cruise.

Edit: forgot to add, the comparison is in the very end of the movie


Have to say that I see no difference at all in that video. The split second gap between the Sedna could be due to to having been started first. In any event, the Cruise seemed to slightly gain on the Sedna towards the very end of the video.

If that was anything to go by, I wouldn't bother.:(

[sswalia]

@hidavi: that would be a decent first step, if the site is down for more than another day, i would go ahead and email them- the worst that could happen is that they say no, at which point we wait and hit up their forums. Also, do ya'll know of any other mags or sites that are scheduled to do a review of the p6500?)

I am anxiously awaiting _DrG_'s benchmark results, it seems like he/she is the only one who has been able to get their hands on a newer p6500....
If we could get that rom, we would be back on top and rolling.

For some reason, i cant get in contact with hdubli to grab the spl that he said he had with this rom. So for now, i think we are stuck with the older rom..


Progress update _DrG_?

[mackaby007]

my bruv is getting his p6500 later today, i have asked him to run the d3d test found here: omikr0n D3D "Lights" Test (http://forum.xda-developers.com/showpost.php?p=1621811&postcount=13) for starters as soon as he gets it out the box, then ill work on him to see if we can get a rom dump :)

Now this lead seems much more promising. Hoping that you and your brother can and will come through on this. Thanks in advance. If you need specific help in extracting/dumping the necessary data, I suggest you PM cmonex and PK as well as others here like Nushrike etc.

[mackaby007]

that would be a decent first step,

I am anxiously awaiting _DrG_'s benchmark results, it seems like he/she is the only one who has been able to get their hands on a newer p6500....
If we could get that rom, we would be back on top and rolling.

For some reason, i cant get in contact with hdubli to grab the spl that he said he had with this rom. So for now, i think we are stuck with the older rom..


Progress update _DrG_?

lol...you beat me to it.;)

[hidavi]

Can we please stop with the commentary and leave this thread open to true progress, even if its slow? Thanks.

[mackaby007]

Can we please stop with the commentary and leave this thread open to true progress, even if its slow? Thanks.

Fair point. But notice that we have some developers on board now....that in itself is progress.;)

[no2chem]

i barely have the knowledge to obtain a kernel log so heres hoping someone else can decipher it :)

this is from msm7500 titan with DDI.dll, QTV*.dll, htc_d3dm and default_d3dm from P6500 cooked in


CertVerify: DDI.DLL trust = 2
ERROR: function @ Ordinal 259162 missing in Module 'wce_rex.dll'
!!! Please Check your SYSGEN variable !!!
Data Abort: Thread=82d30d80 Proc=8033c2b0 'gwes.exe'
AKY=00000021 PC=0005fb20(gwes.exe+0x0004fb20) RA=0006984c(gwes.exe+0x0005984c) BVA=0c000008 FSR=00000007
Data Abort: Thread=82d30d80 Proc=8033c2b0 'gwes.exe'
AKY=00000021 PC=03e2f978(wce_rex.dll+0x00001978) RA=03e2f96c(wce_rex.dll+0x0000196c) BVA=0c000004 FSR=00000007

it seems my wce_rex.dll needs to be replaced as well? too bad its in xip part
or i could be completely on the wrong track... thought id give it a shot

i noticed another thing as well:
Someone mentioned that they had not seen qtv_mp4_decoder.dll before. It is also contained in the new wm6.1 Kaiser 3.14 test ATT rom. (http://forum.xda-developers.com/showthread.php?t=380913)

edit: this was probably a pointless post - after further reading in the ks20 thread it looks like nushrike had already played with wce_rex.

dcd, i haven't looked at this much on the titan, but...

(1) qtv from msm7200 isn't compatible with msm7500 (different qtv api implementation? weird.)

(2) the kitl output above shows that ddi is missing an import from wce_rex.dll - i don't think wce_rex.dll is really device specific... otherwise you can always edit the ordinal to point to another existing function.

(3) default_d3dm is pretty much a default stub driver generate by pb. its unlikely to vary between devices.

[Laurentius26]

This is great, can you please explain how to activate KITL on Kaiser?

Thank you,

dcd, i haven't looked at this much on the titan, but...

(2) the kitl output above shows that ddi is missing an import from wce_rex.dll - i don't think wce_rex.dll is really device specific... otherwise you can always edit the ordinal to point to another existing function.

[no2chem]

This is great, can you please explain how to activate KITL on Kaiser?

Thank you,

its not real kitl,
only kitl output...

in mtty:

task 32
task 37

the output will be really useless unless you take your battery out and boot up once before you do it. be sure htc home is off as well, it produces a lot of garbage that will make debugging difficult at best.

[_DrG_]

@hidavi: that would be a decent first step, if the site is down for more than another day, i would go ahead and email them- the worst that could happen is that they say no, at which point we wait and hit up their forums. Also, do ya'll know of any other mags or sites that are scheduled to do a review of the p6500?)

I am anxiously awaiting _DrG_'s benchmark results, it seems like he/she is the only one who has been able to get their hands on a newer p6500....
If we could get that rom, we would be back on top and rolling.

For some reason, i cant get in contact with hdubli to grab the spl that he said he had with this rom. So for now, i think we are stuck with the older rom..


Progress update _DrG_?

My brother is still waiting for delivery of the p6500, he was promised yesterday but still no show, i'm hoping it is today then i can post a more acurate update.
PS. i'm a "he" :D

[_DrG_]

:( Not sure if this is an indication of anything or not.. ill wait for an "expert" to chip in

Ok so an update on this, my brother has recieved his p6500, he has tried t run the omikr0n D3D "Lights" Test (http://forum.xda-developers.com/showpost.php?p=1621811&postcount=13) but it does not work.
I have asked him to run an independant SPB Benchmark test on it and let me know the results..... i am, like you guys, waiting for this with suspense....

[milesmowbray]

Does anyone here know how CorePlayer utilises QTV to accelerate the Kaiser video output?

I think it probably uses QTV.dll, this is the export table:

000169E8 1 ?graph_tcb@@3Urex_tcb_struct@@A
00005860 2 QTV_Close
00005868 3 QTV_Deinit
000058A4 4 QTV_IOControl
00005870 5 QTV_Init
00005A0C 6 QTV_Open
00005A14 7 QTV_PowerDown
00005A18 8 QTV_PowerUp
00005A1C 9 QTV_Read
00005A24 10 QTV_Seek
00005A2C 11 QTV_Write
00019460 12 graph_tcb

I would love to build QTV support into TCPMP as a new plugin but need to work out the parameters for these functions. If anyone can help let me know.

qtv_mp4_decoder.dll looks interesting as well:

0000186C 1 CreateVideoDecoder
00001ABC 2 CreateVideoDisplay
00001780 3 DeInitVideoDecoder
000019CC 4 DecodeVideoAndDisplay
00001AB4 5 DecodeVideoFrame
00001914 6 DestroyVideoDecoder
00001B3C 7 DestroyVideoDisplay
00001C38 8 DisplayFrameOut
00001DAC 9 InitVideoDecoder
00001708 10 KeepUnattendedModeMoreTime
00001BB8 11 SetDisplayAttribute

[danielherrero]

Probably I am wrong but the program you have used is compiled for subsystem "Win32 Console" instead of "WinCE" like any tipical WinCE program........
Even you can execute it in your pc so Its recognized as a PC program but It throws an exception....

pd. I have used PEEXplorer to get the info about the exe file....

[jockyw2001]

This is great, can you please explain how to activate KITL on Kaiser?

Thank you,

Check this (http://forum.xda-developers.com/showthread.php?t=381028)

[jockyw2001]

Does anyone here know how CorePlayer utilises QTV to accelerate the Kaiser video output?

Funny, I am looking at exactly the same thing. Will drop u a PM in a couple of days.

[fisha21]

Okay, have gone and done it (gulp)!

Have managed to juggle some money around and put in an order for the P6500. Should be with me tomorrow or day after. I already own a Kaiser, so the P6500 will be there for the sole purpose of ROM dumping etc.

Will run Benchmarks once I have it and update you all. (Thought it was fairer on DrG's bro, who is using as his primary device). Will be open to requests for things to try on it soon! Would rather not brick a ~£530 device though!

[danielherrero]

wow fisha21, thanks¡¡

[Nanax]

wow hero! nice!

[juiceppc]

Nice one. I always admired the Sedna. Post lots of pics! I'm all for a quad band 3.5" device with current specs. Not to mention the driver potential.

[DaveShaw]

Okay, have gone and done it (gulp)!

Have managed to juggle some money around and put in an order for the P6500. Should be with me tomorrow or day after. I already own a Kaiser, so the P6500 will be there for the sole purpose of ROM dumping etc.

Will run Benchmarks once I have it and update you all. (Thought it was fairer on DrG's bro, who is using as his primary device). Will be open to requests for things to try on it soon! Would rather not brick a ~£530 device though!

Nice one, my GF would bury me under the patio if I bough a 500 quid device for testing.:D:D

Apprecited.
Dave

[thefunkygibbon]

sorry for seeming thick ,but why are we needing the rom dumped again? i thought it was posted in the original post?

[Kimma]

It's missing part 1 (and maybe 3?), so we don't have the entire contents.

[Moskiitto]

Hopefully this P6500 is the solution to our big trouble with missing drivers. I knew this driver issue before I bought kaiser. I had tytn I (hermes) before kaiser. Even kaiser doesn't have the drivers it kicks ass :D Hope you genius guys find the solution to fix the driver issue. There is ATI acceleration in msn7200 no doubt about it.

[troyk]

If Fishna fixes the problem, i'll give him a discount on his sedna of 10 Euros.

Good luck

Ps: Others are allowed to follow.

[daniel_rh]

Well, the video playback in P6500 is much better than Cruise but in general performance is not good at all in both phones

[zaharakis]

If Fishna fixes the problem, i'll give him a discount on his sedna of 10 Euros.

Good luck

Ps: Others are allowed to follow.

wow :eek: sow much money to donate??? i can't afford it :D

[bouaroudj]

Well, the video playback in P6500 is much better than Cruise but in general performance is not good at all in both phones

Can you do a bench with coreplayer(qtv edition) or tcpmp?

[flushbeer]

i don't want to destroy anybodies hope... but what makes you think there is more in part01?
there's nothing in the DDI.ddl that shows a qualcomm, only the qtv...dll has the qualcomm inside.
so what chance do we have when having the part01?

[johndabrit]

After reading all 18 pages so far of this thread and hoping for a happy ending . (Yes the kind you get at a massage parlor would be acceptable) It seems we have come so far with lots of talented people on board and tons of people willing and ready to test. I am bummed that i get to the end of page 18 which was heavily posted on even today and there is no way to fix this as of yet. The kaiser is such a saweet gadget if it would only perform to its hardware potential. Dutty is a master cooker and i use his builds on all my devices. Is he aware of this progress and is he somebody who might be able to hack his way through this or is he more on the os cooking side only? DUTTYYYYY WHERE ARE YOUUUUUUUUUUUU???

[Kimma]

i don't want to destroy anybodies hope... but what makes you think there is more in part01?
there's nothing in the DDI.ddl that shows a qualcomm, only the qtv...dll has the qualcomm inside.
so what chance do we have when having the part01?
enough of the negative waves! ;)

[Pawel062]

After reading all 18 pages so far of this thread and hoping for a happy ending . (Yes the kind you get at a massage parlor would be acceptable) It seems we have come so far with lots of talented people on board and tons of people willing and ready to test. I am bummed that i get to the end of page 18 which was heavily posted on even today and there is no way to fix this as of yet. The kaiser is such a saweet gadget if it would only perform to its hardware potential. Dutty is a master cooker and i use his builds on all my devices. Is he aware of this progress and is he somebody who might be able to hack his way through this or is he more on the os cooking side only? DUTTYYYYY WHERE ARE YOUUUUUUUUUUUU???

more on the os side really. cmonex is the one that has the skills to make a difference. she has done driver mods before on other devices and has much disassembly skills. the thing though is time. we all have lives so we only do this on our free time.

that doesnt mean though that dutty wont be able to contribute. i'll have him join us soon. bepe also will join soon. they might be more behind the scenes though than posting on here.

[juiceppc]

I'll say it again. Shame on HTC for making people jump through all these hoops. And where is the "fix/patch" they promised?

[GSLEON3]

Guys, PLEASE!!! There are 19 pages already & suffice to say that the vast majority are worthless crap, including this plea.

Let's save some pages for development. The more crap that get's posted the less continuity there is in the information.

I ask that everyone REFRAIN from posting editorial comments, status requests, etc... Unless you have something to say that actually has developmental importance with regard to the issue at hand, don't post.

Let's not make the others, like Cmonex, etc... dig thru 19 pages to find 6 valid & helpful tidbits of information.

THX.

[jockyw2001]

Just cross-flashed P6550 OS on Kaiser, no go

[Pawel062]

Just cross-flashed P6550 OS on Kaiser, no go

ok course it'll be a no go. xips are probably different and some oemdrivers might not be compatible.

[jockyw2001]

More luck on Niki, boots up just fine. Must swap touchscreen and kb drivers tho. Greetings to the guy who said "of course it's a no go" :D

[bobthemonkey]

Ah, but is there any performance gain???

Suprising that it worked on Niki but not Kaiser considering they are essentially the same device. Could you 'cook' the Kaiser touchscreen driver into the p6500 rom? Of course that assumes the Touchscreen driver is what is preventing kaiser from booting - also you could try the same for the kaiser keyboad driver.

[discovery531]

is it wrong to install the _alex_ patch on my Polaris with my step?

just because i install it and hang my Polaris and hang, i have hard reset it finally.

1. install the _alex_ .cab

2. copy the ddi.dll to \windows\

3. soft reset

4. hang out at the htc logo pop up.

I have saw a guy that using Polaris installed this and running fine, but not me.

[Moskiitto]

More luck on Niki, boots up just fine. Must swap touchscreen and kb drivers tho. Greetings to the guy who said "of course it's a no go" :D

Does this mean that the break through has happened? Do we have working Ati acceleration in our kaisers? Wrong day for april fool :(

[majaelx]

:confused: could you, masters of coding and cooking, inform us about the progress of your work? please... we (others with no winCe skills) ar druling on this thread for every post.

[mimoracer]

www.todosmartphone.com they have open their chest for any help


http://forum.xda-developers.com/showpost.php?p=2081007&postcount=914

[jockyw2001]

More luck on Niki, boots up just fine. Must swap touchscreen and kb drivers tho. Greetings to the guy who said "of course it's a no go" :D

Guys i can only remote control it since ts and kb don't work on niki, but i can start a benchmark. Please give me a suggestion on how/what i should use to do the benchmarks.

Edit1: touchscreen does work now :)

Edit2: vsbench (http://vsbench.virtualspaghetti.com/) benchmark results will be posted later

Here we go.

Kaiser with T-Mobile UK ROM
graphics 1118
others 1953
jpeg 2366
game 1371
sound 0626

final score: 1486

Niki with P6550 RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test ROM => OS part only

graphics 1096
others 1669
jpeg 2175
game 1293
sound 0658

final score: 1378

Niki with P6550 RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test ROM => Sedna OS + Radio

graphics 1112
others 1792
jpeg 2201
game 1309
sound 0736

final score: 1430

Niki with WM 6.1 Niki project rom

graphics 1094
others 1803
jpeg 2208
game 1276
sound 0672

final score: 1410

Edit3: will flash sedbra radio and benchmark again

SPB benchmarks:

Arkaball frames per second (frames/sec)
MDA 107; MDAII 98.4; niki_sedna 153;

DDB BitBlt
kaiser 392.9 fps
niki with Sedna Rom 406 fps
sedna P6550 5128 fps

[Chainfire]

Guys i can only remote control it since ts and kb don't work on niki, but i can start a benchmark. Please give me a suggestion on how/what i should use to do the benchmarks.

Edit1: touchscreen does work now :)

Edit2: vsbench (http://vsbench.virtualspaghetti.com/) benchmark results will be posted later

SPB Benchmark? Blt'ing speed is very very very important for most graphics applications!

[jockyw2001]

SPB Benchmark hung in graphics test :(
(i believe some1 with a p6500 posted that as well)

[Moskiitto]

I ran Vsbenchmark 2007 on my kaiser and hermes:
Hermes has Ati chip+drivers

Kaiser:

Graphics Test1 1154
Others Test2 2056
JPEG Test3 2503
Games Test4 1382
Sound Test5 0608

Final Score : 1540

Hermes:

Graphics Test1 1555
Others Test2 1040
JPEG Test3 2290
Games Test4 1364
Sound Test5 1356

Final Score : 1521

[SiGGy]

Another test would be to run core player in benchmark mode with the same video clip.

Enable either GDI or Directdraw then start the benchmark.

Directdraw mode if I remember correctly doesn't even render video when benchmarking with the broken video drivers. Where as it's butter smooth video on my ppc-6700 doing that benchmark.

[jockyw2001]

Which version of core player should that be?

[Moskiitto]

1.2.1 is the newest I think.

My hermes plays smoother and faster benchmark than kaiser.
In other hand using Qtv in coreplayer video playback is good enought.

[jockyw2001]

1.2.1 is the newest I think.

Someone else should test that then, I don't have it.

[SiGGy]

Which version of core player should that be?

I'd use core player version (TCPMP) .72RC1

I'd pass for now on testing with the core player (latest) that uses QTV support, we know that works already.

Using .72RC1 will show you if DirectDraw and GDI and performing adequately for the device.

[Moskiitto]

Someone else should test that then, I don't have it.

TCPMP Is free and working program for that purpose:

Site:
http://picard.exceed.hu/tcpmp/test/

CAB:
http://picard.exceed.hu/tcpmp/test/tcpmp.pocketpc.0.72RC1.cab

EXE:
http://picard.exceed.hu/tcpmp/test/tcpmp.pocketpc.0.72RC1.exe

[NetrunnerAT]

Somebody they have a P6500 ... please Connect via QPST and look what CPU ID you have! I think ... if the P6500 is faster and use ATI Driver ... it have a MSM7200A CPU and not a MSM7200B like Niki, Kaiser or Polaris!

[jockyw2001]

Thx SiGGy & Moskiitto: I can be extremely lazy at times ... do you have a link of a representative video clip :)

[jockyw2001]

I think netrunnerAT is right, check out a few additional SPB benchmarks I posted here (http://forum.xda-developers.com/showpost.php?p=2081457&postcount=191) (courtesy valvarin)

[SiGGy]

Thx SiGGy & Moskiitto: I can be extremely lazy at times ... do you have a link of a representative video clip :)

This should work...

http://dl.speeddemosarchive.com/HalfLife-Hazard_310.avi

If the phone doesn't have the same CPU we're just chasing our tails though...

[fb.knight]

This should work...

http://dl.speeddemosarchive.com/HalfLife-Hazard_310.avi

If the phone doesn't have the same CPU we're just chasing our tails though...

thats what i wanted to ask if hes right and the prossesor is the a and not the b then thats game over right?

edit btw the link in your last post shows up 403 forbidden for me

[mimoracer]

i think that the rom that every one play with is an old rom from old preproduction sedna phone what we are looking for is the rom from the new sedna reviewed at www.todosmartphone.com so can any one contact them for how to dump the sedna rom

[CaliTilt]

Please send step-by-step instructions to dump the rom of the Sedna to Todosmartphone

Thank you


todosmartphone
Junior Member Join Date: Mar 2008
Posts: 1

Spanish reveiwers of HTC Sedna

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

Hello:

We are the spanish reviewers of HTC Sedna (www.todosmartphone.com). We have still the device on our office so if you need the ROM dump we can do it.

Sinceresly, We does not know how to do that on WM6. If anybody can help us to do this, we can make as soon as posible.

Best,

Puri,
TodoSmartphone.com

[duttythroy]

I have tried cooking the drivers in the rom it works and the phone boots up and everything works except that I get low sound and after about 15 mins the device freezes. This is a benchmark of the rom with the built in drivers the highest graphics score on kaiser by a mile, the highest score on kaiser I think was 4386


http://img390.imageshack.us/img390/5518/duttyswm61graphicsoz7.jpg

[fisha21]

Okay, so it arrived today. Here are the VSBenchmark results for the Sedna.

[fisha21]

And here are the same results for Kaiser running Dutty's Hybrid (1st April release)

Just about to run Spb Benchmark on both...

[Moskiitto]

Okay, so it arrived today. Here are the VSBenchmark results for the Sedna.

How the sedna gets so lame results?

[getwilde]

Please send step-by-step instructions to dump the rom of the Sedna to Todosmartphone

Thank you

I think ChainFire has sent instructions to TodoSmartPhone. Hopefully other experts will (or have) as well?

http://forum.xda-developers.com/showpost.php?p=2081310&postcount=920

The speed test results that Fisha21 just posted don't look near as good as what TodoSmartPhone found. Just like the actual performance of my Mogul/Titan isn't near as good as what early review sites seemed to report. It makes me wonder if the early review units contain licensed drivers, to ensure positive reviews, while the standard units sent to consumers do not. How else could the numbers be so different?

Hopefully we can get a full ROM dump from a review unit.

Edit: fisha21's Spb benchmark numbers in his next post look promising!

[fisha21]

Here are the Spb benchmark graphics results for the shipped Sedna

[jockyw2001]

... It makes me wonder if the early review units contain licensed drivers, to ensure positive reviews, while the standard units sent to consumers do not. How else could the numbers be so different?

Hopefully we can get a full ROM dump from a review unit.

I have 2 ROMs:
19/12/2007 10:01 63,092,072 RUU_Sedna_HTC_WWE_1.02.405.1_Radio_Sedna_1.58.13.2 8_signed_Test.exe
08/01/2008 15:19 64,416,724 RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test.exe

Only tried RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test thus far. Will test the other t'morrow.

Dutty :cool:

[fisha21]

And the Spb results for the Kaiser (again on Dutty's latest Hybrid ROM)

Edit: ok, these are the Kaiser results. Doh. Trying to get the info out there too fast!

[RacerII]

Here are the Spb benchmark graphics results for the Sedna


Hmmm now thats weird.
http://forum.xda-developers.com/attachment.php?attachmentid=79221&d=1207253198
http://www.todosmartphone.com/imagenes/fotosreview/htc-sedna-graph-ddb.gif
Thats a big difference.....

Sounds like htc is playing a dirty trick with us.
Remember how reviewers mentioned how fast the kaiser is , and how it beats every other xda on the market....
:rolleyes:

[jug6ernaut]

Hmmm now thats weird.

http://www.todosmartphone.com/imagenes/fotosreview/htc-sedna-graph-ddb.gif
Thats a big difference.....

Sounds like htc is playing a dirty trick with us.
Remember how reviewers mentioned how fast the kaiser is , and how it beats every other xda on the market....
:rolleyes:

:| its happening again

[fisha21]

I have 2 ROMs:
19/12/2007 10:01 63,092,072 RUU_Sedna_HTC_WWE_1.02.405.1_Radio_Sedna_1.58.13.2 8_signed_Test.exe
08/01/2008 15:19 64,416,724 RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test.exe

Only tried RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test thus far. Will test the other t'morrow.

Dutty :cool:


The Sedna I have is:
ROM 1.10.405.3
Date 22/1/08
Radio 1.58.21.23

[XtreMe_G]

And the Spb results for the Kaiser (again on Dutty's latest Hybrid ROM)

you posted the sedna's results here fisha

[RacerII]

:| its happening again

Yup , i guess we should ask them to do the benchmark again to see if it was an error.

If its not an error , htc is messing around.

Edit: i have pmed them and asked if they could redo the benchmark.

[fultotop]

The P6500 SPB Benchmarks bear some relation to the results duttythroy's got when he cooked the drivers into a rom, if you look at the tests.

If you look at the DDB BitBit, DIB BitBit & GAPI tests, I wonder if this rom doesn't have ATI drivers. But HTC have coded in other areas like using some of the QTV routines to output to the display quicker in certain areas.

Why would the P6500 have 3D capablities when it's aimed at corporate users.

That my two pennies thrown in.

Hope I'm wrong.

[fisha21]

you posted the sedna's results here fisha

Thanks, edited

Okay, have also tried running Omikron's Lights app

The message windows are as follows:
Driver:
Desc: Microsoft Direct3D Mobile Reference Driver
Id:0
Name: d3dmref.dll
-----------------------
Hardware rasterization: false
-------------
Hardware T&L: False
-----------------
Using system memory


The program does run but veeeery slowly. It's looking likely that 3D accel is not to be found here. The interface does seem slightly snappier than the Kaiser, but we know how subjective that can be!

Have also run Omikron's D3DDrivers.exe, and get the following:
Driver info
Ordinal:0
Name: d3dmref.dll
Description: Microsoft Direct3D Mobile Reference Driver
Version: 222101509.67086

[dperren]

Sounds like htc is playing a dirty trick with us.
Remember how reviewers mentioned how fast the kaiser is , and how it beats every other xda on the market....
:rolleyes:If this is the case, it is absolute lawsuit gold. I know bait and switch has been mentioned in the past, but this is actually the very definition of it.

[NuShrike]

Looking like the 5K benchmark could have been fake, or incorrect, because there's no independent confirmation as the sci method dictates.

[duttythroy]

And the Spb results for the Kaiser (again on Dutty's latest Hybrid ROM)

Edit: ok, these are the Kaiser results. Doh. Trying to get the info out there too fast!

So my rom beat P6500 without the drivers cooked in, imaging the one i'm using now:)

[RacerII]

If this is the case, it is absolute lawsuit gold. I know bait and switch has been mentioned in the past, but this is actually the very definition of it.

Lawsuit probably wont ever happen.
However if its true, people will loose trust in htc's products.

But again , big chance that something went wrong with the benchmark.

[AllTheWay]

Sorry to butt in here but would it be possible to get a download location of the two ROM's being tested.

[fisha21]

Sorry to butt in here but would it be possible to get a download location of the two ROM's being tested.

Mine is currently on the Sedna sitting in front of me. Am just re-running a full Spb Benchmark on both devices (Sedna and Kaiser) and will then proceed to dump the ROM from the Sedna. Should be about 1 hour from now...stay tuned!!

[AllTheWay]

Mine is currently on the Sedna sitting in front of me. Am just re-running a full Spb Benchmark on both devices (Sedna and Kaiser) and will then proceed to dump the ROM from the Sedna. Should be about 1 hour from now...stay tuned!!

Thank you kind sir...much appreciated.

[Moskiitto]

Somebody they have a P6500 ... please Connect via QPST and look what CPU ID you have! I think ... if the P6500 is faster and use ATI Driver ... it have a MSM7200A CPU and not a MSM7200B like Niki, Kaiser or Polaris!

Hmm.. I found a post about this:

http://forum.xda-developers.com/showpost.php?p=1908390&postcount=10

//The MSM7200a is the 65nm version of the MSM7200 (90nm). The big difference is a speed boost for the ARM11 processor from 400MHz to 528MHz. I assume that there should be some benefits to battery life as well...not sure about any other changes.

Slacker//

Does't this proof that the sedna has MSM7200 not MSM7200A. Sedna has 400MHz processor doesn't it? I tried to find all devices using MSM7200A at www.pdadb.net and only one I found is: Sony Ericsson Xperia X1. Xperia has 528MHz processor.

Links:

Chipset:
http://www.pdadb.net/index.php?m=cpu&id=a7200a

Xperia specs:
http://www.pdadb.net/index.php?m=specs&id=1117

Kaiser and Xperia Comparison:
http://pdadb.net/index.php?m=pdacomparer&id1=1117&id2=733

Sedna and Xperia Comparison:
http://pdadb.net/index.php?m=pdacomparer&id1=1117&id2=822

[hidavi]

A different manufacturing process size doesn't change the functionality of the device, so the drivers should work the same for both.

[mimoracer]

fisha21 please can you write to us a mini review about sedna like camera performance video playback and coreplayer benchmark

[Moskiitto]

Arent we talking here about htc P6500?

There is HTC P6500 (HTC Sirius 100) and HTC P6550 (HTC Sedna)
Almost the same device.

Comparison link:
http://pdadb.net/index.php?m=pdacomparer&id1=822&id2=734

[fisha21]

So, repeating full Benchmark give Sedna a repeat graphics index of 3526, up 300 from 3226 previously. I'm fairly happy this is an accurate measurement of the Sedna sitting in front of me.

Perhaps Jockyw2001 could send me a link to the 2 test ROMs he is using, I can flash those to the Sedna and run benchmarks to see if there is a difference with the pre-production ROMs running on their native hardware?

I will post a mini-review on the device, but will be in a few days time. Look out for it in the Kaiser General forum next week.

[lubinda]

Maybe all it contains is the fix ment to come to kaiser that will hopefull be in the 6.1 rom.

[sebastianmc]

friends.. comparing benchs kais vc sedna... I think qualcomm doesnt have solution.... samsung 400mhz is so better...even intel´s cpus is so better... :(
who knows a decent driver will come in wm7 or never.... oh sh i t....

[fishpony]

friends.. comparing benchs kais vc sedna... I think qualcomm doesnt have solution.... samsung 400mhz is so better...even intel´s cpus is so better... :(
who knows a decent driver will come in wm7 or never.... oh sh i t....

uhhh.... WhAt???

[DarkDvr]

uhhh.... WhAt???

Only thing I undertood was "jesus is the right way" :D

[AllTheWay]

Perhaps Jockyw2001 could send me a link to the 2 test ROMs he is using

I would like to have those as well.

[sebastianmc]

Only thing I undertood was "jesus is the right way" :D
man... I had a hermes, qtek 9000, treo 700wx, treo 750, motoQ,,, now I have a kaiser, I made benchs of all pdas that I already had,, and I think htc isnt the problem,,, qualcomm is the problem.... this cpu is just a big s h i t...lol
sorry for my english :P

[fishpony]

Only thing I undertood was "jesus is the right way" :D

haha too funny. Maybe this is what HTC meant when they said they would release an update before the end of march. Since they legally can't just Give us the drivers without paying for the license on all the phones. They are paying for the license to use them in these phones because they KNOW that someone here will be able to dump them. That way they don't have to pay and we all get what we want. ofcourse they can't tell us that. Is HTC good guys after all??? Pretty Sneaky to get out of paying for them. well keep up the good work here guys.

[AllTheWay]

man... I had a hermes, qtek 9000, treo 700wx, treo 750, motoQ,,, now I have a kaiser, I made benchs of all pdas that I already had,, and I think htc isnt the problem,,, qualcomm is the problem.... this cpu is just a big s h i t...lol
sorry for my english :P

Should have used a Marvell or Intel chip. Qualcomm sucks.

[DarkDvr]

I suggest we try to keep this thread clean.
We're all anxious, some of us cant even sleep at night (maybe). Let deveopers do their thing, and just subscribe to the thread to get latest updates.

I'd also like to ask guys who are undertaking this to keep us updated on the issue..

[schulzj]

haha too funny. Maybe this is what HTC meant when they said they would release an update before the end of march. Since they legally can't just Give us the drivers without paying for the license on all the phones. They are paying for the license to use them in these phones because they KNOW that someone here will be able to dump them. That way they don't have to pay and we all get what we want. ofcourse they can't tell us that. Is HTC good guys after all??? Pretty Sneaky to get out of paying for them. well keep up the good work here guys.

That may be the smartest theory or we are giving HTC WAY too much credit.

[Kavalier]

Hi everybody, this is my first post to the forum.

I am noticing that the thread is becoming a tad off-track and disorganized and wanted to help refocus everyone, as well as help people not have to read through 25 pages to get a few leads.

Current possible leads:
Obtaining dump from reviewer website

Someone mentioned the spl dump would contain all parts of the rom, I saw the owner of the prepurchase sedna say in another thread that he had this and could post it

We have as I can see one dev with a sedna as well as a few more otw

I'm not sure if anyone has mentioned this, but I believe the official reviews of the kaiser were almost all stellar, with no reports of slowdown. That being said, it may be possible to solicit a reviewer for a dump of one of the review kaisers they recieved from HTC.

Current Requests/ problems
Many people have posted looking for the current test roms I believe there are two of these

there appears to be technical evidence of Bait and Switch with the reviewer phones, someone may want to forward this to the lawsuit people.

Someone brought up the possibility of there being more that one type of cpu, which could render the efforts useless. Can anyone substantiate or refute this possibility?

hope this helps get us organized,
Steve S

p.s. My first kaiser (att tilt) will arrive tomorrow, I am fully willing to flash it into oblivion if neccessary

[delta-101]

Perhaps Jockyw2001 could send me a link to the 2 test ROMs he is using, I can flash those to the Sedna and run benchmarks to see if there is a difference with the pre-production ROMs running on their native hardware?


Here is link to one of the rom versions Jockyw2001 is testing : (1.10.405.1_Radio_Sedna_1.58.21.23)
http://rapidshare.de/files/39014256/RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test.exe.html

And the other (1.02.405.1_Radio_Sedna_1.58.13.28)
http://rapidshare.com/files/104682305/RUU_Sedna_HTC_WWE_1.02.405.1_Radio_Sedna_1.58.13.2 8_signed_Test.exe.html

Hope that helps!

[AllTheWay]

Here is link to one of the rom versions Jockyw2001 is testing :
http://rapidshare.de/files/39014256/RUU_Sedna_HTC_WWE_1.10.405.1_Radio_Sedna_1.58.21.2 3_signed_Test.exe.html

Hope that helps!


Nice...do you happen to have the other one. I am really interested in that one.

[delta-101]

Nice...do you happen to have the other one. I am really interested in that one.

See original post...

[Moskiitto]

So... is there any success?

[thefunkygibbon]

So... is there any success?

patience. if there was dont you think there'd be a bit more talk about it?