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?

[Q] Any luck with designgears JH7_OTA.zip?

Before taking the plunge I am looking for success/problem comments from those who have failed with OTA and then tried the JH7_OTA.zip approach.
I have searched and I don't see many comments yet.

It flashed fine for me but now GPS is causing my phone to lock up. Happens if I turn off GPS and just now happened in google maps while driving. Had to pull the battery to reset.

Worked great for me. GPS is working like a champ too.
Thanks to all who worked so hard on the flash.

I updated with the JH7_OTA.zip and it went well, but my phone is worse than before... laggier, bottom buttons seem less responsive (could be due to the increased lag) and the GPS will not see any satellites and much less, lock. I'm sure it's not the file... just another defective unit. This is my fourth Captivate. First two simply lost the ability to connect to 3G and WIFI, the third had a great GPS but the search function would randomly self activate and the body creaked like an old rocking chair, and my current one.

bigdoug2005 said:
It flashed fine for me but now GPS is causing my phone to lock up. Happens if I turn off GPS and just now happened in google maps while driving. Had to pull the battery to reset.
Click to expand...
Click to collapse
This happened to me. You don't need to pull the battery. Just hold the up volume button and power button for about 10 seconds and the phone will shut off.

Edit Disregard my post.

It's working great for me. I usually stream radio during the day and it usually will drop out once or twice an hour. Today, it has been streaming just perfectly with no dropouts. Thanks to all of those that got this working!!!!

No problems here, either. I did remove my previously installed LagFix first, and I flashed over JH3. GPS seems to track me a little better than before, and it does seem that perhaps the radio is working a bit better and battery life is slightly better as well.
I have the same commute on the train each morning, and pretty much do the same routine each time, so that's a good way for me to compare things after a change. This morning I noticed that my streaming radio barely cut out at all in areas where the signal is low, much less than before, and when I got into work my remaining battery PCT was a little better than usual. I applied the RyanZ lag fix from the market this afternoon and overall am pretty happy so far!

My GPS is still jacked up.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Worked great for me. everything working including the 3 button, usb, and better gps/compass. Things other people were complaining about not working. I flashed odin and rooted with update.zip before i applied this rom.

luck? Sure... but...
I went with the Cognition ROM as JH7_OTA didn't do the trick for me.. All in all I like the Cog experience (install went smoothly, seems fast, no weird errors), but the GPS is definitely not fixed. Accuracy is better in that my phone can locate me on the neighborhood level, but it is still not locking and is locating me blocks away from where I'm actually at.

Worked great for me.

No problems flashing for me. That is the answer to your question, now to issues I had.
HSUPA was not working for me. So I did the revert HSUPA to get 3G back and it killed all data for me. So I did a nandroid back to my previous ROM and then I got FC so I had to Odin and then reinstall my nandroid. That is why I don't like his zip, it works fine but if you want to change ROM's you have to basically flash odin to make sure you have no issues. That is how it was for me, others might be different and then you have the nut swingers who are only for Cognition.
I will say this issue happened to me 3 times. I think the issue might stem from being unable to remove voodoo since it is packaged into his zip. Not positive why I had the issue but for the time being I am trying other alternatives.
Last edit: Just went back to his Cognition thread and see that he pulled the HSUPA zip, so it wasn't just me having issues. Unfortunately stuff like that lets me know that all in one package zips like that need to be worked on more.

flashman2002 said:
I will say this issue happened to me 3 times. I think the issue might stem from being unable to remove voodoo since it is packaged into his zip. Not positive why I had the issue but for the time being I am trying other alternatives.
Click to expand...
Click to collapse
you probably should have removed the voodoo lagfix to try to flash other roms since clockwork DOES NOT work with voodoo
alternatively you can install cognition, and install a different kernel if you dont want voodoo lagfix...

flashed it and it's great! except the gps is kind of on and off.

[Q] Some remaining probs with doc 7.6.2

I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03

quite alot galaxy s users have reported issues with the gps reception i used to think its just a driver issue but upon reading into it would seem its related to the antenna. The wifi also suffers from this problem for me it does anyway. you can try out gps booster lite from market it does help outdoors to get a faster fix as for battery issues well im not so sure you would prob better asking in that thread if your still not heard try sending a pm that should work. good luck

boris03 said:
I am trying to get a solution for these 3 problems I am facing with Doc´s 7.6.2.
Maybe it is not a big deal to make it a perfect ROM but these 3 topics are annoying:
I wrote the same message already in Doc´s threat but no answer at all. in 5 min 10 new messages so nobody really takes care for a new question
Hi Guys,
Some problems I do have with the 7.6.2 and for sure I am not alone with these errors.
1 From time to time high energy consumption but sometimes not - this is crazy. One thing I realized when alarm is switched on for all weekdays then it sucks almost 20% in 5h - just in standby mode. Whats wrong here?
2 GPS signal is bad. When you using this tracking tools eg. cardio trainer it looses half time the GPS signal. Was definitely not with older ROMs.
Is that the modem version?
Is this part of the kernel?
3 Bluetooth works but whenever activating and deactivating getting a stupid message about an opp bla bla.
What is wrong?
Who can help?
Thanks
boris03
Click to expand...
Click to collapse
1.) Turn off your lagfix, run stock RFS see if you still get the issue.
Do a fresh install dont add ANY apps other than stock, observe for 1-2 days of battery usage.
2.) GPS is a hit or miss, hardware is broken.
3.) Never had issues with BT, I use it on a day to day basis to pass around files at the office.

