slow texting?

[mwilliams1985]

OK, so I just got my nexus 6 on the 15th. Sprint network in Indiana. From about 20 minutes after unboxkmg until I swapped it out earlier today I noticed that there is some serious lag when sending texts. It will attempt to send for 45sec and send or it will fail for 5 minutes before it sends and my recipients will receive umpteen copies of the same message.

I went and returned it today and got another nexus 6 since they deemed it a hardware issue. This new phone, still does the same thing but about 1/3 as often. Is this a common issue? Help me fix it.

 

[mwilliams1985]

After about 3 hours of digging I found a post on XDA, Apparently it's a Sprint issue and the only workaround is to stay in 3g >.< Now that. that is solved...

How about some cool mods

 

[Greg C]

OK, so I just got my nexus 6 on the 15th. Sprint network in Indiana. From about 20 minutes after unboxkmg until I swapped it out earlier today I noticed that there is some serious lag when sending texts. It will attempt to send for 45sec and send or it will fail for 5 minutes before it sends and my recipients will receive umpteen copies of the same message.

I went and returned it today and got another nexus 6 since they deemed it a hardware issue. This new phone, still does the same thing but about 1/3 as often. Is this a common issue? Help me fix it.

This happens to me as well...sometimes. Yes you can leave it in 3G which defeats any reason to have an LTE phone, deal with it or use Google Hangouts. It is definately NOT your phone. It is a Sprint issue and Sprint is supposedly aware of this issue.

 

[TraderGary]

In the Atlanta area texting works for me on Sprint with no problems. It will be interesting to see what happens when I travel to other areas.

 

[JoePa2624]

Haven't seen that issue, but I have been told by friends that there is a noticeable delay in them receiving my texts.

Sent from my Nexus 6 using Tapatalk

 

[cozzy123]

Yeah sprint has been having issues with this phone that the other carriers haven't. I think the next big patch should address this.

Posted via the Android Central App