[Post your benchmark] Simple Antutu video (N7 2013 vs N5 vs Moto G vs Xperia S) - Android General

Hello guys,
Here is a simple video to show benchmark scores in Antutu between four devices:
- Nexus 7 2013: CleanROM 3.5 (Kitkat 4.4.4), ElementalX kernel
- Moto G Gpe: Stock rooted 4.4.2 Google play edition, stock kernel
- Xperia S: Stock 4.1.2, stock kernel
- Nexus 5: Stock 4.4.3, stock kernel
Link: http://www.youtube.com/watch?v=e8Q7PORuxi0
Thanks for watching !

Cool video, well made!!
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)

n01z said:
Cool video, well made!!
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
Click to expand...
Click to collapse
Well thank you !
Nice score :good:

lulu14150 said:
Well thank you !
Nice score :good:
Click to expand...
Click to collapse
Thanks, right back atcha!! I think I'm the first S5 to break 42K, if I combined all of my best individual catagory scores, I would break 44K.. Got some work to do, got a bunch of tweaks lined up that I haven't tested yet, I think I'm gonna wait for some others to catch up.. or until I get bored again!!
---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------
The settings that I use on my overclock (OC) are borderline stupid dangerous. And the settings I use to bench are straight up dangerous. For this reason, I will not be sharing them.
HOWEVER, You can find my non-overclocked faux settings here:
https://plus.google.com/app/basic/stream/z13tu3aq0krxchnnv234jdkbrnzrvlpcq
These settings scored 38256, no OC, AEL Kernel controlled by fauxclock.
Note: What we are doing here can result in you frying your snartphone- not worth it just to get a ranking.
For me, I just can't help but to experiment and push my device to it's limits. HOWEVER, my benchmark settings differ from my daily use settings, slightly (for stability) because I love my S5 and would possibly cry if we were to have to part!!
I'm going to share some of my best benching tips (no "tricks" just my observations)
1. Make sure that your Kernel control app has a boot delay of at least 20 seconds. (Mine is at 30 seconds, remember-patience is a vitrue!!)
2. Completely dim your screen, put your phone into airplane mode, disable any motion gestures.
3. Turn phone off for 5 min.
4. Boot your phone, but don't touch it, just let the lockscreen time out, wait 2 minutes, unlock the phone and let it sit for another minute.
5. Do not flip screens or pull the notification bar (we want to NOT trigger any background processes, so turn off any motion gestures- because they are using the CPU while monitoring your sensors and be sure to leave your default homescreen free of widgets).
6. Open Antutu, wait about 30 sec..
7. Click Test Again then uncheck Optimize Memory (your ROM should already have optimized memory and I assure you thay Antutu doesn't know your device better than the OEM or Custom ROM devs) Now, wait about a minute and a half..
8. Click TEST then don't touch/move your phone until it's done..
More Notes:
Make sure that you only ever change one parameter at a time and be sure to run a CPU Monitor when you do, to see the affects of each change..
Reboot inbetween every bench and turn your screen brightness to MIN before you reboot to bench..
Also, I recommend to try running a CPU Monitor once or twice while you run a bench in antutu so you can get an idea of how long it takes for antutu's CPU use to chill out, (same can be done after boot to find out what your device likes, since I've never had any samsung bloat- as I rooted and flashed custom ROMS and Kernels the first day I got my S5- I literally have no experience with Stock)..
Also, running a CPU Monitor when you are getting low benches will help you see if it's being thermal throttled during a bench (throttling has caused me to score as low as 32K) and it will give you the best idea of what may be going wrong and where.
I actually know very little about Kernels, I am just patient, never give up and trial and error sweetspots until I get what I want..
Extra Note: Sweetspots vary from each individual device, so ya just gotta keep at it!!
P.S. These tips should work/help with any benching app.
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)

