Raptor912
Android Enthusiast
All Credit goes to DROD2169!! I am just passing along the goods!
IF YOU USED THE NEW SCRIPT, YOU MUST REBOOT AFTER INSTALL AND INITIAL SETUP
This script runs on first boot to scan the SDCard rubiX Folder for apps. If they are there, it copies them to /data/app and corrects their permissions. Reboot for this to take effect.
YOU MUST wipe data before install.
Change Log for 2.0:
gov -ondem for the ondemand governor
gov -cons for the conservative governor
gov -inter for the interactive governor
Alternately, these can be changed via SetCPU or Droid Overclock.
How to install:
Download
Place on SDCard
Bootstrap Recovery via Bootstrap App
Reboot to Clockwork Mod Recovery
Wipe [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]data[/FONT][/FONT][/COLOR]/factory reset[/COLOR]
Select install from sdcard
Choose zip from sdcard
select rubiXBlurry2.0.zip
Select yes
Reboot
Enjoy!
RubiX Blurry 2.0
[/FONT]
YOU MUST BE ON 2.3.340 OTA FOR THIS TO WORK
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
ALSO NOTE: IF YOU INSTALLED THE NEW TRANQUILITY, THE TOOLBOX WILL INSTALL UNLESS YOU SBF BEFORE INSTALL. THIS IS TRUE FOR ANY ROM, NOT JUST RUBIX.
IF YOU USED THE NEW SCRIPT, YOU MUST REBOOT AFTER INSTALL AND INITIAL SETUP
This script runs on first boot to scan the SDCard rubiX Folder for apps. If they are there, it copies them to /data/app and corrects their permissions. Reboot for this to take effect.
YOU MUST wipe data before install.
Change Log for 2.0:
- Sysctl.conf adjustments:
[/FONT][/COLOR] vm.dirty_background_ratio to [/COLOR]70 from 60
Conservative:
Basically, this means more speed and battery life control- Added rm /dev/log/main for extra performance/free memory
- [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]Changed[/FONT][/FONT][/COLOR] [/COLOR]NO_NEW_FAIR_SLEEPERS to NO_FAIR_SLEEPERS; this was a typo, as there are no new fair sleepers in the dx kernel already.
- Cleaned up the /system/app folder
The following market apps were further removed:
Talkback
Kickback
Soundback
[/COLOR]
Talkback
Kickback
Soundback
- Added new Interactive and Conservative kernel scaling governors (credit Milestone team)
This is a Droid X first. These two governors bring a big difference to the table; here is what they do:
(Credit Cyanogenmod GITHub for this, source is here: https://github.com/Cyano...d/cm-ke.../governors.txt)
Interactive:
(Credit Cyanogenmod GITHub for this, source is here: https://github.com/Cyano...d/cm-ke.../governors.txt)
Interactive:
Advantages:
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]load[/FONT][/FONT]
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]load[/FONT][/FONT]
[/COLOR] sampling in a workqueue context, the 'interactive' governor does this in a timer context, which gives more consistent cpu [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]load[/FONT][/FONT][/COLOR][/COLOR] sampling.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
+ higher priority for cpu frequency increase, rt_workqueue is used for scaling up, giving the remaining tasks the cpu performance benefit, unlike existing governors which schedule rampup work to occur after your performance starved tasks have completed.
Conservative:
The CPUfreq governor "conservative", much like the "ondemand"
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]environment[/FONT][/FONT][/COLOR].
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]steps[/FONT][/FONT][/COLOR][/COLOR] the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
[/COLOR]
governor, sets the CPU depending on the current usage. It differs in
behaviour in that it gracefully increases and decreases the CPU speed
rather than jumping to max speed the moment there is any load on the
CPU. This behaviour more suitable in a battery powered [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]environment[/FONT][/FONT][/COLOR].
The governor is tweaked in the same manner as the "ondemand" governor
through sysfs with the addition of:
freq_step: this describes what percentage [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]steps[/FONT][/FONT][/COLOR][/COLOR] the cpu freq should be
increased and decreased smoothly by. By default the cpu frequency will
increase in 5% chunks of your maximum cpu frequency. You can change this
value to anywhere between 0 and 100 where '0' will effectively lock your
CPU at a speed regardless of its load whilst '100' will, in theory, make
it behave identically to the "ondemand" governor.
down_threshold: same as the 'up_threshold' found for the "ondemand"
governor but for the opposite direction. For example when set to its
default value of '20' it means that if the CPU usage needs to be below
20% between samples to have the frequency decreased.
[/COLOR]
- Adjusted 01cpu for a better sampling rate if the new conservative governor is found.
- Added script: gov
gov -ondem for the ondemand governor
gov -cons for the conservative governor
gov -inter for the interactive governor
Alternately, these can be changed via SetCPU or Droid Overclock.
How to install:
Download
Place on SDCard
Bootstrap Recovery via Bootstrap App
Reboot to Clockwork Mod Recovery
Wipe [COLOR=blue ! important][FONT=inherit ! important][COLOR=blue ! important][FONT=inherit ! important]data[/FONT][/FONT][/COLOR]/factory reset[/COLOR]
Select install from sdcard
Choose zip from sdcard
select rubiXBlurry2.0.zip
Select yes
Reboot
Enjoy!
RubiX Blurry 2.0
[/FONT]
)
