WebOS Internals - User contributions [en]

BadBooty

2011-08-26T16:32:15Z

Xanadu73:

<div style='position: relative;'>
{{application
|name=Bad Booty
|type=webOS
|version=Version: 1.0.0 (06-06-2011)
|tag=Fun
|screenshot=Badbooty_2011-06-06_154303.png
|description=No mess!
}}
</div>
== Summary ==
Hit the buttons and point your finger at someone else!

Application:SimpleBigBook

2011-08-19T03:00:01Z

Xanadu73:

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.19 - June 13, 2011
|tag=Self-Help
|screenshot=Simplebigbook_2011-03-06_070047.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
Coming soon:
*Bookmarks!

Current:
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently, git is inline with release, feature wise.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundred times it is hitting that part of the code EVERY page load.
*There's a fair amount of Mojo specific things. Two things here:
**With Mojo dieing, any Mojo-isms need to have Enyo equivalents.
**Bag Palm specific stuff (Mojo/Enyo) and move to straight HTML5/JS for use under whatever Palm does and portability to other mobile OS's.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and manually installing it on your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Testing Feeds

2011-08-03T03:07:07Z

Xanadu73: /* Using Preware */ Should be much better spacing (and I forgot to get rid of borders...)

=Rules that you must agree to before using these feeds=

Before you use our testing feeds, please read and agree to the following rules:
[[image:Tux_with_Warning.png|frameless|right]]
# Anyone participating in WebOS Internals alpha testing of any kind must be prepared to fully erase and webOS Doctor their device at a moment's notice without warning and without any regrets or complaints.
# They must be prepared to and able to log into the command line on the device and type Linux commands when instructed to do so. Knowing Linux commands ahead of time is preferred, but not required if you are willing to learn them when necessary or can follow instructions without making mistakes.
# They must be prepared to go to great and extraordinary lengths to try and reliably reproduce any problems they encounter.
# They must give full and detailed bug reports, leaving out no piece of information which could possibly be remotely connected to the problem.
# They must read any and all documentation and forums threads (in their entirety) before asking a question.
# They must fastidiously follow the forum threads where the alpha testing is being discussed by the authors, and follow precisely any instructions given there.

If you're not prepared to do *all* the above, and do it all in good spirit, then please wait for the public release of the item.

If you are prepared to do *all* the above, then by all means please participate in the alpha testing.

Note that everything above is a function of attitude, not of skill.

=Configuring the WebOS Internals Testing Feeds=

===Using Preware===
[[image:Tux_with_Pre.png|frameless|right]]
With Preware versions 0.9.30 and above, incombination with webOS 1.3.5 and above, users are now able to add custom feeds through Preware without the use of a computer. The following instructions will explain how to add the Webos-Internals Testing feeds.

Note that you will need to enable *TWO* feeds below. You need the *ALL* feed and you need the device-specific feed as well (armv7, armv6 or i686).

{| border="0" width="470"
|colspan="2" align="left"|'''Target Device:''' ALL
|-
|'''Name:'''||webos-testing-all
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/all/ http://ipkg.preware.org/feeds/webos-internals/testing/all]
|-
|} 
{| border="0" width="470"
|-
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pre/Pre+/Pre2/Veer/TouchPad/Pre3</nowiki>
|-
|'''Name:'''||webos-testing-armv7
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv7/ http://ipkg.preware.org/feeds/webos-internals/testing/armv7]
|-
|} 
{| border="0" width="470"
|-
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pixi/Pixi+</nowiki>
|-
|'''Name:'''||webos-testing-armv6
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv6/ http://ipkg.preware.org/feeds/webos-internals/testing/armv6]
|-
|} 
{| border="0" width="470"
|-
|colspan="2" align="left"|'''Target Device:''' Palm SDK Emulator
|-
|'''Name:'''||webos-testing-i686
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/i686/ http://ipkg.preware.org/feeds/webos-internals/testing/i686]
|}
 
#Open Preware and wait for it to finish loading.
#Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.
#Scroll to the bottom until you see the New Feed box.
#Type or paste a name and corresponding URL from above in the appropriate text boxes. Make sure the URL does *not* have a slash at the end.
#Make sure the IS COMPRESSED option is set to YES.
#Tap Add Feed and then tap Yes when the alert pops up.
#Repeat these steps for each feed you wish to enable.
#Gesture swipe back. Preware will alert you that you have added feeds and ask if you want to update them now. Choose YES.
 
Congratulations, you have just added a custom feed! For adding other feeds, be sure to replace the name and URL in these instructions with the proper name and URL.
 
'''TIP:'''

shift+tap (and drag) on text to select
gesture+c to copy
gesture+v to paste
Make sure to delete 'http://' before pasting the URL if the URL already contains 'http://'

 

===Using a Computer===
[[image:Tux_Chat.png|frameless|right]]
1. Gain access to the shell, either through novaterm/ssh or via the terminal application available through the regular WebOS Internals Feed 
2. Execute the following commands:
<pre>
cd /media/cryptofs/apps/etc/ipkg
echo "src/gz webosinternals-testing http://ipkg.preware.org/feeds/webos-internals/testing/all" > webos-internals-testing.conf
echo "src/gz webosinternals-testing-armv7 http://ipkg.preware.org/feeds/webos-internals/testing/armv7" >> webos-internals-testing.conf
</pre>
3. Once Preware is launched, select "Update Feeds" from the Application Menu.

