DTMF tones not being registered. - Nexus 6 Q&A, Help & Troubleshooting

So I had to call a couple different automated systems today, first PayPal then my bank
Both times I had to be redirected to an agent because it said the information I entered is not correct. I changed the length of the tones to long and I know some presses are being entered since I could navigate the menus, but it seemed when I got to multiple presses in a row (like account numbers and passwords) it wouldn't work. I even tested calling my voicemail. It told me my password was wrong, then I called from a different phone and got in just fine. I thought maybe I was going too fast so I tried it slow and still no luck. Is there something else I need to change?

I am having the same problem. Started on 5.1.

Do you have screen protector installed? Some people claim that 5.1 made proximity sensor more sensitive. Removing screen protector ( or cutting around proximity sensor) fixed the problem.

darek65 said:
Do you have screen protector installed? Some people claim that 5.1 made proximity sensor more sensitive. Removing screen protector ( or cutting around proximity sensor) fixed the problem.
Click to expand...
Click to collapse
Not sure about OP, but in my case the numbers I'm pressing show up as being pressed on the screen, but they don't register with the call itself. When I try to call my voicemail I have to push a number several times sometimes to get it to actually register. I may see "3333333", but only the last one actually registers.

I don't use a screen protector. Also like the other guy said, the button is being pressed, I turned on dialpad sounds to be sure.

Same problem on 5.1.
Sent from my Nexus 6 using Tapatalk

Are both of you that are having the same problem on stock? Figured I would submit a bug report if no one has a solution, just want to make sure someone has tested it on stock first.

I had the problem on the stock T-Mobile OTA. I was rooted and unlocked, but otherwise stock.

Stock rooted 5.1M
Sent from my Nexus 6

Same issue. Stock ROM. Franco kernel.

Stock 5.1 Franco Kernel. Same issue. Anyone getting anywhere with this. I've tried changing the DTMF from normal to long, and tried touch sounds on and off, which seems to be the only "fixes" mentioned in various places.

Eetabeetay said:
So I had to call a couple different automated systems today, first PayPal then my bank
Both times I had to be redirected to an agent because it said the information I entered is not correct. I changed the length of the tones to long and I know some presses are being entered since I could navigate the menus, but it seemed when I got to multiple presses in a row (like account numbers and passwords) it wouldn't work. I even tested calling my voicemail. It told me my password was wrong, then I called from a different phone and got in just fine. I thought maybe I was going too fast so I tried it slow and still no luck. Is there something else I need to change?
Click to expand...
Click to collapse
I had this same problem with another phone. I had to call my carrier to fix it because it was something on their end. Is everyone having this problem on the same carrier?

devilsmack said:
I had this same problem with another phone. I had to call my carrier to fix it because it was something on their end. Is everyone having this problem on the same carrier?
Click to expand...
Click to collapse
Verizon Here

Fixed issue by turning off VoLTE. So that sucks. Turned it back on after I was done activating the card I was trying to activate.

Does switching to long tones do anything? I've had this problem since 5.1 and am on Verizon with VoLTE.

Same problem here. Have had it across multiple versions of Chroma ROM (includes Franco kernel). VoLTE on means no DTMF, VoLTE off makes DTMF work perfect. Have seen references to similar problems on other phones and other networks.

New M radio (.16R) fixes DTMF recognition with VoLTE on. I'm on Tmobile if relevant. You can find this and all of the other radios here.

OTA update TO 5.1.1 solved this problem for me. Before the update it was almost impossible to enter my pass code in T-Mo voicemail.

stevemw said:
OTA update TO 5.1.1 solved this problem for me. Before the update it was almost impossible to enter my pass code in T-Mo voicemail.
Click to expand...
Click to collapse
LMY47Z fixes this on Verizon as well. I was having to wait a full second between numbers (which was a pita since I dial into a lot of conference calls every day)

swamp2 said:
New M radio (.16R) fixes DTMF recognition with VoLTE on. I'm on Tmobile if relevant. You can find this and all of the other radios here.
Click to expand...
Click to collapse
Unfortunately the new M (preview) radio fixed this but also does not permit conference calls. The 5.1.1 Tmo OTA radio maintains this fix but also permits conference calls. Specifically, this one:
LYZ48E (5.1.1 T-Mobile - Extracted from OTA - 05/23/2015)
MDM9625_104649.09.05.14R

