HTC 10 Thermal Throttling Thread - HTC 10 Guides, News, & Discussion

Hi there.
I have my 10 for a day now and it's my first HTC phone. Because I love overclocking and stuff I've already installed Qualcomm Trepn Profiler even though I don't even have root yet.
The SD820 is a Quadcore BigLittle with core 0 and core 1 maxing out at 1.59ghz while core 2 and 3 go to 2.15ghz.
So I've used my favorite app called stability test v2.7 and did a short run.
To be fair I've been using the phone the whole time with "normal usage" so it was already pretty warm.
But yeah, I don't know the SoC temperature, the phone itself didn't feel more like 40c.
And it dropped to 1.3ghz pretty fast. Normalised CPU load is about 70%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So yeah. Any experiences outside from Benchmarking? I doubt that a 1.3ghz Kryo core will slow anything down if all 4 of them are working, but still. 1.3 instead of 2.15 +1.6 is a little difference.

That is unfortunate, I have seen many places mentioning how hot HTC 10 can get specially during gaming. It could be due to metal frame or maybe a software optimization issue.

@Haldi4803
thanks for this thread, can you please try the Powersaver and lets us know what changes in terms of cores configurations and CPU clocks
with the M8 HTC almost half the clocks with powersaver while keeping the core count and full GPU speed, with the M9 HTC locks into the small A53 quad cluster (which is a very bad idea considering how slow these cores are) on the X10 devices like M9+ and M9S HTC locks into quad as well and reduces the clocks to 1.2ghz turning the super smooth UI into a laggy experience
also whats the point of doing this test on an already warm device? its not really fair, can you please redo from a idle state?

This is expected. I remember the m9 had a lot of heat issues along with other devices that came with the SD810. Which is why a lot of devices went with the 808 last year. So they may have played it safe and went with more thermal throttling this year.
_ray_ said:
That is unfortunate, I have seen many places mentioning how hot HTC 10 can get specially during gaming. It could be due to metal frame or maybe a software optimization issue.
Click to expand...
Click to collapse
Actually aluminum sheds heat outward faster than plastic, glass or any other type of metal which is it's used to make engine blocks.

What do you expect from a metal slab, folks? I think these tests are silly. All they are saying is "if you pass current through metal slab, the metal slab is going to heat"...well, duh!!
As long as the phone does not shutdown during normal game play for an hour, I am fine with it throttling down to keep the temps under control. Can someone confirm that its fine to game for an hour on this phone and it still keeps functioning as a normal smartphone (calls, videos, audio, gps etc. function normally)?

devsk said:
What do you expect from a metal slab, folks? I think these tests are silly. All they are saying is "if you pass current through metal slab, the metal slab is going to heat"...well, duh!!
As long as the phone does not shutdown during normal game play for an hour, I am fine with it throttling down to keep the temps under control. Can someone confirm that its fine to game for an hour on this phone and it still keeps functioning as a normal smartphone (calls, videos, audio, gps etc. function normally)?
Click to expand...
Click to collapse
Indeed.
Also, go ahead and game for a couple of hours. Sure it throttles, doh, but it settles down rather quickly in regard to performance/temperature.
http://anandtech.com/show/10252/htc-10-battery-storage-results

hamdir said:
@Haldi4803
thanks for this thread, can you please try the Powersaver and lets us know what changes in terms of cores configurations and CPU clocks
with the M8 HTC almost half the clocks with powersaver while keeping the core count and full GPU speed, with the M9 HTC locks into the small A53 quad cluster (which is a very bad idea considering how slow these cores are) on the X10 devices like M9+ and M9S HTC locks into quad as well and reduces the clocks to 1.2ghz turning the super smooth UI into a laggy experience
also whats the point of doing this test on an already warm device? its not really fair, can you please redo from a idle state?
Click to expand...
Click to collapse
So your saying battery life wise,it's a bad idea to use power saver mode on the m9 but a good idea on the 10?
Sent from my 0PJA2 using Tapatalk

Heisenberg420 said:
This is expected. I remember the m9 had a lot of heat issues along with other devices that came with the SD810. Which is why a lot of devices went with the 808 last year. So they may have played it safe and went with more thermal throttling this year.
Actually aluminum sheds heat outward faster than plastic, glass or any other type of metal which is it's used to make engine blocks.
Click to expand...
Click to collapse
This is what lead me to run away from the M9 and Snapdragon 810. The 820 is probably nearly identical to that chipset design one would assume.
Only once we had kernel source and could under volt the CPUs, or turn some cores off did 1) the heat finally start to go away on the M9, and 2) the battery would stop being eaten up by the processor.
Would barely make it 8-10hrs on full battery on the M9. But what did turning off cores/undervolting do? Reduced performance of course. So, kind of defeats the purpose.
Sad to hear this. But I think this is going to be a trend and normal comment from people about the M10/Snapdragon 820.
Was wondering in the back of my head about the M10 and processor if anything has changed. Looks like it hasn't.

Lol, HTC Software sure doesn't like Benchmarking.
You can see the cores throttling 20sec after the Benchmark starts. But then when I tab out and it runs in the bg you can see the spike to 2.2ghz at the end.
Oh yeah, and for this test I did activate the high speed mode in Dev options.

what are the name of the app that are you using for the cpu/gpu onscreen overlay? thanks

@51CK0F1T4LL
Trepn Profiler, made by Qualcomm.
Sadly you have to switch to estimated Battery Power because normal mode doesn't work.

Did another test with powersafe mode on.
Sticks to 1,32ghz all the time.
Currently trying to find out if GPU Clock is also limited

Okay.....
I can totally see why the Adreno 530 GPU is throttling...
That thing draws an easy 7W on 624mhz and even after throttling still eats 5W on 500mhz.
P.S yeah, the result is that bad because of the resolution. It's not offscreen.

Nope,
Powersafe mode doesn't touch the GPU.

Lol.
You know this app? Boost+ with the Smartboost and game battery booster?
The only thing it does is reduce screen resolution from original 2560x1440 to 1920x1080.
Powerdrain is still exactly the same XD
Guess Benchmarks just aren't made for power efficiency XD

For cpu/gpu throttling try to do gfxbench battery test, or run the 3dmark test 5/10 times
I will appreciate if you can do this test for me

If you get 35-40 fps with good battery life this more than enough, unless you don't know what you want from you device.
I heard you can optimize the screen for 1080p for gaming, is that true

