Openmoko - User contributions [en]

Erlang

2010-05-13T16:16:30Z

Zem: /* Example Code */

== Introduction ==
[http://www.erlang.org Erlang] is a programming language which has many features more commonly associated with an operating system than with a programming language: concurrent processes, scheduling, memory management, distribution, networking, etc.

=== Concurrency ===
- Erlang has extremely lightweight processes whose memory requirements can vary dynamically. Processes have no shared memory and communicate by asynchronous message passing. Erlang supports applications with very large numbers of concurrent processes. No requirements for concurrency are placed on the host operating system.

=== Distribution ===
- Erlang is designed to be run in a distributed environment. An Erlang virtual machine is called an Erlang node. A distributed Erlang system is a network of Erlang nodes (typically one per processor). An Erlang node can create parallel processes running on other nodes, which perhaps use other operating systems. Processes residing on different nodes communicate in exactly the same was as processes residing on the same node.

=== Robustness ===
- Erlang has various error detection primitives which can be used to structure fault-tolerant systems. For example, processes can monitor the status and activities of other processes, even if these processes are executing on other nodes. Processes in a distributed system can be configured to fail-over to other nodes in case of failures and automatically migrate back to recovered nodes.

=== Soft real-time ===
- Erlang supports programming "soft" real-time systems, which require response times in the order of milliseconds. Long garbage collection delays in such systems are unacceptable, so Erlang uses incremental garbage collection techniques.

=== [[Hot code loading]] ===
- Many systems cannot be stopped for software maintenance. Erlang allows program code to be changed in a running system. Old code can be phased out and replaced by new code. During the transition, both old code and new code can coexist. It is thus possible to install bug fixes and upgrades in a running system without disturbing its operation.

=== Incremental code loading ===
- Users can control in detail how code is loaded. In embedded systems, all code is usually loaded at boot time. In development systems, code is loaded when it is needed, even when the system is running. If testing uncovers bugs, only the buggy code need be replaced.

=== External interfaces ===
- Erlang processes communicate with the outside world using the same message passing mechanism as used between Erlang processes. This mechanism is used for communication with the host operating system and for interaction with programs written in other languages. If required for reasons of efficiency, a special version of this concept allows e.g. C programs to be directly linked into the Erlang runtime system.

=== Fast and Lean ===
- Erlang is fast and lean. A general erlang application has lots of processes. If you are used to OOP you can compare a process with an object. One process per object instance. To make sure the neo could cope with this I watched top while I was busy dialing a phone number on the [[Aphasia]] dialer. Each of the twelve buttons are a separate process. Each has its own little animation, and if you look carefully you can see they run in parallell and are acting independent of each other. The top statistics show a really low CPU utilization, I have to dial quite fast to exceed 5% CPU. Next test I made was to measure the time it takes to start these 12 processes and have them display themselves on the screen (aka start the dialer app). It takes approximately 0.5 sec! 

[[Image:Dialer.gif]]

== Installation on OpenWrt ==

Follow the guidelines in the [[OpenWrt]] wiki page. Go to "Build Custom Image" and follow the instructions. In "Configure target and packages" scroll down to Languages and select Erlang.

== Installation on FSO distribution ==

The minimal erlang system is only 4 MB. It fits nicely into whats left in the Freerunner and neo1973 after openmoko-fso-image is installed.

Download cean_installer.bin from CEAN http://cean.process-one.net/downloads/ At the CEAN Downloads page, select "Installer" and "Production" and "Linux ARMEL" and Download. Copy the file cean_installer.bin to your neo. To save keystrokes I have added "192.168.0.202 phone" to my /etc/hosts file.

<pre>
scp cean_installer.bin root@phone:/home/root
</pre>

Open a terminal window to the phone. Password is blank. Unless you changed it to something you just have to press enter at the prompt.

<pre>
ssh root@phone
</pre>

Before you can install erlang you have to get a copy of the file libsctp.so.1. I grabbed one from my Debian installation on the cf card at /media/mmcblk0p2/usr/lib/


<pre>
cp /media/mmcblk0p2/usr/lib/libsctp.so.1 /usr/lib
</pre>


Or if you get it from your host:
<pre>
scp ./somedir/libsctp.so.1.0.9 root@phone:/usr/lib/libsctp.so.1
</pre>

Make sure you have "tar" installed on the phone:

<pre>
opkg update
opkg install tar
</pre>


Now you are ready to install erlang. On the phone, type

<pre>
chmod 777 cean_installer.bin
./cean_installer.bin
</pre>


If all goes well you will see the erlang console prompt

<pre>
Erlang (BEAM) emulator version 5.6.3 [source] [async-threads:0] [kernel-poll:false]

Eshell V5.6.3 (abort with ^G)
1>
</pre>

I use ^G and then "q" to exit the shell.

== Installation on SHR-testing distribution ==

Get a version from CEAN, as described above, but get the "Archive", and not the "Installer". You will need the "libsctp" lib, too, but it's not in SHR anywhere. You can get a compatible .so out of the .deb package from this link [http://packages.debian.org/lenny/armel/libsctp1/download]. Find the file libsctp.so.1.0.9, and save it to /usr/lib/ on your SHR freerunner. You should now be able to start the erlang shell.

== Installation on Debian distribution ==

Make sure you have an uboot that is [http://wiki.openmoko.org/wiki/Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader_to_the_NAND compatible], I used Uboot u-boot-gta01bv4-1.2.0+svnnow-r13_0_2632_0.bin

Follow the instructions. I had to type in the setenv string and then saveenv.
Reboot to get the new menu_4 title to show up.

Install Debian, install script is here: [[Debian]]


<pre>
apt-get install erlang-base
</pre>


== Erlang development environment ==
You can in fact choose any text editor, and use a terminal window to compile and copy compiled erlang beam-files to the phone. However, I have found SciTE to be a nice choice. It has erlang colour coding, bracket matching, code completion and lots of more stuff you are accustomed to find in a programmers editor. And it's easily configurable to handle compilation and error tracking, click on an error message to go to the line where the error is located.

In addition to all this you can set it up to let you run your erlang app on the host, and to copy the compiled app to the phone and run it there. All from within SciTE. This gives a very fast turnaround time, I can compile my app - run on host - copy to neo - run on neo in less than a minute. Part of this fast development cycle is of course due to the fact that erlang is platform agnostic - the same compiled code runs on Arm and Intel Linux and Windows.

Mac users have TextMate. Check out the bundle and install.
<pre>
$ svn co http://svn.textmate.org/trunk/Bundles/Erlang.tmbundle
</pre>

{{note |Other options for erlang developers are Eclipse and NetBeans. Add [http://erlide.sourceforge.net/ erlIDE] to Eclipse or use [http://sourceforge.net/projects/erlybird ErlyBird] }}

=== You don't need an emulator ===
All you need to run a phone application on your host is erlang and an X-server. Are you running linux it's just to install erlang and you are done. On a Mac you also have to install the Apple X-server app. It works right out of the box, and is a free download from www.apple.com. Textmate is the recommended erlang ide for mac-users. Windows users have to take another path. You develop and compile erlang source on your windows box, and use erlang's built in [[hot code loading]] to run your code right on the phone without any restart or reboot.

== Example Code ==
=== Use [[D-Bus]] in erlang ===
<pre>
Dbus = open_port({spawn,"mdbus -s"}, [stream, use_stdio, binary]),
loop(Dbus).
</pre>
And get the response
<pre>
loop(Dbus) ->
receive
{Dbus,Msg} -> io:format("Dbus msg:~p~n",[Msg]),loop(Dbus)
end.
</pre>

There also is a Native DBus Implementation available for Erlang:

http://sourceforge.net/projects/dbus-erlang/

===Use GTK in Erlang===

You can design GUIs with glade using erlang-gtknode.

[[Category:Application Developer]]

Erlang

2010-05-13T16:13:59Z

Zem: /* Use D-Bus in erlang */

Distributions

2009-05-23T18:14:55Z

Zem: /* Non-Openmoko distributions */

{{Languages|Distributions}}

{|align=left
|__TOC__
|}

== About distributions ==
Openmoko distributions are designed to run on various mobile devices, with the primary aim of supporting Openmoko Inc.'s [[GTA01:Neo 1973|Neo 1973]] and [[Neo FreeRunner]] phones. They are GNU/Linux distributions -- complete operating systems including user applications. You can install any of them on your phone or even have a dualboot system with two distributions installed. For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].

Besides, Openmoko distributions also run on [[Supported devices|other]] mobile devices and some other software distributions also run on the phones of Openmoko Inc.

=== Choosing a distribution ===
Currently the most used distributions are [[Om 2008]], which comes preinstalled on the Neo FreeRunner, and [[Stable Hybrid Release|SHR]].[http://spreadsheets.google.com/pub?key=p2ZQdcRSVg9XfYLwBVsZicg]

In the future [[Om 2009]] will be the default distribution. It is currently under development and should be released in june 2009. Like SHR it will be based on the [[freesmartphone.org]] framework.

Furthermore, there are many other distributions, like [[Qt Extended]] (for stable basic functions), Google's [[Android]], and some [[Debian]]-based distros.

{| class="wikitable" style="float:right;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"
|Distributions
|-
! style='background-color:#333333;color:#FFFFFF'|
<div align=left>
* Openmoko (official)
** [[Om2009]]
** [[Om 2008.12 Update]]
** [[Om 2008.9 Update]]
** [[Om 2008.8]]
** [[Om 2007.2]]
** [[OpenmokoFramework|FSO]]
* Om Community
** [[SHR]]
** [[FDOM]]
* Other
** [[Qtopia]]
** [[Debian]]
** [[Gentoo]]
** [[Android]]
** [[Hackable:1]]
** [[neovento]]
</div>
|-
|}

=== Please note ===

* Stable in the FreeRunner world does not mean the same thing as stable in the Debian world.
* Most distributions use the same bootloader, kernel, drivers and hardware. Therefore, the same low level bugs are commonly found in all distributions. The latest and greatest software usually has most bug fixes, plus a whole set of new fresh bugs.
* Most of these distributions also have package repositories. It is a BAD idea to feed from another distribution's repository.
* Upgrade path between these distributions are mostly not tested, thus updating by changing the feeds will most likely end in broken packages or even an unbootable system. It is advisable to reflash the whole filesystem with [[dfu-util]] to switch between the different distributions, with the reminder that a dual-boot setup (e.g. via sdcard or NFS) can be used.

== Official Openmoko releases ==

'Release targets' offered by Openmoko Inc. are built out of different branches of the [[OpenEmbedded]] metadistribution source tree.

=== Om series ===

* '''[[Om2009]]''' is intended to be the new distro; it is not a simple follow-on from [[Om 2008.12 Update]]. '''It is still very much in development and by no means ready for production use''' and is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework.

{{Main|Om2009}}

* '''[[Om 2008.12 Update]]''' is the second point release after the initial ''Om 2008.9'' release.

{{Main|Om 2008.12 Update}}

* '''[[Om 2008.9 Update]]''' is the first point release after the initial ''Om 2008.8'' release. Openmoko recommends that all existing installations of Om 2008.8 should be updated to that version. Quality-wise, we are still far from the goal, but this version includes general stability enhancing operating system improvements and a new splash screen. No applications were added or removed. Users with basic telephony needs will find it tolerable as an everyday phone.

{{Main|Om 2008.9 Update}}

* '''[[Om 2008.8]]''' was released on August 8, 2008, to replace 2007.2. Prior to that, its codename was ASU (April/August Software Update). This is still the name of the branch in the version control system. This distribution integrates the [http://trolltech.com/products/qtopia Qtopia] phone stack with a set of new Openmoko applications based on the Enlightenment Foundation Libraries ([[EFL_Documentation|EFL]]). Qtopia being a more mature product than the GNOME Mobile stack, the standard phone applications (dialer, contacts, calculator, calendar) work better than in 2007.2. The Qtopia used in 2008.8 was ported to run on X11, contrary to standard Qtopia which uses the framebuffer. This allows non-Qt applications to safely share the screen with Qt applications. This is a .0 release, many unresolved issues remain in the lower layers (kernel power management, sound, wifi drivers...).

{{Main|Om 2008.8}}

* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand.

{{Main|Om 2007.2}}

=== FSO series ===

'''FSO''' is an abbreviation for FreeSmartphone.Org. Openmoko is working on a stable system services back-end. Focus is on stable highlevel services that you can access from whatever language or UI that supports [http://dbus.freesmartphone.org/ dbus]. The framework will be used in forthcoming Openmoko distributions. FSO is all about middleware, but if one stacks a bootloader+kernel under it and telephony applications on top, one gets a functional distribution. These are made available as FSO-image milestones.

* '''FSO Milestone V''' was released and named 'Calling All Stations'. The telephony application on top of it is Zhone. This is a basic Python dialer/homescreen designed as scaffolding to test the FSO functionalities (even if Zhone is pretty, code path coverage is more critical to it than user-friendliness). More details at
[http://wiki.openmoko.org/wiki/OpenmokoFramework/Status_Update_6 Status Update 6]. You can grab it from http://downloads.freesmartphone.org/fso-stable/milestone5.1/ .

{{Main|FSO}}

== Openmoko community releases ==

=== SHR - Stable Hybrid Release ===

SHR is a community driven distribution. It contains some basic EFL based applications which make use of the FSO. There currently is an [[EFL_Documentation|EFL]] (with elementary) dialer, messages and contacts application programmed in C, as well as a nice Settings-GUI in Python. As of April 12th, 2009, there is no stable release of this distribution yet, as the SHR team doesn't feel it to be good enough. You can find images though on the [http://shr.bearstech.com/shr-testing SHR buildhost].

{{Main|Stable Hybrid Release}}

=== FDOM (FAT and Dirty Openmoko) ===

[[FDOM]] is a distribution based on Openmoko's currently supported image, updated with many ready-to-use applications and with fixes posted in the mailing lists. A combination of applications (everything goes) and fixes to demonstrate the capabilities of the Freerunner and to have a functional phone (sort of). This all while retaining the ability to update through the official feeds.

{{Main|FDOM}}

=== Non-Openmoko distributions ===

These are not Openmoko (and OE) based distributions. These are alternatives you can run on your Openmoko phones.

==== Qt Extended ====
Qt Extended has had several names. The current name is Qt Extended Improved. An Openmoko-based community develops Qt Extended Improved as a Free Software project. Qt Extended Improved builds on the foundation of Qt Extended/Qtopia/Qt by Qt Software/Trolltech. Qt Extended Improved provides a robust telephony stack, a webkit based browser and other smartphone features.

On 5th March 2009 Qt Software released Qt Extended 4.4.3. On 3rd March 2009 Qt Software announced that Qt Extended would 4.4.3 would be the last release of the Qt Extended product. Prior to version 4.3, Qt Extended was known as Qtopia.

{{Main|Qtopia / Qt Extended on FreeRunner}}

==== Debian ====
Debian is "the universal operating system". It comes with thousands and thousands of packages (most of them designed for desktops or servers so far). So in the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team, this is not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the Stable Hybrid Release software in our archive. So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)

{{Main|Debian}}

==== [[Gentoo ]]====
Gentoo is all about choices. When installing Gentoo, this is made clear to you several times -- you can choose how much you want to compile yourself, how to install Gentoo, what system logger you want, etc. Gentoo is a fast, modern metadistribution with a clean and flexible design. Gentoo is built around free software and doesn't hide from its users what is beneath the hood. Portage, the package maintenance system which Gentoo uses, is written in Python, meaning you can easily view and modify the source code. Gentoo's packaging system uses source code (although support for precompiled packages is included too) and configuring Gentoo happens through regular textfiles. In other words, openness everywhere.

{{Main|Gentoo}}

==== Android ====
[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Openmoko is fully supporting Android running on the Freerunner.

Android has now reached a point where it is usable on the FreeRunner as an everyday phone, there are, however, still some caveats. Check out the main Android section of the wiki for more info.

{{Main|Android}}You can also visit the user web page for [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] for some more info.

====Slackware====
As of release 12.2, Slackware is now officially supported on the Neo Freerunner
[http://armedslack.org/]

==== Hackable:1====
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform.
{{Main|Hackable:1}}

====[[neovento]]====
neovento (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project.

{{Main|neovento}}

====[[OpenWRT]]====
The OpenWRT Development Trunk supports Freerunner, too. [http://www.openwrt.org/]

==== Others / unreleased ====
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. pyneo can be considered FSO milestone 0. Afterwards, FSO evolved into an own project with different goals. ''Status: still active, ask around on #pyneo.org ''
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: it does not have its own kernel so a Freerunner distribution waits for a solid basis and an arm-linux-gnueabi toolchain that runs natively on Mac OS X is currently lacking.''

== Features by distribution/release target ==

Generally, distributions can differ on one or more of the following components:
* The bootsplash screen image. This is purely decorative.
* The bootloader. Theoretically, any version of ''uboot'' could be used with any distribution. In the future ''Qi'' will replace ''uboot''.
* The kernel. GNU/Linux kernels versions 2.6.24, 2.6.26 or 2.6.28 can be found. Some have modules compiled in, others have modules compiled separately. If compiled separately, modules can be distributed in the same package file as the kernel or separately.
* Middleware: daemons to handle GSM calls or GPS, sound system, personal information storage and so on. Qt and Android have their own subsystems, FreeSmartphone.Org (FSO) is working towards a standard-based Free Software one.
* Display driver. The original ''Qt Extended'' uses the framebuffer, most other distributions today use ''X11''.
* Libraries and application framework (widget toolkit and and graphical environment) : EFL, Qt, Gtk+ or Java ?
* Basic telephony applications: voice calls, SMS, alarm clock...
* Smartphone applications: GPS, media player, simple games, web browser...
* Open source applications: more games, scientific, you name it...

=== Hardware Support ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| GTA01 || ?? || ?? || ?? || {{Yes}} || ?? || {{Yes}} || {{Yes}} || ?? || ??
|-
| GTA02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
|}

=== Connectivity ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Telephony || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| SMS || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| [[GPRS]] || Not through UI || Not through UI|| Not through UI || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || Not through UI || {{Yes}}
|-
| [[WiFi]] || {{Yes}} (*) || {{Yes}} || Not through UI || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Not through UI || {{Yes}}
|-
| VoIP || ?? || ?? || ?? || ?? || {{Yes}} || {{Yes}} (1) || {{Yes}} || ?? || {{no}}
|-
| Bluetooth || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ?? || {{Yes}}
|-
| GPS (1) || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} (1) || {{Yes}}
|-
|}

=== Power ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|Om 2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Suspend || {{Yes}} || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
| Resumes on Event || ?? || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??
|-
| Functions after Resume || {{Yes}} || ?? || ?? || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
|}

=== User Interaction ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|Om2008.8 !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Stylus friendly || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}
|-
| Finger friendly || Partially || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}}
|-
| Accelerometer || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{No}} || {{yes}} (1) || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}
|-
|}

=== Applications ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| Terminal || {{Yes}} (1) || Basic (2) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}}
|-
| PIM || {{Yes}} || {{Yes}} || {{No}} || N/A || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || ??
|-
| Phonebook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Dialer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Web Browser || {{Yes}} (1) || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| Mail Client || {{Yes}} || ? || ? || ? || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
| XMPP Client || {{Yes}} [[Instant Messaging|(1)]] || {{Yes}} (1) || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || || ??
|-
| Media Player || {{Yes}} (1) || {{Yes}} || ? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}
|-
|}

