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

Is SR3 Ready as PreSR3 TestBuild?

  • Yes

    Votes: 95 75.4%
  • No

    Votes: 31 24.6%

  • Total voters
    126
Search This thread

Skyfall007

Senior Member
Nov 3, 2011
723
301
@spica for a few days i have a problem.. when i turn off my phone battery is fully discharging... i have tried many times to flash the rom and the kernel again(with full wipe) but it doesn't work. What should I do?
 

jaspi72

Senior Member
Sep 15, 2011
168
12
hi,

is there a description for all available powersave modes and how to activate/change them? I couldn't find the to-be-written-tutorial mentioned in the first post ;).

thx!

(RC12) Dynamic On-The-Fly 'powersave' 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 (RC12)
 

McGiverGim

Senior Member
Nov 7, 2008
179
33
Valladolid
Spica, one bad new... I've been testing your great kernel and is stable and smooth... but the memory leak remains. I don't know if is a CPU leak, a wifi leak or another kind of leak, but after two days without rebooting, the phone is slow and the memory free is low...

I will reboot the phone, is not a very big problem... but if you have time and want to try something ;-)

Regards!
 

eyronic

Senior Member
Mar 12, 2011
305
74
Spica, one bad new... I've been testing your great kernel and is stable and smooth... but the memory leak remains. I don't know if is a CPU leak, a wifi leak or another kind of leak, but after two days without rebooting, the phone is slow and the memory free is low...

I will reboot the phone, is not a very big problem... but if you have time and want to try something ;-)

Regards!

What is your mincpu1on and maxcpu1off?
 
Yes, which I think is better than flashing PP10 over stock, right?

I flashed and tested so many variations (always full wipe by running backtoext3 first) without keeping a log but if I recall correctly, I experienced problems with DM stock +SR3 +PP10

If you want to convert to ext4 you can use pp10r...
But if you are happy with your configuration you should remain with it :)

Inviato con il mio P990 DjangoManouche!
 

PAIIITET

Senior Member
Apr 3, 2011
152
37
42
Tomsk
Spica, tell me honestly, are you kidding us all?
Changing variables GPUFREQ, POWERSAVE, etc. it's just a placebo effect?

For example, why the change GPUFREQ from 280 to 380 did not affect the tests.

See, Quadrant 2.0

CPU 1,2 Ghz \ GPU 280
2D = 439
3D = 2415

CPU 1,2 Ghz \ GPU 350
2D = 442
3D = 2530


CPU 1,2 Ghz \ GPU 400
2D = 439
3D = 2467

Change POWERSAVE from 0 to 2 and did not affect the result. Always get about 3050 points +-20

Antutu

CPU 1,2 Ghz \ GPU 400
2D = 577
3D = 1260

CPU 1,2 Ghz \ GPU 280
2D = 582
3D = 1265

CPU 1,2 Ghz \ GPU 340 \ PowerSave 3
2D = 580
3D = 1218

Strong Vibra also be considered a fake, because only works on the keyboard and touch buttons.
On call and SMS strong vibration does not work.
 

spica1234

Retired Recognized Developer
Aug 1, 2010
3,081
3,362
India
Spica, tell me honestly, are you kidding us all?
Changing variables GPUFREQ, POWERSAVE, etc. it's just a placebo effect?

For example, why the change GPUFREQ from 280 to 380 did not affect the tests.

See, Quadrant 2.0

CPU 1,2 Ghz \ GPU 280
2D = 439
3D = 2415

CPU 1,2 Ghz \ GPU 350
2D = 442
3D = 2530


CPU 1,2 Ghz \ GPU 400
2D = 439
3D = 2467

Change POWERSAVE from 0 to 2 and did not affect the result. Always get about 3050 points +-20

Antutu

CPU 1,2 Ghz \ GPU 400
2D = 577
3D = 1260

CPU 1,2 Ghz \ GPU 280
2D = 582
3D = 1265

CPU 1,2 Ghz \ GPU 340 \ PowerSave 3
2D = 580
3D = 1218

Strong Vibra also be considered a fake, because only works on the keyboard and touch buttons.
On call and SMS strong vibration does not work.

Powersave needs one time screen off for 2-5 minutes untill it takes effects,
And about GPU, GPU works on 3D not 2D. CPU works on 2D.
See, Quadrant 2.0

