Database Users

in your opinions..does SetCPU work or not on these builds?

just wondering..i tried it once, but i saw no diffrence..
what are your findings? work for you or not? and what settings worked best for you?

I use these on mattc and they work for me!
I use the pack21 config:
Main Tab:
* 998Mhz Max
* 245Mhz Min
* Ondemand Scaling
* Check Set on Boot
Profile Tab:
* Check Enable
* Check Notifications
* Screen Off Profile
o
o 245 Max
o 245 Min
o Ondemand Governor
o Priority 100
* Battery < 25% Profile
o 652 Max
o 245 Min
o Ondemand Governor
o Priority 0
Advanced Tab:
* 20000 Sampling Rate
* 30 Up Threshold (THIS IS THE KEY: This means when your CPU load hits 30%, it will scale up the mhz. If the phone still responds too slow for your taste, set this lower)
* 0 Ignore Nice
* 0 Powersave
* Check Set on Boot (And Apply)

dvigue said:
just wondering..i tried it once, but i saw no diffrence..
what are your findings? work for you or not? and what settings worked best for you?
Click to expand...
Click to collapse
Seems to work for me but I use it more to scale down the cpu for power saving, rather than overclocking, it only really needs to run at 768 for day to day use anyway, look for the thread about battery saving on all Android roms: those settings seem pretty effective for me.
Edit: the ones just posted by Tinuz97 are the ones I use, except I set the maximum to 768.

tinuz97 said:
I use these on mattc and they work for me!
I use the pack21 config:
Main Tab:
* 998Mhz Max
* 245Mhz Min
* Ondemand Scaling
* Check Set on Boot
Profile Tab:
* Check Enable
* Check Notifications
* Screen Off Profile
o
o 245 Max
o 245 Min
o Ondemand Governor
o Priority 100
* Battery < 25% Profile
o 652 Max
o 245 Min
o Ondemand Governor
o Priority 0
Advanced Tab:
* 20000 Sampling Rate
* 30 Up Threshold (THIS IS THE KEY: This means when your CPU load hits 30%, it will scale up the mhz. If the phone still responds too slow for your taste, set this lower)
* 0 Ignore Nice
* 0 Powersave
* Check Set on Boot (And Apply)
Click to expand...
Click to collapse
great info..i just did it, ill report back...
thank you

Im using overclock widget instead and battery in standby has improved and performance has been smooth constantly. I have 245 while screen off and 998 during screen on.
Sent from my HTC Desire using XDA App

will it always stay in the notification bar or can we take it off?

dvigue said:
just wondering..i tried it once, but i saw no diffrence..
what are your findings? work for you or not? and what settings worked best for you?
Click to expand...
Click to collapse
setcpu gives me an extra 18ish hours on hd2. the issue that MOST people come across is not setting the priories correctly.
the two previous posts also have their priories wrong.
for example:
996 max 256min
<100 battery
priority 50
756max 256min
<65 battery
priority 50
in this case the second profile will be completely ignored. It should be 51 or better in the priority.

I have the same setup as Tinuz97, working fine for me.
Sent from my HTC HD2 using XDA App

CPUFreq Governor Info

