Database Develop

Text's going to wrong person?

i just installed this Rom on my Nexus:
FRF83-update-nexusone-rooted-signed.zip
i wiped everything before installing and everything is running smooth.
i love the Rom, but i started noticing that ppl kept texting me back ? marks
or saying what was i talking about. i guess texts are scrambling and sending to diff ppl, and im receiving text's under ppl that didnt originally send the text if that makes any sence.
is any one else experiencing this? i remember reading an article about it i think on engadget or gizmodo. but im wondering if its a ROM or Google thing.
in all fairness i did use the search button, no flaming or being rude or else u get a stick trown at you

this has been reported long time ago on 2.1 when the nexus first came out. then other phones reported it like the droid. google never figured out what exactly caused it, it was baffling. i've always used handcent insstead just because of this "possible" glitch. i could get in a lot of trouble if i sent a text to the wrong person.

Weird this is the 1st time its happend to me or any one telling me about it. i rebooted hopefully it wont happen, cause i can also get in trouble sending wrong texts to the wrong person. The GF was already asking ?'s because the text she got wasnt related to anything we talked where texting about.

Android Phones Play “Chat-Roulette” With Your Text Messages
I have always been a big fan of Google Android phones. Sure the user interface may not be as polished as the iPhone. I admit the Exchange support might not be as tightly integrated as it is on the Blackberry. But, I’m a geek and I’m willing to put up with some annoyances as a trade-off for speed and flexibility and customization. And I’m not alone. Market researchers Canalys and NPD Group both recently published reports stating Android was running on > 40% of all smart phones in the United States. It would seem Android is destined for dominance.
Except somewhere along the way, Google seems to have forgotten first and foremost Android phones need to be phones. And that is why I’m seriously considering making the move to Blackberry or Windows Phone 7. For the last six months now I’ve been dealing with a huge flaw that makes my phone unusable for SMS texting. From what I’ve been able to tell using analytics provided by Google’s developer site, as many as 77% of Android phone users are at risk of having their text messages sent to a random contact.
That sounds unlikely right? I mean you pay upwards of $200 for a smart phone, and next to making phone calls, sending SMS text messages is probably the most used feature of the phone. But it’s true, and if you don’t believe me just type “android SMS wrong contact” into Google’s search engine and see how many hits you get. It’s astounding. It’s happening. And Google seems to be ignoring it altogether.
The first time I responded to a text message from recipient A, and it went to recipient B, I just wrote it off to user error. I was in a hurry. I fat fingered it. Who knows, right? In time though I’ve begun to qualify and quantify this serious bug and disaster waiting to happen. The worst part is you don’t even know your text message went to the wrong person until you get a call or new message from someone in your contact list asking “what was that last message all about?”
On the sender’s phone, the text message actually shows as sent to the correct recipient, yet I’ve been able to get all three parties with their phones to sit down in one room and verify that in fact the intended recipient did not receive my text, and a random contact did. I will put up with a lot of minor issues for a cool phone, but having my privacy threatened is not one of them.
What irks me the most is that owners of these phones, me included, have no recourse. The bug is part of the core operating system, and has been since Android 2.1, (though it seems worse with 2.2). Phone model doesn’t matter. Using a third-party SMS application won’t help. Contact your phone carrier and you will be told to do a factory reset then call the phone manufacturer. Contact the manufacturer and you will be told to do a factory reset then get in touch with your carrier. This is a flaw with Google’s code so how is it they managed to slip out of the support loop altogether?
Ah, I think now we have reached the heart of the problem haven’t we? By making it an open source solution, Google isn’t really accountable. Or are they? I guess that depends on you and me. Google has a vested interest in fixing any flaws that are impacting their continued effort for world smart phone dominance. If those of us who have made this platform so successful for them draw a line in the sand perhaps someone at Google will take notice.
The issue at hand has been logged in the Google forums for some time now. Sadly, it’s rated as only having a priority of “medium” and I’ve yet to see anyone from Google comment on the current state. I would urge any of you who have Android phones to log into the Google forum and star the issue. You can find the link in the code google forums. In the mean time, I’m going to continue evaluating some of the new Windows phone offerings. Just in case Google decides new UI bounce effects on widgets are more important than where my SMS text messages end up.

I've never had a text message go astray, personally.

