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
Related
I am currently abroad in London. I have unlocked my Captivate to work on a local network, Orange, with a pay as you go plan. Recently when 2.2 was released I used Kies Mini to upgrade, it went fine. However, now I can't use the phone for calls!
When I make or receive a call, its as if the phone is muted. I can't hear a thing, not static, ringing, or the other person when then answer (yes the calls go through), and they can't hear me either. It's very strange. However, I have tested both the mic and internal and external speakers with other apps and they work fine.
I have tried downgrading and re-upgrading and even doing a reset with Odin but it does not help. Strangely enough, when I first upgraded calling worked off and on (1 working call for every 3 silent calls) for about a week, then stopped alltogether.
Any suggestions? I really need this fixed fast. Could this be a SIM card issue?
Hi, I had the same issue, and it was with an Orange prepaid sim card. I unlocked my phone prior to the trip, and I had the same thing with every other call had no audio whatsoever but the SMS still worked. I wonder if somebody had a custom rom that worked fine with Orange
joeyl said:
Hi, I had the same issue, and it was with an Orange prepaid sim card. I unlocked my phone prior to the trip, and I had the same thing with every other call had no audio whatsoever but the SMS still worked. I wonder if somebody had a custom rom that worked fine with Orange
Click to expand...
Click to collapse
Yeah exactly SMS works just fine. Well that sucks, what a strange issue! I wonder if there's some sort of fix for this?
Surely somebody else is using an unlocked Captivate with those pesky Orange pay as you go....
I can't say it'd be a fix or anything, but on some roms, I sometimes have to enable speakerphone, and then disable it. I doubt it'd be a fix for your issue, but it's worth a try
Twicebak3d said:
I can't say it'd be a fix or anything, but on some roms, I sometimes have to enable speakerphone, and then disable it. I doubt it'd be a fix for your issue, but it's worth a try
Click to expand...
Click to collapse
OP did you try that? That would be too easy if it was it. I flashed my phone to a new ROM but I cannot try it until my brother sends me the international Orange sim
Well as the titel says,
since about 1 week I'm facing the problem that i can't receive calls when my phone is locked.
I found a similar thread which is saying thats because of a signal-loss. The strange thing is, that i do have full signal!
If my phone isn't locked all is fine and i get calls, it's only when it's locked. If somebody is trying to call me, only mailbox is answering and just in time i get a sms that there are missed calls.
Does somebody else have this problem, or an idea how to fix this?
btw. I'm on faria rom v5.1. and don't rly want to chance the rom, as I'm pretty happy with this one (except this problem)...
Thanks for your help in advance
cheers, Rob
I have similar problem. No only can't be called, also i can't place calls. It is a strange situation because after restart i have no network. After 2 or 3 restarts i have network. I can't find a solution yet. I sent back to service my phone under warranty and they told me that the situation described by me is not confirmed. In service phone is working normally.
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?
So I bought my Note 5 N920K off eBay. The first few days it worked fine. I would say the first few weeks. Then one Saturday I was on a call and suddenly I could hear the person on the other end. I tried to call back but when the call connected, there was still no sound. I toed another phone and completed the call. I then tried to call VM as a test call. I could hear the welcome note in the first 5 seconds and then it just went quiet. I tried this again and the same results, I tried the SIM card in another phone and it worked fine. I tried another SIM card in the note and same problem. I know of someone who had a Galaxy S5 G906k with similar issues but it went away eventually. Can anyone point me in the right direction as to if this may be a HW or a SW problem?
Any assistance would help. Let me know if any additional info is required to assist.
i believe somehow related to kernel problem. I got the same situation here. It will be solved by flash stock firmware via odin.
you can find stock firmware in below link:
http://www.sammobile.com/firmwares/download/53827/N920KKKU1AOH6_N920KKTC1AOH6_KTC/
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.