[SOURCE][Devlopment] .:HP Project eXtended:. For *Any* Kernel

Search This thread

spica1234

Retired Recognized Developer
Aug 1, 2010
3,081
3,362
India
HP OTF PACK V2.0 GPL V2.0

Author: Spica1234

(c) Copyrights 2011-2012 Spica1234-Xmister


Sources in Compliance with GPL And XDA is Out! (Attached Below!)

WARNING: I strongly recommend ,Don't change/modify lines I commented with "CAUTION" Those are values in specific rangs kernel accepts. Don't change those values untill you know what it means. I will not be held responsible if you toy with those values w/o knowing what It's!



Free free to message me, If you've any doubts

Please mention credit, If you use:)

Hello, I'm really inspired by the concept of Xmister bringing sysfs-procfs features in Android kernel.Big thanks to him.

I'm currently writting kernel module drivers as per Xmister's concepts of libs to export static values as Dynamic at user-land, to be changed On-The_Fly by users. That could be helpful for other Devs as well It could be implemented in *ANY* o2x kernel.
As stupidly thought hypothesis that UV controls battery consumption is completely TRUE, In my personal experience especially with UVing my O2X doesn't seem to improve battery cosumption But aggrevate PLACEBO. There are countless factors/voltages/thresholds that directly and indirectly control battery consumptions. For each and every On-The-Fly features kernel module drivers is written. That could give users an exclusive control over switching between ondemand 'powersave' and 'performance' features as per his own needs without needing to reboot. It works on kernel system call, It does need no Application to listen on event of screen of/off nor any daemon to be work constantly in background. It works by kernel sys calls feature. Kernel instantly update values provided by user.

These will give an exclusive user control upon these factors: it will accept whatever user will write, obviously value should be in range.
E.g. echo "810000" > /data/spica/mincpu1on or it can be written by opening es file explorer and writing and saving value in /data/spica/ folder

Features and work status of project:

(1) Dynamic 2nd core activation frequency:( during freq upword scaling at what freq kernel will activate 2nd core-2nd cpu)

*mincpu1on(Dynamic)( File location /data/spica/mincpu1on, defvalue of HP krnl 810000, supported acceptable values 216000-1100000, for safety concerns kernel wont accept any values except in range, boottime support -/data/spicabootcfg)

Status: Done, Implemented

(2) Dynamic 2nd core off frequncy: (during down freq ramping at what freq kernel will shuts off 2nd core-2nd cpu)

