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] Samsung Galaxy i9000 freezes on standby

I have had my phone for about 2 weeks now, and this has been an issue since about day 1. I will set my phone aside while doing other things. When I want to use it I pick it up and press the power button to activate the screen. It seems that about 20% of the time the phone is non-responsive. I can't even receive calls/texts/email while it is in this state. I end up pressing the power button for 10 seconds or pulling the battery to get it to reboot. Everything seems to work fine.
I have heard that this could be a result of a reception issue, and that an update would be released in September to solve this issue. Is this information correct? Has the update already been released? I believe I am running the most current version, 2.1 update 1
Is there a software fix? Do I have a defective unit that needs to be sent in for repair? Is there a setting I need to look at? Any assistance would be appreciated.

you are describing the typical scenario of too many background services and apps running taking up too much resources thus making the phone non reponsive
install Auto Run Killer http://forum.xda-developers.com/showpost.php?p=8123924&postcount=40
then tick all the apps to disable reboot your phone
then you can choose which apps you really want to let lose for it to run in the background

It's also entirely possible it's faulty though

I don't think it is a matter of apps running because there are no active apps running when I am not using my phone.
I guess I am looking for an answer that tells me that this is an known issue with this model and I wiould be better off with a different product, or if I will be safe to get it replaced/repaired.
Ideally I would love to hear it is only a matter of a software patch or something similar.

go get an iphone
there is no point helping some one that have their mind already set on their own ideas already

Well that was a pretty useless post. The only idea my mind is set on is to get my hands on a dependabel phone, preferably the one I have. You suggested too many apps running, fine, but unless they run automatically on reboot and/or the 'active applications' window that runs by default is inacurate, there aren't too many resources being used and nothing running.

you'll be surprised what runs under the hood
you can run this and find out
http://forum.xda-developers.com/showpost.php?p=8156087&postcount=58
Android System Info
another good thing to disable is the Media Scan

AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Don't be so quick to assume your suggestion was correct either, AllGamer:
http://forum.xda-developers.com/showthread.php?t=775017
Thus far nothing in that thread has suggested taxing the system too far. In fact, hardly installing anything at all from a fresh factory reset still has this problem and no one yet has really worked out why aside Samsung saying the hardware is damaged. I was on the phone to them today, same thing said.

i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen

AllGamer said:
i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen
Click to expand...
Click to collapse
I see no truth in the signal claim I've said why in the other thread. But this is the point, it is an issue a few of us are having from all over the place but as of yet there is absolutely no distinguishable pattern. As I say, a completely fresh phone with official firmware and no installs also has the problems. It's a very frustrating situation because no one can conclusively point to software or hardware yet. Samsung keep saying the same thing, send it in, send it in..

it's true the only way to diagnose those will require to be hands on, and run tests to pin point exactly what is causing that.
Eclair doesn't have the option to auto upgrade, so that's definitely not it
Lag is likely, but what, or which stock apps can cause so much lag?
signal even when the phone is having a hard time switching and scanning for a new signal it shouln't keep the phone unresponsive for such a long period of time unless it's lagging
my Old Treo did that, anytime it lost signal and regained signal there was a minor pause, or a looooooong pause if the phone was lagging
if this is the same case with the SGS we just need to figure out which App is running in the background that is dragging the entire system down.
it could be the internal SD which might have become defective, thus locking up the phone, similar to those people that can't get past the boot screen
i can't think of any other plausible causes at the moment.

Well, I can tell you: having experienced the problem a number of times, it is almost certainly not the lag scenario you have described - this is a proper lock-up. My guess (since it does appear to have some correlation to cell switching, or other signal-related issue) is a bug in the baseband drivers, or something similar, resulting in a panic. I might see if there's any way to get a dump out of this thing to prove it, but at the moment it's just a guess, so I'm not going to tell you that's the definitely the reason, or that you're stupid if you don't agree, even though I'm more qualified to do so, since I've actually experienced the problem.

AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Android is designed to not need auto task killers. It is purely a myth that they are needed whatsoever. This is linux we're talking about here, not windows.... It's possible he has a single app installed causing the issue, but the ideal fix would be to figure it out one app at a time and get rid of the faulty app.

[Q] Anyone care to share up-to-date SoD remedies?

There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work for me...
-Increased minimum clock speed
-Increased voltage of minimum clock speed
-Removed Titanium Backup
-Removed all third party apps
-Disabled deep idle
-Removed/didn't use task killers
-Tried various ICS & JB ROMs
-Tried various ICS and JB kernels, including baked-in versions
-Tried i9000 bootloaders
These are pretty much all the details I have so far on these SoDs, hopefully they add up to a possible cause or explanation...
-SoDs happen anywhere from 1-2 times an hour to 1-2 times a day and only when screen is locked/phone is idle
-Having GrooveIP or Skype running doesn't prevent SoDs, but Pandora Radio running seems to prevent it
-Sometimes on a fresh ROM install I can go about 24-36 hours before the first sleep death, but after that they occur normally
-If I unlock the screen every few minutes it seems to stay on. If I let it sit anywhere from 15-30 minutes or longer then it will usually shut off.
-The only time I can get this phone to not suffer an SoD is on stock software(GB KK4). Not sure what this means, but it is aggravating because I would like to have better software.
What remedies have you tried, and what worked/didn't work for you?

