Database Develop

[Q] Text Messages Get Split Up - Nexus 6 on Verizon Wireless

So I've been having this problem for a few weeks where my texts get split up if they are few sentences or longer. It doesn't happen with everyone either, that I know of. Not only do my texts get split up (with the few people that I know this problem happens with), but the texts they send me get split, too. I've tried different texting applications to see if that fixes the problem but it still occurs. Anyone know why this happens or how to fix it? I bought my Nexus 6 from the Google Play Store and use it on Verizon. It's rooted, unlocked, and running the latest 5.1 build of Chroma and lean kernel. Thank you.:fingers-crossed:

I'm on Verizon as well, with a Nexus 6 and that's just a carrier limitation (to my knowledge)
They have a character limit, and so as a way to keep everything in order when being sent, they split it up into multiple messages and they just seem "split" but they're just being sent as separate texts and made to look like a consistent one
It happens to my phone, and I bought it directly from Verizon
Have you tried Textra? I know there's some settings in Textra SMS that allows you to fiddle with being sent/received as a single message if the carrier allows it and what not :highfive:

Using Verizon Messages is the best way to go if you got a N6 on VZW.

Its always going to be split up when you use CDMA, because of the 160 character limit. If your on GSM or using LTE on CDMA the messages should not be split.
Sent from my Nexus 5 using XDA Free mobile app
Sent from my Nexus 5 using XDA Free mobile app

Sms sending problem when using on Verizon LRA partner carrier

My carrier refuses to help me with this issue since it's not a phone that they carry.
First some background info. I have a problem using the Nexus 6 on my carrier, "Bluegrass Cellular" which is a regional cdma/lte carrier partnered with Verizon Wireless under their "LRA" (LTE in rural America) program. This issue I can guarantee happens with every user using the device on other carriers under the same agreement. Friend who uses a n6 on another partnered carrier has the same problem. The Issue doesn't seem to be ROM dependant either. If more carrier specific info is needed I can provide it.
Before a wonky work around mentioned next, this is the issue. Problem is if connected to LTE, everything works properly, calls in and out, mms in and out, and receiving sms as normal. But you cannot send sms (pre 14r radio, after 14r radio sends but delays). If you are connected to LTE, when you send a sms it will fail with the message message, "cant send message (insert carrier name) error -1. But you could downgrade network to 3g and you can send fine. But back to LTE sms lags.
Only fix/work around is to flash any m preview radio. Which leads me to think it could possibly be radio related. With those, sms sends, but it takes 40 seconds to send per text. Does anyone have any ideas? 14r+ radio with delay is better than nothing, but it's still rather frustrating.
Outgoing sms on LTE/cdma: average 40 second delay to send message, with higher than normal send failure rate.
Outgoing sms with LTE disabled: sms sends within 5 seconds.
Still when on LTE there is no delay on receiving texts. Only sending.
I Tried sms over ims on/off and a few other pokes and prods, no different. Can provide logcat or anything else if desired. Just trying to get an idea what's going on.
Tl;Dr
APNS are set properly, mms in/out works fine, calls in/out work fine, receiving sms is fine, sending sms on cdma 1x/3g is fine.. Just sending sms on LTE has a roughly 40 second send time with a abnormal send failure rate.
Sorry for the long post I am just trying to cover all the bases for which could be applicable to finding a solution. Thanks in advance for any inputs!
Sent from my Nexus 6 using XDA Premium 4 mobile app

Bump still looking for any suggestions at all
Sent from my Nexus 6 using XDA Premium 4 mobile app

Bump, still looking for any input to the situation
Sent from my Nexus 6 using XDA Premium 4 mobile app

Same issue
I just switched to Bluegrass Cellular today and brought my Nexus 6 aboard and am experiencing the exact same issue. I am running Android 5.1.1 with baseband: MDM9625_10446.01.02.101R and cannot send SMS outbound at all. I can receive SMS, calls, and data all fine, but no outbound texts will go through at all. I will follow the advice already in this thread and update to Android M preview to see if the updated baseband will "sorta" fix the issue so I can at least send outbound, even if it is delayed. I am willing to provide logs if anyone can look into this issue and see a possible resolution.

M preview radio will sorta fix it and make it so it will send on LTE after a delay of like 40 seconds. If you are on 1x/3g sms will work fine.
Sent from my Nexus 6 using XDA Premium 4 mobile app