Replace 'armv7' with 'armv6' or 'i686' in the instructions above if you are using a Pixi or the Emulator respectively.

 
=Kernel Testing Feeds=
[http://www.webos-internals.org/index.php?title=Testing_Feeds&action=submit#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]
Also see http://forums.precentral.net/2532084-post3.html for further warnings up to and including your device wiping itself, (literally) melting, and/or eating your kitten.

If you do not want a puddle of molten plastic and silicon where your Pre/Pixi once was, DO NOT CONTINUE.

You have been warned.

[http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ And Palm is not going to help you.]

#Type 'webos-kernels-testing' (without the quotes, and using lower case letters and hyphens only) in the NAME field of the NEW FEED section of the Manage Feeds screen accessible from the Preware application menu. If you make any error in this feed name, the URL below will not be replaced by the real URL when the device is rebooted, and you will not get access to the feeds. MAKE SURE YOU GET THE FEED NAME CORRECT!
#Put http://preware.is.awesome.com/ in the URL field. Note that this is not a real URL - it is a placeholder only. Again, you need to get the feed name correct for the real URL to be replaced correctly when the device is rebooted.
#Leave the IS COMPRESSED toggled on.
#Hit "Add Feed" and read the disclaimer carefully. Yes, the things you might find in kernel testing feeds are likely to completely wipe your device without warning. Hit the Ok button only if you are prepared to lose all your data and destroy your device without any regrets or complaints.
#Immediately reboot the device by simultaneously pressing the Opt, Sym and R keys. If you don't reboot the device, or if you only do a Luna Restart instead of a Device Reboot, then placeholder URL will not be replaced by the real URL and you will not get access to the feeds. MAKE SURE YOU REBOOT THE DEVICE!
#Wait for the device to boot. If you got the feed name correct, the placeholder URL will be replaced by the real feed URL automatically.
#Open Preware, and hit Update Feeds. Make sure you have a working network connection for this.

Preware will repair the URL field automatically when the device boots. Did I mention that you have to get the feed name precisely correct for this to happen? MAKE SURE YOU GET THE FEED NAME CORRECT AND REBOOT THE DEVICE!

You must be running Preware 1.1.4 or later for this to work (yes, this has been possible for quite some time).

Testing Feeds

2011-08-03T03:04:36Z

Xanadu73: /* Using Preware */ The empty-cell-as-table-spacer looked odd in mobile view...

=Rules that you must agree to before using these feeds=

Before you use our testing feeds, please read and agree to the following rules:
[[image:Tux_with_Warning.png|frameless|right]]
# Anyone participating in WebOS Internals alpha testing of any kind must be prepared to fully erase and webOS Doctor their device at a moment's notice without warning and without any regrets or complaints.
# They must be prepared to and able to log into the command line on the device and type Linux commands when instructed to do so. Knowing Linux commands ahead of time is preferred, but not required if you are willing to learn them when necessary or can follow instructions without making mistakes.
# They must be prepared to go to great and extraordinary lengths to try and reliably reproduce any problems they encounter.
# They must give full and detailed bug reports, leaving out no piece of information which could possibly be remotely connected to the problem.
# They must read any and all documentation and forums threads (in their entirety) before asking a question.
# They must fastidiously follow the forum threads where the alpha testing is being discussed by the authors, and follow precisely any instructions given there.

If you're not prepared to do *all* the above, and do it all in good spirit, then please wait for the public release of the item.

If you are prepared to do *all* the above, then by all means please participate in the alpha testing.

Note that everything above is a function of attitude, not of skill.

=Configuring the WebOS Internals Testing Feeds=

===Using Preware===
[[image:Tux_with_Pre.png|frameless|right]]
With Preware versions 0.9.30 and above, incombination with webOS 1.3.5 and above, users are now able to add custom feeds through Preware without the use of a computer. The following instructions will explain how to add the Webos-Internals Testing feeds.

Note that you will need to enable *TWO* feeds below. You need the *ALL* feed and you need the device-specific feed as well (armv7, armv6 or i686).

{| border="1" width="470"
|colspan="2" align="left"|'''Target Device:''' ALL
|-
|'''Name:'''||webos-testing-all
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/all/ http://ipkg.preware.org/feeds/webos-internals/testing/all]
|-
|}

{| border="1" width="470"
|-
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pre/Pre+/Pre2/Veer/TouchPad/Pre3</nowiki>
|-
|'''Name:'''||webos-testing-armv7
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv7/ http://ipkg.preware.org/feeds/webos-internals/testing/armv7]
|-
|}

{| border="1" width="470"
|-
|colspan="2" align="left"|'''Target Device:''' <nowiki>Pixi/Pixi+</nowiki>
|-
|'''Name:'''||webos-testing-armv6
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/armv6/ http://ipkg.preware.org/feeds/webos-internals/testing/armv6]
|-
|}

{| border="1" width="470"
|-
|colspan="2" align="left"|'''Target Device:''' Palm SDK Emulator
|-
|'''Name:'''||webos-testing-i686
|-
|'''URL:'''||[http://ipkg.preware.org/feeds/webos-internals/testing/i686/ http://ipkg.preware.org/feeds/webos-internals/testing/i686]
|}
 
#Open Preware and wait for it to finish loading.
#Open the App Menu (tap "Preware" in the top left corner of the screen) and tap Manage feeds.
#Scroll to the bottom until you see the New Feed box.
#Type or paste a name and corresponding URL from above in the appropriate text boxes. Make sure the URL does *not* have a slash at the end.
#Make sure the IS COMPRESSED option is set to YES.
#Tap Add Feed and then tap Yes when the alert pops up.
#Repeat these steps for each feed you wish to enable.
#Gesture swipe back. Preware will alert you that you have added feeds and ask if you want to update them now. Choose YES.
 
Congratulations, you have just added a custom feed! For adding other feeds, be sure to replace the name and URL in these instructions with the proper name and URL.
 
'''TIP:'''

shift+tap (and drag) on text to select
gesture+c to copy
gesture+v to paste
Make sure to delete 'http://' before pasting the URL if the URL already contains 'http://'

 

===Using a Computer===
[[image:Tux_Chat.png|frameless|right]]
1. Gain access to the shell, either through novaterm/ssh or via the terminal application available through the regular WebOS Internals Feed 
2. Execute the following commands:
<pre>
cd /media/cryptofs/apps/etc/ipkg
echo "src/gz webosinternals-testing http://ipkg.preware.org/feeds/webos-internals/testing/all" > webos-internals-testing.conf
echo "src/gz webosinternals-testing-armv7 http://ipkg.preware.org/feeds/webos-internals/testing/armv7" >> webos-internals-testing.conf
</pre>
3. Once Preware is launched, select "Update Feeds" from the Application Menu.

Replace 'armv7' with 'armv6' or 'i686' in the instructions above if you are using a Pixi or the Emulator respectively.

 
=Kernel Testing Feeds=
[http://www.webos-internals.org/index.php?title=Testing_Feeds&action=submit#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]
Also see http://forums.precentral.net/2532084-post3.html for further warnings up to and including your device wiping itself, (literally) melting, and/or eating your kitten.

If you do not want a puddle of molten plastic and silicon where your Pre/Pixi once was, DO NOT CONTINUE.

You have been warned.

[http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ And Palm is not going to help you.]

#Type 'webos-kernels-testing' (without the quotes, and using lower case letters and hyphens only) in the NAME field of the NEW FEED section of the Manage Feeds screen accessible from the Preware application menu. If you make any error in this feed name, the URL below will not be replaced by the real URL when the device is rebooted, and you will not get access to the feeds. MAKE SURE YOU GET THE FEED NAME CORRECT!
#Put http://preware.is.awesome.com/ in the URL field. Note that this is not a real URL - it is a placeholder only. Again, you need to get the feed name correct for the real URL to be replaced correctly when the device is rebooted.
#Leave the IS COMPRESSED toggled on.
#Hit "Add Feed" and read the disclaimer carefully. Yes, the things you might find in kernel testing feeds are likely to completely wipe your device without warning. Hit the Ok button only if you are prepared to lose all your data and destroy your device without any regrets or complaints.
#Immediately reboot the device by simultaneously pressing the Opt, Sym and R keys. If you don't reboot the device, or if you only do a Luna Restart instead of a Device Reboot, then placeholder URL will not be replaced by the real URL and you will not get access to the feeds. MAKE SURE YOU REBOOT THE DEVICE!
#Wait for the device to boot. If you got the feed name correct, the placeholder URL will be replaced by the real feed URL automatically.
#Open Preware, and hit Update Feeds. Make sure you have a working network connection for this.

Preware will repair the URL field automatically when the device boots. Did I mention that you have to get the feed name precisely correct for this to happen? MAKE SURE YOU GET THE FEED NAME CORRECT AND REBOOT THE DEVICE!

You must be running Preware 1.1.4 or later for this to work (yes, this has been possible for quite some time).

WebOS 2 Upgrade Pre Minus

2011-07-19T01:51:16Z

Xanadu73: /* Minimal System Logging */ oops...

Here are instructions for speeding up your Pre Minus once you have installed WebOS 2.1. As Jon Rubenstein commented at the February 9th event, the Pre Minus simply does not have enough horsepower at stock to run WebOS 2.1 efficiently. Follow this guideline to overclock, patch, hack and modify WebOS so that it will run as fast and as smoothly as possible with WebOS 2.1.

I must note that while all of these steps do help significantly, you still will find the performance not perfect. The Pre Minus hardware is over 2 years old now. You simply can't get something from nothing. These steps help greatly, but do not expect a miracle.

=Warnings and other preambles=

While it is nearly impossible to brick your Pre, you are still modifying the device heavily with these steps. BACK YOUR DEVICE UP FIRST!!!! Back up apps with Save/Restore from Preware, and then copy the entire USB partition to your harddrive on a computer. You will be sorry if you don't.

Also: While patching does not void your warranty, overclocking does. One of these steps involves using a testing kernel feed, and the warnings for that are available on the page we will be referencing for it. Please read that warning. Ill summerise: It voids your warranty and there is a possibility that your phone will turn into a pile of liquid goo. Ok not really but it could break it. So far though I only know of one instance where overclocking destroyed a Pre.

Also these steps have been tried with WebOS 2.1 ONLY. If you attempt any of them with WebOS 1.4.5, do so at your own risk.

=pre.... Pre Setup=

Before starting, please ensure of something:

1. Put your Pre into developer mode. In Just Type write: "upupdowndownleftrightleftrightbastart". Open the Developer Mode app. Switch to 'ON'. Even if you do not use a computer once to perform these operations, you might brick WebOS and its essential you have developer mode on in order to change any files you messed up from a computer terminal.

2. Install Preware. If you have not, install the app Preware to your device. Instructions found here: [http://theunlockr.com/2010/04/29/how-to-install-preware-on-the-palm-pre-install-root-required-apps-themes-patches-and-tweaks/ | Install Preware]

=The Steps to Speed Up the Pre Minus.=

==Step 1: Overclocking==

One of the most important steps is to overclock the processor and RAM using Unixpsycho's F105 Kernel. This kernel allows you to overclock the CPU to 1ghz as well as overclock the RAM, which is essential as RAM is the biggest issue with WebOS 2.1. At rest on a Pre2, I have seen that WebOS 2.1 uses about 300mb of ram. The Palm Pre Minus only has 256mb, so we are already using up more than 100% of the RAM of the phone before we even open an app. We must speed up and manage RAM as best we can in order to have any hope of running WebOS 2.1 smoothly.

The best way to install this kernel is through Preware.

1. First follow the steps to add the testing kernel feeds in Preware here: [http://www.webos-internals.org/wiki/Testing_Feeds#Kernel_Testing_Feeds | Kernel Testing feeds]

2. Once you have installed the feeds, go to Preware and go to '''Available Packages > Kernel > All ''' and install the "F105 Thunderchief" Kernel.

3. Install Govnah from Preware as well. This is used to modify and monitor the CPU speeds.

4. Restart

Your phone should now be overclocked to 1Ghz and your RAM overclocked as well.

==Step 2: Installing Patches to speed up the phone==

Patches are a great and easy way to speed up the Pre Minus. They easily modify the code in WebOS so that your phone runs faster or is more responsive due to several different reasons.

Here are the list of patches to install from Preware in order to speed up the Pre Minus: (They are found under ''' Available Packages > Patches ''')

'''Faster Card Animations HYPER Version

'''Smooth Scrolling

'''Increase Touch Sensitivity and Smoothness

'''Remove Dropped Packet Logging

'''Unset CFQ IO Scheduler

'''Unthrottle Download Manager'''

DO NOT install "Muffle System Logging" patch as this WILL break WebOS from indexing your photos, and any photos you take or download will disappear from the Photos app.

There you have it. Restart your Pre again and it should run faster as well.

==Minimal System Logging==

WebOS by default logs EVERYTHING you do, which can actually bog down the OS quite a bit. To disable this, follow these steps:

1. Open the phone dialer.

2. For Sprint/Verizon/CDMA: Dial ##5647# (##LOGS#) and press SEND. For AT&T/O2/GSM: Dial #*5647# and press SEND.

3. Tap "Change logging levels."

4. Tap "Set logging to minimal."

5. Tap OK to confirm.

6. Tap OK again after it finishes.

7. Reboot your Pre.

8. Enjoy the performance boost!

The overclocked kernels do this by default but its better to be safe than sorry and make sure they are disabled.

DO NOT USE THE MUFFLE SYSTEM LOGGING PATCH, IT WILL BREAK YOUR PHOTOS.

==Install Preset Reset==

Go to Preware and install the Homebrew app Preset Reset. Open it and set it to reset your phone every day at a specific time (most likely when you are sleeping) . This way your phone will be nice and fresh in the morning, and the cache and memory leaks from the day before will be wiped clean from the device.

==Install JSTop==

Install "JSTop" from Preware. Open the app and tap the top left where the name "JSTop appears" to access the preferences for the app. Click "Enable Auto GC" and "Disable Notifications".

This will have JSTop automatically clear out any garbage memory or memory leaks at set intervals, which are pure murder for the RAM starved Pre Minus.

==Cleanup==

Periodically go into apps and clear out any history. This history severally slows the phone down after it builds up.

Phone App - Clear call history

Messaging App - Delete all messages

Email App - Delete any old emails you dont need

Google Maps - Clear search history

Browser - Delete History and Cookies and Cache.

Also, turn off any notification service that you don't need, such as Facebook Updates, etc. All of these services require the app to run in the background to "listen" for notifications and take up RAM.

Remove any Just Type services that you don't use, these also take up indexing cache.

==More advanced hacks==

These next hacks are more advanced and should only be done by those who have some computer experience. They involve using the Terminal as well as installing special patch files to speed up the Pre. These are the most dramatic hacks however that have shown the best performance so far.

====Modify System Control Configuration====

Linux allows you to add a file that will modify how the kernel handles using the RAM as well as virtual memory in the Pre Minus. With such little RAM to spare, we are going to modify how Linux stores applications and cache on the Pre to remedy the hanging, stalls and other issues experienced with using WebOS 2.1 on the Pre Minus.

Simply install the .ipk here to install it.

Reboot your Pre.

Updates will be provided occasionally so come back here to check out newer versions.

===Modify Luna.conf===

There are some modifications that can be done to the luna.conf file on WebOS to speed up the Pre Minus.

For now, the browser app is set to only close when the system runs out of ram. This means that even if you swipe away the Browser card, its still running in the background. The luna.conf has been modified in this patch to close the Browser immediately.

Some other minor tweaks have been added as well.

This will not conflict with the "Increase Touch Sensitivity and Smoothness" patch.

Install it here:

===Resize Swap File and Disable Compcache===

WebOS 2 Upgrade Pre Minus

2011-07-19T01:42:21Z

Xanadu73: /* Minimal System Logging */ Fix #2 instructions for CDMA

Here are instructions for speeding up your Pre Minus once you have installed WebOS 2.1. As Jon Rubenstein commented at the February 9th event, the Pre Minus simply does not have enough horsepower at stock to run WebOS 2.1 efficiently. Follow this guideline to overclock, patch, hack and modify WebOS so that it will run as fast and as smoothly as possible with WebOS 2.1.

I must note that while all of these steps do help significantly, you still will find the performance not perfect. The Pre Minus hardware is over 2 years old now. You simply can't get something from nothing. These steps help greatly, but do not expect a miracle.

=Warnings and other preambles=

While it is nearly impossible to brick your Pre, you are still modifying the device heavily with these steps. BACK YOUR DEVICE UP FIRST!!!! Back up apps with Save/Restore from Preware, and then copy the entire USB partition to your harddrive on a computer. You will be sorry if you don't.

Also: While patching does not void your warranty, overclocking does. One of these steps involves using a testing kernel feed, and the warnings for that are available on the page we will be referencing for it. Please read that warning. Ill summerise: It voids your warranty and there is a possibility that your phone will turn into a pile of liquid goo. Ok not really but it could break it. So far though I only know of one instance where overclocking destroyed a Pre.

Also these steps have been tried with WebOS 2.1 ONLY. If you attempt any of them with WebOS 1.4.5, do so at your own risk.

=pre.... Pre Setup=

Before starting, please ensure of something:

1. Put your Pre into developer mode. In Just Type write: "upupdowndownleftrightleftrightbastart". Open the Developer Mode app. Switch to 'ON'. Even if you do not use a computer once to perform these operations, you might brick WebOS and its essential you have developer mode on in order to change any files you messed up from a computer terminal.

2. Install Preware. If you have not, install the app Preware to your device. Instructions found here: [http://theunlockr.com/2010/04/29/how-to-install-preware-on-the-palm-pre-install-root-required-apps-themes-patches-and-tweaks/ | Install Preware]

=The Steps to Speed Up the Pre Minus.=

==Step 1: Overclocking==

One of the most important steps is to overclock the processor and RAM using Unixpsycho's F105 Kernel. This kernel allows you to overclock the CPU to 1ghz as well as overclock the RAM, which is essential as RAM is the biggest issue with WebOS 2.1. At rest on a Pre2, I have seen that WebOS 2.1 uses about 300mb of ram. The Palm Pre Minus only has 256mb, so we are already using up more than 100% of the RAM of the phone before we even open an app. We must speed up and manage RAM as best we can in order to have any hope of running WebOS 2.1 smoothly.

The best way to install this kernel is through Preware.

1. First follow the steps to add the testing kernel feeds in Preware here: [http://www.webos-internals.org/wiki/Testing_Feeds#Kernel_Testing_Feeds | Kernel Testing feeds]

2. Once you have installed the feeds, go to Preware and go to '''Available Packages > Kernel > All ''' and install the "F105 Thunderchief" Kernel.

3. Install Govnah from Preware as well. This is used to modify and monitor the CPU speeds.

4. Restart

Your phone should now be overclocked to 1Ghz and your RAM overclocked as well.

==Step 2: Installing Patches to speed up the phone==

Patches are a great and easy way to speed up the Pre Minus. They easily modify the code in WebOS so that your phone runs faster or is more responsive due to several different reasons.

Here are the list of patches to install from Preware in order to speed up the Pre Minus: (They are found under ''' Available Packages > Patches ''')

'''Faster Card Animations HYPER Version

'''Smooth Scrolling

'''Increase Touch Sensitivity and Smoothness

'''Remove Dropped Packet Logging

'''Unset CFQ IO Scheduler

'''Unthrottle Download Manager'''

DO NOT install "Muffle System Logging" patch as this WILL break WebOS from indexing your photos, and any photos you take or download will disappear from the Photos app.

There you have it. Restart your Pre again and it should run faster as well.

==Minimal System Logging==

WebOS by default logs EVERYTHING you do, which can actually bog down the OS quite a bit. To disable this, follow these steps:

1. Open the phone dialer.

2. For Sprint/Verizon/CDMA: Dial ##5647 (##LOGS#) and press SEND. For AT&T/O2/GSM: Dial #*5647# and press SEND.

3. Tap "Change logging levels."

4. Tap "Set logging to minimal."

5. Tap OK to confirm.

6. Tap OK again after it finishes.

7. Reboot your Pre.

8. Enjoy the performance boost!

The overclocked kernels do this by default but its better to be safe than sorry and make sure they are disabled.

DO NOT USE THE MUFFLE SYSTEM LOGGING PATCH, IT WILL BREAK YOUR PHOTOS.

==Install Preset Reset==

Go to Preware and install the Homebrew app Preset Reset. Open it and set it to reset your phone every day at a specific time (most likely when you are sleeping) . This way your phone will be nice and fresh in the morning, and the cache and memory leaks from the day before will be wiped clean from the device.

==Install JSTop==

Install "JSTop" from Preware. Open the app and tap the top left where the name "JSTop appears" to access the preferences for the app. Click "Enable Auto GC" and "Disable Notifications".

This will have JSTop automatically clear out any garbage memory or memory leaks at set intervals, which are pure murder for the RAM starved Pre Minus.

==Cleanup==

Periodically go into apps and clear out any history. This history severally slows the phone down after it builds up.

Phone App - Clear call history

Messaging App - Delete all messages

Email App - Delete any old emails you dont need

Google Maps - Clear search history

Browser - Delete History and Cookies and Cache.

Also, turn off any notification service that you don't need, such as Facebook Updates, etc. All of these services require the app to run in the background to "listen" for notifications and take up RAM.

Remove any Just Type services that you don't use, these also take up indexing cache.

==More advanced hacks==

These next hacks are more advanced and should only be done by those who have some computer experience. They involve using the Terminal as well as installing special patch files to speed up the Pre. These are the most dramatic hacks however that have shown the best performance so far.

====Modify System Control Configuration====

Linux allows you to add a file that will modify how the kernel handles using the RAM as well as virtual memory in the Pre Minus. With such little RAM to spare, we are going to modify how Linux stores applications and cache on the Pre to remedy the hanging, stalls and other issues experienced with using WebOS 2.1 on the Pre Minus.

Simply install the .ipk here to install it.

Reboot your Pre.

Updates will be provided occasionally so come back here to check out newer versions.

===Modify Luna.conf===

There are some modifications that can be done to the luna.conf file on WebOS to speed up the Pre Minus.

For now, the browser app is set to only close when the system runs out of ram. This means that even if you swipe away the Browser card, its still running in the background. The luna.conf has been modified in this patch to close the Browser immediately.

Some other minor tweaks have been added as well.

This will not conflict with the "Increase Touch Sensitivity and Smoothness" patch.

Install it here:

===Resize Swap File and Disable Compcache===

BadBooty

2011-06-06T19:55:49Z

Xanadu73: Created page with "<div style='position: relative;'> {{application |name=Bad Booty |type=webOS |version=Version: 1.0.0 (06-06-2011) |tag=Fun |screenshot=Badbooty_2011-06-06_154303.png |descri..."

File:Badbooty 2011-06-06 154303.png

2011-06-06T19:54:52Z

Xanadu73: Badbooty_2011-06-06_154303.png

Badbooty_2011-06-06_154303.png

Application:SimpleBigBook

2011-06-03T11:14:50Z

Xanadu73: /* Remaining Known Issues */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook_2011-03-06_070047.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
Coming soon:
*Bookmarks!

Current:
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently, git is inline with release, feature wise.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundred times it is hitting that part of the code EVERY page load.
*There's a fair amount of Mojo specific things. Two things here:
**With Mojo dieing, any Mojo-isms need to have Enyo equivalents.
**Bag Palm specific stuff (Mojo/Enyo) and move to straight HTML5/JS for use under whatever Palm does and portability to other mobile OS's.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and manually installing it on your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-06-03T11:11:25Z

Xanadu73: /* Status */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook_2011-03-06_070047.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
Coming soon:
*Bookmarks!

Current:
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently, git is inline with release, feature wise.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundred times it is hitting that part of the code EVERY page load.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and manually installing it on your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-06-03T11:03:43Z

Xanadu73: Updated screen shot

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook_2011-03-06_070047.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
Coming soon:
*Bookmarks!

Current:
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently implementing BOOKMARKS! It works pretty well, I just need to make it prettier.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundred times it is hitting that part of the code EVERY page load.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and manually installing it on your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

File:Simplebigbook 2011-03-06 070047.png

2011-06-03T11:03:18Z

Xanadu73: Simplebigbook_2011-03-06_070047.png

Simplebigbook_2011-03-06_070047.png

Application:SimpleBigBook

2011-06-03T11:00:18Z

Xanadu73: /* Installing */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
Coming soon:
*Bookmarks!

Current:
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently implementing BOOKMARKS! It works pretty well, I just need to make it prettier.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundred times it is hitting that part of the code EVERY page load.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and manually installing it on your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-05-23T22:29:31Z

Xanadu73: /* Key Features */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
Coming soon:
*Bookmarks!

Current:
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently implementing BOOKMARKS! It works pretty well, I just need to make it prettier.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundred times it is hitting that part of the code EVERY page load.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and transferring it to your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-05-23T22:28:39Z

Xanadu73: /* Remaining Known Issues */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently implementing BOOKMARKS! It works pretty well, I just need to make it prettier.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundred times it is hitting that part of the code EVERY page load.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and transferring it to your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-05-23T22:28:28Z

Xanadu73: /* Remaining Known Issues */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently implementing BOOKMARKS! It works pretty well, I just need to make it prettier.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The page fade scrim disappears sometimes. I really don't see why. I've verified a hundered times it is hitting that part of the code EVERY page load.
*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and transferring it to your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-05-23T22:27:01Z

Xanadu73: /* Status */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

Currently implementing BOOKMARKS! It works pretty well, I just need to make it prettier.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and transferring it to your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

How To Remove VoiceDial

2011-05-20T18:52:50Z

Xanadu73: /* Restoring */ I made / ro *before* running ldconfig. /etc/ld.so.cache wouldn't be able to be updated! D'oh!

= Summary =
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

= Background =
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

= Disable System Service =
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

= Complete Removal (No Way Back) =
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /
<nowiki>#</nowiki> ldconfig

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time. There is no way to "re-install" VoiceDial with this method. The next method ''can'' make it possible to "re-install" VoiceDial.

= Complete Removal (Reversible) =
If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to a tarball in /media/internal/VoiceDialBackup, remove all the packages, and remove the service from boot-time:

<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvpf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

= Restoring =
You need to have the meta-doctor repo still available to pull out the .ipk's for VoiceDial. If you did a "make clobber", simply re-run the build script for your model phone.

<nowiki>#</nowiki> user@aragorn /srv/meta-doctor $ find -iname '*voice*ipk'
./build/preplus-p101ueu-wr-2.1.0/carrier/contacts.plugin.pmvoicecommand_1.0-2_all.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-dede_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-engb_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-enus_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-eses_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-esmx_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-frca_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-frfr_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-itit_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand_1.4-5.30_armv7.ipk

Install those .IPK's back onto your device:

1) Plug your device into a computer with a '''functioning''' novacomd.
2) cd /srv/meta-doctor/build/preplus-p101ueu-wr-2.1.0/carrier/ (or where ever you have your meta-doctor build directory).
3) for IPK in *voice* ; do palm-install -d usb $IPK ; done
4) novaterm -d usb
5) <nowiki>root@My Pre:/#</nowiki> mount -oremount,rw /
6) <nowiki>root@My Pre:/#</nowiki> tar -xvpf /media/internal/VoiceCommandBackup/VoiceCommandExtras.tar.gz -C /
7) <nowiki>root@My Pre:/#</nowiki> ldconfig
8) <nowiki>root@My Pre:/#</nowiki> mount -oremount,ro /
9) <nowiki>root@My Pre:/#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'
10) <nowiki>root@My Pre:/#</nowiki> reboot