A plethora of info on CPU governors (source):
CPU frequency and voltage scaling code in the Linux(TM) kernel
L i n u x C P U F r e q
C P U F r e q G o v e r n o r s
- information for users and developers -
Dominik Brodowski <[email protected]>
some additions and corrections by Nico Golde <[email protected]>
Clock scaling allows you to change the clock speed of the CPUs on the
fly. This is a nice method to save battery power, because the lower
the clock speed, the less power the CPU consumes.
Contents:
---------
1. What is a CPUFreq Governor?
2. Governors In the Linux Kernel
2.1 Performance
2.2 Powersave
2.3 Userspace
2.4 Ondemand
2.5 Conservative
2.6 Interactive
2.7 MinMax
2.8 SmartassV2
3. The Governor Interface in the CPUfreq Core
1. What Is A CPUFreq Governor?
==============================
Most cpufreq drivers (in fact, all except one, longrun) or even most
cpu frequency scaling algorithms only offer the CPU to be set to one
frequency. In order to offer dynamic frequency scaling, the cpufreq
core must be able to tell these drivers of a "target frequency". So
these specific drivers will be transformed to offer a "->target"
call instead of the existing "->setpolicy" call. For "longrun", all
stays the same, though.
How to decide what frequency within the CPUfreq policy should be used?
That's done using "cpufreq governors". Two are already in this patch
-- they're the already existing "powersave" and "performance" which
set the frequency statically to the lowest or highest frequency,
respectively. At least two more such governors will be ready for
addition in the near future, but likely many more as there are various
different theories and models about dynamic frequency scaling
around. Using such a generic interface as cpufreq offers to scaling
governors, these can be tested extensively, and the best one can be
selected for each specific use.
Basically, it's the following flow graph:
CPU can be set to switch independently | CPU can only be set
within specific "limits" | to specific frequencies
"CPUfreq policy"
consists of frequency limits (policy->{min,max})
and CPUfreq governor to be used
/ \
/ \
/ the cpufreq governor decides
/ (dynamically or statically)
/ what target_freq to set within
/ the limits of policy->{min,max}
/ \
/ \
Using the ->setpolicy call, Using the ->target call,
the limits and the the frequency closest
"policy" is set. to target_freq is set.
It is assured that it
is within policy->{min,max}
2. Governors In the Linux Kernel
================================
2.1 Performance
---------------
The CPUfreq governor "performance" sets the CPU statically to the
highest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.2 Powersave
-------------
The CPUfreq governor "powersave" sets the CPU statically to the
lowest frequency within the borders of scaling_min_freq and
scaling_max_freq.
2.3 Userspace
-------------
The CPUfreq governor "userspace" allows the user, or any userspace
program running with UID "root", to set the CPU to a specific frequency
by making a sysfs file "scaling_setspeed" available in the CPU-device
directory.
2.4 Ondemand
------------
The CPUfreq governor "ondemand" sets the CPU depending on the
current usage. To do this the CPU must have the capability to
switch the frequency very quickly. There are a number of sysfs file
accessible parameters:
sampling_rate: measured in uS (10^-6 seconds), this is how often you
want the kernel to look at the CPU usage and to make decisions on
what to do about the frequency. Typically this is set to values of
around '10000' or more.
show_sampling_rate_(min|max): the minimum and maximum sampling rates
available that you may set 'sampling_rate' to.
up_threshold: defines what the average CPU usage between the samplings
of 'sampling_rate' needs to be for the kernel to make a decision on
whether it should increase the frequency. For example when it is set
to its default value of '80' it means that between the checking
intervals the CPU needs to be on average more than 80% in use to then
decide that the CPU frequency needs to be increased.
ignore_nice_load: this parameter takes a value of '0' or '1'. When
set to '0' (its default), all processes are counted towards the
'cpu utilisation' value. When set to '1', the processes that are
run with a 'nice' value will not count (and thus be ignored) in the
overall usage calculation. This is useful if you are running a CPU
intensive calculation on your laptop that you do not care how long it
takes to complete as you can 'nice' it and prevent it from taking part
in the deciding process of whether to increase your CPU frequency.
2.5 Conservative
----------------
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered environment.
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage steps the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
2.6 Interactive
---------------
The CPUfreq governor "interactive" is designed for latency-sensitive,
interactive workloads. This governor sets the CPU speed depending on
usage, similar to "ondemand" and "conservative" governors. However,
the governor is more aggressive about scaling the CPU speed up in
response to CPU-intensive activity.
Sampling the CPU load every X ms can lead to under-powering the CPU
for X ms, leading to dropped frames, stuttering UI, etc. Instead of
sampling the cpu at a specified rate, the interactive governor will
check whether to scale the cpu frequency up soon after coming out of
idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is very busy between exiting idle and
when the timer fires then we assume the cpu is underpowered and ramp
to MAX speed.
If the cpu was not sufficiently busy to immediately ramp to MAX speed,
then governor evaluates the cpu load since the last speed adjustment,
choosing th highest value between that longer-term load or the
short-term load since idle exit to determine the cpu speed to ramp to.
There is only one tuneable value for this governor:
min_sample_time: The minimum amount of time to spend at the current
frequency before ramping down. This is to ensure that the governor has
seen enough historic cpu load data to determine the appropriate
workload. Default is 80000 uS.
2.7 MinMax
---------------
The CPUfreq governor "maxmin" tries to minimize the frequency jumps by limiting
the selected frequencies to only two frequencies: either the min or the max
frequency of the current policy. The frequency is raised or lowered according
to the current load and the 'up_threshold' and 'down_threshold'.
Its parameters and implementation are similar to that of conservative.
It does not have the freq_step parameter as it jumps right from min to max
and vice-versa.
The sampling_down_factor, unlike conservative, will count the minimal number
of samplings since the last time we saw the 'up_threshold' load on the CPU.
Hence it is set to higher default and acts as a limiter not to do too many
frequency jumps without hurting the performance.
2.8 SmartassV2
---------------
The CPUfreq governor "smartassV2", like other governors, aims to balance
performance vs battery life by using low frequencies when load is low and
ramping the frequency when necessary, fast enough to ensure responsiveness.
The implementation of the governor is roughtly based on the idea of interactive.
The idle loop is used to track when the CPU has idle cycles. The idle loop will
set a relatively high rate timer to sample the load when appropriate, the timer
will measure the load since it was set and schedule a work queue task to do the
actual frequency change when necessary.
The most important tunable is the "ideal" frequency: this governor will aim
for this frequency, in the sense that it will ramp towards this frequency much
more aggresively than beyond it - both when ramping up from below this frequency
and when ramping down from above this frequency. Still, note, that when load is
low enough the governor should choose the lowest available frequency regardless
of the ideal frequency and similarly when load is consistently high enough the
highest available frequency will be used.
Smartass also tracks the state of the screen, and when screen is off (a.k.a
sleep or suspended in the terms of this governor) a different ideal frequency
is used. This is the only difference between the screen on and screen off
states. Proper tuning of the awake_ideal_freq and sleep_ideal_freq should
allow both high responsiveness when screen is on and utilizing the low
frequency range when load is low, especially when screen is off.
Finally, smartass is a highly customizable governor with almost everything
tweakable through the sysfs. For a detailed explaination of each tunable,
please see the inline comments at the begging of the code (smartass2.c).
Click to expand...
Click to collapse

