{{template:patch}}
When the Pre is booting or shutting down, the screen fades between two images - ''/palm-logo.png'' and ''/palm-logo-bright.png'' located in ''/usr/palm/sysmgr/images''. By replacing either or both of these images, the boot logo can be customized. This requires [[Portal:Accessing_Linux | access to the Pre's OS]] if you follow the method outlined below "Replacing the Files". However, boot logos can now be installed via Quick Install...read the next paragraph to find out how.

The easiest way to install a boot theme onto your phone is to use WebOS Quick Install, which can be found at http://forums.precentral.net/homebrew-apps/206905-webos-quick-install-v2-7-beyond.html. You can download any set of boot logos, and then install them with Quick Install via the Change Boot Logo tweak. Alternatively, if you use the website PreThemer, you can download the IPKG files and install them directly through Quick Install. To do this, simply download the IPK file from the website to wherever you want on your computer, and then drag it into the main field of Quick Install and hit Install. If you had a boot log installed previous to webOS 1.2 (or 1.2.1), it is recommended that you uninstall the old ones first with Quick Install if you want to install via that program. To do this, go to Tools > Device Management and then look over your installed applications. You should see the name of your installed boot logo on that list. You can uninstall it by checking its box and then clicking uninstall.

Works with: 1.0.3, 1.1

== Replacing the Files==

NOTE: In webOS 2.x, the boot images are named '''hp'''-logo.png and '''hp'''-logo-bright.png.

'''Step One'''
Log into the phone via ssh and copy the files to the USB drive.
<pre><nowiki>
#/if your login account does not have root permission, you must sudo the commands...the following assumes you do not have root permission
#/if you do not use sudo and do not have root permission, you will get Permission Denied errors...
sudo mkdir /media/internal/bootlogo
sudo cp /usr/palm/sysmgr/images/palm-logo* /media/internal/bootlogo
</nowiki></pre>

'''Step Two'''
Modify the files with your favorite editor (Gimp, Photoshop, ImageMagick, MS Paint, etc.)

'''Step Three'''
Save the new images to the ''bootlogo'' directory on the Pre's USB drive.

'''Step Four'''
Log into the phone via ssh, remount the root filesystem read-write, backup the existing files, copy the new images into place, and remount the root filesystem read-only.
<pre><nowiki>
sudo mount -o rw,remount /
sudo cp -ip /usr/palm/sysmgr/images/palm-logo.png /usr/palm/sysmgr/images/palm-logo.png.orig
sudo cp -ip /usr/palm/sysmgr/images/palm-logo-bright.png /usr/palm/sysmgr/images/palm-logo-bright.png.orig
sudo cp /media/internal/bootlogo/palm-logo.png /usr/palm/sysmgr/images/palm-logo.png
sudo cp /media/internal/bootlogo/palm-logo-bright.png /usr/palm/sysmgr/images/palm-logo-bright.png
sudo mount -o ro,remount /
</nowiki></pre>

'''Step Five'''
Restart Luna and watch your awesome new logo.
<pre><nowiki>
pkill LunaSysMgr
</nowiki></pre>

== Taking it to the Next Step==

With a small bit of scripting, we can have separate boot and shutdown themes. The first thing to do is to create regular and "bright" images for booting and shutting down. Save the new images to the ''bootlogo'' directory on the Pre's USB drive. (Steps 1-3 above).

'''Step One'''
Log into the phone via ssh, remount the root filesystem read-write, and create a directory in /opt to store the new images. We're using /opt, as the script we'll modify later will copy files, and /usr is mounted read-only.
<pre><nowiki>
sudo mount -o rw,remount /
sudo mkdir -p /opt/share/bootimages
</nowiki></pre>

'''Step Two'''
Copy the new images to /opt/share/bootimages, naming them palm-logo-up.png, palm-logo-up-bright.png, palm-logo-down.png and palm-logo-down-bright.png. Additionally, copy the shutdown files to palm-logo.png and palm-logo-bright.png.
<pre><nowiki>
cd /opt/share/bootimages/
sudo cp /media/internal/bootlogo/<boot image> palm-logo-up.png
sudo cp /media/internal/bootlogo/<bright boot image> palm-logo-up-bright.png
sudo cp /media/internal/bootlogo/<shutdown image> palm-logo-down.png
sudo cp /media/internal/bootlogo/<bright shutdown image> palm-logo-down-bright.png
sudo cp palm-logo-down.png palm-logo.png
sudo cp palm-logo-down-bright.png palm-logo-bright.png
</nowiki></pre>

'''Step Three'''
Backup the current logo images, if you haven't already.
<pre><nowiki>
sudo cp -ip /usr/palm/sysmgr/images/palm-logo.png /usr/palm/sysmgr/images/palm-logo.png.orig
sudo cp -ip /usr/palm/sysmgr/images/palm-logo-bright.png /usr/palm/sysmgr/images/palm-logo-bright.png.orig
</nowiki></pre>

'''Step Four'''
Delete the current logo images and replace them with symlinks to the files in our new directory in /opt
<pre><nowiki>
cd /usr/palm/sysmgr/images/
sudo rm palm-logo-bright.png
sudo rm palm-logo.png
sudo ln -s ../../../../../opt/share/bootimages/palm-logo-bright.png palm-logo-bright.png
sudo ln -s ../../../../../opt/share/bootimages/palm-logo.png palm-logo.png
</nowiki></pre>

'''Step Five'''
Back up and edit /etc/init.d/start_animation, adding the switching of the files
<pre><nowiki>
sudo cp -ip /etc/init.d/start_animation /etc/init.d/start_animation.orig
sudo -e /etc/init.d/start_animation
</nowiki></pre>
Before the line starting with ''if [ -x /usr/bin/luna-send'' add the following:
<pre><nowiki>
ok=no
if [ -f /opt/share/bootimages/palm-logo-up.png ] && \
[ -f /opt/share/bootimages/palm-logo-up-bright.png ] && \
[ -f /opt/share/bootimages/palm-logo-down.png ] && \
[ -f /opt/share/bootimages/palm-logo-down-bright.png ] ; then
cp /opt/share/bootimages/palm-logo-down.png /opt/share/bootimages/palm-logo.png
cp /opt/share/bootimages/palm-logo-down-bright.png /opt/share/bootimages/palm-logo-bright.png
ok=yes
fi
</nowiki></pre>
At the very end of the file, add the following:
<pre><nowiki>
if [ "$ok" = "yes" ] ; then
sleep 5
cp /opt/share/bootimages/palm-logo-up.png /opt/share/bootimages/palm-logo.png
cp /opt/share/bootimages/palm-logo-up-bright.png /opt/share/bootimages/palm-logo-bright.png
fi
</nowiki></pre>

'''Step Six'''
Restart Luna and watch your awesome new logos.
<pre><nowiki>
pkill LunaSysMgr
</nowiki></pre>

== Boot Themes==

You can find more boot themes at http://www.prethemer.com/logos.

'''Title:''' Old Default Theme

'''Author:''' Palm

[[Image:Palm-logo.png]]
[[Image:Palm-logo-bright.png]]

'''Title:''' New Default Theme

'''Author:''' HP

[[Image:Hp-logo.png]]
[[Image:Hp-logo-bright.png]]

'''Title:''' HP-Palm Theme

'''Author:''' cwgtex, credit to Palm and HP for original images

[[Image:Hpalm-logo.png]]
[[Image:Hpalm-logo-bright.png]]

'''Title:''' Linux Inside Tux bright Edition

'''Author:''' MmO

[[Image:Linux-Inside.png]]
[[Image:Linux-Inside-Bright.png]]

'''Title:''' Tux - got root?

'''Author:''' JackieRipper

[[Image:Jackieripper-palm-logo.png]]
[[Image:Jackieripper-palm-logo-bright.png]]

'''Title:''' Red and Green

'''Author:''' JackieRipper

[[Image:Jackieripper2-palm-logo-up.png]]
[[Image:Jackieripper2-palm-logo-up-bright.png]]
[[Image:Jackieripper2-palm-logo-down.png]]
[[Image:Jackieripper2-palm-logo-down-bright.png]]

'''Title:''' Blue Tux

'''Author:''' pEEf

[[Image:PEEf-palm-logo.png]]
[[Image:PEEf-palm-logo-bright.png]]

'''Title:''' Glassy Tux

'''Author:''' fish199902

[[Image:Fish109902-palm-logo.png]]
[[Image:Fish109902-palm-logo-bright.png]]

'''Title:''' GunTux

'''Author:''' Xaeonis

[[Image:Xaeonis-GunTux-palm-logo.png]]
[[Image:Xaeonis-GunTux-palm-logo-bright.png]]

'''Title:''' bleeding apples

'''Author:''' predatory1

[[Image:Apv-palm-logo.png‎]]
[[Image:Apv-Palm-logo-bright.png‎ ]]

'''Title:''' Just Pre

'''Author:''' JP_Money

[[Image:Just-pre-palm-logo.png]]
[[Image:Just-pre-palm-logo-bright.png]]

'''Title:''' Jumpman Pre

'''Author:''' dave b

[[Image:daveb-jumpman-pre-palm-logo.png]]
[[Image:daveb-jumpman-pre-palm-logo-bright.png]]

'''Title:''' Transform

'''Author:''' Ahabenezer

[[Image:autobot-palm-logo.png]]
[[Image:decepticon-palm-logo-bright.png]]

'''Title:''' Linux

'''Author:''' 473x15

[[Image:linux2-palm-logo.png]]
[[Image:Linux-palm-logo-bright.png]]

'''Title:''' Zombie Palm

'''Author:''' Steel Shadow

[[Image:Zombie-palm-logo.png]]
[[Image:Zombie-palm-logo-bright.png]]

'''Title:''' Serenity (Firefly)

'''Author:''' HelloNNNewman

[[Image:Serenity_4-4.png]]
[[Image:Serenity_5-5.png]]

'''Title:''' Serenity (Firefly)

'''Author:''' HelloNNNewman

[[Image:Firefly 1.png]]
[[Image:Firefly 2_fire.png]]

'''Title:''' Shodan (SS2)

'''Author:''' osat3ch

[[Image:Palm-logo_shodan.png]]
[[Image:Palm-logo-bright_shodan.png]]

File:Preware 2011-09-03 165049.png

2011-03-09T22:09:45Z

Ght: uploaded a new version of "File:Preware 2011-09-03 165049.png"

File:Preware 2011-09-03 165038.png

2011-03-09T22:09:14Z

Ght: uploaded a new version of "File:Preware 2011-09-03 165038.png"

Application:Preware

2011-03-09T22:05:04Z

Ght: /* Blacklist (Category Filters) */

[[Category:Application]]
This page is currently available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:Preware]]
:[[Image:France.png]] [[Application:Preware-FR]]
:[[Image:Germany.png]] [[Application:Preware-DE]]
:[[Image:China.png]] [[Application:Preware-ZH]]

{{application
|name=Preware
|type=webOS
|version=Version: 1.5.0 (17 Dec 2010)
|tag=Utilities
|screenshot=Preware_ss1.png
|description=
}}

 
=Summary=

[[image:Icon_Preware.png|frameless|left]]
Preware is a package management application for the Palm Pre and the Palm Pixi. Preware allows the user to install any package from any of the open standard package repositories on preware.org (or any other location that hosts an open standard package repository). Preware relies on a custom written service developed from community research which allows the mojo app to talk to the built-in ipkg tool.

'''Preware requires webOS 1.4.0 or later to function. Do not try to install it on earlier webOS versions, it will not work.'''

This application was the result of extensive community-based design in [[IPKG Service]] and [[Preware Design]].

For application management, Preware can access more applications, and has more features, than any other on-device package installer.

And since it is open source, and has a completely open development process supported by a team of world-class WebOS Internals developers, it will continue to get better much faster than any other package management application.

Preware is the open application installer that has been written specifically to support a homebrew ecosystem where any developer can upload any application to any submission site, and that application can then be installed by any user. Developers no longer need to upload their applications to multiple submission sites, and users are no longer excluded from accessing applications from any open standard package repository.

 
===Key Features===
Install / Remove / Update:
*Homebrew Applications including advanced applications with special requirements.
*WebOS Themes
*Patches
*webOS Kernels
*Palm App Catalog Applications
*Support for installation of signed packages

 
===Status===
Preware has been upgraded to release status, and is no longer considered beta.

Some milestones worth mentioning in Preware's history include:

* Since 27 August 2009 it is the only over-the-air installer for the palm capable of installing advanced palm applications such as the [[On_Screen_Keyboard|On Screen Keyboard]] or the terminal application.
* Since 27 August 2009 it is the only application supporting installation from all existing palm homebrew feeds.
* Since 17 September 2009 it also supports installation of themes.
* Since 8 October 2009 it also supports installation of webOS patches.
* Since 12 Jan 2010 it also supports all Palm App Catalog feeds.
* Since 3 May 2010 it also supports installation of webOS custom kernels.
* Since 20 July 2010 it also supports installation of packages from URLs and local files.
* Since 24 July 2010 is also supports blacklisting packages and authors.

 
===License===
Please be aware that org.webosinternals.preware is licensed under the [http://www.gnu.org/licenses/gpl-2.0.html GPLv2].

Code from Preware cannot be used by a closed source application. If you want to use them in a non-GPLv2 but otherwise open source application, please contact the [mailto:support@webos-internals.org authors].

 
=Installing Preware=

There are three supported methods for installing Preware: WebOS Quick Install, Stand Alone Installers, and Command Line.

You do not need to access the Linux command line or "root your Pre" to install or use Preware.

You ''cannot'' use fileCoaster, or PreLoad, or PreUpdate to install or update Preware. Those tools are unable to operate correctly on advanced homebrew packages.

If you are a developer who uses the Palm emulator, you should know that Preware works just as well on the Emulator as it does on a real device, and is installed in exactly the same way.

 
===Installing Preware on webOS 2.0===

To install Preware on a webOS 2.0 device, the following procedure is recommended until WebOS Quick Install and other installation methods have been upgraded to support webOS 2.0:

# Install the official Palm webOS 1.4.5 SDK
# '''Disconnect your device''' (I repeat, do not have your device connected, no cables in the device, device not even anywhere near the computer), and run the webOS 2.0 Doctor to install or upgrade your Novacom drivers
# Close the doctor, and connect your device
# Download the latest Preware package from http://get.preware.org/
# Use palm-install to install that package

 
===Installing Preware with WebOS Quick Install===
You can use version 3.14 or later of [http://forums.precentral.net/canuck-software/228310-webos-quick-install-v3-14-a.html WebOS Quick Install] to install Preware directly from the WebOS Internals feed.

'''Latest Version of WebOS Quick Install available here: [http://forums.precentral.net/canuck-software/228310-webos-quick-install-v3-14-a.html WebOS Quick Install v3.14]'''

# Install the required Software
## [http://www.java.com/en/download/installed.jsp?detect=jre&try=1 Click here] to verify that you have the latest java installed on your computer and update if needed
## [http://images.precentral.net/sites/precentral.net/files/webos-homebrew-apps/wosqi/WebOSQuickInstall.jar Click Here] to download the latest version of WebOS Quick Install
## Optionally, [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Click here] to download the current webOS Doctor for your carrier and phone in a subdirectory your will remember (maybe "Palm"?) and the same one in which WebOSQuickInstall will execute. If you already have it, skip this step.
##* You do not need to download webOS Doctor separately unless you wish to do so, as WebOSQuickInstall will download it itself if not found.
##* '''Do not run the webOS Doctor'''
# Put your device in [[Getting started|Developer Mode]]
# Connect your device to your computer with the USB cable, and select "Just Charge" (do not select USB Drive)
# Run WebOS Quick Install. If webOS Doctor is not present, you will be asked if you wish to download it prior to execution.
# Click the third button on the right (Blue Down Arrow)
# Choose WebOS Internals Feed (Pre) or WebOS Internals Feed (Pixi) from the drop-down list at the top.
# Select ''Preware'' from the list.
# Click Download.
# Click Close.
# Click Install.

 
===Installing Preware with the Standalone Installer===
Preware installers can be downloaded here: [http://get.preware.org Preware Standalone Installers]. These instructions are currently only for Mac and PC users.

# Install the required software.
## [http://www.java.com/en/download/installed.jsp?detect=jre&try=1 Click here] to verify that you have the latest version of Java installed on your computer and update it if needed.
## [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Click here] to download the current webOS Doctor for your carrier and phone in a subdirectory you will remember (maybe "Palm"?). If you already have it, skip this step.
##* '''Do not run the webOS Doctor.'''
# Put your device into [[Getting started|Developer Mode]].
#* '''Windows users:''' When connecting your device to the computer for the first time, you will be prompted to install new hardware. Click Next to start the device installation. You may get a message regarding Novacom drivers not being installed. If so, you can disregard it. Once your device is installed, proceed with the Preware installation.
# Download the [http://get.preware.org/ Preware Standalone Installer] (you should choose the latest file name PrewareInstaller-X.Y.Z.jar) and place it in the same directory as the webOS Doctor .jar file.
# Run the Preware Installer.
# Click on the Tools menu and choose Install Drivers. This will install the Palm Novacom drivers for webOS devices.
# Once the drivers have finished installing, click on Install Preware. After Preware is installed, your device will be unresponsive for a few seconds while Luna restarts.

 
===Installing Preware from the Commandline===
If you have access to the command line of your webOS Device or emulator using Terminal, Novaterm, the "Linux Commandline" in WebOS Quick Install, or other techniques, you can install Preware by typing three lines. This technique is always the shortest and in many ways the simplest, but if you are in any way unsure of operating at the Linux command line, please use either of the methods described above.

<source lang="bash">
cd /tmp
wget http://bit.ly/preware-bootstrap
sh preware-bootstrap</source>

 
===Updating Preware===
To update Preware, just run Preware and select "Package Updates" from the main scene. If an update to Preware is available, it will appear in the list. Then select the "Update" button. Preware will close automatically after the update is complete.

Note that you cannot use fileCoaster, or PreLoad, or PreUpdate to install or update Preware. Those tools are unable to operate correctly on advanced homebrew packages.

 

===Removing Preware===
''Why would you ever want to remove Preware?''

To remove Preware, hold the Orange button on your keypad and choose Preware from the Launcher. Choose Delete.

 
=Usage=

===Preferences===
{| Width="70%" VAlign="top"
|valign="top"|[[image:Preferences.png|160px|frameless|left|text-top]]
|valign="top"|You can select preferences in the top left corner of the Pre to bring up the preferences screen. On the Preferences screen you can specify the look of the application, the frequency that feeds are updated, and what Preware will show you by default.
 
{| style="color:black; background-color:#F9F9F9;border:1px outset;" cellpadding="3" cellspacing="0"
|TIP:
|-
|To make it easier to find things, set "Show Available Types" to yes. This will show separate categories (Applications/Themes/Patches/etc.) rather than show everything in one long list.
|}
|}
 

===Feed Management===
{| Width="70%" VAlign="top"
|valign="top"|[[image:Preware_feeds.png|160px|frameless|left|text-top]]
|valign="top"|In the preferences section on the top bar on the right side is a button that takes you to the feeds screen. On the feeds screen you can select which feeds are loaded and which ones are not. Simply select the on or off button for that feed. (If you are not interested in themes you can disable the two feeds for themes to speed up the updating of feeds) Preware comes with the following feeds by default (some are disabled by default, but are easily enabled if desired).

{| style="color:black; background-color:#FFFFE0;" cellpadding="3" cellspacing="0" Border="1"
|align="center" colspan="4" | '''Default Feeds'''
|-
|align="center" | [http://ipkg.preware.org/feeds/palm-beta/ Palm Beta]
|align="center" | [http://ipkg.preware.org/feeds/palm-beta-updates Palm Beta Updates]
|align="center" | [http://ipkg.preware.org/feeds/palm-catalog/ Palm Catalog]
|align="center" | [http://ipkg.preware.org/feeds/palm-catalog-updates/ Palm Catalog Updates]
|-
|align="center" | [http://ipkg.preware.org/feeds/palm-web-updates/ Palm Web]
|align="center" | [http://ipkg.preware.org/feeds/palm-web-updates/ Palm Web Updates]
|align="center" | [http://ipkg.preware.org/feeds/precentral/ PreCentral]
|align="center" | [http://ipkg.preware.org/feeds/precentral-themes/ PreCentral Themes]
|-
|align="center" | [http://ipkg.preware.org/feeds/webos-internals/ WebOS Internals]
|align="center" | [http://ipkg.preware.org/feeds/optware/ Optware]
|align="center" | [http://ipkg.preware.org/feeds/webos-patches/ WebOS Patches]
|align="center" | [http://ipkg.preware.org/feeds/webos-kernels/ WebOS Kernels]
|-
|}
|}

{| style="color:black; background-color:#F9F9F9;border:1px outset;" VAlign="middle" cellpadding="3" cellspacing="0" Width="70%"
|align="center" | See [[Testing Feeds]] for detailed instructions on adding custom feeds.
|}
 

===Package Updates===
{| Width="70%" VAlign="top"
|valign="top"|[[image:UpdateFeeds.png|160px|frameless|left|text-top]]
|valign="top"|To update feeds, simply select "Update Feeds" from the Application Menu. Preware will download the package list information from your enabled feeds. After processing the data, you will be back at the main list of available items.
|}
 

===Installing Packages===
{| Width="70%" VAlign="top"
|valign="top"|[[image:SelectApp.png|160px|frameless|left|text-top]]
|valign="top"|There are a few ways to select and install a "package" (application/patch/theme/etc.). Using "List of Everything" would be the simplest.
#Find the package you want to install either by scrolling and tapping on it, or just start typing
#Tap the "Install" button that the bottom of the package's page to install.
|}
 

===Removing Packages===
{| Width="70%" VAlign="top"
|valign="top"|[[image:RemoveAppTap.png|160px|frameless|left|text-top]]
|valign="top"|Removing a package is just as easy.
#On the main screen, tap "Installed Packages", then the category of the package you want to remove
#Tap the Package you want to remove
#Tap the "Remove" button that the bottom of the package's page.
|}
 

===Blacklist (Category Filters)===
{| Width="70%" VAlign="top"
[[File:preware_2011-09-03_165038.png]]''' '''[[File:preware_2011-09-03_165049.png]]
|valign="top"|The Preware "Blacklist" is a tool used to hide packages (applications, patches, etc) that you do not want to see, such as mass-produced book apps or real estate apps. This tool can also be used to hide unavailable packages, such as patches that are not compatible with your current webOS version. Got to Preferences in Preware and scroll to the Blacklist section. You can add whatever filters you like to customize your Preware experience. To hide all apps from a particular Maintainer, choose a "Maintainer" filter with the package maintainer in the search field. To hide unavailable packages, choose a "Category" filter, with "Unavailable" in the search field.
 

{| style="color:black; background-color:#F9F9F9;border:1px outset;" cellpadding="3" cellspacing="0"



= Operating notes =

===Limitations===
No known limitations.

 
===Known bugs===
*When selecting a patch with dependencies, if you view those dependencies then install them, when Preware returns you to the original patch's screen it will still have the 'install' button showing even though it is installed successfully. Swiping back and returning will show the correct status.

*The Update All button can get confused if there are patches with complex dependencies. This will be fixed in a future version.

*If updates to App Catalog applications are pending, they will be silently skipped when using the Update All button.

*The Updates feature from the regular Palm Launcher, may claim that application updates are needed, and then when the user clicks Show Updates shows the App Catalog's installed applications, there are none shown that need updating. This isn't as expected. This is because an app that was previously only in Preware has now migrated to the Palm Catalog. Don't worry, your apps are up to date (with the possible exception of the one with the conflict.) This is not a bug in Preware per se' but an app version conflict because the app is in both the Palm Catalog and also in Homebrew. Notice that you don't need to remove Preware to install the app from the official catalog, but simply disable the feed in Preware then "update feeds" to refresh the list then it should install fine from the official app catalog.

 
=Changelog=
 
For those interested, the full Changelog can be [http://git.webos-internals.org/?p=applications/preware.git;a=tags found here]. Listed below is the Changelog since the 1.0 milestone.
 

;1.5.0:
* You must upgrade to this version for full webOS 2.0 compatibility.

;1.4.9:
* Better compatibility with unknown future webOS versions.

;1.4.8:

* Now calls the correct software manager updates screen on webOS 2.0.

; 1.4.7:
* Fixed update, install and remove status messages on webOS 2.0.

;1.4.6:
* New "App Catalog" theme preferences thanks to Garrett92C.
* Added support for "MaxWebOSVersion" in the feeds.

;1.4.5:
* Added support for identifying when running on a Pre 2 device.

;1.4.4:
* Updated the version check to support future webOS versions.

;1.4.2:
* Added Category as a blacklist option.

;1.4.1:
* Added a Changelog button to the Help scene.

;1.4.0:
* Added help to preferences scene.
* Fixed swipe-to-delete bug in blacklist.
* Updated Italian translations (courtesy of Darkmagister).
* Added "Get Info" button to package install scene.
* Added "Send" button to ipkg log scene.
* Fixed bug when loading large package descriptions.

;1.3.8:
* Updated French translations (courtesy of Yannick LE NY).

;1.3.6:
* Preware now supports installation of application package files (.ipk files) directly from URLs, email attachments, and local files.
* Also supported are Send to Preware links on homebrew application gallery and news websites (this requires the Neato! application to also be installed).
* If Preware continually asks you about file associations on every single launch, even after you have answered Yes to the questions it asks, then you may have a damaged file association table and will need to run the Emergency MimeTable Reset tool and then reboot to repair it.

;1.3.5:
* Updated German translations.

;1.3.3:
* Always ask the user before modifying the file association list.
* Updated French translations.

;1.3.1:
* Check whether Preware is the default application for handling packages, and advise the user if it is not.

;1.3.0:
* Added Preware to the Default Applications list to allow for installing packages from email messages and the browser.

;1.2.9:
* Fixed the Saved Package List swipe to delete bug.

;1.2.8:
* Open the My Applications app catalog screen when multiple app catalog applications need updating.

;1.2.7
* Fixed the Install Package problem when running on the emulator.

;1.2.6
* Remove most of the curl download progress messages from the ipkg log (this fixes a buffer overrun crash).

;1.2.5
* Added Ask At Launch option to update preference.
* Added Blacklist support.
* German Translation updates.
* Fixed update banner problem.
* Fixed package with too many dependent packages problem.

;1.2.4
* Added support for MinWebOSVersion, DeviceCompatibility and PreActionMessage package attributes.

;1.2.3
* Enable the Install Package feature to also work for incorrectly formatted filenames.

;1.2.1
* Robustified the Install Package feature - will now run post-install scripts for all correctly formatted filenames (packageid_version_arch.ipk).

;1.2.0
* Added Install Package functionality, allowing installation of packages from URLs and local files.
* Moved Saved Package List from the main screen to the app menu.

;1.1.7
* Added support for Kernel Modules.

;1.1.5
* Use a gentler reboot procedure to allow open files to be flushed to disk.

;1.1.4
* Fixed hang on package download failures.

;1.1.2
*Added support for the ENABLE_TESTING_FEEDS Meta-Doctor feature.
*Removed the tag line about eventually reaching 1.0.
*Minor French translation updates, courtesy of Yannick LE NY.

;1.1.1
*Added languages field in package descriptions.
*Added preference to only show packages with English descriptions.

;1.1.0
*Now defaults (selectable by a preference option) to using an alternative installation method to avoid the webOS 1.4 rescan bug which closes and stops notifications from your phone, email and messaging applications.
*Updated German and French translations.
*Fixed deletion of disabled feeds.
*Added service version number to the ipkgservice API. Robustified the service upgrade process.

;1.0.0
*The Package Manager Service has been rewritten in C and incorporated into this single Preware package.
*Installing Preware 1.0.0 will remove the Package Manager Service as the last step of the upgrade process.

 
=Repository=
Preware and the Package Manager Service are housed in the applications/preware git repository at http://git.webos-internals.org/

For more information getting your application published in the WebOS Internals Source Code Repositories, please see the [[WebOS Internals Source Code Repositories]] page. For commit permission to the open source project, contact rwhitby on #webos-internals or email [mailto:support@webos-internals.org support@webos-internals.org]

File:Preware 2011-09-03 165049.png

2011-03-09T22:00:00Z

Ght:

2011-03-03T21:13:08Z

Ght: /* Palm Profile */

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

Note: Scripts currently exist for the following devices:
* Sprint Pre/FrankenPre+
* Verizon Pre+
* AT&T Pre+
* "WR" devices
* Telcel Pre
* Bell Mobility Pre
* O2 German Pre (or similar)
* O2 German Pre+ (or similar)

The meta-o2-* scripts do not masquerade.
WR folks should try them first, and if they get a 9.9.9 in the palm profile, use the meta-wr-* scripts instead and masquerade.

== 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 Save/Restore 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]

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: Install Prerequisites ==
* '''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 the first 8 steps in Step 1: Setting up Meta-Doctor on that page. When you get to the end of step 8 - "Ensure that there is a downloads directory" on that page, you should come back to this page and continue the procedure on this page. (if you're using a Mac, then follow the Mac instructions up to step #11, which gets you to the same point as on Linux)

* '''Palm SDK ''' - see [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website]

The Palm SDK is required for the correct installation of the novacom drivers for your device, and 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.

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

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

'''From the meta-doctor directory''', run the meta-script that corresponds to your advice. For example, a Sprint user would run:
<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0
</nowiki></pre>

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

For those who for what ever reason can't activate their phones and need to skip first use and get wifi started to sign into their profiles, just add "--wifi-only" as an extra argument to the meta-script:

For example, a user with a Sprint device who was never (without creating and running a different doctor) going to connect to the Sprint cellular network would run:
<pre><nowiki>
./scripts/meta-sprint-pre-2.1.0 --wifi-only
</nowiki></pre>

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.

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

== Step 5: Restore /etc/palm-build-info ==
If your device says version 1.4.5 in the Device Info app, then you must complete this step and also step 6. If your device says version 2.1.0 in the Device Info app, you can skip directly to step 6 (yes, you really should do step 6, don't stop here).

Since some devices have to "masq" their OS version from the Palm Profile to gain access to the App Catalog, some meta-scripts will leave a '''palm-build-info-unmasqed''' file in the ./meta-doctor directory. To get applications like Preware to offer you the correct selection of patches, etc. you will need to "unmasq" your phone.

This is done by replacing the /etc/palm-build-info file ''on your phone'' with the ./meta-doctor/palm-build-info-unmasqed file ''on your computer'', and then rebooting.

Choose '''one''' of the following methods '''after''' you have logged in to your Palm Profile:<blockquote>

=== Via a Terminal, with Novacom ===
# Make sure '''novacomd''' is running on your computer
# Open up a terminal (Linux, OS X, Cygwin, Windows "CMD.exe") on your host computer (not your phone) and change back to the meta-doctor directory. then type in the following:
<blockquote>
<pre><nowiki>
novacom run file://usr/sbin/rootfs_open -t
novacom put file://etc/palm-build-info < palm-build-info-unmasqed
novacom run file://sbin/reboot</nowiki></pre>
</blockquote>
:3. Reboot

=== Copy the File to the USB Partition ===
# Attach your phone to your computer and put it in "USB Drive" mode.
# Copy the ./meta-doctor/palm-build-info-unmasqed file over to your Phone's USB Drive.
# Confirm that '''novacomd''' is running on your computer
# Use a terminal (any mentioned in the step above will work) to run '''novaterm''' and access your phone.
<blockquote>
<pre><nowiki>
cd /
/usr/sbin/rootfs_open -t
cp -f /media/internal/palm-build-info-unmasqed /etc/palm-build-info
/sbin/reboot
</nowiki></pre></blockquote>
:5. Reboot

=== Using WebOS Quick Install ===
# Confirm that '''novacomd''' is running on your computer
# Make sure you have the latest version of [http://forums.precentral.net/showthread.php?p=2850874 WebOS Quick Install].
# Select Tools->Send File from the menu, and enter the following values: 
<blockquote>'''File:''' (Select your palm-build-info-masq file) 
'''Destination:''' /etc/palm-build-info</blockquote>
:4. Click on '''Send to Destination'''
:5. Reboot after that succeeds.</blockquote>

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

== Available Software ==

=== App Catalog ===
* Apps that are marked as only compatible with webOS versions 2.x and above do not currently work with some of these doctored installations of webOS 2.1.0. On some of the devices/carriers, masquerading is used which leads to the Palm profile still reporting version 1.40.50.

==== Masquerading ====
* Palm's servers only accept certain device/OS combinations as valid. While some ROW Pre and Pre Plus devices running 2.1 are accepted (mainly O2 Germany devices), Pre and Pre Plus devices running on Sprint, Verizon and AT&T (and some ROW) have to masquerade as still running webOS 1.4.5. To achieve this, /etc/palm-build-info is replaced with the version from the 1.4.5 doctor to trick Palm's servers into believing it is a valid device/OS combination and allowing app catalog access. Once app catalog access is achieved, /etc/palm-build-info can be replaced with the 2.1 version which is found in meta-doctor/palm-build-info-unmasqed on the computer you built the doctor with.
* Note that if you ever need to log into your palm profile a subsequent time on your device (e.g. after a full erase), you will need to put back the webOS 1.4.5 palm-build-info file and reset your device before logging back into your profile. It may be easier simply to run the procedure on this page from the top again.

=== 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:
<blockquote>
==== 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
</blockquote>

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

=== Flash ===
* Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre2 2.01 doctor.

==== Adding Flash Support (Easy Method) ====
The easiest way to get flash on your webOS 2.1.0 legacy device is via creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser.

It sounds complex, but it much easier overall and a How-To has been detailed [http://tinyurl.com/flash-webos-2-1-0 here].

==== Adding Flash Support Manually ====
# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive 
# Copy the following files from the extracted WebOS.tar to their equivalent locations in your MetaDoctor (alternatively, you can copy them manually to a live device using Novaterm)
<blockquote>/etc/adobe/mms.cfg
 /etc/adobe/oem.cfg
 /usr/lib/BrowserServerPlugins/libflashplayer.so
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
 /usr/lib/libFlashGraphics.so
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
 /usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
 /usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote>
:3. Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
: Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
<blockquote>this.controller.get("flashPref").hide();
 this.controller.get("autoLoadPref").hide(); </blockquote>
:4. Reboot your Pre if the editing was done on a live device

Flash preferences should now be visible under browser preferences.

== 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 substitute the 10240 value for 32768, reboot your Pre and verify it's working by using Govnah.

For example, you could follow these steps:

#Make sure '''novacomd''' is running on your computer.
#Use a terminal (any mentioned in step 5 will work) to run '''novaterm''' and access your phone. Type in the following: <pre>vi /etc/event.d/compcache</pre>
#Go down to line 10 type i then delete 10240 and replace it with 32768, hit the escape key then type :wq
#Reboot your Pre and verify it's working by using Govnah.

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

* You may get lucky if your Profile has information and you managed to pass the "Logging to Profile" screen but are stuck with a message stating that the phone cannot restore your data. If you have developer mode enabled, enter your Pre and overwrite the /etc/palm-build-info file with the palm-build-info-masq file the Doctor generated. Reboot your Pre and see if it manages to boot succesfully.

* If you get 9.9.9 in palm.com/palmprofile, then you can either 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, or you can restore the masqueraded /etc/palm-build-info for your device, erase your backup info in the backup app and use "Erase Apps and Data" from the reset option in the Device Info app.

* If you get the dr. skipped firstuse as a palm profile in the new accounts app in 2.1.0 and/or if the gesture application creates a blank screen, you have the 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 metadoctor latest version and run the appropiate script with the --wifi-only switch.

* 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, make sure your /etc/palm-build-info is masquerading as 1.4.5 for your carrier, erase your backup data from the backup app by turning off backups and chose Erase Apps and Data from the reset options in the Device Info app.

* If you are unable to install the Palm SDK to use the novacom program to transfer files to your device, step 5 can alternatively be performed by putting the device in USB mode, transferring file to the main folder of the USB drive, ejecting the USB drive, and then use WebOSQI 3.x's linux commandline feature to perform the alternate commands in Step 5 (not the novacom ones).

*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==
* To enable GPS functionality it may be necessary to go to the "Location Services" application, make sure that "GPS", and "GPS Location Services" are enabled. Test the GPS using ##477# (##GPS#) from the phone application, and press the "Get Fix" button.
* If neither ##477# utility nor Google Maps is able to successfully fix your position, return to the "Location Services" application, open the ''Preferences'' menu, expand ''Locate Me Using...'' and ensure that both '''GPS''' and '''Google Services''' are selected. After selecting '''Google Services''', you will be prompted to accept the Terms of Service. Once both options are selected, test GPS functionality again. The ##477# utility may still fail the first several times, but should complete successfully after repeated attempts, and should continue to function normally thereafter.

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