That's mainly GPU bound, so CPU will have about 10-20% Load maximum.
The Adreno 530 is not a little dragon but a huge power hungry beast. I think anandtech did a pretty good longtime throttling test.
P.S I get better Random Write in Powersafe mode..... Wtf?
And yeah, check the macro bench. CPU performance is reduced....
Battery safe:
Normal:

Regarding the random write: That's just AndroBench 4 being silly. The power saver doodah didn't do that.
If you want and care and bother, change your settings and runthe Micro benchmark multiple times, at least 5.
And then report the average of those results. (probably better to post that to the benchmark thread??)
When I tested my sister's Z3 Compact before/after FDE, I ran it 10 times.
Settings I used (default):
256MB file size (64MB) (feel free to increase this to 512 (or heck even 1024) if you want more accurate sequential numbers)
256KB/4KB buffer size (32768KB/4KB)
threads 1 (8)
Here's the raw data from my testing, notice the variation. Before FDE random write min/max
https://docs.google.com/spreadsheets/d/1VCT4hbJItyGaCrzJKfDvQG3f9uQ2B6grRl3VDWHik1M/edit
Which just goes to show how important it is to run the micro benchmark multiple times and then using the average, just like Joshua from Anandtech has said.
More info
http://forum.xda-developers.com/showthread.php?p=66602020#post66602020
http://forum.xda-developers.com/htc...est-htc-10-t3364616/post66578426#post66578426

Ahhh right. I vaguely remember disliking androbench.
Now that explains why ^^

Related

[Q] OC'd G2 starting to slow down?

I've had my g2 for a couple months now and I feel like I'm starting to see it slow down. I have it temprooted (w Visionary) and overclocked to 1.4 ghz. I used to never experience any lag at all. Lately, I've been noticing slower speeds with opening apps, navigating, etc. I have a setcpu profile set to turn the speed down to .245 ghz when the screen is off. While I expect to see some lag on turning the screen on, lately it has become extra laggy. Earlier today, I received a call and the screen didnt come up until several seconds after it began ringing. I can't take this slowness anymore.
Has anyone else experienced anything like this? Anyone know how I can fix it? I rarely turn my phone off, its been running for probably about a week and a half straight. Does that wear on the phone, could that be slowing it down?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: Screen off profiles are a waste if you ask me, I have no profiles enabled and I text HEAVILY through the day, it's been 17 hours and I'm currently at 23%. In fact, I'm still heavily texting
Some people say its good to restart at least once a day ..i usually do
[G2/HTC Vision]
Is your phone getting stuck at low clock speeds after you wake up the screen. That happened to me and reflashing the kernel cleared that up.
Sent from my HTC Vision using XDA App
cmccollough said:
I've had my g2 for a couple months now and I feel like I'm starting to see it slow down. I have it temprooted (w Visionary) and overclocked to 1.4 ghz. I used to never experience any lag at all. Lately, I've been noticing slower speeds with opening apps, navigating, etc. I have a setcpu profile set to turn the speed down to .245 ghz when the screen is off. While I expect to see some lag on turning the screen on, lately it has become extra laggy. Earlier today, I received a call and the screen didnt come up until several seconds after it began ringing. I can't take this slowness anymore.
Has anyone else experienced anything like this? Anyone know how I can fix it? I rarely turn my phone off, its been running for probably about a week and a half straight. Does that wear on the phone, could that be slowing it down?
Thanks
Click to expand...
Click to collapse
I know overclocking your device seems cool and all but come on. 1.4 ghz? do you really need it that high? When I first got my g2 and I stumbled upon the 1.8 GHZ kernel I though "DAMN! I'm flashing that right now!!" but I soon realized that the stock 800 MHZ was more than enough for me after my battery life took a ****. I'm not sure how you use your phone, maybe you game a lot, maybe you need the extra 600 mhz. But remember one thing. It takes power to make power. your phone was never meant to be ran past 800 mhz. which is why it came from the manufacturer clocked in at that speed. the hardware within the phone was never meant to work that hard and the manufacturer has already deciphered the perfect combination for your phone to life its life to its full extent. I dont know how much you know about overclocking but when you overclock, you're upping the voltage to gain higher frequencies out of the cpu. this results in more heat output from the hardware. we usually compensate this by upgrading the cooling system but you cant really do that on a phone can you? sure, you can set profiles and what not but whenever you turn that screen back on, your right back at 1.4 ghz. My point is, increasing the clock speeds result in more heat. failure to dissipate that heat effectively will result in damaged components. I currently have my phone set on 245/245 screen off and 245/800 fully charged. and when the battery gets to 60% or lower, its 245/768. and believe me, i experience NO lag whatsoever. the most graphically intense game i have right now is need for speed shift. and it runs fine even on 245/768. of course i dont get insanely high linpack/quadrant scores with these clocks but even so, its not reflected when i use my phone.
All im saying is think about it, think about how you use your phone, and if its really necessary to have such high cpu speeds. Because I'm sure you already know that increasing that cpu speed also decreases its lifespan. It's your decision dude. (sorry about the essay lol)
Ive been runnin' my G2 at 1.51ghz since the day we had temp-root and ive never had any issues. Also setpCPU profiles are a waste of time and im pretty sure youre actually losing more battery life since its always underclocking and overclocking it when youve got specific profiles set for it. I run 1.51ghz on the interactive governor and i can get a good 10+ hours out of the phone with moderate usage - thats with NO profiles set.
You may think the extra mhz isnt needed but trust me it makes a big difference. Then again everyone has their own preference and beliefs.
Nissan350 said:
I know overclocking your device seems cool and all but come on. 1.4 ghz? do you really need it that high? When I first got my g2 and I stumbled upon the 1.8 GHZ kernel I though "DAMN! I'm flashing that right now!!" but I soon realized that the stock 800 MHZ was more than enough for me after my battery life took a ****. I'm not sure how you use your phone, maybe you game a lot, maybe you need the extra 600 mhz. But remember one thing. It takes power to make power. your phone was never meant to be ran past 800 mhz. which is why it came from the manufacturer clocked in at that speed. the hardware within the phone was never meant to work that hard and the manufacturer has already deciphered the perfect combination for your phone to life its life to its full extent. I dont know how much you know about overclocking but when you overclock, you're upping the voltage to gain higher frequencies out of the cpu. this results in more heat output from the hardware. we usually compensate this by upgrading the cooling system but you cant really do that on a phone can you? sure, you can set profiles and what not but whenever you turn that screen back on, your right back at 1.4 ghz. My point is, increasing the clock speeds result in more heat. failure to dissipate that heat effectively will result in damaged components. I currently have my phone set on 245/245 screen off and 245/800 fully charged. and when the battery gets to 60% or lower, its 245/768. and believe me, i experience NO lag whatsoever. the most graphically intense game i have right now is need for speed shift. and it runs fine even on 245/768. of course i dont get insanely high linpack/quadrant scores with these clocks but even so, its not reflected when i use my phone.
All im saying is think about it, think about how you use your phone, and if its really necessary to have such high cpu speeds. Because I'm sure you already know that increasing that cpu speed also decreases its lifespan. It's your decision dude. (sorry about the essay lol)
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
TL24 said:
Ive been runnin' my G2 at 1.51ghz since the day we had temp-root and ive never had any issues. Also setpCPU profiles are a waste of time and im pretty sure youre actually losing more battery life since its always underclocking and overclocking it when youve got specific profiles set for it. I run 1.51ghz on the interactive governor and i can get a good 10+ hours out of the phone with moderate usage - thats with NO profiles set.
You may think the extra mhz isnt needed but trust me it makes a big difference. Then again everyone has their own preference and beliefs.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I totally see where you're coming from with the whole battery life thing with setcpu. But then again it all depends on how we use our phones. My phone is off the charger from 5:00 A.M. to 10:00 P.M. Monday through Friday and I end the day off with about 15% left with moderate/normal usage. Tried doing this without profiles and it was impossible. So there are some of us that simply cannot afford to overclock our devices for two reasons. Number 1 being that we need the extra juice to get us through our day being able to be contacted through our phones. Number 2 being that we simply do not want to cut the life of our phones by 1/3 and there's not a doubt in my mind that you know that OCing anything cuts its lifespan. But then again, there are those who simply do not care about any of that and I say **** if you don't care then why not? My main question to you though, is where? Where does it make a big difference to OC your device to 1.5 GHZ? I'm not in any way saying that you shouldn't because like you said, everyone has their own beliefs. But I want to know where it makes such a big difference? Is it the 1 second you shave off when installing apps? Or is it the 2 seconds you shave off of the boot time? In my eyes, its simply not worth it to put the cpu under so much stress and giving the device a premature death when you only shave off 1 or 2 seconds. If you hit 60+ on linpack, that's great, but I really don't think its going to reflect so much in normal functions of the device such as opening your app drawer, launching an app, or sending a text. If you game a lot, on the other hand, I can totally see why you would want to OC.
Not saying you're wrong dude, it's just something to think about.

