19 replies to this topic

[PillClinton]

If you've ever tried to change your phone's default I/O scheduler and/or CPU Governor but found that the values did not stick after a reboot, hopefully this thread will help you out! With some @$$istance from

Please Login or Register to see this Hidden Content

here on DroidRzr &

Please Login or Register to see this Hidden Content

over at XDA, I have been able to accomplish what I originally set out to do and more. INSERT STANDARD DISCALAIMER HERE:

I'm not responsible for any damage you do to your phone!! Read instructions carefully!

Thanks to:

Please Login or Register to see this Hidden Content

for the guidance & good conversation.

Please Login or Register to see this Hidden Content

for the original thread on XDA & putting in the work & tweak time to make the extra governors/schedulers work on our Razrs!

Please Login or Register to see this Hidden Content

for the great writeup on governors/schedulers.

Before doing anything, if you'd like some background information on what governors & schedulers are, what they do, & which ones are available for our Razrs,

Please Login or Register to see this Hidden Content

.

To install additional some extra kernel modules, CPU governors, and I/O schedulers, read all directions and the rest of the thread carefully, make a backup, then flash both files from this post:

Please Login or Register to see this Hidden Content

Once you have successfully installed everything, to enable your choice of governors and schedulers to boot up as the defaults, follow these steps:

1.) Open up Notepad/

Please Login or Register to see this Hidden Content

or something similar
2.) Copy & paste the following into a new document:

insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpufreq_pegasusq.ko
echo "pegasusq" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "sio" > /sys/block/mmcblk0/queue/scheduler

3.) Go to "Save As" and choose whatever name you want for the file.
4.) Under the "Save As Type" dropdown menu in Notepad, change from a text document (.TXT) and select "All Files". Using

Please Login or Register to see this Hidden Content

, under the "Save As Type" choose unspecified file type.
5.) Before you click save, make sure your file name ends with .sh (ie: GovSched.sh)
6.) Place the file you've just created on your INTERNAL SD CARD - It won't work if run from the SD-EXT!!
7.) If you don't already have a copy of

Please Login or Register to see this Hidden Content

downloaded (or some other app to run scripts) go download it from the

Please Login or Register to see this Hidden Content

.
8.) Using Script Manager: Menu -> Browser -> locate and select the script you created & open it as a Script/Executable
8.) Enable Superuser permission for the script and set it to run at boot. Click save.
9.) Reboot
10.) Profit!

To verify your settings worked correctly, use SetCPU, Rom Toolbox or the like.

I used the pegasusq governor & the SIO scheduler - this has given ME the best battery life. Depending on your own usage patterns, your mileage may vary. If you want to use something different, just edit the parts of the script I highlighted in red so that it reflects your choice of governor/scheduler.

Post in this thread if it worked for you, and if you found this useful, please hit the LIKE button!

[Groundhound]

SetCPU

[FcHsChilD]

SetCPU

+1

Sent from my DROID RAZR using Tapatalk 2

[Memnoch73]

Just stating the obvious but are you checking the apply on boot box??

[PillClinton]

SetCPU

I'd prefer not to add another app if possible. Isn't there a file or a value in build.prop somewhere else that I can change?

Just stating the obvious but are you checking the apply on boot box??

Yes, definitely.

[disturbed58]

Is it possible to change the default I/O scheduler used by the system in a way that it sticks after rebooting? I've tried using Rom Toolbox but the values don't hold for me after a reboot. The same goes for the CPU governor. I'd like to set the values to noop for the scheduler & hotplug for the governor. Upon rebooting however, the values always return to deadline for the scheduler & interactive for the governor. Any tips?

I'm running the .211 OTA file & the .214 kernel I added with Matt's utility for my non-safe side. I'm running Eclipse 1.1 on my safe side. Also running the v6 Supercharger script, I'm wondering if it is because of something in that?

I have done it with a script through script manager, since you are running V6 I'm assuming you have script manager already.

Can you notice a difference with the v6 supercharger? It made a difference on my OG Droid, I wasn't sure if it would be noticeable with the Razr.

[PillClinton]

I have done it with a script through script manager, since you are running V6 I'm assuming you have script manager already.

Yes, I do have Script Manager, which script did you run for that? Do you have a copy you could share or link to?

