I'm having issues with my WiFi calling's caller ID when im home(Optimum Online).
Caller ID always comes up with the caller's phone number with a semicolon and two random digits afterwards(62 or 63)
Went to my friends house and it worked perfectly there(he has FiOS)
Am I the only one with this issue?
This actually a known issue with note 3 wifi calling. Happens to me at work on comcast and at home on fios.
Sent from my SM-N900T using Tapatalk 4
I got time warner. Same thing happens
Sent from my SM-N900T using xda app-developers app
It is a known issue please call T-Mobile and report the issue so they will fix it.
Sent from my SM-N900T using xda app-developers app
It looks like if I get a call from a T-Mobile number, it works fine. All other carriers have the semicolon issue.
Not a home internet carrier issue
Sent from my SM-N900T using xda app-developers app
The really odd thing is that it never happens for me (even with receiving calls from other carriers). I have Comcast for my ISP and no semicolons or extra numbers are displayed. The only thing I haven't tried is receiving a call from a number that I dont have in my contacts. Maybe thats why I dont have a problem?
Related
Hey guys. So im realizing when people send me pictures. You have to click the download button. Well when I click it. It does not download and I can not recieve the pictures. In fact, it doesnt even download. Any way to fix this?
Sent from my SGH-T989 using XDA App
Just realized my pics arent sending either.. what goes on here?
Just sent and received a picture message(With Wifi on). Sounds like it might just be a problem with your phone/connection
**Your phone should Automatically Turn on Mobile Data when Sendin or Receiving MMS Messages while Wifi is active. If this is not happening you may want to Call Customer Care.**
Another thing that may be affecting this is bad Signal
Sent from my SGH-T989 using XDA App
Well i came to the conclusion that i have to be on 4g.. i was tying to send and receive pics under wifi.. how come it does not work under wifi? or is it just me?
ixJay said:
Well i came to the conclusion that i have to be on 4g.. i was tying to send and receive pics under wifi.. how come it does not work under wifi? or is it just me?
Click to expand...
Click to collapse
Same thing is happening to me. Sending and receiving pics only works when 3g\4g is on rather than Wifi
Sent from my Xoom using Tapatalk
This has always happened with me with every phone i had. Including from different carriers. I always thought this was normal.
Sent from my SGH-T989 using XDA App
Very Normal
droidsrus said:
This has always happened with me with every phone i had. Including from different carriers. I always thought this was normal.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Quite normal. Of course Mobile Data has to be on. No phone can send a message through wifi and have it delivered through the carrier
Edit
However, even with WIFI on your phone should start and stop mobile Data to send and receive MMS messages. If yours is not doing this, then you may want to call Customer Care.
Another possible reason for why this is happening is that you may have a very weak or bad signal.
I have continued issues with receiving picture texts.... I almost always have to tell the sender to send it once more for it to come through. I've also noticed my H bars turning from Blue to Grey when this happens.... Any ideas as to what could be causing this? At&t looks dumbfounded every time I go in or call about this....
Sent from my Galaxy Nexus using xda app-developers app
TBH, it sounds like an ATT issue.
I know the common thought is that grey bars means lost connections to Google, but when that happens to me, I have always lost network connectivity.
vodka7 said:
I have continued issues with receiving picture texts.... I almost always have to tell the sender to send it once more for it to come through. I've also noticed my H bars turning from Blue to Grey when this happens.... Any ideas as to what could be causing this? At&t looks dumbfounded every time I go in or call about this....
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Remove your Google account then add again. Reboot.
Edit, custom ROM? I went back to stock because of many random issues since 4.1.2 was officially released.
Sent from my Nexus 7 using XDA Premium HD app
mms is either apn related problem or just bad coverage (no good data in area)
you can google different apn settings to try
I have to use go smd to view mms depending on what ROM I'm using.
Sent from my Galaxy Nexus using xda premium
Uncheck auto retrieve and manually download them when they come. ThTs what I do on my vzw gnex as they sometimes get stuck if it have it auto and don't finish downloading.
Sent from my Galaxy Nexus using xda premium
So ever since I've gotten the phone (9:00 am yesterday) all my calls have been showing up incorrectly when I am receiving them. I just wanted to know if anybody else has the same issue and what you did to resolve it.
Sent from my SM-N900T using xda app-developers app
jastep said:
So ever since I've gotten the phone (9:00 am yesterday) all my calls have been showing up incorrectly when I am receiving them. I just wanted to know if anybody else has the same issue and what you did to resolve it.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I am so glad someone else is having this issue I've spent most of the day trying to resolve it. Ok, what I know so far:
It only happens on WIFI calling. I've cleared the wifi calling app no dice.
Customer service is unaware of the issue. They said use a different email account. UH NO I've had my gmail since it was in Beta.
I've reset my device twice it comes back after I re-install gmail I think it comes with the restore function I've tried stopping the restore function but it keeps coming back
Let me know if you fix it. I had a note two there may be a correlation
Same thing happens to me but only during wifi calling. No big
Sent from my SM-N900T using XDA Premium 4 mobile app
Same boat guys. Only happens during wifi calling. Very annoying to tell you the truth. Any help would be appreciated.
Sent from my SM-N900T using Tapatalk 4
Ahh I see so that's what triggers it. I suppose they'll issue a fix once they find out what's causing it
Sent from my SM-N900T using xda app-developers app
I have a thread on Google + it is somehow tied to wifi calling and to Google contacts sync. Anyway you have to clear the cache partition. Hold down volume up, home and power keys until you see Samsung note 3 then release just power until you are in recovery then chose volume down to clear cache and power button to select then restart you may have to factory reset the device
It seems fixed on my phone but a friend is still having trouble
Sent from my SM-N900T using xda app-developers app
Yeah that didn't work for me. I want to try re flashing instead of resorting but it just so happens that Kies doesn't support the note 3 yet.
Sent from my SM-N900T using xda app-developers app
Mine does the same thing
Sent from my SM-N900T using XDA Premium 4 mobile app
When one of my contacts tries to call me, my phone rings and I am only able to see their phone number but not their name. Their phone info will show in this format 1-234-567-8910; oli;63
When I try to call one of my contacts, it acts normal and also shows in the phone logs. I restored the phone to factory settings, but still not able to solve the problem. Any ideas?
Thanks
Sent from my SM-N900T using Tapatalk 2
Let me guess: T-Mobile // WIFI calling?
Getting the same issue.
ceroglu said:
When one of my contacts tries to call me, my phone rings and I am only able to see their phone number but not their name. Their phone info will show in this format 1-234-567-8910; oli;63
When I try to call one of my contacts, it acts normal and also shows in the phone logs. I restored the phone to factory settings, but still not able to solve the problem. Any ideas?
Thanks
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Is that what is causing it? Man, I have been trying to fix this all day. I did two factory resets!
Sent from my SM-N900T using Tapatalk 2
It's a known issue with wifi calling. ... disable it and everything will be fine
Sent from my SM-N900T using XDA Premium 4 mobile app
Never had this problem with any other Wifi calling device. Hopefully it gets fixed in the next update.
Sent from my SM-N900T using Tapatalk 2
Questions and request for assistance go in the Q&A section not in the General section. Please pay attention to the rules in the future.
Thread moved
Have a great day!
Same here on WiFi calling.
Pedro2NR said:
Same here on WiFi calling.
Click to expand...
Click to collapse
Same problem.
Resolved by disable WiFi Calling, wait 60 secs, and turn in back on (if needed)
I Called T-mobile and Tech support sent me couple of SMS and made me turn off and then turn on the phone and called me again and it
seemed to have fixed the problem , but then I realized that problem is fixed from receiving calls from T-mobile numbers or land lines, but the from Verizon number it came with the ;oli;63
This is very strange, hopefully gets fixed soon.
Well I am having another problem now. That is, my phone calls are being rejected automatically when on Wifi calling when the phone is in a deep sleep. I checked under the call settings and changed the auto rejection mode off, but the problem is still there. Can someone else confirm this by chance?
Sent from my SM-N900T using Tapatalk 2
I'm having the same WiFi calling issue. Sucks
Sent from my SM-N900T using xda app-developers app
If you are having this issue please report it to T-Mobile so they are aware that it is a wide spread issue and work to fix it.
Sent from my SM-N900T using xda app-developers app
foriesg said:
If you are having this issue please report it to T-Mobile so they are aware that it is a wide spread issue and work to fix it.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Ready reported it to T Mobile. Not sure if they will fix it soon enough.
Also not getting HD Voice at all.
I have the same issue. I don't have service in my house, so the wifi calling feature is amazing. I've always used a nexus and hard to use third party apps and voips and connect with gv. For the most part if you recognize the number minus the olli, it's no big for now. I'm glad I can still make calls. Update should fix. At least it doesn't happen on reg network.
Sent from my SM-N900T using XDA Premium 4 mobile app
I called tech support in T Mo and they are sending me a new Note 3. But I doubt that will resolve the issue.
tdoughone said:
I have the same issue. I don't have service in my house, so the wifi calling feature is amazing. I've always used a nexus and hard to use third party apps and voips and connect with gv. For the most part if you recognize the number minus the olli, it's no big for now. I'm glad I can still make calls. Update should fix. At least it doesn't happen on reg network.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I turned wifi off; but now when a call comes in it is reported as "unknown." could this be an issue with root? would odining back to factory resolve this?
Charlie
Alright, just called tmo and they said that they are aware of the problem and working to fix it. Hopefully we should see a fix soon!
Sent from my SM-N900T using Tapatalk 2
When I spoke to TMO yesterday the tech guy said they should have the fix by Thursday. If it is still happening by Friday I will bug them again, so far call from landline and tmobile number are comming in fine.
Sent from my SM-N900T using xda app-developers app
Superdad_98 said:
When I spoke to TMO yesterday the tech guy said they should have the fix by Thursday. If it is still happening by Friday I will bug them again, so far call from landline and tmobile number are comming in fine.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I got a second Note 3 from T Mo and still see the same Caller ID issue along with no HD Voice call capability.
I am returning mine until they fix the bugs (no HD Voice call support, 5Ghz WiFi connection instability, and this Caller ID problem)
I really would like to keep the phone... I love the huge display... but I think I will have to stick with my HTC One for now.
surfsnow said:
I got a second Note 3 from T Mo and still see the same Caller ID issue along with no HD Voice call capability.
Click to expand...
Click to collapse
How can one tell when HD Voice calling is active/inactive?
My wife, daughter and I all have Att smartphones. The past week or so we have been receiving old text messages or delayed text messages. I live in Chicago and have Att service. I am wondering if anyone has experienced this and how to fix it.
Sent from my SAMSUNG-SM-N910A using xda premium
Just started happening to me a couple of days ago. Received a text that was date stamped 2 days prior. Also noticed that I get texts that show up in the notifications but not in the message app. Only way to access them is to open through notification bar. I also live in the Midwest and have At&t service.
Sounds like it's an AT&T issue.
Sent from my SAMSUNG-SM-N910A using xda premium
borijess said:
Sounds like it's an AT&T issue.
Sent from my SAMSUNG-SM-N910A using xda premium
Click to expand...
Click to collapse
My thoughts exactly. Messaging was fine until then. No changes to phone before or during the period the late messages were arriving.
I just got a text yest that was dated from thurs..I thought my phone was messed up...glad I ain't the only one
You guys should also check out if your AT&T message backup & sync is the culprit. It has a tendency to sync and bring back very old messages. I disabled it (hence why it's grayed out in the pic).
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
I use textra. And this is also happening on my wife's iPhone 6. How do u disable that. I don't see the option in applications.
Sent from my SAMSUNG-SM-N910A using xda premium
Sent from my SAMSUNG-SM-N910A using xda premium
AT&T backup was off. (Never have used it). Think was an AT&T issue as mentioned earlier. Haven't had issues lately.