Droid 3 random reboots

[raymccoy]

I am having the feared random reboots in my recently acquired Droid 3.

It is rebooting more than 10 times a day randomly, both when idle and when doing anything in the phone.

The only pattern I've been to able to catch is that around 30 seconds before a reboot, I loose phone signal (the signal strength meter is empty and showing a cross). WiFi keeps working until the reboot.

I am located in Spain and using the phone in GSM/UMTS mode, with CDMA disabled. Some times when I loose the signal prior to a reboot, I get a pop-up asking if I want to put the phone in "global" mode for it to search for CDMA signal.

I am using rooted Steel Droid 3 with OTA 5.6.890, but it happened with Verizon's stock ROM as well.

I have googled extensively for the last couple of days and did everything I have found about possible solutions:

- Factory reset and disabling Google restoring features on initial config (to prevent restoring WiFi hotspot data, alleged to cause reboots)
- Manually wiping all WiFi hotspot info
- Disable WiFi
- Running with no apps installed
- Formatting sd card
- Wiping user data and cache from Recovery
- Checking if the battery is loose, wedge a piece of paper to lock it in place

None of this have prevented or even alleviated the random reboots.

I'm fearing my phone might be a total lemon, but unfortunately as I am in Spain I can't return it and get a replacement. Anyway I have been reading that people have returned their Droids four or five times and still get random reboots in every new or refurbished Droid they get.

Other than that the phone works perfectly well, and I really love it. But having reboots when you are in the middle of something is going to get more and more annoying and I fear I will throw it out of the window sooner or later. I really need to solve this.

I run adb logcat in hopes of finding what is causing it, but it didn't see anything revelatory. Here are the tails of my last 3 logs before a crash:

12-06 22:39:43.764   512  3986 W Smack/Packet: notify conn break (IOEx), close connection12-06 22:39:43.764   512  3986 D Smack   : [XMPPConn] close connection, notifyClosed=false
12-06 22:39:43.921   512   608 I GTalkService: [GTalkConnection.18] connectionClosed: connId=28343, error=CONNECTION FAILED
12-06 22:39:43.921   317   323 D ConnectivityService: reportNetworkCondition(1,0)
12-06 22:39:43.929   317   370 D ConnectivityService: Inet connectivity change,net=1, condition=0,mActiveDefaultNetwork=1
12-06 22:39:43.929   317   370 D ConnectivityService: starting a change hold12-06 22:39:43.936   512   608 I GTalkService: [GTalkConnection.18] (WORKER THREAD) update account status
12-06 22:39:43.999   512   608 I GTalkService: [GTalkConnection.18] (WORKER THREAD) update account status - done, took 58 ms
12-06 22:39:46.944   400   400 D StatusBarPolicy: the netConditon of netType 1 is updated as 0 by android.net.conn.INET_CONDITION_ACTION,icon color should be white.
12-06 22:39:46.944   400   400 V StatusBarPolicy: NetworkInfo: NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true, inetCondition= 0
12-06 22:39:46.944   400   400 V StatusBarPolicy: mModemIsResetting=false
12-06 22:39:46.944   317   370 D ConnectivityService: Inet hold end, net=1, condition =0, published condition =100
12-06 22:39:59.702   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 22:39:59.702   195   237 D libmdmctrl:
12-06 22:39:59.702   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 22:39:59.702   195   237 D libmdmctrl:

12-06 23:12:14.951   533  1016 I EventLogService: Aggregate from 1323209010096 (log), 1323207734851 (data)12-06 23:12:16.654   317   382 D dalvikvm: GC_EXPLICIT freed 143K, 38% free 8201K/13063K, external 5433K/6784K, paused 158ms
12-06 23:12:21.990   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 23:12:21.990   195   237 D libmdmctrl:
12-06 23:12:21.990   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 23:12:21.990   195   237 D libmdmctrl:
12-06 23:12:24.591  4743  4754 W googleanalytics: Problem with socket or streams.
12-06 23:12:24.591  4743  4754 W googleanalytics: java.net.ConnectException: www.google-analytics.com/127.0.0.1:80 - Connection refused
12-06 23:12:24.591  4743  4754 W googleanalytics:       at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:207)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:437)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at java.net.Socket.connect(Socket.java:983)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingEvents(Unknown Source)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at android.os.Handler.handleCallback(Handler.java:587)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at android.os.Handler.dispatchMessage(Handler.java:92)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at android.os.Looper.loop(Looper.java:130)
12-06 23:12:24.591  4743  4754 W googleanalytics:       at android.os.HandlerThread.run(HandlerThread.java:60)
12-06 23:12:24.849   445   467 D dalvikvm: GC_CONCURRENT freed 1098K, 49% free 4008K/7815K, external 2692K/3351K, paused 2ms+2ms
12-06 23:12:24.896   445   445 W KeyCharacterMap: Can't open keycharmap file
12-06 23:12:24.896   445   445 W KeyCharacterMap: Error loading keycharmap file'/data/usr/keychars/omap-keypad.kcm.bin'. hw.keyboards.0.devname='omap-keypad'