Related

Phone rings twice and sends to voicemail.

The caller on the other end says it rings all the way through (5 rings and then to voicemail).
It has done this with several ROM's, the stock HTC cupcake, to JF 1.5, JACHero, and now I am on cyanogen's 3.62 ROM. The radio is 62.50S.20.17H_2.22.19.26I.
The phone will do this even with a clean wipe. No apps.
Any help would be greatly appreciated.
Thanks in advance.
-RotorDemon- said:
The caller on the other end says it rings all the way through (5 rings and then to voicemail).
It has done this with several ROM's, the stock HTC cupcake, to JF 1.5, JACHero, and now I am on cyanogen's 3.62 ROM. The radio is 62.50S.20.17H_2.22.19.26I.
The phone will do this even with a clean wipe. No apps.
Any help would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Check your call forwarding settings. Sometimes, they like to play with themselves and set it as "forward all calls to voicemail". These settings won't show it, because the changes are on the T-Mobile server, not your phone. Only having 2 rings sounds like it connects to the network and then gets pushed away from it, so most likely it's not a problem with your phone.
If you happen to have an old T-Mobile phone laying around, trying switching SIM cards and see if anything changes.
Figured it out. Ran a GSM code
*61*1[vm access number]*11*n#
n= seconds before forwarding. Set it to 25 and it rings all the way through.
Thanks for the info lukekirstein
Double post.
-RotorDemon- said:
Figured it out. Ran a GSM code
*61*1[vm access number]*11*n#
n= seconds before forwarding. Set it to 25 and it rings all the way through.
Thanks for the info lukekirstein
Click to expand...
Click to collapse
Where would you run this code at? I want to be able to set my ring time longer so that it takes longer for it to forward to voicemail.
lukekirstein said:
Where would you run this code at? I want to be able to set my ring time longer so that it takes longer for it to forward to voicemail.
Click to expand...
Click to collapse
Open up your dialer and dial it like you would a phone number.
In my case I entered *61*18056377243*11*25# and dial. Runs the code and then in a few seconds it is done. But check to see if your voicemail number is different than mine.
-RotorDemon- said:
Open up your dialer and dial it like you would a phone number.
In my case I entered *61*18056377243*11*25# and dial. Runs the code and then in a few seconds it is done. But check to see if your voicemail number is different than mine.
Click to expand...
Click to collapse
Cool, was able to set the Voicemail to connect in 35 seconds. Thanks!
I get the error:
Call forwarding.
Connection problem or invalid MMI code.
I've carefully entered the code three times, always get the same reply.
I checked my voicemail number, and it's correct.
Any ideas?
blueheeler said:
I get the error:
Call forwarding.
Connection problem or invalid MMI code.
I've carefully entered the code three times, always get the same reply.
I checked my voicemail number, and it's correct.
Any ideas?
Click to expand...
Click to collapse
What are you trying to do?
Trying to get my phone to wait 20-30 seconds before going to voicemail.
I get, maybe, 2 rings before people are transferred. If my finger isn't already on the button, chances are I can't answer the phone.
These are the codes I tried (as per the instructions above):
*61*18056377243*11*20# (for 20 secs) -and-
*61*18056377243*11*25# (not to go to voicemail)
18056377243 is my voicemail number.
Neither worked.
blueheeler said:
Trying to get my phone to wait 20-30 seconds before going to voicemail.
I get, maybe, 2 rings before people are transferred. If my finger isn't already on the button, chances are I can't answer the phone.
These are the codes I tried (as per the instructions above):
*61*18056377243*11*20# (for 20 secs) -and-
*61*18056377243*11*25# (not to go to voicemail)
18056377243 is my voicemail number.
Neither worked.
Click to expand...
Click to collapse
Are you on a flex pay account? Also, you should only need one 1 MMS number, because that's the immediate point it re-routes to voicemail.
re Flexpay, to be honest, I'm not 100% sure. The wife set all of this up before we were married and we've just continued it. I seem to recall a mention of something like that, but I could very well be wrong.
I'm assuming that this option wouldn't be available to FP customers. Would 611 be able to make a change to fix it? The 2 ring thing is seriously causing problems on this end.
TIA
blueheeler said:
re Flexpay, to be honest, I'm not 100% sure. The wife set all of this up before we were married and we've just continued it. I seem to recall a mention of something like that, but I could very well be wrong.
I'm assuming that this option wouldn't be available to FP customers. Would 611 be able to make a change to fix it? The 2 ring thing is seriously causing problems on this end.
TIA
Click to expand...
Click to collapse
Call forwarding is not available to flex pay customers and thus, custom MMS coding will not work. If this is the case, you should contact T-Mobile (either way, probably a good idea) and talk to them to see what might be causing the problem.
What ROM are you using? Some of the slower ROMS can create dialer lag.
Asked my wife. It is Flexpay. So that solves that.
Thank you so much for your reply.
That got us going in the right connection.
I am using Cyan's rom right now. But this was the way it was ever since we got into any 'Cupcake" versions (OTA or modded). My thoughts are the radio or a tower issue, but that's an uneducated guess. I rarely get phone calls anytime except when I'm home, so it's hard to pinpoint. So I followed your suggestion and tried to call 611 a short while ago. Got through to CS who walked me through some stuff (their basic scripted thing, all of which I've already tried), and it didn't work. So they tried to send me to tech support, and I guess it was either to late or they couldn't connect for whatever reason, so I have to call back in the morning.
Thanks again for heading me in the right direction.
blueheeler said:
Asked my wife. It is Flexpay. So that solves that.
Thank you so much for your reply.
That got us going in the right connection.
I am using Cyan's rom right now. But this was the way it was ever since we got into any 'Cupcake" versions (OTA or modded). My thoughts are the radio or a tower issue, but that's an uneducated guess. I rarely get phone calls anytime except when I'm home, so it's hard to pinpoint. So I followed your suggestion and tried to call 611 a short while ago. Got through to CS who walked me through some stuff (their basic scripted thing, all of which I've already tried), and it didn't work. So they tried to send me to tech support, and I guess it was either to late or they couldn't connect for whatever reason, so I have to call back in the morning.
Thanks again for heading me in the right direction.
Click to expand...
Click to collapse
No problem, glad I could help you out :]. Let me know how that goes!

