WebOS Internals - User contributions [en]

MojoSDK on Fedora

2011-01-11T20:14:05Z

Robertjw: Updated links and comments for Fedora 14

==Installing the Mojo SDK on Fedora==
This guide describes how to install the Mojo SDK and Novacom Debian files provided by Palm on a Fedora system. The procedure described is an extension of the post by mtk on the TreoCentral forums[http://discussion.treocentral.com/web-os-development/197540-mojo-sdk-novacom-packages-easy-install-hand-fedora.html]. It is current as of Fedora 14 and palm-sdk_1.4.5-svn307799-sdk1457-pho465.

Commands shown in this guide use the standard notation for indicating which can be run as the normal user and which must be run as root: commands preceded by "#" are to be run as root, whereas those preceded by "$" are to be run as the normal user.

===Install VirtualBox===
VirtualBox is available from [http://rpmfusion.org/ RPM Fusion]. Install VirtualBox and load the kernel modules:
# yum install VirtualBox-OSE
# /etc/sysconfig/modules/VirtualBox-OSE.modules

===Install the Mojo SDK===
Download the Ubuntu deb package of the Mojo SDK from [http://developer.palm.com/index.php?option=com_content&view=article&id=1585 the Official PalmSDK Linux Page]. deb files are simple archives that can be extracted using ar:
$ ar xv palm-sdk_1.4.5-svn307799-sdk1457-pho465_i386.deb

Extract the contents of data.tar.gz and move them to their respective locations in your filesystem:
$ tar -zxvf data.tar.gz
# mv opt/PalmSDK /opt/.
# mv usr/local/bin/* /usr/local/bin/.
# mv usr/share/doc/palm-sdk /usr/share/doc/.

Extract the contents of control.tar.gz and run the post-install script:
$ tar -zxvf control.tar.gz
# ./postinst

Optionally clean up the extracted files:
$ rm -fr debian-binary data.tar.gz control.tar.gz opt/ usr/ control md5sums postinst

===Install Novacom===
The installation of the Novacom tool is almost identical to that of the Mojo SDK. Start by downloading the Ubuntu deb package of from [http://developer.palm.com/index.php?option=com_content&view=article&id=1585 the Official PalmSDK Linux Page].

Extract the archive:
$ ar xv palm-novacom_1.0.46_i386.deb

Extract the contents data.tar.gz and move them to their respective locations in your filesystem:
$ tar -zxvf data.tar.gz
# mv opt/Palm /opt/.
# mv usr/local/bin/* /usr/local/bin/.
# mv usr/share/doc/palm-novacom /usr/share/doc/.

'''Note:''' If you are using Fedora 64bit, You'll need to install the 32bit version of libusb for the Novacom driver to work.
yum install libusb.i686

Extract the contents of control.tar.gz and run the post-install script:
$ tar -zxvf control.tar.gz
# ./postinst

Optionally clean up the extracted files:
$ rm -fr debian-binary data.tar.gz control.tar.gz opt/ usr/ control md5sums postinst prerm postrm

===Run the Mojo SDK===
The Mojo SDK should now be installed successfully. The first launch will load it into the VirtualBox environment. It can be launched from the command line:
$ palm-emulator

===Other Notes===
For development, using Eclipse and the plugins for Mojo are strongly recommended. Installation instructions of these plugins can be found at [http://developer.palm.com/index.php?option=com_content&view=article&id=1639 the Official Palm Eclipse plugin Installation Guide]

==Install Mojo SDK on Fedora 11 (Legacy Instructions)==
'''Note:''' These instructions provide an alternate method of installing the Mojo SDK on Fedora. These are more involved and therefore might not be as easy as the previous instructions. They are currently left here for historical reasons but may be removed in the future.
* Install VirtualBox RPM package available at:
[http://www.virtualbox.org/wiki/Linux_Downloads VirtualBox Linux Downloads]

''NOTE: If you're running Fedora 64 bit, get the AMD64 version. ( Even if you have an Intel Processor ).

* Install the RPM:
<pre><nowiki>rpm -ivh VirtualBox-<version>_fedora11-1.<platform>.rpm</nowiki></pre>

* Download the Ubuntu deb package of the Mojo SDK from:
[http://developer.palm.com/index.php?option=com_content&view=article&id=1585 the Official PalmSDK Linux Page]

* Download 'alien' package conversion tool:
[http://packages.debian.org/unstable/source/alien Debian Alien utility]

''You will need RPM building packages installed for the following method:
* Build an RPM of alien and install it:
<pre><nowiki>rpmbuild -tb alien_<version>.tar.gz
rpm -ivh ~/rpmbuild/RPMS/noarch/alien-<version>.rpm</nowiki></pre>

''If rpmbuild gives an error similar to:
error: File /download/pre/alien_8.77.tar.gz: No such file or directory

You'll need to extract the archive manually and edit the alien.spec file. Inside that file, find all instances of the old version number ( in my case 8.77 ) and replace it with the version number of the file you downloaded. ( in my case, 8.78 ). Once this is done, regenerate the tar.gz file with the following syntax:
<pre><nowiki>tar -czf alien_8.78.tar.gz alien</nowiki></pre>

''Once this completes, then build and install the RPM as above.

* Use Alien to change the .deb file into a .tgz archive (the RPM feature of alien didn't work for me):
<pre><nowiki>alien -tc palm_mojo_sdk-Ubuntu-<version>.deb</nowiki></pre>

Alien should report that the .tgz version is generated.

* Extract the .tgz version:
<pre><nowiki>mkdir tmp
cd tmp
tar -xzf ../palm-sdk-<version>.tgz</nowiki></pre>

* Copy the extracted files into place:
<pre><nowiki>cp -a opt/* /opt
cp -a usr/* /usr</nowiki></pre>

* Run the installation script:
<pre><nowiki>install/doinst.sh</nowiki></pre>

The script above should add a few entries into your /etc/hosts file.

* Download the Novacom linux drivers linked on this page:
[http://www.webos-internals.org/wiki/Installing_novaterm_on_ubuntu_64-bit Palm Novacom Linux Driver Wiki Page]

* This too will be a .deb. You will convert and install it the same way you did the SDK:
<pre><nowiki>alien -tc palm-novacom_<version>_i386.deb
mkdir novacom
cd novacom
tar -xzf ../palm-novacom-<version>.tgz
cd novacom
cp -a opt/* /opt
cp -a usr/* /usr</nowiki></pre>

''NOTE: If you are using Fedora 64bit, You'll need to install the 32bit version of libusb for the novacom driver to work.
<pre><nowiki>yum install libusb.i586</nowiki></pre>

* Copy the novacomd-upstart script into place:
<pre><nowiki>cp /opt/Palm/novacom/novacomd-upstart /etc/event.d/palm-novacomd</nowiki></pre>

* Start the novacomd driver:
<pre><nowiki>start palm-novacomd</nowiki></pre>

* As your normal user account, launch the emulator. The first launch will install it into VirtualBox.
<pre><nowiki>/opt/PalmSDK/Current/bin/palm-emulator</nowiki></pre>

'''For development, you should strongly consider using Eclipse and the plugins for Mojo. Installation instructions of these plugins can be found at:
[http://developer.palm.com/index.php?option=com_content&view=article&id=1639 Official Palm Eclipse plugin Installation Guide]

MojoSDK on Fedora

2011-01-11T19:39:55Z

Robertjw: Updated for Fedora 14

==Installing the Mojo SDK on Fedora==
This guide describes how to install the Mojo SDK and Novacom Debian files provided by Palm on a Fedora system. The procedure described is an extension of the post by mtk on the TreoCentral forums[http://discussion.treocentral.com/web-os-development/197540-mojo-sdk-novacom-packages-easy-install-hand-fedora.html]. It is current as of Fedora 12 and palm-sdk 1.3.1-svn222348-sdk100-pho314.

Commands shown in this guide use the standard notation for indicating which can be run as the normal user and which must be run as root: commands preceded by "#" are to be run as root, whereas those preceded by "$" are to be run as the normal user.

===Install VirtualBox===
VirtualBox is available from [http://rpmfusion.org/ RPM Fusion]. Install VirtualBox and load the kernel modules:
# yum install VirtualBox-OSE
# /etc/sysconfig/modules/VirtualBox-OSE.modules

===Install the Mojo SDK===
Download the Ubuntu deb package of the Mojo SDK from [http://developer.palm.com/index.php?option=com_sdkdownload&view=home the Official PalmSDK Page]. deb files are simple archives that can be extracted using ar:
$ ar xv palm-sdk_1.3.1-svn222348-sdk100-pho314_i386.deb

Extract the contents of data.tar.gz and move them to their respective locations in your filesystem:
$ tar -zxvf data.tar.gz
# mv opt/PalmSDK /opt/.
# mv usr/local/bin/* /usr/local/bin/.
# mv usr/share/doc/palm-sdk /usr/share/doc/.

Extract the contents of control.tar.gz and run the post-install script:
$ tar -zxvf control.tar.gz
# ./postinst

Optionally clean up the extracted files:
$ rm -fr debian-binary data.tar.gz control.tar.gz opt/ usr/ control md5sums postinst

===Install Novacom===
The installation of the Novacom tool is almost identical to that of the Mojo SDK. Start by downloading the Ubuntu deb package of from [http://developer.palm.com/index.php?option=com_sdkdownload&view=home the Official PalmSDK Page]. (Or get the 1.4.5.465 version from [http://cdn.downloads.palm.com/sdkdownloads/1.4.5.465/sdkBinaries/palm-novacom_1.0.56_i386.deb here]). This procedure has been verified on Fedora 14.

Extract the archive:
$ ar xv palm-novacom_1.0.56_i386.deb

Extract the contents data.tar.gz and move them to their respective locations in your filesystem:
$ tar -zxvf data.tar.gz
# mv opt/Palm /opt/.
# mv usr/local/bin/* /usr/local/bin/.
# mv usr/share/doc/palm-novacom /usr/share/doc/.

'''Note:''' If you are using Fedora 64bit, You'll need to install the 32bit version of libusb for the Novacom driver to work.
yum install libusb.i686

Extract the contents of control.tar.gz and run the post-install script:
$ tar -zxvf control.tar.gz
# ./postinst

Optionally clean up the extracted files:
$ rm -fr debian-binary data.tar.gz control.tar.gz opt/ usr/ control md5sums postinst prerm postrm

===Run the Mojo SDK===
The Mojo SDK should now be installed successfully. The first launch will load it into the VirtualBox environment. It can be launched from the command line:
$ palm-emulator

===Other Notes===
For development, using Eclipse and the plugins for Mojo are strongly recommended. Installation instructions of these plugins can be found at [http://developer.palm.com/index.php?option=com_content&view=article&id=1639 the Official Palm Eclipse plugin Installation Guide]

==Install Mojo SDK on Fedora 11 (Legacy Instructions)==
'''Note:''' These instructions provide an alternate method of installing the Mojo SDK on Fedora. These are more involved and therefore might not be as easy as the previous instructions. They are currently left here for historical reasons but may be removed in the future.
* Install VirtualBox RPM package available at:
[http://www.virtualbox.org/wiki/Linux_Downloads VirtualBox Linux Downloads]

''NOTE: If you're running Fedora 64 bit, get the AMD64 version. ( Even if you have an Intel Processor ).

* Install the RPM:
<pre><nowiki>rpm -ivh VirtualBox-<version>_fedora11-1.<platform>.rpm</nowiki></pre>

* Download the Ubuntu deb package of the Mojo SDK from:
[http://developer.palm.com/index.php?option=com_sdkdownload&view=home Official PalmSDK Page]

* Download 'alien' package conversion tool:
[http://packages.debian.org/unstable/source/alien Debian Alien utility]

''You will need RPM building packages installed for the following method:
* Build an RPM of alien and install it:
<pre><nowiki>rpmbuild -tb alien_<version>.tar.gz
rpm -ivh ~/rpmbuild/RPMS/noarch/alien-<version>.rpm</nowiki></pre>

''If rpmbuild gives an error similar to:
error: File /download/pre/alien_8.77.tar.gz: No such file or directory

You'll need to extract the archive manually and edit the alien.spec file. Inside that file, find all instances of the old version number ( in my case 8.77 ) and replace it with the version number of the file you downloaded. ( in my case, 8.78 ). Once this is done, regenerate the tar.gz file with the following syntax:
<pre><nowiki>tar -czf alien_8.78.tar.gz alien</nowiki></pre>

''Once this completes, then build and install the RPM as above.

* Use Alien to change the .deb file into a .tgz archive (the RPM feature of alien didn't work for me):
<pre><nowiki>alien -tc palm_mojo_sdk-Ubuntu-<version>.deb</nowiki></pre>

Alien should report that the .tgz version is generated.

* Extract the .tgz version:
<pre><nowiki>mkdir tmp
cd tmp
tar -xzf ../palm-sdk-<version>.tgz</nowiki></pre>

* Copy the extracted files into place:
<pre><nowiki>cp -a opt/* /opt
cp -a usr/* /usr</nowiki></pre>

* Run the installation script:
<pre><nowiki>install/doinst.sh</nowiki></pre>

The script above should add a few entries into your /etc/hosts file.

* Download the Novacom linux drivers linked on this page:
[http://www.webos-internals.org/wiki/Installing_novaterm_on_ubuntu_64-bit Palm Novacom Linux Driver Wiki Page]

* This too will be a .deb. You will convert and install it the same way you did the SDK:
<pre><nowiki>alien -tc palm-novacom_<version>_i386.deb
mkdir novacom
cd novacom
tar -xzf ../palm-novacom-<version>.tgz
cd novacom
cp -a opt/* /opt
cp -a usr/* /usr</nowiki></pre>

''NOTE: If you are using Fedora 64bit, You'll need to install the 32bit version of libusb for the novacom driver to work.
<pre><nowiki>yum install libusb.i586</nowiki></pre>

* Copy the novacomd-upstart script into place:
<pre><nowiki>cp /opt/Palm/novacom/novacomd-upstart /etc/event.d/palm-novacomd</nowiki></pre>

* Start the novacomd driver:
<pre><nowiki>start palm-novacomd</nowiki></pre>

* As your normal user account, launch the emulator. The first launch will install it into VirtualBox.
<pre><nowiki>/opt/PalmSDK/Current/bin/palm-emulator</nowiki></pre>

'''For development, you should strongly consider using Eclipse and the plugins for Mojo. Installation instructions of these plugins can be found at:
[http://developer.palm.com/index.php?option=com_content&view=article&id=1639 Official Palm Eclipse plugin Installation Guide]

WLAN

2009-11-16T16:45:50Z

Robertjw: /* Information about a Linux Kernel module */

= WLAN / WIFI=

== Marvell 88W8686 chipset (connected over SDIO) ==

* http://i.cmpnet.com/eetimes/eedesign/2009/image5_060709.jpg

=== Information about a Linux Kernel module ===
modinfo sd8xxx

filename: /lib/modules/2.6.24-palm-joplin-3430/kernel/net/wifi/sd8xxx.ko
license: GPL
author: Marvell International Ltd.
description: M-WLAN Driver
srcversion: 533BB7E5866E52F63B9ACCB
depends:
vermagic: 2.6.24-palm-joplin-3430 mod_unload ARMv7
parm: param_sd_slot_selector:int
parm: param_sdio_bus_width:int
parm: param_use_sdio_irq:int
parm: helper_name:charp
parm: fw_name:charp
parm: mfgmode:int

The sd8xxx driver is open source (although it requires proprietary firmware) and available under the GPL.
But why is it not on palm's open source packages site? Where is the source?
Didn't find it under http://opensource.palm.com/1.1.3/index.html

The original Marvell GPL sources are published in this download: http://www.marvell.com/drivers/driverDisplay.do?driverId=203 however the palm modifications to these sources do not appear to be published.

=== Exploring the /proc/net/wlan===
cat /proc/net/wlan/info

driver_name = "wlan"
driver_version = sd8686-9.15.14-26409.p62-(FP4)
InterfaceName="eth0"
...

=== Exploring Kernel configuration ===
cat /boot/config-2.6.24-palm-joplin-3430

[...]
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
# CONFIG_LIBERTAS is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_HOSTAP is not set
[...]

CONFIG_LIBERTAS is not set ???

==libertas==
* http://wireless.kernel.org/en/users/Drivers/libertas
* http://lists.infradead.org/pipermail/libertas-dev/
Why don't they use libertas ???

==Firmware==

md5sum /lib/firmware/*.bin

2a4d8f4df198ce949c350df5674f4ac6 /lib/firmware/helper_sd.bin
83006642f0ae4d6e9af89f6c852327c2 /lib/firmware/mfg_sd8686.bin
261d6ed255f2cc9f5bad014b2234b8cd /lib/firmware/sd8686.bin

Firmware from: http://www.marvell.com/drivers/driverDisplay.do?driverId=203

md5sum FwImage/*.bin

2a4d8f4df198ce949c350df5674f4ac6 FwImage/helper_sd.bin
3025de2a1ed575fd691958d7da341d8b FwImage/sd8686.bin

WLAN

2009-11-16T16:26:56Z

Robertjw: /* Information about a Linux Kernel module */

= WLAN / WIFI=

== Marvell 88W8686 chipset (connected over SDIO) ==

* http://i.cmpnet.com/eetimes/eedesign/2009/image5_060709.jpg

=== Information about a Linux Kernel module ===
modinfo sd8xxx

filename: /lib/modules/2.6.24-palm-joplin-3430/kernel/net/wifi/sd8xxx.ko
license: GPL
author: Marvell International Ltd.
description: M-WLAN Driver
srcversion: 533BB7E5866E52F63B9ACCB
depends:
vermagic: 2.6.24-palm-joplin-3430 mod_unload ARMv7
parm: param_sd_slot_selector:int
parm: param_sdio_bus_width:int
parm: param_use_sdio_irq:int
parm: helper_name:charp
parm: fw_name:charp
parm: mfgmode:int

The sd8xxx driver is open source (although it requires proprietary firmware) and available under the GPL.
But why is it not on palm's open source packages site? Where is the source?
Didn't find it under http://opensource.palm.com/1.1.3/index.html

=== Exploring the /proc/net/wlan===
cat /proc/net/wlan/info

driver_name = "wlan"
driver_version = sd8686-9.15.14-26409.p62-(FP4)
InterfaceName="eth0"
...

=== Exploring Kernel configuration ===
cat /boot/config-2.6.24-palm-joplin-3430

[...]
#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
CONFIG_WLAN_80211=y
# CONFIG_LIBERTAS is not set
# CONFIG_USB_ZD1201 is not set
# CONFIG_HOSTAP is not set
[...]

CONFIG_LIBERTAS is not set ???

==libertas==
* http://wireless.kernel.org/en/users/Drivers/libertas
* http://lists.infradead.org/pipermail/libertas-dev/
Why don't they use libertas ???

==Firmware==

md5sum /lib/firmware/*.bin

2a4d8f4df198ce949c350df5674f4ac6 /lib/firmware/helper_sd.bin
83006642f0ae4d6e9af89f6c852327c2 /lib/firmware/mfg_sd8686.bin
261d6ed255f2cc9f5bad014b2234b8cd /lib/firmware/sd8686.bin

Firmware from: http://www.marvell.com/drivers/driverDisplay.do?driverId=203

md5sum FwImage/*.bin

2a4d8f4df198ce949c350df5674f4ac6 FwImage/helper_sd.bin
3025de2a1ed575fd691958d7da341d8b FwImage/sd8686.bin

Research Pre GSM Modem Protocol

2009-11-10T22:08:44Z

Robertjw: /* Escaping */

Here we are collecting informations about the modem protocol. At the moment all the research is done on the european UMTS version of the Palm Pre. The CDMA version is likely to be pretty similar to the UMTS variant with regards to the protocol.

What we are doing to get used to the protocol is to strace the different applications that talk to the modem and log everything that goes over /dev/modemuart to the actual modem. From this wire protocol traces we are working backwards to the actual protocol and packet format.

=== Packet Start ===

A new packet starts with: '''0xFA''' (This may be an address instead as rfc1662 uses only one flag for frame separation).

As we found out that the CRC is calculated even over the flag '''0xFA''' and with assuming that the basic for the protocol is HDLC we can say that 0xFA is not the starting flag of the frame. It should be an adress if we have a real implemenation of HDLC that follows the rfc.

=== Packet End ===

A packet ends with: '''0x7E'''

=== Escaping ===

For the packet end marker there is an escaping sequence inside the packet. It is used '''0x7D 0x5E''' instead. Therefore '''0x7D''' is escaped as '''0x7D 0x5D''' as well.

=== Header ===

No informations about the header format have been gathered yet.

=== Payload ===

No informations about the payload format have been gathered yet.

=== Checksum ===

The last two bytes before the packet ending marker are a CRC16-FCS checksum. (See rfc1662 for polynom and table)

=== Similarity to RFC1662 ===

The usage of CRC-16-FCS but even more the frame boundary packet as well as the escaping for it looks similar to what we found about this protocol. Even a grep -i HDLC over the binary firmware image reports the usage of PPP and HDLC as communication protocol format. So we can be almost sureley that HDLC+PPP is used.

http://tools.ietf.org/html/rfc1662

=== Identified byte sequences ===
* Sync Message: 0xfa 0x10 0x0
* Sync Response Message: 0xfa 0x30 0x0
* Configuration Message: 0xfa 0x30 0x00 0x1
* Empty Configuration Message: 0xfa 0x40 0x0
* Configuration Response Message: 0xfa 0x40 0x0
* Acknowledge Message: 0xfa 0x50 0x0
* SIM PIN on startup is sent with: 0xfa 0x60 0xe3 0x0f 0x0e 0x00 0x13 0x00 0x00 0x00 0x00 <4 ASCII digits> 0x00 0x00 0x00 0x00 0x00
* SIM PIN acknowledgement from modem: 0xfa 0x50 0x0f

=== GPS ===
The [[GPS]] receiver is part of the modem in Palm Pre and all data received and sent related to location goes over the same port using the same frame coding as GSM. GPS functionality can not be enabled (at least not using the Palm-provided drivers) until modem radio is enabled and seemingly until the modem successfully registers to the network.

Tracing the data sent over /dev/modemuart the following hostnames can be seen being sent from the OS to the modem chip:
xtra1.gpsonextra.net, xtra2.gpsonextra.net, xtra3.gpsonextra.net

They point to the RX Network's company website (rxnetwork.ca) that claims to provide better geolocation by combining GPS, wifi signals, GSM CellID and live reports downloaded over GPRS. The modem downloads the following files:
http://xtra1.gpsonextra.net/xtra.bin, http://xtra2.gpsonextra.net/xtra.bin, http://xtra3.gpsonextra.net/xtra.bin

Research Pre GSM Modem Protocol

2009-11-10T22:08:00Z

Robertjw:

Here we are collecting informations about the modem protocol. At the moment all the research is done on the european UMTS version of the Palm Pre. The CDMA version is likely to be pretty similar to the UMTS variant with regards to the protocol.

What we are doing to get used to the protocol is to strace the different applications that talk to the modem and log everything that goes over /dev/modemuart to the actual modem. From this wire protocol traces we are working backwards to the actual protocol and packet format.

=== Packet Start ===

A new packet starts with: '''0xFA''' (This may be an address instead as rfc1662 uses only one flag for frame separation).

As we found out that the CRC is calculated even over the flag '''0xFA''' and with assuming that the basic for the protocol is HDLC we can say that 0xFA is not the starting flag of the frame. It should be an adress if we have a real implemenation of HDLC that follows the rfc.

=== Packet End ===

A packet ends with: '''0x7E'''

=== Escaping ===

For the packet end marker there is an escaping sequence inside the packet. It is used '''0x7D 0x5E''' instead. Therefor '''0x7D''' is escaped as '''0x7D 0x5D''' as well.

=== Header ===

No informations about the header format have been gathered yet.

=== Payload ===

No informations about the payload format have been gathered yet.

=== Checksum ===

The last two bytes before the packet ending marker are a CRC16-FCS checksum. (See rfc1662 for polynom and table)

=== Similarity to RFC1662 ===

The usage of CRC-16-FCS but even more the frame boundary packet as well as the escaping for it looks similar to what we found about this protocol. Even a grep -i HDLC over the binary firmware image reports the usage of PPP and HDLC as communication protocol format. So we can be almost sureley that HDLC+PPP is used.

http://tools.ietf.org/html/rfc1662

=== Identified byte sequences ===
* Sync Message: 0xfa 0x10 0x0
* Sync Response Message: 0xfa 0x30 0x0
* Configuration Message: 0xfa 0x30 0x00 0x1
* Empty Configuration Message: 0xfa 0x40 0x0
* Configuration Response Message: 0xfa 0x40 0x0
* Acknowledge Message: 0xfa 0x50 0x0
* SIM PIN on startup is sent with: 0xfa 0x60 0xe3 0x0f 0x0e 0x00 0x13 0x00 0x00 0x00 0x00 <4 ASCII digits> 0x00 0x00 0x00 0x00 0x00
* SIM PIN acknowledgement from modem: 0xfa 0x50 0x0f

=== GPS ===
The [[GPS]] receiver is part of the modem in Palm Pre and all data received and sent related to location goes over the same port using the same frame coding as GSM. GPS functionality can not be enabled (at least not using the Palm-provided drivers) until modem radio is enabled and seemingly until the modem successfully registers to the network.

Tracing the data sent over /dev/modemuart the following hostnames can be seen being sent from the OS to the modem chip:
xtra1.gpsonextra.net, xtra2.gpsonextra.net, xtra3.gpsonextra.net

They point to the RX Network's company website (rxnetwork.ca) that claims to provide better geolocation by combining GPS, wifi signals, GSM CellID and live reports downloaded over GPRS. The modem downloads the following files:
http://xtra1.gpsonextra.net/xtra.bin, http://xtra2.gpsonextra.net/xtra.bin, http://xtra3.gpsonextra.net/xtra.bin

Research Pre GSM Modem Protocol

2009-11-10T22:07:13Z

Robertjw:

Here we are collecting informations about the modem protocol. At the moment all the research is done on the european UMTS version of the Palm Pre. The CDM version is likely to be pretty similar to the UMTS variant with regards to the protocol.

What we are doing to get used to the protocol is to strace the different applications that talk to the modem and log everything that goes over /dev/modemuart to the actual modem. From this wire protocol traces we are working backwards to the actual protocol and packet format.

=== Packet Start ===

A new packet starts with: '''0xFA''' (This may be an address instead as rfc1662 uses only one flag for frame separation).

As we found out that the CRC is calculated even over the flag '''0xFA''' and with assuming that the basic for the protocol is HDLC we can say that 0xFA is not the starting flag of the frame. It should be an adress if we have a real implemenation of HDLC that follows the rfc.

=== Packet End ===

A packet ends with: '''0x7E'''

=== Escaping ===

For the packet end marker there is an escaping sequence inside the packet. It is used '''0x7D 0x5E''' instead. Therefor '''0x7D''' is escaped as '''0x7D 0x5D''' as well.

=== Header ===

No informations about the header format have been gathered yet.

=== Payload ===

No informations about the payload format have been gathered yet.

=== Checksum ===

The last two bytes before the packet ending marker are a CRC16-FCS checksum. (See rfc1662 for polynom and table)

=== Similarity to RFC1662 ===

The usage of CRC-16-FCS but even more the frame boundary packet as well as the escaping for it looks similar to what we found about this protocol. Even a grep -i HDLC over the binary firmware image reports the usage of PPP and HDLC as communication protocol format. So we can be almost sureley that HDLC+PPP is used.

http://tools.ietf.org/html/rfc1662

=== Identified byte sequences ===
* Sync Message: 0xfa 0x10 0x0
* Sync Response Message: 0xfa 0x30 0x0
* Configuration Message: 0xfa 0x30 0x00 0x1
* Empty Configuration Message: 0xfa 0x40 0x0
* Configuration Response Message: 0xfa 0x40 0x0
* Acknowledge Message: 0xfa 0x50 0x0
* SIM PIN on startup is sent with: 0xfa 0x60 0xe3 0x0f 0x0e 0x00 0x13 0x00 0x00 0x00 0x00 <4 ASCII digits> 0x00 0x00 0x00 0x00 0x00
* SIM PIN acknowledgement from modem: 0xfa 0x50 0x0f

=== GPS ===
The [[GPS]] receiver is part of the modem in Palm Pre and all data received and sent related to location goes over the same port using the same frame coding as GSM. GPS functionality can not be enabled (at least not using the Palm-provided drivers) until modem radio is enabled and seemingly until the modem successfully registers to the network.

Tracing the data sent over /dev/modemuart the following hostnames can be seen being sent from the OS to the modem chip:
xtra1.gpsonextra.net, xtra2.gpsonextra.net, xtra3.gpsonextra.net

They point to the RX Network's company website (rxnetwork.ca) that claims to provide better geolocation by combining GPS, wifi signals, GSM CellID and live reports downloaded over GPRS. The modem downloads the following files:
http://xtra1.gpsonextra.net/xtra.bin, http://xtra2.gpsonextra.net/xtra.bin, http://xtra3.gpsonextra.net/xtra.bin

Patch webOS GPS Tracking

2009-11-10T21:58:03Z

Robertjw: /* Installation */

{{template:patch}}
Here is my super happy awesome tracker script!

== Script code ==
<pre><nowiki>
SECRET=make up any secret code here
DEST=put your e-mail address here

track()
{
export IFS=$'\n'
for loc in $(luna-send -n 3 palm://com.palm.location/startTracking '{"appId": "ILovePalm", "subscribe": true}' 2>&1); do
send $(echo $loc|cut -f3- -d,)
done
}

send()
{
echo "Sending Message: $1"
msg=$(echo $1| sed s/\"/\\\\\"/g)
luna-send -n 1 palm://com.palm.messaging/sendMessageFromCompose '{"recipientJSONArray": [{"value": "'${DEST}'", "contactDisplay": "'${DEST}'", "prefix": "to$A", "identifier": "palm_anon_element_8"}], "messageText": "'"$msg"'"}'
}

checkmsg()
{
echo ".timeout 30000" > /tmp/trackersql
cmd='SELECT messageText FROM com_palm_pim_FolderEntry WHERE timeStamp > (strftime("%s000", "now")-600000);'
# output=$(echo $cmd|sqlite3 /var/luna/data/dbdata/PalmDatabase.db3)
output=$(echo $cmd|sqlite3 -init /tmp/trackersql /var/luna/data/dbdata/PalmDatabase.db3)
echo $output|grep $SECRET 2> /dev/null > /dev/null
status=$?

if [ $status = 0 ]; then
track
fi
}

checkmsg

</nowiki></pre>

== Installation==
# mkdir -p /home/scripts
# Let's say you put the script in /home/scripts/track.sh
# rootfs_open -w
# Go [[Crond | here ]] to enable crond.
# Add the following line to /etc/cron/crontabs/root<pre><nowiki>*/5 * * * * /home/scripts/track.sh</nowiki></pre>
# Now just send the secret code you set in the script to $YOURNUMBER@messaging.sprintpcs.com (without dollar sign but as a ten digit number with area code prefix)
> Ex: 3335554444@messaging.sprintpcs.com where 333 is your area code, and 5554444 the rest of your phone number.
and it will send $DEST the GPS data for the device.

Now, just take the latitude and longitude data and generate the URL. As to the other GPS parameter data available we'll have to investigate to see if Google Maps can take those parameters and how they map to the URL. ~Robi

<pre><nowiki>
luna-send -n 1 palm://com.palm.location/getCurrentPosition {}
** Message: serviceResponse Handling: 2, {"errorCode":0,"timestamp":1.245799702311E12,"latitude":37.48660683631897,"longitude":-122.23269581794739,"horizAccuracy":37.947330474853516,"heading":178,"velocity":0.75,"altitude":-13,"vertAccuracy":24}
</nowiki></pre>

which means we can transpose some of that to a Google Maps link:

<pre><nowiki>
http://maps.google.com/?ie=UTF8&q=37.48660683631897,-122.23269581794739+(Heading:%20178%0DSpeed:%200.75%20mph)
</nowiki></pre>

If you know more about the GPS parameters, let us know by updating the page. ~Robi

* The velocity, altitude, and accuracy parameters are specified in meters

* Added heading and speed parameters to the URL. If you hover over the pinpoint on the google map, you can see the information, as well as in the info window if you click on the pinpoint. -xluryan

"If [ll=] is used without a query, then the map is centered at the point but no marker or info window is displayed." To get around this, use q=[Lon,Lat] instead of ll=[Lon,Lat]. I changed the maps link above. -hopspitfire

'''Troubleshooting Tip:''' Make sure track.sh has the correct file permissions set. To encompass all possibilities, try 'chmod 755 /home/scripts/track.sh'. You can restrict permissions later if you wish. On Windows it's probably easiest to do this through WinSCP (right click>Properties>Permissions).

== Development Ideas==
1. Send response as a google maps link that clicked on shows the phones position on a map.
2. Find a way to put a hook into message reception so that messages don't have to be checked with a cron job. Even better if the message could be intercepted before appearing on the phone, it would be a useful way to track a stolen phone.
3. After implementing the script that emails me every 20 minutes, it occured to me that the following would be great:
3a. The ability to log the entries instead of just sending an email, and maintain a preset number of logged entries (say the last 24 entries).
3b. Using the original implementation - send a message to the device to have the logged information emailed. This would show a "track" of where the device has been.
3c. Control of the number of log entries, and the frequency.
== Another Simple Method==
Why not use this script:
<pre><nowiki>
#!/bin/sh

pos=$(luna-send -n 2 palm://com.palm.location/startTracking '{"appId": "ILovePalm", "subscribe": true}' 2>&1 | tail -1 | cut -d, -f4,5,8 | sed -r 's/[^-\.0-9,]//g')

lat=$(echo $pos | cut -d, -f1)
lon=$(echo $pos | cut -d, -f2)
spd=$(echo $pos | cut -d, -f3)
bat=$(grep BATTERY: /var/log/messages | tail -1 | awk '{print $8}' | sed 's/%,//')

ret=$(wget -qO- "http://yoursite.com/trackme/$1/requests.php?lat=$lat&lon=$lon&speed=$spd&batt=$bat" | egrep -o '[0-9]+$')
exit $ret
</nowiki></pre>

I have a web server setup with //requests.php// taking '''//lat//''', '''//lon//''', '''//speed//''', and '''//batt//''' arguments. Then it writes them to a file. Use the data however you want. I have mine plug into a google map and show me the data.

Just set up a cron job to call the script every 20 minutes or so. Hardly effects battery life at all :)

Credit to ddoc for info on how to grab battery status. I would still like to find a more efficient way of grabbing battery level rather than searching through the entire message log. Though for now, it works exactly like it should.

Here's the Method for getting battery status:
<pre><nowiki>Mojo.Service.Request('palm://com.palm.power/com/palm/power/', {method: 'batteryStatusQuery',});</nowiki></pre>
-pEEf

== Email a URL to open Google Maps showing location of phone.==
Below is a code snippet that will send an email with working URL to open Google Map and show you the location of your phone.
The cron job mentioned above is setup to call this script every 20 minutes on my machine...works great. I let GMAIL archive them.
If the phone gets stolen, I can find it as long as it has service.

The larger Accuracy is, the further away the coordinates output will be from your actual position.

Added speed & heading to Google URL. Is there any way to have the sent messages not appear in the Text Messaging app, or to use the shell to email the output via mailx? Until I figure out a built-in mail function, you can use an alternative I'm testing that uses a server's mailx command: echo "$msg2" | /opt/bin/ssh -x user@server /bin/mailx $DEST -hopspitfire

<i>modified by wilderf353 on 09-09-01:</i>
I modified the original script because the Google URL being sent was getting truncated on my phone and a few other people that posted at forums.precentral.net. I did some testing and it looks like when you use sendMessageFromCompose, you are limited to a message with less than 136 characters. I shortened the message and added :
<ul>
<li>at the beginning of the script, turn on GPS if it is off</li>
<li>at the beginning of the script, turn on Location Services if it is off</li>
<li>at the end of the script, turn GPS back off, if it was off when the script started</li>
<li>at the end of the script, turn Location Services back off, if it was off when the script started</li>
<li>added altitude and altitude accuracy information to message</li>
<li>added the ability to only send the message if GPS coordinates have changed since the last run</li>
<li>added the ability to send a message on the hour even if GPS coordinates have not changed</li>
</ul>

(NOTE: You will need to add your email address to the script)

<pre><nowiki>
#!/bin/sh

####### Stuff to set

## email address to mail info to
DEST=johns@gmail.com
# example: DEST=wsmith@aol.com (make sure you don't have any spaces)

## send url with embedded heading/speed info
# we only have ~136 characters to work with. If you embed heading & speed info, you can't
# include altitude and altitude accuracy information
# msg_with_heading=0 (don't embed heading/speed info, but include altitude information)
# msg_with_heading=1 (embed heading/speed info)
msg_with_heading=0

# run_only_if_diff=0, send a message every time
# run_only_if_diff=1, send a message only if GPS coords have changed since last run
run_only_if_diff=1

# file where gps coords should be stored until next run
last_gps_coord_file=/tmp/track_coords

# use with run_only_if_diff
# send_every_hour=1, send a message on the hour, even if the phone hasn't moved
# send_every_hour=0, don't send a message on the hour
send_every_hour=1

######

# get current minute and current time
cur_min=$(date +"%M")
now=$(date +"%D %R")

# The GPS should be turned on to get an accurate fix...otherwise you get the tower location
# Is the GPS turned on?
$(luna-send -n 1 palm://com.palm.location/getUseGps '{}' 2>&1 | grep 'true' > /dev/null)
grep_ret=$?
if [ $grep_ret -eq 0 ] # Test exit status of "grep" command.
then
# gps is on
gps_on=1
else
#gps is off...let's turn it on and remember to turn it back off later
gps_on=0
$(luna-send -n 1 palm://com.palm.location/setUseGps '{"useGps":true}' > /dev/null 2>&1)
# wait for 60 seconds so gps gets a good lock
sleep 60
fi

# Location services must be turned on, or startTracking will not work (you get a {"errorCode":7})
# Are locations service turned on?
$(luna-send -n 1 palm://com.palm.location/getAutoLocate '{}' 2>&1 | grep 'true' > /dev/null)
grep_ret=$?
if [ $grep_ret -eq 0 ] # Test exit status of "grep" command.
then
# location service is on
location_service=1
else
#location service is off...let's turn it on and remember to turn it back off later
location_service=0
$(luna-send -n 1 palm://com.palm.location/setAutoLocate '{"autoLocate":true}' > /dev/null 2>&1)
fi

# Get current coords
pos=$(luna-send -n 2 palm://com.palm.location/startTracking '{"appId": "ILovePalm", "subscribe": true}' 2>&1 | tail -1 | cut -d, -f4,5,6,7,8,9,10 | sed -r 's/[^-\.0-9,]//g')

lat=$(echo $pos | cut -d, -f1)
lon=$(echo $pos | cut -d, -f2)
acc=$(echo $pos | cut -d, -f3 | cut -d. -f1)
dir=$(echo $pos | cut -d, -f4)
spd=$(echo $pos | cut -d, -f5)
alt=$(echo $pos | cut -d, -f6)
altacc=$(echo $pos | cut -d, -f7 | cut -d. -f1)
bat=$(grep BATTERY: /var/log/messages | tail -1 | awk '{print $8}' | sed 's/%,//')

# turn off GPS?
if [ $gps_on -eq 0 ]
then
# the GPS was off when we started the script...turn it back off
$(luna-send -n 1 palm://com.palm.location/setUseGps '{"useGps":false}' > /dev/null 2>&1)
fi

# turn off location service?
if [ $location_service -eq 0 ]
then
# location service was off when we started the script...turn it back off
$(luna-send -n 1 palm://com.palm.location/setAutoLocate '{"autoLocate":false}' > /dev/null 2>&1)
fi

# check if we should send a message
if [ $run_only_if_diff -eq 1 ]
then
# create short coords.
# use "printf("%3.4f\n",$0)" for 4 decimal places (about 30 feet accuracy)
# use "printf("%3.3f\n",$0)" for 3 decimal places (about 280 feet accuracy)
# use "printf("%3.2f\n",$0)" for 2 decimal places (about 0.5 miles accuracy)
sh_lat=$(echo $lat | awk '{printf("%3.4f\n",$0)}')
sh_lon=$(echo $lon | awk '{printf("%3.4f\n",$0)}')

# does the file with the last coords exist?
if [ -f $last_gps_coord_file ]
then
$(grep "$sh_lat $sh_lon" $last_gps_coord_file > /dev/null)
grep_ret=$?
if [ $grep_ret -eq 0 ]
then
# coords match...don't send a message
send_message=0
else
# coords don't match...send a message and update coord file
send_message=1
echo $sh_lat $sh_lon > $last_gps_coord_file
fi
else
# there is not a last coords file...create one for next time
send_message=1
echo $sh_lat $sh_lon > $last_gps_coord_file
fi
else
# $run_only_if_diff is false, so send a message
send_message=1
fi

# if configured to send on the hour...is it time?
if [ $send_every_hour -eq 1 -a $cur_min = "00" ]
then
send_message=1
fi

# Enable this below if you want to keep logs - not sure where to write them /var/home/root not the best place.
# echo $now,$lat,$lon,$acc,$dir,$spd,$alt,$altacc,$bat >>mygpsdata.log

# send the message
if [ $send_message -eq 1 ]
then
#Build message content to be sent
if [ $msg_with_heading -eq 1 ]
then
msg=$(echo $now "\n" Bat:$bat Acc:$acc "http://maps.google.com/maps?q=$lat%2C$lon+(Heading:%20$dir%0DSpeed:%20$spd)")
else
msg=$(echo $now "\n" "http://maps.google.com/maps?q=$lat%2C$lon" "\n" Bat=$bat,Acc=$acc,Dir=$dir,Spd=$spd,Alt=$alt,AltAcc=$altacc)
fi

$(luna-send -n 1 palm://com.palm.messaging/sendMessageFromCompose '{"recipientJSONArray": [{"value": "'${DEST}'", "contactDisplay": "'${DEST}'", "prefix": "to$A", "identifier": "palm_anon_element_8"}], "messageText": "'"$msg"'"}' > /dev/null 2>&1)
fi

</nowiki></pre>
This has been running every 20 minutes on my phone for the last 4 days, no problem.
-dld121

Crond

2009-10-26T05:53:25Z

Robertjw: /* Enabling Stock Cron */

== Enabling Stock Cron==

The [[Patch webOS GPS Tracking]] guide had a nice bit about enabling crond on the Pre. It looks like its already pre-installed, just not set up to start. You will need to edit /etc/event.d/mod-crond (don't modify the existing crond startup-script) to enable cron to start. The settings should look like this:

<pre><nowiki>
# -*- mode: conf; -*-

# jobfile for busybox crond, with pre-start commands to create the
# directory and files it wants by default. That there's not 'start
# on' stanza is intentional: it's for development use only. We can
# turn it on later if we need it, e.g. to keep the clock synced. It
# does work.

start on stopped configure
stop on started start_update

respawn

exec /usr/sbin/crond -f -L /var/log/crond

pre-start script
mkdir -p /var/spool/cron/crontabs
ln -sf /etc/cron/crontabs/root /var/spool/cron/crontabs/root
end script
</nowiki></pre>

A few notes here. Unlike the Dropbear and other scripts I make my upstart scripts so that essential services don't stop when the device exists runlevel 2. This seems to shutdown these services whenever the device locks. I prefer that my upstart services stop only when the updater runs. Also I have made cron log to a separate file under /var/log so that it can be monitored better.

One thing to note about the standard script for cron on the Pre is that the /var/spool/cron/crontabs directory is created every time the process runs and a symlink to /etc/cron/crontabs/root is created. To my surprise this file does not exist. So we need to create it:

<pre><nowiki>
sudo mkdir -p /etc/cron/crontabs
sudo sh -c 'echo > /etc/cron/crontabs/root'
</nowiki></pre>

Now to start up crond:

<pre><nowiki>sudo -i initctl start crond</nowiki></pre>

*Note for clarification: I attempted this and it all works OK, but I can't figure out how to actually schedule jobs. I modified /etc/cron/crontabs/root, but nothing seems to happen. I also tried crontab -e, and that doesn't seem to do anything either. I suggest adding a note here clarifying what needs to be done to actually add a cron job. -irwinr

*Clarification: Edit /etc/cron/crontabs/root with test content something like this:

<pre><nowiki>
# format:
# minute(0-59) hour(0-23) day(1-31) month(1-12) weekday(0-6) command

* * * * * echo "Hello" >> /var/crondtest

</nowiki></pre>

Then restart crond like this:

<pre><nowiki>
sudo -i initctl stop crond
sudo -i initctl start crond
</nowiki></pre>

This test will result in a test file at /var/crondtest that grows at the rate of one line per minute.

==Alternative (ipkg-opt) Method==

* Another request for clarification: It's not clear which of these two methods are preferred. This method appears to not work when the screen is off (rendering cron pretty useless), the above method appears to delete the cron entries every time the cron daemon starts. Has anyone worked out either of these issues? -irwinr.

crond is a system that allows command to be run at specified intervals.

Do not use the built in crontab -e as it is overwritten on each boot.

Optware has cron available as an installable package, and using /opt/etc/cron.d/ for cron files will not conflict with any Palm files.

<pre><nowiki>
sudo -i
mount -o remount,rw /
ipkg-opt update
ipkg-opt install cron
/opt/bin/crontab -e
# Add script and intervals here
mount -o remount,ro /
</nowiki></pre>

This does not seem to work when the phone's screen turns off. I tried it plugged in for two minutes then unplugged, and turned the screen off for two minutes. I ran
<pre><nowiki>echo `date` >> sleep.log</nowiki></pre>

And got...

<pre><nowiki>
# cat sleep.log
Wed Jul 1 18:27:01 CDT 2009
Wed Jul 1 18:28:01 CDT 2009
Wed Jul 1 18:30:16 CDT 2009 ## Turned the screen back on. It seems to play catch up.
Wed Jul 1 18:30:16 CDT 2009
</nowiki></pre>