I have a QWEST 6800 w/ROM v2.13 & Radio 1.39

[dcd]

dishe, could you please cite your sources, or give detail on your own testing to produce these claims. i have compared the following files from 2.13 and 2.14:

btagext.dll
bthamb.dll
bthci.dll
bthcsr.dll
bthsc.dll
bthuart.dll
Serial_BTUR.dll
BT_FIR_Param.txt
BT_Init_Script_TI_300.txt
BT_Init_Script_TI_311.txt
BT_Init_Script_TI_331.txt
BT_Name_INFO.txt
AudioPara.csv
AUDPP_PARAM_TABLE_SYSTEM.TXT

THESE FILES ARE IDENTICAL. Compared with WinMD5.

The OEMDrivers rgu contains the following in 2.14, but its absent in 2.13:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\Layouts\e0010409]
"Keyboard Layout"="00000409"

Otherwise the rgu's are identical.

OEMDrivers that ARE different:
SDHC.dll
battery.dll
msm7500usbfn.dll
rilphone.dll
allledmgr.dll
cif.dll
keybddr.dll
virser_atcmd.dll
virser_dmr_dpram.dll


While I really do appreciate the OP's effort to obtain this rom for us (I like to have as many sources as we can find) I do not see anything 2.13 offers us that we dont have from 2.14 (yet)

Also, I have not looked, but I beleive ImCoKeMaN is packing these into a donor .nb using the 2.09 XIP/kernel. That could have some effect on testing results.

[bunvilla]

i was wondering if i should have done a hard reset before i made a copy of the raws files/ because i do use a different comm mgr and and applied a few reg tweaks and some over progs that might possibly affect what is copied/ or is the raw files the core files which always stay with in the rom?

[bunvilla]

this goes to DCD, im not a real "get in there and right my own kind of drivers guy" and i do understand what u r saying about making sure that there is sufficient information and accurate feedback b4 we jump to conclusions and do something like "sprint might have done, and release something that wasnt thoroughly tested.
my question is : can some of the carriers extra "junk" play a role in the performance of the drivers (BT 4 example) and it not really not be an issue with the drivers themselves.
example ; sprint has the whatever u call it TV service, which im sure requires drivers that lets say QWEST or Verizon wouldnt have in there ROM version because they dont offer that service. And thus indirectly causing issues that might not show up in 1 version of a ROM release but show up in another ROM release even though they still have the same driver version in them / and maybe some reg settings like when verizon made it so u couldnt get phone calls while using wifi- or data connect/ r we possibly looking for the best combination versus needing totally modified drivers/
i think that dishe could possibly be expierencing those results even though the drivers are similar/ with checks and balances i think we could come up with a great ROM with no help from HTC or the carriers/
And i do appreiciate all u do for the seen DCD , we someone to be objective at times to make sure we dont get ahead of our selves/
keep up the good work EVeRY1

[DogGuy]

Originally Posted by dcd

dishe, could you please cite your sources, or give detail on your own testing to produce these claims. i have compared the following files from 2.13 and 2.14:......I do not see anything 2.13 offers us that we dont have from 2.14 (yet)

Also, I have not looked, but I beleive ImCoKeMaN is packing these into a donor .nb using the 2.09 XIP/kernel. That could have some effect on testing results.

Being unable to force the crashing failure to return from standby is a plus. I spoke with someone running it while they were on BT and the quality was slightly echoy, but very good. Other than a forced disconnect, we have not been able to replicate the DSOD that I personally experience with Alltel at will. More testing is needed of course, but if you simply removed the crashing from Alltel's faults, you'd have my ideal BT rom.

- DogGuy

[dcd]

Originally Posted by DogGuy

Being unable to force the crashing failure to return from standby is a plus. I spoke with someone running it while they were on BT and the quality was slightly echoy, but very good. Other than a forced disconnect, we have not been able to replicate the DSOD that I personally experience with Alltel at will. More testing is needed of course, but if you simply removed the crashing from Alltel's faults, you'd have my ideal BT rom.

- DogGuy

hm, i can see how the crashing would obviously be a plus, but after comparing the differences i just dont see how BT would function any different in 2.13 than it does in 2.14, unless its thanks to the 2.09 kernel. maybe we should throw 2.14 into a 2.09 nb and see.

[ImCoKeMaN]

Originally Posted by dcd

Also, I have not looked, but I beleive ImCoKeMaN is packing these into a donor .nb using the 2.09 XIP/kernel. That could have some effect on testing results.

dcd,
The nbh in the rar on the ftp link i posted will split out into an nb. It has the xip from the qwest rom not the 2.09.


also, the radio can not be dumped with pdocread which is why there is no 1.39 radio available for this.