Related
I have the Bell i9000M unlocked and used with Rogers SIM. Nothing else has been done to the phone besides installing apps (got the sd corruption on my first i9000m after using Odin and didn't want to go through that again).
Haven't had any problems for over two months but in the past week, I have dropped calls and could no longer make calls again until I restarted the phone. I have dropped calls before (there's always a couple of areas on my drive home where I drop calls using any phone) and have always recovered. But just this past week, I can no longer make or receive calls after a dropped call.
Sometimes the status bar shows the blue circle with a slash, but that changes to white bars. But even with bars I can't make or receive calls. When I check *#0011# it doesn't show that I'm attached to a network.
I can go to an area with strong signal and leave the phone for hours but still cannot make calls. The only solution for me is to restart the phone.
Anybody have this problem and know how to fix it? I've been searching for days but haven't seen a solution.
Thanks,
yvrRome
Sent from my GT-I9000M using XDA App
I had the exact same problem on my first 2 I9000M's. The only thing I ever found was to replace them. It was annoying as hell and made the phone impossible to use sending or receiving calls. the second one was JH2 with the 3BR fix. Texting was perfect as was the internet (3g).
I searched and searched as well. But I was talking with a bell guy about it and he said it may have to do with an IMEI issue they have a master ticket open 3449667. I know you are on rogers now, but hope that helps in some way.
Thanks, it is very frustrating and dangerous since I'm usually driving when this happens. Unfortunately my 60 days are up and I can't get a replacement. There must be a way to fix it since it was working before. Maybe a SIM issue? I'll keep searching and hoping and if nothing, then I'll do a reset before sending for repair.
Sent from my GT-I9000M using XDA App
Just to update, I got a new SIM card and I don't have the problem anymore.
I got my Optimus 2x Today, the one from Netherlands. And I have a big problem. I can't make calls. When I dial the number, it is calling and after 10-15 seconds it disconnets. Happens everytime, anywhere i call. I tried Hard Reset 2 times, but it haven't fixed that problem.
And also I can't send massages, they are just not send, and there appears that ! warning yellow triangle.
I switched my SIM card back to my old phone (I8910 Omnia HD) and everything works on it like a charm...
I don't know what to do now
You would need to add your providers account information to your phone. I'm far away from being a specialist in these things, so please wait for some one else to help you. But it's not a big deal to get your phone running properly.
Slap me if I'm wrong.
Kind off experiencing the same, although it is not constantly, but intermittent for me. however when phone calls start to fail they keep on failing, untill i pull the battery after which it works for awhile.
I am now having this with wifi aswell ....
Was i too ambitious removing those apps, following that other thread ? ill install a different launcher and see if that changes anything ....
ZajacPL said:
I got my Optimus 2x Today, the one from Netherlands. And I have a big problem. I can't make calls. When I dial the number, it is calling and after 10-15 seconds it disconnets. Happens everytime, anywhere i call. I tried Hard Reset 2 times, but it haven't fixed that problem.
And also I can't send massages, they are just not send, and there appears that ! warning yellow triangle.
I switched my SIM card back to my old phone (I8910 Omnia HD) and everything works on it like a charm...
I don't know what to do now
Click to expand...
Click to collapse
For dutch users there is a vip service, try registering and contact lg through http://www.canyouhandlethespeed.nl/. They can help by your problem or send you a new phone if needed.
Sent from my LG-P990 using XDA App
DenZj said:
For dutch users there is a vip service, try registering and contact lg through http://www.canyouhandlethespeed.nl/. They can help by your problem or send you a new phone if needed.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
I have been to the Orange shop yesterday in my city, they checked my sim and said that this is a fault of sim card. They gave me a new card and now everything works like a charm.
I've had the same problems and also some noise when coming near monitors (didnt had this with any previous phones) so I decided the cancel my contract renewal with this phone. Returned it to T-mobile and i'll just wait a few more months to see what will come! I just didn't want to take a risk to use the VIP service within the 7 days you can decide to agree on the contract or not. And also, having to use the VIP service while your phone is just 2 days old gives me a bad feeling about this phone (also reading other stories about bugs and stuff).
- SnEAky
Arawac said:
Kind off experiencing the same, although it is not constantly, but intermittent for me. however when phone calls start to fail they keep on failing, untill i pull the battery after which it works for awhile.
I am now having this with wifi aswell ....
Was i too ambitious removing those apps, following that other thread ? ill install a different launcher and see if that changes anything ....
Click to expand...
Click to collapse
I have exactly the same problem with calls as you. An issue this huge is intolerable in a 500€ phone or, well, any phone. I think I'll have to ask for a new device or a refund. I'm really dissapointed, I really liked the phone otherwise.
Try another sim card in the O2X. If the phone still does it then it is faulty.
ULJ said:
Try another sim card in the O2X. If the phone still does it then it is faulty.
Click to expand...
Click to collapse
Already did, it happened with two different sim cards. The phone is clearly faulty.
Arawac said:
Kind off experiencing the same, although it is not constantly, but intermittent for me. however when phone calls start to fail they keep on failing, untill i pull the battery after which it works for awhile.
I am now having this with wifi aswell ....
Click to expand...
Click to collapse
I am having the same problem. Any solution for this except changing to 2g? Data is disconnected when I checked in the settings. It is constantly trying to reconnect.
When this happens, I can't receive/send sms or make calls. The only way is to restart the device.
This only happens at some locations (i.e. my workplace) but doesn't encounter this problem at home.
Is this a problem with the kernel, radio, or hardware?
I am on MCR r10 by the way.
Radio/baseband: 1035.21_20110315
Kernel: Tried all available kernels and still getting the same problem.
Let me prefix my post with: please don't call 911 just to "test" your phone if this post title has worried you. There is no reason to believe you have a 911 calling problem (more explained below) and you will take up valuable resources from others who actually have an emergency and need immediate help.
I am the owner of a Samsung SGH-i896 Captivate. Today I had to call 911. The call failed. It acted like it was placing the call to 911, it said "Emergency number" on the screen as it acted like it was dialing, and then in half a second the call failed. Other calls worked fine. I had service. Thankfully I was able to use the phone of a friend that was with me to successfully dial 911.
I know this is really really horrible, especially since my little warning at the top of this thread... but when I came home I removed the SIM from my phone and tried to dial 911 to see if it would ring. It didn't work. The lock screen says "No SIM card." and "Emergency calls only". The phone shows full reception bars. When I dial 911 the screen flashes "Out of service area" at the top with a phone picture underneath and then the text"Emergency number". This comes up for 1 second then the dialer exits to my home screen.
I'd like your help to track down this problem.
Dial 112 (911 is only for us phones)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
911 is used in Canada. And the SGH-I896 is a Canadian phone.
Have you thought of it more as a network issue, and not a phone issue? I have unfortunately had to dial 911 from my Captivate before, and it worked fine. I'm using an i9000 ROM with an i9000 modem in non-3G service areas.
cgi101 said:
911 is used in Canada. And the SGH-I896 is a Canadian phone.
Click to expand...
Click to collapse
I'm not sure then does 112 work? Don't call just to test it but it should work I had this problem on an early i9000 rom 112 worked for me... this should be moved to Q&A though it is a bit of an issue... I guess no one realty tests the emergency call features...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
metalmansam said:
I'm not sure then does 112 work? Don't call just to test it but it should work I had this problem on an early i9000 rom 112 worked for me... this should be moved to Q&A though it is a bit of an issue... I guess no one realty tests the emergency call features...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Perhaps the issue warrants the attention of developement.
I had to dial 911 on my phone. live in us using cognition 4 and it would not work.
Hmm perhaps this does does need more attention if it still doesn't work on cog 4... I had this problem when the first froyo cog rom came out... I do believe it was brought up then & 112 was the temporary fix but I can't believe 911 still doesn't work...
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
112 gives me the same "Out of service area" like when I dial 911 without a SIM.
Alright, so I installed Rogers stock 2.2. I tried with both SIM in and SIM out. I'm not able to dial 911 in either case. Call fails with SIM in, and I get the "Out of service" message when SIM is out.
Sounds like there is definitely something wrong with my phone.
Ok so I can confirm that 911 does work on cog 4.3 on the i897 on att in us so I think it does have something to do with the missing nvdata but why would you still be able to make regular calls & not emergency calls that seems backwards hmm?
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Who needs 911 anyway!
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to help figure this out for evetyone but how the hell do we test this one out??? I guess I could go out looking for trouble.
ridethelight said:
Perhaps the issue warrants the attention of developement.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
If you give me an idea on how to fix it, I will test it out...
I have an i897 and have have used it on phoenix (not sure the version), and andromeda 2.1. Not sure how to test, but that does seem like an network problem. Phone not connecting properly.
I tried putting in a SIM from another carrier. 911 emergency calls don't go through.
I tried putting in a SIM from another carrier. All calls work, not 911. Tested on Rogers and Bell Canada.
Thought I herd on android central podcast that the problem was known?
Sent from my SGH-I897 using XDA Premium App
I just checked. Looks like that's a problem for the Vibrant and only when calling from the lock screen. Seems unrelated to this issue, since those people can still call from the dialer once they unlock their phone.
For anyone who has this problem in the future: I'm pretty sure it was related to having lost the phone's original /efs/ folder including nv_data.bin. You have to have a backup nv_data to restore from to fix the problem, or else it needs to go to samsung for servicing to be re-flashed. This fixed my phone. (well, got a replacement...)
For anyone who has this problem in the future: I'm pretty sure it was related to a bad upgrade to 2.2 via Samsung Kies... Replacement phone is working fine for now.
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?
Well, I just got a new (or like new, dont really now) HK edition from Craigslist, I unlock the phone and loaded Badboyz ROM, everything is great except that I have been experiencing some call drops, most of the times I can still hear the person on the other side but they don't hear me.
I replace the rom for vipervenom, but still the same behavior prevails, so I am not sure what else to check.
Mi main problem is that my carrier kind of sucks (movistar in Tijuana Mexico) so I am not 100% positive all of the call drops are because of the phone, in a couple of test I have been able to complete 30 minutes calls without problems, but some other times the call drops in the first 4 minutes.
is there a way to troubleshoot a log or something?
HK
Android 4.4.3
Baseband: 1.08.20.0612_4
Kernel: 3.4.0-g5fd9b03
After a lots of test and different roms decided to contact HTC support and they ask me to run a Network text tool (same as this posting)
http://forum.xda-developers.com/showpost.php?p=54250361&postcount=18
My phone came back with a big red screen and a banner that reads "NG device" with a log file that says "device has QFE symptom"
So i know now my phone is defective, hopefully I get a warranty replacement....
I am not using the phone on Sprint , M Not able to make calls
Some time i get incoming else other people complains ur phone is not reachable even though i have full Signal bars
phone goes to Attempting HD for 2 mins before it connects call
May time Call Drops & i get an error
Call Origination Attempt fails due to an Immediate Signal loss ( Signal Fade or No Service available)
I have 3 phones having similar issue