Unlocked phone on T-mobile, US.
I'm not sure when this gets started, but I've noticed it after the April update. When on VoLTE, there's no sound for incoming or outgoing calls. When on WiFi Calling, it auto hangs up as soon as the call is picked up.
Any input is highly appreciated. Thanks in advance!
judsonzhao said:
Unlocked phone on T-mobile, US.
I'm not sure when this gets started, but I've noticed it after the April update. When on VoLTE, there's no sound for incoming or outgoing calls. When on WiFi Calling, it auto hangs up as soon as the call is picked up.
Any input is highly appreciated. Thanks in advance!
Click to expand...
Click to collapse
I had an issue recently where all calls I made (wifi calling or though the stock dialer app) would auto hangup and never go through. Incoming calls seemed to work fine though.
I did a factory data reset and set everything up back from scratch, that was the only way to fix it. This maybe something worth trying if you haven't done it already.
If you do a restore of any backup data (i.e. smartswitch, google backup) I would suggest using the google backup and not the smartswitch this time. I made a smartswitch backup before the factory data reset, but ended up not being able to use it. Everytime I did a restore with the backup the same thing would happen. I had no problems with the google backup.
Also if the problem persists (or if you opt to do so anyways, maybe worth trying anyways) I would call T-Mobile support and ask them if there are any problems or etc. It maybe possible they are working on the towers near you, as one time my service was being a little quirky and it was due to them doing some low/mid band additions on nearby towers. They may just need to refresh your phone on there end or send you a replacement sim card in case a problem exists with the one you have..
scottusa2008 said:
I had an issue recently where all calls I made (wifi calling or though the stock dialer app) would auto hangup and never go through. Incoming calls seemed to work fine though.
I did a factory data reset and set everything up back from scratch, that was the only way to fix it. This maybe something worth trying if you haven't done it already.
If you do a restore of any backup data (i.e. smartswitch, google backup) I would suggest using the google backup and not the smartswitch this time. I made a smartswitch backup before the factory data reset, but ended up not being able to use it. Everytime I did a restore with the backup the same thing would happen. I had no problems with the google backup.
Also if the problem persists (or if you opt to do so anyways, maybe worth trying anyways) I would call T-Mobile support and ask them if there are any problems or etc. It maybe possible they are working on the towers near you, as one time my service was being a little quirky and it was due to them doing some low/mid band additions on nearby towers. They may just need to refresh your phone on there end or send you a replacement sim card in case a problem exists with the one you have..
Click to expand...
Click to collapse
Thank you so much for the input! I'm going to factory reset this evening. And if it still persists probably call Tmo. But I guess the chance is low, my other device works just fine with Tmo (both wifi calling and volte)
Let's see! Have a good one!
Related
just burnt this rom, everything works but I can't make phone calls, tried to swich to another sim and it works.
Gonna contact my cellular company, does anyone have any idea how do I recognize the problem?
Data works,incoming calls works... it's weird for me and hard to explain, the main problem is they don't support custom roms and I don't wanna fall into this...
thank you!
forgot to mension
I can send SMS and receive, did factory reset, wipe cache...
found my network on the settings and chose it but no outgoing calls, tried another apps for dialing ...
the other sim is on a different same network but with the same frequencies (UMTS 850,2100) and works!
another thing that I thought, maybe it's not the issue but the SIM that doesn't work is not personal but my work cellular SIM, it worked on the same machine with the previous version , which was 4.2.2 custom but not this one, and I like this one because it's faster.
thank you
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
mghtymse007 said:
Go to mobile carrier settings and set the phone to forward unanswered calls to your S's assigned phone #. This way if the software fails, the carrier's network will forward the call to your watch regardless.
Click to expand...
Click to collapse
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
pdqgp said:
Thanks. I actually do that through a nice widget if I know for sure I'm going to be out with watch only. Mainly so the inbound callers don't have to sit through a number of rings before their call comes to me.
That said, it's really a band aid as the darn auto forward should work. I'm going to check what was suggested above and see what I find. The problem is last week it said it was connected remotely but I wasn't getting any notifications. That coincided with no call forwarding, thus I think the problem is more than just forwarding.
I reset the watch, restored, etc. and it worked once. I'll know more this week. THank you again for the input. Any input if very much appreciated.
Click to expand...
Click to collapse
Sorry to hear you have a&t. Connected remotely and call forwarding are two completely different things as you may know but regardless of the matter its not Samsungs fault. Your device showed that it was connected remotely therefore it was....the real issue is your wireless carriers crappy network not pushing your notifications plain and simple not your watch or your phone. Both are working just fine from what you've stated which leads to the fact that its your network connection. Only GSM networks are capable of auto call forwarding which as I stated is completely carrier network based. No offense but at&t sucks anymore and havent seen these issues with anyone but at&t customers. Its on at&ts end. Call and complain about your issue but unfortunately I doubt they will do crap which is why I left at&t 3 months ago. Hope you can get them to figure it out.
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
pdqgp said:
I love my Gear S and the main reason I bought it is for the fact that it can auto call forward and connect remotely. Lately however the dang thing does not seem to work if at all.
What's the deal? I have my Note 3 connected via BT. Both devices are connected and working just fine, and all is good. If I leave the house 1/10 times the Gear S will work properly forwarding calls and being connected remotely. Otherwise, it just never works and gives me that dumb error on the watch to Try Again. It never works, so I reboot it. Again, 1/10 times it will work.
Today I decided to work through this and of course it's not working. It says that the phone is connected remotely but I am not getting any notifications. I can from the Gear S, I can send email from it, but texts and notifications go into limbo. WTF! I swear, it's a love / hate with Samsung and it's issues like this that make me hate them.
Now I've reset the Gear S and am in the process of restoring it in hopes that somehow this fixes it. If not, I'll blow it away again and remove the gear manager and start from scratch.......again!! I had to do this back in Feb due to the Gear S giving up taking a charge for some stupid reason.
Sorry for my frustration, but WTF is wrong here? Anyone have these issues? I'm on the edge of leaving Samsung for something else just because I"m getting tired of this crap.
Click to expand...
Click to collapse
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
rickleasa said:
The problem is lollipop if restore your phone to kitkat then setup call forwarding then upgrade to lollipop and you will not see sim or network error again
Click to expand...
Click to collapse
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
pdqgp said:
I don't think it's lollipop. It's now been working fine since a Gear S reset. I just think Sammy needs to figure out the bugs where ever they are. Moot point once someone else comes out with a nicer styled one with a sim card as I'll likely go that route.
Click to expand...
Click to collapse
ok glad to hear but that didn't work for me as when i went to call setting on my phone i still received the sim network error until i did the restore but glad it worked for you
djc-wi said:
I was having the same problem. Used Gear Manager to turn off auto forwarding, rebooted phone, turned call forwarding back on and it solved the problem. Unfortunately you have to wait until you are back with your phone to resolve the issue.
Click to expand...
Click to collapse
I finally figured out this only happens to me after I have Bluetooth paired to my car or a headset. Only happens every once in awhile. If I reenter my car and turn it on, as soon as Bluetooth reconnects it's back to working. The problem will come back if I don't reset my phone. Then all is fine for a few days. In my case obviously the bug is in gear S bluetooth not my phone or my car as the same thing at times will happen with a Bluetooth headset.
SaintCrispin said:
I have the AT&T version too and was getting this issue. Go into the call settings on your phone to see if you're getting the NETWORK OR SIM CARD ERROR. If you see this, you need to reboot your phone and your Gear S.
I have a Note 4 on Lollipop, but what I do is:
Go to the Phone app
Tap the three dots on the top right
Tap settings
Tap Call
Tap More Settings
If you see the sim or network error here, the call forwarding to the Gear S will not work and you will have to reboot your phone and watch.
If you keep seeing that error, then call AT&T and have them reregister your device (phone) sim to the network.
That's what I did to fix mine. This might be just a Note 4 issue in my case but the steps might work for the Note 3 also.
It could also mean you have a bad AT&T signal where you are because the watch has to communicate with the phone before initiating the call forwarding.
Click to expand...
Click to collapse
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
foulmouthedruffian said:
You're a doll. This was EXACTLY my issue, and I spent ages pouring through forum posts and even called AT&T. I saw your post, rebooted my devices together, and voila! <3 Best!
Click to expand...
Click to collapse
Hah I'm glad it's working for you now.
Suddenly, my phone has decided to block ALL calls, even from my favorite contacts and voicemail. I just cannot receive incoming calls. The notification shows "Missed call from (blocked) [contact name or phone number]." The [contact name or phone number] part shows the name of the contact or phone number that is being blocked.
EDIT: Outgoing calls work just fine.
I have disabled blocked/black lists on the phone app, removed any restrictions from Hangouts/Voice and any other apps that interfere with the phone functions. I have restarted the phone and restored the phone app from Titanium. I have frozen/uninstalled any third party apps that provide calling/texting functions, such as voice, hangouts, talkatone, etc. I have even cleared cache and removed default app options from phone/contacts.
This problem suddenly started and I just cannot figure out what may be causing this problem. When I search online, it shows listings of apps that block calls, etc., but nothing that addresses my problem.
I am an advanced user - I have root on my current phone (Galaxy s3 with 4.4.2), and have installed custom roms on previous phones (an old Charge, s2, S3), etc. I am not a newbie, so, PLEASE answer my issue without condescension - THANK YOU.
I do not want to factory reset my phone - any ideas about what might be causing this problem and how to resolve it?
Phone info: Galaxy s3 with 4.4.2, rooted, on Verizon (I535).
Thanks.
Verizon tier 2 tech not helping
Tier 2 tech hasn't helped at all!
My only thought would be that what ever file that handled blocked calls got corrupted, and it wasn't removed when you uninstalled it. The only thing that might help is reflashing the rom. Now I never advise a dirty flash due to issues that can come of it but as you don't want to factory reset then it might be an option.
As you are not a noob my suggestion would be to format just the system partition, and reflash. Or you could just reflash. Either way is not 100%
Verizon thinks it might be a SIM card problem. So, I'll replace it and see how that works. If not, a bloody re-flash it will be.
Any other ideas in the meantime?
Thanks.
Hey Guys,
Desperate lurker here saying First of all thanks for all the guides and everything that the devs and everyone that the community has done. I've search all of google and xda but i can't seem to figure out what's wrong with me Xperia Z2 .D6503
. T mobile carrier.
Basically since yesterday, I noticed that my phone couldn't receive or make any phone calls. but data internet, wifi internet and text messaging was working fine. Whenever people call me, i would just get a voicemail notice. At the time I was on the Marshmallow Existence rom. Ive done a lot of troubleshooting since then and still I can only make a call on GSM Mode.
Here's what i've done.
Wiped data and "reset" my phone on the Existence ROM - didn't work.
Wiped everything and flash Resurrection ROM - didn't work still.
Used someone else's sim card , couldn't receive calls either.
Use my sim card on a different phone - that one worked (SO IT'S NOT THE SIM CARD'S FAULT)
Placed back my sim card in the Z2 and reset flashed the stock rom from this page https://forum.xda-developers.com/xperia-z2/general/stock-t3355768
but that didn't work either.
I've also manually put the Tmobile APN.
Basically calls only work when changing it into GSM mode. but when i put LTE/WCDMA/GSM. Calls made under LTE/WCDMA/GSM Won't even make a dialtone when I make a cal. It basically just ends after a few seconds
I'm starting to think it might be a hardware issue because no matter which ROM i put, no matter how many factory resets and data wipes i've done. I can only make calls on GSM Mode.
Does anyone have any other ideas or should I just cry and buy a new phone.?
I suggest you to flash your phone with flashtool v0.9.18.6 and flash 291 ftf and wipe all
@whatsadophone
Have you try resetting APN for your SIM card when on your device?
thanks to everyone who tried to help. I don't know what happened. but after i tried putting the sim back in the Z2 to check my signals using Signal Spy, It suddenly can use LTE again. Only problem is since i installed that stock ROM, I lost my recovery mode and can't get it back. But i wont push my luck and just keep it like it is till i buy a new phone.
whatsadophone said:
Hey Guys,
Desperate lurker here saying First of all thanks for all the guides and everything that the devs and everyone that the community has done. I've search all of google and xda but i can't seem to figure out what's wrong with me Xperia Z2 .D6503
. T mobile carrier.
Basically since yesterday, I noticed that my phone couldn't receive or make any phone calls. but data internet, wifi internet and text messaging was working fine. Whenever people call me, i would just get a voicemail notice. At the time I was on the Marshmallow Existence rom. Ive done a lot of troubleshooting since then and still I can only make a call on GSM Mode.
Here's what i've done.
Wiped data and "reset" my phone on the Existence ROM - didn't work.
Wiped everything and flash Resurrection ROM - didn't work still.
Used someone else's sim card , couldn't receive calls either.
Use my sim card on a different phone - that one worked (SO IT'S NOT THE SIM CARD'S FAULT)
Placed back my sim card in the Z2 and reset flashed the stock rom from this page https://forum.xda-developers.com/xperia-z2/general/stock-t3355768
but that didn't work either.
I've also manually put the Tmobile APN.
Basically calls only work when changing it into GSM mode. but when i put LTE/WCDMA/GSM. Calls made under LTE/WCDMA/GSM Won't even make a dialtone when I make a cal. It basically just ends after a few seconds
I'm starting to think it might be a hardware issue because no matter which ROM i put, no matter how many factory resets and data wipes i've done. I can only make calls on GSM Mode.
Does anyone have any other ideas or should I just cry and buy a new phone.?
Click to expand...
Click to collapse
i have same problem any help pls?
try doing that signal spy solution by luck that I did in the post before that
Hi everyone,
I'm having an issue with my device since yesterday. I wanted to make calls but as soon as I try to call someone I was getting "couldn't connect message"
I thought that it's maybe something to do with the carrier but i restarted my device, and after the restart I saw that I now only have 4g, and not 4g+ displayed, and still got the couldn't connect message then trying to call anyone. When switching to 3g/2g in settings I was able to call, and I was also able to receive calls even when on 4g.
My internet is working fine over mobile data, there were no issues with it.
Also, VoLte icon is being displayed all the time, thatdidn't go away.
At some point yesterday I was able to make calls over 4g again, but never regained the 4g+ and a few calls dropped after 5-6 minutes of talking.
I tried a SIM card from a different provider, but still see just 4g, and not 4g+
So I am not sure what could be the issue anymore.. Did anyone maybe encounter something similar after this last update? Maybe that's the issue. I don't know if I should consider suspecting a hardware issue because internet works fine all the time.
Clear system cache, clear sim toolkit data, and do a network reset.
See if that gets it...
blackhawk said:
Clear system cache, clear sim toolkit data, and do a network reset.
See if that gets it...
Click to expand...
Click to collapse
Thanks for the tip!
I actually tried doing all of that and nothing was helping.
At the end I changed the CSC back to my stock one (TOP) and 4g+ is back.
I have no idea why this happened because I was using BTE csc for months and everything was ok. I'm just glad that it's not a hardware issue.