Related
First off is this a good idea? can such small devices be over clocked in a safe way without risking damaging the hardware?
if yes which would you say was the best app for doing so?
Hi,
A good idea... maybe, maybe not... it depends on what you want... higher scores in bench?A shorter battery life?A very very hot device while browsing or gaming (if you run at 1.8Ghz for example)?A little extra power for some apps/games?
With overclocking a little (1.5/1.6Ghz) I noticied that some apps open a little faster and the genera UI is a little more responsive...
There is always a (little) risk to overclock our phones, generally due to overheat but also some CPU's can't handle high overclock.
For me I don't remember reading someone burn her CPU with overclocking but...
There are still some software protections before to burn a CPU (thermal throttling, CPU temp limit before shutdown, etc...).
Obiously the duration of life could be reduced mainly if you always run at 1.8Ghz with playing games... So the "safe" way would be no overclock or a little overclock like 1.5Ghz... For you to test and decide...
For the apps: SetCpu, System Tuner... there is a bunch on the Play Store.Just for the CPU settings I would say SetCpu.
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
I can't see the need on this device, I might experiment with uv, maybe even underclocking, but as above, super smooth on siyah, and Slim Rom
Sent from my GT-I9300 using xda premium
Talking about battery life i installed darkys rom 3 onto my i9300 and the battery life is already suffering a loss of maybe around 25%. In saying that over clocking will only cause me to lose even more so ill leave it for now
Sent from my GT-I9300 using xda app-developers app
I'm too running on slim ics and siyah kernel. Best battery life and performance!
GGSunny12 said:
For me i will never overclock my cpu. Just install siyah kernel and it's pretty smooth in games. Overclocking will damage your cpu and maybe loose some of the performance.
Click to expand...
Click to collapse
Overclocking won't damage your CPU unless you set crazy voltages, or let it overheat. Also, it won't lose performance... that's crazy talk. Only if it overheats will it throttle, but that only happens on large clock rates like 1.8GHz or if you're in a hot environment.
I had my old LG GT540 overclocked with no heat problems mind that was only a 600mhz cpu, had it up to 825mhz.
But we already have a powerful cpu in this phone, foe now I don't see the need to overclock.
Sent from my GT-I9300 using xda premium
The best app depends a lot on your kernel and device. For example, for my Galaxy S2 the best OC was with TegraK Overclock.
With my Xoom CPU Tuner is still the best.
With the S3 I suppose CPU tuner would be alright as well, but I haven't had the urge to OC it, because I find SiyahKernel still quite unstable in the S3.
You need an overclockable kernel in order to OC your phone.
As for damages, it is hard to tell if they are permanent, but picture this: your battery will have to be recharged more often, because it will drain faster. Since batteries have a limited lifespan which depends on how many charge cycles they go through, the more often you discharge/charge them, the shorter their lifespan will be.
Also, there is no telling what kind of ill-effects the added heat can do to the phone. It may be totally harmless, but it may also affect the quality of the display, since the added heat will be right underneath the screen.
The lifespan of the CPU will be shortened: instead of being able to work well for 20 years, it will work well for 18, 17, 15, but more than enough time for us to already have replaced our S3 for organic, intradermal smartphones!
Is it safe to o/c or set maximum cpu frequency? I want fast speed but don't want to F up my device... I little advice is all I need thanks In advance.
Sent from my SAMSUNG-SGH-I717 using xda premium
I would advise you to learn more about your phone before you even think about overclocking...
There are always potential dangers when you run any piece of electronic equipment at a different spec than the factory sets it at..
And not all silicone is created equal, so a setting that works for me might fry your cpu's.
As stated above ...
Risk is present in overclocking, as it drives the CPU beyond it's design limits.
Heat increases, and perhaps the more interesting part, is the "leakage" that occurs as frequency increases.
Regarding the 2 core note 1 CPU...results begin to go negative after 1.65 ghz on my device. And heat increases by 12%.
So basically, I'm cooking my CPU beyond 1.7 ghz.
Performance curve also begins to revert beyond 1.75ghz on my device.
Long story short, I don't overclock....as I can prove that my device suffers ...g
Thanks for the advice. I think I'll still with 1515 cpu frequency
Sent from my SAMSUNG-SGH-I717 using xda premium
Imbovd to the max and besides a little more heat I notice a severe difference in positive device function. My advice is to start small oc and monitor your device.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
If someone would teach me that would be great!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Better battery life. But be careful with undervolting. It can cause phone to be unstable. Under clocking is more forgiving. If you are going to do either I would suggest only making small changes and then use phone for several hours to settle in. If all good then try next step lower and test until you find the limit of your phone. Then bump it back up to last stable setting.
There are no noticeable benefits.
jimmer411 said:
There are no noticeable benefits.
Click to expand...
Click to collapse
I agree, its mostly the placebo effect regarding lag, a variable effect regarding battery life, due to user apps, and downright dangerous regarding overheating.
But many people whine when its not available for a kernel. I don't have a very high opinion of its necessity.
Battery life in our phones is dominated by the screen and radio (cell and wifi) but I find that undervolting at least reduces the heat when I'm doing something intensive like SNES emulation. Lag in our phones is also primarily a software issue (I have other Android devices with the same hardware running at the same MHz and it's a smoother experience).
Not that my Note got hot, it's just less warm.
ZacksBuilds said:
If someone would teach me that would be great!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
There's no reason not to under volt.
UC=Under clock
UV=Under volt
OC=Over clock
OV=Over volt.
Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz.
Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency.
When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life.
There are two different ways to approach customizing frequency and voltage to your needs.
One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life.
Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success.
Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life.
Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip).
These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded.
If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life.
The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts.
Sent from my SGH-I717 using XDA Premium HD app
Jamesyboy said:
There's no reason not to under volt.
UC=Under clock
UV=Under volt
OC=Over clock
OV=Over volt.
Newer generations of chips have tremendous tolerances. If you were to look at the S3, a Qualcomm built SoC that was a bit long-in-the-tooth by the time the Note was released, you'd see that in many cases, there were phones that featured the chip, but were clocked lower... I.E at 1,000 MHz.
Most chips are designed to run faster than they do, at least for short periods of time. Modern chips use temperature and load to designate the running frequency.
When Qualcomm releases a chip, they need to be sure that 99% of the units they produce, can run with a near-flawless level of stability. Because of this, they often run chips slower, and at a higher voltage than is actually needed. The result is, that Qualcomm or Samsung might design a chip rated for 2ghz, and release their first device with the chip running at 1.5ghz. This is common. Each piece of silicon is slightly different due to manufacturing differences. Chips are made on giant discs, with hundreds of chips on a single disc. The chips in the center are generally considered to be of a slightly higher quality, requiring less voltage, or capable of running at a higher frequency, sometimes both. Because of this, each device is capable of slightly more, or slightly less. The challenge is for Qualcomm to set the speed and power usage for every chip-- the challenge for us, is to see if we can run the chip at a higher frequency, while drawing less power....because power =heat, and power= battery life.
There are two different ways to approach customizing frequency and voltage to your needs.
One: If you could run your Note at 1,900mhz, instead of 1500mhz, and draw the same amount of power, that'd be considered a success case. Your device would be faster, without a hit in battery life.
Two: Or, if you could run the device at the same speed, and lower the voltage (saving battery life), this would also be considered a success.
Sometimes, but rarely in the mobile space, you'll get lucky and receive a prime piece of silicon, and you'll be able to over clock, WHILE undervolting...resulting in a faster phone that uses battery life.
Ranger was correct...clock speed changes on the order of +/-20 percent are hardly noticeable. However, power requirements grow exponentially at higher frequencies, and on a mobile device, they're noticeable. While a device might require 1.2 volts at 1.5 GHz, and 1.3 at 1.6ghz, it might also only require 1.05, or 1.0 volts at 1.4ghz. These numbers are theoretical, and shouldn't be used-they arent even close to correct. They're used merely to illustrate that to over clock, chips often require more power than over clocking is worth, in heat (and heat past a certain point will instantly fry your device, or will reduce the lifespan of the chip).
These are general ideas on over clocking. If you want to know something specific, ask away. When over clocking/underclocking, the governor used (a set of conditions that tells the CPU when to change from, say 300mhz (when the screen is off, and the device isn't being used), to 1.5ghz, when both cores are being used, and fully loaded.
If you want to save battery life, a combination of build.prop radio tweaks, modem tweaks, under clocking profiles, and using a custom governor can significantly increase standby time, and noticeably, but not too significantly increase usage time. Its important to know though, that the screen is the hungriest part of our device, and brightness is the the quickest setting to adjust to gain battery life.
The same is true for performance. Kernel, OC profiles, build.prop and launcher tweaks, GOU over clocking, etc. All in combination can have a noticeable effect, because performance is the net sum of dozens of moving parts.
Sent from my SGH-I717 using XDA Premium HD app
Click to expand...
Click to collapse
So what I understood is this: instead of having let's say, your note running at 1.2ghz consuming 15% battery per hour you can have it at 1.5ghz consuming the same battery life?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
We have smashed into the performance ceiling. Without active cooling or massive increases in efficiency through improved architecture, there is no way smartphones (or tablets) can become more powerful.
I can't use 75% of this phone's potential performance while playing San Andreas. With a custom kernel and thermal throttling disabled, the phone shoots up to 90c in minutes and then reboots; that is with 'On Demand' and max frequency at 1.73 ghz.
Coming from a gnex (max stock freq. could reach 80c), absolute performance has become meaningless. Maybe it has been for a while.
This is absolutely true. We need fans or cooling systems if we shall be able to take full advantage of the massive powers in our phones. For now, I think the only way is to play our favorite games in a freezer.
Sent from my LG-D802 using xda app-developers app
otherwise lg would melt ...
or, you can root your phone and disable thermal throttle. then you can use it at full performance up until you reach the thermal shutdown temp without worrying your cpu being thermally throttled
and i had a gnex as well, it could reach 110C. i always turned off thermal throttle, and always turn off thermal throttle on my nexus 5. you dont reach thermal shutdown without actively trying too, and the cpu doesn't get throttled.
crazysoccerman said:
We have smashed into the performance ceiling.
Click to expand...
Click to collapse
While that statement was not even close to being true when you posted it, tomorrow it'll be less true, etc etc.
If you build the exact same chip with a smaller die process, the smaller die process chip will be more efficient (cooler) and faster. Then there are of course other improvements that are continuously being made, more cores to spread the load, faster ram to reduce bottlenecks, etc, etc, again, all while getting faster and cooler because of improved production methods.
So no, phones will get more powerful, more ram, better screens etc.. Maybe someday we'll have another battery breakthrough, but right now with the massive push on efficiency we're getting some runtime back on batteries, etc.
khaytsus said:
While that statement was not even close to being true when you posted it.
Click to expand...
Click to collapse
Actually it is true. The performance on the G2 is limited by heat. You can't run the phone under load at or near its max specified frequency for any reasonable period of time. Try it yourself. To deny that is to deny facts.
Also, a smaller die reduces the surface area for the dissipation of heat.
crazysoccerman said:
Actually it is true. The performance on the G2 is limited by heat. You can't run the phone under load at or near its max specified frequency for any reasonable period of time. Try it yourself. To deny that is to deny facts.
Also, a smaller die reduces the surface area for the dissipation of heat.
Click to expand...
Click to collapse
Read the OP, it states "smartphones". Oh wait, you are the OP
vPro97 said:
This is absolutely true. We need fans or cooling systems if we shall be able to take full advantage of the massive powers in our phones. For now, I think the only way is to play our favorite games in a freezer.
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
Lol fans aren't a good solution
Sent from my VS980 4G using Tapatalk
Time ago a saw a cooling case. If i find the site again, i will post it.
Imagine the HTC One, but with a heat pipe transferring heat from the SOC to the aluminum case... That would provide more cooling, but I'm not sure of the size penalty of the heat pipe.
Also, more efficient chips CAN provide more power and generate less heat. A perfect example is Intel's pentium4 "netburst" architecture vs the newer and considerably more efficient "core duo" chips.
Take care
Gary
Sent from my Nexus 7 using Tapatalk
are there any phones out there that don't heat up while performing great in all demanding titles?
Sent from my LG-D801 using xda app-developers app
well yeah smartphones aren't designed to run at 100% of the cpu/gpu speed for long periods of time. If they were, they would have to be a lot bigger and/or have active cooling. I guess I never really noticed the "wall" because all the mobile games I play do not push the phone to the limit. When you are comparing it to the past though, remember the newest CPUs are significantly faster clock for clock. 1.5ghz is not the same for an A9 vs Krait 400.
So what iz the solution ? Do we have any modification or init.d script to disable that cooling system ?
Solution Is a thermal pad on CPU
Mantra96 said:
Solution Is a thermal pad on CPU
Click to expand...
Click to collapse
:V ...
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
Vipxpert said:
:V ...
Click to expand...
Click to collapse
It's time to void warranty ! :V
Hello Axon 7 users, I just picked up one a couple of days ago. After finally figuring out the bootloader, bootstack and general stock experience I tested a little bit of gaming. I found that a basic game like Clash Royale heats the battery up to around 42°C already with low brightness and slow charging. A more intensive game like the new Knives Out runs only slightly hotter but it becomes apparent that CPU gets throttled soon after loading to 1036MHz across all cores causing lag.
It's disappointing so I tried to find how to modify the throttling. Using ZTE's Power Manager setting on performance or balanced doesn't seem to have a noticeable difference.I tried the only stock custom kernel AX7 but it's outdated on B32 and I find it randomly reboots regularly. The stock kernel itself allows some configuration, but the thermal settings in Kernel Adiutor don't reflect any charge.
A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself.
I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling.
However as expected the device heats up a few degrees more now. This now puts my battery up to 47°C in Knives Out under the same conditions. Charging is stopped at 45°C by the system so as previously mentioned it's unmodified.
I just wanted to check since I couldn't find it mentioned. Is everyone ok with gaming performance limited to 1036Mhz with the normal throttle? Also are my temperatures normal? I guess CPU doesn't seem that high reaching around 65°C, it's just that the battery has less than 20°C difference in intensive performance. I suppose it's a quirk of the heat pipe to battery as heatsink design. I just expected more from a metal unibody chassis and at least normal CPU gaming performance. I thought my Sony Z3 Compact design was bad for battery thermals, with the battery stacked behind the CPU board, sandwiched in insulating glass. But I didn't expect to see a phone to route a heatpipe directly to it's battery.
Anyway it is what it is. Follow this information if you want some better gaming performance at the cost of your battery cycle life. In my case I bought the Axon7 just as a separate media consumption device rather than a phone so I can live with the tradeoff. If battery gets bad enough before 2 years I'll consider using warranty at the loss of receiving their refurbished replacement. Manufacturer warranty's in fact cover batteries for 80% depletion.
I recommend the app DevCheck Pro for being able to monitor CPU, GPU, temperatures and other things overlayed. I think some others may do similar but they may not be updated for Big Little and are more instrusively overlayed.
Infy_AsiX said:
A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself.
I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling.
Click to expand...
Click to collapse
I read half of that to be honest, but just one thing: To make things harder, ZTE added added a write protection on the system. To disable it you have to use a computer and connect your phone with ADB, then issue "adb reboot disemmcwp" (like DISable EMMC Write Protection). Otherwise all the changes that you made get undone after a reboot, and obviously you'd have to reboot after modifying that file
On LOS you can use BeastMode (even if your phone isn't an A2017U) which for me is the best friggin kernel I've used in performance terms. There you can change thermal limits
Infy_AsiX said:
Hello Axon 7 users, I just picked up one a couple of days ago. After finally figuring out the bootloader, bootstack and general stock experience I tested a little bit of gaming. I found that a basic game like Clash Royale heats the battery up to around 42°C already with low brightness and slow charging. A more intensive game like the new Knives Out runs only slightly hotter but it becomes apparent that CPU gets throttled soon after loading to 1036MHz across all cores causing lag.
It's disappointing so I tried to find how to modify the throttling. Using ZTE's Power Manager setting on performance or balanced doesn't seem to have a noticeable difference.I tried the only stock custom kernel AX7 but it's outdated on B32 and I find it randomly reboots regularly. The stock kernel itself allows some configuration, but the thermal settings in Kernel Adiutor don't reflect any charge.
A quick Google search brings up how LG V20 Snapdragon 820 users edit /system/etc/thermal-engine.conf to tweak the throttling levels. Their config is quite different but they mod big to 1824Mhz and let little scale itself.
I couldn't get thermal-engine.conf to use the thermal-engine-8996-perf.conf values by copying the values to it as it suggests inside. I tried renaming it with the -zte.conf ending as it suggests as well but that didn't work. After just renaming both the normal and perf conf files with a .bak ending, I've found better throttling performance. Big now throttles to 1632Mhz and little to 1324Mhz. As far as I can understand the files don't have charging rates inside, just GPU and CPU throttling.
However as expected the device heats up a few degrees more now. This now puts my battery up to 47°C in Knives Out under the same conditions. Charging is stopped at 45°C by the system so as previously mentioned it's unmodified.
I just wanted to check since I couldn't find it mentioned. Is everyone ok with gaming performance limited to 1036Mhz with the normal throttle? Also are my temperatures normal? I guess CPU doesn't seem that high reaching around 65°C, it's just that the battery has less than 20°C difference in intensive performance. I suppose it's a quirk of the heat pipe to battery as heatsink design. I just expected more from a metal unibody chassis and at least normal CPU gaming performance. I thought my Sony Z3 Compact design was bad for battery thermals, with the battery stacked behind the CPU board, sandwiched in insulating glass. But I didn't expect to see a phone to route a heatpipe directly to it's battery.
Anyway it is what it is. Follow this information if you want some better gaming performance at the cost of your battery cycle life. In my case I bought the Axon7 just as a separate media consumption device rather than a phone so I can live with the tradeoff. If battery gets bad enough before 2 years I'll consider using warranty at the loss of receiving their refurbished replacement. Manufacturer warranty's in fact cover batteries for 80% depletion.
I recommend the app DevCheck Pro for being able to monitor CPU, GPU, temperatures and other things overlayed. I think some others may do similar but they may not be updated for Big Little and are more instrusively overlayed.
Click to expand...
Click to collapse
I have noticed the same performance many months ago.
I tried changing the thermal values with both ways through the conf file or a custom kernel but all implementations seem to be faulty as nothing changed.
In the end I gave up because I couldn't find a solution for this.
But I figured because my games clash of clans, ppsspp, gba emulators don't lag I din't care much.
If you find a solution let me/us know.
Or post the modded confs you're using as well if you can.
That's all from me.
I just renamed both the thermal-engine files with a .bak extension. I've also got ZTE's Power Manager frozen as the performance profiles there don't seem to do anything and I don't use it's other features. There's some kind of CPU GPU throttle still in place but it's much higher as previously mentioned,. After searching further I saw your discussion about /vendor/bin related throttle, maybe that's the fallback it's now on.
The device does get uncomfortably hot with a new demanding game at maximum settings. I wouldn't recommend doing this if you want to maintain your battery. However if you're interested I discovered the Ax7 allows defining a lower maximum battery voltage in another TL/DR post https://forum.xda-developers.com/showpost.php?p=74746734&postcount=1353. To explain simply, it's possible to limit the voltage low for health and safety while keeping the device almost primarily powered by mains. Effectively the battery is at an optimum low voltage, practically idle but very hot. A little complicated sure, but worth it. Getting a Daydream V1 tomorrow to play with, this stuff will help with heat and performance a lot. If anyone wants my long winded explanation, give me a shout.
The CPU temp does jump around higher than 70. I'm tending to think that current powerful mobile processors aren't efficient enough for the physical body constraints of phones. Let alone poorly designed ones. The 820 is meant to be an improvement over the 810, wouldn't believe it by the throttle required and performance lost. The 835 is efficient enough apparently. From experience though I have my doubts on reviews and benchmarks to reflect real usage stress.
edit: Oh and disable VDD restriction in your kernel setting if you've set it to auto enable. That seems to be a switch for the aggressive throttle still available after mod.
Sent from my ZTE Axon 7 using XDA Labs
Infy_AsiX said:
I just renamed both the thermal-engine files with a .bak extension. I've also got ZTE's Power Manager frozen as the performance profiles there don't seem to do anything and I don't use it's other features. There's some kind of CPU GPU throttle still in place but it's much higher as previously mentioned,. After searching further I saw your discussion about /vendor/bin related throttle, maybe that's the fallback it's now on.
The device does get uncomfortably hot with a new demanding game at maximum settings. I wouldn't recommend doing this if you want to maintain your battery. However if you're interested I discovered the Ax7 allows defining a lower maximum battery voltage in another TL/DR post https://forum.xda-developers.com/showpost.php?p=74746734&postcount=1353. To explain simply, it's possible to limit the voltage low for health and safety while keeping the device almost primarily powered by mains. Effectively the battery is at an optimum low voltage, practically idle but very hot. A little complicated sure, but worth it. Getting a Daydream V1 tomorrow to play with, this stuff will help with heat and performance a lot. If anyone wants my long winded explanation, give me a shout.
The CPU temp does jump around higher than 70. I'm tending to think that current powerful mobile processors aren't efficient enough for the physical body constraints of phones. Let alone poorly designed ones. The 820 is meant to be an improvement over the 810, wouldn't believe it by the throttle required and performance lost. The 835 is efficient enough apparently. From experience though I have my doubts on reviews and benchmarks to reflect real usage stress.
edit: Oh and disable VDD restriction in your kernel setting if you've set it to auto enable. That seems to be a switch for the aggressive throttle still available after mod.
Click to expand...
Click to collapse
That's weird... what are the ambient temps where you live? Here it's anything between 20 and 30 degrees and mine never gets that hot, and it barely throttles. Of course you shouldn't game while charging, that WILL throttle the phone.
I have a big old CPU heatsink without a fan, and when I charge the phone at night I just put it upon the heatsink. It keeps the battery around the ambient temp, which I guess helps with battery degradation.
A nice app for monitoring the CPU is Trepn profiler, you can program it to show you anything like frequencies and temps on 2 separate graphs for example