kz121.xp
Member
All,
I too have been experiencing this issue for at least the last 6mo... I switched last summer from an HTC One M8 (after it popped off my motorcycle mount on a parkway and was crushed by a thousand cars in 20 mins - long island ny) to a Samsung Note 4. Love the note 4, BTW - so the issue with the DTMF (touch tones randomly occurring) I thought it was coming from the people I was talking with - mobile to mobile - figured they were on the other end with the phone up to their face and accidently hitting keys from the keypad...
After some time - i began to realize it wasn't the other person at all.
Like a few folks have stated - the DTMF tones are ONLY occurring on my side - the far end caller can NOT hear the tones.
I have also confirmed that the issue occurs both MOBILE to MOBILE and MOBILE to LandLine
I've had the issue occur while in speaker mode (using internal speaker w/ bluetooth off), the ear-piece (in the phone) & various bluetooth and wired headsets as well as my Alpine Nav System in my car - so it is not "attached device errors".
My Service Provider is AT&T Mobility and I'm in the Lower NY market (stradling Eastern NJ, NYC and Long Island)
The issue occurs in every part of that region, which means the issue is NOT on the "Switch Side" unless all the switches have the same source issue. (I say this because that "Echo" condition people have spoken about is related to Echo Canceller failures and bad digital cross connects which occur exclusively mobile to mobile - these connections never hit the PSTN Public Service Telephone Network for LandLine)
I've asked owners of various other manufacturers phones (asus, hauwai, htc, apple, lg, etc...) no one else has ever experienced this issue
This leads me to believe it is something with the Note 4 specifically - it could, in theory, be related to the Samsung Builds for AT&T.
QUESTION:
I'm interested to see if marshmallow has the same issue with it finally gets released for the Note 4 for AT&T.
Anyone have an AT&T note 4 running marshmallow or using a customized ROM other than the at&t lollipop build have this issue?
Chris
I too have been experiencing this issue for at least the last 6mo... I switched last summer from an HTC One M8 (after it popped off my motorcycle mount on a parkway and was crushed by a thousand cars in 20 mins - long island ny) to a Samsung Note 4. Love the note 4, BTW - so the issue with the DTMF (touch tones randomly occurring) I thought it was coming from the people I was talking with - mobile to mobile - figured they were on the other end with the phone up to their face and accidently hitting keys from the keypad...
After some time - i began to realize it wasn't the other person at all.
Like a few folks have stated - the DTMF tones are ONLY occurring on my side - the far end caller can NOT hear the tones.
I have also confirmed that the issue occurs both MOBILE to MOBILE and MOBILE to LandLine
I've had the issue occur while in speaker mode (using internal speaker w/ bluetooth off), the ear-piece (in the phone) & various bluetooth and wired headsets as well as my Alpine Nav System in my car - so it is not "attached device errors".
My Service Provider is AT&T Mobility and I'm in the Lower NY market (stradling Eastern NJ, NYC and Long Island)
The issue occurs in every part of that region, which means the issue is NOT on the "Switch Side" unless all the switches have the same source issue. (I say this because that "Echo" condition people have spoken about is related to Echo Canceller failures and bad digital cross connects which occur exclusively mobile to mobile - these connections never hit the PSTN Public Service Telephone Network for LandLine)
I've asked owners of various other manufacturers phones (asus, hauwai, htc, apple, lg, etc...) no one else has ever experienced this issue
This leads me to believe it is something with the Note 4 specifically - it could, in theory, be related to the Samsung Builds for AT&T.
QUESTION:
I'm interested to see if marshmallow has the same issue with it finally gets released for the Note 4 for AT&T.
Anyone have an AT&T note 4 running marshmallow or using a customized ROM other than the at&t lollipop build have this issue?
Chris