Application:Govnah - Revision history

JohnLBurger: Fixed Current Version release typo from 2010 to 2011.

2011-08-07T20:40:31Z

Fixed Current Version release typo from 2010 to 2011.

RodWhitby at 03:21, 7 August 2011

2011-08-07T03:21:25Z

Oakridge outdoors: Added resources section, govnah specific donation template to header and resources section

2011-05-03T02:15:01Z

Added resources section, govnah specific donation template to header and resources section

Xanadu73: Added "Troubleshooting/FAQs"

2011-04-29T14:53:01Z

Added "Troubleshooting/FAQs"

Xanadu73: Too much BOLD was harming readability...

2011-04-29T14:41:37Z

Too much BOLD was harming readability...

Xanadu73: Eye Pleasing

2011-04-29T12:28:54Z

Eye Pleasing

Xanadu73: /* Installation */ Clarification.

2011-04-29T12:17:40Z

Installation: Clarification.

Xanadu73: /* Purpose */ Clarification.

2011-04-29T12:11:20Z

Purpose: Clarification.

Xanadu73: Moved "Real World Examples" down to the "Governors In-Depth" section.

2011-04-29T11:10:48Z

Moved "Real World Examples" down to the "Governors In-Depth" section.

Xanadu73: Removed "Current Governors". This page is about Govnah, not features fo the various kernels.

2011-04-29T11:07:00Z

Removed "Current Governors". This page is about Govnah, not features fo the various kernels.

@@ Line 9: / Line 9: @@
 |name=Govnah
 |type=webOS
-|version=Version: 1.0.0 <br />(2010-08-07)
+|version=Version: 1.0.0 <br />(2011-08-07)
 |tag=Utilities
 |screenshot=GovnahHome4Life-0.6.1.png

@@ Line 9: / Line 9: @@
 |name=Govnah
 |type=webOS
-|version=Version: 0.7.7 <br />(2010-11-28)
+|version=Version: 1.0.0 <br />(2010-08-07)
 |tag=Utilities
 |screenshot=GovnahHome4Life-0.6.1.png
@@ Line 36: / Line 36: @@
 ==Installation==
-The following guide assumes a Palm Pre/Pre+/Pre2 is currently running Palm's stock kernel with no over-clocking patches.
+The following guide assumes a Palm Pre/Pre+/Pre2/Veer/TouchPad is currently running Palm's stock kernel with no over-clocking patches.
 #On Preware's home screen, type "Govnah" and hit enter.
 #Select "Govnah" and "Install".
 #If you have not yet installed a replacement "Kernel", on Preware's home screen, type "uber" and hit enter.
-#Select "[[Application:UberKernel|UberKernel (Palm Pre/Pre+)]]" and "Install".
+#Select "[[Application:UberKernel|UberKernel]]" and "Install".
 #Restart your phone as prompted.

@@ Line 5: / Line 5: @@
 :[[Image:France.png]] [[Application:Govnah-FR]]
 {{application
 |name=Govnah
@@ Line 11: / Line 12: @@
 |tag=Utilities
 |screenshot=GovnahHome4Life-0.6.1.png
-|description=}}
+|description=<div style='position: absolute; bottom: 0; right: 0; padding-right: 28px; padding-bottom: 16px'>{{GovnahDonation}}</div>
 <BR>
-=Summary=
+==Summary==
 [[image:Icon_WebOSInternals_Govnah.png|frameless|left]]
 Advanced webOS kernels provide mechanisms to control various operating parameters on the device such as clock speed.  These kernels expose one or more "governors" which can control those parameters. An example of such a kernel is the [[Application:UberKernel|UberKernel]].  This application is available through [[Preware]].
@@ Line 32: / Line 35: @@
 <BR>
-=Installation=
+==Installation==
 The following guide assumes a Palm Pre/Pre+/Pre2 is currently running Palm's stock kernel with no over-clocking patches.
@@ Line 47: / Line 50: @@
 <BR>
