DROID X fails all outgoing calls and sending TXTs until reboot

[dromski]

Verizon DROID X can't make outgoing calls.  It will briefly flash 0:00 (call time) and then returns to dialer.  I get this on calls to any phone (home, work, wife’s cell, etc). It will also not send TXT messages (after timeout puts red X beside message).   I tried adjusting many settings without help.  Wifi still works.  I think that I have gotten incoming calls while it was in this mode.  A power cycle will resolve but a few days later it will enter this failure mode again.

=== history ===

My phone had been working flawlessly for 6 months (I loved my DROID X).  I had recently ran the system update to get Android 2.3.3.  It was at least several days after this when I noticed my first outgoing call failure.  A reboot resolved but this pattern of failure/reboot repeated several more times and was getting annoying.  

On July 4th the cellular capability completely failed.   It showed no service, no bars, and status menus indicated no network.  I tried changing every related mode (Airplane, etc) with no impact.  This time a reboot did not recover it.  Wifi was still working.  I tried a factory reset but phone activation process got stuck when  it could not reach the network.  I took to the service center and they spent some time on it and agreed it was hardware issue and sent replacement “like new” phone.

=== replaced phone ===

Activation went fine and it synced all the accounts and apps and was working great.  However, several days later the new phone started showing similar issues of failing outgoing call or sending TXTs.  Took it to the service center while it was in this failure mode and they could not figure it out.  A reboot resolved it.

Last night it was working fine (outgoing call at 6pm).  I may have read some news, checked email, etc.  Today at work it again failed to make any outgoing calls.  I took it to the service center and they again validated issue but had no clue on the cause (speculated it may be having 3G issues).  We did factory reset and it is working again.  This feels like more of the same, and I don't expect it is resolved.

My phone is fairly typical (not rooted).  All installed apps are fairly popular on the Market.  I don't play games or use the social networking.  My main use is the email and merged calendar from Google and Corporate Sync (and sometimes Yahoo).  I have now uninstalled most all my applications to isolate if that will make it stable for the next week.  My wife has an almost identically configured DROID X without these issues (but has not yet updated system to Android 2.3.3).

I am a very technical (Linux kernel developer) and welcome any suggestion, diagnostics, or logs that could identify what is causing this.

[JoeL_VZW]

  Its very frustrating to lose connection on your Droid X.

      We have escalated this to Motorola's product investigation team. They don't have a resolution yet. As soon as they inform us of the resolution to your issue we will post it here. Thank you for your patience and for bringing this to our attention.

[JonBuoy]

I have also experienced the same failures as dromski. Nearly identical scenarios. My wife's identical phone seems to be OK though. I am a highly experienced embedded system and software engineer and frustrated by the response of the support folks. Much like the "just reformat your hard drive" kind of response.

Searching other forums, this problem seems to have preceeded Gingerbread. It is definately related to a 3G radio lock-up. Is it a "safe" app that does it, or is it related to another RF device in close proximity to the phone that causes the 3G radio to fail? Since this has been going on for many months (pre-Android 2.3 aka "GB"), I have to believe that the Moto engineers have a clue to it's origin. The questions are, will Motorola (and Verizon) 1) admit to an inherent flaw with the device, 2) continue recycling "like-new" phones, or 3) cooperate with the technically knowledgable customers to resolve the problem?

From what I've seen reported on this problem, an "outside-the-box" approach is needed. What apps are in common with the failing devices. What other RF devices are used in the vicinity (phones, microwaves, other transmitters)?  Is there an android app that monitors the 3G service to detect the conditions around this failure? Can android report on ALL apps/services registered for relevant OS permissions? We need engineers with the resources to resolve this!

Jon

[JonBuoy]

I need to refine my assumption that it's the 3G service.  The actual symptoms that I experience are 1) the dialer simply beeps, displays "Call time 00:00" for 2 seconds, then exits, and 2) Backup Assistant responds with "Network Unavailable".

Wifi works, Bluetooth works. The CDMA signal strength shows1 bar. Though -81dBm or less, I've had success with much lower signal. Service State is "In Service" and Mobile Network State can show Connected or Disconnected. AT NO TIME during this failure is the "3G" icon displayed. It appears that the "Connected" state is when it attempts to connect, but then it can't.

A reboot will resolve the problem for about 2-3 days.

[RGBot]

I am having this issue as well. It happens about every 2 days or so.

[B33]