n01z said:
Thanks, right back atcha!! I think I'm the first S5 to break 42K, if I combined all of my best individual catagory scores, I would break 44K.. Got some work to do, got a bunch of tweaks lined up that I haven't tested yet, I think I'm gonna wait for some others to catch up.. or until I get bored again!!
---------- Post added at 07:11 PM ---------- Previous post was at 07:04 PM ----------
The settings that I use on my overclock (OC) are borderline stupid dangerous. And the settings I use to bench are straight up dangerous. For this reason, I will not be sharing them.
HOWEVER, You can find my non-overclocked faux settings here:
https://plus.google.com/app/basic/stream/z13tu3aq0krxchnnv234jdkbrnzrvlpcq
These settings scored 38256, no OC, AEL Kernel controlled by fauxclock.
Note: What we are doing here can result in you frying your snartphone- not worth it just to get a ranking.
For me, I just can't help but to experiment and push my device to it's limits. HOWEVER, my benchmark settings differ from my daily use settings, slightly (for stability) because I love my S5 and would possibly cry if we were to have to part!!
I'm going to share some of my best benching tips (no "tricks" just my observations)
1. Make sure that your Kernel control app has a boot delay of at least 20 seconds. (Mine is at 30 seconds, remember-patience is a vitrue!!)
2. Completely dim your screen, put your phone into airplane mode, disable any motion gestures.
3. Turn phone off for 5 min.
4. Boot your phone, but don't touch it, just let the lockscreen time out, wait 2 minutes, unlock the phone and let it sit for another minute.
5. Do not flip screens or pull the notification bar (we want to NOT trigger any background processes, so turn off any motion gestures- because they are using the CPU while monitoring your sensors and be sure to leave your default homescreen free of widgets).
6. Open Antutu, wait about 30 sec..
7. Click Test Again then uncheck Optimize Memory (your ROM should already have optimized memory and I assure you thay Antutu doesn't know your device better than the OEM or Custom ROM devs) Now, wait about a minute and a half..
8. Click TEST then don't touch/move your phone until it's done..
More Notes:
Make sure that you only ever change one parameter at a time and be sure to run a CPU Monitor when you do, to see the affects of each change..
Reboot inbetween every bench and turn your screen brightness to MIN before you reboot to bench..
Also, I recommend to try running a CPU Monitor once or twice while you run a bench in antutu so you can get an idea of how long it takes for antutu's CPU use to chill out, (same can be done after boot to find out what your device likes, since I've never had any samsung bloat- as I rooted and flashed custom ROMS and Kernels the first day I got my S5- I literally have no experience with Stock)..
Also, running a CPU Monitor when you are getting low benches will help you see if it's being thermal throttled during a bench (throttling has caused me to score as low as 32K) and it will give you the best idea of what may be going wrong and where.
I actually know very little about Kernels, I am just patient, never give up and trial and error sweetspots until I get what I want..
Extra Note: Sweetspots vary from each individual device, so ya just gotta keep at it!!
P.S. These tips should work/help with any benching app.
SM-G900F
Alliance ROM
KT Kernel OC to 2.89Ghz
Antutu: 42672 (#2 overall)
Click to expand...
Click to collapse
Thank you for sharing your configuration !
My Nexus 7 2013 configuration:
- ElementalX Kernel (1,7GHz CPU, 490MHz GPU and a small undervolt --> Perferct for daily use)
- Rom CleanROM (just with Forced GPU 2D rendering in Developer Options)
Score between 26k and 27k

Related

[WIP] [7/7] Higher framerate on Novatek panels | Kernel inside | Now for Froyo!

*** THIS IS EXPERIMENTAL ***
Thanks to toastcfh, maejrep, AssassinsLament, Estimated Prophet, Cicatrize, joeykrim, geyes30, kpkimmel and all the others from the kernel & display cap threads who have been working tirelessly, and continue to do so. This isn't over until we can find the real cap! But I think this avenue has progressed enough for it to have its own thread, if only to give hope, since we now know both Epson and Novatek panels physically can do it!
What Doesn't Work
Nothing. Now based on the official kernel with everything working.
About This Kernel
This is just a dirty hack. We haven't yet figured out where the real cap in framerate is coming from. But until we do, this is the best we have. At least it shows the display itself can handle a higher framerate and isn't physically incapable like HTC would have us believe.
Novatek panels can now get up to 46fps pretty reliably. Run fps2d a few times.
Stdev depends on system activity. If you're going to be judging stdev, DON'T measure it immediately after booting, set your CPU throttle mode to "performance", be sure to run fps2d several times, then average those stdev numbers in your head.
The changes are now immediately applied upon boot. There is no need to cycle your display anymore.
This kernel has support for overclocking/underclocking, up to 1.119 MHz. Also includes my own undervolting and overvolting for higher speeds to increase stability.
You can get dramatically tighter stdev numbers by setting your CPU governor to "performance" in SetCPU. It seems scaling really messes with the framerate. Obviously this will drain your battery faster, as your CPU will constantly be running at full speed. Set it back to "ondemand" if you don't need it.
Some people are reporting their touchscreen grounding issues have been cured.
Support to change the T2 value on the fly [thanks to maejrep]
Support for 5 simultaneous touch points! Use Dotty (in the Market) to see it in action. It'd be cool if someone would make a simple app to demonstrate what can be done with more than the mere 2 points we are used to. People have suggested new lock types, security locks, ways to rotate things, etc. [thanks to maejrep]
Some hardware fails to accept 5 points, so a fail-safe has been added to default back to 2 points for some EVOs
AssassinsLament has created an awesome app to provide an easy way for people to change their T2 timing. Check out his app here: http://forum.xda-developers.com/showthread.php?t=716659 [thanks to AssassinsLament]
Changes to display timings are now sticky until rebooted (w/ the above app, or set manually)
What's New
v5.1.1: Using the official kernel. We've lost some fps, but we've gained camera, video, 4G, etc. 46fps is now average.
v5.1.1: Expanded user-modifiable timing settings. Change at your own risk.
v5.1.1: Audio patched [thanks Geniusdog254 and KERKEDAGAIN]
Instructions
Do a nandroid backup, and flash this over pretty much any ROM. If you have problems, you can just flash a stock boot.img again. There should never be any need to wipe anything.
IMPORTANT: This will only work with the stock bcm4329.ko! Using the newer files and flashing this kernel will result in wifi being unable to start, and vice versa. To correct this, you'll need to flash over the correct wifi files.
Changing Timing Settings
You can use the following commands from adb shell to temporarily change timing on the fly. Do it while your screen is on.
Set: echo NUMBER > /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Check: cat /sys/devices/platform/mddi_c_b9f6_5582.1/PARAMETER
Parameters:
t2 - 245 to 1023 [Default Eclair: 437, Froyo: 432]
t3 - 0 to 7 [Default Eclair: 1, Froyo: 0]
fte - 0 to 879 [Default Eclair: 35, Froyo: 60] (Frame Tearing Effect, change this if you have tearing problems)​
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.1 (Eclair) ROMs
Flashable ZIP - Undervolted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Flashable ZIP - Normal-volted kernel v5.1.1 for use with 2.2 (Froyo) ROMs
Note: Certain things like the camera still don't work, since our Froyo ROMs aren't official.
Flashable ZIP - WiFi-N + 4G for all custom kernels based on toastcfh's GoDmOdE kernel (compatible with v5.2+)
Flashable ZIP - WiFi-N + 4G for stock/custom kernels (compatible with v5.1 and below)
Flashable ZIP - WiFi-N + 4G for the OTA kernel (NOT compatible with the kernel in this post)
*** REMEMBER! No one here is responsible if you damage your phone! ***​
See the Evo, Droid X and Nexus One benchmarked together here: http://androidspin.com/2010/06/25/droid-x-vs-htc-evo-vs-google-nexus-one-in-benchmark-face-off
Want NenaMark1? It usually doesn't show in the Market, so get it here: http://nena.se/downloads.html
Awesome, just flashed and it is soo smooth, thank you devs.
This works great for me.
Not really related to this but my phone locks up when I change the cpu frequency with setcpu. EDIT: (How do I overvolt the phone?)
Oh and yes I do get 50hz.
Is there 2.2 support or no
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Nope I wish there was. Droid X skin + 50hz would be very cool.
ttieder said:
Is there 2.2 support or no
Click to expand...
Click to collapse
Second this question..I'm loving the EvolutionX froyo rom and would be sweet to get this baby on board with froyo.
Does this work for Epson panels too?
This works great. Touchscreen SEEMS a bit more responsive in in multitouch vis test. Grounding issue is nowhere near as bad, but still there. If you pull the same trick that everyone is doing to test grounding problem, you won't notice it at first, and very rarely will it stop sensing you finger all together, but it definitely does cut out for an instant every now and then, and I had it drop visibility where it normally does a few times for a split second.
Epic delete
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Can you zip your modified files and post them too? Source would be nice
sweteg said:
As this is a development thread, please don't start posting your results like the Godmode thread. It will only clutter the thread.
Click to expand...
Click to collapse
This thread was made to avoid the clutter from the Godmode thread.
Thanks for the excellent dev work!
You might want to add to the first post that this kernel breaks 4G. it will turn on but not able to find any network.
Other than that, works as described
The device feels so much smoother!
Great work! I get 52 in fps2d, 680 in quadrant, and 51 in gears. I can't wait until this is completely fixed but I'm loving it and the undervolt and oc patches are awesome additions.
automatic brightness still does not work with this kernel though. At least not for me. Is it possible I have a different light sensor as no custom kernel has worked with auto brightness yet and other reports say it works just fine.
Also... fps2d spikes into 99 fps and at one point I watched it flash past 100
Definetly works
Installed the kernel and got over 50 fps on my nova panel i have hardware config 002 it runs much much smoother thanks devs for the hard work.
wow this kernel is insane, I mean FPS hack and overclock hack without force closes...wow is all I can say. Used the OC widget and it detects the oc clocks quickly.
Man if this kernel makes it to Froyo..Evo will be truly evil
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Mrtankjump said:
2 vertical lines just showed up on the right side of the screen, haven't tried anything yet, let me restart and see if it goes back, then try to duplicate the issue.
Edit: It went away after I got a text, not sure if it was coincidence or not. I'm guessing this is the tearing issue that the FPS fix causes, but nothing about it was written in OP.
Click to expand...
Click to collapse
My Evo has an Epson panel so I can't use this fix but, my understanding was that this method didn't cause the tearing like we saw from Toast's custom kernel on Epson displays, so your problem might be something else and not necessarily the fps cap being raised.
Thanks for the kernel, but I still have one big problem- my battery still will not charge with this kernel installed. It will only charge when I turn off the EVO and turn it back on. But as soon as I unplug and replug it in, it will look like it charges for 5 seconds, then the orange light shuts off and it stops charging. I've enclosed a dump of my dmesg. Can someone please take a look at this?

[MOD][Updated 6.2.12]Dual Core Mod v2.1 - Screen Profiles, Auto Tweak, and more!

Hello everybody, I was asked to bring this mod over from the EVO 4G LTE section and since the One X and One S use the same file I am modifying, both devices will get it This is also untested on the One X and One S, so please let me know if you encounter any issues, but it should work! This will ONLY work on phones with the Qualcomm S4 chipset, not the Tegra chipset!
This is a mod that should give you better performance by forcing cpu1 (second core) to run more, depending on the zip you flash below. The system will handle how it scales and the dcmhelper script will modify some parameters if you choose that zip. Some people on the EVO 3D felt that it gave them better battery life, some didn't. Some thought the performance was much better, some didn't. This is just something else for you guys to play with and see what works best for you Here are the details:
=============== How was this done? ===============​
It was pretty easy, instead of modifying the kernel itself, I just modified /system/etc/init.qcom.post_boot.sh. It already sets extra parameters for the CPU and system shortly after boot. Here are the lines that I added:
Code:
echo 1 > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
What this does is it tells cpu1 to come online and then changes the permissions so user read-only so that it can't be overridden. This will be applied on every boot.
You can also verify this is working by any number of apps, but I find SystemPanel to be the best. They have a free lite version. Just download and tap on the top right where the CPU info is. You will the the CPUs changing, when it goes grey it's offline (which you won't see when using the Dual Core Mod).
aLogcat will also show you everything DCM is doing. Just apply a filter in aLogcat called DCM and it will tell you in detail what is going on.
If you want a little bit less info or want to use adb, just type su and then dcmlog and you will see what the 2nd core is doing exactly. This is updated every 1/4 second for extremely accurate results.
Click to expand...
Click to collapse
=============== Requirements ===============​
Custom recovery
Root access (to write to /system)
Click to expand...
Click to collapse
=============== How to Flash ===============​
Download the mod below and place on your internal_sdcard or sdcard (doesn't matter, just remember where you put it!)
Go into Settings > Power > Fast Boot and uncheck that.
Turn the phone off. Once off, press and hold the Volume Down + Power Button until you reach the white bootloader screen
Choose "RECOVERY" (volume down and up to move, power to select)
Choose "Install" and locate the mod wherever you put it. NOTE: If you don't see it, make sure that either internal_sdcard or sdcard is mounted. This can be done via the "Mount" button at the main menu of TWRP. Be sure that either internal_sdcard or sdcard is checked!
Wait until the install is finished and then tap "Reboot to System"
Click to expand...
Click to collapse
=============== Dual Core Mod v2.1 (flash over any existing version) ===============​Updated dcmhelper
Fixed issues with cpu1 turning off when screen on
Fixed issues with cpu1 turning on when screen off
Added double check for cpu1 off when screen off
Added logging to logcat
Updated init.qcomm.post_boot.sh
Set perms of 444 on hotplug file, regardless of dcmhelper present or not
Other
Added /system/bin/dcmlog (type su then dcmlog from terminal or adb) - Tells you current cpu1 status [0 = off, 1 = on]
=============== Dual Core Mod v2 (flash over v1) ===============​
MANY new options!
Added "Screen Profiles" and "Auto Tweak" script option (all located in one configurable file - /system/bin/dcmhelper) - see 2nd post for more info
Added "Memory Optimization" option - see 2nd post for more info
Support AT&T HTC One X
Support T-Mobile One S
"All-in-One" .zips - all devices supported via 1 .zip file (thanks to a very smart updater-script I wrote )
=============== Dual Core Mod v1 ===============​
Initial release
Click to expand...
Click to collapse
=============== Explanation of Mods===============
All DCMs have memory optimizations!​
Dual Core Mod - Full time cpu1 on
Dual Core Mod Plus - cpu1 on when screen on, cpu1 off when screen off
Dual Core Mod Ultimate - Same as Plus but governor is tweaked for more performance when screen on, more battery life when screen off.
Click to expand...
Click to collapse
=============== Downloads ===============
Dual Core Mod v2.1 Ultimate
Dual Core Mod Back to Stock​
Click to expand...
Click to collapse
=============== Credits ===============​
Freeza for doing this on the EVO 3D where I got the idea from
rohandhruva, remedy1419, and ewalk4866 for EXTENSIVE testing to fix issues and make DCM better
Click to expand...
Click to collapse
It has been asked to make it easier to donate for people using Tapatalk, so here are the links...
Donate to -viperboy-
http://bit.ly/n7sB9g​
More Info​
=============== How are all supported phones in 1 zip per file? ===============​I wrote a custom updater-script that will identify your device and automatically give you the right file needed. Just like magic
Click to expand...
Click to collapse
=============== How can I monitor the 2nd core? ===============​You can also verify this is working by any number of apps, but I find SystemPanel to be the best. They have a free lite version. Just download and tap on the top right where the CPU info is. You will the the CPUs changing, when it goes grey it's offline (which you won't see when using the Dual Core Mod).
aLogcat will also show you everything DCM is doing. Just apply a filter in aLogcat called DCM and it will tell you in detail what is going on.
If you want a little bit less info or want to use adb, just type su and then dcmlog and you will see what the 2nd core is doing exactly. This is updated every 1/4 second for extremely accurate results.
Click to expand...
Click to collapse
=============== What are the "Memory Optimizations?" ===============​The optimizations I made are the same that I have made in viperROM. They are as follows:
echo "0,4,6,8,14,15" > /sys/module/lowmemorykiller/parameters/adj
echo "2560,4096,6144,7680,8704,10240" > /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
This will allow better multitasking and should eliminate any issues with apps being killed off very easily.
Click to expand...
Click to collapse
=============== What are the "Screen Profiles?" ===============​The screen profiles are part of a custom script, located in /system/bin/dcmhelper. Once flashed, this .zip runs in the background to monitor screen state (uses hardly any power). When you choose a .zip with this in it, the phone won't just leave the second core always running - it will turn it off when the screen is off and on when the screen is on. This is done via this code here:
while : ; do
awake=`cat /sys/power/wait_for_fb_wake`
if [ $awake = "awake" ]; then
echo 1 > /sys/devices/system/cpu/cpu1/online
awake=
fi
sleep=`cat /sys/power/wait_for_fb_wake`
if [ $sleep= "sleeping" ]; then
echo 0 > /sys/devices/system/cpu/cpu1/online
sleep=
fi
Click to expand...
Click to collapse
Pretty simple and straightforward
Click to expand...
Click to collapse
=============== What is the "Auto Tweaking Script?" ===============​The auto tweaking script is the second part of a /system/bin/dcmhelper. This part of the script will set certain governor settings based on the screen being off or on. In the viperROM version, the screen on settings are the same as in the ROM. In the other versions, the screen on settings are more set for performance. I intentionally kept the same settings in the viperROM version to make sure you get as close to the same battery life as unmodified viperROM. Here is a code snipit (from the non-viperROM version) that shows what the settings are:
ondemand_sampling_rate_awake=40000
ondemand_up_threshold_awake=80
ondemand_down_differential_awake=12
ondemand_sampling_down_factor_awake=3
ondemand_sampling_rate_sleep=80000
ondemand_up_threshold_sleep=95
ondemand_down_differential_sleep=5
ondemand_sampling_down_factor_sleep=1
Click to expand...
Click to collapse
Long story short, when awake, it will check if the CPU needs to increase speed faster and in bigger steps. When asleep, it will wait longer before polling the CPU to scale up and it will take a more gradual approach to scaling up. However, you shouldn't experience any lockscreen lag.
Click to expand...
Click to collapse
=============== Long Term Goals for Dual Core Mod ===============​
Config file and script for users to set their own settings
Profiles for battery
Set max freq when screen off (will affect virtuous_oc daemon in viperROM, still working on that)
Click to expand...
Click to collapse
Any feedback about theses scripts (the "full one" w ith screen+memory+tweaks) on our lovely One S stock/CM9 ? It seems to be a very good option while waiting the OneS sources!
Good Job, will test it soon
Nice, good job!
Would these mods have any effect on custom roms like Lee Droid's and torxx
snwman said:
Would these mods have any effect on custom roms like Lee Droid's and torxx
Click to expand...
Click to collapse
I took a look at the scripts... It should be compatible with Stock (and derivated ROMs like LeeDroid & so on), as on CM9/AOSP ones. The scripts seems to affect on low-level files (/proc) related to the chipset, so the affected files should be present on both Stock/AOSP ones.
I'm under CM9 for now, but a Stock feedback can confirm this? You?
Thanks to me ;-) Well he came here
EDIT: lol sorry, didn't see it was a flashable zip
So, flashed the ZIP, but cpu1 never comes online... The script disables it permanently? I expected a cpu1-offline under a load factor, and goes online over another load factor.
plakers said:
EDIT: lol sorry, didn't see it was a flashable zip
So, flashed the ZIP, but cpu1 never comes online... The script disables it permanently? I expected a cpu1-offline under a load factor, and goes online over another load factor.
Click to expand...
Click to collapse
The One X guys seem to be having issues as well, it's hit or miss. Of course, I don't have issues in my testing lol what file did you use?
by linpack bench I can say 204 (and up) is stable score now.
in quadro bench:
before cpu score is 8486.
after cpu score is 8732.
so it's working.
Regards !
Thanks very much for this mod, going to try it out right now. Some questions on my part: (1) can this put any long-term additional stress on the cpu by forcing it to work more? (2) If a ROM is updated, does the script need to be flashed again after flashing the ROM? Again, thanks a lot; will try it out now and report my findings on the LeeDroid ROM.
Closed Source Project said:
Thanks very much for this mod, going to try it out right now. Some questions on my part: (1) can this put any long-term additional stress on the cpu by forcing it to work more? (2) If a ROM is updated, does the script need to be flashed again after flashing the ROM? Again, thanks a lot; will try it out now and report my findings on the LeeDroid ROM.
Click to expand...
Click to collapse
No, no added stress and yes, you will likely have to reflash after a ROM update since most ROMs wipe /system where this script is located.
The script installed fine and my ROM booted up nice and fast. I will now do benchmarks and other daily tasks while observing my battery life and report back with my final findings in a few hours. So far seems good.
I am on LeeDroid's latest with the full script installed (tweak scrip+mem opt+screen prof).
How did you come about those minfree values? Do you know offhand how the numbers in your script compare to those used by the minfree manager app (i.e. MFM uses MB, are your numbers in KB?)
My results: Battery seems to be better, yet performance is not so much. Both Quadrant and Antutu benchmarks show slightly lower scores than what I got right before flashing the mod. The difference is very minimal, just curious as to why it would be lacking ever so slightly. The general UI seems just as snappy as before.
Is there an app to view exactly what the CPU is doing and how many cores are running? If so, please share! Thanks.
Closed Source Project said:
My results: Battery seems to be better, yet performance is not so much. Both Quadrant and Antutu benchmarks show slightly lower scores than what I got right before flashing the mod. The difference is very minimal, just curious as to why it would be lacking ever so slightly. The general UI seems just as snappy as before.
Is there an app to view exactly what the CPU is doing and how many cores are running? If so, please share! Thanks.
Click to expand...
Click to collapse
Working with some people in IRC to improve everything. And yes, SystemPanel Lite, as said in the OP
-viperboy- said:
The One X guys seem to be having issues as well, it's hit or miss. Of course, I don't have issues in my testing lol what file did you use?
Click to expand...
Click to collapse
I used the modV2 with CPU/RAM/Tweaks, the full one.
Dual Core Mod v2 w/ Screen Profiles AND Auto Tweaking Script AND Memory Optimizations
And only first core is active ...
plakers said:
I used the modV2 with CPU/RAM/Tweaks, the full one.
Dual Core Mod v2 w/ Screen Profiles AND Auto Tweaking Script AND Memory Optimizations
And only first core is active ...
Click to expand...
Click to collapse
I have a fantastic group of testers, we got this sorted out. Just going over the final small details now, but I will have all new builds up in 30-60 mins confirmed working!
-viperboy- said:
I have a fantastic group of testers, we got this sorted out. Just going over the final small details now, but I will have all new builds up in 30-60 mins confirmed working!
Click to expand...
Click to collapse
Yeahhhh haaaaa!!!
hehe good testers, for good scripts man!
Updated to v2.1! Much, much improved thanks to my 3 great testers rohandhruva, remedy1419, and ewalk4866 for testing numerous builds and spending hours making sure this is as bulletproof as possible. Please see the OP for full changelog. A few other notes about v2.1:
I dropped a few of the versions because there were hardly any downloads on it. The "3 in 1" had literally 10 times the amount of downloads as some of the other versions. Based on this, memory optimizations are included in all builds. The naming scheme has changed as well, info in the OP.
Please use aLogcat if you want to view everything DCM is doing. Just apply a filter in aLogcat called DCM and it will tell you in detail what is going on. If you want a little bit less info or want to use adb, just type su and then dcmlog and you will see what the 2nd core is doing exactly. This is updated every 1/4 second for extremely accurate results.
Battery life should be very good on Ultimate because of the settings I have set. If for some reason you can verify that the mod isn't working by using what I said above, please let me know. I have verified with numerous people that it works, so it could be a minor issue in the flashable .zip. I'm not anticipating any issues, but anything can happen.
Enjoy