=== Toolkits / Runtimes ===
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"
! width=10%| !! width=8%|[[Om 2008.8]] !! width=8%|2007.2 !! width=8%|FSO !! width=8%|SHR !! width=8%|FDOM !! width=8%|Qt Extended !! width=8%|Debian !! width=8%|Gentoo !! width=8%|Android
|-
| GTK+ || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || ??
|-
| Qt/Qt Extended || {{Yes}} || {{No}} || {{Yes}} ? || {{Yes}}? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??
|-
| Middleware || qtopia-x11 || gsmd/neod || FSO || FSO || qtopia-x11 || Qt Extended || FSO || FSO || ??
|-
| [[Java]] || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes}} || ?? || {{Yes|CacaoVM, JamVM}} || ?? || ??
|-
| [[Python]] || {{Yes}} || {{Yes}} || {{Yes}} || {{yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??
|-
| [[Mono]] || {{Yes}} (1) || {{Yes}} (1) || ?? || {{no}} || ?? || ?? || {{Yes}} (1) || ?? || ??
|-
| [[Ruby]] || {{Yes}} || ?? || ?? || ?? || ?? || ?? || {{Yes}} (1) || {{Yes}} (1) || ??
|}

=== Images ===
Latest and stable combinations for Neo FreeRunner gta02
{|class="wikitable" border="1" cellpadding="5" cellspacing="0"
| || OM || FDOM || Qt Extended || Android
|-
| current bootloader || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/distro/releases/Om2008.9/ OM daily] version [http://downloads.openmoko.org/] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/repository/experimental/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] || [[U-boot|U-Boot]] from [http://downloads.openmoko.org/repository/experimental/ OM daily] version [http://downloads.openmoko.org/daily/gta02v5_and_up-u-boot.bin gta02v5_and_up] ||
|-
| future bootloader || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu || [[Qi]] from [http://people.openmoko.org/andy/ Andy] latest qi-andy.udfu ||
|-
| splash || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz || [[Configuring_the_boot_splash_screens|U-Boot]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest splash.gz ||
|-
| kernel || [[Linux]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest uImage.bin || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest uImage-gta02-mwester-stable.bin or from [http://downloads.tuxfamily.org/3v1deb/openmoko/ treviño] latest uImage-gta02-stable-3v1n0.bin || [[Linux]] see [[Qt_Extended]] page for latest version || [[Linux]] from [http://koolu.org/releases/ koolu]
|-
| modules || ? || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz || [[Linux]] from [http://moko.mwester.net/download/ mwester] latest modules-min-gta02-mwester-stable.tgz or modules-all-gta02-mwester-stable.tgz ||
|-
| rootfs || [[Main_Page|OM]] from [http://downloads.openmoko.org/releases/ OM releases] or [http://downloads.openmoko.org/daily/ OM daily] latest rootfs.jffs2 || [[FDOM]] from [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/ TuxBrain] version [ftp://ftp.tuxbrain.com/openmoko/fdom/releases/Fat_and_Dirty_OM.200809_20081023.rootfs.jff2 200809_20081023] || See [[Qt_Extended]] for latest rootfs || [[Android]] from [http://koolu.org/releases/ koolu]
|}

Footnotes:

(1) works, but need additional software to be installed

(2) unusable due to lack of certain keyboard characters. [[Switching_Keyboards#Matchbox_keyboard|Various fixes available.]]

(*) unstable

==Quick download page==

[[Download]]

== See also ==

* Mickey Lauer's post "[http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!]" describes the differences between distributions 2007.2, ASU and FSO.

* Latest news and tips are in [[Community Updates]]

* [[Kustomizer]] is a script to change your 2008.12 to a usable phone

[[Category:Distributions| ]]

GPRS FSO

2009-01-30T08:31:07Z

Zem: /* Troubleshooting */

{{FSO}}
This page documents the GSM networking solutions (commonly known as GPRS) using the [[OpenmokoFramework|FreeSmartphone.Org]] framework (FSO).

There are other ways to enable wireless communications on the smartphone, including [[Bluetooth]] and [[Wireless_Networking|WLAN]].

== Current state ==

Since milestone 2 the system dbus has been extended with methods that enables connectivity using GPRS. The functionality is available under <code>org.freesmartphone.ogsmd</code> at <code>/org/freesmartphone/GSM/Device</code>.

The implementation should not interfere with other phone functionality, such as placing calls. In other words: you can use GPRS while talking on the phone without hanging up.

Currently, there's no GUI available but it's fairly easy to use the methods available using any dbus tool.

The methods available:
[METHOD] org.freesmartphone.GSM.PDP.ActivateContext( s:apn, s:user, s:password )
[METHOD] org.freesmartphone.GSM.PDP.DeactivateContext()
[METHOD] org.freesmartphone.GSM.PDP.GetCurrentGprsClass()
[METHOD] org.freesmartphone.GSM.PDP.ListAvailableGprsClasses()
[METHOD] org.freesmartphone.GSM.PDP.SetCurrentGprsClass( s:class_ )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus( i:index, s:status, a{sv}:properties )

Use ''mdbus -s -l'' to monitor the emitted signals. Signals will look roughly like this:

:ActivateContext( s:apn, s:user, s:password )
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:Once the connection is established (takes 3-4 seconds for me) a new signal is emitted
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'active'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:DeactivateContext
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>

== Using scripts ==

While we wait for the preferences part of FSO to be completed (and a GUI), we can use two shell scripts. You need to know three things to successfully connect via GPRS (your carrier should provide this information to you):
* the APN to use,
* the username, and
* the password.
If your APN has no username or password, you must still provide a string to satisfy the framework's input requirements. Entering bogus data, such as the "x" above, will suffice.

To connect, put the following in a file and make it executable (<code>chmod +x gprs-on.sh</code>):
<pre>
#!/bin/sh
APN="internet.parlino.se"
USERNAME="x"
PASSWORD="x"
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.ActivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN "$USERNAME" "$PASSWORD"
</pre>
To disconnect, use the following method instead (<code>chmod +x gprs-off.sh</code>):
<pre>
#!/bin/sh
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.DeactivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME
</pre>
The ''on'' script, using the ActivateContext method, will:
* setup a ppp interface (normally ppp0) (and assign IP address)
* setup (replace) the default route
* setup DNS
with settings received from the ISP.

For a list of known APN:s, see the [[GPRS#Some_APN_names_for_reference|main GPRS page]].

== Troubleshooting ==

* When a something like '''org.freedesktop.DBus.Error.UnknownMethod''' appears make sure that:
** frameworkd is started of course
** That the method did not hide in an other place than expected follow the white [[D-Bus|Rabbit]]
* Online script runs without error but pppd did not start
** use '''logread''' to debug....
** Maybe the kernelmodule ppp-generic is not loaded, try modprobe. ( you can do '''echo ppp-generic > /etc/modutils.d/ppp-generic''' to load the module at boot time )
** Maybe you have to do a '''mknod /dev/ppp c 108 0'''
* No MUX Channels available
** Means that the frameworkd has no free channel available to connect to the GSM Modem.
** Restart the frameworkd and the phone Application (aka ophoned or zhone). Works fine for me.
* MISC Troubleshooting
** Switch the frameworkd loglevel to DEBUG (/etc/frameworkd.conf)
** use the source!

== Using a GUI ==
[[Framework-settings]]

== See also ==
* [[GPRS]]
* [[OpenmokoFramework/mdbus]]

[[Category:FSO]]
[[Category:Networking]]
[[Category:Advanced End User]]

GPRS FSO

2009-01-30T08:25:39Z

Zem: /* Troubleshooting */

{{FSO}}
This page documents the GSM networking solutions (commonly known as GPRS) using the [[OpenmokoFramework|FreeSmartphone.Org]] framework (FSO).

There are other ways to enable wireless communications on the smartphone, including [[Bluetooth]] and [[Wireless_Networking|WLAN]].

== Current state ==

Since milestone 2 the system dbus has been extended with methods that enables connectivity using GPRS. The functionality is available under <code>org.freesmartphone.ogsmd</code> at <code>/org/freesmartphone/GSM/Device</code>.

The implementation should not interfere with other phone functionality, such as placing calls. In other words: you can use GPRS while talking on the phone without hanging up.

Currently, there's no GUI available but it's fairly easy to use the methods available using any dbus tool.

The methods available:
[METHOD] org.freesmartphone.GSM.PDP.ActivateContext( s:apn, s:user, s:password )
[METHOD] org.freesmartphone.GSM.PDP.DeactivateContext()
[METHOD] org.freesmartphone.GSM.PDP.GetCurrentGprsClass()
[METHOD] org.freesmartphone.GSM.PDP.ListAvailableGprsClasses()
[METHOD] org.freesmartphone.GSM.PDP.SetCurrentGprsClass( s:class_ )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus( i:index, s:status, a{sv}:properties )

Use ''mdbus -s -l'' to monitor the emitted signals. Signals will look roughly like this:

:ActivateContext( s:apn, s:user, s:password )
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:Once the connection is established (takes 3-4 seconds for me) a new signal is emitted
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'active'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:DeactivateContext
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>

== Using scripts ==

While we wait for the preferences part of FSO to be completed (and a GUI), we can use two shell scripts. You need to know three things to successfully connect via GPRS (your carrier should provide this information to you):
* the APN to use,
* the username, and
* the password.
If your APN has no username or password, you must still provide a string to satisfy the framework's input requirements. Entering bogus data, such as the "x" above, will suffice.

To connect, put the following in a file and make it executable (<code>chmod +x gprs-on.sh</code>):
<pre>
#!/bin/sh
APN="internet.parlino.se"
USERNAME="x"
PASSWORD="x"
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.ActivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN "$USERNAME" "$PASSWORD"
</pre>
To disconnect, use the following method instead (<code>chmod +x gprs-off.sh</code>):
<pre>
#!/bin/sh
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.DeactivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME
</pre>
The ''on'' script, using the ActivateContext method, will:
* setup a ppp interface (normally ppp0) (and assign IP address)
* setup (replace) the default route
* setup DNS
with settings received from the ISP.

For a list of known APN:s, see the [[GPRS#Some_APN_names_for_reference|main GPRS page]].

== Troubleshooting ==

* When a something like '''org.freedesktop.DBus.Error.UnknownMethod''' appears make sure that:
** frameworkd is started of course
** That the method did not hide in an other place than expected follow the white [[D-Bus|Rabbit]]
* Online script runs without error but pppd did not start
** use '''logread''' to debug....
** Maybe the kernelmodule ppp-generic is not loaded, try modprobe. ( you can do '''echo ppp-generic > /etc/modutils.d/ppp-generic''' to load the module at boot time )
** Maybe you have to do a '''mknod /dev/ppp c 108 0'''
* No MUX Channels available
** Means that the frameworkd has no free channel available to connect to the GSM Modem.
** Restart the frameworkd and the phone Application (aka ophoned or zhone) works fine.
* MISC Troubleshooting
** Switch the frameworkd loglevel to DEBUG (/etc/frameworkd.conf)
** use the source!

== Using a GUI ==
[[Framework-settings]]

== See also ==
* [[GPRS]]
* [[OpenmokoFramework/mdbus]]

[[Category:FSO]]
[[Category:Networking]]
[[Category:Advanced End User]]

GPRS FSO

2009-01-29T23:20:07Z

Zem: /* Troubleshooting */

{{FSO}}
This page documents the GSM networking solutions (commonly known as GPRS) using the [[OpenmokoFramework|FreeSmartphone.Org]] framework (FSO).

There are other ways to enable wireless communications on the smartphone, including [[Bluetooth]] and [[Wireless_Networking|WLAN]].

== Current state ==

Since milestone 2 the system dbus has been extended with methods that enables connectivity using GPRS. The functionality is available under <code>org.freesmartphone.ogsmd</code> at <code>/org/freesmartphone/GSM/Device</code>.

The implementation should not interfere with other phone functionality, such as placing calls. In other words: you can use GPRS while talking on the phone without hanging up.

Currently, there's no GUI available but it's fairly easy to use the methods available using any dbus tool.

The methods available:
[METHOD] org.freesmartphone.GSM.PDP.ActivateContext( s:apn, s:user, s:password )
[METHOD] org.freesmartphone.GSM.PDP.DeactivateContext()
[METHOD] org.freesmartphone.GSM.PDP.GetCurrentGprsClass()
[METHOD] org.freesmartphone.GSM.PDP.ListAvailableGprsClasses()
[METHOD] org.freesmartphone.GSM.PDP.SetCurrentGprsClass( s:class_ )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus( i:index, s:status, a{sv}:properties )

Use ''mdbus -s -l'' to monitor the emitted signals. Signals will look roughly like this:

:ActivateContext( s:apn, s:user, s:password )
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:Once the connection is established (takes 3-4 seconds for me) a new signal is emitted
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'active'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>
:DeactivateContext
<pre>
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus
from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'),
dbus.Dictionary({}, signature=dbus.Signature('sv')))
</pre>

== Using scripts ==

While we wait for the preferences part of FSO to be completed (and a GUI), we can use two shell scripts. You need to know three things to successfully connect via GPRS (your carrier should provide this information to you):
* the APN to use,
* the username, and
* the password.
If your APN has no username or password, you must still provide a string to satisfy the framework's input requirements. Entering bogus data, such as the "x" above, will suffice.

To connect, put the following in a file and make it executable (<code>chmod +x gprs-on.sh</code>):
<pre>
#!/bin/sh
APN="internet.parlino.se"
USERNAME="x"
PASSWORD="x"
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.ActivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN "$USERNAME" "$PASSWORD"
</pre>
To disconnect, use the following method instead (<code>chmod +x gprs-off.sh</code>):
<pre>
#!/bin/sh
BUSNAME="org.freesmartphone.ogsmd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.DeactivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME
</pre>
The ''on'' script, using the ActivateContext method, will:
* setup a ppp interface (normally ppp0) (and assign IP address)
* setup (replace) the default route
* setup DNS
with settings received from the ISP.

For a list of known APN:s, see the [[GPRS#Some_APN_names_for_reference|main GPRS page]].

== Troubleshooting ==

* When a something like '''org.freedesktop.DBus.Error.UnknownMethod''' appears make sure that:
** frameworkd is started of course
** That the method did not hide in an other place than expected follow the white [[D-Bus|Rabbit]]
* Online script runs without error but pppd did not start
** use '''logread''' to debug....
** Maybe the kernelmodule ppp-generic is not loaded, try modprobe. ( you can do '''echo ppp-generic > /etc/modutils.d/ppp-generic''' to load the module at boot time )
** Maybe you have to do a '''mknod /dev/ppp c 108 0'''
* No MUX Channels available
** Means that the frameworkd has no free channel available to connect to the GSM Modem.
** Restart the frameworkd and the phone Application works fine.
* MISC Troubleshooting
** Switch the frameworkd loglevel to DEBUG (/etc/frameworkd.conf)
** use the source!

== Using a GUI ==
[[Framework-settings]]

== See also ==
* [[GPRS]]
* [[OpenmokoFramework/mdbus]]

[[Category:FSO]]
[[Category:Networking]]
[[Category:Advanced End User]]

2009-01-20T13:41:29Z

Zem:

=UBoot=
==start Kernel==
===mount Rootfs===
===starting /sbin/init===

which is a link to /sbin/init.sysvinit

init itself reads the /etc/inittab.
The default runlevel is 5.

The runlevels are:

# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

but first, init starts:

====si::sysinit:/etc/init.d/rcS====

which starts /etc/init.d/rc S which starts all links in runlevel S (Startup)

'''root@om-gta02 /etc $''' ''ls /etc/rcS.d/ | cat''
*S02hostname.sh
*S02mountkernfs.sh
*S03udev
*S04mountdevsubfs.sh
*S06alignment.sh
*S10checkroot.sh
*S20modutils.sh
*S30procps.sh
*S35mountall.sh
*S37populate-volatile.sh
*S40networking
*S43portmap
*S45mountnfs.sh
*S55bootmisc.sh
*S97blueprobe
*S99finish.sh

Then it starts

====l5:5:wait:/etc/init.d/rc 5====

Runlevel 5...

'''root@om-gta02 /etc $''' ''ls /etc/rc5.d/ | cat''
*S03dbus-1
*S05xserver-nodm
*S10alsa-state
*S10dropbear
*S20apmd
*S20cron
*S20syslog
*S21avahi-daemon
*S23bluetooth
*S29frameworkd
*S35fso-gpsd
*S50usb-gadget
*S99rmnologin

====S:2345:respawn:/sbin/getty 115200 ttySAC2====

And finally init starts a getty on serial of course:

2008-02-01T20:09:20Z

Zem:

===Location===
Germany/NRW/Neandertal

===Device===
GTA01v4

===Service Provider===

Vodafone it self

===Incidents===
* see Bug #666
* '''Of course, all my SIM Cards are 3G enabled!'''

===Plans===
* Using the Phone to track Data for the Openstreetmap Project....
* Organizing either a Stone Age SIM Card or a firmware Upgrade for the GSM Modem