Since we cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license), then we need to manage our modifications as patches.

Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied afterwards, we need a procedure and tools for doing this.

This page documents such a procedure.

= Setup procedure=

* Log into your Pre, and gain root privileges.

<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode

<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt packages, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:

<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:

<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Clone the webos-internals modifications repository:

<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

= Importing and applying patches=

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>

* If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

* Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.

<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:

<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch

<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

= Removing all patches=

Before you accept an OTA update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

= Reapplying all patches=

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

* Put your Pre back in to Read Only mode

<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

= **Information for developing patches**=

== Getting Authenticated with gitorious.org==
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next you'll need to generate a public key and share that with gitorious.org, your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.

Getting your key on windows
* Download [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

* To commit changes to gitorious.org from the pre you will need to install openssh on the device.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # since dropbear doesn't do agent forwarding, you need to use openssh
</nowiki></pre>

As an alternative, if you don't use the keys for anything else you could just generate them on the pre after installing open-ssh
<pre><nowiki>
sudo ssh-keygen -t rsa # follow the prompts
cat ~/.ssh/id_rsa.pub # display the public key you need to paste into gitorious
</nowiki></pre>

* Don't forget to upload your public key to gitorious.org after generating it.
Now you should be able to follow the steps below and contribute your code to gitorious.org.

* If you find yourself getting errors about your public key when you try to push changes, check to make sure your keys are under /var/home/root/.ssh/ and not under your regular user account.

== Creating a patch==

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

== Pushing the change back to gitorious.org==

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>

* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

= Extended, annotated sample session with quilt=
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create **before** you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

= Background info=

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

= Script for Updating/Installing Patches=

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>

Applying Patches

2009-07-24T05:34:30Z

SirWill: /* Setup procedure */

Since we cannot legally redistribute Palm source code (it is copyrighted code, and is not released under an open source license), then we need to manage our modifications as patches.

Since these patches will come from many different places, and will need to be removed before each OTA update and then reapplied afterwards, we need a procedure and tools for doing this.

This page documents such a procedure.

= Setup procedure=

* Log into your Pre, and gain root privileges.

<pre><nowiki>
sudo -i # Yes, the -i is important.
</nowiki></pre>

* Put your Pre in to Read Write Mode

<pre><nowiki>
mount -o remount,rw /
</nowiki></pre>

* Ensure that you are set up for optware package installations, and make sure you have the latest package index:
<pre><nowiki>
ipkg-opt update
</nowiki></pre>

* Install the 'quilt packages, which will be used to manage the patches you apply, and the 'git' package, which will be used to download existing patches from the modifications repository:
<pre><nowiki>
ipkg-opt install quilt git
</nowiki></pre>

(If you already have those packages installed, repeating this step will not cause any harm.)

* Create a directory in which 'quilt' will manage your chosen modifications:

<pre><nowiki>
mkdir -p /opt/src/patches
</nowiki></pre>

* Edit /opt/etc/quilt.quiltrc to point quilt to that directory:

<pre><nowiki>
sed -ire 's|^[\s#]*QUILT_PATCHES=.*|QUILT_PATCHES=/opt/src/patches|' /opt/etc/quilt.quiltrc
</nowiki></pre>

* Clone the webos-internals modifications repository:

<pre><nowiki>
cd /opt/src
git clone git://gitorious.org/webos-internals/modifications.git
</nowiki></pre>

= Importing and applying patches=

* Ensure your list of modifications is up to date
<pre><nowiki>
cd /opt/src/modifications
git pull
</nowiki></pre>

* If you find yourself getting errors when you try to pull with the above command then you will need to modify your .git/config file
<pre><nowiki>
sudo vi /opt/src/modifications/.git/config
</nowiki></pre>

* Your [master] section should look like the following
<pre><nowiki>
[branch "master"]
remote = origin
merge = refs/heads/master
</nowiki></pre>

* Browse the set of available patches. Each patch should have a description at the top.

<pre><nowiki>
find /opt/src/modifications -name *.patch
</nowiki></pre>

* Choose a patch from the modifications repository and import it into your own patches directory:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt import /opt/src/modifications/application_name/patch_name.patch # Note that you need to replace application_name and patch_name here.
</nowiki></pre>

* Verify that quilt has imported the patch successfully:

<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt series # you should see your patch listed in here
</nowiki></pre>

* Instruct quilt to apply your patch

<pre><nowiki>
# You should still be in the / directory to run quilt.
quilt push
</nowiki></pre>

* If everything worked correctly, the patch should now be applied. You will usually need to restart the luna service on the Pre to see the effect of patches to applications. Here's how to initiate a rescan.
<pre><nowiki>
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</nowiki></pre>

If that doesn't work, try a service restart with:
<pre><nowiki>
stop LunaSysMgr && start LunaSysMgr
</nowiki></pre>

And if all else fails, simply reboot:
<pre><nowiki>
reboot
</nowiki></pre>

= Removing all patches=

Before you accept an OTA update, you should remove any patches you have applied. Luckily, using quilt makes this very easy.

* Remove all patches:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt pop -a
</nowiki></pre>

= Reapplying all patches=

After your OTA update is complete, you will want to reapply any patches you have selected. This may or may not go smoothly.

* Apply all patches:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt push -a
</nowiki></pre>

= **Information for developing patches**=

== Getting Authenticated with gitorious.org==
Before you can commit to gitorious you need to [http://gitorious.org/users/new create an account].

Next you'll need to generate a public key and share that with gitorious.org, your public key is how gitorious.org authenticates you and checks if have the permissions required to do a commit to a given repository.

Getting your key on windows
* Download [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] and [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant]

--Gitorious.org [http://gitorious.org/about/faq gitorious.org recommends] you use [http://code.google.com/p/msysgit/ msysGit].--

* On Windows use [*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTYgen] to generate a public/private key pair.

<pre><nowiki>
Key -> SSH-2 RSA KEY
Key -> Generate key pair
</nowiki></pre>
After some wiggling of the mouse your keys will be generated. You should fill in the //Key passphrase// and it's confirmation to secure you key. Save off the public and private key pairs to your user folder.

* After which you will need to run [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Pageant] on your pc. Pageant holds your private key in memory for PuTTY to use.

* To commit changes to gitorious.org from the pre you will need to install openssh on the device.
<pre><nowiki>
ipkg-opt update
ipkg-opt install openssh # since dropbear doesn't do agent forwarding, you need to use openssh
</nowiki></pre>

As an alternative, if you don't use the keys for anything else you could just generate them on the pre after installing open-ssh
<pre><nowiki>
sudo ssh-keygen -t rsa # follow the prompts
cat ~/.ssh/id_rsa.pub # display the public key you need to paste into gitorious
</nowiki></pre>

* Don't forget to upload your public key to gitorious.org after generating it.
Now you should be able to follow the steps below and contribute your code to gitorious.org.

* If you find yourself getting errors about your public key when you try to push changes, check to make sure your keys are under /var/home/root/.ssh/ and not under your regular user account.

== Creating a patch==

* Before making any changes to files:

<pre><nowiki>
cd / # It is *very* important to be in the / directory when you run quilt.
quilt new patch_name.patch
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod-assistant.js
quilt add /usr/palm/applications/com.palm.app.appYouWantToMod/app/controllers/mod2-assistant.js
</nowiki></pre>

* Now you can make changes on the Pre using vi/nano/joe/whatever, or sftp files to your machine and make changes. Make sure any file you change has been added in the above step.

<pre><nowiki>
quilt files # view files that are being tracked
quilt header -e # add a header to the patch to describe it (please do this!)
</nowiki></pre>

* Once you are finished and ready to create a patch

<pre><nowiki>
quilt refresh # this will create/update the /opt/src/patches/patch_name.patch file
</nowiki></pre>

== Pushing the change back to gitorious.org==

* copy the patch into the modification tree you cloned above

<pre><nowiki>
mkdir /opt/src/modifications/application_name # You need to change application_name to the leaf of the palm application id.
cp /opt/src/patches/patch_name.patch /opt/src/modifications/application_name/patch_name.patch
</nowiki></pre>

* Identify yourself in git (use the user you have setup at gitorious.org)

<pre><nowiki>
cd /opt/src/modifications
git config --global user.name "user"
git config --global user.email "youremail@example.com"
</nowiki></pre>

* Commit your changes to your local git

<pre><nowiki>
git add application_name/patch_name.patch
git commit
</nowiki></pre>

* Since we did a clone the first time, we need to recreate the origin:

<pre><nowiki>
git remote rm origin # (if you did a clone, we have to replace the origin)
git remote add origin git@gitorious.org:webos-internals/modifications.git
</nowiki></pre>

* Finally, push your changes up to gitorious.org

<pre><nowiki>
git push origin master # first time
git push # any future pushes
</nowiki></pre>

* If the push does not work, try to debug the ssh connection
<pre><nowiki>
/opt/bin/ssh -v git@gitorious.org
</nowiki></pre>

= Extended, annotated sample session with quilt=
* First, we just need to setup a file to muck with
<pre><nowiki>
root@castle:/# cd /
root@castle:/# echo "Original file" > /usr/test
root@castle:/# echo "2nd lien" >> /usr/test
root@castle:/# echo "3rd ilne" >> /usr/test
root@castle:/# echo "last line" >> /usr/test
</nowiki></pre>
* Start a new patch (normally you'll want to use patch_name.patch, I just wanted a shortened name)
<pre><nowiki>
root@castle:/# quilt new p1
Patch /opt/src/patches/p1 is now on top
</nowiki></pre>
* You must quilt add any files that you are going to edit or create **before** you edit or create them.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p1
</nowiki></pre>
* Just using sed to correct the spelling on the 2nd line
<pre><nowiki>
root@castle:/# sed -i -e 's/lien/line/' /usr/test
</nowiki></pre>
* quilt refresh actually finds what you have changed and writes it to the patch file (at this point, you can use git to push your changes)
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p1
</nowiki></pre>
* Just for fun, let's do it again
<pre><nowiki>
root@castle:/# quilt new p2
Patch /opt/src/patches/p2 is now on top
</nowiki></pre>
* Again, add file, make some changes, refresh to update the patch.
<pre><nowiki>
root@castle:/# quilt add /usr/test
File /usr/test added to patch /opt/src/patches/p2
root@castle:/# sed -i -e 's/ilne/line/' /usr/test
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
</nowiki></pre>
* Just an example of rolling back changes
<pre><nowiki>
root@castle:/# quilt pop
Removing patch /opt/src/patches/p2
Restoring usr/test

Now at patch /opt/src/patches/p1
root@castle:/# quilt pop
Removing patch /opt/src/patches/p1
Restoring usr/test

Now at patch /opt/src/patches/enable-browser-downloads.patch
root@castle:/# cat /usr/test
Original file
2nd lien
3rd ilne
last line
</nowiki></pre>
* delete will delete the patch from your series, but leave the actual patch file in /opt/src/patches (so you could import it later)
<pre><nowiki>
root@castle:/# quilt delete p1
Removed patch /opt/src/patches/p1
</nowiki></pre>
* Since we removed p1, push will now apply p2. However, since p2 was applied against p1 originally, p2 will report an error. If the changes are too significant, you can force with -f, but you should carefully inspect the resulting files.
<pre><nowiki>
root@castle:/# quilt push
Applying patch /opt/src/patches/p2
patching file usr/test
Hunk #1 succeeded at 1 with fuzz 2.

Now at patch /opt/src/patches/p2
</nowiki></pre>
* If we want, we can refresh the patch so that future users of the patch do not receive the "fuzz" warning.
<pre><nowiki>
root@castle:/# quilt refresh
Refreshed patch /opt/src/patches/p2
root@castle:/# cat /usr/test
Original file
2nd lien
3rd line
last line
</nowiki></pre>
* cleanup
<pre><nowiki>
root@castle:/# rm /usr/test
</nowiki></pre>

= Background info=

* [http://pkg-perl.alioth.debian.org/howto/quilt.html quilt]

= Script for Updating/Installing Patches=

I just wanted to share the following script that I just finished testing out. It's only been tested on my Pre so far, as I don't have access to any others.. It just updates the patch list, prints out available patches, then lets you choose which to apply.

<pre><nowiki>
cd /opt/src/modifications
tput clear
echo Updating list...
git pull
tput clear
cd /

a=0
for inputline in $(find /opt/src/modifications -name *.patch | sort)
do
a=$(($a+1));
line="$(echo $inputline)"
MYARRAY[$a]="$line"
echo "${a}${line}" | awk -F "/" 'sub(".patch","",$6) {printf "%-3s %-15s %s\n", $1, $5, $6}'
done
echo "q quit"

x=$(($a+1));
until [ -n "$opt" ] ; do
read -p "Enter the line number for patch to apply [1 - $a] " opt
if [ "$opt" = "q" ] ; then
exit 0
fi
if [ "$opt" -lt "$x" 2> /dev/null ] && [ "$opt" -gt 0 2> /dev/null ] ; then
true
else
opt=""
fi
done

tput clear
cd /
quilt import ${MYARRAY[$opt]}
quilt push
luna-send -n 1 palm://com.palm.applicationManager/rescan {}

</nowiki></pre>