Everything should be back to it's MediaServer killing norm!

How To Remove VoiceDial

2011-05-19T15:27:05Z

Xanadu73:

= Summary =
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

= Background =
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

= Disable System Service =
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

= Complete Removal (No Way Back) =
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /
<nowiki>#</nowiki> ldconfig

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time. There is no way to "re-install" VoiceDial with this method. The next method ''can'' make it possible to "re-install" VoiceDial.

= Complete Removal (Reversible) =
If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to a tarball in /media/internal/VoiceDialBackup, remove all the packages, and remove the service from boot-time:

<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvpf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

= Restoring =
You need to have the meta-doctor repo still available to pull out the .ipk's for VoiceDial. If you did a "make clobber", simply re-run the build script for your model phone.

<nowiki>#</nowiki> user@aragorn /srv/meta-doctor $ find -iname '*voice*ipk'
./build/preplus-p101ueu-wr-2.1.0/carrier/contacts.plugin.pmvoicecommand_1.0-2_all.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-dede_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-engb_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-enus_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-eses_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-esmx_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-frca_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-frfr_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand-itit_1.0-5.30_armv7.ipk
./build/preplus-p101ueu-wr-2.1.0/carrier/pmvoicecommand_1.4-5.30_armv7.ipk

Install those .IPK's back onto your device:

1) Plug your device into a computer with a '''functioning''' novacomd.
2) cd /srv/meta-doctor/build/preplus-p101ueu-wr-2.1.0/carrier/ (or where ever you have your meta-doctor build directory).
3) for IPK in *voice* ; do palm-install -d usb $IPK ; done
4) novaterm -d usb
5) <nowiki>root@My Pre:/#</nowiki> mount -oremount,rw /
6) <nowiki>root@My Pre:/#</nowiki> tar -xvpf /media/internal/VoiceCommandBackup/VoiceCommandExtras.tar.gz -C /
7) <nowiki>root@My Pre:/#</nowiki> mount -oremount,ro /
8) <nowiki>root@My Pre:/#</nowiki> ldconfig
9) <nowiki>root@My Pre:/#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'
10) <nowiki>root@My Pre:/#</nowiki> reboot

Everything should be back to it's MediaServer killing norm!

How To Remove VoiceDial

2011-05-19T15:07:09Z

Xanadu73: /* Complete Removal (No Way Back) */ Added "ldconfig" to remove the *.so files from the LD cacher.

=== Summary ===
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

=== Background ===
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== Disable System Service ===
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

=== Complete Removal (No Way Back) ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /
<nowiki>#</nowiki> ldconfig

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time. There is no way to "re-install" VoiceDial with this method. The next method ''can'' make it possible to "re-install" VoiceDial.

=== Complete Removal (Reversible) ===
If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to a tarball in /media/internal/VoiceDialBackup, remove all the packages, and remove the service from boot-time:

<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvpf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

How To Remove VoiceDial

2011-05-19T15:02:56Z

Xanadu73: Added "p" to the tar - preserve permissions!

=== Summary ===
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

=== Background ===
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== Disable System Service ===
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

=== Complete Removal (No Way Back) ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time. There is no way to "re-install" VoiceDial with this method. The next method ''can'' make it possible to "re-install" VoiceDial.

=== Complete Removal (Reversible) ===
If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to a tarball in /media/internal/VoiceDialBackup, remove all the packages, and remove the service from boot-time:

<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvpf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

Application:Govnah

2011-04-29T14:53:01Z

Xanadu73: Added "Troubleshooting/FAQs"

[[Category:Application]]
This page is currently available in these languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.7 (2010-11-28)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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 various Linux kernels.
:* Ability to reduce/raise the amount of power parts of the device uses to reduce battery consumption.
:* 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 enabled Linux IO schedulers.
:* The enabled Linux TCP Congestion algorithms.

 

=Installation=
The following guide assumes a Palm Pre/Pre+/Pre2 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".
#Restart your phone as prompted.