How to undervolt and get better battery life. Please post your results and how to.

Hey all, this is a thread I saw on different forum and think it is would be good for noobs like myself to benefit from. How to undervolt your CPU and also post your Galaxy Note 2 specific results. I have tried these next steps, and so far I'm doing okay (can't give an accurate results on battery life yet). Like I said (I'm not ashamed to say I'm a noob) but if others can throw their two cents in, we can all learn and this thread can be useful. The next part was cut and paste d from other forum. And I deleted the url for the kernel and root
Prerequisites:
1. Must be rooted and recommended kernel
2. Download and install System Tuner
3. Download and install Stability Test
Steps:
1. Open System Tuner and select CPU
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Drag the slider shown in the picture to overclock or underclock CPU. In this picture we are overclocking to 1.8ghz
3. Select Voltage at the top to get to CPU voltage settings.
4. Ok, here select the buttons as they are in the picture.
a. Select the Green circled button to save current stock default settings.
b. Select the Yellow circled button 4 times exactly to reduce the millivolts by 100.
Stability Testing:
Now we really should make sure that it can handle it under load right? :silly:
1. Open Stability Test and select CPU+GPU Stability Test.
2. Select Full Details - Proceed.
3. The app will now start stressing your cores. I waited until at least 10 cpu passes before quiting the app...
Cliffnotes:
-By default, your settings will revert back after you restart your phone. You can set them to load at boot, but don't do this unless your absolutely sure that they're stable!
Open System Tuner - CPU - Menu key - Settings - Active Tweaks - Reapply CPU Settings - On Boot Completed
-Whenever i tried to lower the mv more than 100 below stock at 1.8ghz, my phone rebooted
-I am in no way responsible for anything that might happen after performing the above, even if you start your sentence with the word "but"
-here's stock settings in case you need to revert
[/QUOTE]
This is an interesting project but I would think that the average user would not need this as battery life is pretty good. Speaking for myself, I am able to get through the whole day without any issues.
Of course there might be other reasons why someone would want to do this.
Doc
Thanks
Sent from my SGH-I777 using xda premium
DocEsq said:
This is an interesting project but I would think that the average user would not need this as battery life is pretty good. Speaking for myself, I am able to get through the whole day without any issues.
Of course there might be other reasons why someone would want to do this.
Doc
Click to expand...
Click to collapse
from what i've read, undervolting save very little battery time as the processors are pretty efficient anyways. i don't have actual numbers, but i'd guess you'd get a few extra minutes - which some may really need.
it's that freaking gargantuan screen that sucks the most juice. there used to be a mod to undervolt displays. they had it working on an OG galaxy tab. i never really seen it used anywhere else.
I have an international version of galaxy note 2. I'm currently using AllianceROM and Perseus kernel. And my stock voltage is way way higher than yours. Like 1400mV mine, 913mV yours. Can I undervolt my note 2 to same specifications like yours? Thanks.
This is interesting but setcpu when I had it on my last phone worked awesome and was very easy to use.
Sent from my Amazing Galaxy Note 2!
rjisanandres said:
I have an international version of galaxy note 2. I'm currently using AllianceROM and Perseus kernel. And my stock voltage is way way higher than yours. Like 1400mV mine, 913mV yours. Can I undervolt my note 2 to same specifications like yours? Thanks.
Click to expand...
Click to collapse
You is 1400 mV on 200 MHz? It's probabky 1400 on 1.6 ghz.
Sent from my SCH-I535 using xda premium
I also have Perseus kernel overclocked but still have great battery life. Thanks for the tip though might try it and compare the difference just in case.
I agree with DocEsq.. It is interesting indeed, but is it really necessary?
Can you overclock it?
My note 2 seems to be charging forever after undervolting. I'm talking for about 6-7hrs charging time here. What seems to be the problem? I'm using Perseus kernel. TIA!
Sent from my GT-N7100 using Tapatalk 2
I once conducted a test with my evo3d. I basically ran an amp meter inline with the battery. Measuring the exact power consumption. I dont remember the exact specs, but undervolting and underclocking my phone compared to stock made a very minute difference in actual power consumption. A difference of about 8-15ma. This was during a CPU full load scenario for about 10 seconds. Even loading the CPU with the screen off to take as many variables out as possible it was very little difference. During normal operarion the power consumed was virtually identical.
So the 2 to 3% of the day (overall time) your phone is actually under HEAVY load, it won't make much difference. It did make a performance impact. So not much benefit, just reduced performance.
Now overclocking and/or overvolting did make a larger difference in consumption at high constant load.
Want to ACTUALLY make a large impact on your battery life? Make sure you don't have any apps preventing your phone from sleeping and run the absolute lowest screen brightness you can stand.
YMMV.
Sent from my Galaxy Note 2 using Tapatalk 2
The benefit I found from undervolting isn't better battery life, it's reduced heat which in heavy use provides better performance due to no cpu throttling. I'm running 1800mhz using less battery than 1600mhz and with same temps as stock. Very stable, been running this for a month now at least.
Action B said:
The benefit I found from undervolting isn't better battery life, it's reduced heat which in heavy use provides better performance due to no cpu throttling. I'm running 1800mhz using less battery than 1600mhz and with same temps as stock. Very stable, been running this for a month now at least.
Click to expand...
Click to collapse
What app did you use to undervolt?
Sent from my Amazing Galaxy Note 2!
yankees45us said:
What app did you use to undervolt?
Sent from my Amazing Galaxy Note 2!
Click to expand...
Click to collapse
I'm using the stweaks app that comes with perseus kernel.. I've undervolted quite a bit and I get better battery life.. Still not quite as good as I had stock, but definitely a lot better for being over clocked.. I just reduce each level to the level below it and run for a few to check stability and keep going from there.. So far I have had no trouble at all with undervolting.. Certainly nothing like I did with my elte.. Here's where I've been for almost a week as well as today's battery results so far with Pandora playing over 3 hours straight and moderate use..
Sent from my SPH-L900 using Tapatalk 2
Yeah, just to let you know that there certainly isn't a linear correlation between undervolting and underclocking and power usage. That might have been the case in simpler times, but with modern multi-core microprocessors, you might actually be decreasing battery life by screwing with your clock rate or voltage. Yes, the defaults err on the side of caution, but it's a whole lot of work for little to no gain.
For example, by reducing your phone's clock rate, you might actually be forcing your phone to be spending more time at load; thereby not allowing it to fallback to its sleep state. There is also something called the power wall, where an increase in operating frequency requires an exponential increase in power. However, the reverse is also true. It can be counter-intuitive to think of it this way, so a practical example is how on a 100 mile trip, a 25 mpg sedan saves 4 gallons of gasoline over a 12.5 mpg SUV. However, over the same distance a 50 mpg hybrid saves only 2 gallons over the 25 mpg car. By that same logic, a mythical 100 mpg vehicle would only save 1 gallon of fuel. It's the law of diminishing returns. Then of course, there are the stability issues that you should take into account.
There is a lot that happens behind the scenes regarding power management. Your phone is capable of intelligently scaling it's processors, voltages, and frequencies up or down all based on current and expected demand. There are people who spend a lot more time doing this for a living, and the idea that you can do it better is probably a falsehood. If you want MOAR POWER, by all means overclock/overvolt it (just don't fry it), but trying to get an extra couple minutes of run time is likely a waste of some hard work. It's the software that kills your battery, not the hardware.
Talking about computer architecture can be complicated and boring, but start with searches on "rise time" and "logic level transitions" if you want to want more background.
Action B said:
The benefit I found from undervolting isn't better battery life, it's reduced heat which in heavy use provides better performance due to no cpu throttling. I'm running 1800mhz using less battery than 1600mhz and with same temps as stock. Very stable, been running this for a month now at least.
Click to expand...
Click to collapse
Interesting... whenever I'm dling using a torrent client my phone gets a nasty fever and I've gotta set it down somewhere as it will literally make me sweat, lol. I do b there think I'll be undervolting just for that specific circumstance but that is a very interesting concept...
anishannayya said:
Yeah, just to let you know that there certainly isn't a linear correlation between undervolting and underclocking and power usage. That might have been the case in simpler times, but with modern multi-core microprocessors, you might actually be decreasing battery life by screwing with your clock rate or voltage. Yes, the defaults err on the side of caution, but it's a whole lot of work for little to no gain.
For example, by reducing your phone's clock rate, you might actually be forcing your phone to be spending more time at load; thereby not allowing it to fallback to its sleep state. There is also something called the power wall, where an increase in operating frequency requires an exponential increase in power. However, the reverse is also true. It can be counter-intuitive to think of it this way, so a practical example is how on a 100 mile trip, a 25 mpg sedan saves 4 gallons of gasoline over a 12.5 mpg SUV. However, over the same distance a 50 mpg hybrid saves only 2 gallons over the 25 mpg car. By that same logic, a mythical 100 mpg vehicle would only save 1 gallon of fuel. It's the law of diminishing returns. Then of course, there are the stability issues that you should take into account.
There is a lot that happens behind the scenes regarding power management. Your phone is capable of intelligently scaling it's processors, voltages, and frequencies up or down all based on current and expected demand. There are people who spend a lot more time doing this for a living, and the idea that you can do it better is probably a falsehood. If you want MOAR POWER, by all means overclock/overvolt it (just don't fry it), but trying to get an extra couple minutes of run time is likely a waste of some hard work. It's the software that kills your battery, not the hardware.
Talking about computer architecture can be complicated and boring, but start with searches on "rise time" and "logic level transitions" if you want to want more background.
Click to expand...
Click to collapse
Like the way you put that. Good analogies there it just seems like the other day that undervolting was the hip thing to do. Technology just moves at such a wonderful pace though. Just one little FYI though, since i do like you analogy i would like to point out that the law of diminishing returns actually refers to something else entirely. I know, I know, nitpicking, but it's just that everyone is always off the mark with that one and, well I guess I'm just an anal ahole (and an economics major, ,which I guess just overall makes me an a hole, ,lol)
If you have ever pulled apart a laptop and saw how much thermal paste the engineers at the factory "designed" for their to be on there, or seen the air/fuel ratio most cars roll off the lot with, or ever replaced an intake in a vehicle with a high performance unit I'm not sure you would feel the same way about you yourself not being to do a better job.
I get the point, and I believe often there is validity to that point, but sometime things just aren't that simple. This is where power gains come from in tuning a car (which i do). This is where efficiency is raised by removing restrictive components in a vehicle (intake, exhaust, etc) and where cooling performance is increased on a CPU with the proper application of a quality thermal paste.
Whenever time is money, and you are deciding between your bottom line and something that works and something that works as well as it can, shortcuts are made and corners are cut. Perhaps they could have spent another 200 hours for the team to absolutely optimize the processor for each device, but the cost would have been an additional $20,000 dollars. This is not always the case, but with processors I think it is. I will undervolt everytime and I do take objective measures for battery and I agree gains are relatively small. For cooling, I found the difference to be very significant at 1800, mhzI didn't check at 1600mhz, however. I can run a full Antutu benchmark as much as I want at room temperature and never exceed the throttling point (70 C if i remember correctly). Now, I am in no way saying these are facts, these are opinions, so I could be wrong of course.
Psychotic-Cerebellum said:
Interesting... whenever I'm dling using a torrent client my phone gets a nasty fever and I've gotta set it down somewhere as it will literally make me sweat, lol. I do b there think I'll be undervolting just for that specific circumstance but that is a very interesting concept...
Like the way you put that. Good analogies there it just seems like the other day that undervolting was the hip thing to do. Technology just moves at such a wonderful pace though. Just one little FYI though, since i do like you analogy i would like to point out that the law of diminishing returns actually refers to something else entirely. I know, I know, nitpicking, but it's just that everyone is always off the mark with that one and, well I guess I'm just an anal ahole (and an economics major, ,which I guess just overall makes me an a hole, ,lol)
Click to expand...
Click to collapse
The TIM wasn't put on there by the engineers who designed the chips; they are put there by workers being paid next to nothing.
Your phone doesn't have a CPU, it doesn't even use thermal paste; it's usually just a rubber contact patch and passive heat dissipation. This actually brings another point where overclocking can sometimes reduce performance due to throttling by thermal constraints (why our phone has such a low GPU rate than what it is capable of in other phones with better thermal envelopes).
You aren't replacing the SoC, you are changing the software that determines how to set the voltage/clock multiplier. The car analogy isn't valid.
And I stand corrected regarding the Law of Diminishing Returns; never paid attention in macro-econ. I think was because my prof. was more interested in forcing his political ideology upon us than actually teaching the subject. :silly:
EDIT: Keep in mind, the engineers rarely get what they want. The product the consumer ends up getting is usually dictated through a collaboration of what the business and marketing teams want. The engineer might request a large cooler clamp with a perfectly lapped surface and a carbon-based TIM. In reality, the consumer gets a dinky fan with melt-on TIM and retention springs. Money talks.
anishannayya said:
The TIM wasn't put on there by the engineers who designed the chips; they are put there by workers being paid next to nothing.
Your phone doesn't have a CPU, it doesn't even use thermal paste; it's usually just a rubber contact patch and passive heat dissipation. This actually brings another point where overclocking can sometimes reduce performance due to throttling by thermal constraints (why our phone has such a low GPU rate than what it is capable of in other phones with better thermal envelopes).
You aren't replacing the SoC, you are changing the software that determines how to set the voltage/clock multiplier. The car analogy isn't valid.
And I stand corrected regarding the Law of Diminishing Returns; never paid attention in macro-econ. I think was because my prof. was more interested in forcing his political ideology upon us than actually teaching the subject. :silly:
EDIT: Keep in mind, the engineers rarely get what they want. The product the consumer ends up getting is usually dictated through a collaboration of what the business and marketing teams want. The engineer might request a large cooler clamp with a perfectly lapped surface and a carbon-based TIM. In reality, the consumer gets a dinky fan with melt-on TIM and retention springs. Money talks.
Click to expand...
Click to collapse
1. The voltages are set by an engineer, that is what I was referring to.
2. The CPU thing was an analogy as was the car. Not a direct comparison. The analogy is referring to how there is set fuel and timing tables just like there is set voltage tables, both might not be the most efficient from the factory, tweaking them can improve things. How is this completely not valid?

