issues with droid and messaging appSupport


Last Updated:

  1. Njbrodeur87

    Njbrodeur87 Member This Topic's Starter

    Joined:
    Oct 31, 2009
    Messages:
    22
    Likes Received:
    0
    hey guys i have had no issues with my droid till this morning and i have had it since launch...the issue is when i texting in the messaging app every few texts the app will not let me type inthe box and wont respond to my touch and ill finally 5-10sec later get a force close or wait button. This has started happening today...anyone else see this before?
     

    Advertisement
  2. Njbrodeur87

    Njbrodeur87 Member This Topic's Starter

    Joined:
    Oct 31, 2009
    Messages:
    22
    Likes Received:
    0
    well i went ahead and returned my droid for a new one...i took advice from people that on the back off battery if it says 40/09 its the first one relaized which was my old one...the one i got repalced is now 42/09 which seems to be better in alot of ways...camera works almost everytime, unlike before with long load times andproblems with autofocus, battery life im still testing, and so far no messaging crashing but we will see as time goes on...seems like its btter though as some suggested with the newer model.
     
  3. dmgabe

    dmgabe Well-Known Member

    Joined:
    Nov 9, 2009
    Messages:
    122
    Likes Received:
    0
    I have a 40/09 and it is solid. I did exchange my first droid, also a 40/09, for a headphone jack problem, but haven't had any other issues. I don't really think that any of the common problems can be traced back to a particular batch of phones.
     
  4. Njbrodeur87

    Njbrodeur87 Member This Topic's Starter

    Joined:
    Oct 31, 2009
    Messages:
    22
    Likes Received:
    0
    yea ur right cause now i just had the messaging app do same thing on this phone...maybe its a software issue not hardware...cause it very well could be. seems like i can only get it to happen when the phone goes to sleep while sitting in the texting app is when it happens...if i text then go back to hoemscreen then goes to sleep and wait for a text then go back in messaging then their hasnt been any issues...weird
     
  5. dmgabe

    dmgabe Well-Known Member

    Joined:
    Nov 9, 2009
    Messages:
    122
    Likes Received:
    0
    You could try handcent to replace the default texting app and see if it does the same thing. Free program and much more customizable than the stock app.
     
  6. vincentp

    vincentp Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,640
    Likes Received:
    59
    I've used Handcent and Chomp. Handcent does crash sometimes, but not as much as the default messaging app. I haven't had a crash or issue with Chomp yet, I just hate the stupid bubble chat.
     
  7. dmgabe

    dmgabe Well-Known Member

    Joined:
    Nov 9, 2009
    Messages:
    122
    Likes Received:
    0
    I have been using handcent since I got my phone on 11/07. I have not had a single crash. The only issue I had, as previously mentioned, was the lag. If you find that you also have the lag problem, I have a beta from the developer that fixes this issue. Chomp could be a very good app also, I just have no experience with it. I am pretty sure they both offer the same functionality.
     
  8. jjl207

    jjl207 Member

    Joined:
    Nov 18, 2009
    Messages:
    7
    Likes Received:
    0
    Yeah, I have had the messaging app crash twice (process android.mms) and had to pull the battery to get it to work again and it deleted all of my stored texts. I'm going to try Handcent for a while, see if I have the same problems.
     
  9. Keola

    Keola New Member

    Joined:
    Nov 18, 2009
    Messages:
    3
    Likes Received:
    1
    APPLIES TO: Users who have Anonymous Caller ID Block activated by their cellular service provider. This is where your caller ID information is automatically blocked when you make a phone call (i.e. the person receiving your call sees "private" or "blocked" on their caller ID). In order to allow your caller ID information through, you need to dial *82, then dial the telephone number as normal.

    ISSUE / PROBLEM: Messages SENT from the message app do not go through to the recipient, and you do not receive a warning that your message was not delivered. This also affects the contacts app -- if you list BOTH the *82-nnn-nnn-nnnn and the nnn-nnn-nnnn numbers in separate phone number fields, only the *82-nnn-nnn-nnnn appears in the list when you select a contact for dialing or messaging. And it is the *82 that causes outgoing text messages to fail.

    SOLUTION (until there is a fix to resolve this problem for the message app and the contact app):

    1) Call your cellular service provider and have them remove Anonymous Caller ID Block from your phone number. You can always activate anonymous caller ID block on a call-by-call basis by dialing *67 before your dial a number.

    2) Remove the *82 in front of the listings in your contacts app.

    3) AND VERY IMPORTANT: Delete ALL message threads from numbers that previously contained *82 in your contacts app.

    ANALYSIS: It seems that once you have a number with *82 entered in your contact app, any text message you send to that number will use *82, even though you strip that out the *82 in the "To:" field prior to sending the text message. AND, the message app REMEMBERS the *82 process in the message thread even after you remove the *82 from the contact app.

    For example, I save John Doe's mobile number in my contact app as *82-123-456-7890. I go to my message app and send a text to 123-456-7890. Somehow, the message app "cross-references" this number with my contact app and (without my being aware if it) ADDS the *82 in front of the 123-456-7890 before sending the text. This causes the text to fail without warning.

    Even after I delete the *82 prefix in my contact app, the message app still uses (cross references) all message threads with the number 123-456-7890 and ADDS *82 in front of the number.

    So, once you delete the *82 prefix from a number in the contact app, you must then susequently delete ALL message threads that contain that number in the message app, otherwise message app will still append the *82 prefix from old message threads.

    I hope this helps someone. It took me a day to figure this out.
     
  10. jjl207

    jjl207 Member

    Joined:
    Nov 18, 2009
    Messages:
    7
    Likes Received:
    0
    I tried Handcent, and though I love the app, I got the same android.process.mms crash I had with the default messaging app. I think it is a bug in the OS itself, and Keola's situation doesn't apply to me, though that is great info.
     
  11. dj.shiftie

    dj.shiftie New Member

    Joined:
    Nov 28, 2009
    Messages:
    4
    Likes Received:
    0
    I have also had this same issue with both the native messaging app and chompsms. I believe it is an os glitch as well ...we need an update. With any luck we will get one around December or January. In any case the phone and the network are on point.


    ~FROM SHIFTIE'S DROID~
     
  12. jjl207

    jjl207 Member

    Joined:
    Nov 18, 2009
    Messages:
    7
    Likes Received:
    0
    I think I found the problem. I had had Better Keyboard installed, but removed it. After re-installing it, the crash but has gone away. Don't know why that would cause a problem, but I switched to Chompsms and both it and the native messaging app work fine. Weird, but at least I've stopped losing messages and having text messaging crash my phone.
     
  13. dj.shiftie

    dj.shiftie New Member

    Joined:
    Nov 28, 2009
    Messages:
    4
    Likes Received:
    0
    So it is called better keyboard? And you have not had a problem since?
     
  14. rcummings67

    rcummings67 Member

    Joined:
    Nov 27, 2009
    Messages:
    6
    Likes Received:
    0
    I seem to be having the same issue. I wanna message someone back so I touch the field that brings up the "better keyboard" and one I go to type it doesn't display in the field. It's weird cause I noticed when it does show up in the messaging field, there's an orange outline around the reply box. When it decides to not let me message someone, then there is no orange outline. Kinda strange and under my battery it says: 43/09.
     
  15. jjl207

    jjl207 Member

    Joined:
    Nov 18, 2009
    Messages:
    7
    Likes Received:
    0
    Yes, Better Keyboard. But keep in mind that I had had a messed-up installation that I had removed, and re-installing it fixed the problem. It's also a paid app, 3 bucks I think.
     
  16. dj.shiftie

    dj.shiftie New Member

    Joined:
    Nov 28, 2009
    Messages:
    4
    Likes Received:
    0
    I found it. awesome! I'm going to DL it on payday because this is becoming quite annoying

    Thanks for your suggestion
     
  17. bevginn

    bevginn New Member

    Joined:
    Dec 9, 2009
    Messages:
    2
    Likes Received:
    0
    Each time I send or receive a text I get a force close notice on the messaging app. Is there a solution to this? If not, should I wait for the update, or simply take the phone back to Verizon for a replacement?
     
  18. Phone Guy

    Phone Guy Well-Known Member

    Joined:
    Nov 18, 2009
    Messages:
    51
    Likes Received:
    0

    For most contacts I have *82 in front of the number which will unblock my number because I have my caller ID blocked by default through Verizon. Because text messages will not work with *82 in front of the number I store the same contact without it and use that for texting.

    My Droid when texting will sometimes replace the current number I am using with the *82 version even if I have deleted the *82 number for that contact. The only way I know this has happened is when the person I am texting says they did not received it or if I am texting someone who is also on Verizon network and the text delivery status will stay at pending.

    I did a factory wipe and this has fixed the problem. The *82 number stays in the correct field.
     
  19. DRD318

    DRD318 New Member

    Joined:
    Dec 12, 2009
    Messages:
    2
    Likes Received:
    0
    I'm already on my second droid because of the force close problem. After getting it replaced I had the same problem with the new one so it wasn't just my phone. I tryed the handcent, still force closed. I love the phone other than this one glitch, hopefully they fix it.
     
  20. dj.shiftie

    dj.shiftie New Member

    Joined:
    Nov 28, 2009
    Messages:
    4
    Likes Received:
    0
    Not one messaging app force close since the OTA update. Anyone else?
     
  21. kimberley

    kimberley New Member

    Joined:
    Dec 15, 2009
    Messages:
    2
    Likes Received:
    0

    This really help me. It was exactly what was preventing some of my contacts to NOT recieve texts, they would recieve calls from me just not texts. Thank you for taking the time to post this awesome information.
     
  22. jjl207

    jjl207 Member

    Joined:
    Nov 18, 2009
    Messages:
    7
    Likes Received:
    0
    Nope, not one force close for me either.
     
  23. tgranted

    tgranted Member

    Joined:
    Nov 18, 2009
    Messages:
    12
    Likes Received:
    0

    Yes. I have gotten many force closes and deleted sms messages even after the update. I use Handcent and I uninstalled it yesterday. I will see if the stock has the same problem.

    I had to download the app smsbackup in order to keep from losing my text msgs. PITA
     
  24. jjl207

    jjl207 Member

    Joined:
    Nov 18, 2009
    Messages:
    7
    Likes Received:
    0
    I haven't had issues with ChompSMS since the update, that may be worth a try.
     
  25. kimberley

    kimberley New Member

    Joined:
    Dec 15, 2009
    Messages:
    2
    Likes Received:
    0
    Okay I have a new. I have a pop3 email from centurytel.net set up on my droid and the driod is deleting my emails. I have it set to not delet from server but it is and on phone to. This is the second phone so its not my email service through centurytel. Its this phone any comments?
     

Share This Page

Loading...