Openmoko - User contributions [en]

SFLphone

2011-06-03T21:05:12Z

Guyou: New page: [http://sflphone.org/ SFLphone] is a SoftPhone for desktop and embedded device. == Links == * [http://sflphone.org/ Home page] Category:Telephony Category:Internet Applications

[http://sflphone.org/ SFLphone] is a SoftPhone for desktop and embedded device.

== Links ==
* [http://sflphone.org/ Home page]

[[Category:Telephony]]
[[Category:Internet Applications]]

MiniMoko

2010-12-26T20:14:39Z

Guyou: Links

The '''MiniMoko''' is about building an extension for the [http://www.alwaysinnovating.com/products/minibook.htm MiniBook] from [http://www.alwaysinnovating.com/ Always Innovating].

This device is ARM based, and gets everything a phone would, except GSM connectivity and some other stuff.
Always Innovating agreed with such a project and accepted to giv us a hand !

So this page will list all the documents we have and all the work to do.

== Presenting MiniBook ==
Full specifications
* TI cortex-A8 with 3D and video acceleration
* 512MB (RAM) + 256MB (NAND) Memory
* Main storage: 8GB microSD card
* 480x320 3.5" capacitive touchscreen
* 30fps VGA front webcam
* Wifi 802.11 b/g/n, Bluetooth class 2.1
* Video output HDMI HD
* Two high-quality stereo speakers
* Internal microphone
* Headphone jack
* 3-dimensional accelerometer
* One 1500 mAh battery
* FCC, CE, UL-certified, 5V power adapter
* Bi-color silver/black case
* 64mm x 106mm x 9.3mm
* Secured attachment of the MID into a Touch Book Tablet
[[Image:MiniBook.png]]
== MiniMoko Concept ==

The main Idea of the MiniMoko, is to build a device, plugged through the 40pins connector (link to place here).
This device should be the same size of the MiniBook, so it's like adding a "slice".

In this device, we will put an USB hub, some 3G hardware, and let some plugs available. One should be on the side of the device (Mini USB)

The connector contains everything usefull to start something easilly : usb OTG. I/Os ...

== Features ==

List of features and corresponding components.

* 3G (Voice + Data) : '''Huawei E169''' (supports voice, small form factor) [http://3g-modem.wetpaint.com/page/Huawei+E169+%28E169G,+E169V,+K3520%29]
* GPS (aGPS ?)
* USB hub
* USB Charging+extra battery.
* Audio plug (Headset)

== ToDo ==

* Identifying hardware needed '''Work in progress'''
* Drawing a concept of the board (Basic schematics, then Logical schema )
* Drawing a concept of the box '''Perhaps no need, Have to see with A.I. already-done project'''
* Make the model board

== Links ==

* Minibook : [http://www.alwaysinnovating.com/products/minibook.htm]
* Schematics : [http://www.alwaysinnovating.com/company/schematics.htm]
* 40pins connector : [http://www.alwaysinnovating.com/wiki/index.php/40-pin_connector]
* SourceCode desriptor : [http://git.alwaysinnovating.com/cgit.cgi/ai.openembedded.dev/tree/recipes/linux/linux-omap-psp-2.6.32/omap3-touchbook/board-omap3touchbook.c]
* Schematics (PDF) : [http://freerunner.daily.online.fr/files/AI-TB-schematics.pdf]

[[Category:Hardware]]

Twinkle

2010-08-25T12:07:37Z

Guyou: URL

'''{{Note|This is particulary trivial for the Debian distribution.}}'''

[http://www.twinklephone.com/ Twinkle] is a Voice over IP ( VoIP ) application. Its purpose is to make phone calls via the Internet, instead of using the telephony network. Here is a way to get the command line twinkle working on Debian.

===Debian and QtMoko===
<pre>
apt-get install twinkle
</pre>

It will install some dependencies (about 83.0 MB for me) but after Twinkle have the advantage to be quite ergonomic and lightweight! (about 15MB in memory)

If you have some trouble to change some settings like the sound, you can modify it by editing the file ~/.twinkle/twinkle.sys
for example, alsa:
<pre>
# AUDIO
dev_ringtone=alsa:default
dev_speaker=alsa:default
dev_mic=alsa:default
validate_audio_dev=yes
au_reduce_noise_mic=yes
alsa_play_period_size=128
alsa_capture_period_size=32
oss_fragment_size=128
</pre>

You will probably need to switch between some profil of sound!:
# alsactl -f /usr/share/openmoko/scenarios/voip-handset.state restore

At the end of the utilisation you switch back using:
# alsactl -f /usr/share/openmoko/scenarios/stereoout.state restore
{{Note|<b>([[QtMoko]])</b> If you encouter the problem that you have not enough memory on QtMoko to install Twinkle, you can delete some of the installed deb-package from directory
<tt> /var/cache/apt/archives</tt>
and store them on
<tt>/media/card/archive</tt>
(create directory if necessary)}}

===SHR===
No commandline version yet

===Graphical User Interface===
Not available yet for Neo

===Links===
* [[Linphone]]
[[Category:Internet Applications]]

Wicd

2010-08-25T11:22:02Z

Guyou:

[http://wicd.sourceforge.net/ Wicd] is a wlan-gui written in python which helps setting up a wlan-connection.

= Installation =
== Debian-Image ==
First you need some packages installed to get wicd working:
apt-get install python-glade2 python-gtk2 wireless-tools wpasupplicant dhcp3-client
Now you can download the *_all.deb version of wicd stable from [https://sourceforge.net/project/showfiles.php?group_id=194573 here] and install it with:
dpkg -i *_all.deb
The wicd daemon should automatically be started after installation. You can start the wicd-client now with:
wicd-client -n

In Preferences you should give in: eth0 for wireless and usb0 for wired connection.

Wicd should show now your networks. Connecting to one of them is not working at the moment. You will always end up with "Putting down interface..." and nothing happens after that but work is in progress about this problem: [http://wicd.net/punbb/viewtopic.php?id=132 click].

== SHR ==
* install wicd (from www.opkg.org)
opkg install http://www.opkg.org/packages/ethtool_6_armv4t.ipk http://www.opkg.org/packages/wicd_1.5.6_armv4t.ipk
* write these settings into /etc/wicd/wired-settings.conf <br />
<pre>
[wired-default]
afterscript = None
broadcast = None
dns3 = None
ip = 192.168.0.202
dns1 = None
use_static_dns = False
default = True
netmask = 255.255.255.0
dns2 = None
beforescript = None
disconnectscript = None
gateway = 192.168.0.200
use_global_dns = False
</pre>
* if desired copy also all your wireless settings from your host to the FR: <br />
Host# sudo scp /etc/wicd/wireless-settings.conf root@192.168.0.202:/etc/wicd/.
* uninstall '''connman''' (network-manager)
FR# opkg remove connman*
warning: ssh connection will close and you have to reboot the system so wicd can establish the network
* reboot
FR# reboot

[[Category:Wlan software]]
[[Category:Settings Applications]]

NWA

2010-08-25T11:21:33Z

Guyou:

=Introduction=
[[Image:Nwa1.png|245px|right]]
WiFi on the freerunner has some problems, see [[WiFi Managers]].

So I decided to start a project to concentrate all the ideas about an ideal (but simple) GUI applet to manage WiFi connection.

The project is actually only a ''prealpha prototype'' to discover issues and implementation solutions. When ideas and needs will be clear it may be reimplemented in a more elegant way and with your preferred toolkit, now I'm using what I know better, C++ and QT with fast and dirty coding style!

It actually manages wpa_supplicant trough dbus and spawns udhcpc directly, replicating some Network Manager features. When a solid rock network manager will be available for the freerunner, and will handle the specific device capabilities/issues, NWA may be migrated to use it's api.

'''Please partecipate with contributions, ideas, hints as this may become your preferred WiFi manager for a while!!! feel free to edit this or the discussion page, and to contact me by email at nicola.mfb at gmail.com'''

=Requirements=
==A supplicant==
The main target is to use wpa_supplicant in a decent way, e.g. as a supplicant! You'll add your preferred wifi networks at home, at work, at your friend house and so on, and it will scan silently for them, connect when they are available and show a notification window/sound to alert you.

User has to be able to:
* enable/disable configured networks (for example any open network sometime is not desiderable)
* change the networks priority (for example use any open network only if other are not available)
* add new network manually or from scanning the area
* configure advanced network properties, WPA enteprise, EAP, LEAP, TTLS etc.

==Static IP vs DHCP==
The user should be able to use dhcp or static ip addresses.

==DNS handling==
It has to be able to restore some default DNS when exiting dhcp (eg. opendns, last used dns ...), suggestions on possible solutions are appreciated.

==System tray applet==
A sys tray icon should be showed changing it's aspect to reflect connection status.
It should indicate:
* inactive state (wifi disabled)
* scanning
* associated
* complete (associated + authenticated)
* key renewal
* complete + ip address received from dhcp or set manually
* signal strenght when associated
* historical signal strenght (like a graph scrolling every x seconds)
* foreign networks presence

Some special handling is required for Window Managers that does not support sys tray specification (like E17).
==Popup messages==
Popup transient messages should be showed when:
* connection fully complete, showing the received ip address
* disconnection
* wifi card enabled/disabled
* network found (if not connected)

The last has to be defined better, should you signal a new network only one? only one per session? etc.
==Sounds/Vibration==
Popup and/or vibration has to be associated with sounds to warn the user not looking at the device.

''please suggest some free sounds in every format supported by FSO/gstreamer''

As alternative some software synthetizer may be used.

==Configuration==
The configuration file should be in xml format, a default one will be provided that scan and connect to any open network, so the user may use NWA out of the box. When the user changes settings, the default file is copied in $HOME/.nwa.conf, that one will override the default.

The GUI must be complete but simple and should not allow the user to break the configuration with random clicks, all advanced tasks may be achieved editing the configuration file manually:

* dhcp client to use
* custom scripts to launch at iface up/down, ip received
* ...
==Device Integration==
NWA prefers FSO frameworkd based distro but should be capable to run on everywhere, actually it works fine on my laptop too.

==Power Managment==
With some AP the atheros power managment creates problems, NWA should support disabling it.
==Suspend/Resume==
It has to restore automagically the connection on suspend/resume cycles (the prototype does that without any special code as the nature of how it works).

=Development status/issues=
Wpa_supplicant dbus interface is not complete, if you quit the program in some hard way (signaling, closing X, etc) network definitions will not be deleted and at the next run NWA will be crazy, some workarounds:

* <del>kill wpa_supplicant at startup, it' not nice</del>
* <del>implement</del> implemented a remove/readadd interface to wpa when NWA is starting (it should delete all network definition, to be tested)
* <del>bore wpa_supplicant authors to implement the full dbus interface</del> a new version of dbus interface is on the road and I just contacted wpa_supplicant maintainers
* implements signal handling hooks (howewer a kill -9 will bypass it)

Another problem is that wpa_supplicant when connects to a networks signals only the state change and not the network id or network dbus path. This is a big problem as I would have the dhcp/static ip configuration associated to that and not to the essid as it may be the same between different networks.

Using the bssid to disambiguate the network may not be always possible for example when connecting to two big WDS networks with the same essid and thousand of AP.

'''Please comment the above problem and suggest alternatives. In the mean I added experimental static ip support guessing the net matching essid and bssid and avoiding enabling ambigue network configurations'''

<del>as wpa_supplicant does not signal the connected network we have to retrieve the essid with standard AF_INET ioctl, so qnetutils.cpp has to be improved</del> qnetutils.cpp now read the essid and bssid of the associated network.

The qt stylesheet has to be improved.

A startup script, launched when supplicant association is complete, is already implemented, it's a crude way to disable power management if needed.

<del>Actually destroying a running thread when application quits leads an "application crashed" on E, I'm not caring of it now</del> a better clean and quit handler has to be implemented.

To play sounds notification spawning a shell sound player may be weight and slow, so I think it's better to use FSO, while to have speech synthesis the script approach may be acceptable, <del>parameter passing has to be implemented in the configuration file (network name, ip address and so on)</del> just use $IFACE$ and $IP$ when you want it be automagically replaced with their respective values.

It seems as udhcpc when got an ip address set/unset/set_again the ipaddress, this is strange. The problem is not present with dhcpcd. Updates: this happens with udhcpc on a Cisco MDS wifi network and not with common AP.

<del>FSO returns random errors when PlaySound is used while a sound is already played</del> on debian sid there is no default dmix alsa configuration, this has to be declared in NWA prerequisites

Some small coding fixes need to be done, and some stupid comments removed :)

The first prealpha prototype is quite ready, it was developed on debian with Matchbox and matchbox-panel as sys trayer, under E qt balloon sys tray messages are showed in a random position on the screen, <del>so some special work around is needed</del> a primitive and animated "tooltip" was implemented. Multiple not overlapping message showing are not supported a queue handler has to be implemented.
I preferred to avoid qt sys tray baloon message on not-E wm too, as if the tray icon is in a middle/left position (becouse other tray icon are present), in some cases they are not readable.

It seems that udhcpc at exit does not deconfigure the interface anymore, strange I was quite sure it did before, this results in no "down" sound/notification when nwa disconnects.

Vibration support added, with GUI configuration, note: it does not work on FSO <= 5.1

Make sure your ar6000 kernel module includes the following patch: http://docs.openmoko.org/trac/attachment/ticket/2333/0001-ar6000-minimise-possibility-of-race-in-ar6000_ioctl_.patch otherwise you will experience a random kernel oops when you quit NWA.

=Installation=
Some guys asked for a preview, if you feel adventurous and want to join and test the prototype do the following:
echo "src/gz noko-testing-armv4t http://noko.sourceforge.net/testing/om2009/armv4t" >/etc/opkg/noko-feed.conf
opkg update
opkg install nwa
''This was tested only on *clean* OM2009 testing 5 and on *clean* SHR-unstable''

'''You have to disable all your custom scripts, solution, tricks as it may be incompatible with NWA'''

Versioning support was added, now if updates are available just do:
opkg update
opkg upgrade

''If you installed the very first preview nwa_svn you should remove it and use the versioned packages''

Source is cooming soon.

=Changelog=
* 0.01, the wanted preview version
* 0.02, added support for disabling/enabling sound notifications and/or vibration (work only on fso >= 5.5)
* 0.03, added support for static ip configuration, some other changes may break usability be warned.
* 0.04, modified the stylesheet for checkboxes, now easy clickable

=Using it=
NWA should work out of the box at first startup on the freerunner as it has some hardcoded settings in the xml parser and in the default configuration file targeted for the freerunner, it should connect to any open network as one becomes available without further user intervention.

This is only for demonstration pourpose or when you are traveling :), in normal cases you have to add/remove/edit/enable/disable networks.
==Adding a network==
Go on the "scan page" and click on "scan", after a bit available networks should appear, click on one of them and a wizard dialog will help you to configure the network with every kind of parameter wpa supplicant supports. I was able to add my home wpa/psk network and my campus EAP/TTLS/PAP radius enterprise network without problems.

You may click on "manual add" too without scanning, this is the beginning support for some kind of hidden networks (to be done) asap I have a configurable AP in my hands :)

The network is added and enabled, wpa_supplicant will decide how and when connect to it based on it's status priority etc.
==Enabling/Disabling/Editing/Removing networks==
Go on the "network page", you'll have two box, the upper contains the enabled network, the bottom the available (disabled) network. Clicking on a network shows a menu that permits you to do the needed operation.

So if you want to ignore open networks simply disable the "Any open" profile, and reenable it when walking around in the world.
==Enable/Disable/Autoenable WiFi==
This is the FSO ousaged control, so be warned if you enable wifi from external application you'll see NWA working even if the wifi status is "disabled".

The autoenable button let you choose if autoenable the wifi resource at startup.
==Tray Icon==
On WM with a standard trayer, NWA will show an icon with current wpa_supplicant status and historical signal strenght indication. Clicking on the icon will show the main window, to hide the main window use your window manager capability.

=Advanced Configuration=
NWA read $HOME/.nwa.conf configuration file, if it does not exists it read /usr/share/nwa/defaultconfiguration.xml.
When you change some configuration with the GUI the default file is copied in $HOME/.nwa.conf.

All common configuration is done in the GUI, for advanced usage you may edit your $HOME/.nwa.conf file (copy it if it does not exists yet)
==Example configuration file==
<pre>
<xml version="1.0">



<dhcpclients>
<dhcpclient name="udhcpc -f -i $IFACE$" default="yes"/>
<dhcpclient name="none" />
</dhcpclients>

<autoenable value="yes" />

<iface name="eth0" maxquality="255"/>

<networks>
<network name="Any Open" key_mgmt="NONE" enabled="yes" disabledhcp="false" upscript="" downscript=""/>
</networks>

<ifupscript path="logger NWA iface $IFACE$ up"/>
<ifdownscript path="logger NWA iface $IFACE$ down"/>

<ipupscript path="logger NWA iface $IFACE$ got ip $IP$"/>
<ipdownscript path="logger NWA iface $IFACE$ losed ip $IP$"/>
<brokenkernelhack value="no"/>
<apscan mode="1"/>

<usefso value="true"/>
<upsound path="/usr/share/nwa/sounds/bonus.ogg"/>
<downsound path="/usr/share/nwa/sounds/gameover.ogg"/>

<soundprofile value="1"/>

<alwaysshowwindow value="no" />
</xml>
</pre>

==Static ip address==
<del>It will supported in the GUI asap, I need to study rtnetlink to configure network without spawning externals command, but actually it's possibile to change manually the configuration file to achieve that, here an example:

<network name="my static ip network" key_mgmt="NONE" enabled="yes" disabledhcp="true" upscript="ifconfig $IFACE$ 192.168.1.10 netmask 255.255.255.0" downscript=""></del>

Experimental support for static ip was added, with GUI too.

==Hook scripts==
NWA support a lot of hook scripts to configure it in specific scenarios. You may start vpn, compute advanced routing or network configuration, play sounds, start applications and so on. You have:

* ifupscript: global scope, launched when the wpa_supplicant associates and authenticates to one of the enabled network
* ifdownscript: global scope, launched when wpa_supplicant disconnects from a network
* ipupscript: global scope, launched when the wifi card get an ip address
* ipdownscript: gloabl scope, launched when the wifi card looses an ip address (actually does not work if multiple ip address are set)
* upscript: network scope, launched when the specified network associates and authenticates
* downscript: network scope, launched when the specified network disconnects

==How to setup complex scripts==
You have two options:
* create the needed script with how many commands you need and use it in the configuration file
* use a format compatible with xml and exec call. eg: "sh -c &quote;xxxx; yyyy; zzzz&quote;"

=Test cases=
This is a list of use cases to help in debugging NWA. I use it, if time is available, before pushing a new version to the feed , If some of there are wrong please retrying after opkg remove nwa, opkg update, opkg install and contact me if the problem persists.

Feel free to add your custom cases.

{| border=1
!Test!!Status!!Note
|-
|First launch after installation, autoconnect to the first open network||{{Unknown}}||
|-
|Add WPA PSK network from scan||{{Yes}}||
|-
|Add WPA PSK network from scan forcing bssid||{{Yes}}||
|-
|Add WPA PSK network manually||{{Yes}}||
|-
|Add WPA Radius Enterprise TTLS/PAP network from scan||{{Yes}}||
|-
|Add WPA Radius Enterprise TTLS/PAP network manually||{{Unknown}}||
|-
|Disable network disconnects if currently connected||{{Yes}}||
|-
|Enable network connects if available and currently disconnected||{{Yes}}||
|-
|Delete network disconnects if currently connected||{{Yes}}||
|-
|Delete all networks make ws inactive||{{Yes}}||
|-
|Survive to Suspend/Resume cycle and autoreconnects||{{Yes}}||
|-
|Change Passphrase disconnects a network, at least at next key renewal||{{Maybe}}||
|-
||Static ip configuration/routing by per-network scripts||{{Yes}}||
|-
||Static ip configuration/routing by rtnetlink/GUI||{{Yes}}||
|-
||Multiple static ip||{{Unknown}}||
|-
|Normal user privilege||{{Maybe}}||You need to globally disable dhcp and launch it with ifaceup and ifacedown setuided scripts, tested on my laptop
|-
|Work on systray window manager||{{Yes}}||it shows a systray icon with historical signal strength, clicking on it show the main window, while closing that will only hide
|-
|Work on not systray window manager||{{Yes}}||closing the window will quit NWA
|-
|Work on OM2009 testing v5||{{Yes}}||Out of the box
|-
|Work on OM2009 testing v5 + update/upgrade||{{Yes}}||"
|-
|Work on SHR-unstable||{{Yes}}||
|-
|Work on debian sid||{{Yes}}||random kernel oops with default kernel (might need patch - see above)
|-
|Work on hackable:1||{{Unknown}}
|}

[[Category:Wlan software]]
[[Category:Settings Applications]]

Mokonnect

2010-08-25T11:21:13Z

Guyou:

[[Category:System Applications]]
[[Category:Networking]]
[[Category:Wlan_software]]
[[Category:ApplicationsElementary]]
[[Category:Settings Applications]]

{{Application|Mokonnect}}
[[Image:Mokonnect-ss1.png|thumb]]
[[Image:mokonnect-ss2.png|thumb]]

== About ==
Mokonnect is a project i started to provide an easy yet powerfull to use connection manager for the openmoko neo freerunner.<br/>
It is based on connman, e17, python.<br/>
The goals of the project are:<br/>

* Provide intuitive easy to use interface
* Provide all connectivity options under one application
* Provide advanced routing options from the gui
* Support profiles for every configuration type for faster selection later

== More information ==
More information is at the project's wiki page.<br/>
[http://www.assembla.com/wiki/show/shrdev Mokonnect Wiki]<br/>
(Navigation is on the right side panel)<br/>

== Resources ==
WIKI: [http://www.assembla.com/wiki/show/shrdev Mokonnect Wiki]<br/>
SVN Repository: [http://subversion.assembla.com/svn/shrdev SVN Repo]<br/>
SVN Web Access: [http://code.assembla.com/shrdev/subversion/nodes/Mokonnect/trunk SVN Web Access]<br/>

KnjMokoWifi

2010-08-25T11:20:17Z

Guyou: Category

{{ApplicationBox|
Name=[[knjMokoWifi]]|
Description=|
Screenshot=knjMokoWifi - Connecting to an AP.png|
Homepage=http://wordpress.kaspernj.org/?cat=15|
TestedOn=Debian, Om 2008.8, SHR Testing|
PackageName=knjmokowifi
}}

== About the application ==

knjMokoWifi is an application for managing the wireless interface in the OpenMoko. The first version of the application was released 2009 in february, but the development began in December 2008. It has been written by [[User:Kaspernj|Kaspernj]] and can be downloaded through the [[Knjrepository]].

The newest version is stable and useable. It supports no-encryption, WEP Key, WEP String and WPA through wpa-supplicant. It works be generating working configs for wpa-supplicant and executing commands like udhcp (the DHCP-tool on the OpenMoko), iwconfig and such.

Further more it supports profiles, where you can save essid's and key's, so you dont have to enter all that stuff over and over.

The application is written in [http://www.php.net PHP] and uses the [http://gtk.php.net PHP-GTK] extension.

The application it currently developed for Debian as the operating system on the phone, but it also works with OM2008 or SHR.

== Screenshots ==

[[Image:knjMokoWifi - Main Window.png]]

[[Image:knjMokoWifi - Connecting to an AP.png]]

[[Image:knjMokoWifi - Status Window.png]]

[[Category:Wlan software]]
[[Category:Settings Applications]]

SHR

2010-05-27T13:34:56Z

Guyou: /* Image content */ add link

{{Languages|SHR}}
[[Image:SHR-Logo.png|right|thumb|300px|SHR ]]
{{Distributions|SHR}}

'''SHR''' (Stable Hybrid Release) is a community driven distribution based on the [[FSO]] framework. SHR can use several different graphical toolkits, for example GTK or EFL. At first, SHR was introduced in order to use the [[Om 2007.2]] GTK software in combination with the new FSO, but things have changed, now SHR comes with a full [[SHR User Manual]] in the OpenMoko-Wiki, that supports novice users in their first steps and SHR moves forward to a distribution for every day use.

SHR is based on linux kernel and [http://www.openembedded.org/ Openembedded]. <tt>XGlamo</tt> is providing X server environment and [[Illume]] (Enlightment window manager module for small devices) is providing comfortable finger controlled desktop environment. Under the hood of the pretty desktop there is [[FSO]] middleware talking to the GSM modem, GPS module as well as to the other bits of hardware. SHR <tt>ophonekitd</tt> daemon is run with X server start-up and it communicates with FSO via <tt>d-bus</tt>. SHR phone applications talk to <tt>ophonekitd</tt> and also to FSO so for example when you receive a phone call, the dialer is launched to provide a way of answering it. ''Dialer'', ''Contacts'' and ''Messages'' applications are part of the SHR internal <tt>libframeworkd-phonegui-efl</tt> library, ''Phonelog'' is an extra application written in python-gtk.

SHR wiki with more instructions, descriptions and informations is available on http://wiki.shr-project.org/

==Feature overview==
In the overview below are all the essential features and their status for the current '''out of the box''' SHR unstable distribution (latest+[http://en.wikipedia.org/wiki/Module_(Linux) modules]+updates). Green indicates that this part is functioning well, red indicates a known requirement which will be implemented later on and orange indicates functionality that can (and should) be fixed easily in the distribution for known fixes are available.

{| cellspacing="0" class="sortable wikitable" border="1" style="font-size: 85%; text-align: left; width: auto;"
|-
! Category
! Name
! Functionality
! Comments
|-
| System
| Power Management
| style="background:#88FF88;"| Suspend
| when slow, use [[Qi]]
|-
| System
| Package manager
| style="background:#88FF88;"| Installing and upgrading packages
| Works well. For packages not in the repository, just ask for them to be added via the trac
|-
| System
| Keyboard
| style="background:#88FF88;"| Offer stylus and finger friendly keyboards
| Alternative keyboards are now available in repositories.
|-
| GSM
| Network
| style="background:#88FF88;"| Connect via SIM and PIN
|
|-
| GSM
| Network
| style="background:#FF8888;"| Flight mode
| style="background:#FF8888;"| [http://trac.shr-project.org/trac/ticket/333 SHR ticket #333]
|-
| GSM
| Dailer
| style="background:#88FF88;"| Receiving Call
|
|-
| GSM
| Dailer
| style="background:#88FF88;"| Making Call
|
|-
| GSM
| Dailer
| style="background:#FF8888;"| Speed dial voice mail
| style="background:#FF8888;"| Not available. Should by default have keypad enabled.
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Overview Log (In, Out, Answered, All)
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Display Missed Calls
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Making reply Call from Log
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Sending reply SMS from Log
|
|-
| Shared
| Phone Log
| style="background:#88FF88;"| Creating new SIM contact from Log
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Receiving SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| SIM phonebook lookup for SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| View overview of received SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| View overview of sent SMS|
| Sent SMS are now stored. They share folder with received SMS
|-
| GSM
| SMS
| style="background:#FF8888;"| Request SMS delivery receipt
| style="background:#FF8888;"| [http://trac.shr-project.org/trac/ticket/295 SHR ticket #295]
|-
| GSM
| SMS
| style="background:#88FF88;"| Selecting SMS from Overview
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Viewing SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Writing SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending new SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending reply SMS
|
|-

| GSM
| SMS
| style="background:#88FF88;"| Forwarding SMS
|
|-

| GSM
| SMS
| style="background:#88FF88;"| Making reply Call
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Deleting SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Storing received contact in contacts
|
|-
| GSM
| GPRS
| style="background:#88FF88;"| Configuring and Enabling GPRS
| Settings->Connectivity: GPRS connect
|-
| Shared
| Contacts
| style="background:#88FF88;"| Reading SIM contacts
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Selecting SIM contact from Overview
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Creating new SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Editing SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Deleting SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Quick lookup contact with keyboard
| Tap and hold (or drag) near right side of the screen
|-
| Shared
| Contacts
| style="background:#88FF88;"| Calling contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Sending SMS to contact
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Sending contact via SMS to contact
|
|-
| WiFi
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling WiFi connection
|
|-
| GPS
| Service
| style="background:#88FF88;"| Receiving GPS data
| automatically turning on when needed
|-
| USB
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling USB connection
| done automatically
|-
| Audio
| Headset
| style="background:#88FF88;"| Handsfree calling
|
|-
|-
| Bluetooth
| Headset
| style="background:#FF8888;"| Handsfree calling with bluetooth
|
|-
|}

==Image content==

These applications are included in the full and lite SHR images:
{|class="wikitable" border="1" cellpadding="0" cellspacing="0" width=100%

! width=16%| !! width=42%|Full image content !! width=42%|Lite image content
|-
| Window Manager ||
* illume
||
* illume
|-
| Engine ||
* frameworkd
||
* frameworkd
|-
| Telephony ||
* Dialer (Call/Receive, DTMF, Speaker mode)
* Contacts (Call/Modify/Create/...)
* Messages (Receive/Compose/Answer/...)
* Pyphonelog (received/emitted/missed calls logging)
||
* Dialer (Call/Receive, DTMF, Speaker mode)
* Contacts (Call/Modify/Create/...)
* Messages (Receive/Compose/Answer/...)
* Pyphonelog (received/emitted/missed calls logging)
|-
| GPS ||
* TangoGPS
||
* TangoGPS
|-
| Utilities ||
* Calculator
* Alarm
* Notes (opimd based)
* GPE Scap (Take screenshot)
* GPE Sketchbook
* vala-terminal
||
* Calculator
* Alarm
* vala-terminal

|-

| Media ||

* Vagalume (Last.fm client)
* Intone (audio player)
||

|-

| Internet ||
* Pidgin (Instant Messenger)
* Ventura (Browser)
||

|-

| Games ||
* Numptyphysics
* Mokomaze
||
|-
| Settings ||
* SHR Settings
* [[Mokonnect]] (Network Manager)
||
* SHR Settings
|-
|}

==User Manual==
SHR has a full [[SHR User Manual|User Manual]].

==SHR/Stable release party==
Renaming of SHR/Testing to SHR/Stable was expected in March 2010 but hasn't yet been done. This will be the first SHR Stable release. To celebrate this "historic" event some of the community are planning to have small parties/ get-to-gethers across the world. If you wish to attend/ organise such a party please fill up your details on the [[SHR Party Page]]

==SHR Use cases==
*[[SHR case studies]]

== More Information ==

Visit:
* [http://blog.shr-project.org Blog]
* [http://trac.shr-project.org Project Homepage/Trac (Bugtracker)]
* [http://git.shr-project.org Git (Sourcecode-repository)]
* [http://build.shr-project.org Buildhost (Downloads)]
* [http://shr-project.org/trac/wiki/Tweaks Tweaks (On the Wiki)]
* [http://lists.shr-project.org SHR User and Development Mailing Lists]

[[Category:SHR| ]]

Android

2010-05-11T19:47:05Z

Guyou: Move External links to /* See Also */ section

{{Languages|Android}}
{{Distributions|Android}}

{|align=right
|__TOC__
|}
[[Image:Android-logo.png]]
= Introduction =

{{Note|The Android for [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] development now takes place [http://code.google.com/p/android-on-freerunner/ here].}}

This page is the central place for documentation about Android on the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Although Android is publicized as being [[open source software]] (most of the source code has been released) parts of the code have not been released yet.

A lot of work is being done to get Android functioning properly on the [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] and it is likely, in the near future, to be the distribution most suited for using the FreeRunner as a phone.

Inside the FreeRunner 3 software components are working:
* '''bootloader''': a small program that runs first and starts everything else when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from [[NOR_Flash|NOR]] or NAND is booted).
* '''kernel''': the central component in the Linux operating system.
* '''root filesystem''': contains all the files that make up the commands and applications that you can run.
* Furthermore for the installation you have to format your MicroSD-Card because Android will store data on it.

= Usage =
See: [[Android usage]] for detailed instructions on using Android on the FreeRunner. Updated with the functionality of the Koolu Beta 7 results.

Android is gaining functionality on the FreeRunner all the time and with Michael Trimarchi's [http://panicking.kicks-ass.org/download/ (panicking)] images, and Koolu Beta 7, it is possible to use as an everyday phone!

=== Michael Trimarchi setup ===
Michael has announced he is working on the Glamo (screen aceeleration) code.
Prerequisites for Michael's good work are:

* Use the jffs version 14.6 and the kernel v17.
* Uboot

You can then hope to achieve :

* GSM calls
* SMS
* Adding, removing and importing contacts
* GPRS
* Wi-Fi

Caveats

* Volume during voice calls is very low.
* Wi-Fi does not reconnect after sleep - [http://wiki.openmoko.org/wiki/Android_usage#Wifi setup]
* You have to disable PIN security on your SIM card.

[http://spreadsheets.google.com/ccc?key=popRpaZG1txEXGHDDboxtIA&hl=en_GB Android function sheet]

= Installation =

See: [[Android on Freerunner]]

= Development =
See: [[Android porting]]

There were developers being paid to work on the port by [http://koolu.com/ Koolu.]
For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android].<br/>
There is a Android Freerunner Mailing list hosted by Koolu [http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org]<br/>
Site is dead (2010-05-11).

There is also some great unpaid work going on at [http://panicking.kicks-ass.org/blog/index.php Linux Embedded]

New development is done on http://code.google.com/p/android-on-freerunner/

= News =
* 01 Oct 09 - new Home http://code.google.com/p/android-on-freerunner/ ( including googlegroup,IRC,mailinglist,... )
* 19 Sept 09 - from Koolu-Forum: ..."So I'm glad to announce a new Android Cupcake release for Freerunner! It's basically a merge of the Koolu code with Michael Trimarchi's enhancements and a few bug fixes and cosmetic things I've added. You can download it at our new Google Code site: http://code.google.com/p/android-on-freerunner/downloads/list "...
* 22 May 09 - Koolu Releases Beta7 [http://trac.koolu.org/wiki/Releases]
* 15 April 09 - Koolu Releases Beta6 [http://trac.koolu.org/wiki/Releases]
* 07 March 09 - Panicking released a cupcake [http://panicking.kicks-ass.org/download/ rootfs]
* 26 February 09 - As promised, Sean McNeil has released source code to [[GSM]] libraries [https://review.source.android.com/Gerrit#change,9013 Source]
* 20090204 Koolu releases its Beta3 Android [http://freerunner.android.koolu.com/release-files release].
** Changelog:
*** Added GPS library that supports GPS under Android
*** MAX_PROCESSES patch to enable more background processes to be run (fixes Pictures application)
*** Added Dalvik optimization setting
*** Started including 3rd party applications
*** Updated user interfaces for GPS and Bluetooth to match new kernel
*** Now report RSSI of Wifi signals to upper application layer
*** Enable libsoundpool compilation to support audible clicks

* 20090122 Koolu releases its Beta2 Android [http://freerunner.android.koolu.com/release-files release].

* 20081219 Koolu releases its Beta Android [http://forum.koolu.org/files/androidfs-koolu-1_0.jffs2 Image] and [http://forum.koolu.org/files/uImage-android-patched_bc2caff9cdef8a16.bin kernel].

* 20081202 [http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.org http://git.koolu.org]. For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android]. TODO: Find out where this link supposed to go->See the [[Android_porting#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']

= See also =
* http://code.google.com/p/android-on-freerunner/

== Usage ==

* [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial Short Video demo of Android] on [[FreeRunner]] to show how usable it is.

* [http://braydon.com/blog/2009/5/1/koolu-android-on-neo-freerunner-video Koolu beta6 on Neo Freerunner Video]

* http://www.androidfreeware.org/

* http://andappstore.com/

* http://slideme.org/

* http://www.openintents.org/

== Videos ==
* Videos : [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial]
* [http://youtube.com/watch?v=m4NbsLmF9j0 YouTube Video 1]
* [http://youtube.com/watch?v=r6Op-7tNTiw YouTube Video 2]

[[Category:Android| ]]

Android

2010-05-11T19:42:01Z

Guyou: /* See also */ Google project

{{Languages|Android}}
{{Distributions|Android}}

{|align=right
|__TOC__
|}
[[Image:Android-logo.png]]
= Introduction =

{{Note|The Android for [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] development now takes place [http://code.google.com/p/android-on-freerunner/ here].}}

This page is the central place for documentation about Android on the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Although Android is publicized as being [[open source software]] (most of the source code has been released) parts of the code have not been released yet.

A lot of work is being done to get Android functioning properly on the [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] and it is likely, in the near future, to be the distribution most suited for using the FreeRunner as a phone.

Inside the FreeRunner 3 software components are working:
* '''bootloader''': a small program that runs first and starts everything else when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from [[NOR_Flash|NOR]] or NAND is booted).
* '''kernel''': the central component in the Linux operating system.
* '''root filesystem''': contains all the files that make up the commands and applications that you can run.
* Furthermore for the installation you have to format your MicroSD-Card because Android will store data on it.

= Usage =
See: [[Android usage]] for detailed instructions on using Android on the FreeRunner. Updated with the functionality of the Koolu Beta 7 results.

Android is gaining functionality on the FreeRunner all the time and with Michael Trimarchi's [http://panicking.kicks-ass.org/download/ (panicking)] images, and Koolu Beta 7, it is possible to use as an everyday phone!

=== Michael Trimarchi setup ===
Michael has announced he is working on the Glamo (screen aceeleration) code.
Prerequisites for Michael's good work are:

* Use the jffs version 14.6 and the kernel v17.
* Uboot

You can then hope to achieve :

* GSM calls
* SMS
* Adding, removing and importing contacts
* GPRS
* Wi-Fi

Caveats

* Volume during voice calls is very low.
* Wi-Fi does not reconnect after sleep - [http://wiki.openmoko.org/wiki/Android_usage#Wifi setup]
* You have to disable PIN security on your SIM card.

[http://spreadsheets.google.com/ccc?key=popRpaZG1txEXGHDDboxtIA&hl=en_GB Android function sheet]

== External Links ==

* [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial Short Video demo of Android] on [[FreeRunner]] to show how usable it is.

* [http://braydon.com/blog/2009/5/1/koolu-android-on-neo-freerunner-video Koolu beta6 on Neo Freerunner Video]

* http://www.androidfreeware.org/

* http://andappstore.com/

* http://slideme.org/

* http://www.openintents.org/

= Installation =

See: [[Android on Freerunner]]

= Development =
See: [[Android porting]]

There were developers being paid to work on the port by [http://koolu.com/ Koolu.]
For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android].<br/>
There is a Android Freerunner Mailing list hosted by Koolu [http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org]<br/>
Site is dead (2010-05-11).

There is also some great unpaid work going on at [http://panicking.kicks-ass.org/blog/index.php Linux Embedded]

New development is done on http://code.google.com/p/android-on-freerunner/

= News =
* 01 Oct 09 - new Home http://code.google.com/p/android-on-freerunner/ ( including googlegroup,IRC,mailinglist,... )
* 19 Sept 09 - from Koolu-Forum: ..."So I'm glad to announce a new Android Cupcake release for Freerunner! It's basically a merge of the Koolu code with Michael Trimarchi's enhancements and a few bug fixes and cosmetic things I've added. You can download it at our new Google Code site: http://code.google.com/p/android-on-freerunner/downloads/list "...
* 22 May 09 - Koolu Releases Beta7 [http://trac.koolu.org/wiki/Releases]
* 15 April 09 - Koolu Releases Beta6 [http://trac.koolu.org/wiki/Releases]
* 07 March 09 - Panicking released a cupcake [http://panicking.kicks-ass.org/download/ rootfs]
* 26 February 09 - As promised, Sean McNeil has released source code to [[GSM]] libraries [https://review.source.android.com/Gerrit#change,9013 Source]
* 20090204 Koolu releases its Beta3 Android [http://freerunner.android.koolu.com/release-files release].
** Changelog:
*** Added GPS library that supports GPS under Android
*** MAX_PROCESSES patch to enable more background processes to be run (fixes Pictures application)
*** Added Dalvik optimization setting
*** Started including 3rd party applications
*** Updated user interfaces for GPS and Bluetooth to match new kernel
*** Now report RSSI of Wifi signals to upper application layer
*** Enable libsoundpool compilation to support audible clicks

* 20090122 Koolu releases its Beta2 Android [http://freerunner.android.koolu.com/release-files release].

* 20081219 Koolu releases its Beta Android [http://forum.koolu.org/files/androidfs-koolu-1_0.jffs2 Image] and [http://forum.koolu.org/files/uImage-android-patched_bc2caff9cdef8a16.bin kernel].

* 20081202 [http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.org http://git.koolu.org]. For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android]. TODO: Find out where this link supposed to go->See the [[Android_porting#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']

= See also =
* http://code.google.com/p/android-on-freerunner/

== Videos ==
* Videos : [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial]
* [http://youtube.com/watch?v=m4NbsLmF9j0 YouTube Video 1]
* [http://youtube.com/watch?v=r6Op-7tNTiw YouTube Video 2]

[[Category:Android| ]]

Android

2010-05-11T19:40:21Z

Guyou: /* Development */ Google project

{{Languages|Android}}
{{Distributions|Android}}

{|align=right
|__TOC__
|}
[[Image:Android-logo.png]]
= Introduction =

{{Note|The Android for [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] development now takes place [http://code.google.com/p/android-on-freerunner/ here].}}

This page is the central place for documentation about Android on the [[Neo1973 Hardware|Neo 1973]] and [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] handsets.

[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Although Android is publicized as being [[open source software]] (most of the source code has been released) parts of the code have not been released yet.

A lot of work is being done to get Android functioning properly on the [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] and it is likely, in the near future, to be the distribution most suited for using the FreeRunner as a phone.

Inside the FreeRunner 3 software components are working:
* '''bootloader''': a small program that runs first and starts everything else when the FreeRunner is powered on or reset (depending on [[Booting the Neo FreeRunner|how you reset it]], the version from [[NOR_Flash|NOR]] or NAND is booted).
* '''kernel''': the central component in the Linux operating system.
* '''root filesystem''': contains all the files that make up the commands and applications that you can run.
* Furthermore for the installation you have to format your MicroSD-Card because Android will store data on it.

= Usage =
See: [[Android usage]] for detailed instructions on using Android on the FreeRunner. Updated with the functionality of the Koolu Beta 7 results.

Android is gaining functionality on the FreeRunner all the time and with Michael Trimarchi's [http://panicking.kicks-ass.org/download/ (panicking)] images, and Koolu Beta 7, it is possible to use as an everyday phone!

=== Michael Trimarchi setup ===
Michael has announced he is working on the Glamo (screen aceeleration) code.
Prerequisites for Michael's good work are:

* Use the jffs version 14.6 and the kernel v17.
* Uboot

You can then hope to achieve :

* GSM calls
* SMS
* Adding, removing and importing contacts
* GPRS
* Wi-Fi

Caveats

* Volume during voice calls is very low.
* Wi-Fi does not reconnect after sleep - [http://wiki.openmoko.org/wiki/Android_usage#Wifi setup]
* You have to disable PIN security on your SIM card.

[http://spreadsheets.google.com/ccc?key=popRpaZG1txEXGHDDboxtIA&hl=en_GB Android function sheet]

== External Links ==

* [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial Short Video demo of Android] on [[FreeRunner]] to show how usable it is.

* [http://braydon.com/blog/2009/5/1/koolu-android-on-neo-freerunner-video Koolu beta6 on Neo Freerunner Video]

* http://www.androidfreeware.org/

* http://andappstore.com/

* http://slideme.org/

* http://www.openintents.org/

= Installation =

See: [[Android on Freerunner]]

= Development =
See: [[Android porting]]

There were developers being paid to work on the port by [http://koolu.com/ Koolu.]
For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android].<br/>
There is a Android Freerunner Mailing list hosted by Koolu [http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org]<br/>
Site is dead (2010-05-11).

There is also some great unpaid work going on at [http://panicking.kicks-ass.org/blog/index.php Linux Embedded]

New development is done on http://code.google.com/p/android-on-freerunner/

= News =
* 01 Oct 09 - new Home http://code.google.com/p/android-on-freerunner/ ( including googlegroup,IRC,mailinglist,... )
* 19 Sept 09 - from Koolu-Forum: ..."So I'm glad to announce a new Android Cupcake release for Freerunner! It's basically a merge of the Koolu code with Michael Trimarchi's enhancements and a few bug fixes and cosmetic things I've added. You can download it at our new Google Code site: http://code.google.com/p/android-on-freerunner/downloads/list "...
* 22 May 09 - Koolu Releases Beta7 [http://trac.koolu.org/wiki/Releases]
* 15 April 09 - Koolu Releases Beta6 [http://trac.koolu.org/wiki/Releases]
* 07 March 09 - Panicking released a cupcake [http://panicking.kicks-ass.org/download/ rootfs]
* 26 February 09 - As promised, Sean McNeil has released source code to [[GSM]] libraries [https://review.source.android.com/Gerrit#change,9013 Source]
* 20090204 Koolu releases its Beta3 Android [http://freerunner.android.koolu.com/release-files release].
** Changelog:
*** Added GPS library that supports GPS under Android
*** MAX_PROCESSES patch to enable more background processes to be run (fixes Pictures application)
*** Added Dalvik optimization setting
*** Started including 3rd party applications
*** Updated user interfaces for GPS and Bluetooth to match new kernel
*** Now report RSSI of Wifi signals to upper application layer
*** Enable libsoundpool compilation to support audible clicks

* 20090122 Koolu releases its Beta2 Android [http://freerunner.android.koolu.com/release-files release].

* 20081219 Koolu releases its Beta Android [http://forum.koolu.org/files/androidfs-koolu-1_0.jffs2 Image] and [http://forum.koolu.org/files/uImage-android-patched_bc2caff9cdef8a16.bin kernel].

* 20081202 [http://www.koolu.com Koolu], a Freerunner distributor, has released the source code of their Android port at [http://git.koolu.org http://git.koolu.org]. For details on the project source and some real detailed instructions on building the source, see the [http://trac.koolu.org/ the Koolu Trac Website for Android]. TODO: Find out where this link supposed to go->See the [[Android_porting#Building the Koolu Android Source]] instructions below for how to build an Android image for Freerunner.

* 20081104 The first Android-image has been successfully created by Sean McNeil! - sms and calling works, wifi and bluetooth doesn't. [http://onlinedev.blogspot.com/2008/11/porting-android-phase-3-done.html ''news-source'']

= See also =
* Videos : [http://digg.com/linux_unix/Video_demo_of_Freerunner_running_Android_Cupcake_Tutorial]
* [http://youtube.com/watch?v=m4NbsLmF9j0 YouTube Video 1]
* [http://youtube.com/watch?v=r6Op-7tNTiw YouTube Video 2]

[[Category:Android| ]]

Using the Neo as an USB Mass storage device

2010-05-05T11:58:06Z

Guyou:

==Make the Neo FreeRunner act as a mass storage device==

To access the microSD card in the Freerunner from the host computer as if it were a USB key or memory stick, the following script can be used:

#!/bin/sh
ifdown usb0
umount /media/card
rmmod g_ether
modprobe g_file_storage file=/dev/mmcblk0 stall=0
Reference: [http://lists.openmoko.org/pipermail/community/2008-September/029261.html Petr Vanek's "usb mass media storage" message on the community mailing list], updated by [[User:Mmontour|Mmontour]] 16:25, 21 March 2009 (UTC). The "stall=0" parameter is required on at least some systems to prevent timeouts and errors.

The card is not accessible from the Freerunner in this mode. Sometimes, however, the message displayed may be "interface usb0 already configured" and no device would be detected by the OS FreeRunner is connected to. This issue needs to be addressed properly.

==Make the Neo FreeRunner revert to USB networking==

Be sure to properly unmount on the host computer first, just as you would with any other USB storage.

The following script can be used:

#!/bin/sh
rmmod g_file_storage
mount /dev/mmcblk0p1 /media/card
modprobe g_ether
ifup usb0

==Is it possible to pretend to be a USB hub, providing both g_ether and g_file_storage?==

Not yet. At the moment it's one gadget driver at a time, but there is a project under way to allow use of multiple gadget drivers together. See [http://blog.felipebalbi.com/?p=44 this blog posting called 'USB Composite Gadget Framework'] or [http://www.linux-usb.org/gadget/ Linux-USB Gadget API Framework]

==See also==
* [http://www.linux-usb.org/gadget/file_storage.html Backing Storage for the File-backed Storage Gadget]

[[Category:USB]]
[[Category:USB software]]

Using the Neo as an USB Mass storage device

2010-05-05T11:47:59Z

Guyou: Important info, needed in first page in USB category

Qt

2010-05-03T13:55:22Z

Guyou: QtMobility

* [[Qt Moko]] a Debian distribution based on ''Qt Extended Improved'' (active development)
* [[Qt Extended Improved]] a community fork of the discontinued Qt Extended
* [[Qtopia / Qt Extended on FreeRunner|Qt Extended on FreeRunner]]
* [[Qtopia on Neo1973]]
* [[QtCreator]] the Qt IDE
* [[Developing with C++ and Qt]]
* [[Qt_Extended_4.4.3]]
* [[Qt_Extended_4.4.2]]
* QtMobility: [http://labs.trolltech.com/page/Projects/QtMobility Project page], [http://labs.trolltech.com/blogs/category/qtmobility/ blog], [http://doc.qt.nokia.com/qtmobility-1.0-tp/index.html API doc], [http://qt.gitorious.org/qt-mobility/qt-mobility Git]

==See also==
* [[:Category:Qt based distributions]]

[[Category:Qt based distributions| ]]

User:Guyou

2010-04-25T13:33:56Z

Guyou: me, myself and I

Check my [http://nathguil.free.fr web page].

Interested in application development, mainly GPS related.

See my [http://nathguil.free.fr/mediawiki/index.php?title=Freerunner notes about Freerunner] and sort of [http://nathguil.free.fr/mediawiki/index.php?title=Notes todo list].

Openmoko Local Groups: Toulouse

2010-04-25T13:30:03Z

Guyou: me

Bienvenue a Toulouse !

{|border=1
!Name
!Skills
!Interest
!Location
|-
|[[User:Micktaiwan|Mickael Faivre-Macon]]
|C++/Ruby
|Application development
|Toulouse
|-
|[[User:Guyou|Guilhem Bonnefille]]
|C/C++/Gtk+
|Application development, GPS
|Toulouse
|}

[[Category:Openmoko Local Groups]]

Qi

2010-04-25T09:33:09Z

Guyou: /* Source code */ gitorious link

{{Languages|Qi}}
[[image:Screenshot-Qi.png|frame|Qi Boot messages]] Qi ( [[http://zh.wikipedia.org/wiki/气| '''氣''' ]] ) is a lightweight replacement for the [[Uboot|uBoot]] bootloader with everything that doesn't assist "loading" and "booting" Linux stripped out.

Its advantages comparing to the [[Uboot|u-boot Openmoko port]] are:
* actively developed (u-boot on GTA02 is deprecated)
* easier configuration, more robust and predictable
* SD and SDHC cards supported properly with partitions of any size
* kernel size is detected by checking the start of the kernel image, so large (>2M) kernels are supported without tweaking or loading more than needed
* Very fast, simple boot direct to Linux

==About Qi==
===Requirements===
There is a [[Neo1973|GTA01]] build of Qi, but using it without a debug board is not recommended because Qi itself does not support DFU, so updating or going back to U-Boot is a difficult process.

[[Freerunner|GTA02 Hardware]] has NOR U-Boot always available, so updating to Qi is safe to try it out.

{{Note|The below Qi are for Openmoko. E.g. for SHR - use Qi from the SHR directory if newer.}}

===Download===

*GTA01 -> [http://people.openmoko.org/andy/ qi-s3c2410]
*GTA02 -> [http://people.openmoko.org/andy/ qi-s3c2442]

====New Versions====

These are the versions we are getting ready for release

Download from either the Neo1973 or NeoFreerunner directory.

http://downloads.openmoko.org/distro/testing

====Unstable and Experimental Versions====

These are the latest versions from svn.

Download from either the Neo1973 or NeoFreerunner directory.

http://downloads.openmoko.org/distro/unstable

http://downloads.openmoko.org/distro/experimental

====Older Versions====

The download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
Use the file appropriate to your device:

===Installation===
* Connect Freerunner (e.g GTA02 Hardware) with USB-cable
* Download [[dfu-util]] via package manager (e.g. YAST with OpenSuse) to your computer (not the Neo).
* Download Qi image (e.g. for GTA02 which is [http://people.openmoko.org/andy/ 'qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu'])
* Switch off you freerunner (if necessary) and start NOR uBoot by pressing AUX and Power-On at the same time and then start [[dfu-util]] on your computer with the following parameters:
# dfu-util -a u-boot -R -D qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu
See [[Flashing the Neo FreeRunner]] for more details on flashing your phone.

===Features===
* booting from primary SD partitions (1st, 2nd or 3rd) in /boot directory
* booting from NAND (compatible with U-Boot's dynparts scheme)
* configuration per rootfs, by files in /boot in the rootfs
* automatically choose correct kernel for device hardware so rootfs can be used on multiple device types
* automatically tell kernel correct root= for rootfs kernel image came from, simplifying update
* ext2/3 are supported
* symlinks are supported
* parses identity partition and appends kernel commandline with device identity information
* zero "environment" or private persistent state - operation is completely deterministic
* You can always boot from [http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash NOR menu]

===Use Case===
If you want to install [[Android]] on you OpenMoko you can use Qi. The [[Android on Freerunner]] kernel image can be more than 2MB in size. The UBoot environment that comes with your FreeRunner is only able to boot a kernel of 2MB in size or less. Qi support kernel images greater than 2MB out of the box.

===Limitations===
* no DFU-Mode - USB is not initialized at all (but you can always boot [http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash from NOR])
* no boot menu (but you can always boot [http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash from NOR])
* FAT partitions are ignored

Both the lack of DFU and the boot menu are planned to be addressed by the backup / recovery rootfs.

FAT is not supported because it can't provide a rootfs, and Qi wants the kernel to come from the rootfs.

===Defaults===
If the kernel is found on uSD, Qi assumes the rootfs to be on the same partition as the kernel. In case of boot from NAND, it assumes that rootfs is also on NAND (just as u-boot does). See [[#/boot-Partition|below]] for help with an extra /boot-partition. The default rootdelay is 1 second.

===Files===
; /boot/uImage-GTA0[123].bin
: Kernel images, Qi will look for (can be in either uImage (u-boot image) or zImage format, file name should still be uImage-GTA0[123].bin)
; /boot/append-GTA0[123]
: Additional kernel arguments. All arguments should be on the first and the only line separated by spaces, for example: "<tt>loglevel=8 rootdelay=5 </tt>" . Make sure you have an extra space after the last argument (space is no longer needed if the version is from 31 Jan or older)!
; /boot/noboot-GTA0[123]
: make Qi skip this partition

===Speed up kernel resume for SHR===
Since SHR (and perhaps other distributions as well) ouput log messages during resume which slow down the resume process by ca. 3 seconds it make sense there to append the following settings to /boot/append-GTA0[123]:
: loglevel=1 quiet
The disadvantage of this speedup is that you won't see any lifesign of your phone until it starts the graphical user interface after adding these files, though.
===Boot Order===
[[image:Qi-drawings-bootsequence.png|frame|Qi GTA02 Booting order]]
# SD Partition 1
# SD Partition 2
# SD Partition 3
# NAND
# Memory Test

Qi will try to mount each SD partition as ext2 / 3, if that succeeds it will look for the kernel as /boot/uImage-GTA02.bin. If that is found, it'll be fetched, its CRC is checked and then it's booted into with a generated kernel commandline.

===Kernel Commandline Generation===
[[image:Qi-commandline-composition.png‎|frame|Qi commandline composition]] Because Qi has no private stored state, it infers and composes a suitable kernel commandline on each boot.

One of its tasks is to scan NAND memory using the U-Boot dynparts rules to determine the start offset of the NAND partitions on this device, from that it forms the mtdparts kernel parameter that sets Linux's view of NAND partitioning.

The other thing it does is mount the "identity" partition and get from there the globally unique MAC address for the USB over Ethernet function instead of the random one that is otherwise used (If this doesn't work (like with a GTA01) you may use kernel-commandline parameters g_ether.dev_addr= and g_ether.host_addr= for the mac in device and host mode of the usb-ether module).

===LED and Vibrator Signals===
* AUX LED is turned on either on:
** Successful partition mount
** Successful kernel pull
** Successful initramfs pull
* AUX LED is turned off and vibrator runs briefly either on:
** Fail of kernel pull
** Fail of initramfs pull
** Fail of mount partition
** Skipping of current boot possibility
* AUX LED is turned off either on:
** Start of the kernel
** Start of the mem test
** Start of the kernel pull
** Start of the initramfs pull
* One Blue shine every ~10 second: did not find any valid kernel to boot
* About four RED shines per second: kernel panic.

===Booting===
A short press on the power button is enough to make Qi start booting. In a few seconds the backlight will be lit, but the kernel will not spew any console messages unless something is wrong. It may take up to 2 minutes (depends on distribution) until X is started during which there will be no visual feedback. Please be patient.

You can force debug messages on the LCM console by holding in the power button before Linux starts.

===Choosing a Kernel===
If a user presses the AUX button after successful partition mount and before start of the kernel pull (that is, while the red LED is on), this boot possibility is skipped (and GTA02 owners can feel vibration). So press power, release power, press aux, wait for vibration, release aux.

On versions newer than Jan 18 if a user holds the POWER button just before start of the kernel,
debugging parameters are added to the kernel command line and a lot of information is output to the screen.

===Boot Menu===
Qi's concept is to leave everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. This should rather be implemented by a minimal Kernel, initramfs and menu system. It may be more comfortable for some users and may get them to switch from uboot to Qi.

Such system is already implemented for some Angstrom-supported devices and for Zaurus (see [http://projects.linuxtogo.org/projects/kexecboot/ kexecboot]).

Since 2010-10-08, a such project was initialized by Marc Andre Tanner. The project is called [http://www.brain-dump.org/projects/qi-bootmenu/ qi-bootmenu].

http://www.brain-dump.org/projects/qi-bootmenu/screenshot.png

===Source code===
Dedicated code for openmoko has its [http://git.openmoko.org/?p=qi.git;a=summary own Git repo].

git clone git://git.openmoko.org/git/qi.git

Qi is also [http://gitorious.org/0xlab-bootloader maintained on gitorious].

One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

===README===
The latest README file can be found in the git as well:http://git.openmoko.org/?p=qi.git;a=blob;f=README;hb=HEAD

==Tips, Tricks, Tweaks==
===General troubleshooting===
Qi does not bring up the LCD backlight. If the backlight is lit, it means you have succeeded to boot into Linux.

If nothing else is happening or there is a panic, enable debugging messages as described below.

===Enabling console messages===

You can just hold in the power button, this automatically appends verbose debugging to the kernel commandline (loglevel=8).

If you always want verbose "dmesg" type debugging messages, you can do it like this:

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
loglevel=8
and you'll see the messages on boot.

If it's NAND, according to [http://www.mail-archive.com/community@lists.openmoko.org/msg39256.html] you need to copy the uImage-GTA02.bin under /boot/ directory also under NAND and then create /boot/append-GTA02 there as well. The other way, as that guide does not seem to work per se (fix this wiki if it should work and works for you) is to edit the default commandline in Qi for gta02 and recompile Qi.

===/boot-Partition===
If you have a separate partition for /boot, so that your kernel and rootfs are not in fact on the same partition, you will need to append a root= entry on the kernel commandline to override the default action of trying to use the partition where the kernel came from as the rootfs.

Add this in /boot/append-GTA0[123]:
root=/dev/mmcblk0p2
for a rootfs on the second partition.

Note that a default Debian installation puts the kernel straight in the root of /dev/mmcblk0p1, not in a boot subdirectory, expecting u-boot to mount it as /boot. In order for Qi to recognise this, create a boot subdirectory with a symlink to the kernel.

===SD Initialisation===
If you don't specify loglevel=8 in append-GTAXX, and booting fails with a "VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)", the SD card needs a little bit more time to initialise.

Put a "rootdelay=5" in append-GTAXX like so:
rootdelay=5

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

PLEASE, perform comparable tests !!!!!!!!!!!!

Booting SHR image with uBoot:
* 0:00 power button held down
:: On mine, it apears at 0:05 ... (custom splash)
* 0:07 splash screen appears
:: Here, changing the bootdelay (uboot environnement variable) can improve the delay here
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
:: This can be improved a lot by using the quiet option on the kernel command line !!!!!!!!!
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting
Why 1'20 min from OM splash to end of boot here
and only 1'00 for the Qi version ???
Qi has no relation to this !!!!!!!!!

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the first stages up until init (kernel finished establishing itself) to be faster.

[[Category:Bootloaders]]

Qi

2010-04-25T08:28:08Z

Guyou: /* Boot Menu */

{{Languages|Qi}}
[[image:Screenshot-Qi.png|frame|Qi Boot messages]] Qi ( [[http://zh.wikipedia.org/wiki/气| '''氣''' ]] ) is a lightweight replacement for the [[Uboot|uBoot]] bootloader with everything that doesn't assist "loading" and "booting" Linux stripped out.

Its advantages comparing to the [[Uboot|u-boot Openmoko port]] are:
* actively developed (u-boot on GTA02 is deprecated)
* easier configuration, more robust and predictable
* SD and SDHC cards supported properly with partitions of any size
* kernel size is detected by checking the start of the kernel image, so large (>2M) kernels are supported without tweaking or loading more than needed
* Very fast, simple boot direct to Linux

==About Qi==
===Requirements===
There is a [[Neo1973|GTA01]] build of Qi, but using it without a debug board is not recommended because Qi itself does not support DFU, so updating or going back to U-Boot is a difficult process.

[[Freerunner|GTA02 Hardware]] has NOR U-Boot always available, so updating to Qi is safe to try it out.

{{Note|The below Qi are for Openmoko. E.g. for SHR - use Qi from the SHR directory if newer.}}

===Download===

*GTA01 -> [http://people.openmoko.org/andy/ qi-s3c2410]
*GTA02 -> [http://people.openmoko.org/andy/ qi-s3c2442]

====New Versions====

These are the versions we are getting ready for release

Download from either the Neo1973 or NeoFreerunner directory.

http://downloads.openmoko.org/distro/testing

====Unstable and Experimental Versions====

These are the latest versions from svn.

Download from either the Neo1973 or NeoFreerunner directory.

http://downloads.openmoko.org/distro/unstable

http://downloads.openmoko.org/distro/experimental

====Older Versions====

The download is a ''qi-s3cXXXX-andy_somenumber.udfu'' file at http://people.openmoko.org/andy/ .
Use the file appropriate to your device:

===Installation===
* Connect Freerunner (e.g GTA02 Hardware) with USB-cable
* Download [[dfu-util]] via package manager (e.g. YAST with OpenSuse) to your computer (not the Neo).
* Download Qi image (e.g. for GTA02 which is [http://people.openmoko.org/andy/ 'qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu'])
* Switch off you freerunner (if necessary) and start NOR uBoot by pressing AUX and Power-On at the same time and then start [[dfu-util]] on your computer with the following parameters:
# dfu-util -a u-boot -R -D qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu
See [[Flashing the Neo FreeRunner]] for more details on flashing your phone.

===Features===
* booting from primary SD partitions (1st, 2nd or 3rd) in /boot directory
* booting from NAND (compatible with U-Boot's dynparts scheme)
* configuration per rootfs, by files in /boot in the rootfs
* automatically choose correct kernel for device hardware so rootfs can be used on multiple device types
* automatically tell kernel correct root= for rootfs kernel image came from, simplifying update
* ext2/3 are supported
* symlinks are supported
* parses identity partition and appends kernel commandline with device identity information
* zero "environment" or private persistent state - operation is completely deterministic
* You can always boot from [http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash NOR menu]

===Use Case===
If you want to install [[Android]] on you OpenMoko you can use Qi. The [[Android on Freerunner]] kernel image can be more than 2MB in size. The UBoot environment that comes with your FreeRunner is only able to boot a kernel of 2MB in size or less. Qi support kernel images greater than 2MB out of the box.

===Limitations===
* no DFU-Mode - USB is not initialized at all (but you can always boot [http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash from NOR])
* no boot menu (but you can always boot [http://wiki.openmoko.org/wiki/Boot#Log_into_U-Boot_in_the_NOR_Flash from NOR])
* FAT partitions are ignored

Both the lack of DFU and the boot menu are planned to be addressed by the backup / recovery rootfs.

FAT is not supported because it can't provide a rootfs, and Qi wants the kernel to come from the rootfs.

===Defaults===
If the kernel is found on uSD, Qi assumes the rootfs to be on the same partition as the kernel. In case of boot from NAND, it assumes that rootfs is also on NAND (just as u-boot does). See [[#/boot-Partition|below]] for help with an extra /boot-partition. The default rootdelay is 1 second.

===Files===
; /boot/uImage-GTA0[123].bin
: Kernel images, Qi will look for (can be in either uImage (u-boot image) or zImage format, file name should still be uImage-GTA0[123].bin)
; /boot/append-GTA0[123]
: Additional kernel arguments. All arguments should be on the first and the only line separated by spaces, for example: "<tt>loglevel=8 rootdelay=5 </tt>" . Make sure you have an extra space after the last argument (space is no longer needed if the version is from 31 Jan or older)!
; /boot/noboot-GTA0[123]
: make Qi skip this partition

===Speed up kernel resume for SHR===
Since SHR (and perhaps other distributions as well) ouput log messages during resume which slow down the resume process by ca. 3 seconds it make sense there to append the following settings to /boot/append-GTA0[123]:
: loglevel=1 quiet
The disadvantage of this speedup is that you won't see any lifesign of your phone until it starts the graphical user interface after adding these files, though.
===Boot Order===
[[image:Qi-drawings-bootsequence.png|frame|Qi GTA02 Booting order]]
# SD Partition 1
# SD Partition 2
# SD Partition 3
# NAND
# Memory Test

Qi will try to mount each SD partition as ext2 / 3, if that succeeds it will look for the kernel as /boot/uImage-GTA02.bin. If that is found, it'll be fetched, its CRC is checked and then it's booted into with a generated kernel commandline.

===Kernel Commandline Generation===
[[image:Qi-commandline-composition.png‎|frame|Qi commandline composition]] Because Qi has no private stored state, it infers and composes a suitable kernel commandline on each boot.

One of its tasks is to scan NAND memory using the U-Boot dynparts rules to determine the start offset of the NAND partitions on this device, from that it forms the mtdparts kernel parameter that sets Linux's view of NAND partitioning.

The other thing it does is mount the "identity" partition and get from there the globally unique MAC address for the USB over Ethernet function instead of the random one that is otherwise used (If this doesn't work (like with a GTA01) you may use kernel-commandline parameters g_ether.dev_addr= and g_ether.host_addr= for the mac in device and host mode of the usb-ether module).

===LED and Vibrator Signals===
* AUX LED is turned on either on:
** Successful partition mount
** Successful kernel pull
** Successful initramfs pull
* AUX LED is turned off and vibrator runs briefly either on:
** Fail of kernel pull
** Fail of initramfs pull
** Fail of mount partition
** Skipping of current boot possibility
* AUX LED is turned off either on:
** Start of the kernel
** Start of the mem test
** Start of the kernel pull
** Start of the initramfs pull
* One Blue shine every ~10 second: did not find any valid kernel to boot
* About four RED shines per second: kernel panic.

===Booting===
A short press on the power button is enough to make Qi start booting. In a few seconds the backlight will be lit, but the kernel will not spew any console messages unless something is wrong. It may take up to 2 minutes (depends on distribution) until X is started during which there will be no visual feedback. Please be patient.

You can force debug messages on the LCM console by holding in the power button before Linux starts.

===Choosing a Kernel===
If a user presses the AUX button after successful partition mount and before start of the kernel pull (that is, while the red LED is on), this boot possibility is skipped (and GTA02 owners can feel vibration). So press power, release power, press aux, wait for vibration, release aux.

On versions newer than Jan 18 if a user holds the POWER button just before start of the kernel,
debugging parameters are added to the kernel command line and a lot of information is output to the screen.

===Boot Menu===
Qi's concept is to leave everything possible to Linux, that includes even the video init. Therefore Qi does NOT provide a boot menu. This should rather be implemented by a minimal Kernel, initramfs and menu system. It may be more comfortable for some users and may get them to switch from uboot to Qi.

Such system is already implemented for some Angstrom-supported devices and for Zaurus (see [http://projects.linuxtogo.org/projects/kexecboot/ kexecboot]).

Since 2010-10-08, a such project was initialized by Marc Andre Tanner. The project is called [http://www.brain-dump.org/projects/qi-bootmenu/ qi-bootmenu].

http://www.brain-dump.org/projects/qi-bootmenu/screenshot.png

===Source code===
git://git.openmoko.org/git/qi.git , http://git.openmoko.org/?p=qi.git;a=summary .
One can also just use strings(1) on the .udfu file to get an idea of where Qi currently looks for files.

===README===
The latest README file can be found in the git as well:http://git.openmoko.org/?p=qi.git;a=blob;f=README;hb=HEAD

==Tips, Tricks, Tweaks==
===General troubleshooting===
Qi does not bring up the LCD backlight. If the backlight is lit, it means you have succeeded to boot into Linux.

If nothing else is happening or there is a panic, enable debugging messages as described below.

===Enabling console messages===

You can just hold in the power button, this automatically appends verbose debugging to the kernel commandline (loglevel=8).

If you always want verbose "dmesg" type debugging messages, you can do it like this:

[http://lists.openmoko.org/pipermail/openmoko-kernel/2008-November/006812.html]
If it's SD Card boot, just create a text file, e.g., for a [[GTA02]] use
/boot/append-GTA02
on the rootfs in question, put in there
loglevel=8
and you'll see the messages on boot.

If it's NAND, according to [http://www.mail-archive.com/community@lists.openmoko.org/msg39256.html] you need to copy the uImage-GTA02.bin under /boot/ directory also under NAND and then create /boot/append-GTA02 there as well. The other way, as that guide does not seem to work per se (fix this wiki if it should work and works for you) is to edit the default commandline in Qi for gta02 and recompile Qi.

===/boot-Partition===
If you have a separate partition for /boot, so that your kernel and rootfs are not in fact on the same partition, you will need to append a root= entry on the kernel commandline to override the default action of trying to use the partition where the kernel came from as the rootfs.

Add this in /boot/append-GTA0[123]:
root=/dev/mmcblk0p2
for a rootfs on the second partition.

Note that a default Debian installation puts the kernel straight in the root of /dev/mmcblk0p1, not in a boot subdirectory, expecting u-boot to mount it as /boot. In order for Qi to recognise this, create a boot subdirectory with a symlink to the kernel.

===SD Initialisation===
If you don't specify loglevel=8 in append-GTAXX, and booting fails with a "VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)", the SD card needs a little bit more time to initialise.

Put a "rootdelay=5" in append-GTAXX like so:
rootdelay=5

== Testing speed improvements ==

Stopwatch results on Qi (error is approx ±1/2 second):

PLEASE, perform comparable tests !!!!!!!!!!!!

Booting SHR image with uBoot:
* 0:00 power button held down
:: On mine, it apears at 0:05 ... (custom splash)
* 0:07 splash screen appears
:: Here, changing the bootdelay (uboot environnement variable) can improve the delay here
* 0:15 drops to console showing kernel messages scrolling by for ~1 minute
:: This can be improved a lot by using the quiet option on the kernel command line !!!!!!!!!
* 1:18 Openmoko 'please wait' splash
* 1:31 desktop animated splash
* 2:38 finished booting
Why 1'20 min from OM splash to end of boot here
and only 1'00 for the Qi version ???
Qi has no relation to this !!!!!!!!!

Booting identical setup with Qi flashed over uBoot:
* 0:00 power button held down
* 0:06 backlit black
* 0:13 please wait booting... (only this text on console for next 38 seconds)
* 0:51 Angstrom console message (at the end of kernel output with uBoot, but ONLY text display to appear throughout this stage with Qi)
* 0:54 Openmoko 'please wait' splash
* 1:05 desktop animated splash
* 1:54 finished booting

So for this particular configuration, it reduced time-to-desktop by about 28%, about 44 seconds. Surprisingly, the later segments of booting (desktop) were also noticeably faster than with uBoot - One would have expected just the first stages up until init (kernel finished establishing itself) to be faster.

[[Category:Bootloaders]]

Boot

2010-04-24T20:50:35Z

Guyou: New page: Cf. http://wiki.openmoko.org/wiki/Bootloader

Cf. http://wiki.openmoko.org/wiki/Bootloader

Hackable:1

2010-04-20T15:57:35Z

Guyou: Internal links in intro

{{Languages|Hackable:1}}

{{Distributions|Hackable:1}}

'''hackable:1''' intends to implement the Gnome Mobile platform and uses Debian stable as a base. It therefore aims at creating a Debian Mobile distribution. The [[OM2007.2]] software stack has been kept, improved, and packaged for Debian.

The latest stable version is the rev5, released the 22th December 2009, codenamed Chuck. It is using the openmoko applications and [[gsmd]]. The next version will use [[FSO]].

The user and developer wiki is at http://trac.hackable1.org and the user manual (wip) at http://trac.hackable1.org/trac/wiki/UserManual

==Feature overview==
In the overview below are all the essential features and their status for the current '''out of the box''' hackable:1 rev5 distribution. Green indicates that this part is functioning well, red indicates a known requirement which will be implemented later on and orange indicates functionality that may not work out of the box.

{| cellspacing="0" class="sortable wikitable" border="1" style="font-size: 85%; text-align: left; width: auto;"
|-
! Category
! Name
! Functionality
! Comments
|-
| System
| Power Management
| style="background:#FFCC44;"| Suspend
| style="background:#FFCC44;"| Some users don't get calls when in suspend
|-
| System
| Package manager
| style="background:#88FF88;"| Installing and upgrading packages
| Works well. All debian stable and h:1 packages can be installed via apt-get. For others, use dpkg -i
|-
| System
| Keyboard
| style="background:#88FF88;"| Offer a stylus keyboard
| With some practicing, one can use it with the fingernail
|-
| GSM
| Network
| style="background:#88FF88;"| Connect via SIM and PIN
|
|-
| GSM
| Network
| style="background:#88FF88;"| Flight mode
| You can turn the gsm and the wifi antennas off
|-
| GSM
| Dialer
| style="background:#88FF88;"| Receiving Call
|
|-
| GSM
| Dialer
| style="background:#88FF88;"| Making Call
|
|-
| GSM
| Dailer
| style="background:#FF8888;"| Speed dial voice mail
| style="background:#FF8888;"| Not available.
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Overview Log (In, Out, Answered, All)
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Display Missed Calls
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Making reply Call from Log
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Sending reply SMS from Log
|
|-
| Shared
| Phone Log
| style="background:#88FF88;"| Creating new SIM contact from Log
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Receiving SMS
|
|-
| GSM
| SMS
| style="background:#FF8888;"| SIM phonebook lookup for SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| View overview of received SMS
| received and sent sms are shown IM-style
|-
| GSM
| SMS
| style="background:#88FF88;"| View overview of sent SMS
| received and sent sms are shown IM-style
|-
| GSM
| SMS
| style="background:#FFCC44;"| Request SMS delivery receipt
| style="background:#FFCC44;"|
|-
| GSM
| SMS
| style="background:#88FF88;"| Selecting SMS from Overview
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Viewing SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Writing SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending new SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending reply SMS
|
|-
| GSM
| SMS
| style="background:#FF8888;"| Making reply Call
| style="background:#FF8888;"| Should be easy to implement
|-
| GSM
| SMS
| style="background:#88FF88;"| Deleting SMS
|
|-
| GSM
| SMS
| style="background:#FF8888;"| Storing received contact in contacts
|
|-
| GSM
| GPRS
| style="background:#88FF88;"| Configuring and Enabling GPRS
| Applications -> Connect to gprs
|-
| Shared
| Contacts
| style="background:#88FF88;"| Reading SIM contacts
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Selecting SIM contact from Overview
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Creating new SIM contact
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Editing SIM contact
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Deleting SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Quick lookup contact with keyboard
| Click on the magnifier and type a part of the name.
|-
| Shared
| Contacts
| style="background:#88FF88;"| Calling contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Sending SMS to contact
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Sending contact via SMS to contact
|
|-
| WiFi
| Ethernet
| style="background:#FFCC44;"| Configuring and Enabling WiFi connection
| style="background:#FFCC44;"| Utilities -> Wireless Configuration
|-
| GPS
| Service
| style="background:#88FF88;"| Receiving GPS data
|
|-
| USB
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling USB connection
| root password: "root"
|-
| Audio
| Headset
| style="background:#FFCC44;"| Handsfree calling
| style="background:#FFCC44;"| not tested
|-
|}

==Image content==

These applications are included in the full and lite SHR images:
{|class="wikitable" border="1" cellpadding="0" cellspacing="0" width=100%

! width=16%| !! width=42%|Developer image content !! width=42%|User image content
|-
| Window Manager ||
* matchbox
||
* matchbox
|-
| Engine ||
* gsmd/libgsmd
||
* gsmd/libgsmd
|-
| Telephony ||
* openmoko-dialer (Call/Receive, DTMF, Speaker mode)
* openmoko-contacts (Call/Modify/Create/...)
* openmoko-messages (Receive/Compose/Answer/...)
* openmoko-today (received/emitted/missed calls logging)
||
* openmoko-dialer (Call/Receive, DTMF, Speaker mode)
* openmoko-contacts (Call/Modify/Create/...)
* openmoko-messages (Receive/Compose/Answer/...)
* openmoko-today (received/emitted/missed calls logging)
|-
| GPS ||
* TangoGPS
||
* TangoGPS
|-
| Utilities ||
* File browser
* Text editor
* openmoko-dates
* xterm
* date and time application
||
* File browser
* Text editor
* openmoko-dates
* xterm
* date and time application
|-
| Media ||

||

|-

| Internet ||
* Pidgin (Instant Messenger)
* Woosh! (Browser)
* FeedReader (rss feed reader)
||
* Pidgin (Instant Messenger)
* Woosh! (Browser)
* FeedReader (rss feed reader)
|-
| Games ||
* sgt-puzzles game pack
||
* sgt-puzzles game pack
|-
| Settings ||
* H1settings
* wifig (wifi manager)
||
* H1settings
* wifig (wifi manager)
|-
|}

==User Manual==
The [http://trac.hackable1.org/trac/wiki/UserManual User Manual] is a Work In Progress but awaits your fillings

== More Information ==

Visit:

* [http://download.hackable1.org/rev5 Latest release]

* [http://blog.hackable1.org Blog]
* [http://trac.hackable1.org Project Homepage/Trac/BugTracker/SourceBrowser]
* [http://download.hackable1.org Download page (stable releases)]
* [http://build.hackable1.org Buildhost (daily builds)]
* [http://lists.hackable1.org/mailman/listinfo Mailing lists (user and developer)]

[[Category:Hackable]]

Hackable:1/fr

2010-04-20T15:37:57Z

Guyou: Upstream projects links

{{Languages|Hackable:1}}

[http://www.hackable1.org/ Hackable1] est une [[Distributions|distribution]] communautaire pour "appareil modifiable" à l'image du Neo Freerunner. Elle est basée sur [http://debian.org Debian] et implémente la plateforme [http://www.gnome.org/mobile/ GNOME mobile].

'''État:''' ''En développement''

= Installation =

[http://build.hackable1.org/ Téléchargez] l'archive ou les images et installez de façon usuelle.
Le processus détaillé d'installation sur carte SD est disponible [http://www.hackable1.org/wiki/Documentation sur le site internet]

= Utilisation =

== Boutons ==

* une pression courte sur le bouton AUX affiche le clavier virtuel;
* une pression courte sur le bouton principal (bouton de mise en marche) ferme l'application au premier plan;
* en activant ces boutons pendant au moins une demi-seconde, on fait apparaitre des menus complémentaires;
* le menu auxiliaire (bouton AUX) permet de rechercher un clavier Bluetooth ou encore de basculer entre les différents modes USB.

== SSH ==

Le mot de passe d'administration est par défaut : "root".

Dans le version bêta, le fichier /root/.ssh/authorized_keys mentionne une entrée pour m@one. Ça n'est pas une faille, il faut la remplacer par votre propre clé publique SSH, ou supprimer ce fichier.

== Connexion aux réseaux ==

La configuration par défaut contient une adresse réseau (FR 192.168.0.202, Gateway 192.168.0.200). Vous pouvez la [[Usb_networking#Configure_Default_Neo_DNS|modifier]].

= Problèmes et bugs =

* La puce GSM ne peut être désactivée si la carte SIM n'est pas présente. Le téléphone continue alors à essayer de s'authentifier;
* Lorsque vous rentrez une code PIN correct et qu'un message vous redemande de taper votre code PIN ou vous informe d'une erreur sur ce code, annulez la saisie à l'aide du bouton Cancel et cliquez sur l'icône GSM (en forme d'antenne, située en haut à droite de l'écran) pour activer la puce GSM (Power-Up GSM Antenna);
* Ne pas mettre à jour (apt-get upgrade) le téléphone, ceci corromprait la configuration spécifique au FreeRunner (pas d'image de boot installée, le gps et la puce gsm ne fonctionnerait plus, ...)

[[Category:Hackable]]

Qt Extended Improved

2010-04-20T15:19:13Z

Guyou:

<h2>Community Resources</h2>

Qt Software cancelled the Qt Extended project on 3 March 2009 ([http://www.qtsoftware.com/about/news/qt-software-discontinues-qt-extended Qt Software discontinues Qt Extended]). The community created a fork of it and called it Qt Extended Improved:

* [http://bugs.qtmoko.org/ bug tracking system]
* [http://dashi-x02.karadog.net/~lihouyu/qtextended/4.4.3/ prebuilt rootfs images for 4.4.3 and kernel]
* [http://dashi-x02.karadog.net/~lihouyu/qtextended/snapbuild/ prebuilt tarballs of qt extended improved] (use kernel made for 4.4.3)
* [http://git.karadog.net/qt-extended-improved.git git repository]

<h2>Installing Qt Extended Improved on the FreeRunner</h2>

<h3>Install Qt Extended 4.4.3</h3>

There are no rootfs images for Qt Extended Improved, so first we need to install Qt Extended 4.4.3, then we can upgrade to Qt Extended Improved. Follow the instructions at [[Qt Extended 4.4.3]].

<h3>Install Qt Extended Improved</h3>

Boot your FreeRunner into Qt Extended 4.4.3. Create a [[USB Networking|USB network]] connection between your workstation and the FreeRunner. Download the most recent [http://dashi-x02.karadog.net/~lihouyu/qtextended/snapbuild/ pre-built tarball]. Now you must unpack the tarball to a temporary directory and copy its contents to the FreeRunner's <tt>/opt/Trolltech/Qtopia</tt> directory:

mkdir temp
cd temp
tar -xzvf ../qt-extended-improved-bin-only-20090316.tar.gz
scp -r * 192.168.0.202:/opt/Trolltech/Qtopia/
this can be resumed in a simpler and quicker operation:
( dd if=../qt-extended-improved-bin-only-20090316.tar.gz ) | ( ssh 192.168.0.202 "cd /opt/Trolltech/Qtopia/ && tar xzv" )

Reboot your FreeRunner and you should be running Qt Extended Improved.

<h2>Building Qt Extended Improved</h2>

First download a source tar ball from the [http://git.karadog.net/qt-extended-improved.git git repository]. Then make the build directory and set the environment variables. In this example, I write the environment variables to a file then I source the file.

mkdir -p /opt/QtExtended/build
cd /opt/QtExtended
tar -xzvf qt-extended-improved.tar.gz
echo "export QTOPIA_DEPOT_PATH=/opt/QtExtended/qt-extended-improved" >> setpaths
echo "export QPEDIR=/opt/QtExtended/build/" >> setpaths
. setpaths

Install the toolchain:

cd /opt
wget http://qtextended.org/downloads/toolchains/arm920t-eabi.tgz
tar xzvf arm920t-eabi.tgz /

Do the linux three-step: configure, make, make install. Plus we build the sdk so we can make our own apps later, if we want.

cd $QPEDIR
$QTOPIA_DEPOT_PATH/configure -device neo -D _FORTIFY_SOURCE=0
make
make install
bin/qbuild sdk

The binaries are in the $QPEDIR/image directory. You can copy these to your freerunner over usb like this:

scp -r $QPEDIR/image/* 192.168.0.202:/opt/Trolltech/Qtopia/

<h2>Compiling an Example Qt Extended App</h2>

First set those indispensable Qt environment variables:

. /opt/QtExtended/setpaths

Next create a directory <tt>/opt/Qtopia/build/myapps</tt>. Copy the example app. Rename the example app to something that makes sense (how about "example"!). Create the <tt>Makefile</tt> and build the example.

desktop# mkdir /opt/QtExtended/build/myapps
desktop# cd /opt/QtExtended/build/myapps
desktop# cp -R $QTOPIA_DEPOT_PATH/examples/application .
desktop# mv application example
desktop# cd example
desktop# $QPEDIR/bin/qbuild

Now you have an executable <tt>example</tt>. It won't execute on your workstation - you must secure copy it to your FreeRunner. Then secure shell into the FreeRunner, import the Qtopia environment variables and execute the app:

desktop# scp example root@freerunner:/home/root
root@192.168.0.202's password:
example 100% 33KB 33.4KB/s 00:00
desktop# ssh 192.168.0.202
root@freerunner's password:
freerunner:~# . /opt/Trolltech/Qtopia/qpe.env
freerunner:~# ./example

This is what you should see on the screen (click on image to zoom) : [[Image:Qt_extended_sdk_example_screenshot.png|100px]]

<h2>Packaging</h2>

Create a .qpk file, an installable package:

desktop# $QPEDIR/bin/qbuild packages

Create a packages.list file for the software installer and put it in the http server root:

desktop# sudo $QTOPIA_DEPOT_PATH/bin/mkPackages /srv/www/htdocs/

Copy your new package to the http server root:

desktop# sudo cp pkg/*.qpk /srv/www/htdocs/

On your phone, find Settings > Software Packages; press the Downloads tab; go to Options > Edit Servers; Options > New; then enter a name and URL of http://192.168.0.200:80, or the URL for your web server. The software package manager should then be able to see $HTTPROOT/packages.list and install any packages you have.

<h2>mp3 Support</h2>

If you compile your own version of Qt Extended Improved, you can add mp3 support using [http://radagast.bglug.ca/openmoko/qt-extended-4.4.3-libmad.tar.gz this patch]. Untar the file from your qt-extended-improved directory (it installs some files in the src tree) and patch using the patch file, eg:

desktop# cd $QTOPIA_DEPOT_PATH
desktop# tar -xzvf qt-extended-4.4.3-libmad.tar.gz
desktop# patch -p1 < qt-extended-4.4.3-libmad.patch

Now configure, build, etc.

<h2>Troubleshooting</h2>

If you encounter this error while compiling your example,

<code>
In file included from /opt/QtExtended/build/sdk/qtopiacore/target/include/QtCore/qglobal.h:58,
from /opt/QtExtended/build/sdk/qtopiacore/target/include/QtCore/qatomic.h:41,
from /opt/QtExtended/build/sdk/qtopiacore/target/include/QtCore/qvariant.h:41,
from /opt/QtExtended/build/sdk/qtopiacore/target/include/QtCore/QVariant:1,
from /opt/QtExtended/build/myapps/example/.uic/ui_examplebase.h:13:
/opt/QtExtended/build/sdk/qtopiacore/target/include/QtCore/qconfig.h:2:66: error: /opt/QtExtended/build/sdk/sdk/qtopiacore/qconfig-qpe.h: No such file or directory</code>

edit /opt/QtExtended/build/sdk/qtopiacore/target/include/QtCore/qconfig.h and remove one /sdk/ from /opt/QtExtended/build/sdk/sdk/qtopiacore/qconfig-qpe.h at the top of the file.

A better solution which will work for building packages too is to symbolic link the second sdk to the first...

cd $QPEDIR/sdk
ln -s ../sdk sdk

<h2>Branches and Forks</h2>
There are various other branches and forks of qte/qtei that fix bugs or other things. List taken from http://lists.openmoko.org/pipermail/community/2009-April/046492.html

<h3>Major Distro Efforts</h3>
There are 3 major "distributions" for QtEI: karadogs, Radeks and Franky:

* Karadog runs on 2.6.24 and is behind patches
* Radek (based on karadog) is running on 2.6.28 and behind on
patches
* Franky is running based on Radek (patches included), but no binary
distro, just an install script.

<h3>Initial import of QTE 4.4.3 opensource release</h3>
[http://github.com/FilipBE/qtextended/tree/master Source]

<h3>QTMoko</h3>
QtEI on Debian by Radek.

[http://activationrecord.net/radekp/openmoko/qtmoko/ Homepage]

[http://github.com/radekp/qtmoko/tree/master/ Source]

[http://sourceforge.net/projects/qtmoko/files Rootfs/kernel]

<h3>Karadog</h3>
Trac, Releases, sources and semi-official Roadmap by HouYu Li

[http://trac.karadog.net/qt-extended-improved KaraDog Main Trac Site].

[http://dashi-x02.karadog.net/~lihouyu/qtextended/4.4.3/ Binary releases].

'''2010-04-20''': web site broken.

<h3>Latest and Greatest</h3>
Franky Van Liedekerke's branch.

[http://github.com/liedekef/qtmoko/commits/master Source].

[http://www.e-dynamics.be/openmoko/qt-issues.txt List of Issues].

[http://www.e-dynamics.be/openmoko/qt-issues-fixed.txt Issues Fixed].

[http://www.e-dynamics.be/openmoko/qtmoko_install.sh Install script and instructions]. Execute the script on the Neo.

<h3>Lpotter's Branch</h3>
[http://github.com/lpotter/qtmoko/tree/master Source]

[[Category:Qt based distributions]]