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?
Using Nookie Froyo 0.6.8 eMMC.
I noticed my Wi-Fi takes a couple minutes or more to connect after the Nook had been sleeping. So I went into the Wi-Fi settings and I see "Wi-Fi Turning off...", then it comes on, then it turns off, and repeats over and over.
Eventually it will connect. Any idea what is causing this? This is a freshly install ROM. I've wiped it and reinstalled it and still have the same problem. And it works fine after a reboot, seems to only be a problem when it's gone to sleep.
I also installed Spare Parts and set the Wi-Fi sleep profile to never (this problem was happening before installing Spare Parts by the way) however that doesn't seem to prevent it from sleeping either.
I get the same thing. I'm assuming its a kernel thing, but I don't know, I'm definitely not a dev. Its happened in all the nightlies I've flashed, though.
yep this is a kernel issue i believe as it was better on the older kernels. i think it has something to do with your security settings.
try changing from wpa/wpa2 to something else perhaps?
i went to cm7 17 and so far it has been flawless. earlier builds were almost as bad though so i'm not sure if it will last.
That started happening on mine too. I just installed the newest kernel, that clean black theme, and nookie froyo. Prob the kernel.
It seems to help me on my nooki froyo 0.6.8 to put it back in standby by hitting volume up and power button at same time, then waking it back up and waiting for wifi to turn on usually within 30 seconds. It does not help and actually seems to make it worse to go into wifi settings to watch its progress.
Known issue with dalingrin's kernel. Go look on in the development forums.
Every other thread I see about a wifi problem kinda describes something different. My wifi messes up coming out of sleep. It will just keep connecting and disconnecting. Is their a fix for this? This is the only reason I left CM7.
This seems to be a common issue. I just turn off wifi before I hit the power button to sleep my nc. When I bring it out of sleep, I just turn wifi back on and it usually connects pretty quickly.
Which build are you using? And have you tried using a newer build?
The same issue with Nookie Froyo.
double post, please delete
buffnutz1 said:
Every other thread I see about a wifi problem kinda describes something different. My wifi messes up coming out of sleep. It will just keep connecting and disconnecting. Is their a fix for this? This is the only reason I left CM7.
Click to expand...
Click to collapse
I had the same problem with earlier builds of CM7, but switched Wifi sleep policy to never and am running CM7 nightly 19 and it no longer happens (still takes 30 seconds to a minute to reconnect if the nook has been sleeping for a long time). Now I have problems when I first turn the nook/wifi on!
I suggest updating to the newest CM7 and see if it's fixed. It doesn't seem to be specific to any one setup, but actually comes down to the individual nook.
I had the same problem with Froyo.
The problem went away after I swapped the OC kernel with stock one.
Hi! Can you tell me how you flush the stock kernel. I did the stock 1.0.1 via Rom Manager and it will just shutdown as soon as I login. Thanks.
I have the same wifi issue. I'm using Nookie Froyo 0.6.8. Everytime when I start my NC, the wifi turn on and off. Seems it's searching the signal? SOmetime it takes 1 or 2 mins. to reconnect! Originally, I thought that's hardware issue. It seems now this is a common issue for NC?
I read some post here, is to keep the wifi on, even when the NC sleep, but this will drain more battery.
Is there any better solution?
This happens with my rooted eclair NC as well. I'm now 99% sure it's an inherent NC issue. I though it was because I use Juice Defender to manage Wifi, but if manually turning it off can produce the same effect without the twitching wifi signal, then I'll do that instead.
Is there any app or method to make the wifi work better? Or is there any rom that can solve this issue?
Hi all;
I hope someone could point me to the right direction to fix this problem:
After installing & booting CM7, everything works fine. The problem is that when I put the NookColor into standby/sleep(one quick power button push), the LCD seems there's still dim light -- it doesn't go total black as the stock version.
The next morning, all my battery juice is gone. I believe the LCD dim on standby is the cause.
Also, anyone have good experience w/ Bluetooth? Mine skipping in & out every 2 seconds -- connection keep dropping. I tried turning off WIFI still didn't help.
Thanks in advance.
I assume this is your first time using a custom rom. Stock is able to turn off more of the hardware processes than the custom rom.
The reason for this, is because when the custom rom was set up to turn off the same processes, it would lead to the sleep of death, requiring a complete reboot. So you will lose more battery since it can't turn off all the processes like stock can.
As far as bluetooth... Try a hard reboot, and if that doesn't work. Then go into CWM and goto advanced>fix permissions.
Thanks for the reply,
I was able to turn on the BlueTooth. My problem is the connection -- keep dropping in & out.
Also it's my first time doing the custom rom. So everyone is turning off his/her NC once done using it?
Well I don't really know about the bluetooth, I'm merely suggesting you try those to see if they help. However, the range isn't very long with the bluetooth, so it could be just the item is to far away... What are you trying to connect it too?
Well, the custom rom does still preserve some battery by putting it into sleep mode. However, yes you could turn it off. I usually get it through a 8hr day through putting it into sleep mode, with some battery to spare.
Can Phiremod work on an sd boot or does it have to wipe out stock nook os?