This doesn't happen all the time but when I send an sms to a friend who I have sent plenty of messages to (more than usual friends) there is a lag in the animation when I send it. I have tried limiting the number of messages per thread and that did not help. It also doesn't seem to matter if there are a lot of apps open. It is very annoying and hopefully can be fixed. I am on the stock 2.3.5 firmware (KI3) but this has been happening since I got the phone. Any suggestions?
No one else has this problem?
I did when I first bought the phone, however after updating to 2.3.5 it dissapeared. I stopped usng it anyways, prefer handcent
i noticed that in 2.3.4 which i updated yesterday.....i tried to delete the conversation with lots of sms and it was smooth again, it wasn't doing so in 2.3.3. they fix one thing and another goes off, classic!!
gabrio
I fixed it actually by taking off split view. So far so good.
Related
Hello everyone. I recently ran into a problem, my text messages stopped sending. I am running the latest version of the community rom with the latest OTB kernel from nemesis2all. I have been running this setup since release and have had absolutely no problems. Until today.
Earlier this morning I was texting a couple people as usual. I use chompSMS as my messaging application. Sitting there writing a text when I get the "updates are available" notification from the market. I finish my text and start to update my apps. Everything seems to update just fine so then I reply to another text. It won't send. I try sending it again. No dice. Send like 5 other people a text. Nothing happens, besides "send failed" notifications. All of a sudden I get the crash vibrations and then my phone reboots, and I still can't send texts.
Any help or suggestions would be greatly appreciated. I have had this phone since September and have been flashing roms since before that. I know a pretty good amount of information but have never ran into a problem quite like this.
Does the stock messaging give you the same errors? If so revert to the last known working version of chomp with titanium.
good day.
chopper the dog said:
Does the stock messaging give you the same errors? If so revert to the last known working version of chomp with titanium.
good day.
Click to expand...
Click to collapse
Yes, the stock app gives me the same errors. I have tried reverting back to an older chomp and that doesn't work either. Everything else works, like calls, 3g data, gps, and I can receive texts. I just cannot send anything. It will try to send for like 5 minutes or so before I get a "send failed".
EDIT:Got it working. Didn't realize TiBu had latest version of chomp. Found an earlier version and everything works as it should. Thanks chopper.
hi all I am posting this as an "official" question in this section because it's a known issue and it's not been resolved. this issue was briefly (and by that I mean "very few replies") discussed in this thread: http://forum.xda-developers.com/showthread.php?t=1055407
I am wondering if anyone has come up with a solution or some more hints.
to sum things up:
- in a threaded sms conversation, upon sending AND receiving a message the small contact pictures (both yours and your interlocutors') flash one time (like if they were reloading: you can briefly see the grey android default "no picture" icon meanwhile). this didnt happen on elder builds, and when it happens the phone lags.
- it can happen from time to time that after this strange reloading the pictures won't load anymore and immediately after this, the app will loose sync with contact names too: you'll end with phone numbers anymore like if you had an empty phonebook.
I have found the culprit to be not the messaging app but the contacts app. when this happen, i "just" need to go back to home and tap the contacts app. sometimes it just displays a black screen, sometimes i get a FC message about com.android.process.acore. after pressing the FC button the app will restart and both contacts and messaging will return working normally (although still with the weird reloading thingy).
as far as things go it seems that
- hard resetting / wiping data does not help
- removing and re-adding the google account sync does not help
- it happens on 354 too
- not all users (very few, it seems) are affected by this
- there is no weird backup & restore voodoo procedure implied in the affected streaks
the small amount of users affected by this issue leads me to think we are, in some way, doing something wrong. any help would be greatly appreciated really. thanks in advance folks.
crashDebug said:
hi all I am posting this as an "official" question in this section because it's a known issue and it's not been resolved. this issue was briefly (and by that I mean "very few replies") discussed in this thread: http://forum.xda-developers.com/showthread.php?t=1055407
I am wondering if anyone has come up with a solution or some more hints.
to sum things up:
- in a threaded sms conversation, upon sending AND receiving a message the small contact pictures (both yours and your interlocutors') flash one time (like if they were reloading: you can briefly see the grey android default "no picture" icon meanwhile). this didnt happen on elder builds, and when it happens the phone lags.
- it can happen from time to time that after this strange reloading the pictures won't load anymore and immediately after this, the app will loose sync with contact names too: you'll end with phone numbers anymore like if you had an empty phonebook.
I have found the culprit to be not the messaging app but the contacts app. when this happen, i "just" need to go back to home and tap the contacts app. sometimes it just displays a black screen, sometimes i get a FC message about com.android.process.acore. after pressing the FC button the app will restart and both contacts and messaging will return working normally (although still with the weird reloading thingy).
as far as things go it seems that
- hard resetting / wiping data does not help
- removing and re-adding the google account sync does not help
- it happens on 354 too
- not all users (very few, it seems) are affected by this
- there is no weird backup & restore voodoo procedure implied in the affected streaks
the small amount of users affected by this issue leads me to think we are, in some way, doing something wrong. any help would be greatly appreciated really. thanks in advance folks.
Click to expand...
Click to collapse
I've the same prob. i was thinking it maybe from my rom (simple streak 1.2) but looks like its not.
yeah it seems to be an issue related to android 2.2.2 (I didn't have this problem on stock 318 rom). I have done some more tries yesterday but I didn't come up with a solution. I even tried to desync google account, remove all contacts etc, and create a new test contact with random picture, well as soon as I insert the picture the problem reappears.
I forgot to mention it in the op but go sms pro seems unaffected.
Contacts app in StreakDroid 1.9.1 does this as well.
I'm going to try and roll back contacts.apk, contactsprovider.apk and mms.apk from stock 318. I have checked the filesizes and they actually are slightly different.
well tbh I am 99.9% confident I will end up having to reflash my phone but oh well..
i'll report back!
EDIT: so here's the news. replacing apps didnt work. ROM 360 is still affected by the issue.
back to the drawing board...
I love Android, I truly do... but there is one thing I just cannot stand about any Android phone I've seen: the SMS app(s). The SMS apps and responsiveness of them are atrocious. I've had my system hang plenty of times when trying to send SMS along with MMS too, is there any reason for it? I don't see such an issue when it comes to iOS... I have no other UI responsiveness issues when it comes to Android other than anything SMS related.
I originally had an Acer Liquid E before, granted it's not the best phone, but I flashed a custom ROM for it, UI responsiveness was increased, however one problem still remained: SMS app(s) responsiveness. I recently purchased a Galaxy S2 LTE thinking that it would be fixed, however the problem STILL remains... and I'm boggled as to why it remains even after ICS.
Is there anyone that can provide some sort of explanation or has a similar annoyance with it?
tatootian said:
I love Android, I truly do... but there is one thing I just cannot stand about any Android phone I've seen: the SMS app(s). The SMS apps and responsiveness of them are atrocious. I've had my system hang plenty of times when trying to send SMS along with MMS too, is there any reason for it? I don't see such an issue when it comes to iOS... I have no other UI responsiveness issues when it comes to Android other than anything SMS related.
I originally had an Acer Liquid E before, granted it's not the best phone, but I flashed a custom ROM for it, UI responsiveness was increased, however one problem still remained: SMS app(s) responsiveness. I recently purchased a Galaxy S2 LTE thinking that it would be fixed, however the problem STILL remains... and I'm boggled as to why it remains even after ICS.
Is there anyone that can provide some sort of explanation or has a similar annoyance with it?
Click to expand...
Click to collapse
Same here, HTC Desire, 4.0.4.
Whenever I open a thread which has a larger amount of texts in it, the app hangs on loading and then on scrolling.
I think it's due to the way the interface for reading and storing messages (which is app-independent) has a sub-optimal way of retrieving them, causing the app to hang during operations with the database.
Number22 said:
Same here, HTC Desire, 4.0.4.
Whenever I open a thread which has a larger amount of texts in it, the app hangs on loading and then on scrolling.
I think it's due to the way the interface for reading and storing messages (which is app-independent) has a sub-optimal way of retrieving them, causing the app to hang during operations with the database.
Click to expand...
Click to collapse
I don't really get lag when opening convos, but only when sending SMS/MMS, not sure if anyone else has this issue or if you do too..
I've switched to Sky-ICS and I still have this issue with a little over 20k+ texts... I really, REALLY wonder if there is a fix to this issue, I'm sure I'm not the only one that experiences huge lag when sending and receiving SMSes (on stock or 3rd party apps).
Obviously removing the 20k texts would fix the issue, but I don't see why this should be necessary? iOS doesn't have this issue...
Hey folks,
Anyone have slowness within apps like handscent or chompsms? I thought it was a problem with handscent and switched to chomp but still have the same problem. When I go to open up a thread it stays on a blank transitions screen for a good 5 seconds at times and bouncing between conversations it loads them so slow. I have a stock untouched phone and just wondering if it is just me or what. I have rebooted and it does not seem to help. I guess I should use the stock app and see how it goes huh....
--Steve
What helped for me on my OG evo 4g is that I disabled defaults for stock messaging app. Try that and tell me if it helps.
Sent from my EVO using xda app-developers app
That is the first thing I do....it is also slow in ChompSMS. The default messaging app works fine. It definitely has something to do with 3rd party apps like Handscent and ChompSMS.....oh well.
I've been having this problem too. I am running Mean ROM 5.9. I was using Handcent. Since the problem starting happening, I believe in the last month or so, I've been switching between that and the stock messenger to see which works better. I just uninstalled Handcent in case that was a problem. It doesn't seem to be helping so far though. Maybe I'll try a restart.
I'm running the Viper 4G ROM and I started having this problem like a month ago using Handcent. It sometimes takes almost a full minute when I first try to open the app.
I think this could be an issue with the Facebook contact syncing. See here.
http://androidforums.com/htc-evo-4g...ngtone-issue-fix-8-29-12-a-2.html#post4989279
It's been a week now and I still can't send any text messages.
I receive msgs but unable to respond back...
I thought it was because I finally updated to Jellybean (I've had ICS for awhile so I thought I should just stick to that) but then I downgraded last night to ICS and I still can't send messages.
well today I tried fixing it but still no luck, although I tried sending an MMS instead, I sent myself a picture and it worked! even tried it to other numbers and they received it. I also tried adding a text with the picture and it did work. but it's still not working when I just type in a text...
so anyway in short, I can't send SMS but can send MMS (and receive messages as well)
also extra: I can call people but whenever they call me it comes up as unknown number...
Does anyone of you know what might be the problem? How can I fix it? Thanks
EDIT: and btw I already checked the message centre number and it has the right number in it so I don't think the issues w/ that
I suggest using titanium backup to store user apps and data, then using mr.cook's rom wipe script to allow you to start from a blank slate, then re-install the desired firmware (whatever version)
You could work at fixing this issue individually, but (to me) it's a sign that something more fundamental went wrong, and that other issues may be soon to follow.
It isn't clear whether you upgraded to a stock jellybean, or maybe a 4.1.2 custom jellybean, or maybe a 4.2.2 custom jellybean, or a 4.3 jellybean. The latter, a 4.3 upgrade from ICS has the highest potential for weird issues if a thorough rom-wipe isn't conducted... whichever path was taken, The i777 runs all versions of jellybean well, and something like this suggests that the "upgrade" was not conducted from a clean slate, hence the suggestion for a rom-wipe and re-install.
-Cyril
can't text
Are you unable to text because a keyboard won't open? My daughter couldn't text (never figured out why - she always had a keyboard appear) so she got a replacement, and when I inherited her phone because mine has battery issues, I go through periods when I can't text because no keyboard appears. I have to into settings and play around with assigning a default keyboard before it will finally appear. Doesn't matter if I'm using the stock keyboard or one I've downloaded from a VERY reliable source - I still have to reassign and reassign and reassign to make it work. Powering off the phone doesn't do a thing.