-=Brief Usage=
+==Brief Usage==
 ===Where To Start===
 {| Width="61%" VAlign="top"
@@ Line 98: / Line 101: @@
 <BR>
-=Troubleshooting/FAQs=
+==Troubleshooting/FAQs==
 ==="Unknown" Profile===
 *With webOS 2.1, HP as implemented a 10M compcache natively.  This causes a problem with Govnah's abilty to assign your compcache value before the webOS's upstart scripts does which will cacue Govnah to display "Unknown" as a profile name.  To remedy:
@@ Line 109: / Line 112: @@
 <BR>
-=Governors In-Depth=
+==Governors In-Depth==
 ===Real World Examples===
@@ Line 162: / Line 165: @@
-=Developer Notes=
+==Developer Notes==
 ===Relaunching for Cross-App Integration===
 There are 2 different launch params. One to get a list of profiles returned to your app, and one to apply a profile to the phone. This was implemented in v0.3.1.
@@ Line 230: / Line 233: @@
 Replace 'profileid' parameters value with the profile id you wish Govnah to apply. Note that 'profilename' is also an accepted parameter. This launch will not relaunch your app, it will simply apply if the profileid/name you requested actually exists. (And will just ignore your request if it doesn't.)

@@ Line 95: / Line 95: @@
 |valign="top"|As you can clearly see, you can save many different profiles for testing various settings to find what best suits you and your usage patterns to find that "sweet spot" between speed and battery savings.  Only you can find this.  [http://forums.precentral.net/webos-internals/244701-govnah.html People can help suggest] what works for them, but no two devices are '''exactly''' the same.
 |}
 <BR>

@@ Line 118: / Line 118: @@
 ===Standard Linux Governors===
 ====Generic Items (all)====
-* '''scaling_max_freq''': Set the maximum frequency your CPU(s) are allowed to scale to. Look at the output from scaling_available_frequencies
+* <u>scaling_max_freq</u>: Set the maximum frequency your CPU(s) are allowed to scale to. Look at the output from scaling_available_frequencies
-* '''scaling_min_freq''': Same as scaling_max_freq but setting a value that will not allow the CPU(s) to go below.
+* <u>scaling_min_freq</u>: Same as scaling_max_freq but setting a value that will not allow the CPU(s) to go below.
 ====ondemand====
-* '''sampling_rate''': This is measured in microseconds (one millionth of a second). This is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more. If you wanted to set the sampling rate to 1 second you would set it to 1000000 like in the following example.
+* <u>sampling_rate</u>: This is measured in microseconds (one millionth of a second). This is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more. If you wanted to set the sampling rate to 1 second you would set it to 1000000 like in the following example.
-* '''sampling_rate_(min|max)''': This is minimum and maximum sampling rates available that you may set 'sampling_rate' to. I believe in microseconds also.
+* <u>sampling_rate_(min|max)</u>: This is minimum and maximum sampling rates available that you may set 'sampling_rate' to. I believe in microseconds also.
-* '''sampling_down_factor''': this parameter controls the rate that the CPU makes a decision on when to decrease the frequency. When set to its default value of '5' it means that at 1/5 the sampling_rate the kernel makes a decision to lower the frequency. Five "lower rate" decisions have to be made in a row before the CPU frequency is actually lower. If set to '1' then the frequency decreases as quickly as it increases, if set to '2' it decreases at half the rate of the increase.
+* <u>sampling_down_factor</u>: this parameter controls the rate that the CPU makes a decision on when to decrease the frequency. When set to its default value of '5' it means that at 1/5 the sampling_rate the kernel makes a decision to lower the frequency. Five "lower rate" decisions have to be made in a row before the CPU frequency is actually lower. If set to '1' then the frequency decreases as quickly as it increases, if set to '2' it decreases at half the rate of the increase.
-* '''up_threshold''': This defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
+* <u>up_threshold</u>: This defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
-* '''ignore_nice_load''': This parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilization' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation.
+* <u>ignore_nice_load</u>: This parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilization' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation.
-* '''powersave_bias''': This modifies the behavior of the ondemand governor to save more power by reducing the target frequency by a specified percentage. By default, (powersave_bias  = 0), the ondemand governor selects the minimum processor frequency that can still complete a workload with minimal idle time. Doing so should result in the highest performance to power efficiency ratio. In some cases, you might prefer a greater emphasis on power efficiency than performance. In this case, set the powersave_bias parameter to a value between 1 and 1000 to reduce the target frequency by one-thousandth of that value. For example, set powersave_bias to 100 for a one-tenth reduction in target frequency. In this case, if the governor chooses a target frequency of 2 GHz (with powersave_bias  = 100), the governor instead will request 1.8GHz – a one-tenth reduction. If 1.8 GHz is an exact match with an available hardware frequency (listed in the scaling_available_freq parameter), the processor is set to this frequency. If 1.8 GHz is not available, the processor fluctuates between the closest available upper and lower frequencies for an average frequency of 1.8 GHz. (from IBM web page). The original author of the ondemand powersave_bias code explains it as "For example, If ondemand requests 2.0GHz based on utilization, and powersave_bias=100, this code will knock 10% off the target and seek a target of 1.8GHz instead of 2.0GHz until the next sampling. If 1.8 is an exact match with an hardware frequency we use it, otherwise we average our time between the frequency next higher than 1.8 and next lower than 1.8" (from http://osdir.com/ml/kernel.cpufreq/2006-07/msg00114.html ) - the key word appears to be "average". The author also warns "In practice, users will not be able to detect a difference between 0.1% increments, but 1.0% increments turned out to be too large. Also, the max value of 1000 (100%) would simply peg the system in its deepest power saving P-state, unless the processor really has a hardware P-state at 0Hz".
+* <u>powersave_bias</u>: This modifies the behavior of the ondemand governor to save more power by reducing the target frequency by a specified percentage. By default, (powersave_bias  = 0), the ondemand governor selects the minimum processor frequency that can still complete a workload with minimal idle time. Doing so should result in the highest performance to power efficiency ratio. In some cases, you might prefer a greater emphasis on power efficiency than performance. In this case, set the powersave_bias parameter to a value between 1 and 1000 to reduce the target frequency by one-thousandth of that value. For example, set powersave_bias to 100 for a one-tenth reduction in target frequency. In this case, if the governor chooses a target frequency of 2 GHz (with powersave_bias  = 100), the governor instead will request 1.8GHz – a one-tenth reduction. If 1.8 GHz is an exact match with an available hardware frequency (listed in the scaling_available_freq parameter), the processor is set to this frequency. If 1.8 GHz is not available, the processor fluctuates between the closest available upper and lower frequencies for an average frequency of 1.8 GHz. (from IBM web page). The original author of the ondemand powersave_bias code explains it as "For example, If ondemand requests 2.0GHz based on utilization, and powersave_bias=100, this code will knock 10% off the target and seek a target of 1.8GHz instead of 2.0GHz until the next sampling. If 1.8 is an exact match with an hardware frequency we use it, otherwise we average our time between the frequency next higher than 1.8 and next lower than 1.8" (from http://osdir.com/ml/kernel.cpufreq/2006-07/msg00114.html ) - the key word appears to be "average". The author also warns "In practice, users will not be able to detect a difference between 0.1% increments, but 1.0% increments turned out to be too large. Also, the max value of 1000 (100%) would simply peg the system in its deepest power saving P-state, unless the processor really has a hardware P-state at 0Hz".
 ====conservative====
-* '''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.
+* <u>freq_step</u>: 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''': This is 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.
+* <u>down_threshold</u>: This is 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.
-* '''sampling_rate''': same as ondemand.
+* <u>sampling_rate</u>: same as ondemand.
-* '''sampling_rate_(min|max)''': same as ondemand.
+* <u>sampling_rate_(min|max)</u>: same as ondemand.
-* '''up_threshold''': same as ondemand.
+* <u>up_threshold</u>: same as ondemand.
-* '''ignore_nice_load'''v: same as ondemand.
+* <u>ignore_nice_load</u>: same as ondemand.
 ====userspace====
-* '''scaling_setspeed''': one of the values from scaling_available_frequencies
+* <u>scaling_setspeed</u>: one of the values from scaling_available_frequencies
-* '''NB''': when userspace is selected LunaSysMgr will change the frequency as it feels.
+* <u>NB</u>: when userspace is selected LunaSysMgr will change the frequency as it feels.
 ====powersave====

@@ Line 1: / Line 1: @@
 [[Category:Application]]
-This page is currently available in two languages:
+This page is currently available in these languages:
 :[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
 :[[Image:Germany.png]] [[Application:Govnah-DE]]
@@ Line 8: / Line 8: @@
 |name=Govnah
 |type=webOS
-|version=Version: 0.7.5 <br />(2010-10-22)
+|version=Version: 0.7.7 <br />(2010-11-28)
 |tag=Utilities
 |screenshot=GovnahHome4Life-0.6.1.png
@@ Line 41: / Line 41: @@
 #Restart your phone as prompted.
   See the [http://www.webos-internals.org/wiki/Application:UberKernel the UberKernel page] for
- further information on its abilities and use.
+ Note:
 <BR>
@@ Line 116: / Line 117: @@
 ===Standard Linux Governors===
-* Generic items (needed for all)
+====Generic Items (all)====
-** scaling_max_freq - Set the maximum frequency your CPU(s) are allowed to scale to. Look at the output from scaling_available_frequencies
+* '''scaling_max_freq''': Set the maximum frequency your CPU(s) are allowed to scale to. Look at the output from scaling_available_frequencies
-** scaling_min_freq - Same as scaling_max_freq but setting a value that will not allow the CPU(s) to go below.
+* '''scaling_min_freq''': Same as scaling_max_freq but setting a value that will not allow the CPU(s) to go below.
-* '''ondemand'''
+====ondemand====
-** sampling_rate - This is measured in microseconds (one millionth of a second). This is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more. If you wanted to set the sampling rate to 1 second you would set it to 1000000 like in the following example.
+* '''sampling_rate''': This is measured in microseconds (one millionth of a second). This is how often you want the kernel to look at the CPU usage and to make decisions on what to do about the frequency. Typically this is set to values of around '10000' or more. If you wanted to set the sampling rate to 1 second you would set it to 1000000 like in the following example.
-** sampling_rate_(min|max) - This is minimum and maximum sampling rates available that you may set 'sampling_rate' to. I believe in microseconds also.
+* '''sampling_rate_(min|max)''': This is minimum and maximum sampling rates available that you may set 'sampling_rate' to. I believe in microseconds also.
-** sampling_down_factor: this parameter controls the rate that the CPU makes a decision on when to decrease the frequency. When set to its default value of '5' it means that at 1/5 the sampling_rate the kernel makes a decision to lower the frequency. Five "lower rate" decisions have to be made in a row before the CPU frequency is actually lower. If set to '1' then the frequency decreases as quickly as it increases, if set to '2' it decreases at half the rate of the increase.
+* '''sampling_down_factor''': this parameter controls the rate that the CPU makes a decision on when to decrease the frequency. When set to its default value of '5' it means that at 1/5 the sampling_rate the kernel makes a decision to lower the frequency. Five "lower rate" decisions have to be made in a row before the CPU frequency is actually lower. If set to '1' then the frequency decreases as quickly as it increases, if set to '2' it decreases at half the rate of the increase.
-** up_threshold - This defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
+* '''up_threshold''': This defines what the average CPU usage between the samplings of 'sampling_rate' needs to be for the kernel to make a decision on whether or not it should increase the frequency. For example when it is set to its default value of '80' it means that between the checking intervals the CPU needs to be on average more than 80% in use to then decide that the CPU frequency needs to be increased.
-** ignore_nice_load - This parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilization' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation.
+* '''ignore_nice_load''': This parameter takes a value of '0' or '1'. When set to '0' (its default), all processes are counted towards the 'cpu utilization' value. When set to '1', the processes that are run with a 'nice' value will not count (and thus be ignored) in the overall usage calculation.
-** powersave_bias - This modifies the behavior of the ondemand governor to save more power by reducing the target frequency by a specified percentage. By default, (powersave_bias  = 0), the ondemand governor selects the minimum processor frequency that can still complete a workload with minimal idle time. Doing so should result in the highest performance to power efficiency ratio. In some cases, you might prefer a greater emphasis on power efficiency than performance. In this case, set the powersave_bias parameter to a value between 1 and 1000 to reduce the target frequency by one-thousandth of that value. For example, set powersave_bias to 100 for a one-tenth reduction in target frequency. In this case, if the governor chooses a target frequency of 2 GHz (with powersave_bias  = 100), the governor instead will request 1.8GHz – a one-tenth reduction. If 1.8 GHz is an exact match with an available hardware frequency (listed in the scaling_available_freq parameter), the processor is set to this frequency. If 1.8 GHz is not available, the processor fluctuates between the closest available upper and lower frequencies for an average frequency of 1.8 GHz. (from IBM web page). The original author of the ondemand powersave_bias code explains it as "For example, If ondemand requests 2.0GHz based on utilization, and powersave_bias=100, this code will knock 10% off the target and seek a target of 1.8GHz instead of 2.0GHz until the next sampling. If 1.8 is an exact match with an hardware frequency we use it, otherwise we average our time between the frequency next higher than 1.8 and next lower than 1.8" (from http://osdir.com/ml/kernel.cpufreq/2006-07/msg00114.html ) - the key word appears to be "average". The author also warns "In practice, users will not be able to detect a difference between 0.1% increments, but 1.0% increments turned out to be too large. Also, the max value of 1000 (100%) would simply peg the system in its deepest power saving P-state, unless the processor really has a hardware P-state at 0Hz".
+* '''powersave_bias''': This modifies the behavior of the ondemand governor to save more power by reducing the target frequency by a specified percentage. By default, (powersave_bias  = 0), the ondemand governor selects the minimum processor frequency that can still complete a workload with minimal idle time. Doing so should result in the highest performance to power efficiency ratio. In some cases, you might prefer a greater emphasis on power efficiency than performance. In this case, set the powersave_bias parameter to a value between 1 and 1000 to reduce the target frequency by one-thousandth of that value. For example, set powersave_bias to 100 for a one-tenth reduction in target frequency. In this case, if the governor chooses a target frequency of 2 GHz (with powersave_bias  = 100), the governor instead will request 1.8GHz – a one-tenth reduction. If 1.8 GHz is an exact match with an available hardware frequency (listed in the scaling_available_freq parameter), the processor is set to this frequency. If 1.8 GHz is not available, the processor fluctuates between the closest available upper and lower frequencies for an average frequency of 1.8 GHz. (from IBM web page). The original author of the ondemand powersave_bias code explains it as "For example, If ondemand requests 2.0GHz based on utilization, and powersave_bias=100, this code will knock 10% off the target and seek a target of 1.8GHz instead of 2.0GHz until the next sampling. If 1.8 is an exact match with an hardware frequency we use it, otherwise we average our time between the frequency next higher than 1.8 and next lower than 1.8" (from http://osdir.com/ml/kernel.cpufreq/2006-07/msg00114.html ) - the key word appears to be "average". The author also warns "In practice, users will not be able to detect a difference between 0.1% increments, but 1.0% increments turned out to be too large. Also, the max value of 1000 (100%) would simply peg the system in its deepest power saving P-state, unless the processor really has a hardware P-state at 0Hz".
-* '''conservative'''
+====conservative====
-** 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.
+* '''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 - This is 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.
+* '''down_threshold''': This is 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.
-** sampling_rate - same as ondemand.
+* '''sampling_rate''': same as ondemand.
-** sampling_rate_(min|max) - same as ondemand.
+* '''sampling_rate_(min|max)''': same as ondemand.
-** up_threshold - same as ondemand.
+* '''up_threshold''': same as ondemand.
-** ignore_nice_load - same as ondemand.
+* '''ignore_nice_load'''v: same as ondemand.
-* '''userspace'''
+====userspace====
-** scaling_setspeed - one of the values from scaling_available_frequencies
+* '''scaling_setspeed''': one of the values from scaling_available_frequencies
-** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.
+* '''NB''': when userspace is selected LunaSysMgr will change the frequency as it feels.
-* '''powersave'''
+====powersave====
-** Nothing special
+* Nothing special
-* '''performance'''
+====performance====
-** Nothing special
+* Nothing special
-* '''screenstate'''
+====screenstate====
-** Nothing special
+* Nothing special
@@ Line 155: / Line 156: @@
 ===Profile List===
-The code below is how you would launch govnah and tell it to return a list of profiles to your app:
+The code below is how you would launch Govnah and tell it to return a list of profiles to your app:
 <pre><nowiki>
 this.controller.serviceRequest
@@ Line 197: / Line 198: @@
 ===Profile Apply===
-The code below is how you use the list of profiles you received in the prior relaunch to have govnah apply a profile.
+The code below is how you use the list of profiles you received in the prior relaunch to have Govnah apply a profile.
 <pre><nowiki>
 this.controller.serviceRequest
@@ Line 216: / Line 217: @@
 );
 </nowiki></pre>
-Replace 'profileid' parameters value with the profile id you wish govnah to apply. Note that 'profilename' is also an accepted parameter. This launch will not relaunch your app, it will simply apply if the profileid/name you requested actually exists. (And will just ignore your request if it doesn't.)
+Replace 'profileid' parameters value with the profile id you wish Govnah to apply. Note that 'profilename' is also an accepted parameter. This launch will not relaunch your app, it will simply apply if the profileid/name you requested actually exists. (And will just ignore your request if it doesn't.)

@@ Line 22: / Line 22: @@
 Govnah's UI provides access to:
 :* A real-time graph of CPU speed, CPU temperature, memory usage and system load
-:* A mechanism for setting the parameters of the "governors" exposed by the kernel.
+:* A mechanism for setting the parameters of the governors exposed by the various Linux kernels.
-:* Ability to reduce/raise the amount of power parts of the device uses.
+:* Ability to reduce/raise the amount of power parts of the device uses to reduce battery consumption.
-:* Temperature range which lowers CPU frequency to cool down the device.
+:* Temperature range which lowers/resets CPU frequency to cool down the device under heavy load.
 :* Ability to slow down the CPU when battery is low.
 :* The amount of swap that can be compressed (compcache).
-:* The IO schedulers.
+:* The enabled Linux IO schedulers.
-:* The TCP Congestion algorithms.
+:* The enabled Linux TCP Congestion algorithms.
 <BR>