Please help....

[BraelensNayNay#AC]

"Preceding msg modified. Media objects were removed" is the msg I get after anyone sends me a text that's more than 160 characters. The sender also gets the msg. This is REALLY annoying!! Any suggestions??

 

[Cory Streater]

This is a problem with the built-in messaging app. You need to install Handcent SMS from the Market and in the settings specify that you want messages over 160 characters to be split into multiple messages. This drove me nuts on the Droid also. Handcent will fix it.

 

[TheSultan]

Sweet, just checked the feature myself in Handcent. thanks Cory

 

[Cory Streater]

What's interesting to me, is that I thought this issue was specific to Motorola Droid's on Verizon, but seeing as this problem is being reported in the Eris forum, I guess it's more of an Android/Verizon issue.

Can you guys confirm you have an Eris? If so, I will add this to your FAQ.

 

[BraelensNayNay#AC]

Cory, I do have an Eris. I used Handcent then switched to chompsms. I'm not yet sure of the real differences between the two apps, just trying them out. I'm a nOObie to Droid. I've had Blackberry Storm since they came out and a Pearl before that. I really like this phone since it has so many bells and whistles but it's getting frustrating trying to get the "basics" set up. ANY suggestions welcome!!
Thanks everyone!!

 

[Cory Streater]

Well welcome, BraelensNayNay. We like new members and hope you stick around.

Check out the stickied FAQ's in this forum and in the general help & how-to for starters. The apps forum is also a great place to look.

For Handcent specifically, I found this FAQto help me a lot.

 

[BraelensNayNay#AC]

I've looked around and still can't fix this issue. I'm using chompSMS and BetterKeyboard. Not only do I get this msg but the person sending msg gets it too! I've gone through all the settings and checked the box to split the msgs but it continues to happen....I apologize for keeping this going, but it's driving me and my contacts NUTS!!

 

[doogald]

My Eris definitely splits texts longer than 160 characters into multiple messages. In fact, as I type it has two numbers, like this: 128/2. The second tells me how many messages I will be sending, the first how many characters I have left in the current message before it splits again.

When I had my last phone (a Windows Mobile Moto Q9m on VZW) I used to get those "the preceding message was split ..." when I RECEIVED messages like that from some other Verizon customers, as an extra text message.

 

[cmack]

This happens because CDMA carries (Verizon and Sprint) don't allow text messages longer than 160 characters, for whatever reason. The Eris is actually good about letting you send and recieve in multiple messages. Most phones on Verizon will not even send or let you receive messages longer than 160.

 

[Cory Streater]

googald: ours does the same thing, but if we send a message greater than 160 characters, the sides will see the message in the first post. You *might* not have this problem, because I think some of it is based on region.

braelens: open Handcent and from the main screen push the wrench icon. Then scroll down about 3/4 of the way and enable "Split 160".

 

[BraelensNayNay#AC]

I'm using chompSMS, not Handcent. I tried Handcent and even with the box checked to split the msgs, both me and the other party got the media removed msg after receiving the texts split up. I switched to chompSMS hoping it would stop the problem but both apps do this. It's VERY annoying!!

 

[Cory Streater]

If that's the case I'm stumped. The only other settings I can think of in Handcent are:

Compatibility Check = checked
Auto convert to MMS = checked

Is it just with this person? Also have to tried deleting the thread AFTER installing Handcent and then starting a new conversation? Other than that, I'm not sure, because this fixed all the problems I was having with the Droid.

 

[patches152]

Sms character support is limited. If someone sends a message with an unsupported character, or goes over 160 characters, prompting the network to split the message into multiple messages, you'll get that message.

For future reference, phones with EMS compatibility don't have this issue. Google search sms and ems standards to learn more. Wikipedia has the basics to understand it further.

 

[confused2gether]

I think i figured it out

Im using the handcent SMS and i just changed the Custom User Agent to ghost my phone as an iPhone (3.0) and just tested with a verizon and AT&T customer and i recieved all msgs from them over 160 like normal and didnt get the annoying message nor did they recieve the annoying "plain-text" message.

Hopefully that is it.

 

[confused2gether]

ok well the verizon customer finally kicked back with the error message but the AT&T customer didnt get the kickback message nor did I get the other "proceding msg..." txt. So only sorta fixed for now. More than likely going to be just screwed for the time being.

 

[patches152]

Im using the handcent SMS and i just changed the Custom User Agent to ghost my phone as an iPhone (3.0) and just tested with a verizon and AT&T customer and i recieved all msgs from them over 160 like normal and didnt get the annoying message nor did they recieve the annoying "plain-text" message.

Hopefully that is it.

ghosting the customer user agent doesn't change the network capability or the device capability for EMS. (read this if you need more details), which is why the VZW user gets the error message.

if you send a message with more than 160 characters from an EMS capable phone, the network will split it up into more than 1 message. since your phone isn't EMS capable, you haven't been provisioned for EMS sending and receiving. the app doesn't change that. make sense?

 

[Ty07allstar]

I chose Handcent over chmop because of the way that Handcent will pop up the box when you receive the message. This makes it 100% easier to reply to messages.

 

[Renocat]

This started happening to me but only with texts from my daughter, and only after I blocked her access to the internet which blocked pic and vid messaging. I assumed she was trying to send a pic and it was removed.

 

[pientka]

Samsung Fascinate with same issue

I have a Samsung Fascinate with the same problem. When someone sends me a message over 160 chars I get the message broken into 160 char chunks and then a final message "... media objects were removed...". The sender gets the error "...Destination does not support enhanced messaging service". I tried using handcent but the same issues happens even with the split 160 option set (BTW this is a send option in handcent and this is a receive issue). This would not be a big deal if the sender did not receive an error. I reproduced this using a LG dumb phone as the sender and I made sure I had no special chars, images or other media objects and I still get the error.

The Fascinate is the most advanced phone that Verizon sells and it does not support EMS?

Doers anyone have a solution to this issue?

 

[consultantnomo]

Old, but maybe useful. I have the Fascinate as well and after 2 weeks of active texting, I've never received the message modified notification. Rooted last night and now most texts result in this message. All are in-network w/ VZW and 2 are while texting Droid 1's.

Switching to Handcent and see where we go...