I just had this about two or three times.
The chosen recipient didn't got my text message. But to be honest, noone contacted me, that he got my message, and the reciplient has a very bad mobile network coverage. So hopefully noone is laughing his ass off about my stupid messages

iPhone to Moto X - iMessage?

My pops got the Moto X, and he's not receiving some texts because of iMessage. I'm sure you've all heard this before.
I'm looking for the best solution if anyone has any information?
By googling, it seems the methods are:
-turn off iMessage on the device
-change password of the apple account
-unregister the apple device
-have the person who is trying to text you delete their text message thread and start a new one
I've done the first 2. The third one I can't seem to do because when I login to the site, the device isn't listed, so I guess it was never registered in the first place?
Besides those first 3, it seems the last one is important. The problem is, how can you know who is having problems and who isn't? So how do you know who to tell to delete the thread?
Does anyone else have any easier methods to quickly resolve this? Any help would really be appreciated.

i would call apple support and see what they say i just did some reading on this issue and there are 100s of different so called fixes but none of them work for everyone. so my best bet for you is to call apple support
but here are some websites that might help you idk apple need to get on there game and get this fixed
The only approved steps so far are to turn off iMessage on your old iPhone, have Apple Support revoke the certificate to disassociate your phone number from iMessage/Facetime, and for anyone using an iPhone to send you messages to update to the newest iOS (7.1 for iPhone 4 and higher, 6.1.6 for 3GS).
Code:
Other possible steps:
1. Go to www.icloud.com and make sure the device is removed from Find My iPhone.
2. Backup and then restore as new your old iPhone.
3. Go to id.apple.com and change your Apple ID's primary email address to something different than it currently shows.
4. Go to id.apple.com and change your Apple ID password
5. Have the other iPhone users delete the existing message thread, delete your contact from their iPhone, backup and restore from backup, and then re-add your contact using only your phone number. Also, make sure they have 'Send as SMS' turned on.
The core issue is usually the other iPhones not sending the message as SMS when it should.
Code:
"If you have access to your iPhone 4 you are going to want to go into the phone and turn your iMessaging off, http://vz.to/1hRAZNz.
If you don’t have access to your iPhone follow the steps below:
Step 1
Go to supportprofile.apple.com/MySupportProfile.do.
Step 2
Log in with your Apple ID and password.
Step 3
Select the product you need to de-register (your iPhone, for example).
Step 4
Click ‘Unregister’.
Step 5
You’ll see the message ‘Are you sure you want to unregister and delete this product?’ – Click ‘Unregister’ again.
other info i read was to put the sim card back in the iPhone. restore the iPhone to stock and then go back threw and make sure imessage and facetime is off. and then to call Apple support and have them revoke your certifications.
the issue is a simple problem the iphones are trying to send you a msg via imessage because there iPhone still thinks you have it. why apple can't find a simple and easy fix is blowing my mind.

how long has this been going on. usually after you process steps 1 and 2.. it clears off after 12-24 hours. if its still not.. then double check your other devices.. is it set up on the ipad? or on an apple computer? those can also interfere... gotta turn off imessage on all devices where the phone/imessage account was set up on.
that happened to me with my when i first picked up my moto x... couldn't figure out what was wrong.. even verizon and apple customer service coudldn't tell.. then i noticed my ipad kept going off with missed notifications.. turned it off there.. and voila! problem solved..
steps 3-5 aren't that important... just 1 and 2 are the key ones...

aldouse said:
how long has this been going on. usually after you process steps 1 and 2.. it clears off after 12-24 hours. if its still not.. then double check your other devices.. is it set up on the ipad? or on an apple computer? those can also interfere... gotta turn off imessage on all devices where the phone/imessage account was set up on.
that happened to me with my when i first picked up my moto x... couldn't figure out what was wrong.. even verizon and apple customer service coudldn't tell.. then i noticed my ipad kept going off with missed notifications.. turned it off there.. and voila! problem solved..
steps 3-5 aren't that important... just 1 and 2 are the key ones...
Click to expand...
Click to collapse
Yeah, I figured I would give it time. They also seemed the most important to me. Question: did you turn iMessage off before you switched devices? I didn't think to do that until a day or 2 after the Moto X was up and running. So I turned iMessage off on the iPhone. It was still connected to WiFi so I assume it could still make the connection to apple's servers to remove that account from iMessage.

