is anyone else annoyed with their messaging?

[darylrue]

Ok I will search for that fix. However I want to be able to see the entire message I am sending before I send it. Not just the current line. Bugs the heck out of me. Sprint TP2 Stock Rom. Tried Mighty and Elite a little while back with a few bugs I chose not to live with at the time.

[zachavm]

So Having this problem and searching took me to this thread. What is described here is exactly the problem I was having with Sense 2.1 enabled (Standard Mightyrom.com). Now however, I've disabled Sense and begun to use the default interface. Problem is, in addition to having a massive slow down, the phone will also freeze on occasion. I've had to hard reset multiple times already. Any thoughts or new developments?

[mswlogo]

I'm having this issue on Energy (Leo Manila 2.5, WM 6.5.3)

It takes about 1 minute for it to send myself an SMS. Which seems slow to me.

I don't restore or have ANY messages. None, Zip.

It's a WM6.5 issue. Microsoft changed something with tmail.exe for wm 6.5 that takes a very long time to thread messages whenever a thread is closed. Most 6.1 builds do not have this issue. It's something that you just need to live with for right now, till MS gets around to fixing it in a build. Most people don't seem to bring it up as a problem - and we all know Microsoft floats around places like this, where they can see their latest builds in action. We're doing the free testing for them, you know You really think any company can possibly leak that many builds of anything and stay in business?

If anyone was active before WM6.5 - this was a common complaint. All 6.5 ROMs had issues with tmail.exe using lots of CPU when text threads started getting big. Just clear your texts regularly or cope with it. 28015 seemed to be pretty good while I was running that on my TP1 via RZ's kitchen.

[mswlogo]

Originally Posted by ShadowDrake

It's a WM6.5 issue. Microsoft changed something with tmail.exe for wm 6.5 that takes a very long time to thread messages whenever a thread is closed. Most 6.1 builds do not have this issue. It's something that you just need to live with for right now, till MS gets around to fixing it in a build. Most people don't seem to bring it up as a problem - and we all know Microsoft floats around places like this, where they can see their latest builds in action. We're doing the free testing for them, you know You really think any company can possibly leak that many builds of anything and stay in business?

If anyone was active before WM6.5 - this was a common complaint. All 6.5 ROMs had issues with tmail.exe using lots of CPU when text threads started getting big. Just clear your texts regularly or cope with it. 28015 seemed to be pretty good while I was running that on my TP1 via RZ's kitchen.

I don't have any thread. Zippo. First text message to myself after hard reset with NO text message restore takes 1 minute. I tried sending a Text from email at work and it arrived in a few seconds. So seems outgoing is the issue. I'll test more with my wifes phone when she gets home. It may be confused sending text to myself and adding more delay.

[mswlogo]

Ok, I just tested bewteen my wifes MotoQ phone and Mine. Takes 8-10 seconds in both directions. No Problem. It was the text to myself that was throwing me off.

When I send a text to myself it takes 1 min and 15 seconds. I think that is a sprint thing.

When I turn off Manila and Text to myself it won't even go out and knows it's me and goes direct to received. My wifes MotoQ does the same thing. So I can't test those environments to myself.

Since I don't text much, the big threads issue is not an issue to me. And I never restore texts.

I have seen even WM 6.1 bog down on my diamond (Stock ROM) with only a few 100 texts. And I had Touch Flow turned off on the diamond. It seems to use some critical resources to store text messages. The whole phone would bog down if too many texts were on it.

[halo9909]

yeah im getting this problem on 6.1 as well