johnnyrichter said:
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.
So far the solutions I've tried that did not work are...
-Increase minimum clock speed
-Increase voltage of minimum clock speed
-Remove Titanium Backup
-Remove all third party apps
-Oneclick back to stock with most recent GB bootloaders
-Disable deep idle
-Remove/don't use task killers
My sleep-deaths are random, almost always occur over night while I'm asleep, can sometimes happen within seconds or minutes after locking the screen. Leaving apps running also doesn't stop the problem(GrooveIP is always running, Skype is running most of the time).
The only thing that stops sleep deaths on my phone is leaving it plugged in.
What remedies have you tried, and what worked/didn't work for you?
Click to expand...
Click to collapse
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.

BWolf56 said:
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
Click to expand...
Click to collapse
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.

johnnyrichter said:
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.
I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
Click to expand...
Click to collapse
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?

BWolf56 said:
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel user config (not saying this is the case here).
Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?
If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.
Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
Click to expand...
Click to collapse
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.

johnnyrichter said:
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.
The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
Click to expand...
Click to collapse
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?

BWolf56 said:
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.
If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
Click to expand...
Click to collapse
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.

johnnyrichter said:
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.
I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.
I have also tried no OC with at least three different kernels/ROMs.
Click to expand...
Click to collapse
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.

BWolf56 said:
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).
So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.
You got some testing to do, I'll be looking forward to the results.
Click to expand...
Click to collapse
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.

johnnyrichter said:
The only apps that have been consecutive across all my different software installations have been...
-Gapps
-Gmail
-Facebook
-Pandora
-GrooveIP
-Heywire
-Skype(Only been using this for a couple of weeks so I can probably rule it out)
I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.
You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
Click to expand...
Click to collapse
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.

BWolf56 said:
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
Click to expand...
Click to collapse
I'll check out that app right now and report back with any findings.

johnnyrichter said:
I'll check out that app right now and report back with any findings.
Click to expand...
Click to collapse
Booted phone up just now after an SoD and the only log available is the one it just started. So if it logged anything before it looks like it didn't save it. Crap.

One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.

johnnyrichter said:
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...
-GoLauncherEX
-Skype
-Gmail
-Facebook
-Opera
-GrooveIP
-Heywire
While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.
If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this.
Click to expand...
Click to collapse
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app

BWolf56 said:
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Still no SoD and that's with/without Skype running. GrooveIP boots with phone.
If it won't SoD on stock software then I wonder what the problem could be? It's SoD'd with every kernel and ROM I've ever tried.

Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app

JoeCastellon said:
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?
I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
SoD means, while idle, that it randomly turns itself off. It was a defect in X amount of phones produced up to a certain IMEI number, and ATT/Samsung at one point offered an exchange program so people can turn theirs in for a model that didn't have the issue.
What you're suffering from is low memory. You probably have apps running in the background that are utilizing X amount of RAM, and your browsing/gaming is eating up the rest which slows down the phone. Some ways to fix this...
-Use a kernel that allows you to increase maximum memory. I think Devil kernel allows up to 396mb with no downsides, and 413mb at the cost of something that has to do with playing a certain video resolution IIRC.
-Use a task killer. This lets you kill running tasks except for those you choose to "lock." Some advise against using a task killer, but honestly I've yet to have a problem with any of them. My favorite is the one you can get for GOLauncherEX.
-Use Titanium Backup to delete(or freeze if you buy the pro version) apps that you don't use that you can safely remove, specifically items that constantly run in the background eating up your RAM.
-Use a different ROM. There's plenty of ROMs out there including slim/aosp/etc releases that are faster and arguably better-performing.

I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.

BWolf56 said:
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.
I'm not sure if that would change anything, but try flashing Mosaic.
Click to expand...
Click to collapse
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
ETA: If it matters any, when I got the phone I believe it was on GB KK4 and was never modded before. When I got it I used the easy-root to corn 7.0a method and first ran Legend5 ICS ROM. That was the first time I started suffering sleep deaths. Ever since then I have used the one-click back to stock w/ GB bootloaders before using any other kernel or rom.
I've used several different kernels/cwm versions to obtain root, at least 6 different ROMs, several different versions of gapps, and numerous other kernels after ROM installation. I've also used the baked-in kernel of each ROM for at least several days before upgrading to something like Devil or Sema. SoDs on everything, both ICS and JB.
I have also tried one-clicking back to stock with what I believe were "up-to-date" GB bootloaders. This was posted by another member that did it and fixed his SoD problem. It didn't produce any sort of a change for me.
I have not tried checking for SoDs on just a root(without ROM). I suppose if I did this I could figure out if it's the root or the ROM that is triggering the sleep deaths, but even if I did get any results from that I'm still not sure how to figure out exactly what's causing the problem since this event apparently can't be logged.