[DIY]Heatsink Mod

Tried to make a heat sink for the phone
GOT THE IDEA FROM HERE: http://forum.xda-developers.com/optimus-4x-hd/general/guide-homemade-heatsink-easy-to-make-t2971385​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I didn't knew how to connect them top and bottom together so I tried the scrap left and made a tower like this [emoji14]
I kept the camera clear so that it works [emoji14] well of course I had to do it
Found out that the antennas were at the bottom so cleared that area too.
Now does it work?
I had experienced 50c while charging and using the device without the heat sink
But using the heat sink didn't improve that, it was still a 50c
But what improved was the drop in the temp. The temp dropped quite fast to about to 45c instantly after closing any heavy apps
But the signal quality did became a lil low but it's manageable
The phone now feels packed due to the excess foil in between and the heat is no longer concentrated at a place.
Will do some more tests and see if it's worth it
I'm waiting for others to try and report back their experience.
Update
Actually it helps in my opinion
In my previous test the max freq was at 1.6 GHz. I don't know why but synapse didn't apply the settings.
So I used at 1.2 GHz. It doesn't reach 50c anymore, Also takes a lot more time for the temp to increase.
IF YOU ARE GOING TO TRY THIS MOD I WOULD RECOMMEND YOU TO COVER ANY METALLIC CONTACTS WITH A TAPE OR SOMETHING SO THAT IT WONT SOMEHOW SHORTCIRCUIT !!
Thanks for trying man and the thread. I am gonna try it this weekend and report. BTW what app you use to measure cpu temp?
Nice, but what's the use of the stack?
This was the lowest temp my redmi went when I went to Darjeeling last week
sharan.nyn said:
Actually it helps in my opinion
In my previous test the max freq was at 1.6 GHz. I don't know why but synapse didn't apply the settings.
So I used at 1.2 GHz. It doesn't reach 50c anymore, Also takes a lot more time for the temp to increase.
IF YOU ARE GOING TO TRY THIS MOD I WOULD RECOMMEND YOU TO COVER ANY METALLIC CONTACTS WITH A TAPE OR SOMETHING SO THAT IT WONT SOMEHOW SHORTCIRCUIT !!
Click to expand...
Click to collapse
i actually have tried this a few weeks ago using aluminium cans instead cause I didn't have any aluminium foil in my kitchen, but the result is exactly like what you said in the first post, it still heats up the same 50 - 60c(im in malaysia) but cools off a tad faster....
i also made another mod, I found that one of the area where the heat is prominent beside the camera above the sdcard slot, I opened up the internal case and made a square opening, I hate to say that the heat only reduce in almost placebo effect ,maybe if i had some aluminium foil i could do more experiment. (this is almost useless since the processor is on the other side)
I don't recommend anyone who has Original Warranty and has easy access to Xiaomi Centre to mod their Redmi 1S like this(it will certainly void yours), mine is only AP set and its very hard to send it to Xiaomi centre ..
sinnerz2000 said:
Nice, but what's the use of the stack?
This was the lowest temp my redmi went when I went to Darjeeling last week
Click to expand...
Click to collapse
It's not much high tech.. Just wanted a way to connect the aluminium foil on the back cover to the top one that's all. Also wanted it to be tight enough.
And I'm pretty sure it's tight because it took a lot of efforts and compressing to close the cover
In theory acc to me the stack also has larger surface area because it has many layers and would dissipate heat faster
funtikar said:
i actually have tried this a few weeks ago using aluminium cans instead cause I didn't have any aluminium foil in my kitchen, but the result is exactly like what you said in the first post, it still heats up the same 50 - 60c(im in malaysia) but cools off a tad faster....
i also made another mod, I found that one of the area where the heat is prominent beside the camera above the sdcard slot, I opened up the internal case and made a square opening, I hate to say that the heat only reduce in almost placebo effect ,maybe if i had some aluminium foil i could do more experiment. (this is almost useless since the processor is on the other side)
I don't recommend anyone who has Original Warranty and has easy access to Xiaomi Centre to mod their Redmi 1S like this(it will certainly void yours), mine is only AP set and its very hard to send it to Xiaomi centre ..
Click to expand...
Click to collapse
Thanks for posting your mod too. I am for sure not going to open it up [emoji14]
Also I might be experiencing placebo effect. Don't know I just think that making a heat sink is this easy.
Well it was just a lil' hardware mod I did
Sent from my Armani Running Xcelerate Custom Kernel with Carbon RC6. #HappyTyping with Fleksy
sharan.nyn said:
It's not much high tech.. Just wanted a way to connect the aluminium foil on the back cover to the top one that's all. Also wanted it to be tight enough.
And I'm pretty sure it's tight because it took a lot of efforts and compressing to close the cover
In theory acc to me the stack also has larger surface area because it has many layers and would dissipate heat faster
Thanks for posting your mod too. I am for sure not going to open it up [emoji14]
Also I might be experiencing placebo effect. Don't know I just think that making a heat sink is this easy.
Well it was just a lil' hardware mod I did
Sent from my Armani Running Xcelerate Custom Kernel with Carbon RC6. #HappyTyping with Fleksy
Click to expand...
Click to collapse
Good but please credit the original thread from where u got this
I think applying these thermal graphite strips to our IC's can reduce heating a lot, AFAIK even the mi3 has graphite to dissipate the heat away from the surface.
sinnerz2000 said:
I think applying these thermal graphite strips to our IC's can reduce heating a lot, AFAIK even the mi3 has graphite to dissipate the heat away from the surface.
Click to expand...
Click to collapse
and there is the panasonic pgs too..but theyre supposed to be attached to the board or "baked in" no?,,is it safe to just put them on?
im also not completely sure..TIA
viggyv said:
and there is the panasonic pgs too..but theyre supposed to be attached to the board or "baked in" no?,,is it safe to just put them on?
im also not completely sure..TIA
Click to expand...
Click to collapse
I'm not sure about the application process but from the looks of the pictures they're like stickers.
sharan.nyn said:
Actually it helps in my opinion
In my previous test the max freq was at 1.6 GHz. I don't know why but synapse didn't apply the settings.
So I used at 1.2 GHz. It doesn't reach 50c anymore, Also takes a lot more time for the temp to increase.
IF YOU ARE GOING TO TRY THIS MOD I WOULD RECOMMEND YOU TO COVER ANY METALLIC CONTACTS WITH A TAPE OR SOMETHING SO THAT IT WONT SOMEHOW SHORTCIRCUIT !!
Click to expand...
Click to collapse
It will be better if you didn't put aluminium foil around the battery area since lithium batteries are sensitive to heat and will have shorter lifespan in high heat situation.
I figure the reason that other manufacturers cap the speed of their Qualcomm 8228 cpu phones to 1.2Ghz not 1.6Ghz like Xiaomi, is because they knew that there would be excessive heat from their testing.
barrack1 said:
It will be better if you didn't put aluminium foil around the battery area since lithium batteries are sensitive to heat and will have shorter lifespan in high heat situation.
I figure the reason that other manufacturers cap the speed of their Qualcomm 8228 cpu phones to 1.2Ghz not 1.6Ghz like Xiaomi, is because they knew that there would be excessive heat from their testing.
Click to expand...
Click to collapse
The heat issue in redmi 1s is not because of clocking to 1.6ghz, its because of poor insulation. There are alot of other phones running the same SOC with 1.6ghz clock speed and only redmi 1s is reported to have the overheating issue.
sinnerz2000 said:
The heat issue in redmi 1s is not because of clocking to 1.6ghz, its because of poor insulation. There are alot of other phones running the same SOC with 1.6ghz clock speed and only redmi 1s is reported to have the overheating issue.
Click to expand...
Click to collapse
That doesn't make sense, you don't deal with heat with more insulation, you need a better heatsink design to remove the heat or lower the clockspeed/voltage.
The majority of phones with the same soc mostly run SLOWER than 1.6ghz - t2 ultra 1.4, xolo q1100 1.4, All v1 viper 1.4, S3 Neo 1.4, Xperia T3 1.4, Highscreen boost 2se 1.4, Walton primo s2 1.4.
Only a few phones/tablet like the The HTC desire 816, Yoga 10 HD tab, GX2, run at full speed probably because they are bigger and can allow a larger heatsink to soak up the excess heat.
https://en.wikipedia.org/wiki/Qualcomm_Snapdragon#Snapdragon_400
barrack1 said:
That doesn't make sense, you don't deal with heat with more insulation, you need a better heatsink design to remove the heat or lower the clockspeed/voltage.
The majority of phones with the same soc mostly run SLOWER than 1.6ghz - t2 ultra 1.4, xolo q1100 1.4, All v1 viper 1.4, S3 Neo 1.4, Xperia T3 1.4, Highscreen boost 2se 1.4, Walton primo s2 1.4.
Only a few phones/tablet like the The HTC desire 816, Yoga 10 HD tab, GX2, run at full speed probably because they are bigger and can allow a larger heatsink to soak up the excess heat.
https://en.wikipedia.org/wiki/Qualcomm_Snapdragon#Snapdragon_400
Click to expand...
Click to collapse
Maybe the heatsink is used in this device is the culprit but not the clock speed. I have underclocked it to 1.2ghz but the heat still remains, even the custom Roms built for this device are clocked by default at 1.4ghz.
sinnerz2000 said:
Maybe the heatsink is used in this device is the culprit but not the clock speed. I have underclocked it to 1.2ghz but the heat still remains, even the custom Roms built for this device are clocked by default at 1.4ghz.
Click to expand...
Click to collapse
Then you might have a defective phone. Mine runs noticeably cooler when I set the max speed below 1.6ghz. And you're contradicting yourself when you said earlier that "There are alot of other phones running the same SOC with 1.6ghz clock speed and only redmi 1s is reported to have the overheating issue".
The problem is clocking the MSM8228/8928 too high at 1.6Ghz (which you said was not a problem) . Most manufacturers clock the snapdragon 400 at 1.4Ghz.
http://system-on-a-chip.specout.com...00-MSM8228-vs-Qualcomm-Snapdragon-400-MSM8928
barrack1 said:
Then you might have a defective phone. Mine runs noticeably cooler when I set the max speed below 1.6ghz. And you're contradicting yourself when you said earlier that "There are alot of other phones running the same SOC with 1.6ghz clock speed and only redmi 1s is reported to have the overheating issue".
The problem is clocking the MSM8228/8928 too high at 1.6Ghz (which you said was not a problem) . Most manufacturers clock the snapdragon 400 at 1.4Ghz.
http://system-on-a-chip.specout.com...00-MSM8228-vs-Qualcomm-Snapdragon-400-MSM8928
Click to expand...
Click to collapse
@sinnerz2000 I agree with you..its not all about clock speed. Even on 1.2ghz there us still heating..though not as much or rather not as quick..but its still there..something else is the matter and I can't put a finger on it!
Peace! ✌
Sent from my HM 1SW using XDA Free mobile app

