SMS issue - Fascinate General

Hey I know verizon supports enhanced messaging for over 160 characters and I've had many smartphones with Verizon and never had this problem but now with the fascinate it sends the sender an error message and me the preceeding mess. Was modified message. Why is this? Its really annoying
Sent from my SCH-I500 using XDA App

Hmm, I'm not entirely sure.
This has been a "feature" of Verizon since the dawn of smartphones. It happened to me with the Moto Q9C, Moto Q9M, Blackberry 9630, HTC Incredible, and now my Fascinate.
The only work-around I've found is not using special extended characters, avoiding phone-specific smiley inserts, and making sure not to go over 160 characters (or if you do, get a messaging app like Handcent that will automatically break them up for you before sending).

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.

Message truncated

Anybody knows why I'm getting this message when somebody texts me?: Preceding msg modified, Media objects were removed
I get the message fine but it gives me that
Sent from my SCH-I500 using XDA App
It's a known software bug that vzw is supposed to address in a future update.
Sent from my oc'd Voodoo Fascinate using XDA App
I used to get that all the time on my i910 omnia. So not specific to android. I think it's vzw. It seems to only happen when another friend on vzw with some sorta lg chocolate thingy sends a text.
good day.
The Fascinate is supposed to support EMS, but inbound messages greater then 160 characters are truncated.
Outbound text exceeding the 160 character limit are delivered as one message.
Like others have stated, Verizon/Samsung are expected to release a fix for it.
[tapatalk on android]

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.

LG G2 Messaging App

Does the LG G2 messaging app lag a little bit? Does it take a second or two to open messaging threads?
The phone is really fast but does the LG Messaging app seem a bit sluggish?
Thanks.
Yep, that's the way it is. That's one of the only small complaints that I have about the phone. Maybe and hopefully it will be fixed by LG or a dev.
Sent from my LG-D800 using xda premium
I agree with both of you. It doesn't lag, especially when opening up a specific thread. My main reason for not changing it is that I like the quick reply feature, or whatever weird marketing name they decided to give it. I like being able to reply straight onto the notification.
No one has really even mentioned that in any of the reviews.. Actionable notifications are a big deal, I think.
I own the LG Pro and the LG Messaging is also slow to open threads. Unfortunately it has yet to be resolved and strictly limited to LG Messaging app.
I'll be getting the G2 in October when I am eligible to upgrade. Thanks for the feedback.
Sent from my LG-E980 using XDA Premium 4 mobile app
alias3800 said:
I agree with both of you. It doesn't lag, especially when opening up a specific thread. My main reason for not changing it is that I like the quick reply feature, or whatever weird marketing name they decided to give it. I like being able to reply straight onto the notification.
No one has really even mentioned that in any of the reviews.. Actionable notifications are a big deal, I think.
Click to expand...
Click to collapse
That is part of 4.3.... Had CM10 running on my Gnex. I would much prefer the stock messaging app.
I have noticed this as well. Odd, since it wasn't that way on the G Pro. Add to that the omission of group messaging.
I don't want to use a different app, either. The stock app lets you send videos as MMS (no matter the size) and I like having that functionality. And I may be alone in this, but I like the taskbar popup for new messages.
Noticing the same in my G2.
anybody with kitkat update can tell if it is fixed???
I am on AT&T. Cannot send or receive pictures through standard texting which was working good before kitkat update. Message app lagging too
Sprint considers your message app has problem only if you are unable to send or receive text messages and displaying error codes or network messages when you try to send a text message. But if your app only lags, it's just part of it. Live with it.
Solved
Gulfcoastowl said:
I am on AT&T. Cannot send or receive pictures through standard texting which was working good before kitkat update. Message app lagging too
Click to expand...
Click to collapse
AT&T customer representative did solve the issue. She changed the service number and she told me she changed some provisional settings on her end...Finally it worked. I am now able to send and receive picture messages.

Categories

Resources