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?
Related
I seem to be having issues using Data when I'm on a call. I'm on T-mobile in San Francisco running 2.2.1. Does anyone else have this problem or know how to remedy this?
Contrary to T-Mobile's position that I can do data while on a call, I typically have the same issue as you. I've only been able to get online a few times while on a call. Usually there's no data connection available.
Sent from my Nexus One using XDA App
You can only use data during a call when you see the little 3g symbol at the top near your signal bars. If it shows E, then you can't.
I am not sure if the problem has anything to do with being on T-Mobile. I'm in India & I have observed that on all versions of android, there seems to be a problem in following cases :-
1. Making a call while an sms is being sent out. Try it, and your sms would be returned undelivered & call would not get through. You'll have to reboot the phone to make it work again.
2. Try making a call while data transfer is on. It fails.
3. If some one calls you while data transfer is on, he gets a busy tone.
I started off on my Nexus One with 2.1 & I'm currently on 2.2. My friend who owns a galaxy s and is on 2.1 also has the same problems.
None of these problems existed on my nokia e90.
seventyfivein said:
I am not sure if the problem has anything to do with being on T-Mobile. I'm in India & I have observed that on all versions of android, there seems to be a problem in following cases :-
1. Making a call while an sms is being sent out. Try it, and your sms would be returned undelivered & call would not get through. You'll have to reboot the phone to make it work again.
2. Try making a call while data transfer is on. It fails.
3. If some one calls you while data transfer is on, he gets a busy tone.
I started off on my Nexus One with 2.1 & I'm currently on 2.2. My friend who owns a galaxy s and is on 2.1 also has the same problems.
None of these problems existed on my nokia e90.
Click to expand...
Click to collapse
1. Never tried, but happened to receive calls with SMS being sent. Worked.
2. Works fine.
3. Works fine. Moreover, I happen to use a lot of tethering, and tether for hours while talking on the phone - calling people and getting calls.
I guess it's your carrier to blame, not the OS and not the phone(s).
To the OP: as everyone said and will say in this thread, watch for your connection. Having 3G signal is a requirement.
chronopc said:
I seem to be having issues using Data when I'm on a call. I'm on T-mobile in San Francisco running 2.2.1. Does anyone else have this problem or know how to remedy this?
Click to expand...
Click to collapse
You must be in a 3G area for simultaneous voice and data.
seventyfivein said:
I am not sure if the problem has anything to do with being on T-Mobile. I'm in India & I have observed that on all versions of android, there seems to be a problem in following cases :-
1. Making a call while an sms is being sent out. Try it, and your sms would be returned undelivered & call would not get through. You'll have to reboot the phone to make it work again.
2. Try making a call while data transfer is on. It fails.
3. If some one calls you while data transfer is on, he gets a busy tone.
I started off on my Nexus One with 2.1 & I'm currently on 2.2. My friend who owns a galaxy s and is on 2.1 also has the same problems.
None of these problems existed on my nokia e90.
Click to expand...
Click to collapse
i dont get those errors, and i've specifically tested making a call while transferring data, and many combinations of that.
i have never, though, tried the sms send and call test. i'll have to try that out.
anyway, the nexus one can use data during a phone call on the 3G network. if you are connected to EDGE then it will not work and the data will pause.
My phone does show a 3G signal and I still can't do it. I know that T-Mobile throttle the speed. Do you think it has to do with throttling?
chronopc said:
My phone does show a 3G signal and I still can't do it. I know that T-Mobile throttle the speed. Do you think it has to do with throttling?
Click to expand...
Click to collapse
it must be some isolated case with your spcific sim card or something. when connected to 3g you absolutely should be getting simultaneous voice and data, its very well know. not sure what else you could do.
This is weird. Ive always been able to get simultaneous voice and data. Never had a problem.
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 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.
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?
Ok, I've got a problem that just started happening the last week or two. When certain people call me, I can answer. However my phone always hangs up on them 1 second after the call. The behavior is the same, based on the number calling me.
For instance, if my wife calls me from her cell phone (Sprint iPhone 5S), it will always hang up immediately after answering.
If my wife calls me from our house phone, it always works like normal.
This so far as I can tell, only affects inbound calls. I have no issues calling out.
Running latest OTA. I've updated PRL and profile, and it made no difference. I've never rooted the phone or messed with S-on/off. Pure stock. I have rebooted the phone into safe mode, and the same behavior is present.
Interestingly enough, I'm also on Sprint, I have a Nexus 6 and my wife a Note 4, and we've had the same issue over the past week or two. She can call me and immediately after answering the call will end. This has happened with her calling from her cell phone and her office phone, both of which are attached to her contact. I can call out with no problem, and I've tested calling my phone from different numbers and had no problem. No clue whats going on.
Are one (or both) of you using Sprint's Google Voice integration?
shawndoc said:
Are one (or both) of you using Sprint's Google Voice integration?
Click to expand...
Click to collapse
I am having the same issues when my mom (S4) whose on the same contract as me, calls me (S6 edge) it always hang up immediately after I pick it up. I have no issues calling her though. I am using Sprint's Google voice integration but I do not believe my mom is.
It is the Google Voice integration that is causing the disconnects.
See here:
https://productforums.google.com/forum/?utm_medium=email&utm_source=first_post_notification#!topicsearchin/voice/sprint$20integration|sort:relevance/voice/NxkMd3YpzSw
I'm having the same problem with a Metro PCS phone. I've seen it elsewhere on line - it's some Android issue.