Note:
See the [http://www.webos-internals.org/wiki/Application:UberKernel the UberKernel page] for further information on its abilities and use.

 

=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=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:
#Save your profile with the stock 10M compcache.
#You need to edit /etc/event.d/compcache to reflect your setting.
:*The number is your target size in K. For a 14M compcache: 14 * 1024 = 14336.
:*Reboot your phone.

 

=Governors In-Depth=
===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

 

===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
* scaling_min_freq: 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.
* 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.
* 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.
* 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====
* 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.
* sampling_rate: same as ondemand.
* sampling_rate_(min|max): same as ondemand.
* up_threshold: same as ondemand.
* ignore_nice_load: same as ondemand.

====userspace====
* scaling_setspeed: one of the values from scaling_available_frequencies
* NB: when userspace is selected LunaSysMgr will change the frequency as it feels.

====powersave====
* Nothing special

====performance====
* Nothing special

====screenstate====
* Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Application:Govnah

2011-04-29T14:41:37Z

Xanadu73: Too much BOLD was harming readability...

[[Category:Application]]
This page is currently available in these languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.7 (2010-11-28)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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 various Linux kernels.
:* Ability to reduce/raise the amount of power parts of the device uses to reduce battery consumption.
:* 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 enabled Linux IO schedulers.
:* The enabled Linux TCP Congestion algorithms.

 

=Installation=
The following guide assumes a Palm Pre/Pre+/Pre2 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".
#Restart your phone as prompted.

Note:
See the [http://www.webos-internals.org/wiki/Application:UberKernel the UberKernel page] for further information on its abilities and use.

 

=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

 

===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
* scaling_min_freq: 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.
* 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.
* 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.
* 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====
* 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.
* sampling_rate: same as ondemand.
* sampling_rate_(min|max): same as ondemand.
* up_threshold: same as ondemand.
* ignore_nice_load: same as ondemand.

====userspace====
* scaling_setspeed: one of the values from scaling_available_frequencies
* NB: when userspace is selected LunaSysMgr will change the frequency as it feels.

====powersave====
* Nothing special

====performance====
* Nothing special

====screenstate====
* Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Application:Govnah

2011-04-29T12:28:54Z

Xanadu73: Eye Pleasing

[[Category:Application]]
This page is currently available in these languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.7 (2010-11-28)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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 various Linux kernels.
:* Ability to reduce/raise the amount of power parts of the device uses to reduce battery consumption.
:* 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 enabled Linux IO schedulers.
:* The enabled Linux TCP Congestion algorithms.

 

=Installation=
The following guide assumes a Palm Pre/Pre+/Pre2 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".
#Restart your phone as prompted.

Note:
See the [http://www.webos-internals.org/wiki/Application:UberKernel the UberKernel page] for further information on its abilities and use.

 

=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

 

===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
* '''scaling_min_freq''': 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.
* '''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.
* '''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.
* '''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====
* '''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.
* '''sampling_rate''': same as ondemand.
* '''sampling_rate_(min|max)''': same as ondemand.
* '''up_threshold''': same as ondemand.
* '''ignore_nice_load'''v: same as ondemand.

====userspace====
* '''scaling_setspeed''': one of the values from scaling_available_frequencies
* '''NB''': when userspace is selected LunaSysMgr will change the frequency as it feels.

====powersave====
* Nothing special

====performance====
* Nothing special

====screenstate====
* Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Application:Govnah

2011-04-29T12:17:40Z

Xanadu73: /* Installation */ Clarification.

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.5 (2010-10-22)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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 various Linux kernels.
:* Ability to reduce/raise the amount of power parts of the device uses to reduce battery consumption.
:* 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 enabled Linux IO schedulers.
:* The enabled Linux TCP Congestion algorithms.

 

=Installation=
The following guide assumes a Palm Pre/Pre+/Pre2 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".
#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.

 

=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

 

===Standard Linux Governors===
* Generic items (needed for 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_min_freq - 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.
** 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.
** 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.
** 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'''
** 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.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.

* '''userspace'''
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.

* '''powersave'''
** Nothing special

* '''performance'''
** Nothing special

* '''screenstate'''
** Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Application:Govnah

2011-04-29T12:11:20Z

Xanadu73: /* Purpose */ Clarification.

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.5 (2010-10-22)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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 various Linux kernels.
:* Ability to reduce/raise the amount of power parts of the device uses to reduce battery consumption.
:* 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 enabled Linux IO schedulers.
:* The enabled Linux TCP Congestion algorithms.

 

=Installation=
The following guide assumes a Palm Pre/Pre+ that has the original 1.4.1.1 kernel and no over-clocking patches.

#On Preware's home screen, type "Gov" and hit enter.
#Select "Govnah" and "Install"
#If you have not yet installed a "Kernel", on Preware's home screen, type "uber" and hit enter.
#Select "[[Application:UberKernel|UberKernel (Palm Pre/Pre+)]]" and "Install"
#Restart your phone as promted

 
=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

 

===Standard Linux Governors===
* Generic items (needed for 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_min_freq - 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.
** 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.
** 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.
** 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'''
** 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.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.

* '''userspace'''
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.

* '''powersave'''
** Nothing special

* '''performance'''
** Nothing special

* '''screenstate'''
** Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

WebOS 2 Upgrade

2011-04-29T11:16:42Z

Xanadu73: /* Sprint */ Move SPECIFIC info out of this page and reference the Sprint PRL Update page.

= Overview =
With the release of the webOS 2.1.0 doctor by HP for O2 and Vodafone Pre+ devices, there is now a legal way to get webOS 2.1 onto the legacy devices of carriers that are not onboard with the 2.x upgrade. Compatible devices include all Pre and Pre Plus devices. This is not compatible with Pixi devices.

'''You must read this page from top to bottom twice before starting this procedure. You must complete all steps from 0 to 6. Do not omit any steps. Do not improvise. Do not think you can ignore the instructions. If you do not follow these instructions precisely, completely and without error, you will not achieve your goal and you will annoy a lot of people with a lot of unnecessary questions in the process.'''

'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''

= Disclaimer =
'''This is a process that uses official HP software in unofficial ways. You should always be prepared for the unlikely possibility that your device may be completely wiped and your Palm profile may be permanently destroyed. Do not proceed unless you have made appropriate backups and are OK with that. Working knowledge of MetaDoctor and Linux systems in general is needed.'''

If you feel the need to ask whether you should do this on your primary phone, then you should not, as that indicates that you have not yet taken the required precautions and backups in case something goes wrong.

= Other Tutorials =
'''Note that this wiki page is always the authoritative source of information about this process, so you should refer to this page first for any and all instructions. Here are some other pages which you may find useful in addition to this page. They do not replace the information on this page, which you should read from top to bottom first.'''
== Tutorials that have been updated to match the latest instructions ==
* ''PreCentral'' forum user @malpha recorded a two-part [http://www.youtube.com/watch?v=CJB8NJ72kZg video overview] of the process as she followed this step-by-step. {Sprint Pre-, Ubuntu}.
== Tutorials that are out of date and should not be relied upon ==
* ''PreCentral'' forum user @djwhitey recorded a 9-minute [http://www.youtube.com/watch?v=PF2ciiNFxLc walkthrough] (includes Activation Error). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04}.
* ''PreCentral'' forum user @innocentbystander has written a start-to-finish guide to installing and building the Meta Doctor under Mac OS 10.6 for those with little or no experience with the command line. It can be found [http://forums.precentral.net/showthread.php?p=2885787 here].

= Using MetaDoctor Scripts =

== Step 0: Backup your device ==
Make sure you have copies of all the data that you want to preserve from your palm profile. There is a possibility that you will need to clear your palm profile to be successful in this upgrade, so you should act as if that is going to happen from the start.

Also, make sure you run the [[Application:SaveRestore]] application from Preware to back up your application data - you don't want to lose your Angry Birds progress, do you?

Then copy all the files from the USB drive onto your PC to keep them safe, including music, downloads, and pictures. The webOS Doctor has been known to wipe your USB drive without warning, so you should act as if that is going to happen from the start.

If your phone is set to use the Palm Profile as the default location for contacts you may want to manually export these. To check how many palm profile contacts you have: Contacts App -> Preferences & Accounts -> tap "Palm Profile" under the "accounts" subsection.
To manually export contacts see this post: [http://forums.precentral.net/webos-synergy-synchronization/215705-howto-transfer-contacts-palm-profile-gmail-yahoo-mail-easier-way-2.html#post2886607 PreCentral Forums - How To Transfer contacts]. They can be imported back onto your phone by emailing the file of exported contacts to yourself, and opening that attachment on your phone.

A guide for backing up using Save/Restore can be found [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew here].

== Step 1: Prerequisites ==
=== Disk Space ===

You should allow up to 10GB of disk space for this process.

=== MetaDoctor ===

See [[Application:MetaDoctor]] for information on how to install MetaDoctor.

'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''

Note that the procedure for the WebOS 2 Upgrade is on this page. The MetaDoctor is simply a tool which is used by this procedure. You need to complete only Step 1: Setting up Meta-Doctor on that page. When you get to the end of Step 1: Setting up Meta-Doctor on that page, you should come back to this page and continue the procedure on this page.

=== Palm SDK ===

See [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website] for Windows and [http://developer.palm.com/index.php?option=com_content&view=article&id=1585 for Ubuntu].
Whilst the Palm SDK is not strictly required to complete this procedure, it is the best way to install the novacom and novaterm programs which are used to transfer files to and from your device and to access the command line on your device.

=== Novacom Drivers ===

If you are unable to get the official novacom drivers from the Palm SDK to connect to your device, you can alternately try Jason Robitaille's [http://universal-novacom-installer.googlecode.com/files/Universal%20Novacom%20Installer.jar Universal Novacom Driver Installer]

These drivers are necessary to interface with the Pre. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit). Note that it does not support the Pre 2 on Ubuntu. For that you'll need Linux-specific drivers, which HP makes available [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb here]for 32-bit and [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb here] for 64-bit.

== Step 2: Prepare your Palm Profile ==
With unsupported carrier/device/OS combinations, it may be necessary to clear some Palm Profile data to allow you to sign in on webOS 2.x devices. The process is as follows:
'''Warning: this will delete data from your Palm Profile, including but not limited to: calendars, contacts, account information, email signatures, bookmarks, memos, tasks, SSM/MMS messages, and icon/launcher arrangement.'''
# Open the Backup app.
# Turn off backups, confirming that you wish to erase your palm profile information.

'''This step is extremely important if you find that after finishing the webOS 2.1 installation your saved apps don't download to your device automatically and your Palm Profile account name under Accounts is "Dr. Skipped Firstuse". You should delete your profile info and Doctor again.'''

NOTE: The latest scripts (as of 5:00pm EST) MAY allow direct conversion of a 1.4.5 profile to 2.1.0 without deleting Palm Profile data. Please read the information under "Palm Profile" below to understand the issues that my arise from attempting this, as well as the required solutions to resolve those issues.

== Step 3: Run device-specific MetaDoctor script ==
The MetaDoctor scripts will automatically download the latest necessary webOS doctors, extract and replace CDMA radio firmware as necessary, and will build and launch the modified webOS Doctor.

'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''

'''A NOTE ON "RE-DOCTORING":''' If this is not your first time through this process, you should do a "git pull" and a "make clobber" to ensure you have the latest scripts and a pristine build folder. From the command line, type "cd meta-doctor" without the quotes and press enter. Then type "git pull" without the quotes and press enter. Then type "make clobber" without the quotes and press enter. Voila! You now have the latest scripts and a clean folder to build your doctor in.

'''From the meta-doctor directory''', run the meta-script that corresponds to your device (note that the strings enclosed by < and > in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version>
</nowiki></pre>

You should replace <carrier>, <device>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

A list of all the scripts can be found by typing
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

'''For those who for what ever reason will never be using their phone on a cellular network and wish to use the phone only on wifi, just add "--wifi-only" as an extra argument to the meta-script:'''
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version> --wifi-only
</nowiki></pre>

Again, you should replace <device>, <carrier>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

Then, when your device boots after step 4, all you need to do is configure and start wifi and then run the Gesture Tutorial and you should be good to go. Note that in this case the end of the palm profile login procedure will appear to cycle forever, so just manually reboot the device using Opt-Sym-R when that happens.

Specific additional information for each of the supported device and carrier combinations can be found below:

=== AT&T Pre+ ===
<pre><nowiki>
./scripts/meta-att-preplus-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== BellMo Pre ===
<pre><nowiki>
./scripts/meta-bellmo-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== O2 Pre ===
<pre><nowiki>
./scripts/meta-o2-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== O2 Pre+ ===
<pre><nowiki>
./scripts/meta-o2-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint Pre ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint Franken Unlocked Pre 2 ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

NOTE: Tokens are no longer needed to create a Sprint Franken Unlocked Pre 2. You only need to run the script below. However, it is still a good idea to capture and store the tokens from each phone for potential future use.

<pre><nowiki>
./scripts/meta-sprint-franken-unlocked-pre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

=== Sprint Franken Verizon Pre 2 ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

NOTE: Tokens are no longer needed to create a Sprint Franken Verizon Pre 2. You only need to run the script below. However, it is still a good idea to capture and store the tokens from each phone for potential future use.

<pre><nowiki>
./scripts/meta-sprint-franken-verizon-pre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

=== Telcel Pre ===
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.00 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

'''In Fact, it seems Palm has already locked out all the Telcel activated devices, so, even if you managed to hack your Meta Doctor to have a 1.4.5 profile and see the paid apps in the Catalog, you won't be able to insert your credit card data and won't be able to buy apps anymore.'''

=== Verizon Pre+ ===
<pre><nowiki>
./scripts/meta-verizon-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== Verizon FrankenPre 2 ===
<pre><nowiki>
./scripts/meta-verizon-franken-unlocked-pre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

=== WR Pre ===

For WR devices, you should attempt to use the O2 script above first, and if you end up with a 9.9.9 version in your palm profile, then use this WR script instead.

<pre><nowiki>
./scripts/meta-wr-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

== Step 4: Run the modified webOS Doctor ==
The meta-script will automatically launch the modified webOS Doctor for you. However, if you need to move it to a different location and run it manually, the modified doctor will be a '''.jar''' file located in the build output directory:
<pre><nowiki>meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueu-wr-2.1.0.jar</nowiki></pre>

Note that the directory path will change from that example based on which script you ran, and the script will tell you the exact pathname shortly after it starts running.

Do not USB connect the phone until WebOS Doctor specifically says to.

NOTE: There have been reports that, for some users, the modified webOS doctor fails to recognize the USB connection. Similarly, up-graders have also noted that in some instances their Pre will "disconnect" from the webOS Doctor (while running) and re-boot into v.1.4.5. It has been observed that Doctoring, while putting ones Pre through the "Recovery" Reboot (as detailed [http://www.webos-internals.org/wiki/How_To_Recover here]) may mitigate these issues, and allow the Doctor to continue. There is also an instance where after pressing the "next" button to start the Doctor, the phone appeared to need charging before the Doctor would start( on a 95% full battery), and then stalled at 0%. Putting the phone into emergency recovery mode appeared to solve this problem.

Note: Sprint users please read the PRL section '''before''' running The Doctor: [http://www.webos-internals.org/wiki/WebOS_2_Upgrade#Sprint_2 "5.9.1 Sprint"].

== Step 5: There is no Step 5 ==

There used to be a complex set of additional steps required here. Too many people had trouble following them, so we automated it. You should proceed directly to Step 6.

== Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app ==
If this worked for you, we would appreciate a donation at http://donate.webos-internals.org - and if you want to thank Rod Whitby personally for the many hours that he put into creating the Meta-Doctor and this upgrade procedure, you should purchase the [http://developer.palm.com/appredirect/?packageid=org.preware.docs Preware Homebrew Documentation] app from the official app catalog, and leave a nice 5 star review containing your message of thanks.

= Caveats =

== OTA Updates ==
It is extremely unlikely that any Pre or Pre+ device will ever get another OTA update. If you preform this procedure on those devices, you should not expect OTA updates.

Performing this procedure on a Pre 2 device may allow it to receive OTA updates, but there is no guarantee.

== App Catalog ==
If your palm profile record says version 1.40.50, you will not be able to purchase apps that are marked as only compatible with webOS versions 2.x and above. This cannot be changed for these devices at this time. If your palm profile record says version 2.1.0, then you should be able to purchase all apps (depending upon your geographical restrictions and country of first activation).

=== Masquerading ===
Palm's servers only accept certain device/OS combinations as valid. While some combinations of carrier and devices running 2.1 are accepted, others have to report to the palm profile server that they are running webOS 1.4.5. This is done automatically, and cannot be changed for these devices at this time.

== Carrier-Specific Applications ==
Some carrier apps are not working in webOS 2.1. Apps that have been tested and are known to install cleanly and work will be added to the custom webOS Doctor for the appropriate device/carrier.

Known working carrier apps are listed below.

=== Sprint ===
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

===Verizon Wireless ===
* All Verizon apps should be working at this time. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!
VZW Navigator is working much better for me now on VZ Palm Pre Plus with HP Web OS 2.1. The only problem I havent solved is system updates hangs. Anyone have a solution?

=== AT&T ===
* No testing or reports of AT&T Carrier Apps

== Patches ==
Not all patches have been ported over yet. If you want to check for a certain patch, please see webOS Internals' [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all webOS-Patches Web Portal].

== Adobe Flash ==
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.

=== Adding Flash Support ===
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser. Or you can do it manually. See ([http://www.webos-internals.org/wiki/Adding_flash_support here]) for more detail.

== Performance ==
* '''OVERCLOCKING IS NOW SUPPORTED'''. Palm has just released the source code for the kernel used in webOS 2.1.0. An experimental version of UberKernel has already appeared in the experimental feeds, but casual users should wait for a stable one.
* The Pre Plus has 512 MB of memory and thus runs 2.1 quite well, but this is not the case with the original Pre since it has only 256 MB. Luckily, Palm adopted WebOS Internals's configuration of the standard Linux compcache technology that was ported to the custom kernels, and it comes active, but with only 10 MB. One potential way to enhance performance in original Pre devices is to make the compcache bigger.

=== Increase compcache size, Temporary Method ===
You can use the Govnah application to increase the size of the compcache. Disable compcache, change the size, and then reenable.

=== Increase compcache size, Permanent Method ===
You have to edit the file /etc/event.d/compcache and change the value from 10240 to 32768.

For example, you could follow these steps:

#Make sure '''novacomd''' is running on your computer.
#Use a terminal (as described on the Wiki page [http://www.webos-internals.org/wiki/Portal:Accessing_Linux Accessing Linux on the Pre... ]) to run '''novaterm''' and access your phone. Type in the following: <pre>/usr/sbin/rootfs_open -t</pre><pre>vi /etc/event.d/compcache</pre>
#vi is a bit different so, for those not familiar with how it works, the fastest way to navigate and make the required edit is in parentheses below:
##Go down to line 10 (Type <tt>10</tt> then hit <tt>Shift+G</tt>)
##Move to the first <tt>1</tt> (Type <tt>4w</tt>)
##Enter replace mode (<tt>Shift+R</tt>) and type <tt>32768</tt>
##Exit back to command mode (Press <tt>Esc</tt> or <tt>Ctrl+C</tt>)
##Save and Quit (Type <tt>:wq</tt>)
#Reboot your Pre and verify it's working by using Govnah. While you are still in novaterm, you can type the following to reboot:<pre>/sbin/reboot</pre>

== Palm Profile ==
* Some people have had problems signing in to existing Palm Profiles on 2.1 due to backup data. To make sure that you can sign in to your profile on 2.1, you should disable backups before doctoring to 2.1 and delete server side backups. Of course, this deletes most of the data in your Palm Profile (memos, tasks, calender entries, accounts, ...). Your apps will be restored on 2.1, but that is about it. Note that not all people have issues with backups. If you would rather not delete your Palm Profile data, you can try doctoring to 2.1 without turning backups off and see if restoring everything works. If it doesn't, you'll have to doctor back to 1.4.5 to turn off backups or use a new Palm Profile, though.

* If you get 9.9.9 in palm.com/palmprofile, then you can doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it.

* If you get "Dr. Skipped Firstuse" as the name of your palm profile in the new accounts app in 2.1.0 and/or if the gesture application creates a blank screen, you have a false profile problem. You need to doctor back to 1.4.5 for your carrier and login in, then delete backup info in backup app and then 2.1.0 metadoctor it. To avoid this problem, redownload the latest version of the metadoctor and run the appropiate script with the <tt>--wifi-only</tt> switch. Note: Only use <tt>--wifi-only</tt> if you do not intend to have cellular service on the device as this option disables the modem update and renders cellular service inoperable without re-doctoring.

* Alternative fix for above problem: If your profile works fine but the Impostah app and the Accounts app show your profile name as "Dr. Skipped First Use" although your phone ran the first use app after doctoring, erase your backup data from the backup app by turning off backups and choose Erase Apps and Data from the reset options in the Device Info app.

*If you get stuck at the "Auto Locate" selection screen during the login process, you can re-doctor using the same 2.1 doctor file and it will go through. It appears to be an issue when creating a new profile in 2.1 rather than "porting" your 1.4.5 profile to 2.1. After the second doctoring, you will "Sign In" to an existing profile (the one you created during the first profile login after doctoring), rather than creating a new profile.

==GPS==
Step-by-step approach for those experiencing problems with GPS following upgrade.
# To enable GPS functionality go to the "Location Services" application (click "Turn On" if GPS has been completely disabled). From there go to the "Preferences" menu in the top left hand corner and select the "Locate Me Using..." sub-menu item. Ensure that both "GPS" and "Google Services" are enabled (you may be prompted to accept the Terms of Service). Close the "Location Services" application.
# Next you need to bring up the "GPS Information" application; to do this dial ##477# (or #*477# on GSM/UMTS Pres) in the phone application (the "477" corresponds to the letter keys "GPS").
# Click the "Get Fix" button. You may receive a "GPS Error - Position Unavailable" message which you can close. Keep pressing "Get Fix" until a fix is established (it may take several attempts). You will know a fix has been established when some statistics (Latitude, Longitude etc) are displayed.
# Once a fix has been established, GPS should continue to function normally thereafter.

==Voice Dialing==
For the Sprint-Franken-Pre2 (Pre2-GSM-Unlocked confirmed + sprint-pre(-)comm) and perhaps the Verizon-Franken-Pre2, the voice dialing application may not work after the metadoctor procedure above. The application may or may not even launch after tapped. You may experience problems with sound intermittently not working, esp. when playing media, or using the phone. This will be corrected automatically with a webOS OTA Update to 2.1.0. When the phone prompts for the update, install it.

To speed up the process, go to the "System Updates" app on your phone. The WebOS 2.1 update should appear after it searches for updates. (The update for a Sprint FrankenPre2 is ~7MB and only took a few minutes to install).

==PRL==
=== Sprint ===

After applying 2.1.0 to a Sprint device using this method, there is currently no known way to update the PRL. There are permissions issues, and the conventional "Update Profile" and "Update PRL" from the Phone options will no longer work. The provisioner service binary from the Sprint 1.4.5 doctor does not work on webOS 2.x, so a version of that service for 2.x is required for this to ever work. It is not expected that this situation will change before Sprint releases another webOS phone running webOS 2.0 or above.

====Overview====
:1) Back up /var/lib/software/* before upgrading to webOS 2.1
:2) Restore /var/lib/software/* after upgrading to webOS 2.1
:3) Use PmModemUpdater to update your PRL.

 
For further information, exact directions, caveats, etc., please see the [http://www.webos-internals.org/wiki/Sprint_PRL_Update dedicated Sprint PRL Update Wiki Page].

=== Verizon ===
In order to update your PRL, you will need to manually program your phone OTA by dialing '''*228''' from the dialer, and choose the "Program your phone" option.

Application:Govnah

2011-04-29T11:10:48Z

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

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.5 (2010-10-22)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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.
:* Ability to reduce/raise the amount of power parts of the device uses.
:* Temperature range which lowers CPU frequency to cool down the device.
:* Ability to slow down the CPU when battery is low.
:* The amount of swap that can be compressed (compcache).
:* The IO schedulers.
:* The TCP Congestion algorithms.

 

=Installation=
The following guide assumes a Palm Pre/Pre+ that has the original 1.4.1.1 kernel and no over-clocking patches.

#On Preware's home screen, type "Gov" and hit enter.
#Select "Govnah" and "Install"
#If you have not yet installed a "Kernel", on Preware's home screen, type "uber" and hit enter.
#Select "[[Application:UberKernel|UberKernel (Palm Pre/Pre+)]]" and "Install"
#Restart your phone as promted

 
=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

 

===Standard Linux Governors===
* Generic items (needed for 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_min_freq - 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.
** 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.
** 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.
** 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'''
** 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.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.

* '''userspace'''
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.

* '''powersave'''
** Nothing special

* '''performance'''
** Nothing special

* '''screenstate'''
** Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Application:Govnah

2011-04-29T11:07:00Z

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

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.5 (2010-10-22)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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.
:* Ability to reduce/raise the amount of power parts of the device uses.
:* Temperature range which lowers CPU frequency to cool down the device.
:* Ability to slow down the CPU when battery is low.
:* The amount of swap that can be compressed (compcache).
:* The IO schedulers.
:* The TCP Congestion algorithms.

 

===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

 

=Installation=
The following guide assumes a Palm Pre/Pre+ that has the original 1.4.1.1 kernel and no over-clocking patches.

#On Preware's home screen, type "Gov" and hit enter.
#Select "Govnah" and "Install"
#If you have not yet installed a "Kernel", on Preware's home screen, type "uber" and hit enter.
#Select "[[Application:UberKernel|UberKernel (Palm Pre/Pre+)]]" and "Install"
#Restart your phone as promted

 
=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
* Generic items (needed for 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_min_freq - 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.
** 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.
** 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.
** 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
** 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.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.

* userspace
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.

* powersave
** Nothing special

* performance
** Nothing special

* screenstate
** Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Application:Govnah

2011-04-29T10:52:36Z

Xanadu73: /* Purpose */ Adding things that have been here forever.

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.5 (2010-10-22)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
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.
:* Ability to reduce/raise the amount of power parts of the device uses.
:* Temperature range which lowers CPU frequency to cool down the device.
:* Ability to slow down the CPU when battery is low.
:* The amount of swap that can be compressed (compcache).
:* The IO schedulers.
:* The TCP Congestion algorithms.

===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

===Current Governors===

Current governors available in the Uber-Kernel and supported by Govnah include:
:* On-demand - described above, increases clock speed in response to increases in CPU load.
:* Conservative - The opposite of on-demand conservative decreases CPU clock speed in response to decreases in CPU load.
:* Userspace - sets the CPU speed to a defined rate as chosen by LunaSysMgr
:* powersave - sets the CPU speed to the min frequency value
:* performance - sets the CPU speed to the max frequency value
:* screenstate - runs at a higher speed when the screen is on and at 500MHz when the screen is off

 

=Installation=
The following guide assumes a Palm Pre/Pre+ that has the original 1.4.1.1 kernel and no over-clocking patches.

#On Preware's home screen, type "Gov" and hit enter.
#Select "Govnah" and "Install"
#If you have not yet installed a "Kernel", on Preware's home screen, type "uber" and hit enter.
#Select "[[Application:UberKernel|UberKernel (Palm Pre/Pre+)]]" and "Install"
#Restart your phone as promted

 
=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
* Generic items (needed for 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_min_freq - 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.
** 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.
** 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.
** 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
** 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.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.

* userspace
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.

* powersave
** Nothing special

* performance
** Nothing special

* screenstate
** Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Sprint PRL Update

2011-04-28T12:15:34Z

Xanadu73: Typos, etc.

=Summary=
When you upgrade your Pre to webOS 2.1 using [http://www.webos-internals.org/wiki/WebOS_2_Upgrade the meta-doctor], Sprint users lose the ability to update their PRL ('''P'''referred '''R'''oaming '''L'''ist). This guide aids in restoring that capability. It requires that novacomd be installed and running on a computer because the steps require shell access to the Linux command line of your Pre. This guide DOES NOT discuss illegally obtained and unreleased versions of the software required to do this "normally".

NOTE:
You absolutely '''CANNOT''' use files from another phone's /var/lib/software on your phone.
That location contains unique information for YOUR phone.
If you restore someone else's files to your phone, it will become THEIR phone and no longer YOURS.
Phone number and everything.
The only way to fix this situation is to Doctor back to 1.4.5 and start over.

=Overview=
1) Back up /var/lib/software/* ''before'' upgrading to webOS 2.1 
2) Restore /var/lib/software/* ''after'' upgrading to webOS 2.1 
3) Use PmModemUpdater to update your PRL.

=Prerequisites=
You '''must''' have novacomd installed and functioning on a computer. You can go about this in a couple ways:

1) Get the novacom installer for your OS [https://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 directly from Palm]. 
2) Use the [http://forums.precentral.net/canuck-coding/278224-universal-novacom-installer-uni-v1-11-a.html Universal Novacom Installer] to help do it for you.

=Procedure=
==Step 1==
While your Pre is still running webOS 1.4.5, update PRL:
1) Phone --> App-Menu --> Preferences & Accounts --> Update PRL

NOTE:
As of April 21st 2011, some people are getting PRL# 01115, and others are getting PRL# 60678.
It is unknown why at this time.
The 01115 has some data roaming changes in it that boost data rates for some customers in certain areas.
Unofficial changelogs can be [http://www.batonrougebroadband.info found here].

After this, check to make sure that you have "prefroamlist" on your phone:

1) Plug your Pre into your computer. DO NOT put it in USB Mode.
2) Run novaterm (will open a Linux shell to your phone).
3) cd /var/lib/software/ModemFiles
4) ls

You should see a file named "prefroamlist". This is your PRL file.

==Step 2==
Now back up that location to a tarball in /media/internal (the "Flash Drive" portion of your phone):

1) cd /var/lib/software
2) tar -czvf /media/internal/my_1.4.5_prl_backup.tar.gz *

You will now have a file named "my_1.4.5_prl_backup.tar.gz" in the Flash Drive portion. It's highly recommended that you put your phone in USB mode now and copy that file to your computer for safe keeping.

==Step 3==
After running the Doctor that you created following the [http://www.webos-internals.org/wiki/WebOS_2_Upgrade Upgrade Guide], you are ready to restore that information:

1) novaterm
2) cd /var/lib/software
3) tar -xvf /media/internal/my_1.4.5_prl_backup.tar.gz
4) '''Immediately''' reboot your phone (Orange+Sym+R is the quickest).

==Step 4==
Verify that YOUR phone is still YOUR phone and check your PRL version:
1) Device Info: The first page shows your phone number at the top.
2) Device Info: Tap "More Info" at the bottom: Verify PRL.

=Manually Updating=
One way to get an updated PRL file is to have a webOS 1.4.5 device handy. Update the PRL on the 1.4.5 device and DO NOT reboot.
1) Navigate to /var/lib/software/ModemFiles

There should be a file named "prefroamlist". Make a copy.
1) cp /var/lib/software/ModemFiles/prefroamlist /media/internal/

Now it must be renamed and tarred (using 60677 only as an example - it must be named properly)
1) cd /media/internal/
2) mv prefroamlist Sprint_60677.prl
3) tar -cf prl_update.tar Sprint_60677.prl

Get the .tar file onto the Flash Drive portion of your webOS 2.1 device, then:
1) PmModemUpdater < /media/internal/prl_update.tar -m

It will disconnect the phone from the network and update the PRL. The output is similar to the following:

root@My Pre:/# PmModemUpdater < /media/internal/prl_update.tar
$ Modem is powered-on
Warning! Please make sure you have a fully charged battery or are connected to an external source before you do your update.
Warning! You can potentially trash your modem firmware if system loses power in the middle of updating firmware!
Warning! To abort, press CTRL+C.

PmModemUpdater Version 5.2.1.8 Nov. 2010 @Palm Inc

$ Creating temp file
$ Processing file ....
(05624/981179198) powerd (stop) running, process 5008
(05624/981575927) powerd (stop) pre-stop, (main) process 5008
(05624/981820067) powerd (stop) stopping, process 5008
(05624/982491454) powerd (stop) killed, process 5008
(05625/56618651) powerd (stop) post-stop
(05625/57686766) powerd (stop) waiting
$ PowerD Stopped successfully!
(05625/150734862) PmWanDaemon (stop) running, process 5065
(05625/151864012) PmWanDaemon (stop) pre-stop, (main) process 5065
(05625/152565917) PmWanDaemon (stop) stopping, process 5065
(05625/153786620) PmWanDaemon (stop) killed, process 5065
(05630/184609374) PmWanDaemon (stop) post-stop
(05630/184822997) PmWanDaemon (stop) waiting
$ PmWanDaemon Stopped successfully!
(05630/274270018) TelephonyInterfaceLayer (stop) running, process 5012
(05630/274636229) TelephonyInterfaceLayer (stop) pre-stop, (main) process 5012
(05630/274880370) TelephonyInterfaceLayer (stop) stopping, process 5012
(05630/311745604) TelephonyInterfaceLayer (stop) killed, process 5012
(05630/311989745) TelephonyInterfaceLayer (stop) post-stop
(05630/312142333) TelephonyInterfaceLayer (stop) waiting
$ TIL Stopped successfully!
{"returnValue":true}
Pass-through disabled
$ Passthrough Disabled!.
$ Acquired exclusive access to port /dev/modemdiag
$ Disable handshaking in ROM
$ Going for PRI/PRL update...No modem reset...
$ Probing modem.............
*************************************************
* Modem Firmware Info *
*************************************************
* COMP DATE = Nov 04 201019:05:0911/04/2010
* REL DATE = 11/04/2010
* HW VERSION = A20700E1
* MOB MODEL = AC
* RADIO TYPE = CDMA
* PRL VERSION =60676
* PRI CRC =0x8EF3
* EX BUILD ID = RC1.7(557)
*************************************************
<INFO> saving existing tokens
$ Successfully configured default charging device
$ Finished detecting Modem!
$ USB port active for UPDATE!
$ No version file found in the package!
$ Will Update PRI/PRL files as no firmware version file
$ CDMA Carrier Items Update ...............
$ PRI Version from Modem is 8961(1.35)
$ Updating PRI file to Modem EFS ....
$ No PRI File to Update...
$ Updating PRL .....
$ PRL Sprint_60677.prl Update Success!
$ Enable handshaking in ROM Enable handshaking in ROM
$ Please wait while restoring TIL/WAN.....
(05632/444924315) powerd (start) waiting
(05632/446175536) powerd (start) starting
(05632/446999510) powerd (start) pre-start, process 6933
(05632/464455565) powerd (start) spawned, process 6936
(05632/465584716) powerd (start) post-start, (main) process 6936
(05632/466408690) powerd (start) running, process 6936
$ powerd Restored successfully!
(05632/505135497) TelephonyInterfaceLayer (start) waiting
(05632/506295165) TelephonyInterfaceLayer (start) starting
(05632/507058104) TelephonyInterfaceLayer (start) pre-start
(05632/507821044) TelephonyInterfaceLayer (start) spawned, process 6940
(05632/508583983) TelephonyInterfaceLayer (start) post-start, (main) process 6940
(05632/509316405) TelephonyInterfaceLayer (start) running, process 6940
$ TIL Restored successfully!
(05634/553170165) PmWanDaemon (start) waiting
(05634/553994139) PmWanDaemon (start) starting
(05634/554268798) PmWanDaemon (start) pre-start
(05634/554604491) PmWanDaemon (start) spawned, process 6955
(05634/554940184) PmWanDaemon (start) post-start, (main) process 6955
(05634/555245360) PmWanDaemon (start) running, process 6955
$ PmWanDaemon Restored successfully!
$ Your device is ready for use.
$ Releasing lock to port /dev/modemdiag
root@My Pre:/#

You will see the "Update Success!" line shortly after the "Modem Firmware Info" section. Although it doesn't seem necessary, it would be a good idea to reboot your phone '''now'''. After the reboot, verify the PRL Version:
1) Device Info --> More Info
2) At the bottom it will say your PRL version

Application:SimpleBigBook

2011-04-27T20:25:05Z

Xanadu73: /* Status */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). Features will continue to be added as they are thought up and/or requested.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and transferring it to your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-04-27T20:24:01Z

Xanadu73: /* Summary */ "Fix" verbage...

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but had become largely abandoned. It is being dusted off, getting issues fixed and having features added.

 

=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). As I think of them I will continue to add features as well.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and transferring it to your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Sprint PRL Update

2011-04-27T20:17:41Z

Xanadu73:

=Summary=
When you upgrade your Pre to webOS 2.1 using [http://www.webos-internals.org/wiki/WebOS_2_Upgrade the meta-doctor], Sprint users lose the ability to update their PRL ('''P'''referred '''R'''oaming '''L'''ist). This guide aids in restoring that capability. It requires that novacom be installed on a computer because the steps require shell access to the Linux command line of your Pre. This guide DOES NOT discuss illegally obtained and unreleased versions of the software required to do this "normally".

NOTE:
You absolutely '''CANNOT''' use files from another phone's /var/lib/software on your phone.
That location contains unique information for YOUR phone.
If you restore someone else's files to your phone, it will become THEIR phone and no longer YOURS.
The only way to fix this situation is to Doctor back to 1.4.5 and start over.

=Overview=
1) Back up /var/lib/software/* ''before'' upgrading to webOS 2.1 
2) Restore /var/lib/software/* ''after'' upgrading to webOS 2.1 
3) Use PmModemUpdater to update your PRL.

=Prerequisites=
You '''must''' have novacom installed and functioning on a computer. You can go about this in a couple ways:

1) Get the novacom installer [https://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 directly from Palm]. 
2) Use the [http://forums.precentral.net/canuck-coding/278224-universal-novacom-installer-uni-v1-11-a.html Universal Novacom Installer] to help do it for you.

=Procedure=
==Step 1==
While your Pre is still running webOS 1.4.5, update PRL:
1) Phone --> App-Menu --> Preferences & Accounts --> Update PRL

NOTE:
As of April 21st 2011, some people are getting PRL# 01115, and others are getting PRL# 60678.
It is unknown why at this time.
It is believed that it has something to do with the length of time the account has been open.
The 01115 has some data roaming changes in it that boost data rates for some customers in certain areas.
Unofficial changelogs can be [http://www.batonrougebroadband.info found here].

After this, check to make sure that you have "prefroamlist" on your phone:

1) Plug your Pre into your computer. DO NOT put it in USB Mode.
2) novaterm (will open a Linux shell to your phone).
3) cd /var/lib/software/ModemFiles
4) ls

You should see a file named "prefroamlist". This is your PRL file.

==Step 2==
Now back up that location to a tarball in /media/internal (the "Flash Drive" portion of your phone):

1) cd /var/lib/software
2) tar -czvf /media/internal/my_1.4.5_prl_backup.tar.gz *

You will now have a file named "my_1.4.5_prl_backup.tar.gz" in the Flash Drive portion. It's highly recommended that you put your phone in USB mode now and copy that file to your computer.

==Step 3==
After running the Doctor that you created following the [http://www.webos-internals.org/wiki/WebOS_2_Upgrade Upgrade Guide], you are ready to restore that information:

1) novaterm
2) cd /var/lib/software
3) tar -xvf /media/internal/my_1.4.5_prl_backup.tar.gz
4) Immediately reboot your phone (Orange+Sym+R is the quickest).

==Step 4==
Verify that your phone is still your phone and check your PRL version:
1) Device Info: The first page at the top shows your phone number.
2) Device Info: Tap "More Info" at the bottom: Verify PRL.

=Manually Updating=
One way to get an updated PRL file is to have a webOS 1.4.5 device handy. Update the PRL on the 1.4.5 device and DO NOT reboot.
1) Navigate to /var/lib/software/ModemFiles

There should be a file named "prefroamlist". Make a copy.
1) cp /var/lib/software/ModemFiles/prefroamlist /media/internal/

Now it must be renamed and tarred (using 60677 only as an example - it must be named properly)
1) cd /media/internal/
2) mv prefroamlist Sprint_60677.prl
3) tar -cf prl_update.tar Sprint_60677.prl

Get the .tar file onto the flash Drive portion of your webOS 2.1 device, then:
1) PmModemUpdater < /media/internal/prl_update.tar -m

It will disconnect the phone from the network and update the PRL. The output is similar to the following:

root@My Pre:/# PmModemUpdater < /media/internal/prl_update.tar
$ Modem is powered-on
Warning! Please make sure you have a fully charged battery or are connected to an external source before you do your update.
Warning! You can potentially trash your modem firmware if system loses power in the middle of updating firmware!
Warning! To abort, press CTRL+C.

PmModemUpdater Version 5.2.1.8 Nov. 2010 @Palm Inc

$ Creating temp file
$ Processing file ....
(05624/981179198) powerd (stop) running, process 5008
(05624/981575927) powerd (stop) pre-stop, (main) process 5008
(05624/981820067) powerd (stop) stopping, process 5008
(05624/982491454) powerd (stop) killed, process 5008
(05625/56618651) powerd (stop) post-stop
(05625/57686766) powerd (stop) waiting
$ PowerD Stopped successfully!
(05625/150734862) PmWanDaemon (stop) running, process 5065
(05625/151864012) PmWanDaemon (stop) pre-stop, (main) process 5065
(05625/152565917) PmWanDaemon (stop) stopping, process 5065
(05625/153786620) PmWanDaemon (stop) killed, process 5065
(05630/184609374) PmWanDaemon (stop) post-stop
(05630/184822997) PmWanDaemon (stop) waiting
$ PmWanDaemon Stopped successfully!
(05630/274270018) TelephonyInterfaceLayer (stop) running, process 5012
(05630/274636229) TelephonyInterfaceLayer (stop) pre-stop, (main) process 5012
(05630/274880370) TelephonyInterfaceLayer (stop) stopping, process 5012
(05630/311745604) TelephonyInterfaceLayer (stop) killed, process 5012
(05630/311989745) TelephonyInterfaceLayer (stop) post-stop
(05630/312142333) TelephonyInterfaceLayer (stop) waiting
$ TIL Stopped successfully!
{"returnValue":true}
Pass-through disabled
$ Passthrough Disabled!.
$ Acquired exclusive access to port /dev/modemdiag
$ Disable handshaking in ROM
$ Going for PRI/PRL update...No modem reset...
$ Probing modem.............
*************************************************
* Modem Firmware Info *
*************************************************
* COMP DATE = Nov 04 201019:05:0911/04/2010
* REL DATE = 11/04/2010
* HW VERSION = A20700E1
* MOB MODEL = AC
* RADIO TYPE = CDMA
* PRL VERSION =60676
* PRI CRC =0x8EF3
* EX BUILD ID = RC1.7(557)
*************************************************
<INFO> saving existing tokens
$ Successfully configured default charging device
$ Finished detecting Modem!
$ USB port active for UPDATE!
$ No version file found in the package!
$ Will Update PRI/PRL files as no firmware version file
$ CDMA Carrier Items Update ...............
$ PRI Version from Modem is 8961(1.35)
$ Updating PRI file to Modem EFS ....
$ No PRI File to Update...
$ Updating PRL .....
$ PRL Sprint_60677.prl Update Success!
$ Enable handshaking in ROM Enable handshaking in ROM
$ Please wait while restoring TIL/WAN.....
(05632/444924315) powerd (start) waiting
(05632/446175536) powerd (start) starting
(05632/446999510) powerd (start) pre-start, process 6933
(05632/464455565) powerd (start) spawned, process 6936
(05632/465584716) powerd (start) post-start, (main) process 6936
(05632/466408690) powerd (start) running, process 6936
$ powerd Restored successfully!
(05632/505135497) TelephonyInterfaceLayer (start) waiting
(05632/506295165) TelephonyInterfaceLayer (start) starting
(05632/507058104) TelephonyInterfaceLayer (start) pre-start
(05632/507821044) TelephonyInterfaceLayer (start) spawned, process 6940
(05632/508583983) TelephonyInterfaceLayer (start) post-start, (main) process 6940
(05632/509316405) TelephonyInterfaceLayer (start) running, process 6940
$ TIL Restored successfully!
(05634/553170165) PmWanDaemon (start) waiting
(05634/553994139) PmWanDaemon (start) starting
(05634/554268798) PmWanDaemon (start) pre-start
(05634/554604491) PmWanDaemon (start) spawned, process 6955
(05634/554940184) PmWanDaemon (start) post-start, (main) process 6955
(05634/555245360) PmWanDaemon (start) running, process 6955
$ PmWanDaemon Restored successfully!
$ Your device is ready for use.
$ Releasing lock to port /dev/modemdiag
root@My Pre:/#

You will see the "Update Success!" line shortly after the "Modem Firmware Info" section. Although it doesn't seem necessary, it would be a good idea to reboot your phone now. After the reboot, verify the PRL Version:
1) Device Info --> More Info
2) At the bottom it will say your PRL version

Application:Govnah

2011-04-27T20:03:12Z

Xanadu73: /* Summary */ Move icon to left like other App pages.

[[Category:Application]]
This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Govnah]]
:[[Image:Germany.png]] [[Application:Govnah-DE]]
:[[Image:France.png]] [[Application:Govnah-FR]]

{{application
|name=Govnah
|type=webOS
|version=Version: 0.7.5 (2010-10-22)
|tag=Utilities
|screenshot=GovnahHome4Life-0.6.1.png
|description=}}

 
=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]].

===Purpose===
The application ''Govnah'' does two things:
:* It provides a real-time graph of CPU speed, CPU temperature, memory usage and system load
:* Provides a mechanism for setting the parameters of the "governors" exposed by the kernel and configuring other kernel features.

===Real World Examples===

The Uber-Kernel exposes a governor called ''on-demand''. The on-demand governor increases and decreases clock speed based on the percentage of CPU usage.

The ''on-demand'' governor exposes the following parameters which can be set by Govnah:
:* scaling_max_freq - Set the maximum frequency your CPU is allowed to scale to.
:* scaling_min_freq - Same as scaling_max_freq but setting a minimum value.
:* sampling_rate - How often you want the kernel to look at the CPU usage (in microseconds) Typically this is set to values of 10000 or more.
:* up_threshold - This defines what the average CPU usage percentage increase between samplings for the kernel to decide to increase the CPU frequency.
:* ignore_nice_load - If '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. The bias is in tenths of a percent (0 to 1000). A setting of 100 will result in a 10% smaller increase in CPU speed for a given usage than a setting of 0 would result in.

Each "Governor" in the kernel tells ''Govnah'' what parameters it has that may be set and may also say what the limits of those parameters are.

===Current Governors===

Current governors available in the Uber-Kernel and supported by Govnah include:
:* On-demand - described above, increases clock speed in response to increases in CPU load.
:* Conservative - The opposite of on-demand conservative decreases CPU clock speed in response to decreases in CPU load.
:* Userspace - sets the CPU speed to a defined rate as chosen by LunaSysMgr
:* powersave - sets the CPU speed to the min frequency value
:* performance - sets the CPU speed to the max frequency value
:* screenstate - runs at a higher speed when the screen is on and at 500MHz when the screen is off

 

=Installation=
The following guide assumes a Palm Pre/Pre+ that has the original 1.4.1.1 kernel and no over-clocking patches.

#On Preware's home screen, type "Gov" and hit enter.
#Select "Govnah" and "Install"
#If you have not yet installed a "Kernel", on Preware's home screen, type "uber" and hit enter.
#Select "[[Application:UberKernel|UberKernel (Palm Pre/Pre+)]]" and "Install"
#Restart your phone as promted

 
=Brief Usage=
===Where To Start===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|To begin accessing the power of Govnah's control over the Linux Kernel, tap the "Profile" row at the top of the main screen.
|}
 

===Profiles===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Here is the list of stored Govnah Profiles. Profiles are a simple way for you store various settings that you wish to be applied at boot-time. You have the ability to store several different profiles for testing the best settings for '''your''' usage. Tap "Advanced Settings" at the top to access the individual settings that get stored in the profiles.
|}
 

===Advanced Settings===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|This is the list of configurable items. They are explained in more depth below. You are ''strongly'' encouraged to read about what these settings mean and do. Not all of them are beneficial to you or your battery. Most of the defaults are a happy medium between the two. The main one to change is "CPU Frequency". Tap that now.
|}
 

===CPU Frequency===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|The first time you boot your Pre/Pixi after installing Govnah and UberKernel, it will be running at 600MHz. This is where you ramp it up to 800MHz. Select "800Mhz" in the "Set Speed" section and tap "Apply Settings". Your phone will immediately be running at 800Mhz. Gesture Swipe left return to the "Advanced Settings" screen.
|}
 

===Compressed Swap (compcache)===
{| Width="61%" VAlign="top"
|valign="top"|[[image:govnahCompSwap-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|Compressed swap (compcache) is simply an amount of RAM (memory) that is reserved for compressing data loaded into RAM when the amount of RAM needed exceeds the space available. In a nut shell this provides more RAM space for application data to be loaded in RAM. The trade off is slightly reduced performance of the RAM for the data that is being compressed and uncompressed. But is faster than if the data were in a swap space on the internal storage drive (memory). To use this feature you must first set the amount of space that will be reserved and then toggle compcache enabled to on. Then click apply to make the settings active. If you desire to change the amount of space reserved once it has been active you must turn compcache enabled to off and click apply. Then change the amount of space reserved, turn compcache enabled to on, and click apply to make the new setting active.
|}
 

===Saving your Profile===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahPalm4Life-0.6.1.png|160px|frameless|left|text-top]]
|valign="top"|After leaving the step above, you will have ended up back at the "Advanced Settings" screen where the button "Save Current Profile" is at the bottom. This is where you can make your Pre/Pixi set to boot with your faster speed. Set the name you want here and tap "Save As New Profile". Gesture swipe left to return to the "Profiles" screen.
|}
 

===Profile Management===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahMegaProfiles2-0.6.1.png|160px|frameless|left|text-top]]
|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.
|}

 

