[Q] Phone will not send texts longer than one page? - EVO 4G Q&A, Help & Troubleshooting

I just recently flashed an ICS rom on my Evo, works great but whenever I send messages that are even one character longer than 'one page' I instantly receive an error message saying that it failed, anything less than one page seems to work fine though, any and all advice would be highly appreciated

One page (SMS character split?)
For starters what ICS rom are you running? I am running PreludeDrew's latest ICS rom (P5) and I have no problems with SMS split if that is indeed what you are referring to (going past 160 characters).

160 character bugs are known issues for GSM ports or for phones not on cdma. Some people have it some people don't its based on location. I don't have it. What you can do is use go SMS and enable splitting in the settings.
Sent from my Warm 3.5 Evo using xda app

+1 for GOSMSPro it makes using different apn settings on other carriers painless and has tons of customization options, and it has the split and send as split*over 160 char* in the send settings

Related

Duh! Desire still converts sms into mms, even with Froyo :(

Any known fix to this annoying issue yet? If you type a message that's longer than 3 sms:es it automatically converts the message into a mms message. Normally I wouldn't care about a "small" issue like this, it's just that I have free sms and I pay for mms messages.
Google said this have been fixed in Froyo, and yes it seems they're absolutely right since the problem is gone on the Nexus one & most other phones running 2.2.
But nothing have changed on the Desire, the problem is still there... Sometimes I wonder if the Desire is running an eclair/froyo hybrid and that HTC have just manipulated the numbers in the "about" screen.
Sigh...
I can type upto 5 sms before it convert into mms.. stock Froyo here
Sent from my HTC Desire using XDA App
Download Handcent.
I'm not saying you should switch to it completely (I wont, Stock SMS looks so much better) but you'll benefit from:
- Pattern/Pin lock for SMS messages (even for Stock SMS Program)
- For the rare occasions you're sending a long message, cut from stock SMS, paste into handcent and it shouldn't convert to MMS.
brummiesteven said:
Download Handcent.
I'm not saying you should switch to it completely (I wont, Stock SMS looks so much better) but you'll benefit from:
- Pattern/Pin lock for SMS messages (even for Stock SMS Program)
- For the rare occasions you're sending a long message, cut from stock SMS, paste into handcent and it shouldn't convert to MMS.
Click to expand...
Click to collapse
I know it's good and have lots of features, I've tried handcent before but I agree stock HTC SMS app looks so much better so I uninstalled it after a few days. But I might give your suggestion a try, thanks
handcent actually have a setting not to auto convert sms to mms...
Sent from my HTC Desire using XDA App
its 5 here as well, it is meant to reduce expenses, because (here at least) if you set six messages it will cost more than one mms, hence the converting.
is it related to the sim card and the network preferences? maybe, but if it is than it should detect if you have free SMS and not convert.
either ways i think you should have an option to turn it on/off.
worth mentioning in android issues
irkan said:
its 5 here as well, it is meant to reduce expenses, because (here at least) if you set six messages it will cost more than one mms, hence the converting.
is it related to the sim card and the network preferences? maybe, but if it is than it should detect if you have free SMS and not convert.
either ways i think you should have an option to turn it on/off.
worth mentioning in android issues
Click to expand...
Click to collapse
I have an sms-flat --> mms more expensive. But all in all not a too bad idea if you pay for every single sms...

[Q] Sense 2.0 ROMS Multiple Text Message Problem?

Ever since i flashed my first Sense 2.0 Rom I have always had this problem. No matter which one it always happens and its really annoying. When texting a person and having the text be longer than 2 messages it will not send. It tries to send then i get the usually text message not sent error message. Even after that though it still continuously tries to send the texts and i have to then restart my phone every time. I think I may of seen someone with a similar problem a while ago within a Rom thread. Does anyone else have this problem? Or is it a known problem in Sense 2.0 Roms and can it be fixed?
Its a known issue I believe. You will have to cut every text at 160 chars or it usually doesn't send. Its fixed in cm7 and it works on regular 2.2 froyo sense roms but still an issue with sense 2.0; I think there's a fix if I find ill post it.
~ d3rk
Only fix so far is to use Handcent, Chomp or GO SMS Pro. They have options to automatically split texts at 160. It has something to do with all of the Sense 2.0 ports coming from GSM phones and it handles texts over 160 differently then the CDMA that we use. Or at least that's how it was explained to me.

0001/0002 on text messages

Recently my text messages have been starting with 0001/0002 and I am not sure why but it annoys me. They do it on any rom. I posted a picture. Any ideas?
Im getting the same thing but its only on some texts
Sent from my PC36100 using XDA App
I got a few like that, but only on June 22, and only from one person. She happens to be on an iPhone, but I got other texts that day from iPhones without it.
This happen to me a couple of days ago from my wife BUT she's on Boost Mobile so I figured it was something going on with her network or something........What ROM are you guys running?
I'm on the latest CM7 7.1 running Tiamat's SBC 4.0.5 kernel.....
It must be a sprint thing. I'm using the 3d and I'm getting it too. Or maybe a Sense thing?
Sent from my PG86100 using XDA Premium App
I can confirm. Multi posts doing the same thing.
Sent from my PC36100 using XDA App
I have been seeing the same thing when people send me long text messages, it's happened when people send from verizon/boost/cricket and t-mobile
i think it might be a GB thing, its supposed to do it when your text is so large it need to be split in to 2 or more smaller messages to be able to send, and its numbered so you know which message come first, sencond,etc. but there is a bug in the feature where the message app splits smaller texts too
Its looks to me like that's the message counter, like message 1 of 2, 2 of 2, for messages longer than 160 char.
I get this from my gf, she uses vz droid x running stock gb. Only her, no one else running gb or a different carrier. So my guess is not our phones or sprint but the others carrier.
Btw im on froyo so its not a gb thing for us.
Posted by some phone named the Epic.
Okay so I get it from my girlfriend using a feature phone on verizon so it's not a thing her phone is doing. If just started a month ago. It's not on all her texts and of she sends me a message 3 texts long it only counts her first two then the thrid is untouched. It's not a sense thing because it happens on Miui and cyanogenmod. It has to be at the carrier level.
Sent from my PC36100 using Tapatalk
I think its defiantly a sprint thing that just recently happened... if i get a text that is over 160 characters. Instead of breaking the text into 2 parts i get 1text around 160c and then 2 more saying 0001/0002 that each have only about 20 or so characters but its weird it splits the message into 3 parts leaving 1 alone... Sprint should defiantly change whatever they just recently added into their texting feature....
Yeah this is happening to me as well. My gf is on T-Mobile and if she sends me a long text, it breaks it up, but not in a logical manner. I get the first message of 160 char, then the next might only be a sentence, followed by another short message. So what should have been 2 messages, turns into 4 or 5 sometimes.
happening on my phone as well. Running SnS 2.2 froyo, so its not a gingerbread thing. This ONLY happened before with people using Handcent, people using stock messaging apps it never happened. It used to just break up the text without a 1/2 counter, but now it happens anytime. Specifically my gf who has an Incredible on verizon, and she is using the stock messaging app. So it seems like maybe this is something sprint is doing on their end.
It numbers the texts in order because who ever sent it sent you a text longer than 160 characters, it seems android is numbering the texts for you so you won't have to put together the puzzle figuring out what text came first.
GV
Are you using google voice? I had issues with mine.
I believe it has something to do with the message thread as well...whereas you can delete individual messages from a thread as opposed to the whole thread.
This is a Sprint network thing. They probably changed something in the SMSC (Short Message Service Center) to make it do this. This is happening to both me and my brother. CM7 on my EVO, Mik (I believe) on his EVO Shift. Doesn't matter what carrier or phone the incomming message comes from, it happens all the time.
That should answer it for everyone
Actually that is in the sense 3.0 mms app. Mine does that on my 3D LOL, try an aosp rom it won't do it and based on your screenie you're using sense 3.0/2.1
Sent from my PG86100 using XDA Premium App
dirkyd3rk said:
Actually that is in the sense 3.0 mms app. Mine does that on my 3D LOL, try an aosp rom it won't do it and based on your screenie you're using sense 3.0/2.1
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I'm telling you guys its network related. Both mine and my brothers phone have not changed at all and this started to happen the other day. I'm on aosp he is on sense. Two different devices. But what do we have in common? Location and carrier. Sprint changed the way that texts are handled.

Please Help - Multi Text Issue With ICS & CM9

Hello everyone, I would like to start by saying thank you to everyone here, all of your posts, info, etc has been excellent in helping me along my way to learning enough about this stuff to be dangerous to mine & my friends phones...we're all still using them so that's a "Win" in my book
Now, on to my problem. I've tried googling & searching posts here, and I don't know if it's just the terminology I've searched but I've found nothing similar to my problem except where a thread had to do with EMBS messages coming through incorrectly.
First off, I'm on a Sprint Branded Samsung Epic Touch 4g Galaxy S II (whew that's a mouthful already) It is on Verizon Prepaid Service.
When I first set this phone up, everything worked correctly - Talk, Text, Web, MMS, WiFi Hotspot, Etc - all working perfectly. I was able to send & receive picture mail through MMS, etc.
I am currently running CyanogenMod 9-20120416-SNAPSHOT-epic4gtouch-Alpha 3
Android Ver 4.04
Kernel Ver 3.0.15-SPH-D710.FD10-CL377892
This is the updates I installed to this phone originally:
gapps-ics-20120429-signed
StockCWM-EL26.tar.md5
update-cm-9-20120416-SNAPSHOT-epic4gtouch-alpha3-signed
mmsfix.zip (and made the correct changes for Verizon)
As I said, the phone was 100% functioning at this point for several days. The problem that came up happened out of nowhere, no changes were made to the phone whatsoever, not even a random app was installed from the market.
The only apps I have installed are
Wifi Tether (Rooted Users)
ES File Explorer
Facebook
GMail
Craigslist
Facebook Contact Sync
NFL Scoreboard
QR Droid
SuperUser
Rom Toolbox
Rom Manager
Terminal Emulator
Other than that, it's just what ICS & GApps Installed.
So here's the problem - whenever I recieve a text from anyone now, if it comes in multiple texts (ie 1/2, 2/2/ etc) it shows up as all special characters when I recieve it.
Here is the last one I got, I sent it from another phone on the same carrier - I just typed myself a message until I was sure it would be a 2 part message and this is what came through on my Epic
First Msg
ß<xp¿AcGÉ?üööysgOS&Læ;6lX9W/Ü<9rfEØΨ+FøÆ8xp¿A¥ìÅß<xqF<9$fÅz<EEggÜNixw¿
5¥rdåÆΩÖÅΠ'ålÄ3gF
3vø)rlyscW/Ü>ñzsbEKΨ/ÜÆ_gGEìgVLhurd1äñ2AÅZ#ΛC<z¡@@@@@@@
Second Msg
Ü=ävhPfOÉ?N3vlY1cnÖ<yreIΨ/Ü<9rfEØC¥ìÅÆ8xpaCì
Λ(XΔA$éZTGøΔHEwì/ÖrsOà#Ec=P
I put it in a hex/text converter and the text version came up all "?'s" so I'm pretty much at a loss at this point.
I apologize for a long winded message, but I wanted to include as much information about my phone, etc as possible to get the best answer I could.
Again, thank you all and if anyone has any insight to what might be causing this, I would greatly appreciate the info.
Oh, and in case I didn't make it clear - at this moment, text works fine (if its only 1 text at a time incoming) I can send multiple page texts & the recipient gets them no problem, and I can send/recieve pictures, etc as mms with no problems...the problem only exists if it's multiple pages of text coming in at once.
Thanks
What happens if you use a 3rd party messaging app like handcent?
someguyatx said:
What happens if you use a 3rd party messaging app like handcent?
Click to expand...
Click to collapse
I just tried a few diff versions of Handcent, with the settings Default, then again with the settings on "Default SMS/MMS App (Disables Stock & Other Messaging Apps) and got the same results...
The wierd character code that comes through is exactly the same, both with the stock app & handcent in case that might be a question...
**Update**
I have Google Voice number sending voicemail converted as text to my phone on a secondary number. I got one today, was 3 pages SMS and it came through perfectly, right after that, I got a reg text from someone elses phone that was 2 pages, and it was the same type characters, and a few more since that were all the same special characters.
I've tested the Google Voice translation a few more times, and it comes through perfectly. I also tested just sending a multi-page text to my google voice number, which just forwarded the texts to my phone via SMS and they also come through perfectly.
So SMS from Google Voice in multiple texts works great, but from another phone do not.
If anyone has seen anything like this, I would love to know I'm not alone.
I'm having this exact same problem too. I noticed multiple texts incoming from certain people are fine, but when I receive multiple texts from a few others or a group sms from an iphone I get this really wonky characters. Any help would be appreciated. I am using this phone through pageplus.

[Q] Occasional failure to send SMS on 4.2.1

So I recently updated from stock JB to the latest CM10.1 and I've ran into problems sending SMS messages, I often get the Message Not Sent notification and the red exclamation point out next to the message. No one else, that I've talked to, via FB groups, have seen anything like this.
Some background, SMS was working fine on 4.1 (VZW) but I got the occasional Bug when unlocking the phone where the phone vibrates 2 times and opens up GMail to send a bug report, anyways.
Cm10.1 Experimental
Stock Kernel
Stock Radios
32 GB LTE VZW Nexus
Was suggested it may be the SMSC code, but that would affect every message, not just particular ones.
Other info: I can sometimes, re-word the message(after multiple attempts to resend after reboot, toggle airplane mode/wifi/data) and it will send, though the messages it occurs on have no special characters are small enough not to be converted to MMS
Any info/assistance would be great, Thanks!

Categories

Resources