Hello,
Some time ago I bought a Motorola Droid 3 from Verizon.
As I live in Europe I unlocked it (bought a code on ebay).
I also flashed it with some radio ROM which was for a europe version of the phone.
I restored a stock ROM.
Sometimes when I try to call someone when I hit the Dial button it just starts to 'dial' shows connecting and freezes like that.
All the buttons seem responsive but whatever I click nothing happens
It just stays on connecting I can`t close this I can`t disconnect I can`t do anything other than Power off the phone and then power on again (the Power off is the only button which works normally).
Sometimes when someone tries to call me he/she receives a message that my phone is currently turned off...
I think there`s some problem with the GSM module it just freezes (no data is transfered, no calls can be accepted or no outgoing calls can be made)
When I reboot the phone everything works normally
I tried with many different ROMs but the issue is the same.
I was looking for some other Radio ROMs which I can use but I couldn`t find any.
Does anyone have any Idea what may cause this issue?
what model is listed on label under battery? XT862?
in Menu>Settings>About Phone
which system version is on phone? 5.7.906
which baseband is installed? N_03.18.29P
Related
My TyTN II is no more than one month old. Radio and ROM are all stock and I never tried any custom ROMs nor did I install hardSPL on it. The problem is all of a sudden I can't make any calls. If I dial a number it just says Call Ended following with couple of silent beeps. If someone call me they got to my voicemail. The strange thing is that after couple of retries, it works, I can make a call but then after another try, it stops working again.
In all that time, sending and receiving SMS works normally.
And now the very strange part of the problem. If I switch to 3G mode, everything is ok. No problems at all. If I switich back to GSM only mode, the problem is back.
I've contacted HTC in my country (I'm somewhere in Europe ) and all they can say is, hard reset your phone and if that does not work, send it for repair.
I consider that a valid response and I'm about to do just that but before I go and erase all of my applications and settings from my phone (which will take me ages to get them back) I was wondering if someone has previous experiance with this sort of a problem and if it can be fixed without hard reseting the phone.
I have the same issue but when I turn G3 mode ON. I can not make call with auto G3 mode on (I have to try a lot of times to make a simple call). If I use only GSM its works ok.
Zol
I have the same problem, i cannot make a call on 3g network only on GSM. I took the phone to the service and they said i had to change the motherboard it costs ~335 EUR. F*ck
Can anybody tell me an alternative solution?
Hello all,
I installed the official 2.03.404.2 NLD ROM on my HTC Touch Diamond.
(Radio version is 1.09.25.23). I didn't use the backup utility to restore my settings afterward, instead I installed my few applications by hand again.
I configured the phone to only use GSM, both to conserve power and costs (I have wifi both at home and in the office).
However, with this new ROM, often the phone becomes unresponsive to incoming calls. It happens often after the power management puts the phone to sleep whilst I have an active wi-fi connection using Opera.
People who try to call me then get my mailbox, even though the phone is ON and everything looks normal on the display. Crazy enough, the Diamond itself can make phone calls without problems, and then I'm immediately flooded with text messages from my provider telling me there are messages on my mailbox.
I now make dummy phone calls several times daily just to be sure the phone remains logged into the network, but this really sucks. Does anyone else experience this?
what network are you using?
T-mobile NL over GSM.
But the problem coincides with the installation of the new ROM.
I have exactly the same ROM / same Radio / same provider (T-Mobile NLD) as you have, and I don't have this problem (at least, not that I know off). I also have the phone in GSM mode almost always instead of 3G mode. So I think it's not a bug in the rom. However, there is already a newer rom available than the one we have, so maybe you could try upgrading to the latest?
I have ROM version: 1.93.720.2 WWE (Radio version: 1.00.25.07) on my HTC Diamond. I have never modified or upgraded my ROM. I face a similar kinda problem as yours. The only difference is that it happens once in a day and that too early morning. So I have to make a call to any no. to wake my phone up. This sounds funny but yeah I m facing this problem. Is it bcos of ROM version? Whats the latest ROM version for HTC Diamond? How can I update it? If I update ROM will I lose all my data. Please hlp I m new to this.
I m from India and using AIRTEL network over GSM.
@Suchit_g:
Early in the morning, you mean shortly
after pulling out the charger cable?
Sounds like a power management prob.
@Drazix: Thanks for the info about
the new ROM, I will try it out.
Hmm bobokonijn
Even I thought so but this happens even if my phone is not charging. I charge my phone once in two days but this happens almost every morning. The 1st call of the day should be made by me. If I fail to call, my callers get the unavailability message even if my phone is on and showing network signal bars. My phone starts working only and only if I use network (either call someone or use GPRS) for the 1st time in the morning and then for the rest of the day my phone works without any problems. Hope someone can help me out with 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?
Hello! I am having some issues with upgrading from 4.4.2 (CloudyG2) to 5.0.x. I have installed the modem (as it says that you have to, and I don't feel like bricking my phone xD), and I have double checked that I installed the correct one When I boot up the phone, I can only make 1 call before having to restart my phone - after making that one call, the phone still works fine - I can't make another call. When I try and click the call button the second+ time after entering the number, it simply sends me back to the dialer "home page". I at first thought that it was the but after trying it with another I believe that isn't the issue. Then, I thought that the kernel (Render Kernel) was the culprit, so I tried it without that specific kernel with the exact same result. From that point, I started thinking that the Google Apps (PA) had a connection, so I tried it without the Google Apps, with the exact same result. At this point, the only thing that I haven't changed is the modem - I had to downgrade from 24A to 12B in order to install the 4.4.2. Does anyone with a Verizon VS980 LG G2 have any sort of solution? Thanks!
Update: It seems that if I make a call every time it restarts and make sure that the first call doesn't properly connect, calling has no issues afterwards.
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.