Database Develop

The Boot Loop of Death (BLOD)

Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....

Reserved for future use

My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.

I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done

wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.

I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.

I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.

I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)

The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.

While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.

I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.

I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.

cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.

I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.

DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.

MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?

DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.

I have this on stock 2.1u1 EPE54B

I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.

tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?

ok so i could use some help... please...

alright it is with great pain that i am writing this, but i really need some help here. for months i've read the forums, searched for answers, asked little individual questions, IMed with people directly for help... and i'm still having trouble.
i rooted my T-Mobile G1 all the way back when cupcake first came out. everything was great. life was grand. everything ruled. i was a happy android fanboy, talking friends into switching to android, talking crap about iphones... the works... but slowly things started getting slower and slower and slower...
the obvious thing was to wipe and reflash. i was constantly just updating to newer cyanogen roms at that point without wiping. so i wiped to the newest cyanogen at the time (can't remember at this point, but just picture it was like a couple months after cupcake). so things were good again for a little bit, but then it started slowing down again, getting FC's, etc. so a friend recommended i switch to superD... i did, and again, everything was great for a while. i consistently upgraded superD roms (sometimes wiping in between sometimes not). eventually i got to the point where i was on the most recent superD release. it lasted about a day before things started slowing down. examples include when i hit home to exit an application and go to the home screen, the whole screen would either turn black or just show my wallpaper for a good 5 seconds before my home screen would appear, or opening the browser would take like 10 seconds. lots of slow down.
so with the help of a friend i decided to completely wipe and reformat/repartition my sd card. i bought titanium backup but i didn't even bother with it, i said to myself, look, you barely use any of the stuff you have right now, how about just start fresh and reinstall things as you need them manually. so i formatted, repartitioned (using amon Ra's recovery, using the menu option that helps you do it automatically). i made sure i had the most recent radio and spl (this was just a couple months ago), and reflashed the most recent superD (i think its 1.11 if i remember correctly)... again, maybe one day of good performance before everything slowed down. this was also about the time when my battery life started becoming an issue. i'm not exaggerating when i say i couldn't make it home without breaking under 20% battery by the end of the day... and i really don't use my phone THAT much. i'd say i'm a little above average on my usage. i'll get into my widgets and apps in a second, but i really don't use that much stuff...
SO... continuing my story (thanks for sticking with me if you're still reading...). when cyanogens 2.1 for the g1 rom came out (5.0.8d/s) i decided it was time for a change. i reformatted AGAIN, repartioned AGAIN, and flashed 5.0.8. basically, i've got the same story going on. slowdowns, poor battery life, etc.
so here i am with my cyanogen 5.0.8 flashed g1. let me tell you about apps and widgets and stuff. right now i have a regular wallpaper (not live), 14 icons between my 5 screens and just the google search and power management widgets. i used to have calwidget, the genie widget (both news and weather), and the setcpu widgets too, but i decided to take them off to see if it would help with performance. zero help. apps that i either know for sure are always running or i think may have some impact are twidroyd, newsrob, craigsnotif (craigslist notifier), and dealdroid. i don't think any other apps are running and/or do automatic updates for content and stuff like that.
i also use cachemate (purchased) regularly to clear my caches. apps2sd is enabled.
i'm not sure what other information you'd need to help me out, but just let me know and i'll try to give you more details.
right now, i've got slow down like almost all the time. things are constantly pausing, slowing down. i feel like i'm back on my t-mobile mda with winmo5 haha. and forget about it with the battery. i left the house with 90% battery this morning. i went to the gym. went home. picked up lunch. came to work. its been like 4 hours. i currently have 19% battery. all i've done is make 2 phone calls, about a dozen text messages and i've sent 2 tweets (about my battery problem haha). i also used google maps once to look up a number. my wifi and gps is off.
so there we go. really guys, please please please. help me out if you can. any help would be appreciated. i'm so sick of this. and i'm stuck in contract until july 2011. so i'm not getting a new phone any time soon. i gotta figure this thing out.
i really appreciate your help.
thanks.
Dave

OH... and PS... forgot to mention that I just got a new battery this week thinking maybe the battery was just getting old and bad. obviously, no such luck.

I had the same issues till I flashed a SuperD, then everything was fine. I just recently flashed the Froyo from Cyanogen and its like it fixed everything and I'm on a brand new device (knock on wood)!
How old is your G1? Do we know if there are issues with the first run out of the factory? Is that even an issue?

i got the g1 last july. so it was already out for a while at that point. it was new from a store though. i suppose there could be something actually wrong with the phone itself, but i don't know. i was thinking of trying the cyanogen froyo but because its not a stable release yet i figured it would be just this bad or worse...

I promise cm5.0.8 has wonderful battery life when no custom apps are installed and not on any network..
so the question is what is your phone doing, and ought it be doing what it is doing.
There are some nice built in tools for this
Applications->running services
And
Applications -> manage applications (check out the filter in the menu from that screen)
You may be surprised by the apps the think they need to constantly have a service running for some painful trivial job the android API has better interfaces for.. if in addition to that you don't need the app uninstall it.
Otherwise experiment with comp cache and lock launcher in memory.

another example, as i was reading this i was on the phone and i just finished the call and hung up, and i was previously in text messages, it took 12 seconds for my text messages to come up. thats just insane...
as for running services:
- GTalkService <--- I use GTalk all the time
- GenieRefresh Service (Restarting) <--- weird considering I disabled this widget, although I'd LIKE to have it back
- Maps FriendsAppWidgetUpdater (Restarting) <--- never used this in my life
- NewsRob UnreadWidgetProvidor (Restarting) <--- never used the widget before (as a matter of fact, you have to pay to use the widget and i have the free version... weird)
-Twidroyd Background Service <--- understandable, I use this constantly
- AKNotepad Snaptic Update (Restarting) <---- umm... I use this all the time but I don't know why a notepad program would need an updater service running... interesting...
- Swype <---- gotta have that
- CM Updater (Restarting) <--- Don't really think that needs to be on all the time. Can easily manually refresh that...
So that's it. I didn't realize this was included now. Very cool. On older roms I had to use task managers which don't seem to really work. I'm going to stop everything except twidroyd, gtalk and swype right now and see how that does... at the bottom it says Avail: 3.2MB+0.00B in 0 ... Other: 55MB in 4 ... While typing that the Maps FriendsAppWidget just popped back up... I'm gonna see if theres a setting...
In the meantime, does any of this give you any ideas? thank you so much for the advice. Also what does (Restarting) mean?

ezterry said:
Otherwise experiment with comp cache and lock launcher in memory.
Click to expand...
Click to collapse
oh and i have compcache not checked and launcher in memory IS checked... i just tried turning on the compcache option... lets see how that goes...

ok so...
now that i know about those things that were running, i stopped all the ones i don't need, and also went into the apps to see if there was any options for turning off automatic updates, background syncing, etc etc for those things... i'm gonna charge my phone while getting ready to go out and then we'll see how it goes throughout the evening. lets see if i make it home with more than 20% battery left (i'll be gone for like 5 hours). if so then we're on to something here still i find it weird that i can't have a few widgets loaded. but whatever, i'll take a smoothly running phone that lasts all day and i just have to click on icons to get to stuff any day... thanks for the help, i'll let you know how its going tomorrow.

