Texting issue? My app, or my OnePlus2? - OnePlus 2 Q&A, Help & Troubleshooting

When I start a "new message" and send it, it starts a new conversion. When someone reply's to it, it goes into an older conversation that I had with them earlier that same day, or week. It never did this on my other phones and just started really using the OP2 yesterday.... As soon as I restored my SMS backup I started having this issue, which is when I started using this phone.
Anyone else have this issue?

Are you using stock messaging app?

No, YAATA SMS... But it has worked fine on my last 2 phones. Just stated this issue when I started using the OP2.... I'm going to delete it and reinstall it and try a different app, to try and narrow down the problem.

tele_jas said:
No, YAATA SMS... But it has worked fine on my last 2 phones. Just stated this issue when I started using the OP2.... I'm going to delete it and reinstall it and try a different app, to try and narrow down the problem.
Click to expand...
Click to collapse
Oxygen OS seems to register, for example, +1 (123) 456-7890 different from (123) 456-7890. So if you have (123) 456-7890 saved as a contact and you start an SMS thread with (123) 456-7890, some carriers use the +1 in front of (123) 456-7890. So Oxygen OS doesn't merge the two as one number when they really are the same number.
I had this issue with the messenger app from Google but Textra and Hangouts SMS seem to get around this "issue". I'm on Cricket Wireless, if that matters.
Seems like an oversight from Oneplus, one of many...

Phrankeeh said:
Oxygen OS seems to register, for example, +1 (123) 456-7890 different from (123) 456-7890. So if you have (123) 456-7890 saved as a contact and you start an SMS thread with (123) 456-7890, some carriers use the +1 in front of (123) 456-7890. So Oxygen OS doesn't merge the two as one number when they really are the same number.
I had this issue with the messenger app from Google but Textra and Hangouts SMS seem to get around this "issue". I'm on Cricket Wireless, if that matters.
Seems like an oversight from Oneplus, one of many...
Click to expand...
Click to collapse
Yup, this is it, I don't use the "+" but I did but the 1 in front

Ok..... I just tried 3 different apps and they all did it, so I now know what the issue is and I'll see if I can get around it. Just sort of annoying to have 2 different conversations with the same person going.

Related

[Q] Issue with txts going to the wrong person magically...?