=Governors In-Depth=
* Generic items (needed for 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_min_freq - 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.
** 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.
** 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.
** 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
** 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.
** sampling_rate - same as ondemand.
** sampling_rate_(min|max) - same as ondemand.
** up_threshold - same as ondemand.
** ignore_nice_load - same as ondemand.

* userspace
** scaling_setspeed - one of the values from scaling_available_frequencies
** NB - when userspace is selected LunaSysMgr will change the frequency as it feels.

* powersave
** Nothing special

* performance
** Nothing special

* screenstate
** Nothing special

=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.

===Profile List===
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
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'get-profiles',
returnid: 'app.to.relaunch'
}
}
}
);
</nowiki></pre>
You need to replace the returnid parameters value 'app.to.relaunch' with your apps id.

The object below will be sent to your app-assistants handleLaunch function. (But with real data obviously.)
<pre><nowiki>
{
type: 'govnah-profiles',
profiles:
[
{
id: 1,
name: 'Palm Default'
},
{
id: 8,
name: 'Awesome Profile!'
},
{...}
]
}
</nowiki></pre>

===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.
<pre><nowiki>
this.controller.serviceRequest
(
'palm://com.palm.applicationManager',
{
method: 'launch',
parameters:
{
id: 'org.webosinternals.govnah',
params:
{
type: 'set-profile',
profileid: 1
}
}
}
);
</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.)