dray_jr said:
...the issue is a simple problem the iphones are trying to send you a msg via imessage because there iPhone still thinks you have it. why apple can't find a simple and easy fix is blowing my mind.
Click to expand...
Click to collapse
They have a simple fix - switch back to (or never switch from) iPhone. Just as their lack of a published solution blows your mind, Apple's mind is blown by the fact that anyone who has EVER used an iPhone would EVER choose to use anything else.
With Apple, your once standard SMS becomes needlessly intertwined with iMessage. Stepping into the Apple ecosystem is like stepping into any of the following:
La Brea Tar Pits
Roach Motel
Hotel California
Escape is rare, and often requires outside assistance.

Apple has an official article on this subject; it took me ten seconds to find it via Google...
http://support.apple.com/kb/ts5185

somerandomname1 said:
Yeah, I figured I would give it time. They also seemed the most important to me. Question: did you turn iMessage off before you switched devices? I didn't think to do that until a day or 2 after the Moto X was up and running. So I turned iMessage off on the iPhone. It was still connected to WiFi so I assume it could still make the connection to apple's servers to remove that account from iMessage.
Click to expand...
Click to collapse
No I didn't... And that's what caused it. Had to move the sim card back yo the iPhone, set up Imessage again... Then turn it off. Then finally switched back to the moto x. And then issue resolved almost immediately.
Sent from my XT1060 using Tapatalk

Solutions Etcetera said:
Apple has an official article on this subject; it took me ten seconds to find it via Google...
http://support.apple.com/kb/ts5185
Click to expand...
Click to collapse
and if you would of read the OP you would know he has already done that and still has the problem

dray_jr said:
and if you would of read the OP you would know he has already done that and still has the problem
Click to expand...
Click to collapse
In which case the article suggests contacting Apple support.
I would assume, since it's no secret there can be issues with Apple's cloud services, that there may be times they'd have to give the server a kick from their end.
Also, there is a link at the bottom that accesses another article with more information about unlinking a number from iMessage and FaceTime...
http://support.apple.com/kb/HT5538

Solutions Etcetera said:
Apple has an official article on this subject; it took me ten seconds to find it via Google...
http://support.apple.com/kb/ts5185
Click to expand...
Click to collapse
You can also take 10 seconds to google and see that those instructions are mostly bull**** for a major proportion of people who make the switch. Especially after ios7 which made the "fall back to SMS if iMessage fails to deliver" off by default. People are trying to send via iMessage and when it fails, it doesn't fall back to SMS like it should. People are even continuing to have problems after their iPhone friends/family turn that setting on anyway. It's a really ****ed up system.

You're not supposed to leave iPhone. Can't you take the hint?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
Bet apple goons show up at your door after you've switched....to "persuade " you to return to them. I think they just implemented that procedure.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

somerandomname1 said:
You can also take 10 seconds to google and see that those instructions are mostly bull**** for a major proportion of people who make the switch. Especially after ios7 which made the "fall back to SMS if iMessage fails to deliver" off by default. People are trying to send via iMessage and when it fails, it doesn't fall back to SMS like it should. People are even continuing to have problems after their iPhone friends/family turn that setting on anyway. It's a really ****ed up system.
Click to expand...
Click to collapse
Possibly, but I did not have a problem with it. I simply signed out of all iCloud based accounts before moving to android... with the exception of iCal.