Slow phone after screen turn on and lockscreen (CyanogenMod 7.2 + sd-ext)

Hello everybody!
I'm having a strange problem: if i have the phone locked, with screen turned off for a while, in my pocket, when i turn it on again it is very slow. It takes about 30 seconds to come back to usual performance.
For example, if i unlock the phone and i go to SMS or WhatsApp, the keyboard (Swiftkey) it's so slow that i have to wait for every word to complete, before i can type another one.
After 30 seconds from the unlock the phone works ok.
The problem started when i've upgraded from CyanogenMod 7.1 to CyanogenMod 7.2 and i've created an sd-ext partition (in ext3 format, on a class 6 SD) to move there some apps.
I've got an HTC Desire HD.
I noticed the same problem when i was using a MIUI rom with the CPU Tuner app: i supposed that it slowed down too much the CPU when the screen was locked, so that it took a lot to come back to normal performances. But, now, i don't have that app installed and, looking ad Exaile 2 when i unlock my phone, it seems that CPU frequencies it's a 1 Ghz and even RAM usage is ok.
What could it be?
I have to wipe and install CM 7.2 from scratch?
Or could it be the sd-ext partition with apps on?
Thank you in advance!

Try installing set CPU or CPU Tuner again and set the CPU to something high when the phone is asleep. If that then works and it is no longer laggy try reverting it to a lower speed.

Not sure about the sd ext partition,, but yes, try a full wipe and install 7.2.
Sent from a dream.

Just change the governor. Governor is interactive by default i think.
Had the same problem after weeks i just changed governor to ondemand and everything was prefect.
Sent from my Desire HD using Tapatalk 2

Try installing set CPU or CPU Tuner again and set the CPU to something high when the phone is asleep. If that then works and it is no longer laggy try reverting it to a lower speed.
Click to expand...
Click to collapse
When i had it, i never configured because i am too lazy
I'll give a try, thanks!
Not sure about the sd ext partition,, but yes, try a full wipe and install 7.2.
Click to expand...
Click to collapse
I do not really want to, but i think too that could be a good test
Just change the governor. Governor is interactive by default i think.
Had the same problem after weeks i just changed governor to ondemand and everything was prefect.
Click to expand...
Click to collapse
Good tip!
My governor is "interactive" too, infact. I'm changin it to "ondemand".
Does anyone have a table that explain the difference between governors?

I'm on ARHD and the same started all of a dudden a few months ago. I had the same governor and settings for months without change and this still started. I changed governors (ondemand, smoothass, smartass, etc.) but it still happens sometimes. Not ver often but sometimes.

