WebOS Internals - User contributions [en]

Application:Preware

2015-08-17T08:31:58Z

Pcworld: /* Installing Preware with WebOS Quick Install */ update for Quick Install 4.6

[[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.9.7 (15 December 2011)
| tag=Utilities
| screenshot=Preware_ss1.png
| description=
}}

 
== Summary ==

[[image:Icon_Preware.png|frameless|left]]
Preware is a package management application for the Palm Pre, Palm Pixi, and the HP TouchPad. 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
* 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.
* Since 8 June 2011, access to webOS app catalog feeds is no longer available to third party developers or applications.
* Since 15 December 2011, access to webOS app catalog feeds has been restored via App Tuckerbox.
* Since 15 December 2011, it also supports downloading feeds and packages from authenticated secure sites.

 
=== 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 four supported methods for installing Preware: Official HP/Palm SDK, WebOS Quick Install, Stand Alone Installers, and Command Line.

'''For a step-by-step tutorial, the official [http://bit.ly/phd-ac Preware Homebrew Documentation] is highly recommended'''

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 using the official HP/Palm SDK ===

To install Preware on any webOS device, the following procedure is recommended if you're having problems with WebOS Quick Install:

# Install the latest official Palm webOS SDK from http://developer.palm.com
# '''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 latest webOS Doctor to install or upgrade your Novacom drivers
# Close the doctor
# Your device should remain disconnected
# Download the latest Preware package onto your computer from http://get.preware.net
## To install Preware on a device, download the 'arm' .ipk file
## To install Preware on an emulator, download the 'i686' .ipk file
# Typing webos20090606, select the developer mode icon that will appear, and verify that your device is in developer mode
# Connect your device to your computers USB port, and select 'Just Charge' (or 'Cancel' on your Touchpad)
# If you are installing on a Veer, you will need to reboot the phone while connected to the computer, at this point, or it will not be recognized
# Use palm-install to install the package you downloaded
## Typically you can simply get a command line, navigate to the directory with the Preware package you downloaded, then type palm-install and.the.package.arm.name.ipk

 

=== Installing Preware with WebOS Quick Install ===
You can use version 4.6.0 or later of WebOS Quick Install to install Preware on any device easily and quickly, without the need to download a big 200MB SDK and webOSDoctor.

'''Latest Version of WebOS Quick Install available here: [http://forums.webosnation.com/canuck-coding/274461-webos-quick-install-v4-6-0-a.html WebOS Quick Install v4.6.0]

# 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
## Download the current version of WebOS Quick Install (link see above)
# Put your device in [[Getting started|Developer Mode]]
# Connect your device to your computer with the USB cable, and select "Just Charge" or "Cancel" (on a Touchpad). Do not select USB Drive.
# Run WebOS Quick Install. If the novacom driver is not installed, WebOS Quick Install will download and install that for you.
## '''Do not believe any guide that says you need to download the SDK or webOSDoctor for WOSQI to run.''' The most you'll download is the novacom driver, which is only 11MB on Windows, and will be done via WOSQI.
# If you are installing on a Veer, you will need to reboot the phone at this point or WOSQI will not recognize it. Hold the On/Off button down for about five seconds and release it. Select "Power" then select "Restart".
# Click the third button on the right (the globe icon)
# Select the Applications tab at the top
# Search for Preware
# 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 device 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.
# If you are installing on a Veer, you may need to reboot the phone at this point.
# 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 command line ===
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. 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
curl -L http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/preware-bootstrap.sh > preware-bootstrap.sh
sh /tmp/preware-bootstrap.sh
</source>

Alternatively, you can use the url-shortened address (as of this date):

<source lang="bash">
cd /tmp
curl -L http://bit.ly/preware-bootstrap > preware-bootstrap.sh
sh /tmp/preware-bootstrap.sh
</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.

Alternatively, WebOS Quick Install provides a method for updates as well that is similar to Preware.

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 on webOS 2.x or lower, hold the Orange button on your keypad and choose Preware from the Launcher. Choose Delete.
For Touchpads (3.x), tap and hold the icon and click the "x" that appear on the icon. 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. 
In the upper right corner is a blue question mark. To get additional information on each preference tap on the blue question mark. All preferences are now highlighted in blue. Tap on a certain preference to enter the help screen. To leave the help screen back swipe. Tap again on the blue question mark to leave the help mode.
 
{| 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/precentral/ PreCentral]
|-
| 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.
|}
 



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

* 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.9.12
* Added support for WebOS Community Edition (WOCE) feeds by the WebOS Ports team from WebOS Internals.

; 1.9.10
* Updated German translation (courtesy of DiplPhy).

; 1.9.9
* Added Traditional Chinese translation (courtesy of tonyw).

; 1.9.8
* Updated German translation (courtesy of DocZet).

; 1.9.7
* Added support for secure package downloads.

; 1.9.6
* Added support for secure feed downloads.

; 1.9.5
* Fixed the window orientation for the blue question mark help items.

; 1.9.4
* Added disclaimer when installing apps marked incompatible with current device.

; 1.9.2
* Revamped feed downloading to give better error and status reporting.

; 1.9.1
* Fixed device identification of WiFi TouchPads.

; 1.9.0
* Added feed display and installation support for App Tuckerbox.

; 1.8.7
* Hide authentication information in the Manage Feeds display.

; 1.8.6
* Added support for displaying the Changelog and DeviceCompatibility fields.

; 1.8.5
* Fixed missing package information bug

; 1.8.4
* Added some additional Second Line preference options

; 1.8.3
* Please read http://testing.preware.org/ if you use the testing feeds

; 1.8.2
* Fixed the removal of obsolete testing feeds

; 1.8.1
* Remove the obsolete testing feeds when adding alpha or beta feeds

; 1.8.0
* Disabled support for adding obsolete testing feeds

; 1.7.7
* Enabled support of alpha and beta testing feeds

; 1.7.6:
* Larger screenshots on the TouchPad
* Pressed states for TouchPad back buttons
* Fixed search backspace on TouchPad

; 1.7.5:
* Fixed list rendering on TouchPad (courtesy of chpwn).

; 1.7.4:
* Removed catalog feed specific preferences (show only free/show only english).

; 1.7.3:
* Added support for font packages.

; 1.7.2:
* Replaced the word phone with the word device in all messages.

; 1.7.1:
* Fixed fullscreen screenshot resizing on TouchPad rotate (courtesy of Appsotutely).
* Fixed dependent packages spinner location (courtesy of chpwn).

; 1.7.0:
* Rolled up all the beta release features for a TouchPad-compatible public release.

; 1.6.8:
* Enabled back tap on header for all devices.

; 1.6.7:
* Fixed full-screen formatting of ipkg log screen.

; 1.6.6:
* Preware is now fully compatible with the TouchPad, using the full screen area.

; 1.6.5:
* Now usable on devices without a back gesture.
* Set the wget user-agent to Preware when retrieving indexes and packages.

; 1.6.4:
* Fixed a problem when loading the saved packages list.

; 1.6.3:
* WebOS Internals has been formally notified by Richard Kerris (HP Vice President of Worldwide Developer Relations) that open access to the webOS app catalog feed (including the beta and web feeds) is no longer available to third party developers or applications. Please direct any questions about this decision (which is final and permanent) to HP, not to WebOS Internals.
* Removed all HP webOS app catalog feeds from new installations of Preware.

; 1.6.2:
* Added the clock themes feed (disabled by default).

; 1.6.0:
* webOS 2.x Just Type integration.
* Fixed package list ordering bug.
* Layout fixes for Pixi/Veer.

; 1.5.9:
* Fixed parse errors resulting from packages with very large descriptions.
* Fixed problems with updates to app catalog apps.

; 1.5.8:
* Moved blacklisting to feed load to speed up listing.
* Suggests a reload after changing the blacklist.
* Fixed homebrew feed/catalog feed same appid bug.

; 1.5.7:
* Added check to make sure package has a title before trying to search it.

; 1.5.6:
* Removed support for Visibility feed value - use a category filter to exclude Unavailable packages if desired.

; 1.5.5:
* Added support for Visibility feed value.
* Fix display of screenshots from devices with a different resolution.
* Test fix for custom feed on network with no internet connection.
* Style updates for pre3 screen size.

; 1.5.4:
* Updated French translations (courtesy of Clément).

; 1.5.3:
* Reinstated banner notification of manual saved package list update.

; 1.5.2:
* Check if package dates are actually dates.
* Removed banner notification of saved package list being saved.

; 1.5.1:
* Added support for optware testing feeds.

; 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]

Application:Preware

2014-11-10T00:23:40Z

Pcworld: /* Installing Preware with WebOS Quick Install */ updated WebOS Quick Install; removed link to wosqi guide as App Catalog sales have been discontinued

[[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.9.7 (15 December 2011)
| tag=Utilities
| screenshot=Preware_ss1.png
| description=
}}

 
== Summary ==

[[image:Icon_Preware.png|frameless|left]]
Preware is a package management application for the Palm Pre, Palm Pixi, and the HP TouchPad. 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
* 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.
* Since 8 June 2011, access to webOS app catalog feeds is no longer available to third party developers or applications.
* Since 15 December 2011, access to webOS app catalog feeds has been restored via App Tuckerbox.
* Since 15 December 2011, it also supports downloading feeds and packages from authenticated secure sites.

 
=== 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 four supported methods for installing Preware: Official HP/Palm SDK, WebOS Quick Install, Stand Alone Installers, and Command Line.

'''For a step-by-step tutorial, the official [http://bit.ly/phd-ac Preware Homebrew Documentation] is highly recommended'''

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 using the official HP/Palm SDK ===

To install Preware on any webOS device, the following procedure is recommended if you're having problems with WebOS Quick Install:

# Install the latest official Palm webOS SDK from http://developer.palm.com
# '''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 latest webOS Doctor to install or upgrade your Novacom drivers
# Close the doctor
# Your device should remain disconnected
# Download the latest Preware package onto your computer from http://get.preware.org/
## To install Preware on a device, download the 'arm' .ipk file
## To install Preware on an emulator, download the 'i686' .ipk file
# Typing webos20090606, select the developer mode icon that will appear, and verify that your device is in developer mode
# Connect your device to your computers USB port, and select 'Just Charge' (or 'Cancel' on your Touchpad)
# If you are installing on a Veer, you will need to reboot the phone while connected to the computer, at this point, or it will not be recognized
# Use palm-install to install the package you downloaded
## Typically you can simply get a command line, navigate to the directory with the Preware package you downloaded, then type palm-install and.the.package.arm.name.ipk

 

=== Installing Preware with WebOS Quick Install ===
You can use version 4.5.1 or later of WebOS Quick Install to install Preware on any device easily and quickly, without the need to download a big 200MB SDK and webOSDoctor.

'''Latest Version of WebOS Quick Install available here: ''' Note that currently, the [http://forums.webosnation.com/canuck-coding/274461-webos-quick-install-v4-5-0-a.html last official version] of WebOS Quick Install does not work to install Preware. [https://www.dropbox.com/s/b2ytrauvlqc4p6g/WebOSQuickInstall-4.5.1.jar?dl=1 You can download an unofficial updated build here] ([http://pivotce.com/2014/08/31/tip-preware-net-solutions-for-wosqi-preware-v1-9-13/ source]).

# 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
## Download the current version of WebOS Quick Install (link see above)
# Put your device in [[Getting started|Developer Mode]]
# Connect your device to your computer with the USB cable, and select "Just Charge" or "Cancel" (on a Touchpad). Do not select USB Drive.
# Run WebOS Quick Install. If the novacom driver is not installed, WebOS Quick Install will download and install that for you.
## '''Do not believe any guide that says you need to download the SDK or webOSDoctor for WOSQI to run.''' The most you'll download is the novacom driver, which is only 11MB on Windows, and will be done via WOSQI.
# If you are installing on a Veer, you will need to reboot the phone at this point or WOSQI will not recognize it. Hold the On/Off button down for about five seconds and release it. Select "Power" then select "Restart".
# Click the third button on the right (the globe icon)
# Select the Applications tab at the top
# Search for Preware
# 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 device 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.
# If you are installing on a Veer, you may need to reboot the phone at this point.
# 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 command line ===
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. 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
curl -L http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/preware-bootstrap.sh > preware-bootstrap.sh
sh /tmp/preware-bootstrap.sh
</source>

Alternatively, you can use the url-shortened address (as of this date):

<source lang="bash">
cd /tmp
curl -L http://bit.ly/preware-bootstrap > preware-bootstrap.sh
sh /tmp/preware-bootstrap.sh
</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.

Alternatively, WebOS Quick Install provides a method for updates as well that is similar to Preware.

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 on webOS 2.x or lower, hold the Orange button on your keypad and choose Preware from the Launcher. Choose Delete.
For Touchpads (3.x), tap and hold the icon and click the "x" that appear on the icon. 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. 
In the upper right corner is a blue question mark. To get additional information on each preference tap on the blue question mark. All preferences are now highlighted in blue. Tap on a certain preference to enter the help screen. To leave the help screen back swipe. Tap again on the blue question mark to leave the help mode.
 
{| 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/precentral/ PreCentral]
|-
| 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.
|}
 



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

* 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.9.12
* Added support for WebOS Community Edition (WOCE) feeds by the WebOS Ports team from WebOS Internals.

; 1.9.10
* Updated German translation (courtesy of DiplPhy).

; 1.9.9
* Added Traditional Chinese translation (courtesy of tonyw).

; 1.9.8
* Updated German translation (courtesy of DocZet).

; 1.9.7
* Added support for secure package downloads.

; 1.9.6
* Added support for secure feed downloads.

; 1.9.5
* Fixed the window orientation for the blue question mark help items.

; 1.9.4
* Added disclaimer when installing apps marked incompatible with current device.

; 1.9.2
* Revamped feed downloading to give better error and status reporting.

; 1.9.1
* Fixed device identification of WiFi TouchPads.

; 1.9.0
* Added feed display and installation support for App Tuckerbox.

; 1.8.7
* Hide authentication information in the Manage Feeds display.

; 1.8.6
* Added support for displaying the Changelog and DeviceCompatibility fields.

; 1.8.5
* Fixed missing package information bug

; 1.8.4
* Added some additional Second Line preference options

; 1.8.3
* Please read http://testing.preware.org/ if you use the testing feeds

; 1.8.2
* Fixed the removal of obsolete testing feeds

; 1.8.1
* Remove the obsolete testing feeds when adding alpha or beta feeds

; 1.8.0
* Disabled support for adding obsolete testing feeds

; 1.7.7
* Enabled support of alpha and beta testing feeds

; 1.7.6:
* Larger screenshots on the TouchPad
* Pressed states for TouchPad back buttons
* Fixed search backspace on TouchPad

; 1.7.5:
* Fixed list rendering on TouchPad (courtesy of chpwn).

; 1.7.4:
* Removed catalog feed specific preferences (show only free/show only english).

; 1.7.3:
* Added support for font packages.

; 1.7.2:
* Replaced the word phone with the word device in all messages.

; 1.7.1:
* Fixed fullscreen screenshot resizing on TouchPad rotate (courtesy of Appsotutely).
* Fixed dependent packages spinner location (courtesy of chpwn).

; 1.7.0:
* Rolled up all the beta release features for a TouchPad-compatible public release.

; 1.6.8:
* Enabled back tap on header for all devices.

; 1.6.7:
* Fixed full-screen formatting of ipkg log screen.

; 1.6.6:
* Preware is now fully compatible with the TouchPad, using the full screen area.

; 1.6.5:
* Now usable on devices without a back gesture.
* Set the wget user-agent to Preware when retrieving indexes and packages.

; 1.6.4:
* Fixed a problem when loading the saved packages list.

; 1.6.3:
* WebOS Internals has been formally notified by Richard Kerris (HP Vice President of Worldwide Developer Relations) that open access to the webOS app catalog feed (including the beta and web feeds) is no longer available to third party developers or applications. Please direct any questions about this decision (which is final and permanent) to HP, not to WebOS Internals.
* Removed all HP webOS app catalog feeds from new installations of Preware.

; 1.6.2:
* Added the clock themes feed (disabled by default).

; 1.6.0:
* webOS 2.x Just Type integration.
* Fixed package list ordering bug.
* Layout fixes for Pixi/Veer.

; 1.5.9:
* Fixed parse errors resulting from packages with very large descriptions.
* Fixed problems with updates to app catalog apps.

; 1.5.8:
* Moved blacklisting to feed load to speed up listing.
* Suggests a reload after changing the blacklist.
* Fixed homebrew feed/catalog feed same appid bug.

; 1.5.7:
* Added check to make sure package has a title before trying to search it.

; 1.5.6:
* Removed support for Visibility feed value - use a category filter to exclude Unavailable packages if desired.

; 1.5.5:
* Added support for Visibility feed value.
* Fix display of screenshots from devices with a different resolution.
* Test fix for custom feed on network with no internet connection.
* Style updates for pre3 screen size.

; 1.5.4:
* Updated French translations (courtesy of Clément).

; 1.5.3:
* Reinstated banner notification of manual saved package list update.

; 1.5.2:
* Check if package dates are actually dates.
* Removed banner notification of saved package list being saved.

; 1.5.1:
* Added support for optware testing feeds.

; 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]

Getting started

2014-11-10T00:19:41Z

Pcworld: removed empty headlines

__FORCETOC__
This page is currently available in four languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Getting started]]
:[[Image:France.png]] [[Getting started-FR]]
:[[Image:China.png]] [[Getting started-ZH]]
:[[Image:Germany.png]][[Getting started-DE]]
= Enabling Developer Mode =

# Go to the main (start) screen on your Palm Pre or Pixi
# Start typing "webos20090606" without the quotation marks.
# Tap the Developer Mode icon and turn Developer Mode on.
# Set Developer Mode to ON.
# When asked, tap Reset The Device. Your phone will restart.
# Connect the USB cable to your computer and select "Just Charge" when the phone prompts you.