Slimkat Won't Turn On After Reboot

Slimkat won't turn on after reboot
I was running latest Slimkat (8/28) and rebooted the phone using the reboot menu option from holding the power button. It was plugged into a charger at the time.
A while later I noticed it still wasn't on. I tried pressing buttons, holding the power button for 30 sec., etc. The phone was a little warm before I did the reboot, not sure if that is part of the issue.
Has anyone had their phone unable to be turned on after a reboot? Any solutions?
Thanks in advance.
I can't post in the development forums yet, so forgive me if this post is in the wrong place.
A "little warm" during usage (watching videos / gaming) or charging is not unusual.
If you're using something like a TPU case, the heat from the back of the phone can't esacpe that quickly...
Running SlimKat for a week now, several reboots and complete power off. No problems.
What was your battery percentage when you started charging / at the time of the reboot?
Does it show the "charger icon" / battery percentage when you plug in the charger now or is there no reaction at all?
Discussions about custom ROM related issues are supposed to be in "General" or "Q&A / Help", so you chose the right place. (The development forum is meant for actual DEV material only)
Bingo Bronson said:
A "little warm" during usage (watching videos / gaming) or charging is not unusual.
If you're using something like a TPU case, the heat from the back of the phone can't esacpe that quickly...
Running SlimKat for a week now, several reboots and complete power off. No problems.
What was your battery percentage when you started charging / at the time of the reboot?
Does it show the "charger icon" / battery percentage when you plug in the charger now or is there no reaction at all?
Discussions about custom ROM related issues are supposed to be in "General" or "Q&A / Help", so you chose the right place. (The development forum is meant for actual DEV material only)
Click to expand...
Click to collapse
Thanks for the reply.
The phone is unresponsive when plugged into a charger. No battery logo, doesn't seem to be charging (no heat).
I just tried plugging it into my Windows PC, and device manager is saying:
"A request for the USB device descriptor failed."
No response plugging it into a mac.
timosaur said:
The phone is unresponsive when plugged into a charger. No battery logo, doesn't seem to be charging (no heat).
Click to expand...
Click to collapse
Yikes. Faulty hardware, worst case scenario? But from what you described, quite likely...
Did you buy it from one of the big Ebay deals or directly from Amazon? I think it's time to contact "them".
Bingo Bronson said:
Yikes. Faulty hardware, worst case scenario? But from what you described, quite likely...
Did you buy it from one of the big Ebay deals or directly from Amazon? I think it's time to contact "them".
Click to expand...
Click to collapse
????????? The phone seems to have come back to life, after trying random chargers. The current charger started charging after maybe 30 minutes of no response.
The battery is charging from 0%. I know when the problem occurred yesterday, battery was nowhere close to 0. So the battery had to drain and reset somehow.
Thanks for all the help. I did buy from Amazon, and I'm within my return period... still on the fence if I should return or not.
timosaur said:
The phone seems to have come back to life, after trying random chargers.
Click to expand...
Click to collapse
Can you check the Amazon charger with a multimeter? Maybe he's responsible...
Let's see if it charges properly and also how fast the battery drains afterwards.
Bingo Bronson said:
Can you check the Amazon charger with a multimeter? Maybe he's responsible...
Let's see if it charges properly and also how fast the battery drains afterwards.
Click to expand...
Click to collapse
I was using a third party charger, I'll check when I get the chance. Not sure how to measure those tiny pins
timosaur said:
I was using a third party charger, I'll check when I get the chance. Not sure how to measure those tiny pins
Click to expand...
Click to collapse
I had to go back to stock charger when running slimkat.
Bingo gave me something to think about though. How well do these phones handle high temps/how well do they cool down? I can count on one hand how many random reboots I've had. Strangely it hasn't occurred when playing high res video. But my case, which I really like, provides little to no ventilation (glass on front and back, plastic wrapped with thick rubber on the side). I'm reluctantly going to ask--should I find a case that at least opens up the back?
I'm having no issues aside from common bugs with the custom Roms. But I don't want to slowly cook this thing either. Anyone know about the heat sink we have?
timosaur said:
I'll check when I get the chance. Not sure how to measure those tiny pins
Click to expand...
Click to collapse
That's just me being nosy ^^ You could measure it directly from the USB port of the charger (the outer pins).
KLit75 said:
How well do these phones handle high temps/how well do they cool down? [...] But I don't want to slowly cook this thing either. Anyone know about the heat sink we have?
Click to expand...
Click to collapse
I remember that case, KLit75, I believe it was from the "clunky tank" series. The Snapdragon 800 starts throttling around 145.4 °F, iirc.
A case like this slows down the cool down process, no doubt, but a "naked" phone can get just as hot on the inside.
I guess there's a small advantage with a naked phone as long as the surrounding temperature is low enough to make a real difference and keeping it a bit cooler in the long run.
My default settings keep the CPU around 82 - 88 °F for things like browsing, maximum was 113 °F when playing videos for a longer time with MX Player (HW+ codec setting).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heat sink, M'Lady?
I think I will remove the back cover, rip out the NFC connector, apply some copper foil and drill some holes in the back (Homer Simpson style) for elite cooling results. :laugh:
@Bingo Bronson, above and beyond with the info! Many Thanks!!!
Follow up on CPU settings: (since this thread is getting slightly off the track already ^^)
Since we have to use the voltages (see pic below) provided by the Kernel, I guess I don't save much battery life with these settings, less heat most likely, since the max. freq. is limited the whole time and the Governor scales down faster.
But then, there's also this:
tech_head said:
Please don't confuse voltage with current.
The voltage at which a part runs does not equal power. Power (Watts) = V (voltage) x I (current).
Low voltage threshold processes are used for high performance and high voltage threshold processes are used for low power.
LVT processes have higher leakage and consume more power, not less than the HVT process.
You can draw no conclusion based on the operating voltage, except that the HPM will potentially have higher leakage and therefor a possible higher current draw with all things being equal. It also has a higher clock frequency potential.
Click to expand...
Click to collapse
Keeping the input boost freq. low may have a little impact on battery life when you have a lot of interaction with the screen, as in "much tapping ➜ much boost ➜ much CPU".
Even with the currently lowered settings, I get "only" 3 days battery life with mobile data enabled.
I will lower my max. freq. to the same as input boost freq., both set to 960 MHz @ 800 mV and see how it goes (with the CPU set this low, it might be even worse since it needs more time to compute a task ^^)
Yes, I'm aware that these settings only qualify for basic phone & messaging usage.
Bingo Bronson said:
That's just me being nosy ^^ You could measure it directly from the USB port of the charger (the outer pins).
Click to expand...
Click to collapse
Haha the charger that caused the issue is one of those direct to microusb chargers.. the ones without a USB port. Never trusting one of those again.
Bingo Bronson said:
I will lower my max. freq. to the same as input boost freq., both set to 960 MHz @ 800 mV and see how it goes (with the CPU set this low, it might be even worse since it needs more time to compute a task ^^)
Yes, I'm aware that these settings only qualify for basic phone & messaging usage.
Click to expand...
Click to collapse
How did the 960 go? I've been running at a 1.5Ghz max and I've been happy with it running over a day. I can't find input boost in the app I'm using but would that explain why the CPU jumps over 1.5 sometimes?
timosaur said:
Haha the charger that caused the issue is one of those direct to microusb chargers.. the ones without a USB port. Never trusting one of those again.
Click to expand...
Click to collapse
Yep, had a similar experience with one for my Raspberry Pi 2. It worked for ~ 3 hours, then the Pi didn't boot up. I bought a "good" charger with 5V / 2.4A, turns out he delivered 4,5x volts at best, s#it happens sometimes...
How did the 960 go? I've been running at a 1.5Ghz max and I've been happy with it running over a day...
Click to expand...
Click to collapse
It's decent, right now 46% charge left since unplug, I had multiple longer calls yesterday and some more than ususal texting, needed to take some phots with flash...
Performance is enough for basic tasks. The "multicore power saving" is another thing...
I wonder if it uses less voltage, I guess the voltage indications are meant for "all cores active" but how much lower is the voltage with only 1 core active, if at all...
I can't find input boost in the app I'm using but would that explain why the CPU jumps over 1.5 sometimes?
Click to expand...
Click to collapse
Yes, that explains it.
Input boost is usually set to max. freq. so that the CPU goes "full throttle" everytime the screen is tapped (for that fluid Android experience ^^).
Limiting it may have (some) benefits for "heavy tapping" users.
Side note: I flashed the SlimKat v2015/09/15 build at 95% charge.
Side side note: I started using the 960 MHz setting at around 78% charge.