[DEV][KERNEL][Overclock] CM10.1 (4.2.2) - 3.1 kernel

To All,
I have Compiled a kernel, compatible with Derartem's CM10.1 (4.2.2). It is actually a clone of DerArtems kernel tree, with overclock additions (some borrowed from Xoom and AC100).
Overclock up to 1400Mhz (1600Mhz is also available in the overclocking list, but crashes hard on my Folio, altough it uses similar speed&voltages as the Xoom) -> Update: works at 1.6Ghz (Folio can't handle the overvolting of the Xoom, but is stable at lower voltage). However.. It does not really benefit from 1.6Ghz in benchmarks (probably due to worse multipliers)
I have also changed parameters of the 3D clocks to become similar to the Xoom overclock, so it might also have overclocked the GPU (but I'm not able to test this)
In V2 I have tried to reclaim some memory. GPU uses 128Mb, but 64Mb won't work in Jelly Bean. The HDMI Framebuffer uses 16Mb, so I have reclaimed this space (result: probably broken HDMI)
->361Mb usable
In V3: LP1 state
In V4: LP2 state seems to work better than LP1 (immediate wake-up, no double click of power button). No SOD on my unit up to 1.4Ghz. Not sure what it will do for battery life in sleep (processor still goes to deep sleep state, so impact might be limited). Also first step made to disable battery alarm.
V1: only OC (1.4Ghz works)
V1 OC boot image
V2: OC up to 1.6Ghz, + some memory remapped
V2 OC+mempatch boot image
V3: OC up to 1.6Ghz, + LP1 sleep
V3 OC+mempatch+LP1 boot image
V4: OC up to 1.6Ghz + LP2 sleep
V4 V4 second download source
V4b: OC up to 1.6Ghz, buth with (standard) LP0 sleep
V4b
V5: OC up to 1.6Ghz, LP0 sleep and some clock cleanups (e.g. removed 216Mhz)
V5
V6: V5 + Workaround for 1.6Ghz SOD
V6 link
V7: V6 + Deadline I/O scheduler (can be enabled in developer mode or your favourite overclock app). Default stays the NOOP scheduler
V7
V8: Try SOD workaround on the MMC
V8 link
Source:
Source
Be careful. I'm not responsible to damages to your Folio. Overclocking might destroy your tablet
(Tough, a burned Folio it is a perfect excuse to buy a new tablet... I can really recommend the Nexus 10 or the Galaxy Note 10.1 )
How to install:
Be sure to have DerArtem's CM10.1 release (only tested with alpha2)
run these commands with fastboot (check forum on how to install this on your PC. Enter fastboot mode on the folio by 3xpower+Volume Up):
Code:
fastboot erase linux
fastboot flash linux boot-ovc.img
Overclock can be enabled in "Instellingen -> Prestaties -> Processor -> Maximale kloksnelheid"
(translated to English this should be something like "Setup -> Performance -> Processor -> Maximum clockspeed")
Don't be too quick to set the overclocking speed at boot until you tested it well.
What to expect?
1000Mhz (no overclock)
Antutu: 8211
Linpack Multithread: 80
3DMark: 1461 (on Par with a stock Xoom)
1400Mhz (max overclock)
Antutu: 11654
Linpack Multithread: 121
3DMark: 1915
Credits:
DerArtem
Nopy
m32
guevor
The Cyanogenmod Team
The other Tegra Dev Teams where we have borrowed code (Adam, GTab, Vega, AC100, Xoom)
EDIT (known issue): Some more SOD issues come up when putting the Folio on standby at high clocks, but it is quite stable during use.
SOD's
Apparently not everyone has SOD's, but for some it is still a problem.
- Many use advanced wifi lock: this works, but keeps the tablet completely on (hight battery usage)
- At 1.6Ghz I also have an SOD (reproducable), but can be worked around with the app "Overclock Widget". Here you can set a max speed of 1600 in use, and 1000 when screen is off. Maybe this is also usable for the SOD at 1000Mhz (set e.g. to 600 when screen is off, overclock kernel is not necessary).
Nice job spicyalan.
Just one question, why OC instructions are in german ? Does this mean that the menu will switch to german or the ui will remain as it is now ?
Onother question, whay did you try to reclaim memory ?
Thanks
miazza said:
Nice job spicyalan.
Just one question, why OC instructions are in german ? Does this mean that the menu will switch to german or the ui will remain as it is now ?
Onother question, whay did you try to reclaim memory ?
Thanks
Click to expand...
Click to collapse
They are in dutch, but you will get them in the language your system is setup.
After compiling and installing the kernel several times, I was just too lazy to set the language of my folio to "english" for explaining
(You also need to set the setup app in developer mode (tapping on the build number numerous times)
One of the problems the folio is slow in 4.2, especially task switching, is the lack of memory (even zram does not solve this).
Out of 512mb:
- 128Mb is reserved for the GPU
- 8Mb for the framebuffer
- 16Mb for the hdmi framebuffer
Setting the gpu memory to 64 works, but fails to accellerate some 3d content (even outside games). This would have worked in gingerbread, but not jelly bean. I couldn't try 96Mb (crash at boot), so it needs to stay at 128. Framebuffer is also a nono, but the framebuffer ram of the hdmi can be reused (if you don't use the hdmi)
For the SOD, more investigation is needed.
No folio ROM was ever free of SODs (not even stock), but some roms have more problems with it than others. For me, gingerbread (7.2?) And the most recent derartem was the most stable in that regard. It is not easy to know where the SODs come from, but with the overclocking, I noticed it is worse at higher overclock. I'm starting to guess it has something to do with the processor going from total sleep to max speed too fast (if you prevent cpu sleep, it also helps the sod, but using a lot of battery during sleep. Some roms did this).
Same with wifi.
I'm going to test a new version of the rom soon (derartem's version, with cm10.1 upstream, and oc kernel), so stay tuned (but be patient...)
Very nice work! Finally an overclocked kernel that can increase a bit performances.
Thank you man
Inviato dal mio folio100 utilizzando Tapatalk
I have put an experiment online with the LP state
According to tegra documentation, there are 3 states:
-LP0: shut down everything, only a few interrups can wake the device
-LP1: shut down a lot, but more things can wakeup the device
-LP2: shut down less.
If I look in the the sources, there are only 2 devboards that use LP0, and the betelgeuse (folio) is one of them. But, as all other boards can only use LP1 (andseeing the exceptionally bad SOD track record of the folio), I would be surprised if the folio as actually able to to this.
I have places a version online that uses LP1 state, that I will test (but as I don't have the problem as often, it could be nice if others could also test to confirm if it is better or not). I was not able to have an SOD today on a clock lower than 1.2Ghz.
I did experience sometimes that I have to push twice on the power button to wake it up (reminds me of CM7.2)
next to that, I also suspect the wifi driver of some SOD'in (especially in higher overclock mode). It shouldn't actually shut down in sleep mode....
Hello,
I was on the way to try V3: OC up to 1.6Ghz, + LP1 sleep but the lik seems dead...
Can you check ?
Thanks
PS: V1 works great
miazza said:
Hello,
I was on the way to try V3: OC up to 1.6Ghz, + LP1 sleep but the lik seems dead...
Can you check ?
Thanks
PS: V1 works great
Click to expand...
Click to collapse
Sorry,
Typo in the filename.
I think the lp1 sleep might nog be the answer to the sod (which is worse on higher clocks). But worth a try.
Probably the wifi driver is te cause (wifi lock is the only thing that keeps sod away at high clocks). At 1000mhz, my folio has no sod.
spicyalan said:
At 1000mhz, my folio has no sod.
Click to expand...
Click to collapse
This is really something struggleing me. I have SOD:
- every boot is I do forget to unlock my profile before of sleep (I have two profiles)
- almost every time i put the tablet in std-by
what a strange behaviour and difference...
miazza said:
This is really something struggleing me. I have SOD:
- every boot is I do forget to unlock my profile before of sleep (I have two profiles)
- almost every time i put the tablet in std-by
what a strange behaviour and difference...
Click to expand...
Click to collapse
the same is here - any action with screensaver ends with reboot
branch android-tegra-nv-3.1 i my case is stabler - i'v no sods than rel-15r7
m32 said:
the same is here - any action with screensaver ends with reboot
branch android-tegra-nv-3.1 i my case is stabler - i'v no sods than rel-15r7
Click to expand...
Click to collapse
I have compared both tree's, and it seems rel-15r7 is +500 patches ahead, but also 136 behind. Most changes are now useless (e.g. many refer to the old partition system), but I have found a few wifi and SOD fixes in there not present in rel15r7. But they need to be hand-picked and checked.
For me this ROM update-cm-9.0.0-RC0-2012.03.04-betelgeuse-KANG-signed have NO SOD.
Sometimes have a problem with WiFi connection, but when you clear all saved and then connect again, then have no problem.
Cantdownload de kernels.. it shows only another page with te text.
Or may i have to copy the text?
spicyalan said:
I have compared both tree's, and it seems rel-15r7 is +500 patches ahead, but also 136 behind. Most changes are now useless (e.g. many refer to the old partition system), but I have found a few wifi and SOD fixes in there not present in rel15r7. But they need to be hand-picked and checked.
Click to expand...
Click to collapse
Waiting for you to make the miracle...
miazza said:
Waiting for you to make the miracle...
Click to expand...
Click to collapse
No luck yet...
Most of the patches conflict, and the few others result in an unbootable kernel...
I'm not an experienced kernel developer, so I'm kind of flying blind (and using the trial and error method)
My folio doesn't show sod's that often in cm 10.1 (maybe once every 2 weeks), but is do have them at 1400mhz and up. The only thing keeping them away at this speed is advanced wifi lock.
I'm going to move the file hosting to goo.im soon (the files seem to download fine in firefox on windows, but in the default android browser, I also get a .txt.... weird)
spicyalan said:
No luck yet...
Most of the patches conflict, and the few others result in an unbootable kernel...
I'm not an experienced kernel developer, so I'm kind of flying blind (and using the trial and error method)
My folio doesn't show sod's that often in cm 10.1 (maybe once every 2 weeks), but is do have them at 1400mhz and up. The only thing keeping them away at this speed is advanced wifi lock.
I'm going to move the file hosting to goo.im soon (the files seem to download fine in firefox on windows, but in the default android browser, I also get a .txt.... weird)
Click to expand...
Click to collapse
U have to much free time ?
Cant follow U I'm like U not so expirenced in linux kernel drivers building, perhaps we can share our/ouus findings with nopy and artem ?
My folio works few days without sod - but it weakups time to time when battery goes too low - as i'm in home, i can see it - screen blinks for few seconds, derartem has ported drivers from 2.6 to 3.1. In my opinion it's worth to wait for him.
m32 said:
U have to much free time ?
Cant follow U I'm like U not so expirenced in linux kernel drivers building, perhaps we can share our/ouus findings with nopy and artem ?
My folio works few days without sod - but it weakups time to time when battery goes too low - as i'm in home, i can see it - screen blinks for few seconds, derartem has ported drivers from 2.6 to 3.1. In my opinion it's worth to wait for him.
Click to expand...
Click to collapse
Not too much time... but sometimes I have
Waking up on low battery is still normal (many phones do it), but it shouldn't sod, nor should it wake up at random
Did anyone have contact with nopy or derartem these last months?
miazza said:
Waiting for you to make the miracle...
Click to expand...
Click to collapse
New tryout online
This time with LP2, and some clock fixes. no SOD on my unit up to 1400Mhz (still at 1600).
At 1600Mhz, I just benchmarked sunspiper in Chrome: 982ms. There is now 1 benchmark making this Folio faster than a stock Galaxy Note 10.1 (2012) -> Actually, just proves that javascript is quite single threaded
spicyalan said:
New tryout online
This time with LP2, and some clock fixes. no SOD on my unit up to 1400Mhz (still at 1600).
At 1600Mhz, I just benchmarked sunspiper in Chrome: 982ms. There is now 1 benchmark making this Folio faster than a stock Galaxy Note 10.1 (2012) -> Actually, just proves that javascript is quite single threaded
Click to expand...
Click to collapse
v4 just hangs on cm splash
m32 said:
v4 just hangs on cm splash
Click to expand...
Click to collapse
Weird... Is the size correct ? (maybe something happened in the download)
EDIT: I have added a new download source... Hosting at goo.im is stll not working
EDIT2: found a trick to work around the 1.6Ghz SOD (see 1st post), might give a clue for other SOD's?
According to kernel code, the CPU is set to max speed when resuming (max speed during board initialization might be a bad idea). I think this should be throttled (e.g. 600Mhz) until the screen is on. This can be simulated with overclock widget and its "screen off clockspeed profile".
Again something to test for someone with SOD's
I'm right now testing v4 at 1600. It looks stable. Nice job.
Edit: when the tablet goes to sleep with the blinking led I cannot wake it up. I need to maintain wakelock at 5.
Sent from Folio 100 using tapatalk

[JFLTEXX] Need help in choosing rom

Hello guys!
I would like to ask you for opinion what is best ROM for you. I recently rooted my I9505 and installed CM 12.1 but I want to check another viable ROMs, but there are SO many ones in android development section
Since I love to play many games on my phone, Im looking for a rom that is categorized in order by:
- Maximum performance and fps stability
- System stability (yes it is at second place )
- Battery usage (Im using greenify)
- Features
Im open to any suggestions. In few days these is some free time for testing ROMs
Optimized CM13 or AOSP 6 by JDC Team. In Stweaks app, select the extreme performance profile. Antutu scores over 35000 while other roms score around 32000.
Yet for gaming, I believe 5.1.1 is better, JDC Team made those as well.
^ what he/she said.
When it comes to performance, JDCTeam roms are best, due to the included alucard kernel.
Switch to the extreme performance profile and you're good to go. Note that not all settings take effect after applying the profile, so you may need to reboot.
You will also get good up time, because the kernel automaitically switches to a low power mode when the screen is off.
But when it is in use you will get about 2 hours SOT.
With extreme battery you may get around 4-5 hours SOT.
The stock cm kernel, that comes with pretty much every rom, is ok and all for everyday usage, but when it comes to performance it kinda sucks compared to custom kernels.
@GDReaper Paradoxically, on CM 12.1 with performance battery profile (in notifcation bar) I get AnTuTu score near 38k. However, when I tested JDCTeam optimized CM 12.1 and changed to performance battery mode in notification bar, I got at least 30k score (however I haven't modified kernel via STweaks yet). Maybe I should give it a try .
By the way, is Alucard custom kernel contains fast charging feature? I wanted to test it as well
That battery mode from CM only changes the CPU governor to Performance.
Alucard kernel changes many different settings depending on the kernel profile.
Also, the S4 does not have fast-charge built-in. Only the newer phones have that feature.
Then I don't know why standard CM rom gave me so high score.
However I will test again Optimized CM 12.1 and reply back tomorrow (making backup and so on)
Optimized CM13 by JDC Team is the best in my opinion.
I would go for stock based one like lollirom v8
best stability, no lag over time...
Thank you all for answers
Checked Optimized CM 12.1 and changing profile in STweaks to extreme performance really gives huge boost (over 38k score) as well as extreme battery cuts its performance when battery is more important (under 30k score).
The only cons is that changing between profiles takes about 20-30 seconds but it doesn't bother me so much
EDIT: I read that when you install Lollirom v8 you have to change modem to HPA1 to make WiFi work properly. Is that really needed?
Im not convinced to modify anything other than system. Is it possible to backup my modem easily so I can restore it if something goes wrong?
I will be doing the same as you!! Ive been using Golden Eye for quite some time now, but am ready for something new
KonowaL said:
Thank you all for answers
Checked Optimized CM 12.1 and changing profile in STweaks to extreme performance really gives huge boost (over 38k score) as well as extreme battery cuts its performance when battery is more important (under 30k score).
The only cons is that changing between profiles takes about 20-30 seconds but it doesn't bother me so much
EDIT: I read that when you install Lollirom v8 you have to change modem to HPA1 to make WiFi work properly. Is that really needed?
Im not convinced to modify anything other than system. Is it possible to backup my modem easily so I can restore it if something goes wrong?
Click to expand...
Click to collapse
You can use a custom kernel to avoid the WiFi issue.
I don't know if there is any way to backup the modem, but changing the modem isn't hard either.
Lollirom will not change your modem, only official stock roms can change your modem.

Disable 2 cores for the s810

Considering the fact that every s810 phone out there has over heating issues apart from the one plus 2 because time was actually spent on that phone would it be possible to disable 2 or even 1 core(s) on the s810 to get rid of the heating issues or can that only be done by Sony. You must think i am stupid but hey oh i am just uncomfortable with all the heat i don't mind a bit of performance loss when i know my phone does not feel like its being barbecued.
https://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879
I use this work from rytekk on mm and nougat it is flawless, you have control over cores annytime above 30% battery, if below then z5 takes over...
Oh... Stock roms tested ?
stipi69 said:
https://forum.xda-developers.com/xperia-z5/general/tweak-improve-performance-reduce-t3387879
I use this work from rytekk on mm and nougat it is flawless, you have control over cores annytime above 30% battery, if below then z5 takes over...
Oh... Stock roms tested ?
Click to expand...
Click to collapse
Thx for the reply but could you possibly elaborate further what do you mean because I have installed this before in the sense it would make it faster but not disable 2 cores or under preforming like just tell me what I have to do with this so I can underclock / disable 2 cores
Quantumkk123 said:
Thx for the reply but could you possibly elaborate further what do you mean because I have installed this before in the sense it would make it faster but not disable 2 cores or under preforming like just tell me what I have to do with this so I can underclock / disable 2 cores
Click to expand...
Click to collapse
I dont know the whole science about thos but i folowed the manual, pushed these file in correct folders and rebooted... I use kernel aduitor, app that alpows me to disable or enable cores as i choose ( except if phone is thermal throttling or battery below 30%) now i go to workf iy dou don't do it till evening i can at least telly you how i did it step by step...
stipi69 said:
I dont know the whole science about thos but i folowed the manual, pushed these file in correct folders and rebooted... I use kernel aduitor, app that alpows me to disable or enable cores as i choose ( except if phone is thermal throttling or battery below 30%) now i go to workf iy dou don't do it till evening i can at least telly you how i did it step by step...
Click to expand...
Click to collapse
Oh ok makes more sense so lemme get this straight copy the filez to system etc then reboot. Then go onto kernel auditor and turn off cores of my choice as it's enabled them?
Ok i have those files renamed and ready at my dropbox, just copy them in /system/etc
Make sure to backup original files...
https://www.dropbox.com/sh/ue4bbik61aair9u/AADLznjHZzmExXbiSnZ_iTkra?dl=0
Now reboot
And if you want total control rename thermal-engine.config to:
thermal-engine.configdisabled
Reboot
Now you have control over cores, again if battery above 30% or ifphone is not thermal throttling
It allso takes some knowing in kernel aduitor if you wish i can screenshot my settings
I allso sugest some good cpu governors tp make the mpst of it, you have some in androplus kernels for marshmallowi think, not sure for nougat, and you can allso add then manualy
stipi69 said:
Ok i have those files renamed and ready at my dropbox, just copy them in /system/etc
Make sure to backup original files...
https://www.dropbox.com/sh/ue4bbik61aair9u/AADLznjHZzmExXbiSnZ_iTkra?dl=0
Now reboot
And if you want total control rename thermal-engine.config to:
thermal-engine.configdisabled
Reboot
Now you have control over cores, again if battery above 30% or ifphone is not thermal throttling
It allso takes some knowing in kernel aduitor if you wish i can screenshot my settings
I allso sugest some good cpu governors tp make the mpst of it, you have some in androplus kernels for marshmallowi think, not sure for nougat, and you can allso add then manualy
Click to expand...
Click to collapse
yh thanks would be appreciated to see your settings but i copied the files from the post i will try yours now but the one from the post gave me no control over kernel auditor, however a friend told me it can be done via kernel and odex..? if you know this way please explain if not i will try the configdisabled thing and see if that works thanks again
Still getting a really hot phone
Sory to hear that, i guess it comes up to all factors than annyone can forsee... Best i could do with those files and with greenify was super cool phone almost no drainage, but when working ( if so choosen) it was a performer and yes... Scorched hot
If you wish to have good nougat rom flash xz2 rom from xnoob, leave /system/etc as is, change nothing i am amazed how cool it runs and how great it performs... Battery life best till now for me, But do a clean install,
An easy way to reduce heat is to adjust hotplugging thresholds for the big cores (you'll need root of course). You can do that easily through Kernel Adiutor in the CPU Hotplug settings. Lower the "minimum cpus big" and raise the "busy up threshold". If you really don't want your big cores on just set busy up threshold to 100 or something.
I personally have mine set to 0 minimum and 87 busy up threshold. You'll need to make an extra adjustment to get 0 minimum big cpus to stick, otherwise it will revert back to the default of 1. (note: I'm on the latest stock rom)
Also, setting your cpu governors to interactive and fine tuning the parameters will further reduce heat.
Thx for that I am using the xz2 Rom lol could you send me a pic of the kernel auditor settings?
Quantumkk123 said:
Thx for that I am using the xz2 Rom lol could you send me a pic of the kernel auditor settings?
Click to expand...
Click to collapse
Sure
crono9977 said:
Sure
Click to expand...
Click to collapse
Thx for the pic but I can't seem to find the core control option lol please tell me how you go there and also cool nav bar
stipi69 said:
Sory to hear that, i guess it comes up to all factors than annyone can forsee... Best i could do with those files and with greenify was super cool phone almost no drainage, but when working ( if so choosen) it was a performer and yes... Scorched hot
If you wish to have good nougat rom flash xz2 rom from xnoob, leave /system/etc as is, change nothing i am amazed how cool it runs and how great it performs... Battery life best till now for me, But do a clean install,
Click to expand...
Click to collapse
Yh lol thanks but I have installed the xz2 Rom and yh it was quite good but I was trying to eliminate the heat whilst the good performance oh well but anyway I kinda need those files from the xz2 because mine our kinda messed up now it would be appreciated if you sent me them via Google drive mega mediafire etc so I can redownload those files and not the whole rom thx
crono9977 said:
An easy way to reduce heat is to adjust hotplugging thresholds for the big cores (you'll need root of course). You can do that easily through Kernel Adiutor in the CPU Hotplug settings. Lower the "minimum cpus big" and raise the "busy up threshold". If you really don't want your big cores on just set busy up threshold to 100 or something.
I personally have mine set to 0 minimum and 87 busy up threshold. You'll need to make an extra adjustment to get 0 minimum big cpus to stick, otherwise it will revert back to the default of 1. (note: I'm on the latest stock rom)
Also, setting your cpu governors to interactive and fine tuning the parameters will further reduce heat.
Click to expand...
Click to collapse
thanks for explaining, it will help me further tweak my phone as i like

Categories

Resources