View Single Post
  #76 (permalink)  
Old 08-08-2007, 04:55 AM
johnksss's Avatar
johnksss
Lurker
Offline
 
Join Date: May 2007
Posts: 2
Reputation: 0
johnksss is a n00b
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: Overwritten SMS FROM Address Defect

Quote:
Originally Posted by plargen
Quote:
Originally Posted by Kolano
Quote:
Originally Posted by SpankyDevil
im still having problems with my texts they are not showing who they are sent from instead they as saying its sent from the first word in the text message and if i hit reply it trys to send it to "hey or hello etc etc

cheers
...we don't have a solution yet, but need details to work one out...

Which carrier OEM are you using?
I recreated the "overwritten SMS FROM address" defect as follows:

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.

edited:
my post was bogus and the error is still there...
Reply With Quote