WebOS Internals - User contributions [en]

Angstrom on Touchpad

2011-09-30T07:40:46Z

101pre: Category:HP Touchpad

Booting Angstrom on the TouchPad is actually fairly easy. Here are the steps to get it going.

== What to boot ==

For this, we will have a beagleboard of Angstrom located in an LVM on the touchpad named ext2fs. This is un-tested with an ext3 filesystem, but it will likely work. The Angstrom rootfs needs to be right in the base of the LVM, not in a sub-folder.

We are going to be creating a multi-file uImage. It will be one file with both a uImage kernel as well as an initrd.

== Gather required bits ==

First novaterm into the TouchPad and run the following commands

cd /var/home/root
tar czvf boot.tgz -C /boot/ .

Then exit out of novaterm and back on your PC run the following

mkdir -p uImage/initrd
cd uImage
novacom get file:///var/home/root/boot.tgz > boot.tgz

This will have everything you need to create the multi-file uImage using whatever kernel is currently installed on your TouchPad. I would recommend using either UberKernel or F15, something that gives console output on bootup.

== initrd ==
=== Build the initrd ===

First we need to make an empty file that will be used for our initrd. We will be starting off with an 8 MiB initrd.

dd if=/dev/zero of=ramdisk bs=1M count=8
mke2fs -Fvm0 ramdisk
mount -o loop ramdisk initrd

Now, we have an empty initrd ramdisk file and it is mounted as a loopback so that we can put things into it.

=== Fill the initrd ===

This one is pretty simple. We are going to fill the initrd with the contents of the boot.tgz EXCEPT for the kernel.

