[ns4g] sms problems. - Nexus S General

Running latest nightly cm7 (5). With netarchy's latest kernel. Using handcent for text.
When sending text under 160 everything works great. Once going over causing a split, the recipients of my text gets gibberish. Scrambled letter and symbols. Is anyone else getting this? Both my phone and my brother's phone do the same thing, so I know you should get the same results if you use the same setup as me. My question is why and what can we do to fix it?

I have read about this before but not actually experienced it yet (no long texts). I am running CM7 on my ns4g. I heard the simple solution was to go into your sms settings and simply select to have the app split up your texts at 160 characters.
Oh - sorry - you are using handcent. forgot. I just use cm7 sms app. hmmm. not sure. handcent doesn't have the same option?

Handcent has those options. They don't do anything. I ran cm7 on my evo with handcent, never had this problem before. So I'm thinking its a phone specific problem.

joebags said:
Running latest nightly cm7 (5). With netarchy's latest kernel. Using handcent for text.
When sending text under 160 everything works great. Once going over causing a split, the recipients of my text gets gibberish. Scrambled letter and symbols. Is anyone else getting this? Both my phone and my brother's phone do the same thing, so I know you should get the same results if you use the same setup as me. My question is why and what can we do to fix it?
Click to expand...
Click to collapse
Search is your friend
Its a CDMA issue. Have your texts split up into multiple txts at the 160 character count. There is even a setting in Handcent that says something about compatibly with CDMA

eagercrow said:
Search is your friend
Its a CDMA issue. Have your texts split up into multiple txts at the 160 character count. There is even a setting in Handcent that says something about compatibly with CDMA
Click to expand...
Click to collapse
i have used both settings in handcent for splitting by character and by word at the 160 limit. neither of them seem to work. the recipient receives two texts but it's all gibberish. I never once had this problem on my evo which is cdma also. both phones ran CM and handcent. I've gone through each and every setting in handcent and CM to double check I wasn't missing something. regardless it should work without me changing a setting to allow long texts. It is something that needs to be fixed.
What i'm thinking the problem is, is a setting that was forgotten to change from the gsm phones in the sms settings.
I just installed Miui, using the stock sms app from that it still scrambles the texts over 160. It says it's sending two texts, but something is horribly wrong on the receiving end of the text. So i'm pretty sure it's not a problem with handcent settings. It's the fact that these roms are ported from the GSM NS and we're missing something yet.
I'm going to install a stock image after work today and confirm that it works on stock roms.
I'm very shocked no one else has complained about this. I have two NS4G phones both of which have the same symptoms.

Just confirmed that 160+ sms messages send fine from a stock os on the ns4g. using stock messaging or handcent.
Using CM or Miui is causing gibberish to come through. There seems to be a problem using non stock based roms at the moment.

That is interesting. I had the problem, but I resent the same exact text except I broke it into 2 smaller sms and it was received fine. I can't remember what rom that was though, because I've been through so many and havent heard of the issue since I setup the automatic split sms in handcent.

Related

Issue with samsung and 160 character txt limit ??

With handcent I have had no trouble on other android phones with simply splitting txts over the limit, but I am getting the dreaded "the proceeding message... blah blah blah"
Anyone have any suggestions ?
TYIA
pman219 said:
With handcent I have had no trouble on other android phones with simply splitting txts over the limit, but I am getting the dreaded "the proceeding message... blah blah blah"
Anyone have any suggestions ?
TYIA
Click to expand...
Click to collapse
The handcent dev may have to update the app to work with the fascinate, just report the bug to him
fallingup said:
The handcent dev may have to update the app to work with the fascinate, just report the bug to him
Click to expand...
Click to collapse
thank you, I will
** BUMP **
Is anyone having or not having this issue ??
If everyone isn't maybe its something i'm doing ?
I am just using the regular text messaging client built into the fascinate and noticed when typing a text that there is a counter in the top right corner of my message and it shows a max of 160 characters.
This is a royal pain. There has to be another way to avoid this. The person I am texting is also using the Verizon network as well.
This should probably be added to the list of things that need to be fixed on the phone.
160 Character limit
When I was on froyo stock I did not have this problem, but now I am upto 2.3.5 it still is there. Has anyone been able to fix this?
Are you just on stock 2.3.5? A lot of custom roms I've seen have the option to split SMS messages over 160 characters. It's not a perfect workaround since I've always had longer SMS messages "just work" on other devices, but it's at least something. Maybe look in the settings of the messaging app to see if there's a similar option?
I did, and I could not find any settings on the phone that would limit it.
Sorry about the delay
Hm, that is strange. Short of flashing a different rom I'm not really sure what to suggest. Maybe you could see what Verizon has to say about it since you're using stock software?
it's the network, just the way cdma works. use go SMS or a custom rom.
Sent from my SCH-I500 using Tapatalk 2 Beta-5
FWIW, I never had this issue on my incredible, just on the fascinate.
It's your network operator, not the rom. But a special sms app can fake it