CPU 1,2 Ghz \ GPU 280
2D = 439
3D = 2415

CPU 1,2 Ghz \ GPU 350
2D = 442
3D = 2530


CPU 1,2 Ghz \ GPU 400
2D = 439
3D = 2467
GPU works on 3D rendering .above you can see progress in 3D score. It definately does work. and any benchmarks works on SW not HW so it's results depends on many thing, free RAM, CPU load etc and it's results will be varying wont be the same. and evenif it shows no more results at 400mhz then it's limitation of HW it wont even show more on 500:)
You can see and check codes written in HP eXteneded thread, nothing's fake:). If something not working then may be it's HW.And Powersave overides your values with it's. If you've set whatever GPU/VDEfreq powersave and nitro over rides it with Kernel's powersave function values Powersave changes various values GPFREQ,VDEFREQ,LOWCOREMV,LOWCPUMV,DDR@MINKHZ,LPDDR2MINKHZ,CPU1ON frequency and off frequency. suppose if you have set vdefreq 700000 and gpufreq=400000 and if you activate powersave 1/2/3 profile powersave will set vdefreq to 620000 same applicable for gpufreq=340 powersave and nitro disable whatever values you've set.and activate powersave/nitro kernel set values. So whatever frequency of gpu vde you set it gets override by powersave. BTW Strong vibration I don't use it I gotta check.
If you can understand C then please read OTF codes from extended thread, no mistakes from my side. If something's not working then may be its HW limit:)

if (PWONOFF == 1)
{
NITROONOFF = 0;
NVRM_CPU1_ON_MIN_KHZ = 810000;
GPUFREQ = 320000;
VDEFREQ = 630000;
NVRM_AP20_DDR2_MIN_KHZ = 40000;
NVRM_AP20_LPDDR2_MIN_KHZ = 15000;
NVRM_AP20_LOW_CORE_MV = 910;
NVRM_AP20_LOW_CPU_MV = 760;
NVRM_CPU1_OFF_PENDING_MS = 500;
}
else if (PWONOFF == 2)
{
NITROONOFF = 0;
NVRM_CPU1_ON_MIN_KHZ = 810000;
GPUFREQ = 310000;
VDEFREQ = 620000;
NVRM_AP20_DDR2_MIN_KHZ = 30000;
NVRM_AP20_LPDDR2_MIN_KHZ = 12000;
NVRM_AP20_LOW_CORE_MV = 895;
NVRM_AP20_LOW_CPU_MV = 750;
NVRM_CPU1_OFF_PENDING_MS = 400;
}
else if (PWONOFF == 3)
{
NITROONOFF = 0;
NVRM_CPU1_ON_MIN_KHZ = 1099000;
GPUFREQ = 300000;
VDEFREQ = 610000;
NVRM_AP20_DDR2_MIN_KHZ = 10000;
NVRM_AP20_LPDDR2_MIN_KHZ = 12000;
NVRM_AP20_LOW_CORE_MV = 880;
NVRM_AP20_LOW_CPU_MV = 740;
NVRM_CPU1_OFF_PENDING_MS = 200;
}
else if (NITROONOFF == 1)
{
PWONOFF = 0;
NVRM_CPU1_ON_MIN_KHZ = 750000;
GPUFREQ = 390000;
VDEFREQ = 700000;
NVRM_AP20_DDR2_MIN_KHZ = 50000;
NVRM_AP20_LPDDR2_MIN_KHZ = 18000;
NVRM_AP20_LOW_CORE_MV = 925;
NVRM_AP20_LOW_CPU_MV = 770;
NVRM_CPU1_OFF_PENDING_MS = 900;
}
else if ((PWONOFF == 4) || (PWONOFF == 5) || (PWONOFF == 6))
{
NITROONOFF = 0;
NVRM_CPU1_ON_MIN_KHZ = 810000;
GPUFREQ = 380000;
VDEFREQ = 680000;
NVRM_AP20_DDR2_MIN_KHZ = 50000;
NVRM_AP20_LPDDR2_MIN_KHZ = 18000;
NVRM_AP20_LOW_CORE_MV = 925;
NVRM_AP20_LOW_CPU_MV = 770;
NVRM_CPU1_OFF_PENDING_MS = 800;
};
as above powersave and nitro overrides whatever values you've set with profile values
Full refrence https://raw.github.com/spica234/HP-2X-V20Q/master/drivers/cpufreq/cpufreq.c
 