mkdir boottemp
tar xzvf boot.tgz -C boottemp
rm boottemp/uImage
mv boottemp/uImage-2.6.35-palm-tenderloin
mv boottemp/* initrd

=== Change the pivot_root ===

You need to edit the file <code>/sbin/init</code> within the initrd to alter what rootfs is loaded at bootup.

vi initrd/sbin/init

Find these lines:

lvm.static lvchange -ay --ignorelockingfailure /dev/mapper/store-root

# May need to say "don't update mtab" option below
mount -o ro /dev/mapper/store-root /realroot

... and change them to:

lvm.static lvchange -ay --ignorelockingfailure /dev/mapper/store-ext2fs

# May need to say "don't update mtab" option below
mount -o ro /dev/mapper/store-ext2fs /realroot

Now, you are done with creating the initrd. You can umount initrd now if you like, or leave it mounted if you are going to be making changes and testing them.

== Build the multi-file uImage ==

You will need the package uboot-mkimage (at least on Ubuntu) installed to do this.

== Cheater script ==

I have worked up a script that runs the needed commands for you.

#!/bin/bash
rm uMulti uRamdisk
mkimage -A arm -O linux -T ramdisk -C none -d ramdisk uRamdisk
mkimage -a 0 -e 0 -A arm -O linux -T multi -C none -d uImage-2.6.35-palm-tenderloin:uRamdisk uMulti

Just name the file something like <code>spin-kernel.sh</code> and give it execute permission. It should be inside of the uImage folder we made earlier, then give it a run.

== Update Angstrom ==

You will need to chroot into the angstrom rootfs on the TouchPad over a novaterm session and install lvm with the command:

opkg install lvm2

Also, one thing that I have found is that the checkroot script was not running early enough so it was halting the boot due to the rootfs still being read-only. To fix this go to /etc/rcS.d within your angstrom rootfs. Find the symlink that points to <code>../init.d/checkroot</code> and rename it to <code>S01checkroot</code>.

== Boot Angstrom ==

To do this, just put the TouchPad into recovery mode and memboot the multi-file uImage we made earlier. Because we are membooting it, if something goes wrong and if the TouchPad doesn't boot properly, you can force a reboot by holding Home+Power for 10 seconds, and it will safely reboot into webOS.

[[Category:HP Touchpad]]

Android under webOS on Touchpad

2011-09-30T07:40:09Z

101pre: Category:HP Touchpad

== Project goal ==

To implement Android (probably CyanogenMod 7) on the TouchPad as a card using a <code>chroot</code> execution environment. Perhaps eventually putting each Android app as a card.
: This will allow the use of Android apps (hopefully, including market) while not having to leave webOS or reflash the TouchPad.
: However, it will probably not have 3D support, so people whining for "romz" will probably not be fully satisfied. ;)

== Required pieces ==

* The kernel may need to have Android bits compiled in. This could be added to the standard UberKernel without impacting regular operation.
* The Android graphics and devices need to be rerouted to use SDL and other PDK-supported APIs.

==References==
*[http://bitbucket.spencerelliott.ca/palmdroid/wiki/Home Palmdroid project!] The end goal for this project it to be able to run Android applications within webOS using the Dalvik virtual machine.
***[http://forum.xda-developers.com/showthread.php?p=17558046#post17558046 (ANDROID) Official Palmdroid Development Thread]

[[Category:HP Touchpad]]

Tutorials webOS Activating Touchpad Demo Unit

2011-09-30T07:39:40Z

101pre: Category:HP Touchpad

When the TouchPad went on clearance, many stores were sold out immediately after opening. In many cases, the demo unit was sold as is. The demo unit is a fully functional unit, but it has a modified version of WebOS on it. In order to restore it to a standard model, you must go through this process:

== Permanent solution ==
The best thing to do is change your demo unit <code>PN</code> and <code>ProductSKU</code> tokens to match with a 32 GiB TouchPad's (I believe that most demo units are 32 GiB. If yours is 16 GiB, make the tokens match another 16 GiB TouchPad's).

On a demo unit, the tokens are:
<pre>
<Val name="PN" value="180-10928-00"/>
<Val name="ProductSKU" value="FB359UA#ABA"/>
</pre>

On a normal unit, they are:
<pre>
<Val name="PN" value="180-10871-00"/>
<Val name="ProductSKU" value="FB464UA#ABA"/>
</pre>

For now, you can make a WebOS doctor using meta doctor to change the <code>topaz.xml</code> file. There are instructions here on how to do this: [http://www.webos-internals.org/wiki/Sprint_Pre_Plus#Step_2:_Setup_meta-doctor]. Alternatively, the file will be called <code>topaz.xml</code>, not <code>castle.xml</code>.

This will allow you to create a WebOS doctor that will forcibly overwrite your tokens for you.

== Temporary workaround ==
This section is not an actual fix. It is a temporary workaround that will soon be obsolete.

=== Restoring HP WebOS ===
First, restore the default firmware with WebOS doctor: [http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar http://palm.cdnetworks.net/rom/touchpad/p302r0d08012011/wifip302rod/webosdoctorp302hstnhwifi.jar].

You must put the TouchPad into recovery mode by powering it off and pressing the power button and the volume up button at the same time. You will see a large USB logo to confirm that this is successful.

Run the Doctor, and connect the TouchPad via USB.

The update process takes several minutes. This will put the full version of webOS on your TouchPad, but you will find that you cannot get past the first run page.

=== Bypassing activation ===
Download this zip file and extract the contents to the desktop: [http://onebluepoint.net/chekz-devicetool.zip http://onebluepoint.net/chekz-devicetool.zip].

Open a command line (Start > Run > cmd) or terminal window, and run these commands in order:
# <code>cd \Desktop</code>
# <code>java -jar devicetools.jar</code>

Allow the program to run for several minutes. Your tablet will reboot a few times in the process. The program will tell you when the device is ready. Once it boots, you'll be able to use WebOS freely, although you still will not have an account.

=== Load Impostah ===
Now that you're up and running, all you need is a WebOS account. Download Preware from this page: [http://en.m.webos-internals.org/wiki?search=preware http://en.m.webos-internals.org/wiki?search=preware].

Once this program is loaded, simply type "Impostah" into the bar, and click install.

You will see the app under the downloads tab on your TouchPad when it is ready. Run it.

=== Creating your WebOS account ===
Once Impostah is open, we need to delete the dummy account that the activation bypass program created in order to add our own.
# Click Palm Profile, and reset it. Confirm that you want to do this. This will reboot your tablet.
# Once rebooted, you will be at the same activation screen that we had to bypass earlier.
# Go to create your account again. This time, instead of saying you cannot create it, the loading tab should spin forever. After a few minutes, you will want to force your tablet to restart by holding the home button and the power button. Check your email to make sure that you got a welcome message from HP. Once you do, you can either login again or bypass the activation.

=== Updating HP App Catalog ===
One more step before you're up and running!

It seems that the version of HP App Catalog included is out of date and only shows a blank page. However, you can use the menu to get into software manager and update it.

Congratulations, you just beat the madness by buying the demo unit that no one wanted. ;) Special thanks to Jack87, djhomeboy, and rwhitby for helping make this happen!

[[Category:HP Touchpad]]

Changing keyboard layout on Touchpad

2011-09-30T07:38:45Z

101pre: Category:HP Touchpad

Virtual keyboard layouts on the TouchPad are hardcoded into the LunaSysMgr binary. Therefore, editing the keyboard layouts requires a ''binary patch'' to the LunaSysMgr executable. HP/Palm has not released the source for LunaSysMgr.

This article describes how to perform that patch. Some patches for dvorak and other layouts can be found on this [http://forums.precentral.net/hp-touchpad-homebrew/297295-keyboard-layouts-patches.html PreCentral thread]
== Built-in layouts ==

Generally, there are three keyboard layouts: QWERTY, QWERTZ and AZERTY.
On the selected keys of these layouts, extended characters can be accessed with a long tap on some keys. The long tap causes a lookup of the extended character set defined for that key, and those optional characters are displayed to be selected from. For example, the "a" key may have extended characters of á or à or â or ã.

== I. Keyboard layouts ==

Each keyboard layout consists of a main layout and 3 interchangeable bottom rows on the keyboard for different applications.

The main keyboard layout describes 5 rows of 12 keys each.

The 3 bottom rows are 12 keys each.

In total, there are 8 rows of 12 keys each.

Each key is described by 4 double words (4 bytes).

# Button type (big endian)
#: 2 last bytes are used
#: Mostly they are set of flags but there is too few info to decode all of them.
## The least one is button type
### BF - no button. i.e. there is button and if you press it it will type but it is invisible (try typing to the right of 0 or to the left of 1 to check what is being typed in normal keyboard)
### 3F - normal button
### 40 - long button (like spacebar)
## The second is length class:
### 40 - short one (mostly spacers)
### 80 - normal width
### C0 - long one (Shift etc.)
### A0 - very long one (space bar)
#: Normal button will look like 0x0000803F
# UTF-16LE code of main symbol followed bt 2 byte code of source (0x0000 if normal symbol, 0x0001 if special like shift enter etc, 0x2001 if text from static variable)
# UTF-16LE code of secondary symbol followed bt 2 byte code of source (0x0000 if normal symbol, 0x0001 if special like shift enter etc, 0x2001 if text from static variable)
# Extended characters set address (little endian)

About symbols (2,3)
If the greatest byte (the most right one in LE) is 01, then it is not symbol but the text from some static variable defined in the file (like smiles, .com, etc.) or special button like shift, enter, etc.
If main symbol is considered regional by system (it is hardcoded somewhere in LunaSysMgr), then the behaviour is as follows:
* When shift is pressed, the big letter is produced.
* Without shift, small letter is produced.
* With caps on, big letter is produced.
* When switched to secondary keys ([]-/ button), secondary symbol is
*: produced always.
* Button is white
If main symbol is not considered regional (unfortunately, Russian letters are not considered regional),
* When shift is pressed, secondary symbol is produced.
* Without shift small (if applicable), main symbol is produced.
* With caps on big (if applicable), main symbol is produced.
* When switched to secondary keys ([]-/ button) behaviour of
*: previous statements is not changed. And look of keys too.
* Button is light grey.

To make non-regional keys act like regional ones, the only workaround is to duplicate them as main and secondary symbols.

Alternative way is to modify some code elements of LunaSysMgr to make it think that characters are regional.
This process was researched by '''Isaac Garzón (isagar2004)''' and automated in the script described in [[#III._Patching_script]]

It is easy to say that any zero key is just skipped during keyboard generation process, so in reality, there can be less then 12 buttons in a row.

Extended characters set address is internal pointer not and offset, so it is quite a work to find which one corresponds to which character set.

== II. Extended characters sets ==

There are 65 extended character sets.

Namely:

* 17 for letters (E R T Y U I O P A S D G L Z C N M). They are general for all 3 keyboard layouts.
* 3*10 for numbers (1 2 3 4 5 6 7 8 9 0). For each layout there are different sets for each number
* 5+5+6 for punctuations and .com. There are 4 for QWERTY and QWERTZ and 5 for AZERTY. And for each layout, there is special set for .com.
* Also there is a set for http:// and for choosing keyboard size. They are general for all 3 layouts.

Each set is a sequence of double words with utf-codes of letters (or links to static text) ending with zero dword.

For example, for the A-letter set, it is:
41000000 c0000000 c1000000 c2000000 c3000000 c4000000 c5000000 e6000000 aa000000 00000000

== III. Patching script ==

Just finished patching script that is run on a TouchPad, generates needed layout from JSON file and then patches LunaSysMgr on the fly.

It is really easy to use. The only thing you should do is to enable developer mode and have novaterm to be able to access console (Of course, you can use ssh if you've installed openssh or dropbear from preware feeds).

=== Disclaimer ===

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Use it at your own risk.

It is a shell script which besides internal instructions uses the following commands:

* echo (For feedback and pipelined passing of variables)
* sha1sum (for determining version)
* mv, cp, rm (mostly operations with tempfiles as I found that file operations are faster then string variables)
* hexdump (reading hexcodes)
* dd (patching main file)
* sed (parsing JSON)
* diff, ls, awk (Checking differences while self test and checking size during patching process)
* date (for selftest and timing only)
* sleep (for pausing after mount and luna stop as some people complained on errors sometimes)
* initctl (to start stop luna during replacing)
* mount (to remount / as rw and ro)

As all these commands are part of core *nix functions, they are present in TouchPad, and so no need to install any other software.

=== Script description ===

Script consists of several files

* patch.sh - main file that governs the process
* funcs.sh - repositary of functions that are used during patching process
* map.sh - Variables for mapping human readable variables to machine codes where they are necessary (like width and class of buttons)
* vars - Variables that are subject to change. Naming
** VERSIONS - Set of versions that are used during version check
** FILEPATH - Path to LunaSysMgr. Usually /usr/bin/LunaSysMgr but can be changed to run not on TouchPad but linux machine or other.
** SHA1SUMPARAMS - Parameters for sha1sum command, as I found out that they differ on TouchPad and my debian-based OS (-cs for TouchPad and --check --status for debian)
* <version>.offsets.sh files - They contains offset and sha1sum information about versions of LunaSysMgr. DO NOT EDIT THESE FILES UNLESS YOU ARE ABSOLUTELY SURE OF WHAT YOU ARE DOING.
* (optionally). rus.json - Containes example of layout file. It describes my original Cyrillic Russian layout replacement for AZERTY. DO NOT USE THIS FILE AS STARTING POINT. Only as example.

=== Definitions ===

* Main file - File that is stated as FILEPATH in "vars" file
* Backup file - File with path "FILEPATH.orig"
* Original file - Main or backup file, which have detected version. If both versions are detected Main file will be used.
IF MAIN AND BACKUP FILES HAVE DIFFERENT BUT DETECTABLE VERSIONS (For ex. after OTA) THEN BACKUP FILE WILL BE REPLACED DURING PATCHING PROCESS WITH NEW ONE.

=== Script Usage ===

There are few actions that you can do with this script.

* sh patch.sh --help
*: Display information on developer and short info of usage.
* sh patch.sh version
*: Just checks the version of main and backup and shows message wheather pathcing or generation processes are available
* sh patch.sh generate
*: If detectable version is found, generates (or forcibly regenerates) <version>.data and <version>.template.json files using original file.
*: The first one is used afterwords for patching and mostly saved to save time in future. But it safely can be deleted after each execution. Script will regenerate it whenever needed.
*: The second contains full JSON info about layouts in original file
* sh patch.sh check
*: Performs a self test of script. Operations done are as follows:
** Checks versions of main and backup files
** Generates <version>.data file if not present. If present then just read info from it
** Generates <version>.template.json if not present.
** Reads and parses <version>.template.json.
** Copies original file to temp location and patches it
** Compares patched and original file and echoes the result
** Deletes patched file
*: If self test is failed it is strongly recommended NOT to use this script and contact developer.
*: WARNING: Parsing JSON process can take 5-8 minutes for full template. Be patient.
* sh patch.sh check <layout file>
*: Almost the same as self test but uses given template and does not delete patched file but echoes it's name (<version>.patched)
*: Also if REGIONPATCH parameter is supplied in JSON file, patches code sections. ONLY AVAILABLE FOR 3.0.2 VERSIONS OF DEVICE AND EMULATOR.
*: WARNING: Parsing JSON process can take 5-8 minutes for full template. Be patient.
* sh patch.sh patch <layout file>
*: Main patching procedure. After making patched file it backs up main file (if needed) and replaces main file with patched one.
*: Also if LANGCODE parameters is supplied, adds lines of format
<syntaxhighlight lang="javascript">
{"languageName":"KeyBoardPatch_<langcode>","languageCode":"<langcode>","countries":[]},
</syntaxhighlight>
*: to /usr/lib/luna/customization/locale.txt (or /etc/palm/locale.txt if missing). ONLY AVAILABLE FOR 3.0.2 VERSIONS OF DEVICE AND EMULATOR.
*: Prior to adding langcodes it deletes old ones(from previous patchings).
*: If any of specified langcodes are found in locale.txt then script just ignores them with the message.
*: WARNING: Parsing JSON process can take 5-8 minutes for full template. Be patient.
*: WARNING: Replacement of main file is followed with Luna restart, do not leave any unsaved data open and don't be afraid.
*: WARNING: If LANGCODE is supplied full devise restart is required for changes to take effect.
* sh patch.sh revert
*: Restores backed up file if it has detectable version.
*: Also removes any KeyBoardPatch_ langcodes from /usr/lib/luna/customization/locale.txt (or /etc/palm/locale.txt if missing)

WARNING: During process the following files could be created in script folder
* tmp, tmp0
*: Temp files that are used by script during template generation and parsing processes. Should be auto deleted after execution. But if interrupted feel free to delete them yourselves (If they interfere with your means)
* <version>.data
*: File that contains important variables of layouts: offsets, button counts, virtual addresses and so on. They are needed during almost any processing of the script. If deleted file will be regenerated. It is strongly advised not to delete the file, because it speeds up the process.
* <version>.template.json
*: JSON file containing layout info for user

=== JSON layout file structure and editing hints ===

Layout file have standard [http://en.wikipedia.org/wiki/JSON JSON] structure

Here is short example of it:

<syntaxhighlight lang="javascript">
{
"layouts": {
"QWERTY": {
"0": {
"0": {
"WIDTH": "none",
"CLASS": "invisible",
"MAIN": {"TYPE": "C", "CHAR": "Q"},
"SEC": {"TYPE": "C", "CHAR": "["},
"EXT": ""
},
"1": {
"WIDTH": "normal",
"CLASS": "normal",
"MAIN": {"TYPE": "C", "CHAR": "1"},
"SEC": {"TYPE": "C", "CHAR": "!"},
"EXT": "SET0"
}
}
}
},
"sets": {
"SET0": {
"0": {"TYPE": "C", "CHAR": "1"},
"1": {"TYPE": "C", "CHAR": "!"},
"2": {"TYPE": "C", "CHAR": "¹"},
"3": {"TYPE": "C", "CHAR": "¼"},
"4": {"TYPE": "C", "CHAR": "½"},
"5": {"TYPE": "C", "CHAR": "¡"}
}
},
"params": {
"REGIONPATCH": "0",
"LANGCODE": {
"0": ""
}
},
}
</syntaxhighlight>

The file consists of 3 main objects: layouts, sets and params.

# layouts
#: Layouts describes 3 main layouts
## QWERTY
## QWERTZ
## AZERTY
#: Each layout consists of maximum 8 rows (0 - 7): 0 - numbers row, 1-3 - letter rows, 4 - Bottom row, 5 - bottom row by default, 6 - bottom row for url, 7 - bottom row for email
#: Each row consists of maximum 12 buttons (0 - 11)
#: Each button is described by sevral parameters
## WIDTH
##: Evidently width of the button. It can be of 5 values
### "none" - No special width set. Autosized by system
### "short" - Short button. Shorter then normal sized approximately by half
### "normal" - Standard-sized button
### "long" - Long button like shift and enter in original layouts.
### "spacebar" - Very long button. Used only for spacebar and language/special char changer. Also used in conjuction with CLASS="spacebar"
## CLASS
##: Class or type of the button. It can be
### "none" - no class. "If there is no class, then there is no button" ( Almost citation :-) )
### "normal" - standard button class
### "invisible" - Self-explaining. There is button but we cannot see it. Mostly used for indents. The can have characters assigned and even will type them(look to the left and right of number row in QWERTY, try to type them)
### "spacebar" - Used for spacebar. (Suppose that width is not just stored in 1 byte and spreads to half of class byte too)
## EXT
##: This is the name of set of extended characters, which are accessed by long press. If there is no extended characters on a button empty string ("") is used
## MAIN and SEC
##: Main and secondary character respectively. They have two parameters each
### TYPE
###: Type of character
#### "C" - normal Сharacter
#### "S" - Special character (like shift, enter, backspace etc.)
#### "V" - character from static Variable. (Smiles, .com, http:// etc.)
### CHAR
###: The character itself.
###: If type is "C" then it is just normal UTF-8 character
###: If type is "S" or "V" it's value is some hex numeric constant.
# sets
#: Sets are sets of extended characters that are accessed by long tap on a button.
#: There are 65 sets (0-64) and each set is named SET#.
#: Each set consists of several characters (0,1,...)
#: Each character is described by TYPE and CHAR which are absolutely the same as in layout description.
# params
#: Params contains special parameters for patching process. It is optional and should be used with CAUTION.
#: Right now it supports only 2 options
## REGIONPATCH
##: It is an option that enables patching regional status of keys made by '''Isaac Garzón (isagar2004)'''.
##: By default it is off. Enabling it. i.e. setting value to "1" mades some changes in ASM code of LunaSysMgr and alters its behaviour, assigning key backgrounds and look
## LANGCODE
##: This option is made only for aesthetic reason. It adds two-character abbreviation to /usr/lib/luna/customization/locale.txt (or /etc/palm/locale.txt if missing) with name KeyBoardPatch_<langcode> so you can assign it in language select to chosen keyboard. There can be any number of additional Langcodes/ Just specify them like
<syntaxhighlight lang="javascript">
"0": "ru",
"1": "ua"
</syntaxhighlight>
::::etc...
:::: WARNING: Full device reboot is required for these changes to be effective.
:::: WARNING: DO NOT USE THIS OPTION WITH ANY LOCALIZATION PACKAGE.

As you can see in stated example, there are 2 first buttons (0,1), in number row (0), in QWERTY layout.
The first one is invisible button with characters ''Q'' and ''/'', and the second is the normal button with ''1'' and ''!'', and SET0 binded to it.

Also, we can see that SET0 consists of 6 buttons (0-5) which are: 1, !, ¹, ¼, ½, ¡

WARNING: Symbols ''\'' and ''"'' should be escaped in JSON format, so to use them type "\\" and "\"" respectively

NOTICE: If object or parameter of an object have not been changed from original template, you can delete it from template to speed further parsing process, but do it ONLY IF YOU REALLY KNOW how JSON is structured and know that you won't ruin it's structure.

In keyboard layout, you can easily change button type flags, primary and secondaty symbol.

Extended characters set can be changed too.

Characters in extended characters sets can be changed.

You can choose which set should be assigned to which button by changing EXT in layout.

WARNING: Do not change names of sets, or they won't be read.

WARNING: It is not possible to increase number of rows, buttons or characters in set, as we cannot increase size of data in binary file, so any extra character, rows, buttons, even layouts and sets will be ignored during patching.

NOTICE: Though you surely can decrease these numbers (well, not rows, I suppose) by filling unneeded buttons and extended symbols with zeros. i.e.

For removing button, it's WIDTH and CLASS should be "none", MAIN and SEC TYPE should be "C", CHAR should be empty string (""), and EXT should be empty too.

For removing extended character from set, just set TYPE to "C" and CHAR to empty string.

To remove SET, well actually not remove but do not use, remove reference to it from EXT parameter in layout.

=== Patching process ===

Patching process looks pretty easy.

First of all, download the archive with script, and extract it. [http://dl.dropbox.com/u/34455792/keypatch.zip keypatch.zip]

You will get folder "keypatch".

Copy this folder on your device.

Now, connect to your device via novaterm or ssh, and enter the directory.

Run template generation script

#sh patch.sh generate
Checking main file...
Main version not detected
Checking backup file...
Backup file 3.0.2 device version found
Backup file will be used
Reading data from file /usr/bin/LunaSysMgr.orig
Storing data into 302.data
Generating template
Writing template to file 302.template.json
Ok.

Now, copy this template to the computer and open it with editor that affords editing UTF-8 files with no BOM ([http://en.wikipedia.org/wiki/Byte_order_mark Byte Order Mark]) and Unix style endings. For example Notepad++ (on Windows) or vim (on *nix)
Editing instructions in previous subsection [[#JSON layout file structure and editing hints]]

After editing, copy newly created file in the same folder and run patch or check options
(you can use "check" instead of "patch" if you want to check patched file first or replace original file manually yourself)

sh patch.sh patch <new layout file>
Main version not detected
Checking backup file...
Backup file 3.0.2 device version found
Backup file will be used
Found file data 302.data
Reading template <new layout file> and redefining variables
Copying source file to temp location
Applying patch to tempfile
Patched file 302.patched generated
Installation started
Remounting / as rw
Original file aleready backed up in /usr/bin/LunaSysMgr.orig
Stopping Luna
Coping file 302.patched to /usr/bin/LunaSysMgr
Starting Luna
Remounting / back as ro
Removing temp file 302.patched
Ok.

or

sh patch.sh check <new layout file>
Checking main file...
Main version not detected
Checking backup file...
Backup file 3.0.2 device version found
Backup file will be used
Found file data 302.data
Mon Aug 29 15:08:50 MSD 2011
Reading template <new layout file> and redefining variables
Mon Aug 29 15:09:07 MSD 2011
Copying source file to temp location
Applying patch to tempfile
Patched file 302.patched generated
Mon Aug 29 15:09:15 MSD 2011
Ok.

== IV. Changing layout manually ==

In keyboard layout, you can easily change button type flags, primary and secondary symbol.

Extended characters set address can be changed too, but you should deduce it by initial values of layouts. It is not very hard but requires time.

Characters in extended characters sets can be changed too. Although you cannot change the number of characters in a particular set, you can choose the one with needed number of symbols and reassign it to needed button by changing address in the layout.

After you are satisfied with the result, you need to replace LunaSysMgr in the device with newly edited file. For this purpose, you need to have shell access to it. You can use either ssh server from preware packages or novaterm to do it. You cannot use on-device terminal as you would need to stop luna in process.

First, you need to copy file on the device using USB drive mode (or you can scp it). Let the new file be /media/internal/LunaSysMgr.

After that, do the following commands:

remount / for write access

#mount -o r,w remount /

backup original file

#cp -dpR /usr/bin/LunaSysMgr /usr/bin/LunaSysMgr.orig

stop the luna

#initctl stop LunaSysMgr

copy new file

#cp /media/internal/LunaSysMgr /usr/bin/LunaSysMgr

start luna back

#initctl start LunaSysMgr

remount / back as read only

#mount -o r,o remount /

And enjoy your new keyboard.

== V. Offsets ==

{| class="wikitable"
|- style="vertical-align:top;"
! 3.0.0 emul!!3.0.0 device!!3.0.2 device!!keyboard/letter
|-
| 0x003EE840||0x003BEE80||0x003CACB0||QWERTY Main layout
|-
| 0x003EEC00||0x003BF240||0x003CB070||QWERTY Default bottom row
|-
| 0x003EECC0||0x003BF300||0x003CB130||QWERTY URL bottom row
|-
| 0x003EED80||0x003BF3C0||0x003CB1F0||QWERTY Email bottom row
|-
|
|-
| 0x003EEE40||0x003BF480||0x003CB2B0||QWERTZ Main layout
|-
| 0x003EF200||0x003BF840||0x003CB670||QWERTZ Default bottom row
|-
| 0x003EF2C0||0x003BF900||0x003CB730||QWERTZ URL bottom row
|-
| 0x003EF380||0x003BF9C0||0x003CB7F0||QWERTZ Email bottom row
|-
|
|-
| 0x003EF440||0x003BFA80||0x003CB8B0||AZERTY Main layout
|-
| 0x003EF800||0x003BFE40||0x003CBC70||AZERTY Default bottom row
|-
| 0x003EF8C0||0x003BFF00||0x003CBD30||AZERTY URL bottom row
|-
| 0x003EF980||0x003BFFC0||0x003CBDF0||AZERTY Email bottom row
|}

Extended character offsets are too numerous to list them all.
I will just name offsets for the first one and the order of sets. As each set is ended with 0x00000000, it will be quite easy to distinguish them.

The order is the following:

{| class="wikitable"
|- style="vertical-align:top;"
! 3.0.0 emul!!3.0.0 device!!3.0.2 device!!letter to which character set is bind
|-
| 0x003C33DC||0x00388BB4||0x00393608||QWERTY 1
|-
||||||| QWERTY 2
|-
||||||| QWERTY 3
|-
||||||| QWERTY 4
|-
||||||| QWERTY 5
|-
||||||| QWERTY 6
|-
||||||| QWERTY 7
|-
||||||| QWERTY 8
|-
||||||| QWERTY 9
|-
||||||| QWERTY 0
|-
|
|-
||||||| E
|-
||||||| R
|-
||||||| T
|-
||||||| Y
|-
||||||| U
|-
||||||| I
|-
||||||| O
|-
||||||| P
|-
||||||| A
|-
||||||| S
|-
||||||| D
|-
||||||| G
|-
||||||| L
|-
||||||| Z
|-
||||||| C
|-
||||||| N
|-
||||||| M
|-
|
|-
||||||| QWERTY ,/
|-
||||||| QWERTY .?
|-
||||||| QWERTY '"
|-
||||||| QWERTY -_
|-
|
|-
||||||| Hide keyboard(size of it)
|-
|
|-
||||||| URL key /
|-
|
|-
||||||| QWERTY .com
|-
|
|-
||||||| QWERTZ 1
|-
||||||| QWERTZ 2
|-
||||||| QWERTZ 3
|-
||||||| QWERTZ 4
|-
||||||| QWERTZ 5
|-
||||||| QWERTZ 6
|-
||||||| QWERTZ 7
|-
||||||| QWERTZ 8
|-
||||||| QWERTZ 9
|-
||||||| QWERTZ 0
|-
|
|-
||||||| QWERTZ ,;
|-
||||||| QWERTZ .:
|-
||||||| QWERTZ #?
|-
||||||| QWERTZ -'
|-
||||||| QWERTZ .com
|-
|
|-
||||||| AZERTY 1
|-
||||||| AZERTY 2
|-
||||||| AZERTY 3
|-
||||||| AZERTY 4
|-
||||||| AZERTY 5
|-
||||||| AZERTY 6
|-
||||||| AZERTY 7
|-
||||||| AZERTY 8
|-
||||||| AZERTY 9
|-
||||||| AZERTY 0
|-
|
|-
||||||| AZERTY ,?
|-
||||||| AZERTY .;
|-
||||||| AZERTY :/
|-
||||||| AZERTY @_
|-
||||||| AZERTY !*
|-
||||||| AZERTY .com
|}

[[Category:HP Touchpad]]

Touchpad Bluetooth Keyboard

2011-09-30T07:38:16Z

101pre: Category:HP Touchpad

== HP Touchpad Bluetooth Keyboard ==
=== Keycode/Scancode for Media/Specialty Keys ===
Hopefully this information will make it easier to implement support for the HP Touchpad Bluetooth Keyboard on other devices such as a Pre2 or Veer.

{| class="wikitable"
|-
! Key
! Keycode
! Scancode (Decimal)
! Scancode (Hex)
|-
| Notifications
| 1
|
|
|-
| Search
| 217
| 786977
| 0xC0221
|-
| Keyboard
| 204
|
|
|-
| Brightness Down
| 224
|
|
|-
| Brightness Up
| 225
|
|
|-
| Rewind
| 168
| 786612
| 0xC00B4
|-
| Play/Pause
| 164
| 786637
| 0xC00CD
|-
| Forward
| 208
| 786611
| 0xC00B3
|-
| Mute
| 113
| 786658
| 0xC00E2
|-
| Volume Down
| 114
| 786666
| 0xC00EA
|-
| Volume Up
| 115
| 786665
| 0xC00E9
|-
| Power
| 142
| 65666
| 0x10082
|}

Using various tools under Ubuntu 11.04, I haven't been able to get info for Keyboard, Brightness Down, and Brightness Up. These keys may need a Touchpad device to get the information for, as the keys are known working there.
--[[User:SineOtter|SineOtter]] 07:34, 9 September 2011 (UTC)

=== Keyboard layouts ===

The keymaps are located in the /usr/share/qt4/keymaps directory. There are 3 of them: keymap-us.qmap, keymap-de.qmap, keymap-fr.qmap. The keymap is loaded after the keyboard was successfully paired with the touchpad.

kmap2qmap is a tool to generate keymaps in qmap format (http://doc.qt.nokia.com/latest/qt-embedded-kmap2qmap.html). Original kmap2qmap source file was downloaded from http://svn.netlabs.org/repos/qt4/trunk/tools/kmap2qmap/main.cpp, then some changes from http://palm.cdnetworks.net/opensource/3.0.2/qt4-4.7.1-patches.gz were applied.
Download the patched kmap2qmap.cpp[http://users.openinkpot.org/~lunohod/kmap2qmap.cpp] and compile it:

'''gcc -o kmap2qmap kmap2qmap.cpp -I/usr/include/qt4 -I/usr/include/qt4/QtCore -lQtCore'''

Now grab the kmap[http://users.openinkpot.org/~lunohod/us.kmap] file, modify it if you want and generate the qmap file with:

'''./kmap2qmap us.kmap keymap-us.qmap'''

The us.kmap file was generated with ckbcomp (it's in the console-setup package in Debian) and then the touchpad related keys were added:

'''ckbcomp -keycodes evdev -layout us -compact > us.kmap'''

There is also a modified kmap file[http://users.openinkpot.org/~lunohod/us_modified.kmap] with CapsLock changed to Control key, added AltGr and germanic umlauts mapped to AltGr+[aous]. You can take this kmap as a reference or just diff it with the us.kmap to see what should be changed.

It is possible to create new layouts (with dvorak, colemak, cyrillic or whatever you want), but there is still no way to switch layouts on the fly.

[[Category:HP Touchpad]]

Touchpad Touch-down

2011-09-30T07:37:49Z

101pre: Category:HP Touchpad

[[Portal:Where_to_Get_Started |Where to get started]]

[[Category:HP Touchpad]]

Touchpad Teardown

2011-09-30T07:36:46Z

101pre: Category:HP Touchpad

<html><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="480" height="296" id="utv889877" name="utv_n_881019"><param name="flashvars" value="loc=%2F&autoplay=false&vid=17096227&locale=en_US&hasticket=false&v3=1" /><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="src" value="http://www.ustream.tv/flash/viewer.swf" /><embed flashvars="loc=%2F&autoplay=false&vid=17096227&locale=en_US&hasticket=false&v3=1" width="480" height="296" allowfullscreen="true" allowscriptaccess="always" id="utv889877" name="utv_n_881019" src="http://www.ustream.tv/flash/viewer.swf" type="application/x-shockwave-flash" /></object>
</html>

== References ==
* [http://www.ustream.tv/recorded/17096227 http://www.ustream.tv/recorded/17096227]
* [http://www.ifixit.com/Device/HP_TouchPad HP TouchPad Repair Manual], 15 Step-by-step Guides, iFixit

[[Category:HP Touchpad]]

Category:HP Touchpad

2011-09-30T07:35:50Z

101pre: HP Touchpad

HP Touchpad

Android under webOS on Touchpad

2011-09-30T07:32:47Z

101pre:

Touchpad Teardown

2011-09-30T07:29:49Z

101pre:

Touchpad Touch-down

2011-09-30T07:28:36Z

101pre:

[[Portal:Where_to_Get_Started |Where to get started]]

Python

2011-09-30T07:23:34Z

101pre: python etc

==Python on the webOS==
Various options:

* [http://code.google.com/p/python-for-webos/ python-for-webos], Python for HP-Palm webOS devices. A Python VM/Interpreter in order to allow Python code to run inside a Palm Pre / Pixi

* [http://sourceforge.net/projects/webos-python/ Unofficial Python on webOS], and related packages for Palm webOS. Built using the WebOS Internals PDK. (Pygame & Python 2.5)
** [http://thp.io/2011/webos/ webOS hacks], Python on webOS and the python-webos module (thp.io)

* [https://github.com/thp/python-webos Python module "webos" wrapping the PDL functionality.] from [https://developer.palm.com/content/api/reference/pdk/plug-in-api-summary.html hp]

==Tools in Python==

*[https://github.com/grundprinzip/PyPalm PyPalm] a tool that should help to work with the Palm webOS SDK from the command line.

DebianChroot

2011-09-29T07:10:34Z

101pre: /* How to remove the ext3fs partition */