[Q] Enhanced Messaging Service

Does anyone know if any of the custom roms fix the long text message (EMS) limitation of the Fascinate?
A friend sent me a long text message (over 160 chars but shorter than 300 chars) and received the following message back from VZW... "Message delivered to <number> as plain text. Destination does not support enhanced messaging service.
This never happened with my DROID 1 and supposedly Samsung is fixing this in a future release. However, I am not a patient person.
thanks
so far no custom rom has resolved this issue to my knowledge.
Handcent corrects it.
If Handcent corrects it then I must be doing something wrong.
I have the stock ROM rooted, deBing'd, running ADW Launcher and Handcent and still get the EMS errors. Handcent is set as my default app for messaging. Is there a Handcent setting I missed to correct this?
--
RogueGeek said:
If Handcent corrects it then I must be doing something wrong.
I have the stock ROM rooted, deBing'd, running ADW Launcher and Handcent and still get the EMS errors. Handcent is set as my default app for messaging. Is there a Handcent setting I missed to correct this?
--
Click to expand...
Click to collapse
There are settings to parse messages above 160. Perhaps it's a desperate issue that I haven't experienced.
Sent from my SCH-I500 using XDA App
I have been getting this as well. Handcent user. Kinda lame, but nothing to write home about.
Sent from my Fascinate using the XDA app
There is an option in Handcent to split messages over 160 character. It even provides a countdown when composing a message so you know when it will be split. Really nice feature!
Thanks for the tips, I will dig around in Handcent and see if it resolves the issue.

Weird outgoing SMS garbled text.

