WebOS Internals - User contributions [en]

HamachiVPN

2011-02-10T15:55:12Z

Epyon22:

= Hamachi VPN for Palm Pre =

This document assumes you're familiar with the Hamachi VPN, specifically the linux version. It is geared towards a person wanting to "get it working" on the Pre. If you're not familiar, there are endless Googlable web pages that describe running Hamachi on desktop linux systems you can use for reference.

Become root:

<source lang="text">
sudo su
</source>

Make the filesystem writable:

<source lang="text">
mount -o remount,rw /
</source>

Download the hamachi binary to your pre via wget:

: '''Note:''' It is recommended that you use the nokia build, because it included the install script. Whereas the direct hamachi link would require that make be installed.

<source lang="text">
cd /opt/share
wget http://files.hamachi.cc/linux/nokia-770/hamachi-0.9.9.9-20-lnx-n770.tar.gz
</source>

Unpack the archive:
<source lang="text">
tar zxvf hamachi-0.9.9.9-20-lnx-n770.tar.gz
cd hamachi-n770-0.9.9.9-20
</source>

Hamachi depends on libcrypto.so.0.9.7. The Palm Pre has libcrypto.so.0.9.8 installed. I made a symlink, and it worked. So...
<source lang="text">
ln -s /usr/lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7
</source>

Edit the "install" script using your favorite editor (like vi) to change the installation locations.
Also fix line 7 or you'll get an error.

I changed it to:

<source lang="text">
HAMACHI_DST=/opt/bin
TUNCFG_DST=/opt/sbin

echo
echo Copying hamachi into $HAMACHI_DST ..
</source>

Then follow the instructions in the README under Quick Start, but basically:

<source lang="text">
./install
/opt/sbin/tuncfg
hamachi-init
hamachi start
hamachi login
hamachi set-nick <your nickname>
hamachi join <network>
hamachi go-online
</source>

== Hint ==
Adding your Pre to your Windows hamachiVPN.

<source lang="text">

If you want to join a group made on the hamachi.cc (the official logmein page) webpage you need the group ID (joining by group name fails).
On the logmein website click on My Computers and on the left side click on the Network tab.
You can create a new network here under "add network"
To get an ID for an existing network click on "edit" on the right side of the group name.
This will bring up the edit page under the ID is the 9 digit group ID (XXX-XXX-XXX) with dashes these are also part of the group ID.
To join this network on your pre type "hamachi join (9 digit ID don't forget the dashes) (password)".

</source>

If you use Hamachi to connect to web services running on your machines at home or elsewhere, you might make your life easier by adding some entries to the /etc/hosts file. Then you can access your servers by name instead of having to use the Hamachi 5.x.x.x IP addresses.

A simple sample entry in /etc/hosts which would allow you to access your server "beaker" at 5.1.2.3 would be:
(Add your servers below the "castle" line.)
<source lang="text">
127.0.0.1 localhost.localdomain localhost
127.0.0.1 castle
5.1.2.3 beaker
</source>

When done, make the filesystem read-only again:
<source lang="text">
mount -o remount,ro /
</source>

== Ping Test ==

When you've got hamachi up, you can try pinging one of your servers.
<source lang="text">
root@castle:/var/home/root# ping beaker
PING beaker (5.1.2.3): 56 data bytes
64 bytes from 5.1.2.3: seq=0 ttl=128 time=5.493 ms
64 bytes from 5.1.2.3: seq=1 ttl=128 time=32.257 ms
64 bytes from 5.1.2.3: seq=2 ttl=128 time=56.976 ms
64 bytes from 5.1.2.3: seq=3 ttl=128 time=74.249 ms
</source>

== Sleep/Wake and Battery Impact ==
On first testing:
* When the device went to sleep, the VPN went down.
* When the device woke up, the VPN came back up and was pingable again.

This morning, while at my workstation, and with the Pre idle in my pocket, I noticed my Pre was available/pingable on Hamachi. I am not totally sure of what the long-term battery impact might be of running Hamachi on the Pre. I'm not yet sure if it keeps the device "awake" all the time, which clearly would drain the battery. I have push GMail IMAP going, so I assume there is some kind of connection either being periodically established or constantly maintained. But I don't know enough about the networking aspects to determine at this time whether running Hamachi all the time will negatively impact the battery. Feel free to message me if you learn anything.

Further Testing:
* With Hamachi running I would achieve 12 hours of battery life on my pre
* Without Hamachi running after 12 hours I am sitting at 60% battery life

So to conclude running Hamachi all the time significantly decreases battery life in my situation. I personally would not recommend running Hamachi all the the time.

== Upstart script ==
This script will start Hamachi up after a reboot.

Place the following script in /etc/event.d/hamachi

<source lang="text">
description "Hamachi VPN for WebOS"
version 1.0

# don't start until the WebOS finishes it's normal boot
# that way no delay is added to the GUI startup
start on stopped finish
stop on runlevel [!2]

console output

script
/opt/bin/hamachi -c /var/home/root/.hamachi start 2>&1 /var/home/root/hamachi.log
end script

pre-start script
/opt/sbin/tuncfg
end script
</source>

Patch Launcher To Allow More Icons Per Row

2009-08-17T20:11:29Z

Epyon22:

{{template:patch}}
[[Image: 5by4Launcher.png|thumb|right]]

==Introduction==

'''THIS IS 1.1.0 SAFE, DO NOT TRY IT WITH ANY OTHER WEBOS VERSION'''

This patch allows you to have a 20 icon, 5x4 launcher page. It decreases icon size and text size, changes the apps per row, and moves the text closer to the icon. It also modifies where the page indicators and margins are a little.

==End Result==

The thumbnail image on the right shows launcher after the patch is applied.

==Patch Process==

If you are not familiar with the Webos-Internals patching process, you'll need to visit the [[Applying Patches|Applying Patches]] section of the wiki to know how to use the patch. After you have set up everything and are ready to download the patch, it is in the''' modifications''' repo under '''"luna/more_icons_per_row.patch"''' ===address forthcoming===

This patch also includes the patch to allow a user to add and remove additional launcher pages. You might have to remove that patch before applying this one.

==Patch Code==

<pre>
Index: /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
===================================================================
--- .orig/usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
+++ /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
@@ -16,7 +16,7 @@ var LauncherAssistant = Class.create({
*/
kBottomFadeHeight: 0,

- kPageIndicatorSpacing: 6, /* spacing between each page indicator */
+ kPageIndicatorSpacing: 1, /* spacing between each page indicator */
kPageMargin: 10, /* 10 pixel margin on each side of a page */
kTopMargin: 12,
kPageWidthNoMargin: NaN,
@@ -30,8 +30,8 @@ var LauncherAssistant = Class.create({
visible: true,
label: $L('Launcher'),
items: [
- /*{ label: $L('New page'), command: 'newpage' },
- { label: $L('Delete page'), command: 'deletepage' },*/
+ { label: $L('New page'), command: 'newpage' },
+ { label: $L('Delete page'), command: 'deletepage' },
Mojo.Menu.editItem,
{ label: $L('List Apps...'), command: 'listapps' },
Mojo.Menu.helpItem
@@ -125,7 +125,24 @@ var LauncherAssistant = Class.create({
ApplicationService.launch(this.deviceInfo.id, this.deviceInfo.params);
break;
/*
- case 'newpage':
+ START ENABLE PAGE ADD AND DELETE */
+ case 'newpage':
+ if (this.pageDivs.length < 10) {
+ this.insertPage(this.activePageIndex, true);
+ }
+ break;
+ case 'deletepage':
+ if (this.pageDivs.length > 1) {
+ this.deletePage(this.activePageIndex);
+ if (this.activePageIndex >= this.pageDivs.length) {
+ this.activePageIndex = this.pageDivs.length - 1;
+ }
+ }
+ break;
+ /*
+ END ENABLE PAGE ADD AND DELETE
+
+ case 'newpage':
if (this.pageDivs.length < 10) {
this.insertPage(this.activePageIndex, true);
}
@@ -382,9 +399,9 @@ var LauncherAssistant = Class.create({
var newAppDiv = $(newAppInfo.launchPointId);
Mojo.assert(newAppDiv !== undefined, "Application (%d) was inserted into the DOM but unable to be retrieved!", newAppInfo.launchPointId);
if (isNaN(this.kAppWidth) || isNaN(this.kAppHeight)) {
- this.kAppWidth = newAppDiv.getWidth();
- this.kAppHeight = newAppDiv.getHeight();
- this.kAppsPerRow = Math.round(this.kPageWidthNoMargin / this.kAppWidth);
+ this.kAppWidth = 55;
+ this.kAppHeight = 90;
+ this.kAppsPerRow = 5;
}

Mojo.listen(newAppDiv, Mojo.Event.tap, this.onAppTapped.bindAsEventListener(this));
@@ -498,7 +515,7 @@ var LauncherAssistant = Class.create({
/* determines the position of an app element at appIndex within a page */
calculateAppPosition: function(appIndex) {
return {
- left: (((appIndex % this.kAppsPerRow) * this.kAppWidth) + this.kPageMargin),
+ left: (((appIndex % this.kAppsPerRow) * this.kAppWidth)),
top: (Math.floor(appIndex/this.kAppsPerRow) * this.kAppHeight + this.kTopMargin)
};
},
Index: /usr/lib/luna/system/luna-applauncher/stylesheets/launcher.css
===================================================================
--- .orig/usr/lib/luna/system/luna-applauncher/stylesheets/launcher.css
+++ /usr/lib/luna/system/luna-applauncher/stylesheets/launcher.css
@@ -116,7 +116,7 @@ body.palm-default

.launcher_page .name {
position:absolute;
- top: 68px;
+ top: 48px;
width:100px;
height: 34px;
max-height: 34px;
@@ -125,7 +125,7 @@ body.palm-default
color:white;
text-align:center;
font-weight:bold;
- font-size: 14px;
+ font-size: 9px;
overflow: hidden;
text-overflow: ellipsis;
z-index:5;
@@ -148,8 +148,8 @@ body.palm-default
}

.draggable {
- width:64px;
- height:64px;
+ width:48px;
+ height:48px;
margin: 0 auto;
-webkit-user-drag: any;
-webkit-user-select: none;
@@ -192,8 +192,8 @@ body.palm-default

#app-icon {
float:left;
- width:64px;
- height:64px;
+ width:32px;
+ height:32px;
background: center center no-repeat;
}
</pre>

[[Image: 4pre_row.jpg|thumb|right]]
I noticed that this makes some of the apps with longer names run into each other. I fixed this by going into the stylesheet and modifying
<pre>
.launcher_page .name
left:12px;
width:80px;
</pre>
The values may be different for you, I am using 4 icons per row instead of 5.

For 5 per row you can use:
<pre>
.launcher_page .name
left: 20px;
width: 60px;
</pre>
This looks fairly center and none of the words run over each other.

Patch Launcher To Allow More Icons Per Row

2009-08-17T20:11:12Z

Epyon22:

{{template:patch}}
[[Image: 5by4Launcher.png|thumb|right]]

==Introduction==

'''THIS IS 1.1.0 SAFE, DO NOT TRY IT WITH ANY OTHER WEBOS VERSION'''

This patch allows you to have a 20 icon, 5x4 launcher page. It decreases icon size and text size, changes the apps per row, and moves the text closer to the icon. It also modifies where the page indicators and margins are a little.

==End Result==

The thumbnail image on the right shows launcher after the patch is applied.

==Patch Process==

If you are not familiar with the Webos-Internals patching process, you'll need to visit the [[Applying Patches|Applying Patches]] section of the wiki to know how to use the patch. After you have set up everything and are ready to download the patch, it is in the''' modifications''' repo under '''"luna/more_icons_per_row.patch"''' ===address forthcoming===

This patch also includes the patch to allow a user to add and remove additional launcher pages. You might have to remove that patch before applying this one.

==Patch Code==

<pre>
Index: /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
===================================================================
--- .orig/usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
+++ /usr/lib/luna/system/luna-applauncher/app/controllers/launcher-assistant.js
@@ -16,7 +16,7 @@ var LauncherAssistant = Class.create({
*/
kBottomFadeHeight: 0,

- kPageIndicatorSpacing: 6, /* spacing between each page indicator */
+ kPageIndicatorSpacing: 1, /* spacing between each page indicator */
kPageMargin: 10, /* 10 pixel margin on each side of a page */
kTopMargin: 12,
kPageWidthNoMargin: NaN,
@@ -30,8 +30,8 @@ var LauncherAssistant = Class.create({
visible: true,
label: $L('Launcher'),
items: [
- /*{ label: $L('New page'), command: 'newpage' },
- { label: $L('Delete page'), command: 'deletepage' },*/
+ { label: $L('New page'), command: 'newpage' },
+ { label: $L('Delete page'), command: 'deletepage' },
Mojo.Menu.editItem,
{ label: $L('List Apps...'), command: 'listapps' },
Mojo.Menu.helpItem
@@ -125,7 +125,24 @@ var LauncherAssistant = Class.create({
ApplicationService.launch(this.deviceInfo.id, this.deviceInfo.params);
break;
/*
- case 'newpage':
+ START ENABLE PAGE ADD AND DELETE */
+ case 'newpage':
+ if (this.pageDivs.length < 10) {
+ this.insertPage(this.activePageIndex, true);
+ }
+ break;
+ case 'deletepage':
+ if (this.pageDivs.length > 1) {
+ this.deletePage(this.activePageIndex);
+ if (this.activePageIndex >= this.pageDivs.length) {
+ this.activePageIndex = this.pageDivs.length - 1;
+ }
+ }
+ break;
+ /*
+ END ENABLE PAGE ADD AND DELETE
+
+ case 'newpage':
if (this.pageDivs.length < 10) {
this.insertPage(this.activePageIndex, true);
}
@@ -382,9 +399,9 @@ var LauncherAssistant = Class.create({
var newAppDiv = $(newAppInfo.launchPointId);
Mojo.assert(newAppDiv !== undefined, "Application (%d) was inserted into the DOM but unable to be retrieved!", newAppInfo.launchPointId);
if (isNaN(this.kAppWidth) || isNaN(this.kAppHeight)) {
- this.kAppWidth = newAppDiv.getWidth();
- this.kAppHeight = newAppDiv.getHeight();
- this.kAppsPerRow = Math.round(this.kPageWidthNoMargin / this.kAppWidth);
+ this.kAppWidth = 55;
+ this.kAppHeight = 90;
+ this.kAppsPerRow = 5;
}

Mojo.listen(newAppDiv, Mojo.Event.tap, this.onAppTapped.bindAsEventListener(this));
@@ -498,7 +515,7 @@ var LauncherAssistant = Class.create({
/* determines the position of an app element at appIndex within a page */
calculateAppPosition: function(appIndex) {
return {
- left: (((appIndex % this.kAppsPerRow) * this.kAppWidth) + this.kPageMargin),
+ left: (((appIndex % this.kAppsPerRow) * this.kAppWidth)),
top: (Math.floor(appIndex/this.kAppsPerRow) * this.kAppHeight + this.kTopMargin)
};
},
Index: /usr/lib/luna/system/luna-applauncher/stylesheets/launcher.css
===================================================================
--- .orig/usr/lib/luna/system/luna-applauncher/stylesheets/launcher.css
+++ /usr/lib/luna/system/luna-applauncher/stylesheets/launcher.css
@@ -116,7 +116,7 @@ body.palm-default

.launcher_page .name {
position:absolute;
- top: 68px;
+ top: 48px;
width:100px;
height: 34px;
max-height: 34px;
@@ -125,7 +125,7 @@ body.palm-default
color:white;
text-align:center;
font-weight:bold;
- font-size: 14px;
+ font-size: 9px;
overflow: hidden;
text-overflow: ellipsis;
z-index:5;
@@ -148,8 +148,8 @@ body.palm-default
}

.draggable {
- width:64px;
- height:64px;
+ width:48px;
+ height:48px;
margin: 0 auto;
-webkit-user-drag: any;
-webkit-user-select: none;
@@ -192,8 +192,8 @@ body.palm-default

#app-icon {
float:left;
- width:64px;
- height:64px;
+ width:32px;
+ height:32px;
background: center center no-repeat;
}
</pre>

[[Image: 4pre_row.jpg|thumb|right]]
I noticed that this makes some of the apps with longer names run into each other. I fixed this by going into the stylesheet and modifying
<pre>
.launcher_page .name
left:12px;
width:80px;
</pre>
The values may be different for you, I am using 4 icons per row instead of 5.

For 5 per row you can use:
<pre>
.launcher_page .name
left: 20px;
width: 60px;
</pre>
this looks fairly center and none of the words run over eachother

HamachiVPN

2009-08-03T01:06:48Z

Epyon22:

= Hamachi VPN for Palm Pre =

This document assumes you're familiar with the Hamachi VPN, specifically the linux version. It is geared towards a person wanting to "get it working" on the Pre. If you're not familiar, there are endless Googlable web pages that describe running Hamachi on desktop linux systems you can use for reference.

Become root:

<source lang="text">
sudo su
</source>

Make the filesystem writable:

<source lang="text">
mount -o remount,rw /
</source>

Download the hamachi binary to your pre via wget:

: '''Note:''' It is recommended that you use the nokia build, because it included the install script. Whereas the direct hamachi link would require that make be installed.

<source lang="text">
cd /opt/share
wget http://files.hamachi.cc/linux/nokia-770/hamachi-0.9.9.9-20-lnx-n770.tar.gz
</source>

Unpack the archive:
<source lang="text">
tar zxvf hamachi-0.9.9.9-20-lnx-n770.tar.gz
cd hamachi-n770-0.9.9.9-20
</source>

Hamachi depends on libcrypto.so.0.9.7. The Palm Pre has libcrypto.so.0.9.8 installed. I made a symlink, and it worked. So...
<source lang="text">
ln -s /usr/lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7
</source>

Edit the "install" script using your favorite editor (like vi) to change the installation locations.
Also fix line 7 or you'll get an error.

I changed it to:

<source lang="text">
HAMACHI_DST=/opt/bin
TUNCFG_DST=/opt/sbin

echo
echo Copying hamachi into $HAMACHI_DST ..
</source>

Then follow the instructions in the README under Quick Start, but basically:

<source lang="text">
./install
/opt/sbin/tuncfg
hamachi-init
hamachi start
hamachi login
hamachi set-nick <your nickname>
hamachi join <network>
hamachi go-online
</source>

== Hint ==

If you use Hamachi to connect to web services running on your machines at home or elsewhere, you might make your life easier by adding some entries to the /etc/hosts file. Then you can access your servers by name instead of having to use the Hamachi 5.x.x.x IP addresses.

A simple sample entry in /etc/hosts which would allow you to access your server "beaker" at 5.1.2.3 would be:
(Add your servers below the "castle" line.)
<source lang="text">
127.0.0.1 localhost.localdomain localhost
127.0.0.1 castle
5.1.2.3 beaker
</source>

When done, make the filesystem read-only again:
<source lang="text">
mount -o remount,ro /
</source>

== Ping Test ==

When you've got hamachi up, you can try pinging one of your servers.
<source lang="text">
root@castle:/var/home/root# ping beaker
PING beaker (5.1.2.3): 56 data bytes
64 bytes from 5.1.2.3: seq=0 ttl=128 time=5.493 ms
64 bytes from 5.1.2.3: seq=1 ttl=128 time=32.257 ms
64 bytes from 5.1.2.3: seq=2 ttl=128 time=56.976 ms
64 bytes from 5.1.2.3: seq=3 ttl=128 time=74.249 ms
</source>

== Sleep/Wake and Battery Impact ==
On first testing:
* When the device went to sleep, the VPN went down.
* When the device woke up, the VPN came back up and was pingable again.

This morning, while at my workstation, and with the Pre idle in my pocket, I noticed my Pre was available/pingable on Hamachi. I am not totally sure of what the long-term battery impact might be of running Hamachi on the Pre. I'm not yet sure if it keeps the device "awake" all the time, which clearly would drain the battery. I have push GMail IMAP going, so I assume there is some kind of connection either being periodically established or constantly maintained. But I don't know enough about the networking aspects to determine at this time whether running Hamachi all the time will negatively impact the battery. Feel free to message me if you learn anything.

Further Testing:
* With Hamachi running I would achive 12 hours of battery life on my pre
* Without Hamachi running after 12 hours I am sitting at 60% battery life

So to conclude running Hamachi all the time significantly decreases battery life in my situation. I personally would not recommend running Hamachi all the the time. I will later post up start and shutdown scripts (should be very simple I just need to write them for myself) that can be used through terminal when you need them.

== Upstart script ==
This script will start Hamachi up after a reboot.

Place the following script in /etc/event.d/hamachi

<source lang="text">
description "Hamachi VPN for WebOS"
version 1.0

# don't start until the WebOS finishes it's normal boot
# that way no delay is added to the GUI startup
start on stopped finish
stop on runlevel [!2]

console output

script
/opt/bin/hamachi -c /var/home/root/.hamachi start 2>&1 /var/home/root/hamachi.log
end script

pre-start script
/opt/sbin/tuncfg
end script
</source>

User talk:Eain

2009-07-29T19:49:27Z

Epyon22:

Hey your edit doesn't work because the straight linux pkg doesn't have the required install file or else you would have to use make. so i fixed it

[[User:Epyon22|Epyon22]] 19:49, 29 July 2009 (UTC)Epyon22

User talk:Eain

2009-07-29T19:49:10Z

Epyon22: New page: Hey your edit doesn't work because the straight linux pkg doesn't have the required install file or else you would have to use make. so i fixed it

Hey your edit doesn't work because the straight linux pkg doesn't have the required install file or else you would have to use make. so i fixed it

HamachiVPN

2009-07-29T19:42:18Z

Epyon22: /* Hamachi VPN for Palm Pre */

= Hamachi VPN for Palm Pre =

This document assumes you're familiar with the Hamachi VPN, specifically the linux version. It is geared towards a person wanting to "get it working" on the Pre. If you're not familiar, there are endless Googlable web pages that describe running Hamachi on desktop linux systems you can use for reference.

Become root:

<source lang="text">
sudo su
</source>

Make the filesystem writable:

<source lang="text">
mount -o remount,rw /
</source>

Download the hamachi binary to your pre via wget:

: Note: It is reccomended that you use the nokia build, because it included the install script. Whereas the direct hamachi link would require that make be installed.

<source lang="text">
cd /opt/share
wget http://files.hamachi.cc/linux/nokia-770/hamachi-0.9.9.9-20-lnx-n770.tar.gz
</source>

Unpack the archive:
<source lang="text">
tar zxvf hamachi-0.9.9.9-20-lnx-n770.tar.gz
cd hamachi-n770-0.9.9.9-20
</source>

Hamachi depends on libcrypto.so.0.9.7. The Palm Pre has libcrypto.so.0.9.8 installed. I made a symlink, and it worked. So...
<source lang="text">
ln -s /usr/lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7
</source>

Edit the "install" script using your favorite editor (like vi) to change the installation locations.
Also fix line 7 or you'll get an error.

I changed it to:

<source lang="text">
HAMACHI_DST=/opt/bin
TUNCFG_DST=/opt/sbin

echo
echo Copying hamachi into $HAMACHI_DST ..
</source>

Then follow the instructions in the README under Quick Start, but basically:

<source lang="text">
./install
/opt/sbin/tuncfg
hamachi-init
hamachi start
hamachi login
hamachi set-nick <your nickname>
hamachi join <network>
hamachi go-online
</source>

== Hint ==

If you use Hamachi to connect to web services running on your machines at home or elsewhere, you might make your life easier by adding some entries to the /etc/hosts file. Then you can access your servers by name instead of having to use the Hamachi 5.x.x.x IP addresses.

A simple sample entry in /etc/hosts which would allow you to access your server "beaker" at 5.1.2.3 would be:
(Add your servers below the "castle" line.)
<source lang="text">
127.0.0.1 localhost.localdomain localhost
127.0.0.1 castle
5.1.2.3 beaker
</source>

When done, make the filesystem read-only again:
<source lang="text">
mount -o remount,ro /
</source>

== Ping Test ==

When you've got hamachi up, you can try pinging one of your servers.
<source lang="text">
root@castle:/var/home/root# ping beaker
PING beaker (5.1.2.3): 56 data bytes
64 bytes from 5.1.2.3: seq=0 ttl=128 time=5.493 ms
64 bytes from 5.1.2.3: seq=1 ttl=128 time=32.257 ms
64 bytes from 5.1.2.3: seq=2 ttl=128 time=56.976 ms
64 bytes from 5.1.2.3: seq=3 ttl=128 time=74.249 ms
</source>

== Sleep/Wake and Battery Impact ==
On first testing:
* When the device went to sleep, the VPN went down.
* When the device woke up, the VPN came back up and was pingable again.

This morning, while at my workstation, and with the Pre idle in my pocket, I noticed my Pre was available/pingable on Hamachi. I am not totally sure of what the long-term battery impact might be of running Hamachi on the Pre. I'm not yet sure if it keeps the device "awake" all the time, which clearly would drain the battery. I have push GMail IMAP going, so I assume there is some kind of connection either being periodically established or constantly maintained. But I don't know enough about the networking aspects to determine at this time whether running Hamachi all the time will negatively impact the battery. Feel free to message me if you learn anything.

== Upstart script ==
This script will start Hamachi up after a reboot.

Place the following script in /etc/event.d/hamachi

<source lang="text">
description "Hamachi VPN for WebOS"
version 1.0

# don't start until the WebOS finishes it's normal boot
# that way no delay is added to the GUI startup
start on stopped finish
stop on runlevel [!2]

console output

script
/opt/bin/hamachi -c /var/home/root/.hamachi start 2>&1 /var/home/root/hamachi.log
end script

pre-start script
/opt/sbin/tuncfg
end script
</source>

HamachiVPN

2009-07-29T19:39:22Z

Epyon22: /* Hamachi VPN for Palm Pre */

= Hamachi VPN for Palm Pre =

This document assumes you're familiar with the Hamachi VPN, specifically the linux version. It is geared towards a person wanting to "get it working" on the Pre. If you're not familiar, there are endless Googlable web pages that describe running Hamachi on desktop linux systems you can use for reference.

Become root:

<source lang="text">
sudo su
</source>

Make the filesystem writable:

<source lang="text">
mount -o remount,rw /
</source>

Download the hamachi binary to your pre via wget:
<source lang="text">
cd /opt/share
wget http://files.hamachi.cc/linux/nokia-770/hamachi-0.9.9.9-20-lnx-n770.tar.gz
</source>

Unpack the archive:
<source lang="text">
tar zxvf hamachi-0.9.9.9-20-lnx-n770.tar.gz
cd hamachi-0.9.9.9-20-lnx
</source>

Hamachi depends on libcrypto.so.0.9.7. The Palm Pre has libcrypto.so.0.9.8 installed. I made a symlink, and it worked. So...
<source lang="text">
ln -s /usr/lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7
</source>

Edit the "install" script using your favorite editor (like vi) to change the installation locations.
Also fix line 7 or you'll get an error.

I changed it to:

<source lang="text">
HAMACHI_DST=/opt/bin
TUNCFG_DST=/opt/sbin

echo
echo Copying hamachi into $HAMACHI_DST ..
</source>

Then follow the instructions in the README under Quick Start, but basically:

<source lang="text">
./install
/opt/sbin/tuncfg
hamachi-init
hamachi start
hamachi login
hamachi set-nick <your nickname>
hamachi join <network>
hamachi go-online
</source>

== Hint ==

If you use Hamachi to connect to web services running on your machines at home or elsewhere, you might make your life easier by adding some entries to the /etc/hosts file. Then you can access your servers by name instead of having to use the Hamachi 5.x.x.x IP addresses.

A simple sample entry in /etc/hosts which would allow you to access your server "beaker" at 5.1.2.3 would be:
(Add your servers below the "castle" line.)
<source lang="text">
127.0.0.1 localhost.localdomain localhost
127.0.0.1 castle
5.1.2.3 beaker
</source>

When done, make the filesystem read-only again:
<source lang="text">
mount -o remount,ro /
</source>

== Ping Test ==

When you've got hamachi up, you can try pinging one of your servers.
<source lang="text">
root@castle:/var/home/root# ping beaker
PING beaker (5.1.2.3): 56 data bytes
64 bytes from 5.1.2.3: seq=0 ttl=128 time=5.493 ms
64 bytes from 5.1.2.3: seq=1 ttl=128 time=32.257 ms
64 bytes from 5.1.2.3: seq=2 ttl=128 time=56.976 ms
64 bytes from 5.1.2.3: seq=3 ttl=128 time=74.249 ms
</source>

== Sleep/Wake and Battery Impact ==
On first testing:
* When the device went to sleep, the VPN went down.
* When the device woke up, the VPN came back up and was pingable again.

This morning, while at my workstation, and with the Pre idle in my pocket, I noticed my Pre was available/pingable on Hamachi. I am not totally sure of what the long-term battery impact might be of running Hamachi on the Pre. I'm not yet sure if it keeps the device "awake" all the time, which clearly would drain the battery. I have push GMail IMAP going, so I assume there is some kind of connection either being periodically established or constantly maintained. But I don't know enough about the networking aspects to determine at this time whether running Hamachi all the time will negatively impact the battery. Feel free to message me if you learn anything.

== Upstart script ==
This script will start Hamachi up after a reboot.

Place the following script in /etc/event.d/hamachi

<source lang="text">
description "Hamachi VPN for WebOS"
version 1.0

# don't start until the WebOS finishes it's normal boot
# that way no delay is added to the GUI startup
start on stopped finish
stop on runlevel [!2]

console output

script
/opt/bin/hamachi -c /var/home/root/.hamachi start 2>&1 /var/home/root/hamachi.log
end script

pre-start script
/opt/sbin/tuncfg
end script
</source>

== Edit ==

Modified it to the previous wget line for the nokia build. I did this because it included the install script. Whereas the direct hamachi link you would need make installed.
--Epyon22

Application:Terminal

2009-07-28T04:11:35Z

Epyon22:

{{application
|name=Terminal
|type=Linux
|version=Version: Pre-Alpha 0.1.4 (7/27/2009) (fourth public release)
|tag=Utilities
|screenshot=Application_Terminal.jpg
|description=

== Status ==

This is early-alpha software. Consider yourself lucky if it works at all. Many people have put many hours of hard work in to get just this far - respect that effort when making comments and suggestions.

== License ==

Please be aware that org.webosinternals.terminal and x-webosinternals-termplugin are licensed under the GPLv2.

They cannot be used by a closed source application. If you want to use them in a non-GPLv2 but otherwise open source application, please contact the authors.

=== Operating notes ===

Non-obvious keys:

{{{!}} border="1" cellpadding="4"
{{!}}Desired
{{!}}On Pre
{{!}}-
{{!}}Up
{{!}}Gesture area - 2
{{!}}-
{{!}}Left
{{!}}Gesture area - 4
{{!}}-
{{!}}Right
{{!}}Gesture area - 6
{{!}}-
{{!}}Down
{{!}}Gesture area - 8
{{!}}-
{{!}}Control
{{!}}Sym
{{!}}-
{{!}}Esc
{{!}}Orange-Space
{{!}}-
{{!}}Tab
{{!}}Sym-I
{{!}}}

* (Sym is Control and Control I is the standard tab code)

Rotating the pre will take the terminal to landscape mode. The keyboard will not rotate with you. Attempting to physically force the keyboard to rotate to the proper orientation for landscape mode is known to bork a Pre. :)

Support for both "linux" and "vt100" term types should now be supported, so an export TERM line should no longer be needed. If you find your screen filling with gibberish that looks like ANSI codes, however, make sure you're using 0.1.4 or later version, and report here or in the IRC channel what you were running in the terminal that caused the issue.

If you do see odd behavior, you can force the more compatible vt100 terminal type by typing:

export TERM=vt100

(followed by enter) Note that the case of that command is important.

=== Recent enhancements ===

* Prompt for login to enhance security / protect against rogue applications embedding termplugin (more convenient and equally secure method being developed for future release)

* Color!

* Arrow keys, hold a finger on the gesture area so that the white LED lights up, and use the numbers area as if it were a direction pad (ie 2, 4, 6, 8, correspond to up, left, right, down, respectively)

* Several performance enhancements

* Screen scrolls automagically (no more flicking to keep up)

* Comma / underscore key bugs fixed

=== Known bugs ===

Remember, this is early alpha software. You're lucky it works at all.

As of 0.1.4 (7/27/2009), all reported bugs have been fixed. That does not mean that there aren't plenty of bugs still around. Please find them and report them here.

Some limitations: Many keys are not implemented. We're working on it, maybe even as you read this. :)

Y and U:

If you run the terminal in the emulator provided with the Palm webOS SDK 1.1, be aware that a bug in the emulator causes the keys for U and Y to both send the raw keycode for the button Y. You can see the same result in Device Info, More Info, Preferences, Interactive Tests, Hardware Buttons. This is not a bug in the Terminal application.

* Doesn't display a return in nano properly unless the screen is rotated
* No action after running exit in session should restart and ask for a new login

== Installation ==

Do not stray from or vary these instructions. If you don't do it all, in precisely the right order, with zero mistakes, it's not going to work. Copy & Paste will be your friend.

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

<source lang="text">
mkdir -p /var/etc/ipkg/
ln -s /etc/ipkg/arch.conf /var/etc/ipkg/
echo "src/gz all http://ipkg.preware.org/feeds/preware/all" > /var/etc/ipkg/preware.conf
</source>

If you are on the Pre, type:

<source lang="text">
echo "src/gz armv7 http://ipkg.preware.org/feeds/preware/armv7" >> /var/etc/ipkg/preware.conf
</source>

If you are on the Emulator, type:

<source lang="text">
echo "src/gz i686 http://ipkg.preware.org/feeds/preware/i686" >> /var/etc/ipkg/preware.conf
</source>

Then type:

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var install x-webosinternals-termplugin
ln -s /var/usr/lib/BrowserPlugins/termplugin.so /usr/lib/BrowserPlugins/
/usr/bin/ipkg -o /var install org.webosinternals.terminal
</source>

Then refresh the GUI to show your new app:

<source lang="text">
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</source>

If you performed an upgrade and aren't seeing the changes, restart the GUI service:

<source lang="text">
initctl stop LunaSysMgr && initctl start LunaSysMgr
</source>

If the above two fail to show the results you're expecting, reboot the device.

== Update ==

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

From a shell:

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var upgrade
reboot
</source>

== Other PreWare Applications ==

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

Note that you can use the same commands to install other applications from PreWare:

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var list
/usr/bin/ipkg -o /var install <package> # choose a package from the list
/usr/bin/ipkg -o /var remove <package>
</source>

== Removal ==

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

<source lang="text">
rm /usr/lib/BrowserPlugins/termplugin.so
/usr/bin/ipkg -o /var remove org.webosinternals.terminal
/usr/bin/ipkg -o /var remove x-webosinternals-termplugin
rm /var/etc/ipkg/preware.conf
</source>

Then refresh the GUI to remove the icon:

<source lang="text">
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</source>

If you aren't seeing the icon removed, restart the GUI service:

<source lang="text">
initctl stop LunaSysMgr && initctl start LunaSysMgr
</source>

If the above two fail to show the results you're expecting, reboot the device.
}}

Application:Terminal

2009-07-28T04:09:01Z

Epyon22:

{{application
|name=Terminal
|type=Linux
|version=Version: Pre-Alpha 0.1.4 (7/27/2009) (fourth public release)
|tag=Utilities
|screenshot=Application_Terminal.jpg
|description=

== Status ==

This is early-alpha software. Consider yourself lucky if it works at all. Many people have put many hours of hard work in to get just this far - respect that effort when making comments and suggestions.

== License ==

Please be aware that org.webosinternals.terminal and x-webosinternals-termplugin are licensed under the GPLv2.

They cannot be used by a closed source application. If you want to use them in a non-GPLv2 but otherwise open source application, please contact the authors.

=== Operating notes ===

Non-obvious keys:

{{{!}} border="1" cellpadding="4"
{{!}}Desired
{{!}}On Pre
{{!}}-
{{!}}Up
{{!}}Gesture area - 2
{{!}}-
{{!}}Left
{{!}}Gesture area - 4
{{!}}-
{{!}}Right
{{!}}Gesture area - 6
{{!}}-
{{!}}Down
{{!}}Gesture area - 8
{{!}}-
{{!}}Control
{{!}}Sym
{{!}}-
{{!}}Esc
{{!}}Orange-Space
{{!}}-
{{!}}Tab
{{!}}Sym-I
{{!}}}

* (Sym is Control and Control I is the standard tab code)

Rotating the pre will take the terminal to landscape mode. The keyboard will not rotate with you. Attempting to physically force the keyboard to rotate to the proper orientation for landscape mode is known to bork a Pre. :)

Support for both "linux" and "vt100" term types should now be supported, so an export TERM line should no longer be needed. If you find your screen filling with gibberish that looks like ANSI codes, however, make sure you're using 0.1.4 or later version, and report here or in the IRC channel what you were running in the terminal that caused the issue.

If you do see odd behavior, you can force the more compatible vt100 terminal type by typing:

export TERM=vt100

(followed by enter) Note that the case of that command is important.

=== Recent enhancements ===

* Prompt for login to enhance security / protect against rogue applications embedding termplugin (more convenient and equally secure method being developed for future release)

* Color!

* Arrow keys, hold a finger on the gesture area so that the white LED lights up, and use the numbers area as if it were a direction pad (ie 2, 4, 6, 8, correspond to up, left, right, down, respectively)

* Several performance enhancements

* Screen scrolls automagically (no more flicking to keep up)

* Comma / underscore key bugs fixed

=== Known bugs ===

Remember, this is early alpha software. You're lucky it works at all.

As of 0.1.4 (7/27/2009), all reported bugs have been fixed. That does not mean that there aren't plenty of bugs still around. Please find them and report them here.

Some limitations: Many keys are not implemented. We're working on it, maybe even as you read this. :)

Y and U:

If you run the terminal in the emulator provided with the Palm webOS SDK 1.1, be aware that a bug in the emulator causes the keys for U and Y to both send the raw keycode for the button Y. You can see the same result in Device Info, More Info, Preferences, Interactive Tests, Hardware Buttons. This is not a bug in the Terminal application.

- Doesn't display a return in nano properly unless the screen is rotated
- No action after running exit in session should restart and ask for a new login

== Installation ==

Do not stray from or vary these instructions. If you don't do it all, in precisely the right order, with zero mistakes, it's not going to work. Copy & Paste will be your friend.

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

<source lang="text">
mkdir -p /var/etc/ipkg/
ln -s /etc/ipkg/arch.conf /var/etc/ipkg/
echo "src/gz all http://ipkg.preware.org/feeds/preware/all" > /var/etc/ipkg/preware.conf
</source>

If you are on the Pre, type:

<source lang="text">
echo "src/gz armv7 http://ipkg.preware.org/feeds/preware/armv7" >> /var/etc/ipkg/preware.conf
</source>

If you are on the Emulator, type:

<source lang="text">
echo "src/gz i686 http://ipkg.preware.org/feeds/preware/i686" >> /var/etc/ipkg/preware.conf
</source>

Then type:

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var install x-webosinternals-termplugin
ln -s /var/usr/lib/BrowserPlugins/termplugin.so /usr/lib/BrowserPlugins/
/usr/bin/ipkg -o /var install org.webosinternals.terminal
</source>

Then refresh the GUI to show your new app:

<source lang="text">
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</source>

If you performed an upgrade and aren't seeing the changes, restart the GUI service:

<source lang="text">
initctl stop LunaSysMgr && initctl start LunaSysMgr
</source>

If the above two fail to show the results you're expecting, reboot the device.

== Update ==

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

From a shell:

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var upgrade
reboot
</source>

== Other PreWare Applications ==

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

Note that you can use the same commands to install other applications from PreWare:

<source lang="text">
/usr/bin/ipkg -o /var update
/usr/bin/ipkg -o /var list
/usr/bin/ipkg -o /var install <package> # choose a package from the list
/usr/bin/ipkg -o /var remove <package>
</source>

== Removal ==

'''You need to be logged in as root with a writeable filesystem.''' Instructions for both those things can be found elsewhere on this wiki.

<source lang="text">
rm /usr/lib/BrowserPlugins/termplugin.so
/usr/bin/ipkg -o /var remove org.webosinternals.terminal
/usr/bin/ipkg -o /var remove x-webosinternals-termplugin
rm /var/etc/ipkg/preware.conf
</source>

Then refresh the GUI to remove the icon:

<source lang="text">
luna-send -n 1 palm://com.palm.applicationManager/rescan {}
</source>

If you aren't seeing the icon removed, restart the GUI service:

<source lang="text">
initctl stop LunaSysMgr && initctl start LunaSysMgr
</source>

If the above two fail to show the results you're expecting, reboot the device.
}}