"Call ended" right after dialing

First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?

Calling via Touchless Control

I've experienced a couple of problems recently and I'm not sure if it's a bug or something they changed with the last update. I'm on 4.4.2 with Sprint.
Previously, when I tried to call a business (i.e. "Call Pizza Hut"), it would find it via Google Now and make the call. Recently, I've noticed that if the business is not listed in my contacts, it will try to call one of my contacts.
Also, if there's a contact with more than one phone number, it used to give you a prompt to confirm whichever number you're trying to call. Now, it just calls the default number.
Has anyone else noticed this and do you know of a fix?
clankfu said:
I've experienced a couple of problems recently and I'm not sure if it's a bug or something they changed with the last update. I'm on 4.4.2 with Sprint.
Previously, when I tried to call a business (i.e. "Call Pizza Hut"), it would find it via Google Now and make the call. Recently, I've noticed that if the business is not listed in my contacts, it will try to call one of my contacts.
Also, if there's a contact with more than one phone number, it used to give you a prompt to confirm whichever number you're trying to call. Now, it just calls the default number.
Has anyone else noticed this and do you know of a fix?
Click to expand...
Click to collapse
Unfortunately, I have the same exact issue on Republic Wireless (Sprint MVNO) 4.4.2 and haven't found a solution....
Strangely, the issue seems to come and go. Additionally, the voice recognition is WAYYY off....it will try to call a contact that doesn't even sound like who I'm trying to call.
My solution is to instead, turn the screen on, then hit the microphone icon (top right corner). From there if you say "Call Pizza Hut", it seems to work 100% of the time.
I agree that the issue is quite irritating. Hopefully a future update to Touchless Controls fixes this.
It will be interesting to see if those on later android versions also experience the same issue...
Are you also experiencing the 2nd problem?
Voice recognition doesn't seem to be an issue for me.
clankfu said:
Are you also experiencing the 2nd problem?
Voice recognition doesn't seem to be an issue for me.
Click to expand...
Click to collapse
Nope, just confirmed -- tried to call a contact with 2 numbers in phonebook (cell & home) and the phone responded:
"I found two matches. Say the name after you hear the one you want to call. 'Person' home. 'Person' cell."
samwathegreat said:
Nope, just confirmed -- tried to call a contact with 2 numbers in phonebook (cell & home) and the phone responded:
"I found two matches. Say the name after you hear the one you want to call. 'Person' home. 'Person' cell."
Click to expand...
Click to collapse
Yea, that's what mine used to do. Now it just calls the top number.

