Discussion in 'Android Devices' started by mach1man, Aug 26, 2010.
I was wondering if the droid 2 had random rebooting issues.
I haven't had any. I reboot it myself once or twice a day due to the reception problem.
Can't say that mine does, good luck!
Had mine for a little over a week and it runs perfect.
Rebooting issues are problems caused by junk apps that people install and for some reason keep around. Neither the X, Incredible, or 2 will just reboot randomly, there will always be a reason.
I havent had any issues with mine, and Ive had aton of crap installed since day one... hope that helps someones study
no probs with mine, maybe 12 apps loaded up since day one.
Actually alot of the incredibles when they first came out would randomly reboot if you got in a low service area so that has nothing to do with an app.
My phone hasn't had a issue at all, with either restarts or reception issues. The only issue I had was one battery pull due to installing crap apps, or crapps...lol
Mine randomly rebooted once in my first 24 hours with it. Hasn't happened since (two weeks later).
No random reboots on our Droid 2 or Droid X.
Haven't had any reboots or hangs on the Incredible in the 3 days I've had it with about 7 App installs.
exact same for me, one random reboot, (as I put it in the car dock and plugged it in) on day one but since then NADA
and I remember my droid 1 rebooting every time I closed the keyboard (until I swapped it out under warranty)
I had random reboots on my first Inc. I had no third party apps installed. My replacement INC had no random reboots.
My first DX I didn't have long enough to tell. My replacement DX in the 29 days I had it has had 1 random reboot.
So, I dunno wtf is going on with these phones...
I have this problem with my Droid 2 sometimes right in the middle of a call.
negative ghostrider no problems here
No reboots for me.
I have a 5 week old Droid 2 (R2D2 edition) and yesterday it turned itself off and would not respond to button presses to turn it back on for about 30 minutes. After that there were about 4-5 reboots in a row, then everything was fine. A little over a day later, a.k.a. right freaking now, it crashed and rebooted itself while I was in the text message app and it's in a cycle of constant reboots (it's on #8 now). The only marketplace apps I've installed are Facebook, Accuweather, and Bump, and there were no troubles with them for three weeks.
just call verizon and get a replacement, don't even stress over why, they'll send you another one
Droid 2 Global --2 weeks old... reboots every few days when swiping unlock and having a call in the background .... definitely annoying
I have had the same problem with my phone as well (10 days old) and while the reboots only take around a minute to complete, it is certainly very annoying. I decided to install a logging utility called CatLog in hopes of catching some details about what is causing the crash. My phone just rebooted and I was able to capture some of the logging which I have attached to this posting. Here are the lines that are probably the root cause of the reboot though:
03-15 13:05:54.420 W/Cursor (18149): at dalvik.system.NativeStart.main(Native Method)
03-15 13:05:54.498 D/NetworkLocationProvider( 8683): onDataConnectionStateChanged 2
03-15 13:05:56.100 D/RadioSignalLevel( 8683): evdo dbmLevel: 4, snrLevel: 2
03-15 13:05:56.413 E/dalvikvm-heap( 8683): 303360-byte external allocation too large for this process.
03-15 13:05:56.413 E/GraphicsJNI( 8683): VM won't let us allocate 303360 bytes
03-15 13:05:56.413 W/dalvikvm( 8683): threadid=20: thread exiting with uncaught exception (group=0x400208b0)
03-15 13:05:56.467 E/AndroidRuntime( 8683): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
03-15 13:05:56.467 E/AndroidRuntime( 8683): java.lang.OutOfMemoryError: bitmap size exceeds VM budget
03-15 13:05:56.467 E/AndroidRuntime( 8683): at android.graphics.Bitmap.nativeCreate(Native Method)
03-15 13:05:56.467 E/AndroidRuntime( 8683): at android.graphics.Bitmap.createBitmap(Bitmap.java:498)
03-15 13:05:56.467 E/AndroidRuntime( 8683): at com.motorola.android.widget.AbsSlideButton.drawButton(AbsSlideButton.java:652)
03-15 13:05:56.467 E/AndroidRuntime( 8683): at com.motorola.android.widget.AbsSlideButton.onDraw(AbsSlideButton.java:549)
03-15 13:05:56.467 E/AndroidRuntime( 8683): at android.view.View.draw(View.java:6742)
03-15 13:05:56.467 E/AndroidRuntime( 8683): at android.view.ViewGroup.drawChild(ViewGroup.java:1640)
03-15 13:05:56.467 E/AndroidRuntime( 8683): at android.view.ViewGroup.dispatchDraw(ViewGroup.java:1367)
I encourage others to do the same, maybe we can catch the eyes of Verizon/Motorola to resolve this problem. I hope this helps somebody down the road!