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?
I would have posted this in the development forum in the KANG thread, but I cannot because I lack the ability to do so, and yes, I read the thread for this already. I am just having a problem finding 10 things to reply to to get access to post in that forum, and I do not want to run around posting random crap all over the forum that don't add anything. Maybe someone will merge this thread into the development thread for that or something.
I am having issues (on my Nook at least) with the latest build of KANG's 7.2-RC1
I am not posting looking for a fix, or a suggestion. I just want someone running this to try it for a day or two and see if it occurs with you...Mainly wondering if my problem is this release, or my Nook going to crap.
Basically, if i enable "create shortcuts to applications automatically" in the Play Store settings, my Nook Color locks up every now and then while installing apps.
The best way I have found to reproduce this is to start an install of multiple apps from your computer, and just let it run. I did have it also lock up on a manual install of the MyWater APK that was patched up for Nook Color...
Anyway, someone see if you can reproduce this on your end.
Well for the first time in 2 days it has locked up since i turned that feature off while installing something from the Play Store.
I will wipe/reinstall 7.2 and hope for the best. I do not see any replies to this, and I still do not see any similar reports on these forums or forums like it...so cross your fingers please
well since i was obviously faced with a reinstall anyway threw ICS onto my NC and took it for a test drive. for as early as it is it was really pretty impressive. i felt dirty when it was time to do the 7.2-rc1 reinstall... but i finally broke down and did it.
so far the nook has done installs of about 30 apps and has not skipped a beat. something was flaky with emmc so i wiped it and reinstalled clockwork mod, 7.2, did a data/cache wipe, and then installed the market... booted, market updated, and everything has been smooth ever since.
guess i solved my own problem
Hi guys,
I'm new to this forum but I have read all rules before posting. I hope I got everything right. If not, please let me know and I'll make changes ASAP.
I have installed Paranoid Android 3.68 last week and have been experiencing this problem (couldn't post it in that thread because I am still a newbie).
My phone crashes into Safe Mode at least once daily without me doing anything. Every time I reboot to normal mode, I would have to restore my 3D Background, Swiftkey, and NiLS apps. So I'm guessing that the crash happened due to (one of) these apps. Could this be an incompatibility issue? Is there any way I can prevent this from happening because it gets quite troublesome to restore these apps so often...
Thanks a lot!
mycxmei said:
Hi guys,
I'm new to this forum but I have read all rules before posting. I hope I got everything right. If not, please let me know and I'll make changes ASAP.
I have installed Paranoid Android 3.68 last week and have been experiencing this problem (couldn't post it in that thread because I am still a newbie).
My phone crashes into Safe Mode at least once daily without me doing anything. Every time I reboot to normal mode, I would have to restore my 3D Background, Swiftkey, and NiLS apps. So I'm guessing that the crash happened due to (one of) these apps. Could this be an incompatibility issue? Is there any way I can prevent this from happening because it gets quite troublesome to restore these apps so often...
Thanks a lot!
Click to expand...
Click to collapse
Hi there;
Try removing one app at a time and observe and good luck
Hey all, got a problem which needs solving - haven't been able to figure this one out myself.
Okay, here's the dealio:
I'm running CM 12.1 nightly on my HTC One (m7) device and haven't really had any problems which proved to be as hard to solve as this one. My launcher - i use ADWLauncher -constantly crashes no matter what I do (Trebuchet is acting no differently).
Also noteworthy, many areas of my settings are unreachable (such as settings->apps) as they immediately crash upon attempting to access them as well. I've tried numerous methods to fix this annoyance to no avail.
This has been ongoing for over a week now although yesterday my launcher worked flawlessly for a good 8 hours (just the launcher, the other crashables within 'settings' were still crashing. And now for some reason a selection of my apps are crashing as well.
kayohbe said:
Hey all, got a problem which needs solving - haven't been able to figure this one out myself.
Okay, here's the dealio:
I'm running CM 12.1 nightly on my HTC One (m7) device and haven't really had any problems which proved to be as hard to solve as this one. My launcher - i use ADWLauncher -constantly crashes no matter what I do (Trebuchet is acting no differently).
Also noteworthy, many areas of my settings are unreachable (such as settings->apps) as they immediately crash upon attempting to access them as well. I've tried numerous methods to fix this annoyance to no avail.
This has been ongoing for over a week now although yesterday my launcher worked flawlessly for a good 8 hours (just the launcher, the other crashables within 'settings' were still crashing. And now for some reason a selection of my apps are crashing as well.
Click to expand...
Click to collapse
Do not expect nightly builds of CM to be stable and bug free. You should only flash a nightly build if you are ready to deal with various bugs. I would try the latest stable or at least snapshot build (if available) and see if you have the same problems.
I hadn't upgraded for a few days when this started which leads me to believe it's not cm's fault but I'll take your advice and give a go with a stable then post my results. Thank you for your time [:=
Got it
Turns out it was an application I had installed causing some sort of confliction. Managed to uninstall it (after a whole lot of messing around due to being unable to access most of my system) and everything has been working just fine ever since.
The app was SD Maid.......