sberla54 said:
Good tip!
My governor is "interactive" too, infact. I'm changin it to "ondemand".
Does anyone have a table that explain the difference between governors?
Click to expand...
Click to collapse
Here you go
7. CPU Scaling Governors
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Click to expand...
Click to collapse
Here as well
CPUFreq governors in the Android Kernel
=======================================
+ performance
The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq.
+ powersave
The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq.
+ userspace
The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory.
+ ondemand
The CPUfreq governor "ondemand" sets the CPU depending on the current usage. To do this the CPU must have the capability to switch the frequency very quickly. There are a number of sysfs file accessible parameters: sampling_rate, show_sampling_rate_min, up_threshold, ignore_nice_load, sampling_down_factor.
+ conservative
The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of: freq_step & down_threshold
+ interactive
The CPUfreq governor "interactive" is designed for latency-sensitive, interactive workloads. This governor sets the CPU speed depending on usage, similar to "ondemand" and "conservative" governors. However, the governor is more aggressive about scaling the CPU speed up in response to CPU-intensive activity. The tuneable value for this governor are: min_sample_time & go_maxspeed_load
+ smartass (By [email protected])
The smartass governor is a complete rewrite of the interactive governor. CPU spends much more time at the lower frequencies for improved battery life. It gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
+ savagedzen (By [email protected])
SavagedZen is a governor based on the Smartass governor. With tweaks to paramaters which control how much and how fast cpu ramps up/down. Main difference versus Smartass is that cpu ramps down not in fixed steps, but based on cpu load heuristics, i.e. when cpu load falls below threshold (min_cpu_load), cpu immediately ramps down to a frequency derived from the measured load.
+ interactiveX (By [email protected])
Modified version of interactive with suspend code which locks at lowest clock speed when screen is off. Has a sleep+awake profile, meaning you don't need to set up manual profiles, it will lock at your minimum frequency during screen off
Click to expand...
Click to collapse

andreasy said:
I'm on ARHD and the same started all of a dudden a few months ago. I had the same governor and settings for months without change and this still started. I changed governors (ondemand, smoothass, smartass, etc.) but it still happens sometimes. Not ver often but sometimes.
Click to expand...
Click to collapse
Me too i didn't changed the governor, but in my case, a ROM upgrade and a sd-ext creation are some major changes that can affect performances...
l33ch0r said:
Here you go
Here as well
Click to expand...
Click to collapse
Thank you l33ch0r!
There doesn't seem to be much difference between "ondemand" and "interactive"; regarding to this documentation, "interactive" seems more quick.
Anyway, i've changed my governor to "ondemand" and i must say that all yesterday the phone has been fast and responsive. I'll keep you updated!
Thank you very much!

★ Kernel Profile Sharing Thread for LG G3 ★

Introduction:
Hey there, this thread is all about sharing profile setups for our beloved G3.
Feel free to share your settings too or PM me and i link it straight to the second post ​
A few things explained:
Android Modders Guide ( thanks to @gsstudios )
Explanation of LMK & Adj and Minfree settings ( thanks to @Papa Smurf151 )
What is ZRAM and how does it work??? ( thanks to @-CALIBAN666- )
How to apply Synapse Profiles:
Code:
- Unzip
- Move .tgz file to your Internal storage > Synapse > saved_profiles
- Profile > Profiles > choose .tgz file > press "check-mark" and not "X" > choose "restore profile"
- Synapse will restart and then press "X"
- Check all values and if you have to change something press "check-mark"
How to reset Synapse Profiles:
Code:
tools > clear synapse data > restart device > start synapse > choose "check-mark" = stock values