12-06 23:46:26.576   677  1930 W IdleConnectionHandler: Removing a connection that never existed!12-06 23:46:26.576   677  1930 D News Processor:  SAVED http://www.meneame.net/rss2.php
12-06 23:46:26.584   677  1932 D News Processor:  PROCESSING source: 20 http://www.meneame.net/rss2.php
12-06 23:46:26.646   677  1932 D News Processor:  HAS NEW: false - http://www.meneame.net/rss2.php
12-06 23:46:33.584  1480  1491 W googleanalytics: Problem with socket or streams.
12-06 23:46:33.584  1480  1491 W googleanalytics: java.net.ConnectException: www.google-analytics.com/127.0.0.1:80 - Connection refused
12-06 23:46:33.584  1480  1491 W googleanalytics:       at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:207)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at org.apache.harmony.luni.net.PlainSocketImpl.connect(PlainSocketImpl.java:437)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at java.net.Socket.connect(Socket.java:983)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:119)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at com.google.android.apps.analytics.PipelinedRequester.maybeOpenConnection(Unknown Source)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at com.google.android.apps.analytics.PipelinedRequester.addRequest(Unknown Source)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.dispatchSomePendingEvents(Unknown Source)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at com.google.android.apps.analytics.NetworkDispatcher$DispatcherThread$AsyncDispatchTask.run(Unknown Source)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at android.os.Handler.handleCallback(Handler.java:587)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at android.os.Handler.dispatchMessage(Handler.java:92)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at android.os.Looper.loop(Looper.java:130)
12-06 23:46:33.584  1480  1491 W googleanalytics:       at android.os.HandlerThread.run(HandlerThread.java:60)
12-06 23:46:36.334   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 23:46:36.334   195   237 D libmdmctrl:
12-06 23:46:36.334   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 23:46:36.334   195   237 D libmdmctrl:

I have seen that the most common before-reboot output is

12-06 22:39:59.702   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control, buff = auto
12-06 22:39:59.702   195   237 D libmdmctrl:
12-06 22:39:59.702   195   237 D libmdmctrl: file /sys/bus/usb/devices/usb2/power/control opened in write only mode
12-06 22:39:59.702   195   237 D libmdmctrl:

But I have googled for libmdmctrl and there is only 1 result that has nothing to do with anything.

I am really in the dark, thanks for any help!

 

[Cdjones187]

I am having the feared random reboots in my recently acquired Droid 3.

It is rebooting more than 10 times a day randomly, both when idle and when doing anything in the phone.

I assume your already out of the 14 day return period (yes they changed it to 14 when they changed the data plans). If it was happening stock straight out of the box I would of returned it for a new D3. My suggestion would be to return it to 100% stock and contact motorola, it should be covered by manufactures warranty so you wouldn't have to make a insurance claim.

And not to be a debbie downer but you would have more luck posting your logs over at XDA where there are more devs that would understand it. I will contact a friend that could probably figure it out, he helped me un-brick my D3 weeks before we had a way of recovery.

From what I see you have multiple problems, keyboard mapping and usb being 2 of them if it wasn't obvious.

 

[raymccoy]

I assume your already out of the 14 day return period (yes they changed it to 14 when they changed the data plans). If it was happening stock straight out of the box I would of returned it for a new D3. My suggestion would be to return it to 100% stock and contact motorola, it should be covered by manufactures warranty so you wouldn't have to make a insurance claim.

I bought it second hand in eBay, so I don't think I can do this through Motorola in Spain...

I contacted the seller and she will refund me if I can't get this solved, but I really don't want to go through the hassle of sending the phone back to the US and buying another one off eBay that might be another lemon... so I really need to get this fixed or at least improved.

I can live with a couple of reboots a day, but 10 or 15 a day as now is really unbearable.

 

[Cdjones187]

I bought it second hand in eBay, so I don't think I can do this through Motorola in Spain...

I contacted the seller and she will refund me if I can't get this solved, but I really don't want to go through the hassle of sending the phone back to the US and buying another one off eBay that might be another lemon... so I really need to get this fixed or at least improved.

I can live with a couple of reboots a day, but 10 or 15 a day as now is really unbearable.

Sorry to hear that... Personally I wouldnt want a defected phone especially from ebay, that was pretty shady of them. They knew that the phone was messed up and that is why they sold it.. I would seriously just send the phone back before they change their mind. Might be a hassle but it is most likely going to be easier than trying to figure out a phone that someone else screwed up before they sold it to you.


I would also make them pay return shipping and other fees you might run into, contact ebay if they dont agree. If they sold a defect phone without stating it had problems it is 100% on them to make it right or they will be flagged on ebay/paypal for fraud.

 