{{article-two-columns
|width1=320px
|width2=320px
|column1=
== Step 1 ==

Type what's below in universal search to find the Developer Mode Enabler app. Run it.
This is the classic [http://en.wikipedia.org/wiki/Konami_Code Konami Code]

<source lang="text">
upupdowndownleftrightleftrightbastart
</source>

Since webOS 1.1 a shorter version also works:

<source lang="text">
webos20090606
</source>

[[Image:Enable_developer_mode_step1.png]]

|column2=
== Step 2 ==

Set the Developer Mode toggle switch to the on position.

[[Image:Enable_developer_mode_step2.png]]
}}

Komodo WebOS Add-on Install

2011-12-23T12:16:35Z

Pcworld: corrected dead links, reuploaded rawmojo.cix

{{article-two-columns
|width1=60%
|column1=
==Brief Description==
* The Palm Development Kit (SDK) is a free download from Palm
* Komodo Edit is a free cross-platform editor from ActiveState
* There is a '''Komodo webOS Add-on''' from Austin (IRC, twitter Templarian) to assist the Palm Pre development in this environment to make things easier.
* The '''Komodo WebOS Add-on''' features:
** Quick Project Generation
*** [[Image:Komodo_Folder_Pre_Add.png]] New Project
*** [[Image:Komodo_Page_White_Add.png]] New Scene
** One Click Deploy
*** [[Image:Komodo_Box_Add.png]] Package, Install, Launch to Emulator
*** [[Image:Komodo_Box_Magnifier.png]] Package, Install, Inspect in Emulator
*** [[Image:Komodo_Box_Delete.png]] Remove Application from Emulator
*** [[Image:Komodo_Box_Go.png]] Launch Application in the Emulator
*** [[Image:Komodo_Box_Cancel.png]] Close Application in the Emulator
*** [[Image:Komodo_Pre_Add.png]] Package, Install, Launch to Device
*** [[Image:Komodo_Pre_Delete.png]] Remove Application from the Device
*** [[Image:Komodo_Pre_Go.png]] Launch Application on the Device
*** [[Image:Komodo_Pre_Cancel.png]] Close application on the Device
** [[Image:Komodo_Script_Gear.png]] Integrated JSLint with line and character jump!
** [[Image:Komodo_Cog_Go.png]] Quick Commands for even more features like "log" or "ssh"
** [[Image:Komodo_Keyboard.png]] Editable Key Bindings for all important views and commands.
** [[Image:Komodo_Clipboard.png]] ToDo List
** GUI Application Options
*** [[Image:Komodo_Page_White_Text_Edit.png]] Edit Information with quick one click reversion. (appinfo.json)
*** [[Image:Komodo_Cog_20.png]] One click change of log settings. (framework_config.json)
** Sorting of .ipk files into debug and release builds.
** Other
*** Over 100 icons including animated processing icons.
*** Constantly updating with extended features.
*** Extends Komodo macros for more specific functionality.
*** Work side-by-side non webOS Projects.
** Coming Soon
*** [[Image:Komodo_Script_Palette.png]] Beautifier
*** [[Image:Komodo_Bug.png]] Integrated Debugging
 Below are specific installation instructions for the Komodo webOS Add-on. 
|column2=
==Add-On Prerequisites==
* Virtual Box
* The SDK (Palm Software Development Kit. - including the emulator.)
* You need [http://www.activestate.com/komodo_edit/ Komodo Edit v.5.2.x] - Click the "Download Now" button to download it and install. (not covered here.)
}}
==Komodo WebOS Add-on Download==
[http://community.activestate.com/xpi/webos Download the Komodo webOS Add-on from Templarian HERE]
*This is the Add-on you'll need for Palm Pre development. Go to this page and view the link to the file.
* You'll need the .xpi file itself, save into any folder. 
===Komodo WebOS Add-on Install===
* Run Komodo first.
* Then open the folder where you've saved the Add-On .xpi file
* Arrange windows so that you can view them With both Komodo and the Folder open at the same time.
* Drag-and-drop the .xpi into Komodo, to the blank space right of Help on the menu bar, below the blue title bar as shown here (the white icon in this image is the dragged-over .xpi file)
[[Image:Komodo_XPI_Drop.png|frame|none|Dropping the XPI file into Komodo]]
* When you release the dragged-over icon, it will install itself into Komodo.
* Komodo detects the install attempt and shows the Authors Whom You Trust warning.
* You must choose INSTALL NOW button - this is the execution of the install.
[[Image:Komodo_XPI_Install.png|frame|none|Install Screen]]
* You only need to do this once - future upgrades happen automatically from within Komodo Edit, itself.
* Next Komodo should show the completed Add-ons completion screen shown below.
* Choose RESTART KOMODO EDIT button to restart Komodo, for the Add-On to begin running.
[[Image:Komodo_XPI_Restart.png|frame|none|Restart Screen]]
 
===Enable the WebOS Add-On===
* The Komodo WebOS Add-On is disabled by default after install.
* In order to enable it, go into menu item View - and choose WebOS near the bottom.
[[Image:Komodo_Drop_Down.png|frame|none|Enable webOS Tab]] 
===Verify the Install===
* Your finished Komodo should look like the below.
* If you can see the new tab for the Add-On near the bottom section "WebOS", the install worked.
* Some options are disabled (greyed-out) at first if there isn't yet a project open. This is expected.
* Future updates are automatic on startup of Komodo! 
[[Image:Komodo_Tab.png|frame|none|webOS Tab]]
 

==Code Intelligence==
* Next we'll install the "Code Intelligence" add-on, which splashes code suggestions as-you-type.
===Download Code Intelligence===
* [http://www.mediafire.com/?d427teb7apbd7ii Download Code Intelligence] to any local folder
===Install Code Intelligence===
From within Komodo, do menu items:
*Edit
*Preferences
*Code Intelligence
**Add an API CATALOG BUTTON near the bottom-right, and
**Browse to your download folder and Select the .cix file for Code Intelligence.
===Verify Code Intelligence===
* Open any .js file,
* type the word ''' ''them'' '''
* A pop-up should suggest ''' ''theme'' '''
* If you don't see a pop-up, then you may be out of scope try '''Mojo.'''.
* If you see the pop-up, then Code Intelligence is successfully enabled.
[[Image:Komodo_Code_Completion.png|frame|none|Code Completion Test]]
 
==Updates==
* Updates to Komodo WebOS Add-on are detected automatically, but not installed.
* You can also check for them manually
===Install the Update===
[[Image:Komodo_Manual_Update.png|frame|none|Manual Update]] 
* To see available updates and install, do Tools - Add-Ons...
** At the bottom use the FIND UPDATES button
** If an update is found for the webOS Add-on, use the INSTALL UPDATES button.
** At completion of the upgrade, choose RESTART KOMODO EDIT button.
[[Image:Komodo_Update.png|frame|none|Install Update]] 
===Verify===
* In Komodo, do Tools - Add-Ons...
* At the bottom use the FIND UPDATES button again.
* Now, the result should be "no updates were found" - if so, you've successfully updated!

Testing Feeds-DE

2011-09-24T08:51:59Z

Pcworld: added donate links to "Enabling the Beta Testing Feeds" and "Enabling the Alpha Testing Feeds"

Diese Seite ist derzeit in zwei Sprachen verfügbar.
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

=Übergang zu den neuen Alpha und Beta Testing Feeds=

Die alten WebOS Internals Testing Feeds (für Programme und Kernels) wurden durch separate Alpha und Beta Testing Feeds ersetzt. Dafür gibt es eine Menge Gründe:

# Wir wollen die instabilen und im Versuchsstadium begriffenen Alpha Testing Programme von den generell eher harmlosen Beta Testing Programmen trennen. Der alte Testing Feed ließ diese Möglichkeit nicht zu.
#Zu viele Internetseiten haben die direkte URL des Testing Feeds veröffentlicht, ohne die Regel zu nennen, welche auf dieser Seite stehen. Das bedeutet, dass viele Leute die Testing Feeds aktiviert haben ohne die dadurch entstehenden Gefahren zu kennen.
# Es gab eine Menge Programme die während des Ausverkaufs des TouchPads im Testing Feed gelandet waren. Als Ergebnis der großen Aufmerksamkeit dieser wenigen Programme in der Öffentlichkeit haben viele Leute die Testing Feeds nur wegen dieser Programme aktiviert. Diese Programme sind nun in den öffentlichen Feeds von Preware verfügbar, und die Leute sind sich nicht der Risiken bewusst, welche andere Programme des alten Testing Feeds mit sich bringen.

Bitte lies den [[#Testing_Feeds_F.26A|Testing Feeds F&A]] um die Gründe für diese Änderung zu erfahren.

Sowohl der Alpha als auch der Beta Testing Feed haben jeweils vier untergeordnete Feeds: Programme, Kernels, Patches & Optware. Jeder dieser untergeordneten Feeds kann unabhängig von den anderen einzeln aktiviert oder deaktiviert werden.

Der Übergang zu den neuen Alpha und Beta Testing Feeds ist nun auf den Weg gebracht. Preware 1.8.x unterstützt die neuen Alpha und Beta Testing Feeds und die Anleitungen wie diese neuen Feeds aktiviert werden findest du auf dieser Seite. Wenn du die neuen Alpha und Beta Testing Feeds aktivierst werden die veralteten Testing Feeds automatisch aus Preware entfernt.

=Regeln die du akzeptieren musst, bevor du diesen Feed nutzt=
Bevor du unseren Testing Feed nutzen kannst, musst du folgende Regel vollständig lesen und akzeptieren:
[[image:Tux_with_Warning.png|frameless|right]]

# Jeder Teilnehmer am WebOS Internals Alpha- oder Beta-Testing-Programm jeder Art muss damit rechnen, ohne Vorwarnung alle seine Daten löschen und das Betriebssystem per webOS Doctor neu aufspielen zu müssen, ohne es zu bereuen oder sich dabei zu beschweren.
# Du musst bereit sein und auch das nötige Wissen besitzen, um dich in die Kommandozeile auf deinem Gerät einzuloggen und dort Linux Befehle einzugeben, wenn du so angewiesen wirst. Linux Befehle im Voraus zu kennen ist von Vorteil, aber keine Voraussetzung solange du bereit bist es dann zu lernen wenn es nötig ist, oder Anweisungen ohne Fehler zu befolgen.
# Du musst bereit sein sehr viel Zeit zu investieren um die Umstände, die zu Problemen geführt haben, verlässlich zu reproduzieren.
# Du musst vollständige und detaillierte Fehlerbeschreibungen verfassen können, ohne jegliche Details auszulassen, die auch nur im entferntesten mit dem Problem verknüpft sein könnten.
# Du musst jegliche Dokumentationen und Foreneinträge vollständig lesen, bevor du eine Frage stellst.
# Du musst den Threads, in denen das Alpha-Testing von den Autoren diskutiert wird, gewissenhaft folgen, sowie allen Anweisungen präzise Folge leisten.
# Du wirst nie und nirgends den Originallinks zu den Testing Feeds oder diese Anweisungen veröffentlichen, sondern dich immer auf die URL "http://testing.preware.org/" beziehen.
# Wenn du nach Hilfe fragst wird du immer die Phrase "Ich habe die Regeln gelesen" (oder ähnlich abgewandelt) einfügen. Das Fehlen dieser Phrase wird dazu führen, dass deine Anfrage stillschweigend ignoriert wird.

Wenn du nicht bereit bist *ALLE* der oben genannten Regel mit gutem Gewissen zu befolgen, dann warte bitte auf die öffentliche Erscheinung der Programme/Patches in den normalen Feeds von Preware.

Wenn du bereit bist *alle* oben genannten Regel zu befolgen, dann sei herzlich dazu eingeladen am Alpha- oder Beta-Testing teilzuhaben.

Beachte, dass all diese Regeln eher eine Frage deiner Einstellung als deiner Fähigkeiten sind.

= Alleinige Nutzung von sicheren, stabilen Feeds =

Wenn du einer der Personen bist, die durch Artikel oder Foreneinträge angewiesen wurden, die Testing Feeds zu nutzen, aber du nichts wirklich testest, dann solltest du das folgende tun, um in Preware nur sichere, stabile Feeds zu nutzen:
* Öffne Preware
* Öffne das App-Menu -> Feeds verwalten
* Lösche jeden Eintrag durch Wischen, der das Wort "testing" auch nur irgendwo im Namen enthält

Beachte, dass dies nur Pakete betrifft, die du noch nicht auf deinem Gerät installiert hast.

Nachdem du dies getan hast, und du willst nur die sicheren, stabilen Feeds beibehalten, kannst du hier aufhören. Dann ist nämlich der Rest dieser Seite nicht relevant für dich, und du solltest nach diesem Abschnitt sonst nichts tun, was hier noch beschrieben wird.

= Beta Testing Feeds aktivieren =

Beta Packages wurden bereits teilweise getestet, können in seltenen Fällen aber dennoch deine Daten löschen oder dein Gerät unbrauchbar machen. Du wurdest gewarnt. Wenn du nicht explizit eine Beta-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Beta-Package aktualisieren oder installieren willst.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um die Beta-Feeds zu aktivieren, musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Beta-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.
* Spende WebOS Internals: http://donate.webos-internals.org/ und http://bit.ly/phd-ac

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Beta-Feeds deaktivieren =
Um temporär die Beta-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Beta-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Lösche im "Feeds verwalten"-Dialog alle beta-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-beta-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Beta-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Alpha Testing Feeds aktivieren =

Alpha-Packages wurden wenig bis gar nicht getestet, und es besteht eine große Gefahr Daten zu verlieren, dein Profil zu zerstören und möglicherweise dein Gerät unbrauchbar zu machen. Pakete im Alpha-Feed *werden* regelmäßig etwas kaputt machen (vielleicht sogar absichtlich). Du wurdest gewarnt. Wenn du nicht explizit eine Alpha-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Alpha-Package aktualisieren oder installieren willst.

Im Allgemeinen werden nur sehr sehr sehr wenige Personen erwartet, die Alpha Testing Feeds zu aktivieren. Die größte Mehrheit der User sollte höchstens den Beta Testing Feed verwenden.

Der Beta-Testing Feed und der Alpha-Testing Feed können beide zeitgleich aktiv sein, wenn gewünscht.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um den Alpha-Testing Feed zu aktivieren musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Alpha-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.
* Spende WebOS Internals: http://donate.webos-internals.org/ und http://bit.ly/phd-ac

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Alpha-Feeds deaktivieren =
Um temporär die Alpha-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Alpha-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Lösche im "Feeds verwalten"-Dialog alle alpha-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-alpha-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Alpha-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Testing Feeds F&A =

'''F: Wer sollte die Alpha-Testing Feeds nutzen?'''

A: Wenn du diese Frage stellst, solltest du den Feed nicht aktivieren. Nur sehr sehr sehr sehr wenige Personen sollten die Alpha-Testing Feeds jemals aktivieren. Wenn du kein GIT Repository gecloned hast und Code bearbeitest, sollten du den Feed nicht aktivieren.

'''F: Wer sollte den Beta-Testing Feed nutzen?'''

A: Jeder darf den Beta-Testing Feed benutzen, wenn er mit den Regeln vollständig einverstanden ist, und genau weiß warum er den Beta-Testing Feed verwendet (und z. B. nicht einfach blind irgendwelchen Anleitungen in Artikeln oder Foren folgt)

'''F: Warum benötigt die Aktivierung der Feeds eine Verbindung zu meinem Computer?'''

A: Wenn du die Testing-Feeds zum ersten mal aktivierst, wollen wir sicherstellen dass du in der Lage bist dein Gerät mit einem PC zu verbinden, um Fehler finden zu können und dein Gerät wiederherzustellen wenn etwas schief geht.

'''F: Warum benötigt die Aktivierung der Feeds eine Neuinstallation von Preware?'''

A: Die Feeds werden erstellt wenn Preware installiert wird. Deshalb musst du Preware reinstallieren, dass die Feeds auf deinem Gerät erstellt werden.

'''F: Warum benötigt die Aktivierung der Feeds die Nutzung der Linux Kommandozeile?'''

A: Um ein erfolgreicher Tester zu sein, musst du in der Lage sein auf dein Gerät über die Linux Kommandozeile zuzugreifen um Debug-Infomationen liefern zu können. Wir stellen so sicher dass du das kannst, bevor du auf die Feeds zugreifen kannst.

'''F: Warum kann ich nicht einfach die Feeds-URLs direkt eingeben?'''

A: Zu viele User verwenden die falschen Feed-Namen oder Feed-URLs, daher haben wir diese Möglichkeit entfernt.

'''F: Warum darf ich die Anleitungen nicht einfach auf meinem Blog oder einem Forum veröffentlichen?'''

A: Zu viele Leute veröffentlichten die URLs ohne die dazugehörigen Regeln und Warnungen. Dies ist nun strengstens verboten.

'''F: Wofür werden die Alpha-Patches und Beta-Patches Feeds verwendet?'''

A: Der Alpha-Patches Feed wird zum Testen der AUTP-Scripte genutzt werden, welche in der Lage sind Dateien in <code>/media/cryptofs/apps/</code> zu patchen (Dateien, die nicht in <code>/md5sums</code> enthalten sind). Sobald das funktioniert, werden wir den Beta-Patch Feed verwenden um alle Patches zu upgraden, die neue AUPT-Scripts zu nutzen und diese anschließend im Beta-Stadium zu testen.

Application:Xecutah-DE

2011-09-19T17:48:13Z

Pcworld: /* Zusammenfassung */ fixed spelling

[[Category:Application]]
Diese Seite ist derzeit in zwei Sprachen verfügbar.
: [[Image:Australia.png]] [[Image:USA.png]] [[Application:Xecutah]]
: [[Image:Germany.png]] [[Application:Xecutah-DE]]

{{application
| name=Xecutah
| type=webOS
| version=Version: 0.9.0 (16. September 2011)
| tag=Utilities
| screenshot=Xecutah_ss1.png
| description=
}}

 
== Zusammenfassung ==

[[image:X.png|frameless|left]]

Xecutah ermöglicht es ein X Windows System Server in einer webOS Karte zu starten und dort andere X Applikationen auszuführen. Dieses Programm ist verfügbar für Pre, Pixi, Palm Pre2 Veer and TouchPad (mit webOS Versoin 3.0.2).

'''Xecutah benötigt webOS 1.4.0 oder höher zur Ausführung. Versuch es nicht in einer früheren Version
von webOS zu installieren. Es wird nicht funktionieren.'''
 

=== wichtigste Eigenschaften ===

=== zugehörige Pakete ===

* XServer - Wird benötigt um X Window Programme unter webOS auszuführen
* XTerm - Wird benötigt um eine Linux Kommandoeile unter webOS bereit zustellen.
* Ubuntu Chroot - Ermöglicht eine chroot installation für Ubuntu OS
* Debian Chroot - Ermöglicht eine chroot installation für Debian OS

 
=== Status ===
Xecutah wurde erweitert und hat nun den Beta Status verlassen.
Experimentelle Updates sind im [http://testing.preware.org Testing Feed] zu finden. Die dort zur Verfügung gestellten Pakete sind Beta Versionen und laufen möglicherweise instabil.
 

== Xecutah installieren ==

#Öffne [http://www.webos-internals.org/wiki/Application:Preware-DE Preware].
#Warte bis Preware die Feeds aktualisiert hat.
#Tippe Xecutah (die Buchstaben werden oben im Header dargestellt, um anzuzeigen, dass du eine Suche startest).
#Drücke Enter.
#Drücke auf Installieren am unteren Ende des Bildschirms.
 

== Benutzung ==
=== Hauptbildschirm ===
{| Width="70%" VAlign="top"
| valign="top"|[[image:Xecutah_Main.png|160px|frameless|left|text-top]]
| valign="top"|Du kannst hier auswählen welche X-Applikation du ausführen möchtest.
 
| valign="top"|Du musst den XServer immer zuerst starten bevor du weitere Programme starten kannst.
|}

 
=== Einstellungen ===
{| Width="70%" VAlign="top"
| valign="top"|[[image:Xecutah_Pref.png|160px|frameless|left|text-top]]
| valign="top"|Im Hauptbildschirm in der linken oberen Ecke befindet sich das Menü. Dort gibt es einen Eintrag Preferences (Einstellungen). Im Einstellungsmenü kannst du das Aussehen von Xecutah einstellen. Derzeit gibt es die Einstellungen Palm Default und Palm Dark (dunkel).
|}

=== bekannte Fehler ===

*Derzeit keine Unterstützung für die ESC Taste

 
== Änderungen ==
 
Für die Interessierten, die Liste der Veränderungen ist [http://git.webos-internals.org/applications/xecutah/refs/tags hier zu finden (engl.)].
Unterhalb ist eine Liste der Änderungen seit der Vorstellung im öffentlichen Feed.
 

; 0.9.0
* öffentliche Vorstellung

 

== Repository ==
Xecutah ist in der applications/Xecutah git repository unter http://git.webos-internals.org/ zu finden.

 
=== Lizens ===
Bitte beachte, dass org.webosinternals.xecutah nach [http://www.gnu.org/licenses/gpl-2.0.html GPLv2] lizensiert ist.

Der Quellcode von Xecutah darf nicht für eine Closed Source Applikation verwendet werden. Wenn du den Quellcode in einer Form anders als GPLv2, aber trotzdem Open Source nutzen möchtest kontaktiere bitte die [mailto:support@webos-internals.org Autoren (Englisch bitte)].

Testing Feeds-DE

2011-09-19T17:46:13Z

Pcworld: /* Alleinige Nutzung von sicheren, stabilen Feeds */ +"Note that this does not affect any packages that you have already installed on your device"

Diese Seite ist derzeit in zwei Sprachen verfügbar.
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

=Übergang zu den neuen Alpha und Beta Testing Feeds=

Die alten WebOS Internals Testing Feeds (für Programme und Kernels) wurden durch separate Alpha und Beta Testing Feeds ersetzt. Dafür gibt es eine Menge Gründe:

# Wir wollen die instabilen und im Versuchsstadium begriffenen Alpha Testing Programme von den generell eher harmlosen Beta Testing Programmen trennen. Der alte Testing Feed ließ diese Möglichkeit nicht zu.
#Zu viele Internetseiten haben die direkte URL des Testing Feeds veröffentlicht, ohne die Regel zu nennen, welche auf dieser Seite stehen. Das bedeutet, dass viele Leute die Testing Feeds aktiviert haben ohne die dadurch entstehenden Gefahren zu kennen.
# Es gab eine Menge Programme die während des Ausverkaufs des TouchPads im Testing Feed gelandet waren. Als Ergebnis der großen Aufmerksamkeit dieser wenigen Programme in der Öffentlichkeit haben viele Leute die Testing Feeds nur wegen dieser Programme aktiviert. Diese Programme sind nun in den öffentlichen Feeds von Preware verfügbar, und die Leute sind sich nicht der Risiken bewusst, welche andere Programme des alten Testing Feeds mit sich bringen.

Bitte lies den [[#Testing_Feeds_F.26A|Testing Feeds F&A]] um die Gründe für diese Änderung zu erfahren.

Sowohl der Alpha als auch der Beta Testing Feed haben jeweils vier untergeordnete Feeds: Programme, Kernels, Patches & Optware. Jeder dieser untergeordneten Feeds kann unabhängig von den anderen einzeln aktiviert oder deaktiviert werden.

Der Übergang zu den neuen Alpha und Beta Testing Feeds ist nun auf den Weg gebracht. Preware 1.8.x unterstützt die neuen Alpha und Beta Testing Feeds und die Anleitungen wie diese neuen Feeds aktiviert werden findest du auf dieser Seite. Wenn du die neuen Alpha und Beta Testing Feeds aktivierst werden die veralteten Testing Feeds automatisch aus Preware entfernt.

=Regeln die du akzeptieren musst, bevor du diesen Feed nutzt=
Bevor du unseren Testing Feed nutzen kannst, musst du folgende Regel vollständig lesen und akzeptieren:
[[image:Tux_with_Warning.png|frameless|right]]

# Jeder Teilnehmer am WebOS Internals Alpha- oder Beta-Testing-Programm jeder Art muss damit rechnen, ohne Vorwarnung alle seine Daten löschen und das Betriebssystem per webOS Doctor neu aufspielen zu müssen, ohne es zu bereuen oder sich dabei zu beschweren.
# Du musst bereit sein und auch das nötige Wissen besitzen, um dich in die Kommandozeile auf deinem Gerät einzuloggen und dort Linux Befehle einzugeben, wenn du so angewiesen wirst. Linux Befehle im Voraus zu kennen ist von Vorteil, aber keine Voraussetzung solange du bereit bist es dann zu lernen wenn es nötig ist, oder Anweisungen ohne Fehler zu befolgen.
# Du musst bereit sein sehr viel Zeit zu investieren um die Umstände, die zu Problemen geführt haben, verlässlich zu reproduzieren.
# Du musst vollständige und detaillierte Fehlerbeschreibungen verfassen können, ohne jegliche Details auszulassen, die auch nur im entferntesten mit dem Problem verknüpft sein könnten.
# Du musst jegliche Dokumentationen und Foreneinträge vollständig lesen, bevor du eine Frage stellst.
# Du musst den Threads, in denen das Alpha-Testing von den Autoren diskutiert wird, gewissenhaft folgen, sowie allen Anweisungen präzise Folge leisten.
# Du wirst nie und nirgends den Originallinks zu den Testing Feeds oder diese Anweisungen veröffentlichen, sondern dich immer auf die URL "http://testing.preware.org/" beziehen.
# Wenn du nach Hilfe fragst wird du immer die Phrase "Ich habe die Regeln gelesen" (oder ähnlich abgewandelt) einfügen. Das Fehlen dieser Phrase wird dazu führen, dass deine Anfrage stillschweigend ignoriert wird.

Wenn du nicht bereit bist *ALLE* der oben genannten Regel mit gutem Gewissen zu befolgen, dann warte bitte auf die öffentliche Erscheinung der Programme/Patches in den normalen Feeds von Preware.

Wenn du bereit bist *alle* oben genannten Regel zu befolgen, dann sei herzlich dazu eingeladen am Alpha- oder Beta-Testing teilzuhaben.

Beachte, dass all diese Regeln eher eine Frage deiner Einstellung als deiner Fähigkeiten sind.

= Alleinige Nutzung von sicheren, stabilen Feeds =

Wenn du einer der Personen bist, die durch Artikel oder Foreneinträge angewiesen wurden, die Testing Feeds zu nutzen, aber du nichts wirklich testest, dann solltest du das folgende tun, um in Preware nur sichere, stabile Feeds zu nutzen:
* Öffne Preware
* Öffne das App-Menu -> Feeds verwalten
* Lösche jeden Eintrag durch Wischen, der das Wort "testing" auch nur irgendwo im Namen enthält

Beachte, dass dies nur Pakete betrifft, die du noch nicht auf deinem Gerät installiert hast.

Nachdem du dies getan hast, und du willst nur die sicheren, stabilen Feeds beibehalten, kannst du hier aufhören. Dann ist nämlich der Rest dieser Seite nicht relevant für dich, und du solltest nach diesem Abschnitt sonst nichts tun, was hier noch beschrieben wird.

= Beta Testing Feeds aktivieren =

Beta Packages wurden bereits teilweise getestet, können in seltenen Fällen aber dennoch deine Daten löschen oder dein Gerät unbrauchbar machen. Du wurdest gewarnt. Wenn du nicht explizit eine Beta-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Beta-Package aktualisieren oder installieren willst.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um die Beta-Feeds zu aktivieren, musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Beta-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Beta-Feeds deaktivieren =
Um temporär die Beta-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Beta-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Lösche im "Feeds verwalten"-Dialog alle beta-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-beta-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Beta-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Alpha Testing Feeds aktivieren =

Alpha-Packages wurden wenig bis gar nicht getestet, und es besteht eine große Gefahr Daten zu verlieren, dein Profil zu zerstören und möglicherweise dein Gerät unbrauchbar zu machen. Pakete im Alpha-Feed *werden* regelmäßig etwas kaputt machen (vielleicht sogar absichtlich). Du wurdest gewarnt. Wenn du nicht explizit eine Alpha-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Alpha-Package aktualisieren oder installieren willst.

Im Allgemeinen werden nur sehr sehr sehr wenige Personen erwartet, die Alpha Testing Feeds zu aktivieren. Die größte Mehrheit der User sollte höchstens den Beta Testing Feed verwenden.

Der Beta-Testing Feed und der Alpha-Testing Feed können beide zeitgleich aktiv sein, wenn gewünscht.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um den Alpha-Testing Feed zu aktivieren musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Alpha-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Alpha-Feeds deaktivieren =
Um temporär die Alpha-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Alpha-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Lösche im "Feeds verwalten"-Dialog alle alpha-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-alpha-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Alpha-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Testing Feeds F&A =

'''F: Wer sollte die Alpha-Testing Feeds nutzen?'''

A: Wenn du diese Frage stellst, solltest du den Feed nicht aktivieren. Nur sehr sehr sehr sehr wenige Personen sollten die Alpha-Testing Feeds jemals aktivieren. Wenn du kein GIT Repository gecloned hast und Code bearbeitest, sollten du den Feed nicht aktivieren.

'''F: Wer sollte den Beta-Testing Feed nutzen?'''

A: Jeder darf den Beta-Testing Feed benutzen, wenn er mit den Regeln vollständig einverstanden ist, und genau weiß warum er den Beta-Testing Feed verwendet (und z. B. nicht einfach blind irgendwelchen Anleitungen in Artikeln oder Foren folgt)

'''F: Warum benötigt die Aktivierung der Feeds eine Verbindung zu meinem Computer?'''

A: Wenn du die Testing-Feeds zum ersten mal aktivierst, wollen wir sicherstellen dass du in der Lage bist dein Gerät mit einem PC zu verbinden, um Fehler finden zu können und dein Gerät wiederherzustellen wenn etwas schief geht.

'''F: Warum benötigt die Aktivierung der Feeds eine Neuinstallation von Preware?'''

A: Die Feeds werden erstellt wenn Preware installiert wird. Deshalb musst du Preware reinstallieren, dass die Feeds auf deinem Gerät erstellt werden.

'''F: Warum benötigt die Aktivierung der Feeds die Nutzung der Linux Kommandozeile?'''

A: Um ein erfolgreicher Tester zu sein, musst du in der Lage sein auf dein Gerät über die Linux Kommandozeile zuzugreifen um Debug-Infomationen liefern zu können. Wir stellen so sicher dass du das kannst, bevor du auf die Feeds zugreifen kannst.

'''F: Warum kann ich nicht einfach die Feeds-URLs direkt eingeben?'''

A: Zu viele User verwenden die falschen Feed-Namen oder Feed-URLs, daher haben wir diese Möglichkeit entfernt.

'''F: Warum darf ich die Anleitungen nicht einfach auf meinem Blog oder einem Forum veröffentlichen?'''

A: Zu viele Leute veröffentlichten die URLs ohne die dazugehörigen Regeln und Warnungen. Dies ist nun strengstens verboten.

'''F: Wofür werden die Alpha-Patches und Beta-Patches Feeds verwendet?'''

A: Der Alpha-Patches Feed wird zum Testen der AUTP-Scripte genutzt werden, welche in der Lage sind Dateien in <code>/media/cryptofs/apps/</code> zu patchen (Dateien, die nicht in <code>/md5sums</code> enthalten sind). Sobald das funktioniert, werden wir den Beta-Patch Feed verwenden um alle Patches zu upgraden, die neue AUPT-Scripts zu nutzen und diese anschließend im Beta-Stadium zu testen.

Testing Feeds

2011-09-18T12:20:40Z

Pcworld: /* Disabling the Beta Feeds */ fixed formatting

This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

=Migration to the Alpha and Beta Testing Feeds=

The old WebOS Internals Testing Feeds (for applications and kernels) have been replaced by separate Alpha and Beta testing feeds. There are a number of reasons for this change:

# We needed to separate out bleeding-edge unstable alpha testing packages from generally benign beta testing packages. The old testing feeds did not allow this distinction.
# Too many sites have published the raw testing feed URLs without referencing the rules below, which means many people have the old testing feeds enabled without understanding the risks associated with doing so.
# There were a number of packages which were caught in the old testing feeds when the TouchPad fire sale happened, and as a result of the publicity surrounding those packages many people have the old testing feeds enabled just for those packages (which have since been promoted to the public feeds) and are not aware of the risks associated with other packages which they may be presented with via those old testing feeds.

Please read the [http://www.webos-internals.org/wiki/Testing_Feeds#Testing_Feeds_Q.26A Testing Feeds Q&A] for more information about the rationale for this change.

Each of the Alpha and Beta testing feeds has four sub-feeds: Apps, Kernels, Patches & Optware. Each of these sub-feeds can be enabled or disabled independently.

Transition to the new Alpha and Beta testing feeds is now complete. Preware 1.8.x now supports the new Alpha and Beta testing feeds, and instructions on how to enable the new feeds are on this page. When you enable the new Alpha or Beta testing feeds, the old obsolete testing feeds are automatically removed from your Preware configuration.

=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 or beta 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.
# They will never post the raw testing feed URLs or instructions anywhere, but will always refer others directly to this page using only the URL "http://testing.preware.org/"
# When asking for help, they will include the phrase (which may change occasionally) "I've read the rules". Failure to include the phrase will result in the request for help being silently ignored.

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 or beta testing.

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

=How to only use safe stable feeds=

If you are one of the people who were told to use testing feeds by some article or forum post, but are really not actively testing anything, then you should do the following to revert your Preware configuration to only using safe stable feeds:

# Open Preware
# Go to the Manage Feeds page
# Swipe to delete any feed which has "testing" anywhere in the name

If you have done this, and want to stick with safe stable feeds only, you can stop here. The rest of this page is not relevant to you and you should not do anything else on this page after this point.

= Enabling the Beta Testing Feeds =

Beta quality packages have had some end-user testing, but may still delete your data or wipe your device in rare circumstances. You have been warned. Unless you are directly and specifically beta testing a package, you should disable all beta feeds at all times other than when you are explicitly updating or installing a beta package.

[http://www.webos-internals.org/wiki/Testing_Feeds#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]

[http://www.webos-internals.org/wiki/Testing_Feeds#Testing_Feeds_Q.26A It is also wise to read all of the Q&A before continuing.]

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

To enable the beta testing feeds, you must do the following:

:1. Uninstall Preware. Yes, seriously. You must uninstall Preware. This will not affect any other packages that you have installed.

:2. Gain access to the Linux command line on your device and run the following two commands. If you do not already know how to do this using novaterm or Xecutah, or cannot find out how to do this using Google, then you should not be beta testing.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-beta-feeds

:3. Install Preware 1.8.3 or later.

:4. Start Preware, open the Manage Feeds screen, and enable *only* those feeds which you wish to use. Before enabling a kernel testing feed, you should [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ read this].

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

=Disabling the Beta Feeds=

To temporarily disable the beta feeds, simply set the toggle switch in the Preware Manage Feeds screen to Off for each feed.

To permanently disable the beta feeds, you must do the following:

:1. Gain access to the Linux command line on your device and run the command.
rm -f /var/preferences/org.webosinternals.preware/enable-beta-feeds

:2. Swipe to delete all the beta-* feeds in the Preware Manage Feeds screen.

Note that if you do not remove the <code>enable-beta-feeds</code> file, the beta feeds will reappear the next time you install a new version of Preware.

= Enabling the Alpha Testing Feeds =

Alpha quality packages have had little or no end-user testing, and are likely to delete your data, wipe your device and profile, and potentially damage your device. Packages in the alpha feed *will* regularly break (perhaps even intentionally). You have been warned. Unless you are directly and specifically alpha testing a package, you should disable all alpha feeds at all times other than when you are explicitly updating or installing an alpha package.

In general, very very very very few users would be expected to enable the Alpha testing feeds. The large majority of users should only ever use the Beta testing feeds.

The Beta testing feeds and the Alpha testing feeds can both be enabled at the same time if desired.

[http://www.webos-internals.org/wiki/Testing_Feeds#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]

[http://www.webos-internals.org/wiki/Testing_Feeds#Testing_Feeds_Q.26A It is also wise to read all of the Q&A before continuing.]

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

To enable the alpha testing feeds, you must do the following:

:1. Uninstall Preware. Yes, seriously. You must uninstall Preware. This will not affect any other packages that you have installed.

:2. Gain access to the Linux command line on your device and run the following two commands. If you do not already know how to do this using novaterm or Xecutah, or cannot find out how to do this using Google, then you should not be alpha testing.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-alpha-feeds

:3. Install Preware 1.8.3 or later.

:4. Start Preware, open the Manage Feeds screen, and enable *only* those feeds which you wish to use. Before enabling a kernel testing feed, you should [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ read this].

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

=Disabling the Alpha Feeds=

To temporarily disable the alpha feeds, simply set the toggle switch in the Preware Manage Feeds screen to Off for each feed.

To permanently disable the alpha feeds, you must do the following:

:1. Gain access to the Linux command line on your device and run the following command.
rm -f /var/preferences/org.webosinternals.preware/enable-alpha-feeds

:2. Swipe to delete all the alpha-* feeds in the Preware Manage Feeds screen.

Note that if you do not remove the <code>enable-alpha-feeds</code> file, the alpha feeds will reappear the next time you install a new version of Preware.

=Testing Feeds Q&A=

'''Q: Who should use the Alpha testing feeds?'''

A: If you're asking that question, then you should not be using the Alpha testing feeds. Very very very very very few people should ever enable the Alpha testing feeds. Unless you have a git repository cloned and are editing code, you should not enable the Alpha testing feeds.

'''Q: Who should use the Beta testing feeds?'''

A: Anyone is welcome to use the Beta testing feeds, as long as they comply fully with the rules and know exactly why they are using a Beta testing feed (i.e. they are not just blindly following some instructions in some article or forum post somewhere).

'''Q: Why does enabling the feeds require connecting my device to a computer?'''

A: When you are enabling testing feeds for the first time, we want to ensure that you are able to connect to your device from a computer to assist in debugging the things you are testing, or to be able to recover your device if something goes wrong.

'''Q: Why does enabling the feeds require reinstalling Preware?'''

A: The feeds are actually created when Preware is installed, so you need to reinstall Preware for the feeds to be created on your device.

'''Q: Why does enabling the feeds require the use of the Linux command line?'''

A: To be an effective tester, you need to be able to access your device on the Linux command line to provide debugging information. We ensure that you can do that before you are able to access the feeds.

'''Q: Why can't I just enter in the feed URLs directly?'''

A: Too many people got the feed names or feed URLs wrong, so we took those things out of the equation.

'''Q: Why can't I publish the instructions on my blog or website or forum post?'''

A: Too many people were publishing the URLs without the corresponding rules and warnings. This is now strictly forbidden.

'''Q: What are the alpha-patches and beta-patches feeds going to be used for?'''

A: The alpha-patches feed will be used for testing new AUPT scripts which will be able to handle patching files in <code>/media/cryptofs/apps/</code> (files not inside <code>/md5sums</code>). Once that is working, we'll use the beta-patches feed to do a complete upgrade of all patches to use the new AUPT scripts and then beta test those.

Testing Feeds

2011-09-18T12:19:47Z

Pcworld: corrected minor content issues; formatting; Q&A: +md5sums file notice

This page is currently available in two languages:
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

=Migration to the Alpha and Beta Testing Feeds=

The old WebOS Internals Testing Feeds (for applications and kernels) have been replaced by separate Alpha and Beta testing feeds. There are a number of reasons for this change:

# We needed to separate out bleeding-edge unstable alpha testing packages from generally benign beta testing packages. The old testing feeds did not allow this distinction.
# Too many sites have published the raw testing feed URLs without referencing the rules below, which means many people have the old testing feeds enabled without understanding the risks associated with doing so.
# There were a number of packages which were caught in the old testing feeds when the TouchPad fire sale happened, and as a result of the publicity surrounding those packages many people have the old testing feeds enabled just for those packages (which have since been promoted to the public feeds) and are not aware of the risks associated with other packages which they may be presented with via those old testing feeds.

Please read the [http://www.webos-internals.org/wiki/Testing_Feeds#Testing_Feeds_Q.26A Testing Feeds Q&A] for more information about the rationale for this change.

Each of the Alpha and Beta testing feeds has four sub-feeds: Apps, Kernels, Patches & Optware. Each of these sub-feeds can be enabled or disabled independently.

Transition to the new Alpha and Beta testing feeds is now complete. Preware 1.8.x now supports the new Alpha and Beta testing feeds, and instructions on how to enable the new feeds are on this page. When you enable the new Alpha or Beta testing feeds, the old obsolete testing feeds are automatically removed from your Preware configuration.

=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 or beta 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.
# They will never post the raw testing feed URLs or instructions anywhere, but will always refer others directly to this page using only the URL "http://testing.preware.org/"
# When asking for help, they will include the phrase (which may change occasionally) "I've read the rules". Failure to include the phrase will result in the request for help being silently ignored.

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 or beta testing.

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

=How to only use safe stable feeds=

If you are one of the people who were told to use testing feeds by some article or forum post, but are really not actively testing anything, then you should do the following to revert your Preware configuration to only using safe stable feeds:

# Open Preware
# Go to the Manage Feeds page
# Swipe to delete any feed which has "testing" anywhere in the name

If you have done this, and want to stick with safe stable feeds only, you can stop here. The rest of this page is not relevant to you and you should not do anything else on this page after this point.

= Enabling the Beta Testing Feeds =

Beta quality packages have had some end-user testing, but may still delete your data or wipe your device in rare circumstances. You have been warned. Unless you are directly and specifically beta testing a package, you should disable all beta feeds at all times other than when you are explicitly updating or installing a beta package.

[http://www.webos-internals.org/wiki/Testing_Feeds#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]

[http://www.webos-internals.org/wiki/Testing_Feeds#Testing_Feeds_Q.26A It is also wise to read all of the Q&A before continuing.]

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

To enable the beta testing feeds, you must do the following:

:1. Uninstall Preware. Yes, seriously. You must uninstall Preware. This will not affect any other packages that you have installed.

:2. Gain access to the Linux command line on your device and run the following two commands. If you do not already know how to do this using novaterm or Xecutah, or cannot find out how to do this using Google, then you should not be beta testing.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-beta-feeds

:3. Install Preware 1.8.3 or later.

:4. Start Preware, open the Manage Feeds screen, and enable *only* those feeds which you wish to use. Before enabling a kernel testing feed, you should [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ read this].

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

=Disabling the Beta Feeds=

To temporarily disable the beta feeds, simply set the toggle switch in the Preware Manage Feeds screen to Off for each feed.

To permanently disable the beta feeds, you must do the following:

:1. Gain access to the Linux command line on your device and run the command.
rm -f /var/preferences/org.webosinternals.preware/enable-beta-feeds

:2. Swipe to delete all the beta-* feeds in the Preware Manage Feeds screen.

Note that if you do not remove the <code>enable-beta-feeds file</code>, the beta feeds will reappear the next time you install a new version of Preware.

= Enabling the Alpha Testing Feeds =

Alpha quality packages have had little or no end-user testing, and are likely to delete your data, wipe your device and profile, and potentially damage your device. Packages in the alpha feed *will* regularly break (perhaps even intentionally). You have been warned. Unless you are directly and specifically alpha testing a package, you should disable all alpha feeds at all times other than when you are explicitly updating or installing an alpha package.

In general, very very very very few users would be expected to enable the Alpha testing feeds. The large majority of users should only ever use the Beta testing feeds.

The Beta testing feeds and the Alpha testing feeds can both be enabled at the same time if desired.

[http://www.webos-internals.org/wiki/Testing_Feeds#Rules_that_you_must_agree_to_before_using_these_feeds Re-read the rules above before continuing.]

[http://www.webos-internals.org/wiki/Testing_Feeds#Testing_Feeds_Q.26A It is also wise to read all of the Q&A before continuing.]

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

To enable the alpha testing feeds, you must do the following:

:1. Uninstall Preware. Yes, seriously. You must uninstall Preware. This will not affect any other packages that you have installed.

:2. Gain access to the Linux command line on your device and run the following two commands. If you do not already know how to do this using novaterm or Xecutah, or cannot find out how to do this using Google, then you should not be alpha testing.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-alpha-feeds

:3. Install Preware 1.8.3 or later.

:4. Start Preware, open the Manage Feeds screen, and enable *only* those feeds which you wish to use. Before enabling a kernel testing feed, you should [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ read this].

'''''You must never repost or copy or rewrite these instructions anywhere else, but must always refer others directly to this page using only the URL "http://testing.preware.org/"'''''

=Disabling the Alpha Feeds=

To temporarily disable the alpha feeds, simply set the toggle switch in the Preware Manage Feeds screen to Off for each feed.

To permanently disable the alpha feeds, you must do the following:

:1. Gain access to the Linux command line on your device and run the following command.
rm -f /var/preferences/org.webosinternals.preware/enable-alpha-feeds

:2. Swipe to delete all the alpha-* feeds in the Preware Manage Feeds screen.

Note that if you do not remove the <code>enable-alpha-feeds</code> file, the alpha feeds will reappear the next time you install a new version of Preware.

=Testing Feeds Q&A=

'''Q: Who should use the Alpha testing feeds?'''

A: If you're asking that question, then you should not be using the Alpha testing feeds. Very very very very very few people should ever enable the Alpha testing feeds. Unless you have a git repository cloned and are editing code, you should not enable the Alpha testing feeds.

'''Q: Who should use the Beta testing feeds?'''

A: Anyone is welcome to use the Beta testing feeds, as long as they comply fully with the rules and know exactly why they are using a Beta testing feed (i.e. they are not just blindly following some instructions in some article or forum post somewhere).

'''Q: Why does enabling the feeds require connecting my device to a computer?'''

A: When you are enabling testing feeds for the first time, we want to ensure that you are able to connect to your device from a computer to assist in debugging the things you are testing, or to be able to recover your device if something goes wrong.

'''Q: Why does enabling the feeds require reinstalling Preware?'''

A: The feeds are actually created when Preware is installed, so you need to reinstall Preware for the feeds to be created on your device.

'''Q: Why does enabling the feeds require the use of the Linux command line?'''

A: To be an effective tester, you need to be able to access your device on the Linux command line to provide debugging information. We ensure that you can do that before you are able to access the feeds.

'''Q: Why can't I just enter in the feed URLs directly?'''

A: Too many people got the feed names or feed URLs wrong, so we took those things out of the equation.

'''Q: Why can't I publish the instructions on my blog or website or forum post?'''

A: Too many people were publishing the URLs without the corresponding rules and warnings. This is now strictly forbidden.

'''Q: What are the alpha-patches and beta-patches feeds going to be used for?'''

A: The alpha-patches feed will be used for testing new AUPT scripts which will be able to handle patching files in <code>/media/cryptofs/apps/</code> (files not inside <code>/md5sums</code>). Once that is working, we'll use the beta-patches feed to do a complete upgrade of all patches to use the new AUPT scripts and then beta test those.

Testing Feeds-DE

2011-09-18T12:16:17Z

Pcworld: /* Regeln die du akzeptieren musst, bevor du diesen Feed nutzt */ removed double

Diese Seite ist derzeit in zwei Sprachen verfügbar.
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

=Übergang zu den neuen Alpha und Beta Testing Feeds=

Die alten WebOS Internals Testing Feeds (für Programme und Kernels) wurden durch separate Alpha und Beta Testing Feeds ersetzt. Dafür gibt es eine Menge Gründe:

# Wir wollen die instabilen und im Versuchsstadium begriffenen Alpha Testing Programme von den generell eher harmlosen Beta Testing Programmen trennen. Der alte Testing Feed ließ diese Möglichkeit nicht zu.
#Zu viele Internetseiten haben die direkte URL des Testing Feeds veröffentlicht, ohne die Regel zu nennen, welche auf dieser Seite stehen. Das bedeutet, dass viele Leute die Testing Feeds aktiviert haben ohne die dadurch entstehenden Gefahren zu kennen.
# Es gab eine Menge Programme die während des Ausverkaufs des TouchPads im Testing Feed gelandet waren. Als Ergebnis der großen Aufmerksamkeit dieser wenigen Programme in der Öffentlichkeit haben viele Leute die Testing Feeds nur wegen dieser Programme aktiviert. Diese Programme sind nun in den öffentlichen Feeds von Preware verfügbar, und die Leute sind sich nicht der Risiken bewusst, welche andere Programme des alten Testing Feeds mit sich bringen.

Bitte lies den [[#Testing_Feeds_F.26A|Testing Feeds F&A]] um die Gründe für diese Änderung zu erfahren.

Sowohl der Alpha als auch der Beta Testing Feed haben jeweils vier untergeordnete Feeds: Programme, Kernels, Patches & Optware. Jeder dieser untergeordneten Feeds kann unabhängig von den anderen einzeln aktiviert oder deaktiviert werden.

Der Übergang zu den neuen Alpha und Beta Testing Feeds ist nun auf den Weg gebracht. Preware 1.8.x unterstützt die neuen Alpha und Beta Testing Feeds und die Anleitungen wie diese neuen Feeds aktiviert werden findest du auf dieser Seite. Wenn du die neuen Alpha und Beta Testing Feeds aktivierst werden die veralteten Testing Feeds automatisch aus Preware entfernt.

=Regeln die du akzeptieren musst, bevor du diesen Feed nutzt=
Bevor du unseren Testing Feed nutzen kannst, musst du folgende Regel vollständig lesen und akzeptieren:
[[image:Tux_with_Warning.png|frameless|right]]

# Jeder Teilnehmer am WebOS Internals Alpha- oder Beta-Testing-Programm jeder Art muss damit rechnen, ohne Vorwarnung alle seine Daten löschen und das Betriebssystem per webOS Doctor neu aufspielen zu müssen, ohne es zu bereuen oder sich dabei zu beschweren.
# Du musst bereit sein und auch das nötige Wissen besitzen, um dich in die Kommandozeile auf deinem Gerät einzuloggen und dort Linux Befehle einzugeben, wenn du so angewiesen wirst. Linux Befehle im Voraus zu kennen ist von Vorteil, aber keine Voraussetzung solange du bereit bist es dann zu lernen wenn es nötig ist, oder Anweisungen ohne Fehler zu befolgen.
# Du musst bereit sein sehr viel Zeit zu investieren um die Umstände, die zu Problemen geführt haben, verlässlich zu reproduzieren.
# Du musst vollständige und detaillierte Fehlerbeschreibungen verfassen können, ohne jegliche Details auszulassen, die auch nur im entferntesten mit dem Problem verknüpft sein könnten.
# Du musst jegliche Dokumentationen und Foreneinträge vollständig lesen, bevor du eine Frage stellst.
# Du musst den Threads, in denen das Alpha-Testing von den Autoren diskutiert wird, gewissenhaft folgen, sowie allen Anweisungen präzise Folge leisten.
# Du wirst nie und nirgends den Originallinks zu den Testing Feeds oder diese Anweisungen veröffentlichen, sondern dich immer auf die URL "http://testing.preware.org/" beziehen.
# Wenn du nach Hilfe fragst wird du immer die Phrase "Ich habe die Regeln gelesen" (oder ähnlich abgewandelt) einfügen. Das Fehlen dieser Phrase wird dazu führen, dass deine Anfrage stillschweigend ignoriert wird.

Wenn du nicht bereit bist *ALLE* der oben genannten Regel mit gutem Gewissen zu befolgen, dann warte bitte auf die öffentliche Erscheinung der Programme/Patches in den normalen Feeds von Preware.

Wenn du bereit bist *alle* oben genannten Regel zu befolgen, dann sei herzlich dazu eingeladen am Alpha- oder Beta-Testing teilzuhaben.

Beachte, dass all diese Regeln eher eine Frage deiner Einstellung als deiner Fähigkeiten sind.

= Alleinige Nutzung von sicheren, stabilen Feeds =

Wenn du einer der Personen bist, die durch Artikel oder Foreneinträge angewiesen wurden, die Testing Feeds zu nutzen, aber du nichts wirklich testest, dann solltest du das folgende tun, um in Preware nur sichere, stabile Feeds zu nutzen:
* Öffne Preware
* Öffne das App-Menu -> Feeds verwalten
* Lösche jeden Eintrag durch Wischen, der das Wort "testing" auch nur irgendwo im Namen enthält
Nachdem du dies getan hast, und du willst nur die sicheren, stabilen Feeds beibehalten, kannst du hier aufhören. Dann ist nämlich der Rest dieser Seite nicht relevant für dich, und du solltest nach diesem Abschnitt sonst nichts tun, was hier noch beschrieben wird.

= Beta Testing Feeds aktivieren =

Beta Packages wurden bereits teilweise getestet, können in seltenen Fällen aber dennoch deine Daten löschen oder dein Gerät unbrauchbar machen. Du wurdest gewarnt. Wenn du nicht explizit eine Beta-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Beta-Package aktualisieren oder installieren willst.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um die Beta-Feeds zu aktivieren, musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Beta-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Beta-Feeds deaktivieren =
Um temporär die Beta-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Beta-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Lösche im "Feeds verwalten"-Dialog alle beta-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-beta-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Beta-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Alpha Testing Feeds aktivieren =

Alpha-Packages wurden wenig bis gar nicht getestet, und es besteht eine große Gefahr Daten zu verlieren, dein Profil zu zerstören und möglicherweise dein Gerät unbrauchbar zu machen. Pakete im Alpha-Feed *werden* regelmäßig etwas kaputt machen (vielleicht sogar absichtlich). Du wurdest gewarnt. Wenn du nicht explizit eine Alpha-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Alpha-Package aktualisieren oder installieren willst.

Im Allgemeinen werden nur sehr sehr sehr wenige Personen erwartet, die Alpha Testing Feeds zu aktivieren. Die größte Mehrheit der User sollte höchstens den Beta Testing Feed verwenden.

Der Beta-Testing Feed und der Alpha-Testing Feed können beide zeitgleich aktiv sein, wenn gewünscht.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um den Alpha-Testing Feed zu aktivieren musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Alpha-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Alpha-Feeds deaktivieren =
Um temporär die Alpha-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Alpha-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Lösche im "Feeds verwalten"-Dialog alle alpha-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-alpha-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Alpha-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Testing Feeds F&A =

'''F: Wer sollte die Alpha-Testing Feeds nutzen?'''

A: Wenn du diese Frage stellst, solltest du den Feed nicht aktivieren. Nur sehr sehr sehr sehr wenige Personen sollten die Alpha-Testing Feeds jemals aktivieren. Wenn du kein GIT Repository gecloned hast und Code bearbeitest, sollten du den Feed nicht aktivieren.

'''F: Wer sollte den Beta-Testing Feed nutzen?'''

A: Jeder darf den Beta-Testing Feed benutzen, wenn er mit den Regeln vollständig einverstanden ist, und genau weiß warum er den Beta-Testing Feed verwendet (und z. B. nicht einfach blind irgendwelchen Anleitungen in Artikeln oder Foren folgt)

'''F: Warum benötigt die Aktivierung der Feeds eine Verbindung zu meinem Computer?'''

A: Wenn du die Testing-Feeds zum ersten mal aktivierst, wollen wir sicherstellen dass du in der Lage bist dein Gerät mit einem PC zu verbinden, um Fehler finden zu können und dein Gerät wiederherzustellen wenn etwas schief geht.

'''F: Warum benötigt die Aktivierung der Feeds eine Neuinstallation von Preware?'''

A: Die Feeds werden erstellt wenn Preware installiert wird. Deshalb musst du Preware reinstallieren, dass die Feeds auf deinem Gerät erstellt werden.

'''F: Warum benötigt die Aktivierung der Feeds die Nutzung der Linux Kommandozeile?'''

A: Um ein erfolgreicher Tester zu sein, musst du in der Lage sein auf dein Gerät über die Linux Kommandozeile zuzugreifen um Debug-Infomationen liefern zu können. Wir stellen so sicher dass du das kannst, bevor du auf die Feeds zugreifen kannst.

'''F: Warum kann ich nicht einfach die Feeds-URLs direkt eingeben?'''

A: Zu viele User verwenden die falschen Feed-Namen oder Feed-URLs, daher haben wir diese Möglichkeit entfernt.

'''F: Warum darf ich die Anleitungen nicht einfach auf meinem Blog oder einem Forum veröffentlichen?'''

A: Zu viele Leute veröffentlichten die URLs ohne die dazugehörigen Regeln und Warnungen. Dies ist nun strengstens verboten.

'''F: Wofür werden die Alpha-Patches und Beta-Patches Feeds verwendet?'''

A: Der Alpha-Patches Feed wird zum Testen der AUTP-Scripte genutzt werden, welche in der Lage sind Dateien in <code>/media/cryptofs/apps/</code> zu patchen (Dateien, die nicht in <code>/md5sums</code> enthalten sind). Sobald das funktioniert, werden wir den Beta-Patch Feed verwenden um alle Patches zu upgraden, die neue AUPT-Scripts zu nutzen und diese anschließend im Beta-Stadium zu testen.

Testing Feeds-DE

2011-09-18T12:12:30Z

Pcworld: language; spelling; grammar; wikimedia syntax; added/corrected/removed content; +"How to only use safe stable feeds"; +"Disabling the Beta Feeds"; +"Disabling the Alpha Feeds"

Diese Seite ist derzeit in zwei Sprachen verfügbar.
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

=Übergang zu den neuen Alpha und Beta Testing Feeds=

Die alten WebOS Internals Testing Feeds (für Programme und Kernels) wurden durch separate Alpha und Beta Testing Feeds ersetzt. Dafür gibt es eine Menge Gründe:

# Wir wollen die instabilen und im Versuchsstadium begriffenen Alpha Testing Programme von den generell eher harmlosen Beta Testing Programmen trennen. Der alte Testing Feed ließ diese Möglichkeit nicht zu.
#Zu viele Internetseiten haben die direkte URL des Testing Feeds veröffentlicht, ohne die Regel zu nennen, welche auf dieser Seite stehen. Das bedeutet, dass viele Leute die Testing Feeds aktiviert haben ohne die dadurch entstehenden Gefahren zu kennen.
# Es gab eine Menge Programme die während des Ausverkaufs des TouchPads im Testing Feed gelandet waren. Als Ergebnis der großen Aufmerksamkeit dieser wenigen Programme in der Öffentlichkeit haben viele Leute die Testing Feeds nur wegen dieser Programme aktiviert. Diese Programme sind nun in den öffentlichen Feeds von Preware verfügbar, und die Leute sind sich nicht der Risiken bewusst, welche andere Programme des alten Testing Feeds mit sich bringen.

Bitte lies den [[#Testing_Feeds_F.26A|Testing Feeds F&A]] um die Gründe für diese Änderung zu erfahren.

Sowohl der Alpha als auch der Beta Testing Feed haben jeweils vier untergeordnete Feeds: Programme, Kernels, Patches & Optware. Jeder dieser untergeordneten Feeds kann unabhängig von den anderen einzeln aktiviert oder deaktiviert werden.

Der Übergang zu den neuen Alpha und Beta Testing Feeds ist nun auf den Weg gebracht. Preware 1.8.x unterstützt die neuen Alpha und Beta Testing Feeds und die Anleitungen wie diese neuen Feeds aktiviert werden findest du auf dieser Seite. Wenn du die neuen Alpha und Beta Testing Feeds aktivierst werden die veralteten Testing Feeds automatisch aus Preware entfernt.

=Regeln die du akzeptieren musst, bevor du diesen Feed nutzt=
Bevor du unseren Testing Feed nutzen kannst, musst du folgende Regel vollständig lesen und akzeptieren:
[[image:Tux_with_Warning.png|frameless|right]]

# Jeder Teilnehmer am WebOS Internals Alpha- oder Beta-Testing-Programm jeder Art muss damit rechnen, ohne Vorwarnung alle seine Daten löschen und das Betriebssystem per webOS Doctor neu aufspielen zu müssen, ohne es zu bereuen oder sich dabei zu beschweren.
# Du musst bereit sein und auch das nötige Wissen besitzen, um dich in die Kommandozeile auf deinem Gerät einzuloggen und dort Linux Befehle einzugeben, wenn du so angewiesen wirst. Linux Befehle im Voraus zu kennen ist von Vorteil, aber keine Voraussetzung solange du bereit bist es dann zu lernen wenn es nötig ist, oder Anweisungen ohne Fehler zu befolgen.
# Du musst bereit sein sehr viel Zeit zu investieren um die Umstände, die zu Problemen geführt haben, verlässlich zu reproduzieren.
# Du musst vollständige und detaillierte Fehlerbeschreibungen verfassen können, ohne jegliche Details auszulassen, die auch nur im entferntesten mit dem Problem verknüpft sein könnten.
# Du musst jegliche Dokumentationen und Foreneinträge vollständig lesen, bevor du eine Frage stellst.
# Du musst den Threads, in denen das Alpha-Testing von den Autoren diskutiert wird, gewissenhaft folgen, sowie allen Anweisungen präzise Folge leisten.
# Du must akribisch den Forumseinträgen folgen in denen die Autoren der Programme/Patches im Testing Feeds Probleme diskutieren und den dort gegebene Instruktionen präzise Folge leisten.
# Du wirst nie und nirgends den Originallinks zu den Testing Feeds oder diese Anweisungen veröffentlichen, sondern dich immer auf die URL "http://testing.preware.org/" beziehen.
# Wenn du nach Hilfe fragst wird du immer die Phrase "Ich habe die Regeln gelesen" (oder ähnlich abgewandelt) einfügen. Das Fehlen dieser Phrase wird dazu führen, dass deine Anfrage stillschweigend ignoriert wird.

Wenn du nicht bereit bist *ALLE* der oben genannten Regel mit gutem Gewissen zu befolgen, dann warte bitte auf die öffentliche Erscheinung der Programme/Patches in den normalen Feeds von Preware.

Wenn du bereit bist *alle* oben genannten Regel zu befolgen, dann sei herzlich dazu eingeladen am Alpha- oder Beta-Testing teilzuhaben.

Beachte, dass all diese Regeln eher eine Frage deiner Einstellung als deiner Fähigkeiten sind.

= Alleinige Nutzung von sicheren, stabilen Feeds =

Wenn du einer der Personen bist, die durch Artikel oder Foreneinträge angewiesen wurden, die Testing Feeds zu nutzen, aber du nichts wirklich testest, dann solltest du das folgende tun, um in Preware nur sichere, stabile Feeds zu nutzen:
* Öffne Preware
* Öffne das App-Menu -> Feeds verwalten
* Lösche jeden Eintrag durch Wischen, der das Wort "testing" auch nur irgendwo im Namen enthält
Nachdem du dies getan hast, und du willst nur die sicheren, stabilen Feeds beibehalten, kannst du hier aufhören. Dann ist nämlich der Rest dieser Seite nicht relevant für dich, und du solltest nach diesem Abschnitt sonst nichts tun, was hier noch beschrieben wird.

= Beta Testing Feeds aktivieren =

Beta Packages wurden bereits teilweise getestet, können in seltenen Fällen aber dennoch deine Daten löschen oder dein Gerät unbrauchbar machen. Du wurdest gewarnt. Wenn du nicht explizit eine Beta-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Beta-Package aktualisieren oder installieren willst.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um die Beta-Feeds zu aktivieren, musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Beta-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Beta-Feeds deaktivieren =
Um temporär die Beta-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Beta-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-beta-feeds
* Lösche im "Feeds verwalten"-Dialog alle beta-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-beta-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Beta-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Alpha Testing Feeds aktivieren =

Alpha-Packages wurden wenig bis gar nicht getestet, und es besteht eine große Gefahr Daten zu verlieren, dein Profil zu zerstören und möglicherweise dein Gerät unbrauchbar zu machen. Pakete im Alpha-Feed *werden* regelmäßig etwas kaputt machen (vielleicht sogar absichtlich). Du wurdest gewarnt. Wenn du nicht explizit eine Alpha-Version einer App testen möchtest, solltest du alle Beta-Feeds deaktivieren, wenn du nicht gerade ein bestimmtes Alpha-Package aktualisieren oder installieren willst.

Im Allgemeinen werden nur sehr sehr sehr wenige Personen erwartet, die Alpha Testing Feeds zu aktivieren. Die größte Mehrheit der User sollte höchstens den Beta Testing Feed verwenden.

Der Beta-Testing Feed und der Alpha-Testing Feed können beide zeitgleich aktiv sein, wenn gewünscht.

* [[#WebOS_Internals_Testing_Feed_konfigurieren|Lies die Regeln noch einmal bevor du weitermachst.]]
* [[#Testing_Feeds_F.26A|Es ist auch empfehlenswert, vorher noch die FAQ zu lesen.]]

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

Um den Alpha-Testing Feed zu aktivieren musst du folgendes tun:

* Deinstalliere Preware. Ja, wirklich - du musst Preware deinstallieren. (Gründe hierzu siehe in den [[#Testing_Feeds_F.26A|FAQ]])
* Greife per Kommandozeile auf das Gerät zu und führe die folgenden 2 Befehle aus. Wenn du nicht schon weißt, wie man diese Befehle per novaterm oder Xecutah ausführt oder nicht z. B. per Google herausfindest wie dies geht, solltest du die Alpha-Feeds nicht benutzen.
mkdir -p /var/preferences/org.webosinternals.preware
touch /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Installiere Preware 1.8.3 oder höher.
* Starte Preware und öffne den "Feeds verwalten"-Dialog. Aktiviere nun *nur* die Feeds, die du nutzen möchtest. Bevor du einen Kernel Testing-Feed aktivierst, solltest du [http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ diesen Eintrag auf dem HP webOS Developer Blog] lesen.

'''''Poste, kopiere oder umschreibe diese Anleitung nirgendwo anders, sondern setze immer einen Link auf "http://testing.preware.org/"'''''

= Alpha-Feeds deaktivieren =
Um temporär die Alpha-Feeds zu deaktivieren, setze im "Feeds verwalten"-Dialog die entsprechenden Einträge einfach auf "aus".

Um die Alpha-Feeds permanent zu deaktivieren, musst du folgendes tun:
* Greife per Kommandozeile auf das Gerät zu und führe den folgenden Befehl aus.
rm -f /var/preferences/org.webosinternals.preware/enable-alpha-feeds
* Lösche im "Feeds verwalten"-Dialog alle alpha-* Feeds durch Wischen.

Beachte, dass wenn du nicht die <code>enable-alpha-feeds</code>-Datei wie im ersten Schritt beschrieben löschst, werden die Alpha-Feeds wieder erscheinen, sobald du eine neue Version von Preware installierst.

= Testing Feeds F&A =

'''F: Wer sollte die Alpha-Testing Feeds nutzen?'''

A: Wenn du diese Frage stellst, solltest du den Feed nicht aktivieren. Nur sehr sehr sehr sehr wenige Personen sollten die Alpha-Testing Feeds jemals aktivieren. Wenn du kein GIT Repository gecloned hast und Code bearbeitest, sollten du den Feed nicht aktivieren.

'''F: Wer sollte den Beta-Testing Feed nutzen?'''

A: Jeder darf den Beta-Testing Feed benutzen, wenn er mit den Regeln vollständig einverstanden ist, und genau weiß warum er den Beta-Testing Feed verwendet (und z. B. nicht einfach blind irgendwelchen Anleitungen in Artikeln oder Foren folgt)

'''F: Warum benötigt die Aktivierung der Feeds eine Verbindung zu meinem Computer?'''

A: Wenn du die Testing-Feeds zum ersten mal aktivierst, wollen wir sicherstellen dass du in der Lage bist dein Gerät mit einem PC zu verbinden, um Fehler finden zu können und dein Gerät wiederherzustellen wenn etwas schief geht.

'''F: Warum benötigt die Aktivierung der Feeds eine Neuinstallation von Preware?'''

A: Die Feeds werden erstellt wenn Preware installiert wird. Deshalb musst du Preware reinstallieren, dass die Feeds auf deinem Gerät erstellt werden.

'''F: Warum benötigt die Aktivierung der Feeds die Nutzung der Linux Kommandozeile?'''

A: Um ein erfolgreicher Tester zu sein, musst du in der Lage sein auf dein Gerät über die Linux Kommandozeile zuzugreifen um Debug-Infomationen liefern zu können. Wir stellen so sicher dass du das kannst, bevor du auf die Feeds zugreifen kannst.

'''F: Warum kann ich nicht einfach die Feeds-URLs direkt eingeben?'''

A: Zu viele User verwenden die falschen Feed-Namen oder Feed-URLs, daher haben wir diese Möglichkeit entfernt.

'''F: Warum darf ich die Anleitungen nicht einfach auf meinem Blog oder einem Forum veröffentlichen?'''

A: Zu viele Leute veröffentlichten die URLs ohne die dazugehörigen Regeln und Warnungen. Dies ist nun strengstens verboten.

'''F: Wofür werden die Alpha-Patches und Beta-Patches Feeds verwendet?'''

A: Der Alpha-Patches Feed wird zum Testen der AUTP-Scripte genutzt werden, welche in der Lage sind Dateien in <code>/media/cryptofs/apps/</code> zu patchen (Dateien, die nicht in <code>/md5sums</code> enthalten sind). Sobald das funktioniert, werden wir den Beta-Patch Feed verwenden um alle Patches zu upgraden, die neue AUPT-Scripts zu nutzen und diese anschließend im Beta-Stadium zu testen.

Testing Feeds-DE

2011-09-17T15:29:46Z

Pcworld: changed warning that this instructions are *now* deprecated

Die Anleitungen dieser Seite existieren derzeit in zwei Sprachen
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

'''Hinweis''': Diese Anweisungen hier sind '''veraltet'''. Die verwendeten Techniken sind durch beta-/alpha-Feeds ersetzt worden. Bitte schau derweil im englischen Artikel, oder hilf mit die Änderungen zu übersetzen.

=Regeln die du akzeptieren musst, bevor du diesen Feed nutzt=

Bevor du unseren Testing Feed nutzt musst du folgende Regel vollständig lesen und akzeptieren:
[[image:Tux_with_Warning.png|frameless|right]]

#Wenn du beim Alphatest von WebOS Internals mit machen willst, musst damit rechnen, dass du ohne Vorwarnung alle deine Daten löschen und den WebOS Doktor aufspielen musst, ohne dich dabei zu beschweren. Die Nutzung erfolgt auf eigene Gefahr und niemand kann dafür verantwortlich gemacht werden.
# Du musst bereit sein und auch das nötige Wissen besitzen um dich in die Kommandozeile auf deinem Gerät einzuloggen und dort Linux Befehle einzugeben, um aufgetretene Probleme wieder zu beheben. Die Linux Befehle zu kennen ist von Vorteil, ist aber keine Voraussetzung solange du bereit bist es dann zu lernen wenn es nötig ist, oder Anweisungen ohne Fehler zu befolgen.
# Du musst bereit sein sehr viel Zeit zu investieren um die Umstände, die zu Problemen geführt haben, verlässlich zu reproduzieren.
# Du musst eine vollständige und detaillierte Fehlerbeschreibung geben können und kein Detail auslassen was auch nur im entferntesten mit dem Problem verknüpft sein könnte.
#Du musst alle Dokumentationen und Forumseinträge vollständig lesen bevor du eine Frage stellst.
# Du must akribisch den Forumseinträgen folgen in denen die Autoren der Programme/Patches im Testing Feeds Probleme diskutieren und den dort gegebene Instruktionen präzise Folge leisten.
# Du wirst nie und nirgends den Originallink zum Testing Feed veröffentlichen. Wenn du dich auf den Testing Feed beziehst wirst immer du die URL "http://testing.preware.org/" nutzen.
# Wenn du nach Hilfe fragst wird du immer die Phrase "Ich habe die Regeln gelesen" (oder ähnlich abgewandelt) einfügen. Das Fehlen dieser Phrase wird dazu führen, dass die Anfrage um Hilfe stillschweigend ignoriert wird.

Wenn du nicht bereit bist *ALLE* der oben genannten Regel mit guten Gewissen zu befolgen, dann warte bitte auf die öffentliche Erscheinung der Programme/Patches in den normalen Feeds von Preware.

Wenn du bereit bist *alle* oben genannten Regel zu befolgen, dann sei herzlich dazu eingeladen am Alphatest teilzuhaben.

Beachte, dass all diese Regeln eher eine Frage deiner Einstellung als deiner Fähigkeiten sind.

Testing Feeds für Kernels sind am unteren Ende der Seite.

=WebOS Internals Testing Feed konfigurieren=

===Mit Preware===
[[image:Tux_with_Pre.png|frameless|right]]
Mit Preware ab der Version 0.9.30 und höher, zusammen mit webOS 1.3.5 und höher ist es Nutzern möglich selbst definierte Feeds in Prekäre hinzu zufügen, ohne einen Computer nutzen zu müssen. Die folgende Anleitung erklärt wie man den WebOS Internals Testing Feed in Preware hinzufügt.

Beachte, dass du *ZWEI* Feeds hinzufügen musst. Du benötigst den *ALLE* Feed und den gerätespezifischen Feed (armv7, armv6 pder i686). Das Zielgerät steht dabei für dein Handy/Table/Emulator.

{| border="0" width="470"
|colspan="2" align="left"|'''Zielgerät:''' ALLE
|-
|'''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"|'''Zielgerät:''' <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"|'''Zielgerät:''' <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"|'''Zielgerät:''' 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]
|}
 
#Starte Preware und warte bis es fertig geladen hat.
#Öffne das Programmenü (drücke auf "Preware" in der oberen linken Ecke des Bildschirms) und drücke auf "Feeds verwalten").
#Scrolle bis zum Ende der Seite, bis du die "Neuer Feed" Box siehst.
#Tippe oder kopiere den Namen und die korrespondierende URL aus der oberen Anleitung in den entsprechende Textzeile. Gehe sicher dass die URL am Ende *keinen* Schrägstrich hat "/".
#Gehe sicher dass KOMPRIMIERT auf JA steht.
#Drücke auf Feed hinzufügen und auf OK wenn die Warnung erscheint.
#Wiederhole jeden Schritt für jeden Feed den du hinzufügen möchtest.
#Führe die Zurück Geste (swipe back) aus. Preware zeigt eine Meldung, dass neue Feeds hinzugefügt wurden und empfiehlt die Feeds zu aktualisieren. Drücke OK.
 
Glückwunsch, du hast eben einen selbstdefinierten Feed hinzugefügt! Um andere Feeds hinzuzufügen ersetzte den Namen und die URL in dieser Anleitung mit den entsprechenden Namen und der entsprechenden URL.
 
'''TIP:'''

Shift-Taste halten + auf den Text drücken (bzw. halten) markiert den Text
Auf das Gestureareal drücken (gesture) + c um zu kopieren
gesture+v um einzufügen
Lösche 'http://' bevor du eine URL einfügst, die schon 'http://' enthält.

 

===Mit dem Computer===
[[image:Tux_Chat.png|frameless|right]]

1. Öffne einen Zugang zur Shell, entweder mittels Novaterm/ssh oder mit dem Terminal Programm welches du über den regulären WebOS Internals Feed installieren kannst. 
2. Führe die folgenden Kommandos aus:
<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. Wenn Preware geöffnet ist, aktualisiere die Feeds mittels "Feeds aktualisieren" im Programmmenü.

Ersetze 'armv7' mit 'armv6' or 'i686' in der oberen Anleitung, wenn du einen Pixi oder den Emulator benutzt.

 
=Kernel Testing Feeds=
[http://www.webos-internals.org/wiki/Testing_Feeds-DE#Regel_die_akzeptiert_werden_m.C3.BCssen_bevor_du_diesen_Feed_nutzt Ließ diese Regeln noch einmal bevor du weiter machst.]

Beachte auch die Warnungen auf der folgenden Seite http://forums.precentral.net/2532084-post3.html Hier ist beschrieben, dass der Kernel Testing Feed dazu führen kann, dass dein Gerät nicht mehr funktioniert, schmilzt (wörtlich nehmen) oder anderweitig zerstört wird.

Wenn du keine Pfütze geschmolzenes Plastik und Silizium an der Stelle sehen willst wo eben noch dein Pre/Pixi/TouchPad lag, HÖRE HIER AUF und mache NICHT WEITER!

Du wurdest gewarnt.

[http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ Und HP/Palm wird dir nicht helfen.]

#Schreibe 'webos-kernels-testing' (ohne die Anstriche, nur kleine Buchstaben und die Bindestriche) in das NAME Feld in der NEUER FEED Box unter dem Eintrag Feeds verwalten. Wenn du irgend einen Fehler machst wird die URL beim Neustart des Gerätes nicht durch die richtige URL ersetz und du wirst keinen Zugang zu den Feeds erhalten. GEHE SICHER DAS DU DEN RICHTIGEN FEED NAME NUTZT!
#Schreibe http://preware.is.awesome.com in das URL Feld. Achtung dies ist nicht die richtige URL es ist nur ein Platzhalter. Noch einmal - der Feed Name muss korrekt sein, damit die richtige URL eingesetzt wird wenn das Gerät neustartet. Die URL ist nicht wichtig, sie ist nur ein Platzhalter.
#Stelle KOMPRIMIERT auf JA.
#Drücke auf "Feed Hinzufügen" und ließ die Warnung aufmerksam. Die Dinge die du im Kernel Testing Feed findest bergen die Möglichkeit, dass dein Gerät ohne Vorwarnung zerstört wird. Drücke nur dann OK, wenn du damit einverstanden bist, dass die Möglichkeit besteht alle Daten zu verlieren und, dass dein Gerät vollkommen zerstört wird. Du kannst nachträglich niemanden dafür verantwortlich machen oder beschuldigen dass du nicht gewanrt wurden wärst.
#Starte sofort dein Gerät neu indem du gleichzeitig die Tasten Opt, Sym und R an eine Pre/Pixi drückst, oder durch Drücken der Sperr- und Power-Taste am TouchPad bis das Gerät neustartet. Wenn du dein Gerät nicht sofort neustartest oder nur einen LUNA Neustart machst, wird der Platzhalter in der URL nicht durch die richtige URL ersetzt und du wirst keinen Zugang zu den Feeds erhalten. GEHE SICHER, DAS DU DAS GERÄT NEUSTARTEST!
#Warte bis das Gerät neugestartet ist. Wenn du den Fed Name richtig eingetragen hast wird die Platzhalter URL durch die richtige URL automatisch ersetzt.
#Öffne Preware und drücke auf Feeds aktualisieren. Stelle sicher, dass eine Netzwerkverbindung hergestellt ist.

Preware wird das URL Feld automatisch reparieren wenn das Gerät neustartet. Habe ich erwähnt, dass du den Feed Namen präzise eingeben musst? STELLE SICHER, DASS DER FEED NAME RICHTIG IST UND STARTE NEU!

Du musst Preware 1.1.4. oder höher laufen haben damit dies funktioniert (ja dies kann man schon eine ganze Weile lang so machen).

Testing Feeds-DE

2011-09-17T14:41:55Z

Pcworld: added warning for obsolete feeds, beta-/alpha-feeds

Die Anleitungen dieser Seite existieren derzeit in zwei Sprachen
:[[Image:Australia.png]] [[Image:USA.png]] [[Testing_Feeds]]
:[[Image:Germany.png]] [[Testing_Feeds-DE]]

'''Hinweis''': Diese Anweisungen hier sind bald '''veraltet'''. Die verwendeten Techniken werden durch beta-/alpha-Feeds ersetzt. Bitte schaue derweil im englischen Artikel, oder hilf mit die Änderungen zu übersetzen.

=Regeln die du akzeptieren musst, bevor du diesen Feed nutzt=

Bevor du unseren Testing Feed nutzt musst du folgende Regel vollständig lesen und akzeptieren:
[[image:Tux_with_Warning.png|frameless|right]]

#Wenn du beim Alphatest von WebOS Internals mit machen willst, musst damit rechnen, dass du ohne Vorwarnung alle deine Daten löschen und den WebOS Doktor aufspielen musst, ohne dich dabei zu beschweren. Die Nutzung erfolgt auf eigene Gefahr und niemand kann dafür verantwortlich gemacht werden.
# Du musst bereit sein und auch das nötige Wissen besitzen um dich in die Kommandozeile auf deinem Gerät einzuloggen und dort Linux Befehle einzugeben, um aufgetretene Probleme wieder zu beheben. Die Linux Befehle zu kennen ist von Vorteil, ist aber keine Voraussetzung solange du bereit bist es dann zu lernen wenn es nötig ist, oder Anweisungen ohne Fehler zu befolgen.
# Du musst bereit sein sehr viel Zeit zu investieren um die Umstände, die zu Problemen geführt haben, verlässlich zu reproduzieren.
# Du musst eine vollständige und detaillierte Fehlerbeschreibung geben können und kein Detail auslassen was auch nur im entferntesten mit dem Problem verknüpft sein könnte.
#Du musst alle Dokumentationen und Forumseinträge vollständig lesen bevor du eine Frage stellst.
# Du must akribisch den Forumseinträgen folgen in denen die Autoren der Programme/Patches im Testing Feeds Probleme diskutieren und den dort gegebene Instruktionen präzise Folge leisten.
# Du wirst nie und nirgends den Originallink zum Testing Feed veröffentlichen. Wenn du dich auf den Testing Feed beziehst wirst immer du die URL "http://testing.preware.org/" nutzen.
# Wenn du nach Hilfe fragst wird du immer die Phrase "Ich habe die Regeln gelesen" (oder ähnlich abgewandelt) einfügen. Das Fehlen dieser Phrase wird dazu führen, dass die Anfrage um Hilfe stillschweigend ignoriert wird.

Wenn du nicht bereit bist *ALLE* der oben genannten Regel mit guten Gewissen zu befolgen, dann warte bitte auf die öffentliche Erscheinung der Programme/Patches in den normalen Feeds von Preware.

Wenn du bereit bist *alle* oben genannten Regel zu befolgen, dann sei herzlich dazu eingeladen am Alphatest teilzuhaben.

Beachte, dass all diese Regeln eher eine Frage deiner Einstellung als deiner Fähigkeiten sind.

Testing Feeds für Kernels sind am unteren Ende der Seite.

=WebOS Internals Testing Feed konfigurieren=

===Mit Preware===
[[image:Tux_with_Pre.png|frameless|right]]
Mit Preware ab der Version 0.9.30 und höher, zusammen mit webOS 1.3.5 und höher ist es Nutzern möglich selbst definierte Feeds in Prekäre hinzu zufügen, ohne einen Computer nutzen zu müssen. Die folgende Anleitung erklärt wie man den WebOS Internals Testing Feed in Preware hinzufügt.

Beachte, dass du *ZWEI* Feeds hinzufügen musst. Du benötigst den *ALLE* Feed und den gerätespezifischen Feed (armv7, armv6 pder i686). Das Zielgerät steht dabei für dein Handy/Table/Emulator.

{| border="0" width="470"
|colspan="2" align="left"|'''Zielgerät:''' ALLE
|-
|'''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"|'''Zielgerät:''' <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"|'''Zielgerät:''' <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"|'''Zielgerät:''' 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]
|}
 
#Starte Preware und warte bis es fertig geladen hat.
#Öffne das Programmenü (drücke auf "Preware" in der oberen linken Ecke des Bildschirms) und drücke auf "Feeds verwalten").
#Scrolle bis zum Ende der Seite, bis du die "Neuer Feed" Box siehst.
#Tippe oder kopiere den Namen und die korrespondierende URL aus der oberen Anleitung in den entsprechende Textzeile. Gehe sicher dass die URL am Ende *keinen* Schrägstrich hat "/".
#Gehe sicher dass KOMPRIMIERT auf JA steht.
#Drücke auf Feed hinzufügen und auf OK wenn die Warnung erscheint.
#Wiederhole jeden Schritt für jeden Feed den du hinzufügen möchtest.
#Führe die Zurück Geste (swipe back) aus. Preware zeigt eine Meldung, dass neue Feeds hinzugefügt wurden und empfiehlt die Feeds zu aktualisieren. Drücke OK.
 
Glückwunsch, du hast eben einen selbstdefinierten Feed hinzugefügt! Um andere Feeds hinzuzufügen ersetzte den Namen und die URL in dieser Anleitung mit den entsprechenden Namen und der entsprechenden URL.
 
'''TIP:'''

Shift-Taste halten + auf den Text drücken (bzw. halten) markiert den Text
Auf das Gestureareal drücken (gesture) + c um zu kopieren
gesture+v um einzufügen
Lösche 'http://' bevor du eine URL einfügst, die schon 'http://' enthält.

 

===Mit dem Computer===
[[image:Tux_Chat.png|frameless|right]]

1. Öffne einen Zugang zur Shell, entweder mittels Novaterm/ssh oder mit dem Terminal Programm welches du über den regulären WebOS Internals Feed installieren kannst. 
2. Führe die folgenden Kommandos aus:
<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. Wenn Preware geöffnet ist, aktualisiere die Feeds mittels "Feeds aktualisieren" im Programmmenü.

Ersetze 'armv7' mit 'armv6' or 'i686' in der oberen Anleitung, wenn du einen Pixi oder den Emulator benutzt.

 
=Kernel Testing Feeds=
[http://www.webos-internals.org/wiki/Testing_Feeds-DE#Regel_die_akzeptiert_werden_m.C3.BCssen_bevor_du_diesen_Feed_nutzt Ließ diese Regeln noch einmal bevor du weiter machst.]

Beachte auch die Warnungen auf der folgenden Seite http://forums.precentral.net/2532084-post3.html Hier ist beschrieben, dass der Kernel Testing Feed dazu führen kann, dass dein Gerät nicht mehr funktioniert, schmilzt (wörtlich nehmen) oder anderweitig zerstört wird.

Wenn du keine Pfütze geschmolzenes Plastik und Silizium an der Stelle sehen willst wo eben noch dein Pre/Pixi/TouchPad lag, HÖRE HIER AUF und mache NICHT WEITER!

Du wurdest gewarnt.

[http://developer.palm.com/blog/2010/03/a-statement-on-the-overclocking-patches/ Und HP/Palm wird dir nicht helfen.]

#Schreibe 'webos-kernels-testing' (ohne die Anstriche, nur kleine Buchstaben und die Bindestriche) in das NAME Feld in der NEUER FEED Box unter dem Eintrag Feeds verwalten. Wenn du irgend einen Fehler machst wird die URL beim Neustart des Gerätes nicht durch die richtige URL ersetz und du wirst keinen Zugang zu den Feeds erhalten. GEHE SICHER DAS DU DEN RICHTIGEN FEED NAME NUTZT!
#Schreibe http://preware.is.awesome.com in das URL Feld. Achtung dies ist nicht die richtige URL es ist nur ein Platzhalter. Noch einmal - der Feed Name muss korrekt sein, damit die richtige URL eingesetzt wird wenn das Gerät neustartet. Die URL ist nicht wichtig, sie ist nur ein Platzhalter.
#Stelle KOMPRIMIERT auf JA.
#Drücke auf "Feed Hinzufügen" und ließ die Warnung aufmerksam. Die Dinge die du im Kernel Testing Feed findest bergen die Möglichkeit, dass dein Gerät ohne Vorwarnung zerstört wird. Drücke nur dann OK, wenn du damit einverstanden bist, dass die Möglichkeit besteht alle Daten zu verlieren und, dass dein Gerät vollkommen zerstört wird. Du kannst nachträglich niemanden dafür verantwortlich machen oder beschuldigen dass du nicht gewanrt wurden wärst.
#Starte sofort dein Gerät neu indem du gleichzeitig die Tasten Opt, Sym und R an eine Pre/Pixi drückst, oder durch Drücken der Sperr- und Power-Taste am TouchPad bis das Gerät neustartet. Wenn du dein Gerät nicht sofort neustartest oder nur einen LUNA Neustart machst, wird der Platzhalter in der URL nicht durch die richtige URL ersetzt und du wirst keinen Zugang zu den Feeds erhalten. GEHE SICHER, DAS DU DAS GERÄT NEUSTARTEST!
#Warte bis das Gerät neugestartet ist. Wenn du den Fed Name richtig eingetragen hast wird die Platzhalter URL durch die richtige URL automatisch ersetzt.
#Öffne Preware und drücke auf Feeds aktualisieren. Stelle sicher, dass eine Netzwerkverbindung hergestellt ist.

Preware wird das URL Feld automatisch reparieren wenn das Gerät neustartet. Habe ich erwähnt, dass du den Feed Namen präzise eingeben musst? STELLE SICHER, DASS DER FEED NAME RICHTIG IST UND STARTE NEU!

Du musst Preware 1.1.4. oder höher laufen haben damit dies funktioniert (ja dies kann man schon eine ganze Weile lang so machen).

PDK on Linux

2011-07-25T15:06:11Z

Pcworld: removed notice about "untested", I think it's now more than confirmed that this is working (see threads in HP dev forum); +xar .deb packages

The official Palm PDK development kit for writing native programs is not supported on Linux.

The instructions on this page should allow you to get the official Palm webOS PDK for OSX working on Linux.

==Prerequisites==
* Get the command line tool "xar". Some debian based systems have it, try apt-get install xar. If not found, get it from http://code.google.com/p/xar/ (I needed package libxml2-dev to compile it) (I also needed openssl-dev to compile it on Ubuntu 10.10)
To install xar in a recent Debian/Ubuntu system and it isn't found via apt-get, you can download these packages and install them manually: [http://packages.ubuntu.com/hardy/libxar1 libxar1], [http://packages.ubuntu.com/hardy/xar xar]
* You will need to have git installed to retrieve files from the WIDK repository.
* Building the pkg file requires Curl and libbz2-dev
* Since you're planning to write native software for webOS, this assumes you have things like gcc and make and normal developer stuff like that.

We will be using tools found in the WIDK cross-compile repository is really helpful as it already has functionality to download and extract the OSX PDK, most of which will "just work" on Linux. Tools found in the WIDK repository can also download the CodeSourcery toolchain for Linux to replace the one included in the PDK, built for Darwin.

==Setup==
===Get the Palm PDK using the Webos-Internals makefile===

This downloads Palm's DMG file, downloads and patches a tool for converting DMG's, and runs it against the Palm DMG, ending up with a Xar format package file. (filename ends in .pkg)

<pre style="margin-left:50px;">
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg
</pre>

You now have a Palm_webOS_SDK-Mac-1.4.5.465.pkg in doctors/ .

===Extract that .pkg file===

Now let's extract it into / (this will create /opt/PalmPDK)

<pre style="margin-left:50px;">
xar -xf doctors/Palm_webOS_SDK-Mac-1.4.5.465.pkg palmpdk.pkg
sudo sh -c 'gzip -cd palmpdk.pkg/Payload | (cd /; cpio -i)'
</pre>

You now have a Palm PDK in /opt/PalmPDK, but you don't have a working cross-compile toolchain, because the one Palm supplied was for osX / Darwin not Linux. We need to fix that.

===Get CodeSourcery Linux cross-compiler===
Install the CodeSourcery Linux cross-compiler toolchain where Palm's toolchain built for OSX was.

<pre style="margin-left:50px">
make toolchain
sudo cp -r toolchain/arm-2007q3 /opt/PalmPDK
cd /opt/PalmPDK
sudo mv arm-gcc arm-gcc-darwin
sudo ln -s arm-2007q3 arm-gcc
</pre>

Someone who is familiar with the PDK should test this at this point to see if you can actually use it in the proper ways.

== Alternative setup ==

The github project [http://github.com/kayahr/linux-webos-pdk linux-webos-pdk] automates the process of creating a webOS PDK for Linux. The only requirements are wget, 7zip, pax and patch. All these requirements are available even in Debian Stable (So I guess all other distributions provide them, too).

To install the PDK just do this:

$ git clone git://github.com/kayahr/linux-webos-pdk.git
$ cd linux-webos-pdk
$ ./linux-webos-pdk.sh
$ sudo mv opt/PalmPDK /opt

After this the PDK is installed in /opt/PalmPDK and ready to be used. This PDK is successfully used to create the official [http://wiki.scummvm.org/index.php/Compiling_ScummVM/WebOS ScummVM app] for WebOS and all of its required libraries.

Setup SFTP

2011-07-25T13:35:21Z

Pcworld: added note to Application:OpenSSH page

{{reorganize|This page is deprecated (see Introduction). '''It is strongly recommended that unless you are an advanced Linux user, you use the automated setup meta-package instead of doing this manually. We suggest that you go [[Next_steps | here]] instead.''' Install "OpenSSH SFTP Server" from Preware and go to [[Application:OpenSSH]] for further instructions.

'''Note also that if you are a windows user, winSCP is faster and just as secure using the SCP protocol without doing all this. We suggest just using winSCP without bothering to set it up for SFTP which is slower and no more secure.''' }}

Once you have accessed Linux on your Pre, it would be nice to be able to get and put files off the Pre without having to switch to usb drive mode, and copy the files over,and switch back to user mode, and move the files out of the media/internal folder and so forth.

One good way to do this is via SFTP. If you are not sure what that is, please visit [http://en.wikipedia.org/wiki/SSH_File_Transfer_Protocol this wiki page].

This document assumes you know why you want sftp, and how to use it once it's on the Pre.

Step 1: [[Portal:Accessing_Linux | Login to your Pre's Linux shell]]. You must also have Optware packages configured, as outlined [[Next_steps|here]]:

Step 2: Set Read/Write Access:
<pre><nowiki>
sudo -i
mount -o remount,rw /
</nowiki></pre>

Step 3: Install the needed components from ipkg-opt:
<pre><nowiki>
cd /opt/bin
ipkg-opt update
ipkg-opt install openssh-sftp-server
</nowiki></pre>

Step 4: Modify the sudoers file to allow your user account to sudo sftp-server without a password:
<pre><nowiki>
visudo
</nowiki></pre>
Once in the file, add the following line after the existing ALL line for your user - where //myusername// should be replaced with the user account that you are using to access your Pre via SSH. The order of the lines count here :

Example:
<pre><nowiki>
myusername ALL=(ALL) ALL
myusername ALL=NOPASSWD: /opt/libexec/sftp-server
</nowiki></pre>

Quit and save your changes (ESC :wq)

Step 5: Mount the Pre's file system as read-only:
<pre><nowiki>
mount -o remount,ro /
</nowiki></pre>

Step 6: Reboot via one of the methods below:

Method 1:
<pre><nowiki>
su
/sbin/reboot
</nowiki></pre>

Method 2:
<pre><nowiki>
sudo su -l
reboot
</nowiki></pre>

Method 3:
Turn off the Pre by holding the power button until the 'Turn Off' button appears and then pressing it. Turn the Pre back on after it has turned off by holding the power button until you see the Palm logo.

Other Methods:
You may be able to reboot the phone with other commands. You can hit Orange+Sym+R on your Pre's keyboard to perform a soft reset, as well.

To login to the Pre using WinSCP:

<pre><nowiki>
Hostname: [my pre's ip]
port: [my pre's port] (222 if you followed the Optware enabling instructions verbatim)
username and password you set

Check 'Advanced Options' and select "Environment>SFTP".
In the SFTP server box enter: sudo /opt/libexec/sftp-server

Be sure to set "mount -o remount,rw /" to write and "mount -o remount,ro /" when done. (If on Windows, do this through PuTTY. I haven't found a way to do it through WinSCP, but you can go to "Commands>Open in PuTTY" from the main toolbar.)
</nowiki></pre>

Courtesy of jhoff80 and blakeb at PreCentral.net

Next steps

2011-07-25T13:10:14Z

Pcworld: /* Introduction */ Install_OpenSSH replaced with Application:OpenSSH

__notoc__
{{reorganize|This page is deprecated (see Introduction).}}
==Introduction==
The Portal [[Accessing_Linux|Accessing Linux]] links here (Set up users, Optware, and access). There, this page here is marked '''DEPRECATED'''.
The topics mentioned here have been superseded with the following pages:
*[[Application:Preware]] to install Preware (containing optware feeds as well)
*[[Application:OpenSSH]] to install OpenSSH
*[[Dropbear_Install|Dropbear Install]] to install Dropbear (alternatively to OpenSSH)
*[[Setup_Bash|Setup bash]] to replace sh by bash

See also the other portals on the left navigation pane:
#[[Portal:webOS_Applications|webOS Applications]] introduces you to the Preware application manager. A convenient programm to install further apps to your device.
#[[Portal:Linux_Applications|Linux Applications]] introduces you to common linux applications, mainly contained in the optware feeds. The optware feeds can also be accessed via preware.

==The following is deprecated==
To start getting the most out of your new webOS Device you should install Preware. Continue on to the [[Application:Preware|Preware]] page. There you will see all the ways to install Preware on your device.

Then go to the Optware section in [[Preware]] and install OpenSSH and OpenSSH SFTP Server from there.

Then go to the [http://www.webos-internals.org/wiki/Application:OpenSSH OpenSSH package homepage] and read the instructions there to create an SSH key for use when accessing your phone via ssh or sftp.

If you want to access the optware command line package library, then also install the Optware Advanced Linux Command Line Installer package.

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address on your Pre with [http://checkmyip.com/ CheckMyIP.com]
**In many cases, you are in a local network, but checkmyip.com gives you the WAN addess. Install whatismyip from the homebrew catalog to get your pre's ip address within the local network and use that
*SSH to that IP address on port 22
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
**[[Tutorials_Linux_DDNS_for_EVDO|Dynamic DNS]] is helpful for consistently accessing the Pre over EVDO with a simple name.
*Log in as root using the SSH key you created during the Optware installation

OpenSSH Install

2011-07-25T13:08:12Z

Pcworld: since this page is deprecated, redirecting to Application:OpenSSH

#REDIRECT [[Application:OpenSSH]]

WebOS Doctor Versions

2011-02-22T12:14:40Z

Pcworld: /* Pre Plus */ 2.0: +".0"

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''

=== Sprint ===
==== Pre ====
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

==== Pixi ====
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

=== Bell Mobility ===
==== Pre ====
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

=== O2 Germany, UK and Ireland / Movistar Spain ===
==== Pre ====
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

==== Pre Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== Pixi Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

=== Vodafone Europe ===
==== Pixi Plus ====
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

==== Pre Plus ====
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

=== SFR France ===
==== Pre Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar

==== Pixi Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

==== Pre 2 ====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar

=== Telcel GSM, Mexico ===
==== Pre ====
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar

=== Verizon Wireless ===
==== Pre Plus ====
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar

==== Pixi Plus ====
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar

==== Pre 2 ====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar

=== AT&T ===
==== Pre Plus ====
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

==== Pixi Plus ====
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

=== Unlocked ===
==== Pre 2 ====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

WebOS Doctor Versions

2011-02-22T12:14:12Z

Pcworld: /* Pre Plus */ +2.1

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''

=== Sprint ===
==== Pre ====
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

==== Pixi ====
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

=== Bell Mobility ===
==== Pre ====
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

=== O2 Germany, UK and Ireland / Movistar Spain ===
==== Pre ====
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

==== Pre Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

==== Pixi Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

=== Vodafone Europe ===
==== Pixi Plus ====
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

==== Pre Plus ====
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar
* version 2.1 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar

=== SFR France ===
==== Pre Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar

==== Pixi Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

==== Pre 2 ====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar

=== Telcel GSM, Mexico ===
==== Pre ====
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar

=== Verizon Wireless ===
==== Pre Plus ====
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar

==== Pixi Plus ====
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar

==== Pre 2 ====
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar

=== AT&T ===
==== Pre Plus ====
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

==== Pixi Plus ====
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

=== Unlocked ===
==== Pre 2 ====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

WebOS Doctor Versions

2011-02-03T15:57:55Z

Pcworld: +Vodafone Europe/Pre Plus

== How to get webOS ROM ==

You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm
by using your Palm device serial number.

== Download links ==
It seems the webOS Doctor jar files provided by Palm keep changing:

'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''

=== Sprint ===
==== Pre ====
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar

==== Pixi ====
* version 1.3.1 http://palm.cdnetworks.net/rom/pixi/px131r0d11172009/sr1ntp131rod/webosdoctorp200ewwsprint.jar
* version 1.3.2 http://palm.cdnetworks.net/rom/pixi/px132r0d12032009/sr1ntp132rod/webosdoctorp200ewwsprint.jar
* version 1.3.5 http://palm.cdnetworks.net/rom/pixi/px135r0d12302009/sr1ntp135rod/webosdoctorp200ewwsprint.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/sr1ntp1351rod/webosdoctorp120ewwsprint.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/sr1ntp140rod/webosdoctorp200ewwsprint.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixi/px1411r0d03312010/sr1ntp1411rod/webosdoctorp200ewwsprint.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixi/px145r0d08102010/spr1ntp145rod/webosdoctorp200ewwsprint.jar
''(Palm changed p200eww to p120eww in version 1.3.5.1)''
''(Palm changed p120eww back to p200eww in version 1.4.0)''

=== Bell Mobility ===
==== Pre ====
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar

=== O2 Germany, UK and Ireland / Movistar Spain ===
==== Pre ====
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar

==== Pre Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar

==== Pixi Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

=== Vodafone Europe ===
==== Pixi Plus ====
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

==== Pre Plus ====
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar

=== SFR France ===
==== Pre Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar

==== Pixi Plus ====
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar

==== Pre 2 ====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar

=== Telcel GSM, Mexico ===
==== Pre ====
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar

=== Verizon Wireless ===
==== Pre Plus ====
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar

==== Pixi Plus ====
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar

=== AT&T ===
==== Pre Plus ====
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar

==== Pixi Plus ====
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar

=== Unlocked ===
==== Pre 2 ====
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)
''(Palm changed p103ueu to p102ueuna in 2.0.1)''

== License ==

Note that the webOS Doctor package comes with the following license:

RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.

So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.

== MD5 sums ==

Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):

Date # MD5SUM Filename
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)

== Notes ==

1.0.3 is the last version to contain PmModemFactory

Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.

WebOS Internals PDK

2011-01-09T10:28:37Z

Pcworld: /* Errors during make stage */ +fuse/libtool error

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [[PuffTheMagic NDK]].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|}

* it has been reported that sun-java6-jdk isn't necessary

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile.

'''Note 2:''' If you're using Ubuntu and <code>xar</code> cannot be installed with <code>sudo apt-get install xar</code>, then you have to download two <code>.deb</code>-files manually and install them (in the order they are listed):
# [http://packages.ubuntu.com/hardy/libxar1 libxar1]
# [http://packages.ubuntu.com/hardy/xar xar]
After that execute the above command again.

Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage ==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

=== ecore ===
*TRUE and FALSE are not defined:
Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

*<code>$po_makefile_in</code> could not be found:
**Open the file <code>/srv/preware/cross-compile/packages/dev-e/ecore/build/src/configure.ac</code> and search for the line with: <code>$po_makefile_in</code> (in my case line 1437) and replace it with <code>po/Makefile.in</code>

=== /bin/sh errors ===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

=== fuse ===
If you get an error like this (happened to me on Ubuntu 10.10):

make[5]: Entering directory '/srv/preware/cross-compile/packages/common/fuse/build/armv7/lib'
if /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DFUSERMOUNT_DIR=\"/usr/local/bin\" -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=26 -Wall -W -Wno-sign-compare -Wstrict-prototypes -Wmissing-declarations -Wwrite-strings -g -O2 -fno-strict-aliasing -MT fuse.lo -MD -MP -MF ".deps/fuse.Tpo" -c -o fuse.lo fuse.c; \
then mv -f ".deps/fuse.Tpo" ".deps/fuse.Plo"; else rm -f ".deps/fuse.Tpo"; exit 1; fi
libtool: Version mismatch error. This is libtool 2.1a Debian 1.9+20051221-1, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6b.
libtool: You should recreate aclocal.m4 with macros from libtool 2.1a Debian 1.9+20051221-1
libtool: and run autoconf again.
make[5]: *** [fuse.lo] Error 1
make[5]: Leaving direcotry '/srv/preware/cross-compile/packages/common/fuse/build/armv7/lib'

Then open the file <code>/srv/preware/cross-compile/packages/common/fuse/build/src/ltmain.sh</code> and search for <code>exit $EXIT_MISMATCH</code> (in my case line 1028) and comment it out by placing a <code>#</code> before this line. I know that's a dirty fix, but it worked for me. Note that you will see the same error messages as before, but it won't stop there.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

WebOS Internals PDK

2011-01-08T18:58:16Z

Pcworld: /* Ecore */ +"$po_makefile_in"-fix

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [[PuffTheMagic NDK]].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|}

* it has been reported that sun-java6-jdk isn't necessary

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile.

'''Note 2:''' If you're using Ubuntu and <code>xar</code> cannot be installed with <code>sudo apt-get install xar</code>, then you have to download two <code>.deb</code>-files manually and install them (in the order they are listed):
# [http://packages.ubuntu.com/hardy/libxar1 libxar1]
# [http://packages.ubuntu.com/hardy/xar xar]
After that execute the above command again.

Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage (22:46, 10 October 2010)==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

=== ecore ===
*TRUE and FALSE are not defined:
Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

*<code>$po_makefile_in</code> could not be found:
**Open the file <code>/srv/preware/cross-compile/packages/dev-e/ecore/build/src/configure.ac</code> and search for the line with: <code>$po_makefile_in</code> (in my case line 1437) and replace it with <code>po/Makefile.in</code>

===/bin/sh errors===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

WebOS Internals PDK

2011-01-03T16:36:13Z

Pcworld: /* Update */ added notes for "xar" on Ubuntu (noticed on Ubuntu 10.10)

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [[PuffTheMagic NDK]].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|}

* it has been reported that sun-java6-jdk isn't necessary

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile.

'''Note 2:''' If you're using Ubuntu and <code>xar</code> cannot be installed with <code>sudo apt-get install xar</code>, then you have to download two <code>.deb</code>-files manually and install them (in the order they are listed):
# [http://packages.ubuntu.com/hardy/libxar1 libxar1]
# [http://packages.ubuntu.com/hardy/xar xar]
After that execute the above command again.

Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>
make toolchain
make stage

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage (22:46, 10 October 2010)==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===math_vfp.S===

There may be some errors with compiling math_vfp.c that look like this:

math_vfp_asm.S:107: Error: selected processor does not support `fldmias r1!,{s0}'
math_vfp_asm.S:107: Error: selected processor does not support `fldmias r2!,{s1}'
math_vfp_asm.S:107: Error: selected processor does not support `fadds s2,s0,s1'
math_vfp_asm.S:107: Error: selected processor does not support `fstmias r0!,{s2}'
math_vfp_asm.S:107: Error: selected processor does not support `fmrx lr,fpscr'
math_vfp_asm.S:107: Error: selected processor does not support `fmxr fpscr,fp'

Using information from [https://gstreamer.ti.com/gf/project/gstreamer_ti/forum/?_forum_action=MessageReply&message_id=6188&action=ForumBrowse this thread at TI], edit two files in packages/common/liboil/build/armv6/liboil/arm/ and change math_vfp.c (line 33) and math_vfp_asm.S (line 27) from

#if __VFP_FP__

to

#if defined(__VFP_FP__) && !defined(__SOFTFP__)

If you re-run make stage, the code is created again, so when it starts compiling hit ^Z (ctrl-Z) to pause and then edit the file and type "fg" to continue as before.

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

===Ecore===
*TRUE and FALSE are not defined

Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

===/bin/sh errors===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

WebOS Internals PDK

2011-01-01T15:05:54Z

Pcworld: /* Update */ autopoint was needed in Ubuntu 10.10

[[Category: SDL]]
Palm's binary sdk the "Plugin Developer Kit" became available to all developers in March 2010.

When the widk was developed, the Palm PDK didn't exist, and until Dec 2010, it was not possible to run the PDK in Linux. If you would like to run the official Palm PDK, see [[PDK on Linux]] for directions.

In addition to the PDK, webOS Internals has released a full "WIDK" (webOS Internals Development Kit) for you using Scratchbox2.

Less than 10% of developers in the webOS developer community use Linux variants. Among those 10% there are dozens of different linux distributions that people use. Palm, therefore has chosen to support only Mac and Windows platforms for their PDK. Palm reccomends that Linux based developers use the webOS-internals WIDK instead.

We ''strongly'' urge the open-source homebrew community to standardize on this WIDK. It uses the same underlying technologies, and is entirely open.

Scratchbox 2 is a cross-compilation engine, it can be used to create a highly flexible SDK.

As installed below, the install process uses a script which extracts the required Palm provided files from a copy of webOS doctor, and downloads from other sources, and builds a complete compilation environment automatically which can compile SDL and openGLES apps for webOS.

SB2 ''itself'' is totally distribution neutral but the webOS cross-compile environment is designed and tested on Ubuntu 9.10 32 bit. (At least one user in #webos-internals reports complete success running the cross compile environment in Ubuntu 9.10 64 bit after installing curl via apt-get.) See [[WebOS_Internals_PDK_on_Mandriva]] if you want to run it on Mandriva. If you want to run the WIDK on other distributions and are willing to support that yourself and not ask webOS Internals any questions about it then please enjoy and if you succeed come back here and make a new article on how you did it. Otherwise, use the recommended OS.

The webOS Internals team ''strongly suggest'' apt-get install into the Ubuntu environment only for this purpose. The same installation of Sun Virtualbox which hosts the Palm SDK emulator can host an Ubuntu 9.10 server with very little effort on any operating system.

Developers wanting to work in an open environment 'without' SB2 can consider using the [[PuffTheMagic NDK]].

==SB2 Homepage==
[http://www.freedesktop.org/wiki/Software/sbox2 http://www.freedesktop.org/wiki/Software/sbox2]pdk

==License==
Scratchbox 2 is distributed under LGPL version 2.1, portions are under GPL version 2. Some minor stuff is under MIT style license.

== Installation on Ubuntu for webOS PDK cross compiling ==

If setting up in a Virtual Box instance, it is recommended that you first complete the openSSH config as described in the VirtualBox tips for Windows users to the right. This is helpful even with a Linux host, as SSH into the PDK Virtual Machine will allow copy and paste of the commands listed below and reduce errors.

== Update ==
There is an automated installer avaliable [http://forums.precentral.net/webos-internals/266139-webos-internals-automated-installers.html#post2718551 here]

<div style="float:right; clear:right; width:30%">{{Ubuntu_VM_notes_for_Windows_users}}</div>
===Toolchain===

===Prerequisites===
Your Ubuntu installation will need the following installed. If you do not have them, run the command after the package name. You can test if they are found by just typing the command name. If it says command not found, you need to install it.

{| border="1"
|+
|'''git''' || sudo apt-get install git-core
|-
|'''gcc''' || sudo apt-get install build-essential
|-
|'''curl''' || sudo apt-get install curl
|-
|'''unzip'''|| sudo apt-get install unzip
|-
|'''autoconf'''|| sudo apt-get install autoconf
|-
|'''subversion'''|| sudo apt-get install subversion
|-
|'''libtool'''|| sudo apt-get install libtool
|-
|'''wget'''|| sudo apt-get install wget
|-
|'''pkg-config'''|| sudo apt-get install pkg-config
|-
|'''gettext'''|| sudo apt-get install gettext
|-
|'''fakeroot'''|| sudo apt-get install fakeroot
|-
|'''javac'''|| sudo apt-get install sun-java6-jdk
|-
|'''ant'''|| sudo apt-get install ant
|-
|'''xsltproc'''|| sudo apt-get install xsltproc
|-
|'''intltool'''|| sudo apt-get install intltool
|-
|'''mkimage'''|| sudo apt-get install uboot-mkimage
|-
|'''lsdiff'''|| sudo apt-get install patchutils
|-
|'''flex'''|| sudo apt-get install flex
|-
|'''bison'''|| sudo apt-get install bison
|-
|'''libssl-dev'''|| sudo apt-get install libssl-dev
|-
|'''libz-dev'''|| sudo apt-get install libz-dev
|-
|'''libbz2-dev'''|| sudo apt-get install libbz2-dev
|-
|'''xar'''|| sudo apt-get install xar
|-
|'''help2man'''|| sudo apt-get install help2man
|-
|'''texinfo'''|| sudo apt-get install texinfo
|-
|'''automake 1.10'''|| sudo apt-get install automake1.10
|-
|'''autopoint'''|| sudo apt-get install autopoint
|}

* it has been reported that sun-java6-jdk isn't necessary

If you're uncertain at all, just cut and paste the following. If they are already installed, they'll be skipped.

sudo apt-get install git-core build-essential curl unzip autoconf subversion libtool wget pkg-config gettext fakeroot ant xsltproc intltool uboot-mkimage patchutils flex bison libssl-dev libz-dev libbz2-dev xar help2man texinfo automake1.10 autopoint

'''Note:''' If you are a beginner with Ubuntu Linux Distribution, you should update all the packages on your system to avoid problems when you will compile. 
Use these 2 command line : 
Update repositories :
sudo aptitude update
And next, update the packages :
sudo aptitude safe-upgrade

If you're on a 64-bit system, you will also need to install the ia32-libs package.

'''Note:''' The ''make toolchain'' command and later steps will download approximately a half-gig of tools and sources from various locations. Do not start this if you do not have time for a large download. Additionally, if you already have downloaded a copy of the correct version of the WebOS doctor, you can reduce the download time by copying the doctor file into cross-compile/doctors/ with the correct name. This will cause the appropriate command to skip that download. Note that codesourcery rate limts downloads and at a minimum this process will take 10 to 15 minutes irrespective of your connection speed.

====Start setup====
Create a preware folder, copy the cross-compile tools into it (if you have not installed git, apt-get install git-core), and use a make script to begin the set up of the compilation toolchain.

sudo mkdir -p /srv/preware
cd /srv/preware
sudo chmod 777 .
git clone git://git.webos-internals.org/preware/cross-compile.git
cd cross-compile
make toolchain

If errors occur, browse the [http://git.webos-internals.org/?p=preware/cross-compile.git;a=shortlog repository online] and checkout earlier commits until you get something that gets through "make toolchain" and the later "make stage" commands like so:

git checkout <commit-ish>
make toolchain
make stage

====Fix mmap errors====
The following commands appear redundant. They are not. The install this fixes your mmap config to fix an mmap: permission denied error, but we don't need the package itself. (Do each command separately with cut and paste).

sudo apt-get install qemu-arm-static
sudo apt-get remove qemu-arm-static

: OR As a workaround, if this package is not available,
::: the following commands can be executed in a root shell (sudo -s) to fix the mmap configuration to enable qemu-arm to work.

echo "vm.mmap_min_addr = 4096" > /etc/sysctl.d/mmap_min_addr.conf
/etc/init.d/procps restart

(note that the value should not be "0". 4096 is chosen to avoid null pointer attacks.)

====Verify sh shell====
On Ubuntu /bin/sh is a symbolic link to dash. This will cause errors with the make stage command below, as some of the scripts assume bash. Run the following command to see what shell sh is linked to.

ls -l /bin/sh

If the result is a link to dash:

lrwxrwxrwx 1 root root 4 2010-07-06 23:55 /bin/sh -> dash

You will want to correct it with the following:

sudo dpkg-reconfigure dash

You will be asked if you want to "Install dash as /bin/sh?". Select "<No>" and bash will be used. Rerun the command to verify:

ls -l /bin/sh

You should now see:

lrwxrwxrwx 1 root root 4 2010-07-09 21:12 /bin/sh -> bash

====Setup Scratchbox====
Now, use apt-get to setup scratchbox...

sudo apt-get install scratchbox2 qemu-kvm-extras

...and set it up for compiling for webOS.

cd /srv/preware/cross-compile/toolchain/arm-2007q3/arm-none-linux-gnueabi/libc
PATH=/srv/preware/cross-compile/toolchain/arm-2007q3/bin:${PATH} sb2-init -c /usr/bin/qemu-arm armv7 arm-none-linux-gnueabi-gcc
cd /srv/preware/cross-compile

Then:

make stage

Once this setup is complete, compiling sdl apps for webOS is very simple.

==Verified installed clean list==

If you have successfully built the WIDK from scratch, with NO problems, feel free to add your information to this list. This will help us assess what distributions and versions it is fully compatible with.

{| border="1" class="wikitable"
|-
|'''IRC name'''
|'''Linux Distribution'''
|'''Version'''
|'''Date'''
|'''Comments'''
|-
|Scoutcamper
|Ubuntu
|9.04,9.10,10.04,10.10
|10-18-10
|Works Great!
|}

It just doesn't work tried for over a week, with fresh Ubuntu 10.4 inside and outside of virtual box, fails on libtool for common/fuse/. Tried -j4 option with make stage, tried make staging-armv7. Also installed automake-1.9 after seeing complaints about that. -- please sign your comments

==Errors during make stage (22:46, 10 October 2010)==

===automake1.10===

If you see the error below, you need the latest automake (1.10)

/usr/share/automake-1.9/am/depend2.am: am__fastdepOBJC does not appear in AM_CONDITIONAL
configure.in:88: installing `./config.guess'
configure.in:88: installing `./config.sub'
Makefile.am: installing `./INSTALL'
autoreconf2.50: automake failed with exit status: 1

Install automake1.10 and it should work (according to [http://old.nabble.com/AC_PROG_OBJC-and-automake-1.9-td22434760.html this page])

===math_vfp.S===

There may be some errors with compiling math_vfp.c that look like this:

math_vfp_asm.S:107: Error: selected processor does not support `fldmias r1!,{s0}'
math_vfp_asm.S:107: Error: selected processor does not support `fldmias r2!,{s1}'
math_vfp_asm.S:107: Error: selected processor does not support `fadds s2,s0,s1'
math_vfp_asm.S:107: Error: selected processor does not support `fstmias r0!,{s2}'
math_vfp_asm.S:107: Error: selected processor does not support `fmrx lr,fpscr'
math_vfp_asm.S:107: Error: selected processor does not support `fmxr fpscr,fp'

Using information from [https://gstreamer.ti.com/gf/project/gstreamer_ti/forum/?_forum_action=MessageReply&message_id=6188&action=ForumBrowse this thread at TI], edit two files in packages/common/liboil/build/armv6/liboil/arm/ and change math_vfp.c (line 33) and math_vfp_asm.S (line 27) from

#if __VFP_FP__

to

#if defined(__VFP_FP__) && !defined(__SOFTFP__)

If you re-run make stage, the code is created again, so when it starts compiling hit ^Z (ctrl-Z) to pause and then edit the file and type "fg" to continue as before.

===Libtool===

make[5]: Entering directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -Wall -g -O2 -MT libdotconf_la-dotconf.lo -MD -MP -MF .deps/libdotconf_la-dotconf.Tpo -c -o libdotconf_la-dotconf.lo `test -f 'dotconf.c' || echo './'`dotconf.c
libtool: Version mismatch error. This is libtool 2.2.6b, but the
libtool: definition of this LT_INIT comes from libtool 2.2.6.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6b
libtool: and run autoconf again.
make[5]: *** [libdotconf_la-dotconf.lo] Error 63
make[5]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6/src'
make[4]: *** [install-recursive] Error 1
make[4]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf/build/armv6'
make[3]: *** [build/armv6.built] Error 2
make[3]: Leaving directory `/srv/preware/cross-compile/packages/common/libdotconf'
make[2]: *** [build_common/libdotconf] Error 2
make[2]: Leaving directory `/srv/preware/cross-compile'
make[1]: *** [staging-armv6] Error 2
make[1]: Leaving directory `/srv/preware/cross-compile'
make: *** [stage] Error 2

Confirmed by 3 people. Fix this by either (your choice)
*upgrading to Ubuntu 10.04 or newer (the WIDK now relies on a slightly newer version of libtool that's not in 9.10 or earlier)
*updating libtool to 2.2.6b-2 (backported to 9.10, see available downloads on http://linuxappfinder.com/package/libtool#ubuntu_karmicpartner)

If you're getting an error where sb2-init gives you the following output:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

Running /usr/bin/sb2-build-libtool failed
You can run this manually later, otherwise your
sb2 environment is correctly setup and ready to use

You need to upgrade qemu. Alternatively, if your sb2-init output fails with a different output, like this:

checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

sb2-init completed successfully, have fun!

Then you need to upgrade scratchbox, too (install 2.0 instead of 1.99).

===Ecore===
*TRUE and FALSE are not defined

Manually add the definition:

#ifndef TRUE
# define TRUE 1
#endif

#ifndef FALSE
# define FALSE 0
#endif

===/bin/sh errors===
If you are getting a "bad fd number" or other /bin/sh error, make sure your /bin/sh points to bash, not another shell (such as dash.)

Go back through the Verify sh shell section above to correct.

==Sample build of [[Application:Doom]]==

Now, go to [[Building DOOM with scratchbox2]] and follow the simple directions.

==In Process Enhancements==
[[Extracting the PDK on Linux]]

Backing Up via Rsync

2010-08-24T10:03:22Z

Pcworld: /* Setting up the host */ -mistake in /etc/rsyncd.conf

=Synopsis=

The rsync remote-update protocol allows rsync to transfer just the differences between two sets of files across the network link, using an efficient checksum-search algorithm.

Some of the additional features of rsync are:

* support for copying links, devices, owners, groups and permissions
* exclude and exclude-from options similar to GNU tar
* a CVS exclude mode for ignoring the same files that CVS would ignore
* can use any transparent remote shell, including rsh or ssh
* does not require root privileges
* pipelining of file transfers to minimize latency costs
* support for anonymous or authenticated rsync servers (ideal for mirroring)

=Background & Purpose=

Using rsync as a means to make full backups of the Pre, both for disaster recovery and convenience. I have been using Rsync as a means to backup all my Gentoo and FreeBSD servers, and even a 4TB volume on our NetApp. I was able to restore every system simply by using rsync to push the files to a new disk/array. Using a special string of commands, rsync backups are nearly as depth-oriented as 'dd', while still being much more convenient.

=Requirements=

*1 Unix-based computer (with access to the same WIFI or [[USBnet_networking_setup | usbnet]] subnet as the Pre)
*On your Palm Pre, you need to have [[Portal:Accessing_Linux | access to linux]] and have completed the [[Next_steps|next steps]] after accessing linux.

The Unix-based computer will be consistently referred to as the "host".

The rsync binary is part of Palm's original package, so it is possible to make a wrap-around gui-based ipk for users who do not want access to linux.

=Backup Procedure=

==Notice==
The backup method has been tested, but there are '''no guarantees''' explicitly or implicitly given for data replication and retention. These tools have worked exceptionally well for me, but they might not work for you.

Out of respect for Sprint, I will only document how to use rsync over WIFI or [[USBnet_networking_setup | usbnet]]. '''I strongly disadvise against using rsync over EVDO (even through SSH). This process is bandwidth intensive and we don't want Sprint complaining to Palm.'''

==Quick Overview==
1. We will set up the rsync daemon on the Palm Pre and make it acccessible by the host.

2. The host will be set up to download the Pre's files.

3. The transfer will take place.

4. The daemon on the Pre will be killed to prevent anyone else from gaining access.

==Setting up the Pre==
1. Access your Pre via WIFI or [[USBnet_networking_setup | usbnet]].

2. Edit '''/etc/rsyncd.conf''' and make sure you fill in the host IP address (your computer)

pid file = /var/run/rsyncd.pid
uid = root
gid = root
hosts allow = '''FILL_YOUR_HOST_IP_HERE'''
hosts deny = *
use chroot = no

[root]
path = /

3. Start the rsync daemon and allow the rsync daemon to communicate with the host. Make sure you fill in the host IP address (your computer):
<source lang=bash>
export IPADDRESS='''enter the IP Address of your host'''
rsync --daemon && /usr/sbin/iptables -I INPUT 1 -p TCP --dport 873 -s $IPADDRESS -j ACCEPT
</source>

==Setting up the host==
1. Make sure you are the root user.
<source lang=bash>
sudo -i
</source>

or

<source lang=bash>
su -l
</source>

2. On the host, you will need to create a directory where the Palm Pre will back up the files. My example will be '''/media/pre-backup'''
<source lang=bash>
mkdir /media/pre-backup
</source>

==Running the transfer==
===On the host===

1. If you want to exclude any directories you are already backing up (or simply don't want to include), add --exclude=/path/to/your/dir after "-stats" in the command (in Step 3). You will need to do this for every directory you wish to NOT include in the transfer.

2. '''1st time:''' If this is the first time running the backup, make sure to create the /sys and /proc directories (we're excluding them in the backup, but the directory needs to be there for the filesystems to mount correctly). Replace /media/pre-backup with the backup directory.

mkdir /media/pre-backup/sys /media/pre-backup/proc

3. Fill your IP Address in the command below, along with your excludes (if you have any), and begin the transfer from the host computer. '''Make sure to set the correct backup directory (if you deviated from /media/pre-backup), otherwise you could overwrite data on your host machine.'''
<source lang=bash>
export IPADDRESS='''enter the IP Address of your pre'''
rsync -HrlptgoDPvvS --force --delete --del --stats --exclude=/sys --exclude=/proc rsync://root@$IPADDRESS/root/ /media/pre-backup/
</source>

3a. Every time you run the transfer, it will retain the exact same file-structure of the Pre, only deleting files that don't exist and only sending files that have changed.

==Disabling the rsync daemon on the Pre==

1. You need to disable the rsync daemon on the Pre to prevent anyone from gaining access to your files. To kill the rsync daemon, you will need to find the Process ID first, then kill the process.
<source lang=bash>
ps auxw | grep rsync
root 11567 0.0 0.0 10480 624 ? Ss 09:18 0:00 rsync --daemon
root 11576 0.0 0.0 6124 640 pts/1 S+ 09:18 0:00 grep rsync (IGNORE THIS ONE)
</source>

Then kill the process:
<source lang=bash>
kill 11567
</source>

=Restore Procedure=
==Quick Overview==
1. Set up the host's rsync daemon

2. Gain access to the Pre's Linux.

3. Transfer the backed-up files to the pre and pray it works.

==Setting up the host==
1. Edit '''/etc/rsyncd.conf''' (or '''/usr/local/etc/rsyncd.conf''' for FreeBSD). Check your documentation. Be sure to fill in the Pre's IP Address, and set the correct directory for the Pre backup (my example will be '''/media/pre-backup''').

pid file = /var/run/rsyncd.pid
uid = root
gid = root
hosts allow = '''FILL_YOUR_PALM_PRE_IP_HERE'''
hosts deny = *
use chroot = no

[pre-backup]
path = /media/pre-backup/

2. Start the rsync daemon (you can use an init script, I'm using the command below just for simplicity. Check your documentation)
<source lang=bash>
rsync --daemon
</source>

==Setting up the Pre and restoring==

A. For the scope of this guide, the requirements above still apply for the Palm Pre: you need to have [[Portal:Accessing_Linux | access to linux]].

1. Access the Pre via WIFI or usbnet.

2. Turn off the GUI while we restore all the files.
<source lang=bash>
/sbin/initctl stop LunaSysMgr
</source>

3. Fill your IP Address in the command below, and start the transfer. This command will take everything from your Host system and overwrite '''EVERYTHING''' on the Pre.
<source lang=bash>
export IPADDRESS='''enter the IP Address of your host'''
cd /
mount -o remount,rw /
mount -o remount,rw /boot
mount -o remount,rw /media/internal
rsync -HrlptgoDPvvS --force --delete --del --stats rsync://root@$IPADDRESS/pre-backup/ /
</source>

3a. If you have any "Out of Space" issues, try removing the ''--delete --del'' and replacing it with ''--delete-before''

4. Reboot immediately and pray it works.
<source lang=bash>
reboot
</source>

=Development/Improvement Ideas=
*'''I need more people to test the restore process and get back to me with suggestions.'''
*It would be awesome if the Palm Pre supported NFS, otherwise we're stuck to setting up '''/etc/rsyncd.conf''' on the Pre (for backup) and the Host (for restore).
*A gui wrapper is possible because the Palm Pre comes shipped with rsync. Also, there needs to be an easy Windows server program to make this mainstream, only thing to use at the moment that's Windows based is cygwin. Otherwise we're stuck with Unix.
*It's possible to create a cron job to run the backup every evening over WIFI (especially if you dock you're phone overnight). The cron job would be run from the Host computer. It's also recommended to set up iptables for allowing port 873 only for the host on the interface eth0 or usb0.
* Would be nice to be able to have it run at a low priority and not kill any ssh connections. Have tried renicing the rsync daemons but has had no affect.

=Contributor(s)=
*hopspitfire
*NetWhiz

Talk:Backing Up via Rsync

2010-08-23T18:24:13Z

Pcworld: New section: Error in /etc/rsyncd.conf on host?

==Rsync Daemon==

Why turn on the rsync daemon at all? This could easily be accomplished simply by running

'''rsync -HrlptgoDPvvS --force --delete --del --stats -e ssh root@IPADDRESS:/ /media/pre-backup/'''

Also, since ''-P'' includes ''--progress'', there's no reason to call it a second time.

-JackieRipper

We don't have a root password set up on the Pre, it's using sudo therefore that's why ssh won't work. Rsyncd.conf gives the rsync daemon root privileges so it can mirror the device. I'm be open to suggestions, but I'm trying to make this fit in with the [[Next_steps | next steps]] guide and limit the number of steps.

Thanks for pointing out the redundancy on --progress.

-hopspitfire

Ahhh yes. I keep forgetting that not everyone set up keys for root access.

-JackieRipper

You dont need to be root to use the rsync over ssh to backup, the pervious command will work if you are using the username and password set up in the optware setup.

'''rsync -HrlptgoDPvvS --force --delete --del --stats -e username@IPADDRESS:/ /media/pre-backup/'''

I also dont think you need the "ssh" in the command the new versions of rsync use it automatically.
I have writen up another tutorial of how to back up the pre without setting up the rsync daemon. check it out [http://forums.precentral.net/web-os-development/207665-using-rsync-do-complete-backup-your-pre.html here]. I have not done a restore yet so I still have to look into that but I see no reason why it cant be done over ssh as long as the partition is r/w and the user has sudo configured.

-elpollodiablo

The problem with running 'rsync -avz' (in your article) is that the files in your backup directory won't get removed when they're not present on the Pre, only overwritten. Have you tested your command above with a normal user account, and did you run into any permission issues? I tested the restore process and it works so far with the methods in the article. -[[User:Hopspitfire|hopspitfire]] 16:07, 13 October 2009 (UTC)

Yes you are correct mine is not set up to delete folder/files that are no longer on the Pre. I didnt want to do that, I wanted it to back up all the files and keep a backup in case I needed to go back to files I had which I deleted from my Pre. I am also only overwriting the files that have changed. For a general backup utility your command would be best. I have not tested the command above but I have used the one in my article to back up my pre. There was a few problems one with the /dev/gadget folder it backedup one file then it seems to froze on me. so I exclude that folder and ran it again. It restarted on me in /sys/devices/ I excluded that folder and it all seemed to work, but there were alot of errors in the /sys folder. so I am probably going to exclude that one as well. why are you excluding the /proc folder? here is my final code:
'''rsync -avz --size-only --exclude gadget/ --exclude sys/ --progress / username@sshserverIP:/Directory/To/Backup/To'''

--[[User:Elpollodiablo1|Elpollodiablo1]] 01:09, 14 October 2009 (UTC)

==Additions==

I've added these to my .profile on the Pre:
exclude1="--exclude=/proc --exclude=/sys --exclude=/tmp/webdiskcache"
exclude2="--exclude=/media/internal/AUDIO --exclude=/media/internal/Place_iTunes_Uses"
syncopt1="-az --partial --progress --stats --delete-after --bwlimit=300 --numeric-ids"
syncpath=" / me@$IPADDRESS:~/PreRSync/ "
alias Sync='d=`date +%Y%m%d.%H%M%S` ; sudo rsync --rsync-path=sudo\ rsync $syncopt1 -b --backup-dir=~/PreRSync.bak/$d $syncpath $exclude1 $exclude2'
On the server in the /etc/sudoers I've added something like this (not sure this is the most secure thing to do):
me ALL=(ALL) ALL, NOPASSWD: /usr/bin/rsync
Now I can simply login to the Pre and run Sync, it prompts for a password at the server but hostkeys could be used to avoid that.
The addition of the dated backup options means that I get a copy of any removed or overwritten files at the server.
I use something called cwrsync which I believe is the cygwin rsync command without installing all of cygwin, might be handy and simple enough for windows users.
--[[User:Dolio|Dolio]] 07:02, 1 October 2009 (UTC)

:Nice additions and thanks for sharing, feel free to add them to the article. I'll have to try these myself. -[[User:Hopspitfire|hopspitfire]] 07:05, 1 October 2009 (UTC)

==Pre Rebooting Issue==

If you don't exclude some of the directories then the Pre reboots when the backup process touches them. [[User:hmagoo|-hmagoo]]

:Can you specify which files/directories prompt the reboot? -[[User:Hopspitfire|hopspitfire]] 02:57, 20 August 2009 (UTC)

::I could narrow it down to proc and/or sys, that's narrow enough for me to exclude both, any progress on restore testing? I'm not running an emulator. [[User:hmagoo|-hmagoo]]

:I tested the restore process and it works. Can you run the backup process and send the output to a file (rsync ... > /media/internal/rsync.log) and post it? -[[User:Hopspitfire|hopspitfire]] 00:49, 24 August 2009 (UTC)

::[http://sites.google.com/site/hmagoosite/rsync-outputs.tar.gz rsync-outputs.tar.gz] this was the console and log output from running a backup. I had already a backup in place in the destination but excluded /dev, /sys/ and /proc initially, ran it this time without those exclusions to test it out (again, as I saw this reboot the very first time I tried this method). rebooted right after this line in the console, similar in the log.
rsync: read errors mapping "/sys/devices/platform/lcd-controller/ctrl_reg_dump" (in root): No data available (61)
[[User:hmagoo|-hmagoo]]
::I ran the backup again excluding /sys and everything completed, only errors I got in the console were:

rsync: send_files failed to open "/proc/sys/kernel/sched_nr_migrate" (in root): Permission denied (13)

rsync: send_files failed to open "/proc/sys/net/ipv4/route/flush" (in root): Permission denied (13)

rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1524) [generator=3.0.5]

[[User:hmagoo|-hmagoo]]

Thanks for attaching your log. /sys and /proc don't need to be included in the backup, but /dev does (to initialize devices on boot). After testing the backup and restore, the easiest way is just mkdir the /sys and /proc directories and exlude them in the backup. Does the pre still restart when you excluded those directories?? -[[User:Hopspitfire|hopspitfire]] 21:23, 26 August 2009 (UTC)

Shouldn't /dev exist fine after a restore and before rsync backup restore? I guess if you made some strange volume changes, but still. --[[User:NetWhiz|NetWhiz]] 21:59, 26 August 2009 (UTC)

I was using /dev as an example of a directory that _shouldn't_ be excluded in the backup process, so /dev will exist after a backup prior to a restore (otherwise the Pre won't boot because it can't initialize the mapper devices for storage). -[[User:Hopspitfire|hopspitfire]] 22:37, 26 August 2009 (UTC)

You mean it SHOULD be excluded b/c you will not need to restore it. --[[User:NetWhiz|NetWhiz]] 22:54, 26 August 2009 (UTC)

(failed=reboot).. failed with no excludes. successful with /dev/,/proc,/sys excluded. successful with /sys excluded. but with those three error messages.--[[User:Hmagoo|Hmagoo]] 23:52, 26 August 2009 (UTC)

:@NetWhiz: /dev needs to be populated on the actual filesystem (before devfs/udev get loaded) for a *nix system to boot.

:@Hmagoo: Thanks, I went ahead and fixed the lines in the article.

:-[[User:Hopspitfire|hopspitfire]] 00:12, 27 August 2009 (UTC)

I understand, BUT when you do a restore with WebOS Doctor it will already be there. Are we not talking about the same thing or are we just cross talking? --[[User:NetWhiz|NetWhiz]] 01:11, 27 August 2009 (UTC)

:OH, I'm talking about a restore using rsync ;) (in this guide, after the intial webOS Doctor). I still don't know if we should be overwriting the entire system (with the rsync backup, including /dev). Any ideas on this? My reasoning for doing a full system overwrite is version compatibility. -[[User:Hopspitfire|hopspitfire]] 01:16, 27 August 2009 (UTC)

:LOL! I would say NOT to overwrite /dev b/c it should already be setup correctly and there is nothing anyone should be doing in there with any mod anyway that I have seen. Trying to overwrite some of the virtual devices can be a BAD thing as some have seen (crashes, freezes, etc.) Just my thoughts. --[[User:NetWhiz|NetWhiz]] 01:58, 27 August 2009 (UTC)

== Error in /etc/rsyncd.conf on host? ==

Shouldn't been in the /etc/rsyncd.conf on the host ([[Backing Up via Rsync#Setting up the host 2]]) instead of "[root]" "[pre-backup]"? On restoring process came "unknown module" until I changed it. --[[User:Pcworld|Pcworld]] 18:24, 23 August 2010 (UTC) (sorry for my bad English please!)