My wife stole my Moto x recently, and finally gave up her just brutal iPhone 4s..(iPhone updated the iPhone 4s into uselessness (slow slow slow)....to sell more 5's I figure)...and yeah, she signed out of imessage first, like I told her..then switched to the Moto x.....and had no issues by the next day.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

I'm glad you guys are getting this working.
I've done every step in this thread and then some and I can't SEND texts to an iPhone, I can receive them with a delay.
Hopefully time will resolve this.

sorry, but the Galaxy S6 + TMobile = Death

i have had nothing but bad luck with my brand new s6 on tmobile.
the main issue:
outgoing sms messages take at least 45 seconds to either get marked as send, or fail. when the fail, they are actually being sent. when they send, they send twice. 30% of the texts i send from my phone and to my phone do not make it to their destination at all.
fixes i have tried:
disabling volte, disabling wifi calling, switching back to stock messaging, factory resetting
tmobile support swore that a new sim card would fix the issue. it did not.
then support guaranteed me that a factory reset would fix the issue. against my better judgment, i reset the device. naturally, this made it worse; when i turn my phone on now i have zero bars of service for at least 5 minutes. literally no service. i am in nyc and normally have 5 bars of LTE.
nobody will recognize that this is actually a problem with tmobile, yet when i google "tmobile can't text over wifi" i get pages and pages of people with the exact same issue over years. reading through those threads there is no solution because tmobile support closes every one of them after 36 hours of inactivity, assuming the problem has been solved. what the **** kind of customer support is this?
texting is my primary form of communication and i am unable to use it. this is unacceptable behavior for any phone, let alone a brand new $700 super-hyped phone. i was on verizon for ten years and it never lost a single text. it's worth noting that there were similar issues with my last phone, an s4.
is nobody else having these issues?

postmastergeneral said:
i have had nothing but bad luck with my brand new s6 on tmobile.
the main issue:
outgoing sms messages take at least 45 seconds to either get marked as send, or fail. when the fail, they are actually being sent. when they send, they send twice. 30% of the texts i send from my phone and to my phone do not make it to their destination at all.
fixes i have tried:
disabling volte, disabling wifi calling, switching back to stock messaging, factory resetting
tmobile support swore that a new sim card would fix the issue. it did not.
then support guaranteed me that a factory reset would fix the issue. against my better judgment, i reset the device. naturally, this made it worse; when i turn my phone on now i have zero bars of service for at least 5 minutes. literally no service. i am in nyc and normally have 5 bars of LTE.
nobody will recognize that this is actually a problem with tmobile, yet when i google "tmobile can't text over wifi" i get pages and pages of people with the exact same issue over years. reading through those threads there is no solution because tmobile support closes every one of them after 36 hours of inactivity, assuming the problem has been solved. what the **** kind of customer support is this?
texting is my primary form of communication and i am unable to use it. this is unacceptable behavior for any phone, let alone a brand new $700 super-hyped phone. i was on verizon for ten years and it never lost a single text. it's worth noting that there were similar issues with my last phone, an s4.
is nobody else having these issues?
Click to expand...
Click to collapse
I have the S6 on T-Mobile. I can text just fine using the stock app. Both SMS and MMS. Play with your APN settings, OR, use textra SMS. There is an option under MMS specifically for sending MMS while using wifi on T-Mobile.
Sent from my SM-G920T using Forum Runner

dc82 said:
I have the S6 on T-Mobile. I can text just fine using the stock app. Both SMS and MMS. Play with your APN settings, OR, use textra SMS. There is an option under MMS specifically for sending MMS while using wifi on T-Mobile.
Sent from my SM-G920T using Forum Runner
Click to expand...
Click to collapse
i do use textra and have tried every combination of their settings. i think my hardware is faulty; tmobile agreed to give me a replacement device. god help me.

postmastergeneral said:
i do use textra and have tried every combination of their settings. i think my hardware is faulty; tmobile agreed to give me a replacement device. god help me.
Click to expand...
Click to collapse
Odd. Well, hope it works out for you.
Sent from my SM-G920T using Forum Runner

When i left Verizon a few years ago for t-mobile, i had had plenty of texts not making it to their destination, so trust me, verizon is not perfect. (they should be though with the amount that they charge)

Try using IP v6 in your settings...
Then try IP v4 in your settings
Then try IP v4 / v6 in your settings and see if that helps with
Native texting App text to yourself to test.
Restart each change of APN.

troysyx said:
When i left Verizon a few years ago for t-mobile, i had had plenty of texts not making it to their destination, so trust me, verizon is not perfect. (they should be though with the amount that they charge)
Click to expand...
Click to collapse
Use to happen to me at least once a month on Verizon. T-Mobile hasn't lost one text for me yet. I keep asking myself why I stayed with big red for so long.

Reflash the original firmware - wipe everything start over. My GS6 works fine for me

robertkoa said:
Try using IP v6 in your settings...
Then try IP v4 in your settings
Then try IP v4 / v6 in your settings and see if that helps with
Native texting App text to yourself to test.
Restart each change of APN.
Click to expand...
Click to collapse
IPv6 is what newer phones are coming preset with as opposed to IPv4 since that is what is correct going forward, per T-Mobile.
Sent from my SM-G920T using Forum Runner

still waiting on my replacement device, but here's an interesting thing i realized today: this problem only occurs in my apartment. BUT i am not connected to wifi (it's turned off and i told android to forget my home network), and i'm on a 9th floor apartment with no other buildings around me. i've never had reception issues in the past here...this doesn't make sense to me at all