*maxcpu1off(Dynamic) ( File location /data/spica/macpu1onff, defvalue of HP krnl 860000, supported acceptable values 216000-1100000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

Status: Done, Implemented

(3) Dynamic suspended core voltage in mV( When 2nd core is in suspend state efficient minimum voltage is initial to be supplied for it's functionality)

*suspended_core_mv(Dynamic) ( File location /data/spica/suspend_core_mv, defvalue of HP krnl 750(LG defvalue-1000), supported acceptable values 3000-1000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

Status: Done, Implemented

(4) Dynamic Powersave mode on/off: (You can switch to 'PowerSave' moe as and when needed with your prefferable profile for 'powersave')

*powersave(Dynamic) ( File location /data/spica/powersave. defvalue of HP krnl 0(disable), supported acceptable values 0-3,'1' to enable 'light powersave' mode, '2' to enable 'moderate powersave' mode and '3' to enable 'very aggressive powersave' mode. When enabled kernel will smartly adjust fail-safe different various values that's being supplied,boot time support /data/spicabootcfg)
Status: Done, Implemented

(5) Dynamic DDR2(SDRAM)'s minimum frequency:(The default minimum frequency of RAM on which SDRAM works. Note: It's not maximum but minimum freq)

*ddr2_min_khz(Dynamic) ( File location /data/spica/ddr2_min_khz, defvalue of HP krnl 50000, supported acceptable values 10000-50000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

Status: Done, Implemented

(6) LPDDR2 minimum frequency:(minimum frequency for LPDDR2)

*lpddr2_min_khz(Dynamic) ( File location /data/spica/lpddr2_min_khz, defvalue of HP krnl 18000, supported acceptable values 10000-18000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

Status: Done, Implemented

(7) Max CPU Frequency during suspend, during screen off:

*maxscreenoff_cpufreq(Dynamic) ( File location /data/spica/macpu1onff, defvalue of HP krnl 503000, supported acceptable values 216000-999000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

Status: Done, Implemented

(8) Dynamic GPU frequency: (Set max gpufreq from range specified)

*gpufreq(Dynamic) ( File location /data/spica/gpufreq, defvalue of HP krnl 340000, supported acceptable values 280000-350000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

Status: Done, Implemented

(9) Dynamic VDEFrequency:

*vdefreq(Dynamic) ( File location /data/spica/vdefreq, defvalue of HP krnl 600000, supported acceptable values 550000-70000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

Status: Done, Implemented

-Coming up later OTF (Pending features yet to be done)


-Dynamic OC/UV on/off

Status: Pending

-Dynamic Ramhack

Status: Pending

-Dynamic Voodoo on/off

Status: Pending

-Dynamic SDRAM freq

Status: Pending

-Dynamic Screen off Values

Status: Pending

-Dynamic Fuel Gauge Reset

Status: Pending

-Dynamic Vibrator Intensity

Status: Pending

-Dynamic 2nd core on pedding ms

Status: Pending

-Dynamic 2nd core off pedding ms

Source?: Attached Below!

Credits:
Xmister
 

Attachments

  • RC12-RevOTF-Updated.patch
    48.3 KB · Views: 106
Last edited:

civato

Inactive Recognized Contributor
Apr 20, 2011
4,296
19,224
I m a nooby in this phone world but what you are doing sounds really good and way over my head , so I'm looking forward to it.
 
  • Like
Reactions: spica1234

spica1234

Retired Recognized Developer
Aug 1, 2010
3,081
3,362
India
Project Status update: (06-02-2012)
+powersave mode has 6 profiles nownote: powersave & nitros doesnt touch OC/UV). File location /data/spica/powersave. Accepts seven user supplied values '0' to '6'
0-disable
1-light powersave
2-moderate powersave
3-aggressive powersave
4-powersave '1' only during screen off
5-powersave '2' only during screen off
6-powersave '3' only during screen off
+"nitros" -performance mode. Responsible file location /data/spica/nitros. Accepts only two user supplied values '0' (disable) & '1' (enable)

Sent from my LG-P990 using Tapatalk
 
Last edited:

Barnabe619

Member
Mar 31, 2011
31
0
Project Status update: (06-02-2012)
+powersave mode has 6 profiles nownote: powersave & nitros doesnt touch OC/UV). File location /data/spica/powersave. Accepts seven user supplied values '0' to '6'
0-disable
1-light powersave
2-moderate powersave
3-aggressive powersave
4-powersave '1' only during screen off
5-powersave '2' only during screen off
6-powersave '3' only during screen off
+"nitros" -performance mode. Responsible file location /data/spica/nitros. Accepts only two user supplied values '0' (disable) & '1' (enable)

Sent from my LG-P990 using Tapatalk

Are these profiles usable in SetFsb ?

Nice Work it seems interesting :)
 

spica1234

Retired Recognized Developer
Aug 1, 2010
3,081
3,362
India
Project status update(14/02/2012):
-sources will be out after 2 days for o2x developers for *any* kernel to run with

*Results: (with 2 days testing with same usage and environment)
:-Results were obtained through consumed averaged mA, remaining averaged mV, estimated averaged mV,screen state off idle state averaged mA consumption, screen on averaged mA consumption within same usage of 3 hrs wifi, 1 hours of 3g . results may not be accurate though but identical
-In my initial testing within same environment of ROM and same kernel with and without OTF Revised pack,

+OTF kernel delivers ~10% more battery life with 'powersave' profile "1"
+OTF kernel delivers ~16% more battery life with 'powersave' profile "2"
+OTF kernel delivers ~21% more battery life with 'powersave' profile "3"
-And with OTF Revised Values no freeze/BSOD events occured within testing period
+OTF Kernel delivers slight more responsiveness with 'nitros' profile "1" w/o affecting battery life in compare to 'powersave' profile "0"

Sent from my LG-P990 using Tapatalk
 
Last edited:

vadonka

Senior Member
Jul 25, 2007
2,060
2,740
Debrecen
Project status update(14/02/2012):
-sources will be out after 2 days for o2x developers for *any* kernel to run with

*Results: (with 2 days testing with same usage and environment)
:-Results were obtained through consumed averaged mA, remaining averaged mV, estimated averaged mV,screen state off idle state averaged mA consumption, screen on averaged mA consumption within same usage of 3 hrs wifi, 1 hours of 3g . results may not be accurate though but identical
-In my initial testing within same environment of ROM and same kernel with and without OTF Revised pack,

+OTF kernel delivers ~10% more battery life with 'powersave' profile "1"
+OTF kernel delivers ~16% more battery life with 'powersave' profile "2"
+OTF kernel delivers ~21% more battery life with 'powersave' profile "3"
-And with OTF Revised Values no freeze/BSOD events occured within testing period
+OTF Kernel delivers slight more responsiveness with 'nitros' profile "1" w/o affecting battery life in compare to 'powersave' profile "0"

Sent from my LG-P990 using Tapatalk

looking forward to the source :)
 
  • Like
Reactions: spica1234

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    HP OTF PACK V2.0 GPL V2.0

    Author: Spica1234

    (c) Copyrights 2011-2012 Spica1234-Xmister


    Sources in Compliance with GPL And XDA is Out! (Attached Below!)

    WARNING: I strongly recommend ,Don't change/modify lines I commented with "CAUTION" Those are values in specific rangs kernel accepts. Don't change those values untill you know what it means. I will not be held responsible if you toy with those values w/o knowing what It's!



    Free free to message me, If you've any doubts

    Please mention credit, If you use:)

    Hello, I'm really inspired by the concept of Xmister bringing sysfs-procfs features in Android kernel.Big thanks to him.

    I'm currently writting kernel module drivers as per Xmister's concepts of libs to export static values as Dynamic at user-land, to be changed On-The_Fly by users. That could be helpful for other Devs as well It could be implemented in *ANY* o2x kernel.
    As stupidly thought hypothesis that UV controls battery consumption is completely TRUE, In my personal experience especially with UVing my O2X doesn't seem to improve battery cosumption But aggrevate PLACEBO. There are countless factors/voltages/thresholds that directly and indirectly control battery consumptions. For each and every On-The-Fly features kernel module drivers is written. That could give users an exclusive control over switching between ondemand 'powersave' and 'performance' features as per his own needs without needing to reboot. It works on kernel system call, It does need no Application to listen on event of screen of/off nor any daemon to be work constantly in background. It works by kernel sys calls feature. Kernel instantly update values provided by user.

    These will give an exclusive user control upon these factors: it will accept whatever user will write, obviously value should be in range.
    E.g. echo "810000" > /data/spica/mincpu1on or it can be written by opening es file explorer and writing and saving value in /data/spica/ folder

    Features and work status of project:

    (1) Dynamic 2nd core activation frequency:( during freq upword scaling at what freq kernel will activate 2nd core-2nd cpu)

    *mincpu1on(Dynamic)( File location /data/spica/mincpu1on, defvalue of HP krnl 810000, supported acceptable values 216000-1100000, for safety concerns kernel wont accept any values except in range, boottime support -/data/spicabootcfg)

    Status: Done, Implemented

    (2) Dynamic 2nd core off frequncy: (during down freq ramping at what freq kernel will shuts off 2nd core-2nd cpu)

    *maxcpu1off(Dynamic) ( File location /data/spica/macpu1onff, defvalue of HP krnl 860000, supported acceptable values 216000-1100000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

    Status: Done, Implemented

    (3) Dynamic suspended core voltage in mV( When 2nd core is in suspend state efficient minimum voltage is initial to be supplied for it's functionality)

    *suspended_core_mv(Dynamic) ( File location /data/spica/suspend_core_mv, defvalue of HP krnl 750(LG defvalue-1000), supported acceptable values 3000-1000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

    Status: Done, Implemented

    (4) Dynamic Powersave mode on/off: (You can switch to 'PowerSave' moe as and when needed with your prefferable profile for 'powersave')

    *powersave(Dynamic) ( File location /data/spica/powersave. defvalue of HP krnl 0(disable), supported acceptable values 0-3,'1' to enable 'light powersave' mode, '2' to enable 'moderate powersave' mode and '3' to enable 'very aggressive powersave' mode. When enabled kernel will smartly adjust fail-safe different various values that's being supplied,boot time support /data/spicabootcfg)
    Status: Done, Implemented

    (5) Dynamic DDR2(SDRAM)'s minimum frequency:(The default minimum frequency of RAM on which SDRAM works. Note: It's not maximum but minimum freq)

    *ddr2_min_khz(Dynamic) ( File location /data/spica/ddr2_min_khz, defvalue of HP krnl 50000, supported acceptable values 10000-50000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

    Status: Done, Implemented

    (6) LPDDR2 minimum frequency:(minimum frequency for LPDDR2)

    *lpddr2_min_khz(Dynamic) ( File location /data/spica/lpddr2_min_khz, defvalue of HP krnl 18000, supported acceptable values 10000-18000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

    Status: Done, Implemented

    (7) Max CPU Frequency during suspend, during screen off:

    *maxscreenoff_cpufreq(Dynamic) ( File location /data/spica/macpu1onff, defvalue of HP krnl 503000, supported acceptable values 216000-999000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

    Status: Done, Implemented

    (8) Dynamic GPU frequency: (Set max gpufreq from range specified)

    *gpufreq(Dynamic) ( File location /data/spica/gpufreq, defvalue of HP krnl 340000, supported acceptable values 280000-350000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

    Status: Done, Implemented

    (9) Dynamic VDEFrequency:

    *vdefreq(Dynamic) ( File location /data/spica/vdefreq, defvalue of HP krnl 600000, supported acceptable values 550000-70000, for safety concerns kernel wont accept any values except in range,boot time support /data/spicabootcfg)

    Status: Done, Implemented

    -Coming up later OTF (Pending features yet to be done)


    -Dynamic OC/UV on/off

    Status: Pending

    -Dynamic Ramhack

    Status: Pending

    -Dynamic Voodoo on/off

    Status: Pending

    -Dynamic SDRAM freq

    Status: Pending

    -Dynamic Screen off Values

    Status: Pending

    -Dynamic Fuel Gauge Reset

    Status: Pending

    -Dynamic Vibrator Intensity

    Status: Pending

    -Dynamic 2nd core on pedding ms

    Status: Pending

    -Dynamic 2nd core off pedding ms

    Source?: Attached Below!

    Credits:
    Xmister
    9
    Vdefreq stands for Video Decoding Engine Frequency. You can manually change frequencies it works on. Power save should be zero.
    When power save is 1-6 it overrides what ever values you have selected with all above to power save. Power save 1 means light power save,2 medium and 3 aggressive power save. Power save 1 2 3 works during screen on and off. Power save 4 5 6 is profile 1 2 3 in order but works only during screen off.
    Power save significantly enhances battery life up to 20% in compare to non otf kernel based on same source:)

    Sent from my LG-P990 using xda premium
    8
    Project status update(14/02/2012):
    -sources will be out after 2 days for o2x developers for *any* kernel to run with

    *Results: (with 2 days testing with same usage and environment)
    :-Results were obtained through consumed averaged mA, remaining averaged mV, estimated averaged mV,screen state off idle state averaged mA consumption, screen on averaged mA consumption within same usage of 3 hrs wifi, 1 hours of 3g . results may not be accurate though but identical
    -In my initial testing within same environment of ROM and same kernel with and without OTF Revised pack,

    +OTF kernel delivers ~10% more battery life with 'powersave' profile "1"
    +OTF kernel delivers ~16% more battery life with 'powersave' profile "2"
    +OTF kernel delivers ~21% more battery life with 'powersave' profile "3"
    -And with OTF Revised Values no freeze/BSOD events occured within testing period
    +OTF Kernel delivers slight more responsiveness with 'nitros' profile "1" w/o affecting battery life in compare to 'powersave' profile "0"

    Sent from my LG-P990 using Tapatalk
    6
    Final testing goin on
    RC12-R final testing goin on, inCall BSOD fixed, if all went well with RevisedOTF(almost goin well till now) then it will be out very soon.
    Powersave 1 results overall ~6% lesser power consumption and ~5-7% longer battery life in compared to same kernel source w/o R-OTF
    Powersave 2 results overall ~8% lesser power consumption and ~7-9% longer battery life in compared to same kernel source w/o R-OTF
    Powersave 3 results overall ~10% lesser power consumption and ~9-12% longer battery life in compared to same kernel source w/o R-OTF
    Big thanks to carburano,superskill,yan73,stevie,shreeprajay etc for being participant for BREAKTHROUGH RevisedOTF implementation and success.
    -If i will get time i will write a module driver for Dynamic-Auto VM Management for assured no cpu memory leakage over hours and days.
    Revolution has begun, as promised:)

    Everything seems stable now the sources will be out for other Developers:)

    Sent from my LG-P990 using Tapatalk
    2
    Thank you bro. I will:) thanks for helping hand:)

    Sent from my LG-P990 using Tapatalk

    i just see that this value is adjustable in the otf, in that case modify the default value too, set back to 1000. it seems its very sensitive and easily issued the endcall bsod. its still can be adjustable by the users. for me even the 850mV is working but many users have problem if this lower than 1000mV.

    by the way sent you an msg :)