--= Android 5.x.x Profiles =--
gr3ud´s synapse profiles:
R21 Profile with EuphoriaOS & 777 Kernel ( thanks to @777jon )
--> Old/Experimental/Beta Profiles - Android 5.1.1 @ 777Kernel (R21)
--> Old/Experimental/Beta Profiles - Android 5.1.1 @ 777Kernel (R15 - R20)
--= Android 6.x.x Profiles =--
gr3ud.6.0.1.V1 - Alucard + Alucard Hotplug
http://pastebin.com/jEKAmYVZ
CPU:
- MSM Limiter: Disabled
- min: 300MHz
- max Freq: 2457 MHz
- Governor: Alucard
- CPU Tunables:
> cpus_down_rate: 4
> cpus_up_rate: 1
> freq_responsiveness: 2256
> sampling_rate: 50000
- Multicore Powersaving: Disabled
- CPU Boost: Interval: 0ms / Sync Threshold: Disabled / Input Interval: 1000ms / Input Boost: 1958 MHz
CPU Voltage (optional for extra battery):
- Global Offset: -25 (stable, tested with Antutu)
HOTPLUG:
- Alucard Hotplug
- Sampling Rate: 50%
- Prevent to Suspend: Disabled
- Minimum CPUs Online: 4
- Maximum CPUs Online: 4
- Max Cores Screen Off: 2
THERMAL:
(optional) Thermal Compound Cooling Mod -> https://www.youtube.com/watch?v=PH5wCeootNI
- Intellithermal Enabled
- Core Control OFF
- Freq Throttle Temp = 75°c
- Core Throttle Temp = 80°c
GPU:
- min. freq.: 330
- max. freq.: 547
- Governor: msm-adreno-tz
- Simple GPU Algorithm: Enabled
- Laziness: 10
- Ramp Threshold: 0
- Adreno Idler: Disabled
SCREEN ("personal preference/vibrant colors"):
- Saturation Intensity: 60
- Screen Value: 120
- Screen Contrast: 148
I/O:
- Internal Storage: ZEN (128 kB)
- Rotational Storage: Off
- Add Random: Off
- I/O Stats: Off
- RQ Affinity: 0
KSM:
- Disabled
LMK:
- Adaptive Low Memory Killer: Disabled
Virtual Memory:
- Laptop Mode 1 = more performance but can cause random reboots (use this only with stable builds)
- Z-RAM: Disabled
Misc Controls:
F-Sync: Disabled = more performance but can cause random reboots and data loss ( use this only with stable builds)
★ souler456´s profile - Slim + IntelliPlug ★
http://forum.xda-developers.com/showpost.php?p=66659439&postcount=343 ( thanks to @souler456 )

1st
gr3ud said:
List of shared profiles:​
My profile with 777 Kernel (R21) + Euphoria-OS 1.1 (Android 5.1.1) (thanks to @777jon ):
- Performance Profile (aka " almost Nexus smooth")
- Not very battery friendly (~3h - 5h SOT with default 3000 mAh battery)
- I don't know how it works out for "Gamers" because i just run simple 2D games when i got the time for that.
- Please don't expect too much, this works for me and my daily usage.
- Enjoy
Setup Values:
CPU:
min: 345 MHz
max: 2457 MHz
MSM Limiter: Disabled
Debug Mask: OFF
Suspend Min Frequency: irrelevant but 345 MHz
Resume Max Frequency: irrelevant but 2457 MHz
Suspend Max Frequency: irrelevant but 2457 MHz
Suspend Defer Time: irrelevant but 0
Input Boost Frequency: 2457 MHz
Boost interval: 5000 ms
Min Input Interval : 100ms
Maximum CPUs Boosted: 4
Multi-core Power Saving: OFF
Arch Power: OFF
CPU Governor(0-3): Nightmare
HOTPLUG:
Msm Hotplug Driver: Enabled
min: 4
max: 4
boost: 4
Screen Off: 2
Boost Lock: 5000 ms
Down Lock Duration: 5000 ms
History Size: 1
Fast Lane Load: 0
Offline Load: 0
Suspend Defer Time: 0
Thermal: ( I use "thermal paste/copper shim mod" so you may choose higher values without)
Intellithermal: Enabled
Core Control : Enabled
Frequency Throttle Temperature: 80c
Core Throttle Temperature: 85c
I/O:
Read-ahead Size: 1024 KB
I/O scheduler: zen
CRC Control: OFF
MMC Clock Scaling Control: ON
Add Random: OFF
I/O Stats: OFF
Rotational: OFF
No Merges: All
RQ Affinity: Disabled
NR Requests: 128
GPU:
GPU min Frequency: 27 MHz
GPU max Frequency: 657 MHz
GPU Governor: Performance
All Add-on´s : Off
GAMMA:
Saturation: 270
Memory(experimental): (beta = ** stock values)
Z-RAM: 0 MB
Dirty Background Ratio: 80% (**5%)
Dirty Ratio: 90% (**40%)
Dirty Expire Centisecs: 200 cs
Dirty Write-back Centisecs: 500 cs
Drop Caches: ON
Extra Free KB: 49050 kB (**43200 kB)
Laptop Mode: ON
Swappiness: 60% (**10%)
VFS Cache: 10% (**100%)
Misc:
TCP: cubic - westwood or what you desire.
How to test:
Run net speed tests with each protocol at least 3 times to compare the average with this Speedtest App
Power Suspend Mode: LCD Hooks
FSYNC: ON
ADV:
Krait-C States: All ON
KSM: ON
Pages to Scan: 128
Scan Delay Interval: 750
Deferred Timer: OFF
Gentle Fair Sleepers: OFF
Adaptive LMK: OFF
Build.PROP:
Wifi Scan: 300 sec
VM Heapsize: 512 MB
Allow purging of assests: OFF
Tools:
SELinux Status: Permissive
--------------------------​
Click to expand...
Click to collapse
Nice to see you made a thread bro