Debian 6.0.2 Chroot has been compiled to work with armv6 and armv7 processors, unlike the Ubuntu Chroot that only works with armv7. This means that you can now have a functional linux chroot on your pixi as well.

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instruction how to create partition is available here [[Chrooting]]). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

* Using Preware, install Xecutah and Debian 6.0.2 Chroot.

* Hit the relevant buttons on Xecutah to run the XServer and the Debian 6.0.2 Chroot.

* Run XServer first, which will open an Xserver window, then return to Xecutah and tap Debian 6.0.2 Chroot. When you return to the Xserver card, you should see a command prompt.

* Use "apt-get install" to install whatever apps you like from Debian. Then run in the Debian chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=debian.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 debian.img 1048576

mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/debian.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/debian.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Debian 6.0.2 Chroot from Preware and it will populate the image file.

== How to remove the ext3fs partition ==

*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]

DebianChroot

2011-09-29T07:09:52Z

101pre:

Debian 6.0.2 Chroot has been compiled to work with armv6 and armv7 processors, unlike the Ubuntu Chroot that only works with armv7. This means that you can now have a functional linux chroot on your pixi as well.

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instruction how to create partition is available here [[Chrooting]]). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

* Using Preware, install Xecutah and Debian 6.0.2 Chroot.

* Hit the relevant buttons on Xecutah to run the XServer and the Debian 6.0.2 Chroot.

