can you get a text of 160 characters from a VZW customer?

[Mark16q]

I know..lots of threads on the 160 topic but didn't see this issue. Over the last few weeks, if a vzw phone sends a plain text message over 160 characters to me, it gets broken up into 3 pieces, with the 3rd piece an error message that I can't get enhanced messages. The sender also gets an error message that their text message was converted to plain text as I can't received an enhanced message.

Weird thing is I used to receive over 160 texts no problem, and my son and wife can both receive over 160. just not my phone. Wife has a centro and son on Incredible.

Verizon has sent me a new phone that didn't fix the issue, and is sending me another quite confident that this one will work.

So...does anybody out there get plain text messages over 160 characters without error messages on either side?

Thanks,

Mark

p.s. running 1.5 and almost nothing else, as haven't had the time to load any app's. Loading and running Handcent didn't fix the problem

 

[cmajpwc]

Yeah this happens to me too. It's just a 1.5 thing. The reason your son can receive them is because the Incredible comes with 2.1

 

[Mark16q]

Yeah this happens to me too. It's just a 1.5 thing. The reason your son can receive them is because the Incredible comes with 2.1

thanks for the feedback. I am 99.9% sure I used to received longer messages, and that the sender didn't receive an error message if it went over 160 characters. And odd that my wife's ancient Centro has no problem either. I can understand from non-VZW customers, but within the network don't get why this is happening.

The VZW rep on the phone offered to sell me a used Droid for $290 if I wanted to switch...I laughed out loud and said it wasn't going to happen. We'll see how many replacement phones they'll send me before they either acknowledge it won't work or give me something that will. Very frustrating waste of time. I just want this to work right...not looking for something for nothing.

mg

 

[cableguynoe]

So...does anybody out there get plain text messages over 160 characters without error messages on either side?

Not positive this will work, but inhandcent there is a setting called Split 160.
Gives you the option to split or not split messages over 160 characters.

 

[smacky]

Texts over 160 from VZW come to as one big text. 160+ character texts from others come fragmented.

When sending texts, I no longer get the confirmation text back from VZW letting me know it was sent. This seemed to take effect with the 2.1 leak.

 

[Mark16q]

Texts over 160 from VZW come to as one big text. 160+ character texts from others come fragmented.

When sending texts, I no longer get the confirmation text back from VZW letting me know it was sent. This seemed to take effect with the 2.1 leak.

I tried using the Handcent split option, and it made no difference. The sender still gets the error message and I still get three pieces.

Confirmation of texts have never been received on mine, whether over or under 160 characters. When I get or send over 160 to non VZW I get a message that it's split, but not an error message, which seems reasonable.

mg

 

[smacky]

I tried using the Handcent split option, and it made no difference. The sender still gets the error message and I still get three pieces.

Confirmation of texts have never been received on mine, whether over or under 160 characters. When I get or send over 160 to non VZW I get a message that it's split, but not an error message, which seems reasonable.

mg

That's the "confirmation" message I'm talking about.

With 2.1, that goes away.

 

[Adam63impala]

Same happens to me too. Frustrating

 

[mc48]

The texts > 160 from my daughter (and son), who is on the same verizon plan as me and has an ENV2, are split into 3. I use Chomps. I don't think she has a problem with receiving my texts >160 but does receive a msg when sending it to me. We never had a problem when we all had ENV2s. I always heard it was a 1.5 problem and was corrected with 2.1. I am still on 1.5 so I don't know for sure.

 

[Mark16q]

That's the "confirmation" message I'm talking about.

With 2.1, that goes away.

That makes sense...I know few people that aren't on VZW so don't see it much. Odd that VZW doesn't seem to be aware of this specific issue given how many people I've talked to there.

Just spoke with them again (they screwed up the shipping order) and they are going to start giving me credits, amounts to be determined If they'd just get that f(*&ing 2.1 update done, it would seem so many problems solved.

mg

 

[smacky]

That makes sense...I know few people that aren't on VZW so don't see it much. Odd that VZW doesn't seem to be aware of this specific issue given how many people I've talked to there.

Just spoke with them again (they screwed up the shipping order) and they are going to start giving me credits, amounts to be determined If they'd just get that f(*&ing 2.1 update done, it would seem so many problems solved.

mg

The problem is with the other carriers, actually. I think VZW and Sprint allow for 160 characters on an SMS, but T-Mobile, I believe allows only 140..or 150...less than 160. Not sure about AT&T, but it may be a CDMA vs. GSM thing.

 

[cmajpwc]

The texts > 160 from my daughter (and son), who is on the same verizon plan as me and has an ENV2, are split into 3. I use Chomps. I don't think she has a problem with receiving my texts >160 but does receive a msg when sending it to me. We never had a problem when we all had ENV2s. I always heard it was a 1.5 problem and was corrected with 2.1. I am still on 1.5 so I don't know for sure.

I can affirm this. My girlfriend has an ENV3, and she gets all my texts over 160 characters. But, if she were to send me one, it would get broken up. I don't mind it breaking up so much as the error messages that get sent to my phone and hers that it didn't go through/supposed "objects" were removed.

Also, when I had an ENV2 and later ENV3, I never had issues from sending texts over 160 characters. I agree though hearing that it was a 1.5 issue but I haven't done too much research into if 2.1 fixed it.

 

[Mark16q]

I can affirm this. My girlfriend has an ENV3, and she gets all my texts over 160 characters. But, if she were to send me one, it would get broken up. I don't mind it breaking up so much as the error messages that get sent to my phone and hers that it didn't go through/supposed "objects" were removed.

Also, when I had an ENV2 and later ENV3, I never had issues from sending texts over 160 characters. I agree though hearing that it was a 1.5 issue but I haven't done too much research into if 2.1 fixed it.

Agreed...it isn't the breaking it up so much but the repeated error messages on both sides, then the sender wondering if I got so they send it again....when this happens I get a ton of the same texts, the thing is beeping, and flashing like crazy etc. Quite annoying and happening too often lately. And of course, with the lag on the phone, it takes awhile before I can even go in and start deleting the garbage and trying to figure out what I was supposed to get.

Now that everyone has a keypad on their phone, the occurence of >160 characters texts is frequent so I guess that's why it's driving me crazy.

 

[Demache]

The problem is with the other carriers, actually. I think VZW and Sprint allow for 160 characters on an SMS, but T-Mobile, I believe allows only 140..or 150...less than 160. Not sure about AT&T, but it may be a CDMA vs. GSM thing.

Its a limitation on how GSM phones send SMS's. They can only send 160 character messages. And then the phone splits longer messages and sends them. So this limitation would apply to AT&T as well.

 

[rick311]

i use chomp. there is an option for 160 split. i never have a problem with sending or receiving texts with more than 160 characters.