|
|
11-11-2007, 10:27 AM
|
||||
|
||||
|
looks real similar to 2.14 versions
"Adobe Reader"="2.00.261818" "AVDecDll"="1.00.070110.0" "Camera"="4.05.26938.00" "CyberonVSD"="1_2_b070626_0" "DShow"="1.00.070213.0" "HTCWMPPlug"="1.07.0412.0" "IOTA"="20070427" "LockStreamDRM"="1_1_x_070209" "MFCDLL"="1.0.20060406.0001" "mHub"="6.37.070320.X0" "RingtonePlugin"="1.00.070124.0" "ShareDLL"="2.0.070404.0000" 
|
|
11-11-2007, 10:34 AM
|
||||
|
||||
|
Quote:
So far, this seems the most stable of the official releases. More testing is required, but it may be a good candidate for a new ROM core.
__________________
Techcitement.com - I write for these guys pretty regularly. A Blog about tech that makes people excited.
Diary of a Mobile Enthusiast - My personal blog... haven't had time to update it.... *sigh* Hey, if I've helped you in any way, click the ads on my blog so I can make some $$!!
|
|
11-11-2007, 10:43 AM
|
||||
|
||||
|
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. Last edited by dcd; 11-11-2007 at 11:03 AM.
|
|
11-11-2007, 01:14 PM
|
||||
|
||||
|
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?
|
|
11-11-2007, 01:46 PM
|
||||
|
||||
|
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 Last edited by bunvilla; 11-11-2007 at 01:50 PM.
|
|
11-11-2007, 01:31 PM
|
||||
|
||||
|
Quote:
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
|
|
11-11-2007, 06:21 PM
|
||||
|
||||
|
Quote:
|
|
11-11-2007, 10:46 PM
|
||||
|
||||
|
Quote:
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.
__________________
Note: 3 Color screen is stuck in bootloader NOT "bricked"; just flash a stock rom exe
 Touch Custom rom unlocker Undoing advances in Mogul's since 2007. Titan ReLocker, WM5 roms (don't use w/ gps radio): Telus, TNZ
|
 |
|
«
Previous Thread
|
Next Thread
»
Hybrid Mode
|
|
All times are GMT -4. The time now is 05:14 PM.