* Run XServer first, which will open an Xserver window, then return to Xecutah and tap Debian 6.0.2 Chroot. When you return to the Xserver card, you should see a command prompt.

* Use "apt-get install" to install whatever apps you like from Debian. Then run in the Debian chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=debian.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 debian.img 1048576

mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/debian.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/debian.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Debian 6.0.2 Chroot from Preware and it will populate the image file.

== How to remove the ext3fs partition ==

[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition]]

UbuntuChroot

2011-09-29T07:07:43Z

101pre: one step less renumber the rest

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

* Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

* Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

* Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

* Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=ubuntu.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 ubuntu.img 1048576

rootfs_open -t
mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/ubuntu.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/ubuntu.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

== Instructions ==

===Intro: What you need to know===
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.

* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''

===Step 1: Creating a WebOS Doctor===
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)
**[[Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor Step 1: |Application:MetaDoctor - Setting up Meta-Doctor Step 1:]]
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says "# EXT3FS_PARTITION_SIZE = 2GB". Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. '''BUT BE AWARE THAT THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU.''' Now save the file still with no file extension.
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.

===Alternative Step 1: Re-partitioning by hand===
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.

# connect with novaterm
# get rid of cryptofs process <code>pkill -SIGUSR1 cryptofs</code>
# <code>umount /media/internal</code>
# <code>resizefat /dev/mapper/store-media 4G</code> - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation should not delete your data.
# <code>lvresize -L 4G /dev/mapper/store-media</code>
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises <code>pkill -SIGUSR2 cryptofs</code> here.
# <code> lvcreate -l 100%FREE -n ext3fs store </code>
# <code>mkfs.ext3 /dev/mapper/store-ext3fs</code>
# <code>mount -o remount,rw /</code>
# <code>echo "/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0" >> /etc/fstab</code>
# <code>mkdir /media/ext3fs</code>
# <code>mount -o remount,ro /</code>
# <code>mount -a</code> or <code>reboot</code>

Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.

===Step 2: Mounting the ext3fs partition===
*Follow the intructions of the Chrooting wiki page.
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]

