Related
You can overclock n1 only to 1.190ghz, while desire hd 1.9ghz and the htc desire Z (G2) 2.0ghz. Does N1 has to old cpu?
-------------------------------------
Sent via the XDA Tapatalk App with my Sexy Nexy
Yes. 1st Gen snapdragon
Sent from my Nexus One using XDA App
if you want to OC you N1 go and OC you Desktop is the best choice
Why would you wanna over clock your phone? I have my N1 clocked @ 691 and works really fast with the MIUI rom and battery performance is better than stock. I'm not a fan of custom rom & rooting but I been pretty pleased so far. overclocking the nexus one will drain your battery like crazy plus the 1st Gen of snapdragons weren't as good with graphics as the A4chips and humming birds.
i have mine underclocked too and it works fine. try going a step further and underclocking it to like 422 when it's sleeping/standby. it'll help your battery
josemedina1983 said:
Why would you wanna over clock your phone? I have my N1 clocked @ 691 and works really fast with the MIUI rom and battery performance is better than stock. I'm not a fan of custom rom & rooting but I been pretty pleased so far. overclocking the nexus one will drain your battery like crazy plus the 1st Gen of snapdragons weren't as good with graphics as the A4chips and humming birds.
Click to expand...
Click to collapse
The connection between clockspeed and power consumption is not as strong as you think. But without a doubt it has an influence. Much more important is the voltage. If you "undervolt" the Nexus One CPU you can even get better battery live with higher clockspeed.
And if you use a tool to change the clockspeed depending on the situation (display on/off, battery % left, workload) and undervolt the cpu you can safe A LOT of juice.
With Wildmonks kernel, MIUI and SetCPU I get a much better lifetime than ever before even though my Nexus runs at 1152MHz.
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other.
Nexus has examples that overclock to 1.5GHz when overvolted, like Desire Z and Desire HD (both of those have to be overvolted to go up stable from 1.2GHz). Most of Nexus Ones fail when overclocking and don't reach higher than 1.2GHz, but it might be not because of the CPU, but because of other devices on system board.
Generally, it is only when you change the voltage (which is required to stabilize the higher frequency) that you see noticeable differences in battery life.
Jack_R1 said:
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other.
Nexus has examples that overclock to 1.5GHz when overvolted, like Desire Z and Desire HD (both of those have to be overvolted to go up stable from 1.2GHz). Most of Nexus Ones fail when overclocking and don't reach higher than 1.2GHz, but it might be not because of the CPU, but because of other devices on system board.
Click to expand...
Click to collapse
willverduzco said:
Generally, it is only when you change the voltage (which is required to stabilize the higher frequency) that you see noticeable differences in battery life.
Click to expand...
Click to collapse
Ok, some additions required.
Leakage is also dependent on power, and the dependency graph isn't linear - and starts breaking upwards at some point, usually being a tad above the max designed voltage.
Going down in voltage makes leakage change approximately linear, and doesn't affect nearly as much as going up.
Overclocking will draw power just as I noted above - exactly with the same percentage difference - only when the clock is reaching the overclocked area, which happens only when you're playing games or doing CPU-intensive tasks.
Undervolting will affect leakage, which happens 100% of the time.
So yes, when running in dynamically scaled environment, undervolting has more effect than overclocking. On desktop PC, running the same clock frequency constantly, the effect is the same.
Very True. And I wasn't saying that overclocking, while at the same voltage, didn't draw ANY more power... I just am trying to say that (for example in this graph) overclocking only has a small effect on power draw until you actually change the voltage. In that same example, going from 3.4 to 3.8 GHz only adds about 6% current draw while at the same vCore, while going up a similar amount in clock speed.
I'd even wager to say that if you're slightly under-volted and as heavily overclocked as you can go at that given voltage, you'll save some trivial amount of power versus stock because of the fact that voltage affects power draw significantly more than clock speed. I would also wager that if you are at an overclocked speed and are at stock voltage, the amount of current and power draw will be almost indistinguishable to the end user, since things like display will almost always use much more power if the display is on for any appreciable amount of time.
Jack_R1 said:
Ok, some additions required.
Leakage is also dependent on power, and the dependency graph isn't linear - and starts breaking upwards at some point, usually being a tad above the max designed voltage.
Going down in voltage makes leakage change approximately linear, and doesn't affect nearly as much as going up.
Overclocking will draw power just as I noted above - exactly with the same percentage difference - only when the clock is reaching the overclocked area, which happens only when you're playing games or doing CPU-intensive tasks.
Undervolting will affect leakage, which happens 100% of the time.
So yes, when running in dynamically scaled environment, undervolting has more effect than overclocking. On desktop PC, running the same clock frequency constantly, the effect is the same.
Click to expand...
Click to collapse
Jack_R1 said:
Actually, the frequency makes a BIG difference in power consumption. Think of it this way - each clock causes changes propagating in transistors, which are the actual power draw. More clocks = more changes = more power drawn. As easy as that.
So, having 10% higher frequency and 10% lower voltage compensates each other
Click to expand...
Click to collapse
I wouldn't call 10% more peak power consumption big if you take in account that the cpu is only running at the max clock speed a very small amount of time. 90% of the time the device is sleeping anyway and even if it's not you barely need the max clock speed. But if you do you will recognize the difference.
On the other side the reduced voltaged can safe you power all the time.
willverduzco said:
I'd even wager to say that if you're slightly under-volted and as heavily overclocked as you can go at that given voltage, you'll save some trivial amount of power versus stock because of the fact that voltage affects power draw significantly more than clock speed. I would also wager that if you are at an overclocked speed and are at stock voltage, the amount of current and power draw will be almost indistinguishable to the end user, since things like display will almost always use much more power if the display is on for any appreciable amount of time.
Click to expand...
Click to collapse
That's exactly what I experienced.
Pommes_Schranke said:
I wouldn't call 10% more peak power consumption big if you take in account that the cpu is only running at the max clock speed a very small amount of time. 90% of the time the device is sleeping anyway and even if it's not you barely need the max clock speed. But if you do you will recognize the difference.
On the other side the reduced voltaged can safe you power all the time.
Click to expand...
Click to collapse
Yes, you're right, and that's why I corrected myself in my second post. I totally forgot about the frequency scaling.
Off topic, but this is why I love XDA. Rational debate over a subject by intelligent people, where there usually isn't flaming. Thanks added to the two of your posts.
Hello, can someone please explain how my battery life improves when I set minimum cpu clock from 200 to 500?
I usually get 3 hours of screen time, with 500 as minimum I get nearly 4 hours. This difference is significant enough to make me wonder and ponder about how this happens.
It's counter logical, something with a higher minimum should drain faster.. right?
Does both cpu states are working at the same voltage? If yes (or the difference is very small) then the battery saving are from the increased execution speed .
In my own opinion, i dont think it affect much, while more than 70%+ battery drain by screen, unless u use cpu 100% all the time, otherwise i wouldnt too much concern abt that
Sent from my GT-N7000 using XDA Premium HD app
Chip efficiency changes with frequency. We tested this on my other phone (an Atrix- nice phone even now!)
Sometimes the CPU is just more power efficient doing tasks at higher frequencies. In a sense, the processor works faster, but for less time- so although it is running faster and requires more battery power, it completes the task much earlier and uses less power in total for that process.
My note, when running at 1.4ghz uses battery so much faster than at 1ghz, but the battery saving when dropping down from 1ghz is minimal, if existent at all.
Welcome to the not-always-intuitive world of modern CPU power usage.
The old mantra "higher frequencies use more power" becomes muddy in situations where the CPU can clock-gate parts of the chip when idle (cpuidle) and where the CPU voltage can change.
It was proven nearly a decade ago that if you don't change voltage at all with clock AND you have a good cpuidle implementation - it is actually best to always clock the CPU at maximum frequency. When voltage changes are in effect - it's harder to tell.
On most devices, the voltage for 500 and 200 are nearly identical. 500 does, I believe, have a somewhat higher bus frequency. So for a given workload, 500 MHz at, say, 20% load will use not much more power than 200 MHz at 50% load. In some cases, a device running at 500 MHz will finish a task more quickly and enter deep sleep faster.
Pretty much - 200 vs. 500 is really questionable in terms of which is best for power consumption. This is why I always set my screen-on minimum to 500.
Any frequency below 200 MHz is pointless as you can't undervolt those frequencies enough compared to 200 to make them have any benefit - in fact in many cases, adding a 100 MHz step is WORSE for battery.
Edit: One thing to note - In Gingerbread, the cpuidle driver was FAR less effective than it is in ICS. Only LPA and IDLE states were enabled by default, and the target residency for both was 40 ms.
In ICS, LPA, AFTR, and IDLE states are enabled and the target residency is 10ms. So it can hit deeper idle states far more often. For example, AFTR isn't as good as LPA - but it's better than dropping all the way to IDLE if you can't enter LPA. This is, in general, why the power consumption when wakelocked is much lower in ICS.
The bad news is that the suspend/resume cycle of the device is longer in ICS, AND cpuidle is totally blocked during suspend/resume - so the suspend/resume cycle eats even more juice than it did before, and it was historically one of the biggest users of power. Eventually I want to try and reduce this consumption.
Thanks for the good explanation mate, it has made things clear for me
Will be keeping my note on minimum of 500MHz aswell as it is a good improvement with no or next to no extra battery drain
As we all know, the Snapdragon 810 processor in our OnePlus 2 phones is prone to overheat, especially during heavy tasks such as gaming. With the stock kernel (which probably most of you are using) this leads to the A57 cores being partially or fully shut down and the display - which generates additional heat - being dimmed in order for the phone to keep a healthy temperature (healthy for both its components and the hands that are holding it.) This, in turn, leads to lag when playing especially demanding games. Which in turn leads to a frustrated user.
With root access, it's possible to use custom kernels and/or custom thermal throttling profiles in order to (at least partially) circumvent these issues, by throttling the CPU frequency and/or limiting the number of active cores, using different schedulers and governors, and by applying thermal profiles that allow the phone to get hotter (in order to keep higher CPU frequencies for a longer duration).
Since I bought the OPT, I was playing a very power hungry game - Republique - which, at its highest graphics quality setting, pushes the phone to its limits. I quickly switched from the stock kernel to the Boeffla kernel and started experimenting with schedulers, governors, hotplugging settings, CPU/GPU frequencies and thermal profiles, but nothing I have done so far makes it possible to play the game for more than 15-20 minutes before some kind of throttling / heat control sets in and the game starts lagging.
I tried limiting both CPU clusters to only 2 cores while maintaining higher frequencies, I tried throttling the frequencies and keeping all 8 cores active, and I tried all kinds of solutions in-between with anything from 4-8 cores active and frequencies anywhere between 60% and 100%. I also tried the various thermal profiles that the kernel offers. But whatever I did, the game was either lagging right from the start, or running smoothly for about 15 minutes before the screen was dimmed and the CPU was throttled, leading to a laggy experience.
So my question is, what do you guys do to keep the OnePlus 2 from overheating during gaming, while at the same time maintaining a lag-free experience? I don't seem to get anywhere with anything I try, so I'd be extremely grateful for some useful input.
vonotny said:
As we all know, the Snapdragon 810 processor in our OnePlus 2 phones is prone to overheat, especially during heavy tasks such as gaming. With the stock kernel (which probably most of you are using) this leads to the A57 cores being partially or fully shut down and the display - which generates additional heat - being dimmed in order for the phone to keep a healthy temperature (healthy for both its components and the hands that are holding it.) This, in turn, leads to lag when playing especially demanding games. Which in turn leads to a frustrated user.
With root access, it's possible to use custom kernels and/or custom thermal throttling profiles in order to (at least partially) circumvent these issues, by throttling the CPU frequency and/or limiting the number of active cores, using different schedulers and governors, and by applying thermal profiles that allow the phone to get hotter (in order to keep higher CPU frequencies for a longer duration).
Since I bought the OPT, I was playing a very power hungry game - Republique - which, at its highest graphics quality setting, pushes the phone to its limits. I quickly switched from the stock kernel to the Boeffla kernel and started experimenting with schedulers, governors, hotplugging settings, CPU/GPU frequencies and thermal profiles, but nothing I have done so far makes it possible to play the game for more than 15-20 minutes before some kind of throttling / heat control sets in and the game starts lagging.
I tried limiting both CPU clusters to only 2 cores while maintaining higher frequencies, I tried throttling the frequencies and keeping all 8 cores active, and I tried all kinds of solutions in-between with anything from 4-8 cores active and frequencies anywhere between 60% and 100%. I also tried the various thermal profiles that the kernel offers. But whatever I did, the game was either lagging right from the start, or running smoothly for about 15 minutes before the screen was dimmed and the CPU was throttled, leading to a laggy experience.
So my question is, what do you guys do to keep the OnePlus 2 from overheating during gaming, while at the same time maintaining a lag-free experience? I don't seem to get anywhere with anything I try, so I'd be extremely grateful for some useful input.
Click to expand...
Click to collapse
All the phones throttle while gaming. I use thermal extreme with boeffla kernel. And use 2 a53 at 1,3ghz and 2-4 a57 at 1,4ghz and I modified the throttle file and it underclock to 1,2ghz when it gets hot but it doesn't happen if you don't play longer than 30minutes and it doesn't lag either. You can leave stock settings but if course it will get hot quicker. Also with thermal hotplugged or something like that, I used it all cores online all the time at full speed and it doesn't throttle for a long time, so I don't know what overheating are you talking about. My nexus 5 throttle faster and disable 2 of 4 cores and leave the other 2 at half speed, and our processor overheats?. Oneplus throttle the device a lot because of the rumors, fortunately we can change that. Try what I said, cheers.
Sent from my ONE A2005 using Tapatalk
Migdilu said:
All the phones throttle while gaming. I use thermal extreme with boeffla kernel. And use 2 a53 at 1,3ghz and 2-4 a57 at 1,4ghz and I modified the throttle file and it underclock to 1,2ghz when it gets hot but it doesn't happen if you don't play longer than 30minutes and it doesn't lag either. You can leave stock settings but if course it will get hot quicker. Also with thermal hotplugged or something like that, I used it all cores online all the time at full speed and it doesn't throttle for a long time, so I don't know what overheating are you talking about. My nexus 5 throttle faster and disable 2 of 4 cores and leave the other 2 at half speed, and our processor overheats?. Oneplus throttle the device a lot because of the rumors, fortunately we can change that. Try what I said, cheers.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip with thermal extreme! The implementation in the latest Boeffla kernel v1.1 beta1 seem to do a very good job of not letting the phone get too hot while at the same time not throttling the CPU too much. Today, the performance was stable for almost 30 minutes of gaming, and when I checked the CPU stats I saw that all cores were still active (2x A53 + 4x A57), and only throttled to 960 MHz. This still delivered enough performance. (I started the game with both CPU clusters at 1.2 GHz, so this also seemed to help with keeping the phone at an acceptable temperature. I'm sure it would've gotten much hotter much quicker at higher CPU frequencies.)
I have to admit though, I was playing inside in an unlit room and thus the screen wasn't at max. brightness. We'll see how it will perform during my next work break when I have to make the screen much brighter.
vonotny said:
Thanks for the tip with thermal extreme! The implementation in the latest Boeffla kernel v1.1 beta1 seem to do a very good job of not letting the phone get too hot while at the same time not throttling the CPU too much. Today, the performance was stable for almost 30 minutes of gaming, and when I checked the CPU stats I saw that all cores were still active (2x A53 + 4x A57), and only throttled to 960 MHz. This still delivered enough performance. (I started the game with both CPU clusters at 1.2 GHz, so this also seemed to help with keeping the phone at an acceptable temperature. I'm sure it would've gotten much hotter much quicker at higher CPU frequencies.)
I have to admit though, I was playing inside in an unlit room and thus the screen wasn't at max. brightness. We'll see how it will perform during my next work break when I have to make the screen much brighter.
Click to expand...
Click to collapse
Does it throttle to 960mhz? for me never reach 1,2ghz. Playing real Racing for 30min it stays at 1,2ghz. And with thermal hotplugged (all cores enabled, all at stock freq gpu too) it doesnt throttle for 30 min, gpu only sometimes to 510mhz, i played 30 minutes and it didnt throttle, i dont know when it was going to throttle because i stop playing. But also, gaming with all cores and no throttling eats the battery.
Migdilu said:
Does it throttle to 960mhz? for me never reach 1,2ghz. Playing real Racing for 30min it stays at 1,2ghz. And with thermal hotplugged (all cores enabled, all at stock freq gpu too) it doesnt throttle for 30 min, gpu only sometimes to 510mhz, i played 30 minutes and it didnt throttle, i dont know when it was going to throttle because i stop playing. But also, gaming with all cores and no throttling eats the battery.
Click to expand...
Click to collapse
I guess it throttled to 960 MHz because the game I'm currently playing (République) is pretty resource hungry.
Devs,
The performance of le 2 is very bad when it comes to gaming.
It is the same in every stock eui to miui and all lineage os ROMs like AICP which uses lineage is kernel.
As per my finding this is due to severe thermal throttling in eui as well as in lineage os 13 and 14.1.
Firstly the two A72 CORES don't run while any task making it like SD 650 and clock go soo down at reaching 34° to 35°c and at above temp all A72 CORES ARE DOWN in lineage is and only one works in stock eui, same goes with GPU under clocking starts at 32°c making gaming experience horrible,
Even kernel auditor don't have any control in any of the ROMs and in lineage is 14.1 27 Feb build it is told it have core control but it can make all A72 cores run couldn't control clock speeds and result is the same ,
So I request devs please make a kernel from scrap and don't take hints from eui kernel and give us good gaming experience.
Thank you
ajroxxx said:
Devs,
The performance of le 2 is very bad when it comes to gaming.
It is the same in every stock eui to miui and all lineage os ROMs like AICP which uses lineage is kernel.
As per my finding this is due to severe thermal throttling in eui as well as in lineage os 13 and 14.1.
Firstly the two A72 CORES don't run while any task making it like SD 650 and clock go soo down at reaching 34° to 35°c and at above temp all A72 CORES ARE DOWN in lineage is and only one works in stock eui, same goes with GPU under clocking starts at 32°c making gaming experience horrible,
Even kernel auditor don't have any control in any of the ROMs and in lineage is 14.1 27 Feb build it is told it have core control but it can make all A72 cores run couldn't control clock speeds and result is the same ,
So I request devs please make a kernel from scrap and don't take hints from eui kernel and give us good gaming experience.
Thank you
Click to expand...
Click to collapse
My findings were exactly same as yours, the cpu and gpu, both are underclocking for even slightest of temperature rise. This is bad, but the good news is, I figured out a way, by which we can disable this poorly configured thermal throtling.
Delete this file here: /system/etc/thermal-engine-s2.conf
I don't know it it is safe or not, but I have been gaming with my device after deleting this file for about 10 days and there is no explosions yet. Hahaha.
Also, if you want, instead of deleting this file, you can modify some parameters so that, it starts throttling after some really high temperatures, instead of current values, but I like deleting that file because some thermal throtlling algorthm is always embedded in soc anyways.
shivamg95 said:
My findings were exactly same as yours, the cpu and gpu, both are underclocking for even slightest of temperature rise. This is bad, but the good news is, I figured out a way, by which we can disable this poorly configured thermal throtling.
Delete this file here: /system/etc/thermal-engine-s2.conf
I don't know it it is safe or not, but I have been gaming with my device after deleting this file for about 10 days and there is no explosions yet. Hahaha.
Also, if you want, instead of deleting this file, you can modify some parameters so that, it starts throttling after some really high temperatures, instead of current values, but I like deleting that file because some thermal throtlling algorthm is always embedded in soc anyways.
Click to expand...
Click to collapse
See your findings are correct but I myself renamed thermal config s2 but it didnot have any effect and at 33 ° I can see GPU under clocked at 432 MHz and CPU under clocks itself , and at 35° the lagging in games can be seen easily
Will try deleting the file also ,hoping it can have any effect
ajroxxx said:
See your findings are correct but I myself renamed thermal config s2 but it didnot have any effect and at 33 ° I can see GPU under clocked at 432 MHz and CPU under clocks itself , and at 35° the lagging in games can be seen easily
Will try deleting the file also ,hoping it can have any effect
Click to expand...
Click to collapse
My cpu temp have gone over 60°c but I haven't seen any throttling in cpu or gpu. But when, that file was present, those temperatures were never reached because of thermal throttling.
shivamg95 said:
My findings were exactly same as yours, the cpu and gpu, both are underclocking for even slightest of temperature rise. This is bad, but the good news is, I figured out a way, by which we can disable this poorly configured thermal throtling.
Delete this file here: /system/etc/thermal-engine-s2.conf
I don't know it it is safe or not, but I have been gaming with my device after deleting this file for about 10 days and there is no explosions yet. Hahaha.
Also, if you want, instead of deleting this file, you can modify some parameters so that, it starts throttling after some really high temperatures, instead of current values, but I like deleting that file because some thermal throtlling algorthm is always embedded in soc anyways.
Click to expand...
Click to collapse
Deleting this file is an absolutely terrible idea. Modify it instead.
Jelixis said:
Deleting this file is an absolutely terrible idea. Modify it instead.
Click to expand...
Click to collapse
At first, I thought the same. But yesterday, i have played asphalt 8 in bright sunlight(to test if there is some thermal throttling left embedded in soc). And I was right, it throttles down the gpu, big cores, small cores, even some cores went offline automatically. After the device was cooled, everything wqs back to normal. So, IMO, there is no harm even if we play in extreme conditions with the file deleted, thermal throttling will kick in when its needed. Although, I advise modifying the file to others. Hahaha
shivamg95 said:
At first, I thought the same. But yesterday, i have played asphalt 8 in bright sunlight(to test if there is some thermal throttling left embedded in soc). And I was right, it throttles down the gpu, big cores, small cores, even some cores went offline automatically. After the device was cooled, everything wqs back to normal. So, IMO, there is no harm even if we play in extreme conditions with the file deleted, thermal throttling will kick in when its needed. Although, I advise modifying the file to others. Hahaha
Click to expand...
Click to collapse
Thermal throttling happens even in the best chips. Most of the time, it's integrated in the lower level portions of the chip.
Just let it be, really. Thermal throttling is the way of the chip of protecting itself from heat damage. PC processors, for example, shut down when removing the fan and reaching critical temperatures.
Jelixis said:
Thermal throttling happens even in the best chips. Most of the time, it's integrated in the lower level portions of the chip.
Just let it be, really. Thermal throttling is the way of the chip of protecting itself from heat damage. PC processors, for example, shut down when removing the fan and reaching critical temperatures.
Click to expand...
Click to collapse
Ya true it is present in every chip but optimizing is Also a thing right.
In le 2 the two A72 cores don't run at all above 30°(except when opening apps while it is cool ,so after 33 or 34° they are not used in anything,and 34 is average temp of the phone while using ,that means it just exactly works like a loweclocked SD 650 which even more throttled with each degree rise in temp and at 36 ° ( which is avg temperature while gaming ) phone turns off one more A72 core meaning three A72 cores are off and one a72 is throttle to around 800 mhz and even all a53 cores run at half clock speeds and till that time GPU also reaches below 350mhz and lower a and it impossible to run even minor games like subway surfers lag free,
And since lineage is kernel has taken hint from eui kernel ,it performs exactly the same as stock kernel which leaves us with no choice left.
@codeworkx please look into this issue and please build a kernel for gaming performance as SD 652 is getting wasted due to thermal throttling, @codeworkx I am sure you know this issue better than me ,please find time to work on it.
@shivamg95 deleting the thermal file couldn't help this
ajroxxx said:
Ya true it is present in every chip but optimizing is Also a thing right.
In le 2 the two A72 cores don't run at all above 30°(except when opening apps while it is cool ,so after 33 or 34° they are not used in anything,and 34 is average temp of the phone while using ,that means it just exactly works like a loweclocked SD 650 which even more throttled with each degree rise in temp and at 36 ° ( which is avg temperature while gaming ) phone turns off one more A72 core meaning three A72 cores are off and one a72 is throttle to around 800 mhz and even all a53 cores run at half clock speeds and till that time GPU also reaches below 350mhz and lower a and it impossible to run even minor games like subway surfers lag free,
And since lineage is kernel has taken hint from eui kernel ,it performs exactly the same as stock kernel which leaves us with no choice left.
@codeworkx please look into this issue and please build a kernel for gaming performance as SD 652 is getting wasted due to thermal throttling, @codeworkx I am sure you know this issue better than me ,please find time to work on it.
@shivamg95 deleting the thermal file couldn't help this
Click to expand...
Click to collapse
Deleting that thermal engine file, did help. Don't know why it doesn't work for you.
shivamg95 said:
Deleting that thermal engine file, did help. Don't know why it doesn't work for you.
Click to expand...
Click to collapse
It is not working and would have been not working for you also just check with kernel auditor,
I have check it thoroughly .
I think you don't know how to check
Tell me the process you check
ajroxxx said:
It is not working and would have been not working for you also just check with kernel auditor,
I have check it thoroughly .
I think you don't know how to check
Tell me the process you check
Click to expand...
Click to collapse
First i make the soc heat by playing games or running benchmarks, then i open kernel auiditor and check if maximum cpu freq gets lowered or automatically or not. But it doesn't happen after deleting that file. Also, the gameplay seems very fluid then before. I also check for gpu max freq.
Hey, I have Cool 1 (same Soc) and yes, very dissapointed because in second 1 starts the throtling...
I have Kernel auditor. Which settings should I force?
hello, very nice threat.
I had some different experiences.
For me throotling starts slightly at 37° and bigger at 39 or 40 ... this results to throotled big cores at 1248mhz and a gpu to 432
to avoid that I made some underclocking settings which gives my setting antutu score of 69000 instead of 82000 and a geekbench score of 1000/3500 which is giving me cool and fast gaming enough
https://forum.xda-developers.com/le-2/how-to/kernel-adiutor-settings-8h-sot-colour-t3721254
Hi there,
Is it possible to overclock the cpu and gpu?
If so how? Or which rom/kernel?
Running G model 4gb ram
Even if you can, it will chew the battery and heat up.
RobboW said:
Even if you can, it will chew the battery and heat up.
Click to expand...
Click to collapse
Not a problem as I would only be using it sometimes not permanently
Kendal21 said:
Not a problem as I would only be using it sometimes not permanently
Click to expand...
Click to collapse
in theory it is, we had a a kernel that OC'd the CPU way back then, but the SoCs on the Axons are probably low-binned - shutdowns and stuff like that are commonplace
But still, do you know what OC does to a phone? New phones are thermally constrained devices, starting from the snapdragon 800 series onwards. remember the sd805/810 disaster? Well...
If you run your phone at 100% load, it will run at max speed (1.56/2.15) for a very short time (say, 30 seconds), until the SoC reaches a specific temperature. After that it'll go down to a more manageable frequency, eventually going even further down or staying at 1.8 ghz, depending on your specific situation (the pink thermal blob might be bad).
That's why VR mode sets your cores at around 1.8 ghz, to keep them from going hot and lowering frequency even more. Sustained performance is better than burst performance on gaming.
Day to day usage is another matter, because more frequency won't mean thermal throttling when opening apps or unlocking the phone, beside the obvious battery usage
TL/DR: Be prepared to make your own kernel if you want to OC. It might not work