=Links=
* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Sprint PRL Update

2011-04-25T14:58:50Z

Xanadu73: Initial Typing. Not complete.

'''This work is in progress and is not finished.'''

=Summary=
When you upgrade your Pre to webOS 2.1 using [http://www.webos-internals.org/wiki/WebOS_2_Upgrade the meta-doctor], Sprint users lose the ability to update their PRL ('''P'''referred '''R'''oaming '''L'''ist). This guide aids in restoring that capability. It requires that novacom be installed on a computer because the steps require shell access to the Linux command line of your Pre. This guide DOES NOT discuss illegally obtained and unreleased versions of the software required to do this "normally".

NOTE:
You absolutely '''CANNOT''' use files from another phone's /var/lib/software on your phone.
That location contains unique information for YOUR phone.
If you restore someone else's files to your phone, it will become THEIR phone and no longer YOURS.
The only way to fix this situation is to Doctor back to 1.4.5 and start over.

=Overview=
1) Back up /var/lib/software/* ''before'' upgrading to webOS 2.1 
2) Restore /var/lib/software/* ''after'' upgrading to webOS 2.1 
3) Use PmModemUpdater to update your PRL.

=Prerequisites=
You '''must''' have novacom installed and functioning on a computer. You can go about this in a couple ways:

1) Get the novacom installer [https://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 directly from Palm]. 
2) Use the [http://forums.precentral.net/canuck-coding/278224-universal-novacom-installer-uni-v1-11-a.html Universal Novacom Installer] to help do it for you.

=Procedure=
==Step 1==
While your Pre is still running webOS 1.4.5, update PRL:
1) Phone --> App-Menu --> Preferences & Accounts --> Update PRL

NOTE:
As of April 21st 2011, some people are getting PRL# 01115, and others are getting PRL# 60678.
It is unknown why at this time.
It is believed that it has something to do with the length of time the account has been open.
The 01115 has some data roaming changes in it that boost data rates for some customers in certain areas.
Unofficial changelogs can be [http://www.batonrougebroadband.info found here].

After this, check to make sure that you have "prefroamlist" on your phone:

1) Plug your Pre into your computer. DO NOT put it in USB Mode.
2) novaterm (will open a Linux shell to your phone).
3) cd /var/lib/software/ModemFiles
4) ls

You should see a file named "prefroamlist". This is your PRL file.

==Step 2==
Now back up that location to a tarball in /media/internal (the "Flash Drive" portion of your phone):

1) cd /var/lib/software
2) tar -czvf /media/internal/my_1.4.5_prl_backup.tar.gz *

You will now have a file named "my_1.4.5_prl_backup.tar.gz" in the Flash Drive portion. It's highly recommended that you put your phone in USB mode now and copy that file to your computer.

==Step 3==
After running the Doctor that you created following the [http://www.webos-internals.org/wiki/WebOS_2_Upgrade Upgrade Guide], you are ready to restore that information:

1) novaterm
2) cd /var/lib/software
3) tar -xvf /media/internal/my_1.4.5_prl_backup.tar.gz
4) Immediately reboot your phone (Orange+Sym+R is the quickest).

==Step 4==
Verify that your phone is still your phone and check your PRL version:
1) Device Info: The first page at the top shows your phone number.
2) Device Info: Tap "More Info" at the bottom: Verify PRL.

Application:SimpleBigBook

2011-04-25T11:42:42Z

Xanadu73: Added "Installing". Updated "Status".

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but has become largely abandoned at this point. I am dusting it off, fixing issues, and adding features.

 
=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). As I think of them I will continue to add features as well.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=Installing=
The official App Catalog Version can be found in the App Catalog on your device, or through [http://www.precentral.net/simple-big-book-1 this web page]. The git version (raw source) can be downloaded by using git on your computer:
git clone git://git.webos-internals.org/applications/simplebigbook.git
And installing it with Preware by building an ipk and transferring it to your device.

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-04-25T11:36:59Z

Xanadu73: /* Status */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but has become largely abandoned at this point. I am dusting it off, fixing issues, and adding features.

 
=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
The git version is receiving continual updates as things are found to be wrong (typos in the text, etc.). As I think of them I will continue to add features as well.

 

=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

How To Remove VoiceDial

2011-04-23T15:20:52Z

Xanadu73:

=== Summary ===
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

=== Background ===
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== Disable System Service ===
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

