Note 9 WiFi Calling - can`t make calls but receiving works. - Samsung Galaxy Note 9 Questions & Answers

Hi there.
I have Note 9 without any brand. Updated to newest firmware that existed and about two updates ago there was problem - i cant make any calls. Restarts one helps, and other time don`t help at all. And now - it was no use to restart phone because of this problem. I felt that it might be this problem and i turned off this option and tried to make call - and nothing. Only when i restarted phone again - i can make phone calls normally like before. This problem exists not everytime, it looks like when i make call to my second phone it is only "connecting..." at my note9, and other phone is ringing. And there is two kind of behavior, first - in note i cant hear anything, just this "connecting..." message, and other phone after few seconds hangs up and ask about reconnect. And second - after few seconds after receiving call it finally works but it have take some time between receiving call at second phone and hearing anything. Its lottery.
Now i have this option disabled, phone is restarted and now i can make calls. I contacted Samsung via chat (samsung members app) and via Twitter and they said to me to go to their service to diagnose or sth, but i know what i will hear at service: "please reset your phone to factory settings and if then this issue will be present we will take your phone and try to repair it" but i don`t want to do this because of all this configuration and hours of clicking... I dont like to do this when i dont have to.
So my question - do you have similar or the same problem? Is WiFi calling have anything to do with sim provider?

DeVilio said:
Hi there.
I have Note 9 without any brand. Updated to newest firmware that existed and about two updates ago there was problem - i cant make any calls. Restarts one helps, and other time don`t help at all. And now - it was no use to restart phone because of this problem. I felt that it might be this problem and i turned off this option and tried to make call - and nothing. Only when i restarted phone again - i can make phone calls normally like before. This problem exists not everytime, it looks like when i make call to my second phone it is only "connecting..." at my note9, and other phone is ringing. And there is two kind of behavior, first - in note i cant hear anything, just this "connecting..." message, and other phone after few seconds hangs up and ask about reconnect. And second - after few seconds after receiving call it finally works but it have take some time between receiving call at second phone and hearing anything. Its lottery.
Now i have this option disabled, phone is restarted and now i can make calls. I contacted Samsung via chat (samsung members app) and via Twitter and they said to me to go to their service to diagnose or sth, but i know what i will hear at service: "please reset your phone to factory settings and if then this issue will be present we will take your phone and try to repair it" but i don`t want to do this because of all this configuration and hours of clicking... I dont like to do this when i dont have to.
So my question - do you have similar or the same problem? Is WiFi calling have anything to do with sim provider?
Click to expand...
Click to collapse
Well need a few things to be able to help.
Carrier?
Model? I'm guessing N960I1?
What is the firmware version you're on?

Jammol said:
Well need a few things to be able to help.
Carrier?
Model? I'm guessing N960I1?
What is the firmware version you're on?
Click to expand...
Click to collapse
Carrier - Poland, Play but not branded phone , model - SM-N960F, FW version N960FXXS2CSD2/N960FOXM2CSA7/N960FXXS2CSD1

DeVilio said:
Carrier - Poland, Play but not branded phone , model - SM-N960F, FW version N960FXXS2CSD2/N960FOXM2CSA7/N960FXXS2CSD1
Click to expand...
Click to collapse
And I'm assuming the carrier Support Wi-Fi calling right? It may be a provisioning issue. You should try contacting your carrier and verify Wi-Fi calling is a feature and that they support it on your device. They should also be able to help you activate it if they support it.

I wrote that it was working normally before, and now it stops. I`ve had this thing working.

Related

Unable to make a call in GSM network - works in 3G

My TyTN II is no more than one month old. Radio and ROM are all stock and I never tried any custom ROMs nor did I install hardSPL on it. The problem is all of a sudden I can't make any calls. If I dial a number it just says Call Ended following with couple of silent beeps. If someone call me they got to my voicemail. The strange thing is that after couple of retries, it works, I can make a call but then after another try, it stops working again.
In all that time, sending and receiving SMS works normally.
And now the very strange part of the problem. If I switch to 3G mode, everything is ok. No problems at all. If I switich back to GSM only mode, the problem is back.
I've contacted HTC in my country (I'm somewhere in Europe ) and all they can say is, hard reset your phone and if that does not work, send it for repair.
I consider that a valid response and I'm about to do just that but before I go and erase all of my applications and settings from my phone (which will take me ages to get them back) I was wondering if someone has previous experiance with this sort of a problem and if it can be fixed without hard reseting the phone.
I have the same issue but when I turn G3 mode ON. I can not make call with auto G3 mode on (I have to try a lot of times to make a simple call). If I use only GSM its works ok.
Zol
I have the same problem, i cannot make a call on 3g network only on GSM. I took the phone to the service and they said i had to change the motherboard it costs ~335 EUR. F*ck
Can anybody tell me an alternative solution?

