Database Develop

Calls not coming through

Hi, gang. I've been surfing the forum silently for a little while and got my G1 all rooted and hacked the other night. It's been awesome and thus far I've been able to resolve any issues I've had in the process.
This one is throwing me off but I know someone has run into it before. Sometimes when someone calls me, they say that it rings twice and then goes to voicemail. I never get any missed call notification or anything. It's like the call never existed. After testing, I found that data transfer is taking precedence over voice data when they both try to come through at once. It's really annoying!
Does anyone know of a way to reverse the importance of these 2 things? Obviously I want to receive my calls if they happen to arrive when data is transferring. My phone constantly accesses some sort of data throughout the day (only texts and email).
For reference:
- White T-Mobile G1
- ROM: OpenEclair v1.2.1 BACONWEAVE
Thanks in advance.

No one else has run into this? A friend said I could try a wipe and re-flashing the ROM and see if that works. I'm thinking of going back to Cyanogen and seeing if the problem occurs with that.

Roaming in Citrus Springs?
Check Settings/Wireless & Networks settings/Mobile network settings/Data roaming. The choice is to connect to data services when roaming. This should not be selected.
Regards

David,
I totally overlooked that setting. Before my phone was rooted, I apparently had disabled this but failed to do so after modding. I just tested it by loading a website in the browser and making a call to it while it was loading. The call came through without a hitch!
Thanks a lot. I had searched high and low but no one ever mentioned this. I thought I had already tried it actually, but I was wrong. Much appreciated.

Okay, apparently it was only a partial fix. If wifi is enabled, the web browser just defaults to using that (obviously). When I disabled wifi and loaded a webpage while calling the phone, the call went to voicemail after 2 rings and never showed up on my phone.
I've never had this happen before. I've only seen this after flashing everything required to root the phone. It's not a huge deal but it baffles me. I guess when you're not on 3G, it only allows data through if both voice and data are trying to transfer at the same time.

No Data While in Phone Call

While I'm in a phone call, I can't access the internet or data. Is this a known bug? If I remember correctly, you could do this before 1.6 on the G1.

You can't do it on the G1. It's one of the facts that Apple/AT&T uses against Android/Verizon. It's a known bug I think, if you consider it a bug? It sucks because while my I'm Tethering and I get a call I have to wait until the other person hangs up.
Does my name make you think I bricked my G1?

are you using the g1 or the nexus one?
anyways i have the att n1 with att service, and phone call and data works fine. i just tested this right now, was browsing around the market while leaving a message on my house phone. Have to make sure that im on 3G/HSDPA though. wont work on EDGE. i dont know about tmobile being able to do the same thing.....
I have rooted and using cyanogenmod 5053 rom. It was also working with the stock nexus one. i tried this out the first thing when i pulled out the phone from the box.

Any phone should work with data as long as its a 3G or higher connection. if your on 2G/Edge or worse, sorry not going to happen. Perhaps two phones like the ATT v Verizon commericials?

I have a Nexus. I'm pretty sure I could do this on the G1 prior to Donut. This happens to me on 3g. Should be able to access data over wifi in a call but no go.

Im on T-mobile and my nexus browses just fine when im talking on the phone

Missed Calls

Hello,
I'm on EE UK network and I keep getting text messages that i've missed a call even when i'm at home where i'm connected to wireless and also have 3 or 4 bars signal.
don;t understand why this keeps happening. I try calling my phone from another mobile and it works OK.
Any one know why this might happen?
Thanks

Are you sure its recent calls? Depending on your carrier it might log it and send it as a reminder later or something like that.

Iwannagiv said:
Are you sure its recent calls? Depending on your carrier it might log it and send it as a reminder later or something like that.
Click to expand...
Click to collapse
yes very sure, just had a msg saying a mate tried calling 4 minutes before the text arrived. called him back and asked if he tried calling. he said yes.

tauran said:
Hello,
I'm on EE UK network and I keep getting text messages that i've missed a call even when i'm at home where i'm connected to wireless and also have 3 or 4 bars signal.
don;t understand why this keeps happening. I try calling my phone from another mobile and it works OK.
Any one know why this might happen?
Thanks
Click to expand...
Click to collapse
Problems like this are quicker to fix by wiping your phone, if you have data you want to backup either use titanium backup or do a nandroid backup (build into CWM)

Magik_Breezy said:
Problems like this are quicker to fix by wiping your phone, if you have data you want to backup either use titanium backup or do a nandroid backup (build into CWM)
Click to expand...
Click to collapse
I've wiped the phone but just found the problem still exists, any help with this will be appreciated. It's very annoying that people cant get through to me.

I read somewhere that the problem might be something to do with the 4g network. the network needs to switch from 4g to 3g to receive voice calls and if it doesn't switch quick enough, it results in a rejected/unconnected call but gives me a text to say someone couldn't get through.
is that possible?

I also have the same problem. While I was holding my device which had three bars of signal ,I was calling my number from a friend and kept getting the msg that it was not available, ..after 2 mins I received about 5 "missed call" messages. I think it's problem of EE though.
Sent from my GT-I9305 using xda app-developers app

[Q] Can Anyone Reliably Make and Receive Calls?

I recently switched from an iPhone 5 to the One Dev Edition. After having some signal issues, I went to AT&T, got a microSIM, they switched me an Android data plan, etc. But I'm still having an issue where I can't reliably send and receive calls, especially from my desk at work. I can dial the number and hit Call but that's it. No ringing, nothing. Just dead air, then the "call" ends. If the call does go through, I can hear the other person but they can't hear me. Same thing when receiving a call. I'll hear them but they can't hear me. Sometimes my phone won't ring and it just rolls to voice mail. I can see the signal switching from LTE to H, etc, and I have practically full bar strength. I just don't understand why the calls aren't going through.
Is this an issue with the phone itself? Something with AT&T? Is there a newer radio firmware I can try flashing? I didn't have any issues with the iPhone 5, and I even had my coworker put his iPhone into field test mode so we could compare the numeric signal and they're about even, though the iPhone usually does have a slightly better db signal. I really like the One but not being able to send or receive calls while at my desk is a deal breaker.
Thanks!

From the sounds of it, you are running the stock firmware still? Any root or other possible modifications? If you answered Yes then no to those questions, I would head back to the AT&T store and have them try it out, if anything they should be able to take your SIM card and put it into another Android device and see what happens.
What about text/data, do those work?
You said mainly at your desk you notice this issue, so does that mean it happens at other places as well, same symptoms (full bars, allows to send call then nothing?) You may just be the lucky contestant with a defunct unit, HTC should be able to help you out.
I would suggest first going to AT&T store, try out their suggestions, then if anything give HTC a call/email to see if they can be of any help. At this point I would stay away from flashing custom radios as they may void your warranty then you will really be up $hit creek.

Sounds like att.
I had this problem with tmobile once. The signal wasn't strong enough and it wouldn't call.
Some please are spotty.

Something is wrong with your phone. That should be obvious. Of course the vast majority of people who got this phone can reliably make and receive calls or it would be the biggest mobile phone bust in history.
Sorry to be blunt but you already know it's not the signal so it has to be a defect in the phone.

Thanks for the suggestions. This is the stock Dev Edition ROM. I haven't made any changes other other than just installing apps.
I haven't made a lot of calls but I don't seem to have an issue any where else.
No issues with LTE. Data has been fine.
I wasn't sure if AT&T would assist since this is the Dev Edition but that's worth a shot to have them run some tests on it. Otherwise I'll try to get a replacement (or refund) from HTC.
Thanks!
Sent from my HTC One using xda premium

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