Last edited:

Thorbear

Senior Member
Oct 8, 2011
55
6
Uppsala
Spica, one bad new... I've been testing your great kernel and is stable and smooth... but the memory leak remains. I don't know if is a CPU leak, a wifi leak or another kind of leak, but after two days without rebooting, the phone is slow and the memory free is low...

I will reboot the phone, is not a very big problem... but if you have time and want to try something ;-)

Regards!

same here.. after about 24 hours of up time the slowdown makes my phone pretty much unusable (but just rebooting is more of a little annoyance than a problem)

on the other hand my phone can finally handle the brilliance of the HP-kernel without freezes with the latest release =D
much appreciated!
 
  • Like
Reactions: spica1234

spica1234

Retired Recognized Developer
Aug 1, 2010
3,081
3,362
India
same here.. after about 24 hours of up time the slowdown makes my phone pretty much unusable (but just rebooting is more of a little annoyance than a problem)

on the other hand my phone can finally handle the brilliance of the HP-kernel without freezes with the latest release =D
much appreciated!

Which version u are using w/ compcache?

Sent from my LG-P990 using Tapatalk
 

mascaras

Member
Mar 5, 2012
15
0
spica,same slowdowns problem here,rebooting solves,but is annoying.v20q sr3r2 oc no comp
 
Last edited:

krajova

Member
Sep 29, 2011
39
4
I have slow down after 12-14 h but its only when I use it for calling. To specify when I click on some contact and then I have choice skype, call or something else... I click on call and it takes 10-20 seconds for the device to star calling? Restart solves it. Django 1.1, No OC / comp

Otherwise the battery is INSANE. From 09:20-20:30 - I lost only 40% but I used it for music, made photos, calls, web.. I actually don't know if I have ever used my optimus so much.
 

zic1

Senior Member
Nov 9, 2011
172
11
Hi Spica1234,
I just installed your version SR3R2 Final NoOC(Alike Stock) without Compcache on rebuild stock v20q ROM. Please, can you explain how to use voodoo control plus beacuse after installing your kernel this app in not working anymore. Tried to reinstall voodoo but without success...
Cheers
EDIT: After reboot voodoo app is working again!
 
Last edited:

DeepRed89

Senior Member
Sep 2, 2011
141
8
Salerno
hi spica, with the new sr3r2 i've problem to set the strong vibe...i delete 0 and write 1, but the strong vibe don't go...why?
 

Ferrum Master

Senior Member
Dec 22, 2010
1,117
277
Rīga
Hi Spica1234,
I just installed your version SR3R2 Final NoOC(Alike Stock) without Compcache on rebuild stock v20q ROM. Please, can you explain how to use voodoo control plus beacuse after installing your kernel this app in not working anymore. Tried to reinstall voodoo but without success...
Cheers