Well, this is the perfect place to share your "imagination". Great
Sent from my LG-D855 using Tapatalk

? ? ? much appreciated effort here ? ? ?

Thank you for creating a profile thread!

Got 40066 in Antutu yesterday on your 30th October set up.
Got this today with the 31st October.
Might not sell my G3 for a OnePlus X now.

johnnzey said:
Got 40066 in Antutu yesterday on your 30th October set up.
Got this today with the 31st October.
Might not sell my G3 for a OnePlus X now.
Click to expand...
Click to collapse
Hey mate glad to hear, i would personally wait for custom 6.x.x ROMs/Kernels for our device tho before moving on
To all others, thanks for your kind words i appreciate it
But without @m1trand1r and @metalgearhathaway motivating words + all the other dudes that dig my work, this thread would not exist :good:
Cheers.

Just applied your settings, great! Never had such a smooth G3! Thanks for the update!

What settings do you use for Marshmallow?

@6th_Hokage
Well since Synapse does not play nice for me and i generally have some weird issues with custom kernels on 6.x.x ROMs (Overheating,BSODs,Crashes,Random Reboots,etc) i decided to use the ROMs respective kernel.
I�´m trying Broken OS right now and they know their stuff pretty well.
They have Kernel Adiutor inbuilt so i basically switched just a few things...like:
- zzmove CPU gov with profile 8 and its inbuilt hotplug, changed the "punch freq" to 2457MHz
- CPU Boost/Interval 5000ms, Sync/Boost Freq. @ 2457MHz
- GPU min/max 587MHz with msm adreno gov
- I/O: row or zen @ 512kB
- Kernel Sampage Merging with 300 pages / 1000 ms scan
- I disabled Adaptive LMK
- Enabled Laptop Mode
- Entropy: Read 128 / Write 256
...and that's pretty much it, its not battery friendly but i don't care for battery life, still got 4hs of SOT with that setup... Lionheart works well too on 6.x.x also does smartmax , so yeah, its butter smooth as i like it for now, i miss KCAL stuff tho, but this ROM (BrokenOS) is still in alpha phase so there will be much more stuff added in the next releases from what i�´ve read on G+
I�´m also waiting for Eliminater74�´s own Kernel Manager, then i will play around with hes kernel i guess so stay tuned :good:
Also, some users mentioned that my 5.1.1 profile works very well for them on 6.x.x maybe give it a shot.
edit:
I forgot to mention that i also disable the default hotplug with Lionheart or smartmax to have all 4 cores permanent online for a little extra performance boost.

Thanks bro. Good job.

*Android 6.x.x update*
http://pastebin.com/jEKAmYVZ

Thank you for the excellent kernel setup for Marshmallow. My G3 is so much smoother than before. I give it a two thumbs up.