stlpengineer said:
I just switched to Bluegrass Cellular today and brought my Nexus 6 aboard and am experiencing the exact same issue. I am running Android 5.1.1 with baseband: MDM9625_10446.01.02.101R and cannot send SMS outbound at all. I can receive SMS, calls, and data all fine, but no outbound texts will go through at all. I will follow the advice already in this thread and update to Android M preview to see if the updated baseband will "sorta" fix the issue so I can at least send outbound, even if it is delayed. I am willing to provide logs if anyone can look into this issue and see a possible resolution.
Click to expand...
Click to collapse
No need to flash the entire M. Just flash the radio unless you want more that don't work.

I just wish we could figure out why it delays and how to resolve it. Any radio but m preview sms will just fail after so long. M preview radio will delay but eventually send after average 45 seconds. It's just so odd to me.
Calls in out fine
Mms in out fine
Sms in fine
Sms out 1x/3g fine
Sms out LTE no m radio no send
Sms out LTE m radio 40 seconds to send but will send.
Interestingly enough if you go into network settings and set to LTE only rather than LTE cdma sms will not send. So I can't tell if it's radio or it not wanting to use the ims features I'm really lost at this point
Sent from my Nexus 6 using XDA Premium 4 mobile app

prdog1 said:
No need to flash the entire M. Just flash the radio unless you want more that don't work.
Click to expand...
Click to collapse
Can you please provide me a link to a tutorial or explain how I can flash the baseband on my current version of Android? I've never done that before, but would love to learn how to.

stlpengineer said:
Can you please provide me a link to a tutorial or explain how I can flash the baseband on my current version of Android? I've never done that before, but would love to learn how to.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 all you need to know is here
Sent from my Nexus 6 using XDA Premium 4 mobile app

Anybody at all????? I also suffer from this annoyance and along with evilryry have tried multiple things to no avail...
Sent from my Nexus 6 using XDA Premium 4 mobile app

If it is delayed it is carrier. Nothing you do to device outside APN and PRL will fix in my opinion. Carrier/tower problem.

