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.

occasional clock lagg

hey all, question here. I have noticed this in the last few roms, not sure if this happens in stock, but i have been running cognition, currently 3.04 ( before that 3.02, 3.0 and 2.3b6), Occasionally I notice that after the phone comes out of sleep I see the clock go from example 1:30 to 3:30 or something like that. IS that a bug in cognition? or does the clock occasionally turn off when in sleep mode, and the reason for the lag sometimes be the phone cpu usage is doing some thing when i come out of sleep causing the jump to current time? or whats the reasoning behind this?
thanks.

JJ133169 said:
hey all, question here. I have noticed this in the last few roms, not sure if this happens in stock, but i have been running cognition, currently 3.04 ( before that 3.02, 3.0 and 2.3b6), Occasionally I notice that after the phone comes out of sleep I see the clock go from example 1:30 to 3:30 or something like that. IS that a bug in cognition? or does the clock occasionally turn off when in sleep mode, and the reason for the lag sometimes be the phone cpu usage is doing some thing when i come out of sleep causing the jump to current time? or whats the reasoning behind this?
thanks.
Click to expand...
Click to collapse
When the device goes to standby, all the widgets and screen updating apps are put to sleep to save battery. When u turn on screen, all these are refreshed. This is normal.

alright. Just curious, how come sometimes i see the clock go super speed to catch up, and other times it at the correct time? ( I usually dont see it, Ive only seen it maybe 5 times past month)

JJ133169 said:
alright. Just curious, how come sometimes i see the clock go super speed to catch up, and other times it at the correct time? ( I usually dont see it, Ive only seen it maybe 5 times past month)
Click to expand...
Click to collapse
No clue. Didn't go into so deep architecture I shall see if I can find out how it works internally when I get some time.

Thanks. Anyone else feel free to answer as well.
I am looking forward to your research. I am a techy as well, and not knowing why somethings happen and dont happen when it comes to things like this bug the heck out of me.

JJ133169 said:
Thanks. Anyone else feel free to answer as well.
I am looking forward to your research. I am a techy as well, and not knowing why somethings happen and dont happen when it comes to things like this bug the heck out of me.
Click to expand...
Click to collapse
As a more visible and more frequent occurrence, load a time app onto ur home screen. You can see it get updated when u turn the screen on frequently.
I think its more dependent on how many apps/widgets need to be updated when u turn ur screen on. I hardly have any on my screen so its a rare case I see the time update.

ok, so let me get this right, your saying it probably happens more often when i haven't used my phone in a while, because lets say I have things that update every four hours, and if the phones in sleep, and they haven't updated, they all could possibly be updating when i come out of sleep because there over due, thus sometimes causing the system clock to jump?

Any one else know anything ?

JJ133169 said:
lets say I have things that update every four hours, and if the phones in sleep, and they haven't updated, they all could possibly be updating when i come out of sleep because there over due, thus sometimes causing the system clock to jump?
Click to expand...
Click to collapse
All that u set for 4 hours to update, get updated but in the 'background'. The 'display' part of them is not updated, and is 'refreshed' when screen turns on.

Hey, anyone else got any theories or updates?
I'm using ultimate Rom, newest version as of a couple of days ago.
Just noticed this about 3 times in half an hour or less.
Interested in learning why I will see my clock jump from like 2:13 - 2:17 instantly at times when I come out of sleep...

a google search using different words found this :
http://code.google.com/p/android/is...ec=ID Type Status Owner Summary Stars&id=9524
Are there any devs here that could explain or potentially fix this issue ?
Reading all that worried me, thinking hey, maybe my alarm clock isn't reliable either...

I had this issue when I was running 2.1 stock. I haven't had the issue since flashing 2.2 (have used both cog 3.02 and andromeda 2.0).
Your link also seems specific to 2.1, and I believe is a known issue coming out of 'deep' sleep. I had some luck with app called 'load monitor'. It's free and has a setting I think is called prevent suspend that doesn't allow phone to go into deep sleep.
Not sure if re-flash might help since what you describe shouldn't happen running 2.2
i897 running Andromeda 2.0

Okay. But what are the chances of me repeatingly getting bad flashes? Ive been on cog 2.3b6, 3.0 , 3.02, 3.04 snd now ultimate rom. Sometimes i wont see it happen for weeks. Other times ital happen a few times in 30 mns.
Sent from my GT-I9000 using XDA App