No problems with Voodoo here... clean dalvik and cache and try again to install.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 158
    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:p)
    -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!
    23
    Got an hour of time today.

    Finished writing HP Pro RT(Real Time) Scheduler and now remained to restore my backup and to merge changes into kernel. And to check for testing for stability as I/O RT processing changes are known for system instabilities.
    Users interested to test can PM me so as soon as I could get time to restore my OS to build kernel

    Info about HP Pro RT(Real Time) Schedular Load Balancing For Any Kernel For Any Devices:

    {*} periodicallyscanning running processes and auto prioritizing of processes for new processes for adequate load balancing for the max Real Time responsiveness
    {*} To be merged with OOM and android low memory killer to make low memory killer easier
    {*} unrelating with cpu prioritizing and making stand alone max Input/Output throughput
    {°} Many more still pending. Limiting factor for me is time:/

    Main aim set to be achieved:
    Max responsiveness during Multi-Tasking and performance related to snappiness by intellectualy prioritizing dynamic runtime resource management as per load requirement and to limit cpu and io as and when needed as per actual load for max battery

    Q: Why it was needed(for me)?
    A: Because only optimizing cpu management isnt crucial as performance depends on I/O resourses management aswell

    Edit:
    More implementation to be done in OTFV3.0:
    + memory leak to be fixed present in OTFv2
    +DCA (Direct Cache(L1 &L2) Access) for OTF V3.0
    +Continueous Memory Alignment for OTFV3 for faster OTF module loading and unloading and for faster OTF access
    +To be fixxed unaligned 64K access caused by memcpy() in OTFV2
    +to implement 8K Unaligned Direct Memory Access for OTFV3.0


    Sent from my LG-P990 using Tapatalk 2
    22
    HP Pro SuperSonic12 TestBuild:

    HP Pro SuperSonic12 Embeded TestBuild:

    Changelogs:

    +As always alike other SuperSonic series compiled with HP Pro SuperSonic Toolchain
    +More ARM Multi-Threading improvements for the best performance. And better Parallel Multi-Tasking
    + ARM isb mode Level 1(L1) & Level 2(L2) 32 bit cpu-cache acess with 50% L1 to L2 reserved response with Full 50% cache-flushing for better smoothness & more responsiveness. CPU L1 and L2 Cache is the more specific area this build is optimized for.
    +Various memory leaks fixed, now always free ram near about ~200MB anytime. No micro-lag even after hours.
    +Faster Application loading and processing, Faster gallery loading
    +Visibly Optimized 2D/3D. Visible improvements in FPS in games and various benchmarks. 2D FPS Atleast +5 FPS and 3D atleast +5-6 FPS
    +Using extensive ARM Powermanagement
    +Structures same as previous built re-mapped in 32 bit boundaries.
    +Ferrum bug fixed.
    +Various hysteresis values change for stability
    +I guess this is the smoothest and fastest build in SuperSonic Series.
    +Major Break-Through Performance Oriented Supersonic series release

    Download:

    http://db.tt/5Ky6uldU
    20
    Thanks to all HP users

    Alright guys, This is a Final Build for a while, as I'm starting ICS kernel development, But I dont want this GB kernel development to be abandoned, Because It's really deep hard work of mine. And it's the journey I begin with here on XDA. So I'll always update it once in every 10-15 day and whenever LG releases new kernel sources to give you maxium the Best Of Me:) I must Thank every HP users who joined journey since Beta to SR3R. If I've not recieved such a good appreciation then I might have not come so far, Thanks to everybody:)

    I do hold a good job, But after being married, it is hard to afford many expensises which comes after daily expense. One of them is HDD primary failure. I'm still using my Data Traveller(mini HD) as a main HD which was provided to me by my company I work for:). Although I've save almost half amount(some by my job salary and some by donators who donated to me, thanking them) for buying new HDD. I dont even like to ask for but I hope you can understand, If I've not lost my HDD then I even might have put no DONATE button either like the past days:)

    So if anybody who wishes to support my serious dedication and My O2X Development can DONATE to me now . DONATE link:) It will help me buy a new HDD sooner to continue my Further Development at full force:)

    And great thanks to every Donators who has donated so far:) Thanks to SuperSkill, Striatrum_bdr, wapz, Basil 123, Steieve, yan73, civato, carburano, psonic2k, PhunKee, zerocoolrider (Sorry If i have forgotten anybody's name, Please remind me)
    15
    Everybody is showing him the deepest respect and is thankful, he's work is amazing, but i'm refreshing this thread probably every 30min, because he told us he will upload it yesterday, so i don't think it is unrespectful when somebody asks for uploading. This waiting is just killing you.

    Sorry yesterday it was ready fully stable and responsive but with inCall BSOD . If i remove my OTF then no BSOD And fully stable i could either name it SR3. But i want to launch RC12-R without OTFcause that's my very much hardwork with proven benefits and w/o adding nothing new i dont wanna increment SR and RC series by nothing new but same old with recompile with whatever worked. Cause wrting new codes for new implements is not enough atleast for platform OS for mobile where every phone has different story with different reactions so need a lot testing. I am really sorry for giving commitment for release, from now on words I wont commit nor mention anything untill next version is fully ready. Once again Sorry for the commit of release I made. I returned home from job now and working single hand for BSOD fix for my OTF. It could take a minute or hours to get it solved. Thank you once again for the patience and Sorry once again for the wrong estd commit I gave:)

    Sent from my LG-P990 using Tapatalk