the next day
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
so back to square one... any ideas guys?
thanks so much for any help you can give me. i really really appreciate it.

polarbearmc said:
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
Click to expand...
Click to collapse
Um... The compcache instability scares me a bit
Compcache has had issues (maybe still does) where the first time you enable it the phone crashes.. but then works fine with Compcache on reboot. Otherwise it really ought no make the phone unstable. (it may or may not speed things up depending on how memory is being used.. usually however it allows 12MB of memory that is rarely used to be compressed, allowing a little more active memory to be utilized) You may want to look into wiping dalvik-cache both on the internal memory and SD card:
Enter console and run (this will restart the phone)
Code:
rm -rf /data/dalvik-cache/*
rm -rf /cache/dalvik-cache/*
rm -rf /sd-ext/dalvik-cache/*
reboot
if you get an error about no files found thats not an issue; but other errors may indicate a problem.
This may help system stability (with or without compcache) .. but won't do anything about the battery life (nor speed unless something was seriously wrong)
-------------------
Unfortunately you will either need to erase all your apps and just run stock CM5 [maybe slowly restore your apps you really need] -- OR -- be very patient and debug whatever application(s) are causing issues on your phone (and maybe complain to the dev for failing to read/understand google's documentation on how to write android applications.. not that some of the google apps haven't quite figured that out until recently)
Thus again the main question is what is running on your phone.. The places I mentioned before allow you to see the services (most of which usually restart if you run the related application again) but not strictly all the details to look for.
Example 1 An widget service is likely holding onto memory starving timer services (those not listed) and swapping out other services (phone/launcher making everything feel slow) At the same time the widget is not very active usually and may not connect to the internet at all; thus may not reduce battery life.
Example 2 An IM client on the other hand may requires a service to keep TCP/IP connections alive, and if not coded properly may be very persistent and cause a slow continual stream of data from your phone requiring a large amount of power to keep the phone on 2G/Edge.
Example 3 A Task killer an kill tasks that re-spawn, or kill a task in use if it doesn't know better causing things to behave in strange ways.. so can killing services/applications from the setting screens btw.. but at least that is a one off by user decision not a automatic operation in the background. Tasks when re-spawned may require more data from the internet thus more power to 2G/Edge
User: Then the one that causes me the most problems: A user that keeps the phone in his/her pocket rather than surfing the web, checking XDA, or continuously checking the battery level is using the device less thus will have longer battery life. (careful to not fall into this trap)
Other Ideas:
SetCPU: set the sleep CPU low in profiles (sleep for me is 245/160)[/*]
Verify End action: Settings->End Button Behavior->Go to sleep[/*]
Set longer periods between polls in applications that poll the net (example twitter every 10 or 20mins.. not 5)[/*]
Larger net transfers on wifi if available (example tell newsrob to sync on wifi only) wifi drains the battery faster than idle, but is much cheaper if larger amounts of data are involved.[/*]
As you can see many things will impact the system. You will need to find the ones eating your battery
Another helpful screen for debugging this may be Settings->Spare Parts->Battery History and Settings->Spare Parts->Usage Statistics
I get between 4h and 12h batter life under semi-normal conditions. 4h = surfing 3g + tappatalk + games.. 12h check email/tweat if i get one.. otherwise stays in my pocket. I've seen my test phone hang out for days on a 2g network without data. (so you can always set your apn type to mms if you just need it to be a phone for many hours.. mms keeps mms support btw)
Ebuddy (and most other MSN/AIM/ect chat clients is frequently one of the biggest problems on my phone.. so if I need more battery those are the first to go.. and whomever it is can poke me on gtalk/txt/or wait
Good luck in your search.. Took me a while to make cm5 work as long as cm4.. most of it was mis-behaving apps that I either know to shut off when I need longer battery life.. or have found replacements for.. or avoid widget functionality if the widget was misconfigured. (

[Q] Random Reboots

Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.

I noticed it yesterday once (and I just got the phone then too ;-; ), and it was while I was opening the camera app, I decided to open the keyboard for some reason (I don't know why), the phone locked up for a minute and then just rebooted. I also had a temporary lockup while opening up the keyboard while opening Handcent, but it regained responsiveness after about 15 seconds. For me it happens to be something to do with the keyboard while opening apps. We need more people to reproduce this problem so we can get down to the root cause :|

Got two droid 3`s in my house and haven't experience any random boots.
Sent from my DROID3 using XDA Premium App

Happened to me while talking on the phone a few times. Got a replacement and it happened again. Never with the keyboard though. Very troubling especially with the second handset.

I have experienced reboots with the camera and camcorder apps lagging, and just general issues with those apps anyway.
Sent from my DROID3 using XDA Premium App

I haven't had it happen since I originally posted until today. Today it rebooted in my pocket.

Perhaps it could just be a heat issue. I noticed that another thing along with my other conditions I posted was that the phone felt really hot.

Immolate said:
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
Click to expand...
Click to collapse
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.

justinsaunders57 said:
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
Click to expand...
Click to collapse
1. Everyone knows that it's dual-core.
2. It runs Android 2.3.4. (Hence no root yet)
3. To the OP, no reboots. Had it since the 13th.
Sent from my DROID3 using XDA Premium App

I haven't seen another reboot since the 28th but I did have the odd experience last night of not being able to get a new wallpaper to take. In fact, I noticed that it had one of the stock wallpapers on it, the diagonal black and grey bars, but couldn't change it. Then this morning I thought about it and rebooted the phone. The last wallpaper I'd tried to change it to came up on reboot. Interesting but not alarming... unless it starts doing that frequently.
FYI I haven't noticed it running hot at any point.
Thanks for all the input everyone.

Probably seen it do it half a dozen times. IIRC it's not a full reboot, just the Android stack (i.e., same Linux kernel instance).
Have a logcat of one and don't seen anything that suggests where the problem is..just a whole bunch of "com.xxxxxx.xxxx has died" followed by normal restart log messages.

Odd that you all are experiencing this. I have not had a single reboot.
Sent from my DROID3 using XDA Premium App

This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.

I went into wifi settings and chose to forget all the connections. No more random rebooted.

rustynutzz said:
I went into wifi settings and chose to forget all the connections. No more random rebooted.
Click to expand...
Click to collapse
I wouldn't count on that being the issue.
I've had the problem out in the field (not connected to WiFi) and have had random reboots as well.

Heres a tip for troubleshooting this issue which i 90% guarantee - factory reset your phones put zero apps on them and tweaks, use it for a week and see if u get a reboot.
Then each week after add a single tweak or app(install/uninstall/freeze), may take a yr for some of us since we can't seem to stop downloading random badly coded apps lol...
-smc

For me at least SMC, I've had random reboots from stock during the first week. I'm putting it down to bad software for now.
I usually get 1 a week, sometimes less.

tliebeck said:
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
Click to expand...
Click to collapse
The same thing was happening to me, the whole rebooting and I went to Verizon for a replacement and got a refurbished DROID 3 Not a New :\
I really hope they fix this because its really bugging me. >:\
-eXsoR
Sent from my DROID3 using XDA App

I get a random reboot usually once a week or sometimes twice a week. It depends on how often I use my camera too.

[Q] Random Reboot after flash.

Since it seems Cyan has halted release of cyan 11 nightlies for the Atrix HD (indicative of what, I'm not sure), I figure it's worth solving this personal issue now; since it will most likely require another factory reset and I'd rather do it now.
Since day one of using custom ROMs, I've had the issue of my phone randomly crashing. Despite previously using only stable cyan releases, making sure to do clean resets (factory, dalvik, formatting system partitions,etc), letting the phone "stabilize" after installing (no clue what this means, but people seem to suggest just letting the phone sit about 10 min after flashing a new ROM, claiming a more stable experience), and even flashing a new kernel, I still see the same issue.
At this point, I've pretty much accepted that more likely than not, I'll have my phone randomly freeze and reset in my hands during basic use, calls, texting, internet use, listening to music, etc. Though clearing the Dalvik cache seems to quell the problem, it soon returns to the familiar behavior a day or two later. Any other basic solutions I might be overlooking? Suggestions, even obvious, very welcome.

CM11 switched to unified builds for the Moto 8960 family . http://www.cmxlog.com/11/moto_msm8960/
You can safely download a zip and dirty flash it over your current CM11 installation. At least that's what I did and I'm having possibly the smoothest experience so far on this phone/CM combo running Sat March 01 nightly.
About your crashes, do you get a phone freeze with signal loss before restarts? Do you always get a restart when the phone crashes?
Did you try enabling 2G only for a while? Do you crash while on WiFi?

You could also try another ROM such as Validus. I find the 4.3 release to be quite stable.

Thank you for the link to the new unified build. I've been busy with approaching midterm that I'd only heard of the new builds but didn't look into it personally.
As for the freezing. It's always been the same behavior: screen and all function buttons suddenly becoming unresponsive with no warning or change in signal (regardless of wifi or data use) remaining frozen for 10 to 30 sec, before returning to the unlocked bootload warning screen and the normal cyan reboot animation and normal lock screen after.
Everytime is has froze it will restart (i suspected a memory issue at one point, but after watching the memory usage long enough to see it randomly freeze but no change in mem, I doubt that it's directly the issue). I have not tried switching to 2g, so it would be worth a try. It will freeze regardless of whether wifi is off or on.
The only real "pattern" I could argue seeing is that it freezes most often during skype calls, while playing music (pandora and play music), and internet using browser; though it might only be because I'm actually paying attention to the phone while it is doing these tasks, I'm sure that it's probably freezing and resetting in my pocket thoughout the day. It will also randomly reset while looking through settings or non-data dependent tasks. Ironically, I've never had it reset on me while I was watching a youtube video. Go figure.

audit13 said:
You could also try another ROM such as Validus. I find the 4.3 release to be quite stable.
Click to expand...
Click to collapse
Any ROM, stable, nightly, cyan or other, with still see it start randomly freezing and rebooting an hour to a day after flashing.

-update*
After having switched to 2g signal instead of LTE, I haven't seen anymore randomly rebooting. I'm not sure if this was the issue but it's already been a day which is longest I've seen it remain stable.

1 Week later, back to the same behavior as before. Seems I might just screwed for having a stable modded phone.

WiFi Turning Off During Deep Sleep

Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.

Just as a follow up question, would the 'turn Doze off' option help with this? Surely I shouldn't have to do this though?

Am I the only one having this issue? That would suck. Even so, would anybody more adept at these things than me like to have a guess at solving the issue.

IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.

Greedyfly said:
Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.
Click to expand...
Click to collapse
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.

smilirulz said:
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.
Click to expand...
Click to collapse
I haven't 'cried' about anything, pal, so keep your unhelpful comments to yourself or help. Don't middle ground-it by offering your own personal, and incorrect, opinions.
I hadn't upgraded anything, I was running stock OS and stock marshmallow, so I had literally done nothing to my device other than switch it on and download the same apps I've been using for years.
I've also rooted several devices in the past with no issues and chime in when I can to help, but I'm not a dev and there are far more technologically gifted individuals operating in this forum which is why I sought help here... Not that I got much from you. But I'm more than capable of reading release notes and making sure I can revert backwards before installing anything.
Now to anyone still here, and with the same issue, it appears that carrying out the update to Nougat, re-adding my WiFi networks and clearing system cache solved the problem or at least for the first night. Should this change I'll update here.

ISO_Metric said:
IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.
Click to expand...
Click to collapse
Hi Iso, thank you for your response, I hadn't seen this until now.
The upgrade to 4.0.1 does appear to have done the trick somewhat as it stayed on overnight without issue. I did notice it wasn't on a little later this morning but I am giving the device the benefit of the doubt on that one as I have been messing about with certain things and it's possible I or a profile in tasker switched it off.
As an aside do you recommend any other potential fixes, just to be on the safe side.

Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery

ISO_Metric said:
Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery
Click to expand...
Click to collapse
I didn't factory reset, only Cache wipe after the upgrade, and as it seems ok so far, I am reluctant to factory reset the device as it took so long to set up in the first instance.
Should it start becoming an issue again I'll try it but for now...
Also I know there are backup options though I haven't found one that works flawlessly which gives me the confidence to explore this avenue just yet.

You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode

ISO_Metric said:
You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode
Click to expand...
Click to collapse
Are you sure ISO? The UI has been updated and the already snappy OS feels snappier. Is there a way to tell for sure if it's required?
If so, any good recommendations for backup capability. I have used Helium to mixed results and I can't use Titanium as I have no root (and don't wish to).

Maybe not but it all elts fails