Database Info

Steps to fixing overheat?

Hello all
My Galaxy Note runs hot.
Can someone tell me, preferably in methodical order, the steps that should be followed to sort out overheating issues.
If you watch the Australian Open tennis then you will see how hot it gets here in summer at the moment!

1. Root
2. Install SetCPU
3. Set some temperature profiles so when your Note reaches a certain temperature the clock speed is automatically dropped
4. Close unused apps and stuff
5. Don't use 100% brightness

If I was you, I would use, in fact, lowest brightness when indoors, and underclock the CPU (even when it's not hot, as opposed to what vantt1 says).
I underclocked my Sensation from 1'5 Ghz to 1'0 Ghz (both cores). And boy, It's running smooth with ICS, no lag at all.
In fact, my settings are:
Min clock: 192 Mhz
Max clock 1005 Mhz (or something around that)
Governor: Ondemand
But your CPU is probably different than mine... Keep in mind that I underclocked around 30% of it's total capacity. You might want to do the same.
Also, direct sunlight causes overheating. (Might be obvious, but when the sun hits our skin, the body starts several cooling methods, so that you only start to notice the overheating around 30 minutes of direct exposure... And 30 mins of direct sunlight for a phone is a total kill, so also one more tip for when you're on the beach: cover it with clothes, or something. It will also decrease posibilities of thieves )

My Galaxy S2 doesn't really overheat when clocked at 1.4 GHz ondemand. It's the maximum safe clock for the Exynos 4210 found in the S2 and Note. The speed is there when I need it (but that's only 2% of the time) and when I don't, it's around 200-800 MHz. I have a solid aluminium case on it, so when left on the table it can go down to 25°C. In my pocket it's a bit higher at 34°C but it's acceptable. When I play GTA3 though, it can go up to 56°.
Sent from my GT-I9100 using XDA App

force reboot of phone isn't always overheat. the kernel also depends on how high you can overclock.

[Q] Overclocking: Minimum/Maximum CPU Clocking Settings?

Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a minimum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.

shonkin said:
Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a maximum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.
Click to expand...
Click to collapse
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun

DJLamontagneIII said:
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun
Click to expand...
Click to collapse
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.

shonkin said:
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.
Click to expand...
Click to collapse
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving

wcypierre said:
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving
Click to expand...
Click to collapse
I have setcpu but after mucking about with it managed to end up with an unstable system (spontaneous reboots, esp. after closing then opening lid and "waking up" the TF101). Currently I'm just using the EOS Rom's own system settings and having low end all the way to minimum (200 something) and top end at 1500+. The 1600 mhz setting is apparently a problem for this machine (the spontaneous resets again). But at 1500 whatever it seems just fine
One other issue, very important to all of us (harhar), is that Angry Birds seems unstable since I updated to this custom EOS rom. I noted elsewhere that someone said simply turning off wireless would disable ads and stablize the game. I've not tried that yet. Losing angry birds for me would not be a major blow.

S7 SuperKernel V1.8.5 Feedback (new user, can't post in official forum)

Unfortunately I; being a new user can't post currently in the forum (at least until I rack up a few posts); but hopefully the developer Tkkg1994 might see this.
First off, i'm fairly happy with this Kernel; it seems to be reliable and reasonably fast (at least with a few changes!), and does provide decent battery life (3Days, 15 hours w/ 7 hours screen on time is my record so far). I use it mostly to stream video (Netflix, Crunchyroll) and with netflix especially I get around 7.5 minutes -> 8 minutes per percentage point (1/2 brightness);
This is especially encouraging since when I purchased this phone, I had every intention of rooting the phone (and voiding my warranty!), and I knew at that stage about Samsung's ASV chip binning; I had a lot of fun undervolting my previous S3 to extend the battery life; so I was a bit worried about what quality chip I would get as I handed my hard earned money to the salesman.
See I have terrible luck with chip binning quality for some reason; Ever since I found that my newly purchased Celeron 566MHz could not be overclocked to 850MHz despite the numerous successess of others, I tend to attract bad bin quality chips, so much so I yearn to simply get an average chip that happens to be somewhere in the bulk of that lovely bell curve. but alas...:
ASV_SUMMARY:
big:2, LITTLE:1, INT:10, MIF:7, G3D:10, ISP:10
I think that makes me class E; As I understand it, big:2 is the lowest you can get; and LITTLE:1 is also the lowest. I win!; unfortunately, not the lottery ticket, but the lightning bolt from the heavens
Alright now I got that off my chest, There are some positives that help alleviate this most voltage hungry Exynos 8890 chip. For example, I have managed to undervolt reasonably well (Although to be fair my undervolts are probably equivalent to moving to stock voltages for a good percentage of Galaxy S7 owners out there). I shaved 100mV of the A72 (big) chip's 2.6GHz bringing me down to 1.1v and for most of the other speeds I have managed to drop 125mV. I have managed to drop 100mV on the little(A53) chips speeds.
Now on to some useful information (finally..hopefully?).
I am not an expert, so within synapse, I do not understand all options available to me. But I noticed that unlike the stock Samsung Kernel, getting all 4 of the 'big' cores to work wasn't happening. I found that Geekbench 3 and Antutu weren't really using those extra cores. However, changing the option "Exynos Hotplug" to Disabled fixed this; certainly helped my scores and despite the promised higher power consumption of having those 2 additional cores on all the time, I did not see much change to my battery life.
There is a bug I noticed where Synapse keeps trying to change my big cores minimum speed to 312MHz despite being told not to do it for some reason. I'm always having to hit the 'x" option every time I open Synapse to make sure it leaves my minimum speed at the custom 628MHz. I do not know whether this is a bug with the kernel or with synapse however, so it may not be useful.
In addition, I've noticed that when I first installed Synapse, it seemed to set the Big core voltages to values which while seemingly average, seem far too low for my ASV:2 grade ****ty floor scraping quality chip. It seemed to come right when I attempted to reinstall the system again, but it may be worth checking to make sure the Kernel reads the correct values (if that is indeed a kernel problem rather than a synapse problem.)
I've also noticed this with my GPU voltages. I may be looking at the wrong thing, but here is the ASV_GROUP frequencies and voltages for G3D:
G3D LV3 freq : 650000 volt : 1137500, group: 10
G3D LV4 freq : 600000 volt : 1125000, group: 10
G3D LV5 freq : 572000 volt : 1068750, group: 10
G3D LV6 freq : 546000 volt : 1025000, group: 10
G3D LV7 freq : 455000 volt : 981250, group: 10
G3D LV8 freq : 419000 volt : 931250, group: 10
G3D LV9 freq : 338000 volt : 887500, group: 10
G3D LV10 freq : 260000 volt : 850000, group: 10
Yet without me doing any undervolting, my GPU voltages look like this:
650MHz: 706.25mV
600MHz: 687.5mV
546MHz: 668.75mV
419MHz: 618.75mV
338MHz: 600mV
260MHz: 600mV
It looks like the stock synapse gpu settings are hugely undervolting the GPU...now it seems to be perfectly stable, which could mean that despite having poor CPU's at least the GPU is up to the task, though those undervolts seem rather extreme. What could be happening is that the voltages may be displaying these values, but are actually running at the stock settings; may be worth a look.
In addition for anyone wanting to undervolt there CPU; I highly recommend disabling exynos hotplugging.
The reason why is that I seemed to think I had found a stable voltage configuration with the 2 cores hotplugging only to discover massive instability when forcing all four cores on. I suspect this is because the overall ASV is determined by the lowest grade core of the 4, and so I did not hit any problems since the system was rarely using those 2 additional cores, even within stress testing benchmarks.
I certainly had to add more volts to get it stable, but overall the performance is higher and battery life is probably the most I can hope for out of the Grade E setup I have.
Sorry about the story length first post; but my thanks to Tkkg1994 for creating a very stable, configurable kernel for the Samsung S7

Root cause of Yuphoria's heating problem, not discussed anywhere

Hi, If you use yuphoria in a non-ac environment in India in summer where outside temperature is easily between 35-40 degree Celsius, your ear and nearby head area start hurting. Its a very dangerous, as it can cause permanent damage to ears or head.
Now before anyone say, common its a smartphone, it will heat up in such temperature, its normal, I would like to inform you, when I use my father's moto E3 power in same environment I don't feel any heat.
So obviously there is some problem with Yuphoria. consider this, your phone is sitting ideal from past one hours, a call comes, you pic the call, talk for 15 minutes and then you can feel that the screen is warm in the top right corner. you are not playing any game, doing nothing which involves heavy cpu processing, you are just taking a call for 15 minutes.
You should not feel any discomfort by doing this if mobile is Ok, as proved by moto E3 power. So something is seriously wrong with yuphoria.
So I tried to search the net to know the reason why yuphoria is overheating and came across useless advice, like stop the running processes , use different charger etc (I mean basic stuffs), but my question was still unanswered , why motoE3 power is cool even if other apps are running and yuphoria is not.
In my experiment I came across one very interesting observation which is not discussed anywhere, so here I am presenting the real cause of yuphoria's heating problem.
If we see the cpu usage using CPU-Z app in moto E3 power when no other application is running, we can find that its 201 MHz for single core most of the time. This I have checked in moto E3 power having stock ROM and data connection off. I am attaching here screenshot.
https://ibb.co/ddCmLF
If we do the same thing with Yuphoria , it never goes below 800 MHz. here are the screenshots of Yuphoria CPU usage and governors selected
https://ibb.co/bUJyZa
here is the governors
https://ibb.co/iCJXua
So obviously Yupohria CPU is always running at higher frequency than Moto E3power .
FURTHER MOTO E3 POWER HAS METAL PLATS ATTACHED TO PROCESSOR TO ACT AS HEAT SINK. you can check out the disassembling video of yuphoria and moto e3 power on youtube to see that moto e3 power has heat sink whereas yuphoria doesn't have it.
Moto E3 power is using mediatek processor which produces less heat and also the highest frequency of Moto E3 Power is less, still they included a heat sink in moto e3 power.
yuphoria is using more heat producing snapdragon 410 processor, still the engineers have not included heat sink. why yuphoria ? why?
I experimented by setting minimum cpu frequncy to 200 MHz and using powersave governor and found that now I can take calls without any heating issue. Remember still in this case yuphoria is using 3 cores with 200 Mhz frequency where as moto e3 power is using only one core with 201 MHz.
now I understand that moto E3 power is running on stock and my yuphoria is running on RR Rom, but I used to feel same heating problem even when my mobile was on original cyanogen ROM, so I think this problem of processor not going below 800 MHz is present even in original cyanogen ROM of yuphoria.
Now I want to know from all the technical experts here, why yuphoria's cpu is not going below 800 Mhz even when no other app is running. Is it the limitation of snapdragon 410 processor and nothing can be done about it, or it depends upon kernel and flashing another kernel or ROM will solve the issue.
obviously we don't want to use powersave governor with 200 MHz setting, otherwise what's the point of buying a 1.21 Ghz processor mobile. We want it to use minimum frequency that 200 single core when no other application is running and using higher frequency only when required like moto E3 power.
Is it possible? If yes , how?
I am also curious to know why they decided to not include heat sink in yuphoria?

I am not a technical expert but i don't think 800mhz might be a limitation of snapdragon 410.
Plus with ur experiment results i think it might be actually software flaw and with custom kernel or a custom rom which gives the ability to choose min and max speeds should fix it as u can choose min to 200mhz even with other governors.

Moto X Pure Battery Performance and Replacement

So my Moto X Pure only gets around 5 hours SOT and around 2-3 hours playing games. I seen a 3200 mAh battery replacement on Amazon and I'm wondering if anyone has tried it? I'm using the Resurrection Remix OS with my CPU set to power save in the battery options. Please post your battery stats and ROM information so I can see if my phone would benefit from a battery change.

Hybrid Theory said:
So my Moto X Pure only gets around 5 hours SOT and around 2-3 hours playing games. I seen a 3200 mAh battery replacement on Amazon and I'm wondering if anyone has tried it? I'm using the Resurrection Remix OS with my CPU set to power save in the battery options. Please post your battery stats and ROM information so I can see if my phone would benefit from a battery change.
Click to expand...
Click to collapse
LoL... With your SOT and game times, your battery is holding up pretty well. I would not expect much of an increase from any battery replacement you may get.
Regarding batteries from Amazon, be wary-especially of those claiming more mAh. Typically higher mAh means a larger battery so be skeptical. Based on what I have read in forums and reviews, it seems many of the batteries for this phone from Amazon, regardless of advertised mAh, have been hit or miss. Some manage to do well for 3 to 6 months then problems start.

aybarrap1 said:
LoL... With your SOT and game times, your battery is holding up pretty well. I would not expect much of an increase from any battery replacement you may get.
Regarding batteries from Amazon, be wary-especially of those claiming more mAh. Typically higher mAh means a larger battery so be skeptical. Based on what I have read in forums and reviews, it seems many of the batteries for this phone from Amazon, regardless of advertised mAh, have been hit or miss. Some manage to do well for 3 to 6 months then problems start.
Click to expand...
Click to collapse
I lowered my GPU frequency to 300 MHz that seemed to help a lot especially when playing games my battery doesn't drain as fast. I even lowered my screen resolution to 720p and set my GPU frequency to 180 MHz. The OS is smooth but when I start playing some 3D games you can definitely notice FPS drop so I put it back at 300 MHz. I couldn't increase my battery by lowering my CPU frequency for some reason my battery life seems worse when I try to mess with the CPU. The only thing I managed to do was disable my big cores in kernel auditor when they aren't needed and setting my low memory killer to aggressive in kernel auditor seemed to help my battery as well. That's just my personal experience hopefully someone will get something out of it.

Hybrid Theory said:
I lowered my GPU frequency to 300 MHz that seemed to help a lot especially when playing games my battery doesn't drain as fast. I even lowered my screen resolution to 720p and set my GPU frequency to 180 MHz. The OS is smooth but when I start playing some 3D games you can definitely notice FPS drop so I put it back at 300 MHz. I couldn't increase my battery by lowering my CPU frequency for some reason my battery life seems worse when I try to mess with the CPU. The only thing I managed to do was disable my big cores in kernel auditor when they aren't needed and setting my low memory killer to aggressive in kernel auditor seemed to help my battery as well. That's just my personal experience hopefully someone will get something out of it.
Click to expand...
Click to collapse
The CPU for the most part does pretty well scaling up and down based off processing needs. You probably just don't have CPU intensive apps so didn't notice much. You notice the GPU while playing games though. I think for the most part setting to a lower resolution might help with games at lower frequencies on the GPU in terms of maintaining higher fps at lower frequencies, but a 5.5 2K screen with simulated 720p probably doesn't net much battery life in other usage areas.

aybarrap1 said:
The CPU for the most part does pretty well scaling up and down based off processing needs. You probably just don't have CPU intensive apps so didn't notice much. You notice the GPU while playing games though. I think for the most part setting to a lower resolution might help with games at lower frequencies on the GPU in terms of maintaining higher fps at lower frequencies, but a 5.5 2K screen with simulated 720p probably doesn't net much battery life in other usage areas.
Click to expand...
Click to collapse
Right I am able to keep my GPU on power save and it'll sit on 180 MHz and the OS is still smooth on 720p if I bump it up to 1080p I'll have to put the frequency at 300 MHz or else it'll lag. I noticed when I move through the OS the GPU will jump to unnecessary frequencies like 300 MHz or even 450 MHz. Keeping it locked to 180 MHz while using Firefox or watching YouTube helped a little bit. The main problem for me is the lack of kernels to choose from. I used this tutorial https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 to tune my CPU governor since the Nexus 5X has the same SOC but my rom Remix OS has a feature called CPU boost that I can't turn off unless I flash another kernel. The problem with the Moto X Pure is that it doesn't have many custom kernels. I managed to find one that works with my rom but the camera doesn't work. I could simply go to another rom but they lack the customization Remix has and some of them have SeLinux set to permissive and I don't really feel like dealing with escalation attacks and having my bank information stolen.

Hybrid Theory said:
Right I am able to keep my GPU on power save and it'll sit on 180 MHz and the OS is still smooth on 720p if I bump it up to 1080p I'll have to put the frequency at 300 MHz or else it'll lag. I noticed when I move through the OS the GPU will jump to unnecessary frequencies like 300 MHz or even 450 MHz. Keeping it locked to 180 MHz while using Firefox or watching YouTube helped a little bit. The main problem for me is the lack of kernels to choose from. I used this tutorial https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 to tune my CPU governor since the Nexus 5X has the same SOC but my rom Remix OS has a feature called CPU boost that I can't turn off unless I flash another kernel. The problem with the Moto X Pure is that it doesn't have many custom kernels. I managed to find one that works with my rom but the camera doesn't work. I could simply go to another rom but they lack the customization Remix has and some of them have SeLinux set to permissive and I don't really feel like dealing with escalation attacks and having my bank information stolen.
Click to expand...
Click to collapse
Wow. Since I first got the phone 3 years ago, i personally just have had very little time to delve much into doing custom ROMs and kernels for this device due to work scheduling I'm moving to a new job this month and should have more time on my hands. I'm probably going to get back into things.

aybarrap1 said:
Wow. Since I first got the phone 3 years ago, i personally just have had very little time to delve much into doing custom ROMs and kernels for this device due to work scheduling I'm moving to a new job this month and should have more time on my hands. I'm probably going to get back into things.
Click to expand...
Click to collapse
I'd compile a kernel for lineage based roms with the nougat modem but I'm not that smart I don't even have a computer to do it with lol.

So I went ahead and installed the EX Kernel Manager app and I downloaded the Hawktail governor profile. After doing that my battery went from 2-3 hours SOT to 4-6 SOT from 100%. When I play slither.io on the default CPU setup my battery would drop 10% every 10-15 minutes. With the Hawktail profile it drops 10% every 30-40 minutes. I thought this was incredible because NFC and Bluetooth was still on. I also found that the Alucard CPU governor gave me similar results during my observations. I really hope somebody else can benefit from this thread.
Here is the download link https://androidfilehost.com/?fid=24686679545610694
Remove the .txt extension and put it on your micro SD card or in the ElementalX folder. From the Ex Kernel Manager app go to CPU>Governor Options>Load then load the HawkTail file then click apply on boot.