**Android 7.x.x Update**
CPU:
- MSM Limiter: Disabled
- min: 300 MH
- max Freq: 2457 MHz
- Governor: Nightmare
- Multicore Powersaving: Disabled
- CPU Boost: Interval: 0ms / Sync Threshold: Disabled / Input Interval: 2500ms / Input Boost: 2265 MHz
HOTPLUG:
- All Disabled
THERMAL:
(optional) Thermal Compound Cooling Mod -> https://www.youtube.com/watch?v=PH5wCeootNI
- Delete "Thermal-Engine" under system/bin
- Intellithermal Enabled
- Core Control Disabled
- Freq Throttle Temp = 75°c
- Core Throttle Temp = 80°c
GPU:
- min. freq.: 330
- max. freq.: 578
- Governor: msm adreno-tz
- Simple GPU Algorithm: Disabled
- Adreno Idler: Disabled
SCREEN ("personal preference/vibrant colors"):
- Saturation Intensity: 55
- Screen Value: 125
- Screen Contrast: 140
I/O:
- Internal Storage: bfq
- Read-ahead: 512 kB
- Rotational Storage: On
- Add Random: Off
- I/O Stats: Off
- RQ Affinity: 0
KSM:
- Disabled
LMK:
- Adaptive Low Memory Killer: Disabled
Virtual Memory:
- Laptop Mode = Disabled
- Z-RAM = 500 MB (16/2GB model only)
Misc Controls:
F-Sync = Enabled

gr3ud said:
**Android 7.x.x Update**
CPU:
- MSM Limiter: Disabled
- min: 300 MH
- max Freq: 2457 MHz
- Governor: Nightmare
- Multicore Powersaving: Disabled
- CPU Boost: Interval: 0ms / Sync Threshold: Disabled / Input Interval: 2500ms / Input Boost: 2265 MHz
HOTPLUG:
- All Disabled
THERMAL:
(optional) Thermal Compound Cooling Mod ->
- Delete "Thermal-Engine" under system/bin
- Intellithermal Enabled
- Core Control Disabled
- Freq Throttle Temp = 75°c
- Core Throttle Temp = 80°c
GPU:
- min. freq.: 330
- max. freq.: 578
- Governor: msm adreno-tz
- Simple GPU Algorithm: Disabled
- Adreno Idler: Disabled
SCREEN ("personal preference/vibrant colors"):
- Saturation Intensity: 55
- Screen Value: 125
- Screen Contrast: 140
I/O:
- Internal Storage: bfq
- Read-ahead: 512 kB
- Rotational Storage: On
- Add Random: Off
- I/O Stats: Off
- RQ Affinity: 0
KSM:
- Disabled
LMK:
- Adaptive Low Memory Killer: Disabled
Virtual Memory:
- Laptop Mode = Disabled
- Z-RAM = 500 MB (16/2GB model only)
Misc Controls:
F-Sync = Enabled
Click to expand...
Click to collapse
thank you,,with those do you get decent battery..

jlb1959.01 said:
thank you,,with those do you get decent battery..
Click to expand...
Click to collapse
It's okay, was not really my intention to save battery juice.

gr3ud said:
It's okay, was not really my intention to save battery juice.
Click to expand...
Click to collapse
thanks,looking for mid point settings,both perform and some kind of battery..thanks again..

jlb1959.01 said:
thanks,looking for mid point settings,both perform and some kind of battery..thanks again..
Click to expand...
Click to collapse
Hmm try my 6.x.x alucard profile then, had some good experience with it. No problem btw you welcome

gr3ud said:
Hmm try my 6.x.x alucard profile then, had some good experience with it. No problem btw you welcome
Click to expand...
Click to collapse
I will try it,,much appreciated..

Need help of kernel devs/experts :fingers-crossed:

Hi,
I'm using YU Yureka Plus YU5510A with 64-bit octa-core Snapdragon 615 processor running CM13 snapshot.
Coming to the point, I want to change the default cpu governor and I/O scheduler and default min frequencies.
I tried adding init.d script for governor and I/O scheduler:
Code:
[B]#!/system/bin/sh
echo 'ondemand' > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 'ondemand' > /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor
echo "noop" > /sys/block/mmcblk0rmpb/queue/scheduler
echo "noop" > /sys/block/mmcblk0/queue/scheduler[/B]
And I tried editing build.prop to set min frequencies:
Code:
[B]ro.min_freq_0=200000
ro.min_freq_4=200000[/B]
But these Scripts doesn't works at all everything reverts back to:
Governor = interactive
I/O scheduler = cfq
min cpu0-3 freq = 960000
min cpu4-7 freq = 800000
P.S: The device just ignores the minimum frequencies edited in build.prop while using "interactive" governor and "cfq" I/O scheduler and keep running the device at:
min cpu0-3 freq = 960000
min cpu4-7 freq = 800000
and even manually No-frills CPU Control the device ignores the min frequencies and continues to use the default frequencies mentioned above.