johnnyrichter said:
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.
Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?
Click to expand...
Click to collapse
Mosaic is a ROM that was made by The Family; http://forum.xda-developers.com/showthread.php?t=1061203
It is I9000 based so I'm thinking you won't get any SoD on it. Thing is that it's not JB based. Devs aren't porting from I9000 anymore so you won't find a I9000 ported JB ROM. (Hoping I'm not wrong on this lol)
And yeah, many users reported that flashing the I9000 bootloaders with a JB ROM fixed their SoD problem. Back in GB, it wasn't suggested to have I9000 bootloaders and run a I897 ROM (music player wouldn't work and some other little things) but it seems fine now.
EDIT: I highly doubt root is the problem.

WiFi Turning Off During Deep Sleep

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

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

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

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

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

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

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

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

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

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

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

Maybe not but it all elts fails

Is samsung ruining our devices intentionally?

i have a display issue with my note 8 (N950f), the screen gets greenish and messes up the colors making it very unpleasant to look at (started happening right after september 2020 update) i could fix it by pressing the power button, taping the screen to turn on always on display but then it would switch back to that annoying green display after seconds or minutes (weirdly enough the Always On Display is always good and never shows any green), so i tried to fix it by : Factory reseting, clearing cache, flashing stock os, custom roms pie, 10, 11, nothing worked until i tried flashing a custom kernel (Phantom Kernel for Pie) on a stock os. that fixes the green screen issue temporarily (2 to 3 weeks) i mean it's still there but it gets green very rarely, until it starts to gradually get worse overtime. And also im not the only one! i found another user @B3anbeanbean who has the EXACT problem and he fixes it like i do with the phantom kernel. This can't be a coincidence.

If you have a fast, stable platform that fulfills its mission, leave it be.
My 10+ is still running very well on Pie and will be for the life of the device.
If Samsung doesn't break it, Gookill Android surely will. What applies to MS XPx64, W7 applies more so now with Android.
For all those "upgrades" what did you gain?
Rather than enjoying the device how much time did you lose? Which bring me back to my original statement.
Play games and don't let the game play you.

blackhawk said:
If you have a fast, stable platform that fulfills its mission, leave it be.
My 10+ is still running very well on Pie and will be for the life of the device.
If Samsung doesn't break it, Gookill Android surely will. What applies to MS XPx64, W7 applies more so now with Android.
For all those "upgrades" what did you gain?
Rather than enjoying the device how much time did you lose? Which bring me back to my original statement.
Play games and don't let the game play you.
Click to expand...
Click to collapse
mate, i would've never touched the phone, i love pie and i dont mind using it, the problem occurred on itself on stock os i hadn't touched anything. i did those "upgrades" in hopes of fixing the display.

omae_wa said:
mate, i would've never touched the phone, i love pie and i dont mind using it, the problem occurred on itself on stock os i hadn't touched anything. i did those "upgrades" in hopes of fixing the display.
Click to expand...
Click to collapse
If it running right when first purchased it's likely hardware if a factory reset wouldn't resolve it.
When you start changing firmware rather than find the root cause you throw more variables into the mix. Making it more difficult.

blackhawk said:
If it running right when first purchased it's likely hardware if a factory reset wouldn't resolve it.
When you start changing firmware rather than find the root cause you throw more variables into the mix. Making it more difficult.
Click to expand...
Click to collapse
if it's an hardware problem then why would flashing a different KERNEL fix it? there's no way this can be an hardware issue. please read what i said and dont throw useless opinions if you can't explain them or fix them.

omae_wa said:
if it's an hardware problem then why would flashing a different KERNEL fix it? there's no way this can be an hardware issue. please read what i said and dont throw useless opinions if you can't explain them or fix them.
Click to expand...
Click to collapse
Ever wonder what happens when one or a couple dozen of the billions of transistors in the processor fails?
Firmware doesn't just of a sudden fail, hardware does.
Firmware can get corrupted. Did you ever reflash the original stock firmware version back onto it?
You know verify the firmware load was intact?
You probably lost some digital pathways and/or memory cells in the CPU or another chipset.
The current firmware for whatever reason(s) doesn't use them.
Major carriers like AT&T, Verizon etc are partnered with Samsung and actively dictate what software and firmware goes in those phones to Samsung.
What could go wrong?

I personally never update, rooted and up... well (actually downdates) turned off for all its days.
although to answer the question directly, in my opinion yes spammy ruins stuff for more sales (aka rips off it's customers) then inturn they eventually never want to see a spammed cell again. so realistically they loose money, not a smart choice obviously, but when blinded by greed all kinds stuff will happen.