[KERNEL][Sense/AOSP][aroma] lONELyX #023|3.1.10|S2W,DT2W,FC,UMS,UV,OC,MPDec,CPUQuiet

http://host.bindroid.com/lyapota/lON...ernel_head.png

http://forum.xda-developers.com/pict...ictureid=31974

Source : Original thread on xda

Stock HTC 4.18.401.2 kernel sources.
+Sweep 2 Wake
+Double tap 2 Wake
+Fast charge
+UMS

src GitHub link.

IMAGES

Spoiler:

http://host.bindroid.com/lyapota/lON...yx_kernel1.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel2.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel3.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel4.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel5.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel7.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel8.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel9.pnghttp://host.bindroid.com/lyapota/lON...yx_kernel6.png

Quote:

---

Configuring kernel parameters:

Spoiler:

S2W Configs: Turn off: codice: echo "0" > /sys/android_touch/sweep2wake Button panel locks to s2w after this distance: codice: /sys/android_touch/s2w_register_threshold Screen turns on/off after this distance: codice: /sys/android_touch/s2w_min_distance Direction independent(1 - Yes, 0 - No): codice: /sys/android_touch/s2w_allow_stroke Pocket protection(1 - Yes, 0 - No): codice: /sys/android_touch/pocket_detect DoubleTap2Wake Configs: Turn on: codice: /sys/android_touch/s2w_allow_double_tap Time double taps (ms) codice: /sys/android_touch/s2w_double_tap_threshold Time between double taps codice: /sys/android_touch/s2w_double_tap_duration Dead area in points from top of screen put 1780 for dt2w works only on virtual keys area codice: //sys/android_touch/s2w_double_tap_dead_area Activate fast charge (1 active - non active): codice: /sys/devices/platform/htc_battery/fast_charge Disable CPU freq limit in early suspend mode codice: /sys/module/cpu_tegra/parameters/perf_early_suspend Disable EDP limit codice: /sys/module/cpu_tegra/parameters/disable_edp_limit Backlight button brightness (0-255) codice: /sys/class/leds/button-backlight/button_brightness Quick GPU OC 0 - 416 Mhz, 1 - 484 Mhz, 2 - 520 Mhz codice: /sys/kernel/tegra3_dvfs/gpu_quick_oc CPU UV one digital value such as 25 or 0 or -25, -50, etc codice: /sys/kernel/tegra3_dvfs/cpu_millivolts CORE UV one digital value such as 25 or 0 or -25, -50, etc codice: /sys/kernel/tegra3_dvfs/core_millivolts Eco mode 0 - disabled, 1 - enabled (plug up to max 2 core) codice: /sys/module/intelli_plug/parameters/eco_mode_active

---

Quote:

---

aroma installer

Spoiler:

UMS Mass storage (Sense applications) common presets turn on/off S2W S2W direction dependent S2W three/two buttons distance pocket protection on/off turn on/off DT2W DT2W only on the VK board usb fast charge on/off VK button brightness set 0 set 60 set 140 set 255 GPU OC 416, 484, 520 416 Mhz set 484 Mhz set 520 Mhz boost CPU on resume disable/enable EDP limitation disable/enable LP mode on resume disable/enable ECO mode limit CPU max freq Undervolting CPU -25 mV -50 mV CORE -25 mV -50 mV frandom device flash kernel image (for S-OFF device) Sense LM seria Sense LQ seria Sense LI seria Sense UV LM seria Sense UV LQ seria Sense UV LI seria Sense MV LM seria Sense MV LQ seria Sense MV LI seria

---

COME SI INSTALLA
Per S-OFF
1. Scaricare il file zip e copiarlo nella SDCard
2. Flash ZIP da recovery

Per S-ON
1. Scaricare il file zip ed estrarre il kernel\boot.img nella cartella fastboot del Kernel Flasher
2. Copiare il file ZIP nella SDCard e flasharlo da recovery
3. Riavviare in bootloader e installare il Kernel da pc tramite Kernel Flasher

Quote:

---

Short explanation:

Tegra 3 Tegra 3 have two CPU clasters G cluster: 4 high performance Cortex A9 cores LP cluster: 1 low leakage Cortex A9 core Only 1 cluster can be active at a time To enable use of LP cluster, must only 1 CPU to be active No interrupts or other wakeups possible for other cores CPU management Handles both onlining/offlining cores and cluster switch Use hotplug to online/offline cores Uses the per cpu frequency targets set by cpufreq, and number of runing threads, as a measure of load CPUFreq The cpufreq architecture allows frequency scaling of a target CPU and is a basic driver installed in the kernel. Controlling of frequency and its corresponding voltage results in lower power of the target device. On the Android device, dynamic frequency scaling is realized by using the governors. Governor monitors the current usage on each core at certain time intervals. When the load exceeds or falls below the threshold, frequencies are made higher or lower dynamically. Use SMP to identify power suspend/resume events. Governors Deside with what frequency must works cpu Decide how long time cpu must stay with this frequency and which be next Good gide by governors HERE. HotPlug The hotplug is an extended function of cpufreq, which was developed specifically for the power control of multicore processors. When cpufreq sets a core to the maximum frequency that runs for a certain period of time, the hotplug adds another core to distribute the load. Similarly, when cpufreq sets a core to the minimum frequency and the load stays low, the hotplug shuts down excess cores to reduce power consumption. HTC best trade (HTC) Cpu auto-hotplug/unplug based on cpufreq and runnable threads Automatic decision wether to switch to low power core or not Automatic decision wether to switch off cpus 1,2,3 Qualcom mpdecision (showp1984) Cpu auto-hotplug/unplug based on system load (runqueue) Automatic decision wether to switch to low power core or not Low power single core while screen is off Nvidia cpuquiet (maxwen) Uses load status to hotplug cpus Uses also rq_stats to detect situations with lots of threads, but low load Froze cpus instead turn off as in best trade and mpdecision. Cpuquiet implements pluggable policies for forcing cpu cores into a quiescent state. Appropriate policies will save power without hurting performance Basically its a governer for the CPU cores Runnable activates cores based on multithreading Balanced activates based on load Userspace basically forces them online RQ_STATS and LOAD_STATS use the rq information to scale the CPUs Cpu quiescent state, instead turning off it was main idea for develop cpuquiet by nvidia

---

ver #023

androidfilehost.com
http://host.bindroid.com/lyapota/lON...oad-button.png
mirror
bindroid.com
http://host.bindroid.com/lyapota/lON...oad-button.png
CHANGE LOG

≠

Ver 023 + added MV kernels - middle undervolting from the box (CORE -25 mV/CPU -50 mV) - complette removed LS seria. full kernel set now: LM, LM_UV, LM_MV, LQ, LQ_UV, LQ_MV, LI, LI_UV, LI_MV aroma + added value 10 backlight button brightness Ver 022 + the golden kernel seria LM UV -50 from the box return back in full team UV - LM, LQ, LI, LS look in ZIP with uv predicate. - removed quick core uv option as incompatible with UV -50 kernels, the core_millivolts stay. aroma * fixed mistakes. + added eco mode option + account UV -50 kernels features Ver 021 + added intelly hot plug (faux123), LI seria in ZIP * restored Best trade hot plug (HTC), LS seria in ZIP Ver 020 * fixed bluetooth for AOSP, checked with CM 10.2.1 Ver 019 + restored frandom compiled as separate module * restored /sys/kernel/tegra3_dvfs/core_millivolts getter show CPU clock freq with CPU voltage, setter takes one digital value: 25 or -25 or -50 etc. Entered value applying to all CPU voltage table. + added core voltage attribute /sys/kernel/tegra3_dvfs/core_millivolts getter show GPU clock freq with CORE voltage, setter takes one digital value: 25 or -25 or -50 etc. Entered value applying to all CORE voltage table. + added quick core voltage atrribute /sys/kernel/tegra3_dvfs/core_quick_mv 0 - stock mV table, 1 set -25 mV, 2 set -50 mV into core_millivolts * compiled two kernel files LM and LQ with stock voltage aroma + added undervolting option to CORE and CPU voltage. * restored frandom option * in zip file two kernel images LM and LQ seria packed with Sense ramdisk. To get AOSP repack appropriate sense kernel into AOSP image. Ver 018 * DVFS GPU table 484 Mhz set as default * -25 mV core voltage aroma + design by LeSScro + default GPU OC 484 Mhz + reboot dialogue on the finish install after FS sync (thx @fichl) - removed endeavoru model checks before install Ver 017 * undervolted -50mV for all freq table from the box * enhanced gpu_quick_oc to three position. 0 - 416 Mhz(default), 1 - 484 Mhz, 2 - 520 Mhz * no_edp_limit reworked and renamed to disable_edp_limit. Now applied values from init.d without losing after. + added gaming governor + compiled with linaro 4.7 Cortex A9 toolchain with appropriated compiler options + added frandom and erandom char devices + added 56frandom file to init.d This script replace random with frandom and urandom with erandom. If you want to stay with stock google char devices just remove 56frandom file from init.d dirrectory. Ver 016 - reverted to stock variant button backlight - removed blink virtual key supports, button_brightness stay here. + swap support + reworked init.d/55sw2wake + reworked min scale frequnce same as max + compiled with linaro 4.7 * fixed not applied CPU voltage * fixed abnormal battery consuming * GPU OC set default to 484 Mhz + added gpu_quick_oc to 520 Mgz Ver 015 * user policy max freq sync vs scaling max. + applied fix for proximity sensor with not enough light. +applyed wi-fi patch. To init.d/55sw2wake added ------------------------ ##Blink VK with events echo "0" > /sys/class/leds/button-backlight/auto_bln; #Actual anly for cpuquiet LQ seria #echo "0" > /sys/module/cpu_tegra/parameters/disable_lp_mode_on_resume; Ver #014 separated on the three named serias: LS - stock HTC best trade hotplug LM - mpdecision hotplug LQ - Nvidia cpuquiet hotplug Ver 014 * Remade no_edp_limit attribute. Now can be applied from init.d Ver 013 + added Backlight button brightness /sys/class/leds/button-backlight/button_brightness (0-255) Ver 012 * UV-mv table /sys/kernel/tegra3_dvfs/cpu_millivolts * GPU OC 520 persist removed gpu_oc and quick_gpu_oc attributies (not needed), but forgot to remove commented string gpu_quick_oc from init.d/sw2wake - Removed intellidemand, ondemand1 and touchdemand governors old release not compatible with new kernel, may be i'm add reworked versions latter * Thermal throttle limitation to disable /sys/module/cpu_tegra/parameters/no_thermal_throttle_limit (1-disable control) i'm highly do not recommending touch it thermal throttle prevent cpu damage from overheating more then 85 deg by C * EDP limitation to disable /sys/module/cpu_tegra/parameters/no_edp_limit (1-disable max CPU freq limits in multi cpu mode) EDP set freq limits dinamicalky decide battery level and cpu temperature below 85 deg by C * perf mode for awake /sys/module/cpu_tegra/parameters/perf_early_suspend (1-enable perfomance mode in early suspend mode) + Support HTC power save mode /sys/htc/power_save (1 - enable power save mode 1.3 Ghz cpu limitation) controlled by ROM HTC power manager no need touch it + Support HTC media boost Don't investigate it. In code it some alghoritm to boost cpu freq for audio and video processing. looks like controled by ROM + Support HTC ril boost Boost cpu freq in deep sleep mode for ril modem(incoming call) Ver 011 died in beta stage Ver 010 + GPU OC 520 optional in init.d/sw2wake + MP Decision instead HOTPLUG + IO Schedules (bfq, row, sio) + Governors (touchdemand, ondemand1) Ver 009 - GPU 520 removed * do over again dt2w * possible fixed stuck after deep sleep * possible fixed vk responsible for Venom users Ver 008 + Voltage control + GPU 520 + smartmax, smartmax_eps governors. Ver 007 *Code revised and cleaned *Pocket protection rewrited, now it work as expected -Dead area by default revert back to 0 Ver 006 +s2w Added pocket protection /sys/android_touch/pocket_detect, enabled by default in 55sw2wake +dt2w Added dead area /sys/android_touch/s2w_double_tap_dead_area, 1780 by default in 55sw2wake (dt2w work only in virtual key panel) put 0 for dt2w works on all screen and not only on virtual keya area.