[raymccoy]

Sorry to hear that... Personally I wouldnt want a defected phone especially from ebay, that was pretty shady of them. They knew that the phone was messed up and that is why they sold it.. I would seriously just send the phone back before they change their mind. Might be a hassle but it is most likely going to be easier than trying to figure out a phone that someone else screwed up before they sold it to you.

I would also make them pay return shipping and other fees you might run into, contact ebay if they dont agree. If they sold a defect phone without stating it had problems it is 100% on them to make it right or they will be flagged on ebay/paypal for fraud.

I am not so sure she knew the phone was wrong, this is a seller with 100% positive feedback in over 700 sold smartphones. I don't think she would risk selling a defective phone without stating it in the description.

The phone was in mint condition as described, I just believe she booted it, run it for a few minutes, saw it was working fine and thought the phone was OK. You need to idle the phone for a while to get the reboot, is not easy to get in a short use.

 

[raymccoy]

Found a solution!

I tried a different approach, after concluding that the problem was with radio / telephony...


I put in another SIM from a different carrier, and so far I am having no reboots!


What is the difference? My main carrier is a "virtual carrier", a company that rents other company's network to offer their service, usually with more competitive prices.


The SIM I'm using now is from a traditional carrier that owns the network directly.


What I think happens is that when using a virtual carrier, you are having a sort of permanent roaming: the phone has to first get into the network owning carrier and then join the virtual network of the virtual carrier. Somehow this is making the Droid 3 crazy.


The signal strength meter was indeed showing a small "R" indicating I was in roaming. I assumed this was because being an US phone, it took any non-US network as roaming, but now that I am using the regular carrier SIM, the signal strength bar is not showing "R" anymore.


Seems I will have to change my carrier to a network owner, which unfortunately have much less competitive prices. But at least I found a way of using the Droid 3 without constant reboots!!


For future reference to other Spanish users: I am having the reboots using a Simyo SIM (which runs on the Orange network), but with a Movistar SIM there are no reboots.

 

[kcd1369]

I have been having the same problem with 3 droid 3's in my company.
It started the same day we received a OS update.

It is very annoying.

Does anyone know of a problem with that update? These phone were great before this. Very stable. But now, what a pain.


Sent from my DROID3 using DroidForums

 

[mysticalmalissa]

Mine has also started to do this. Its about 4 times a day now. Im doing my second factory reset right now. :/

 

[Geoffroy]

Hello,

I have the same problem, I bought the phone on ebay and although it was marked as "new", it always reboots.

I've read the log and found that it perhaps has something to do with the carrier name, which caused an uncaught exception. From that time the device lose network connection, and will ask for PIN code after several seconds.

In the beginning, the phone was most of the time blocking on the "Unlocking Pin" message, but now everything goes well, althought it's still locked !

I also have the same problem, the phone rebooting from time to time, and as far as I know it only occurs _after_ the carrier signal is lost.

I will try a different SIM card, to see if the problem come from there or not...​

 

[reimer]

I am in Uruguay, and just received my second Droid 3 marked as new in Amazon, but had some differences on packaging as the one I bought in USA last year.
As I cannot send it back, and no warranty in my country, have to look for a solution. Maybe is the same case with Spain.

These were my procedures and results:

First with no SIM installed:

- Started with random reboots so first I upgraded firmware to 5.7.906 to discard firmware corruption. No luck
- Rooted to get more control
- Installed Safestrap to have ICS CM9 and Gingerbread Stock to test and compare.
- I have more than one battery to discard problems on battery feed.

Results:

With ICS CM9 , reboots were more frecuent than in stock. As CM9 is optimized to get more speed, specially on memory. I focused on memory and CPU.
I reduced CPU with SETCPU to 800 MAX, and phone got much more stable on Stock, and more but not what I call stable.
Then I reduced to 600MZ top, and got to a stable condition on stock 5.7.906, and little less stable condition on ICS.

It seems for me that this phone was faulty and returned.
Instead of repairing, they covered with plastic side and screen protection, and repackaged to sell through dealers as new. The store who sold me, told me that he bought it from a Motorola Official dealer as new, so beware that it can happen to anyone.
The small differences in packaging from my other phone, one of this was the screen protector that was printed on original, and transparent on this it was clear that it was not a factory new unit.

As it is a hardware issue that it will need future repair, and no way to send it back to USA, I asked for a partial refund from provider and gave it to me.

Now I have a different phone, a Motorola Droid 3 Lite (600-800 MHZ), that costed me 2/3 of price.
I needed a phone with keyboard and couldn't wait for send it and repairing (takes long times here to get spare parts or find qualify service) , so I bought another to use, and have more time to repair the other.
The "new" unit works, no I will concentrate on old one stable to be repaired.

Hope this will help