Related
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
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
Hi, if you can enjoy putting this on your phone you Will be glad to have freely more autonomy on your phone, also, less heat that you will see in the same moment that you apply it, and, what is better, you will be able to have a lot more battery Avoiding being dependent of the charging and you can use your very well "heat efficient" phone with their polymer case which made a "sandwich" having it the cpu backed every time that a girl text you on tinder or stuff or, you put on a game to play.
What it does :
- Tweaks the Cpu to have less heat as well as more performance, enables You to choose what's better for you, in four options.
WHY I need this:
Apple have their iphone with 6 cores instead of 8. Their cores are: "two cortex X2 rebranded" and four low energy cores. And, they use only one program (iOS) and above them they run "complements" of the program, called "apps". Based on this, you can have FOUR different browsers on your iOS device that are essentially the same (WebKit) with a skin and some functionality. Avoiding you to have options. Likely better than that. So, you don't need power. Because you are not using it. Since everything runs fast because it's pre-loaded with this iOS, android developers paid by companies put a lot of cpu and Gpu power on your android phone to OVERPOWER that iOS devices. And that, comes at cost of battery.
So, in order to have the same functionality as before, and the same power level of apple, when you cut down the power of s processor you will have the same app opening/closing speed of apps as well as functions but, with a lot of more battery. Maybe you see one of tho "stutters" but that aren't granted, and you will have less heat also.
So, this module created by @yc9959 works very well letting you choose from four options to fine tweak your cpu. Install should be through magisk.
【Preset Performance Mode】
Caton powersave: Large performance limit, suitable for users who do not require high fluency
Balanced balance: Moderate performance limit, suitable for daily mobile phone
Power consumption performance: approximately equal to no performance limit, suitable for tablet daily life
Extremely fast: similar to the cost of electricity, with continuous performance output, suitable for mobile gaming
【Sub-module description】
SfAnalysis: Recommended, reduces dropped frames at the cost of lower power consumption
SsAnalysis: optional, try it if you experience dropped frames in desktop animations
GitHub Link to download:
Releases · yc9559/uperf
Userspace performance controller for android. Contribute to yc9559/uperf development by creating an account on GitHub.
github.com
Instructions: [1] Open BL
[2] Install Module
[3] Enjoy.
Greetings to the Devs.
Does anyone try it?
Waiting for feedback before I try
I downloaded and installed it but the presets commands are not well explained, I'm trying to understand
fpsRevoltz said:
I downloaded and installed it but the presets commands are not well explained, I'm trying to understand
Click to expand...
Click to collapse
I come back here to say that I found it, I had to open the .json to find it, since the creator doesn't say..
The presets are:
Balance
Powersave
Performance
Fast
You can change the values too, inside .json
anyone used this? does it really work?
Hi, just recently upgraded my S21U to S23U, one setting that was on S21U seems missing from S23U it was called processing speed and could be set to optimised, high or max.
Is this an option that's just not in this new phone, or not needed etc?
Regards
James
In battery you can choose light mode instead. So on stock you have performance and with the light mode (not theme) you can downclock the SoC a bit to save some battery.
You have a setting in the battery section that lower the speed of the processor if you want to save some battery, that's the only thing I've seen so far that meets your request.
MOD EDIT: No placeholder allowed and the major content of this post saying "S7"?
OP, please take some time to edit your forwarded post in a proper format. Thanks.
The T800 travels from the FUTURE to bring YOU the POWER AND BATTERY of a Galaxy S10+ to your beloved S7, while fighting obsolescence...
Version III features:
° 14 hours of battery life sustained with OneUI 5.1 (STOCK kernel)
+ 14 hours of SOT
° About twice or more the speed with no Lag por shutter
° Vídeo about how to apply UV properly and recommended ROM and kernel and many extras (Such as GPU Turbo and FPS screen uncap) ( In s23U don't needed! All of that in only 14 hours! And for free!!
This revolutionary CREATION of mine will give you the SAME (not shame) optimization as Apple do with it's phones (Tremendous battery life and smoothness) But with two or three times the amount of ram, better screens twice the cores, battery ,etc. So:
HERE IS THE AWESOME SPEED YOU CAN SPECT Before/After:
AND HERE IS A BENCHMARK WHERE YOU CAN SEE TEMPERATURES OF 20 OR MORE DEGREES LESS THAN STOCK ROM, WHILE SAVING BATTERY Classic s7 results.
"65% of charge in 30 minutes full charge achieved in less than a hour..." With Aosp only
Q: Why does the manufactures do this bad on stock on purpose?
Two things, MARKETING and PROGRAMMED OBSOLESCENCE which lead them to even put 10 core when a Apple device with two high power cores (Iphone 7 plus) eats it (Mediatek 10 core setup)
Q: What kind of results will i experiment?
With LATEST LINEAGE 16 + Morokernel + this AWESOME PROFILE and with a non-degraded battery you will experience the performance of a Samsung Galaxy S10 with the battery life (and also charging speed, if you have a QC 3.0 charger... of the Latest huawei/honor phones (8 hours SOT, 65% in 30 min) feeling the ui completely lag free, the apps opens right at the moment, and scrolling is like butter. Also runs very very well like a SD 855
IN S23U and, from that, ALL S23 LINE YOU CAN SPECT MUCH BETTER RESULTS!
So i upload you the profile, you will need the following: *Updated S23*
1: Root and follow the guide as close as the video on S7, disable two cores (7/8) and put the freqs as close as the video, you can even CUSTOMIZE it If you want. B throut the best results, following the Guide. You can use Mtweaks or Kernel auditor.
And If you want throw some benchmarks for cpu/gpu temp and SOT feel free to TEST.
Morokernel installed
Mtweaks latest
Download the latest LAG_TERMINATOR™
Open Mtweaks menu and select "profiles" then import the latest "LAG_TERMINATOR™" profile of mine.
APPLY THIS SETTINGS ON BOOT AND YOU ARE DONE. Vídeo settings:
You have to apply this settings on Mtweaks to Morokernel and you are Done. You can also flash the attached zip's to uncap 60fps in all the system animations and GPU turbo for more gaming/phone normal use performance.
1Morokernel and mtweaks download (all in 1 flashable zip) (Works on aosp and TW roms) https://androidfilehost.com/?w=files&flid=295574
2DOWNLOAD NOW THIS AWESOMENESS:
https://www.mediafire.com/file/k964wlh4c4qz5ol/LAG_TERMINATOR™.json ***SEE THE ABOVE YOUTUBE VIDEO AND APPLY THE SAME SETTINGS AND LATTER YOU WILL ENJOY THIS.[/COLOR]
Disclaimer: You don't have the right to post my content in any site without my explicit permission[/U].
Note: If you want me to buy some toys/good sweets to my dear cat you can always donate some money to my paypal: MOD EDIT: donation link removed. Thank you
Hi! touching my phone and having common sense let me know that the Exynos GPU and the low power cores/high power cores have a little nonsense regarding to STOCK thermal and CPU/GPU freq/usage, so, i change between low power cores to high power cores at 50% it's minimum frequences and let the system to use ONLY the high power cores, heavy underclocked, since our phone have thermal copper plate to avoid high temperatures there should be no problem.
But the MORE INTERESTING part of it, it's that this Exynos allows to underclock a LOT among other things, except the GPU which doesn't go really well with underclocking so, when i do this mod, i was able to boost the overall system performance (daily use) like our S7 Exynos is like two or three generations after it regarding to performance! While turning on only hardcore CPU's and not the EIGHT OF THEM the phone not only runs wayyy better, but also runs VERY stable and cold, even better than stock.
Regarding battery life, the overall pack which you only have to import through "Morotweaks" you not only have a lot more benefits regarding low power consumption, but, when you use the powerfull cores ONLY at higher frequency, the Exynos is able to deep sleep more often than before... Regarding additional benefits into the battery life/heat area.
This looks amazing, but where are the download links? Also, will I void my warranty if I use this kernel?
Uhm this look sus
does anyone know how to install? I don't quite understand how to do it
ULTRA90 said:
does anyone know how to install? I don't quite understand how to do it
All the descriptions are claimed for the S7 exynos, so look very sus
Click to expand...
Click to collapse
@Therazorsedge OP, please take some time to edit your forwarded post in a proper format.
Contact me to unlock this thread after all is done. Thanks.