Related
my nexus one is charging on a regular basis around 106-7 F. I know there is another thread about this issue but the question was not resolved. So does anyone have experience with this issue. Is it a defect or dangerous? I have OSmonitor installed, this si where I am reading my temps. I also notice the CPU usage is pegged around 98-99%..is this normal?
I heard using setCPU with a charging profile can solve this problem if you have root?
No, it is not normal for the cpu to be maxed out while charging. Are you using the car dock or a wall charger?
nexous one
mine does the same thing all the time its not going to damage your phone at all
my phone has got about 120 F on car doc
my phone is perfect just set your set cpu for fail safe and your all good
You probably could use SetCPU to solve this problem, but the fact that your CPU usage is so high in the first place means there is something going wrong - my guess would be a rogue app.
Try downloading a task killer from the Market. Kill each app running one at a time then check your CPU usage. You'll soon find the culprit.
sn95chico said:
my phone has got about 120 F on car doc
Click to expand...
Click to collapse
Yeah I'm starting to see the problem with the phone having a metal casing. Not good when it's summer and you have to place it under direct sunlight for extended amounts of time, while using navigation AND charging
That thing can get burning hot alright.
Are you using froyo 2.2?
I have had the same problem; I also have random periods of high cpu use when not charging as well. This issue is not caused by problem apps either. I must reboot to fix the issue, sometimes I must reboot several times until the cpu load is back to normal.
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
I will also try to reapply the 2.2 update.
Marine6680 said:
I am not sure it is a bug or a hardware fault. Maybe a quick call to HTC and/or google is in order.
Click to expand...
Click to collapse
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
frandavid100 said:
Been there, done that. I opened a thread asking other users about the problem, and even mailed HTC's support. In the end I decided to try flashing the stock 2.1 rom again to see if the problem persisted, and it didn't.
I'm pretty sure it's not a hardware problem, but you might want to install eclair too and see if it works for you.
Click to expand...
Click to collapse
I bet your heat issues are related to cpu loads or staying at high frequencies like mine. Sometimes the phone does not feel like it is really running as hard as the system monitors say, though it may still get hot.
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
I am re-flashing the leaked 2.2 update to make sure there was no issue with the original install. I am also using the copy my GF downloaded when I sent her the instructions on the off chance that my download was corrupted in some small way; unlikely but hey. I do think that the original flash may have gone wrong, as mine hung and never rebooted after the flash was complete; I had to manually reboot. Lets hope this fixes it.
This issue may be more widespread than we realize, as many people do not actively monitor their cpu or notice/worry about the heat after charging. I do believe that these leaked ROMs send debug data to google, I remember reading something along those lines; these are internal test ROMs after all. Maybe this is a reason that 2.2 is not out yet, this and other bugs found during real world use.
Marine6680 said:
Where can I find the older ROM? I thought the bootloader would not allow going to older ROMs, or maybe I am mistaken.
Click to expand...
Click to collapse
What I did was follow this guide up to the point where you have a stock eclair rom, then not upgrade to Froyo. Keep using that for some time, see whether the phone gets hot or not, THEN (if you want) move back to Froyo.
I am using the wall charger hat came with the nexus one. I am also running Froyo 2.2... can I set a CPU fail safe without my phone being rooted? Also what is a quick to check if my phone is rooted? I just bought this Nexus One from someone. I know on my G1 it was rooted bc I had Superuser permissions.
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
The fastest way I can think would be installing Lamppu, then trying to use it to light up the camera flash. If it works your phone is flashed, if it doesn't it's not.
As for your other questions... sorry, i don't know. I hope someone else can help you.
foethalove said:
Using OSmonitor I can sort the processes by their CPU load and the one process that always has the highest load is " /init" which always has around 85-96% of the load. You can also kill these processes directly inside of OSmonitor and I have tried killing " /init" to no avail.
Click to expand...
Click to collapse
Thats a system process so you can not kill it.
Going to test my GFs nexus and see if she has these issues as well.
I restored my N1 to the factory image, the updated back through each update to 2.2; so far so good. My GF's N1 has been running fine since I really started watching it, so I figured it would hurt to try to restore and redo the update.
No 100% cpu load during charging any more!
i am using the Motorola charger and my phone is not getting hot at all. with the charger that comes in the box for the N1 it seems to heat up.
Still had the CPU load get stuck at 100% today; though charging is not forcing 100% loads any more.
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
frandavid100 said:
By the way, how do you measure how busy the processor is? How do you know that it's at 100%?
Click to expand...
Click to collapse
System monitor apps, some will even put a little icon in the notification tray that shows current cpu load.
First of all, for anyone who has not yet tried the new Manhattan Project 1.6ghz kernel by Team Whiskey, i suggest you do so (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=821514). It is currently in alpha but so far has gotten outstanding feedback. Ive personally been running it and I'm not looking back.
Up until now its been well known that SetCPU profiles not only dont work on our phone, but also causes crashes and severe instability. However, SINCE I FLASHED THIS NEW KERNEL (and running Bionix Fusion 1.1), I have successfully profiled my phone. Here is what I've been running all day with absolutely no issues, and my phone running like LIGHTNING:
Main: 1600-200 Conserv.
Screen Off: 200-200 Conserv.
Temp > 50: 800-200 Conserv.
I posted these results in the kernel forum, but I also wanted to post them here for everyone to see because i know that the lack of SetCPU profiles has been a major complaint around here. If anyone would like to try this out and verify that it works for them also with this kernel, please post here, so everyone can finally enjoy the beauty of overclocking AND underclocking.
Once again, I'm running Manhattan Project Kernel and Bionix Fusion 1.1
Outstanding!
Appreciate the profiles. Should be a great help. I personally lowered my Temp to 40c but thats just my opinion
Excited to get the running will tell results soon!
So had my phone sitting for a bit, it became unresponsive and i think it had something to do with the sleep profile. I went ahead and changed it to 400/200 conserv for testing.
Awesome. But is the set on boot option still not working?
Oh and just an educated guess bit I would figure no Voodoo on this kernel. So disabling just in case before I update
YatimaMeiji said:
Awesome. But is the set on boot option still not working?
Click to expand...
Click to collapse
i dont even bother, its not really needed....even if its unchecked yoru settings are preserbed upon reboot
----------------
UPDATE #2: after 5 hours of no problems my phone finally started crashing, so i have may have spoken prematurely. But I'm stubborn, so Im still gonna try every damn combination possible until my phone tells me to go f*ck myself haha
I will post my feedback as well...
OP, are you running any lag fixes?
drizze99 said:
I will post my feedback as well...
OP, are you running any lag fixes?
Click to expand...
Click to collapse
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
TopShelf10 said:
OCLF Ext2 v2.2
--------
I'm also trying "Overclock Widget" to see if i get better results
As much as I love Overclocking to 1600ghz, my it is beautiful....id also feel much more comfortable being able to underclock when its sleeping.........this is probably a wild goose chase, but i dont care, im bored at work
Click to expand...
Click to collapse
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
jnp1974 said:
With screen off 200/200, phone does not wake up, changed to 400/200, still no wake up. Both set to conservative. Disabling profiles for now.
EDIT: Found the problem, if you enable Performance scaling on the main tab, and switch it back to conservative, it really doesn't switch. This is what was causing my Vibrant to not wake up! I had to set it to on-demand, leave setCPU and switch it to conservative, before it would stick. Re-testing 200/200 screen off.
Click to expand...
Click to collapse
probably not going to help, but i certainly hope it does!!!
TopShelf10 said:
probably not going to help, but i certainly hope it does!!!
Click to expand...
Click to collapse
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
EDIT: I was testing different benchmarks with scaling on conservative, on-demand and performance to see if they altered my benchmark results. The difference was minimal, but I forgot to change scaling back to conservative and it wouldn't wake. When I pulled the battery, rebooted and checked SetCPU, it said conservative, but was stuck on performance. Changed to on-demand, left SetCPU, back in and changed to Conservative. It worked.
jnp1974 said:
Thanks for the hope, it worked. YEAH! It now wakes when it should, and profiles appear to be working just fine.
Click to expand...
Click to collapse
dont be fooled, it can often work for a while before it shows its ugly side, be patient
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
edit: for screen off don't be so stingy trying to set it to 200/200, if you need more battery life then get a bigger battery or spare batteries or Juice Defender , I usually set it to 200/800 and I have no issues.
TopShelf10 said:
dont be fooled, it can often work for a while before it shows its ugly side, be patient
Click to expand...
Click to collapse
I was fooled, ditching profiles altogether, boo
Can conferm that both profiles and set on boot work.
Sent from my Vibrant.
Mouahmong said:
I've never had any problems with profiles? The only thing that needs to be kept in mind is that if you check "set on boot" you'll get errors. Anything but "conservative" for scaling will give you errors.
Click to expand...
Click to collapse
i never check set on boot....what are your profile settings and what ROM/kernel are you running?
OK, I don't have mine OCLF yet but so far so good.
I have run Sleep profiles of 200/200 and 400/200 and the phone wakes up every time. I have gotten a txt message as well during my test and the screen lit up just like Bionix should! Will continue to kep messing with it....
turbosix said:
you realize that the phone does this automatically, right?
turn on set cpu with nothing going on in the background and just let the phone sit. it will drop down to 200mhz and stay there.
the profile setting for temp is a good idea, but screen off is just going to cause lag issues. if the screen is off and the phone isnt doing a sync or something else, you can bet its probably chilling out at 200mhz
Click to expand...
Click to collapse
if it does so automatically then why is there an option to adjust "screen off" values?
Setcpu automatically scales between the high/low you set. SO if you let the main value stay at 1600-100..when the screen is off it will scale at a lower value of course cus you're not using the phone..but it wont stay at 200, because it has a Max of 1600! So depending on background processes it could scale back up to 4 or even 600 while screen is off
MY suggestions:
Download superpower battery saver from market, tweak to turn data on/off with screen and force ondemand cpu scaling
Download Autokiller--donate to get extra functions-- and set the value to Extreme or Ultimate when screen is off and Moderate or Optimal when it is on
I did that without setcpu profiles and it took 4 1/2 hrs to go from 81 % to 70
Im running Fusion 1.1 w/ Manhattan Project
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™
jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.
So recently I've been running the smurf kernel to play games like pubg with OC. But all of a sudden my note began glitching and caused graphic glitches. I thought that this might just be in game but it happens when I exit. When I exit usually the display just goes black but the digitzer underneath is still working. Any ideas on what's going on. Oh also. I thought this might be a smurf kernel glitch so I switched to notorious but it just repeats. This happens at random too . Screenshots.
Skulldron said:
So recently I've been running the smurf kernel to play games like pubg with OC. But all of a sudden my note began glitching and caused graphic glitches. I thought that this might just be in game but it happens when I exit. When I exit usually the display just goes black but the digitzer underneath is still working. Any ideas on what's going on. Oh also. I thought this might be a smurf kernel glitch so I switched to notorious but it just repeats. This happens at random too . Screenshots.
Click to expand...
Click to collapse
Does it happen in other games? Graphically glitches such as that typically means that the GPU is not capable of process the visuals at the settings requested and bottlenecks. At least when it comes to PC.
Sent from my SM-N950U using Tapatalk
GPU artifacts. Your phone's GPU is overheated.
It doesn't happen in other games. Also, are you sure that it's just an overheating issue than a defect?
Try reinstalling the stock OS back onto your device. There is a chance that the GPU drivers may have gotten corrupted
Skulldron said:
It doesn't happen in other games. Also, are you sure that it's just an overheating issue than a defect?
Click to expand...
Click to collapse
Most likely. The common factor is artefacts during PUBG. Since the issue doesn't occur during other intense games (if you've tried others), then PUBG is the factor causing the issue.
Sent from my SM-N950U using Tapatalk
Ok so an update on the situation. Switching to a different kernel doesn't appear to help at all. In fact the situation can get a little worse at times. It doesn't happen instant but can happen at random times. It's spread to other games but only if I play the game for a while (2 hours usually). Honestly don't know what to do at this point. Usually when you overheats it downclocks automatically right? So I doubt it's overheated. I am about to wipe everything off and start new. Maybe then my problem will disappear. If anyone can please give me the direct cause of this error I will be forever grateful
Skulldron said:
Ok so an update on the situation. Switching to a different kernel doesn't appear to help at all. In fact the situation can get a little worse at times. It doesn't happen instant but can happen at random times. It's spread to other games but only if I play the game for a while (2 hours usually). Honestly don't know what to do at this point. Usually when you overheats it downclocks automatically right? So I doubt it's overheated. I am about to wipe everything off and start new. Maybe then my problem will disappear. If anyone can please give me the direct cause of this error I will be forever grateful
Click to expand...
Click to collapse
I would do a full wipe, go back to latest stock firmware with Odin, and then test from there. If the problem persists, then I think it's safe to say it's hardware failure of some type, which would require repair.
Any updatess?
Yes, So I have gone back to stock and have played PUBG. The artefacts dont appear however sometimes you catch a glimpse of very minor glitching. Now I wonder whether this is due to the fact that my note has a low GPU bin of 2 out of 15 (I think). I have switched over to a new ROM and it appears that the RED flashes of death were temporary and maybe gone for now. I will report if it repeats itself.
Skulldron said:
Yes, So I have gone back to stock and have played PUBG. The artefacts dont appear however sometimes you catch a glimpse of very minor glitching. Now I wonder whether this is due to the fact that my note has a low GPU bin of 2 out of 15 (I think). I have switched over to a new ROM and it appears that the RED flashes of death were temporary and maybe gone for now. I will report if it repeats itself.
Click to expand...
Click to collapse
Thanks for the update, glad to hear things have improved! PUBG is kind of buggy overall, so those new minor glitches could possibly just be the app itself. Keep testing and see, but hopefully everything goes smoothly
Skulldron said:
Yes, So I have gone back to stock and have played PUBG. The artefacts dont appear however sometimes you catch a glimpse of very minor glitching. Now I wonder whether this is due to the fact that my note has a low GPU bin of 2 out of 15 (I think). I have switched over to a new ROM and it appears that the RED flashes of death were temporary and maybe gone for now. I will report if it repeats itself.
Click to expand...
Click to collapse
https://www.redmondpie.com/pubg-mob...s-fix-lag-more-heres-how-to-configure-it-all/
Decent write up of how to fix some of PUBG glitches and lag. I haven't tried that game but could possibly help.
Ok everyone! I believe the issue is solved!. A reflash of the stock ROM appears to have fixed the glitches. Even on low battery it doesn't seem to affect the device so I'm going to put it down to corrupt gpu drivers. Thanks everyone for your help, y'all have been awesome.
Are you doing Dream UX for the galaxy tab s2. If you are, I have a SM-T813 and I am willing to test on it since you do not have one for this device and I don't expect for Samsung to release 8.0 Oreo on it.
Please and Thanks
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!