I'm using a T-mobile S6 since April 10th. I use Textra also over WiFi with 0 issues. All sms and mms come and go without issue.

philliman said:
I'm using a T-mobile S6 since April 10th. I use Textra also over WiFi with 0 issues. All sms and mms come and go without issue.
Click to expand...
Click to collapse
Same, guess we're fortunate lol. I haven't seen or heard any text related issue specific to the S6, I know MMS is sometimes wonky with T-Mobile while connected to WiFi
Sent from my SM-G920T using Forum Runner

"READ Tmobile acknowledge Native message app is corrupt. Don't update Says TMobile

"READ Tmobile acknowledge Native message app is corrupt. Don't update Says TMobile
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.

Um check your wifi calling settings
Sent from my [device_name] using XDA-Developers Legacy app

androidddaaron said:
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Click to expand...
Click to collapse
seemles said:
Um check your wifi calling settings
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What about it ? Wether on wifi calling or not this is a message issue acknowledged and very pronounced In many ways . It's simple to see with a few trial and error tests regardless of wifi
Or LTE Data
Seeing all your messages show up on TMO digits comparing them to messages you've got or never got .....putting a SIM card in a different phone and seeing multiple messages pop up that have still been trying to push through that are tied to specific time line conversations. TMobile literally already acknowledges this it's just nobody is realizing it because they're not expecting messages that they're actually missing from people.
Feel free to test it if you would like have multiple people text you wait for it to come through not saying it affects everybody T-Mobile did tell me that they already have a ticket out for it and it's software related to this particular phone.
On top of the SMS of all things is one of the most critical uses of a phone .
Just trying to shed light on a rising issue that most would never be aware of .

Because all Android phones ship with settings set to wifi preferred wich leads to dropped calls and unsent messages after setting up a home wifi. And if you have no sim installed your obviously using wifi calling wich is most definitely not as dependable as volte.
Sent from my [device_name] using XDA-Developers Legacy app

seemles said:
Because all Android phones ship with settings set to wifi preferred wich leads to dropped calls and unsent messages after setting up a home wifi. And if you have no sim installed your obviously using wifi calling wich is most definitely not as dependable as volte.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll look into that....but if your not on wifi calling "connected" to a wifi network you would still be using volte right ? This is happening to people conversating anywhere Mobily in a vehicle not on wifi. Messages for instance with my brother whereas I never got a reply in which I would have came through after I put my SIM in my s8.
People are seeing ungotten messages in TMobile digits.
I don't really care i was just looking out for the community here with a potential problem hindering, and T-Mobile tech support made acknowledgement about it . I highly doubt a community across United States all at once is screwing up by keeping WiFi preferred on.
You're only going to be using WiFi calling if you're connected to an actual at work under that settings menu otherwise you would be using cellular by default just like it says to choose below that

You're only going to use Wifi calling if you're connected to a WiFi network otherwise you're going to use cellular default which is the same as being on cellular by default correct me if I'm wrong

Can you post a link to the discussion? I can't find anything after searching for a while.
Sent from my [device_name] using XDA-Developers Legacy app

Z2 force sms MMS broken discussion link

http://support.t-mobile.com/thread/143284

Multiple replied posts from z2 users
How this has not made it to xda is beyond me but it is real situation

It's really not a good feeling to really not know all the messages you should be getting that you're not especially the ones that you're not expecting the scenario is playing out just like it shows in these support forums and with myself.
It's like not "Some messages are blocked in a limbo status never reaching the target device
Like myself you could stick a SIM card potentially in another phone and see stuff that pops up that was related to conversations long ago that you never got replied too.
I haven't had much of a problem with T-Mobile to T-Mobile network SMS but many other people I know that use other carriers I never got replied to until I stuck my SIM card into a different phone of mine.
It's a janky situation and if TMobile is already acknowledge this and told to replace phones one time then evidently the issue has gotten out to the people that needs to I just don't know how nobody here on XDA knows about this .
I have tried multiple text apps and nothing seems to be different I even thought about editing access point but usually that only solves MMS problems

