Recently my text messages have been starting with 0001/0002 and I am not sure why but it annoys me. They do it on any rom. I posted a picture. Any ideas?
Im getting the same thing but its only on some texts
Sent from my PC36100 using XDA App
I got a few like that, but only on June 22, and only from one person. She happens to be on an iPhone, but I got other texts that day from iPhones without it.
This happen to me a couple of days ago from my wife BUT she's on Boost Mobile so I figured it was something going on with her network or something........What ROM are you guys running?
I'm on the latest CM7 7.1 running Tiamat's SBC 4.0.5 kernel.....
It must be a sprint thing. I'm using the 3d and I'm getting it too. Or maybe a Sense thing?
Sent from my PG86100 using XDA Premium App
I can confirm. Multi posts doing the same thing.
Sent from my PC36100 using XDA App
I have been seeing the same thing when people send me long text messages, it's happened when people send from verizon/boost/cricket and t-mobile
i think it might be a GB thing, its supposed to do it when your text is so large it need to be split in to 2 or more smaller messages to be able to send, and its numbered so you know which message come first, sencond,etc. but there is a bug in the feature where the message app splits smaller texts too
Its looks to me like that's the message counter, like message 1 of 2, 2 of 2, for messages longer than 160 char.
I get this from my gf, she uses vz droid x running stock gb. Only her, no one else running gb or a different carrier. So my guess is not our phones or sprint but the others carrier.
Btw im on froyo so its not a gb thing for us.
Posted by some phone named the Epic.
Okay so I get it from my girlfriend using a feature phone on verizon so it's not a thing her phone is doing. If just started a month ago. It's not on all her texts and of she sends me a message 3 texts long it only counts her first two then the thrid is untouched. It's not a sense thing because it happens on Miui and cyanogenmod. It has to be at the carrier level.
Sent from my PC36100 using Tapatalk
I think its defiantly a sprint thing that just recently happened... if i get a text that is over 160 characters. Instead of breaking the text into 2 parts i get 1text around 160c and then 2 more saying 0001/0002 that each have only about 20 or so characters but its weird it splits the message into 3 parts leaving 1 alone... Sprint should defiantly change whatever they just recently added into their texting feature....
Yeah this is happening to me as well. My gf is on T-Mobile and if she sends me a long text, it breaks it up, but not in a logical manner. I get the first message of 160 char, then the next might only be a sentence, followed by another short message. So what should have been 2 messages, turns into 4 or 5 sometimes.
happening on my phone as well. Running SnS 2.2 froyo, so its not a gingerbread thing. This ONLY happened before with people using Handcent, people using stock messaging apps it never happened. It used to just break up the text without a 1/2 counter, but now it happens anytime. Specifically my gf who has an Incredible on verizon, and she is using the stock messaging app. So it seems like maybe this is something sprint is doing on their end.
It numbers the texts in order because who ever sent it sent you a text longer than 160 characters, it seems android is numbering the texts for you so you won't have to put together the puzzle figuring out what text came first.
GV
Are you using google voice? I had issues with mine.
I believe it has something to do with the message thread as well...whereas you can delete individual messages from a thread as opposed to the whole thread.
This is a Sprint network thing. They probably changed something in the SMSC (Short Message Service Center) to make it do this. This is happening to both me and my brother. CM7 on my EVO, Mik (I believe) on his EVO Shift. Doesn't matter what carrier or phone the incomming message comes from, it happens all the time.
That should answer it for everyone
Actually that is in the sense 3.0 mms app. Mine does that on my 3D LOL, try an aosp rom it won't do it and based on your screenie you're using sense 3.0/2.1
Sent from my PG86100 using XDA Premium App
dirkyd3rk said:
Actually that is in the sense 3.0 mms app. Mine does that on my 3D LOL, try an aosp rom it won't do it and based on your screenie you're using sense 3.0/2.1
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I'm telling you guys its network related. Both mine and my brothers phone have not changed at all and this started to happen the other day. I'm on aosp he is on sense. Two different devices. But what do we have in common? Location and carrier. Sprint changed the way that texts are handled.
Related
I remember this happening to my rooted g1 with the slow and sort of crappy sense ui installed; so when my wife complained that her text messages on her Slide dont go in order i was shocked that the problem STILL exists.
I didnt see a thread about it here, sorry if i missed it. Anyone else have text message conversations where the texts are out of order? Phone is stock btw
I appear to have that same problem too, but I'm using stock Android right now. If we have the same problem I can elaborate on it more.
My problem seems to be that if I get a text message reply from someone and it's in the same minute as the last text message I sent the person, their text will go above mine, even though they sent their's after I sent my text.
So for example: I send a text to somebody at 3:20:15PM and that person sends a text to me at 3:20:55PM, their text will go above my 3:20 text, making it look like they sent the message first.
I had this problem as well, before my phone was rooted and even after. The only solution i have found is to install a different SMS app, which i use Handcent because its the closest to the stock app, and its free.
interesting, my wifes is stock and she said it happened with texts that were no more than a minute apart as you mentioned.
i just cannot believe this is still a problem. Sense UI is neat but this sure seems like a fundamental feature that shouldnt have such issues...
same thing has been happening to my texts, before and after root.
i can say the same thing happens to me also
Sent from my T-Mobile myTouch 3G Slide using the XDA mobile application powered by Tapatalk
I've searched far and wide, and can't seem to find anything on the issue I'm having. Or maybe I'm not looking in the right places, but it's been about a straight hour know that I'm looking and can't find the answer I'm looking for.
My problem: When I send a SMS as ONE text it sends perfectly, but once the text reaches 2 texts and I try to send it does not work, it says "sending..." for literally 10 minutes then I get a notification saying the message cannot be sent. I have no idea what I could possibly do to fix this. Someone help, please?
My suggestion is picking up the phone and calling them.. clearly you have alot to say.
(its late... you'll have to excuse me... lol)
criccio said:
My suggestion is picking up the phone and calling them.. clearly you have alot to say.
(its late... you'll have to excuse me... lol)
Click to expand...
Click to collapse
Yeah, I was expecting something like that from this time at night..lol. I did laugh.
I think the problem is that the message you're trying to send is over 160 characters, and since SMS messages can't be over 160 characters, and the messages app isn't breaking the text into two texts, it can't send and just times out. Try using chompSMS or Handcent as an alternative, as they have auto-160 breakout features.
A known problem with that Rom. Can't send texts over 160. Why I tries fresh Rom. Can't stand that and don't like the sms in the market. If I can find out to put froyo sms on the Rom id switch back to pick. Bit that's a downfall to me personally.
Sent from my PC36100 using XDA App
martyzidek said:
A known problem with that Rom. Can't send texts over 160. Why I tries fresh Rom. Can't stand that and don't like the sms in the market. If I can find out to put froyo sms on the Rom id switch back to pick. Bit that's a downfall to me personally.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I really must agree with you. The rom is awesome, but that's a major issue for me. ah well, guess I'll go back to Virus or someone else.
Sent from my PC36100 using XDA App
I should spell check before sending. Amyways, on cm6 my sms never had the letter counter so could never tell if over or not. I thought it was the kernel I installed. Then went to the Rom topic and people had the same problem. If I can find out how to pull the sms apk from froyo and push it to cm6 is say I have a perfect Rom.
Sent from my PC36100 using XDA App
Removed...
Yeah, this is a real issue. CM6 was originally for GSM networks, which don't have problems with extra large SMS messages. They haven't tweaked the AOSP messenger for CDMA networks yet (by splitting messages).
Here's the issue on the bug tracker. http://code.google.com/p/cyanogenmod/issues/detail?id=1942
Be sure to go there, reply and star the issue.
Saturn2K said:
Yeah, this is a real issue. CM6 was originally for GSM networks, which don't have problems with extra large SMS messages. They haven't tweaked the AOSP messenger for CDMA networks yet (by splitting messages).
Here's the issue on the bug tracker. http://code.google.com/p/cyanogenmod/issues/detail?id=1942
Be sure to go there, reply and star the issue.
Click to expand...
Click to collapse
That makes perfect sense. That's pretty game-breaking if you ask me. I'm sure I'm not the only one who finds that to be a huge problem. I'll definitely go to the link you provided and take it from there. Thanks everyone for your responses.
Sent from my PC36100 using XDA App
I was running synergy for a while. It was the beat rom out there to me, absolutely loved it until I ran into an issue. I'd go a half day or so without receiving a text but would think nothing of it because I'd be at work. When I'd get off though people would call me asking why I was ignoring them when in fact I hadn't received any texts. This started happening day in and day out. There would be the rare occasion that I did receive the texts and just not get any notifications of them but mostly they just weren't received. Does anyone know what may be the cause of my text issues. Any info would be greatly appreciated. Thanks in advance
Sent from my PC36100 using XDA App
i would always do a full wipe and reflash. I've had that problem on Synergy as well as MikG. I also use an app called Ghostly Gingerbread SMS from the market which catches all of the missed messages (i highly recommend it). Apparently Gingerbread has some kind of bug with the internal database.
I wouldn't blame that issue on Gingerbread. I've been using Gingerbread forever and the ONLY time I had that issue was when Google Voice completely screwed up my message handling.
OP, if you're using Google Voice make sure your Sprint number isn't integrated with it at all. If it is then Google Voice is handling your messages and you'll have to modify strings within the Google Voice app in order to get them on your normal messaging app.
Sent from my Supercharged HTC Evo 4G using XDA App
I would because it has happened to me and I've had to use that same app with Syngergy. I use Google Voice but ALWAYS skip Sprint intergration as I want my texts going to the Sense SMS not Google Voice. I only use GV for my voicemails.
Apparently, if your RAM gets too low, GB will end the SMS database process which will cause your phone to lose messages.
I had this happen between me and my girlfriend. We text constantly and there has been many instances when I have used Synergy or really any Sense 3.0 based ROM that several messages would not come to my phone.
It does not seem to happen as much on the Sense 3.5 Roms I've used as there is either more RAM available or perhaps the later versions of gingerbread (I'm running 2.3.5) have this bug fixed.
It was very annoying to say that least, thinking your being ignored when really your phone just never "saved" the text, lol.
Thank you for the help, ghostly does the trick wonderfully
Sent from my PC36100 using XDA App
I know this was an old issue before we had Gingerbread, but I was surprised when a coworker of mine with the same phone (Tmo GS2) told me (and showed) me that he was experiencing this still even on a brand new phone (used to have the issue on his old Vibrant).
What happens:
Receive a text message, open up the conversation. Shows the correct conversation, but if you look more closely at who the actual Recipient is, it will be some other random contact.
Any ideas out there? Is Samsung using older, unpatched source for messaging?
kevinbear said:
I know this was an old issue before we had Gingerbread, but I was surprised when a coworker of mine with the same phone (Tmo GS2) told me (and showed) me that he was experiencing this still even on a brand new phone (used to have the issue on his old Vibrant).
What happens:
Receive a text message, open up the conversation. Shows the correct conversation, but if you look more closely at who the actual Recipient is, it will be some other random contact.
Any ideas out there? Is Samsung using older, unpatched source for messaging?
Click to expand...
Click to collapse
I remember when that happened on my vibrant and i accidentally texted my friends dad...was a nightmare. Sorry drifted off topic lol.
Sent from my SGH-T989 using XDA App
kevinbear said:
I know this was an old issue before we had Gingerbread, but I was surprised when a coworker of mine with the same phone (Tmo GS2) told me (and showed) me that he was experiencing this still even on a brand new phone (used to have the issue on his old Vibrant).
What happens:
Receive a text message, open up the conversation. Shows the correct conversation, but if you look more closely at who the actual Recipient is, it will be some other random contact.
Any ideas out there? Is Samsung using older, unpatched source for messaging?
Click to expand...
Click to collapse
This is actually a random android issue including with the one were recipients get double text messages.
Sent from my SGH-T989 using xda premium
Killbynature said:
This is actually a random android issue including with the one were recipients get double text messages.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I thought this was an issue that had been resolved though. I've never experienced the problem, on the same device, though I run custom ROMs not stock.
Wasn't this Tiger Woods' excuse?
Sent from my SGH-T989 using xda premium
OK quick question... searched a bit and cant find anything, but I swear I have seen this before... just flashed my old Epic with the newest MIUI for the old lady, and now her phone is sending jibberish texts... she will type one and it will send a couple extra of all @#%$$%$*&%*^**(&)(**&*&$%$#^^*(&()&) stuff... Ideas? I was thinking it was because she has been playing with the themes, and one of them jacked up the SMS... ??? Or possibly it needs hands free activation?? It did get the 9016 texts saying it was activated... help?
Known issue you need to have it split the messages after a 160 characters. Also don't send mms over wifi...
Sent from my SPH-D700 using xda premium
Thanks for the replies, but my question was not about the split sms issue, as in a text 'testing' ALSO sends a jibberish message or three. Reflashed and now no texts go outbound whatsoever. Will try gosms etc to see if it solves this problem as well, wasnt looking for the split issue, already knew about that... but Ill try anyways... Read all the sms related issues in the MIUI thread... but under 160 chars... idunno.
EDIT: Installed gosms, killed its notificaitons, turned on split... no dice.
Are you on wifi.....
Sent from my SPH-D700 using xda premium
I deleted my post. We misunderstood.
Sent from my SPH-D700 using xda premium
Thanks Kennyglass... been googling and found all sorts of sms issues, almost all Sprint (ns4g, OG Evo, Epic)... but none exactly the same as this issue. Now its not sending sms at all... (not mms, but I will try that too) but can receive. At least this time it registered the *99 for my airrave (it was already connected to it, just to confirm)... think ill flash back to stock and try again... so let me get this straight, with MIUI currently you have to turn off wifi to send mms, sms, or both? And of course the split message thing... thats easy...
Edit: killing wifi but as I had already reflashed now I cant replicate the jibberish... will see after another clean download and return to stock... thanks guys... I kinda think its a network issue... not sure...
You sure its not jibberish mms? That's a known issue
Sent from my SPH-D700 using XDA
stevie13.xo said:
You sure its not jibberish mms? That's a known issue
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
I have read threads where the jibberish is triggered by 160+ char. texts, but not by one word texts. I haven't been on the Epic thread in quite a while, so maybe im missing something. Could you describe the known issue... and how to solve get around it???
OK so not sure if this was related to the jibberish, but phone would not send messages until I called sprint, (forgot hands free activation dialer code), did that, profile, prl... still didnt work. Power cycled Airvana... bam... works... stupid Airvana... cmon go team Network Vision! Id love to know if the jibberish is related to the Airvana, or just some weird bug though...
I had this same problem on AOKP. About a third of my txt msgs were being received as gibberish.
It's really what caused me to switch to People's ROM. That and the camera problems.
Edit: in believing that the issue is likely fixable, I have switched back to aokp.
Sent from my SPH-D700 using xda premium