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?
So I love froyo and for the past week that I've had it (via ota) it has been really great, but today I began having these sudden problems:
I can't install certain apps (market or sideloaded), even though I have plenty of room for them.
Random apps that are normally stable just crash out of the blue.
The phone just keeps slowing down and things are taking longer than they should for both 2.1 and 2.2.
The phone crashed today, meaning it decided to reboot on its own accord, once when I was running a few apps at once (something that I do almost every time I pick up the phone) and was switching between them, the second time was when I had some background processes and I was browsing the web.
I was just wondering if anyone else was experiencing these problems, and if you are did it just happen suddenly one day like me or was it from the beginning? I also want to know if anyone has suggestions or a diagnosis that I should consider before emailing google.
Thanks for all the help,
Liam
Try resetting the phone to Factory (Settings-Privacy). Or if you're rooted...Wipe.
SiNJiN76 said:
Try resetting the phone to Factory (Settings-Privacy). Or if you're rooted...Wipe.
Click to expand...
Click to collapse
Does that wipe apps, settings and all other data, and is there a way to get it all back?
Let's start with some basic information. I am running not rooted stock Froyo 2.2.1, Baseband version I9000XXJPY, Kernel version 2.6.32.9 [email protected] #1, Build number FROYO.XXJPY. Using stock TW Launcher.
In the morning I've moved couple of apps to SD card. Few hours later my battery went flat and the phone turned off. I've replaced the battery with a fully charged one and the phone was booting quite a while and when it finished it started with locale setting screen. At the same time several apps started to force close unexpectedly. When I went through all the initial settings the wallpaper was the same, icons and widget layout was the same. There were many apps missing (I reckon all of them were installed on the SD card). Many apps that remained were either force closing just after starting or had the settings reverted to defaults.
Some examples:
- Android Agenda widget was in its place but settings missing.
- I've reinstalled TwittCaster and moved to Phone - although it looks like the data/settings are being wiped after every phone restart and I need to put my login details every time.
It looks like many of the apps are reverting settings to default every time I restart the phone.
Both my external and internal cards seems fine, I can access and open files (e.g. photos and music) on them.
When I was trying to install some apps from the Market I was getting error messages that the app cannot be installed in the chosen destination, or there is not enough space. But after few tries I've managed to install them. As far as I know there should be quite a lot of available space.
I've tried to unmount/mount external card, take it out and in again. I've formatted cache partition from recovery mode. I've tried to clear RAM with Task Manager.
I would be grateful if someone could help me to diagnose the reason behind all this, help me to fix it and prevent it from happening in future. I really want to understand the problem and the trigger so I can avoid similar problems in the future
I will appreciate any help.
Thanks!
Sorry to bump, but this is really driving me mad.
It appears that I need to reinstall every app as they all closing unexpectedly on starting. after I reinstall them they loosing settings every time I restart the phone. Is it an external or internal card issue or maybe internal memory? Please help!
I have also noticed that Android Market is quite slow on me. Muc, much slower then before it ask happened.
Sent from my GT-I9000 using XDA App
sounds like hardware failure to me. Its back to factory and exhibiting problems. Why not take it back and have it replaced/fixed?
Sent from my GT-I9000M using XDA App
Strange problem this...
I guess format, reflash and clean install of apps would be a better option... instead of just re-installing apps...
I just wish to avoid sending it for a repair. This is a new replacement I get several days ago from Samsung, for which I was fighting for 4 months.
Anyway I will try to format and reset everything and build everything up from scratch. But if only I could understand how and why it happened maybe I would be able to prevent it from happening in the future.
Is there a special way I can format sd cards before installing and moving apis there?
Sent from my GT-I9000 using XDA App
Hey all,
I am currently running my VZW Galaxy Tab with a stock 2.2 Froyo build that is rooted and running Boushh's KhasMek Kernel V5.
Ever since I installed that kernel, I have been experiencing constant force closes. It's really not any one app either, it is most of them. So far, I have put the freeze (via Titanium Backup) on all the apps that have FC'd a lot that I don't use. Maps was one of the biggest culprits. Facebook FCs a lot as well, and the only way to fix it is to go into app management and clear data. Similar issues with random games and such as well.
I have tried uninstalling and reinstalling multiple apps, and this helps for a time, but doesn't last too long. I have tried switching launchers, just in case it was somehow related, but it doesn't seem to be.
Basically, whenever I leave the tablet on idle for more than a few minutes, when I unlock it something hangs and I get an FC of a random app.
And a lot of times, it just does the single vibrate, followed by two quick ones, and nothing comes up as having FC. But, in the mean time, the tablet is unusable until it hits the second set of vibrations.
This is extremely annoying and is preventing usage of the tablet for periods of time. So, I am wondering, is anyone else experiencing this? If so, what have you done to fix it? At this point, I am inclined to just revert back to stock, though I would rather not.
Thanks for any insight.
As of now, I am constantly getting
com.google.process.gapps
force closing.
Hi guys,
I just came from CM7 to this CM6 by Milaq. Love it, everything is much faster, always enough RAM.
I did 3 wipes, flashed ROM through OpenRecovery, reboot, flash gapps for HDPI, reboot, and then restored some apps with titanium backup.
I'm having some issues, I'll list them in order of how much they're bothering me:
1) A bunch of system apps aren't showing up in the market and therefore aren't getting updated. Ex. Facebook, youtube, twitter, etc. What do I do and why did this happen?
2) Titanium backup seems to fail at restoring data for a lot of apps (ex. Shazam, LauncherPro, ColorNote, etc). At the very least I want my Shazam tags back. It doesn't say it fails, it says it's successful but once you open the app, the data isn't there. Interestingly enough, the data IS there in /data/data, at this point basically just taking up space. Now I'm wondering how many apps it restored data to which the data just sits there, useless.
3) The custom LED blink frequency in HandcentSMS just broke. It was working fine until I turned the CM setting "succession" on, and then off. Basically now the LED either blinks as it wants to (no matter what setting), or will stay on if I choose the "Default" setting OR a custom setting with 0 for the "off time."
HELP please?!?
I have had similar problems with market some time ago once switched from CM7 to CM6. I did several cleanups of the marked data and even full wipe plus SD card cleanup (there are some system folders) and suddenly it helped. Can't confirm what are the correct steps to recover from the problem ...
Additionaly had an impression the Google backup is causing some troubles so disabled it.
Edit:
The led blinking is controled by some hardware device so either you can't change the frequency OR apps controls the led by itself using main CPU, which costs extra battery ...
I stay with apps settings only and not change anything by CM settings and works fine. Every time have beeing playing with CM led settings ends up with some mess I could not recover from.
Sent from my Milestone using Tapatalk
janosik47 said:
I have had similar problems with market some time ago once switched from CM7 to CM6. I did several cleanups of the marked data and even full wipe plus SD card cleanup (there are some system folders) and suddenly it helped. Can't confirm what are the correct steps to recover from the problem ...
Additionaly had an impression the Google backup is causing some troubles so disabled it.
Edit:
The led blinking is controled by some hardware device so either you can't change the frequency OR apps controls the led by itself using main CPU, which costs extra battery ...
I stay with apps settings only and not change anything by CM settings and works fine. Every time have beeing playing with CM led settings ends up with some mess I could not recover from.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
1) is solved: I fixed the market by rolling back to the old market that is included with gapps. I forgot to write that I had updated to the new one (provided by Milaq though so I thought it'd be fine). All apps are seen now.
3) As for the LED, I know what you mean, as soon as you touch CM settings it gets messed up!!! How can I reset the CM settings? Tried data wipe through titanium backup on CM settings but it didn't do a thing... This is gonna bother me to no end.
EDIT: I somehow managed to find this thread: http://forum.cyanogenmod.com/topic/18051-solid-led-notifications/
Going to CM settings, selecting Succession and then clicking cancel at the dialog box seems to have brought the blinking frequency function back to handcent. Although...it's kind of buggy, doesn't alway blink properly. But at least some change is visible now. Does your led listen perfectly to on and off times?
Flyview said:
...
Going to CM settings, selecting Succession and then clicking cancel at the dialog box seems to have brought the blinking frequency function back to handcent. Although...it's kind of buggy, doesn't alway blink properly. But at least some change is visible now. Does your led listen perfectly to on and off times?
Click to expand...
Click to collapse
I do not use Handcent just the stock app and do not chage the CM led settings and everything works as expected.
In case seriuos problems Titanium Backup + full wipe is OK for me
Sent from my Milestone using Tapatalk