Progress
Ok, I flashed the 24R Android M Preview 3 baseband to my phone last night and texts were still failing altogether this morning when on LTE. I had alot of text messages on my phone (over 21,000 total according to the SMS Backup and Restore app). I deleted alot of old text messages on my phone and my texts are now going through without delay. However...MMS is still not working, but I suspect that has something to do with me not having a Bluegrass APN setup on my phone (if anyone has BG's APN settings, I would be happy if you could provide me a link to them, because I do not see them on their website).

stlpengineer said:
Ok, I flashed the 24R Android M Preview 3 baseband to my phone last night and texts were still failing altogether this morning when on LTE. I had alot of text messages on my phone (over 21,000 total according to the SMS Backup and Restore app). I deleted alot of old text messages on my phone and my texts are now going through without delay. However...MMS is still not working, but I suspect that has something to do with me not having a Bluegrass APN setup on my phone (if anyone has BG's APN settings, I would be happy if you could provide me a link to them, because I do not see them on their website).
Click to expand...
Click to collapse
If you want to use mms on a non bluegrass phone you are limited to one specific texting app "8sms" with mms settings as shown in picture. Make sure you don't forget the last setting X-MDN:##LINE1#. Mainly you need the mmsc mms on wifi (yes bluegrass supports it) and the extra http header above.
Sent from my Nexus 6 using XDA Premium 4 mobile app

prdog1 said:
If it is delayed it is carrier. Nothing you do to device outside APN and PRL will fix in my opinion. Carrier/tower problem.
Click to expand...
Click to collapse
Why would it work fine in other phones across multiple carriers in this instance? I've tested several different phones also and I've noticed this happens only in Motorola phones not made specifically for Verizon lra carriers. I've used a Verizon galaxy s4 and everything worked great. It feels like somewhere in the radio software or wherever is not letting the ims feature work.
Sent from my Nexus 6 using XDA Premium 4 mobile app

Still Occuring on Android 6.0
So here's an update. I had been running Android 5.1.1 on my Nexus 6 for months with the 24R baseband and had zero problems with SMS being delayed. Everything worked like normal. I updated to Android 6.0 which installed the 27R baseband and the delayed SMS issue is back. I tried reverting the baseband to 24R and the delayed SMS issue was still present. Any ideas on how to fix this? I will be happy to provide logs or any other diagnostic information.

Odd....
Quite frankly, I'm still baffled by this issue. I bought the Nexus 6p and am still with Bluegrass Cellular. Once I popped in my SIM and had them change my IMEI number, I thought that the delayed SMS issue would be a thing of the past. The issue is STILL PRESENT on the Nexus 6p which is manufacturered by an entirely different company than the 6 was (Huawei). I don't suspect it is the radio any longer, as this has happened to me on multiple phones.

I've been toying with different remedies and strategies for months. I've started thinking it's software related and needs to be addressed to Google, but unfortunately I highly doubt they'd care.

stlpengineer said:
Quite frankly, I'm still baffled by this issue. I bought the Nexus 6p and am still with Bluegrass Cellular. Once I popped in my SIM and had them change my IMEI number, I thought that the delayed SMS issue would be a thing of the past. The issue is STILL PRESENT on the Nexus 6p which is manufacturered by an entirely different company than the 6 was (Huawei). I don't suspect it is the radio any longer, as this has happened to me on multiple phones.
Click to expand...
Click to collapse
Check your pm

evilryry said:
If you want to use mms on a non bluegrass phone you are limited to one specific texting app "8sms" with mms settings as shown in picture. Make sure you don't forget the last setting X-MDN:##LINE1#. Mainly you need the mmsc mms on wifi (yes bluegrass supports it) and the extra http header above.
Sent from my Nexus 6 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know you had a thread going for this. Do you still need 8sms with those headers added? I could probably change your http header elsewhere and get it working with all message apps.
For the SMS delayed issue, I have found a fix with the help of @evilryry and have made a flashable for it. Just waiting for a little more confirmation so I can be sure to give accurate instructions.

daheazle said:
Didn't know you had a thread going for this. Do you still need 8sms with those headers added? I could probably change your http header elsewhere and get it working with all message apps.
For the SMS delayed issue, I have found a fix with the help of @evilryry and have made a flashable for it. Just waiting for a little more confirmation so I can be sure to give accurate instructions.
Click to expand...
Click to collapse
I can comment that I've been using Google messenger for somebtime now and it's been fully functional. Just have to restore apns with apn backup and restore that I got from a rooted thumb cellular phone and then add mms line to apn type under vzwinternet and so far so good.

Not Receiving Phone Calls

Hi guys. Been having issues receiving calls lately. The phone doesn't ring and the caller says it goes straight to voicemail. I read through some support forums on Verizon's website and it looked like other people were having the same issue. Verizon suggested making sure Advanced Calling was on. However, it DOES work for me when Advanced Calling is OFF. Has anyone experienced this? It's pretty frustrating. I'm on Computerfreek's 1.5 build. Thanks in advance.
Sent from my XT1254 using XDA Free mobile app

I too have been having this issue; it does not occur consistently but every few days I am told by people trying to contact me that their calls are going straight to voicemail. I do have Advanced Calling on but I noticed the last time it happened (last Friday afternoon 10-23 at my office where I always have service) that when I made a phone call, I could not access data / internet simultaneously also. After a reboot, everything was back to normal though; I too am on Computerfreek's 1.5B Pon-3 Base w. IOS Emoji build.

met the same issue in China, everyday received several SMS says somebody called you but not answered...

Are either of you using Google voice as your voicemail by any chance?
Sent from my XT1254 using XDA Free mobile app

papstar said:
Are either of you using Google voice as your voicemail by any chance?
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
I use Google Voice strictly for voicemail (no calling), but I do not have the app installed on my phone. I just receive vm notifications via gmail.

I ask because after this issue I went back to using Verizon voicemail and everything is working as expected.
Sent from my XT1254 using XDA Free mobile app

papstar said:
I ask because after this issue I went back to using Verizon voicemail and everything is working as expected.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I have used google voice since its inception on other phones but have been having issues with it since advanced calling was added to this phone; at first with kitkat, I would get calls and see if I missed calls, but if someone left me a voicemail, I would not receive it. On rooted lollipop roms, I have tried using GV with and without the app installed but it never seems to work perfectly. On a positive note, I haven't noticed the issue occurring since the last time I posted about it but I will most likely make the switch to vzw if it does.

Receiving SMS issues

Has anyone had issues with receiving SMS messages? Happens randomly where I won't receive messages from different people etc. I came from a nexus s6 so it isn't the iMessage issue. I've tried searching for reasons or solutions, factory reset the phone, called the carrier to see if settings were wrong. But no one has an answer.
Any help or if anyone experiencing the same thing would be helpful.

I have issues with getting the notifications for text messaging but only for TMobile lines. I still get the message but the phone refuses to light up, make any sound or vibrate when they come in.
Again it's only with T-Mobile numbers, all other texts work like normal
Sent from my SM-N950U1 using XDA Premium HD app

"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