This issue was already addressed with a fix to boot by xda. I had the issue my self. With no issues after I updated to oreo.
https://forum.xda-developers.com/z2-force/how-to/t-mobile-how-to-3rd-party-sms-apps-root-t3661703

seemles said:
This issue was already addressed with a fix to boot by xda. I had the issue my self. With no issues after I updated to oreo.
https://forum.xda-developers.com/z2-force/how-to/t-mobile-how-to-3rd-party-sms-apps-root-t3661703
Click to expand...
Click to collapse
I tried this method and it did not work, after the Oreo update I tried again but kept having issues. Decided to Force stop the CPS app and install the Google Carrier services app and this worked. Don't remember where I heard/read about Google carrier services. BTW using Googles messages app now and seem to be receiving all messages.

I discovered this a few weeks ago then installed google messages and everything works now

Missing messages FIXED
androidddaaron said:
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Click to expand...
Click to collapse
I have already experienced this issue. It's NOT related to wifi calling at all. I tested it with wifi calling on and with it off, same results.
What worked for me to FIX it was to clear storage and clear cache on the "native" app. You won't lose messages already on the device but you should backup with Carbonite sms first to be safe. Once I wiped storage and cache for the app I started receiving messages again normally.
I found out I was missing messages by installing digits. It's all working now but I'm keeping digits temporarily just to be safe.

texasaggie1 said:
I have already experienced this issue. It's NOT related to wifi calling at all. I tested it with wifi calling on and with it off, same results.
What worked for me to FIX it was to clear storage and clear cache on the "native" app. You won't lose messages already on the device but you should backup with Carbonite sms first to be safe. Once I wiped storage and cache for the app I started receiving messages again normally.
I found out I was missing messages by installing digits. It's all working now but I'm keeping digits temporarily just to be safe.
Click to expand...
Click to collapse
Wait so your saying this is a fix wether on Oreo or nougat and digits is the whole reason why .
And the native message app just need to clear cache and data in settings app
Sent from my [device_name] using XDA-Developers Legacy app

I deleted and deactivated digits completely. After I had it completely removed from my account, I rebooted and changed to Android Messages and everything has been fine since October.

Are the issues with this phone sorted yet? I was looking to purchase the T-Mobile variant of this phone but have read about issues such as not receiving texts (huge problem), VoLTE not working with Galaxy S7s, and WiFi connection issues. If they are not fixed, can they at least be avoided by refusing the Oreo update? I would like to avoid rooting my phone just to fix a defect and would only consider using a 3rd party messaging app if it fixed the problem without introducing other problems.
I have my phone choices currently narrow down to the Z2 Force, LG G6, and Galaxy S7 (all are currently in the $400 range). I was leaning towards the Z2 since it's the most powerful, but the issues I'm reading about seem quite severe.

