[Kernel] Devil [4.3/4.4] Samsung/AOSP - Linaro TC - Dualboot

[interzippo]

Consumo spropositato batteria c'è da settare qualcosa ?

[danigsxr]

Ho flashato il Devil2-2.1.2 oggi pomeriggio sulla mia ditto 3.1.1 e installato anche Devil Kernel Manager la prima cosa che ho notato un consumo minore della ram e una reattività maggiore lasciate impostazioni stock.....ce qualche settaggio particolare da fare?( x la miglior resa ci vorrà qualche ciclo di ricarica completo x far si che si assesti x bene giusto? )

[ingwye]

Ho flashato il Devil2-2.1.2 oggi pomeriggio sulla mia ditto 3.1.1 e installato anche Devil Kernel Manager la prima cosa che ho notato un consumo minore della ram e una reattività maggiore lasciate impostazioni stock.....ce qualche settaggio particolare da fare?( x la miglior resa ci vorrà qualche ciclo di ricarica completo x far si che si assesti x bene giusto? )

Idem, consumo minore della ram e reattività maggiore in generale

[andy88de]

SETTING KERNEL DEVIL 2.1.2 (credits @ph03n!x)
Non è il mio settore premetto....ma questi sono i setting apportati da un grande senior member di XDA (CREDITS @ph03n!x)

È in inglese ma molto comprensibile.
Questo setting dovrebbe dare ottimi risultati sia per prestazioni sia per risparmio batteria.
RISOLTO problema riconoscimenti NOTE 2 da PC...
I setting sono pensati per DITTO V 3.1.1 e kernel 2.1.2 ma si possono adeguare anche a tutti gli altri kernel Devil.
Gli screen sono esaustivi sul consumo....1°ciclo
La CPU e GPU non sono undervoltate né overcloccate.
Installazione
1)Wipe data e cache dalla app devil che usate(es. Devil manager o devil tools)
2)Flash da recovery

Download
http://forum.xda-developers.com/atta...1&d=1387650042

Per togliere il tweak
Cancellare: 99devilkerneltweaks da /system/etc/init.d e riavviare.

VI LASCIO AL POST ORIGINALE
http://forum.xda-developers.com/member.php?u=3339433

These are my settings for Devil Kernel and DN3 v3.1.1 ROM, though the setting should hold good for any other ROM too:
Code:
#!/system/bin/sh

echo devilq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 18 > /sys/devices/system/cpu/cpufreq/devilq/cpu_down_rate
echo 12 > /sys/devices/system/cpu/cpufreq/devilq/cpu_up_rate
echo 30000 > /sys/devices/system/cpu/cpufreq/devilq/down_sample_time
echo 0 > /sys/devices/system/cpu/cpufreq/devilq/early_demand
echo 400000 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_freq_1_1
echo 200000 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_freq_2_0
echo 400000 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_freq_2_1
echo 200000 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_freq_3_0
echo 400000 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_freq_3_1
echo 200000 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_freq_4_0
echo 150 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_rq_1_1
echo 150 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_rq_2_0
echo 200 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_rq_2_1
echo 200 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_rq_3_0
echo 300 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_rq_3_1
echo 300 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_rq_4_0
echo 40000 > /sys/devices/system/cpu/cpufreq/devilq/hotplug_sampling_rate
echo 50 > /sys/devices/system/cpu/cpufreq/devilq/dec_cpu_load
echo 75 > /sys/devices/system/cpu/cpufreq/devilq/inc_cpu_load
echo 40000 > /sys/devices/system/cpu/cpufreq/devilq/up_sample_time

echo 0 > /sys/devices/system/cpu/sched_mc_power_savings

echo 0 > /sys/devices/virtual/misc/touchboost/input_boost_enabled

echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active

echo 1 > /sys/kernel/mm/ksm/run

echo 3 > /sys/module/cpuidle_exynos4/parameters/enable_mask

echo 0 > /proc/sys/vm/swappiness

echo noop > /sys/dev/block/179:0/queue/scheduler
echo noop > /sys/dev/block/179:48/queue/scheduler
A word about my CPU Governor settings. I understand that almost all of us prefer higher thresholds for CPU Hotplugging (triggering the second, third and fourth CPU core in our quad core processor), but I am experimenting with something different as you can see. I am enabling an early hotplug, and am trying to get the run queue cleared at a lower CPU speed with multiple cores than running one or two cores at higher frequency. The run queue for the first hotplug is 150 because I want the CPU to fall to one core as soon as it is close to idle, because I am using AFTR+LPA for deep sleep mode, which won't kick in if more than one core is active. For the same reason, I ensure that SCHED_MC is disabled.

I didn't require a touchboost with the configuration I am running, hence it is disabled, and I am habitual to disabling DYN_FSYNC - the integrity of the data, however safe it is with DYN FSYNC on, is paramount for me. Same reason why I do not have a higher read_ahead_cache.

This is my battery life, first cycle after v2.1.2 upgrade. Note that I am not even Undervolting the CPU or the GPU or underclocking them:

This includes-
2 Google Accounts, 4 email accounts, WhatsApp, BBM, Hangouts, FB Sync - syncing all the time
About 30 minutes of phone call
About one hour of YouTube or MX Player video
A lot of XDA, Google+ and a bit of FB
I do not use WiFI - don't have one at home and my 3G is faster than my work WiFI :P

I am also attaching these settings as a recovery flashable zip file - note that I have tested if it flashes fine though Should work, let me know if otherwise. Note that only the settings I have given in this post is included in the zip file. I of course have other settings, like turning on Master Sequence for the mDNIE, USB Charging tweaks, etc. which I have not included.

And before you flash this, make sure you disable other kernel setting tools - including Devil tools/ Trickster Mod. Force Stop the app and clear its data to be sure. You can open the app after flashing my settings and rebooting, you should see my settings automatically in the app, and can make further changes from there after that.

These settings have been working reat for me, I have based these on what I used in Andrei's Perseus earlier, and have tweaked it since Devil2 1.8.x to my usage. YOUR MILEAGE WILL VARY!

If you hate these settings, just delete the 99devilkerneltweaks file from /system/etc/init.d using a root explorer and reboot.

[kawashi]

Flash to anche questo... prima ero già ok ora vediamo queste impostazioni

[pierpaolos]

con il flash del file zip continua a non riconoscere il cell da pc... soluzioni... capita anche a voi?

[kawashi]

Mi dite un modo per verificare che le impostazioni siano funzionanti?

[andy88de]

Mi dite un modo per verificare che le impostazioni siano funzionanti?

Apri il tuo kernel Manager e controlli che il governor sia devilq...e sei a posto.

[kawashi]

Dkm- Governor tweaks... che faccio? Da premettere che prima dell'installazione ho fatto solo il wipe data dell'app e non anche wipe cache poiché non me lo ha fatto fare dopo il data

[andy88de]

Dkm- Governor tweaks... che faccio? Da premettere che prima dell'installazione ho fatto solo il wipe data dell'app e non anche wipe cache poiché non me lo ha fatto fare dopo il data

Tap CPU e controlla su quale governor sei.