Database Develop

*[31-OCT]*[SuperSonic]*[Kernel] HP Pro SuperSonic SR4R SNAPPY|| FLUID || POWERSAVER:

WARNING:THIS METHOD CAN BE DANGEROUS. DONT DO ANYTHING IF YOU DO NOT KNOW WHAT YOU DO.I AM NOT RESPONSIBLE IF YOU TRANSFORM YOUR PHONE INTO A BRICK.​
Horse Power 2x eXtreme SuperSonic SR4R​
Welcome to HP Development, If you like my work, you can buy me a beer
I dont work for donations but they do help and helped in the past to counter accidential expenses that comming unplanned. And helped me to buy caffeine for my development.
Here are the list of Donators who have donated so far. I'd like to thank everybody including users of HP Kernels for support, without support and contribution it cant reach till here:
Names of Donators who donated since development of HP Kernels:
-SuperSkill (multi time donator, greatest contributors of development)
-Striatrum_bdr (My neuro protective donator)
-yann73(Multi Time Donators)
-Carburano( Thanks my friend)
-Civato(Thanks my friend)
-wapz
-Basil 123
-Steieve
-psonic2k
-PhunKee
-zerocoolrider
-fuxman
-skylight
-shreeprajay
-patiiet
-Omar Cornejo Sanchez
-abwyatt,-
-tablighs
-Rehborn-
-Jonas Andrulis
-Chris Daßler
- Bert van Hoesel
-Miguel Angel Mulero Martinez
-DARIO FRANZONI,
-Antonello Picerno
-sorry if i've forgot anybody's name please remind me if i've
HP Pro SuperSonic SR4
Changelogs(Kernel Specific)
-too long list of changelogs
-Included all changes since SS1 to SS21
-HP Pro RT Scheduler removed temporarily for stability issue
-Compiled with HP Pro SuperSonic ToolChain for maxium Performance, snappiness and fluidity
Compiled with HP Pro SuperSonic ToolChain.​
HP Pro SuperSonic ToolChain Features: (Based on GCC Linaro Sources)[/U][/B]
(-) Tegra specific optimization
(-) Toolchain Target flags has been optimized in same manner as the kernel drivers are written
(-) "Optimizing as the way program is written". I have overy observed all the codes by , as they're written and used same appropriate optimizations
(-) By observing codes 1st thing that comes in mind is Structures & Unions. Used Target Optimizations for it: '-fpack-struct and mstructure-size-boundary=32' for proper alignments of Structures and Unions for faster access
(-) fivopts for variable strength optimizations
(-) fforce-mem with fomit-frame-pointer for faster pointer access
(-) Except tegra codes most of the kernel codes have inlined functions. All functions inlined for faster access of codes. By inlining functions it can be accessed as fast as macro
(-) Code assembly and linking with ArmV7-A architecture's Cortex-A9 cpu's Virtulizations, Integer Division Float and Multi-Processing CPU Extensions
(-) CortexA9 Processor has support for Array Prefetching same like windows does SW based Prefetch. This CPU features during runtime loads longer arrays in advance in CPU memory via AX/BX registers. Which can significantly improve runtime execution and overall snappiness. Target toolchain optimized with array-prefetch optimizations to compile codes with array pre-fetch instructions
(-) By observing Tegra and LG drivers, there are very few short loops, which needs no optimizations, thus graphite loop optimizations disabled.
(-) LTO( Link Time Optimizations) for removal of unused codes during linking stage and re-sections of functions and data for faster access
(-) As armv7-a architecture supports Unaligned Access, instead of disabling, its optimized with 8K access
(-) This is the same toolchain that has been used since 5 months to speedup SuperSonic Test builds for Stock Kernel. No extra blind optimizations used for issue of stability but only as drivers and kernel codes are written "Target specific optimizations" for maxium possible performance
(-) toolchain: Complete set of Used CFLAGS_FOR_TARGET: -O0 -finline-functions -fpack-struct=8 -mstructure-size-boundary=32 -fpreferch-loop-arrays -fivopts -fforce-mem -fomit-frame-pointer CFLAGS_FOR_BUILD: -O0 -march=atom -mtune=atom( as my cpu is atom) Cflags:-O0 -finline-functions
Download
OC Version: https://www.dropbox.com/s/1byhged9oqw5a6n/HP_Pro_SuperSonic_SR4R_OC.zip
No-OC Version: https://www.dropbox.com/s/uvnq7fppcsd8z7e/HP_Pro_SuperSonic_SR4R_No-OC.zip
BIG THANKS TO SUPERSKILL & SHREEPRAJAY FOR PROVIDING ALL HP KERNEL MIRRORS WORKING LINK, IF ANYBODY ELSE HAS ALSO MIRRORED PLEASE PM ME THE LINKS
Downlaod HP Krnls(Latest Build is SR3R2/R:
https://www.box.com/s/5995c4bdcf9abb4e375f
Download HP Performance Packs
https://www.box.com/s/d2a5c32bd3cc0e5d174f
An APP To Control On-The-Fly features of RC12, A Big Thanks to Developer Keshav0001, Who without saying Created an application and still progressing, He is New to XDA as needed 10 or more posts:
Downloads:
search in Market "HorsePower 2x OTF Kernel Tweaker"
Horse Power 2x eXtreme 16/24/32BPP RC12-R(RC Release)​
This kernel is based on LG V20Q sources. This kernel is competible and should only be flashed with STOCK MCR FROYO and GINGERBREAD. NOT COMPETIBLE WITH CM AND MIUI
Cryptic Changelogs History:
PHP:
Code:
+Fixed core cpu memory leak
+ Fixed group scheduler"s cpu memory leak, no need to restart phone every 100 hours.
+[B][U](SR3R2)[/U][/B] Reverted to original BackLight drivers as request of many users [B][U](SR3R2)[/U][/B]
+[B][U](SR3R2)[/U][/B] Fixed missing codes in PowerSave [B][U](SR3R2)[/U][/B]
+[B][U](SR3R2)[/U][/B] Fixed with NoOC Version without compcache [B][U](SR3R2)[/U][/B]
+[B][U](SR3R)[/U][/B] Fixed missing definition of CPU memory leak. After hours by hours, days by days more smoothness w/o slow down due to memory leak [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] Full SMP support, enhancing Real Time Dual Core Performance for Multi-Tasking And activated PowerSave profile 4,5,6 [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] Full IP Tables supported, by an upgraded IP Tables [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] Included farajep's backlight driver (Thanks to farajep for making source available) [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] Quick responsiveness and smoothness like SR3 [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] Longest battery performance [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] Fixed freeze, no need to apply +mV patch. One version for all devices [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] Fast WiFi browsing [B][U](SR3R)[/U][/B]
+[B][U](SR3R)[/U][/B] More smooth scrolling [B][U](SR3R)[/U][/B]
+[B][U](SR3)[/U][/B] Introducing OTF V2.0 including Strong Vibrator OTF Function and many bug fixes. To activate strong vibrater just set value "1" in /data/spica/strong_vibe and save, Instantly strong vibrator driver will be activated. To enable boot time Strong Vibrator support set value "1" to /data/spicabootcfg/strong_vibe. For +mV versions and BPP patch InstallKernel first than apply patches for that reffer post #2 after this [B][U](SR3)[/U][/B]
+[B][U](SR3)[/U][/B] Fixed EndCall BSOD(Thanks to Vadonka) [B][U](SR3)[/U][/B]
+[B][U](SR3)[/U][/B] Extra responsiveness with Low Latency Realtime Processing [B][U](SR3)[/U][/B]
+[B][U](SR3)[/U][/B] Mega Smooth UI performance and Rock Solid Stability [B][U](SR3)[/U][/B]
+[B][U](SR3)[/U][/B] Longest battery life. 2 versions available one with my modded battery driver and another with DS battery driver(jumpy-funky reading but long battery life) (Thanks to DS available sources) [B][U](SR3)[/U][/B]
+[B][U](RC12-R)[/U][/B] Longest battrery performance on v20q source kernel with RevisedOTF PowerSave functionality [B][U](RC12-R)[/U][/B]
+[B][U](RC12-R)[/U][/B] Mega Smooth UI Smoothness, You'll really be amazed by never seen smoothness [B][U](RC12-R)[/U][/B]
+[B][U](RC12-R)[/U][/B] RockSolid Stability [B][U](RC12-R)[/U][/B]
+[B][U](RC12-R)[/U][/B] Fully Functional Spica Revised OTF Pack, Lesser freeze free re-mastered values for powersave, gentle yet effective, Selected target values for powersave to significantly reduce battery drainage, PowerSave profile 1-6 (tutorial soon to be written) [B][U](RC12-R)[/U][/B]
+[B][U](RC12-R)[/U][/B] Fixed InCall BSOD previously reported with TestBuilds [B][U](RC12-R)[/U][/B]
+[B][U](RC12-R)[/U][/B] By default screen off max freq setted to 503 Mhz as always, You can exclusively play with different values On-The-Fly with RevisedOTF Functionalities for music listenings w/o distortion or for incoming call as per your needs by setting MaxScreenOff CPU freq values of choice by GUI Application (Thanks to Kaunshik001) or by writing values to /data/spica/maxscreenofffreq. No need to reply on pre-set values. [B][U](RC12-R)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly Pack, Exported many HW controlled values from static to dynamic at userspace level (Originally I was inspired by the the concept of Xmister)([B]Credits to Xmister[/B])[B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly VDEFREQ/GPUFREQ/MINCPU1ON/MAXCPU1OFF/SUSPEND_CORE_MV/POWERSAVE/NITROS/SCREENOFFMAXFREQ/DDR2_MIN_KHZ/LPDDR2_MIN_KHZ Support. No need to reboot/restart daemon. It works on kernel syscalls. It takes effect in notime.[B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly [B]VDEFREQ [/B]change support. Responsible file is located in /data/spica/vdefreq & /proc/spica/vdefreq. You can change the value in any of these both files. I preffer user-friendly /data/spica/vdefreq. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is 600000. Supported Values in between 600000-700000. Any values above 600000 will OC it w/o increasing supplying voltage. For safety concern no values except in range will be accepted. To enable boot-time support select values in /data/spicabootcfg/vdefreq [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly [B]GPUFREQ[/B] change support. Responsible file is located in /data/spica/gpufreq & /proc/spica/gpufreq. You can change the value in any of these both files. I preffer user-friendly /data/spica/gpufreq. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is 280000. Default value is 300000 Supported Values in between 280000-350000. Any values above 280000 will OC it w/o increasing supplying voltage. For safety concern no values except in range will be accepted.To enable boot-time support select values in /data/spicabootcfg/gpufreq [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly [B]MINCPU1ON[/B] freq change support. Means during upword scaling at what freq 2nd core will be activated. Responsible file is located in /data/spica/mincpu1on & /proc/spica/mincpu1on. You can change the value in any of these both files. I preffer user-friendly /data/spica/mincpu1on. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is what you see after boot. Supported Values in between 216000-1100000. Default value of spica kernel is 810000 For safety concern no values except in range will be accepted.To enable boot-time support select values in /data/spicabootcfg/mincpu1on [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly [B]MAXCPU1OFF[/B] freq change support. Means at what max freq 2nd core will be off during returning phaze. Responsible file is located in /data/spica/maxcpu1off & /proc/spica/maxcpu1off. You can change the value in any of these both files. I preffer user-friendly /data/spica/maxcpu1off. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is what you see after boot. Supported Values in between 216000-1100000. Default value of spica kernel is 860000 For safety concern no values except in range will be accepted.To enable boot-time support select values in /data/spicabootcfg/maxpu1off [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly [B]MaxScreenOffFreq[/B] support. Means During screen off what will be the max freq.Responsible file is located in /data/spica/screenoff_maxcpufreq & /proc/spica/screenoff_maxcpufreq. You can change the value in any of these both files. I preffer user-friendly /data/spica/maxcpu1off. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is what you see after boot. Supported Values in between 216000-999000. For safety concern no values except in range will be accepted.To enable boot-time support select values in /data/spicabootcfg/screenoff_maxcpufreq. [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly [B]DDR2 MINIMUM FREQUENCY[/B] support. It's theminimum frequency of DDR2(SDRAM).Responsible file is located in /data/spica/ddr2_min_khz & /proc/spica/ddr2_min_khz. You can change the value in any of these both files. I preffer user-friendly /data/spica/ddr2_min_khz. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is what you see after boot. Supported Values in between 10000-50000. Default value is 50000 For safety concern no values except in range will be accepted.To enable boot-time support select values in /data/spicabootcfg/ddr2_min_khz. [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly[B] LPDDR2 MINIMUM FREQUENCY[/B] support. It's theminimum frequency of LPDDR2.Responsible file is located in /data/spica/lpddr2_min_khz & /proc/spica/lpddr2_min_khz. You can change the value in any of these both files. I preffer user-friendly /data/spica/lpddr2_min_khz. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is what you see after boot. Supported Values in between 1000-18000. Default value is 18000 For safety concern no values except in range will be accepted.To enable boot-time support select values in /data/spicabootcfg/lpddr2_min_khz. [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] On-the-fly [B]SUSPENDED CORE VOLTAGE SUPPLY[/B] support. It's theminimum frequency of CORE VOLTAGE WHEN Core is in suspend state.Responsible file is located in /data/spica/suspend_core_mv & /proc/spica/suspend_core_mv. You can change the value in any of these both files. I preffer user-friendly /data/spica/suspend_core_mv. Edit values with ES file explorer and just save file. No need to change permissions. It takes effect instantly. Default value is what you see after boot. Supported Values in between 600-1000. Default value is 1000 For safety concern no values except in range will be accepted.To enable boot-time support select values in /data/spicabootcfg /suspend_core_mv. [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] Dynamic On-The-Fly '[B]powersave'[/B] profile. Which accepts value from '0' to '6'. During 'powersave' kernel smartly adjust various thresholds of voltage to lower possible values. "0' value means disable(Defult) "1" light powersave "2" moderate powersave "3" aggressive powersave "4" Profile "1" during screen off "5" Profile "2" during only screen off "6" Profile "3" during screen off only(POWERSAVE doesnt touch UV). Make sure 'nitros' mode disable aka value '0' Responsible file location /data/spica/powersave and boot time file location /data/spicabootcfg/powersave [B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] Dynamic On-The-Fly "[B]Nitros[/B]" -"Performance" mode. It accepts two values, "0" Disable "1"Enable. During "Nitros" Profile Kernel sets max fail-safe values (It doesnt touch OC). File location /data/spica/nitors and boot time file location /data/spicabootcfg.Make sure 'powersave' is disabled aka value '0'[B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] V20Q Sources merged[B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] Slight loud crystal clear volume in headphone[B][U](RC12)[/U][/B]
+[B][U](RC12)[/U][/B] Optimized SCHED_RR & SCHED_FIFO[B][U](RC12)[/U][/B]
+[B][U](RC11-R)[/U][/B] Fixed CpuFreq of 2nd Core not syncing with 1st core's cpufreq. NOW Very quicker 2nd core activation and very quicker 2nd core suspension. Thus fastest realtime resposnses and excellent reduced battery drainage. Standby battery drainage with OC/UV ~1-2mA [B][U](RC11-R)[/U][/B]
+[B][U](RC11-R)[/U][/B] Re-injected Compcache and removed ZRAM [B][U](RC11-R)[/U][/B]
+[B][U](RC11-R)[/U][/B] Modified Deadline Scheduler's FIFO parametrs to 20 instead of 16 for quicker response [B][U](RC-11R)[/U][/B]
+[B][U](RC11)[/U][/B] More snapier, stable and performance oriented [B][U](RC11)[/U][/B]
+[B][U](RC11)[/U][/B] Featuring ZRAM/(Previously known as CompCache) HW Compressed RAM with SWAP_FREE_NOTIFY feature [B][U](RC11)[/U][/B]
+[B][U](RC11)[/U][/B] Fixed freeze issue by re-compiling GCC HardFolat ARM tool chain [B][U](RC11)[/U][/B]
+[B][U](RC11)[/U][/B] OC/UV & VOODOO remerged [B][U](RC11)[/U][/B]
+[B][U](RC10)[/U][/B]Removed LG's lowmemorykiller.c and added same modified by me for assured oom optimal functionality with no possible memory leak[B][U](RC10)[/U][/B]
+[B][U](RC10)[/U][/B]Longest battery performance among all HP KRNLS. Extended battery life[B][U](RC10)[/U][/B]
+[B][U](RC10)[/U][/B]NVMAP enabled to kill processes envoked by GPU to assure GPU mem functionality without allocation of static GPU memory[B][U](RC10)[/U][/B]
+[B][U](RC10)[/U][/B]Enabled Android pMem functionality[B][U](RC10)[/U][/B]
+[B][U](RC10)[/U][/B]Patched tegra framebuffer to allow pseudo color palate support on same x,y axis with >/= 16 bits support[B][U](RC10)[/U][/B]
+[B][U](RC10)[/U][/B]Quicker apps response[B][U](RC10)[/U][/B]
+[B][U](RC10)[/U][/B]Extended most efficious multi-tasking[B][U](RC10)[/U][/B]
+[B][U](RC10)[/U][/B]ARM Hard Float VFP support. Compilation along with ARMHF tool chains[B][U](RC10)[/U][/B]
+[B][U](RC9)[/U][/B] Fully based on Official released V20L sources, Merged all HP kernel changes since beta to RC8 with V20L[B][U](RC9)[/U][/B]
+[B][U](RC9)[/U][/B]More optimized scheduling, Quicker APP response and More smooth UI (Taken from SR3 Test release)[B][U](RC9)[/U][/B]
+[B][U](RC9)[/U][/B]Fixed wifi with dynamic msallocation (Taken from SR3 Test build)[B][U](RC9)[/U][/B]
+[B][U](RC9)[/U][/B]More optimized for power saving (Taken from SR3 Test build)[B][U](RC9)[/U][/B]
+[B][U](RC9)[/U][/B]SMBFS file system support as a module (Taken from SR3 Test build) [B][U](RC9)[/U][/B]
+[B][U](SR2)[/U][/B] Power Saving optimizations [B][U](SR2)[/U][/B]
+[B][U](SR2)[/U][/B] More optimized for smoother responce [B][U](SR2)[/U][/B]
+[B][U](SR2)[/U][/B] Merged changes of RC7 & RC8 without JRCU daemon[B][U](SR2)[/U][/B]
+[B](RC8-Revised)[/B] Fixed EMC core UV issue and Max OCed reverted back to 1408Mhz[B][U](RC8-Revised)[/U][/B]
+[B][U](RC8)[/U][/B] JRCU as daemon support[B][U](RC8)[/U][/B]
+[B][U](RC8)[/U][/B] OCed upto 1.55 Ghz Normal Vibrator Version[B][U](RC8)[/U][/B]
+[B][U](RC8)[/U][/B] More possible optimizations for lesser battery drainage[B][U](RC8)[/U][/B]
+[B][U](RC7)[/U][/B] Watchdog Support added: Tegra ODM Watchdog support as a module[B][U](RC7)[/U][/B]
+[B][U](RC7)[/U][/B] SDRAM related EMC core voltage undervolted to -50mV[B][U](RC7)[/U][/B]
+[B][U](RC7)[/U][/B] More possibly optimized for better possible battery[B][U](RC7)[/U][/B]
+[B][U](RC7)[/U][/B] Max OC frequency back to 1.4Ghz[B][U](RC7)[/U][/B]
+[B][U](SR1)[/U][/B] Strong Vibrator driver, Both version availibility with Strong Vibrator driver and with Default vibrator driver [B][U](SR1)[/U][/B]
+[B][U](SR1)[/U][/B] Best hand-picked stuff from RCs, Default frequencies of CPU towards 1.4Ghz[B][U](SR1)[/U][/B]
+[B][U](SR1)[/U][/B] Assured Stability, Better Performance and energy-saving battery performance[B][U](SR1)[/U][/B]
+[B][U](RC6)[/U][/B] TEMP info fixed[B][U](RC6)[/U][/B]
+[B][U](RC6)[/U][/B]Minor debug clean-ups[B][U](RC6)[/U][/B]
+[B][U](RC6)[/U][/B] In-call volume mute issue in Froyo fixed[B][U](RC6)[/U][/B]
+[B][U](RC5)[/U][/B] OCed upto 1.5Ghz, New freq steps 216,389,655,816,1015,1216,1408,1504[B][U](RC5)[/U][/B]
+[B][U](RC5)[/U][/B] Declaration of NVODM FULL VOLTAGE in mV undefined ,Depends now on FUSE functionality .Low and Critical NVODM voltage in mV selected 9400 & 8800 respectively in NVODM initialization file[B][U](RC5)[/U][/B]
+[B][U](RC5)[/U][/B] All Kernel drivers from SU660 GB sources except power,odm_kit,base,nvos fixed for the competibility and merged[B][U](RC5)[/U][/B]
+[B][U](RC5)[/U][/B] "Anticipatory" I/O scheduler as mainline scheduler[B][U](RC5)[/U][/B]
+[B][U](RC5)[/U][/B] Compiled with GCC-4.6.2 Linaro tool chain with Voku's favourite -Ofast flags. Removed tegra specific flags and added ARM standard graphic optimized flags for cortex-a9. CFLAGS_KERNEL and MODFLAGS: -Ofast -pipe -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=vfpv3-d16 -mfloat-abi=soft -floop-block -floop-interchange -floop-strip-mine -ffast-math -funsafe-loop-optimizations -funsafe-math-optimizations -fbranch-target-load-optimize2[B][U](RC5)[/U][/B]
+[B][U](RC4)[/U][/B] Dual SPI drivers supporting HSPA+ from su660[B][U](RC4)[/U][/B]
+[B][U](RC4)[/U][/B] Wifi modules fixed for re-loading issue and Quicker connect after several hours (Needs testing)[B][U](RC4)[/U][/B]
+[B][U](RC4)[/U][/B] Regluator & RTC drivers from SU660[B][U](RC4)[/U][/B]
+[B][U](RC4)[/U][/B] Battery driver reverted to modified RC1 driver[B][U](RC4)[/U][/B]
+[B][U](RC3)[/U][/B] Featuring BPP(Bits-Per-Pixel) On-The-Fly Support, select bits in init.d/bpp file and reboot[B][U](RC3)[/U][/B]
+[B][U](RC3)[/U][/B] Modified star_battery_charger.c to allow extra-voltage charge [B][U](RC3)[/U][/B]
+[B][U](RC3)[/U][/B] Some drivers previously merged from SU660 reverted as of no visible improvement , And new NVOS NVDDK CORE drivers merged from SU660[B][U](RC3)[/U][/B]
+[B][U](RC3)[/U][/B]SCHED_FIFO optimizations for quicker SCHED operations [B][U](RC3)[/U][/B]
+[B][U](RC3)[/U][/B]Voodoo and missing batt temp in RC2 fixed with RC3[B][U](RC3)[/U][/B]
+[B][U](RC3) [/U][/B] More optimized SCHED_OTHER & SCHED_RR/FIFO for optimum I/O operation[B][U](RC3)[/U][/B]
+[B][U](RC 2)[/U][/B]NEW released su660's V20D GB kernel sources' WLAN module, MMC, USB, I2C, MTD, SPI, NVRM, NVODM, ODM_KIT, STAR, POWER dirvers fixed for the competibility and merged[B][U](RC 2)[/U][/B]
+[B][U](RC 2)[/U][/B]Ext2 support enabled.[B][U](RC 2)[/U][/B]
+[B][U](RC1)[/U][/B] Fixed pre-mature reboots on Terminal Emulator, USB debugging, Script Manager, Compeitble with Andrev OC Daemon APP, fixed reboot on restart daemon service.[B][U](RC1)[/U][/B]
+[B][U](RC1)[/U][/B] Optimized for Quicker APPs response[B][U](RC1)[/U][/B]
+[B][U](RC1)[/U][/B] 32BPP/24BPP Tegra-FB enabled kernel. For 32BPP, Enabled Virtual A8R8G8B8 32BPP to 24BPP to 18BPP panle color with changed RGB and Transperency OFFSET and LENGTH[B][U](RC1)[/U][/B]
+[B][U](RC1)[/U][/B] Heridant topogigi's vold.fstab in installation zip file, for preventing unmounted SD issue on other ROMs [B][U](RC1)[/U][/B]
+[B][U](RC1)[/U][/B] tocuhscreen fix credits to pastime[B][U](RC1)[/U][/B]
+[B](Beta1.1)[/B] Re-strctured modded battery driver with Beta1. OverHeat suspenstion now supports 410-550 TEMP instead of 450-550. Assured up-to 50% lesser battery drainage. Battery driver now supports scaling through 3360 to 4182 mv instead of 4150mv[B].(Beta1.1)[/B]
+Mega-smooth UI Fluidity/smoothness and higher benchmarks
+Quicker UI and/or APP responsiveness
+Efficient multi-tasking
+OC/UV Codes merged from Cpsjuste Sources([B]Thanks cpsjuste ,impertius sources available[/B])
+Voodoo codes from [B]Supecorio[/B] sources(Thanks)
+Ext4 supported
+Competible with V20 l/j/g/i/c/e/q/p/o/l/m And Froyo MCR
If you appreciate my work than feel free to Support My O2x Development
Recommendation:
-Battery calibration. After calibration let it disachrge full for the first time then full charge. Then you're ready to go! Full discharge needs to be done ONLY ONCE after calibration.
Procedure:
-charge phone full when its off, start phone. Charge till it shows full status. Charge more for 15mins untill you see battery voltage at 4182mv. Then calibrate battery with Battery Calibration App.
HP TB Sources: https://github.com/spica234/HP-TestBuild-Repo-upwords-Sr3R
HP 2x Kernel Sources since RC1 to Sr3R2: https://github.com/spica234/HP-2X-V20Q
HP 2x Deprecated Sources since RC1 to RC11 https://github.com/spica234/HP-Krnl-2.6.32.9
revOTF Patch Attached in the post!

Various Patches
+10mV Patch:
http://www.box.com/s/5vbo951za4x0yyx9jvn8
+15mV Patch:
http://www.box.com/s/ei3elm0d7ey30a2pbfvh
BPP Patch Default 24BPP:
http://www.box.com/s/3ikgfufphfb3bl5x7805

Flashing now! What are the differences from the first beta in Topogigi's thread?
Ah: "And I've released beta1.1 with major battery fix and more UI responsiveness".
Great

wapz said:
Flashing now! What are the differences from the first beta in Topogigi's thread?
Click to expand...
Click to collapse
Knwon issues are persistent. Got not much time for it. But it has been overall optimized for more fluid UI responsiveness and more efficient lesser battery drain. this time modded battery driver lessens battery drains and consumptions more than previous test versions.

Thanks for your work!!!

Just flashed beta 1.1 on Topogigi 1.9, will report if i notis any bugs.
A huge tanks to u and all other devs that has finally made me happy white my hardware.
Sent from my LG-P990 using xda premium

Thanks , something new to play, yeahhh

The kernel version is listed correctly now as well

Yes
wapz said:
The kernel version is listed correctly now as well
Click to expand...
Click to collapse
Sent from my LG-P990 using Tapatalk

beta1 in standby (3G, wifi off) use my battery 1-2mA
very GOOD!!!

that is extremely low, nicee

for most efficient effect you need battery calibration as we ve different battery driver this time
PAIIITET said:
beta1 in standby (3G, wifi off) use my battery 1-2mA
very GOOD!!!
Click to expand...
Click to collapse
Sent from my LG-P990 using Tapatalk

i know this dev from samdroid.net (galaxy spica) and i have to say...he's good

At 22% now, will start full recharge too 100% and wipe stats.

Charge full first during phone is off. Then start phone and charge to 100% full status shown , wait till more 15mins 15 minutes more till you see 4182 mv . Then calibrate battery via battery calibration app.
wapz said:
At 22% now, will start full recharge too 100% and wipe stats.
Click to expand...
Click to collapse
Sent from my LG-P990 using Tapatalk

Hey man nice to c u inhere i miss spica still:/ you got lg 2x?
ker0ltjuh said:
i know this dev from samdroid.net (galaxy spica) and i have to say...he's good
Click to expand...
Click to collapse
Sent from my LG-P990 using Tapatalk

So this kernel reduces battery drain upto 50%? Lets say I do happen to do something wrong, I can always smart flash right?

Does GPS work for you mates, or this is Topo's ROM problem?

downloaded, installed without any problems and now to test the battery, thanks for the work spica

You can restore if youve backed up
Soulj4h said:
So this kernel reduces battery drain upto 50%? Lets say I do happen to do something wrong, I can always smart flash right?
Click to expand...
Click to collapse
Sent from my LG-P990 using Tapatalk

[ROM] [4.3] [HALO 2.0] EnergyROM 1.0 - Energy

EnergyROM 1.0 on JB 4.3 for GS III
Changelog
Code:
[SIZE="4"][list]Based on the awesome SuperNexus ROM by farjaab
[*]Build.prop improvements
[*]Android performances improved at 360°
[*]Radically improved management ram on android (Lags...adios!)
[*]Script lightweight and revised to be adapted to this engine
[*]Improves a lot the graphics: of course Pure Graphic™HD, Pure Dithering Plus™ and... AOSPA 3.60 system tweaks
[*]Scan multimedia time drastically reduced
[*]Network Improvements, 3G experience even in 2G modality
[*]All SQlite database optimized
[*]Enable hardware features turned off by default for a better experience on entry level devices
[*]Greatly increases the score AnTuTu: Try it to believe it!!
[*]Reduces the startup time of Android
[*]A version for stock rom and one for CM, to squeeze any roms!
[*]Allows you to play ported games without lags
[*]Cleans the system every 24 hours, thecache every week and the Dalvik every month (cronos easter egg)
[*]Automatically Zipalign on each boot (sensitive to the user)
[*]Drastically decreased the drainage of battery
[*]Check the activities that consume too much battery stop them with PureWakelocks™
[*]When the phone is charging reduces system services for faster charging
[*]The battery is calibrated on every boot
[*]Disable animation of the system when the battery is nearly exhausted
[*]Improvements in build.prop as regards the part of consumption
[*]Enables a non-aggressive dithering to save CPU
[*]When you lock the device, the engine makes sure that the GPU is turned off
[*]Enables deep sleepalso in the bugged rom
[*]Parts of bravia engine
[*]Of course parts of CrossBreeder (credits to dev)
[*]Of course parts of Adrenaline Engine (credits to dev)
[*]Of course PureGraphics HD, even though I already told you
[*]Of course V6 supercharger
[*]Generates video entropy (like seeder)
[*]Slightly improves the scaling of the frequencies (for better results you need a good kernel)
[*]Lightens the load on the CPU switching the workload to GPU rendering
[*]Enable the swap partition in Android (experimental)
[*]CrossBreeder
[*]Adrenaline Engine
[*]Smooth - Fast - Incredible !
[*]Clear sound
[*]No more track noise
[*]Beats™ Audio by Dr.Dre
[*]Audio Pure™ Control not to damage your hearing
[*]Also compatible with the headphones that don't support audio render of 60kHz
[*]Where possible, arrange for the conversion of the songs (in background) below 256 kbps to 320kbps
[*]During playback of songs / sounds make a soft frequency scaling to reduce noise and highlight the track
[*]It offers more powerful and closed bass
[*]Efficient even with stock headphones
[*]Improves a lot the audio call
[*]Enhance the speakers for playing music without headphones in high quality[/size][/list]
Flash Procedure
Code:
[size=4][list]Download [url=http://www.mediafire.com/download/bntttb9uuybfcgo/GT-i9300_EnergyROM_build1.zip]ROM[/url] and [url=www.goo.im/gapps]GApps[/url]
[*]Go CWM
[*]Wipe Data
[*]Wipe Cache
[*]Wipe Dalvik Cache
[*]Install zip - ROM
[*]Install zip - GApps
[*]Reboot[/list][/size]
Thanks to........
Code:
[size=4][list]farjaab for his awesome SuperNexus ROM
[*]Jeeko for PurePerformance and PureAudio
[*]Me[/list][/center][/size]

Screenshoots

Reserved

Rserved

looks interesting
:good:

Super...

Is not it possible using CM themes in this Rom? Can you port it if its easy?

Hi,
on CM 10.2 nightly we all see battery drain in idle especially when you place call - the batt drain disappear after reboot. How is the battery with this rom?

Logcat
It seems that logcat is disabled. Any way to enable it? Thx

yken said:
Is not it possible using CM themes in this Rom? Can you port it if its easy?
Click to expand...
Click to collapse
Unfortunately not....but this is still an alpha build....next buiild will include themes
No Problem

can you add nav bar, navbar long press, nav bar height, ring shortcuts ?

* ViPER|Audio || ViPER|Atmos || ViPER|DD+ 4.8/5.5 * Driver * Stock * Sony * Beats *

ViPER|Audio™ || ViPER|Atmos™
ViPER|DD+™​Stock | Sony™ | Beats™
Universal​
for 5.x.x - 6.x.x.​
Est. 12/09/2015​Tested first on Nexus 6​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Got a Nexus 6 and want to try the very first official rom with ViPER|Atmos™ fully injected with no root whatsoever?
Become part of ViPER4Android history and flash the rom at the link below:
http://forum.xda-developers.com/nexus-6/development/rom-stock-debloated-deodexed-n6-t3318315
Not on Lollipop or Marshmallow?
Here is the link to my AndroidFileHost JB & KK folder:
https://www.androidfilehost.com/?w=files&flid=48267​
Features:
5.x uses ViPER4Android 2.4.0.1 with its driver preinstalled
4.x uses ViPER4Android 2.3.4.0 with its Super Quality driver preinstalled
Dark Material theme
Works in Permissive and Enforcing Selinux
Works with no root as long as a Permissive kernel is installed
Installed in /system/priv-app
Advanced Linux Sound Architecture
Sony™ and Beats™ libraries and effects (No apk's or settings to look for!)
Library & Effect entries in /system/ect/audio_effects.conf, /system/vendor/etc/audio_effects.conf, /vendor/etc/audio_effects.conf, and /system/etc/htc_audio_effects.conf
Five custom audio_effects.conf files for the Sony™ Beats™ Editions
Deep Buffer removal from /system/etc/audio_policy.conf
Backup script to survive rom updates
Official ViPER Packages​
ViPER|Audio™ is for those only wanting ViPER processing. There is also a Stock version that has no additional files or effects for those seeking a pure "vanilla" ViPER4Android installation.
ViPER|Atmos™ includes @worstenbrood's Dolby Atmos™ found here: http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446, fully functional in Enforcing. There is also a Stock version without the additional effects for a pure "vanilla" ViPER|Atmos™ experience.
ViPER|DD+™ includes Dolby Digital Plus™ courtesy of @aki_007 which can be found here: http://forum.xda-developers.com/android/software/audio-mod-dolby-digital-plus-universal-t3078802 and is the perfect solution for those experiencing issues with the Dolby Atmos™ app. Both are fantastic and extremely similar in sound and identical in setup. This is certainly not a downgraded ViPER|Atmos™ but just another available option for the user. Dolby Digital Plus™ requires a Permissive Selinux environment so packages including DD+™ also include a Permissive script during the installation to avoid any issues after the installation. There is also a stock version without the additional effects.
These three versions provide the ultimate compatibility across all devices in your quest for the ultimate experience in seamless sound enhancement.
!! Versions not described above are just for fun !!
!! Make sure /system has 50mb+ of available free space !!
!! If it is necessary for you to run Cyanogenmod 13 with its own SuperUser you must change Selinux from Enforcing Strict to Permissive as SuperSU is required for processing in Enforcing !!​
Installation:
Boot to recovery
Wipe > Advanced > Dalvik Cache, Cache
Install > ViPER|Audio™ OR ViPER|Atmos™ OR ViPER|DD+™
Reboot
!! Be sure to enable Storage Permissions for ViPER4Android through its App Info page !!​
Open v4a
Menu > Show Notification (block if desired by long pressing notification)
Menu > UI Setting > Expert
Menu > Save Effect Profile > New Effect Profile > "Stock" (this will help you find your working v4a directory)
Begin playing audio file
Open v4a
Uncheck Enable v4a
Check Enable v4a
If you experience problems with the normal installation instructions, the awesome @dr.ketan has allowed me to link his Viper Fix 1.1.apk which will essentially disable all other effects from your system by eliminating their libraries from your audio_effects.conf using v4a instead. Flash this apk as a normal user app, open, reboot when prompted, boot to recovery and flash your desired ViPER package. You can find info and support as well as the apk at this link: http://forum.xda-developers.com/showpost.php?p=61858278&postcount=3079
and
http://forum.xda-developers.com/showpost.php?p=63425983&postcount=658
It is possible your /system is dirty enough to require at least a System wipe in TWRP and a dirty flash of your current rom before flashing ViPER|Atmos™ if you experience any Force Closes or any other signs of an incomplete/failed installation.
!! Do NOT delete /system/priv-app/MusicFX !!
In initial testing I found that I had to move MusicFX back to get ViPER working and I haven't removed it since. I do disable it and recommend doing the same if it's not working "out of the box".
!! Audiophile™ Profile zip is NOT flashable !!
Extract both folders in zip into the following two directories:
Code:
/data/media/legacy/ViPER4Android
and
Code:
/storage/emulated/0/ViPER4Android
Uninstallation and Removal:
The best and easiest way to remove this and any other /system mod from your device is to dirty flash your rom after wiping System in TWRP. Before you begin, make sure you have a compatible rom zip on your internal storage as an OS will need to be installed. As long as you do not Factory Reset or check Data or Internal Storage, your data will be left intact but with a fresh /system partition.
Verify compatible rom zip is on device
Boot to recovery
Wipe > Advanced > System, Dalvik Cache, Cache
Mount > uncheck System
Install > current/compatible rom zip
Reboot
Audiophile™ ViPER|Audio™ Active Settings​
ViPER4Android™ > Enabled
ExtremeBeats™ Perfection EQ Preset > 3.5, 4.5, 5.0, 3.5, 1.5, 1.0, 3.5, 4.5, 5.0, 3.5 (Enabled when needed)
Convolver > Enabled
Impulse Response > DFX Hip Hop Modern.irs or DFX Metal Rap Big Bass.irs
Cross Channel > 0%
Dynamic System > Enabled (Headset only, when needed)
Listening Device > Common Earphone v2 (I use Sony™ MDR-XB90EX - http://www.amazon.com/gp/aw/d/B008G...ony+xb90ex&dpPl=1&dpID=41dggsErE4L&ref=plSrch
Dynamic Bass > 14%
ViPER Bass > Enabled
Bass Mode > Natural
Bass Frequency > 40hz
Bass Boost > 10db
ViPER Clarity > Enabled
Clarity Mode > Natural
Clarity > 6db
Experience ViPER|Atmos™ & ViPER|DD+™
ViPER4Android & Dolby Atmos™ - Enforcing and Permissive Selinux
ViPER4Android & Dolby Digital Plus™ - Permissive Selinux
When combined with ViPER running my Audiophile™ profile, optimal results can be achieved using the following settings in Dolby Atmos™ or Dolby Digital Plus™:​
Music profile
EQ Preset > Open (Flat to tame bass if needed)
Surround Virtualizer > Off
Dialog Enhancer > On
Volume Leveler > Off or On
The resulting sound is absolutely massive!
ViPER|Audio™ || ViPER|Atmos™ || ViPER|DD+™
Sony™ Beats™ Editions
The Xperia™ Z5 Premium Marshmallow audio system as well as the M7 Beats™ files shared by @androidexpert35 found here: http://forum.xda-developers.com/android/software/mod-htc-beats-audio-beats-xperience-t3281603, compliment ViPER|Audio™, ViPER|Atmos™, and ViPERDD+™ amazingly well. I was surprised how it fit in so seamlessly, adding a very welcomed and natural bass boost while retaining the Audiophile™ clarity. My favorite combination, by far.
Short List of Reference Songs Used for All Sound Profiling
Best processing when used with 16 bit 44.1 kHz FLAC sources. Sound quality degrades deviating up or down from this format. Trust me, I have DSD that play at 30mbps and more.​
Nero - Satisfy https://play.google.com/music/m/T3umvfdsg6nlsbyxiq7he7r5enu?t=Satisfy_-_Nero
Born of Osiris - Exhil∆r∆te https://play.google.com/music/m/Tbkw4olkiaj4ncvcuqimh6525oe?t=Exhilarate_-_Born_Of_Osiris
Bar 9 - The Beginning https://play.google.com/music/m/Tcdnzqm4nvitqtnxemjhb5dxwky?t=The_Beginning_VIP_Mix_-_Bar9
Stick Figure - Breathe https://play.google.com/music/m/Tf4jnzzlzx2vgqgpg6gqbckjrpe?t=Breathe_-_Stick_Figure
Tove Lo - This Time Around https://play.google.com/music/m/Tnwlggfz6k7rxth6lkpwympov74?t=This_Time_Around_-_Tove_Lo
August Burns Red - Echoes https://play.google.com/music/m/Txboufaitol43nwfehjwylplmii?t=Echoes_-_August_Burns_Red
August Burns Red - Black Sheep https://play.google.com/music/m/Ti4zm65ym6mfeb4leax6d7t7t6a?t=Black_Sheep_-_August_Burns_Red
Zomboy - Bad Intentions https://play.google.com/music/m/Tnojluypzn2cuirhwc4bhjohzdm?t=Bad_Intentions_Original_Mix_-_Zomboy
Liquid Stranger - Nintendo https://play.google.com/music/m/Tt3ngoekwqkzyre6bm4wlolew3u?t=Rocket_Fuel_-_Liquid_Stranger
All Shall Perish - There is No Business to be Done on a Dead Planet https://play.google.com/music/m/T5uq4qmmsrnepzwcztuzk6xmj4q?t=There_Is_No_Business_to_Be_Done_on_a_Dead_Planet_-_All_Shall_Perish
Crotchduster - Mammal Sauce https://play.google.com/music/m/T3szem6dbui32ghaiy2succx3uy?t=Mammal_Sauce_-_Crotchduster
Testing Environment​Headset
> Sony™ MDR-XB90EX http://www.amazon.com/MDR-XB90EX-In-Ear-Headphones-Japanese-Import/dp/B008G80FIU
Bluetooth
> Pioneer™ DEH80PRS http://www.amazon.com/gp/aw/d/B006Y...s=deh80prs&dpPl=1&dpID=41zvBwNuamL&ref=plSrch
> Focal™ Integration ISC 165 6.75" http://www.amazon.com/gp/aw/d/B0159...cal+isc165&dpPl=1&dpID=41eyRcNORfL&ref=plSrch
> Two unknown 6" subs in a ported box
> Old Kicker™ 2 channel 250 watt amplifier
That completes my service van setup where most testing takes place.
> Sony™ SRSX55 Portable Speaker http://www.amazon.com/gp/aw/d/B00TT...ny+srs+x55&dpPl=1&dpID=51sgE76lJzL&ref=plSrch
Some of your IRS files not active when loaded?
A discovery I made a long time ago that is still largely unknown:
For this to work ViPER4Android™ MUST be uninstalled from /data if applicable.​
If ViPER4Android™ still shows in App Drawer after dirty flashing your rom (while you're checking for free /system space and BusyBox ) then uninstall from App Drawer or delete /data/app/com.vipercn.viper4android_v2-1.
After flashing ViPER|Atmos™ or ViPER|Audio™, setting everything up, and confirming everything is functioning, extract the ViPER zip.
Tap on the apk in the extracted location to "install an update to this built-in application."
Tap Open and dismiss the only instance of "ViPER4Android has stopped" that you will see.
ViPER is now installed in /system and /data allowing you to enjoy every IRS in your collection.
In a situation where you could really use all the settings available to other outputs while processing through Speaker tab in ViPER4Android™?​Swipe over to output tab with the settings you seek to use.
Menu > Lock Effect Mode
Now, this locked output tab will be the only settings used while processing audio. Remember to unlock effect mode if this is only for certain scenarios when done.
Audio Focus causing processing issues?​I haven't had an opportunity to devote enough time testing audio_policy.conf edits but here's a couple that seem to help with no processing after audio interruptions:
Open /system/etc/audio_policy.conf in text editor
Add 44100 to voice_rx
Add 48000 to a2dp
Save changes
Reboot
Do this only if you experience no processing after a notification or voice call when ViPER4Android™ was processing immediately before the audio focus.
derekr44 said:
The audio_policy.conf edits worked. One thing to note (I found out through trial and error) is that the freqs need to be listed in numerical order on those line items (not just added to the end). For example:
Code:
sampling rates 8000|16000|44100|48000
is not seen the same as
Code:
sampling rates 8000|16000|48000|44100
Click to expand...
Click to collapse
Snapping or popping sounds? Upgrade your kernel's minimum frequency to 422mhz or higher (Nexus 6, device may vary) or switch to ondemand-based governor. See @wrongway213's post here for more info!
http://forum.xda-developers.com/showpost.php?p=65346831&postcount=6223
Experiencing audio disturbances while using a custom kernel? Our friend, @Woody explains:​
Woody said:
Back in the day, when Viper4Android started, it only worked on JellyBean 4.1 ROMs. This was when it was new and the iterations were just as fast as they are in this thread. Everything was finally figured out once Viper got to version 2.3.3.0 and then finally 2.3.4.0. Just about the same time that the final version of Viper was completed, KitKat came around with it's new experimental run time called ART. At that time, you could choose between either ART or the traditional Dalvik runtimes. But that choice came with a word of caution-"ART might not work with certain apks." At the same time, the Linux kernel was updated.
So now you have a SoundMOD that was reasonably perfected (and unfortunately abandoned as there has been no update since), a new Android OS and an updated Linux kernel that all needed to work together. Not saying that v4a was instrumental in a change of general ideology, but with so many people using it, many preferred sounds quality over battery quality. Let's not get all high and mighty on the Viper Is King train, as it was not the first to do what it does. If you've been around Android since Froyo/GB times, but more specifically the Galaxy S1/2 series, you should remember Supercurio's VoodDoo Sound Control. For the time, it blew anything away that was available and had a GUI apk that you could tweak. That was then, this is now; but really still talking in the KK days.
Since the sound mod was the greatest thing to headphones since aluminum, people wanted it to work on their custom ROMs/Kernels. In comes faux123 and his tweaks to his kernels that allowed for ramdisk injections of audio patches (generally AnyPatch kernels are what you will mostly find as it uses the "stock" ramdisk as a foundation). So if you ran a kernel during the middle 2013 to 2014, most had the Faux sound patch, as it allowed for peak sound for the device through the use of a custom kernel (this is why most kernels now days have a sound section in their .conf files or GUI). It lasted forever and is still being incorporated in custom kernels to this day (check your Kernel Thread OPs/GITs ). Since kernel devs are few and far between, they tend to either work closely together, cherry pick commits or try depart themselves from each other.
Android moves to Lollipop and ART is no longer optional, like in the previous KitKat. LP also introduced 2 kernel toolchain updates over it's lifetime. This caused kernel devs to tweak their setups and Governors. There were still the usual suspects like Interactive, On-Demand, Performance and Conservative, as well as all their derivatives. At this point sound mods were still working mainly because of the Faux sound and/or Franco patches were being included in most kernels and being built from AnyPatch kept that possible. Viper4Android worked as advertised, even after the /system folder structure had also changed).
Now comes MarshMallow. Again with another folder structure change and the adaptation of custom recoveries to be able to properly wipe them. Ever wonder why you can't find your Profile and Kernel folders when you dirty flash? I figured it out shortly after MM came out. The thing was, with the new OS, something in the kernel changed and now my trusted Interactive governor was creating popping and cracking sounds. I actually posted (should read the few posts after mine as well. They talk about Faux's sound too and my realization that On-Demand removes the popping and cracking) in this thread about it when it was under previous management by kah-el. Here are my final findings regarding using On-Demand over Interactive.
So what does this all mean? It means that if you have popping and cracking, you should switch your kernel governor to On-Demand or one of it's derivatives. Some other culprits can be if you are running a Permissive or Enforcing kernel and/or ROM. If you don't know if you are or not, open a terminal and type (without the quotes) "su" [ENTER] "setenforce" [ENTER] and see which number it puts out. 0=Permissive; 1=Enforcing. You can change this without the SELinuxpolicy changer apk by using the commands above. Some kernels, such as ElemetalX, have a radio button that you can tick at installation to have it as Enforcing or Permissive. Even though the latest zips from OP are getting more directed to being able to be used with Enforcing, it would be good for you to know what yours is. I run Permissive and will for the foreseeable future (Google it to find out why). You also need to check your gain strength and if it is set too high. Louder doesn't mean cleaner.
On-Demand isn't for everyone, but we have to find out why the Interactive governor ramps up the frequencies too fast and the audio portion of the kernel effects the output of Viper. This is something that a new kernel dev upstart could really make his mark in the Android custom kernel/sound mod world. *Hint*Hint* Until then, I don't mind On-Demand and SIO (I used to use Deadline but started to get RRs, though those were probably self-inflicted).
Click to expand...
Click to collapse
If using auxiliary port on Nexus 6, make this a routine:
(Since ViPER|Atmos™ testing this has not been necessary so far...)​Turn off ViPER Headset profile by unchecking Enable ViPER in Headset tab.
Slooowly insert auxiliary cord into phone port, if Google Voice Search opens that's even better, but not required.
Play desired audio file with desired audio player.
Open ViPER and turn ViPER Headset profile back on by checking Enable ViPER in Headset tab.
Feel free to share this wherever with whomever, no credit or permission needed as this is still the work of the developers below. If you feel obligated to give credit when sharing please include those below.​
Thanks to @viper520 & @zhuhang for the glorious ViPER4Android™.
Thanks to @worstenbrood for the Dolby Atmos™ dap_r6.5.zip and the necessary scripts inside which I was able to edit for this Installer.
Thanks to @aki_007 for Dolby Digital Plus™, providing more options for the user and allowing me to extend the compatibility range for devices that might have issues with Dolby Atmos™
Thanks to @BSDgeek_Jake for the highest quality IRS files on XDA - http://forum.xda-developers.com/showthread.php?t=2439254
Thanks to @maximumentropy for the updated Enforcing script for systemless root.
Thanks to @androidexpert35 for the fantastic Beats™ files for the Beats™ editions.
Thanks to @tupac4u for providing the perfect rom base for the ViPER|Atmos™ Edition Nexus 6 rootless rom.
Thanks to @dr.ketan for allowing me to link to his Viper Fix apk, useful when the normal ViPER installation doesn't work for you.
Thanks to @Viper4713 for the Material v4a apk's.
Thanks to @Hitti2 for the OP imagery.
Thanks to @-decipher- for the ViPER|Audio™ banner.
Thanks to you guys for always providing feedback and never settling for anything but the best!
And my biggest thanks to these generous donators!:
@joetheshmo X 2!
@Roi007leaf X 3!
@churapa
@dingermtb
@jesssiii
@ffejy462 X 2!
@Brock Guffman
@NullyOne
@luigidk
@derekr44
@elevatorguy
@heleos
@J.Guido85
@bkkzak
@Rhonin86
@Unclecharlo
@stueycaster
@deebray36 X 3!
@GODSPD
@williwood X 2!
@meckipower
@JellyTooth
@jshamoon
Mikko L. (guest)
Many thanks guys!! :good:
Enjoy the zips attached below and provide any feedback you have.​
Edit Archive:
Edit∆∆*******
4.3 is now using the Super Quality Driver to correct an oversight from I don't even know when. The Power Saving Driver file size is the exact same as the Super Quality Driver so somewhere along the way, it got mixed up and placed in the ViPER packages. The MD5 for the Super Quality Driver ends in "27a5" if you want to check libv4a_fx_ics.so on your device in /system/lib/soundfx.
Edit∆∆********
4.3.1 modifies the install script to accommodate every scenario of switching from different ViPER packages. No wipes necessary and no need to update unless you are wanting to try a different package. 4.3.1 also introduces the ViPER|DD+™ Stock version with no additional Beats™ and Huawei™ files.
Edit∆∆*********
4.4 introduces the phasing out of Huawei™ as part of the official packages as I was never fully convinced of any contribution, but highly suspect its inclusion caused many issues. All 4.4 packages include complete removal of Huawei™ files in the install script so no wipes are ever necessary. I don't plan on adding any Beats™ removal lines into the script as I fear that might delete stock files on HTC devices and that will certainly cause issues and be a very irresponsible act on my part. Essentially, this means a desire to try a Stock package will require a System wipe followed by a dirty flash of your rom before flashing a Stock package, otherwise, you'll still end up with the Beats™ files.
Edit∆∆∆
4.5.1 introduces the Xperia™ Z5 libraries and effects from @jancsessz's Xperia™ Z5 port as well as a change in the supolicy script pointing to /su/bin/supolicy for the latest SuperSU systemless root for full ViPER4Android functionality with Enforcing Selinux. 4.5.1 also begins the phasing out of the Beats™ only editions to keep a manageable number of packages.
Edit∆∆∆*
4.5.2 makes minor changes to the Supolicy script to make it compatible for all SuperSU users in an Enforcing Selinux environment (Thanks @Shadowghoster!). 4.5.2 also cleans the install script in all packages by removing the former Huawei™ removal lines which should no longer be necessary at this point. Users with a fully functional 4.5.1 installation should not feel compelled to update to 4.5.2, this is for everyone else or if you're flashing ViPER again because your rom update wiped your system in the installation process. Finally, Beats™ only editions will continue for those that have incompatibility issues with the other packages.
Edit∆∆∆**
5.0 includes the latest ViPER4Android 2.4.0.1 and its driver as well as a minor tweak to the Supolicy script
Edit∆∆∆***
5.1 brings Material Dark back to ViPER|Audio™ courtesy of @Viper4713's themed 2.4.0.1 apk. 5.1 also no longer removes ViPER4Android's /data/app installation or /data/data (app data) thanks to @-decipher-'s thorough testing and reports.
Edit∆∆∆****
5.2 returns the official ViPER4Android apk into all ViPER packages. This makes for a better flashing experience and the Material apk's can always be easily copied over the existing official apk if desired. 5.2 also includes /system/etc/sony_effect to all Sony™ Beats™ editions. Lastly, all 5.2 packages include a Version Info text file in /system and include more removal lines in the installation script for third party v4a installs including those included in some roms.
Edit∆∆∆*****
5.2.1 removes the /system/etc/sony_effect folder introduced in 5.2. A system wipe will be required to remove this folder as deleting through my installer might delete stock files on some Sony™ devices. Alternatively, this file can be manually deleted to avoid a system wipe if desired. 5.2.1 also removes the data removal of ViPER4Android during installation.
Edit∆∆∆******
5.3 adds the following lines to /system/build.prop:
audio.deep_buffer.media=false
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
lpa.releaselock=false
lpa.use-stagefright=false
persist.sys.media.use-awesome=1
Edit∆∆∆*******
4.6 continues work using the previous ViPER4Android 2.3.4.0 after reports of the new ViPER4Android apk being a downgrade in sound quality. This is not an unreasonable assumption given that the new apk only provides one compatible driver with no reference to its purpose being more sound quality driven or more power saving driven. I am testing this now and would have to say this is definitely the recommended version rather than 5.3 which uses the new apk. 4.6 also includes the /system/build.prop lines from 5.3 which have proven to be very beneficial to Audio Focus and curing all problems experienced with the supolicy scipt on Enforcing Selinux. Honestly, everything seems absolutely perfect and I can't see anything improving this build other than sound enhancements that are later found. :good:
Edit∆∆∆********
4.7.1/5.4 introduces Advanced Linux Sound Architecture into all packages. Dark Material returns with an available Light Material switcher flashable in recovery.
Click to expand...
Click to collapse
Edit∆∆∆*********
4.8/5.5 are rebased on Xperia™ Z5 Premium Marshmallow's audio system.
Using the entire Z5 Premium library with a custom audio_effects.conf incorporating only what is included in the mod.
Five custom audio_effects.conf locations and correct naming schemes which provide the most compatibility yet.
Sony Effect build.prop section.
Updating only requires the deletion of existing ViPER|Audio™ and Sony Effect build.prop lines if present to prevent duplicate entries.
XDA:DevDB Information
ViPER|Audio || ViPER|Atmos || ViPER|DD+
Contributors
guitardedhero
Version Information
Status: Stable
Current Stable Version: 4.8/5.5
Stable Release Date: 2016-03-15
Created 2016-03-04
Last Updated 2016-03-15
ViPER|Atmos™ ReDUX™ Test Build Resource​
Click to expand...
Click to collapse

I tried but couldnt get it to work. Audio just doesnt sound the same without it. Im hoping that when Im finally able to install it, the sound quality from the speakers will improve. It gets plenty loud, and I think it does a great job of sounding "surround", but I was hoping for the same sound quality as the M8s boomsound speakers.

User Content Area​
sonophilos said:
3/3/2016
Hey friends, Sonophilos here with an update:
You can update my Lover of Sound Profiles 5.2.1 to 4.7.1 as I have it set up with my suggested tweaks by changing the following:
Sonophilos-Speakers Profile: drop PlaybackAGC Max Output to -1.9Db (default) - was -1.0Db
Everything else is the same - smooth curve, +8.0Db Natural Bass, +8.0Db Natural Clarity, 0.0Db Output Gain
Sonophilos-Headphones Profile: drop PlaybackAGC Max Output to -1.9Db (default) - was -1.0Db
Drop Dynamic Bass to 16 Percent (was 20 Percent)
Everything else is the same - smooth curve, +8.0Db Natural Bass, +8.0Db Natural Clarity, -3.0Db Output Gain
With these settings at 8-9/15 volume "notches" (bearing in mind 10 is technically 100% on most devices, higher is pushing the limiter especially with audiofx like this) my speakers sound excellent and fill the room on the device speakers, my cheap desktop speakers or decent stereo alike;
in my Audio-Technica ATH-M50 s 8 volume is quite loud and isolating, 9 overcomes the sound of a dryer running next to me easily and 10 (highest before the Safe Headset Volume dialog comes up, I'm sure for good reason) it is absolutely deafening massive and crystal clear even at the peaks.
Update: the track I was testing the difference with. Massive and full-range sound. On A Brighter Note
I'm totally satisfied, @guitardedhero - thanks for your hard work!
Lover of Sound Profiles 4.7.1.zip is attached below.
2/29/2016
So after a couple sleepless nights of listening for every nuance of each build.prop from the XTREMEMusic project (some of which have already been suggested by other users and myself) I offer my refined tweaks and some reflections here:
Code:
# Make sure below enabled / added if not present
dev.pm.dyn_samplingrate=1
tunnel.audio.encode=false
audio.offload.gapless.enabled=true
audio.offload.buffer.size.kb=256
audio.offload.video=true
audio.offload.pcm.16bit.enable=true
audio.offload.track.enabled=true
audio.offload.passthrough=false
audio.offload.multiple.enabled=false
audio.offload.pcm.24bit.enable=true
# This is a multiplier - 4 = 4x48000Hz = 192KHz
# M9 has this by default, v4.7 adds this to ViPER section.
# Use only one - I comment out duplicate default props so these take priority
af.resampler.quality=4
# These are default on M9 - add if not present
htc.audio.global.state=0
htc.audio.global.profile=0
htc.audio.q6.topology=0
htc.audio.global.speaker=1
#
## ViPERAudio ##
#
audio.deep_buffer.media=false
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
lpa.releaselock=false
lpa.use-stagefright=false
persist.sys.media.use-awesome=1
# This is a multiplier - 4x48000Hz = 192KHz rate
persist.af.resampler.quality=4
# Separate from default resampling, use both
persist.dev.pm.dyn_samplingrate=1
# ALSA props for ViPERAudio 4.7
ro.sound.alsa=snd_pcm
AUDIODRIVER=alsa
ro.sound.driver=alsa
clock.allow_streaming_errors=false
# Changed this to "best" as XM project had it
default.pcm.rate_converter=samplerate_best
#
# XTREMEMusic Experimental Props #
#
audio.offload.track.enabled=true
# 16bit offload and track are required for DSEE
audio.offload.pcm.32bit.enable=true
# 32 and 64bit might have no effect but no issues
audio.offload.pcm.64bit.enable=true
# ALSA Mixer (Experimental - no issues yet)
alsa.mixer.playback.master=Speaker
alsa.mixer.capture.master=Mic
alsa.mixer.playback.earpiece=Earpiece
alsa.mixer.capture.earpiece=Mic
alsa.mixer.playback.headset=Headset
alsa.mixer.capture.headset=Mic
alsa.mixer.playback.speaker=Speaker
alsa.mixer.capture.speaker=Mic
alsa.mixer.playback.bt.sco=BTHeadset
alsa.mixer.capture.bt.sco=BTHeadset
# HTC/Beats/Boomsound/Dolby associated props
ro.config.hw_dolby=true
ro.config.hw_dts=true
htc.audio.swalt.enable=1
# Can go as high as 14512 - this is a smooth value
htc.audio.swalt.mingain=1920
persist.htc.audio.pcm.samplerate=192000
persist.htc.audio.pcm.channels=2
persist.audio.vr.enable=false
htc.audio.lpa.a2dp=0
htc.audio.alc.enable=1
persist.audio.SupportHTCHWAEC=1
# These may have no effect but create no issues
support_harman=true
support_boomsound_effect=true
# Sony Edition associated props
# This seems totally necessary for some of Sony's effects - adding it was an audible change
mpq.audio.decode=true
sony.support.effect=0x1FF
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
com.sonyericsson.xloud_enabled=true
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
com.sonymobile.clearphase_enabled=true
ro.somc.cp.default_setting=true
ro.somc.xloud.default_setting=true
ro.somc.sforce.supported=true
persist.service.sforce.enable=1
com.sonymobile.sforce_enabled=true
ro.somc.sfs.default_setting=true
ro.somc.dseehx.supported=true
ro.semc.dseehx.enable=1
persist.service.dseehx.enable=1
# Confirmed "semc"/"somc" are as on Xperia Z5P
# S Audio mod suggested props (from Xperia Z5P)
# SONY effect
# Allocate bit for each effect.
# If necessary, define effect list with logical sum.
# EFFECT_DN 0x0001 (Dynamic Normalizer)
# EFFECT_SF 0x0002 (S-Force)
# EFFECT_CPHP 0x0004 (ClearPhase Headphone)
# EFFECT_CA 0x0008 (ClearAudio)
# EFFECT_VPT 0x0010 (VPT)
# EFFECT_CPSP 0x0020 (ClearPhase Speaker)
# EFFECT_XLOUD 0x0040 (xLOUD)
# EFFECT_CAPLUS 0x0080 (ClearAudio+)
# EFFECT_SPBUNDLE 0x0100 (Speaker Bundle)
# EFFECT_ALC 0x0200 (ALC)
# Effect used by Speaker Bundle.
# EFFECT_SF | EFFECT_CPSP | EFFECT_SPBUNDLE = 0x122
sony.effect.custom.sp_bundle=0x122
# Effect used by ClearAudio+ headset
# EFFECT_CA | EFFECT_VPT | EFFECT_CAPLUS | EFFECT_ALC = 0x298
sony.effect.custom.caplus_hs=0x298
# Effect used by ClearAudio+ speaker
# EFFECT_CA | EFFECT_VPT | EFFECT_CPSP | EFFECT_CAPLUS | EFFECT_ALC = 0x2B8
sony.effect.custom.caplus_sp=0x2B8
# Noise reduction tweaks (Beta phase - seems working)
# These reduce in call noise by using dual mics
# Remove these if unsure if you have dual mics
htc.audio.enable_dmic=1
persist.audio.handset.mic=digital
# Legacy tweaks - these reduce noise noticeably
htc.audio.alt.enable=0
htc.audio.hac.enable=0
Do with this knowledge what you will. I offer no insight or support beyond that this setup is working flawlessly on my HTC One M9 with the ViPERAudio 4.6 Dark Sony Beats Edition (Permissive) I posted recently and the Lover of Sound Profiles I shared.
---------- Post added at 01:41 AM ---------- Previous post was at 01:35 AM ----------
Hey @guitardedhero just noticed this post after I made mine about the XM revival. As soon as you have a ViPERAudio Sony Beats 4.7 up I'll upload my Dark Permissive version and update that post to reflect the correct and working ALSA props.
--EDIT: I have revised and updated the build.prop section for v4.7 - users may want to copy the entire section starting with ViPERAudio and carefully paste over that section in build.prop. I also strongly recommend combing through default build.prop settings to make sure there are no conflicts or duplicates - this was totally necessary for me to achieve the glorious setup I have running as I type this.
I've also updated this post's attachments with ViPER|Audio™ 4.7 Dark Sony Beats Edition (Permissive) for users with Permissive Selinux only.
ViPERAudio_4.7_Dark_Sony_Beats_Edition_Permissive.zip is attached below
Click to expand...
Click to collapse
.
sonophilos said:
Hey @guitardedhero - here's my setup working with my Lover of Sound Profiles as of 2/8/16:
ViPERAudio 5.2.1 - Dark Sony Beats Edition (Permissive)
Once again, the only changes from ViPERAudio Sony Beats 5.2.1 are the replacement of the stock V4A APK with the Material Dark version, and the removal of the su.d folder and its entry from the updater script, for use with devices with an outside solution for Permissive Selinux, such as an init.d script or the Selinux Mode Changer app.
To clarify: If you have Enforcing Selinux this will not operate properly. If you already have Permissive Selinux set up on your device, or if your device has problems with supolicy scripts (as mine does), this should work excellently for you.
I've removed Atmos (rebased on just ViPERAudio) in this version as it was introducing severe popping, skipping and even slowdown to my sound even with every solution I've suggested so far implemented, which may be an issue unique to my device but it's not one I'm willing to tolerate. Atmos only really adds some volume and clarity to midrange and vocals, experientially, for me anyway, and the latest Lover of Sound Profiles easily compensate. I was also tired of having to mess with Memory Locker to keep Atmos from dying every time I started literally any other app besides it, Spotify and V4A.
--
Sonophilos (Lover of Sound) Profiles
Lock Effect Mode - Headset (so Speakers/Bluetooth get all ViPER options) - You will use separate profiles for Headphones and Speakers rather than the separate tabs. The Lover of Sound profiles include both preset as described below.
UI Setting - Expert (so you can see all these settings)
Sonophilos-Headphones:
PlaybackAGC - Enabled, Moderate / 4x Max Gain / -1.0Db Max Output
ViPER-DDC - Enabled, audio-technica ATH-M50 (set this to your headset after first install, then save over Headphones profile)
Spectrum Expansion - 0.5
FiREqualizer - (0.0, -0.6, -1.2, -1.8, -2.4, -3.0, -2.1, -1.3, -0.6, 0.0)
Convolver disabled, it's a major battery drain
Field Surround disabled, it's only really helpful on larger speakers
Differential Surround disabled, it's only really helpful on speakers spaced widely apart
Headphone Surround + Enabled, Level 1
Reverb disabled
Dynamic System enabled / High-End Headphone (v2) / 20%
^You may want to set this to Common Headphone (v2) or if you have one of the specific models listed use that preset
ViPER Bass - Enabled / Natural / 40Hz / 8.0Db
ViPER Clarity - Enabled / Natural / 8.0Db
Cure Tech+ Enabled, Moderate
AnalogX - Enabled, Moderate
Output Gain (-3.0Db) / Channel Pan 0.5:0.5 / Limit Threshold 0Db
Sonophilos-Speakers:
PlaybackAGC - Enabled, Moderate / 4x Max Gain / -1.0Db Max Output
ViPER-DDC - disabled
Spectrum Expansion - 0.5
FiREqualizer - (0.0, -0.6, -1.2, -1.8, -2.4, -3.0, -2.1, -1.3, -0.6, 0.0)
Convolver disabled, it's a major battery drain
Field Surround disabled, it's only really helpful on larger speakers
Differential Surround disabled, it's only really helpful on speakers spaced widely apart
Headphone Surround + disabled
Reverb disabled
Dynamic System disabled
ViPER Bass - Enabled / Natural / 40Hz / 10.0Db
ViPER Clarity - Enabled / Natural / 8.0Db
Cure Tech+ disabled
AnalogX - Enabled, Moderate
Output Gain 0Db / Channel Pan 0.5:0.5 / Limit Threshold 0Db
--
I recommend adding the following section to build.prop:
Code:
#
# ViPER4Android
#
audio.deep_buffer.media=false
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
lpa.releaselock=false
lpa.use-stagefright=false
persist.sys.media.use-awesome=1
ro.audio.samplerate=48000
ro.audio.pcm.samplerate=48000
You can set the bottom two higher - check in your audio_policy.conf under compress_offload to see how high the dynamic sampler will go. My HTC One M9's goes to 192000 and so I have those bottom two samplerate settings set to that.
I also recommend adding the two values to audio_policy.conf as described in the OP, and the use of Don't Pause! so notifications go to vibrate when music is playing instead of "ducking" or pausing the music stream.
The combination of this mod and profiles and tweaks is an absolutely gorgeous sound out of the internal speakers, realizing the potential of the device much better and adding some substantial volume, and the headphone experience is practically theatrical. The sound and its processing also defies being interrupted, making for an immersive headphone experience or lengthy playlist jam.
--Cheers all, from Sonophilos the lover of Sound.
ViPERAudio 5.2.1 Dark Sony Beats Edition Permissive.zip and Lover of Sound Profile 5.2.1.zip attached below
Click to expand...
Click to collapse
-decipher- said:
Hey, I'm using latest Viper|Atmos sony beats 4.5.1 and it's SUPERB. Maybe it's me, but I've noticed sound is noticeably cleaner compared to 4.4 beats only. I was thinking of contributing to the thread as a way of showing my appreciation so I'm sharing my settings here if anyone is interested, I use not so high quality earphones (30$ more or less) so these settings are oriented mainly to similar budget earphones.
Viper settings:
Headset:
Playback Gain Control: On (if you are using Poweramp, first switch off it's built in AGC)
Effect strength: moderate
Max Gain: 4x
Max output: -1.9 DB (for smoother output)
Viper DDC: Off
Spectrum Extension: On
Strength: 0.5 (switch off if you face bass distortion)
FIREquializer: Off
Convolver: On
Impulse Response: Tracks Regular 1.irs from here
Cross Channel: 0
Field Surround: Off
Differential Surround: Off
Headphone Surround+: Off
Reverberation: Off
Dynamic System: On
Select Listening Device: Common Earphone v2
Select Dynamic Bass: 3 percent
Fidelity Control
Viper Bass: On
Bass Mode: Natural
Bass frequency: 50Hz
Bass Boost: 10dB
Viper Clarity: Off
Auditory System Protection
Cure Tech: On
Binaural Level: Slight
Master Gate: Defaults (0)
For Dolby Atmos:
Music Mode
Intelligent Equalizer: Rich (middle preset)
Surround Virtualizer: On
Dialogue Enhancer: On
All surround processing will be done by Dolby Atmos Alone, without interference from Viper. Also All setting That I didn't mention were left with default value. Keep In mind that some IRS may or may not work if Viper is installed as system app, to solve this issue I thank @guitardedhero for explaining this, You must extract Viper4Android APK from the zip file and install it manually, this will make Viper a system AND user app, so full convolver functionality is restored.
Click to expand...
Click to collapse
tcat007 said:
Here's mine. Atmos setting "open" (left), surround on. V4a profile attached, irs: BBE Generic2.
Tcat007.zip is attached below.
Click to expand...
Click to collapse
-decipher- said:
Viper4Android Look:
CM13 theme engine theme: DEEPDARKNESS//. Screen below.
Click to expand...
Click to collapse
rolarocka said:
Here are my settings with the Atmos Sony Beats Edition, they are perfect for me who hears mostly electronic music with in ears monitors.
Viper Ui setting is at moderate, headset tab
Spectrum extension at 0,1
Convolver with WavesMusic.IRS
Reverberation *sometimes* on with 25m2, 8m, 50%, 10%, 60%
Viper Bass on at 40Hz, 6dB
Viper Clarity on at 3,5dB
Anything else off.
Dolby Atmos is full on bass and highs, a bit of mids, music preset and manual equalizer, surround virtualizer, dialog enhancer and volume leveler are off.
Just try it , bass is punchy and the highs are crystal clear, mids are there too
A0001 - oneplus one
Click to expand...
Click to collapse
ranaxda200 said:
I'm attaching my all favorites convolvers. Hope it'll be useful for those who need it.
convolver.zip attached below.
Click to expand...
Click to collapse
Jimbus369 said:
Hi guys, I want share my experience with Viper4Android. I'm not an expert, but I like play with audio settings.
My configuration:
I9505 Jfltexx CM13 crDroid
ViPERAtmos 4.5.1 Sony Beats Edition
Sony Music 9.1.4.A.2.1 - 1.4 (Amazing!)
Headset:
Standard S4 audio Headset.
Bluetooth:
Philips PIX3L
Amplifier:
JBL ESC200
Low end things, I know...
Albums used for my test:
Eagles - Hotel California MFSL 1-126 Flac 2830 Kbps
Dire Straits - Money For Nothing MP3 128 Kbps
Ac/Dc - Dirty Deeds Done Dirt Cheap MP3 320 Kbps
Guns N' Roses - Appetite For Destruction MP3 320 Kbps
Paramore - RIOT! [Limited Edition] MP3 320 Kbps
Tell me how I can do better and where I have done something wrong. I want study something more about Differential surround, but I like it!
Dolby Atmos settings:
Intelligent Equalizer: Rich
Surround Virtualizer: On
Dialogue Enhancer: On
Volume Leveler: Off
Viper4Android profile is attached below.
I'm sorry for my english!
V4A_(Extreme_Profile_by_Jimbus369).rar attached below.
Click to expand...
Click to collapse
derekr44 said:
Ok, I'll try my hand at sharing settings. I mostly listen to Trance and Progressive, heavy electronic sounds and lots of subtle details with harmonic chords. So I'm not positive how this will sound with other genres of music... It's not perfect by any means, but it's getting there. Plus I'm partially deaf in my left ear, so...
Zip: Viper|DD+ 4.5.2
Listening Device: VOXOA HD Wireless
Viper Settings
Spectrum Extension - Enabled
Strength - 0.6
Convolver - Enabled
IRS - BBE Wide Stereo.irs
Viper Bass - Enabled
Bass Mode - Natural
Bass Freq - 40Hz
Bass Boost - 6.0db
Viper Clarity - Enabled
Clarity Mode - XHiFi
Clarity - 3.5db
Dolby Settings
Dialogue Enhancer - On
Intelligent EQ - Rich, Bass+2, Treble+2
Click to expand...
Click to collapse
tcat007 said:
If anyone wants a Red/Gold layer for v4a I have attached what I use.
Tcat-v4a.apk attached below.
Click to expand...
Click to collapse
dead0 said:
@guitardedhero
For anyone interested, you can add the following lines to your build.prop. It may just be a placebo effect on my part but I have noticed a small difference with these added in. This has only been tested on the oneplus one with darkobas rom/lightning kernel however should work for others.
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=2072
af.resampler.quality=255
persist.af.resampler.quality=255
persist.htc.audio.pcm.samplerate=48000
persist.htc.audio.pcm.channels=2
persist.audio.vr.enable=false
htc.audio.alc.enable=1
htc.audio.global.state=0
htc.audio.q6.topology=0
htc.audio.global.speaker=1
persist.audio.SupportHTCHWAEC=1
sony.support.effect=0x1FF
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
ro.semc.clearphase.supported=true
persist.service.clearphase.enable=1
com.sonyericsson.xloud_enabled=true
ro.semc.xloud.default_setting=true
com.sonymobile.clearphase_enabled=true
Click to expand...
Click to collapse
stueycaster said:
Check out this profile. I strengthened the reverb a little and cranked down the gain some so there shouldn't be any hissing. At least I don't get any.
FX:
Master Power:
Playback Gain Control: ✘
Viper DDC - X
Spectrum Extension - X
FIREqualizer:
Select Preset: Custom (see image)
Convolver:
Impulse Response: TruTheatre Surround Headphone Live Room.irs
Field Surround: ✘
Differential Surround X
Headphone Surround +:
Effect Level - 2
Reverberation:
Room size - 49m2
Sound Field - 10m
Damping Factor - 80%
Wet Signal - 20%
Dry Signal - 60%
Dynamic System:
Listening Device - unknown type 2
Dynamic Bass - 14%
Fidelity Control:
Viper Bass:
Bass Mode: Natural Bass
Bass Frequency: 78Hz
Select Bass Boost: 14.0 dB
Viper Clarity: ✘
Clarity Mode: Natural
Select Clarity: 6.0
Auditory System Protection ✘
Master Gate (Limiter)
Output Gain: -10.5dB
Channel Pan - 0.5 - 0.5
Limit Threshold - 0dB
Then I also use Dolby Atmos for nothing but a little extra surround. My earphones give a fairly balanced sound so this setup gives me a pretty balanced sound with a bit of a fat bottom, wide separation and a pretty decent ring. If your earphones are naturally bassy this profile will probably be pretty boomy. Anyway give it a try if you like. I hope you like it.
In case you need the TruTheater irs.
Stueycaster TruTheatre profile with TruTheatre IRS.zip is attached below.
Sent from my SM-N910V DE
Click to expand...
Click to collapse
RSDamasceno said:
@guitardedhero
I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:
https://db.tt/4WIJXf8O
Mirror: https://docs.google.com/uc?id=0B2NPIEc31bRpNV9VZW4wbzlXcXc&export=download
V1
* 50 profiles (50 IRS + 2 VDC)
* All revised
* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set)
* All profiles tested in my Moto Maxx / JBL-J22 / Home Theater Samsung F5555WK via Bluetooth
* A good starting point for beginners
* Credit to the creator of the profile is the profile name (if possible!)
Next releases
* I plan to review more than 200 profiles that collect
Instructions:
Just extract to your ViPER4Android folder
P.S.: If you do not agree with my collection I can remove.
Profiles_(mega_pack)_v1.zip attached below
I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:
.
* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set) *
* A good starting point for beginners *
* Credit to the creator of the profile is the profile name (if possible!) *
.
Change log V2:
* 100 profiles (62 IRS + 2 VDC)
* All revised with ViPERAudio 4.7.1 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Home Theater Samsung F5555WK via Bluetooth
Change log V1:
* 50 profiles (50 IRS + 2 VDC)
* All revised with ViPERAtmos 5.3 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Home Theater Samsung F5555WK via Bluetooth
.
Instructions:
Just extract to your ViPER4Android folder
Next releases
* I plan to review more than 170+ profiles that collect
P.S.: If you do not agree with my collection I can remove.
Profiles_(mega_pack)_v2.zip attached below.
I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:
.
* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set) *
* A good starting point for beginners *
* Credit to the creator of the profile is the profile name (if possible!) *
.
Change log V3:
* 150 profiles (81 IRS + 4 VDC)
* All revised with ViPERAudio 4.8.2 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
Change log V2:
* 100 profiles (62 IRS + 2 VDC)
* All revised with ViPERAudio 4.7.1 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
Change log V1:
* 50 profiles (50 IRS + 2 VDC)
* All revised with ViPERAtmos 5.3 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
.
Instructions:
Just extract to your ViPER4Android folder
Next releases
* I plan to review more than 290+ profiles that collect
Profiles_(mega_pack_v3.zip attached below.
Added V4
I "created" a package with the profiles in #2 + with many many many profiles that collect long time, and upload here:
* Initially created for personal purposes (Perhaps a profile does not sound good to your hardware set) *
* A good starting point for beginners *
* Credit to the creator of the profile is the profile name (if possible!) *
Change log V4:
* 200 profiles (102 IRS + 4 VDC)
* All revised with ViPERAudio 4.8.1.1-2 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
Old change logs:
Change log V3:
* 150 profiles (81 IRS + 4 VDC)
* All revised with ViPERAudio 4.8.2 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
Change log V2:
* 100 profiles (62 IRS + 2 VDC)
* All revised with ViPERAudio 4.7.1 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
Change log V1:
* 50 profiles (50 IRS + 2 VDC)
* All revised with ViPERAtmos 5.3 Sony Beats Edition
* All profiles tested in my Moto Maxx / JBL-J22 / Samsung F5555WK via Bluetooth
Instructions:
*If you are upgrading delete the folder called STOCK inside the folder viper4android
Just extract to your ViPER4Android folder
Next releases
* I plan to review more than 220+ profiles that collect
Profiles_(mega_pack)_v4.zip attached below.
Click to expand...
Click to collapse
abeloman said:
Well. here's my contribution... Juanpro (Just Another Profile) only for Headset
I'm currently using JBL J22, and I think I have a decent performance with this settings... It should work well with most earphones and you can play with the "Dynamic System" (to get more bass according to your headset)... I borrow the template from @sonophilos (hope it doesn't mind) to share settings here, because I'm using another lenguage
PlaybackAGC - Enabled / Slight / 2x Max Gain
Convolver - Enabled / DFX Urban RB.irs
Dynamic System - Enabled / Common Earphone(v1) or (v2) *the choise depends on you* / 5%
ViPER Bass - Enabled / Natural Bass / 40Hz / 8.0 Db
ViPER Clarity - Enabled / Natural / 3.5 Db
Cure Tech+ - Enabled / Moderate
Output Gain - 3.5 Db *this depends on you*
Obviously the settings I didn't mention are default, or disabled. Personally I don't have any distorsion or crackle with rising "Output Gain", and even I play with the sound values from my kernel (my device without this modifications has a very low volume). Hope you like it!
Juanpro.zip attached below.
Click to expand...
Click to collapse
adm1jtg said:
@guitardedhero sent you a pm
Also found these if u havent already seen them
http://en.miui.com/thread-71540-1-1.html
Click to expand...
Click to collapse

yep got it working on my N6.
downloaded your n5 lollipop V4A, installed SELinux Mode Changer, changed mode to "Permissive", and it works perfectly.

tflogic said:
yep got it working on my N6.
downloaded your n5 lollipop V4A, installed SELinux Mode Changer, changed mode to "Permissive", and it works perfectly.
Click to expand...
Click to collapse
Sweet man thanks. I'll get the OP set up soon with the zip.

AndrasLOHF said:
Sweet man thanks. I'll get the OP set up soon with the zip.
Click to expand...
Click to collapse
oh! forgot to mention thus but the only qualm I have with V4A on the device is that the "Driver Status" option is greyed out and unclickable. it doesn't really make a difference since I can notice sound effects changing whenever I'm messing around with the settings but I thought it might be mentionable.

Installed apk, set it to permissive and installed driver and then it worked.

zephiK said:
Installed apk, set it to permissive and installed driver and then it worked.
Click to expand...
Click to collapse
What did you set to permissive? And how did you set it to permissive?

recepo1 said:
What did you set to permissive? And how did you set it to permissive?
Click to expand...
Click to collapse
If you read the thread, just get the app SELinux Mode Changer from Play Store and you can set it to permissive instead of enforcing.

zephiK said:
If you read the thread, just get the app SELinux Mode Changer from Play Store and you can set it to permissive instead of enforcing.
Click to expand...
Click to collapse
Read the thread was just curious if it was a different method

tflogic said:
oh! forgot to mention thus but the only qualm I have with V4A on the device is that the "Driver Status" option is greyed out and unclickable. it doesn't really make a difference since I can notice sound effects changing whenever I'm messing around with the settings but I thought it might be mentionable.
Click to expand...
Click to collapse
Bi-product of compatibility mode.

Got it working. Thanks!!!

1: Set SELinux to PERMISSIVE mode
2: Installed zip via TWRP.
3: Installed driver upon app first open (super quality mode)
4: Allowed all root prompts.
5: Tried both compatibility mode and normal mode with unchecking NuPlayer
Anything I'm missing? It's still not working...
EDIT: It's Finally working... It's on compatible mode & super high quality driver.

Bjray said:
1: Set SELinux to PERMISSIVE mode
2: Installed zip via TWRP.
3: Installed driver upon app first open (super quality mode)
4: Allowed all root prompts.
5: Tried both compatibility mode and normal mode with unchecking NuPlayer
Anything I'm missing? It's still not working...
Click to expand...
Click to collapse
Double check the permissive app. I've had issues with it reverting to enforcing after a reboot. What music player are you using?

AndrasLOHF said:
Double check the permissive app. I've had issues with it reverting to enforcing after a reboot. What music player are you using?
Click to expand...
Click to collapse
Don't know exactly what fixed it but I'm using GPM.

Does it work when you play YouTube video's? Or just music player

Worked like a charm!

kepapas said:
Does it work when you play YouTube video's? Or just music player
Click to expand...
Click to collapse
It should process system wide when in normal mode.

I am unable to make this work.
I have permissive SELinux, I checked every time I rebooted my phone.
I redownloaded and reflashed the zip while wiping cache+dalvik via twrp.
Installed the super high quality driver and rebooted phone.
Tried compativility mode and normal mode with the dev setting off.
Rebooted and when I check driver status it says everything is enabled, but it is not processing.
Any help would be appreciated!

TmobileDash12 said:
I am unable to make this work.
I have permissive SELinux, I checked every time I rebooted my phone.
I redownloaded and reflashed the zip while wiping cache+dalvik via twrp.
Installed the super high quality driver and rebooted phone.
Tried compativility mode and normal mode with the dev setting off.
Rebooted and when I check driver status it says everything is enabled, but it is not processing.
Any help would be appreciated!
Click to expand...
Click to collapse
This might sound stupid but... What effect are you trying to activate and use? Try setting some of the effects to the extreme values to see if it changes anything, especially the EQ, seems like they only make noticeable differences at high values. And some effects just plain don't work it seems.

Velocity Kernel (3.10.104) v14.0 (64-Bit) for Lollipop (5.1.1)/Marshmallow (6.0.x)

After a lot of testing and hours of hard-work, I have developed a kernel based on the latest sources. As the name of the kernel suggests, the primary focus of the kernel is speed and performance. As a result, I have fine-tuned and optimized this kernel to perform in the best possible manner. However, I haven't missed to look into the Battery issues of the phone. A lot of effort has been made to fix unnecessary consumption of battery along with regulated CPU usage. Further, I have worked really hard to include almost all features and fixes so as to make my kernel the most feature-packed All-in-One solution.
Main Features---
Display---
Support for kCAL Colour Control v2.0 (enhances Colour Vibrance and Intensity). (available as a Screen TAB in Kernel Adiutor).
Up-to-date LiveDisplay Driver.
Support for Colour Enhancement (Updated).
Support for HotPlugs---
MSM (Fast Lane Load)
Mako
AluCard
IntelliPlug
ThunderPlug
AutoSMP (Modified and Enhanced for big.LITTLE architecture by ME )
State Helper v2.0 (Modified and Enhanced for big.LITTLE architecture by ME )
MSM mP-Decision (Bricked)
Support for Governors---
Conservative
Darkness
ElementalX
LionFish
IntelliDemand
Interactive
OnDemand
Performance
PowerSave
SmartMax
Hyper
Wheatley
YankActive
AluCard
Support for I/O Schedulers---
FIOPS
BFQ v7r8 with Hierarchical Scheduling
ROW
NOOP
DeadLine
CFQ
SIO
CPU---
Fixed High-Load Average from UnInterruptible Waits (reduces CPU-Load even more in idle state).
Overclocked CPU upto 1.7GHz (big Cluster) and 1.2GHz (LITTLE Cluster) for Extreme Performance (Modified and Enhanced by ME ).
Proper and Uniform Frequency Table Format with 200MHz Gap between each Frequency
Support for Fast-IDLING of CPU (should reduce Power-Consumption a lot).
Support for Power Efficient WorkQueue to reduce Power-Consumption (available in CPU tab of Kernel Adiutor).
GPU---
Support for ADRENO-IDLER algorithm (saves a lot of Battery by reducing GPU Frequency to minimum when there is less load).
Altered GPU-Frequency Table for more Power-Savings without noticeable decrease in Performance.
Memory---
Support for Swap, FrontSwap, and zSwap techniques (improve performance significantly when zRAM is full).
Support for Memory Compaction (improves performance).
Support for CleanCache Driver (improves I/O performance).
Support for zsmAlloc with Page-Table Mapping techniques (improve memory performance).
Support for zRAM with LZ4 compression algorithm (improves performance by saving memory).
Battery---
Support for ARCH_Power to reduce Power-Consumption and increase Battery-Life.
Support for the new PowerSuspend algorithm (improves Battery-Life).
Support for preventing unnecessary WakeLocks (improves Battery-Life). (available under the Misc. Tab of Kernel Adiutor)
Support for ThunderCharge Current Control Driver v2.1 (accelerates Charging by a large margin).
Optimizations and Tweaks---
Based on the latest sources of CyanogenMod (CM) for Yu Yureka/Yureka PLUS.
Disabled CRC-Check for upto 30% faster I/O.
Support for FRandom RNG Driver (upto 50x faster than the default one).
Compiled with UberTC 4.9.4 Optimized for 64-BIT (Uber uses the latest of every component as well as increases the Battery-Life too).
Support for Touch-Boost and CPU-Boost (Updated).
Support for Vibration Intensity Control (available in Misc. TAB of Kernel Adiutor).
Lowest Possible CPU-Usage (a lot of tweaks have been implemented system-wide).
Support for various Wake-Up Gestures including D2W.
Disabled Debug-Info (should reduce the size of the kernel making it lighter).
Support for HMP Aware and Power-Aware Task Allocation (should improve Performance and Battery-Life).
Support for Faux Sound Control v4.1 (Modified and Enhanced by ME ).
Support for a Custom Thermal Driver with Optimized Core Control v2.0 (Better Heat-Management with Flexible Controls, Modified and Enhanced by ME ).
Support for Load Shifter Mechanism (allows more Power-Savings, built by ME ).
The above mentioned features are just the main ones (many are omitted due to word limit), there are many more small technical changes done to improve the overall experience. By the way, the number written after the # symbol in the "Kernel Version" available in About Phone section, tells the number of times I have compiled the kernel. That number alone is an evidence of the amount of time, hard-work and patience I have applied in developing this kernel.
I have tried my best to make my kernel the most polished one. From minor tweaks to major improvements, everything is perfectly done. Moreover, I'll update my kernel whenever a useful feature or new sources come out so as to make you people experience the best and the latest of everything.
I encourage all the people here to try this kernel and squeeze out every bit of performance from our hot-tempered Yu Yureka/Yureka Plus.
Notes---
1. This kernel performs best when used with ROMs based on the latest sources of CyanogenMod.
2. My kernel doesn't requires any other app except for Kernel Adiutor to control the features. Therefore, you people are free to uninstall any other Kernel-Management app. #NoHassles
3. The *NEW word written after a feature indicates that this feature is NOT present in any other Kernel at the time of release.
4. The words 'Modified and Enhanced' written after any Feature indicate that I, myself, have modified that feature to make it more Efficient for our specific Device.
Installation Instructions---
1. It is recommended to clean-flash the kernel if you face any problems such as LED not blinking, unstable frequencies, etc.
2. To download the kernel, head over to the ChangeLogs and Downloads post and select the version of kernel you want.
3. To install the kernel, just flash the .zip using TWRP recovery.
Credits---
1. Google (for everything related to Android)
2. Cyanogen (for Source Code)
3. Varun Chitre (for ThunderCharge)
4. Savoca (for kCAL Colour Control v2.0)

Changelogs and Download Links---
v14.0---
For Changelog and Download Link, refer here.

Recommended Settings---
Note---
1. Use Kernel Adiutor-MOD to apply settings!
Download Link for Kernel Adiutor-MOD---
https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk
2. Always set the Apply on Boot Delay to 20 seconds or more. This is useful to avoid situations in which a certain feature malfunctions everytime after it is enabled at boot and thus results in a bootloop. Setting the delay to a higher value allows to disable that particular feature before it gets enabled.
CPU TAB---
For Balanced Performance---
1. Set Min. to 200MHz and Max. to Max. Available for both Clusters.
2. Interactive/Impulse Governor for both Clusters.
3. Enable Schedule WorkQueues Toggle.
For Battery-Saving and Less Heat---
1. Set Min. to 200MHz and Max. to 1200MHz for big Cluster.
2. Darkness/LionFish Governor for both Clusters.
3. Enable Schedule WorkQueues Toggle.
CPU HotPlugs TAB---
Use AutoSMP if you want more Battery-Life and Decent Performance with Less Heating than Stock Kernel.
State Helper---
1. Max. Core Online (Screen On) at 6 (Useful for Gamers)---
More Battery-Saving and Lesser Heating than Stock Kernel.
2. Max. Core Online (Screen On) at 4 (Useful for Normal Usage)---
Excellent Battery-Saving and Minimal Heating but Lesser Performance than Stock Kernel.
3. Max. Core Online (Screen On) at 2 (Useful for those who don't play Games or do much Browsing)---
Extreme Battery-Saving and Least Heating but much Lower Performance than Stock Kernel.
Thermal TAB---
1. Least Heating Profile---
Enable Core Control.
Temperature Throttle at 45 C.
2. Balanced Heating Profile---
Enable Core Control.
Temperature Throttle at 60 C.
3. Gaming Heating Profile---
Disable Core Control.
Temperature Throttle at 75 C.
Note---
Keep rest of the Thermal Settings at Default Values for all Profiles!
GPU TAB---
Enable Adreno IDLER.
Screen TAB---
Improved Colour Enhancement is in-built in kernel. Still, this is what I use---
LiveDisplay---Night Mode
Minimum RGB Value---32
Saturation Intensity---48
Wake Controls TAB---
As per your own preference.
Sound TAB---
As per your preference.
Battery TAB---
I don't use ThunderCharge as I feel that the stock values provided by YU charge the phone within a decent time. So, again, use as per your preference. However, using Charge Rate beyond 1250mAh may damage the hardware.
I/O Scheduler TAB---
BFQ for both Internal and External Storage.
WakeLocks TAB---
Disable all (to Save Power). However, if you face any problems, then re-enable all.
Misc Controls TAB---
Disable Android Logging.
Init.d TAB---
Enable Emulate Option.
Leave the rest TABs as they are.
Note---
In order to reset settings to default, just Disable the Apply On Boot option of the particular TAB in Kernel Adiutor and reboot the phone.
ENJOY!!!

Reserved.

Shoaib05 said:
Reserved
Click to expand...
Click to collapse
Will this kernel work on stock cm12?????
as currently I'm using Sandy kernel
And getting average battery life and performance ????

gtsfreak said:
Will this kernel work on stock cm12?????
as currently I'm using Sandy kernel
And getting average battery life and performance ????
Click to expand...
Click to collapse
Since the stock CM12 ROM is based on the older sources, I doubt that my kernel will work perfectly. However, you may try and tell me whether it works or not. It would be really helpful.
By the way, which version of Sandy Kernel are you using?

Shoaib05 said:
Since the stock CM12 ROM is based on the older sources, I doubt that my kernel will work perfectly. However, you may try and tell me whether it works or not. It would be really helpful.
By the way, which version of Sandy Kernel are you using?
Click to expand...
Click to collapse
Sandy kernel v1.5
Battery life and performance is average

gtsfreak said:
Sandy kernel v1.5
Battery life and performance is average
Click to expand...
Click to collapse
Try mine if you're unhappy with the results you're getting with your current kernel.
However, I don't think everything will work i.e., LED or Camera but you'll get better performance and Battery-Life, this I can promise.

Support for Android Marshmallow (6.0) has been added!!! Check 2nd post for Download Link!!! (thanks to Hriday Sharma for the commits!)

From now onwards, this thread will not be maintained. Head to Yu Forums to stay updated!!!
Edit---
Thread will be maintained here on XDA too.

Kernel Manager ?
Shoaib many thanks for creating this for us ! God bless you !
Hi Dev Champs !
I am a noob when it comes.to Kernel and Kernel manager. I am a user of Yu Yureka running custom CM13 rom (Created by SantoshM) and im running Velocity 2.0+.
Can you pls suggest the best Kernal Manager in ur opinion. I am using Ex Kernal Manager right now.
Can you also walk me through the steps of setting up the best units for saving battery as well... Of course if thats not a lot of trouble.

download links not working , wanted to check this out with cm13 latest built

Update---
Velocity Kernel v14.0!!!
Changelog---
1. Merged Latest CM's Source Updates into Velocity's Source (contains many improvements).
2. Updated the Linux Base Version to the latest one of 3.10 branch i.e., 3.10.104 (contains BUG-Fixes). *NEW
3. Updated the PowerSuspend Drivers to the latest version i.e., v1.7 (should improve Battery-Life).
4. Added Support for Impulse 2016 Edition Governor (a Balanced Governor for smooth performance and decent Battery-Life). *NEW
5. Added Support for State Notifier Driver (an Optimized mechanism for knowing about Panel's State). *NEW
6. Tuned the LionFish Governor (for better Performance). *NEW
7. Modified the Touch-Boost to be user-controllable (In CM, it is enabled by default and is not user-controllable. This makes the Battery deplete much faster. In my kernel, it is disabled by default and is also user-controllable.). *NEW
8. Improved the Thermal Mechanism (better Heat-Management without much degradation in Performance). *NEW
9. Tuned the Interactive Governor for Efficient operation and more Power-Savings. *NEW
10. Removed Franco's Sound Control (Although, I ported it in the best possible manner, it still wasn't quite upto my standards.).
11. Removed the stock CyanogenMOD Core Control Feature (the current implementation wasn't as Efficient as it should have been in reducing Heat and improving Battery-Life). *NEW
12. Minor BUG-Fixes and Improvements.
Now, the Highlights of v14.0 (unique features which only Velocity Kernel offers for Yu-Devices)---
1. Core Control v2.0---
Built from scratch by me, this version of Core Control is much more efficient than the stock one. In this version, Cores are disabled according to temperature in a much more optimized manner. Further, this Core Control of mine, offers efficient Heat-Management as well as improved Battery-Life. To sum up, this is the best Core-Based Heat-Management Technique for Yu-Devices.
2. Faux Sound Control v4.1---
In this Sound Control, I have used Faux Sound v3.6 as base and on top of it, I have modified, fixed and enhanced the Driver. All of the changes are done by me! I have named this version as v4.1 because I have made 5 changes to the Driver (v3.6 + 5 Changes = v4.1). Coming to the point, this Sound Control is finally the best one. I have worked hours on it to port and fix it in the best way. Thus, now, there is no Low-Volume issue. Further, even the Negative Values work too. Also, the Volumes are boosted without distortion now i.e., higher Volumes can be achieved easily. Also, now, there is a fully functional Enable/Disable Toggle for Sound Control. To bring this feature and make it Compatible with the Modified Kernel Adiutor, I did a very clever workaround too. To sum up, this is indeed the best Sound Control for Yu-Devices with No BUGs.
3. Perfect Core-HotPlug Mechanism---
In this version of my kernel, I have added two HotPlugs, AutoSMP and State Helper. Now, you may ask what is unique about it? Well, I have just used these HotPlugs as base. On top of these HotPlugs, I have done huge modifications, wrote many new Codes and worked on them many hours and I am very happy with the results.
AutoSMP (Modified)---
I have modified this HotPlug to only work as an On/Off Toggle. I have removed all the Options and Codes to make this HotPlug lightweight. Th only function of this HotPlug now is to turn an Octa-Core Soc into a Quad-Core one retaining the HMP or big.LITTLE technique. This will allow much more Power-Savings without degrading Performance as well as lesser Heat too.
State Helper (Modified) v2.0---
I have modified this HotPlug to a great extent. The original State Helper was only meant for Normal Architectures and not big.LITTLE architectures. I worked on this HotPlug to make it support big.LITTLE architecture as well as I have Optimized it to Perform in an efficient way too. Also, I have fixed a critical BUG of this HotPlug. Further, I have removed the unnecessary Codes to make it lightweight. Since I have Optimized this HotPlug for big.LITTLE architecture, this HotPlug now offers the ability to disable the big Cluster completely. Further, this HotPlug also offers the ability to turn an Octa-Core HMP Soc to a Hexa-Core one just like the setup of Snapdragon 650. This Optimization allows for Extreme Power-Savings.
These Core-HotPlug mechanisms offer the best way to Control the Cores for managing Heat and Improving Battery-Life. The best part is that users can control these HotPlugs to find the Perfect Combination according their usage. Also, an important point about these HotPlugs is that they are not Load-Based ones. These HotPlugs don't use CPU-Resources and thus offer Better Battery-Life and Lesser CPU-Usage. To sum up, I have Modified and Optimized these HotPlug in the best possible manner. These HotPlugs are the best ones for Yu-Yureka/Yureka PLUS.
4. Perfect OverClock for Snapdragon 615 1st Gen SoC---
As you all know, our devices seem to use the 1st Gen of SD615 SoC. Probably, that's why, we have 1.5 GHz of Max. Frequency. Further, due to great variations among the same SoC, developing OC to work on every device is a very difficult task. The Max. Frequency that our SoC can run properly is 1.7GHz. Above it, the SoC fails to boot. Further, kernels which were offering OCs above 1.7GHz were containing fake OCs i.e., only the numbers change, not the actual Frequency. Now, after weeks of testing by myself as well as some very good testers, I have managed to find the perfect way of implementing the 1.7GHz and 1.2GHz OC Frequency for big and LITTLE Cluster respectively. In my implementation of the OC, I have applied an Efficient Voltage Distribution technique. This allows to not only consume the least amount of Power but also helps in achieving Perfect Stability i.e., the OC will work on every Device irrespective of Revisions. Further, people who choose to not use the OCs, then the kernel will return to use the stock voltages thus providing the same level of efficiency as the stock kernel.
5. Load Shifter---
As I have already discussed in the Load Shifter's own thread, this feature transfers the Workload from the big Cluster to the LITTLE CLuster. Even the Android Background Processes are forced to run on the LITTLE Cluster with the help of this feature. Since we use LITTLE Cluster for most of the tasks except Gaming, there are considerable Gains in Battery-Life as well as Lesser Production of Heat.
Notes---
1. Due to variations in SoC, the Sound Control will work properly at different levels of Volume for different people. For ex, value 5 of Mic Gain may be too loud for some but too low for others. So, you people have to find out the perfect value for yourselves. By the way, value 10 of Mic Gain is known to be the most suitable for every device.
2. In order to avoid conflicts, I have added a failsafe regarding Core-Control and Core-HotPlug Mechanism. This means, out of AutoSMP, State Helper and Core Control, only one can be used at a time. Even if you try to enable each one of them simultanouesly, they won't get enabled. I have done this to avoid malfunctions.
3. After manually changing the CPU Governor or Frequency, all the Cores will come online even if any HotPlug is enabled. So, you just need to re-enable any HotPlugs you were using in order to disable the Cores again.
4. Currently, AOSParadox ROM and a few other voLTE enabled ROMs too have 100% Core-Load Issue. This leads to more Heat-Generation. Further, High CPU-Usage makes Charging Time a lot slower as well as decreases the Battery-Life by a large margin. Until this BUG is fixed, nothing much can be done to improve upon these areas.
5. Sometimes, enabling Core Control may cause the ROM to hang. In this case, rebooting via ROM doesn't work. So, just press and hold Power button until the phone restarts.
6. When Core 0 gets disabled (due to Core Control or State Helper HotPlug), Adiutor fails to get Frequency and Governor information and hence shows 0MHz in Frequency Panel and Blank Space in Governor Panel. This is normal. In this case, if you need to change Governor or Frequency, then you need to disable Core Control or State Helper HotPlug as the case may be. After this, force close Adiutor and then re-open it. This will make Adiutor get CPU information again.
Recommended Settings are also updated!!!
That's it folks! My best creation till date for Yu-Devices. My aim was always to improve the experience we get from our phones and provide the users with control over everything. Today, I have achieved that goal. This became possible only due to months of hard-work by me and testing-work done by some very reliable testers.
Testers (without these people, developing a Stable and BUG-Free Kernel would be near to impossible)---
dixan43
Bijendra barman
Frozen_Lemon
Ryuk and many others were there, thanks to all of you!!!
Download Links---
For all Lollipop (5.1.1) and Yu-OS ROMs---
https://www.androidfilehost.com/?fid=385035244224394352
For Marshmallow (6.0.x) ROMs only---
https://www.androidfilehost.com/?fid=529152257862677379
For AOSParadox 3.x (6.0.x) ROM only---
https://www.androidfilehost.com/?fid=529152257862677377
Enjoy the most efficient and thoughtfully made Kernel.

Shoiab I always use urs kernel as a daily driver but there is low mic volume issue in V14 and unable to resolve that so back to V13 ...so plz share the recommended settings for V13 ....

I hv yu yureka plus running on RRrom6.0.1.Is this kernel good for the rom

Will it work for my yu yureka plus 5510?I have RR rom installed based on Android MM6.0.1

Does this kernel work for 7.1.1 yureka builds?
Sent from my YU5510 using Tapatalk

Same question here does this kernel work for yu yureka on LineageOS 14.1 ?
Sent from my AO5510 using XDA-Developers Legacy app
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
Shoaib05 said:
Update---
Velocity Kernel v14.0!!!
Changelog---
1. Merged Latest CM's Source Updates into Velocity's Source (contains many improvements).
2. Updated the Linux Base Version to the latest one of 3.10 branch i.e., 3.10.104 (contains BUG-Fixes). *NEW
3. Updated the PowerSuspend Drivers to the latest version i.e., v1.7 (should improve Battery-Life).
4. Added Support for Impulse 2016 Edition Governor (a Balanced Governor for smooth performance and decent Battery-Life). *NEW
5. Added Support for State Notifier Driver (an Optimized mechanism for knowing about Panel's State). *NEW
6. Tuned the LionFish Governor (for better Performance). *NEW
7. Modified the Touch-Boost to be user-controllable (In CM, it is enabled by default and is not user-controllable. This makes the Battery deplete much faster. In my kernel, it is disabled by default and is also user-controllable.). *NEW
8. Improved the Thermal Mechanism (better Heat-Management without much degradation in Performance). *NEW
9. Tuned the Interactive Governor for Efficient operation and more Power-Savings. *NEW
10. Removed Franco's Sound Control (Although, I ported it in the best possible manner, it still wasn't quite upto my standards.).
11. Removed the stock CyanogenMOD Core Control Feature (the current implementation wasn't as Efficient as it should have been in reducing Heat and improving Battery-Life). *NEW
12. Minor BUG-Fixes and Improvements.
Now, the Highlights of v14.0 (unique features which only Velocity Kernel offers for Yu-Devices)---
1. Core Control v2.0---
Built from scratch by me, this version of Core Control is much more efficient than the stock one. In this version, Cores are disabled according to temperature in a much more optimized manner. Further, this Core Control of mine, offers efficient Heat-Management as well as improved Battery-Life. To sum up, this is the best Core-Based Heat-Management Technique for Yu-Devices.
2. Faux Sound Control v4.1---
In this Sound Control, I have used Faux Sound v3.6 as base and on top of it, I have modified, fixed and enhanced the Driver. All of the changes are done by me! I have named this version as v4.1 because I have made 5 changes to the Driver (v3.6 + 5 Changes = v4.1). Coming to the point, this Sound Control is finally the best one. I have worked hours on it to port and fix it in the best way. Thus, now, there is no Low-Volume issue. Further, even the Negative Values work too. Also, the Volumes are boosted without distortion now i.e., higher Volumes can be achieved easily. Also, now, there is a fully functional Enable/Disable Toggle for Sound Control. To bring this feature and make it Compatible with the Modified Kernel Adiutor, I did a very clever workaround too. To sum up, this is indeed the best Sound Control for Yu-Devices with No BUGs.
3. Perfect Core-HotPlug Mechanism---
In this version of my kernel, I have added two HotPlugs, AutoSMP and State Helper. Now, you may ask what is unique about it? Well, I have just used these HotPlugs as base. On top of these HotPlugs, I have done huge modifications, wrote many new Codes and worked on them many hours and I am very happy with the results.
AutoSMP (Modified)---
I have modified this HotPlug to only work as an On/Off Toggle. I have removed all the Options and Codes to make this HotPlug lightweight. Th only function of this HotPlug now is to turn an Octa-Core Soc into a Quad-Core one retaining the HMP or big.LITTLE technique. This will allow much more Power-Savings without degrading Performance as well as lesser Heat too.
State Helper (Modified) v2.0---
I have modified this HotPlug to a great extent. The original State Helper was only meant for Normal Architectures and not big.LITTLE architectures. I worked on this HotPlug to make it support big.LITTLE architecture as well as I have Optimized it to Perform in an efficient way too. Also, I have fixed a critical BUG of this HotPlug. Further, I have removed the unnecessary Codes to make it lightweight. Since I have Optimized this HotPlug for big.LITTLE architecture, this HotPlug now offers the ability to disable the big Cluster completely. Further, this HotPlug also offers the ability to turn an Octa-Core HMP Soc to a Hexa-Core one just like the setup of Snapdragon 650. This Optimization allows for Extreme Power-Savings.
These Core-HotPlug mechanisms offer the best way to Control the Cores for managing Heat and Improving Battery-Life. The best part is that users can control these HotPlugs to find the Perfect Combination according their usage. Also, an important point about these HotPlugs is that they are not Load-Based ones. These HotPlugs don't use CPU-Resources and thus offer Better Battery-Life and Lesser CPU-Usage. To sum up, I have Modified and Optimized these HotPlug in the best possible manner. These HotPlugs are the best ones for Yu-Yureka/Yureka PLUS.
4. Perfect OverClock for Snapdragon 615 1st Gen SoC---
As you all know, our devices seem to use the 1st Gen of SD615 SoC. Probably, that's why, we have 1.5 GHz of Max. Frequency. Further, due to great variations among the same SoC, developing OC to work on every device is a very difficult task. The Max. Frequency that our SoC can run properly is 1.7GHz. Above it, the SoC fails to boot. Further, kernels which were offering OCs above 1.7GHz were containing fake OCs i.e., only the numbers change, not the actual Frequency. Now, after weeks of testing by myself as well as some very good testers, I have managed to find the perfect way of implementing the 1.7GHz and 1.2GHz OC Frequency for big and LITTLE Cluster respectively. In my implementation of the OC, I have applied an Efficient Voltage Distribution technique. This allows to not only consume the least amount of Power but also helps in achieving Perfect Stability i.e., the OC will work on every Device irrespective of Revisions. Further, people who choose to not use the OCs, then the kernel will return to use the stock voltages thus providing the same level of efficiency as the stock kernel.
5. Load Shifter---
As I have already discussed in the Load Shifter's own thread, this feature transfers the Workload from the big Cluster to the LITTLE CLuster. Even the Android Background Processes are forced to run on the LITTLE Cluster with the help of this feature. Since we use LITTLE Cluster for most of the tasks except Gaming, there are considerable Gains in Battery-Life as well as Lesser Production of Heat.
Notes---
1. Due to variations in SoC, the Sound Control will work properly at different levels of Volume for different people. For ex, value 5 of Mic Gain may be too loud for some but too low for others. So, you people have to find out the perfect value for yourselves. By the way, value 10 of Mic Gain is known to be the most suitable for every device.
2. In order to avoid conflicts, I have added a failsafe regarding Core-Control and Core-HotPlug Mechanism. This means, out of AutoSMP, State Helper and Core Control, only one can be used at a time. Even if you try to enable each one of them simultanouesly, they won't get enabled. I have done this to avoid malfunctions.
3. After manually changing the CPU Governor or Frequency, all the Cores will come online even if any HotPlug is enabled. So, you just need to re-enable any HotPlugs you were using in order to disable the Cores again.
4. Currently, AOSParadox ROM and a few other voLTE enabled ROMs too have 100% Core-Load Issue. This leads to more Heat-Generation. Further, High CPU-Usage makes Charging Time a lot slower as well as decreases the Battery-Life by a large margin. Until this BUG is fixed, nothing much can be done to improve upon these areas.
5. Sometimes, enabling Core Control may cause the ROM to hang. In this case, rebooting via ROM doesn't work. So, just press and hold Power button until the phone restarts.
6. When Core 0 gets disabled (due to Core Control or State Helper HotPlug), Adiutor fails to get Frequency and Governor information and hence shows 0MHz in Frequency Panel and Blank Space in Governor Panel. This is normal. In this case, if you need to change Governor or Frequency, then you need to disable Core Control or State Helper HotPlug as the case may be. After this, force close Adiutor and then re-open it. This will make Adiutor get CPU information again.
Recommended Settings are also updated!!!
That's it folks! My best creation till date for Yu-Devices. My aim was always to improve the experience we get from our phones and provide the users with control over everything. Today, I have achieved that goal. This became possible only due to months of hard-work by me and testing-work done by some very reliable testers.
Testers (without these people, developing a Stable and BUG-Free Kernel would be near to impossible)---
dixan43
Bijendra barman
Frozen_Lemon
Ryuk and many others were there, thanks to all of you!!!
Download Links---
For all Lollipop (5.1.1) and Yu-OS ROMs---
https://www.androidfilehost.com/?fid=385035244224394352
For Marshmallow (6.0.x) ROMs only---
https://www.androidfilehost.com/?fid=529152257862677379
For AOSParadox 3.x (6.0.x) ROM only---
https://www.androidfilehost.com/?fid=529152257862677377
Enjoy the most efficient and thoughtfully made Kernel.
Click to expand...
Click to collapse
Shoaib05 please can you make it for Yu yureka on LineageOS 14.1 ?
CAN YOU MAKE IT FULL VOLTE FOR IT CAN DO HD VOICE CALLING BUT VIDEO AND WI-FI CALLINGS ARE STILL MISSING , i searched all threads on XDA but still can't find what i am looking for.
Sent from my AO5510 using XDA-Developers Legacy app

I Clean Flash the Velocity Kernel 14.0 Old but after flashing WiFi and WiFi Hotspot Not Working
How to Solve this Issue
Flashed on CM 12.1
Sent from my YU5510A using Tapatalk

O
Sent from my AO5510 using XDA-Developers Legacy app

[MOD] BlackenedMod v1.5 (Pixel 3a / Pixel 3a XL)

Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
This script is created with the goal of improving both battery life and performance on our Pixel 3a (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: This script is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the script
3) Move the script to the following location;
/data/adb/service.d and give it the following & needed file permissions (0755)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621 in-depth video here. The installation method is the same for all generations of released Pixels!
Credits:
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-07-06
Last updated: 2019-07-21

Update!
Note: It is recommended that you reboot your phone after you have applied v1.0 so the customized changes / improvements takes full effect and is fully up & running as intended.
Version v1.0 (Initial release):
- Initial test release for Google Pixel 3a (XL)
- Enabled, and tuned, Boefflas wakelock blocker
- Enabled the backlight dimmer per default
- Disabled some useless kernel stuff for less overhead
- Some additional high quality customizations & improvements
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go!
Enjoy!

I try it thanks a lot

Update!
Note: It is recommended that you reboot your phone after you have applied v1.1 so the customized changes / improvements takes full effect and is fully up & running as intended.
Version v1.1 (Semi-major release):
- Adjusted the task scheduler for better system responsivness
- Added my own Schedutil governor profile for a better balance between performance and battery life through the whole day
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go!
Enjoy!

Update!
Note: It is recommended that you reboot your phone after you have applied v1.2 so the customized changes / improvements takes full effect and is fully up & running as intended.
Be aware that you have to flash the Busybox Magisk module by @osm0sis for getting the newest enhancements, that is featured / included on v1.2, up and running as intended!
Version v1.2 (Major release):
- Added a few crucial filesystem tweaks for improved performance (Credits goes to @pkgnex for this contribution. Be aware that you have to flash the Busybox Magisk module for getting those modifications up and running as fully intended)
- Fully removed all of the alternative task scheduler values / settings (they was only causing random freezes and lagspikes)
- Slightly adjusted the default stock CPUSet values for hopefully improved power efficiency as well as system responsivness
- Cleaned up the script on a few minor typos and what not
- Disabled a few minor CPU related loggers (experimental)
- Reduced suspend latency by enabling console_suspend
- Added a few tweaks for overall better network performance
- Shifted to Westwood TCP congestion algorithm per default
- Disabled the useless Adreno GPU frequency throttling tunable
- Disabled RCU expedited and 'replaced' it with RCU normal for improved real-time latency, CPU utilization and energy efficiency
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go!
Enjoy!

Does 'Boefflas wakelock blocker' also get enabled on stock kernel? I am thinking of getting my Mother the 3a as a present, but would prefer to stick to stock. If not I can flash EX Kernel.

xFirefly93 said:
Update!
Note: It is recommended that you reboot your phone after you have applied v1.2 so the customized changes / improvements takes full effect and is fully up & running as intended.
Be aware that you have to flash the Busybox Magisk module by @osm0sis for getting the newest enhancements, that is featured / included on v1.2, up and running as intended!
Version v1.2 (Major release):
- Added a few crucial filesystem tweaks for improved performance (Credits goes to @pkgnex for this contribution. Be aware that you have to flash the Busybox Magisk module for getting those modifications up and running as fully intended)
- Fully removed all of the alternative task scheduler values / settings (they was only causing random freezes and lagspikes)
- Slightly adjusted the default stock CPUSet values for hopefully improved power efficiency as well as system responsivness
- Cleaned up the script on a few minor typos and what not
- Disabled a few minor CPU related loggers (experimental)
- Reduced suspend latency by enabling console_suspend
- Added a few tweaks for overall better network performance
- Shifted to Westwood TCP congestion algorithm per default
- Disabled the useless Adreno GPU frequency throttling tunable
- Disabled RCU expedited and 'replaced' it with RCU normal for improved real-time latency, CPU utilization and energy efficiency
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go!
Enjoy!
Click to expand...
Click to collapse
My pixel didn't go Deep sleep with 1.2

MrPhilo said:
Does 'Boefflas wakelock blocker' also get enabled on stock kernel? I am thinking of getting my Mother the 3a as a present, but would prefer to stick to stock. If not I can flash EX Kernel.
Click to expand...
Click to collapse
It does only exist on a few selected custom kernels.
djisma86 said:
My pixel didn't go Deep sleep with 1.2
Click to expand...
Click to collapse
Deep sleep is fine for me here. Go and check which partial wakelocks that is screwing up your phone by using BBS.

How do I know it's working? Set the permissions to 755.
Sent from my Pixel 3a XL using Tapatalk

arenaboy007 said:
How do I know it's working? Set the permissions to 755.
Click to expand...
Click to collapse
The changelog isn't needed inside the service.d folder.. ;p
And.. Have you created a logs folder inside your internal storage on your device, and tried with rebooting once?

xFirefly93 said:
The changelog isn't needed inside the service.d folder.. ;p
And.. Have you created a logs folder inside your internal storage on your device, and tried with rebooting once?
Click to expand...
Click to collapse
I have not created a logs folder yet. How do I generate one? So far I moved the file in the service.d folder and media/0 folder.
Sent from my Pixel 3a XL using Tapatalk

arenaboy007 said:
I have not created a logs folder yet. How do I generate one? So far I moved the file in the service.d folder and media/0 folder.
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
You don't have to do it yourself, the automatically folder creation will be featured on v1.3, which will be released either tomorrow or at Friday.
I've to try a few minor things out first before firing it up into the wild.

I have placed the script in both the service.d and 0 folder, but no logs have been generated after reboot? I already have busybox installed too.
Edit: I noticed that some settings within EX Kernel manager have been changed, like cubic to Westwood, and fiops to cfq. I guess it worked?
Sent from my Pixel 3a XL using Tapatalk

arenaboy007 said:
I have placed the script in both the service.d and 0 folder, but no logs have been generated after reboot? I already have busybox installed too.
Edit: I noticed that some settings within EX Kernel manager have been changed, like cubic to Westwood, and fiops to cfq. I guess it worked?
Click to expand...
Click to collapse
Just make a new empty folder on the sdcard. /sdcard/logs/ Then reboot your device. After boot has completely finished wait 30-60 seconds. Then look into the new logs folder. You should see a new log file in the folder. The log tells you that the script has run successfully.

12paq said:
Just make a new empty folder on the sdcard. /sdcard/logs/ Then reboot your device. After boot has completely finished wait 30-60 seconds. Then look into the new logs folder. You should see a new log file in the folder. The log tells you that the script has run successfully.
Click to expand...
Click to collapse
It worked! I created a log folder and on next reboot saw a log inside. Thank you!
Sent from my Pixel 3a XL using Tapatalk

Not for teasing far too much right now but.. The weird maxing out on the LITTLE cluster cores have finally been fixed once and for all!
Thanks to everyone that reported about this issue that I sadly enough introduced.

xFirefly93 said:
Not for teasing far too much right now but.. The weird maxing out on the LITTLE cluster cores have finally been fixed once and for all!
Thanks to everyone that reported about this issue that I sadly enough introduced.
Click to expand...
Click to collapse
Is it possible for you to set the min clock speed to 300mhz for both clusters? This clock speed is available on the elementalx kernel.
Sent from my Pixel 3a XL using Tapatalk

arenaboy007 said:
Is it possible for you to set the min clock speed to 300mhz for both clusters? This clock speed is available on the elementalx kernel.
Click to expand...
Click to collapse
I can give it a try.

Update!
Note: It is recommended that you reboot your phone after you have applied v1.3 so the customized changes / improvements takes full effect and is fully up & running as intended.
Version v1.3 (Minor release):
- Added the needed commands so the logs folder, and the output message, will be automatically generated after each completed boot sequence (Thanks to @crian for giving a few seconds of his time helping me out with this contribution. You rock, dude!)
- Simplified a few explanations of what each section does
- Fully enabled the RET idle power state for both clusters (may, or may not, lead to slightly improved battery life for everyone)
- Most likely fixed the minor issue with the weird all over the place maximum CPU frequency bouncing on the whole LITTLE cluster
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go!
Enjoy!

Update!
Note: It is recommended that you reboot your phone after you have applied v1.4 so the customized changes / improvements takes full effect and is fully up & running as intended.
Version v1.4 (Minor release):
- Disabled RET idle state for all of the cores again (it wasn't showing any major notable power savings as expected)
- Fully disabled the 'block_validity' mount option for the /system partition (this slightly improves overall system performance)
- Enabled power efficient workqueues (improves battery life - was actually enabled on v1.3, it was just I that forgot to mention it)
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go!
Enjoy!