WebOS Internals - User contributions [en]

WebOS Survival Kit

2011-12-02T23:52:54Z

Jakeeeee: /* Backup your contacts to Gmail */

This page is available in three lanuages:
:[[Image:Australia.png]] [[Image:USA.png]] [[WebOS_Survival_Kit|WebOSSurvival Kit]]
:[[Image:Germany.png]] [[WebOS_Survival_Kit-DE| webOS Survival Kit (Überlebensset)]]
:[[image:Italy.png]] [[Kit_di_Sopravvivenza_webOS|Kit di Sopravvivenza webOS]]

''The year is 2013. It's a post-webOS world.''

''HP has sold off the webOS group, and the buyer has stripped it for the patents, and shut down all the infrastructure needed to support webOS devices.''

''The HP App Catalog and the Palm Profile servers can no longer be reached.''

''The @palm and @webOSdev twitter accounts no longer respond. The developer forums are a barren wasteland.''

''Some people take the easy way out, and simply move to another platform.''

''Others learn how to survive, using'' ... '''''The webOS Survival Kit'''''

= Follow @webosinternals =

Get a Twitter account and follow @webosinternals. Think of it as your Early Warning System and Short-Wave Radio. When the disaster arrives, watch for further instructions.

Other key homebrew developers to follow include: @JayCanuck @TheRealSconix

