Hi,
I use CM9 nightly 20120611. A few weeks ago, after installing a nightly, I've started having issues with the messaging app. Sometimes after sending a text message, the application force closes, and the text is either received by the recipient or not, but the state of the message will remain 'Sending' even when restarting the app...
Sometimes just entering the app will cause it to hand and FC, especially right after going back from a message thread to the main app screen...
I have a bit over 10,000 messages, and I'm trying to figure out if that's the issue, or the new nightly, or both combined?
Has anyone else come across this?
Thanks!
Related
I'm hoping someone can shed some light on why this is happening to my vibrant all of a sudden. Quick little history on my phone: samsung vibrant, purchased 8/25, no modding, no rooting, no lag fixes, no nothing, straight out of box...i started getting this message after I sent a few normal yahoo emails out the other night:
Application process com. android.email has stopped unexpectedly. Please try again: dumpstate_app 201010071404_com android email.
Log has been saved. Use *#9900# to copy out log.
When I do the *#9900# it takes me to a few options, none of which I would have any clue about which to pick. Does anyone know what this is, how I can get rid of it? I use the app that came on the phone to access my yahoo email ( the app is the one that has the white envelope with the blue at symbol on it. I have deleted the account and configured again but nothing, I received the force close message again 10 min later. I had one person who tried to help me for hours, poor guy! But I really just want to find whatever it is that's doing this. I installed the offical yahoo app and its been working ok, a little slow, glitchy, freezes a lot, but I'm getting my email without a force close! Thanks to my tmobile friend who suggested the app...i would appreciate if anyone could help me. Thanks so much!
You should look for an email you just received that may be corrupted somehow. If you figure out which one, try to delete the email (online). I got similar messages repeatedly after I created a Google contact on line and it appeared in my phone's contacts. I had left the year off the person's birthdate and apparently there's a bug in the Vibrant such that it chokes and core dumps when it encounters an empty year field. I deleted the contact (on line, because I couldn't get to it on the phone without force closing) and the problem went away.
dirtyhamster73 said:
I'm hoping someone can shed some light on why this is happening to my vibrant all of a sudden. Quick little history on my phone: samsung vibrant, purchased 8/25, no modding, no rooting, no lag fixes, no nothing, straight out of box...i started getting this message after I sent a few normal yahoo emails out the other night:
Application process com. android.email has stopped unexpectedly. Please try again: dumpstate_app 201010071404_com android email.
Log has been saved. Use *#9900# to copy out log.
When I do the *#9900# it takes me to a few options, none of which I would have any clue about which to pick. Does anyone know what this is, how I can get rid of it? I use the app that came on the phone to access my yahoo email ( the app is the one that has the white envelope with the blue at symbol on it. I have deleted the account and configured again but nothing, I received the force close message again 10 min later. I had one person who tried to help me for hours, poor guy! But I really just want to find whatever it is that's doing this. I installed the offical yahoo app and its been working ok, a little slow, glitchy, freezes a lot, but I'm getting my email without a force close! Thanks to my tmobile friend who suggested the app...i would appreciate if anyone could help me. Thanks so much!
Click to expand...
Click to collapse
Go to app manager in settings and try clearing data. Also, as previous post suggests try deleting the email from online server and restart the sync process.
Thank You all! The force close issue is still happening. I've started using the browser to receive my yahoo email. I've done everything you all have suggested and nothing has helped. Thank you all again.
there doesnt appear to be anything in search relating to this so here goes.......
.....im getting sick of htc changing so many features and settings on this phone everytime they release an update. ive got another issue now. not mentioning the dozen ive managed to sort myself in the last day or so.
my text messages are now all over the place. if i recieve a message i hit the message icon on the scroll bar and it opens. reply and then close. normal situation. however. when i want to send another message to the same person either by opening their contact info or hitting the message icon and finding the conversation there is no info at all. wtf!!!
if i go to all messages i get a list of all recipients and the last message either sent or recieved but when i click on that person to reply the entire conversation, 1,2 10, 100 messages that are in brackets next to their name are nowhere to be seen. ive tried removing contact pictures, deleting numbers and attaching them to the contact when a message comes in. no luck. been through the messaging settings, cant find anything else to check or uncheck to resolve this situation. ive no contacts on my sim card just the phone.
cheers. i do need to know if its a general thing with this rom or is my phone just playing up? anyone else noticed this? communications is a big part of messaging and as all phones nowadays seem to be able to record and display conversations with each contact i find it hard to believe htc suddenly decided to bin the idea.
anyone got any suggestions as to how i recover this option as i cant be asked to remember the last few messages of every conversation i have. not to mention important information that i cant access if i cant pull up more than one previous message!
I have the new stock Rom 3.14, and I haven't encountered anything like you've described here. What application did you use to restore the backed-up messages after you flashed the ROM?
fixed this. i had installed a cab recently which disables the annoying 'sent message successfully' notification. but this was also causing the above mentioned problem. unistalling the cab means ive got my conversations back and all contacts/messages link properly. see here for all info and further links... http://www.htchd2forum.com/general-htc-hd2-discussion/more-hatred-for-new-3-14-rom-(conversations)/
So when I was on stock, periodically my stock Moto sms app would say "phone storage full, delete some files to make room" and not show any messages. Sometimes I would have to reboot, clear a lot of cache or something, force close the app, etc. etc. to get it to work. And then I started using GoSMS and when it happened, Go would just not show any messages, and without any error messages. Then I go into stock and try to fix.
Now on GingerBlur, with the stock messaging app, sometimes it does the same thing, but it has way more problems...Messages randomly won't send in Go, and I open the gingerbread stock app and it continuously force closes. I HAVE to reboot in these circumstances, which is very frustrating. It basically just crashes in a ton of different ways, and no amount of cache clearing or force closing or anything will fix, so I'm forced to reboot like 3 times a day to fix this. It happens randomly. I'll be texting someone, no problems.. Then I'll just get another text from them at some point in the conversation and when I open like normal it'll just crash (stock AND GoSMS). This is a really frustrating problem, does anyone know what the deal is? Perhaps this phone isn't meant to have the Gingerbread stock messaging app?
Then again, i still had problems on Motoblur with the Moto app...
Hi guys,
I'm having an issue where if I reply immediately to a text message, my text bubble will appear on top of the message I have replied to.
Both timestamps will show the same time, eg 11:20am, but even though I had received the message first and THEN replied to it, the order of my reply is ABOVE that of the message that I received.
It's rather weird. I have tried playing around with time settings. Someone had advised me to clear cache of the MMS app, but the option to clear cache is greyed out.
Anyone facing similar issues?
I'm on Leomar 2.7.1 KI3, Siyah kernel 1.8. Using Muveszur's MMS apk mod.
I think I fixed that by installing Go SMS and leaving the notifications for Go off and letting it run in the background.
I'm not sure if that will work for you, but try.
You could also try using "sms time fix" and set the delay time accordingly.
Thanks for the help guys, I dont really want to use a third party messaging app like GoSMS.
Thanks for SMS time fix, I guess it helps, but is there any way to fix my default messaging app itself?
I did not use to have this problem prior to upgrade to leomar 2.7.1 and/or muveszur's mod.
Hey guys...so since I've owned my V30 I've always been a user of Google's Messages app. It works flawelessly other than the fact that MMS's and Group Messages don't always come through. They'll show who sent them and state something along the lines of "unable to download, please click to retry" after doing so, sometimes the message is recovered sometimes it is not able to. More often not able to. Recently, it would seem I've become more annoyed with this issue. After many calls back and forth the with T-Mobile they've recommended I ditch Google's Messages app and use the included LG Messaging app.
Well, I can tell you...I no longer have issues not receiving MMS's or Group Messages....The issue I have now is, the LG app is SUPER SLOW. It can take 10-30 seconds just to open a chat....and if I have a group chat open with an active chat...the entire phone and app will freeze until the last message has stopped being received.
Does anybody have any suggestions to getting Google Messages working, or speeding up the LG Messaging app? I am not rooted so I'm stuck using this crappy app even disabled and not the default messaging app. I also removed LG Package disabler to see if turning something off was the issue but it is not.