Oh and reading through that link you see tons on 2.2 have that issue, not just 2.1
Sent from my GT-I9000 using XDA App

Yeah not sure. Really thought was general 2.1 issue, not just on captivate.
Try load monitor. I forget the setting there, but it'll prevent deep sleep. That or you could try app 'no led' and send yourself an email before going to bed (when active notification that app prevents deep sleep too).
Sorry those are lame options that'll affect you battery life to some degree. Perhaps there are better options posted here but you'll have to dig for it.
i897 running Andromeda 2.0

I'm assuming a ton of people have it but dont pay much attention to it expecially that it comes and goes in seconds.
Sent from my GT-I9000 using XDA App

Important topic bump.
Sent from my GT-I9000 using XDA App

Stil no fixes?
Sent from my GT-I9000 using XDA App

I've been on some or other version of the ROM I have in my signature, and never observed a clock lag so far. Maybe u cud try this ROM once. By the way, I am on xcal's kernel, and not the kernel supplied in this ROM.

Just want to figure out the reason of black screen freeze, it makes me crazy

Well, to tell the truth, I like this phone. Dual-core CPU, perfect screen, HDMI output etc.
But as soon as I get this phone, I found it cannot be wake up from sleep.
I heard that LG has released a update software to fix this problem, but after I had connected my phone to the computer and opened the LGMobile Update, it told me there was no newer update available.
So I'm trying to figure out the reason of this problem.
This problem does not happened every time when I push the ON/OFF button to put the phone to the sleep mode. If I just reboot the phone, and then turn off the screen, there will never be any trouble, even I put it on the desk for the whole night.
But if some programs has been run, like the games, map, internet browser, or even a call or SMS, then lock the screen, it will never wake up. Or if I plug in the charger or connect the phone to the computer, it works great with no trouble.
What's more, after the phone has 'dead', the temperature of the phone became high, and even became higher and higher, very strange.
So I try these way to solve the problem with no success:
-replace the battery with another one.
-wipe the battery information by using ClockworkMod and then re-calibrate the battery.
-flash a different version ROM, including MCR ROM and LG Stock ROM.
-flash a different version baseband.
-force the CPU frequency to stay in 800Mhz by using 'pimp my CPU'.
-lower the voltage of the CPU.
-forced the frequency to stay about 400Mhz when the screen is locked.
-remove any applications installed by myself.
-disallow any background applications.
-put the phone in the rom with air conditioner turning on which the air temperature is about 25°c.
Then I guess this problem is caused by power management bug.
There will never be any problem when the phone is awake, or the charger is plugged in, so I don't think it's a hardware bug.