[Q] Duplicate SMS - Sprint Nexus 6

Hello,
I've been trying to figure this out for days now and I can't seem to find any permanent solution. My Nexus 6 on Sprint (Android L 5.0 / LRX21O / Up to Date PRL) 50%-75% of the time sends duplicate SMS messages to recipients. On my end I see one SMS message outbound and it sends without issue. On the other end, people will get the same message one to six times. I've seen it myself on a separate Sprint phone and a Verizon phone.
From what I can tell, sometimes updating the profile helps for a few minutes and that's it. It doesn't matter if I uninstall/disable the stock Google Messenger or Hangouts. This issue happens in every single 3rd party SMS messenger I've used. The only time I've got the problem to stop is if I force 3G service and not the Global or LTE settings. Strangely enough, If I'm on LTE, and I switch to WiFi, the issue remains. If I force 3G and then go on WiFi, the issue is gone.
I've tried uninstalling certain applications that come stock with the phone.. I've tried not updating any applications. I've done factory resets (and I sent an SMS to test without doing 1 update) and it still duplicated. I returned the phone and got another phone. Same issue. On the Sprint end, they changed some settings on my phone and had me reset the network connection via the phone *#*# etc. menu. That fixed the issue, and it lasted 24 hours. Upon either a reboot, or perhaps just a power cycle, the problem returned.
Any ideas as to why this is happening? I have zero Data issues. Hangouts works fine. Youtube, Gmail, Chrome etc are all super fast without issue.
Thank you in advance.
off1c3r said:
Hello,
I've been trying to figure this out for days now and I can't seem to find any permanent solution. My Nexus 6 on Sprint (Android L 5.0 / LRX21O / Up to Date PRL) 50%-75% of the time sends duplicate SMS messages to recipients. On my end I see one SMS message outbound and it sends without issue. On the other end, people will get the same message one to six times. I've seen it myself on a separate Sprint phone and a Verizon phone.
From what I can tell, sometimes updating the profile helps for a few minutes and that's it. It doesn't matter if I uninstall/disable the stock Google Messenger or Hangouts. This issue happens in every single 3rd party SMS messenger I've used. The only time I've got the problem to stop is if I force 3G service and not the Global or LTE settings. Strangely enough, If I'm on LTE, and I switch to WiFi, the issue remains. If I force 3G and then go on WiFi, the issue is gone.
I've tried uninstalling certain applications that come stock with the phone.. I've tried not updating any applications. I've done factory resets (and I sent an SMS to test without doing 1 update) and it still duplicated. I returned the phone and got another phone. Same issue. On the Sprint end, they changed some settings on my phone and had me reset the network connection via the phone *#*# etc. menu. That fixed the issue, and it lasted 24 hours. Upon either a reboot, or perhaps just a power cycle, the problem returned.
Any ideas as to why this is happening? I have zero Data issues. Hangouts works fine. Youtube, Gmail, Chrome etc are all super fast without issue.
Thank you in advance.
Click to expand...
Click to collapse
I always just thought this was an issue on Sprints side and not the phone itself. I just started with Sprint myself when I picked up the Nexus, prior to this I had Verizon.
My girlfriend however has been with Sprint forever and no matter what ROM or phone she had, this issue would pop up from time to time.
Now that I'm with Sprint she's told me a few times that she's gotten duplicate messages from me. It seems to happen when we are in spotty service areas from what I can tell. I haven't even bothered calling Sprint like you have though... I just chalked it up as Sprint service is sketchy.
Mistertac said:
I always just thought this was an issue on Sprints side and not the phone itself. I just started with Sprint myself when I picked up the Nexus, prior to this I had Verizon.
My girlfriend however has been with Sprint forever and no matter what ROM or phone she had, this issue would pop up from time to time.
Now that I'm with Sprint she's told me a few times that she's gotten duplicate messages from me. It seems to happen when we are in spotty service areas from what I can tell. I haven't even bothered calling Sprint like you have though... I just chalked it up as Sprint service is sketchy.
Click to expand...
Click to collapse
The issue here is that it's not popping up from time to time...it's pretty consistent. I've been with Sprint for at least 7 years and have never ran into the issue until this phone. My prior phone was a Nexus 5...and I have a galaxy s3 here which I can't duplicate the issue on.
We all need to complain to Sprint so they either fix it on their side, or put pressure on Google to fix it on their own side.
---------- Post added at 06:07 AM ---------- Previous post was at 06:04 AM ----------
Let Sprint know you're experiencing the issue here: https://community.sprint.com/baw/thread/179054
Call and complain, perhaps we should also complain to google? Here is their Nexus 6 product forum: https://productforums.google.com/forum/#!categories/nexus/nexus-6
iil said:
The issue here is that it's not popping up from time to time...it's pretty consistent. I've been with Sprint for at least 7 years and have never ran into the issue until this phone. My prior phone was a Nexus 5...and I have a galaxy s3 here which I can't duplicate the issue on.
We all need to complain to Sprint so they either fix it on their side, or put pressure on Google to fix it on their own side.
---------- Post added at 06:07 AM ---------- Previous post was at 06:04 AM ----------
Let Sprint know you're experiencing the issue here: https://community.sprint.com/baw/thread/179054
Call and complain, perhaps we should also complain to google? Here is their Nexus 6 product forum: https://productforums.google.com/forum/#!categories/nexus/nexus-6
Click to expand...
Click to collapse
I'll try and contact them today if I have time. Its worth a shot right?!
Let me know how you make out and I'll do the same. Thanks for the links
This phone is really flaky for me with SMS. Doesn't want to send when I am on wifi. My wife did get a duplicate from me one night when I was trying to figure out why it won;t send when wifi is on but she hasn't mentioned it since. ( I am on Sprint)
Evo_Shift said:
This phone is really flaky for me with SMS. Doesn't want to send when I am on wifi. My wife did get a duplicate from me one night when I was trying to figure out why it won;t send when wifi is on but she hasn't mentioned it since. ( I am on Sprint)
Click to expand...
Click to collapse
What SMS application are you using? Did you install any 3rd part SMS applications?
off1c3r said:
Hello,
I've been trying to figure this out for days now and I can't seem to find any permanent solution. My Nexus 6 on Sprint (Android L 5.0 / LRX21O / Up to Date PRL) 50%-75% of the time sends duplicate SMS messages to recipients. On my end I see one SMS message outbound and it sends without issue. On the other end, people will get the same message one to six times. I've seen it myself on a separate Sprint phone and a Verizon phone.
From what I can tell, sometimes updating the profile helps for a few minutes and that's it. It doesn't matter if I uninstall/disable the stock Google Messenger or Hangouts. This issue happens in every single 3rd party SMS messenger I've used. The only time I've got the problem to stop is if I force 3G service and not the Global or LTE settings. Strangely enough, If I'm on LTE, and I switch to WiFi, the issue remains. If I force 3G and then go on WiFi, the issue is gone.
I've tried uninstalling certain applications that come stock with the phone.. I've tried not updating any applications. I've done factory resets (and I sent an SMS to test without doing 1 update) and it still duplicated. I returned the phone and got another phone. Same issue. On the Sprint end, they changed some settings on my phone and had me reset the network connection via the phone *#*# etc. menu. That fixed the issue, and it lasted 24 hours. Upon either a reboot, or perhaps just a power cycle, the problem returned.
Any ideas as to why this is happening? I have zero Data issues. Hangouts works fine. Youtube, Gmail, Chrome etc are all super fast without issue.
Thank you in advance.
Click to expand...
Click to collapse
Yep, this has been happening to me. My girlfriend started complaining she was getting my text 2x-3x for each message. She is on T-Mo, I'm on Sprint. Tested with a few coworkers on different providers and only 1 out 4 received it more than once and they are on Verizon. Rebooted, tried updating PRL and data profile. She hasn't complained about it doing it anymore but we will see. Super frustrating
unregistered825 said:
What SMS application are you using? Did you install any 3rd part SMS applications?
Click to expand...
Click to collapse
Just google messenger.
Evo_Shift said:
Just google messenger.
Click to expand...
Click to collapse
I've tried every combination you can think of:
1. Google Messenger as default with and without Hangouts installed.
2. Hangouts as default with and without Google Messenger installed.
3. SMS Messenger AOSP, ChompSMS, 8sms, Textra, Handcent, all with and without Google Messenger and or Hangouts installed.
I've tried forcing 1x, updating PRL and Profile and then going back to LTE. Same issue. Multiple Hard Resets and Data Network Resets. Only ONCE the Sprint support person did something on their end ("Changed a number") and out of nowhere the duplicates stopped. But it only lasted 1 day while using Google Messenger.
This happened to me with my G3 on Att, it just stopped one day and I still don't know what started it
Mistertac said:
I'll try and contact them today if I have time. Its worth a shot right?!
Let me know how you make out and I'll do the same. Thanks for the links
Click to expand...
Click to collapse
I posted on the Sprint Community page. I'm glad others are finding this issue too.
off1c3r said:
I posted on the Sprint Community page. I'm glad others are finding this issue too.
Click to expand...
Click to collapse
I just joined you over on the Community Page as well.. Guess we'll see how it plays out, although I must admit I don't have much faith this will get fixed lol
But, I'm willing to take it the distance in an effort to try!!
Evo_Shift said:
This phone is really flaky for me with SMS. Doesn't want to send when I am on wifi. My wife did get a duplicate from me one night when I was trying to figure out why it won;t send when wifi is on but she hasn't mentioned it since. ( I am on Sprint)
Click to expand...
Click to collapse
I'm having the same exact issue
Mistertac said:
I just joined you over on the Community Page as well.. Guess we'll see how it plays out, although I must admit I don't have much faith this will get fixed lol
But, I'm willing to take it the distance in an effort to try!!
Click to expand...
Click to collapse
Lol. Yeah. Doesn't hurt. I'm on the phone with Sprint again and they said they are making a ticket with their engineers.
Just picked mine up today from sprint. My buddy who is also on sprint made me aware that he was getting repeat sms from me already. It's funny because I would always complain that I was getting them from him before I jumped to sprint. He's on a LG G2 though.
kmmxracer said:
Just picked mine up today from sprint. My buddy who is also on sprint made me aware that he was getting repeat sms from me already. It's funny because I would always complain that I was getting them from him before I jumped to sprint. He's on a LG G2 though.
Click to expand...
Click to collapse
Don't get me wrong.. the phone is absolutely amazing. I love it. I can't go back to my Moto X, which to me was one of the best Android phones ever made. Again, what people don't understand is this is a REAL issue. People are very quick to say that "bad service" caused it. We're all smart enough to know that if you have bad service, 1 or 2 duplicates can happen, on occasion. Not repeatedly in a full service area or on WiFi.
As an Update:
Everything Sprint tried has failed. However, my original debug information holds true:
1. If the phone is set to 3G mode only: The problem is SOLVED.
2. If the phone is on WiFi, AFTER being set to 3G mode only: The problem is SOLVED.
3. If the phone is set to LTE mode only: The problem REMAINS, unless you are in a no LTE service area and revert to 3G or less.
4. If the phone is on WiFi, AFTER being set to LTE mode only: The problem REMAINS.
kmmxracer said:
Just picked mine up today from sprint. My buddy who is also on sprint made me aware that he was getting repeat sms from me already. It's funny because I would always complain that I was getting them from him before I jumped to sprint. He's on a LG G2 though.
Click to expand...
Click to collapse
Please post to the Sprint forums of your issue here: https://community.sprint.com/baw/thread/179054
Somebody also started a thread in the Nexus forum: https://productforums.google.com/forum/#!category-topic/nexus/nexus-6/JM44M3bofBc
Well both me and my girlfriend have reset the network settings from the dialer like suggested, so I guess today we'll see if that helps.
She's already complained of getting my messages 4x a piece this morning, so I'm thinking positive!
iil said:
Please post to the Sprint forums of your issue here: https://community.sprint.com/baw/thread/179054
Somebody also started a thread in the Nexus forum: https://productforums.google.com/forum/#!category-topic/nexus/nexus-6/JM44M3bofBc
Click to expand...
Click to collapse
I just posted my issue.

