http://wiki.webos-internals.org/api.php?action=feedcontributions&feedformat=atom&user=KostkaWebOS Internals - User contributions [en]2026-04-25T22:41:31ZUser contributionsMediaWiki 1.35.1http://wiki.webos-internals.org/index.php?title=Application:MetaDoctor&diff=19027Application:MetaDoctor2011-09-22T13:32:02Z<p>Kostka: /* How to remove the ext3fs partition */</p>
<hr />
<div>[[Category:Application]]<br />
This page is currently available in four languages:<br />
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]<br />
:[[Image:France.png]] [[Application:MetaDoctor-FR]]<br />
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]<br />
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]<br />
<br />
= What is the Meta Doctor? =<br />
<br />
The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.<br />
<br />
'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''<br />
<br />
= Step 1: Setting up Meta-Doctor=<br />
<br />
== Windows ==<br />
<br />
'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''<br />
<br />
Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.<br />
<br />
# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''<br />
# Burn that file to a cd or mount to virtual drive<br />
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''<br />
# Click on '''Install Inside windows'''.<br />
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine. <br />
# Restart your computer and you can dual boot to Windows or Ubuntu <br />
<br />
The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.<br />
<br />
If you are still wondering what Wubi is, the following link should explain it to you better.<br />
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]<br />
<br />
Once you have installed WUBI, you should follow the instructions in the Linux section below.<br />
<br />
== Linux == <br />
<br />
# Open terminal from the ( Applications > Accessories ) menu.<br />
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.<br />
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].<br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre><br />
# Create a downloads directory. Type: <pre>mkdir downloads</pre><br />
<br />
== Mac OS X 10.6 ==<br />
<br />
#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site], on your Mac OS X installation CDs/DVD, or in the [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# App Store].<br />
#Install md5sum: <pre>sudo port install md5sha1sum</pre><br />
#Install gnutar: <pre>sudo port install gnutar</pre><br />
#Install git: <pre>sudo port install git-core</pre><br />
#Install wget: <pre>sudo port install wget</pre><br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
#Install patch: <pre>sudo port install gpatch</pre><br />
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].<br />
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].<br />
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre><br />
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre><br />
<br />
= Step 2: Running the webOS Doctor=<br />
<br />
Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.<br />
<br />
'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''<br />
<br />
# Navigate to the meta-doctor directory in the terminal<br />
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .<br />
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)<br />
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre><br />
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].<br />
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.<br />
# Type one of the following: <br />
#: <pre>make DEVICE=pre CARRIER=wr all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pre CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre><br />
#: <pre>make DEVICE=pre CARRIER=telcel all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre><br />
#: depending on the carrier in question.<br />
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France<br />
<br />
This should begin a process within the terminal that should take 10 minutes max.<br />
<br />
<br />
<br />
=== Error conditions ===<br />
<br />
If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).<br />
<br />
=== If the build fails ===<br />
<br />
If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.<br />
<br />
The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar''.<br />
<br />
If you are running in Ubuntu or Cygwin, you can just run the new jar file now. <br />
<br />
If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS. <br />
<br />
CD to the folder where your new jar file is, and type something like: <br />
<br />
java -jar webosdoctorp302hstnhwifi.jar<br />
<br />
If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it. <br />
<br />
<br />
''Windows host:''<br />
<br />
[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]<br />
<br />
[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]<br />
<br />
''Mac OSX host:''<br />
<br />
[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]<br />
<br />
<br />
: ''NOTE: this only applies to WUBI Users'' <br />
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows <br />
<br />
Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar</pre><br />
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.<br />
<br />
== Once the Doctor is running ==<br />
<br />
# Select your language<br />
# Accept the license agreement<br />
# Connect your Pre to your PC via USB and select "Next" when it becomes available<br />
<br />
After completion the device will reboot and present you with the activation set-up.<br />
<br />
If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:<br />
<br />
# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)<br />
# Hold down the Up button on the volume rocker<br />
# While holding the Up button, power on the Pre<br />
# "Next" should now be enabled - proceed with the recovery<br />
{{tux|Tux_with_Pre.png|float:right;}}<br />
The above steps will put the Pre 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.<br />
<br />
When the process finishes, the Pre will reboot and your new modified image will have been installed.<br />
<br />
----<br />
<br />
After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:<br />
<br />
'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.<br />
<br />
'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.<br />
*'''1.''' Open the Phone App.<br />
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)<br />
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.<br />
*'''4.''' Select ''Edit''.<br />
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.<br />
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).<br />
*'''7.''' Select ''Save''.<br />
*'''8.''' Backswipe out of the the view.<br />
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.<br />
<br />
You should now be able to run the ''First Use'' application without any problems.<br />
<br />
=If the Doctor will not run=<br />
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.<br />
<br />
=Miscellaneous=<br />
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.<br />
Steps:<br />
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).<br />
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config<br />
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl<br />
4. Put com.palm.wifi.prefsDB.sl in the config directory.<br />
5. Continue following instructions in the makefile.<br />
<br />
==How to enable WIFI profiles==<br />
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile. <br />
<br />
# Move to the meta-doctor directory (cd meta-doctor)<br />
# Create a "config" folder in the meta-doctor directory (mkdir config)<br />
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.<br />
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes<br />
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.<br />
# Build the custom doctor by running the script, or otherwise building it.<br />
<br />
<br />
On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.<br />
<br />
See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].<br />
<br />
==How to get the optional ext3fs partition mounted at device boot==<br />
<br />
'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''<br />
<br />
Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.<br />
<br />
All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).<br />
<br />
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:<br />
<br />
<pre>mount -o remount,rw /<br />
mkdir -p /media/ext3fs</pre><br />
<br />
it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.<br />
<br />
After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.<br />
<br />
<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice<br />
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre><br />
<br />
Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.<br />
<br />
<pre>mount -a</pre><br />
<br />
If you do not want it mounted at bootup, but you do need it mounted, you can use this command.<br />
<br />
<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre><br />
<br />
== How to remove the ext3fs partition ==<br />
<br />
# Connect your webOS device to your PC<br />
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"<br />
# And after you presented by your webOS device's root shell, run this command:<br />
* Unmount EXT3FS partition:<br />
# umount /dev/mapper/store-ext3fs<br />
<br />
* Remove EXT3FS partition:<br />
# lvremove /dev/mapper/store-ext3fs<br />
<br />
Then run meta-doctor to re-assign all space to user's diskspace<br />
<br />
<br />
Or, if you already do Meta-Doctor first, you can follow these steps:<br />
# Connect your webOS device to your PC<br />
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"<br />
# And after you presented by your webOS device's root shell, run this command:<br />
* Display LV size of EXT3FS partition, don't forget to write that down:<br />
# lvdisplay /dev/mapper/store-ext3fs<br />
<br />
* Remove EXT3FS partition:<br />
# lvremove /dev/mapper/store-ext3fs<br />
<br />
* Display existing user diskspace partition:<br />
# df -kh<br />
<br />
[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg image of df-kh]<br />
<br />
* Unmount existing user diskspace partition:<br />
# umount /dev/mapper/store-media<br />
<br />
<br />
<br />
Resize existing user diskspace by adding size of previous EXT3FS partition:<br />
<br />
I'm using /etc/fstab to see the filesystem of user's diskspace and /proc/partitions to see total allocation for user's diskspace:<br />
<br />
[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg image of cat /etc/fstab]<br />
<br />
[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg image of cat /etc/proc/partitions]<br />
<br />
# resizefat /dev/mapper/store-media 6995968K<br />
<br />
[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg image of resizefat /dev/mapper/store-media 6995968K]<br />
<br />
And here's what you've got on user's diskspace after everything is done:<br />
<br />
[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg image of lvdisplay /dev/mapper/store-media]<br />
<br />
==How to change a provider's DB-entry so 3G data can be used on the Pre==<br />
<br />
[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1<br />
<br />
== Problems with Novacom ==<br />
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].<br />
<br />
== How to Install webOS 2.x on "unoffical" Devices==<br />
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Application:MetaDoctor&diff=19025Application:MetaDoctor2011-09-22T13:30:50Z<p>Kostka: /* How to remove the ext3fs partition */</p>
<hr />
<div>[[Category:Application]]<br />
This page is currently available in four languages:<br />
:[[Image:Australia.png]] [[Image:USA.png]] [[Application:MetaDoctor]]<br />
:[[Image:France.png]] [[Application:MetaDoctor-FR]]<br />
:[[Image:Germany.png]] [[Application:MetaDoctor-DE]]<br />
:[[Image:Mexico.png]] [[Image:Spain.png]] [[Application:MetaDoctor-ES]]<br />
<br />
= What is the Meta Doctor? =<br />
<br />
The Webos Internals Meta Doctor is a Makefile which can modify a copy of the Palm webOS Doctor to bypass the "First Use" application and allow the phone to run without having been activated on a cell network. It accomplishes this by reaching into Palm's distributed Doctor JAR file and making changes to it. It can prevent the first use app from running, as well as applying other tweaks to the OS.<br />
<br />
'''Documentation for the features that the MetaDoctor offers is at the top of the Makefile (you need to clone the repository and then look in the Makefile file to see that).'''<br />
<br />
= Step 1: Setting up Meta-Doctor=<br />
<br />
== Windows ==<br />
<br />
'''NOTE THAT USING CYGWIN ON WINDOWS IS NO LONGER SUPPORTED AND WILL MAKE YOUR PHONE FAIL TO BOOT'''<br />
<br />
Windows users can use the meta doctor without harming your current installation of windows using simple Ubuntu installer called WUBI. Also no need for moding any partitions or installing any boot loaders. It will just appear as program in your installed software list and when you do not want it anymore simply uninstall it while in windows through Control Panel. It is easy and there is no virtual machine headaches of trying to configure USB, Network and File sharing with host computer... To access it you just reboot and choose Ubuntu from dual boot screen.<br />
<br />
# Download [http://www.ubuntu.com/getubuntu/download Ubuntu 11.04], look for the Ubuntu Desktop Edition, '''not the Windows Installer'''<br />
# Burn that file to a cd or mount to virtual drive<br />
# Run cd in windows (the wubi.exe file inside the disk, it also comes up in auto run) - '''Don't boot your machine with the CD (called as using the LiveCD, as this option won't give you enough space for the MetaDoctor process to complete.'''<br />
# Click on '''Install Inside windows'''.<br />
#: This will install Ubuntu while running Windows without the need of making a partition I would recomand making the install image the full recommended 30 gigs if you have the hard drive space and think you are interested in actually using the Ubuntu OS, otherwise the minimum recommended by Wubi should be just fine. <br />
# Restart your computer and you can dual boot to Windows or Ubuntu <br />
<br />
The nice thing about this is that it will allow you to uninstall Ubuntu right from Windows as if it was never there and remove the dual boot, not to mention the fact you do not need to partition your drive.<br />
<br />
If you are still wondering what Wubi is, the following link should explain it to you better.<br />
[https://wiki.ubuntu.com/WubiGuide Wubi Guide]<br />
<br />
Once you have installed WUBI, you should follow the instructions in the Linux section below.<br />
<br />
== Linux == <br />
<br />
# Open terminal from the ( Applications > Accessories ) menu.<br />
# Update your package lists and install git and Java runtime (the Canonical Partner Repository is needed to install the Sun Java JRE because it was moved out of the Multiverse in Ubuntu 10.04). Type: <pre>sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"</pre><pre>sudo apt-get update</pre><pre>sudo apt-get install git</pre><pre>sudo apt-get install sun-java6-jre</pre> (To accept the Java License Page, press tab until 'OK' is highlighted, then press enter) If the java install fails, look for support on the Java website [http://www.java.com/en/download/linux_manual.jsp here]. If you receive an error about git, repeat the command using git-core instead.<br />
# Download and install the Palm Novacom software: [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_i386.deb 32-bit] or [https://cdn.downloads.palm.com/sdkdownloads/2.1.0.519/sdkBinaries/palm-novacom_1.0.64_amd64.deb 64-bit]. If you have trouble installing, you can find more information [https://developer.palm.com/content/resources/develop/sdk_pdk_download.html#c28522 here].<br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Download the meta-doctor scripts using git. Type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
# Navigate to the meta-doctor directory. <pre>cd meta-doctor</pre><br />
# Create a downloads directory. Type: <pre>mkdir downloads</pre><br />
<br />
== Mac OS X 10.6 ==<br />
<br />
#Install MacPorts first, which will allow us to easily install the necessary packages for MetaDoctor. [http://www.macports.org/install.php]. Please note that MacPorts requires Apple's Xcode Developer Tools (version 3.2.1 or later for Snow Leopard, 3.1.4 or later for Leopard, or 2.5 for Tiger), found at the [http://connect.apple.com/ Apple Developer Connection site], on your Mac OS X installation CDs/DVD, or in the [http://itunes.apple.com/us/app/xcode/id448457090?mt=12# App Store].<br />
#Install md5sum: <pre>sudo port install md5sha1sum</pre><br />
#Install gnutar: <pre>sudo port install gnutar</pre><br />
#Install git: <pre>sudo port install git-core</pre><br />
#Install wget: <pre>sudo port install wget</pre><br />
# Make sure you are not running as root, and navigate to your home directory. <pre>cd</pre><br />
# Now type: <pre>git clone git://git.webos-internals.org/tools/meta-doctor.git</pre><br />
#Install patch: <pre>sudo port install gpatch</pre><br />
#If you do not have Java installed, do so. To install Java, click on the "Apple" icon and select "Software Update." This will automatically update you to the latest version of Java if necessary, as Apple supplies their own version of Java. Further instructions can be found [http://support.apple.com/kb/HT1338?viewlocale=en_US here].<br />
#Download and install the Palm Novacom software from http://developer.palm.com. The Mac OS X SDK is located [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/Palm_webOS_SDK.1.4.5.465.dmg here].<br />
#Open a terminal and navigate to the meta-doctor directory where the meta-doctor was copied to in step 6 above.<pre>cd meta-doctor</pre><br />
#Ensure that there is a downloads directory. If there is not one, create one using <pre>mkdir downloads</pre><br />
<br />
= Step 2: Running the webOS Doctor=<br />
<br />
Note that if you are following a procedure on another wiki page which only requires the installation of the MetaDoctor and then tells you to return to that other page, then this is the place at which you should return.<br />
<br />
'''If you intend to enable WIFI Profiles, you must copy a file off of the phone before doctoring. See the section below on enabling wifi profiles.'''<br />
<br />
# Navigate to the meta-doctor directory in the terminal<br />
# Download the latest webosdoctor file using the download paths found at [http://www.webos-internals.org/wiki/Webos_Doctor_Versions Webos Doctor Versions] .<br />
'''Note ''': if you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar)<br />
The wr version is the French,German,Irish,Spanish and UK GSM version. An example (e.g. current Web OS as of 11/23/11) download command would be: <pre>cd downloads</pre><pre>wget http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar</pre><br />
# If you would like Meta-Doctor to apply patches to webOS in order to add or change functionality from the factory install, open the Makefile with your favorite text editor and uncomment (remove the leading # characters from) the options you would like to use. For example, if you plan to install Ubuntu, now is the time to uncomment the EXT3FS_PARTITION_SIZE option in the Makefile and edit it per [http://www.webos-internals.org/wiki/Chrooting these instructions].<br />
# Before doing the next step, make sure you change back into the meta-doctor directory first. All the following commands must be run from the meta-doctor directory.<br />
# Type one of the following: <br />
#: <pre>make DEVICE=pre CARRIER=wr all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=wr all</pre><br />
#: <pre>make DEVICE=pre CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pixi CARRIER=sprint all</pre> <br />
#: <pre>make DEVICE=pre CARRIER=bellmo all</pre><br />
#: <pre>make DEVICE=pre CARRIER=telcel all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=verizonwireless all</pre><br />
#: <pre>make DEVICE=preplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=pixiplus CARRIER=att all</pre><br />
#: <pre>make DEVICE=touchpad CARRIER=wifi all</pre><br />
#: depending on the carrier in question.<br />
'''Note ''': use make DEVICE=palm_smartphone_type CARRIER=wr all for O2 Germany, UK and Ireland / Movistar Spain / SFR France<br />
<br />
This should begin a process within the terminal that should take 10 minutes max.<br />
<br />
<br />
<br />
=== Error conditions ===<br />
<br />
If you receive an error message when running the make file, (e.g 'Please download the correct version of the webOS Doctor .jar file and then move it to downloads/webosdoctorp220manta-wr-2.2.0.jar'), and you are sure you have the correct doctor you need to rename your doctor file, so it matches the name in the error message (e.g. sudo mv webosdoctorp220mantawr.jar webosdoctorp220manta-wr-2.2.0.jar).<br />
<br />
=== If the build fails ===<br />
<br />
If the make command fails, you can use <pre>make clobber</pre> to clean up the build directory. After this you can re-run the command.<br />
<br />
The updated doctor version has the same name as the original, but is in a new folder: ''meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar''.<br />
<br />
If you are running in Ubuntu or Cygwin, you can just run the new jar file now. <br />
<br />
If you are running Ubuntu using VM, you will need to copy the new jar out of the VM into your live desktop to run the jar in your native OS. <br />
<br />
CD to the folder where your new jar file is, and type something like: <br />
<br />
java -jar webosdoctorp302hstnhwifi.jar<br />
<br />
If you were using a VM or some other virtual method, you will need to copy the jar file out to your main operating system before running it. <br />
<br />
<br />
''Windows host:''<br />
<br />
[http://ubuntuexperiment.wordpress.com/2008/11/12/sharing-folders-between-host-and-guest-os-in-virtualbox/ VirtualBox folder Sharing]<br />
<br />
[http://www.howtogeek.com/howto/ubuntu/how-to-share-folders-with-your-ubuntu-virtual-machine-guest/ VMWare folder Sharing]<br />
<br />
''Mac OSX host:''<br />
<br />
[http://davidherron.com/blog/topics/628-virtualbox-running-ubuntu-accessing-host-file-system-mac-os-x VirtualBox folder Sharing]<br />
<br />
<br />
: ''NOTE: this only applies to WUBI Users'' <br />
You should be able to run the JAR as if you had Linux installed natively because in a sense you do (as long as Java is installed and you run the Jar using Java) but if you rather run it in windows <br />
<br />
Using terminal the following command in a Wubi installation of Ubuntu will copy the JAR file to the host Windows OS :<pre>cp /meta-doctor/build/<name_and_version>/webosdoctorp302hstnhwifi.jar /host/webosdoctorp302hstnhwifi.jar</pre><br />
This will place the Jar either in your Windows C:\ drive or whatever drive you installed Wubi to.<br />
<br />
== Once the Doctor is running ==<br />
<br />
# Select your language<br />
# Accept the license agreement<br />
# Connect your Pre to your PC via USB and select "Next" when it becomes available<br />
<br />
After completion the device will reboot and present you with the activation set-up.<br />
<br />
If your PC does not recognize your Pre and you cannot go past step 3 above, try the following steps:<br />
<br />
# With the USB cable connected, completely power off the Pre (hold down the power button until the option to power off appears)<br />
# Hold down the Up button on the volume rocker<br />
# While holding the Up button, power on the Pre<br />
# "Next" should now be enabled - proceed with the recovery<br />
{{tux|Tux_with_Pre.png|float:right;}}<br />
The above steps will put the Pre 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.<br />
<br />
When the process finishes, the Pre will reboot and your new modified image will have been installed.<br />
<br />
----<br />
<br />
After the doctor completes, you will need to run the "First Run" application. To do this, you will need an active internet connection. Either WiFi or Cellular. If you do not have WiFi and cannot connect to the Palm Profile servers, you might have a problem with your programming. This Meta Doctor (or webOS Doctor in general) could possibly erase the modem's programming. To resolve you will need to perform the following steps:<br />
<br />
'''Note:''' This has only been confirmed to resolve Sprint CDMA issues, YMMV.<br />
<br />
'''Note 2:''' You should try to update your profile first. Open the phone app, open the App Menu and select ''Preferences'' then select ''Update Network Settings''. If you get an error, then procede with these instructions.<br />
*'''1.''' Open the Phone App.<br />
*'''2.''' Enter ''##MSL#'' (MSL= 6 digit lock code. Get this from Sprint.)<br />
*'''3.''' Verify your MDN and MSID are incorrect. If they are incorrect, continue. If they are correct, this is not your problem and you should not continue.<br />
*'''4.''' Select ''Edit''.<br />
*'''5.''' Select the first box (MDN) and enter your 10-digit cellular number.<br />
*'''6.''' Select the second box (MSID) and enter your 10-digit MSID (Get this from Sprint).<br />
*'''7.''' Select ''Save''.<br />
*'''8.''' Backswipe out of the the view.<br />
*'''9.''' You should now be able to open complete '''Note 2''' above without any errors.<br />
<br />
You should now be able to run the ''First Use'' application without any problems.<br />
<br />
=If the Doctor will not run=<br />
Go [http://www.webos-internals.org/wiki/How_To_Recover here] if you have further problems connecting your Pre to the running Meta'ed Doctor.<br />
<br />
=Miscellaneous=<br />
Clarification for Linux beginners on where to place the prefsDB.sl file, per instructions in the makefile.<br />
Steps:<br />
1. Open makefile using a text editor (like WordPad) and use the instructions there to retrieve your prefsDB.sl file from your device. Save it somewhere convenient on your host machine (aka, computer).<br />
2. Navigate to the meta-doctor directory and create the config directory: mkdir -p config<br />
3. Rename your prefsDB.sl file to com.palm.wifi.prefsDB.sl<br />
4. Put com.palm.wifi.prefsDB.sl in the config directory.<br />
5. Continue following instructions in the makefile.<br />
<br />
==How to enable WIFI profiles==<br />
To enable wifi profiles it is necessary to copy your wifi profile file off of your phone and place this in a directory, as well as enable the wifi profile option in the makefile. <br />
<br />
# Move to the meta-doctor directory (cd meta-doctor)<br />
# Create a "config" folder in the meta-doctor directory (mkdir config)<br />
# Copy the prefsDB.sl file off of your phone from the var/preferences/com.palm.wifi/ and into the "config" directory that you just created.<br />
# Rename this file "com.palm.wifi.prefsDB.sl" without the quotes<br />
# Open the makefile (which is in the meta-doctor directory) and remove the "#" from the line "# INSTALL_WIFI_PROFILES = 1". Save the makefile.<br />
# Build the custom doctor by running the script, or otherwise building it.<br />
<br />
<br />
On launch of the new doctor your wifi profile should automatically connect, but '''only if''' you had previously connected to the WIFI network you are trying to use.<br />
<br />
See these links for more information: [http://forums.precentral.net/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-27.html#post2882495 Post 1], [http://discussion.treocentral.com/webos-internals/276460-how-install-webos-2-1-0-pre-pre-using-meta-doctor-43.html#post2884415 Post 2].<br />
<br />
==How to get the optional ext3fs partition mounted at device boot==<br />
<br />
'''(NOTE: This is a necessary step to get UbuntuChroot working on the touchpad and must be done before UbuntuChroot is installed)'''<br />
<br />
Note that you have to use the Meta-Doctor as shown earlier in this page to doctor your device to create the ext3fs partition before attempting the following steps.<br />
<br />
All of this is done on device either via novaterm or an SSH login. Instructions for running novaterm on your desktop computer are [http://www.webos-internals.org/wiki/Accessing_Linux_Using_Novaterm here] (you may skip step 1 if you already downloaded the Palm SDK while setting up the Meta-Doctor).<br />
<br />
If your device does NOT have a folder at /media/ext3fs then you will need to create it first. Use the following two commands:<br />
<br />
<pre>mount -o remount,rw /<br />
mkdir -p /media/ext3fs</pre><br />
<br />
it is important that you use /media/ext3fs as the location, otherwise some homebrew applications (such as Optware and the Ubuntu 11.04 Chroot) will not be able to find it and use it properly.<br />
<br />
After you have created the mountpoint, we are going to edit the fstab file to set it up to mount at bootup.<br />
<br />
<pre>mount -o remount,rw / *****Not necessary if you performed the previous steps, but doesn't hurt if you do it twice<br />
echo "/dev/mapper/store-ext3fs /media/ext3fs ext3 noatime,data=writeback 0 0" >> /etc/fstab</pre><br />
<br />
Now to get it mounted you have several options, the best one is the first command as it will use the data in /etc/fstab. If that works, then you have done this correctly and your ext3fs will mount at bootup.<br />
<br />
<pre>mount -a</pre><br />
<br />
If you do not want it mounted at bootup, but you do need it mounted, you can use this command.<br />
<br />
<pre>mount /dev/mapper/store-ext3fs /media/ext3fs</pre><br />
<br />
== How to remove the ext3fs partition ==<br />
<br />
# Connect your webOS device to your PC<br />
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"<br />
# And after you presented by your webOS device's root shell, run this command:<br />
* Unmount EXT3FS partition:<br />
# umount /dev/mapper/store-ext3fs<br />
<br />
* Remove EXT3FS partition:<br />
# lvremove /dev/mapper/store-ext3fs<br />
<br />
Then run meta-doctor to re-assign all space to user's diskspace<br />
<br />
<br />
Or, if you already do Meta-Doctor first, you can follow these steps:<br />
# Connect your webOS device to your PC<br />
# Open up Terminal (Mac/ Linux) or Command Prompt (Windows), then type "novaterm"<br />
# And after you presented by your webOS device's root shell, run this command:<br />
* Display LV size of EXT3FS partition, don't forget to write that down:<br />
# lvdisplay /dev/mapper/store-ext3fs<br />
<br />
* Remove EXT3FS partition:<br />
# lvremove /dev/mapper/store-ext3fs<br />
<br />
* Display existing user diskspace partition:<br />
# df -kh<br />
<br />
[http://3.bp.blogspot.com/-orFK9AjZYM4/Tk3RF0HnB6I/AAAAAAAAB_w/29uQBnN46PI/s1600/df-kh.jpg image of df-kh]<br />
<br />
* Unmount existing user diskspace partition:<br />
# umount /dev/mapper/store-media<br />
<br />
<br />
<br />
* Resize existing user diskspace by adding size of previous EXT3FS partition:<br />
<br />
I'm using /etc/fstab to see the filesystem of user's diskspace and /proc/partitions to see total allocation for user's diskspace:<br />
<br />
[http://1.bp.blogspot.com/-fNgZpAme8wE/Tk3RG8SeWzI/AAAAAAAAB_0/GC0t5KrDUDQ/s1600/fstab.jpg image of cat /etc/fstab]<br />
<br />
[http://2.bp.blogspot.com/-FAmvlsY6mSc/Tk3RImBEnqI/AAAAAAAACAA/m6piDWuxxro/s1600/proc-partitions.jpg image of cat /etc/proc/partitions]<br />
<br />
# resizefat /dev/mapper/store-media 6995968K<br />
<br />
[http://1.bp.blogspot.com/-EqnW7-WzJnU/Tk3RJCElO4I/AAAAAAAACAE/xbrps-xnWaI/s1600/resizefat.jpg image of resizefat /dev/mapper/store-media 6995968K]<br />
<br />
And here's what you've got on user's diskspace after everything is done:<br />
<br />
[http://4.bp.blogspot.com/-ZmKHhll3G6w/Tk3RHWhrzGI/AAAAAAAAB_4/hfyiDE-BIEA/s1600/lvdisplay-storemedia.jpg image of lvdisplay /dev/mapper/store-media]<br />
<br />
==How to change a provider's DB-entry so 3G data can be used on the Pre==<br />
<br />
[http://forums.precentral.net/gsm-pre/211728-modifying-webos-carrier-network-settings.html#post2002079 This post] and [http://forums.precentral.net/palm-pre/209222-few-questions-about-german-palm-pre-6.html this thread] describe various ways to adjust the provider's data base in the Pre, so the 3G datacom works on non-supported networks. webOS 1.3.1 allows setting of the providers data directly from the activation screen for providers that are present in the DB. Some report that they are not able to do that and that they cannot get 3G datacom working on 1.3.1<br />
<br />
== Problems with Novacom ==<br />
If you are Running a new Distro, like Archlinux, you could run into problem with novacom while trying to connect your pre. Running novacomd on the command line could provide further information. This may be a problem with libusb. Get a older version like described in [http://developer.palm.com/distribution/viewtopic.php?f=11&t=4233&start=0 this thread].<br />
<br />
== How to Install webOS 2.x on "unoffical" Devices==<br />
With the release of the O2-DE webOS Doctor, efforts have been made to apply the techniques of MetaDoctor and create a custom doctor to apply 2.1.0 to devices that it was not been officially released for. For those not faint of heart, a step-by-step can be found at the following: [[WebOS 2 Upgrade]]</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Application:Linphone&diff=14367Application:Linphone2011-03-21T09:14:18Z<p>Kostka: /* Test Report */</p>
<hr />
<div>{{application<br />
|name=Linphone<br />
|type=webOS<br />
|version=0.1.8<br />
|tag=Communications<br />
|screenshot=Icon_WebOSInternals_Linphone.png<br />
|description=}}<br />
<br />
This is the very first true VoIP application running on any webOS device.<br />
<br />
Linphone for webOS is a port of the original [http://www.linphone.org/ Linphone] command-line application.<br />
<br />
== Summary ==<br />
Linphone is a general purpose SIP softphone. It allows you to place and receive VoIP calls on any SIP account you may have.<br />
<br />
Linphone isn't bound to any operator. Because it is compatible with SIP, it can work with any VoIP operator using SIP (most of them use SIP, the most notable exception being Skype).<br />
<br />
== Alpha Test ==<br />
<br />
Linphone / webOS is currently in '''''alpha''''' test.<br />
<br />
At the moment, to get Linphone you have to already have a good understanding of VoIP (the open standard SIP kind, not the closed proprietary Skype kind) and make yourself known in the [irc://chat.freenode.net/webos-internals #webos-internals IRC channel] (see [[WebOS-Internals_IRC_Channel_Policy|policy]], daily logs available in [http://logs.nslu2-linux.org/livelogs/webos-internals.txt current], [http://logs.nslu2-linux.org/livelogs/webos-internals-prev.txt previous] and [http://logs.nslu2-linux.org/livelogs/webos-internals/ all past days]).<br />
<br />
Alpha testers, please report at the bottom of this page success & failure with your SIP provider(s). Add or update your own rows in the table (please use your P|C or WOI identity so we can PM you if needed).<br />
<br />
Any other information/request you would like to share/ask, please report [http://forums.precentral.net/webos-internals/274615-linphone-alpha-testing.html in the dedicated thread at PreCentral].<br />
<br />
== SIP Account ==<br />
<br />
You will have received some registration information from your SIP provider by the end of the sign-up process:<br />
:* '''username''' or '''phonenumber'''<br />
:* '''password'''<br />
:* '''domain'''<br />
:* '''proxy''' (''optional'')<br />
<br />
<br />
Your SIP identity is formed by grouping the '''Username''' or '''Phonenumber''' and the '''Domain''' together:<br />
:* sip:'''''username'''''@'''''domain'''''<br />
or<br />
:* sip:'''''phonenumber'''''@'''''domain'''''<br />
and will be used by other people willing to call you on your webOS device when running Linphone.<br />
<br />
== Dialpad ==<br />
[[File:Linphone_Dialpad.png|200px|right]]<br />
<br />
This is (obviously!) where you dial a number you want to call...<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Preferences ==<br />
<br />
The Linphone preferences screen can be accessed by tapping the menu button on the top left corner of your device. <br />
[[File:Linphone_Preferences.png|200px|right]]<br />
<br />
<br />
The "'''SIP'''" group:<br />
:* '''NAME''' - enter your '''''username''''' or '''''phonenumber'''''<br />
:* '''PASSWORD''' - enter your '''''password'''''<br />
:* '''DOMAIN''' - enter your SIP provider's '''''domain'''''<br />
:* '''USE PROXY''': select<br />
::- '''NO''' if your SIP provider does not require a specific proxy ('''PROXY''' field hidden)<br />
::- '''YES''' if a '''''proxy''''' is required with an address different from '''''domain''''' ('''PROXY''' field shown)<br />
:* '''PROXY''' - enter your SIP provider '''''proxy''''' (or '''''proxy:port'''''), if any<br />
<br />
The "'''NETWORK'''" group:<br />
:* '''FIREWALL''' - select<br />
::- '''NONE''' if you have a direct connection to the internet or you are behind a router with an [http://en.wikipedia.org/wiki/Application_Layer_Gateway application-level gateway] for SIP ('''ADDRESS''' and '''SERVER''' fields hidden)<br />
::- '''NAT''' to provide the public IP address of your router ('''ADDRESS''' field shown)<br />
::- '''STUN''' to rely on a STUN server to discover the public IP address of your router ('''SERVER''' field shown)<br />
:* '''ADDRESS''' - enter your router's public IP address<br />
:* '''SERVER''' - enter the address of the STUN server<br />
<br />
== Limitations ==<br />
<br />
:* The sound comes from the back-speaker for now. Work is underway to bring the sound from the front speaker<br />
:* Until echo-cancellation is activated, the person on the other end will suffer some echo because of the back-speaker...<br />
:* The proximity sensor is not activated (yet!). To prevent unintentional screen touch from the ear when close to the head, it is better to turn-off the screen for now...<br />
<br />
== Test Report ==<br />
{| {{prettytable}}<br />
<br />
!colspan="4" border="5"|SIP Provider<br />
!colspan="3"|VoIP Test<br />
!colspan="6"|Test Conditions<br />
<br />
|-<br />
<br />
!{{Hl3}} align="center"|Name<br />
!{{Hl3}} align="center"|Domain<br />
!{{Hl3}} align="center"|Proxy<br />
!{{Hl3}} align="center"|Firewall<br />
<br />
!{{Hl3}} align="center"|Register<br />
!{{Hl3}} align="center"|Call-Out<br />
!{{Hl3}} align="center"|Call-In<br />
<br />
!{{Hl3}} align="center"|Linphone<br />
!{{Hl3}} align="center"|Network (WiFi/EVDO/3G)<br />
!{{Hl3}} align="center"|Device<br />
!{{Hl3}} align="center"|When<br />
!{{Hl3}} align="center"|Who<br />
!{{Hl3}} align="center"|Comments<br />
<br />
|-<br />
<br />
|[http://fr.wikipedia.org/wiki/Freephonie Freephonie]||freephonie.net||''(empty)''||NONE<br />
||OK||OK ''(pstn)''||''(untested)''<br />
||0.1.8||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Mar 2011||Thibaud||Call-in not really a feature of Freephonie<br />
|-<br />
|[http://www.iptel.org/service iptel.org]||iptel.org||sip.iptel.org ''(optional)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||proxy.sipthor.net||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://support.gizmoproject.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=409 Gizmo]||proxy01.sipphone.com||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.draytel.org/features Draytel]||draytel.org||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||NONE<br />
||OK||OK||OK (most of the time- inconsistent),'' ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011 ''(updated)''||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||STUN, stun.sipgate.net:10000<br />
||OK||untested||hangs at INCOMING_INITIATED ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||pbxes.com||<br />
||REG PENDING||||<br />
||0.1.8||||Pre2 2.1||Mar 2011||wprater||<br />
|-<br />
|[http://www.vonage.com vonage]||sphone.vopr.vonage.net||(empty)||Tried With and Without||OK*||OK* (to vonage & sprint mobile)<br />
||OK* (from vonage & sprint mobile)||0.1.8 ||Both Wifi+NAT and Sprint ||Pre 1.4.5 ||Mar 2011||jjeansonne||*with some struggle to get sucessful registration and calls placed. Had to restart the app many times and go in/out of account setting page<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||pbxes.org||NONE<br />
||OK||hangs at CALL_OUT_RINGING||untested<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Entry for pbxes above has wrong domain entered<br />
|-<br />
|[http://1und1.de 1und1]||1und1.de||sip.1und1.de||STUN, stun.1und1.de<br />
||REG PENDING||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://ekiga.net ekiga]||ekiga.net||(empty)||STUN, stun.1und1.de<br />
||REG OK||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.linphone.org linphone]||sip.linphone.org||(empty)||''(n/a)''<br />
||OK||''(untested)''||''(untested)''<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||<br />
|-<br />
|[http://www.callcentric.com callcentric]||callcentric.com||(empty)||''(n/a)''<br />
||REG_PENDING||||<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||(empty)||''(n/a)''<br />
||OK||''(untested)''||hangs at CALL_IN_INVITE<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||hangs at CALL_IN_INVITE<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|''New entry...''|| || ||<br />
|| || || <br />
|| || || || || || ''Please copy this row so the template still exists... :-)''<br />
|-<br />
|}</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Application:Linphone&diff=14365Application:Linphone2011-03-21T09:06:00Z<p>Kostka: /* Test Report */</p>
<hr />
<div>{{application<br />
|name=Linphone<br />
|type=webOS<br />
|version=0.1.8<br />
|tag=Communications<br />
|screenshot=Icon_WebOSInternals_Linphone.png<br />
|description=}}<br />
<br />
This is the very first true VoIP application running on any webOS device.<br />
<br />
Linphone for webOS is a port of the original [http://www.linphone.org/ Linphone] command-line application.<br />
<br />
== Summary ==<br />
Linphone is a general purpose SIP softphone. It allows you to place and receive VoIP calls on any SIP account you may have.<br />
<br />
Linphone isn't bound to any operator. Because it is compatible with SIP, it can work with any VoIP operator using SIP (most of them use SIP, the most notable exception being Skype).<br />
<br />
== Alpha Test ==<br />
<br />
Linphone / webOS is currently in '''''alpha''''' test.<br />
<br />
At the moment, to get Linphone you have to already have a good understanding of VoIP (the open standard SIP kind, not the closed proprietary Skype kind) and make yourself known in the [irc://chat.freenode.net/webos-internals #webos-internals IRC channel] (see [[WebOS-Internals_IRC_Channel_Policy|policy]], daily logs available in [http://logs.nslu2-linux.org/livelogs/webos-internals.txt current], [http://logs.nslu2-linux.org/livelogs/webos-internals-prev.txt previous] and [http://logs.nslu2-linux.org/livelogs/webos-internals/ all past days]).<br />
<br />
Alpha testers, please report at the bottom of this page success & failure with your SIP provider(s). Add or update your own rows in the table (please use your P|C or WOI identity so we can PM you if needed).<br />
<br />
Any other information/request you would like to share/ask, please report [http://forums.precentral.net/webos-internals/274615-linphone-alpha-testing.html in the dedicated thread at PreCentral].<br />
<br />
== SIP Account ==<br />
<br />
You will have received some registration information from your SIP provider by the end of the sign-up process:<br />
:* '''username''' or '''phonenumber'''<br />
:* '''password'''<br />
:* '''domain'''<br />
:* '''proxy''' (''optional'')<br />
<br />
<br />
Your SIP identity is formed by grouping the '''Username''' or '''Phonenumber''' and the '''Domain''' together:<br />
:* sip:'''''username'''''@'''''domain'''''<br />
or<br />
:* sip:'''''phonenumber'''''@'''''domain'''''<br />
and will be used by other people willing to call you on your webOS device when running Linphone.<br />
<br />
== Dialpad ==<br />
[[File:Linphone_Dialpad.png|200px|right]]<br />
<br />
This is (obviously!) where you dial a number you want to call...<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Preferences ==<br />
<br />
The Linphone preferences screen can be accessed by tapping the menu button on the top left corner of your device. <br />
[[File:Linphone_Preferences.png|200px|right]]<br />
<br />
<br />
The "'''SIP'''" group:<br />
:* '''NAME''' - enter your '''''username''''' or '''''phonenumber'''''<br />
:* '''PASSWORD''' - enter your '''''password'''''<br />
:* '''DOMAIN''' - enter your SIP provider's '''''domain'''''<br />
:* '''USE PROXY''': select<br />
::- '''NO''' if your SIP provider does not require a specific proxy ('''PROXY''' field hidden)<br />
::- '''YES''' if a '''''proxy''''' is required with an address different from '''''domain''''' ('''PROXY''' field shown)<br />
:* '''PROXY''' - enter your SIP provider '''''proxy''''' (or '''''proxy:port'''''), if any<br />
<br />
The "'''NETWORK'''" group:<br />
:* '''FIREWALL''' - select<br />
::- '''NONE''' if you have a direct connection to the internet or you are behind a router with an [http://en.wikipedia.org/wiki/Application_Layer_Gateway application-level gateway] for SIP ('''ADDRESS''' and '''SERVER''' fields hidden)<br />
::- '''NAT''' to provide the public IP address of your router ('''ADDRESS''' field shown)<br />
::- '''STUN''' to rely on a STUN server to discover the public IP address of your router ('''SERVER''' field shown)<br />
:* '''ADDRESS''' - enter your router's public IP address<br />
:* '''SERVER''' - enter the address of the STUN server<br />
<br />
== Limitations ==<br />
<br />
:* The sound comes from the back-speaker for now. Work is underway to bring the sound from the front speaker<br />
:* Until echo-cancellation is activated, the person on the other end will suffer some echo because of the back-speaker...<br />
:* The proximity sensor is not activated (yet!). To prevent unintentional screen touch from the ear when close to the head, it is better to turn-off the screen for now...<br />
<br />
== Test Report ==<br />
{| {{prettytable}}<br />
<br />
!colspan="4" border="5"|SIP Provider<br />
!colspan="3"|VoIP Test<br />
!colspan="6"|Test Conditions<br />
<br />
|-<br />
<br />
!{{Hl3}} align="center"|Name<br />
!{{Hl3}} align="center"|Domain<br />
!{{Hl3}} align="center"|Proxy<br />
!{{Hl3}} align="center"|Firewall<br />
<br />
!{{Hl3}} align="center"|Register<br />
!{{Hl3}} align="center"|Call-Out<br />
!{{Hl3}} align="center"|Call-In<br />
<br />
!{{Hl3}} align="center"|Linphone<br />
!{{Hl3}} align="center"|Network (WiFi/EVDO/3G)<br />
!{{Hl3}} align="center"|Device<br />
!{{Hl3}} align="center"|When<br />
!{{Hl3}} align="center"|Who<br />
!{{Hl3}} align="center"|Comments<br />
<br />
|-<br />
<br />
|[http://fr.wikipedia.org/wiki/Freephonie Freephonie]||freephonie.net||''(empty)''||NONE<br />
||OK||OK ''(pstn)''||''(untested)''<br />
||0.1.8||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Mar 2011||Thibaud||Call-in not really a feature of Freephonie<br />
|-<br />
|[http://www.iptel.org/service iptel.org]||iptel.org||sip.iptel.org ''(optional)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||proxy.sipthor.net||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://support.gizmoproject.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=409 Gizmo]||proxy01.sipphone.com||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.draytel.org/features Draytel]||draytel.org||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||NONE<br />
||OK||OK||OK (most of the time- inconsistent),'' ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011 ''(updated)''||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||STUN, stun.sipgate.net:10000<br />
||OK||untested||hangs at INCOMING_INITIATED ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||pbxes.com||<br />
||REG PENDING||||<br />
||0.1.8||||Pre2 2.1||Mar 2011||wprater||<br />
|-<br />
|[http://www.vonage.com vonage]||sphone.vopr.vonage.net||(empty)||Tried With and Without||OK*||OK* (to vonage & sprint mobile)<br />
||OK* (from vonage & sprint mobile)||0.1.8 ||Both Wifi+NAT and Sprint ||Pre 1.4.5 ||Mar 2011||jjeansonne||*with some struggle to get sucessful registration and calls placed. Had to restart the app many times and go in/out of account setting page<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||pbxes.org||NONE<br />
||OK||hangs at CALL_OUT_RINGING||untested<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Entry for pbxes above has wrong domain entered<br />
|-<br />
|[http://1und1.de 1und1]||1und1.de||sip.1und1.de||STUN, stun.1und1.de<br />
||REG PENDING||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://ekiga.net ekiga]||ekiga.net||(empty)||STUN, stun.1und1.de<br />
||REG OK||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.linphone.org linphone]||sip.linphone.org||(empty)||''(n/a)''<br />
||OK||''(untested)''||''(untested)''<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||<br />
|-<br />
|[http://www.callcentric.com callcentric]||callcentric.com||(empty)||''(n/a)''<br />
||REG_PENDING||||<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||(empty)||''(n/a)''<br />
||OK||''(untested)''||hangs at INCOMING_CALL_INIT<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||hangs at INCOMING_CALL_INIT<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|''New entry...''|| || ||<br />
|| || || <br />
|| || || || || || ''Please copy this row so the template still exists... :-)''<br />
|-<br />
|}</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Application:Linphone&diff=14363Application:Linphone2011-03-21T09:03:00Z<p>Kostka: /* Test Report */</p>
<hr />
<div>{{application<br />
|name=Linphone<br />
|type=webOS<br />
|version=0.1.8<br />
|tag=Communications<br />
|screenshot=Icon_WebOSInternals_Linphone.png<br />
|description=}}<br />
<br />
This is the very first true VoIP application running on any webOS device.<br />
<br />
Linphone for webOS is a port of the original [http://www.linphone.org/ Linphone] command-line application.<br />
<br />
== Summary ==<br />
Linphone is a general purpose SIP softphone. It allows you to place and receive VoIP calls on any SIP account you may have.<br />
<br />
Linphone isn't bound to any operator. Because it is compatible with SIP, it can work with any VoIP operator using SIP (most of them use SIP, the most notable exception being Skype).<br />
<br />
== Alpha Test ==<br />
<br />
Linphone / webOS is currently in '''''alpha''''' test.<br />
<br />
At the moment, to get Linphone you have to already have a good understanding of VoIP (the open standard SIP kind, not the closed proprietary Skype kind) and make yourself known in the [irc://chat.freenode.net/webos-internals #webos-internals IRC channel] (see [[WebOS-Internals_IRC_Channel_Policy|policy]], daily logs available in [http://logs.nslu2-linux.org/livelogs/webos-internals.txt current], [http://logs.nslu2-linux.org/livelogs/webos-internals-prev.txt previous] and [http://logs.nslu2-linux.org/livelogs/webos-internals/ all past days]).<br />
<br />
Alpha testers, please report at the bottom of this page success & failure with your SIP provider(s). Add or update your own rows in the table (please use your P|C or WOI identity so we can PM you if needed).<br />
<br />
Any other information/request you would like to share/ask, please report [http://forums.precentral.net/webos-internals/274615-linphone-alpha-testing.html in the dedicated thread at PreCentral].<br />
<br />
== SIP Account ==<br />
<br />
You will have received some registration information from your SIP provider by the end of the sign-up process:<br />
:* '''username''' or '''phonenumber'''<br />
:* '''password'''<br />
:* '''domain'''<br />
:* '''proxy''' (''optional'')<br />
<br />
<br />
Your SIP identity is formed by grouping the '''Username''' or '''Phonenumber''' and the '''Domain''' together:<br />
:* sip:'''''username'''''@'''''domain'''''<br />
or<br />
:* sip:'''''phonenumber'''''@'''''domain'''''<br />
and will be used by other people willing to call you on your webOS device when running Linphone.<br />
<br />
== Dialpad ==<br />
[[File:Linphone_Dialpad.png|200px|right]]<br />
<br />
This is (obviously!) where you dial a number you want to call...<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Preferences ==<br />
<br />
The Linphone preferences screen can be accessed by tapping the menu button on the top left corner of your device. <br />
[[File:Linphone_Preferences.png|200px|right]]<br />
<br />
<br />
The "'''SIP'''" group:<br />
:* '''NAME''' - enter your '''''username''''' or '''''phonenumber'''''<br />
:* '''PASSWORD''' - enter your '''''password'''''<br />
:* '''DOMAIN''' - enter your SIP provider's '''''domain'''''<br />
:* '''USE PROXY''': select<br />
::- '''NO''' if your SIP provider does not require a specific proxy ('''PROXY''' field hidden)<br />
::- '''YES''' if a '''''proxy''''' is required with an address different from '''''domain''''' ('''PROXY''' field shown)<br />
:* '''PROXY''' - enter your SIP provider '''''proxy''''' (or '''''proxy:port'''''), if any<br />
<br />
The "'''NETWORK'''" group:<br />
:* '''FIREWALL''' - select<br />
::- '''NONE''' if you have a direct connection to the internet or you are behind a router with an [http://en.wikipedia.org/wiki/Application_Layer_Gateway application-level gateway] for SIP ('''ADDRESS''' and '''SERVER''' fields hidden)<br />
::- '''NAT''' to provide the public IP address of your router ('''ADDRESS''' field shown)<br />
::- '''STUN''' to rely on a STUN server to discover the public IP address of your router ('''SERVER''' field shown)<br />
:* '''ADDRESS''' - enter your router's public IP address<br />
:* '''SERVER''' - enter the address of the STUN server<br />
<br />
== Limitations ==<br />
<br />
:* The sound comes from the back-speaker for now. Work is underway to bring the sound from the front speaker<br />
:* Until echo-cancellation is activated, the person on the other end will suffer some echo because of the back-speaker...<br />
:* The proximity sensor is not activated (yet!). To prevent unintentional screen touch from the ear when close to the head, it is better to turn-off the screen for now...<br />
<br />
== Test Report ==<br />
{| {{prettytable}}<br />
<br />
!colspan="4" border="5"|SIP Provider<br />
!colspan="3"|VoIP Test<br />
!colspan="6"|Test Conditions<br />
<br />
|-<br />
<br />
!{{Hl3}} align="center"|Name<br />
!{{Hl3}} align="center"|Domain<br />
!{{Hl3}} align="center"|Proxy<br />
!{{Hl3}} align="center"|Firewall<br />
<br />
!{{Hl3}} align="center"|Register<br />
!{{Hl3}} align="center"|Call-Out<br />
!{{Hl3}} align="center"|Call-In<br />
<br />
!{{Hl3}} align="center"|Linphone<br />
!{{Hl3}} align="center"|Network (WiFi/EVDO/3G)<br />
!{{Hl3}} align="center"|Device<br />
!{{Hl3}} align="center"|When<br />
!{{Hl3}} align="center"|Who<br />
!{{Hl3}} align="center"|Comments<br />
<br />
|-<br />
<br />
|[http://fr.wikipedia.org/wiki/Freephonie Freephonie]||freephonie.net||''(empty)''||NONE<br />
||OK||OK ''(pstn)''||''(untested)''<br />
||0.1.8||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Mar 2011||Thibaud||Call-in not really a feature of Freephonie<br />
|-<br />
|[http://www.iptel.org/service iptel.org]||iptel.org||sip.iptel.org ''(optional)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||proxy.sipthor.net||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://support.gizmoproject.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=409 Gizmo]||proxy01.sipphone.com||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.draytel.org/features Draytel]||draytel.org||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||NONE<br />
||OK||OK||OK (most of the time- inconsistent),'' ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011 ''(updated)''||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||STUN, stun.sipgate.net:10000<br />
||OK||untested||hangs at INCOMING_INITIATED ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||pbxes.com||<br />
||REG PENDING||||<br />
||0.1.8||||Pre2 2.1||Mar 2011||wprater||<br />
|-<br />
|[http://www.vonage.com vonage]||sphone.vopr.vonage.net||(empty)||Tried With and Without||OK*||OK* (to vonage & sprint mobile)<br />
||OK* (from vonage & sprint mobile)||0.1.8 ||Both Wifi+NAT and Sprint ||Pre 1.4.5 ||Mar 2011||jjeansonne||*with some struggle to get sucessful registration and calls placed. Had to restart the app many times and go in/out of account setting page<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||pbxes.org||NONE<br />
||OK||hangs at CALL_OUT_RINGING||untested<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Entry for pbxes above has wrong domain entered<br />
|-<br />
|[http://1und1.de 1und1]||1und1.de||sip.1und1.de||STUN, stun.1und1.de<br />
||REG PENDING||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://ekiga.net ekiga]||ekiga.net||(empty)||STUN, stun.1und1.de<br />
||REG OK||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.callcentric.com callcentric]||callcentric.com||(empty)||''(n/a)''<br />
||REG_PENDING||||<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||(empty)||''(n/a)''<br />
||OK||''(untested)''||hangs at INCOMING_CALL_INIT<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||hangs at INCOMING_CALL_INIT<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|''New entry...''|| || ||<br />
|| || || <br />
|| || || || || || ''Please copy this row so the template still exists... :-)''<br />
|-<br />
|}</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Application:Linphone&diff=14361Application:Linphone2011-03-21T09:00:46Z<p>Kostka: /* Test Report */</p>
<hr />
<div>{{application<br />
|name=Linphone<br />
|type=webOS<br />
|version=0.1.8<br />
|tag=Communications<br />
|screenshot=Icon_WebOSInternals_Linphone.png<br />
|description=}}<br />
<br />
This is the very first true VoIP application running on any webOS device.<br />
<br />
Linphone for webOS is a port of the original [http://www.linphone.org/ Linphone] command-line application.<br />
<br />
== Summary ==<br />
Linphone is a general purpose SIP softphone. It allows you to place and receive VoIP calls on any SIP account you may have.<br />
<br />
Linphone isn't bound to any operator. Because it is compatible with SIP, it can work with any VoIP operator using SIP (most of them use SIP, the most notable exception being Skype).<br />
<br />
== Alpha Test ==<br />
<br />
Linphone / webOS is currently in '''''alpha''''' test.<br />
<br />
At the moment, to get Linphone you have to already have a good understanding of VoIP (the open standard SIP kind, not the closed proprietary Skype kind) and make yourself known in the [irc://chat.freenode.net/webos-internals #webos-internals IRC channel] (see [[WebOS-Internals_IRC_Channel_Policy|policy]], daily logs available in [http://logs.nslu2-linux.org/livelogs/webos-internals.txt current], [http://logs.nslu2-linux.org/livelogs/webos-internals-prev.txt previous] and [http://logs.nslu2-linux.org/livelogs/webos-internals/ all past days]).<br />
<br />
Alpha testers, please report at the bottom of this page success & failure with your SIP provider(s). Add or update your own rows in the table (please use your P|C or WOI identity so we can PM you if needed).<br />
<br />
Any other information/request you would like to share/ask, please report [http://forums.precentral.net/webos-internals/274615-linphone-alpha-testing.html in the dedicated thread at PreCentral].<br />
<br />
== SIP Account ==<br />
<br />
You will have received some registration information from your SIP provider by the end of the sign-up process:<br />
:* '''username''' or '''phonenumber'''<br />
:* '''password'''<br />
:* '''domain'''<br />
:* '''proxy''' (''optional'')<br />
<br />
<br />
Your SIP identity is formed by grouping the '''Username''' or '''Phonenumber''' and the '''Domain''' together:<br />
:* sip:'''''username'''''@'''''domain'''''<br />
or<br />
:* sip:'''''phonenumber'''''@'''''domain'''''<br />
and will be used by other people willing to call you on your webOS device when running Linphone.<br />
<br />
== Dialpad ==<br />
[[File:Linphone_Dialpad.png|200px|right]]<br />
<br />
This is (obviously!) where you dial a number you want to call...<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Preferences ==<br />
<br />
The Linphone preferences screen can be accessed by tapping the menu button on the top left corner of your device. <br />
[[File:Linphone_Preferences.png|200px|right]]<br />
<br />
<br />
The "'''SIP'''" group:<br />
:* '''NAME''' - enter your '''''username''''' or '''''phonenumber'''''<br />
:* '''PASSWORD''' - enter your '''''password'''''<br />
:* '''DOMAIN''' - enter your SIP provider's '''''domain'''''<br />
:* '''USE PROXY''': select<br />
::- '''NO''' if your SIP provider does not require a specific proxy ('''PROXY''' field hidden)<br />
::- '''YES''' if a '''''proxy''''' is required with an address different from '''''domain''''' ('''PROXY''' field shown)<br />
:* '''PROXY''' - enter your SIP provider '''''proxy''''' (or '''''proxy:port'''''), if any<br />
<br />
The "'''NETWORK'''" group:<br />
:* '''FIREWALL''' - select<br />
::- '''NONE''' if you have a direct connection to the internet or you are behind a router with an [http://en.wikipedia.org/wiki/Application_Layer_Gateway application-level gateway] for SIP ('''ADDRESS''' and '''SERVER''' fields hidden)<br />
::- '''NAT''' to provide the public IP address of your router ('''ADDRESS''' field shown)<br />
::- '''STUN''' to rely on a STUN server to discover the public IP address of your router ('''SERVER''' field shown)<br />
:* '''ADDRESS''' - enter your router's public IP address<br />
:* '''SERVER''' - enter the address of the STUN server<br />
<br />
== Limitations ==<br />
<br />
:* The sound comes from the back-speaker for now. Work is underway to bring the sound from the front speaker<br />
:* Until echo-cancellation is activated, the person on the other end will suffer some echo because of the back-speaker...<br />
:* The proximity sensor is not activated (yet!). To prevent unintentional screen touch from the ear when close to the head, it is better to turn-off the screen for now...<br />
<br />
== Test Report ==<br />
{| {{prettytable}}<br />
<br />
!colspan="4" border="5"|SIP Provider<br />
!colspan="3"|VoIP Test<br />
!colspan="6"|Test Conditions<br />
<br />
|-<br />
<br />
!{{Hl3}} align="center"|Name<br />
!{{Hl3}} align="center"|Domain<br />
!{{Hl3}} align="center"|Proxy<br />
!{{Hl3}} align="center"|Firewall<br />
<br />
!{{Hl3}} align="center"|Register<br />
!{{Hl3}} align="center"|Call-Out<br />
!{{Hl3}} align="center"|Call-In<br />
<br />
!{{Hl3}} align="center"|Linphone<br />
!{{Hl3}} align="center"|Network (WiFi/EVDO/3G)<br />
!{{Hl3}} align="center"|Device<br />
!{{Hl3}} align="center"|When<br />
!{{Hl3}} align="center"|Who<br />
!{{Hl3}} align="center"|Comments<br />
<br />
|-<br />
<br />
|[http://fr.wikipedia.org/wiki/Freephonie Freephonie]||freephonie.net||''(empty)''||NONE<br />
||OK||OK ''(pstn)''||''(untested)''<br />
||0.1.8||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Mar 2011||Thibaud||Call-in not really a feature of Freephonie<br />
|-<br />
|[http://www.iptel.org/service iptel.org]||iptel.org||sip.iptel.org ''(optional)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||proxy.sipthor.net||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://support.gizmoproject.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=409 Gizmo]||proxy01.sipphone.com||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.draytel.org/features Draytel]||draytel.org||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||NONE<br />
||OK||OK||OK (most of the time- inconsistent),'' ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011 ''(updated)''||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||STUN, stun.sipgate.net:10000<br />
||OK||untested||hangs at INCOMING_INITIATED ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||pbxes.com||<br />
||REG PENDING||||<br />
||0.1.8||||Pre2 2.1||Mar 2011||wprater||<br />
|-<br />
|[http://www.vonage.com vonage]||sphone.vopr.vonage.net||(empty)||Tried With and Without||OK*||OK* (to vonage & sprint mobile)<br />
||OK* (from vonage & sprint mobile)||0.1.8 ||Both Wifi+NAT and Sprint ||Pre 1.4.5 ||Mar 2011||jjeansonne||*with some struggle to get sucessful registration and calls placed. Had to restart the app many times and go in/out of account setting page<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||pbxes.org||NONE<br />
||OK||hangs at CALL_OUT_RINGING||untested<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Entry for pbxes above has wrong domain entered<br />
|-<br />
|[http://1und1.de 1und1]||1und1.de||sip.1und1.de||STUN, stun.1und1.de<br />
||REG PENDING||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://ekiga.net ekiga]||ekiga.net||(empty)||STUN, stun.1und1.de<br />
||REG OK||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.callcentric.com callcentric]||callcentric.com||(empty)||''(n/a)''<br />
||REG_PENDING||||<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|''New entry...''|| || ||<br />
|| || || <br />
|| || || || || || ''Please copy this row so the template still exists... :-)''<br />
|-<br />
|}</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Application:Linphone&diff=14359Application:Linphone2011-03-21T08:50:59Z<p>Kostka: /* Test Report */</p>
<hr />
<div>{{application<br />
|name=Linphone<br />
|type=webOS<br />
|version=0.1.8<br />
|tag=Communications<br />
|screenshot=Icon_WebOSInternals_Linphone.png<br />
|description=}}<br />
<br />
This is the very first true VoIP application running on any webOS device.<br />
<br />
Linphone for webOS is a port of the original [http://www.linphone.org/ Linphone] command-line application.<br />
<br />
== Summary ==<br />
Linphone is a general purpose SIP softphone. It allows you to place and receive VoIP calls on any SIP account you may have.<br />
<br />
Linphone isn't bound to any operator. Because it is compatible with SIP, it can work with any VoIP operator using SIP (most of them use SIP, the most notable exception being Skype).<br />
<br />
== Alpha Test ==<br />
<br />
Linphone / webOS is currently in '''''alpha''''' test.<br />
<br />
At the moment, to get Linphone you have to already have a good understanding of VoIP (the open standard SIP kind, not the closed proprietary Skype kind) and make yourself known in the [irc://chat.freenode.net/webos-internals #webos-internals IRC channel] (see [[WebOS-Internals_IRC_Channel_Policy|policy]], daily logs available in [http://logs.nslu2-linux.org/livelogs/webos-internals.txt current], [http://logs.nslu2-linux.org/livelogs/webos-internals-prev.txt previous] and [http://logs.nslu2-linux.org/livelogs/webos-internals/ all past days]).<br />
<br />
Alpha testers, please report at the bottom of this page success & failure with your SIP provider(s). Add or update your own rows in the table (please use your P|C or WOI identity so we can PM you if needed).<br />
<br />
Any other information/request you would like to share/ask, please report [http://forums.precentral.net/webos-internals/274615-linphone-alpha-testing.html in the dedicated thread at PreCentral].<br />
<br />
== SIP Account ==<br />
<br />
You will have received some registration information from your SIP provider by the end of the sign-up process:<br />
:* '''username''' or '''phonenumber'''<br />
:* '''password'''<br />
:* '''domain'''<br />
:* '''proxy''' (''optional'')<br />
<br />
<br />
Your SIP identity is formed by grouping the '''Username''' or '''Phonenumber''' and the '''Domain''' together:<br />
:* sip:'''''username'''''@'''''domain'''''<br />
or<br />
:* sip:'''''phonenumber'''''@'''''domain'''''<br />
and will be used by other people willing to call you on your webOS device when running Linphone.<br />
<br />
== Dialpad ==<br />
[[File:Linphone_Dialpad.png|200px|right]]<br />
<br />
This is (obviously!) where you dial a number you want to call...<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Preferences ==<br />
<br />
The Linphone preferences screen can be accessed by tapping the menu button on the top left corner of your device. <br />
[[File:Linphone_Preferences.png|200px|right]]<br />
<br />
<br />
The "'''SIP'''" group:<br />
:* '''NAME''' - enter your '''''username''''' or '''''phonenumber'''''<br />
:* '''PASSWORD''' - enter your '''''password'''''<br />
:* '''DOMAIN''' - enter your SIP provider's '''''domain'''''<br />
:* '''USE PROXY''': select<br />
::- '''NO''' if your SIP provider does not require a specific proxy ('''PROXY''' field hidden)<br />
::- '''YES''' if a '''''proxy''''' is required with an address different from '''''domain''''' ('''PROXY''' field shown)<br />
:* '''PROXY''' - enter your SIP provider '''''proxy''''' (or '''''proxy:port'''''), if any<br />
<br />
The "'''NETWORK'''" group:<br />
:* '''FIREWALL''' - select<br />
::- '''NONE''' if you have a direct connection to the internet or you are behind a router with an [http://en.wikipedia.org/wiki/Application_Layer_Gateway application-level gateway] for SIP ('''ADDRESS''' and '''SERVER''' fields hidden)<br />
::- '''NAT''' to provide the public IP address of your router ('''ADDRESS''' field shown)<br />
::- '''STUN''' to rely on a STUN server to discover the public IP address of your router ('''SERVER''' field shown)<br />
:* '''ADDRESS''' - enter your router's public IP address<br />
:* '''SERVER''' - enter the address of the STUN server<br />
<br />
== Limitations ==<br />
<br />
:* The sound comes from the back-speaker for now. Work is underway to bring the sound from the front speaker<br />
:* Until echo-cancellation is activated, the person on the other end will suffer some echo because of the back-speaker...<br />
:* The proximity sensor is not activated (yet!). To prevent unintentional screen touch from the ear when close to the head, it is better to turn-off the screen for now...<br />
<br />
== Test Report ==<br />
{| {{prettytable}}<br />
<br />
!colspan="4" border="5"|SIP Provider<br />
!colspan="3"|VoIP Test<br />
!colspan="6"|Test Conditions<br />
<br />
|-<br />
<br />
!{{Hl3}} align="center"|Name<br />
!{{Hl3}} align="center"|Domain<br />
!{{Hl3}} align="center"|Proxy<br />
!{{Hl3}} align="center"|Firewall<br />
<br />
!{{Hl3}} align="center"|Register<br />
!{{Hl3}} align="center"|Call-Out<br />
!{{Hl3}} align="center"|Call-In<br />
<br />
!{{Hl3}} align="center"|Linphone<br />
!{{Hl3}} align="center"|Network (WiFi/EVDO/3G)<br />
!{{Hl3}} align="center"|Device<br />
!{{Hl3}} align="center"|When<br />
!{{Hl3}} align="center"|Who<br />
!{{Hl3}} align="center"|Comments<br />
<br />
|-<br />
<br />
|[http://fr.wikipedia.org/wiki/Freephonie Freephonie]||freephonie.net||''(empty)''||NONE<br />
||OK||OK ''(pstn)''||''(untested)''<br />
||0.1.8||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Mar 2011||Thibaud||Call-in not really a feature of Freephonie<br />
|-<br />
|[http://www.iptel.org/service iptel.org]||iptel.org||sip.iptel.org ''(optional)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||proxy.sipthor.net||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://support.gizmoproject.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=409 Gizmo]||proxy01.sipphone.com||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.draytel.org/features Draytel]||draytel.org||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||NONE<br />
||OK||OK||OK (most of the time- inconsistent),'' ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011 ''(updated)''||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||STUN, stun.sipgate.net:10000<br />
||OK||untested||hangs at INCOMING_INITIATED ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||pbxes.com||<br />
||REG PENDING||||<br />
||0.1.8||||Pre2 2.1||Mar 2011||wprater||<br />
|-<br />
|[http://www.vonage.com vonage]||sphone.vopr.vonage.net||(empty)||Tried With and Without||OK*||OK* (to vonage & sprint mobile)<br />
||OK* (from vonage & sprint mobile)||0.1.8 ||Both Wifi+NAT and Sprint ||Pre 1.4.5 ||Mar 2011||jjeansonne||*with some struggle to get sucessful registration and calls placed. Had to restart the app many times and go in/out of account setting page<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||pbxes.org||NONE<br />
||OK||hangs at CALL_OUT_RINGING||untested<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Entry for pbxes above has wrong domain entered<br />
|-<br />
|[http://1und1.de 1und1]||1und1.de||sip.1und1.de||STUN, stun.1und1.de<br />
||REG PENDING||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://ekiga.net ekiga]||ekiga.net||(empty)||STUN, stun.1und1.de<br />
||REG OK||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WIFI (DSL router, 8/1Mbps)||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|''New entry...''|| || ||<br />
|| || || <br />
|| || || || || || ''Please copy this row so the template still exists... :-)''<br />
|-<br />
|}</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Application:Linphone&diff=14357Application:Linphone2011-03-21T08:48:52Z<p>Kostka: /* Test Report */</p>
<hr />
<div>{{application<br />
|name=Linphone<br />
|type=webOS<br />
|version=0.1.8<br />
|tag=Communications<br />
|screenshot=Icon_WebOSInternals_Linphone.png<br />
|description=}}<br />
<br />
This is the very first true VoIP application running on any webOS device.<br />
<br />
Linphone for webOS is a port of the original [http://www.linphone.org/ Linphone] command-line application.<br />
<br />
== Summary ==<br />
Linphone is a general purpose SIP softphone. It allows you to place and receive VoIP calls on any SIP account you may have.<br />
<br />
Linphone isn't bound to any operator. Because it is compatible with SIP, it can work with any VoIP operator using SIP (most of them use SIP, the most notable exception being Skype).<br />
<br />
== Alpha Test ==<br />
<br />
Linphone / webOS is currently in '''''alpha''''' test.<br />
<br />
At the moment, to get Linphone you have to already have a good understanding of VoIP (the open standard SIP kind, not the closed proprietary Skype kind) and make yourself known in the [irc://chat.freenode.net/webos-internals #webos-internals IRC channel] (see [[WebOS-Internals_IRC_Channel_Policy|policy]], daily logs available in [http://logs.nslu2-linux.org/livelogs/webos-internals.txt current], [http://logs.nslu2-linux.org/livelogs/webos-internals-prev.txt previous] and [http://logs.nslu2-linux.org/livelogs/webos-internals/ all past days]).<br />
<br />
Alpha testers, please report at the bottom of this page success & failure with your SIP provider(s). Add or update your own rows in the table (please use your P|C or WOI identity so we can PM you if needed).<br />
<br />
Any other information/request you would like to share/ask, please report [http://forums.precentral.net/webos-internals/274615-linphone-alpha-testing.html in the dedicated thread at PreCentral].<br />
<br />
== SIP Account ==<br />
<br />
You will have received some registration information from your SIP provider by the end of the sign-up process:<br />
:* '''username''' or '''phonenumber'''<br />
:* '''password'''<br />
:* '''domain'''<br />
:* '''proxy''' (''optional'')<br />
<br />
<br />
Your SIP identity is formed by grouping the '''Username''' or '''Phonenumber''' and the '''Domain''' together:<br />
:* sip:'''''username'''''@'''''domain'''''<br />
or<br />
:* sip:'''''phonenumber'''''@'''''domain'''''<br />
and will be used by other people willing to call you on your webOS device when running Linphone.<br />
<br />
== Dialpad ==<br />
[[File:Linphone_Dialpad.png|200px|right]]<br />
<br />
This is (obviously!) where you dial a number you want to call...<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Preferences ==<br />
<br />
The Linphone preferences screen can be accessed by tapping the menu button on the top left corner of your device. <br />
[[File:Linphone_Preferences.png|200px|right]]<br />
<br />
<br />
The "'''SIP'''" group:<br />
:* '''NAME''' - enter your '''''username''''' or '''''phonenumber'''''<br />
:* '''PASSWORD''' - enter your '''''password'''''<br />
:* '''DOMAIN''' - enter your SIP provider's '''''domain'''''<br />
:* '''USE PROXY''': select<br />
::- '''NO''' if your SIP provider does not require a specific proxy ('''PROXY''' field hidden)<br />
::- '''YES''' if a '''''proxy''''' is required with an address different from '''''domain''''' ('''PROXY''' field shown)<br />
:* '''PROXY''' - enter your SIP provider '''''proxy''''' (or '''''proxy:port'''''), if any<br />
<br />
The "'''NETWORK'''" group:<br />
:* '''FIREWALL''' - select<br />
::- '''NONE''' if you have a direct connection to the internet or you are behind a router with an [http://en.wikipedia.org/wiki/Application_Layer_Gateway application-level gateway] for SIP ('''ADDRESS''' and '''SERVER''' fields hidden)<br />
::- '''NAT''' to provide the public IP address of your router ('''ADDRESS''' field shown)<br />
::- '''STUN''' to rely on a STUN server to discover the public IP address of your router ('''SERVER''' field shown)<br />
:* '''ADDRESS''' - enter your router's public IP address<br />
:* '''SERVER''' - enter the address of the STUN server<br />
<br />
== Limitations ==<br />
<br />
:* The sound comes from the back-speaker for now. Work is underway to bring the sound from the front speaker<br />
:* Until echo-cancellation is activated, the person on the other end will suffer some echo because of the back-speaker...<br />
:* The proximity sensor is not activated (yet!). To prevent unintentional screen touch from the ear when close to the head, it is better to turn-off the screen for now...<br />
<br />
== Test Report ==<br />
{| {{prettytable}}<br />
<br />
!colspan="4" border="5"|SIP Provider<br />
!colspan="3"|VoIP Test<br />
!colspan="6"|Test Conditions<br />
<br />
|-<br />
<br />
!{{Hl3}} align="center"|Name<br />
!{{Hl3}} align="center"|Domain<br />
!{{Hl3}} align="center"|Proxy<br />
!{{Hl3}} align="center"|Firewall<br />
<br />
!{{Hl3}} align="center"|Register<br />
!{{Hl3}} align="center"|Call-Out<br />
!{{Hl3}} align="center"|Call-In<br />
<br />
!{{Hl3}} align="center"|Linphone<br />
!{{Hl3}} align="center"|Network (WiFi/EVDO/3G)<br />
!{{Hl3}} align="center"|Device<br />
!{{Hl3}} align="center"|When<br />
!{{Hl3}} align="center"|Who<br />
!{{Hl3}} align="center"|Comments<br />
<br />
|-<br />
<br />
|[http://fr.wikipedia.org/wiki/Freephonie Freephonie]||freephonie.net||''(empty)''||NONE<br />
||OK||OK ''(pstn)''||''(untested)''<br />
||0.1.8||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Mar 2011||Thibaud||Call-in not really a feature of Freephonie<br />
|-<br />
|[http://www.iptel.org/service iptel.org]||iptel.org||sip.iptel.org ''(optional)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||proxy.sipthor.net||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://support.gizmoproject.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=409 Gizmo]||proxy01.sipphone.com||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.draytel.org/features Draytel]||draytel.org||''(empty)''||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.6||WiFi ''(DSL router, 18/1Mbps)''||Pre- 1.4.5||Feb 2011||Thibaud||Call initiated from linphonec-3.1.2@Ubuntu-9.10<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||NONE<br />
||OK||OK||OK (most of the time- inconsistent),'' ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011 ''(updated)''||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.sipgate.com sipgate]||sipgate.com||sipgate.com||STUN, stun.sipgate.net:10000<br />
||OK||untested||hangs at INCOMING_INITIATED ''(sip)''<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Call initiated from Voogle (Google Voice)<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||pbxes.com||<br />
||REG PENDING||||<br />
||0.1.8||||Pre2 2.1||Mar 2011||wprater||<br />
|-<br />
|[http://www.vonage.com vonage]||sphone.vopr.vonage.net||(empty)||Tried With and Without||OK*||OK* (to vonage & sprint mobile)<br />
||OK* (from vonage & sprint mobile)||0.1.8 ||Both Wifi+NAT and Sprint ||Pre 1.4.5 ||Mar 2011||jjeansonne||*with some struggle to get sucessful registration and calls placed. Had to restart the app many times and go in/out of account setting page<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.org||pbxes.org||NONE<br />
||OK||hangs at CALL_OUT_RINGING||untested<br />
||0.1.8||WiFi ''(University of Kentucky WiFi)''||Pre- 2.1||Mar 2011||Ricyteach||Entry for pbxes above has wrong domain entered<br />
|-<br />
|[http://1und1.de 1und1]||1und1.de||sip.1und1.de||STUN, stun.1und1.de<br />
||REG PENDING||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://ekiga.net ekiga]||ekiga.net||(empty)||STUN, stun.1und1.de<br />
||REG OK||||<br />
||0.1.8||WIFI (DSL router, 16/1Mbps)||Pre 1.4.5||Mar 2011||einalex||<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pixi+ 1.4.5||Feb 2011||puuj||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://www.pbxes.com pbxes]||pbxes.com||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|[http://wiki.sip2sip.info/ SIP2SIP]||sip2sip.info||(empty)||''(n/a)''<br />
||OK||''(untested)''||OK ''(sip)''<br />
||0.1.8||WiFi||Pre 2.1.0||Mar 2011||kostka||Call initiated from Google Voice via IPKall number<br />
|-<br />
|''New entry...''|| || ||<br />
|| || || <br />
|| || || || || || ''Please copy this row so the template still exists... :-)''<br />
|-<br />
|}</div>Kostkahttp://wiki.webos-internals.org/index.php?title=WebOS_Doctor_Versions&diff=14117WebOS Doctor Versions2011-03-16T02:51:16Z<p>Kostka: /* Pre */</p>
<hr />
<div>== How to get webOS ROM ==<br />
<br />
You can download webOS ROM for your specific Palm device at http://ws.palm.com/webosdoctor/serialnumberinitial.htm <br />
by using your Palm device serial number.<br />
<br />
== Serial Numbers ==<br />
<br />
Please add the first five characters of your serial number in the appropriate download link section below if it is not there already. Then put your serial number in http://palm.com/rom to get the text inside the brackets describing your device configuration.<br />
<br />
== Download links ==<br />
It seems the webOS Doctor jar files provided by Palm keep changing:<br />
<br />
'''''NOTE: Since March 18th 2010, the Palm servers are no longer hosting old WebOSDoctor versions via the links below. The current versions are still available.'''''<br />
<br />
=== Sprint ===<br />
==== Pre ====<br />
* P100EWW: P5PE0XXXXXXX (Pre on the Sprint network)<br />
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/sr1ntp121rod/webosdoctorp100ewwsprint.jar<br />
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/sr1ntp131rod/webosdoctorp100ewwsprint.jar<br />
* version 1.3.5 http://palm.cdnetworks.net/rom/pre/p135r0d12302009/sr1ntp135rod/webosdoctorp100ewwsprint.jar<br />
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/sr1ntp1351rod/webosdoctorp100ewwsprint.jar<br />
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/sr1ntp140rod/webosdoctorp100ewwsprint.jar<br />
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pre/p1411r0d03312010/sr1ntp1411rod/webosdoctorp100ewwsprint.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d08102010/spr1ntp145rod/webosdoctorp100ewwsprint.jar<br />
<br />
==== Pixi ====<br />
*P120EWW: P6P20XXXXXXX (Pixi on the Sprint network)<br />
* version 1.3.1 <br />
* version 1.3.2 <br />
* version 1.3.5 <br />
* version 1.3.5.1 <br />
* version 1.4.0 <br />
* version 1.4.1.1 <br />
* version 1.4.5 <br />
''(Palm changed p200eww to p120eww in version 1.3.5.1)''<br />
''(Palm changed p120eww back to p200eww in version 1.4.0)''<br />
<br />
=== Bell Mobility ===<br />
==== Pre ====<br />
* version 1.2.1 http://palm.cdnetworks.net/rom/p121r0d10092009/b11ep121rod/webosdoctorp100ewwbellmo.jar<br />
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/b11ep131rod/webosdoctorp100ewwbellmo.jar<br />
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/b11ep1351rod/webosdoctorp100ewwbellmo.jar<br />
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/b11ep140rod/webosdoctorp100ewwbellmo.jar<br />
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/b11ep141rod/webosdoctorp100ewwbellmo.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d07142010/b11ep145rod/webosdoctorp100ewwbellmo.jar<br />
<br />
=== O2 Germany, UK and Ireland / Movistar Spain ===<br />
==== Pre ====<br />
* P100UEU: P5FU0XXXXXXX (Pre on the Movistar network)<br />
* P100UEU: P5HUGXXXXXXX (Pre on the Excelcomindo network)<br />
* version 1.1.3 http://palm.cdnetworks.net/rom/p113r0d10122009/wr640xdfgy12z/webosdoctorp100eww-wr.jar<br />
* version 1.3.1 http://palm.cdnetworks.net/rom/pre/p131r0d11172009/wrep131rod/webosdoctorp100ueu-wr.jar<br />
* version 1.3.5.2 http://palm.cdnetworks.net/rom/pre/p1352r0d01182010/wrep1352rod/webosdoctorp100ueu-wr.jar<br />
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/wrep140rod/webosdoctorp100ueu-wr.jar<br />
* version 1.4.1 http://palm.cdnetworks.net/rom/pre/p141r0d03312010/eudep141rod/webosdoctorp100ueu-wr.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pre/p145r0d06302010/eudep145rod/webosdoctorp100ueu-wr.jar<br />
<br />
==== Pre Plus ====<br />
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar<br />
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar<br />
<br />
==== Pixi Plus ====<br />
* P121UEU: P8GUGXXXXXXX (Pixi Plus)<br />
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04282010/wrep141rod/webosdoctorp121ewweu-wr.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar<br />
<br />
=== Vodafone Europe ===<br />
==== Pixi Plus ====<br />
* version 1.4.1.2 http://palm.cdnetworks.net/rom/pixiplus/px1412r0d04282010/wrep1412rod/webosdoctorp121ewweu-wr.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar<br />
<br />
==== Pre Plus ====<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar<br />
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d02212011/eudep210rod/webosdoctorp101ueude-wr.jar<br />
<br />
=== SFR France ===<br />
==== Pre Plus ====<br />
* P101EU: P7JUAXXXXXXX (Pre Plus on the SFR network)<br />
* version 1.4.1 http://palm.cdnetworks.net/rom/preplus/p141r0d04272010/wrep141rod/webosdoctorp101ueu-wr.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d06302010/eudep145rod/webosdoctorp101ueu-wr.jar<br />
* version 2.1.0 http://palm.cdnetworks.net/rom/preplus/p210r0d03142011/eudep210rod/webosdoctorp101ueu-wr.jar<br />
<br />
==== Pixi Plus ====<br />
* version 1.4.1 http://palm.cdnetworks.net/rom/pixiplus/px141r0d04272010/wrep141rod/webosdoctorp121ueu-wr.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d06302010/wrep145rod/webosdoctorp121ewweu-wr.jar<br />
<br />
==== Pre 2 ====<br />
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar<br />
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar<br />
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar<br />
<br />
=== Telcel GSM, Mexico ===<br />
==== Pre ====<br />
* version 1.2.5 http://palm.cdnetworks.net/rom/pre/p125r0d11252009/tce11p125rod/webosdoctorp100ewwtelcel.jar<br />
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/tce11p1351rod/webosdoctorp100ewwtelcel.jar<br />
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/tce11p140rod/webosdoctorp100ewwtelcel.jar<br />
<br />
=== Verizon Wireless ===<br />
==== Pre Plus ====<br />
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pre/p1351r0d01082010/ver1z0np1351rod/webosdoctorp101ewwverizonwireless.jar<br />
* version 1.4.0 http://palm.cdnetworks.net/rom/pre/p14r0d02252010/ver1z0np140rod/webosdoctorp101ewwverizonwireless.jar<br />
* version 1.4.1.1 http://palm.cdnetworks.net/rom/preplus/p1411r0d04282010/ver1z0np1411rod/webosdoctorp101ewwverizonwireless.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/ver1z0np145rod/webosdoctorp101ewwverizonwireless.jar<br />
<br />
==== Pixi Plus ====<br />
* version 1.3.5.1 http://palm.cdnetworks.net/rom/pixi/px1351r0d01082010/ver1z0np1351rod/webosdoctorp121ewwverizonwireless.jar<br />
* version 1.4.0 http://palm.cdnetworks.net/rom/pixi/px14r0d02252010/ver1z0np140rod/webosdoctorp121ewwverizonwireless.jar<br />
* version 1.4.1.1 http://palm.cdnetworks.net/rom/pixiplus/px1411r0d04282010/ver1z0np1411rod/webosdoctorp121ewwverizonwireless.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d08302010/ver1z0np145rod/webosdoctorp121ewwverizonwireless.jar<br />
<br />
==== Pre 2 ====<br />
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar<br />
<br />
=== AT&T ===<br />
==== Pre Plus ====<br />
* P101UNA : P7CG0XXXXXXX (Pre Plus on AT&T)<br />
* version 1.4.2 http://palm.cdnetworks.net/rom/preplus/p142r0d05162010/attp142rod/webosdoctorp101ewwatt.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/preplus/p145r0d09132010/attp145rod/webosdoctorp101ewwatt.jar<br />
<br />
==== Pixi Plus ====<br />
P121EWW: P8WU0XXXXXXX (Pixi Plus on the AT&T network)<br />
* version 1.4.3 http://palm.cdnetworks.net/rom/pixiplus/px143r0d06062010/attp143rod/webosdoctorp121ewwatt.jar<br />
* version 1.4.5 http://palm.cdnetworks.net/rom/pixiplus/px145r0d10112010/attp145rod/webosdoctorp121ewwatt.jar<br />
<br />
=== Rogers ===<br />
==== Pre 2 ====<br />
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar<br />
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210r0d03082011/wrep210rod/webosdoctorp104ueu-wr.jar<br />
''(Palm changed p102ueuna to p104ueu in 2.1.0)''<br />
<br />
=== Unlocked ===<br />
==== Pre 2 ====<br />
* P102UEU: PG4U0XXXXXXX (Pre 2 on the Unlocked – Europe network)<br />
* P102UNA: PG9U0XXXXXXX (Pre 2 on the Unlocked - North America network)<br />
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11012010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU only)<br />
* version 2.0.0 http://palm.cdnetworks.net/rom/pre2/p20r0d11182010/wrep20rod/webosdoctorp103ueu-wr.jar (P102UEU & P102UNA)<br />
* version 2.0.1 http://palm.cdnetworks.net/rom/pre2/p201r0d11242010/wrep201rod/webosdoctorp102ueuna-wr.jar (P102UEU & P102UNA)<br />
* version 2.1.0 http://palm.cdnetworks.net/rom/pre2/p210sfr03082011/wrep210rod/webosdoctorp103ueuna-wr.jar (P102UEU & P102UNA)<br />
''(Palm changed p103ueu to p102ueuna in 2.0.1)''<br />
''(Palm changed p102ueuna to p103ueuna in 2.1.0)''<br />
<br />
== License ==<br />
<br />
Note that the webOS Doctor package comes with the following license:<br />
<br />
RESTRICTIONS: The Software is licensed for use only with the single Palm device you originally purchased, and you may not distribute or make the Software available over a network or for use with multiple devices. The Software and supporting documentation may be copied only as necessary for backup or archive purposes in support of your use of the Software.<br />
<br />
So we can't host different versions of it anywhere - the best we can do is record the md5sums of the versions we know about so that individuals can match this to the files they have for use with their Palm device.<br />
<br />
== MD5 sums ==<br />
<br />
Here is a list of all the versions that we know about (with md5sums for each, and the build date and build number as displayed in the title bar of the webOS Doctor):<br />
<br />
Date # MD5SUM Filename<br />
20090522 118 4b3e396f8b1f1c5d3388e3c298af0484 webosdoctorp100ewwsprint-1.0.2.jar<br />
20090616 124 0c8027b5a707eb0d02b1997d48021bd5 webosdoctorp100ewwsprint-1.0.3.jar<br />
20090623 129 32852c4b57d938e85f0fc819e57eacb7 webosdoctorp100ewwsprint-1.0.4.jar<br />
20090717 143 fc602490fdd7b3be8c5f727349c6195f webosdoctorp100ewwsprint-1.1.0.jar<br />
20090717 83 ffd1bc50066d8f54d134b7aac194e3ec webosdoctorp100ewwbellmo-1.1.0.jar<br />
20090913 111 c8f80b3cdbb9b96fd73bbb6062950a83 webosdoctorp100ewwbellmo-1.2.0.jar<br />
20090913 171 93c3f106b7a7e5ef572465dcb4488e1c webosdoctorp100ewwsprint-1.2.0.jar<br />
20090924 100 bc29e1144823afc05a50dcdc2c84475d webosdoctorp100eww-wr-1.1.3.jar<br />
20090929 112 52f4a4cd9b182004a7060cfaa5be2c6f webosdoctorp100ewwbellmo-1.2.1.jar<br />
20090929 172 e7600251e12e5b96f3143138ba61b9eb webosdoctorp100ewwsprint-1.2.1.jar<br />
20091008 7 477f6c3d2ff1673aa9a9d1670aa5e88f webosdoctorp100ewwtelcel-1.2.5.jar<br />
20091015 98 1957476e6d9d221413285c6d5ab697d6 webosdoctorp200ewwsprint-1.2.9.1.jar<br />
20091101 112 063c2f66682dd246fa3bf518adae0f53 webosdoctorp200ewwsprint-1.3.1.jar<br />
20091101 122 9bb8e7547996b5b62ce8742198a9d8bb webosdoctorp100ueu-wr-1.3.1.jar<br />
20091101 122 b93f2f6af2c8eefc89f6ccc03b72eeb6 webosdoctorp100eww-wr-1.3.1.jar<br />
20091101 131 c4202a32ca49a1c843f30b77515cac46 webosdoctorp100ewwbellmo-1.3.1.jar<br />
20091101 194 8261682a25ac21bb2f3107ec5c50dc84 webosdoctorp100ewwsprint-1.3.1.jar<br />
20091113 119 eb33e68b07ccad81847d96f546303880 webosdoctorp200ewwsprint-1.3.2.jar<br />
20091125 140 e9a00b0a24a08f4cca4683bc5ec62227 webosdoctorp100ewwbellmo-1.3.5.jar<br />
20091130 134 4af3d5c4a6d0461b95e75b3fadf93435 webosdoctorp100ueu-wr-1.3.5.jar<br />
20091212 147 00b2575415c5645e9840cce4b8d075e6 webosdoctorp200ewwsprint-1.3.5.jar<br />
20091212 219 4daef882c96461dc1c60cc907c4dfbf0 webosdoctorp100ewwsprint-1.3.5.jar<br />
20100103 148 b78ad564fd8dcdfd469ca43285a5cd90 webosdoctorp120ewwsprint-1.3.5.1.jar<br />
20100103 154 ff9784382ef53e491cb4d81015a34135 webosdoctorp100ewwbellmo-1.3.5.1.jar<br />
20100103 220 14e3c4168030498b42370115b33ee278 webosdoctorp100ewwsprint-1.3.5.1.jar<br />
20100103 27 173dea06595c3c2080b0a8522a160d1c webosdoctorp100ewwtelcel-1.3.5.1.jar<br />
20100103 98 257ee7c9751a0ff909d3f81792a9b874 webosdoctorp101ewwverizonwireless-1.3.5.1.jar<br />
20100106 148 a3c7ae6d93409dea9f0461636f5c79c0 webosdoctorp100ueu-wr-1.3.5.2.jar<br />
20100108 140 89cc6fbaff0d0ce4a05ed5bae53793f8 webosdoctorp121ewwverizonwireless-1.3.5.1.jar<br />
20100214 179 0593f3b94ec4050febacea14c8af7b10 webosdoctorp100ueu-wr-1.4.0.jar<br />
20100214 187 646dd275690fcd7b3819ddddc488c2de webosdoctorp100ewwbellmo-1.4.0.jar<br />
20100214 195 46025f5f59c98721dee4ef4214e5f90b webosdoctorp200ewwsprint-1.4.0.jar<br />
20100214 254 7aee384f4fdcc6189a027617efaac983 webosdoctorp100ewwsprint-1.4.0.jar<br />
20100214 52 e9a1d644a447d460e340725869f3ad46 webosdoctorp100ewwtelcel-1.4.0.jar<br />
20100220 136 4bb776010b0b88da25630887d72faa18 webosdoctorp101ewwverizonwireless-1.4.0.jar<br />
20100220 169 f7f3296db9ef0682d98f92354f696ba2 webosdoctorp121ewwverizonwireless-1.4.0.jar<br />
20100313 198 7f7d258ba662dcd3085d76cb67dee906 webosdoctorp101ueu-wr-1.4.1.jar <br />
20100317 208 edf4fa9cbac537f4b734339820b85030 webosdoctorp100ewwbellmo-1.4.1.jar<br />
20100318 121 f9b8aaa955255e9645f833b57010b60a webosdoctorp101ewwatt-1.4.2.jar<br />
20100319 190 bd9d4aca9f1b9657956e29a09648e4b0 webosdoctorp121ueu-wr-1.4.1.jar<br />
20100324 202 63ea69769b8b066f7525cba3d3c2d1bc webosdoctorp100ueu-wr-1.4.1.jar<br />
20100324 278 5f736a8baf27a3ea4d525c30f871f2d2 webosdoctorp100ewwsprint-1.4.1.1.jar<br />
20100325 225 a6779bbdbb34a52cde1104a29dab64ca webosdoctorp200ewwsprint-1.4.1.1.jar<br />
20100401 158 edb45ceebb21de02aecf4ae457e785de webosdoctorp101ewwverizonwireless-1.4.1.1.jar<br />
20100401 199 48912881581fb240e2a27e688b80ac79 webosdoctorp121ewwverizonwireless-1.4.1.1.jar<br />
20100419 222 eba97405cc882687567aa0988a206fb4 webosdoctorp121ewwatt-1.4.3.jar<br />
20100614 299 a55a377dd38fd7a8e94ba9514e1d9e18 webosdoctorp100ewwsprint-1.4.5.jar<br />
20100614 222 ca6a2e3a976b593859b11dee9941a80e webosdoctorp100ueu-wr-1.4.5.jar<br />
20100614 222 dddc78516c6770b475d08bdcf20f22d0 webosdoctorp101ueu-wr-1.4.5.jar<br />
20100614 231 1b0c63976ef3bc783770e35cfad55e5f webosdoctorp121ewweu-wr-1.4.5.jar<br />
20100614 232 e11d44f00d7d9b44e7dcddb3f5b45bee webosdoctorp100ewwbellmo-1.4.5.jar<br />
20100614 171 2e1cbe14267c61941d62d2d7fd82a544 webosdoctorp101ewwverizonwireless-1.4.5.jar<br />
20100615 226 7d25cd1a8dbda76d297a9d4998d8e32a webosdoctorp121ewwverizonwireless-1.4.5.jar<br />
20100722 142 6c0c12ae2585e8f8e1adf3965603ba78 webosdoctorp101ewwatt-1.4.5.jar<br />
20100818 233 957acf91ecc1d126c7062477bd10093c webosdoctorp121ewwatt-1.4.5.jar<br />
20101009 70 5152f9f3f9fd24f5491ac809d1138735 webosdoctorp103ueu-wr-2.0.0.jar (P102UEU)<br />
20101009 70 1aa510de51394e490428cc053d3cdfd0 webosdoctorp103ueu-wr-2.0.0.jar (P102UNA)<br />
20101117 79 e9f7c688266718a319b9fdfd6ef6c599 webosdoctorp102ueuna-wr-2.0.1.jar (P102UEU & P102UNA)<br />
20101222 100 643824a4c103e266fd8e2760b098815c webosdoctorp102verizonwireless-2.0.1.jar (P102EWW)<br />
20110201 284 ed2c394171d19a4af9d9d42c670e9791 webosdoctorp101ueude-wr-2.1.0.jar (P101UEU & P101UNA)<br />
20101117 108 477f12cc73f5d8a3a00761dcb3751e6b webosdoctorp103ueuna-wr-2.1.0.jar (P102UEU & P102UNA)<br />
20110202 100 1b9d7d63e0f765647705bac6a867da02 webosdoctorp104ueu-wr-2.1.0.jar (P102UEU & P102UNA)<br />
<br />
== Notes ==<br />
<br />
1.0.3 is the last version to contain PmModemFactory<br />
<br />
Using a 2.0 doctor will wipe your usb partition, unless you already have 2.0 on your device. For example, 1.4.5 > 2.0.1 will wipe usb, but 2.0.0 > 2.0.1 will not.</div>Kostkahttp://wiki.webos-internals.org/index.php?title=WebOS_2_Upgrade&diff=13983WebOS 2 Upgrade2011-03-15T03:52:24Z<p>Kostka: /* Adobe Flash */</p>
<hr />
<div>= Overview =<br />
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.<br />
<br />
'''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.'''<br />
<br />
= Disclaimer =<br />
'''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.'''<br />
<br />
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.<br />
<br />
= Other Tutorials =<br />
'''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.'''<br />
== Tutorials that have been updated to match the latest instructions ==<br />
* ''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}.<br />
== Tutorials that are out of date and should not be relied upon ==<br />
* ''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}.<br />
* ''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].<br />
<br />
= Using MetaDoctor Scripts =<br />
<br />
== Step 0: Backup your device ==<br />
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.<br />
<br />
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?<br />
<br />
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.<br />
<br />
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. <br />
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.<br />
<br />
A guide for backing up using Save/Restore can be found [http://www.precentral.net/backing-your-application-data-settings-save-restore-homebrew here].<br />
<br />
== Step 1: Prerequisites ==<br />
=== Disk Space ===<br />
<br />
You should allow up to 10GB of disk space for this process.<br />
<br />
=== MetaDoctor ===<br />
<br />
See [[Application:MetaDoctor]] for information on how to install MetaDoctor.<br />
<br />
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.<br />
<br />
=== Palm SDK === <br />
<br />
See [http://developer.palm.com/index.php?option=com_content&view=article&layout=page&id=1661 Palm Developer Website]<br />
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.<br />
<br />
=== Novacom Drivers === <br />
<br />
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]<br />
<br />
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. There are no public drivers available for Pre 2 on Linux.<br />
<br />
== Step 2: Prepare your Palm Profile ==<br />
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:<br />
'''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.'''<br />
# Open the Backup app.<br />
# Turn off backups, confirming that you wish to erase your palm profile information.<br />
<br />
'''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.'''<br />
<br />
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.<br />
<br />
== Step 3: Run device-specific MetaDoctor script ==<br />
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. <br />
<br />
'''A NOTE ON "RE-DOCTORING":''' If this is not your first time through this process, you should do a "git pull" and a "make clobber" to ensure you have the latest scripts and a pristine build folder. From the command line (I use Cygwin), type "cd meta-doctor" without the quotes and press enter. Then type "git pull" without the quotes and press enter. Then type "make clobber" without the quotes and press enter. Voila! You now have the latest scripts and a clean folder to build your doctor in.<br />
<br />
'''From the meta-doctor directory''', run the meta-script that corresponds to your device (note that the strings enclosed by &lt; and &gt; in the following line are placeholders for values that you must supply - you cannot type the string exactly as shown):<br />
<pre><nowiki><br />
./scripts/meta-&lt;carrier&gt;-&lt;device&gt;-&lt;version&gt;<br />
</nowiki></pre><br />
<br />
You should replace &lt;carrier&gt;, &lt;device&gt;, and &lt;version&gt; 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.<br />
<br />
A list of all the scripts can be found by typing<br />
<pre><nowiki><br />
ls ./scripts/<br />
</nowiki></pre><br />
<br />
'''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:'''<br />
<pre><nowiki><br />
./scripts/meta-&lt;carrier&gt;-&lt;device&gt;-&lt;version&gt; --wifi-only<br />
</nowiki></pre><br />
<br />
Again, you should replace &lt;device&gt;, &lt;carrier&gt;, and &lt;version&gt; 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.<br />
<br />
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.<br />
<br />
Specific additional information for each of the supported device and carrier combinations can be found below:<br />
<br />
=== AT&T Pre+ ===<br />
<pre><nowiki><br />
./scripts/meta-att-preplus-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You will not be able to purchase apps that require a minimum webOS 2.x version.<br />
<br />
=== BellMo Pre ===<br />
<pre><nowiki><br />
./scripts/meta-bellmo-pre-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You will not be able to purchase apps that require a minimum webOS 2.x version.<br />
<br />
=== O2 Pre ===<br />
<pre><nowiki><br />
./scripts/meta-o2-pre-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).<br />
<br />
=== O2 Pre+ ===<br />
<pre><nowiki><br />
./scripts/meta-o2-preplus-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).<br />
<br />
=== Sprint Pre ===<br />
'''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'''<br />
<br />
<pre><nowiki><br />
./scripts/meta-sprint-pre-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).<br />
<br />
=== Sprint FrankenPre 2 ===<br />
'''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'''<br />
<br />
<pre><nowiki><br />
./scripts/meta-sprint-frankenpre2-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).<br />
<br />
=== Telcel Pre ===<br />
<pre><nowiki><br />
./scripts/meta-telcel-pre-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You will not be able to purchase apps that require a minimum webOS 2.x version.<br />
<br />
=== Verizon Pre+ ===<br />
<pre><nowiki><br />
./scripts/meta-verizon-preplus-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).<br />
<br />
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.<br />
<br />
=== Verizon FrankenPre 2 ===<br />
<pre><nowiki><br />
./scripts/meta-verizon-frankenpre2-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You should be able to purchase apps that require a minimum webOS 2.x version (depending upon geo-restrictions and country of first activation).<br />
<br />
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.<br />
<br />
=== WR Pre ===<br />
<br />
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.<br />
<br />
<pre><nowiki><br />
./scripts/meta-wr-pre-2.1.0<br />
</nowiki></pre><br />
<br />
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.<br />
<br />
You will not be able to purchase apps that require a minimum webOS 2.x version.<br />
<br />
== Step 4: Run the modified webOS Doctor ==<br />
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: <br />
<pre><nowiki>meta-doctor/build/meta-sprint-pre-2.1.0/webosdoctorp101ueude-wr-2.1.0.jar</nowiki></pre><br />
<br />
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.<br />
<br />
Do not USB connect the phone until WebOS Doctor specifically says to.<br />
<br />
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.<br />
<br />
== Step 5: There is no Step 5 == <br />
<br />
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.<br />
<br />
== Step 6: Donate to WebOS Internals and purchase the Preware Homebrew Documentation app ==<br />
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.<br />
<br />
= Caveats =<br />
<br />
== App Catalog ==<br />
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).<br />
<br />
=== Masquerading ===<br />
Palm's servers only accept certain device/OS combinations as valid. While some ROW Pre and Pre Plus devices running 2.1 are accepted (mainly O2 Germany devices), Pre and Pre Plus devices running on Verizon and AT&T (and some ROW) 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.<br />
<br />
== Carrier-Specific Applications ==<br />
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.<br ><br /><br />
<br />
:Known working Carrier Apps:<br />
<blockquote><br />
=== Sprint ===<br />
* Sprint Portal<br />
* Sprint TV<br />
* Sprint Football Live<br />
* NASCAR<br />
<br />
===Verizon Wireless ===<br />
* ''All Verizon apps should be working at this time! However, '''no one has tested the VZW Navigator subscription''' to confirm that the service carries over to a Meta-Doctored phone. You could be the first!''<br />
<br />
=== AT&T ===<br />
* No testing or reports of AT&T Carrier Apps<br />
</blockquote><br />
<br />
== Patches ==<br />
bNot 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].<br />
<br />
== Adobe Flash ==<br />
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.<br />
<br />
=== Adding Flash Support ===<br />
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.<br />
<br />
== Performance ==<br />
* '''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.<br />
* 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.<br />
<br />
=== Increase compcache size, Temporary Method ===<br />
You can use the Govnah application to increase the size of the compcache. Disable compcache, change the size, and then reenable.<br />
<br />
=== Increase compcache size, Permanent Method ===<br />
You have to edit the file /etc/event.d/compcache and substitute the 10240 value for 32768, reboot your Pre and verify it's working by using Govnah.<br />
<br />
For example, you could follow these steps:<br />
<br />
#Make sure '''novacomd''' is running on your computer.<br />
#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><br />
#Go down to line 10 type <tt>i</tt> then delete <tt>10240</tt> and replace it with <tt>32768</tt>, hit the escape key then type <tt>:wq</tt><br />
#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><br />
<br />
== Palm Profile ==<br />
* 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.<br />
<br />
* You may get lucky if your Profile has information and you managed to pass the "Logging to Profile" screen but are stuck with a message stating that the phone cannot restore your data. If you have developer mode enabled, enter your Pre and overwrite the /etc/palm-build-info file with the palm-build-info-masq file the Doctor generated. Reboot your Pre and see if it manages to boot succesfully.<br />
<br />
* If you get 9.9.9 in palm.com/palmprofile, then you can either doctor back to 1.4.5 for your carrier and log in, then delete backup info in backup app and then 2.1.0 metadoctor it, or you can restore the masqueraded /etc/palm-build-info for your device, erase your backup info in the backup app and use "Erase Apps and Data" from the reset option in the Device Info app.<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
*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.<br />
<br />
==GPS==<br />
Step-by-step approach for those experiencing problems with GPS following upgrade.<br />
# 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.<br />
# 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").<br />
# 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.<br />
# Once a fix has been established, GPS should continue to function normally thereafter.<br />
<br />
==PRL==<br />
=== Sprint ===<br />
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.<br />
<br />
:* It is possible to preserve a backup of the current PRL (as of this writing, 60676) and "push" it back onto a doctored-to-2.1.0 phone with the following procedure:<br />
::* Before doctoring to 2.1<br />
::# Update your PRL and Network settings<br />
::# Connect your phone to your computer via a USB cable<br />
::# Do the following (example was done in Terminal on OS X 10.6):<br />
<pre><br />
[dario@guarneri ~]$ novaterm<br />
root@YourPre:/# tar -czvf /media/internal/prl.tar.gz /var/lib/software<br />
root@YourPre:/# exit<br />
</pre><br />
<br />
::* After doctoring to 2.1 and all basic setup/configuration is done<br />
::# Again, connect your phone to your computer via a USB cable<br />
::# Do the following (example was done in Terminal on OS X 10.6): <br /><br />
<pre><br />
[dario@guarneri ~]$ novaterm<br />
root@YourPre:/# rootfs_open -t<br />
root@YourPre:/# cd /<br />
root@YourPre:/# tar -zxvf /media/internal/prl.tar.gz<br />
root@YourPre:/# exit<br />
</pre><br />
::* Now reboot your phone to ensure the new PRL takes effect and to "close" (make read-only) your root filesystem.<br />
<br />
=== Verizon ===<br />
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.</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Adding_flash_support&diff=13981Adding flash support2011-03-15T03:46:14Z<p>Kostka: /* Adding Flash Support */</p>
<hr />
<div>== Adobe Flash ==<br />
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.<br />
<br />
=== Adding Flash Support ===<br />
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.<br />
<br />
----<br />
<br />
==== Step 1. Prerequisites ====<br />
*Download the Verizon 2.0.1 Pre 2 Doctor ([http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar here])<br />
*Download Jason Robitaille's IPK Packager ([http://code.google.com/p/ipk-packager/downloads/list here])<br />
*Download webOS Quick Install ([http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-04-a.html here])<br />
*Download temporary directory ([http://forums.precentral.net/attachments/canuck-coding/56009d1298772359-how-get-flash-legacy-devices-2-1-0-flashplugincontainer.zip here]) and unzip the FlashPluginContainer folder to your desktop<br />
*Download patch to enable Flash preferences in the browser ([http://forums.precentral.net/attachments/canuck-coding/55913d1298547118-how-get-flash-legacy-devices-2-1-0-show-flash-prefs-legacy-devices.patch here])<br />
<br />
==== Step 2. Unpack ====<br />
*Open the 2.0.1 doctor with an archive manager, like 7zip. Navigate to "<code>resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./</code>" This is where the Flash files are stored.<br />
*Extract the following files from the webOS ROM:<br />
<br />
<blockquote>/etc/adobe/mms.cfg<br />
<br />/etc/adobe/oem.cfg<br />
<br />/usr/lib/BrowserServerPlugins/libflashplayer.so<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-scrim.png<br />
<br />/usr/lib/libFlashGraphics.so<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote><br />
<br />
==== Step 3. Drag 'N' Drop ====<br />
*Simply place the files from the ROM into the FlashPluginContainer folder in their respective locations.<br />
*Pay close attention to where each file/folder is stored inside the webOS ROM.<br />
<br />
==== Step 4. Packaging ====<br />
*Open Jason's IPK Packager and point the program to the '''files''' folder. Do NOT point to FlashPluginContainer, as the install will fail.<br />
*The rest of the fields will populate on their own.<br />
*Save the IPK file somewhere using "Create IPK Package." You may want to keep it handy.<br />
<br />
==== Step 5. Wrap Up ====<br />
*Use webOS Quick Install to install both IPK and patch.<br />
<br />
Note: The patch to enable Flash preferences is also available in Preware.<br />
<br />
==== Step 6. Edit system files ====<br />
Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)<br />
:<br />Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:<br />
<blockquote>this.controller.get("flashPref").hide();<br />
<br />this.controller.get("autoLoadPref").hide();<br /></blockquote><br />
<br />
==== Step 7. Reboot ====<br />
Reboot your devices for changes to take effect<br />
<br />
Support thread: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html<br />
<br />
----<br />
<br />
=== Adding Flash Support Manually ===<br />
# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive<br /><br />
# Copy the following files from the extracted WebOS.tar to their equivalent locations in your MetaDoctor (alternatively, you can copy them manually to a live device using Novaterm)<br />
<blockquote>/etc/adobe/mms.cfg<br />
<br />/etc/adobe/oem.cfg<br />
<br />/usr/lib/BrowserServerPlugins/libflashplayer.so<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-scrim.png<br />
<br />/usr/lib/libFlashGraphics.so<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote><br />
:3. Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)<br />
:<br />Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:<br />
<blockquote>this.controller.get("flashPref").hide();<br />
<br />this.controller.get("autoLoadPref").hide();<br /></blockquote><br />
:4. Reboot your Pre if the editing was done on a live device<br />
<br />
Flash preferences should now be visible under browser preferences.<br />
<br />
----<br />
<br />
=== Flash Troubleshooting ===<br />
After adding Flash support, you may find that visiting any page with the browser will never completely load, and then automatically refresh in a loop. Disabling and the enabling Flash content in the browser preferences will fix this issue.</div>Kostkahttp://wiki.webos-internals.org/index.php?title=Adding_flash_support&diff=13979Adding flash support2011-03-15T03:44:39Z<p>Kostka: Created page with '== 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 t…'</p>
<hr />
<div>== Adobe Flash ==<br />
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.<br />
<br />
=== Adding Flash Support ===<br />
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.<br />
<br />
----<br />
<br />
==== Step 1. Prerequisites ====<br />
*Download the Verizon 2.0.1 Pre 2 Doctor ([http://palm.cdnetworks.net/rom/pre2/p201r0d02172011/ver1z0np201rod/webosdoctorp102verizonwireless.jar here])<br />
*Download Jason Robitaille's IPK Packager ([http://code.google.com/p/ipk-packager/downloads/list here])<br />
*Download webOS Quick Install ([http://forums.precentral.net/canuck-coding/274461-webos-quick-install-v4-04-a.html here])<br />
*Download temporary directory ([http://forums.precentral.net/attachments/canuck-coding/56009d1298772359-how-get-flash-legacy-devices-2-1-0-flashplugincontainer.zip here]) and unzip the FlashPluginContainer folder to your desktop<br />
*Download patch to enable Flash preferences in the browser ([http://forums.precentral.net/attachments/canuck-coding/55913d1298547118-how-get-flash-legacy-devices-2-1-0-show-flash-prefs-legacy-devices.patch here])<br />
<br />
==== Step 2. Unpack ====<br />
*Open the 2.0.1 doctor with an archive manager, like 7zip. Navigate to "<code>resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./</code>" This is where the Flash files are stored.<br />
*Extract the following files from the webOS ROM:<br />
<br />
<blockquote>/etc/adobe/mms.cfg<br />
<br />/etc/adobe/oem.cfg<br />
<br />/usr/lib/BrowserServerPlugins/libflashplayer.so<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-scrim.png<br />
<br />/usr/lib/libFlashGraphics.so<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote><br />
<br />
==== Step 3. Drag 'N' Drop ====<br />
*Simply place the files from the ROM into the FlashPluginContainer folder in their respective locations.<br />
*Pay close attention to where each file/folder is stored inside the webOS ROM.<br />
<br />
==== Step 4. Packaging ====<br />
*Open Jason's IPK Packager and point the program to the '''files''' folder. Do NOT point to FlashPluginContainer, as the install will fail.<br />
*The rest of the fields will populate on their own.<br />
*Save the IPK file somewhere using "Create IPK Package." You may want to keep it handy.<br />
<br />
==== Step 5. Wrap Up ====<br />
*Use webOS Quick Install to install both IPK and patch.<br />
<br />
Note: The patch to enable Flash preferences is also available in Preware.<br />
<br />
==== Step 6. Edit system files ====<br />
Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)<br />
:<br />Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:<br />
<blockquote>this.controller.get("flashPref").hide();<br />
<br />this.controller.get("autoLoadPref").hide();<br /></blockquote><br />
<br />
Support thread: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html<br />
<br />
----<br />
<br />
=== Adding Flash Support Manually ===<br />
# Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive<br /><br />
# Copy the following files from the extracted WebOS.tar to their equivalent locations in your MetaDoctor (alternatively, you can copy them manually to a live device using Novaterm)<br />
<blockquote>/etc/adobe/mms.cfg<br />
<br />/etc/adobe/oem.cfg<br />
<br />/usr/lib/BrowserServerPlugins/libflashplayer.so<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/resource/plugin-scrim.png<br />
<br />/usr/lib/libFlashGraphics.so<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png<br />
<br />/usr/lib/BrowserServerPlugins/FlashMiniPlugin.so</blockquote><br />
:3. Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)<br />
:<br />Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:<br />
<blockquote>this.controller.get("flashPref").hide();<br />
<br />this.controller.get("autoLoadPref").hide();<br /></blockquote><br />
:4. Reboot your Pre if the editing was done on a live device<br />
<br />
Flash preferences should now be visible under browser preferences.<br />
<br />
----<br />
<br />
=== Flash Troubleshooting ===<br />
After adding Flash support, you may find that visiting any page with the browser will never completely load, and then automatically refresh in a loop. Disabling and the enabling Flash content in the browser preferences will fix this issue.</div>Kostka