I have an issue when I am reading a text message and then click OK to go back to my inbox. It will show the inbox but also show remnants of the text message I just read at the top of the screen. It is locking the phone up for about 15 seconds. It seems as though it has to reload all of my messages in my inbox. This is a Tilt 2 with the stock rom on it.
Any help would be greatly appreciated.
I didnt have much experience with the ATT stock ROM...but with most custom ROMS that include the HTC Text Messenger it is a common problem. I changed to a Custom ROM that doesnt include the HTC messenger....and uses the Windows Mobile Text Message interface..much quicker. The latest Energy ROMS utilize the Windows Mobile Text interface.
Might try clearing out old text messages if they are not important...should help with load times.
I've tried that. Upon browsing HTC's website I found this hotfix. Sounds promising.
Hotfix: Hotfix: TILT 2 Freezes in SMS application | 12.17.2009
This Hotfix when installed prevents the device from becoming sluggish and/or freezing in the SMS application on the device. This is NOT a ROM update and you will not lose your data. Also, these files will survive a Hard Reset so they need only to be installed once.
kletiz said:
I have an issue when I am reading a text message and then click OK to go back to my inbox. It will show the inbox but also show remnants of the text message I just read at the top of the screen. It is locking the phone up for about 15 seconds. It seems as though it has to reload all of my messages in my inbox. This is a Tilt 2 with the stock rom on it.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I am also facing this problem in MightyRom. Did you find any solution?
kletiz said:
I've tried that. Upon browsing HTC's website I found this hotfix. Sounds promising.
Hotfix: Hotfix: TILT 2 Freezes in SMS application | 12.17.2009
This Hotfix when installed prevents the device from becoming sluggish and/or freezing in the SMS application on the device. This is NOT a ROM update and you will not lose your data. Also, these files will survive a Hard Reset so they need only to be installed once.
Click to expand...
Click to collapse
HTC released a new hot"fix" a couple days ago, but it only works for European phones, and according to at least one person, it doesn't work anyways.
http://forum.xda-developers.com/showthread.php?t=718297&page=2
I have heard that switching to a ROM without the HTC client does help.
Microsoft/HTC really should issue a new ROM. This is a well-documented problem to a basic, core function and it was known about immediately after WM6.5 was sent out. There's no way no one found out about this before it was released. Now I really don't like Apple products or their fanboys, but you have to give them credit in that they at least address their issues in some form or another.
Have you read this terrible notice from engadget.com?
Android still has horrible text messaging bugs that'll get you fired, busted, or otherwise embarrassed
By Chris Ziegler posted Dec 31st 2010 1:12PM
Pardon us if the headline is a little sensational, but this is one that we've personally experienced -- and it's not pretty. For at least the last couple versions, Android has been plagued with a couple extremely serious bugs in its text messaging subsystem that can ultimately end up causing you to text the wrong contact -- even contacts that you've never texted before. There appear to be a few failure modes; the one we definitely experience on the Gingerbread-powered Nexus S involves being routed to the wrong thread when you tap it either in the Notifications list or the master thread list in the Messaging application, so if you don't notice, you'll end up firing a message to the wrong person.
More seriously, though, there's also an open issue in Android's bug tracking system -- inexplicably marked "medium" priority -- where sent text messages can appear to be in the correct thread and still end up being sent to another contact altogether. In other words, unless you pull up the Message Details screen after the fact, you might not even know the grievous act you've committed until your boss, significant other, or best friend -- make that former best friend -- texts you back. There seem to have been some attempts on Google's part over the year to fix it; we can't confirm that it still happens in 2.3, but for what it's worth, the issue hasn't been marked resolved in Google Code... and it was opened some six months ago.
This is akin to an alarm clock that occasionally won't go off (we've been there) or a car that randomly won't let you turn the steering wheel -- you simply cannot have a phone that you can't trust to communicate with the right people. It's a deal-breaker. We're pretty shocked that these issues weren't tied up and blasted to all affected phones as an over-the-air patch months ago, but whatever the reason, we'd like to see Google, manufacturers, and carriers drop every other Android update they're working on and make sure this is completely resolved immediately.
Want to see this fixed as much as we do? Scroll to the bottom of the Google Code page and hit "Vote for this issue and get email change notifications."
Click to expand...
Click to collapse
Contribute yourself to convince GoogleGuys to fix it!
Never had any issue with this...
Maybe, it happens only on the default Google sms app not the HTC one.
I've often sent 2 - 3000 text messeges a month with two diffrent devices over the last 18 months and never had this problem. on the otherhand engadget are known for chatting sensationalist rubbish, only to have to apologise later in an editorial.
Fightspit said:
Maybe, it happens only on the default Google sms app not the HTC one.
Click to expand...
Click to collapse
I have experienced this with the HTC messaging one. When I individually texted "Happy new year!!" to everyone, the bug happened twice and it actually sent to someone else.
AndroHero said:
I've often sent 2 - 3000 text messeges a month with two diffrent devices over the last 18 months and never had this problem. on the otherhand engadget are known for chatting sensationalist rubbish, only to have to apologise later in an editorial.
Click to expand...
Click to collapse
is not sensationalism, is an actual big ugly bug.
crapula512 said:
is not sensationalism, is an actual big ugly bug.
Click to expand...
Click to collapse
If it's a bug, then why have I not encountered it since owning this phone for 7 months?
It could be a stock Android problem as already mentioned (HTC Sense ROMs have a different messaging application).
I found a post in the discuss thread where a guy explain how to reproduce this *bug*:
killerbee3 said:
If anyone is interested, evidently "Darth Mo" has been able to replicate it - found in ACentral Forums - entire post follows;
"It's not user error, or at least it's a combination of user technique and a possible design. It has to do with how the stock messaging app interacts with the Android system notification.
I recreated it this way. Open a text, but only from the notification bar. You will be taken directly to the conversation from that contact. Now, just hit the home button to get back to the home screen. Repeat this four times to let the open conversations build up. We'll call the earliest contact 1, the next 2, etc. for this example. Let's say you converse with these contacts over some time so that messages occur in this chronological order (opened from the notification menu if possible) : 1, you, 2, you, 3, you, 4, you, 1, 3, you, 3.
Now, you've read the message from contact 3, but quickly hit the back button because you need to send a message to contact 4. So you're back at the conversation list and select conversation 4. You compose and send your message and off you go. But, what can actually happen is that your message went to contact 1 because there is a bug that when you use the back button, it will take you to the conversation screen and when you select one, it will take you to the conversation with the last "unreplied" message received before the last conversation you didn't reply to, regardless of the one you actually select from the list. It's easy to miss that it took you to the wrong conversation as the on screen info can take a beat to update and it looks like you've select the right conversation. The kicker is the conversation list does highlight the one you meant to select, but will take you to that other conversation. It's as if it's saying, "Hey, I know you want to go to that one, but you opened this message and jumped out of it without replying. Maybe you didn't see it."
It's pretty easy for people to not have seen this for a few reasons:
1. You open messages directly from the messaging app
2. You close out every conversation using the back button and don't let them build up on top of each other
3. Messages can come in such a sequence that the conditions are never correct
4. It has actually happened, only the last "unreplied" message was from the conversation you actually intended to enter
I was able to create reliably using my Google voice number to send myself text and watched it bounce around conversations seemingly randomly. It was only when I looked at the times of each message with no replies that I saw what it was doing actually had order to it.
About 30 minutes of experimentation to figure it out, but I had to know how this was happening as I could see it leading to an egregious error later. Now to explain it to HTC..."
Click to expand...
Click to collapse
i've never had this either - i use handcent
Since a few minutes ago, the issue is considered critical instead of of medium:
http://code.google.com/p/android/issues/detail?id=9392#c794
Are kiddin me?
I dont send any sms for a while , this is a very big issue !
It never happened to me but , this is a realy really big bug!
Mekrel said:
If it's a bug, then why have I not encountered it since owning this phone for 7 months?
It could be a stock Android problem as already mentioned (HTC Sense ROMs have a different messaging application).
Click to expand...
Click to collapse
why havent you encountered it? i have no frikking clue and i dont care.
fortunately now it is a critical bug.
btw, i just care about android stock problems, im not using that sense stuff.
I quite often get messages which are meant for other people from someone who has a samsung galaxy (seems that's it's a copy of the message, rather than it being sent to the wrong sender).
I don't text as much, so less prone to the error.
happened to me on stock Android. Never on HTC Sense or mod
I have actually had this bug... but it reported the message had gone to the wrong person, but the correct person replied so I assumed it was reporting it wrong.... only happened twice.
on stock rom unrooted desire
I'm using a stock ROM & native SMS. I get this bug quite a few times.
I'm working in a very loud environment, so I send & receive lots & lots of text messages.
I notice that when i have lots of threaded messages, the SMS starts to slow down & sooner or later the bug will cause me send a text to the wrong recipient.
I'm quite careful of what I'm sending now.
HTC & they told me to reset the phone.
It hasn't been fun for me since I have to reset the phone once a month because my threaded sms buildup very quickly...
I'll update to 2.29.405.5 to see if this fixes anything.
Guys,
Is the 'wrong' person who receives the message someone in your phonebook or a total stranger. If it'd someone you don't know... how does your phone pick that number up? Randomly?
I had my Desire since April, and never had this issue. I open texts from notification bar and have sent them frequently.
I've had a G1, Magic, Milestone and now a Desire and I've never experienced this at all.
I don't think this bug is very common... I've never experienced it myself and none of my android friends have either...
Just some evil forces trying to make the Android OS look bad. Not our fault they couldn't resist taking a bite of that apple so screw them!
Overblown sensationalism AKA typical journalism. It's a bug but seldom a problem encountered by users, or XDA-Dev would've been flooded with such problem threads long before such publicity sites noticed. Just me personally having switched between over a dozen ROMs/kernels and their versions since March with over 60 average text out per day since and not one occurrence means it isn't anything but rare. I rely on SMS very much daily.
------------------------------
- Sent via HTC Desire -
I am a regular user of the MyYearbook site and mobile app (social networking, a bit like Facebook).
I also use to Adfree Android to get block ads, which worked pretty well until a while ago.
On the latest MYB app update (and the previous one actually) they changed the settings or perhaps the ad provider, and now Adfree shows a massive full-screen "Webpage not available" message at the top of my chatter (like FB feed). This is in stark contrast to the small unobtrusive white box which is the way it used to look.
No problem I thought, I'll just go back to my backup of the old version. But now this old version of the app nags me to update every time I use it - very annoying!
I know this is probably an obscure problem, and not a whole lot of people use MYB so it's possible no-one else here has experienced the problem. But can anyone suggest a fix? Either for the nagging in the old app, or the big full-screen "Webpage not available" message when I use the new app?
Revert > Uninstall Adfree
One way to avoid this problem
Yeah, I've pretty much come to the same conclusion :-/ I think I've investigated everything else...
Ever since December 23rd or so, when I first rooted my stock Nexus 5X, Google Messenger has been behaving strangely. Long SMS messages have seemingly random characters attached to the end of them, which do not show up on the sender's end. The most common is a "¿", but occasionally I get a delta ∆ on the end. I cannot find anyone else with this problem either here or elsewhere online. Does anyone have ideas? It's not necessarily a problem, but it is a mysterious inconvenience.
I am running the latest update of Marshmallow (stock ROM), with systemless root (SuperSU 2.61 I believe) and TWRP recovery. Nothing else out of the ordinary. This did only become a problem after rooting my phone, which may be part of the problem. Any help would be appreciated!
Edit: it should be noted that while these are valid characters, they do not appear when searched for with Messenger's built-in search function.
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Broken303 said:
just to be sure: these symbols appear on your end after receiving a sms? in that case it would be interesting to know what phones/apps the sender of those uses.
if this is the case with sms you have written, it could be useful to know what keyboard/input method you are using. did you restore your sms' and/or the messenger app from a previous backup?
first thing you could try is clearing the app data and maybe de-/reinstalling possible updates of it.
interested to see how your case turns out, since i never heard of anything like this.
Click to expand...
Click to collapse
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
OGNatan said:
Yes, they are on my end. It has happened so far with iPhone and Android senders using their stock messages application. And I have already cleared cache/data for Messenger with no change. It is a most unusual problem. I may just try uninstalling and reinstalling the app.
(I am unable to insert image links, or else I would provide a screenshot)
Click to expand...
Click to collapse
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
plwalsh88 said:
Also seeing this behavior occasionally, from both iPhone and Android senders. Haven't been able to figure out a pattern yet as it's only happened three times so far (three different senders, one time each). It's the strangest thing. I wish Messenger had some sort of bug reporting utility, since I've found several already.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have switched to Textra indefinitely, as this does not solve the problem, but does support many features that Messenger is lacking. If you find a way to submit a bug report, I would be interested in that information