After a little more research I see 2 patches were released for the Z2F after the Android 8.0 update.
https://support.t-mobile.com/docs/DOC-35970
I found a Reddit thread (https://www.reddit.com/r/Moto_Z/comments/7zxcpo/tmobile_moto_z2_force_ocx271_update/) where some people mentioned it fixed the SMS notification and Galaxy S7 VoLTE issues. I didn't see anything anything discussing the Bluetooth/WiFi issues or more importanly, the SMS not being received issue (the topic of this thread). Can anyone comment if those were fixed?

cyborgLIS said:
Are the issues with this phone sorted yet? I was looking to purchase the T-Mobile variant of this phone but have read about issues such as not receiving texts (huge problem), VoLTE not working with Galaxy S7s, and WiFi connection issues. If they are not fixed, can they at least be avoided by refusing the Oreo update? I would like to avoid rooting my phone just to fix a defect and would only consider using a 3rd party messaging app if it fixed the problem without introducing other problems.
I have my phone choices currently narrow down to the Z2 Force, LG G6, and Galaxy S7 (all are currently in the $400 range). I was leaning towards the Z2 since it's the most powerful, but the issues I'm reading about seem quite severe.
Click to expand...
Click to collapse
The latest 2 Oreo updates have fixed those problems, and they didn't affect everyone.
Sent from my Moto Z (2) using XDA Labs

Help: Weird SMS Problem

Need help diagnosing and solving a bizarre problem: S10 doesn't receive texts from a specific sender, except after restarting, retroactively receives all texts sent by that sender. Supernatural powers might be involved, given the sender's phone is mine, and the fickle S10 is my wife's.
I'm including a lot of info below, b/c this seems to be a tough problem to diagnose, so I'm erring on the side of completeness.
Specs: My phone is an LG V35, rooted with Magisk, Android 9. Her S10 is not rooted, running Android 9. Her phone is logged in to the same Google account I use on the Play Store, so that she can use any of my paid apps without paying again. (This has never caused any SMS problems in the past, just annoyances like her getting my reminders, which I then turned off on her phone.)
The problem started on 10/26/22 (about three weeks ago). I know this b/c I sent her a long text that day, which her phone received immediately, followed by another text that same day, which she didn't receive until eight days later on 11/3/22. There were several other texts I sent btw 10/26 and 11/2 that she didn't receive until 11/3. However, we did not catch this problem until yesterday (11/17), when she discovered that I had not, in fact, been ghosting her, but that her phone was not getting my texts. We found this out b/c some other app on her phone wasn't behaving normally, so I restarted her phone -- and BAM, all my unreceived texts suddenly arrived on her phone. Since then, I've tried texting her phone, and it receives nothing from me until a restart, and then her phone receives all my texts retroactively.
As far as we can tell, neither of our phones has any problem with SMS communications with anyone else's phone (except some iPhones -- don't get me started). Other people receive my texts normally, and her phone receives other people's texts normally.
I tried texting her from two different Google Voice accounts I have (both different from the Google account our phones share), and her phone received both G-Voice texts immediately.
I tried changing my SMS app (from Pulse to Textra). No effect (her S10 didn't receive texts until restarting). I tried changing her SMS app. No effect. I did a Samsung software update (thru Settings) on her phone. No effect.
I have an old S10e, my last phone before I switched to the LG. As an experiment, I popped her phone's SIM card into my old S10e. I installed an SMS app neither of us has ever used before, Handcent Next, on the S10e. Without doing anything else (i.e. w/o transferring her S10 data or settings to the S10e), I texted her number from my LG. The text arrived immediately in Handcent. I thought, Eureka!
I promptly factory-reset my S10e, and used Samsung's Smart Switch to transfer "Everything" from her S10 to the S10e. After all her data, apps, & settings were transferred to the S10e, I texted her number, and… NOTHING. The S10e did not receive my text, until I restarted it.
So, my question to all Android sleuths out there is: What the hell?

Excellent detail and info.
My initial guess may be because you're sharing the Google account. Yes, I know you said this didn't cause problems before, but now with Google Messages (I know you're not using that, but still) doing lots of RCS and background stuff, I imagine there may be some behind-the-scenes interaction that is causing problems. I'm not saying this is a fault of RCS or anything like that, but I think the sharing may be the issue?
I would suggest trying to create a new Google account, and keeping the phones on separate accounts... it's a free and easy test, I figure... and you seem quite skilled in more difficult things, so this should be easy enough?
Also note, some apps support family sharing, so if you setup a "family" between the two accounts, you may get the purchased apps on both accounts without too much issue. My wife and I do this and it has worked pretty well for our apps. (FWIW, we both have S10+ and use GMessages on separate google accounts, family shared, and don't have any issues with texts, etc.)

schwinn8: I liked your idea & reasoning, and I implemented it -- new personal Gmail account for her, added to my G-family. Restarted her phone, and sent her a text which did not arrive. (I texted her from a Google Voice account, and that SMS arrived instantly.) I then restarted her phone again, and, for the first time, the initial text still did not arrive. That's new, at least.
What setting could possibly delay a text from coming in?

Well, that's not the direction I wanted things to go either!
Not sure what else could delay texts from coming in... not aware of any delay mechanisms in most cases.
Are both on Wifi during this process? Is the LG running a ROM with working VOWIFI? Yes, I am grasping at straws...

Well, recalling my old Windows 3.x experiences, I factory-reset the S10e (my old phone), and installed all of my wife's apps and recreated all her settings on it from scratch -- i.e. no transferring apps or settings from her phone. A labor-intensive solution, to be sure, but it is working so far. The S10e receives my texts normally.