|
||||
Quote:
|
|
||||
Quote:
http://www.ssec.wisc.edu/data/paw/ You should be able to get the image links from there, or just bookmark it in your browser. |
|
||||
Overwritten SMS FROM Address Defect
Quote:
I tried several ROM builds, each exhibiting the defect if I let the Extended ROM load, and not exhibiting the defect if I reset before Extended ROM loaded. I therefore loaded each line of the Extended ROM manually, sending a text message between each installation until the defect appeared. I repeated the test to prove it was not intermittent and could be recreated. My test environment is radio 1.41 with Sprint service and the following minimal 1.04 ROM build: Transcriber Enterprise Games Windows Live Mobile NET Compact Framework II.sp2 SqlCe Mobile Windows Media Firmware Update Remote Desktop Mobile Office 2005 HTC Camera 10-Button Comm Manager Cyberon Voice Commander Crossbow Dialer HTC Smart Dial Microsoft Internet Sharing Wireless Modem (Wmodem) I have seen the defect exhibited with radio 1.29 as well, with 1.02 and 1.03 ROMs, and with or without the Sprint Extended ROM OEM option selected. However, I did not repeat this test in other environments as it is time consuming. My Extended ROM config.txt is as follows: LOCK:Enabled SHOW:\Extended_ROM\Sprint_Logo.bmp CAB: \Extended_ROM\PPST_FILE_SPCS_1_19_003_with_PRL2022 4.sa.CAB EXEC:\Windows\PPST.exe CAB: \Extended_ROM\DirectShow.sa.CAB CAB: \Extended_ROM\RTPlugin_CDMA.sa.CAB CAB: \Extended_ROM\Cert_SPCS.sa.CAB CAB: \Extended_ROM\Cert_SPCS.CAB CAB: \Extended_ROM\IOTA.sa.CAB CAB: \Extended_ROM\Customize_SPCS.sa.CAB CAB: \Extended_ROM\ButtonLock.sa.CAB CAB: \Extended_ROM\Enable_RingTone.sa.CAB CAB: \Extended_ROM\PhoneSetting_HelpFile.sa.CAB CAB: \Extended_ROM\PowerICON.sa.CAB CAB: \Extended_ROM\TimeSnyc.sa.CAB CAB: \Extended_ROM\ResString.sa.CAB CAB: \Extended_ROM\PP_IOTA_v1_10_Apache_206300.sa.CAB CAB: \Extended_ROM\PP_ErrCodeForSPCS_Apache_206300.sa.C AB CAB: \Extended_ROM\PT_RemoveHTCBatteryICON_Apache_20630 0.sa.CAB CAB: \Extended_ROM\PP_Version_Apac_206303.sa.CAB CAB: \Extended_ROM\PP_HTC_CM_Guardian_Apache_206300.sa. CAB CAB: \Extended_ROM\PP_LockUp_Apac_212705.sa.CAB CAB: \Extended_ROM\PT_Ril_Apac_206301.sa.CAB CPY1:\Extended_ROM\AddContact CPY2:\Windows\AddContact EXEC:\Extended_ROM\AddContacts.exe LOCKisabled RST: Reset The error does not occur until PP_LockUp_Apac_212705.sa.CAB is loaded and a soft reset is performed. You may test this by loading each cab in order, performing a soft reset, and sending a text message to yourself. I compared the Extended ROM that came with my PPC-6700 when I received it with the current contents. It did not have the following four lines: CAB: \Extended_ROM\PPST_FILE_SPCS_1_19_003_with_PRL2022 4.sa.CAB EXEC:\Windows\PPST.exe CAB: \Extended_ROM\PP_LockUp_Apac_212705.sa.CAB CAB: \Extended_ROM\PT_Ril_Apac_206301.sa.CAB In addition, instead of executing CAB: \Extended_ROM\PP_Version_Apac_206303.sa.CAB the older config.txt executed CAB: \Extended_ROM\PP_Version_Apache_206300.sa.CAB and the files are different sizes. I had purposefully removed the following junkware lines from both versions: CAB: \Extended_ROM\Fetch.CAB CAB: \Extended_ROM\WTLAudiblePlayerPocketPC.arm.CAB CAB: \Extended_ROM\AudibleSample.sa.CAB CAB: \Extended_ROM\Getmail.ppc2003.ARMV4Rel.sprint.CAB CAB: \Extended_ROM\sprint_software_store.CAB CAB: \Extended_ROM\GetGL.CAB That's my complete analysis. I can recreate the error, but I do not know how to solve it. I hope this can help someone locate the conflict. I can do additional testing upon request. Thanks for everything. |
|
||||
Re: Overwritten SMS FROM Address Defect
Quote:
edited: my post was bogus and the error is still there... |
|
||||
plargen excellent analysis but if you are allowing any of your ExtROM to load then you've missed the point of building in the Sprint Carrier Customization OEM. The reason those exist is so you don't have to install the ExtROM contents.
I made those OEMs for a few reasons (one of which is to leave out the junkware) but the main reason is that these ExtROM cabs were designed to be applied to an AKU2 environment--so in cases like the Apache lockup cab it is actually overwriting newer dlls in your ROM with OLDER (AKU2-era) ones. That's why your text messages got screwed up. For the very first person who had this problem, we narrowed it down to the fact that he was letting the ExtROM install (even after building in the OEM package for his carrier). I suspect every person that has experienced this issue since then is doing the same thing (whether they realize it or not). Just to reiterate for anyone else reading, so there is no confusion--by checking the box for your carrier while building your ROM you have already included all of the "good" parts of the ExtROM contents into the ROM itself--you should therefore never allow the ExtROM to install on the first boot (do a soft reset at the "customize your device in 3 seconds" box). To save yourself that hassle in the future also include the "Unlock and Unhide ExtROM" OEM (it is selected by default). Then you can tap the "ExtROM Unlock" application in Start->Programs, navigate to "Extended_ROM2" using file explorer, and delete out all that crap. Once it's gone you won't ever have to worry about preventing it from installing. |
|
||||
Great work on this kitchen but let me ask...
1) Is it intentional that the 10-button comm mgr has no icon for sound off? If you turn the volume off with the sliders and then go into comm mgr there is no longer an icon under ringer. 2) Other than making ext rom hidden, is there a way to make the ext rom not show as a storage card or to mount the actual storage card before the ext rom loads because this set up is forcing certain programs to automatically write to the ext rom which is not something that is necessarily desired i.e., live search sets the cache here and there appears no way to move it anywhere else. As well, outlook wants to load the mail attachments here. 3) Does anyone else get the sensation that this build is not as peppy and a little buggy? I dont know what it is as I am not able to place my finger on it but for some reason I find myself having to tap my screen more than once to get something to click (less responsive) and menus dont just pop up they kind of crawl (compared to the 1.02 kitchen build). Keep in mind I'm not talking about changing menu animations or altering the cache etc. Before all the adjustments are made, my unit is usually very snappy - kinda gets bogged down as Im loading all my software and then picks up again after I alter the caches and turn off animations. With this build however it kind of feels heavily bogged down from the start (I put next to nothing on my rom build). As well I have seen some very strange behavior such as blinking cursors, such as you would see at the end of a line of text, in the middle of the today screen and the whole 'locking up when soft rebooting' thing and also other minor stuff happening (nothing consistent, but def. obvious and fluky) such as going into settings > today and clicking on options for say audionotes and being brought to the options for spb phone suite (both installed after the kitchen but worked flawlessly together on every other rom) 4) Was using internet sharing yesterday and for whatever reason the unit kept switching back and forth btwn evdo and 1x... I dont know if it was a system thing or a unit thing but overall very poor performance. Ill keep an eye on it. Thanks and again great work.
__________________
d6l9p
Peace Within... |
|
||||
Quote:
|
|
|
|