Must be a bad unit. :-(
Sent from my LG-P990 using Tapatalk

As I said before.
When you press power button to wake-up the screen, and the screen is black (bsod), press power button again (so it would power off the screen, even tho the screen is black), count till 20/30sec and press power button again....
There yoy go, phone working again!
Ive overwon my bsod since I know this trick!
Sent from my LG-P990 using XDA App

Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk

Sckank said:
Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
No, no work.
Now, after playing games or using Google Map, I must turn off the phone, and then turn it on again to avoid this issue.

OK, now I can almost confirm that this issue is caused by overheat.
I boot the phone, then put it on the desk without any operation, it will remain OK.
Then I put it into my jeans pocket for about 1~2 minutes, it will be dead.
Again, after playing games, I put the phone just near the air conditioner, it will be cooled down very soon, and the issue will not happen.
So, is there any way to make the ‘temperature protection’ or something like that higher? Or just remove it from the Android OS.

I don't think removing any sort of temp failsafe would be a good idea.
I just had a bsod and the phone was really hot. If anything, it needs a proper failsafe put in, so it at least reboots in stead of hanging on the black screen
Sent from my LG-P990 using XDA App

I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym

TrymHansen said:
I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym
Click to expand...
Click to collapse
Thanks for reply dude.
But I've tried almost every version of baseband and rom already.
I'm from China, newest version of baseband I got is V10S, which is a Korean version, and the newest Chinese version is V10K. I have tried to flash the phone back to V10A - a European version ROM, and then update the phone using LG Mobile Update software to V10D, and this did no help to the issue.
As I said, this problem always happen when the temperature of the phone is high. I'm not sure whether the CPU/GPU temperature or the battery temperature will cause this issue (I prefer to believe it's because of the battery temperature, cuz the Google Map won't use too much CPU and GPU resource)
Another interesting thing I found, is that if I leave the music playing in background, then lock the screen, the phone will never meet any issue.
So now, my solution is to avoid the high temperature, or playing the music in background, muted, and then lock the screen. This may drain the battery faster, but at least I will never miss any call.

N950U Shutting Down - CPU Usage Maxes Out

I am out of things to try on this thing, I bought it used in February and ever since upgrading to Pie the phone will beginning shutting down during use, even while only watching youtube. Something is causing the cores to ramp up to 100%, it begins to warm up but not overheat and then shuts down usually around 70c I believe, no overheating message just straight cuts power. The only way to get it to power back on is to cool it down in front of a fan or car AC for a minute or so, then it will stay on and I can watch the CPU usage drop after a few minutes and then I can use it again. I have factory reset, cleared cash but the issue remains. As Android no longer allows seeing what is using CPU I have no way of trying to figure this out further. Any ideas?

Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk

butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
Click to expand...
Click to collapse
I havent tried this, kind of terrifies me. I have touched firmware since my S3. lol kind of afraid it might shut down while doing this and brick it

butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Click to expand...
Click to collapse
Can anyone clarify if my device will brick if it shuts down while flashing firmware? Im getting desperate enough to want to try but I can't afford to replace the phone right now if it bricks.

drosenberg85 said:
Can anyone clarify if my device will brick if it shuts down while flashing firmware? Im getting desperate enough to want to try but I can't afford to replace the phone right now if it bricks.
Click to expand...
Click to collapse
No it shouldn't brick it. It'll just take you to a screen that says the update failed and on that same screen you try to flash it again. In order to try to avoid that from happening can't you do it in front of a fan or something blowing air at the back of the phone to keep it cool? I really don't think it'll be doing so much with the CPU to cause it to do that but just in case use a fan or something.

MrMike2182 said:
No it shouldn't brick it. It'll just take you to a screen that says the update failed and on that same screen you try to flash it again. In order to try to avoid that from happening can't you do it in front of a fan or something blowing air at the back of the phone to keep it cool? I really don't think it'll be doing so much with the CPU to cause it to do that but just in case use a fan or something.
Click to expand...
Click to collapse
Its not so much something I'm running that's causing the CPU usage, it happens even if only chrome or YouTube is open. I can go days without it happening , or somedays it's worse, 3 times today and the last time was the worst, it took 20 minutes to get it back. Sometimes turning off halfway through the Samsung logo. There's no overheat warning,CPU can be in the low 70s and it happens. Shutting off during the Samsung logo, could it even be the firmware? Is the battery a possibility?

drosenberg85 said:
Its not so much something I'm running that's causing the CPU usage, it happens even if only chrome or YouTube is open. I can go days without it happening , or somedays it's worse, 3 times today and the last time was the worst, it took 20 minutes to get it back. Sometimes turning off halfway through the Samsung logo. There's no overheat warning,CPU can be in the low 70s and it happens. Shutting off during the Samsung logo, could it even be the firmware? Is the battery a possibility?
Click to expand...
Click to collapse
I would say if there's no update to the apps that are causing the problem then go into the app and uninstall the update by just uninstalling the app. See if that stops it. I don't think a battery would cause an overheating problem with the CPU but the battery itself could overheat causing the phone to shutdown but it wouldn't have any effect on the CPU like you're having so it has to either be the app itself the firmware or the CPU is having a problem.

MrMike2182 said:
I would say if there's no update to the apps that are causing the problem then go into the app and uninstall the update by just uninstalling the app. See if that stops it. I don't think a battery would cause an overheating problem with the CPU but the battery itself could overheat causing the phone to shutdown but it wouldn't have any effect on the CPU like you're having so it has to either be the app itself the firmware or the CPU is having a problem.
Click to expand...
Click to collapse
That's the thing, neither the battery or the cpu get overly hot, phone gets slightly warm to the touch but around 70c doesn't seem like overheating to me. I have no idea what app,.if it is an app causing it. Thanks to android 9 there's no way to tell what's eating cpu. My monitoring apps only show they are maxing out. My concern with the battery is that maybe it's a voltage issue, maybe it can't keep up the all the cores maxing out

drosenberg85 said:
That's the thing, neither the battery or the cpu get overly hot, phone gets slightly warm to the touch but around 70c doesn't seem like overheating to me. I have no idea what app,.if it is an app causing it. Thanks to android 9 there's no way to tell what's eating cpu. My monitoring apps only show they are maxing out. My concern with the battery is that maybe it's a voltage issue, maybe it can't keep up the all the cores maxing out
Click to expand...
Click to collapse
Well for the Note 8 70c (158F) is a bit too hot for normal operating temperature. I read that someone's hasn't gone above 50c (122F) with normal usage for over 2 weeks so there's definitely something contributing to that. Do you have a ton of apps and stuff on the phone where it has to constantly check all kinds of stuff? Can you do dialer codes? Like *#9900# to run a dumpstate/logcat and then copy it to your SD card to read through it and see if anything seems out of order? It's huge just so you know..

butchieboy said:
Have you tried to flash firmware with Odin? Save all your important stuff to sd card, do a complete wipe..dalvik.. system..data..and cache. Flash firmware in odin BL,AP,CP,CSC
Sent from my SM-A205G using Tapatalk
Click to expand...
Click to collapse
Happy Thanksgiving bro!

Same to you bro
Sent from my SM-A205G using Tapatalk

MrMike2182 said:
Well for the Note 8 70c (158F) is a bit too hot for normal operating temperature. I read that someone's hasn't gone above 50c (122F) with normal usage for over 2 weeks so there's definitely something contributing to that. Do you have a ton of apps and stuff on the phone where it has to constantly check all kinds of stuff? Can you do dialer codes? Like *#9900# to run a dumpstate/logcat and then copy it to your SD card to read through it and see if anything seems out of order? It's huge just so you know..
Click to expand...
Click to collapse
I'm around 55 to 60c with normal use, but when the cores ram up it can get high 70s, but no overheating message, I dont run many apps, mostly games but I ran a factory reset and uninstalled a bunch of stuff still no go. I just happened again, I ran the dump and saved the log, I'll try and look at it tonight on my computer but have no idea what I'm looking for lol

drosenberg85 said:
I'm around 55 to 60c with normal use, but when the cores ram up it can get high 70s, but no overheating message, I dont run many apps, mostly games but I ran a factory reset and uninstalled a bunch of stuff still no go. I just happened again, I ran the dump and saved the log, I'll try and look at it tonight on my computer but have no idea what I'm looking for lol
Click to expand...
Click to collapse
Starting to seem like it's either a hardware issue or the firmware you're using. Have you tried using a different firmware version as long as it's the same bootloader version?

MrMike2182 said:
Starting to seem like it's either a hardware issue or the firmware you're using. Have you tried using a different firmware version as long as it's the same bootloader version?
Click to expand...
Click to collapse
Not yet, I downloaded the same firmware version I have and was gonna try as a last resort, currently on
N950USQS6DSI3. Had no issues until I believe I updated to pie, lol

drosenberg85 said:
Not yet, I downloaded the same firmware version I have and was gonna try as a last resort, currently on
N950USQS6DSI3. Had no issues until I believe I updated to pie, lol
Click to expand...
Click to collapse
Then get away from that version just go back one lol.

MrMike2182 said:
Then get away from that version just go back one lol.
Click to expand...
Click to collapse
So an update and some more questions. I ran a few factory resets and the phone shut down during initial OS setup, had to put it in the freezer. I have done a firmware flash yet as I was finally able to reproduce the issue multiple times. I ran a cpu stress test and as soon as it gets in the mid to high 80s it shuts down, did it 3 times. Shouldn't there be a warning and shouldn't it throttle? It seems to be the temp sensor on one core, I'm not sure how accurate these. I attached a screenshot, the circled core is the one that spikes in temp causing the shutdown. I think I'm looking at a hardware failure maybe?

drosenberg85 said:
So an update and some more questions. I ran a few factory resets and the phone shut down during initial OS setup, had to put it in the freezer. I have done a firmware flash yet as I was finally able to reproduce the issue multiple times. I ran a cpu stress test and as soon as it gets in the mid to high 80s it shuts down, did it 3 times. Shouldn't there be a warning and shouldn't it throttle? It seems to be the temp sensor on one core, I'm not sure how accurate these. I attached a screenshot, the circled core is the one that spikes in temp causing the shutdown. I think I'm looking at a hardware failure maybe?
Click to expand...
Click to collapse
Yep definitely hardware! You need a new phone or board!