Related
[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.
In theory, using SetCPU or other underclocking app to reduce CPU clock should reduce the power draw from the CPU, therefore reducing battery consumption.
However, underclocking does not reduce the amount of work that needs to be done. That is to say, whatever app or kernel processing that needs to be done will still be done. When UC'ed, they will be done at a slower pace, therefore taking longer time. In some cases, the UI becomes sluggish, requiring more user interaction time as well.
If, at 1Ghz, a process takes 10 seconds to complete and requires 10mA per second. This task should consume 100mA. By underclocking to 500mHz, perhaps the CPU takes only 6mA, but the task will require 20 seconds to complete. Now the task actually takes 120mA (plus the longer screen on time).
Is my theory sound?
Also, does the constant scaling itself consume power?
As far as I know, Froyo is supposed to scale the CPU anyway. So why underclock? Does it actually work or does it hurt the battery life?
Input please!
Thanks.
Edit: I know the function of CPU speed vs. efficiency vs. battery drain is never linear, and each situation has a different break-even point, but I'm curious the general application of underclocking within the Android environement and its effect on battery life, and more specifically, the Evo.
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNFlNlZCm-gnvD1PzEsDezCIPeA8jQ
Sent from my PC36100 using Tapatalk
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
snovvman said:
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
Click to expand...
Click to collapse
both pics depicts very different device usages. not a fair comparison imo.
quocamole said:
both pics depicts very different device usages. not a fair comparison imo.
Click to expand...
Click to collapse
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
snovvman said:
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
Click to expand...
Click to collapse
Do you think i am right on any part of which i said or am i talking out of my arse lol
A microprocessor does not live by its clock alone. lol
It can cycle through a huge math operation, which is loaded into its registers lickity split with a fast clock. It will have to wait while the memory/code of the programs it runs are loaded either into its cache memory or into execution space. So in calculating theoretical energy use, you got to figure the bus speed, as well as the type of operations the processor is doing.
Golly, ( pronounced like a resident of Mayberry) the bus is key on loading programs to be run. What's the bus clock triggered off? That's the key. You don't want the bus to slow while slowing the cpu. If you can cycle the processor while it prefetches then you've got optimal use, providing it isn't thrashing.
Google cpu wait states for bus synchronization
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
In practice, I haven't seen all that much of a difference.
iitreatedii said:
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
Click to expand...
Click to collapse
iitreatedii said:
Do you think i am right on any part of which i said or am i talking out of my arse lol
Click to expand...
Click to collapse
What you wrote makes sense and the concept is sound. I just wish we knew what that sweet spot is, although I think it changes constantly based on load, code, and operational requirements.
With the two posts above, it would seem like phone manufactures would do everything they can to optimize efficiency. Having SetCPU loaded for 24 hours, I too, can say that I have not seen a huge difference...
Noxious Ninja said:
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
Click to expand...
Click to collapse
Does the stock HTC kernel, 2.6.32 "#11" have/use HAVS?
I am new to android phones. And i have no experience about overclock.
Will my cpu easily break down due to keep overclocking?..
Honestly, i seldom change my cell phone model, i want my defy can stay a life at least 1.5yr.
i think overclocking can't really damage your phone, voltage can. so i suggest you keep the voltage around [email protected] (default is [email protected], so this should be fine), and if the phone doesn't hang or reboot, you're good to go but you could try lowering vsels, you know, the lower the voltage, the lower the power consumption, the heat and the chance to fry your cpu but i'm not sure!
Yep, 1 GHz is safe, I'm using [email protected] as well, and the CPU is capable to run easily at [email protected] continuously. The leaked Gingerbread ROM from Motorola uses 1GHz as well, so don't worry, you just have to find the safe vsel settings.
thanks for replying, i m currently using 1GHz @ 58 .. Everything is alright
Should I make the voltage as low as possible?
yeah, just to lower the power consumption and temperature, but it isn't necessary.
Can you share your voltage setting please..?
I do the stability test and it gets successful run for 5min then this means the setting is okay?
i don't overclock, just undervolt, here are my settings (with setvsel):
800MHz - 45vsel
600MHz - 30vsel
300MHz - 18vsel
up_threshold: 90%
actually if you wanna make absolutely sure your device is stable, you should run it like for an hour. but if it runs for 5 minutes without error that's quite okay, you shouldn't have problems with those settings
Thanks so much, i m trying to lower my voltage setting.
Besides, i want to ask about the battery temperature, what is the maximum temperature before getting damage to the cell? I usually goes up to 37~39 degree celsius.. is it normal?
mine is usually around 29-32 °C, but i have it undervolted, so idk. but 37-39 seems a bit high, that means the cpu temp is way over 40 degrees, you should check it out!
EDIT: tried stress testing for 20 minutes with [email protected], it went up to 35°C, so you should definitely find out what's wrong with your device!
I actually underclocked to 600MHz, since I couldn't see a big difference even at 1200MHz in normal usage. A Pentium3 at 4Ghz will still not perform as well as a slower clocked new CPU for example, CPU design is more important - what instructions it supports.
Battery life is more imprtant to me and heat is very bad for Li-ion batteries too.
Also I found changing the CPU governor to "interactive" made a difference in GUI responsiveness and I have had less stuttering.
nisamtetreb said:
I actually underclocked to 600MHz, since I couldn't see a big difference even at 1200MHz in normal usage. A Pentium3 at 4Ghz will still not perform as well as a slower clocked new CPU for example, CPU design is more important - what instructions it supports.
Battery life is more imprtant to me and heat is very bad for Li-ion batteries too.
Also I found changing the CPU governor to "interactive" made a difference in GUI responsiveness and I have had less stuttering.
Click to expand...
Click to collapse
so, what's your standby lifetime after underclocked cpu?
I can see the performance improved when i was watching flash video on browser. But honestly, i dont think there are anymore huge difference after overclocking..
But as the battery life still remains quite well, i will still keep overclocking to 1GHz.. Isn't it a good idea?
nisamtetreb said:
I actually underclocked to 600MHz, since I couldn't see a big difference even at 1200MHz in normal usage. A Pentium3 at 4Ghz will still not perform as well as a slower clocked new CPU for example, CPU design is more important - what instructions it supports.
Battery life is more imprtant to me and heat is very bad for Li-ion batteries too.
Also I found changing the CPU governor to "interactive" made a difference in GUI responsiveness and I have had less stuttering.
Click to expand...
Click to collapse
lol... What happend to HD and THD games... Did u try playing them at 600mhz??
Overclocking to 1 GHz with the right voltage values seems to be absolutely no problem for Defy.
BTW, does anyone know whether it's possible to set scaling governor to "Interactive" mode under Froyo? Gingerbread kernel let me set it, but I haven't found the way under Froyo.
Battery life was a little bit better, the display and 3G always draw a lot of power.
Standby time got better, but I don't use very low vsel any more due to errors in YouTube and dropped connection of radio streams.
Before I used 300-600-800 at 20-30-48, this was very stable in stability test, but for example Youtube would start showing "error playing video". After I increased vsel, it went away.
I mostly did it to lower temperature, optimal temperature for li-ion is around 25°C according to Wikipedia I think.
I don't play 3d games, they would benefit the most from overclock I believe.
Angry birds RIO for example would stutter for a second or two after a level loaded, but it would become as smooth as at higher clocks, when I wait for a second.
I hope flash gets better, when hardware acceleration gets enabled in Quarx's CM7.
I was running [email protected] for a month straight. No issues at all. The highest my temp reached was 112F after playing games for about an hour straight. I now just run it at [email protected], and it's plenty fast for me. I did some "testing" with all the options in SetVsel. It's not science sound, but if you use the Gingerbread Icon in the notification bar, and are running at stock (800 speed) you will notice when the CPU maxes out it doesn't even reach full capacity. I found Words with Friends to really use the CPU, and at 800 it pings the meter in the orange (The notification icon shows green, orange, and red for "zones"). If I overclock it at 1000 or above then the meter goes into the red. I don't know the exact number it switches from orange to red, but being at stock 800 is well below what the chip can really do since it doesn't even max out the meter. I hope I didn't confuse anyone. It makes sense to me.
weird...my cpu at any game reach the 800mhz
yet even in normal situations like browsing through the files on the phone it reaches 800mhz
and also despite the values i use in setvsel are not high(which is:
24 @ 300
34 @ 600
48 @ 800
)
the phone still reaches maximum 38C when i play games and if i set the value in the third vsel the games starts to hang!!
seems like i am the only one who have these problems..but why
anyone have any idea
im running stock arabic froyo btw
if someone can confirm to me that i can keep Arabic language if i installed another rom using custom restore in nandroid then i would be using prays or official 2.3 but no one answered me about that
anyway the important thing is anyone knows why my cpu temp is always high?
Well ambient temperature is important too. If it is 30°C where you live and your phone's temperature is at 35°C I'd say you are good. If the outside temperature is 10°C and your phone is dat 40°C I'd say there is something wrong (unless you were playing games or watching a movie).
in my opinion, it is definitely safe that you overclocking to the leaked moto level.
however, the voltage is still a mystery.
there's no constant conclusion about this.
i'm using [email protected], [email protected], [email protected], and it works fine for me
I'm getting really annoyed. No problems clocking up to 1100mhz with stock voltage (58). But changing the voltage settings, even slightly, makes the phone more or less unstable.
Hi,
I'm using a Canadian Galaxy S4, SGH-I337M.
Rooted, running on Liquidsmooth 4.4.4 ROM. Also has Ktoonsez kernel. It is currently undervolted+underclock a bit, and is stable (I could overclock it, but I don't. No need).
Been wondering for a long time about the operating CPU temperatures of the Galaxy S4... Never had the possibility to do testing with CPU temperatures before. I do have a LG P500 that I have overclocked a ton in the past, still work just fine, but the LG P500 is old and do not support viewing CPU temperature, so it's my first time experimenting with that.
How hot would be too hot for this phone? There are several opinions, but never figured out if I... "minimize" the risks of my actual temperatures, for some reason. My laptop CPU throttle at 85 celcius for instance. While it's a phone, it's completely different.
At night, while connected to charger, it would be pretty cool, at 25-30 degrees when I wake up;
I would say that most of the time, my CPU is running at 50 celsius, and rarely ever exceed 65-70 under normal use, or even gaming. Plus, the CPU is undervolted and a bit underclock, so I do feel like it run cooler than usual.
Quoting Meowmix from Rogers forums:
It varies on the usage of everyone else & how you handle the phone ( cases & such). Also if you are in extreme heat or having the device in direct sunlight.
Click to expand...
Click to collapse
So, the case does matter? I do have that Otterbox case which is pretty tight and enclose the phone pretty well, I would believe that the phone would get less.. air.. but I mean, it's just a case, didn't thought it would affect much..?
Quoting Ahmed from AndroidCentral Forums, I would say that I have a quite similar situation.
No, just when i ran AnTutu when it runs the 4 cores at the maximum frequency the temperature is between 80-91c, and at normal use while surfing the internet the temp. 45-55c and the battery reaches 38c after an hour of continuous using.
Click to expand...
Click to collapse
I CAN reach 80-90 celsius, but only if I really want it to happen. 38 celsius for the battery is also correct, I never exceeded 41 degrees yet, on any Android phone (I don't know the dangerous battery temps.. But when I reach 40 degrees I try to put it down as fast as possible). With benchmarks, usually at the max frequency, or testing my undervolt with Stability Test, I CAN reach 80-90 celsius, which look really high. Additionally, I would remind that I don't overclock, and the CPU is undervolted so seems a bit cooler.
So on AndroidCentral, this is the reply Ahmed got, from "CR6" user:
I had to use my temp converter to look up & convert them to Fahrenheit. 80-91c equates to 176-195 Fahrenheit and that's extremely dangerous. These temps will not only physically burn you, but will fry your phone if you continue using it at these temperatures. 45-55c equates to 113-131 degrees Fahrenheit, and that is normal under really heavy usage. Optimally, you'd like to keep it at 38-45c. You may have a defective device if you regularly see temps over 80c and I would advise checking on a replacement.
Click to expand...
Click to collapse
THAT dangerous? Well, I don't phisically feel the heat - I do feel it, but since I have that phone case, that doesn't hurt at all. But like I mentionned, I never reach 80 celcius or more unless doing benchmarks. Usually I never exceed 65-70. But still it left me wondering - Why does Android allow such high temperatures in first place? Isn't the system suppose to shut down at some point in case of danger, and when?
I've also experimented with thermal throttling in the Ktoonsez kernel, and the throttling values of the ROMs. Touchwiz Stock ROM with DVFS disabled, seems to throttle at 80 celsius, look decent. Liquidsmooth AOSP ROM, stock kernel, does not seem to throttle at all (Huh)! Once, and that was exceptionnal, I've reached 100 CELSIUS using Wifi, connect to a charger after like 2 hours, room temperature was very warm, was not surprised, but when I noticed I reached 100 CELSISUS, I was WOAW, I should shut down. I did reached 100 degrees again, using Stability Test at max frequency after a few minutes. Needless to say I manually stopped the test, because I had no idea how much heat the phone could handle...
So been aware of this, "Ktweaker" app, for the Ktoonsez kernel I use now, does have a thermal throttling option, but I wondering which thermal value should I enter for best "performance"? Default was 70 degrees, I set mine at 80, I've heard of people even putting 90 for the same kernel. Besides, maybe I worry about it too much, because in no way the phone should exceed 70 degrees celcius under normal use anyway, or even gaming. Only way to reach insane temperatures would be benchmarking/stress testing...
Still, first time seeing these CPU temperatures also. I've overclocked my LG P500 several times in the past, dealing sometimes with random reboot, so make stability/overheating questionnable, but the device did not supported seeing the actual CPU temp. So I don't know which temperatures would be considered normal - probably, nothing above 75-80, correct (For the Galaxy S4, actually)?
(Jason) said:
(From another thread)
I do know it can run up to about 180 before hitting critical and shutting down
Edit: its about a 75 degree ambient temp where im at.
Tapped² from my I5³5
Click to expand...
Click to collapse
At which point is the device supposed to shut down? Is that in the kernel or a hardware CPU trigger? Because heck, I've reached 100 degrees 2 times, I mean, how far/close was I from a shut down? I'm quite surprised.
I've also read of people complaining of S4 overheating, especially maybe after it was released - It's possible that it heats up more than other phones, but honnestly I have no idea.
Thanks for your answer =)
Going thru this exact same thing. Same temps. This is not normal. Mines just started happening one day. Idk how or exactly when
Kennii said:
Going thru this exact same thing. Same temps. This is not normal. Mines just started happening one day. Idk how or exactly when
Click to expand...
Click to collapse
Thank you for your answer;
Used to think some temps look normal to me - Besides, since I've undervolted last week, it's stable and run cooler, maybe better battery as well. I never can exceed 70 degrees even when gaming I supose..
I can reach 80 degrees, but only when benchmarking or stability testing, so I'm not worried, but I do wonder;
I've reached 100 degrees 2 times, once while doing a stability test at 1,89 GHz for like 5 minutes (or more), I had to manually stop. And last time was long ago, watched YouTube videos in bed, like under covers ha, maybe as well connected to charger. Not even surprised I've reach such temps after a while in such conditions, under covers, just no air (Used to do it with my LG P500 too. While I never was able to see the CPU temps on this device. Even then, LG P500 still works, but guessing build quality was much better). Needless to say I was like WOAW when I've noticed 100 degrees, and just put the phone down. Probably went from 80 to 100 quickly, didn't noticed that fast. But yeah, that 100 degrees was.. almost expected under such conditions.
I just really wonder about thermal throttling. Like I've mentionned, stock Touchwiz with DVSF disabled seems to throttle at 80, while KTweaker app for a different AOSP kernel have the default temp limit set to 70. Liquidsmooth ROM, AOSP, does not seem to have a throttling point, since I've reached 100 degrees 2 times with it (Don't intend to test 100 degrees again, huh). What would be the maximum ideal temp for throttling? Maybe I think about it too much, since under normal circumstances, I never exceed 70 degrees, besides benchmarks.
Also wondered at which temp is the phone supposed to shut down... 120 degrees?! XD Because 100 seems ridiculous to me, probably is, but yeah, my laptop throttle at 85, and it's a laptop (Intel Core i3) - Can't imagine a phone going any higher without any risk.
Thanks for the feedback
Just wondering if its normal for the temp sensor to read 160c+ in -10c weather.
This happened when i was walking home. Cpu reports extremely high temp and just wondering if this effect any performance.
Bell, htc 10, boot unlocked, S-OFF, 1.90.666.4
.....
Wondering if it's a false reading. Can you download another app that monitors CPU temps and see if there are any discrepancies between the two apps?
Sent from my HTC 10
Wow,that's really interesting. For my information, are you holding the phone in boiling water?
matthewacbroad said:
Just wondering if its normal for the temp sensor to read 160c+ in -10c weather.
This happened when i was walking home. Cpu reports extremely high temp and just wondering if this effect any performance.
Bell, htc 10, boot unlocked, S-OFF, 1.90.666.4
Click to expand...
Click to collapse
Probably a false reading. Your battery is too cool for a cpu this hot. Also cpu gets permanently damaged at temperatures this high. Either a sensor is damaged or app giving false reading.
that's because of the minus 10°C outside ^^
This has happened quite a few times for me when i used the phone in the freezer.
the CPU sensor somehow doesn't handle minus temperatures very well. Because the battery is constantly used it heats itself up and does not go into minus temperature.
The SoC itself is often in DeepSleep or almost idle. So it doesn't draw that much power, not enugh to keep the temperature over minus degrees, especially with an aluminum body that sends the complete outside temperature inside, not isolating like glass.
Don't worry about it
If you're curious you can install the app Stability Test https://play.google.com/store/apps/details?id=com.into.stability
It heats up the CPU pretty fast, then you can find out what's the lowest normal temperature the sensor can recognize ^^
P.S
You probably cannot damage a CPU due to heat. On my old Xperia Z2 i tried to disable ALL Thermal throttling, and run a Stresstest, when the CPU temp reached 91°C the phone simply shut down. Emergency shutdown to prevent overheating damage. Not sure if it's from Android or CPU hardware protection.
Most Intel CPU's do have a hardware protection, wouldn't be surprised if Snapdragons had the same.
Haldi4803 said:
that's because of the minus 10°C outside ^^
This has happened quite a few times for me when i used the phone in the freezer.
the CPU sensor somehow doesn't handle minus temperatures very well. Because the battery is constantly used it heats itself up and does not go into minus temperature.
The SoC itself is often in DeepSleep or almost idle. So it doesn't draw that much power, not enugh to keep the temperature over minus degrees, especially with an aluminum body that sends the complete outside temperature inside, not isolating like glass.
Don't worry about it
If you're curious you can install the app Stability Test https://play.google.com/store/apps/details?id=com.into.stability
It heats up the CPU pretty fast, then you can find out what's the lowest normal temperature the sensor can recognize ^^
P.S
You probably cannot damage a CPU due to heat. On my old Xperia Z2 i tried to disable ALL Thermal throttling, and run a Stresstest, when the CPU temp reached 91°C the phone simply shut down. Emergency shutdown to prevent overheating damage. Not sure if it's from Android or CPU hardware protection.
Most Intel CPU's do have a hardware protection, wouldn't be surprised if Snapdragons had the same.
Click to expand...
Click to collapse
with no OC (AKA 2GHZ + 1.5GHZ) I got 81c, with 2.2Ghz + 1.7Ghz I hit 92c but it kept going with no throttling
95c, i made a video
https://www.youtube.com/watch?v=jIwjn8h1Raw
If you do that next time can you do me a favour and get the dmesg?
If you want to you can "dmesg | grep [THERMAL]" to make it smaller.
I have gained root privileges. As you know, pixel6Pro has a strict temperature limit. This means that once the temperature of the mobile phone rises to about 40°C, the processor will start to reduce the operating frequency. When it reaches 43°C, all cores will not be allowed to work at a frequency above 1G... This will cause the phone to freeze very much. So will there be any mods to turn it off? I have an extra phone cooler./translate form Google
So you'd rather it have unlimited temperature to cause components to melt? There's a good reason why there is a temperature limit. I suggest that you don't mess around with it, or you will end up with a heap of garbage.
96carboard said:
So you'd rather it have unlimited temperature to cause components to melt? There's a good reason why there is a temperature limit. I suggest that you don't mess around with it, or you will end up with a heap of garbage.
Click to expand...
Click to collapse
I mean to increase the upper limit instead of closing it ... I also have a Redmi K40, equipped with Snapdragon 870, and the phone temperature exceeds 48 ° C to start limiting the processor frequency ... In contrast, TensorG1's frequency limit from less than 40 ° C is too early..For example, at room temperature of 23 ° C, my Pixel6Pro played at a current of about 1A (power consumption of about 4W). About 15 minutes, the back cover temperature of the mobile phone would be close to 40 ° C, and then a disgusting frequency limit appeared. 40 ° C is very safe for the phone, isn't it? And the lower area of the Pixel6Pro heating speed is much faster than the camera area and processor area, which is not common sense, and I also want to know why.If the frequency limit starts at about 46 ° C, it will be a good choice.
I think people should study electronics first before they tinker. This is proof. MORE HEAT?
Gytole said:
I think people should study electronics first before they tinker. This is proof. MORE HEAT?
Click to expand...
Click to collapse
Thank you for your reply, but I can't understand what you mean by translating.
He means that different devices have different specification, and you will likely damage your device.
Arealhooman said:
He means that different devices have different specification, and you will likely damage your device.
Click to expand...
Click to collapse
But this is based on root, which has assumed that I bear all the consequences, right? Having said that, the Pixel6Pro is the phone with the lowest temperature limit I have ever used.Even the same garbage Snapdragon 888 chip has a frequency limit at about 43 ° C.I just use it to run small games, but it can't last for too long, which makes me wonder if this can be called a flagship phone. Leaving aside the peak performance, the Snapdragon 778G is much better than Tensor in many scenes.And Google made a lot of mistakes. In fact, the X1 core is much more efficient than the A76 core, but I don't understand why the more used is the A76 core? ? ? I like to test the power consumption data of the processor. After about half a month I conclude that [email protected] and [email protected] have almost the same performance, but the latter one needs to pay an additional power of about 0.25W+.Too crazy,right?
Juuuuune said:
But this is based on root, which has assumed that I bear all the consequences, right? Having said that, the Pixel6Pro is the phone with the lowest temperature limit I have ever used.Even the same garbage Snapdragon 888 chip has a frequency limit at about 43 ° C.I just use it to run small games, but it can't last for too long, which makes me wonder if this can be called a flagship phone. Leaving aside the peak performance, the Snapdragon 778G is much better than Tensor in many scenes.And Google made a lot of mistakes. In fact, the X1 core is much more efficient than the A76 core, but I don't understand why the more used is the A76 core? ? ? I like to test the power consumption data of the processor. After about half a month I conclude that [email protected] and [email protected] have almost the same performance, but the latter one needs to pay an additional power of about 0.25W+.Too crazy,right?
Click to expand...
Click to collapse
Its a different SoC and different phone altogether, and the temperature reading could be from a different point, and it takes time for the heat to be conducted from the point of highest temperature to the sensor, which means that when you have a READING of 40C, the actual highest temperature point could be 75C.
Arealhooman said:
He means that different devices have different specification, and you will likely damage your device.
Click to expand...
Click to collapse
But you won't. Removing the OEM throttling mechanism doesn't completely remove throttling. The SOC WILL throttle regardless of when it hits the set TjMax.
Also, the throttling they set is based on SKIN/Shell temperatures, usually on Pixel 6/7 starting around 37c SKIN, that's on the battery around 37c (all approximate). I don't own the Pixel 6, but the 7, and the SKIN temperature is set to start at 37c very mild throttling, and the more the temperature rises, the throttling level increases.
Ultimately, the "only" hardware that will suffer in the LONG RUN is the battery since batteries don't like high temperatures and degrade faster when exposed to XY temps.
Juuuuune said:
But this is based on root, which has assumed that I bear all the consequences, right? Having said that, the Pixel6Pro is the phone with the lowest temperature limit I have ever used.Even the same garbage Snapdragon 888 chip has a frequency limit at about 43 ° C.I just use it to run small games, but it can't last for too long, which makes me wonder if this can be called a flagship phone. Leaving aside the peak performance, the Snapdragon 778G is much better than Tensor in many scenes.And Google made a lot of mistakes. In fact, the X1 core is much more efficient than the A76 core, but I don't understand why the more used is the A76 core? ? ? I like to test the power consumption data of the processor. After about half a month I conclude that [email protected] and [email protected] have almost the same performance, but the latter one needs to pay an additional power of about 0.25W+.Too crazy,right?
Click to expand...
Click to collapse
The temperature limits DEPEND on the OEM. It's NOT SOC SPECIFIC.
CPU and GPU are MOSTLY set to 85c/95c on Qualcomm Snapdragon SOCs. Pixel 7 series has the CPU set to 100C TjMax (I think the GPU is set to 95c, didn't check...)
The throttling you're talking about is based on the SKIN/Shell and EACH OEM has its own way of tunning this throttling mechanism.
JohnTheFarm3r said:
The temperature limits DEPEND on the OEM. It's NOT SOC SPECIFIC.
CPU and GPU are MOSTLY set to 85c/95c on Qualcomm Snapdragon SOCs. Pixel 7 series has the CPU set to 100C TjMax (I think the GPU is set to 95c, didn't check...)
The throttling you're talking about is based on the SKIN/Shell and EACH OEM has its own way of tunning this throttling mechanism.
Click to expand...
Click to collapse
The temperature limit of a specific SoC is determined by the characteristics of *that SoC*, not by whoever glues parts together.
96carboard said:
The temperature limit of a specific SoC is determined by the characteristics of *that SoC*, not by whoever glues parts together.
Click to expand...
Click to collapse
I'm suggesting you go and check (inform/educate yourself) a bit on this topic and how exactly this works. A SOC has an operating temperature range (from-to), THAT IS VERY TRUE (and I'm not talking about the operating temperature range specification here) but OEM decides what TJMax they want to set on the CPU or GPU (or any other component inside the phone)
So, if the OEM wants, they can set the TJMax for the CPU at 110c or more. Obviously, they don't do this for various reasons and most importantly to decrease the degradation of the silicon as much as possible (lower temps, longer life). And if you're experienced enough and know how to configure the throttling you can raise the Tjmax yourself. Google raised the TjMax on Tensor G2 to 100c. G1 was set to 90c, but they could have set it to 100C too if they wanted. And this is done on the OS side. (OEM side)
For your information, on Tensor (both G1 and G2), you can raise the TJMax of the CPU or GPU (or any other component) just by editing the thermal zones inside sys/devices/virtual/thermal > Thermal Zones (needs root).
And as someone who already made various thermal mods (magisk modules for various devices), I'm VERY well aware of how is thermal throttling handled and what can be done.
JohnTheFarm3r said:
I'm suggesting you go and check (inform/educate yourself) a bit on this topic and how exactly this works. A SOC has an operating temperature range (from-to), THAT IS VERY TRUE (and I'm not talking about the operating temperature range specification here) but OEM decides what TJMax they want to set on the CPU or GPU (or any other component inside the phone)
So, if the OEM wants, they can set the TJMax for the CPU at 110c or more. Obviously, they don't do this for various reasons and most importantly to decrease the degradation of the silicon as much as possible (lower temps, longer life). And if you're experienced enough and know how to configure the throttling you can raise the Tjmax yourself. Google raised the TjMax on Tensor G2 to 100c. G1 was set to 90c, but they could have set it to 100C too if they wanted. And this is done on the OS side. (OEM side)
For your information, on Tensor (both G1 and G2), you can raise the TJMax of the CPU or GPU (or any other component) just by editing the thermal zones inside sys/devices/virtual/thermal > Thermal Zones (needs root).
And as someone who already made various thermal mods (magisk modules for various devices), I'm VERY well aware of how is thermal throttling handled and what can be done.
Click to expand...
Click to collapse
Thank you for your reply. In the file directory you mentioned, I found many files starting with "thermal_zone" followed by numbers. But I'm not good at this field, can you tell me more? I know you have a magisk module for pixel7Pro, I want to know if you can modify some parameters to make it work on pixel6Pro? （Or are they inherently universal?） I have a pixel6Pro which rooted , maybe it can be used for your test.