I get this error about 2-3 times per day while text messaging. It happens randomly when I'm attempting to access my messages or while selecting to type out a new message to someone and then I have to hit 'ok' and go back and start over again (which will then work fine). Getting annoying. Any known fix for this? I'm using the stock messaging app that came with the phone and haven't added anything else to the phone.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
'Unfortunately messaging has stopped'
- Thread starter larry510
- Start date
-
- Tags
- lg optimus g
I was unable to capture a screenshot on the phone itself using quickmemo but I took a picture instead. It appears to happen the most when I tap on a message (with the phone in the upright position) and then quickly turn the phone around so that the screen orientation and keyboard move to the widesceen position for easier typing to reply.
Attachments
Someone over on androidcentral forums reported having this too. But I really expected to see more by now.
I would never send it in to LG. I don't want to risk getting the phone back even more messed up or with scratches on it plus I don't have a spare phone. I sold my spares on ebay last month.
I just don't think it's a serious enough issue for me to want to pay $35 either. It only happens about twice a day and once it does happen all I have to do is hit 'ok' and then it works again instantly. I will just live with it. My intention was to figure out if this was a widespread issue or not and was hoping others would confirm it so they would be forced to fix it in a software update. But I guess I just somehow got a defective phone (although on the Sprint buzz about wireless forum a couple of others reported the same issue). Weird how a defective phone would only have one thing wrong with one certain app and nothing else.
I suppose there's still a small chance that Jelly Bean will fix it.
I just don't think it's a serious enough issue for me to want to pay $35 either. It only happens about twice a day and once it does happen all I have to do is hit 'ok' and then it works again instantly. I will just live with it. My intention was to figure out if this was a widespread issue or not and was hoping others would confirm it so they would be forced to fix it in a software update. But I guess I just somehow got a defective phone (although on the Sprint buzz about wireless forum a couple of others reported the same issue). Weird how a defective phone would only have one thing wrong with one certain app and nothing else.
I suppose there's still a small chance that Jelly Bean will fix it.
Hopefully. Have you thought about calling star 2 and letting Sprint corporate techs know about the problem? Just to make sure it's logged? I have to admit, twice a day seems like too often to have to live with that.