Database Info

XDA I & II does´t dial - "Call ended", "A

I have the following problems:
Last year i bought an xda i which was locked. So i unlocked it & tried the XDA-Special-Edition-Rom and everything worked fine.
Perhaps 5 month later i had the problem that some outgoing calls didn´t go out. the xda even didn`t start dialing and the message "call ended" appeared shortly after pressing the call-button.
So i bought a XDA II via ebay and it started quite good!
but 4 month later the same problem arrived and now nearly no call
can be done and all the incoming calls get directly into the box. afterwards i get a sms notification but i can't phone back! nothing helped (phone on/off, new radio version, hard resets, ...). i'm so angry because
i need it every day and i can't find a solution. the signal strength is nearly full, but i can't make a call. sms works fine.
is it a hardware problem??
i did my sim-card in my old siemens handy and it works well...
please please please help me if you can!
yours,
hansi

the phone is stolen and its eime number has been blocked on the uk networks

i don't think so!
i don't think, it's stolen. it doesn't work in austria not in the uk. and that not always ...
please help me!!
thanx,
hansi

Fuze doesn't receive calls

I've been having a problem with my Fuze randomly not being able to receive text messages or calls.
Sometimes when people call, they say it rings twice and goes to voice mail. All the while, I never hear anything or get a notification. This happened once after I texted someone to call me when they get a chance. They tried 3 times and then texted me back to say that they were getting sent to voice mail. I didn't get notification for either until after I called this person myself 20 minutes later. Right when the call connected, I got notification of a new text message.
Another time, somebody was calling me for 3 days. I didn't know he was trying to reach me until he finally left a voice mail and I got the notification for that (no missed call notifications).
I called AT&T and their tech support did some tests (called my phone) but since it isn't reproducible 100% of the time, they couldn't offer any explanation.
This isn't a bars/signal issue either as this is occurring in the same spot where my Tilt would always receive calls fine.
Has anyone else seen this?

I had the exact same problem with my Sprint Touch Pro & ended my contract early & switched to at&t. Hopefully it's not a fundamental hardware problem.

8notime said:
I had the exact same problem with my Sprint Touch Pro & ended my contract early & switched to at&t. Hopefully it's not a fundamental hardware problem.
Click to expand...
Click to collapse
Did you get a Fuze when you switched? Has that worked better for you? I'm still within my 30 days, so I'm debating exchanging it or just returning it and giving up.

I'm having the same problem. I did a quick search and found this;
This AT&T Forum Post
I tried the workaround and haven't had a chance to really test it yet though. I also noticed a few other settings in there that might have accounted for it.
One selection inside the phone settings had to do with whether calls went to voicemail when you're "Unavailable" or "Busy." I'm not familiar enough with the phone to know when it might tag me as either one so I unchecked both and I'm going to recreate my missed calls this morning.
Someone called after the phone had been sitting on my desk all night so I thought maybe it thought I was "Unavailable" due to inactivity (I dunno, I'm winging it) so I'm letting it idle for a few hours and getting a call later to see what happens.
Incidentally I have the exact same problem, no call coming in, but then I get the voicemail message after I try calling someone.

Unless I'm misunderstanding your point, "Unavailable" just means that your phone is switched off or out of signal, and "Busy" means you are already in a call. It's nothing to do with the behaviour or features of the phone.
Cheers,
Steve.

Yeah, I'm wondering if the phone is becoming "Unavailable" for some other reason than me being out of range. I have full bars in the house and that's where this all happened.
I've noticed, too, that I didn't get any email (I have it set to check every hour, even hit send/receive after someone told me they sent me something and it still didn't find it until I sent a second email to myself from another address)
Again, I don't know much about phones but it almost seems like the phone has bars but drops off the network for accepting calls/messages until you do something to activate the system again... or something. I dunno, just speculating.

Last week I went in and exchanged my Fuze for a new one since it was still within the 30 days. Up until tonight, I thought the problem was fixed. I was chatting with my wife over IM and she told me that she tried to call but that it just went to voicemail. I asked her to call back and leave a voicemail to see if it would notify me. I also asked her to send me a text. I didn't get notification for either. I checked my data connection by starting up Opera and going to a few sites. So I know that I had a verifiable connection to the network. I called my voicemail and checked the message I knew that she had left. Only after I made the call did I get notifications for the text messages I had missed. I never got any notification for the voicemail or missed calls.
Unfortunately, it seems this is a problem that isn't related to individual hardware as this is my 2nd phone with the same problem. I've also replaced my SIM card since a salesperson at an AT&T store suggested that it might help. I'm running the stock AT&T ROM minus the bloat, so it's not a custom ROM issue either. At this point, I'm not sure what I should do.
The only other thing I can think of that makes me unique is that I currently reside in Washington state but my number is one that I had ported from California. Is there anything about you're (skyau) situation that makes you unique?

Well the same thing happened again tonight. I received text messages 10 minutes late and I didn't get a voicemail notification until I initiated a call. As much as this sucks, I'm hoping it will stay this consistent so that I can have tech support replicate the problem and then try and fix it.

You may have a problem with your phone number. I'd try changing it.

Have you had experience with a problem like this? Is the phone number really the issue?
If that's what the problem actually is, I'm willing to get a new number. But I don't want to change it just to check and see if that fixes it.

same problem! Really pissing me off I just lost a important job because of this issue a few moments ago! Is everyone running a stock rom? I tested a few, now back to stock no apps nothing trying to find this gremlin WTF!

I'm running stock ROM without the bloat.
I exchanged my Fuze (I'm now on my 3rd) on Saturday and changed my phone number yesterday. I'm waiting to see if the issue happens again. If it does, I'll probably do stock ROM, all the bloat, no apps. If there are still problems, I'll probably try different ROMs.
I was able to get AT&T tech support on the line when the problem was occurring luckily. We went through his battery of tests and he verified that there was a problem. It would seem that the phone forgets/loses it's connection to the towers/network. Notifications (calls, texts, voicemails) aren't received until after the phone remembers/reconnects to the network. It remembers/reconnects when you initiate a call or send a text (essentially require the phone to use the network).
The tech told me that as far as he could tell, it was a hardware issue and that I should exchange my phone. So I'm on number 3 now and hoping for the best. I changed my number because I've been in a different state for 2 years and I had no ties to previous area code. So I figured now was as good a time as any to get a full fresh start (phone/number/SIM).
That sucks about losing the job.

Bump, I just realized a few moments ago that my phone rings once and then it says missed call, i always assumed they called me and then hung up after one ring in case i was in class or i was busy so that i could call them back. this is not the case? Also a few cases a call will drop every now a then... is this due to the radio rom i flashed? typical symptoms of a incompatible radio for a specific location? I'm using the .25.35 blackstone radio in ithaca, ny.

Having the same issue. Phone is asleep, then alerts me to a VM. Missed call doesn't show up in missed call list.
Really pissing me off and I think is responsible for my issues with Slide2Answer somehow.

The only time I have missed calls is because of MSVC. If someone calls and it is private or unknown, it will not ring. If it is somebody in my phone book or who doesn't have a private number, the phone will ring.
So I turned MSVC off and the private callers and the unknown callers will ring in.

it happens to me sometimes as well sometimes the d pad area will flash but i cant answer and it wont appear on screen then it wont say missed call.
sometimes if i try to hit the dial button it will also drop connection and instantly pick it up again
annoying but not a huge problem for me
and of course not on stock rom

S5 wont Ring on incoming calls?

I can do everything else on it. Text, Place calls, receive text and emails, surf the web. It won't ring calls are going to voicemail. I got a replacement phone from best buy. I have spent 2+ hours with sprint CS resetting and upgrading everything. I'm coming from a S4 that has been wiped.
Has anyone else had this issue? Fix?
Thanks
Phone is completely stock.
Have tried:
Battery Pull
Update Profile, PRL, System update
Did the ##72786# "refresh"
HELP!

Had the same issue where my phone wasn't ringing on calls received. The ##72786# refresh fixed it for me. Has not happened again.

Yeah, i thought maybe I was imagining it but i had like 2 calls go to voicemail from a roadside assistance company i was waiting for call from last night. Thought it was odd but now you say your experiencing it too.

CeloCRF said:
Had the same issue where my phone wasn't ringing on calls received. The ##72786# refresh fixed it for me. Has not happened again.
Click to expand...
Click to collapse
What is the ##72786# refresh? I searched for it but came up empty.

AdRock02gt said:
What is the ##72786# refresh? I searched for it but came up empty.
Click to expand...
Click to collapse
It resets the provisioning on the phone and forces it to re-download the activation settings. Aka kinda like a re-provision.

I'm having the same problem, but only when connected to LTE. Have you tried turning off LTE and seeing if you can get calls? Maybe we have the same issue with our phones/area.

same issue
It's been a while so I assume you resolved the issue.
I have the same issue. Switch to CDMA fixes the issue but then I have no LTE. tried the phone reprovision code. It worked but then stopped working after 1 call.

Same stupid issue
I have this issue and would really appreciate it if someone could share the secret to getting incoming calls.

Issue is with the service provider. In my case Sprint. Turning off Wi-Fi calling and Wi-Fi helps but CDMA only mode for places where there's only 1 to 2 bars for LTE Spark is the solution for now. Call up your provider and let them know about your issue.

Call ended right away? Can't make calls

Hello,
I was wondering if anyone is experiencing this weird hang up. When I try to make calls, it automatically ends my call without any rings. I keep trying to call and it keeps ending right after it dials.
I had to restart my phone to finally get it to work. It has happened twice to me now.

Same exact issue here. Rebooting sometimes works, sometimes doesn't. Tried uninstalling Google Voice, same issue. Annoying as heck.

Same issue here, on T-Mobile. I exchanged my original phone because I was having radio issues (phone would not connect to the mobile network), but this problem seems to have carried over. Phone is set to use WiFi calling, I'm wondering if there is a handover issue when I leave my home wireless network.

I'm on T-Mobile as well, in north Dallas area. I do not have mine set to do WiFi calling, as it is guaranteed to drop your call when you leave your house (happens every time to me, so now I don't bother with WiFi calling).
This instant "Call Ended" issue is separate.

Yup, happened to me earlier, i had to turn the phone off for 15 minutes. Im on t-mobile

Solution!
I believe I have figured out how to fix this. Go into Settings, then More..., then make sure Wi-Fi Calling is on, then click on Wi-Fi Calling then make sure you have Cellular preferred selected. After I did this, I was able to make calls with Wi-Fi on or off. Hope this fixes yours too.

Same issue here. Call hangs up right after i hit dial. Tonight even resetting the phone twice didn't solve. Finally after 20 minutes I was able to make a call. So frustrating as I had an important conference call I needed to be on. I ended up texting a few people in the call, and my texts were successfully received, just couldn't call out. So frustrating, but comforting knowing that I am not alone. Think I might return this phone as this is the 5th time this issue has occurred and I've only had the phone for 6 days.
-Hayden

I have same issue. I turned off VoLTE and problem gone. Hope this helps.
Sent from my SGP561 using Tapatalk

qarbonite said:
I believe I have figured out how to fix this. Go into Settings, then More..., then make sure Wi-Fi Calling is on, then click on Wi-Fi Calling then make sure you have Cellular preferred selected. After I did this, I was able to make calls with Wi-Fi on or off. Hope this fixes yours too.
Click to expand...
Click to collapse
Sorry, that is not a fix. I've used that configuration and still ran into the instant call ended problem. Thanks for the suggestion though.
---------- Post added at 07:44 AM ---------- Previous post was at 07:41 AM ----------
ngvuanh said:
I have same issue. I turned off VoLTE and problem gone. Hope this helps.
Sent from my SGP561 using Tapatalk
Click to expand...
Click to collapse
VoLTE (voice over LTE) could actually be the problem - that is a setting that comes pre-enabled and I never disabled it. Makes sense to try disabling it and see if it happens again.
I'll report back in a couple days whether the issue happens again with VoLTE disabled.

Man I really like this phone, but the call ending and camera issue, I had to return it. Damn you sony!

asianizeboy said:
Man I really like this phone, but the call ending and camera issue, I had to return it. Damn you sony!
Click to expand...
Click to collapse
The call ended issue hasn't happened to me since disabling VoLTE. Though I did get a call from my wife when she got off work, which when I swiped to answer, my phone rebooted.. that was fun.

simplyphp said:
The call ended issue hasn't happened to me since disabling VoLTE. Though I did get a call from my wife when she got off work, which when I swiped to answer, my phone rebooted.. that was fun.
Click to expand...
Click to collapse
It only happened to me once. Rebooting had no effect, but after turning off LTE everything worked. Makes sense that it would be a VoLTE issue.

you can try fiddling with the network mode settings in the more wireless/network option. the t-mobile rep. got it working again after switching the network preferences from LTE Preferred to GSM. That got calls working again. I believe I switched it back to LTE afterwards and I'm not experiencing any more problems with that error.

Same here. It was totally random as to when and how long it would automatically end calls.
VoLTE settings made no difference. Eventually the problem would return.
I just replaced it at the TMobile store.

Problem Solved!
So, I was having this same problem and reading this forum, I discover that I just need to change the network mode
Go to settings > More... > Mobile Networks > Network Mode
And it probably its marked LTE (only).. Just change it for LTE(preferred)/WCDMA/GSM
I hope it can help you

I have HTC One M7 with cm12.1 and I'm having this issue too!

Nexus 5 Drops Received and Made Calls

Hey guys,
I have a Nexus 5 running 5.1 stock with an LTE connection in La Paz, Bolivia. Most of the time when I make a call or receive a call, the call is dropped. I have observed that as soon I make the call (with full reception bars) the LTE legend switches to E and then 20 to 30 seconds later, the reception bar dissapears and then the call is dropped.
I was hoping that with 5.1 update the issue will be resolved but nothing has happened.
I have contacted my carrier several times and my APN settings are correct and they haven't been able to troubleshoot the problem with the connection.
I would truly appreciate any ideas that you might have to solve this issue!

Ok, so after looking at several threads in Google Support for the Nexus 5, I tested a solution in which you booted the phone in Safemode and voila, my phone would not drop any calls and LTE would work just fine.
The problem is that Safe Mode does not allow loading anything but the core applications, so I can't use the apps that I have installed.
At this point, I think I have a software problem in which an app or a process drops the calls.
Do any of you have any ideas on how to diagnose which app or process is creating the problem?
Thank you
dcab said:
Hey guys,
I have a Nexus 5 running 5.1 stock with an LTE connection in La Paz, Bolivia. Most of the time when I make a call or receive a call, the call is dropped. I have observed that as soon I make the call (with full reception bars) the LTE legend switches to E and then 20 to 30 seconds later, the reception bar dissapears and then the call is dropped.
I was hoping that with 5.1 update the issue will be resolved but nothing has happened.
I have contacted my carrier several times and my APN settings are correct and they haven't been able to troubleshoot the problem with the connection.
I would truly appreciate any ideas that you might have to solve this issue!
Click to expand...
Click to collapse