Big Cores are always stopped!

Hey Guys,
i have a problem with my Nexus 5X since weeks and now I think I have founded the problem. On daily usage, in games or in Benchmarks: the two big Cores are always stopped. Bit I don't know why. I have tested it with some Games, Geekbench and CPU-Z. Can anyone help me?
Thanks
chris.k00 said:
Hey Guys,
i have a problem with my Nexus 5X since weeks and now I think I have founded the problem. On daily usage, in games or in Benchmarks: the two big Cores are always stopped. Bit I don't know why. I have tested it with some Games, Geekbench and CPU-Z. Can anyone help me?
Thanks
Click to expand...
Click to collapse
The thermal throttle stops the big cores when they reach a certain temperature. It's "normal" behavior on this cpu.
But they are stopped all time. When I Power on the device and start a big game, when I wake up the device after a while and play a big game... ever! Temperatures are round about 55°C
If you're on one of the Android N Dev Previews then it is probably the well known bug that shuts the big cores off. If you're on Marshmallow then it is most likely thermal throttling. I think the big cores turn off at about 45C.
Okay. But why does my device heat up so fast? I have read a few Tests and the Processor never gets hotter then 42°C.
chris.k00 said:
Okay. But why does my device heat up so fast? I have read a few Tests and the Processor never gets hotter then 42°C.
Click to expand...
Click to collapse
It's your use mostlikely, e.g. camera (, cpu intensive games, benchmarks etc) takes all the cpu power possible, that'll heat up your device into range of thermal throttling in no time, while one can browser normal websides for hours without any signifcant heat building up.
---
I think it's a general misunderstanding of how a big.little cluster cpu works. Those aren't 6 equal cores, the big ones are (most of the time) just there for short term boosts and otherwise drag down performance overall, especially when the cpu heats up. I can see a much higher use of the big cores e.g. when loading websides compared to gaming, where it comes down to how the game can run on the remaining cores (little ones) after a few minutes.
But the Cores shouldn't heat up after a few seconds, should they? And they are simply alsways off.
I have tested it with the Geekbench 3, Smash Hit and the Camera App. The results like the temperature and the clock Speed came from CPU-Z.
My Standard result of the Geekbench is 650 and 2500 points. The two big Cores are stopped and the temperature is round about 50°C
The Standard witch I have found in the Internet was 1300 and 3600 points. The temperature shoult be round about 42°C-44°C

Categories

Resources