Message truncated - Fascinate General

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]

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

SMS issue

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).

[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.

Text message after getting voicemail

Ok so I'm on bonsai 1.1.3 with the new cwm and emotionless beast theme. This just started a couple days ago. When I get a new voicemail I then all of a sudden get a new text message. The text message is from 9016 and it says android ###-###-#### (the phone number that sent me the voicemail) has sent you a sprint voice message. Call 408-970-0000. Mmsn,106bee099,9fc6,v69bdosvezi//cm. This is just one example of one I got. Like I said it just started a couple days ago. Anyone ever had this and know what it is? It's really annoying when this happens. Thanks for your help!
Do you have the no bubble messaging app? Or the stock messaging app?
Sent from my SPH-D700 using XDA App
I have this too after I replaced the bubble MMS app with the white one with square pictures on the left (similar to a facebook chat looking thing). Looks like the evo sms app from what i've seen.
Is that whats causing it? All I did was push the Mms.apk from viperrom to bonsai 1.13
all you have to do is blacklist the number the text message comes from. Not sure if the stock app will do it, but handcent will.
I never changed my SMS or anything. I just updated the bonsai rom. As soon as I get my voicemail notification I get those new text messages.
This is happening to me as well.
this is going to be funny...
but can someone attach the MMS.apk that is causing..i kinda actually want this to happen after i get a voicemail..
thanks
No 9016 txt with qr 2.7 b ut when I added on the 1.7.3 theme I get the txt
Sent from my SPH-D700 using XDA App
Leviuqse said:
this is going to be funny...
but can someone attach the MMS.apk that is causing..i kinda actually want this to happen after i get a voicemail..
thanks
Click to expand...
Click to collapse
I just have my VM setup to forward to my Google Voice number. That way I never get VM in my Sprint inbox - no fuss with visual VM either. You can use either the Google Voice app or have Google Voice send you a text.
Anybody know why its happening. Is it something in the bonsai rom cause.i havent messed with my sms and voicemail?
Sent from my Evo killer!
that is the visual voicemail to text thing it happens on all phones with vvm to text, call tech support tell them to block the number from texting and problem solved, i have to do this a few times a day d]since i do their tech support lol
Its from the messaging app with the rom. Its using the no bubble mod with the 5mb mod. I figured out that was causing it and just found a stock messaging.apk in the theme forums. Once you switch it out, call your self a couple times and you will notice the text after voicemail goes away.
Sent from my SPH-D700 using XDA App
Leviuqse said:
this is going to be funny...
but can someone attach the MMS.apk that is causing..i kinda actually want this to happen after i get a voicemail..
thanks
Click to expand...
Click to collapse
Check in the theme section for the no bubble mod mms.apk. I would post it but I'm at work and don't have a computer near by.
Sent from my SPH-D700 using XDA App
I'm not positive, but I think if you are getting VM notification texts saying "call 408-970-0000(or any number)to listen to your VM messages, its because your voice mail isn't provisioned properly. The network doesn't realize your phone has visual voice mail, so its sending you a text to let you know to call to hear them. This happened to me a few times on my HTC hero when flashing cyanogen mod, and also a few times on my epic when i had a bad flash, or i had a poor signal on my first boot.
You should be receiving a message with a sort of code in it, something like {android}/noreply/notificationon(i don't remember the exact syntacs or message, but it will look something like that) it was caused by your MMS.apk.
When i had the provisioning issue, this is what i did to resolve it:
1. Dialed *38(resets VM to carrier in case it as setup to go to google voice, or other third party VM).
2. Open the VVM app
3. Hit menu
4. press Compose
5. in the "to" field put "[email protected]"
6. press record
7. as soon as the "send" button ungrays and ill allow you to, press it.
If this doesn't work you can try making a nandroid backup and odining to a stock rom, then re-rooting and restoring your nandroid.
Best of luck
gunrunner25 said:
all you have to do is blacklist the number the text message comes from. Not sure if the stock app will do it, but handcent will.
Click to expand...
Click to collapse
I have this same issue, but when I blacklist it with Handcent, it still gives me a notification that I have an unread text message even though it doesn't show up on my conversation list...Looks like I might just have to go back to stock and re-root unfortunately...
PS - Also tried the above and haven't seen any changes, still get the stupid 9016 text that I have an unread voicemail...
Well I did the email to activate and got a txt back. Still get the 9016...odd didn't happed on qr 2.67 but mold mms is 1.73 theme did....
Sent from my SPH-D700 using XDA App
I'm pretty sure this is google voicemail interfering with your regular voice mail. You need to go into gvoice and deactivate the number from going to google, and it will stop.
I'm using viper rom and get the same text message so it is not rom specific. I have tried the messaging.apk change and still get the messages. Does not appear anything is working so far to stop the texts
Sent from my SPH-D700 using XDA App
Hey mikel719 or anyone who has the stock Froyo Messaging app, can you please post it here so we can fix the issue if we dont want to download handcent to blacklist or download redlist to hide the message?
byransays said:
Hey mikel719 or anyone who has the stock Froyo Messaging app, can you please post it here so we can fix the issue if we dont want to download handcent to blacklist or download redlist to hide the message?
Click to expand...
Click to collapse
I'm not at a computer at the moment but I can email it to someone, or I can post it when I get off work.
Sent from my PC36100 using XDA App

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.

Categories

Resources