=== Complete Removal (No Way Back) ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time. There is no way to "re-install" VoiceDial with this method. The next method ''can'' make it possible to "re-install" VoiceDial.

=== Complete Removal (Reversible) ===
If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to a tarball in /media/internal/VoiceDialBackup, remove all the packages, and remove the service from boot-time:

<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

How To Remove VoiceDial

2011-04-23T15:18:52Z

Xanadu73: Separated No Way Back from Reverible removals.

=== Summary ===
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

=== Background ===
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== Disable System Service ===
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

=== Complete Removal (No Way Back) ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time. There is no way to "re-install" VoiceDial with this method. The next method ''can'' make it possible to "re-install" VoiceDial.

=== Complete Removal (Reversible) ===
If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to your /media/internal, remove all the packages, and remove the service from boot-time:
<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

How To Remove VoiceDial

2011-04-23T15:16:09Z

Xanadu73: typos

=== Summary ===
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

=== Background ===
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== Disable System Service ===
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / file system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping up and killing MediaServer.

=== Complete Removal ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time.

'''BUT'''

If you even ''THINK'' you ''may'' want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to your /media/internal, remove all the packages, and remove the service from boot-time:
<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

How To Remove VoiceDial

2011-04-23T14:11:22Z

Xanadu73: Added service disable as a quick option. Minor edits.

=== Summary ===
For those plagued by the buggy and inaccurate VoiceDial that comes with webOS 2.1 (meta-doctor or otherwise), here's how to disable/remove it as cleanly as possible.

=== Background ===
All the VoiceDial packages in webOS 2.1:

<nowiki>#</nowiki> ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== Disable System Service ===
The simplest and easiest way to stop VoiceDial from getting in your way and crashing the MediaServer (kills system sounds) is to simply disable the service from starting at boot-time. This requires NO file / fiel system alterations:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Reboot. You'll be VoiceDial free. The codecs and such will still be loading and the actual app will still be there, but it won't work anymore so you won't have it randomly popping upand killing MediaServer.

=== Complete Removal ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

<nowiki>#</nowiki> mount -oremount,rw /
<nowiki>#</nowiki> for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
<nowiki>#</nowiki> mount -oremount,ro /

Then:

<nowiki>#</nowiki> luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time.

'''BUT'''

If you even ''THINK'' you may want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to your /media/internal, remove all the packages, and remove the service from boot-time:
<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

How To Remove VoiceDial

2011-04-22T01:37:18Z

Xanadu73: typos

=== SUMMARY ===
For those plagued by the buggy and inaccurate VoiceDial that comes in the meta-doctor for webOS 2.1, here's how to remove it as cleanly as possible.

=== BACKGROUND ===
All the VoiceDial packages in webOS 2.1:

ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== REMOVAL ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

mount -oremount,rw /
for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
mount -oremount,ro /

Then:

luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time.

'''BUT'''

If you even ''THINK'' you may want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codecs to your /media/internal, remove all the packages, and remove the service from boot-time:
<nowiki>#!/bin/sh</nowiki>
VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Remember
Enjoy!

How To Remove VoiceDial

2011-04-22T01:35:13Z

Xanadu73: Created page with "=== SUMMARY === For those plagued by the buggy and inaccurate VoiceDial that comes in the meta-doctor for webOS 2.1, here's how to remove it as cleanly as possible. === BACKGROU..."

=== SUMMARY ===
For those plagued by the buggy and inaccurate VoiceDial that comes in the meta-doctor for webOS 2.1, here's how to remove it as cleanly as possible.

=== BACKGROUND ===
All the VoiceDial packages in webOS 2.1:

ipkg list_installed | grep voice

contacts.plugin.pmvoicecommand
palmvoicecodec
palmvoicedecoder
palmvoiceencoder
pmvoicecommand
pmvoicecommand-dede
pmvoicecommand-engb
pmvoicecommand-enus
pmvoicecommand-eses
pmvoicecommand-esmx
pmvoicecommand-frca
pmvoicecommand-frfr
pmvoicecommand-itit

=== REMOVAL ===
If you have absolutly NO desire to EVER re-install it, then you can simply:

mount -oremount,rw /
for PKG in $(ipkg list_installed | grep voice | awk '{print $1}') ; do ipkg remove -force-depends "$PKG" ; done
mount -oremount,ro /

Then:

luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

To remove it from the list of services to start at boot time.

'''BUT'''

If you even 'THINK' you may want to re-install it at some future time, it gets a little tricky. In the Doctor, we have IPKs for everything EXCEPT the codecs. These need to be backed up BEFORE removing the packages themselves. This handy dandy script will back up the codes to your /media/internal, remove all the packages, and remove the service from boot-time:

VCBACKUP="/media/internal/VoiceCommandBackup"

echo -e \\vMaking codec backup dir at "${VCBACKUP}"\\n
if [ ! -d "${VCBACKUP}" ] ; then mkdir "${VCBACKUP}"; fi

cd /

mount -oremount,rw /

echo -e \\vBacking up codecs\\n
tar -czvf "${VCBACKUP}"/VoiceCommandExtras.tar.gz /usr/lib/libpalmvoicecodec.so /usr/lib/gstreamer-0.10/libpalmvoicedecoder.so /usr/lib/gstreamer-0.10/libpalmvoiceencoder.so

echo -e \\vRemoving all VoiceDial packages\\n
for PKG in $(ipkg list_installed | grep voice | awk '{print $1'}) ; do ipkg remove -force-depends "$PKG" ; done

mount -oremount,ro /

echo -e \\vRemoving VoiceDial from boot-time service list\\n
luna-send -n 1 palm://com.palm.systemservice/setPreferences '{"enableVoiceCommand":false}'

Enjoy!

Application:SimpleBigBook

2011-04-18T20:56:00Z

Xanadu73:

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but has become largely abandoned at this point. I am dusting it off, fixing issues, and adding features.

 
=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
This app is not dead yet! I am in the process of giving this app a complete over-haul. I am currently proof-reading the entire text. Most other features are done.

 
=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-04-18T20:55:42Z

Xanadu73:

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.2.3 - April, 17, 2011
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but has become largely abandoned at this point. I am dusting it off, fixing issues, and adding features.

 
=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
This app is not dead yet! I am in the process of giving this app a complete over-haul. I am currently proof-reading the entire text. Most other features are done.

 
=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-04-16T14:12:55Z

Xanadu73:

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.1.0 - November 29, 2010
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but has become largely abandoned at this point. I am dusting it off, fixing issues, and adding features.

 
=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
This app is not dead yet! I am in the process of giving this app a complete over-haul. I am currently proof-reading the entire text. Most other features are done.

 
=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

WebOS 2 Upgrade

2011-04-08T01:21:36Z

Xanadu73: Added bit about turing off virus scanners on Windoze.

= Overview =
With the release of the webOS 2.1.0 doctor by HP for O2 and Vodafone Pre+ devices, there is now a legal way to get webOS 2.1 onto the legacy devices of carriers that are not onboard with the 2.x upgrade. Compatible devices include all Pre and Pre Plus devices. This is not compatible with Pixi devices.

'''You must read this page from top to bottom twice before starting this procedure. You must complete all steps from 0 to 6. Do not omit any steps. Do not improvise. Do not think you can ignore the instructions. If you do not follow these instructions precisely, completely and without error, you will not achieve your goal and you will annoy a lot of people with a lot of unnecessary questions in the process.'''

= Disclaimer =
'''This is a process that uses official HP software in unofficial ways. You should always be prepared for the unlikely possibility that your device may be completely wiped and your Palm profile may be permanently destroyed. Do not proceed unless you have made appropriate backups and are OK with that. Working knowledge of MetaDoctor and Linux systems in general is needed.'''

If you feel the need to ask whether you should do this on your primary phone, then you should not, as that indicates that you have not yet taken the required precautions and backups in case something goes wrong.

