Hi guys, I have a strange problem.
Sometimes when I try to call someone, the phone cuts off the connection right before it should vibrate to signal that the phone was answered. This means I can hear the other side picking the phone up, but I hear like "H" (sharp, short) when they try to say "hello". No matter whether I have phone by my ear or laying on the table, sometimes it cuts off, other times it doesn't. When I make the call again, it works.
This started to happening to me since I've updated my sw version to 1.21, when it was 1.15, it worked like a charm. For the last 4 days I tried to make 3 calls, every one of them was cut out and worked on the second try.
Anyone has the same problem/knows the solution?
Thank you very much, It's annoying as hell since every call costs me twice
EDIT: I'm using stock ROM, updated with OTA, no root
------------------------------
Sorry for my English, I'm Czech.
Really? No one?
desire drops calls after a few seconds
Hi!
I've the same problem, since today - very annoying. All start with a call from a friend and after I said "hello" the call ends, but network connection was fine (4 bars). After that I tried to call him back 10 times, every time the same thing - call drops after 1-3 seconds.
A Reboot solved the problem for one time, next call same issue. Tried my sim in the HTC Wildfire of my colleague - same network, everything is fine.
Now I started to uninstall all Taskkiller and other apps i recently added - no change. After 30 min try and error I realised that if I turn of the "Mobile Internet" and therefore the 3g connection, it works better.
anyone have a clue what this could cause?
Joint the club.... http://forum.xda-developers.com/showthread.php?t=712030
Mine does exactly the same thing... first of all I thought it was the phone... returned it... new phone, different sim.... same problem.
Geeba have you tried to turn off "mobile internet"?
After my problems yesterday I turned it off and since that no call was dropped!!
Maybe its some sort of concurrent use of 3g Network and the data threads kill the call ... actually I'm no expert in Mobile Networks.
I'm looking forward to Froyo and hope to get rid of the probs.
Minos - yes I have turned off the 3g - but I then have internet connection problems... pretty pointless having a smart phone that has no internet access..
But yes it does help... the Desire I think should be able to monitor the two signals and switch between them accordingly .... but it doesn't. my Mrs has the Hero... it doesn't suffer this problem so personally I think its a problem with the desire.... I'm going to wait till Froyo then if its no better there will be a nice unbranded black Desire gracing ebay!
had the same issue for a few days then i uninstalled juice defender and i havnt had a single dropped call after
I have had the same issue. And then I have read somewhere here what to do.
You must first enter the phone's debug menu: *#*#4636#*#*
Then Choose "Phone Info", scroll down to" Set preferred network type" and set this to GSM auto (PRL). For me it solved all the call drop problem. As you are on different network maybe some other setting will work for you but it might worth to take a try with it.
I am not exactly sure what this sets. One thing is sure I still have 3G and HSUPA connection - and all type of connection works like charm. So nothing changed just no more call drops since then.
benoke: Thanks for your idea, actually my Desire is now beying hospitalized as it had dust under the screen, anyway I reported dropping calls as an issue too while returning in warranty so we'll see what happens
i sent a support question to htc and got that answer:
"Thank you for contacting HTC. In regards to your question, I can help you with that. It does indeed sound like a hardware fault, I would be grateful if you would call our tech-suooprt team and let our agents arrange the return / repair of this device for you. If you could just call 0845 890 0079, we can arrange the collection. I trust that this resolves your query. Please do not hesitate to contact us again if required."
But I don't think its an HW issue.
@benoke: the GSM auto setting worked - four 1h now.
Minos: it is good to hear that it might work for you too. I have recommended it to some of my friends and they all say it works for them.. so it really seems like solution...
Try the new version 5.09x radio in the android development in desire forum to see if that miight help
Sent from my HTC Desire using XDA App
Haven't found a way to solve this issue yet. They told me at the service station that this is unrepairable issue occuring only with some SIM cards and that they would give me a refund.
I'm buying HTC Desire HD when it is available...
I do have the problem that my Defy restarts just when a call comes in. Restart at least 50% of calls and receiving SMS / MMS. Unfortunately not reproducible because the device sometimes restarts , sometimes not - with the same number calling.
Addidionally the phone restarts 2 times a day just so, although it has been hours in standby or is charging.
Task Killer is installed, but without auto-kill. I also tried to uninstall all the apps, that could have been the potential cause - no change. It does not seem to be due to an app.
Does anyone have any idea why this might happen and what I could do about it?
Have you tried a different sim in the Defy?
Not yet, only have that one for the cell number. It's a pretty new SIM, you think here could be a problem?
Did you come up with any solution please? I'm having the same exact problem.
Yes. Problem was the SIM card, it was too new or of a too new generation. I got another one after I explained the problem to the provider; another sort of sim card, probably older generation does work perfectly now.
Hello! I don't know why but my phone started having this problem. It was out of nowhere. Well, maybe not, I've flashed my phone with the official mango update like two weeks ago, and it was working fine.
And today I saw that that I messages doesn't send out. I tried to call/text myself from other phone, and I couldn't. Phone displays gsm network name in phone hub, and also it shows full gsm connection bars(five of them), so you couldn't tell that something is wrong until you try to text or call. When you call the phone says "dialing..." but this shows forever and there's no sound from the speaker. It's worth mentioning that I've received few messages I've send to myself, but just about 2hours from sending, and then I tried to send a few more and haven't received those. Also, I've suceeded to call for a few times but after a long long wait(like at least 30sec) with the "dialing..." message shown. However, I cannot reach the phone when calling from my other phone.
I've tried to turn my phone on/off, to take the battery/sim card off, reseting the device, but none of these things helped. Then I've decided to flash my device. I've flashed my phone with DeepShining Mango custom ROM, and it seems to be working fine, but the problem still exists.
I don't know what else to do. And that's a major problem, because noone can call or text me. As I've said in the beginning, it was out of the sudden, I haven't done anything to my phone. Just yesterday I was using my phone normally, texted and called with no problem.
So I'm asking yours, guys, help. Could you please suggest what I could do? Thank you very much!
P.S. I've bought this phone from second hand and it was unlocked, but it has an orange logo on the battery cover, so I suppose it was locked to orange.
Did you pay your bill?
I have a prepaid card.
Ok, do you have a another SIM to test
My new VZW Galaxy Nexus has been occasionally entering a mode where it will not receive any phone calls.
The problem is corrected once I initiate an outgoing phone call.
The outgoing call connects immediately, is clear, and has no issues at all. If I then hang up and try calling the device it will ring immediately and work perfectly.
The problem tends to occur a couple of times per day. I've not found a direct trigger for it.
When the problem occurs, IP network connectivity still works perfectly. I can ping from the device, browse FTP sites, and run a speed test. Using the speedtest.net app (while the phone is unable to receive calls), I'm seeing 26mpbs down and 18mbps up (just like I would if the phone was working).
Powering down and then powering up the device does not correct the issue. Adding a battery pull while the device is powered down doesn't help. Once booted, the device will still not receive calls until you make an outgoing call from the device.
Phone is bone stock. Is not and has never been rooted or modified. Purchased on launch day. Indicated signal strength is great, and service in my area is very good on both 3G and 4G.
There's no indication whatsoever of an issue other than friends later notifying me that I was unreachable.
I believe text messaging may be halted as well, but have not verified this.
Verizon has no idea, indicates everything is provisioned correctly. Device was activated by a VZW store.
Any suggestions or reports of similar issues would be greatly appreciated. I can still take it back to Verizon and replace it with a new item (and I probably will).
I've seen a story of a guy who upgraded to the gnex but left his old phone turned on and used it as a bedside clock. He was saying he wouldn't receive any calls. He powered off his old phone and was then able to receive calls. Seems like a long shot but maybe your having the same problem.
Sent from my Galaxy Nexus using XDA App
Maybe your phone can automatically detect when someone you don't like is calling
Has anyone seen John Connor?
xxprodigyxx11 said:
I've seen a story of a guy who upgraded to the gnex but left his old phone turned on and used it as a bedside clock. He was saying he wouldn't receive any calls. He powered off his old phone and was then able to receive calls. Seems like a long shot but maybe your having the same problem.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Thought this was the case as well after a Verizon tech suggested it. In a rare event, I actually picked this phone up at a VZW store and they activated it for me (while my previous phone was remained on).
Since then I've turned off the old phone (and left it off) and rebooted the Nexus immediately thereafter. The problem still occurs at roughly the same interval.
I actually do a lot of switching between phones for development work, but have never seen this before. Then again I always *228 it myself where the "old" phone has to be turned off.
I just experienced this problem today for the first time. I didn't realize my phone was unable to receive calls until my Gmail account notified me that I had a bunch of voicemails waiting. Then as soon as I made an outgoing call, I had about 12 text messages deliver to me. The weird part is that I was still receiving Facebook and Twitter notifications during this time. I haven't been able to replicate the problem again, but it has happened to me as well. Very weird.
My only hunch is that earlier in the day I was out in the middle of nowhere where my signal was dropping in & out and perhaps when I came back to the city, the network didn't connect properly? I don't know if that's even possible? Also, could my home wifi network be interfering somehow?
I have tested it since I made an outgoing call and now people are able to text me and call me, so it all seems back to normal. It's a very odd problem indeed.
I had the same issue this morning and its funny because I just turned my old phone on last night and that could be the problem
Sent from my Galaxy Nexus using xda premium
I've had a Galaxy Nexus on Verizon for a couple of weeks now and noriced this problem early on, but only in the evenings and night. I stumbled upon this thread looking for a solution. Thanks tliebeck for mentioning it.
I was using my old OG Droid as a bedside clock. In the evenings, after getting home from work, I place the Galxy Nexus on the same bedside table as my old cell phone.
Then I saw xxprodigyxx11's response (thanks, btw!) and tried turning off the old phone. Sure enough, my Galaxy Nexus hasn't missed a call since. It seems to be proximity related, since I was receiving calls just fine on my gnex at work even with my old phone on at home; I'll have to do more testing on that to see just how far apart they need to be.
Sorry that did not work for you, tliebeck.
There is very little information on this situation out there, so I am grateful for the help here. Hopefully someone can come up with a more permanent and universal solution.
Good to know I'm not alone, thanks all for posting!
Still a major issue here.
Took the device to a VZW store and had them replace it with a new one. Problem still happens in exactly the same fashion. They did reuse my SIM card.
Phone seems to do it about every day lately. I've had two calls to VZW level 2 tech support. First guy tried changing a bunch of account settings around, to no avail. Second guy thinks it's a bad SIM card, I'll be heading to a VZW to get a new one of those today, but am doubtful that it will be effective.
The fact that this works across battery pulls and on two different phones just plain screams network or firmware problem.
I had the same issue. First swapped out my 4g sim card...worked OK in store, after being home for 45 minutes it did the same thing again...wouldn't accept calls until an outgoing call was placed. Drove back to Verizon and was able to reproduce the issue in the store. They replaced it with a brand new GNex and haven't had the issue since (a couple weeks). Good luck!!
Sent from my Galaxy Nexus using XDA App
Had the SIM card replaced a couple days ago, today it's doing it again.
Based on the responses here, I think this issue may be quite widespread and many people aren't realizing it because it's intermittent (every one/two/three days) and is cured if you place an outgoing call (with no indication there was ever a problem).
For me at least, a replacement new phone, new SIM card, and various account updates have had no effect.
tliebeck said:
Had the SIM card replaced a couple days ago, today it's doing it again.
Based on the responses here, I think this issue may be quite widespread and many people aren't realizing it because it's intermittent (every one/two/three days) and is cured if you place an outgoing call (with no indication there was ever a problem).
For me at least, a replacement new phone, new SIM card, and various account updates have had no effect.
Click to expand...
Click to collapse
Not to belittle your problem, but 3-4 people having an issue =/= "quite widespread."
When you say its not accepting a call, do you mean all calls go straight to VM, don't ring at all, or the call isn't going through(I.e. other person sees call failed)?
Sent from my Galaxy Nexus.
unremarked said:
Not to belittle your problem, but 3-4 people having an issue =/= "quite widespread."
When you say its not accepting a call, do you mean all calls go straight to VM, don't ring at all, or the call isn't going through(I.e. other person sees call failed)?
Sent from my Galaxy Nexus.
Click to expand...
Click to collapse
The reason I think it's not an isolated issue is because very few people are going to notice and correctly identify the issue. It's a new device (small userbase), and the more frequently you're placing calls the less likely you are to notice it. It's intermittent with what appears to be an interval of at least a few hours up to a day or more.
The calling party will either go straight to voicemail or experience between two and four rings before being routed to voicemail.
I suppose I should chime in and saying I'm having this issue also. I've found that toggling airplane mode on and then off restores ability for me to receive calls. This is a particularly bad problem for me as my wife is pregnant. She was PISSED the other day because she thought I was ignoring the 6 back-to-back calls she made. I first thought it was a google voice issue but it wasn't. I verified by calling my actual cell number once I caught it in this "mode" again today. Until we figure this out, I have the luxury of being able to add my work cell to the list of phones that GV rings so that I don't miss another call from her. That's actually how I discovered the GNex was in that "mode" again.
The comment about the previous phone is an interesting one. I also use my old phone as a nightstand deskclock and alarm clock. I will try throwing that one in airplane mode for awhile and see if that fixes anything. I don't believe it to be a proximity issue though because my GNex has entered this mode while I was at work and the old phone was at home. It's a half hour drive and there's a mountain in between.
-Josh
I also think that more people could be having this issue without knowing at all which would lead to less complaining. The caller just thinks the receiver is just too busy to answer and leaves a message. Unless you don't get a really important call that a wife/friend complains heavily about, one would never know.
I had purchased a new GNEX a few days ago and I had a really strange problem where the phone would work (receive / make calls) for about 10 minutes, then the radio would just stop working.
Wait a few minutes, and it would come back to life.
Since it was new, I took it back to the Verizon store and they tried to claim it was due to some software issue that was being fixed in the next two weeks, but I disagreed.
Ultimately got a new GNEX and haven't had the problem since. Seems like maybe there is a bad batch out there with faulty radios?
I don't have anything to add except to say that my father's HTC Raider/Vivid did the same thing last night, and it was spooky. I phoned him a few times, and it went straight to VM every time. As soon as he placed a call, all the VM notifications came flooding in, and his phone could receive calls again.
My guess is that it is a quirk with the way 4g is authenticated. Since it's a new type of connection (requires sim card instead of esn) there's some kind of glitch where the old esn isn't fully un-registered with the network. Does your dad also use an old 3g phone as a deskclock or anything?
Me Too! Galaxy nexus stops receiving calls until I place an outgoing cal
Hi,
This is my first post here. Just wondering if this has been resolved? My Gnexus was on all day Saturday, Sunday and most of today without receiving a call or a text. When I called out it started working, but none of the incomming calls in my voicemail showed up in my log. No text messages were received either. Thanks for starting the thread.
pcnerdman said:
Hi,
This is my first post here. Just wondering if this has been resolved? My Gnexus was on all day Saturday, Sunday and most of today without receiving a call or a text. When I called out it started working, but none of the incomming calls in my voicemail showed up in my log. No text messages were received either. Thanks for starting the thread.
Click to expand...
Click to collapse
Do u have a phone that used to be on that line turned on?
Sent from my Galaxy Nexus using XDA App
Update: have not had this issue come up again since i put my old phone in airplane mode. I always wait for both of my gv phones to ring to ensure this problem is resolved.
Sent from my GalIaxy Nexus using XDA App
This issue is not exclusive to the Verizon Nexus. I have the GSM version through TMobile and quite often (several times a week, maybe more) my phone just stops receiving text messages. I can't even make outgoing calls.
So now, periodically throughout the day I call Google Voice to see if it works. If I get my own voicemail I know that I'm still receiving text messages. If it doesn't connect, then I have to turn on airplane mode, then turn it off again, and the network comes back.
During the outage I still show full bars over 3G.
It's so freaking annoying. I thought the latest update to Android would fix it, but it didn't. There's a Google thread on this too:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=34ad876196cb21c4&hl=en&start=40
Hi there.
My M9 has a strange problem where it rejects phone calls on a seemingly random basis. When I try to call the phone from a landline or another mobile it shows no sign that there's an incoming call. The phone making the call hears a ringing tone twice, and then only a beeping (like an engaged tone but with one beep longer than the other). The odd part is that it doesn't always happen. I get the occasional cold call come through, and sometimes people phoning me can get through, but at other times they can't. It seems consistent that when I'm at home in the evenings it rejects all calls. I'm sitting at home now and if I try to phone from a landline or mobile it won't get through yet the phone is showing full signal and can make calls. I've tried with WiFi and mobile data on and off and rebooting the phone to no avail. SMS messages come through fine all the time.
I've contacted my network (Virgin mobile UK) and they've issued a replacement SIM - same problem. I've tried the SIM in a Nokia and it seems to work perfectly, so I've come to the conclusion it must be the M9 causing this.
To start with I was on the stock HTC Android, and I've not got any auto-reject settings turned on (that I can see). To try and solve this I've done a factory reset via the phone, and when that didn't work I tried doing a complete wipe and installing TWRP recovery and ViperOneM9. It still rejects calls!
Anyone got any ideas? I've tried searching for this but all the posts seem to be about setting up auto rejects, or not receiving any calls at all. Are there any logs I could look at to see if the M9 is getting the call but then rejecting it without my knowledge? Any hints here would be appreciated!
TIA
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
shivadow said:
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
Click to expand...
Click to collapse
Thank you. I started doing that but had some problems, so in the end I bought a new phone, and lo and behold I had the same problem as I had with the HTC, and that was when the phone was fresh out of the box before I'd installed any apps.
After a LOT of playing around with settings, I've now figured out that if I have 4G turned on when I'm at home then all calls are rejected, even if WiFi is also turned on. Forcing the phone to use 3G when I'm at home means I get calls, and if I have 4G turned on when I'm at work I get calls OK. I guess the test with the Nokia worked OK as it wasn't a 4G phone.
After repeated calls to Virgin they've finally admitted that there's a fault on the phone mast close to my house, and by the sounds of it they have a lot of open tickets for that mast. As they use EE's network they say they can't do anything until EE pull their finger out, but as I've had the issue for months I bet it won't be anytime soon. For now I'll have to switch to 4G manually whenever I'm away from home and try to remember to put it back to 3G when I get back. Not ideal but at least I know what the problem is now!
Thanks for your suggestion, even though it wouldn't have worked in this case.