Are you using one of those OC kernels? Or any of the suggested kernels for the matter? I was using Super Optimized Kernel for a while and the battery drain was outstanding even on the non-OC versions. Switched to SpeedMod 300hz. Haven't monitored the battery though but it seems better with normal usage. Also, what lagfix are you using? For a time I was using the Ext-4 Overkill lagfix from the ULF and I noticed considerably less battery life.
As Earlz suggested, try disabling lagfixes and tweaks and monitor..then if it is better than before perhaps using a different lagfix would be a solution. Try switching up kernels (remembering to disable lagfixes prior). Try running different launchers too. I'm no expert on how these things work and affect battery life, but this is all based from personal experience.
My GPS never worked from the start no matter what firmware/ROM I'm on so it seems to really be a hardware issue as EarlZ mentioned. If the problem came about after flashing 7.6.2 then try reflashing to stock firmware with repartition and installing 7.6.2 again after clearing cache and factory reset. Somehow that (having a super clean install) usually fixes random problems I get with any ROM. I'm not certain if it will have any affect on GPS performance but it's worth a try.
Bluetooth is still working fine for me. Perhaps the aforementioned clean install advice I gave could remedy this.

Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?

darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
There is investigation on that one...
For now, it seems to be a modem issue from the stock modem of ADJP5
Flash another modem seems to fix this issue

darkfire_bg said:
Hi there, i rescently installed DJP5 v8.0.1 . And have some problems with it. When i'm making call i hear the other side perfect, but they dont hear me well. Is it some issue with the ROM or ? Have someone else experienced similar problems?
Click to expand...
Click to collapse
Sigh....Thats covered in the main thread for this rom, try a different modem.
Sent from my GT-I9000 using XDA App

[Q] Odd battery drain with partial wake usage on Maps?

Hi All,
I'm having this odd battery drain. I've installed Battery History and saw that under partial wake usage, "Maps" is top on the list. Even higher than "Android System".
Now, does this "Maps" refer directly to the Maps app? Or does any other app also reports as "Maps" on battery history?
Odd is that even after reboot, it still gets high partial wake usage but checking Samsung's task manager, the Maps app is not running, or at least not visible on the current tasks.
Does anyone has experienced this? I'm using Doc's ROM v9.9.5 (JS8) with Damian's Kernel and Crysis Revolution Theme, if that can be of help.
A second question: If I was to go back to an Eclair stock ROM, that would upgrade through KIES to Froyo, which version would I use? My product code is HKDXEU. Also, do I need to change bootloader if I was to do such thing? Or does Gingerbread's bootloader would work on Eclair?
I was thinking of reverting back to Eclair (repartition, 512.pit), then upgrade through Kies and then go to Doc's ROM again. Kind of really reseting from "as much original" as it could be.

tfvaldo said:
Hi All,
I'm having this odd battery drain. I've installed Battery History and saw that under partial wake usage, "Maps" is top on the list. Even higher than "Android System".
Now, does this "Maps" refer directly to the Maps app? Or does any other app also reports as "Maps" on battery history?
Odd is that even after reboot, it still gets high partial wake usage but checking Samsung's task manager, the Maps app is not running, or at least not visible on the current tasks.
Does anyone has experienced this? I'm using Doc's ROM v9.9.5 (JS8) with Damian's Kernel and Crysis Revolution Theme, if that can be of help.
A second question: If I was to go back to an Eclair stock ROM, that would upgrade through KIES to Froyo, which version would I use? My product code is HKDXEU. Also, do I need to change bootloader if I was to do such thing? Or does Gingerbread's bootloader would work on Eclair?
I was thinking of reverting back to Eclair (repartition, 512.pit), then upgrade through Kies and then go to Doc's ROM again. Kind of really reseting from "as much original" as it could be.
Click to expand...
Click to collapse
hi. I had this problem with my HTC Desire 2.3.3 Oxygen Rom by adamg. why don't you try to signing out of latitude? it seemed to work for me..

I never logged in on Latitude (or can't remember doing so). But I'll check this. Thanks for the tip.

tfvaldo said:
I never logged in on Latitude (or can't remember doing so). But I'll check this. Thanks for the tip.
Click to expand...
Click to collapse
I thought I solved my random battery drains with 2.3.3 but I think Maps is another factor. Anytime I use a Maps related App (like MyTracks a few days ago or Places + Navigation today) not the Maps app would show up in the battery history, but "Android OS" is rising and sucking the battery dry. The CPU never goes to "deep sleep" until I restart the phone
I signed off latitude some weeks ago, but i looks like some parts of Maps causes problem with the system :-(

Try uninstall and fresh install from the market
GTi9000 insanitycm010/insaneglitch

[Q] Galaxy NOTE SOD problems.

My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:

Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2

abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware

Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.

Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?

if u're using pure stock rom still facing the same problems then definitely is hardware issues！
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...

Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..

psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2

I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab

updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?

SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...