I have brought two phones to the UK. Both of them are Samsung Captivates, one of which has Eclair, and the other has Froyo. I recently purchased a SIM card from the 3 (Three) Network and except for a small APN problem. Everything seemed to be working fine. Recently, I've been periodically unable to make calls from either of the phones. Text messaging and internet over the 3G network work fine, but when I try to call, it looks as though it connects, but I can't hear anyone and they can't hear me. If a friend calls me, I do see an incoming call on my phone, but when I pick up, we can't hear each other. I've noticed that when I reboot my phone after having the SIM card removed for a while, it connects for the first call made, and both people can hear each other, but after that first call, it goes back to not working. Has anyone here had a similar issue, or have any idea what could be causing this?
By the way, I was on the phone with 3 (Three) customer support, and they had me completely reset one of the phones, and the problem still happened. Also, I put in a SIM card that I knew was working, so it seems to me that it must be some weird compatibility issue with the Captivate, although I can't imagine why, because it's a phone almost exactly like the i9000 in Europe and the UK, and should be able to work fine with any network.
Related
My first full day using the phone. Hadnt had an issue until this evening. For some reason i can not make a call. Im in an area that only gets edge, but it shows i have three bars. When i try to make a call it never rings or says connected, it simply ended after about 7 seconds or so. I can however browse the internet or watch my slingbox on the phone so it seems my connection is good. I tried a hard reset, but issue remains. If i try to make a call it will go through maybe once out of every 20 attempts.
I saw a few similar threads, but nothing like this. Anyone have any thoughts?
apparently there is a huge outage in the NYC metro area with cingular. So, thankfully its not the phone. way to go cingular!
im having a similar problem on fido in Vancouver, tho i dont think its as bad as yours. intermittent phone use at best.
I am having the same problem as well. It just says dialing but no tone. I remove the battery and it works again. But a day later and then it starts to act up again.
I was advised to update my sim card since its 3 years old now.
I am with Fido in Montreal Quebec Canada.
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
I have a Samsung Captivate from ATT with stock Froyo (Android 2.2). I am using a T-Mobile prepay Sim Card with the phone (no 3G/data plan). I have rooted and unlocked the phone, and initially (for several days) the phone worked perfectly without problems.
I took a trip from the US to Vancouver, and while in Vancouver, I texted back and forth a few times to the US and made one phone call (Rogers Network) without problems, using data roaming. When I returned to the US, my problem began. I can still text without problems, but when I make a phone call, my reception consists of mostly or all static through the earpiece, speakerphone or earphones. The person on the other end can hear me perfectly, but I receive static. I also receive static when I dial up voice mail. My earpiece and earphones work OK with music and voice recordings.
There have been a couple of occasions where the static went away and I do not know the reasons for this (the static later returned). Other than the static, I have no other apparent problems with the phone.
I have tried a factory reset and that did not correct the problem. I also installed the simcard from my husband's iphone, and the problem was the same (static on reception). I was wondering what else I could try to correct the problem:
1) Should I reinstall Froyo or some other ROM? How would I do that with a rooted and unlocked phone?
2) Could it be a modem problem? How can I check for this?
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?
I've had an issue twice now where I can't make or answer voice calls. When I answer I get nothing but silence, and the other person says it keeps ringing, and when I call I get nothing but silence (no ring or anything on my end, but it does ring for the person I'm calling.). I updated to the OTA after getting it yesterday, and things seemed to be fixed, but today it is doing it again. I have great signal (both LTE and the older network), IMS registered, and not roaming. Has anyone else had this problem? It is extremely frustrating.
Edit: Texts work, mobile data works, everything except calls.
I've noticed the call quality on 1X has been pretty poor. Also, I've had call roaming pop up a couple of times where I've never had any problems in the past. I haven't experienced exactly what you describe tough. We need VoLTE, and we need it quick.
It's still going today. I'm going to take the phone back to Verizon. Completely unacceptable.
Update: Verizon swapped out two SIMs and still couldn't figure it out. Sending me a brand new one.
Sent from my XT1254