Results 1 to 3 of 3
  1.    #1  
    I've seen a few unanswered posts about duplicate SMS's and SMS messages being sent to the wrong area codes. I've been experiencing it myself, but haven't realized why until today. After nearly an hour with Verizon support, I realized they weren't going to be of any assistance. I dug a little deeper and performed a battery of tests.

    Before I post my entire report, I'd appreciate asking that others who have figured out ways to overcome the problem, please share their experiences.



    • I use a Treo 650 over Verizon Wireless. Firmware is 1.04a (same as 1.04).
    • My area code is 215.
    • LDAC, as used below, stands for "Long Distance Area Code", meaning any area code but 215.
    • All of the phone numbers in my Contacts list are in the following format: (AAA) PPP-XXXX, the Outlook-preferred format. Notice the space between the area code and the prefix.

    SMS recipients entered in different formats yields different results:
    Example 1 (manual entry): 302-555-6789
    Result (SUCCESS): 1 message sent successfully to 302-555-6789
    Example 2 (manual entry): (302)555-6789
    Result (SUCCESS): 1 message sent successfully to 302-555-6789
    Example 3 (number lookup from Contacts): (302) 555-6789
    Result (PARTIAL SUCCESS): Two messages in "Sent" folder
    1 message sent successfully to 302-555-6789
    *1 message sent to 5556789
    Example 4 (manual entry, by using PASTE): (302) 555-6789
    Result (FAILURE): Two messages in "Sent" folder
    1 message sent to 302
    *1 message sent to 5556789
    It also stated "2 recipients" at the top of the screen before I hit send! I can't yet understand why this would behave differently than Example 3.
    Example 5: (manual entry): (302) 555-6789
    Result (FAILURE): SMS app would not let me type in a space. It replaced it with a comma as if I was starting a new phone number. This explains it all!

    *For 7-digit SMS (at least via the Treo 650 over VZW), the area code is assumed to be the sender's area code. In my case, this is 215. There are 3 possible outcomes:
    Outcome 1: 215-555-6789 is a working MOBILE number, and the message gets delivered. Both sender and receiver are confused and get charged for the message.
    Outcome 2: 215-555-6789 is a non-working number, and sender is NOT charged for the message.
    Outcome 3: 215-555-6789 is a working LANDLINE. At this point, sender will get the following automated response from Verizon Wireless: "2155556789 is a landline #. Reply Y to send al TXT messages to this # as voice messages for $0.25/msg. + std msg fee. Details @, TexttoLandline". If sender takes no further action, sender is not charged for the message, and the message is not delivered.

    Parentheses and Hyphens seem transparent to the Treo 650's SMS and Dialer programs. However, spaces are apparently a problem. If spaces are being entered manually for a recipient, real-time SMS validation attempts to convert them to delimiters on-the-fly (instantly). Essentially, having any spaces within an SMS recipient address/number is likely to yield unpredictable results.

    RECOMMENDATION (preferred)
    Remove all spaces from within all phone numbers in your contact list if you do not need them for any other reason.

    RECOMMENDATION (alternate)
    Manually remove any spaces within a number/address as you're adding the contact as a new message recipient.


    There is another bug somewhere between the Treo 650's Contacts and SMS apps. I noticed this when sending a message to a mobile contact with the same last-7 digits as another mobile contact, each with different LDACs. Here is the sequence of events:
    1. Sent SMS to 917-555-6789.
    2. Message sent successfully to 917-555-6789.
    3. Received SMS reply from 917-555-6789 (confirmed, positively!). However, the number in the From: field of the reply was misrepresented as the name of my Contact at 267-555-6789.

    There is a bug in the way the Treo auto-associates a stored contact name with a message sender. This is probably not an issue for most, as having two stored contacts with the same prefix and exchange is a huge coincidence. No recommendation on this one.
  2. #2  
    Speaking of fixes, have you tries a phone with the latest VZW firmware? This bug may have been fixed ages ago. It doesn't occur in Sprint 1.13a.
  3. #3  
    Quote Originally Posted by supersocialist View Post
    Speaking of fixes, have you tries a phone with the latest VZW firmware? This bug may have been fixed ages ago. It doesn't occur in Sprint 1.13a.
    Sadly enough 1.04 was the last Verizon ROM ever released. I thought there was a rummor of a firwmare release late this summer, but i am guessing 700p being out killed that.

    As for SMS, I can definately confirm the first SMS bug and can add that once you are in a "conversation mode" it is not an issue.

    I can also offer SMS Bug#3

    Ever since visiting Hawaii, SMS messages from my wife show with timestamps in hawaiian time (off by 3 hours in my case, I am on Pacific time) My messages to her in MY 650 show up with correct local time and everywhere else in treo time is correct. Now HER verizon 650 has exact same issue with SMS messages from me being 3 hours early while her messages appear correct. Now the REALLY strange bit is that SMS messages from my sister, who lives in NY and ALSO has 650 (though GSM), also show up on hawaiian time - she never been in Hawaii. I SMS with a number of people localy and those timestamps are correct both ways -- none of them have 650's though.

    All of these problems started when we got BACK from Hawaii, not when we WERE in Hawaii. :-(

    It seems like with every generation Treo just gets worse and worse. I actually thought of upgrading to 700p, but looking at their forum and number of problems they are having made me rethink. I miss my 600, yeah it did not have bluetooth, but it was mostly functional - car speakerphone worked, SMS worked, and it did not crash every few hours...


Posting Permissions