= Other Tutorials =
'''Note that this wiki page is always the authoritative source of information about this process, so you should refer to this page first for any and all instructions. Here are some other pages which you may find useful in addition to this page. They do not replace the information on this page, which you should read from top to bottom first.'''
== Tutorials that have been updated to match the latest instructions ==
* ''PreCentral'' forum user @malpha recorded a two-part [http://www.youtube.com/watch?v=CJB8NJ72kZg video overview] of the process as she followed this step-by-step. {Sprint Pre-, Ubuntu}.
== Tutorials that are out of date and should not be relied upon ==
* ''PreCentral'' forum user @djwhitey recorded a 9-minute [http://www.youtube.com/watch?v=PF2ciiNFxLc walkthrough] (includes Activation Error). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04}.
* ''PreCentral'' forum user @innocentbystander has written a start-to-finish guide to installing and building the Meta Doctor under Mac OS 10.6 for those with little or no experience with the command line. It can be found [http://forums.precentral.net/showthread.php?p=2885787 here].

= Using MetaDoctor Scripts =

== Step 0: Backup your device ==
Make sure you have copies of all the data that you want to preserve from your palm profile. There is a possibility that you will need to clear your palm profile to be successful in this upgrade, so you should act as if that is going to happen from the start.

Also, make sure you run the [[Application:SaveRestore]] application from Preware to back up your application data - you don't want to lose your Angry Birds progress, do you?

Then copy all the files from the USB drive onto your PC to keep them safe, including music, downloads, and pictures. The webOS Doctor has been known to wipe your USB drive without warning, so you should act as if that is going to happen from the start.

If your phone is set to use the Palm Profile as the default location for contacts you may want to manually export these. To check how many palm profile contacts you have: Contacts App -> Preferences & Accounts -> tap "Palm Profile" under the "accounts" subsection.
To manually export contacts see this post: [http://forums.precentral.net/webos-synergy-synchronization/215705-howto-transfer-contacts-palm-profile-gmail-yahoo-mail-easier-way-2.html#post2886607 PreCentral Forums - How To Transfer contacts]. They can be imported back onto your phone by emailing the file of exported contacts to yourself, and opening that attachment on your phone.

A guide for backing up using Save/Restore can be found [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew here].

== Step 1: Prerequisites ==
=== Disk Space ===

You should allow up to 10GB of disk space for this process.

=== MetaDoctor ===

See [[Application:MetaDoctor]] for information on how to install MetaDoctor.

Note that the procedure for the WebOS 2 Upgrade is on this page. The MetaDoctor is simply a tool which is used by this procedure. You need to complete only Step 1: Setting up Meta-Doctor on that page. When you get to the end of Step 1: Setting up Meta-Doctor on that page, you should come back to this page and continue the procedure on this page.

'''Note If you are using Cygwin on Windows 7 or Vista, it is extremely important to disable UAC. If you don't disable it you may get permission errors when building the Doctor, and even if it succesfully runs and reflashes your Pre, it won't work correctly. YOU HAVE BEEN WARNED.
http://windows.microsoft.com/en-US/windows-vista/Turn-User-Account-Control-on-or-off '''

=== Palm SDK ===

See [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website] for Windows and [http://developer.palm.com/index.php?option=com_content&view=article&id=1585 for Ubuntu].
Whilst the Palm SDK is not strictly required to complete this procedure, it is the best way to install the novacom and novaterm programs which are used to transfer files to and from your device and to access the command line on your device.

=== Novacom Drivers ===

If you are unable to get the official novacom drivers from the Palm SDK to connect to your device, you can alternately try Jason Robitaille's [http://universal-novacom-installer.googlecode.com/files/Universal%20Novacom%20Installer.jar Universal Novacom Driver Installer]

These drivers are necessary to interface with the Pre. The Installer is cross-platform and supports Windows (32bit and 64bit), Mac OS, and Ubuntu (32bit and 64bit). Note that it does not support the Pre 2 on Ubuntu. For that you'll need Linux-specific drivers, which HP makes available [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb here]for 32-bit and [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb here] for 64-bit.

== Step 2: Prepare your Palm Profile ==
With unsupported carrier/device/OS combinations, it may be necessary to clear some Palm Profile data to allow you to sign in on webOS 2.x devices. The process is as follows:
'''Warning: this will delete data from your Palm Profile, including but not limited to: calendars, contacts, account information, email signatures, bookmarks, memos, tasks, SSM/MMS messages, and icon/launcher arrangement.'''
# Open the Backup app.
# Turn off backups, confirming that you wish to erase your palm profile information.

'''This step is extremely important if you find that after finishing the webOS 2.1 installation your saved apps don't download to your device automatically and your Palm Profile account name under Accounts is "Dr. Skipped Firstuse". You should delete your profile info and Doctor again.'''

NOTE: The latest scripts (as of 5:00pm EST) MAY allow direct conversion of a 1.4.5 profile to 2.1.0 without deleting Palm Profile data. Please read the information under "Palm Profile" below to understand the issues that my arise from attempting this, as well as the required solutions to resolve those issues.

== Step 3: Run device-specific MetaDoctor script ==
The MetaDoctor scripts will automatically download the latest necessary webOS doctors, extract and replace CDMA radio firmware as necessary, and will build and launch the modified webOS Doctor.

'''Windows users''': Before proceeding ''ANY'' further, disable, turn off, unload, shutdown, kill, uninstall if you have to, your virus scanner. Virus scanners lock the files as they are reading them which causes corruption of The Doctor's file(s) which leads to failed installs.

'''A NOTE ON "RE-DOCTORING":''' If this is not your first time through this process, you should do a "git pull" and a "make clobber" to ensure you have the latest scripts and a pristine build folder. From the command line (I use Cygwin), type "cd meta-doctor" without the quotes and press enter. Then type "git pull" without the quotes and press enter. Then type "make clobber" without the quotes and press enter. Voila! You now have the latest scripts and a clean folder to build your doctor in.

'''From the meta-doctor directory''', run the meta-script that corresponds to your device (note that the strings enclosed by < and > in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version>
</nowiki></pre>

You should replace <carrier>, <device>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

A list of all the scripts can be found by typing
<pre><nowiki>
ls ./scripts/
</nowiki></pre>

'''For those who for what ever reason will never be using their phone on a cellular network and wish to use the phone only on wifi, just add "--wifi-only" as an extra argument to the meta-script:'''
<pre><nowiki>
./scripts/meta-<carrier>-<device>-<version> --wifi-only
</nowiki></pre>

Again, you should replace <device>, <carrier>, and <version> with the specific values that match your particular situation, using the detailed information given in the section below that matches your particular device and carrier.

Then, when your device boots after step 4, all you need to do is configure and start wifi and then run the Gesture Tutorial and you should be good to go. Note that in this case the end of the palm profile login procedure will appear to cycle forever, so just manually reboot the device using Opt-Sym-R when that happens.

Specific additional information for each of the supported device and carrier combinations can be found below:

=== AT&T Pre+ ===
<pre><nowiki>
./scripts/meta-att-preplus-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== BellMo Pre ===
<pre><nowiki>
./scripts/meta-bellmo-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

=== O2 Pre ===
<pre><nowiki>
./scripts/meta-o2-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== O2 Pre+ ===
<pre><nowiki>
./scripts/meta-o2-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint Pre ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

=== Sprint FrankenPre 2 ===
'''Be aware that there is no publicly available solution for Sprint Navigation or Sprint PRL Update for this procedure. If you depend on either of those things, you should not upgrade to webOS 2.x'''

NOTE: Tokens are no longer needed to create a Sprint FrankenPre 2. You only need to run the script below. However, it is still a good idea to capture and store the tokens from each phone for potential future use.

<pre><nowiki>
./scripts/meta-sprint-franken-unlocked-pre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

=== Telcel Pre ===
<pre><nowiki>
./scripts/meta-telcel-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.00 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

'''In Fact, it seems Palm has already locked out all the Telcel activated devices, so, even if you managed to hack your Meta Doctor to have a 1.4.5 profile and see the paid apps in the Catalog, you won't be able to insert your credit card data and won't be able to buy apps anymore.'''

=== Verizon Pre+ ===
<pre><nowiki>
./scripts/meta-verizon-preplus-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

=== Verizon FrankenPre 2 ===
<pre><nowiki>
./scripts/meta-verizon-franken-unlocked-pre2-2.1.0
</nowiki></pre>

You will end up with version 2.1.0 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).

In order to update your PRL, you will need to manually program your phone OTA by dialing *228 from the dialer, and choose the "Program your phone" option.

The "Voice Dial" app may not work. Please see the Voice Dialing section below to remedy this.

=== WR Pre ===

For WR devices, you should attempt to use the O2 script above first, and if you end up with a 9.9.9 version in your palm profile, then use this WR script instead.

<pre><nowiki>
./scripts/meta-wr-pre-2.1.0
</nowiki></pre>

You will end up with version 1.40.50 listed in your palm profile, and version 2.1.0 listed in the Device Info application.

You will not be able to purchase apps that require a minimum webOS 2.x version.

== Step 4: Run the modified webOS Doctor ==
The meta-script will automatically launch the modified webOS Doctor for you. However, if you need to move it to a different location and run it manually, the modified doctor will be a '''.jar''' file located in the build output directory:
<pre><nowiki>meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueu-wr-2.1.0.jar</nowiki></pre>

Note that the directory path will change from that example based on which script you ran, and the script will tell you the exact pathname shortly after it starts running.

Do not USB connect the phone until WebOS Doctor specifically says to.

NOTE: There have been reports that, for some users, the modified webOS doctor fails to recognize the USB connection. Similarly, up-graders have also noted that in some instances their Pre will "disconnect" from the webOS Doctor (while running) and re-boot into v.1.4.5. It has been observed that Doctoring, while putting ones Pre through the "Recovery" Reboot (as detailed [http://www.webos-internals.org/wiki/How_To_Recover here]) may mitigate these issues, and allow the Doctor to continue. There is also an instance where after pressing the "next" button to start the Doctor, the phone appeared to need charging before the Doctor would start( on a 95% full battery), and then stalled at 0%. Putting the phone into emergency recovery mode appeared to solve this problem.

Note: Sprint users please read the PRL section '''before''' running The Doctor: [http://www.webos-internals.org/wiki/WebOS_2_Upgrade#Sprint_2 "5.9.1 Sprint"].

== Step 5: There is no Step 5 ==

There used to be a complex set of additional steps required here. Too many people had trouble following them, so we automated it. You should proceed directly to Step 6.

== Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app ==
If this worked for you, we would appreciate a donation at http://donate.webos-internals.org - and if you want to thank Rod Whitby personally for the many hours that he put into creating the Meta-Doctor and this upgrade procedure, you should purchase the [http://developer.palm.com/appredirect/?packageid=org.preware.docs Preware Homebrew Documentation] app from the official app catalog, and leave a nice 5 star review containing your message of thanks.

= Caveats =

== OTA Updates ==
It is extremely unlikely that any Pre or Pre+ device will ever get another OTA update. If you preform this procedure on those devices, you should not expect OTA updates.

Performing this procedure on a Pre 2 device may allow it to receive OTA updates, but there is no guarantee.

== App Catalog ==
If your palm profile record says version 1.40.50, you will not be able to purchase apps that are marked as only compatible with webOS versions 2.x and above. This cannot be changed for these devices at this time. If your palm profile record says version 2.1.0, then you should be able to purchase all apps (depending upon your geographical restrictions and country of first activation).

=== Masquerading ===
Palm's servers only accept certain device/OS combinations as valid. While some combinations of carrier and devices running 2.1 are accepted, others have to report to the palm profile server that they are running webOS 1.4.5. This is done automatically, and cannot be changed for these devices at this time.

== Carrier-Specific Applications ==
Some carrier apps are not working in webOS 2.1. Apps that have been tested and are known to install cleanly and work will be added to the custom webOS Doctor for the appropriate device/carrier.

Known working carrier apps are listed below.

=== Sprint ===
* Sprint Portal
* Sprint TV
* Sprint Football Live
* NASCAR

===Verizon Wireless ===
* All Verizon apps should be working at this time. However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!

=== AT&T ===
* No testing or reports of AT&T Carrier Apps

== Patches ==
Not all patches have been ported over yet. If you want to check for a certain patch, please see webOS Internals' [http://patches.webos-internals.org/?do=browse&webosver=2.1.0&category=all webOS-Patches Web Portal].

== Adobe Flash ==
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.

=== Adding Flash Support ===
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser. Or you can do it manually. See ([http://www.webos-internals.org/wiki/Adding_flash_support here]) for more detail.

== Performance ==
* '''OVERCLOCKING IS NOW SUPPORTED'''. Palm has just released the source code for the kernel used in webOS 2.1.0. An experimental version of UberKernel has already appeared in the experimental feeds, but casual users should wait for a stable one.
* The Pre Plus has 512 MB of memory and thus runs 2.1 quite well, but this is not the case with the original Pre since it has only 256 MB. Luckily, Palm adopted WebOS Internals's configuration of the standard Linux compcache technology that was ported to the custom kernels, and it comes active, but with only 10 MB. One potential way to enhance performance in original Pre devices is to make the compcache bigger.

=== Increase compcache size, Temporary Method ===
You can use the Govnah application to increase the size of the compcache. Disable compcache, change the size, and then reenable.

=== Increase compcache size, Permanent Method ===
You have to edit the file /etc/event.d/compcache and change the value from 10240 to 32768.

For example, you could follow these steps:

#Make sure '''novacomd''' is running on your computer.
#Use a terminal (as described on the Wiki page [http://www.webos-internals.org/wiki/Portal:Accessing_Linux Accessing Linux on the Pre... ]) to run '''novaterm''' and access your phone. Type in the following: <pre>/usr/sbin/rootfs_open -t</pre><pre>vi /etc/event.d/compcache</pre>
#vi is a bit different so, for those not familiar with how it works, the fastest way to navigate and make the required edit is in parentheses below:
##Go down to line 10 (Type <tt>10</tt> then hit <tt>Shift+G</tt>)
##Move to the first <tt>1</tt> (Type <tt>4w</tt>)
##Enter replace mode (<tt>Shift+R</tt>) and type <tt>32768</tt>
##Exit back to command mode (Press <tt>Esc</tt> or <tt>Ctrl+C</tt>)
##Save and Quit (Type <tt>:wq</tt>)
#Reboot your Pre and verify it's working by using Govnah. While you are still in novaterm, you can type the following to reboot:<pre>/sbin/reboot</pre>

== Palm Profile ==
* Some people have had problems signing in to existing Palm Profiles on 2.1 due to backup data. To make sure that you can sign in to your profile on 2.1, you should disable backups before doctoring to 2.1 and delete server side backups. Of course, this deletes most of the data in your Palm Profile (memos, tasks, calender entries, accounts, ...). Your apps will be restored on 2.1, but that is about it. Note that not all people have issues with backups. If you would rather not delete your Palm Profile data, you can try doctoring to 2.1 without turning backups off and see if restoring everything works. If it doesn't, you'll have to doctor back to 1.4.5 to turn off backups or use a new Palm Profile, though.

* If you get 9.9.9 in palm.com/palmprofile, then you can doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it.

* If you get "Dr. Skipped Firstuse" as the name of your palm profile in the new accounts app in 2.1.0 and/or if the gesture application creates a blank screen, you have a false profile problem. You need to doctor back to 1.4.5 for your carrier and login in, then delete backup info in backup app and then 2.1.0 metadoctor it. To avoid this problem, redownload the latest version of the metadoctor and run the appropiate script with the <tt>--wifi-only</tt> switch. Note: Only use <tt>--wifi-only</tt> if you do not intend to have cellular service on the device as this option disables the modem update and renders cellular service inoperable without re-doctoring.

* Alternative fix for above problem: If your profile works fine but the Impostah app and the Accounts app show your profile name as "Dr. Skipped First Use" although your phone ran the first use app after doctoring, erase your backup data from the backup app by turning off backups and choose Erase Apps and Data from the reset options in the Device Info app.

*If you get stuck at the "Auto Locate" selection screen during the login process, you can re-doctor using the same 2.1 doctor file and it will go through. It appears to be an issue when creating a new profile in 2.1 rather than "porting" your 1.4.5 profile to 2.1. After the second doctoring, you will "Sign In" to an existing profile (the one you created during the first profile login after doctoring), rather than creating a new profile.

==GPS==
Step-by-step approach for those experiencing problems with GPS following upgrade.
# To enable GPS functionality go to the "Location Services" application (click "Turn On" if GPS has been completely disabled). From there go to the "Preferences" menu in the top left hand corner and select the "Locate Me Using..." sub-menu item. Ensure that both "GPS" and "Google Services" are enabled (you may be prompted to accept the Terms of Service). Close the "Location Services" application.
# Next you need to bring up the "GPS Information" application; to do this dial ##477# (or #*477# on GSM/UMTS Pres) in the phone application (the "477" corresponds to the letter keys "GPS").
# Click the "Get Fix" button. You may receive a "GPS Error - Position Unavailable" message which you can close. Keep pressing "Get Fix" until a fix is established (it may take several attempts). You will know a fix has been established when some statistics (Latitude, Longitude etc) are displayed.
# Once a fix has been established, GPS should continue to function normally thereafter.

==Voice Dialing==
For the Sprint-Franken-Pre2 (Pre2-GSM-Unlocked confirmed + sprint-pre(-)comm) and perhaps the Verizon-Franken-Pre2, the voice dialing application may not work after the metadoctor procedure above. The application may or may not even launch after tapped. You may experience problems with sound intermittently not working, esp. when playing media, or using the phone. This will be corrected automatically with a webOS OTA Update to 2.1.0. When the phone prompts for the update, install it.

To speed up the process, go to the "System Updates" app on your phone. The WebOS 2.1 update should appear after it searches for updates. (The update for a Sprint FrankenPre2 is ~7MB and only took a few minutes to install).

==PRL==
=== Sprint ===
After applying 2.1.0 to a Sprint device using this method, there is currently no known way to update the PRL. There are permissions issues, and the conventional "Update Profile" and "Update PRL" from the Phone options will no longer work. The provisioner service binary from the Sprint 1.4.5 doctor does not work on webOS 2.x, so a version of that service for 2.x is required for this to ever work. It is not expected that this situation will change before Sprint releases another webOS phone running webOS 2.0 or above.

:* It is possible to preserve a backup of the current PRL (60677 as of 03/27/11) and "push" it back onto a doctored-to-2.1.0 phone with the following procedure:
::* Before doctoring to 2.1
::# Update your PRL and Network settings
::# Connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6):
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# tar -czvf /media/internal/prl.tar.gz /var/lib/software
root@YourPre:/# exit
</pre>

::* After doctoring to 2.1 and all basic setup/configuration is done
::# Again, connect your phone to your computer via a USB cable
::# Do the following (example was done in Terminal on OS X 10.6): 
<pre>
[dario@guarneri ~]$ novaterm
root@YourPre:/# rootfs_open -t
root@YourPre:/# cd /
root@YourPre:/# tar -zxvf /media/internal/prl.tar.gz
root@YourPre:/# exit
</pre>
::* Now reboot your phone to ensure the new PRL takes effect and to "close" (make read-only) your root filesystem.

=== Verizon ===
In order to update your PRL, you will need to manually program your phone OTA by dialing '''*228''' from the dialer, and choose the "Program your phone" option.

Application:SimpleBigBook

2011-03-25T01:12:54Z

Xanadu73: Add links

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.1.0 (OLD!)
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=
[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from [http://www.precentral.net/simple-bible Simple Bible]. It was re-worked into Simple Big Book by Rick B and John K, but has become largely abandoned at this point. I am dusting it off, fixing issues, and adding features.

 
=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!).
*Remembers the exact location in the book you were when you close it for easy resuming.
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
This app is not dead yet! I am in the process of giving this app a complete over-haul. I am currently proof-reading the entire text. Most other features are done.

 
=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*FIXED: On orientation change, the page scrolls wildly.

*The larger chapters take a short pause to load. There's a way with AJAX to load a single DIV, ''then'' load the rest of the surrounding text. This is (seemingly) easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=License=
The original code as written by the [http://www.precentral.net/simple-bible Simple Bible] folks and was/is licensed under the [http://www.gnu.org/licenses/ GPL]. Simple Big Book is listed as [http://www.gnu.org/licenses/gpl.html GLPv3]. I need to check with the [http://www.precentral.net/simple-bible Simple Bible] people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the [http://en.wikipedia.org/wiki/Public_domain public domain]. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. [http://aa.org/lang/en/subpage.cfm?page=94 AA has not given permission] for the distribution of those stories in this form at this time.

Application:SimpleBigBook

2011-03-22T12:05:16Z

Xanadu73: /* Remaining Known Issues */

[[Category:Application]]

{{application
|name=Simple Big Book
|type=webOS
|version=Version: 1.1.0 (OLD!)
|tag=Self-Help
|screenshot=Simplebigbook.png
|description=GPLv3
}}

 
=Summary=

[[image:Bookicon.png|frameless|left]]
Simple Big Book is an application which presents you with the first edition of the A.A. Big Book originally printed in 1939. The code for this app was originally from Simple Bible. It was re-worked into Simple Big Book by Rick B and John K, but has become largely abandoned at this point. I am dusting it off, fixing issues, and adding features.

 
=Key Features=
*Complete main text of the A.A. Big Book (1st Edition), including some appendices.
*Remembers the exact location in the book you were when you close it for easy resuming.
*Exhibition mode that cycles though sentences from the entire text (speed configurable in main app).
*For webOS1.*, Exhibition is accessible in the app menu ("Quote Generator") so you can still experience it.
*Full screen mode. Double-tap the screen to active/deactivate. There's a preference for the app starting full screen, too.
*Day/Night mode (palm-light & palm-dark) for easy reading in darker situations. (Thank you yet again, Jev!)
*Search function that acts on the entire book in a configurable any/all/phrase fashion.
*Text laid out in the fashion of the 4th edition (as best as possible).
*Several external support and help links.

 

=Status=
This app is not dead yet! I am in the process of giving this app a complete over-haul. I am currently proof-reading the entire text. Most other features are done.

 
=Remaining Known Issues=
While I've fixed a lot of the usage hindering issues, a couple still remain that I will fix once the basic framework of the app is solid, which is not far away.

*FIXED: On orientation change, the page scrolls wildly.

*The larger chapters take a short pause to load. There's an AJAX load function that will load a single DIV, ''then'' load the rest of the surrounding text. This is easy to do, but it'll throw off the search function and things like that requiring a good bit of re-write. I need it to WORK first...

 

=License=
The original code as written by the Simple Bible folks and was/is licensed under the GPL. Simple Big Book is listed as GLPv3. I need to check with the Simple Bible people and see if that's accurate.

 

=Notes=
The first edition of Alcoholics Anonymous is in the public domain. This version contains the foreword, the Doctor's Opinion, the front sections, and Dr. Bob's story from the first edition. The page numbers in this version correspond to those in the third and fourth editions. The stories in the back of the third and fourth editions of Alcoholics Anonymous are copyright by the AA World Services Inc and by The AA Grapevine, Inc. AA has not given permission for the distribution of those stories in this form at this time.