Captivate Unusual Problem. Please HELP :(

Dear users,
So 2 months ago I returned to Europe from USA. I bought an AT&T Captivate over there and since it could not be used over here, I unlocked it. But after unlocking the phone I noticed an very frustrating problem :
When someone calls me there are absolutely no problems no mater how many times they call.
When I call someone the first time everything is also ok.
But when I try to call someone after I already called once, there is no sound. I can't hear absolutely nothing and neither can the person that is beeing called. Not a sound, not even the "beep...beep" sound (sorry, i don't know how it's called in English) when you are making a phone call.
So basicly I have to restart my phone after every time I call someone to be able to make a call and actualy speak to them, and then restart again.
I hope I described clearly what the problem is. Is there some way I can fix this because it is extreamly frustrating ?
P.S. i'm using Froyo OS.
The Froyo build is Beta - so it could be your problem. Also, the Captivate is still an AT&T phone, so even though it is unlocked, it may not like the network you are using.
You could try the following:
1. Different SIM - different provider
2. Roll back to 2.1

"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?

Help, I can't receive any calls but no problems to make them.

Hello, everyone.
I need help with an issue I'm facing. My phone is not receiving any calls whatsoever and I don't know why. I can make calls without any problems, the issue is that I can't receive them.
I don't know when this started happening since I don't receive many calls, I don't know if it's a result of rooting the phone, because it's rooted, or what else can it be. I don't remember if the phone received calls before or immediately after being rooted.
I've tried flashing different modems but I haven't been successful. Also, I have gone through the settings and disabled everything that could be causing the calls to be blocked. I have also called T-Mobile and they disconnected and reconnected my phone to the network and I have gone to one store to have the sim card replaced and that didn't help either. I have wiped the cache and the Dalvik cache and nothing. The only option left that I know is to factory reset the phone wich I'm trying to avoid because I have a ton of apps and my home screens are already setup and folders created and I don't want to do all this setup again.
Here is the weird part. Under just this specific scenario I can make my phone receive calls.
Make a call to any phone
Hangup a couple of seconds after the other phone starts ringing.
IMMEDIATELY BEFORE the call is terminated (lost) dial from the other phone (the one that was called in step 1). This should be within one second and no more after the call is lost.
If I follow this procedure then the call goes through and my note 4 receives it, but the call shall be made immediately after I hang up, otherwise it doesn't go through.
Does anybody have an idea of what could be happening?
Thanks!!
try this, go to settings all the down to calls and click on call rejection which says auto rejection turn that to off, ive had the Same problem and thats what help me out

Question S21 Ultra sometimes doesn't show that someone is calling me

Hello,
For many months I have had a strange problem with my S21 Ultra, namely it does not seem to show me at random times that someone is calling me, no matter if via the cellular network or some communicators, it simply does not show notifications that someone is calling no matter how is calling. I often have it that only when I pick up the phone, unlock it and check something on it, suddenly messages come that someone tried to communicate with me, and only from then on I can answer calls until I hang up the phone and in an hour or two the same problem - over and over again. I have such an impression as if the phone itself went into some hibernation after putting away, although I have no indications that something like this is happening, because everything looks normal. The phone has the latest update, and I have restarted it several times with no effect.
I would like to add that this happens both in an apartment where I have wifi turned on (I do not use lte calls), and when I am outside while walking in the city.
Is there something I can do to fix this?
This is a very strange issue indeed. Have you checked if your phone has cell coverage when the screen is off? Did you try calling yourself from another phone and number? If the answer is negative to either question, I would suggest resetting your network settings. If that fails, try a factory reset which should solve any issues. If the issue still persists, it could be hardware related and you might need to take the phone to Samsung centre to get it checked.
I don't have a second phone to call myself. Friends say that on their end it sounds like I am not answering the call (i.e. they have a call signal, but just nobody is answering). They have no busy or unavailable signal. What exactly do you mean by a network reset, what would I exactly have to do? I was thinking about a factory reset, but I'm afraid that I will lose all my data and application settings. I do not know if it matters, but I have been using this phone since the premiere of the S21 Ultra, and when I bought it, I transferred all data via the data migration service from the previous S10+ phone, to which a few years ago I similarly transferred data from the S9+, to which I transferred data from S8 + earlier
Maybe you have the "do not disturb" option on? When I have this on, I can't see who is calling me.
I checked, unfortunately it's not that, if it were, I would never see someone calling, but my problem seems to be random.
Sierra76 said:
I don't have a second phone to call myself. Friends say that on their end it sounds like I am not answering the call (i.e. they have a call signal, but just nobody is answering). They have no busy or unavailable signal. What exactly do you mean by a network reset, what would I exactly have to do? I was thinking about a factory reset, but I'm afraid that I will lose all my data and application settings. I do not know if it matters, but I have been using this phone since the premiere of the S21 Ultra, and when I bought it, I transferred all data via the data migration service from the previous S10+ phone, to which a few years ago I similarly transferred data from the S9+, to which I transferred data from S8 + earlier
Click to expand...
Click to collapse
u need to go to settings>general>reset and there tap reset network settings..
Hi,
I experience very similar problem. I tried to reset network settings, "hard" reset the phone, playing around different mobile network settings... nothing helps. I'm not sure if it is phone hibernation issue or kind of removal of the phone from cellular antenna.
I have another phone I use to watch this s21ultra issue. Practically each day it happens that the s21 ultra does not react to my call, of course most of the time it works properly, but there are some tries, when it fails. In such case on the phone I call from I get a message "user is not available". But then, leaving the s21ultra untouched for 10 minutes I get SMS saying that someone tried to contact me, so it is not obvious that the phone hibernated.
I was not able to reproduce the problem on the other sim card put in s21ultra (the carrier is different). I was not able to reproduce the problem on the other phone and the sim card from taken from s21ultra. In my opinion it is related to "weak" mobile signal and kind of "sensitivity" of s21ultra to low signal quality.
I reported the problem to my mobile network provider, but I'm still waiting for the answer. Anyway, I'm going to do the following:
- ask for sim card replacement (cheapest option),
- (if above does not help) go to samsung service and ask to check the phone - I hope they have some diagnostics tools,
- (if above does not help) install the second sim card (from different provider) and configure redirection of calls in case of "user unavailable" - I know it is "stupid" solution - but at least one of the carrier should work
- optionally root the phone - Can anyone confirm if it may help? At least I could enable toggling airplane mode each minute

Categories

Resources