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.1
- Adjusted scripts for better functionality and less errors.
- Added the option to set whichever governor you’d like on boot (NOT TESTED)
To do this: use root explorer to get to /system/etc/init.d
long press on 01cpu
select open in text editor
change the variables at the top
is the stock setting. To set one at boot, simply change ONDEMAND to =0, and one of the other two to =1
- Custom ringtone fix (credit to kejar31)
- Potential Programming menu fix (someone test please, i’m not sure)
Change Log for 2.0:
- Sysctl.conf adjustments:
- Added rm /dev/log/main for extra performance/free memory
- Changed 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
- Added new Interactive and Conservative kernel scaling governors (credit Milestone team)
(Credit Cyanogenmod GITHub for this, source is here: https://github.com/CyanogenMod/cm-ke…/governors.txt)
+ significantly more responsive to ramp cpu up when required (UI interaction)
+ more consistent ramping, existing governors do their cpu load sampling in a workqueue context, the ‘interactive’ governor does this in a timer context, which gives more consistent cpu load 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.
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 environment.
The governor is tweaked in the same manner as the “ondemand” governor
through sysfs with the addition of:
freq_step: this describes what percentage steps 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.
Basically, this means more speed and battery life control
- Adjusted 01cpu for a better sampling rate if the new conservative governor is found.
- Added script: gov
gov allows you to control which governor you use; ondemand, conservative, or interactive. The function is:
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.
To remove data throttling, click this:
rubiX Focused 1.9.7, back and better than ever – Page 3 – Droid Forum – Verizon Droid & the Motorola Droid Forum
Credit to Plower.Net
How to install:
Place on SDCard
Bootstrap Recovery via Bootstrap App
Reboot to Clockwork Mod Recovery
Wipe data/factory reset
Select install from sdcard
Choose zip from sdcard
If you like my work, please support me going to Google I/O Developer’s Conference 2011! All donations received are going towards a plane ticket.