Texts stuck "sending" and other issues

Ok everyone figured I'd come here to where the experts live. Haven't been here in awhile.
Recently my S8, wifes S8, and our sons S8+ all have the same issues.
The first issue is texts get stuck "sending". This happens with WiFi on or off, with wifi calling on or off, and I even tried changing off LTE to just 4G/3G/2G and even 2g in settings to see if that would help. I'm on the latest firmware from TMO ending in QEF, well we all are.
The other one is apps like FB and others aren't alerting but they will show the number of alerts even after they've been checked. I've reinstalled these apps and the problem persists, and then I can reboot my phone or wifes phone and all the alerts start working again for awhile and then die eventually.
The texting issue though persists and is random when it will hang and when it doesn't.
According to TMO rep at the store it's a bug in the firmware with bixpy that was pushed out, but I frankly don't buy it and figured I'd hit the guru's up here and see if you guys have any thoughts.
Thanks in advance guys and gals....
I too have had the random "texts get stuck sending" issue. I haven't had it in a while though (now that I've said that I'm sure I will).
I unfortunately don't have any suggestions.
I ended up using googles version of messages due to this. Only on stock text app do i have any problems anymore. I also noticed on the stock app that my phone would say "sending" when the other side would actually get it, but it was at random.
You don't have a cellspot repeater or router do you? Last time I had it, my device was hung and needed reboots. Just a thought.
Thanks for the feedback, yes I have a cell spot, but I also have the issue other areas of town too with no real specific place thatbit always happens.
I'm going to reverse back from the qef firmware and see if that resolves things. This has been so annoying, and it just started about two weeks ago.
Thanks again everyone.
I have had the same issue with sending texts too. I have been using the stock messenger app. I may just switch to textra.
Same issue here. A temporary fix, try turning on airplane mode and off. Works for me a times
Also happening to me on the XAA firmware (have unlocked NA variant) with the stock messaging and Google messages.
So I'll ask the question begging to be asked (at least by me): How does one disable this messaging app and use "stock messaging" app?
Thanks in advance....
rabilancia said:
So I'll ask the question begging to be asked (at least by me): How does one disable this messaging app and use "stock messaging" app?
Thanks in advance....
Click to expand...
Click to collapse
Just get a app disabler for Samsung from play store like BK Disabler.
If I were you, just download Android Messages. It's simple and fast.
However, I do not recommend disabling stock messaging, unless you don't like getting EAS (Amber/Weather/Presidential Alert)
Having the exact same issues and it's driving me crazy because I really like this phone. I don't get notifications for any of my apps but when I open them I can see the new messages. A reset seems to fix the problem but it only lasts about an hour before it starts doing the same thing. I've tried using different messaging apps but the same thing. And the fact that I don't get notifications for other apps it can't just be a text messaging issue right?
Happened to me for almost 2 months but haven't had an issue in about a week. Called t mobile, they created a ticket and said they'll be working on it. Few days after speaking to them, problem went away.
This has been happening intermitantly for me as well. It's been bad the past three days. I'm currently in coversations with T-mo's engineering team and they seem to be coming up with a bunch of dead ends. It's not a location based thing as it's been happening over a 20 mile radius in the past few days for me. Other people on T-mo network that I'm freinds with or I work with aren't having any problems. I'm wondering if just a fresh SIM card could solve it?
I have data connection although it seems a little sluggish compared to when I originally got the phone. Similar to OP I've tried all the "G's" modes, with wifi calling on, with it off, with cellular network preffered with wifi calling on and off. With Textra, with stock messaging app. I've factory reset to no avail. I've pulled and re-inserted the SIM card to no avail. This is incredibly frustrating for a flagship phone on a network where I've had no previous issues.
UPDATE: T-Mobile sent me a new SIM card and that seems to have cleared up the issues. Not sure if it just hapened to coincide with T-Mo tower fixes or anything else like that in my area but I'm back to normal operation. Anybody else experiencing this I recommend you push customer service to send you a new sim.
my husband and i are having a strange issue where we can message pictures and video clips to other people that don't have the s8, or aren't on tmobile and they'll send and receive just fine, but when we try to send to each other, the first attempt to send fails, but the second attempt goes through?
balthuszar said:
my husband and i are having a strange issue where we can message pictures and video clips to other people that don't have the s8, or aren't on tmobile and they'll send and receive just fine, but when we try to send to each other, the first attempt to send fails, but the second attempt goes through?
Click to expand...
Click to collapse
i had same problem one of you is not using stock message app, if you check it ull find pictures all there i think its new messages plus thing

Categories

Resources