===Step 3: Installing UbuntuChroot, Xecutah, and XServer===
* Open up Preware and tap List Of Everything.
* Search for and install the following: UbuntuChroot, Xecutah, and XServer
* Now opened Xecutah and tap XServer and a new card will come up.
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:

===Step 4: What's Next?===
* Now to have some fun after all that work you put in!
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.
**[http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html Easy Autoconfiguration for Ubuntu]
* Type the below and it will update the program lists.
<pre>apt-get update</pre>
* Now type the following in the box to install what ever you wish!
<pre>/***type the below for LibreOffice
apt-get install LibreOffice

/***type the below for the Chromium Browser
apt-get install chromium-browser

/***type the below for GIMP
apt-get install gimp

/***type the below for Eclipse
apt-get install eclipse

/***type the below for LXDE
apt-get install lxde</pre>

== How to remove the ext3fs partition ==

*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]

UbuntuChroot

2011-09-29T06:58:04Z

101pre:

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

* Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

* Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

* Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

* Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=ubuntu.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 ubuntu.img 1048576

rootfs_open -t
mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/ubuntu.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/ubuntu.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

== Instructions ==

===Intro: What you need to know===
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.

* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''

===Step 1: Creating a WebOS Doctor===
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)
**[[Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor Step 1: |Application:MetaDoctor - Setting up Meta-Doctor Step 1:]]
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says "# EXT3FS_PARTITION_SIZE = 2GB". Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. '''BUT BE AWARE THAT THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU.''' Now save the file still with no file extension.
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.

===Alternative Step 1: Re-partitioning by hand===
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.

# connect with novaterm
# get rid of cryptofs process <code>pkill -SIGUSR1 cryptofs</code>
# <code>umount /media/internal</code>
# <code>resizefat /dev/mapper/store-media 4G</code> - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation should not delete your data.
# <code>lvresize -L 4G /dev/mapper/store-media</code>
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises <code>pkill -SIGUSR2 cryptofs</code> here.
# <code> lvcreate -l 100%FREE -n ext3fs store </code>
# <code>mkfs.ext3 /dev/mapper/store-ext3fs</code>
# <code>mount -o remount,rw /</code>
# <code>echo "/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0" >> /etc/fstab</code>
# <code>mkdir /media/ext3fs</code>
# <code>mount -o remount,ro /</code>
# <code>mount -a</code> or <code>reboot</code>

Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.

===Step 2: Mounting the ext3fs partition===
*Follow the intructions of the Chrooting wiki page.
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]

===Step 3: [No longer required]===

===Step 4: Installing UbuntuChroot, Xecutah, and XServer===
* Open up Preware and tap List Of Everything.
* Search for and install the following: UbuntuChroot, Xecutah, and XServer
* Now opened Xecutah and tap XServer and a new card will come up.
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:

===Step 5: What's Next?===
* Now to have some fun after all that work you put in!
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.
**[http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html Easy Autoconfiguration for Ubuntu]
* Type the below and it will update the program lists.
<pre>apt-get update</pre>
* Now type the following in the box to install what ever you wish!
<pre>/***type the below for LibreOffice
apt-get install LibreOffice

/***type the below for the Chromium Browser
apt-get install chromium-browser

/***type the below for GIMP
apt-get install gimp

/***type the below for Eclipse
apt-get install eclipse

/***type the below for LXDE
apt-get install lxde</pre>

== How to remove the ext3fs partition ==

*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]

User:101pre

2011-09-29T06:57:05Z

101pre: UbuntuChroot

* [http://www.webos-internals.org/wiki/UbuntuChroot UbuntuChroot]

UbuntuChroot

2011-09-29T06:55:53Z

101pre: /* Step 1: Creating a WebOS Doctor */ Application:MetaDoctor

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=ubuntu.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 ubuntu.img 1048576

rootfs_open -t
mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/ubuntu.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/ubuntu.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

== Instructions ==

===Intro: What you need to know===
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.

* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''

===Step 1: Creating a WebOS Doctor===
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)
**[[Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor Step 1: |Application:MetaDoctor - Setting up Meta-Doctor Step 1:]]
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says "# EXT3FS_PARTITION_SIZE = 2GB". Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. '''BUT BE AWARE THAT THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU.''' Now save the file still with no file extension.
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.

===Alternative Step 1: Re-partitioning by hand===
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.

# connect with novaterm
# get rid of cryptofs process <code>pkill -SIGUSR1 cryptofs</code>
# <code>umount /media/internal</code>
# <code>resizefat /dev/mapper/store-media 4G</code> - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation should not delete your data.
# <code>lvresize -L 4G /dev/mapper/store-media</code>
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises <code>pkill -SIGUSR2 cryptofs</code> here.
# <code> lvcreate -l 100%FREE -n ext3fs store </code>
# <code>mkfs.ext3 /dev/mapper/store-ext3fs</code>
# <code>mount -o remount,rw /</code>
# <code>echo "/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0" >> /etc/fstab</code>
# <code>mkdir /media/ext3fs</code>
# <code>mount -o remount,ro /</code>
# <code>mount -a</code> or <code>reboot</code>

Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.

===Step 2: Mounting the ext3fs partition===
*Follow the intructions of the Chrooting wiki page.
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]

===Step 3: [No longer required]===

===Step 4: Installing UbuntuChroot, Xecutah, and XServer===
* Open up Preware and tap List Of Everything.
* Search for and install the following: UbuntuChroot, Xecutah, and XServer
* Now opened Xecutah and tap XServer and a new card will come up.
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:

===Step 5: What's Next?===
* Now to have some fun after all that work you put in!
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.
**[http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html Easy Autoconfiguration for Ubuntu]
* Type the below and it will update the program lists.
<pre>apt-get update</pre>
* Now type the following in the box to install what ever you wish!
<pre>/***type the below for LibreOffice
apt-get install LibreOffice

/***type the below for the Chromium Browser
apt-get install chromium-browser

/***type the below for GIMP
apt-get install gimp

/***type the below for Eclipse
apt-get install eclipse

/***type the below for LXDE
apt-get install lxde</pre>

== How to remove the ext3fs partition ==

*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]

UbuntuChroot

2011-09-29T06:52:23Z

101pre: /* Step 5: What's Next? */ Easy Autoconfiguration for Ubuntu

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=ubuntu.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 ubuntu.img 1048576

rootfs_open -t
mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/ubuntu.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/ubuntu.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

== Instructions ==

===Intro: What you need to know===
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.

* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''

===Step 1: Creating a WebOS Doctor===
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)
**http://www.webos-internals.org/wiki/Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says "# EXT3FS_PARTITION_SIZE = 2GB". Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. BUT BE AWARE THST THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU. Now save the file still with no file extension.
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.

===Alternative Step 1: Re-partitioning by hand===
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.

# connect with novaterm
# get rid of cryptofs process <code>pkill -SIGUSR1 cryptofs</code>
# <code>umount /media/internal</code>
# <code>resizefat /dev/mapper/store-media 4G</code> - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation should not delete your data.
# <code>lvresize -L 4G /dev/mapper/store-media</code>
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises <code>pkill -SIGUSR2 cryptofs</code> here.
# <code> lvcreate -l 100%FREE -n ext3fs store </code>
# <code>mkfs.ext3 /dev/mapper/store-ext3fs</code>
# <code>mount -o remount,rw /</code>
# <code>echo "/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0" >> /etc/fstab</code>
# <code>mkdir /media/ext3fs</code>
# <code>mount -o remount,ro /</code>
# <code>mount -a</code> or <code>reboot</code>

Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.

===Step 2: Mounting the ext3fs partition===
*Follow the intructions of the Chrooting wiki page.
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]

===Step 3: [No longer required]===

===Step 4: Installing UbuntuChroot, Xecutah, and XServer===
* Open up Preware and tap List Of Everything.
* Search for and install the following: UbuntuChroot, Xecutah, and XServer
* Now opened Xecutah and tap XServer and a new card will come up.
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:

===Step 5: What's Next?===
* Now to have some fun after all that work you put in!
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.
**[http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html Easy Autoconfiguration for Ubuntu]
* Type the below and it will update the program lists.
<pre>apt-get update</pre>
* Now type the following in the box to install what ever you wish!
<pre>/***type the below for LibreOffice
apt-get install LibreOffice

/***type the below for the Chromium Browser
apt-get install chromium-browser

/***type the below for GIMP
apt-get install gimp

/***type the below for Eclipse
apt-get install eclipse

/***type the below for LXDE
apt-get install lxde</pre>

== How to remove the ext3fs partition ==

*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]

UbuntuChroot

2011-09-29T06:51:22Z

101pre: /* How to remove the ext3fs partition */ Application:MetaDoctor

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=ubuntu.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 ubuntu.img 1048576

rootfs_open -t
mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/ubuntu.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/ubuntu.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

== Instructions ==

===Intro: What you need to know===
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.

* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''

===Step 1: Creating a WebOS Doctor===
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)
**http://www.webos-internals.org/wiki/Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says "# EXT3FS_PARTITION_SIZE = 2GB". Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. BUT BE AWARE THST THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU. Now save the file still with no file extension.
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.

===Alternative Step 1: Re-partitioning by hand===
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.

# connect with novaterm
# get rid of cryptofs process <code>pkill -SIGUSR1 cryptofs</code>
# <code>umount /media/internal</code>
# <code>resizefat /dev/mapper/store-media 4G</code> - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation should not delete your data.
# <code>lvresize -L 4G /dev/mapper/store-media</code>
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises <code>pkill -SIGUSR2 cryptofs</code> here.
# <code> lvcreate -l 100%FREE -n ext3fs store </code>
# <code>mkfs.ext3 /dev/mapper/store-ext3fs</code>
# <code>mount -o remount,rw /</code>
# <code>echo "/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0" >> /etc/fstab</code>
# <code>mkdir /media/ext3fs</code>
# <code>mount -o remount,ro /</code>
# <code>mount -a</code> or <code>reboot</code>

Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.

===Step 2: Mounting the ext3fs partition===
*Follow the intructions of the Chrooting wiki page.
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]

===Step 3: [No longer required]===

===Step 4: Installing UbuntuChroot, Xecutah, and XServer===
* Open up Preware and tap List Of Everything.
* Search for and install the following: UbuntuChroot, Xecutah, and XServer
* Now opened Xecutah and tap XServer and a new card will come up.
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:

===Step 5: What's Next?===
* Now to have some fun after all that work you put in!
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.
**http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html
* Type the below and it will update the program lists.
<pre>apt-get update</pre>
* Now type the following in the box to install what ever you wish!
<pre>/***type the below for LibreOffice
apt-get install LibreOffice

/***type the below for the Chromium Browser
apt-get install chromium-browser

/***type the below for GIMP
apt-get install gimp

/***type the below for Eclipse
apt-get install eclipse

/***type the below for LXDE
apt-get install lxde</pre>

== How to remove the ext3fs partition ==

*[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition |Application:MetaDoctor - How to remove the ext3fs partition ]]

UbuntuChroot

2011-09-29T06:50:22Z

101pre: /* Step 2: Mounting the ext3fs partition */ Application:MetaDoctor

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=ubuntu.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 ubuntu.img 1048576

rootfs_open -t
mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/ubuntu.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/ubuntu.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

== Instructions ==

===Intro: What you need to know===
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.

* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''

===Step 1: Creating a WebOS Doctor===
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)
**http://www.webos-internals.org/wiki/Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says "# EXT3FS_PARTITION_SIZE = 2GB". Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. BUT BE AWARE THST THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU. Now save the file still with no file extension.
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.

===Alternative Step 1: Re-partitioning by hand===
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.

# connect with novaterm
# get rid of cryptofs process <code>pkill -SIGUSR1 cryptofs</code>
# <code>umount /media/internal</code>
# <code>resizefat /dev/mapper/store-media 4G</code> - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation should not delete your data.
# <code>lvresize -L 4G /dev/mapper/store-media</code>
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises <code>pkill -SIGUSR2 cryptofs</code> here.
# <code> lvcreate -l 100%FREE -n ext3fs store </code>
# <code>mkfs.ext3 /dev/mapper/store-ext3fs</code>
# <code>mount -o remount,rw /</code>
# <code>echo "/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0" >> /etc/fstab</code>
# <code>mkdir /media/ext3fs</code>
# <code>mount -o remount,ro /</code>
# <code>mount -a</code> or <code>reboot</code>

Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.

===Step 2: Mounting the ext3fs partition===
*Follow the intructions of the Chrooting wiki page.
**[[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot |Application:MetaDoctor - How to get the optional ext3fs partition mounted at device boot]]

===Step 3: [No longer required]===

===Step 4: Installing UbuntuChroot, Xecutah, and XServer===
* Open up Preware and tap List Of Everything.
* Search for and install the following: UbuntuChroot, Xecutah, and XServer
* Now opened Xecutah and tap XServer and a new card will come up.
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:

===Step 5: What's Next?===
* Now to have some fun after all that work you put in!
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.
**http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html
* Type the below and it will update the program lists.
<pre>apt-get update</pre>
* Now type the following in the box to install what ever you wish!
<pre>/***type the below for LibreOffice
apt-get install LibreOffice

/***type the below for the Chromium Browser
apt-get install chromium-browser

/***type the below for GIMP
apt-get install gimp

/***type the below for Eclipse
apt-get install eclipse

/***type the below for LXDE
apt-get install lxde</pre>

== How to remove the ext3fs partition ==

[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition]]

Talk:UbuntuChroot

2011-09-29T06:47:57Z

101pre:

The process of extracting the rootfs archive can be done without copying the file to the device:

novacom -s run "file:///bin/tar zxvf - -C /media/ext3fs/ubuntu" < armel-rootfs-201107071349.tgz

==The easiest/safest way to wipe your install if using a file image==
*[http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu-7.html#post3143847]

UbuntuChroot

2011-09-29T06:43:49Z

101pre: Donations

You need a large-enough ext3fs partition created with Meta-Doctor mounted at /media/ext3fs (instructions for how to create a partition are available below). Note that the latest optware bootstrap package will also use this if it exists. '''If you have not already done so you should setup the ext3fs partition to mount at bootup.''' (Failure to do so will cause you to run out of disk space) Instructions can be found on the [[Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot|Meta Doctor]] page.

Make sure you have the WebOS Internals Testing Feeds enabled.

Using Preware, install Xecutah and Ubuntu 11.04 Chroot.

Hit the relevant buttons on Xecutah to run the XServer and the Ubuntu 11.04 Chroot.

Run XServer first, which will open an Xserver window, then return to Xecutah and tap Ubuntu 11.04 Chroot. When you return to the Xserver card, you should see a Ubuntu command prompt.

Use "apt-get install" to install whatever apps you like from Ubuntu. Then run in the Ubuntu chroot and render on the XServer.

Please support the project with a [[WebOS_Internals:Site_support|Donation]], and install the Preware Homebrew Documentation app from the official app catalog to learn how to install Preware on your device.

<center>'''NOTE ABOUT DISK IMAGES'''</center>
It is possible to use a disk image instead of creating a partition. However, this comes with a few caveats, such as slower speed, disk size restriction (mounting a disk image in cryptofs may limit you to < 2GB) or breaking USB connectivity (on /media/internal). Do this at your own risk. '''Partitioning with Meta Doctor is the faster and slightly stabler method.'''

If you do not want to re-doctor your phone, this is how to do it with an image file:
First, open a terminal (XServer >XTerm - everything is done on device).

1048576 (KB) means 1 GB, you can replace that (used in two commands). NOTE: You can not create an image file in /media/cryptofs larger than 2GB.

cd /media/cryptofs
dd if=/dev/zero of=ubuntu.img bs=1024 count=1048576
mkfs.ext3 -F -b 1024 ubuntu.img 1048576

rootfs_open -t
mkdir /media/ext3fs

Next, you must mount the new image file.

mount -o loop /media/cryptofs/ubuntu.img /media/ext3fs

To make this mount at boot, you need to add an entry to the fstab:

echo "/media/cryptofs/ubuntu.img /media/ext3fs ext3 loop 0 0" >> /etc/fstab
mount -a

Now you can install Ubuntu 11.04 Chroot from Preware and it will populate the image file.

== Instructions ==

===Intro: What you need to know===
UbuntuChroot is the raw Ubuntu terminal without the familiar GNOME graphical interface that all have come to think of Ubuntu. With this installed, you will be able to install ubuntu programs and launch them with in the terminal card. However, you can install a GUI windows manager such as LXDE which will let you use it as you would a normal computer.
To do this, the basic rundown will be making a new WebOS Doctor that has a separete partition of memory for Ubuntu to run with in. Then we will install it on your TouchPad and mount that partition so it will be able to be used after a reboot of the device. Lastly, we will install Xecutah, XServer, and UbuntuChroot from Preware and boot up Ubuntu on your TouchPad.
Both credit and Props go to WebOS Internals for making this possible and putting in all the hard work they have to make it as easy as it is.

* '''Warnings: WebOS Internals takes no responsibility over what may happen to your device. If you follow these instructions it 'should' work perfectly. If you do endup messing something up you 'should' be able to just doctor the device using the stock WebOS Doctor from HP.'''
**'''You my want to backup app data and the like using Save/Restore in Preware as you will lose all your data buy installing a WebOS Doctor. Please do so!'''

===Step 1: Creating a WebOS Doctor===
* We will be using the Meta Doctor to create a special WebOS Doctor that will create a 2GB (or more if you wish to do so) partition in /media/ext3fs/ were Ubuntu will be.
* Use the WebOS Internals Guide to installing and running the Meta Doctor (the link below)
**http://www.webos-internals.org/wiki/Application:MetaDoctor#Step_1:_Setting_up_Meta-Doctor
* Make sure you uncomment the correct setting in the Makefile to actually create the ext3fs partition. Which will be a little ways down in the file were it says "# EXT3FS_PARTITION_SIZE = 2GB". Delete that # before it to make it readable to the program and if you desire to you may change the 2GB to the size you wish to have for Ubuntu. BUT BE AWARE THST THIS TAKES AWAY THE MEMORY FROM THE USB PARTITION AND ADDS IT TO UBUNTU. Now save the file still with no file extension.
*If you are using a Wifi Only TouchPad you will be using the last one which has touchpad for device and WiFi all for the carrier.
* Once the Meta Doctor is done, run the WebOS Doctor it created under the 'builds' folder. And setup your device.

===Alternative Step 1: Re-partitioning by hand===
If you do not want to run the doctor, but do want to do the right thing and give your Ubuntu a partition of its own, here's, roughly, how: [note: [[User:Habbie|Habbie]] 08:10, 17 September 2011 (UTC) writing this from memory. somebody should try it and update the details.]:
[[User:Midnite|Midnite]] 26 September 2011 confirmed, below works correctly.

# connect with novaterm
# get rid of cryptofs process <code>pkill -SIGUSR1 cryptofs</code>
# <code>umount /media/internal</code>
# <code>resizefat /dev/mapper/store-media 4G</code> - I picked 4G to leave about 9G for my Ubuntu. Decide for yourself. This operation should not delete your data.
# <code>lvresize -L 4G /dev/mapper/store-media</code>
# now, remount /media/internal and /media/cryptofs. I decided to just reboot but you could do the remount/reboot later. rwhitby advises <code>pkill -SIGUSR2 cryptofs</code> here.
# <code> lvcreate -l 100%FREE -n ext3fs store </code>
# <code>mkfs.ext3 /dev/mapper/store-ext3fs</code>
# <code>mount -o remount,rw /</code>
# <code>echo "/dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0" >> /etc/fstab</code>
# <code>mkdir /media/ext3fs</code>
# <code>mount -o remount,ro /</code>
# <code>mount -a</code> or <code>reboot</code>

Skip the next step (Step 2: Mounting the ext3fs partition) - we have already done this above in step 10.

===Step 2: Mounting the ext3fs partition===
*Follow the intructions of the Chrooting wiki page.
**http://www.webos-internals.org/wiki/Application:MetaDoctor#How_to_get_the_optional_ext3fs_partition_mounted_at_device_boot

===Step 3: Adding Testing Feeds===
*Follow the instructions on the Testing Feeds wiki page. Please understand the risks noted.
**http://www.webos-internals.org/wiki/Testing_Feeds

===Step 4: Installing UbuntuChroot, Xecutah, and XServer===
* Open up Preware and tap List Of Everything.
* Search for and install the following: UbuntuChroot, Xecutah, and XServer
* Now opened Xecutah and tap XServer and a new card will come up.
* Go back to Xecutah and tap UbuntuChroot. Then swipe back to the new card that came up.
* Now you should have the Ubuntu terminal. Done. It should have a few 'mount' commands and then the @Touchpad:

===Step 5: What's Next?===
* Now to have some fun after all that work you put in!
* Take a look at the auto configuration script that will install and setup most of the what is in the next bullet for you in just a few steps.
**http://forums.precentral.net/webos-development/295909-easy-autoconfiguration-ubuntu.html
* Type the below and it will update the program lists.
<pre>apt-get update</pre>
* Now type the following in the box to install what ever you wish!
<pre>/***type the below for LibreOffice
apt-get install LibreOffice

/***type the below for the Chromium Browser
apt-get install chromium-browser

/***type the below for GIMP
apt-get install gimp

/***type the below for Eclipse
apt-get install eclipse

/***type the below for LXDE
apt-get install lxde</pre>

== How to remove the ext3fs partition ==

[[Application:MetaDoctor#How_to_remove_the_ext3fs_partition]]

Talk:Main Page

2011-09-17T13:00:47Z

101pre: /* Article organization */