I 've had a few issues as well mine stims from when i'm on Wi-Fi an listing to Winamp or Other Music an when Decide to kick off my Wi-Fi it goes off but the 3G indicator Does'nt like to come back Regardless of what i do an at time my bars will Drop off to 1 bar but a rep said as u got 3G the bar strenth does'nt Matter.

Something i like to suggest to you guys you might call Verizon Teck Services an ask them what you sid is.  if your running an old Sid in you phone that might cause some issues i say it might so give it a check  an also make sure your updating your PRL once a month as well as that's how the phone keeps in contact with the Towers. you can do one  other thing every time you feel the need an that is a *18 Send it what it does is it Hits the Tower to give you a Connection.

So give those few things a try an see if helps.   Ra

[JonBuoy]

Thanks for the tips DincX110! They may be very helpful. However, this is a VERY SPECIFIC problem with new phones and Android 2.3.3. Maybe older ones also? My wife & I got ours on 6/18/11. Other symptoms MAY have a common fault, but we need to focus on dromski's initial symptom (and subject line). PRL "shouldn't" come into play since it pertians to roaming and re-connection is only after a reboot. Can one use *611, or *18, when the dialer is failing?

[Wildman]

Have any of the users having this issue try wiping their system cache and see if that helps any?

 Wiping cache partition

• Power off
• Power On Holding Home Key
• When Andy with Exlamation Point Shows up Press BOTH Volume keys
• Use Volume Keys to navigate to "wipe cache partition" and tap power button to select
• Wait for it to finish and select reboot system

[JonBuoy]

Cache partition wiped 35 hrs ago. Problem has now returned. Rebooting again. Methodically removing least used apps.

[rlyle]

Getting the same problem here as well .... 

Usually after leaving work I'll notice my "3G" isn't on anymore.. If I try to make it a call it just hangs up. The only way to fix the problem is to reboot the phone.

[#11]

@ rlyle   I did some research on this and it seems that the 3g/dialing out problem is a reported known issue.  With that being said the fixes have been integrated with a new software update which is currently being tested, and should be available in Mid August. Hope this helps.  Thanks.

[WillyB10]

I am experiencing the same issue, missing incoming phone calls as well. It is an inconvenience as well as a hazard, calling 911 for instance????

[Meshe]

Same issues with me.  Will lost 3g on my phone and can not make calls until reboot.

[droidsw]

You folks aren't alone. Mine does it about every other day. Next time, I'm going to call my X from my other phone to check, voicemail, missed call notifications.........

More from the Moto forum:

https://supportforums.motorola.com/thread/51905?tstart=0 https://supportforums.motorola.com/thread/51905?tstart=0

[SteelerFan]

I got a replacement X last week and the last 2 nights I have lost 3G and had to do a battery pull to get it back. This is not good.

[buffalo4747]

This has been one of many issues for me since the Soak Test of Memorial Day weekend. You would think that somehow a VZW or Moto employee would recognize this as an issue from the GB update, and post when a fix is coming (not a "Target Date", but an actual date). A target date of mid August is the latest rumor, but that still puts it as about twelve weeks that my phone has had NUMEROUS issues.

It has been 10 weeks now, and my phone is no longer what I contracted and paid for! I don't want to factory reset or anything related to that. I don't want a used phone as an exchange. I want the phone I apid for to work!

---

[droidsw]

That date is given as a target, because if testing reveals issues that delays it from any specific release date given, people will be furious.

Kind of like when my wife asks when I will be back from 18 holes of golf. "Before too late" is much safer than "5 P.M."

As for any official admission that any specific issues are attributed to GB, again, it is much safer for Moto to be vague and just announce that they are "working on it".

As for your not wanting to troubleshoot, do a reset, etc..... no offense, but you might want to consider something other than a smartphone.

At least for now, troubleshooting is a part of ownership. That includes iphones, by the way, just to a much lesser extent.

The personnel at a Verizon Store can assist you, if you are uncomfortable doing the troubleshooting yourself.

We all want our phones to work. If the folks at the Verizon Store are unable to get your phone back up to a usable condition, they will take the next step.

And, unless your phone is less than 14 days old, the replacement will be a used phone. Used phones aren't like used underwear. Try and get the notion out of your head that used phones are inferior. You likely wouldn't even know it was used if someone hadn't told you.

My experience with this phone hasn't been a walk in the park, either. But, you know what? It's only a phone. Not worth getting upset about.

Let's just hope that this update fixes things.