When you have a text log with the original person? I have noticed it shows up in the notification tray under 1 name and then under the actual msg app its to the right person but it makes me scared at times who the last txt REALLY went too..
In the stock messaging app (all I use) Ill start a txt conversation with person x then down the line it'll send the next to person y... idk if it was a confusion between the linked fbook accounts but it almost got me in trouble so now for safety sake I dont have fbook linked to contacts...
Anyone notice this or is it just me?
Sorry to hear this. If its the same two contacts each time, I'd suspect your two contacts may have automatically linked or merged phone numbers. Inspect each one's details for the other's phone number. For example, I found that two contacts who shared the same email were merged, completely deleting one's name entirely.
I'm using Handcent myself so not sure if this would be related, but I've found that text messages received from one particular number (my bank's alerts) always appear as another contact (a friend) in the initial pop-up alert but then appear correctly in Handcent's actual message threads. I've since swapped and rebuilt the handset to no avail. This issue remains a mystery.
Sent from my SGH-T959 using XDA App
not the same contact. Thats what I originally thought it was something merged weird but its random. so I am not too sure but it makes me whery what I send to certain ppl. For some reason im friends with enemies of the other friend so saying 1 thing starts a fight btwn the 2.. lol I cant win.
same problem, HTC EVO, seems like it goes to a random person, facebook contact or not.
This is a huge problem and is related to the Android platform, not just the Vibrant. You can find more information in the following two links:
1. www.google.com.vn/support/forum/p/android/thread?tid=345259e6d424bad3&hl=en
2. http://code.google.com/p/android/issues/detail?id=9392
The best thinking that we have on the problem so far is that it is in the ComposeMessageActivity.java file. But it would be great to get more eyes looking over the code to try to get this one licked.
Note: A 3rd party app may make the situation better, but will not resolve it. Best solution is that if you receive a text or e-mail message (or anything that plays with the notification bar or takes focus from what you're typing), quit your message and start over.
This scares the hell out of me. Is there any specific instance when this always happens?
Strange, never had this problem and I've been using Android since the G1. There must be something you are doing or a setting you have that specifically triggers it.
There's nothing related to Facebook - I don't have anything linked on my phone. And I never had this issue on my G1, but I also didn't start screwing with the Vibrant until recently, so it's not something I'm "doing" - it's happened within weeks of getting the Vibrant on launch day.
It can be quite scary. Luckily my friends getting msgs meant for my wife hasn't bit me in the ass yet. But if it ever gets mixed up going to a female friend, I could see this not working out in my best interests, ya know?
-bZj
I've had the same problem on my vibrant and my g1. What I've noticed is that if I send a nescafe to person A then receive a message from person B and access that message by using the notification bar and answer person B, the message can go to person A (the last person I sent to.) I've found that if I remember to not use the notification bar and only access messaging by using the icon, I haven't had the problem. Not the best solution but at least it seems to work.
This could be bad
This could be bad especially if you have more than one girlfriend
Omg glad im not the only one. Had to couch it one night cuz of this issue. Now i only text my girl from my phone. Everyone else i text through gv lol.
I use the notification bar all the time and occasionally reply to the weekend person but that's just because I didn't press on the right notification...
yea i had this happen to me as well. luckily or unluckily a txt i was sending to a girl whom i was fooling around with got sent to a girl i had just met 3 days prior. after that needless to say she wouldnt talk to me waa waaa. it was prob a random bug introduced in earlier builds.. say around a month and a half ago. oh yea i had about 12 threads running around 50 a piece.. maybe that had something to do with that and maybe the random stuttering of the vibrant when too many programs are running. Havent had that happen again thankfully but one would have to say.. slow down on the texting sometimes lol
vinnydakid said:
This scares the hell out of me. Is there any specific instance when this always happens?
Click to expand...
Click to collapse
The evidence seems to suggest that the problem is in the ComposeMessageActivity.java file, which means it is not SMS Client related. Said differently, using a 3rd party SMS client might reduce the likelihood of the problem but does not eliminate it.
Now, to answer your question. It seems like the problem happens when multiple threads or events happen when using SMS. For example, it might happen when you are editing a message and when you receive a SMS text message. (It is more likely if you use the notification bar to pull down the message rather than navigating to it in the SMS client.) The good news is that people are trying to reliably reproduce the problem so that we can troubleshoot and fix the problem. (See my earlier post in this thread for a link of those discussions).
kangxi said:
Strange, never had this problem and I've been using Android since the G1. There must be something you are doing or a setting you have that specifically triggers it.
Click to expand...
Click to collapse
Based on the review of the code, one fix seems to have been made to the 2.2 code branch. However, people using 2.2 have indicated that they are still experiencing the problem. The problem is in the library. However, there is a very unique set of circumstances that have to occur before you see the problem. It's quite possible that people who haven't seen this problem yet just use the UI in such a way that the problem doesn't show up.
98classic said:
Omg glad im not the only one. Had to couch it one night cuz of this issue. Now i only text my girl from my phone. Everyone else i text through gv lol.
Click to expand...
Click to collapse
i second that. this glitch can be nasty. hopefully it will be addressed soon. GV for the win.
I have the same issue here. It will show one name but have a conversation for another, or the name and the convo are right, but the picture is wrong.
I think I found a solution to the thing. Been getting it a LOT and pissed me off on more than a single occasion.
So. If you are talking to someone and SUDDENLY receive a text message from that person but when you open it, it changes the name of the contact to someone else or ....I guess everyone who has experienced it KNOWS what it looks like. So when you GET IT, open it, then CLOSE the whole messaging app. Then restart it and it should fix itself and be back to texting the right person. If it doesn't (or if you want to be on the safe side), kill the messaging app with a task killer or task manager and restart it.
This has fixed it recently for me. Had it happen a total of about 15 times, with me finding and using the trick about the latest 5 times and it worked every time.
Note that I AM running Bionix Fusion 1.0 with Voodoo if that makes any bit of a difference.

Facebook phone number issue.

I searched around and found a few people that had this issue, but not with the Continuum any fixes I found/suggested, I have tried. I just recently rooted and loaded clean DL17 ROM. Everything is working great, phone seems to be little bit more responsive and more snappy. Now before rooting and flashing I never had this issue. So it could be a newer issue or older and I'm just now experiencing it. If I receive a text from anyone that has their number on their Facebook profile the format comes up (+1-###-###-####), if I reply to the message they won't get it. I have tried deleting all conversations in messaging and fixed the number format to (###-###-####)and initiating a conversation. Once I get a reply number format changes back to the +1 format. I scoured google and it seems some people just started having this issue Monday and I also read this is an older Facebook issue. Apparently the +1 is a country code, I have tried creating a phone contact and linking with the Facebook contact, as well as setting certain numbers as default with no luck. No matter what it always defaults back to +1 format. I can call people using that format no problem. I don't think the new ROM has anything to do with it but could be. I more or less think its just a coincidence this just happened to start on the week I decided to root and flash my phone. If anyone has any ideas or info. on this please share. Thanks
PS: The two buddies who numbers I'm experiencing this with have Droids. They don't have an issue. My number shows up on their phone in regular format ###-###-#####.
+1
I had the same problem with regular texts. It is the +1 that is doing it. I had to edit all my numbers in google voice. I resorted to going to Verizon and having them monitor my tests. It is device specific on their end.
Logan

[FIX] People not receiving your texts? Read this

When you download the Facebook for Android app, it asks you to sync contacts. DON'T DO IT. Whenever someone has a phone number in their Facebook profile, regardless of if there is an existing contact that it will link to or not, the number will have a +1 in front of it. For instance, a number that should read 123-456-7890 would read +1123-456-7890. Facebook adds this for unknown reasons. When you send a text to the borked number, the text goes through, even on verizon.com, it says that the text was sent by you and that the other person received it on their profile. However, the person does not receive it on their phone. Also, if you call someone with a borked number, the phone will not ring.
In conclusion: Don't sync Facebook contacts, and your SMS should send fine and calling should work fine. Alternatively, you can use any messaging app but stock, such as Go SMS Pro and the message will go through fine, even with the +1 format.
Hope this helped someone.
AgalychnisCallidryas said:
When you download the Facebook for Android app, it asks you to sync contacts. DON'T DO IT. Whenever someone has a phone number in their Facebook profile, regardless of if there is an existing contact that it will link to or not, the number will have a +1 in front of it. For instance, a number that should read 123-456-7890 would read +1123-456-7890. Facebook adds this for unknown reasons. When you send a text to the borked number, the text goes through, even on verizon.com, it says that the text was sent by you and that the other person received it on their profile. However, the person does not receive it on their phone. Also, if you call someone with a borked number, the phone will not ring.
In conclusion: Don't sync Facebook contacts, and your SMS should send fine and calling should work fine. Alternatively, you can use any messaging app but stock, such as Go SMS Pro and the message will go through fine, even with the +1 format.
Hope this helped someone.
Click to expand...
Click to collapse
Nice Find man i havent noticed this but ill be weary of this from now on
How does this explain people receiving some messages and not others? If it was the number they wouldn't receive any texts at all, not just 30% of them. I noticed this a while ago and I couldn't call people with the +1, but they received texts just fine.
Sent from my Optimized Shift using XDA App
Only people who have their numbers listed in their Facebook profile are affected.
This is what worked for me. If it doesn't work for you, then I'm sorry.
I'm not saying you're wrong. I'm just saying maybe there's two seperate issues. Without my Facebook contacts synced some messages are going through and some aren't. Maybe its just me, but I've seen posts with people saying the same. Thank you for your solution nonetheless.
Sent from my Optimized Shift using XDA App
You're welcome. I'm not saying by any means that this will solve everyone's issues. Just my experienced and it worked for me. Best of luck to you on sorting whatever is up with your SMS out. What ROM are you using?
+1 is the country code for the USA, no idea why it's adding it though. I know that wavesecure requires you add +1 to the contacts on your contact list since the texts come from somewhere in asia IIRC (may not be true now since McAfee owns them).
I know it is, but since it's a cell phone, you don't use the 1 or +1, which messes it up.
Thank you for putting this up. I was confused and frustrated as to why lots of my contacts didn't receive or was able to send any texts or calls to me. But now its all good
I'm going to test this theory. Hope this works. Thanks
AgalychnisCallidryas said:
When you download the Facebook for Android app, it asks you to sync contacts. DON'T DO IT. Whenever someone has a phone number in their Facebook profile, regardless of if there is an existing contact that it will link to or not, the number will have a +1 in front of it. For instance, a number that should read 123-456-7890 would read +1123-456-7890. Facebook adds this for unknown reasons. When you send a text to the borked number, the text goes through, even on verizon.com, it says that the text was sent by you and that the other person received it on their profile. However, the person does not receive it on their phone. Also, if you call someone with a borked number, the phone will not ring.
In conclusion: Don't sync Facebook contacts, and your SMS should send fine and calling should work fine. Alternatively, you can use any messaging app but stock, such as Go SMS Pro and the message will go through fine, even with the +1 format.
Hope this helped someone.
Click to expand...
Click to collapse
Try using Contacts Clean-up from Android Market. It works great and resolved my issue on the fly. Dev just made it CDMA compatible
I think this only matters on sense roms. I know I need to be on aosp for dialing businesses through voice search to work because it also adds a +1 (at least it used to).
Thanks for the post. It was driving me crazy.
MorphiousGX said:
Try using Contacts Clean-up from Android Market. It works great and resolved my issue on the fly. Dev just made it CDMA compatible
Click to expand...
Click to collapse
Just downloaded and used, great app! Thanks for the suggestion.

Strangest issue I have ever seen....

Not even sure if this is XPlay specific. I have ONE contact, one friend that if I try to text message her my messaging program FC's. I even tried deleting her and physically entering her phone number, and it FC's. Every other contact or anything else I do, works fine. I tried clearing data for messaging, tried clearing data for contacts. My phone is stock and not rooted or anything at all. Anyone ever seen this?
Your phone is just looking out for you. Stay away from her!
j/k
I've never seen this issue before...
hairdewx said:
Your phone is just looking out for you. Stay away from her!
j/k
I've never seen this issue before...
Click to expand...
Click to collapse
She is a bit crazy lol, but a good friend.
I can't even imagine if it was my girlfriend that this problem was with. "Sorry sweetie I can't text you because my phone keeps crashing the text message app, but ONLY for you". That would go over real well!
That's odd.
Try using GoSMS and/or handcent sms and see if they get the same problem.
well I just made it worse...
I called her and had her text me, instead of a text coming through i get a force close message. Even better I think its jammed and trying to send it through so I'm getting the error over again every few minutes.
I think I'm gonna need to reset my phone
EDIT: it stopped after a bit. Also scrolling through my contacts I found another contact with the same issue.
EDIT #2: While typing Edit #1 I realized both are contacts that I text often. However recently I lowered my saves message limit from 100 to 50. I had manually deleted some threads including threads from these two people and they had over 100 messages. I went into messages and did a "delete all" and that cleared the issue.

No contact name on 3rd party SMS apps

I have tried gosms and hand cent and one other and my contacts name do not show up its just there phone number twice is. Am I the only one dealing with this and if not is there a fix?
Sent from my Crespo4G using Tapatalk
I had to change my contacts numbers to +15555555555 format for them to work in GoSMS, someone else mentioned they just took the dashes out of one contact and that fixed them for him.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1399603
Dam ... I thought I was the only one having trouble. Am using Pansi SMS and thought it was the problem with the app. Went back to an older version, tried restoring old messages to see if old app plus old back up would do the trick, but no go ...
Are you on ICS? I think I noticed this problem since moving to ICS.

Categories

Resources