This page is for discussion of the Main Page. For discussion of general policies, see [[WebOS Internals talk:Policies and guidelines]]

== Beta Main Page ==

This isn't in use right now, but when It comes the time to swap out the main page again.

[[Main_Page_beta]]
[[Template:Page-main-beta]]

== Article title capitalization ==

Are we sure we want to use title case for article titles? [http://en.wikipedia.org/wiki/Wikipedia:Mos#Article_titles Wikipedia uses sentence case], and i think it looks much better.
—[[User:X1011|X1011]] 06:35, 20 July 2009 (UTC) 
Also, same question for section headings —[[user:X1011|X1011]] 12:45, 20 July 2009 (UTC)

I think it usually works out good since a lot of pages are displayed as: <nowiki>[[Page Name]], also with the headers of course don't uppercase "a", "and", etc.</nowiki> --[[User:Templarian|Templarian]] 13:21, 20 July 2009 (UTC)

'''from #webos-internals:'''
<source lang="text" enclose="div">
Rick_: X1011, the pages-to-be-moved page on the new wiki uses the PAGE NAME as a link to create the page on the new wiki rather than the old page link from the old wiki.
Rick_: In general _most_ of them are fine.
Rick_: We prefer "Page About Smashing the Pre" to "Page about smashing the Pre" because it _is_ the title of the page, and so _should_ be in title case.
Rick_: or that's the consensus of the team to date.
</source>

== Registration error warning ==

Instead of having the warning about getting an error on confirming your registration on the main page, could an admin put it on the [http://www.webos-internals.org/index.php?title=Special:Userlogin&type=signup create account page]? —[[user:X1011|X1011]] 01:58, 23 July 2009 (UTC)

The Special:* namespace pages are not editable. -- Rod

Maybe not inside the wiki editing system, but surely it's editable at some level. I think we should put user experience before "that's too hard to do". —[[user:X1011|X1011]] 23:55, 23 July 2009 (UTC)

Agreed - I'll look into it. -- Rod

==Front page mispelling and Description Addition==

There's a mispelling on the top of the front page (I don't have rights to edit this page)

"Thank you for heling us convert all the pages from the old wiki!"

should be:

"Thank you for hel'''p'''ing us convert all the pages from the old wiki!"

Also, can you add something referencing "Kernels" in the development tools' description?

-[[user:hopspitfire|hopspitfire]] 05:33, 23 July 2009 (UTC)

Added kernels to the list --[[User:Templarian|Templarian]] 19:23, 27 July 2009 (UTC)

== Protection ==

Why is Main Page protected? It shouldn't be protected unless it is vandalised; see [[wikipedia:WP:NO-PREEMPT]]. As seen in the above section, regular people have useful contributions. —[[user:X1011|X1011]] 21:52, 24 July 2009 (UTC)

I disagree. We're getting 20K page views a day. Let's keep the main page clean and functonal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

the main page has 14,428 total views to date. we shouldn't assume our users will make it dirty and unfunctional before we even give them a chance. Wikia has [[wikia:c:help:help:main page#What if I don't want visitors to edit my main page?|a good writeup]] on why the main page should not be protected.

also, in the future, when you protect a page, please include a note explaining why you are doing so.

—[[user:X1011|X1011]] 08:07, 28 July 2009 (UTC)

The main page is currently editable, was this intentional? [[User:Hopspitfire|hopspitfire]] 07:03, 1 August 2009 (UTC)

Yea, rick only set it to be protected till aug 1st while updates were going on. The idea was so that users wouldn't mess with it as the site was being setup / structured. --[[User:Templarian|Templarian]] 22:42, 2 August 2009 (UTC)

: The idea was that there was a gazillion links on the FRONT page of the old wiki. we wanted the front page of the new wiki to lead to DEPARTMENTS instead of having a zillion links on it. -- that's worked out now, and seems institutionally embedded so why not let the protection expire? [[User:Rboatright|rboatright]] 22:51, 2 August 2009 (UTC)

As many of seen the front page is no longer protected. The edit tab has been hidden, but editing can be easily done by "?title=Main_Page&action=edit". Hopefully this solved any disagreements people may have with the editing/protection of the main page. --[[User:Templarian|Templarian]] 14:24, 5 August 2009 (UTC)

That can be simplified even more just by typing "?action=edit". -[[User:Hopspitfire|hopspitfire]] 21:20, 5 August 2009 (UTC)

== Research/Reference Portal ==

We need to add the Research/Reference portal to the front page. I recommend re-organizing the front page.

I'd start with putting "Getting Started" on the top-middle by itself, then follow the diagram below:

<pre><nowiki>
-------------Getting Started-------------
Linux Apps---Source Patches---Dev Tools
Research-------webOS Apps-----Hardware
Recovery--------SDK Docs------Wiki Help
</nowiki></pre>

We also need an icon for "Research", maybe put a lab suit over Tux with a doctor's mask. What do you think?

I also agree with the post above regarding the unprotection of the front page (at least to autoconfirmed users). -hopspitfire

yes, we need to add a box for the research portal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

As of today all of this has been done (including Tux in a lab coat). --[[User:Templarian|Templarian]] 15:11, 5 August 2009 (UTC)

== featured article ==
I think we need a "featured article" on the main page. Right now, that wuld be
terminal. [[User:Rboatright|rboatright]] 02:57, 28 July 2009 (UTC)

the featured articles look great. --[[User:Templarian|Templarian]] 13:15, 30 July 2009 (UTC)

== Article organization ==

I noticed that there are a lot of manually maintained lists on this wiki. I'm not sure why the Category system is not being used, since it provides a better way to manage lists. A manually maintained list provides more information such as a summary, but a category is much easier to maintain and the users can browse a category page. Pages such as the [[Portal:webOS_Applications_All]] might be better as a category page. Actually, it looks like [[Special:Categories]] are rarely used. The category system could also compliment the current system as well.
: Any problem if I start adding lots of pages into appropriate categories?