Brand new Nexus S 4g on Sprint.
I have an N1 and as of today started getting random garbled texts like below.
Phone was bought and system update installed on Friday afternoon.
No "unusual" apps installed other than Handcent+emoji , and Pulse.
Tried installing GoogleVoice for it to work "the classic" way as described on these forums could that be causing an issue ?
The person with the Nexus S says they dont see those messages in there outgoing. Only recipients.
Yep definitely weird, I texted my sister yesterday using handcent and she replied saying it was all numbers and symbols, on my end it looked fine. I wonder if it was a handcent thing.
Sent from my Nexus S 4G using XDA Premium App
Nope not a Handcent thing. I texted my boss and the next day he showed me it and said, "Dude. What the f*** is this ****...?" Hahahaha, I was using the stock messaging application. Hasn't done it since.
So I just found the problem... It's only if the text is more than 160 characters long. I just tested it...
I same thing happened to me using the evo.
Sent from my Nexus S 4G using XDA App
info[]box1 said:
I same thing happened to me using the evo.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Never had that problem when I use to send texts containing over 160 on my EVO
This happened to me yesterday with a message over 160. Freaking weird. Is this a ginger bread "feature"?
Sent from my Nexus S 4G using Tapatalk
From what I hear it is a problem with CDMA, not sure what though. The way you can fix it is to go into your txt settings (I use handcent) and have messages longer than 160 characters broken up into multiple messages of 160 characters or less automatically. Or pay attention to your character count and break into a second message when it gets to 160.
I had this problem when i was using Sprint Google Voice integration.
Once i disabled that integration, this problem (and many others) stopped.
eagercrow said:
From what I hear it is a problem with CDMA, not sure what though. The way you can fix it is to go into your txt settings (I use handcent) and have messages longer than 160 characters broken up into multiple messages of 160 characters or less automatically. Or pay attention to your character count and break into a second message when it gets to 160.
Click to expand...
Click to collapse
That's probably it. I had just flashed a Rom and forgot to check that. Thanks
Sent from my Nexus S 4G using Tapatalk
It's not so much a problem but a limitation of CDMA. GSM networks will automatically split messages up larger than 160 characters, CDMA can't do so effectively. I ran into the same problem when I installed handcent sms, since by default the feature to break apart messages is deactivated. If you're using the stock sms app then you won't have this problem since it limits any text being sent to 160 characters. If you want to send more you have to create a new message.
That limitation is a problem
I am not sure if it´s a limitation. I had a lot of those, not sure if any sms of mine reached more than 160 chars.
After googling it a lot, someone reported it as a bug in gingerbread, and it happens if you use accentuation.
I followed this, and never had any friend complaining of garbled SMS again.
Interesting. I had them uninstall handcent and it stopped. But they also said theyve only been sending short messages.
Will try the character fix to see if it works.
eagercrow said:
From what I hear it is a problem with CDMA, not sure what though. The way you can fix it is to go into your txt settings (I use handcent) and have messages longer than 160 characters broken up into multiple messages of 160 characters or less automatically. Or pay attention to your character count and break into a second message when it gets to 160.
Click to expand...
Click to collapse
I was having this issue and this resolved it for me.
Just happened to me. I enabled split SMS and we'll see what my friends say.
I did not have this problem with my EVO 4G on Sprint, (using the stock sms or Go SMS Pro) but I am having it with my Nexus S using Go SMS Pro (stock sms app won't let me send more than 160 chars).
I can confirm that having handcent split the message fixes this issue. I also have the .apk of the stock messaging app with similar settings to split the messages.
http://forum.xda-developers.com/showthread.php?t=1202223
Happend to me today
So I texted my brother earlier this morning and he said that it happened, but the weird thing is that afterwards my data stopped working.
So since I couldn't get it to work no matter what I did, I decided to wipe and reflashed my phone but it still doesn't work. Now i'm stuck with a phone that doesn't have any contacts, and no working data but i get texts fine, although I'm not sure if they send fine since i haven't tried. D:
So has anyone had this happen to them, if so do you have any suggestions.
Thanks in advance.
Edit:
I forgot to say that i have a Nexus S 4g with sprint.

[Q] Atrix 4G CM7 MMS (unknown label as "1")

Hi, i installed the newest rom from http://forum.xda-developers.com/showthread.php?t=1257574
I just started noticing that i'm now getting MMS text from "1" and not the contact name because when i download the message either from goSMS or handcent or even the defaulted one messager, after the download, it then places it under the correct name/contact...all text messagers behaves the same way. i went to search throughout the forums but coming up empty (sorry if this has been brought up before).
If someone can point to the forums with the information that I lamely could not find or explain if it is a bug because the release notes or known bugs doesn't list this as an issue.
xmontx said:
Hi, i installed the newest rom from http://forum.xda-developers.com/showthread.php?t=1257574
I just started noticing that i'm now getting MMS text from "1" and not the contact name because when i download the message either from goSMS or handcent or even the defaulted one messager, after the download, it then places it under the correct name/contact...all text messagers behaves the same way. i went to search throughout the forums but coming up empty (sorry if this has been brought up before).
If someone can point to the forums with the information that I lamely could not find or explain if it is a bug because the release notes or known bugs doesn't list this as an issue.
Click to expand...
Click to collapse
ditto. and i use goSMS as well
Did u try geting rid of your Mms app and using the stock one
get rid of MLS? sorry for not understanding that but what is this?
i have tried to use the stocked one (removed all handcent and go SMS apps) but still gets the "1" or duplicates where i see "1" and the receiver contact name with the same mms...but sometimes i don't.
i'm searching some more, does the APN selection make a difference? like if i go to Network Operator, i see preferred network selection...2 ATT (listed as AT&T and AT&T...nothing really indicates the difference from each other) and Tmobile.
im having the same issue..using gosms. i've used every cm releases for atrix there is and only now started having this issue with nightly 4. i'm using fauxs enhanced stock kernal now. jus switched from the 2.1 1.3oc last night on which i noticed the issue. will try out this enhanced stock n see if the issue happens with it.
I use GO SMS Pro as well - and I do NOT have this issue..... I dont know whats going wrong for you guys :/
GoSMS here and no problems!
I only have this problem if I click on the download button in the MMS. If the message auto-downloads then there is no problem. I've had this problem on other ROMS as well so I'm thinking this is a GoSMS issue.
If it were a GoSMS issue - we would all have it.... CaelanT and myself don't have this issue and we both use GoSMS......
i tried with the stock messanger too, and still got the same issue, i don't think it's the aps (handcent or goSMS). ahh it's so crazy!
GoSMS here and Homebrew ROM, FAUX 2.1 1.0 extended kernal and I am having the same issue, but only if it's an MMS message, not with regular texts. Once I click on D/L, another text comes in from the sender with whatever image was attached.
I too have the issue. I am on CM7 Not Beta and not Nightly, and am using Handcent. My wife, who is completely stock running 4.5.91 and not unlocked or rooted, running Handcent is also seeing this issue....
My son and I both use GoSms and he gets them , but I don't. Also I'm on CM7 and he is stock 4.5.91.
i am on CM7 and use handcent and i get this as well! very strange. not a big deal, just strange. the "1" message is always empty. If i go back out I see the MMS properly inside the proper thread.

[Q] Issue receiving multipart SMS message (CyanogenMod)

I'm using CyanogenMod 10.1.3 on my Sprint S4, and I cannot receive multipart text messages and it is driving me nuts. I always get the "1/2" or "1/3" notation and the first part of the message but then I never get the second or third part.
Has anyone else experienced this with this phone and ROM combo? This is with both the stock messaging app as well as Handcent. Not sure if it's the phone, the carrier, the ROM...or what. I've never even ran the stock ROM on this thing unfortunately so I don't have any experience to go on with that.
I've tried other messaging apps too with the same issue...really strange.
jdostal said:
I've tried other messaging apps too with the same issue...really strange.
Click to expand...
Click to collapse
I've noticed that the issue seems to only be from certain carriers. I have several friends that are on Sprint and I can usually get mulitpart messages from them. I have a few people that always send me long messages from US Cellular and those always get cut off.
I've updates to new CM Nightly's, new SMS apps, put a stock rom on and updates PRLs etc...
I have no clue what is going on with this. Anyone else had this problem?

Categories

Resources