Database Develop

Serious reception problems

I'm experiencing reception problems with my phone. The first two weeks this was not a problem but end of last week and yesterday and today I'm having troubles with the phone. I have between 2-5 bars (average 3) when talking and I'm always calling from the exact same location and same room (working from home).
The problem is that after a few minutes I can't hear the other person. The person calling me can hear me without problems but I can't hear him. So I hang up, call back and the same happens after a few minutes.
I have tried with and without headset and also tried to soft reset it without result. Any ideas what to do? Anyone else experiencing the same problem?

Laban said:
Any ideas what to do? Anyone else experiencing the same problem?
Click to expand...
Click to collapse
No idea sorry! But I don't have that problem. Do u have a SIM card from another provider to check?

Mar'Cel said:
No idea sorry! But I don't have that problem. Do u have a SIM card from another provider to check?
Click to expand...
Click to collapse
Yes, I might be able to try that or I'll try to get it replaced. Looks like no one else is experiencing the same.

I to am having some serious Reception issues but im with Optus in Australia. When on 3G at home.. cant make or take calls. So i have turned it to just GSM so i can get calls and make them.. Sometimes I did get calls and messages on 3G at home.. but today, it just wouldnt do anything..
There are updates from other counties which seem to have a radio update.
http://forum.xda-developers.com/showthread.php?t=514092&page=1

Hi,
Is there any way just to extract the Radio upgrade ?
I have my Diamond 2 in french, and want to keep it like that.
I wrote to the french HTC Support, and they just ask me to :
- Hard reset the phone : Done and useless
- Change the sim card : not done as the sim card I used is completely new
- Disable encryption : disabled and useless....
So the only solution will be a radio upgrade only.
Thanks
F.

Peoples can't call me...

Hello everyone. Usually when somebody trying call me, then hear this message: "We can't connect your call. Please try again later". I'm using a stock rom (Android 2.3.3), and i think it was started happening after update or i didn't know about this issue before. I tried reset phone to the factory defaults, change the sim cards, run the sim card in a different mobile and i had the same symptom.
Maybe someone has any idea what might be causing or had the same problem?
Try several times call on Your mobile from a diferrent phone and check it for me plase, maybe it is a bug in a software ??

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

Note 9 WiFi Calling - can`t make calls but receiving works.

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.

Question 😠 SIM1 is dead after upgrading to UI 5.0

Hi,
After OTA to A13 (5DVJA) SIM 1 is dead most of the time.
People say they can't call me, they just leave a message.
I get a text message that somebody called me......
Never had this problem before.
Hard reset did not help.
Anyone else had this problem?

My S21 Ultra has issues, and both sim cards don't work anymore. I had to reset settings factory reset still no joy.
I left my sim in, and after several hrs, it started working!
I also set up wifi calling, which helped, and it activated the sims.
However, the reception has been extremely poor so something has been damaged by the update, I assume.

qwerty1q said:
Hi,
After OTA to A13 (5DVJA) SIM 1 is dead most of the time.
People say they can't call me, they just leave a message.
I get a text message that somebody called me......
Never had this problem before.
Hard reset did not help.
Anyone else had this problem?
Click to expand...
Click to collapse
Also, try resetting network settings

riz157 said:
My S21 Ultra has issues, and both sim cards don't work anymore. I had to reset settings factory reset still no joy.
I left my sim in, and after several hrs, it started working!
I also set up wifi calling, which helped, and it activated the sims.
However, the reception has been extremely poor so something has been damaged by the update, I assume.
Click to expand...
Click to collapse
It doesnt changes anything. Also Wifi calling is useless for me as nativ call recorded doesnt record call via wifi.

qwerty1q said:
It doesnt changes anything. Also Wifi calling is useless for me as nativ call recorded doesnt record call via wifi.
Click to expand...
Click to collapse
Wifi calling could fix the issue. Once done, you can turn off wifi calling.
Put the phone in aeroplane mode, then turn it off
Take sim tray out turn the phone off, insert sim tray then turn back on

others are reporting the same - you're definitely not alone
Nothing else works If under warranty, send to Samsung to repair

let me know if any of the solutions work