Noi che siamo in S-ON per installare questo kernel dobbiamo flashare lo .zip da recovery e poi flashare il boot.img da pc con Kernel Flasher (si può fare con i comandi fastboot?)?

Quote:

---

Originariamente inviato da Lorenzone

Noi che siamo in S-ON per installare questo kernel dobbiamo flashare lo .zip da recovery e poi flashare il boot.img da pc con Kernel Flasher (si può fare con i comandi fastboot?)?

---

Si kernel flasher è per i più pigri :p ma se apri lo script di kernel flasher troverai gli stessi comandi che dai con fastboot

Quote:

---

Originariamente inviato da -Luke-

Si kernel flasher è per i più pigri :p ma se apri lo script di kernel flasher troverai gli stessi comandi che dai con fastboot

---

Ok :D altra cosa, io flasho lo .zip via recovery, fatto ciò faccio "reboot now" quando si riavvia devo tener premuto il tasto accensione + vol - oppure posso far avviare il cell e ravviarlo in bootloader? Grazie :)

Qualcuno di voi questo kernel lo ha provato? :)
Volevo installarlo perché da quanto vedo negli screenhost oltre al modulo MTP (che funziona solo dove vuole) ha anche l'opzione di archivio di massa :)

Quote:

---

Originariamente inviato da Lorenzone

Ok :D altra cosa, io flasho lo .zip via recovery, fatto ciò faccio "reboot now" quando si riavvia devo tener premuto il tasto accensione + vol - oppure posso far avviare il cell e ravviarlo in bootloader? Grazie :)

Qualcuno di voi questo kernel lo ha provato? :)

---

Nelle opzioni di reboot mi pare che c'è anche "reboot to bootloader" o sbaglio ? :D se non c'è allora lo spegni e lo riavvii in bootloader

Quote:

---

Originariamente inviato da -Luke-

Nelle opzioni di reboot mi pare che c'è anche "reboot to bootloader" o sbaglio ? :D se non c'è allora lo spegni e lo riavvii in bootloader

---

Ah ok grazie :D

Aggiornato alla Ver 007
*Code revised and cleaned
*Pocket protection rewrited, now it work as expected
-Dead area by default revert back to 0

3.1.10-g7f360be ver 007
androidfilehost.com
http://host.bindroid.com/lyapota/lON...oad-button.png
mirror
bindroid.com
http://host.bindroid.com/lyapota/lON...oad-button.png

grazie luke per l impaginazione...come lo reputi questo kernel?

Quote:

---

Originariamente inviato da fillo82

grazie luke per l impaginazione...come lo reputi questo kernel?

---

Dato che non ho più il HOX non posso provarlo personalmente, però su xda ho letto molti commenti positivi, c'è chi dice che gira meglio dello stock kernel e quindi la ViperX va molto bene... Io lo proverei subito :)