= Install [http://bit.ly/phd-ac Preware Homebrew Documentation] =

In a post-webOS world, you will need to have Preware installed on your device. The HP App Catalog will no longer be available to you, so you need to get the documentation you need to install Preware now.

The [http://bit.ly/phd-ac Preware Homebrew Documentation] app will guide you through the details of many of the following steps already with step-by-step installation instructions.

= Install Preware =

Use the instructions in the [http://bit.ly/phd-ac Preware Homebrew Documentation] app to do this. Do not delay, you need to have Preware installed now, not after HP and webOS are gone.

If you have any problems running WebOS Quick Install (especially if you are on a Windows computer), install the [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and follow the troubleshooting guide in there.

Do not rest until you have Preware installed and working. It is your key to app distribution and installation in a post-webOS world.

By following these instructions, you will also end up with WebOS Quick Install available on your host computer. Multiple redundant ways to install things is key in a post-webOS world.

= Empty Your Profile =

The data in your HP webOS Account (formerly Palm Profile) will not be available to you in a post-webOS world.

Move it all to somewhere else now. Your webOS device supports a number of Synergy providers - choose one with which you are comfortable and move all your data there.

==Backup your contacts to Gmail==
To create a .vcf (VCard or "Virtual Business Card") file of all your contacts that can then be imported into an Address Books/Contact Lists across a wide range of applications and devices (including any webOS device) just follow the following steps:

-Open the Phone App: For CDMA phones, dial ##66623#. For GSM phones, dial #*66623# and press Call Button

-Tap the green "CelleBrite Export" button

-After "Step 1: Export File..." is complete, follow directions for "Step 2: Connect USB cable" and connect your phone to a computer via a USB cable

-Access the USB drive by tapping on USB drive notification

-Make sure that you set the option on the computer's File Manager to "Show hidden files and folders" and then open up the ".temp" folder on your phone

-A file called "PmMigration.vcf" will be inside the ".temp" folder. Just copy this file off your phone and on to your computer.

-Properly eject your phone from USB Mode

-You can either just backup this file for later, or use it to import your contact list into a program or site that accepts .vcf files (e.g. Gmail).

Note that this will save ALL your contacts, not just those in your Palm Profile (to Merge Duplicate contacts in Gmail, go to Contacts > More, Find & Merge Duplicate Contacts).

= Install Save/Restore =

Go into Preware. Search for "Save/Restore" and install the app. Save your application settings.

If you depend on an application which is not supported by Save/Restore, then visit the [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore thread] on PreCentral and put up a bounty for developers to add support for that app.

Make sure you copy the saverestore directory contents from your webOS device to your host computer (or online storage account) regularly.

= Save Your Tokens =

Install the "Show Properties" app from Preware, and email yourself a '''Full''' token list (use the '''Full''' menu option, not the '''Comms Board Swap''' menu option).

Don't worry about what it all means right now, just do it. With the token list and the webOS Doctor you can resurrect your device from just about any calamity.

= Download the webOS Doctor =

Make sure you have the correct webOS Doctor for your device downloaded from the HP servers and available locally on your host computer.

Visit our [[WebOS_Doctor_Versions|webOS Doctor Versions]] page and download the correct webOS Doctor version now.

In a post-webOS world, the doctors will not be available from HP servers, so make sure you have your own copy archived now.

= Get Command-Line Ready =

To perform some key survival measures, you will need to have a way to access the Linux command line on your device.

The latest Novacom drivers can be found on http://opensource.palm.com/packages.html at the bottom of the page. In a post-webOS world, that page will no longer be accessible. Download the drivers for your current and future host computer platforms before they disappear.

Install the drivers and test that your host computer recognises your webOS device when you plug it in.

Work out how to use novaterm or the WOSQI command line interface (which is a GUI wrapper around a novacom connection) to access the Linux command line on your device.

The [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] contains a visual how-to on how to get access to the command line on your device from a host computer.

Install Xecutah to access the command line from on your device itself.

Many post-webOS survival techniques may require command line interactions. Get ready for this now. Learn some [[Basic Linux Use]] techniques before it is too late.

= What About Activation? =

There are techniques available for all webOS devices to bypass both carrier and HP/Palm activation requirements. We can take a brand-new never-used webOS device and make it fully functional with access to any HP/Palm servers.

= What About My Apps? =

When the HP App Catalog is shut down, we will need to be able to reinstall paid apps that we have purchased on the devices for which they have been purchased.

[http://bit.ly/webos-survival-kit The webOS Survival Kit] includes everything you need to be in a position ready for further instructions to be able do that when the eventuality arises.

The tools required to re-package apps for re-installation via Preware have already been written and tested.

Obviously, whilst the app catalog is still functioning it is not appropriate to give those instructions.

= Cover All Devices =

Perform all the above steps for every webOS device which you own.

= Buy Some Batteries =

Batteries dont last forever and in a post-webOS world they will stop being made. Make sure you grab a couple to keep you going.

On all webOS devices other than the TouchPad it's straight-forward to replace batteries (your warranty will be well and truly expired by that time).

For the TouchPad, [http://www.ifixit.com/Guide/Installing-HP-TouchPad-Battery/6082/1 it's not easy at all]. So this tip really only applies to the webOS phones.

= Contribute Your Tips =

Subscribe to the [http://forums.precentral.net/webos-internals/303114-webos-survival-kit.html corresponding forum thread] in the [http://forums.precentral.net/webos-internals/ WebOS Internals forum] and post any other tips for inclusion in [http://bit.ly/webos-survival-kit The webOS Survival Kit] there or edit this wiki page directly.

= Spread The Word =

Make sure every webOS users has http://bit.ly/webos-survival-kit (the official URL for this page) imprinted in their brain. Write it on a piece of paper, and stick it to your monitor. Never forget it, you will eventually need it.

= Subscribe To Forums =

There are a number of webOS forums with lots of other users who can help you in this time of need.

[http://www.precentral.net PreCentral] and [http://www.webosroundup.com webOSRoundup] are two of the leading information sources.

= Donate =

The homebrew developers who bring you these tools rely on donations to be able to continue to do so.

WebOS Internals: http://donate.webos-internals.org/

Jason Robitaille: http://donate.canuckcoding.ca/

= Don't Panic =

WebOS Internals and other homebrew developers have your back. Don't Panic.

You will be able to use your webOS device for as long as you please, even if all support and infrastructure from HP disappears overnight.

[http://farm3.static.flickr.com/2593/3892664015_e410aac714.jpg We've got you covered.]

WebOS Survival Kit

2011-12-02T23:52:07Z

Jakeeeee:

This page is available in three lanuages:
:[[Image:Australia.png]] [[Image:USA.png]] [[WebOS_Survival_Kit|WebOSSurvival Kit]]
:[[Image:Germany.png]] [[WebOS_Survival_Kit-DE| webOS Survival Kit (Überlebensset)]]
:[[image:Italy.png]] [[Kit_di_Sopravvivenza_webOS|Kit di Sopravvivenza webOS]]

''The year is 2013. It's a post-webOS world.''

''HP has sold off the webOS group, and the buyer has stripped it for the patents, and shut down all the infrastructure needed to support webOS devices.''

''The HP App Catalog and the Palm Profile servers can no longer be reached.''

''The @palm and @webOSdev twitter accounts no longer respond. The developer forums are a barren wasteland.''

''Some people take the easy way out, and simply move to another platform.''

''Others learn how to survive, using'' ... '''''The webOS Survival Kit'''''

= Follow @webosinternals =

Get a Twitter account and follow @webosinternals. Think of it as your Early Warning System and Short-Wave Radio. When the disaster arrives, watch for further instructions.

Other key homebrew developers to follow include: @JayCanuck @TheRealSconix

= Install [http://bit.ly/phd-ac Preware Homebrew Documentation] =

In a post-webOS world, you will need to have Preware installed on your device. The HP App Catalog will no longer be available to you, so you need to get the documentation you need to install Preware now.

The [http://bit.ly/phd-ac Preware Homebrew Documentation] app will guide you through the details of many of the following steps already with step-by-step installation instructions.

= Install Preware =

Use the instructions in the [http://bit.ly/phd-ac Preware Homebrew Documentation] app to do this. Do not delay, you need to have Preware installed now, not after HP and webOS are gone.

If you have any problems running WebOS Quick Install (especially if you are on a Windows computer), install the [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] app and follow the troubleshooting guide in there.

Do not rest until you have Preware installed and working. It is your key to app distribution and installation in a post-webOS world.

By following these instructions, you will also end up with WebOS Quick Install available on your host computer. Multiple redundant ways to install things is key in a post-webOS world.

= Empty Your Profile =

The data in your HP webOS Account (formerly Palm Profile) will not be available to you in a post-webOS world.

Move it all to somewhere else now. Your webOS device supports a number of Synergy providers - choose one with which you are comfortable and move all your data there.

==Backup your contacts to Gmail==
To create a .vcf (VCard or "Virtual Business Card") file of all your contacts that can then be imported into an Address Books/Contact Lists across a wide range of applications and devices (including any webOS device) just follow the following steps:

-Open the Phone App: For CDMA phones, dial ##66623#. For GSM phones, dial #*66623# and press Call Button

-Tap the green "CelleBrite Export" button

-After "Step 1: Export File..." is complete, follow directions for "Step 2: Connect USB cable" and connect your phone to a computer via a USB cable

-Access the USB drive by tapping on USB drive notification

-Make sure that you set the option on the computer's File Manager to "Show hidden files and folders" and then open up the ".temp" folder on your phone

-A file called "PmMigration.vcf" will be inside the ".temp" folder. Just copy this file off your phone and on to your computer.

-Properly eject your phone from USB Mode

-You can either just backup this file for later, or use it to import your contact list into a program or site that accepts .vcf files (e.g. Gmail)

Note that this will save ALL your contacts, not just those in your Palm Profile(to Merge Duplicate contacts in Gmail, go to Contacts > More, Find & Merge Duplicate Contacts)

= Install Save/Restore =

Go into Preware. Search for "Save/Restore" and install the app. Save your application settings.

If you depend on an application which is not supported by Save/Restore, then visit the [http://forums.precentral.net/webos-internals/237558-save-restore-community-development.html Save/Restore thread] on PreCentral and put up a bounty for developers to add support for that app.

Make sure you copy the saverestore directory contents from your webOS device to your host computer (or online storage account) regularly.

= Save Your Tokens =

Install the "Show Properties" app from Preware, and email yourself a '''Full''' token list (use the '''Full''' menu option, not the '''Comms Board Swap''' menu option).

Don't worry about what it all means right now, just do it. With the token list and the webOS Doctor you can resurrect your device from just about any calamity.

= Download the webOS Doctor =

Make sure you have the correct webOS Doctor for your device downloaded from the HP servers and available locally on your host computer.

Visit our [[WebOS_Doctor_Versions|webOS Doctor Versions]] page and download the correct webOS Doctor version now.

In a post-webOS world, the doctors will not be available from HP servers, so make sure you have your own copy archived now.

= Get Command-Line Ready =

To perform some key survival measures, you will need to have a way to access the Linux command line on your device.

The latest Novacom drivers can be found on http://opensource.palm.com/packages.html at the bottom of the page. In a post-webOS world, that page will no longer be accessible. Download the drivers for your current and future host computer platforms before they disappear.

Install the drivers and test that your host computer recognises your webOS device when you plug it in.

Work out how to use novaterm or the WOSQI command line interface (which is a GUI wrapper around a novacom connection) to access the Linux command line on your device.

The [http://bit.ly/wosqi-guide WOSQI Homebrew Guide] contains a visual how-to on how to get access to the command line on your device from a host computer.

Install Xecutah to access the command line from on your device itself.

Many post-webOS survival techniques may require command line interactions. Get ready for this now. Learn some [[Basic Linux Use]] techniques before it is too late.

= What About Activation? =

There are techniques available for all webOS devices to bypass both carrier and HP/Palm activation requirements. We can take a brand-new never-used webOS device and make it fully functional with access to any HP/Palm servers.

= What About My Apps? =

When the HP App Catalog is shut down, we will need to be able to reinstall paid apps that we have purchased on the devices for which they have been purchased.

[http://bit.ly/webos-survival-kit The webOS Survival Kit] includes everything you need to be in a position ready for further instructions to be able do that when the eventuality arises.

The tools required to re-package apps for re-installation via Preware have already been written and tested.

Obviously, whilst the app catalog is still functioning it is not appropriate to give those instructions.

= Cover All Devices =

Perform all the above steps for every webOS device which you own.

= Buy Some Batteries =

Batteries dont last forever and in a post-webOS world they will stop being made. Make sure you grab a couple to keep you going.

On all webOS devices other than the TouchPad it's straight-forward to replace batteries (your warranty will be well and truly expired by that time).

For the TouchPad, [http://www.ifixit.com/Guide/Installing-HP-TouchPad-Battery/6082/1 it's not easy at all]. So this tip really only applies to the webOS phones.

= Contribute Your Tips =

Subscribe to the [http://forums.precentral.net/webos-internals/303114-webos-survival-kit.html corresponding forum thread] in the [http://forums.precentral.net/webos-internals/ WebOS Internals forum] and post any other tips for inclusion in [http://bit.ly/webos-survival-kit The webOS Survival Kit] there or edit this wiki page directly.

= Spread The Word =

Make sure every webOS users has http://bit.ly/webos-survival-kit (the official URL for this page) imprinted in their brain. Write it on a piece of paper, and stick it to your monitor. Never forget it, you will eventually need it.

= Subscribe To Forums =

There are a number of webOS forums with lots of other users who can help you in this time of need.

[http://www.precentral.net PreCentral] and [http://www.webosroundup.com webOSRoundup] are two of the leading information sources.

= Donate =

The homebrew developers who bring you these tools rely on donations to be able to continue to do so.

WebOS Internals: http://donate.webos-internals.org/

Jason Robitaille: http://donate.canuckcoding.ca/

= Don't Panic =

WebOS Internals and other homebrew developers have your back. Don't Panic.

You will be able to use your webOS device for as long as you please, even if all support and infrastructure from HP disappears overnight.

[http://farm3.static.flickr.com/2593/3892664015_e410aac714.jpg We've got you covered.]

Remove/Reduce Drag Radius

2011-08-30T22:23:56Z

Jakeeeee:

==Overview==
When dragging any element, system widget or the Launcher, there is a radius of 25 pixels before your drag goes into effect. Once the radius has been exceeded, WebOS will jerk suddenly to meet your finger's location. This large distance, and the subsequent sudden motion, reduce usability.

==Download your version==

webOS 1.4.5: http://forums.precentral.net/webos-patches/249025-patch-reduce-drag-radius-10px.html

webOS 2.1: http://forums.precentral.net/webos-patches/286547-patch-increase-touch-response-luna-aka-make-webos-feel-like-ios.html

webOS 3.0.2: "Increase Touch Sensitivity And Smoothness 10"

USB Host Mode

2011-08-30T22:17:09Z

Jakeeeee:

External vbus power is easy:

Connect your type A (with ID-pin shorted) microUSB to USB cable into webOS. Plug the data leg of USB-Y cable (usually found with 2.5" external HDD enclosures and such) into this cable. Plug the root of the Y cable into a hub or whatever device you plan to use.
Plug the "power" leg of the Y cable into some powered usb socket be it a powered hub, a PC or whatever.
Enjoy your usb device.

Example of cable that will work: http://www.ebay.com/itm/High-Quality-micro-USB-USB-Female-Cable-USB-OTG-N900-/170687828639?pt=PDA_Accessories&hash=item27bdc9929f
Search for OTG cable on eBay and thee are plenty.

Internal VBUS:

TBD.

WebOS 2 Upgrade

2011-08-30T22:16:28Z

Jakeeeee: /* Tutorials that have been updated to match the latest instructions */

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

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

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

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

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

= Other Tutorials =
'''Note that this wiki page is always the authoritative source of information about this process, so you should refer to this page first for any and all instructions. Here are some other pages which you may find useful in addition to this page. They do not replace the information on this page, which you should read from top to bottom first.'''
== Tutorials that have been updated to match the latest instructions ==
* ''PreCentral'' forum user @malpha recorded a two-part [http://www.youtube.com/watch?v=CJB8NJ72kZg video overview] of the process as she followed this step-by-step. {Sprint Pre-, Ubuntu}.
* ''[http://www.webosworld.com/ WebOS World]'' writer Jake Morrison has written a [http://webosworld.com/2011/03/07/my-meta-doctor-to-2-1-experience/ How-To guide] based directly off the [http://www.webos-internals.org/wiki/WebOS_2_Upgrade WebOS Internals walkthrough]. {Sprint Pre-, Ubuntu}.

== Tutorials that are out of date and should not be relied upon ==
* ''PreCentral'' forum user @djwhitey recorded a 9-minute [http://www.youtube.com/watch?v=PF2ciiNFxLc walkthrough] (includes Activation Error). {Sprint Pre-, Win7 x86, Ubuntu Server 10.04}.
* ''PreCentral'' forum user @innocentbystander has written a start-to-finish guide to installing and building the Meta Doctor under Mac OS 10.6 for those with little or no experience with the command line. It can be found [http://forums.precentral.net/showthread.php?p=2885787 here].

= Using MetaDoctor Scripts =

== Step 0: Backup your device ==
A guide by PreCentral on backing up your device can be found [http://www.precentral.net/backup here].

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

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

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

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

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

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

=== MetaDoctor ===

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

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

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

=== Palm SDK ===

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

=== Novacom Drivers ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Verizon Pre 2 ===
<pre><nowiki>
./scripts/meta-verizon-pre2-2.1.0
</nowiki></pre>

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

The Verizon specific apps (Amazon MP3, VZ Navigator, Skype Mobile) and Voice Dialing will be present and fully functional.

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

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

=== WR Pre ===

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

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

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

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

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

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

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

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

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

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

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

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

= Caveats =

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

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

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

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

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

Known working carrier apps are listed below.

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

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

=== AT&T ===
* So far the only AT&T specific app tested with this method is the Amazon MP3 app, which may be installed using the process found [http://forums.precentral.net/palm-pre-2/279364-how-install-amazon-mp3-app-your-unlocked-pre2-step-step.html here]. However, non-free music has NOT yet been tested with this process.

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

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

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

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

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

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

For example, you could follow these steps:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Application:Preware

2011-08-25T23:27:21Z

Jakeeeee: /* Installing Preware with WebOS Quick Install */

[[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.6.3 (8 June 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 and the Palm Pixi. Preware allows the user to install any package from any of the open standard package repositories on preware.org (or any other location that hosts an open standard package repository). Preware relies on a custom written service developed from community research which allows the mojo app to talk to the built-in ipkg tool.

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

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

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

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

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

 
===Key Features===
Install / Remove / Update:
*Homebrew Applications including advanced applications with special requirements.
*WebOS Themes
*Patches
*webOS Kernels
*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.

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

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 phone should remain disconnected
# Download the latest Preware package onto your computer from http://get.preware.org/
## To install Preware on a phone, 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 appears, and verify that your phone is in developer mode
# Connect your device to your computers USB port, and select 'Just Charge'
# 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.1.1 or later of [http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-1-1-a.html 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.precentral.net/canuck-coding/274461-webos-quick-install-v4-2-3-a.html WebOS Quick Install v4.2.3]'''

# Install the required Software
## [http://www.java.com/en/download/installed.jsp?detect=jre&try=1 Click here] to verify that you have the latest java installed on your computer and update if needed
## [http://dl.dropbox.com/u/2774158/WebOSQuickInstall-4.2.3.jar Click Here] to download WebOS Quick Install v4.2.3
# Put your device in [[Getting started|Developer Mode]]
# Connect your device to your computer with the USB cable, and select "Just Charge" (do not select USB Drive)
# Run WebOS Quick Install. If 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.
# 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 phone in a subdirectory you will remember (maybe "Palm"?). If you already have it, skip this step.
##* '''Do not run the webOS Doctor.'''
# Put your device into [[Getting started|Developer Mode]].
#* '''Windows users:''' When connecting your device to the computer for the first time, you will be prompted to install new hardware. Click Next to start the device installation. You may get a message regarding Novacom drivers not being installed. If so, you can disregard it. Once your device is installed, proceed with the Preware installation.
# Download the [http://get.preware.org/ Preware Standalone Installer] (you should choose the latest file name PrewareInstaller-X.Y.Z.jar) and place it in the same directory as the webOS Doctor .jar file.
# Run the Preware Installer.
# Click on the Tools menu and choose Install Drivers. This will install the Palm Novacom drivers for webOS devices.
# Once the drivers have finished installing, click on Install Preware. After Preware is installed, your device will be unresponsive for a few seconds while Luna restarts.

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

<source lang="bash">
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/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.

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

 

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

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

 

=Usage=

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

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

{| style="color:black; background-color:#FFFFE0;" cellpadding="3" cellspacing="0" Border="1"
|align="center" colspan="4" | '''Default Feeds'''
|-
|align="center" | [http://ipkg.preware.org/feeds/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.
 

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



= Operating notes =

===Limitations===
No known limitations.

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

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

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

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

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

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

Patch Launcher Reset Scroll on Page Change

2011-08-22T00:42:16Z

Jakeeeee:

{{template:patch}}

This is only for webOS 1.4.5 or lower. webOS 2.x and higher have a different launcher implementation that will not work with this patch.
==Introduction==

If you have many apps on a page, you may have to scroll to see some of those. The launcher maintains the scroll state (the amount you have scrolled) on each page, which means when you return to a page, you are still at the location that you last scrolled to. This can be annoying. For example, it can make it difficult to train your muscle memory because, when repeating the same steps, the app you want is not always at the same location on the screen. This patch resets the scroll of each page back to the top when it goes out of view.

Update Dec '09: I've changed the way the patch is implemented, this new version is now compatible with the Wrap Pages patch.

==Editing Process==

* SSH in.
* Remount the filesystem as read/write:
<blockquote><source lang="bash">
sudo rootfs_open -w
</source></blockquote>
* Load launcher-assistant.js in vi:
<blockquote><source lang="bash">
sudo vi /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
</source></blockquote>
* Locate the end of the setup method, around line 98:
<blockquote><source lang="javascript">
// setup the initial dimensions for launcher/global-search
this.adjustLayout();
},

ready: function() {
this.globalSearchAssistant.ready();
},
</source></blockquote>
* Add the lines below to the end of the setup method (that is, make sure they're inside the '},' before the ready method on line 102), so that it now looks like this:
<blockquote><source lang="javascript">
// setup the initial dimensions for launcher/global-search
this.adjustLayout();

// add a separate listener for resetting the scroll position on page changes, and also on deactivate
Mojo.listen($('launcher_root'), Mojo.Event.propertyChange, this.resetScrollPosition.bindAsEventListener(this));
Mojo.listen(this.controller.document, Mojo.Event.deactivate, this.resetScrollPosition.bindAsEventListener(this));
},

ready: function() {
this.globalSearchAssistant.ready();
},
</source></blockquote>
* Add the following method somewhere else in the file, I suggest just below the ready method and before the deleteAllPages method, around line 105 (don't forget the comma after the closing brace, unless you add it right at the end of the class, as the last method):
<blockquote><source lang="javascript">
resetScrollPosition: function(event) {
var pageIndex = (event.type === 'mojo-event-deactivate') ? this.activePageIndex : event.value;
var scroller = this.getPageScroller(pageIndex);
if (scroller && scroller.mojo) { scroller.mojo.revealTop(); }
},
</source></blockquote>
* Save the file and quit vi.
* Remount the filesystem as read only - this should reboot your Pre:
<blockquote><source lang="bash">
sudo rootfs_open -w
</source></blockquote>

==Patch Process==

An older version of the patch is in the git/Preware repository, hopefully this version will be submitted soon. Until then, you can copy and paste the source below. Visit [[Applying Patches]] for info on how to use it. You can also apply it using webOS Quick Install. To apply the patch, follow the instructions above, and after remounting the filesystem as read/write, do the following:

* Apply the patch (In this example, I have the patch file located in my home directory under '''patches'''):
<blockquote><source lang="bash">
cd /
sudo patch -p0 --backup-if-mismatch < ~/patches/reset-scroll.patch
</source></blockquote>
<blockquote>
This is what you should see if it ran properly:
<source lang="text">
patching file /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
</source></blockquote>
* Remount the filesystem as read only as described above.

===Patch Source (reset-scroll.patch)===

<source lang="diff">
--- /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js.orig Sat Dec 5 11:48:12 2009
+++ /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js Thu Dec 3 19:42:03 2009
@@ -98,5 +98,9 @@
// setup the initial dimensions for launcher/global-search
this.adjustLayout();
+
+ // add a separate listener for resetting the scroll position on page changes, and also on deactivate
+ Mojo.listen($('launcher_root'), Mojo.Event.propertyChange, this.resetScrollPosition.bindAsEventListener(this));
+ Mojo.listen(this.controller.document, Mojo.Event.deactivate, this.resetScrollPosition.bindAsEventListener(this));
},

ready: function() {
@@ -188,6 +188,12 @@
onResize: function(event) {
this.adjustLayout();
},

+ resetScrollPosition: function(event) {
+ var pageIndex = (event.type === 'mojo-event-deactivate') ? this.activePageIndex : event.value;
+ var scroller = this.getPageScroller(pageIndex);
+ if (scroller && scroller.mojo) { scroller.mojo.revealTop(); }
+ },
+
/* remove page data and their corresponding HTML */
deleteAllPages: function() {

</source>

Application:Quake

2011-08-22T00:36:09Z

Jakeeeee:

[[Category:SDL]]

=Quake=
[[Image:Quake_icon3_copy.png|left]]
Quake is a first-person shooter video game that was released by ''id Software'' on June 22, 1996. It was the first game in the popular Quake series of video games.

==Story==
The player takes the role of an un-named protagonist sent into a portal in order to stop an enemy code-named "Quake". Previously, the government had been experimenting with teleportation technology, and upon development of a working prototype called a "Slipgate", this enemy has compromised the human connection with their own teleportation system, using it to insert death squads into the "human" dimension, supposedly in order to test the martial capabilities of humanity.
The sole surviving protagonist in Operation Counterstrike is the player, who must advance, starting each of the four episodes from a human held but overrun military base, before fighting through into other dimensions, traversing these via slipgate or their otherworld equivalent. Once passing through each slipgate, the player's main objective is to survive and locate the exit which will take him to the next level, not unlike that of id Software's previous hit, Doom.

==License==
The source code of the Quake and QuakeWorld engines was licensed under the GPL in 1999. The id Software maps, objects, textures, sounds and other creative works remain under their original license. The shareware distribution of Quake is still freely redistributable and usable with the GPLed engine code. One must purchase a copy of Quake in order to receive the registered version of the game which includes more single player episodes and the deathmatch maps.

==Credit==
Ported by Will Dietz Jan 2010. 
Packaged by Rod Whitby 
Keyboard/Control Scheme & Overlay art by Jack87 

Thanks to Jack87 for lots of help testing and feedback.

On October 11, 2006, John Romero released the original map files for all of the levels in Quake under the GPL. [http://planetquake.gamespy.com/fullstory.php?id=106530]

== Donate ==
Lots of work has gone into making this a great game for you to enjoy!
If you like it please consider [https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=3S7ULCYRCDWS8&lc=US&item_name=Will%20Dietz&item_number=palm%20pre&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_LG%2egif%3aNonHosted donating]

==Screenshots==
[[Image:Quake_Menu.png]]
[[Image:Quake_Lava.png]]
[[Image:Quake_Ogre.png]]
== Controls ''v1.1.0 and up'' ==
Controls were designed with the idea of JHBN forming a diamond and when thumb is on J at 45 degrees holding phone comfortably you should be able to reach all action keys easily without the need to take thumb off the keyboard. 

With Virtual Joy Stick and Strafe Gesture you can play with keyboard closed if you like. 

 
'''Gesture controls:''' 
Gesture down= Next Weapon 
Gesture up= Previous Weapon 
Hold Gesture= Strafe mode where joystick left right is strafe 
 
'''Screen Controls:''' 
Just as displayed in picture with virtual Joystick for Look & Move 
Tip 1: Find the "dead zone" for the virtual joystick this is where nothing happens while finger is on screen. Once dead zone is established roll your thumb around it. The further you go the faster you will move/turn. It acts like a real joystick so keep that in mind. 
Tip 2: Moving around with finger on gesture strafe seems to work really well and letting go to turn/aim. 
Tip 3: Lower mouse speed in options menu. 
 
'''Red: Action''' 
J= Fire 
H= Strafe Left 
N= Strafe Right 
B= Jump 
Sym= Fire 
 
'''Blue: Turbo''' 
I= Turbo Forward 
U= Turbo Strafe Left 
K= Turbo Strafe Right 
 
'''Yellow: Weapons''' 
Select Weapon by pressing corresponding number 1-8 
 
'''Purple: Only work during Action Keyboard mode''' ''Note- "Orange+Key" means you '''hold down''' orange key and press corresponding button'' 
@= Toggle Between Action & Normal Keyboard (For typing in console use etc.) 
Q= Menu/Esc 
'= Quick Load (Orange+L) 
_=Quick Save (Orange+,) 
W= Left arrow 
S= Up Arrow 
Z= Right Arrow 
A= Down Arrow 
%= Console (Orange+I) 
0=Toggle overlay(Orange+@) 
 
[[Image:Quake-pre-Config.png]]

== Notes ==
Discussion on the topic can be found [http://forums.precentral.net/webos-internals/222222-quake.html Here] 
Video can be found on WebOS-Internals youtube [http://www.youtube.com/webosinternals channel] 
-Keep in mind Quake does not have a "Use Key" 
-You can customize Keyboard controls in the options menu ''Note: Remember to toggle to regular keyboard mode when doing this''. 

====Beta Builds====
Beta builds are available--there are no guarantees on betas, but we'll try to keep them stable, and they'll get you extra features early. Run "wget http://wdtz.org/files/quake.sh -O- |/bin/sh" from terminal to get the beta.

== Changelog ==
 
v1.2.0 Added visual control overlay, Settings/binds/cvars now are saved across execution, Misc bugfixes. 
v1.1.0 Increased performance, Drastic improvements to control scheme (including virtual joystick, continuous fire, added gesture controls), Modal Keyboard, fix for Segfault Error" (doom worked but not quake). 
v1.0.11 Playable Release: Fixed New Game crash, Better Performance, Adjusted resolution for Pre Screen, Added Keyboard Bindings w/Touch screen controls 
v1.0.9 Initial version (Demo) 

[http://git.webos-internals.org/?p=games/sdlquake.git;a=shortlog git Shortlog]

== Known Issues ==

--Improved in 1.1.0: Performance could be better 
--Fixed in 1.1.0: Unable to lower sliders on option screen 
--Fixed in 1.1.0 replaced with gesture weapon change: Quick Weapon Switch is not functioning 
--Fixed in 1.1.0: Need to implement holding down fire for continues fire

FirstUse Application Functionality

2011-08-22T00:32:52Z

Jakeeeee:

This page will be used to document what we now about the com.palm.app.firstuse application (the one which allows you to create and/or access a HP Profile).

com.palm.app.firstuse (hereafter referred to as just "firstuse") starts in app-assistant.js as follows:

* StageAssistant(stageController)
** pushHome()
*** pushScene("home");
*** isInitialized = false;
*** if (running on emulator)
**** setupSimulator();
***** isDevice = false;
***** isActivated = true;
***** Account.platformType = "CDMA";
***** simStatus = "simready";
***** isConnected = true;
**** pushScene("language");
*** else
**** isInitialized = true;
**** setUpFirstUse();
***** isInitialized = true;
***** isConnected set according to network connection status
**** activateDevice();
***** eventually pushScene("language");

*; isTelephonyReady();
*: luna-send -i palm://com.palm.telephony/isTelephonyReady
*:; emulator
*:: {"returnValue":true,"errorCode":0,"extended":{"security":false,"networkRegistered":true,"emergency":false,"ready":true,"power":true,"securityLocked":false,"dataRegistered":true,"radioConnected":true}}
*:; device
*::

Portal:Where to Get Started

2011-08-22T00:28:45Z

Jakeeeee:

__notoc__
{{portal-one-column-blue
|header=What is it that you want to do on your webOS device?
|column1=Look below and choose the best option for you:

# '''''Easy''''' Using a computer to install homebrew applications on your webOS device. Suitable for those that do not have a lot of computer know-how. Compatible with Mac, Windows, and Linux Computers.
# '''''Moderate''''' The second option is best for those that have some computer know-how and want to get to know ''how'' their device works a little bit more. This option requires more work, however. Since webOS devices are Linux based devices, it is helpful if you know how to use Linux. Cross-platform compatible.

''*Hacking is called "Accessing linux." It is highly recommended that you '''read this article''' if you are thinking about doing option two: [http://forums.precentral.net/web-os-development/193679-accessing-linux-rooting-your-pre.html Accessing Linux!="Rooting your webOS device"]''
}}

'''Recommended for Non-Computer-Savvy Folks'''
----

{{portal-two-columns
|column1=
{{nav-block
|imageName={{#icon:Favorites.png|Getting Started|48|Tutorials_webOS_Installing_An_Ipk}}
|title=[[Tutorials_webOS_Installing_An_Ipk|Option 1: Installing a Homebrew App Easily]]
|description= [http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-2-3-a.html WebOS Quick Install]is a Mac/Windows/Linux computer app that installs the homebrew apps onto your webOS device. You'll need [http://www.java.com/en/download/manual.jsp the latest version of Java] and install WebOS Quick Install, and it'll do the rest for you!

To install and update applications while on the device use [[Application:Preware|Preware]]. Follow the steps on the page to install [[Application:Preware|Preware]] through the WebOS Quick Install.

}}
|column2=
{{nav-block
|imageName={{#icon:WebOS.png|Webos Applications|48|Portal:webOS_Applications}}
|title=[[Portal:webOS_Applications|WebOS Homebrew App Listings]]
|description=This list contains pages where people can write about their various applications and is the portal for WebOS-Internals projects.

Note: [http://forums.precentral.net/homebrew-apps/194104-links-all-homebrew-apps-updated-8-3-a.html PreCentral has more apps available.]
Already able to add apps? Then check out the homebrew apps made by webos-internals.org users and affiliates.
Can be used with options 1 and 2.
}}
}}
'''Recommended for Moderate-Advanced Computer Users'''
----

{{portal-two-columns
|column1=
{{nav-block
|imageName={{#icon:Kompare-icon.png|Getting Started|48|Portal:Accessing_Linux}}
|title=[[Portal:Accessing_Linux|Option 2: Accessing Linux]]
|description=Do you want to take the extra risk of accessing the Linux on your webOS device? Or do you have a good understanding of Linux or programing? (Cross-platform)

Remember-Read this article if you're going to [http://forums.precentral.net/web-os-development/193679-accessing-linux-rooting-your-pre.html Access Linux!="Root your webOS device"]
}}
|column2=
{{nav-block
|imageName={{#icon:Applications-development.png|Development Tools|48}}
|title=[[Portal:Tools|Development Tools and Programs]]
|description=Get all the tools you need to make your own applications, to access you webOS device's Linux codes, for cross-compiling, etc,
}}
}}
{{portal-one-column-blue
|header=Need help/Want to contribute?
|column1=
{{nav-block
|imageName={{#icon:System-help.png|Development Tools|48|Portal:Community}}
|title=[[Portal:Community|IRC]]
|description=
Download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.

The same rules apply as those on the wiki for discussion.
}}
|leftnav=
[[About|Overview]] '''·''' [[Help:Questions|Questions]] '''·''' [[Help:Contents|Help]]
}}

Portal:Where to Get Started

2011-08-22T00:27:56Z

Jakeeeee:

__notoc__
{{portal-one-column-blue
|header=What is it that you want to do on your webOS device?
|column1=Look below and choose the best option for you:

# '''''Easy''''' Using a computer to install homebrew applications on your webOS device. Suitable for those that do not have a lot of computer know-how. Compatible with Mac, Windows, and Linux Computers.
# '''''Moderate''''' The second option is best for those that have some computer know-how and want to get to know ''how'' their device works a little bit more. This option requires more work, however. Since webOS devices are Linux based devices, it is helpful if you know how to use Linux. Cross-platform compatible.

''*Hacking is called "Accessing linux." It is highly recommended that you '''read this article''' if you are thinking about doing option two: [http://forums.precentral.net/web-os-development/193679-accessing-linux-rooting-your-pre.html Accessing Linux!="Rooting your webOS device"]''
}}

'''Recommended for Non-Computer-Savvy Folks'''
----

{{portal-two-columns
|column1=
{{nav-block
|imageName={{#icon:Favorites.png|Getting Started|48|Tutorials_webOS_Installing_An_Ipk}}
|title=[[Tutorials_webOS_Installing_An_Ipk|Option 1: Installing a Homebrew App Easily]]
|description= [http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-2-3-a.html WebOS Quick Install]is a Mac/Windows/Linux computer app that installs the homebrew apps onto your webOS device. You'll need [http://www.java.com/en/download/manual.jsp the latest version of Java] and install WebOS Quick Install, and it'll do the rest for you!

To install and update applications while on the device use [[Application:Preware|Preware]]. Follow the steps on the page to install [[Application:Preware|Preware]] through the WebOS Quick Install.

}}
|column2=
{{nav-block
|imageName={{#icon:WebOS.png|Webos Applications|48|Portal:webOS_Applications}}
|title=[[Portal:webOS_Applications|WebOS Homebrew App Listings]]
|description=This list contains pages where people can write about their various applications and is the portal for WebOS-Internals projects.

Note: [http://forums.precentral.net/homebrew-apps/194104-links-all-homebrew-apps-updated-8-3-a.html PreCentral has more apps available.]
Already able to add apps? Then check out the homebrew apps made by webos-internals.org users and affiliates.
Can be used with options 1 and 2.
}}
}}
'''Recommended for Moderate-Advanced Computer Users'''
----

{{portal-two-columns
|column1=
{{nav-block
|imageName={{#icon:Kompare-icon.png|Getting Started|48|Portal:Accessing_Linux}}
|title=[[Portal:Accessing_Linux|Option 2: Accessing Linux]]
|description=Do you want to take the extra risk of accessing the Linux on your webOS device? Or do you have a good understanding of Linux or programing? (Cross-platform)

Remember-Read this article if you're going to [http://forums.precentral.net/web-os-development/193679-accessing-linux-rooting-your-pre.html Access Linux!="Root your Pre"]
}}
|column2=
{{nav-block
|imageName={{#icon:Applications-development.png|Development Tools|48}}
|title=[[Portal:Tools|Development Tools and Programs]]
|description=Get all the tools you need to make your own applications, to access you webOS device's Linux codes, for cross-compiling, etc,
}}
}}
{{portal-one-column-blue
|header=Need help/Want to contribute?
|column1=
{{nav-block
|imageName={{#icon:System-help.png|Development Tools|48|Portal:Community}}
|title=[[Portal:Community|IRC]]
|description=
Download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.

The same rules apply as those on the wiki for discussion.
}}
|leftnav=
[[About|Overview]] '''·''' [[Help:Questions|Questions]] '''·''' [[Help:Contents|Help]]
}}

Portal:Where to Get Started

2011-08-22T00:27:00Z

Jakeeeee:

__notoc__
{{portal-one-column-blue
|header=What is it that you want to do on your webOS device?
|column1=Look below and choose the best option for you:

# '''''Easy''''' Using a computer to install homebrew applications on your webOS device. Suitable for those that do not have a lot of computer know-how. Compatible with Mac, Windows, and Linux Computers.
# '''''Moderate''''' The second option is best for those that have some computer know-how and want to get to know ''how'' their device works a little bit more. This option requires more work, however. Since webOS devices is a linux based devices, it is helpful if you know how to use Linux. Cross-platform compatible.

''*Hacking is called "Accessing linux." It is highly recommended that you '''read this article''' if you are thinking about doing option two: [http://forums.precentral.net/web-os-development/193679-accessing-linux-rooting-your-pre.html Accessing Linux!="Rooting your Pre"]''
}}

'''Recommended for Non-Computer-Savvy Folks'''
----

{{portal-two-columns
|column1=
{{nav-block
|imageName={{#icon:Favorites.png|Getting Started|48|Tutorials_webOS_Installing_An_Ipk}}
|title=[[Tutorials_webOS_Installing_An_Ipk|Option 1: Installing a Homebrew App Easily]]
|description= [http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-2-3-a.html WebOS Quick Install]is a Mac/Windows/Linux computer app that installs the homebrew apps onto your webOS device. You'll need [http://www.java.com/en/download/manual.jsp the latest version of Java] and install WebOS Quick Install, and it'll do the rest for you!

To install and update applications while on the device use [[Application:Preware|Preware]]. Follow the steps on the page to install [[Application:Preware|Preware]] through the WebOS Quick Install.

}}
|column2=
{{nav-block
|imageName={{#icon:WebOS.png|Webos Applications|48|Portal:webOS_Applications}}
|title=[[Portal:webOS_Applications|WebOS Homebrew App Listings]]
|description=This list contains pages where people can write about their various applications and is the portal for WebOS-Internals projects.

Note: [http://forums.precentral.net/homebrew-apps/194104-links-all-homebrew-apps-updated-8-3-a.html PreCentral has more apps available.]
Already able to add apps? Then check out the homebrew apps made by webos-internals.org users and affiliates.
Can be used with options 1 and 2.
}}
}}
'''Recommended for Moderate-Advanced Computer Users'''
----

{{portal-two-columns
|column1=
{{nav-block
|imageName={{#icon:Kompare-icon.png|Getting Started|48|Portal:Accessing_Linux}}
|title=[[Portal:Accessing_Linux|Option 2: Accessing Linux]]
|description=Do you want to take the extra risk of accessing the Linux on your webOS device? Or do you have a good understanding of Linux or programing? (Cross-platform)

Remember-Read this article if you're going to [http://forums.precentral.net/web-os-development/193679-accessing-linux-rooting-your-pre.html Access Linux!="Root your Pre"]
}}
|column2=
{{nav-block
|imageName={{#icon:Applications-development.png|Development Tools|48}}
|title=[[Portal:Tools|Development Tools and Programs]]
|description=Get all the tools you need to make your own applications, to access you webOS device's Linux codes, for cross-compiling, etc,
}}
}}
{{portal-one-column-blue
|header=Need help/Want to contribute?
|column1=
{{nav-block
|imageName={{#icon:System-help.png|Development Tools|48|Portal:Community}}
|title=[[Portal:Community|IRC]]
|description=
Download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.

The same rules apply as those on the wiki for discussion.
}}
|leftnav=
[[About|Overview]] '''·''' [[Help:Questions|Questions]] '''·''' [[Help:Contents|Help]]
}}

How To Recover

2011-08-21T21:53:53Z

Jakeeeee: /* Device not booting? webOS Doctor How-To */

= Device not booting? webOS Doctor How-To =
{{tux|Tux_with_Broken_Pre.png|float:right;}}

ALWAYS RUN THE WEBOS DOCTOR ON THE COMMAND LINE SO THAT YOU CAN SEE THE CONSOLE OUTPUT WHICH CONTAINS ALL THE DEBUGGING INFORMATION - YOU WILL USUALLY SPOT THE ISSUE IMMEDIATELY IF YOU DO THIS: java -jar doctor-file

If you're running Windows, the java executable is probably not within the PATH environment variable. This means you need to first navigate to your java installation folder before running the webOS Doctor. On most systems it will be something like this:
# cd "c:\Program Files (x86)\Java\jre6\bin"
# java -jar <path to doctor-file>

Fortunately, HP has created a tool called webOS Doctor intended for users to easily restore their devices in the event that they cannot boot for one reason or another.

Note: Before Trying the following steps below. Try removing the battery first and reinsert the battery and turn on the device this will determine whether or not you need to perform the following steps.

Note 2: As of WebOS 1.3.1 your USB data (Pictures, Videos, etc.) is no longer deleted during the process. Older versions of WebOS Doctor WILL DELETE ALL YOUR PERSONAL DATA ON THE DEVICE.

'''HP webOS Doctor:''' [http://ws.palm.com/webosdoctor/serialnumberinitial.htm http://ws.palm.com/webosdoctor/serialnumberinitial.htm]

'''All HP WebOS Doctor Versions:''' [http://www.webos-internals.org/wiki/Webos_Doctor_Versions http://www.webos-internals.org/wiki/Webos_Doctor_Versions]

After the download is complete, launch webOS Doctor:

# Select your language
# Accept the license agreement
# Connect your device to your PC [http://kb.hpwebos.com/wps/portal/kb2/common/article/44768_en.html while in recovery mode] via USB and select "Next" when it becomes available
{{tux|Tux_with_Pre_and_Screwdriver.png|float:right;}}
After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your device and you cannot go past step 3 above, try the following steps:

# Disconnect the USB cable
# Completely power off the device (hold down the power button until the option to power off appears)
# Remove the battery
# Connect the USB cable and wait for the battery image to appear on the screen (or wait around 10-15 seconds)
# Hold down the Up button on the volume rocker
# While holding the Up button, insert the battery. The USB logo will appear on the screen
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the device into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual HP startup logo.

It may be necessary to manually start novacom in OSX 10.6. To do this search (Apple-space) for "novacomd" and run the "start-novacomd" executable. Your phone should now be detected and the "next" step will be available.

The process usually proceeds as follows:

(If you're on a Mac, you can follow the progress in /var/log/system.log, on a PC the log is in your personal temporary files area)

# WebOS Doctor begins
# At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
# At 4%, the screen changes to the HP logo
# At 9%, the screen changes to a big arrow pointing down to an integrated circuit
# Novaterm access is available from 12% onwards
# The progress bar advances by 2% increments every 20 seconds or so
# If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
# Around 54% the filesystems are being partitioned
# Around 64% the modem firmware is being reflashed
# Around 72% the carrier apps are being installed
# Around 82% the ROM is being verified

If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.

== Doctor disconnects at 8% ==

If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).

If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.

First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):

novacom boot mem:// < nova-installer-image-castle.uImage

After it boots, run novaterm:

novaterm

Once connected to the device, type:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

then type:

mkdosfs -f 1 -s 64 /dev/store/media

Once that completes, put the device back into recovery mode and run the webOS Doctor.

== Modifications to the recovery process ==

Between about 18% and 54% complete, you can novaterm into the device while it is being flashed, and modify the filesystem that will be run after the phone reboots (e.g. to touch /var/luna/preferences/ran-first-use).

If you stay in a mounted directory, you can even cause the flashing to abort after the carrier apps are installed and just before the ROM is verified. This is another point where manual modifications can be made.

After you have made your modifications, unmount any filesystems you have mounted and "tellbootie reboot".

== Can't boot into recovery mode? ==

In the very unlikely event that your device will not boot into recovery mode (indicating that your boot loader on the flash disk may be damaged or corrupted) you can try booting bootie into recovery mode over USB instead: [[Last_Resort_Emergency_BootLoader_Recovery]] '''Note that there has only been one incidence of this being required which ultimately was due to hardware failure, we do not recommend that you attempt this unless you have tried all the steps above exactly as described at least 10 times.'''

Short of hardware damage, it should not be possible to "brick" a device.

'''DANGER - The Veer definitely is brickable.'''

 

= Troubleshooting =

== The Doctor's "Next" button is grayed out! ==

That is, when you're asked to plug in your device, you have plugged it in, and nothing happens. If you have a terminal window open, you may see a message similar to the following repeating indefinitely:

Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0

The first thing to try is simply unplugging the USB cable from your device, and then plugging it back in again. Often this will cause the device to be detected and all will be well. If that does not work, do the following:

=== Windows ===
* Right-Click "My Computer", choose "Manage".
* Click "Services", then on the right find "Novacom".
* Stop the service, then start it
* Try The Doctor again
=== Linux ===
* Open a shell, type "ps -e | grep novacom"
* If nothing comes back, then it's not running.
* "/etc/init.d/novacomd start"
=== OSX ===
* Open Terminal.app
* "sudo /opt/nova/bin/stop-novacomd"
* "sudo /opt/nova/bin/start-novacomd"
* Leave Terminal.app running while flashing the device

Note, older version of the SDK put novacomd in a different location and you would use this command: "sudo /opt/palm/nova/novacomd"

== Attempting to install Novacom fails! ==
=== OSX 10.6 and Higher ===
''This is due to a recent change in the way that launchctl handles LaunchDaemons, something that Novacomd is part of''
* Exit out of the Novacom installer, but do not exit the webOS Doctor itself
* Find /Library/LaunchDaemons/
* Rename com.palm.novacomd to com.palm.novacomd.plist
* Open Terminal.app
* "launchctl unload -w /Library/LaunchDaemons/com.palm.novacomd" ''(This should return that it was unable to unload. That is to be expected!)''
* "sudo launchctl load -w /Library/LaunchDaemons/com.palm.novacomd.plist"
* You should be able to continue with the doctoring and will no longer need to manually run Novacomd

How To Recover

2011-08-21T21:52:49Z

Jakeeeee: /* Device not booting? webOS Doctor How-To */

= Device not booting? webOS Doctor How-To =
{{tux|Tux_with_Broken_Pre.png|float:right;}}

ALWAYS RUN THE WEBOS DOCTOR ON THE COMMAND LINE SO THAT YOU CAN SEE THE CONSOLE OUTPUT WHICH CONTAINS ALL THE DEBUGGING INFORMATION - YOU WILL USUALLY SPOT THE ISSUE IMMEDIATELY IF YOU DO THIS: java -jar doctor-file

If you're running Windows, the java executable is probably not within the PATH environment variable. This means you need to first navigate to your java installation folder before running the webOS Doctor. On most systems it will be something like this:
# cd "c:\Program Files (x86)\Java\jre6\bin"
# java -jar <path to doctor-file>

Fortunately, HP has created a tool called webOS Doctor intended for users to easily restore their devices in the event that they cannot boot for one reason or another.

Note: Before Trying the following steps below. Try removing the battery first and reinsert the battery and turn on the device this will determine whether or not you need to perform the following steps.

Note 2: As of WebOS 1.3.1 your USB data (Pictures, Videos, etc.) is no longer deleted during the process. Older versions of WebOS Doctor WILL DELETE ALL YOUR PERSONAL DATA ON THE DEVICE.

'''HP webOS Doctor:''' [http://ws.HP.com/webosdoctor/serialnumberinitial.htm http://ws.HP.com/webosdoctor/serialnumberinitial.htm]

'''All HP WebOS Doctor Versions:''' [http://www.webos-internals.org/wiki/Webos_Doctor_Versions http://www.webos-internals.org/wiki/Webos_Doctor_Versions]

After the download is complete, launch webOS Doctor:

# Select your language
# Accept the license agreement
# Connect your device to your PC [http://kb.hpwebos.com/wps/portal/kb2/common/article/44768_en.html while in recovery mode] via USB and select "Next" when it becomes available
{{tux|Tux_with_Pre_and_Screwdriver.png|float:right;}}
After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your device and you cannot go past step 3 above, try the following steps:

# Disconnect the USB cable
# Completely power off the device (hold down the power button until the option to power off appears)
# Remove the battery
# Connect the USB cable and wait for the battery image to appear on the screen (or wait around 10-15 seconds)
# Hold down the Up button on the volume rocker
# While holding the Up button, insert the battery. The USB logo will appear on the screen
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the device into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual HP startup logo.

It may be necessary to manually start novacom in OSX 10.6. To do this search (Apple-space) for "novacomd" and run the "start-novacomd" executable. Your phone should now be detected and the "next" step will be available.

The process usually proceeds as follows:

(If you're on a Mac, you can follow the progress in /var/log/system.log, on a PC the log is in your personal temporary files area)

# WebOS Doctor begins
# At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
# At 4%, the screen changes to the HP logo
# At 9%, the screen changes to a big arrow pointing down to an integrated circuit
# Novaterm access is available from 12% onwards
# The progress bar advances by 2% increments every 20 seconds or so
# If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
# Around 54% the filesystems are being partitioned
# Around 64% the modem firmware is being reflashed
# Around 72% the carrier apps are being installed
# Around 82% the ROM is being verified

If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.

== Doctor disconnects at 8% ==

If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).

If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.

First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):

novacom boot mem:// < nova-installer-image-castle.uImage

After it boots, run novaterm:

novaterm

Once connected to the device, type:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

then type:

mkdosfs -f 1 -s 64 /dev/store/media

Once that completes, put the device back into recovery mode and run the webOS Doctor.

== Modifications to the recovery process ==

Between about 18% and 54% complete, you can novaterm into the device while it is being flashed, and modify the filesystem that will be run after the phone reboots (e.g. to touch /var/luna/preferences/ran-first-use).

If you stay in a mounted directory, you can even cause the flashing to abort after the carrier apps are installed and just before the ROM is verified. This is another point where manual modifications can be made.

After you have made your modifications, unmount any filesystems you have mounted and "tellbootie reboot".

== Can't boot into recovery mode? ==

In the very unlikely event that your device will not boot into recovery mode (indicating that your boot loader on the flash disk may be damaged or corrupted) you can try booting bootie into recovery mode over USB instead: [[Last_Resort_Emergency_BootLoader_Recovery]] '''Note that there has only been one incidence of this being required which ultimately was due to hardware failure, we do not recommend that you attempt this unless you have tried all the steps above exactly as described at least 10 times.'''

Short of hardware damage, it should not be possible to "brick" a device.

'''DANGER - The Veer definitely is brickable.'''

 

= Troubleshooting =

== The Doctor's "Next" button is grayed out! ==

That is, when you're asked to plug in your device, you have plugged it in, and nothing happens. If you have a terminal window open, you may see a message similar to the following repeating indefinitely:

Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0

The first thing to try is simply unplugging the USB cable from your device, and then plugging it back in again. Often this will cause the device to be detected and all will be well. If that does not work, do the following:

=== Windows ===
* Right-Click "My Computer", choose "Manage".
* Click "Services", then on the right find "Novacom".
* Stop the service, then start it
* Try The Doctor again
=== Linux ===
* Open a shell, type "ps -e | grep novacom"
* If nothing comes back, then it's not running.
* "/etc/init.d/novacomd start"
=== OSX ===
* Open Terminal.app
* "sudo /opt/nova/bin/stop-novacomd"
* "sudo /opt/nova/bin/start-novacomd"
* Leave Terminal.app running while flashing the device

Note, older version of the SDK put novacomd in a different location and you would use this command: "sudo /opt/palm/nova/novacomd"

== Attempting to install Novacom fails! ==
=== OSX 10.6 and Higher ===
''This is due to a recent change in the way that launchctl handles LaunchDaemons, something that Novacomd is part of''
* Exit out of the Novacom installer, but do not exit the webOS Doctor itself
* Find /Library/LaunchDaemons/
* Rename com.palm.novacomd to com.palm.novacomd.plist
* Open Terminal.app
* "launchctl unload -w /Library/LaunchDaemons/com.palm.novacomd" ''(This should return that it was unable to unload. That is to be expected!)''
* "sudo launchctl load -w /Library/LaunchDaemons/com.palm.novacomd.plist"
* You should be able to continue with the doctoring and will no longer need to manually run Novacomd

How To Recover

2011-08-21T21:51:47Z

Jakeeeee: /* Device not booting? webOS Doctor How-To */

= Device not booting? webOS Doctor How-To =
{{tux|Tux_with_Broken_Pre.png|float:right;}}

ALWAYS RUN THE WEBOS DOCTOR ON THE COMMAND LINE SO THAT YOU CAN SEE THE CONSOLE OUTPUT WHICH CONTAINS ALL THE DEBUGGING INFORMATION - YOU WILL USUALLY SPOT THE ISSUE IMMEDIATELY IF YOU DO THIS: java -jar doctor-file

If you're running Windows, the java executable is probably not within the PATH environment variable. This means you need to first navigate to your java installation folder before running the webOS Doctor. On most systems it will be something like this:
# cd "c:\Program Files (x86)\Java\jre6\bin"
# java -jar <path to doctor-file>

Fortunately, Palm has created a tool called webOS Doctor intended for users to easily restore their devices in the event that they cannot boot for one reason or another.

Note: Before Trying the following steps below. Try removing the battery first and reinsert the battery and turn on the device this will determine whether or not you need to perform the following steps.

Note 2: As of WebOS 1.3.1 your USB data (Pictures, Videos, etc.) is no longer deleted during the process. Older versions of WebOS Doctor WILL DELETE ALL YOUR PERSONAL DATA ON THE DEVICE.

'''Palm webOS Doctor:''' [http://ws.palm.com/webosdoctor/serialnumberinitial.htm http://ws.palm.com/webosdoctor/serialnumberinitial.htm]

'''All Palm WebOS Doctor Versions:''' [http://www.webos-internals.org/wiki/Webos_Doctor_Versions http://www.webos-internals.org/wiki/Webos_Doctor_Versions]

After the download is complete, launch webOS Doctor:

# Select you language
# Accept the license agreement
# Connect your device to you PC [http://kb.hpwebos.com/wps/portal/kb2/common/article/44768_en.html while in recovery mode] via USB and select "Next" when it becomes available
{{tux|Tux_with_Pre_and_Screwdriver.png|float:right;}}
After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your device and you cannot go past step 3 above, try the following steps:

# Disconnect the USB cable
# Completely power off the device (hold down the power button until the option to power off appears)
# Remove the battery
# Connect the USB cable and wait for the battery image to appear on the screen (or wait around 10-15 seconds)
# Hold down the Up button on the volume rocker
# While holding the Up button, insert the battery. The USB logo will appear on the screen
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the device into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

It may be necessary to manually start novacom in OSX 10.6. To do this search (Apple-space) for "novacomd" and run the "start-novacomd" executable. Your phone should now be detected and the "next" step will be available.

The process usually proceeds as follows:

(If you're on a Mac, you can follow the progress in /var/log/system.log, on a PC the log is in your personal temporary files area)

# WebOS Doctor begins
# At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
# At 4%, the screen changes to the palm logo
# At 9%, the screen changes to a big arrow pointing down to an integrated circuit
# Novaterm access is available from 12% onwards
# The progress bar advances by 2% increments every 20 seconds or so
# If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
# Around 54% the filesystems are being partitioned
# Around 64% the modem firmware is being reflashed
# Around 72% the carrier apps are being installed
# Around 82% the ROM is being verified

If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.

== Doctor disconnects at 8% ==

If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).

If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.

First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):

novacom boot mem:// < nova-installer-image-castle.uImage

After it boots, run novaterm:

novaterm

Once connected to the device, type:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

then type:

mkdosfs -f 1 -s 64 /dev/store/media

Once that completes, put the device back into recovery mode and run the webOS Doctor.

== Modifications to the recovery process ==

Between about 18% and 54% complete, you can novaterm into the device while it is being flashed, and modify the filesystem that will be run after the phone reboots (e.g. to touch /var/luna/preferences/ran-first-use).

If you stay in a mounted directory, you can even cause the flashing to abort after the carrier apps are installed and just before the ROM is verified. This is another point where manual modifications can be made.

After you have made your modifications, unmount any filesystems you have mounted and "tellbootie reboot".

== Can't boot into recovery mode? ==

In the very unlikely event that your device will not boot into recovery mode (indicating that your boot loader on the flash disk may be damaged or corrupted) you can try booting bootie into recovery mode over USB instead: [[Last_Resort_Emergency_BootLoader_Recovery]] '''Note that there has only been one incidence of this being required which ultimately was due to hardware failure, we do not recommend that you attempt this unless you have tried all the steps above exactly as described at least 10 times.'''

Short of hardware damage, it should not be possible to "brick" a device.

'''DANGER - The Veer definitely is brickable.'''

 

= Troubleshooting =

== The Doctor's "Next" button is grayed out! ==

That is, when you're asked to plug in your device, you have plugged it in, and nothing happens. If you have a terminal window open, you may see a message similar to the following repeating indefinitely:

Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0

The first thing to try is simply unplugging the USB cable from your device, and then plugging it back in again. Often this will cause the device to be detected and all will be well. If that does not work, do the following:

=== Windows ===
* Right-Click "My Computer", choose "Manage".
* Click "Services", then on the right find "Novacom".
* Stop the service, then start it
* Try The Doctor again
=== Linux ===
* Open a shell, type "ps -e | grep novacom"
* If nothing comes back, then it's not running.
* "/etc/init.d/novacomd start"
=== OSX ===
* Open Terminal.app
* "sudo /opt/nova/bin/stop-novacomd"
* "sudo /opt/nova/bin/start-novacomd"
* Leave Terminal.app running while flashing the device

Note, older version of the SDK put novacomd in a different location and you would use this command: "sudo /opt/palm/nova/novacomd"

== Attempting to install Novacom fails! ==
=== OSX 10.6 and Higher ===
''This is due to a recent change in the way that launchctl handles LaunchDaemons, something that Novacomd is part of''
* Exit out of the Novacom installer, but do not exit the webOS Doctor itself
* Find /Library/LaunchDaemons/
* Rename com.palm.novacomd to com.palm.novacomd.plist
* Open Terminal.app
* "launchctl unload -w /Library/LaunchDaemons/com.palm.novacomd" ''(This should return that it was unable to unload. That is to be expected!)''
* "sudo launchctl load -w /Library/LaunchDaemons/com.palm.novacomd.plist"
* You should be able to continue with the doctoring and will no longer need to manually run Novacomd

How To Recover

2011-08-21T04:34:50Z

Jakeeeee: /* Device not booting? webOS Doctor How-To */

= Device not booting? webOS Doctor How-To =
{{tux|Tux_with_Broken_Pre.png|float:right;}}

ALWAYS RUN THE WEBOS DOCTOR ON THE COMMAND LINE SO THAT YOU CAN SEE THE CONSOLE OUTPUT WHICH CONTAINS ALL THE DEBUGGING INFORMATION - YOU WILL USUALLY SPOT THE ISSUE IMMEDIATELY IF YOU DO THIS: java -jar doctor-file

If you're running Windows, the java executable is probably not within the PATH environment variable. This means you need to first navigate to your java installation folder before running the webOS Doctor. On most systems it will be something like this:
# cd "c:\Program Files (x86)\Java\jre6\bin"
# java -jar <path to doctor-file>

Fortunately, Palm has created a tool called webOS Doctor intended for users to easily restore their devices in the event that they cannot boot for one reason or another.

Note: Before Trying the following steps below. Try removing the battery first and reinsert the battery and turn on the device this will determine whether or not you need to perform the following steps.

Note 2: As of WebOS 1.3.1 your USB data (Pictures, Videos, etc.) is no longer deleted during the process. Older versions of WebOS Doctor WILL DELETE ALL YOUR PERSONAL DATA ON THE DEVICE.

'''Palm webOS Doctor:''' [http://ws.palm.com/webosdoctor/serialnumberinitial.htm http://ws.palm.com/webosdoctor/serialnumberinitial.htm]

'''All Palm WebOS Doctor Versions:''' [http://www.webos-internals.org/wiki/Webos_Doctor_Versions http://www.webos-internals.org/wiki/Webos_Doctor_Versions]

After the download is complete, launch webOS Doctor:

# Select you language
# Accept the license agreement
# Connect your device to you PC via USB and select "Next" when it becomes available
{{tux|Tux_with_Pre_and_Screwdriver.png|float:right;}}
After completion the device will reboot and present you with the activation set-up.

If your PC does not recognize your device and you cannot go past step 3 above, try the following steps:

# Disconnect the USB cable
# Completely power off the device (hold down the power button until the option to power off appears)
# Remove the battery
# Connect the USB cable and wait for the battery image to appear on the screen (or wait around 10-15 seconds)
# Hold down the Up button on the volume rocker
# While holding the Up button, insert the battery. The USB logo will appear on the screen
# "Next" should now be enabled - proceed with the recovery
{{tux|Tux_with_Pre.png|float:right;}}
The above steps will put the device into bootloader recovery mode and should allow the PC to recognize your device and proceed with the restore. In this mode the screen will display a giant USB logo instead of the usual Palm startup logo.

It may be necessary to manually start novacom in OSX 10.6. To do this search (Apple-space) for "novacomd" and run the "start-novacomd" executable. Your phone should now be detected and the "next" step will be available.

The process usually proceeds as follows:

(If you're on a Mac, you can follow the progress in /var/log/system.log, on a PC the log is in your personal temporary files area)

# WebOS Doctor begins
# At 3%, a ramdisk is transferred to the phone, and the phone is rebooted
# At 4%, the screen changes to the palm logo
# At 9%, the screen changes to a big arrow pointing down to an integrated circuit
# Novaterm access is available from 12% onwards
# The progress bar advances by 2% increments every 20 seconds or so
# If it gets stuck at 52% for more than 30 seconds, it's not going to progress further and you will need to try again.
# Around 54% the filesystems are being partitioned
# Around 64% the modem firmware is being reflashed
# Around 72% the carrier apps are being installed
# Around 82% the ROM is being verified

If the process fails at 84% or later, the flash and modem have actually been written, so if you reboot you will get what you were flashing.

== Doctor disconnects at 8% ==

If the webOS Doctor continually disconnects at 8%, then you probably have a corrupted USB drive. This is how you can fix that (note that this will completely and utterly destroy all data on the USB drive).

If you are reading this following an interrupted webOS Doctor, you might want to try to extract the installer uImage from the version that was there before the interrupted procedure. For example if you were upgrading from webOS 2.0.0 to webOS 2.1.0, you might want to try the uImage from the 2.0.0 webOS Doctor jar.

First put the device into recovery mode, then memboot the device using the installer uImage (extracted from your webOS Doctor jar):

novacom boot mem:// < nova-installer-image-castle.uImage

After it boots, run novaterm:

novaterm

Once connected to the device, type:

lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure

then type:

mkdosfs -f 1 -s 64 /dev/store/media

Once that completes, put the device back into recovery mode and run the webOS Doctor.

== Modifications to the recovery process ==

Between about 18% and 54% complete, you can novaterm into the device while it is being flashed, and modify the filesystem that will be run after the phone reboots (e.g. to touch /var/luna/preferences/ran-first-use).

If you stay in a mounted directory, you can even cause the flashing to abort after the carrier apps are installed and just before the ROM is verified. This is another point where manual modifications can be made.

After you have made your modifications, unmount any filesystems you have mounted and "tellbootie reboot".

== Can't boot into recovery mode? ==

In the very unlikely event that your device will not boot into recovery mode (indicating that your boot loader on the flash disk may be damaged or corrupted) you can try booting bootie into recovery mode over USB instead: [[Last_Resort_Emergency_BootLoader_Recovery]] '''Note that there has only been one incidence of this being required which ultimately was due to hardware failure, we do not recommend that you attempt this unless you have tried all the steps above exactly as described at least 10 times.'''

Short of hardware damage, it should not be possible to "brick" a device.

'''DANGER - The Veer definitely is brickable.'''

 

= Troubleshooting =

== The Doctor's "Next" button is grayed out! ==

That is, when you're asked to plug in your device, you have plugged it in, and nothing happens. If you have a terminal window open, you may see a message similar to the following repeating indefinitely:

Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:48 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got controller
Jun 7, 2011 9:33:49 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
INFO: got devices 0

The first thing to try is simply unplugging the USB cable from your device, and then plugging it back in again. Often this will cause the device to be detected and all will be well. If that does not work, do the following:

=== Windows ===
* Right-Click "My Computer", choose "Manage".
* Click "Services", then on the right find "Novacom".
* Stop the service, then start it
* Try The Doctor again
=== Linux ===
* Open a shell, type "ps -e | grep novacom"
* If nothing comes back, then it's not running.
* "/etc/init.d/novacomd start"
=== OSX ===
* Open Terminal.app
* "sudo /opt/nova/bin/stop-novacomd"
* "sudo /opt/nova/bin/start-novacomd"
* Leave Terminal.app running while flashing the device

Note, older version of the SDK put novacomd in a different location and you would use this command: "sudo /opt/palm/nova/novacomd"

== Attempting to install Novacom fails! ==
=== OSX 10.6 and Higher ===
''This is due to a recent change in the way that launchctl handles LaunchDaemons, something that Novacomd is part of''
* Exit out of the Novacom installer, but do not exit the webOS Doctor itself
* Find /Library/LaunchDaemons/
* Rename com.palm.novacomd to com.palm.novacomd.plist
* Open Terminal.app
* "launchctl unload -w /Library/LaunchDaemons/com.palm.novacomd" ''(This should return that it was unable to unload. That is to be expected!)''
* "sudo launchctl load -w /Library/LaunchDaemons/com.palm.novacomd.plist"
* You should be able to continue with the doctoring and will no longer need to manually run Novacomd