Also, an [http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style_%28infoboxes%29 infobox] on certain article types such as applications would help with origination. A script such as the one used on the [http://www.mediawiki.org/wiki/Extension_Matrix Extension Matrix] might eventually be plausible in the future once infoboxes are more commonly used.
: Can I create them?
How zealous about organization is it ok to be?
:[[User:Servel333|Servel333]] 18:59, 8 December 2009 (UTC)

i'm all for both ideas. i tried organizing this wiki at one point but i didn't have time to teach everyone how to properly use a wiki and was also meeting resistance. i never even bothered with the application pages because there were plans to make a proper repo site ([[Preware Design#Site]]). see also [[Talk:Portal:Patches to webOS#naming]] for my suggestions on organizing the patches. —[[user:X1011|X1011]] 22:20, 8 December 2009 (UTC)

When I have some free time I'll add pages to categories and see what issues come up. An infobox would even help with linking to an external repository, since most of the URL could be hidden by the infobox and if certain parts of the URL change, every single application page doesn't have to be updated for the links to work. Thanks. Hopefully, I can be of some help around here.
:[[User:Servel333|Servel333]] 23:10, 8 December 2009 (UTC)

==How about mentioning Devices==

Be inclusive to cover/include the touchpad.

Komodo New Project

2011-09-17T01:17:37Z

101pre:

Creating a new project is pretty straight forward in Komodo and the whole process is automated.

'''Step 1.''' Click the Drop down on the far left of the webOS Tab ([[Image:Komodo_Page_White_Arrowdown.png]]).

'''Step 2.''' Select New Project ([[Image:Komodo_Folder_Pre_Add.png]]).

'''Step 3.''' Select a Empty folder in which to place the project (Ex. "documents/projects/com.domain.myapp/")

'''Step 4.''' Fill in the various data asked for. The defaults are probably what you want for everything below the "main" textbox.

[[Image:Komodo_New_Project.png|frame|none|New Project Screen Expanded (you will probably have a scroll bar)]]

Buy levitra 100mg cheap - purchase levitra 20mg online - levitra and valium taking together

2011-09-17T01:15:16Z

101pre: delete this page

delete this page

Application:Govnah-FR

2011-09-17T01:12:27Z

101pre:

[[Category:Application]]
[[Category:French]]

: [[Image:France.png]] [[Application:Govnah-FR]] '''Attention : cette page est la traduction en français de la page anglaise du wiki : http://www.webos-internals.org/index.php?title=Application:Govnah
: [[Image:Australia.png]] [[Image:USA.png]] '''Note : this page/article is the french translation of the english wiki page : [[Application:Govnah]]

Veuillez vous référer à la page anglaise pour avoir les informations les plus à jour'''

{{application
|name=Govnah
|type=webOS
|version=Version: 0.6.8 (10 septembre 2010)
|tag=Utilities
|screenshot=Govnah-main-FR.png
|description=}}

= Résumé =

[[image:Icon_WebOSInternals_Govnah.png|frameless|right]]
Les noyaux avancés de Linux pour webOS fournissent des mécanismes pour contrôler les différents paramètres de fonctionnement de l'appareil tels que la vitesse d'horloge. Ces noyaux Linux exposent un ou plusieurs "governors" qui permettent de contrôler ces paramètres. Un exemple d'un tel noyau Linux est [[Application:UberKernel|UberKernel]]. Cette application est disponible via [[Application:Preware-FR]].

=== But ===

L'application ''Govnah'' fait deux choses:
:* Elle fournit un graphique en temps réel de la vitesse du processeur, de la température du processeur, de l'utilisation de la mémoire et de la charge du système
:* Elle fournit aussi un mécanisme qui permet de régler les paramètres des "governors" exposés par le noyau Linux et de faire la configuration d'autres options du noyau Linux.

=== Exemples dans le monde réel ===

Le noyau Uber-Kernel expose un 'governor' appelé ''à la demande (on-demand)''. Le "governor" à la demande permet d'augmenter et de réduire la vitesse d'horloge en fonction du pourcentage d'utilisation du processeur.

Le "governor" ''à la demande'' expose les paramètres suivants qui peuvent être paramétrés par Govnah:
:* scaling_max_freq - Réglage de la fréquence de votre processeur au maximum de ce qui est possible.
:* scaling_min_freq - Meme chose que scaling_max_freq mais dans le sens opposé avec le paramétrage d'une valeur minimum.
:* sampling_rate - Paramètre l'intervalle de temps après lequel vous voulez que le noyau Linux vérifie l'utilisation du processeur (en microsecondes) En général, cela est fixé à des valeurs de 10000 ou plus.
:* up_threshold - Ce paramètre permet de définir l'augmentation moyenne du pourcentage d'utilisation du processeur entre les mesures réalisées par le noyau Linux afin de décider d'augmenter la fréquence du CPU.
:* ignore_nice_load - Si le paramètre est mis à '0' (par défaut), tous les processus sont pris en compte pour la valeur d' 'utilisation du processeur'. Lorsqu'il est réglé à '1', les processus qui sont exécutés avec une valeur de type 'nice' (bon) ne comptent pas (et donc peuvent être ignorée) dans le calcul de l'utilisation globale.
:* powersave_bias - Ce paramètre modifie le comportement du "governor" à la demande (ondemand) pour sauvegarder le plus de puissance possible en réduisant la fréquence cible suivant un pourcentage déterminé. La pente ou pas est en dixièmes de pour cent (0 à 1000). Une valeur de 100 se traduira par une augmentation modeste de 10% de la vitesse du processeur pour une utilisation donnée alors qu'une valeur de 0 n'entraîne aucune augmentation.

Chaque "Governor" dans le noyau Linux indique à ''Govnah''quels sont les paramètres dans le noyau Linux qu'il est possible de paramétrer et peut dire aussi quelles sont les limites de ces paramètres.

=== Governors actuels===

Les governors actuels qui sont disponibles dans le noyau Linux Uber-Kernel et qui sont supportés par Govnah sont :

:* On-demand (à la demande) - décrit ci-dessus, augmente la vitesse d'horloge, en réponse à l'augmentation de la charge du processeur.
:* Conservative (conservateur) - le contraire de On-demand (à la demande), Conservative (conservateur) diminue la vitesse de l'horloge du processeur en réponse à une diminution de la charge du processeur.
:* Userspace - paramètre la vitesse du processeur à une vitesse définie qui a été choisi par LunaSysMgr
:* powersave - paramètre la vitesse du processeur à la valeur minimale de la fréquence
:* performance - paramètre la vitesse du processeur à la valeur maximale de la fréquence
:* screenstate - fait fonctionner le processeur à une vitesse plus élevée lorsque l'écran est allumé et à 500MHz lorsque l'écran est éteint

 
= Installation =

Le guide suivant suppose que vous utilisez un Palm Pre/Pre+ qui a noyau Linux d'origine de webOS 1.4.1.1 et pas de patches d'overclocking.

#Sur l'écran d'accueil de Preware, tapez "Gov" et appuyez sur Entrée.
#Sélectionnez "Govnah" et "Installer"
#Si vous n'avez pas encore installé un "Noyau (Kernel)", sur l'écran d'accueil Preware, tapez "uber" et appuyez sur Entrée.
#Sélectionnez "[[Application:UberKernel|UberKernel (Palm Pre/Pre+)]]" et "Installet"
#Redémarrez votre téléphone lorsque celà vous est demandé

 
= Usage rapide =

=== Par où commencer ===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapProfile-FR.png|160px|frameless|left|text-top]]
|valign="top"|Pour commencer à accéder à la puissance du contrôle de Govnah sur le noyau Linux, appuyez sur le texte "Profil" sur la ligne en haut de l'écran principal.
|}
 

=== Profils ===

{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahTapAdvanced-FR.png|160px|frameless|left|text-top]]
|valign="top"|Voici la liste des profils stockés dans Govnah. Les profils sont un moyen simple pour stocker différents paramètres que vous souhaitez appliquer au moment du démarrage (boot). Vous avez la possibilité de stocker plusieurs profils différents pour tester les meilleurs réglages pour '''votre ''' utilisation. Appuyez sur le texte "Paramètres avancés" en haut de l'écran pour accéder aux paramètres individuels qui sont stockés dans le profil.
|}
 

=== Paramètres avancées ===

{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahAdvSettings2-FR.png|160px|frameless|left|text-top]]
|valign="top"|Ceci est la liste des éléments configurables. Ils sont expliqués plus en détail ci-dessous. Vous êtes ''fortement''encouragés à lire sur ce que sont et font ces paramètres. Tous ne sont bénéfiques pour vous ou votre batterie. La plupart des valeurs par défaut sont un juste milieu entre les deux. Le principal changement est de "Fréquence processeur". Tapez maintenant.
|}
 

=== Fréquence processeur ===
{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCPUFreq-FR.png|160px|frameless|left|text-top]]
|valign="top"|La première fois que vous démarrez votre Pré/Pixi après l'installation et Govnah et de UberKernel, il fonctionnera à 600MHz. C'est là que vous pouvez le pousser jusqu'à 800 MHz. Sélectionnez "800Mhz" dans la section "Freq Définie pour Définir vitesse (Set Speed)" et appuyez sur le bouton "Appliquer les paramètres" en bas de la page. Votre téléphone fonctionnera immédiatement à 800Mhz. Dans la zone de gestes, le geste avec un glissement vers la gauche permet de revenir sur l'écran "Paramètres avancés".
|}
 

===Mémoire d'échange (compcache)===

{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahCompSwap-FR.png|160px|frameless|left|text-top]]
|valign="top"|La mémoire d'échange (swap) compressé (compcache) est simplement une quantité de RAM (mémoire vive) qui est réservée à la compression des données chargées dans la mémoire vive (RAM) lorsque la quantité de mémoire vive (RAM) nécessaire dépasse l'espace disponible en mémoire. Dans un espace d'adressage mémoire précis (In a nut shell), celà permet d'offrir plus d'espace mémoire pour les données des applications doivent être chargée dans la mémoire vive (RAM). Ce compromis réduit légèrement les performances de la mémoire vive (RAM) pour ces données qui d'abord compressées et ensuite décompressées par rapport à une mémoire non compressée. Mais ce compromis permet un accès plus rapide aux données que si elles étaient stockées dans un espace de mémoire d'échange (swap) sur le disque de stockage interne (de mémoire). Pour utiliser cette fonctionnalité, vous devez d'abord définir la quantité d'espace mémoire qui sera réservée et ensuite permettre à compcache de basculer sur celle-ci. Puis cliquez ensuite sur le bouton "Appliquer paramètres" pour rendre ces paramètres actifs. Si vous désirez changer la quantité d'espace mémoire réservé une fois qu'il aura été rendu actif, vous devez désactiver compcache et cliquez ensuite sur le bouton "Appliquer paramètres". Puis changez ensuite la quantité d'espace mémoire réservée, réactivez compcache et cliquez ensuite sur le bouton "Appliquer paramètres" pour rendre de nouveau ce réglage actif.
|}
 

=== Enregistrer votre profil ===

{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahSaveProfile-FR.png|160px|frameless|left|text-top]]
|valign="top"|Après avoir quitté l'étape précédente, vous avez fini par revenir à l'écran "Paramètres avancés" où le bouton "Enregistrer nouveau profil" est en bas de la page. C'est là que vous pouvez configurer votre Pre/Pixi pour le faire démarrer (boot) avec une vitesse plus rapide. Définissez le nom d'un profil personnalisé que vous souhaitez ici et appuyez sur le bouton "Enregistrer nouveau profil". Dans la zone de gestes, le geste avec un glissement vers la gauche permet de revenir sur l'écran "Profils".
|}
 

=== Gestion du profil ===

{| Width="61%" VAlign="top"
|valign="top"|[[image:GovnahProfilesList-FR.png|160px|frameless|left|text-top]]
|valign="top"|Comme vous pouvez le voir clairement, vous pouvez enregistrer plusieurs profils différents pour tester différents réglages afin de trouver celui qui vous convient le mieux et celui qui convient le mieux à vos habitudes d'utilisation afin de trouver le "juste milieu" entre la vitesse et les économies d'énergie sur la batterie. Vous seul pouvez trouver cela. Certaines [http://forums.precentral.net/webos-internals/244701-govnah.html personnes peuvent vous aider en suggérant] ce qui fonctionne pour eux, mais aucun des appareils n'est '''exactement'' le même.
|}

 

= Governors en profondeur =

Liste détaillée de l'ensemble des Governors du noyau Linux avec une description et une explication du paramétrage de chacun d'entre eux.
Voir [http://www.webos-internals.org/index.php?title=Application:Govnah#Governors_In-Depth Governors In-Depth]

= Note pour les développeurs =

Voir [http://www.webos-internals.org/index.php?title=Application:Govnah#Developer_Notes Developer Notes]

= Liens externes =

* http://www.pantz.org/software/cpufreq/usingcpufreqonlinux.html
* http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=/liaai/cpufreq/TheOndemandGovernor.htm
* http://fasterdata.es.net/TCP-tuning/linux.html
* http://www.pdfgeni.com/book/Performance-analysis-of-loss-based-high-speed-TCP-congestion-control-algorithms-pdf.html - collection of documents on implementation of different IPv4 congestion control methods.
* http://www.mjmwired.net/kernel/Documentation/cpu-freq/governors.txt - Kernel documentation for the standard Linux CPU frequency governors

Category:Application

2011-09-17T01:08:04Z

101pre: Applications

Applications

User:101pre

2011-09-16T01:53:02Z

101pre: hate red links

101pre

Talk:Lighttpd

2011-09-16T01:51:07Z

101pre: Autostart ssh and lighty demons

==Autostart ssh and lighty demons==
*[http://webos-dafyddg.tumblr.com/ Autostart ssh and lighty demons], scroll down the page

Lighty

2011-09-16T01:48:50Z

101pre: redirect to Lighttpd

#REDIRECT [[Lighttpd]]