I think the v6 Supercharger helps a bit with some of the launcher homescreen redraws. They happen less frequently since running that, and I use Apex Launcher Pro.

[JMSexton]

I was going to ask about V6 too. I had it on my DX and could most definitely tell a difference, but wasn't sure if it would work, or work correctly, with the Razr Maxx....

Thanks!

Sent telepathically from my Droid X... I mean Razr Maxx

[disturbed58]

Yes, I do have Script Manager, which script did you run for that? Do you have a copy you could share or link to?

I think the v6 Supercharger helps a bit with some of the launcher homescreen redraws. They happen less frequently since running that, and I use Apex Launcher Pro.

It's possible that the v6 may be setting the but I haven't looked into it.

I use a script to load the extra kernel modules and io scheduler, check out post 2 in the thread

Please Login or Register to see this Hidden Content

. If you have any existing scripts running at boot you could just add the lines to it. I'm just learning scripts myself so I am no expert.

Adding these lines to a script running at boot should work
echo "hotplug" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "noop" > /sys/block/mmcblk0/queue/scheduler

[PillClinton]

It's possible that the v6 may be setting the but I haven't looked into it.

I use a script to load the extra kernel modules and io scheduler, check out post 2 in the thread

Please Login or Register to see this Hidden Content

. If you have any existing scripts running at boot you could just add the lines to it. I'm just learning scripts myself so I am no expert.

Adding these lines to a script running at boot should work
echo "hotplug" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "noop" > /sys/block/mmcblk0/queue/scheduler

Thanks for the suggestions! I'm trying out the extra kernel modules you linked to now. I'll let you know how it goes!

[PillClinton]

I use a script to load the extra kernel modules and io scheduler, check out post 2 in the thread

Please Login or Register to see this Hidden Content

. If you have any existing scripts running at boot you could just add the lines to it. I'm just learning scripts myself so I am no expert.

I installed the script & verified all of the new kernel/scheduler modules are present on my system. I selected new governor/scheduler in Rom Toolbox, but the values still don't stick after a reboot. I tried making an Init.D script to run on boot and got errors. I'm not sure what I'm doing wrong? Any tips?

Edit: Not really sure what to do with the scripts. I used the flashable zips to install everything. There are additional scripts present in init.d now, am I supposed to edit 1 of those or create a new one?

[garywojdan81]

I installed the script & verified all of the new kernel/scheduler modules are present on my system. I selected new governor/scheduler in Rom Toolbox, but the values still don't stick after a reboot. I tried making an Init.D script to run on boot and got errors. I'm not sure what I'm doing wrong? Any tips?

Edit: Not really sure what to do with the scripts. I used the flashable zips to install everything. There are additional scripts present in init.d now, am I supposed to edit 1 of those or create a new one?

Have you set permissions on the init.d scripts to make them executable? The only way I can ever get them to stick is to give them complete permission.

Sent from my XT912 using Tapatalk 2

[PillClinton]

SUCCESS! With some assistance from

Please Login or Register to see this Hidden Content

here on DroidRzr &

Please Login or Register to see this Hidden Content

over at XDA, I have been able to accomplish what I originally set out to do and more. I edited the original thread title & the OP to clarify with extra directions. Hopefully some others will find this useful!

[PillClinton]

Edited the OP to reflect my current setup.

[disturbed58]

Here are some additional tweaks for the Pegasusq governor. I tried the "Relaxed" settings and haven't noticed at difference in performance, but did notice better battery life when not using the phone.

Please Login or Register to see this Hidden Content

[smeekteek]

Is there a guide somewhere that shows how to install the governors and schedulers?

[smeekteek]

Bueller...Bueller...

[BigJArm]

Is there a guide somewhere that shows how to install the governors and schedulers?

It's in the overclocking threads. It's pretty easy.

Sent from my DROID RAZR using Tapatalk 2

[disturbed58]

Is there a guide somewhere that shows how to install the governors and schedulers?

There is a link in the OP on how to install them.

[Maxxaholic]

IT WORKS! Thank you for this write up! Very helpful. I'm a n00b though what does that script do exactly? I can see all the governors in my SetCPU app. Do I have to change the script if I ever decide to use a different governor?