http://openmoko.org/api.php?action=feedcontributions&user=Dareus&feedformat=atomOpenmoko - User contributions [en]2024-03-28T22:55:21ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/Main_PageMain Page2012-01-07T09:38:26Z<p>Dareus: UNDO SPAM</p>
<hr />
<div>{{Languages|Main Page}}__NOTOC__<br />
__NOEDITSECTION__[[Image:Neo front 3.gif|right]]<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
'''Openmoko™''' is a project dedicated to delivering mobile phones with an open source software stack. Openmoko was earlier more directly associated with Openmoko Inc, but is nowadays a gathering of people with the shared goal of "Free The Phone". Distributors are currently selling updated versions of the Openmoko Inc's phone released in 2008, [[Neo FreeRunner]], to advanced users, while the software stack for FreeRunner and future free phones is being developed by the community. A modern 3G / OMAP3 upgrade to FreeRunner, [http://projects.goldelico.com/p/gta04-main/ GTA04], is currently in pre-order phase until February 2012, see below.<br />
<br />
* [[Introduction]]<br />
* [[Why Openmoko|Why Openmoko?]]<br />
<br />
[[More Information]]<br />
<br />
===Get Involved===<br />
Openmoko is a project driven by a community of passionate and intelligent volunteers. If you have the ability, please contribute to our cause. Openmoko's ambitions far exceed the resources available. <br />
<br />
* [[Community Resources]]<br />
* [[Gta02-core|Create a new hardware revision of the gta02 hardware]] with completely free software tools for the hardware creation<br />
* [[GTA04|Follow the ”GTA04” project by Golden Delicious Computers]]<br />
* [[Create User Manuals]] for [[Distributions]] and [[Applications]]<br />
* Enhance the multi-device multi-vendor [[FSO]] middleware.<br />
<br />
===How To Purchase===<br />
The Neo FreeRunner is sold by various [[distributors]] around the world.<br />
<br />
If you have FreeRunner already, [http://www.handheld-linux.com/wiki.php?page=GTA04 GTA04 pre-order page is open!] - ''only'' if enough people will pre-order, mass-market GTA04 will become reality. Please spread the world to your FreeRunner owning friends.<br />
<br />
See [[Getting Openmoko]] for more information.<br />
<br />
----<br />
<br />
====Latest News====<br />
<br />
{{News}}<br />
[[News Archive|more news...]]<br />
<br />
----<br />
Problems with this Site or a List? http://admin-trac.openmoko.org/trac<br />
----<br />
<br />
[[Category:Community| ]]<br />
[[Category:Categories| ]]</div>Dareushttp://openmoko.org/wiki/More_InformationMore Information2011-04-20T12:42:31Z<p>Dareus: Undo revision 83882 by Creditrepairfixcredit (Talk) SPAM</p>
<hr />
<div>{{Languages|More informations}}<br />
__NOTOC__<br />
__NOEDITSECTION__[[Image:Neo front 3.gif|right]]<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
<br />
Openmoko™ is a project dedicated to delivering mobile phones with an [[Source Code|open source software stack]]. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.<br />
<br />
The Openmoko stack, which includes a full X server, allows users and developers to transform mobile hardware platforms into unique products. Our license gives developers and users freedom to cosmetically customize their device or radically remix it; change the wallpaper or rebuild the entire house! It grants them the freedom, for example, to transform a phone into a medical device or point of sale device or the freedom to simply install their own favorite software. Beyond freeing the software on our devices we have also released our [http://downloads.openmoko.org/CAD/ CAD] files. And at LinuxWorld 2008, we announced the release of the [http://downloads.openmoko.org/schematics/ schematics for our products]. <br />
<br />
<div style="clear:both">&nbsp;</div><br />
<br />
<table class="wikitable" cellspacing="4" cellpadding="6" width="100%" style="color:white"><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">News and events</td><br />
<td width="50%">New to Openmoko?</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
<!-- News are included from the Template:News --><br />
{{News}}<br />
<br />
* [[News Archive|(news archive)]]<!--Editors: copy removed news to News Archive! --><br />
</td><br />
<td><br />
<br />
===<font color=white>About Openmoko</font>===<br />
* [[Introduction]]<br />
* [[Why Openmoko]]<br />
* [[Neo FreeRunner|Neo FreeRunner phone]]<br />
* [[Supported Hardware]]<br />
* [[FAQ]]<br />
<br />
===<font color=white>Getting Openmoko</font>===<br />
* [[Getting Openmoko]]<br />
* [http://www.openmoko.com Openmoko Inc.]<br />
</td><br />
</tr><br />
<tr style="background:#ff6600; text-align:center; font-weight:bold"><br />
<td width="50%">for Users</td><br />
<td width="50%">for Developers</td><br />
</tr><br />
<tr valign="top" style="background:#333333"><br />
<td><br />
===<font color=white>Getting started</font>===<br />
* [[Getting Started with your Neo FreeRunner | Neo FreeRunner getting started guide]]<br />
* [[Applications|Applications list (wiki)]] and [http://opkg.org directory (opkg.org)]<br />
<br />
===<font color=white>Distributions</font>===<br />
* [[Distributions|Features comparison table]]<br />
* [[Om 2008.8|Om 2008.8 (ASU)]] - [[Om 2007.2|Om 2007.2 (old stable)]]<br />
* [[OpenmokoFramework|FSO]] - [[FDOM - a Fat and Dirty OM based distribution|FDOM]] - [[Qtopia / Qt Extended on FreeRunner|Qt Extended]] - [[Debian]] - [[Gentoo]] - [[Android]] - [[Stable Hybrid Release]] - [[Hackable:1]]<br />
<br />
===<font color=white>Openmoko community</font>===<br />
* [[Discussion_Forums| Discussion Forums]]<br />
* [[Jokes]]<br />
* [[Community Repository]]<br />
* [[Development resources | Development resources]]<br />
* [[Openmoko E-courseware | E-courseware]]<br />
* [[University Program#Student Projects | Student Projects]]<br />
<br />
===<font color=white>Help</font>===<br />
* [[Trouble shooting]]<br />
</td><br />
<td><br />
===<font color=white>Applications development</font>===<br />
* [[Openmoko developer guide]]<br />
* [[Toolchain|The toolchain]]<br />
<!-- * <font color=white>VMware</font> --><br />
* [[Python|Introduction to Python]]<br />
* [http://projects.openmoko.org/ Projects hosted in our GForge]<br />
* [[OpenmokoFramework|Openmoko dbus-based service level framework]]<br />
<br />
===<font color=white>Integration and distributions</font>===<br />
* [[OpenEmbedded|The OpenEmbedded distribution building framework]]<br />
* [[MokoMakefile|Building Openmoko using the MokoMakefile ]]<br />
* [[Opkg|The Opkg package manager]]<br />
<br />
===<font color=white>Emulation</font>===<br />
* [[Openmoko under QEMU]]<br />
</td><br />
</tr><br />
</table><br />
<br />
Browse articles by [[:Category:Categories|Categories]].<br />
<br />
[[Category:Community]]</div>Dareushttp://openmoko.org/wiki/QtMokoQtMoko2010-09-20T12:14:26Z<p>Dareus: /* Installation in NAND Memory with u-Boot */</p>
<hr />
<div>{{Languages}}<br />
QtMoko is a [[Debian]] based distribution for the [[Neo FreeRunner]]. The phone and user interface are based on [[Qt Extended Improved]] formerly known as [[Qtopia / Qt Extended on FreeRunner|Qtopia]]. The QtMoko wiki can be found [http://qtmoko.org/ here].<br />
<br />
===Download===<br />
Download the following files from [https://sourceforge.net/projects/qtmoko/files/ radekp download] to you desktop computer:<br />
* latest<br />
** https://sourceforge.net/projects/qtmoko/files/<br />
<br />
===Installation===<br />
If you flash the FreeRunner with a kernel image from QtMoko, then you must install the kernel and the root file system with [http://wiki.openmoko.org/wiki/Dfu-util#Binaries_dfu-util dfu-util]. <br />
{{Note|You need a fully charged Freerunner for installation.}}<br />
<br />
<br />
==== Installation on SD card with Qi ====<br />
Installing QtMoko on your microSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.<br />
<br />
If you have [[Qi]] installed then you can install QtMoko on the SD card. This seems to be useful if you want to work with different distribution and you can change the distribution just by changing the Mirco SD card in your FreeRunner. <br />
{{Note|Installation in NAND-Memory with Qi is possible without errors, but with an installed bootloader [[Qi]] the boot process will terminate (with Qi installed by Android, which is modified). Install u-Boot instead!}}<br />
<br />
If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the root filesystem image file [http://sourceforge.net/projects/qtmoko/files/ qtmoko-debian-v26.tar.gz]. In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .<br />
<br />
==== Installation in NAND Memory with u-Boot ====<br />
If you have [[Qi]] installed then install u-boot again as a [[bootloader]] by downloading a u-boot-binary on http://downloads.openmoko.org/distro/unstable/daily/ otherwise the boot process will terminate and you have to install u-Boot.<br />
<br />
All versions of the GTA02 (Neo FreeRunner) that have been sold to the public are version 5 hardware, so look for a file with "gta02" and "v5" in the name, for example:<br />
[http://downloads.openmoko.org/distro/unstable/daily/om-gta02/20100131/u-boot-gta02v5-1.3.1+gitr650149a53dbdd48bf6dfef90930c8ab182adb512-r1.bin u-boot-gta02v5-1.3.1.bin] (linked U-Boot-Version from 31.Jan 2010):<br />
<br />
sudo dfu-util -a u-boot -R -D u-boot-gta02v5-1.3.1.bin<br />
<br />
==== Installation of Kernel and Root-FS NAND-Memory ====<br />
Switch off your FreeRunner and press the AUX and Power-On button at the same time. Your FreeRunner is showing the following U-Boot Menu:<br />
<br />
*** BOOT MENU (NOR) ***<br />
<br />
Boot<br />
Boot from Mirco SD (FAT/ext2)<br />
Set Console to USB<br />
Set Console to Serial<br />
Reboot<br />
Power Off <br />
<br />
The FreeRunner will stay in this mode for only 30 sec. Within this time you have to start <tt>dfu-util</tt>. If you want to flash the kernel image (you will need to be root on your PC) then you have to start the following command in the 30sec your see the BOOT MENU (use kernel and rootfs from [http://sourceforge.net/projects/qtmoko/files/ http://sourceforge.net/projects/qtmoko/files/]):<br />
<br />
# for the Neo FreeRunner:<br />
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-v24.bin<br />
<br />
and finally the root fs with this one:<br />
<br />
# for the Neo FreeRunner:<br />
dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D qtmoko-debian-v24.jffs2<br />
<br />
====Preparations on the Connected PC/Laptop====<br />
* To enable connections just by using the hostname <tt>openmoko</tt> edit the <tt>/etc/hosts</tt> and add line <br />
192.168.0.202 openmoko<br />
* Enable internet connection via [[USB Networking]] so that the installation of packages will be possible.<br />
<br />
==== First Boot ====<br />
After finishing the installation without errors you have to start the FreeRunner and calibrate the touch screen. Then you see the installed ''QtMoko'' on your device. <br />
[[Image:qtmokomain.png|200px|thumb|QtMoko after first boot]]<br />
<br />
====First Login====<br />
If you want to login to your FreeRunner set up a network connection (see [[USB Networking]]) with USB cable and start:<br />
desktop# ssh -X -l root 192.168.0.202<br />
<br />
The root password is empty so set it for security reason especially when you open the ssh-daemon on the WLAN network interface. Define root password as usual on a linux box with<br />
neo# passwd<br />
If you have established the internet connection via USB cable then update the repository data:<br />
neo# apt-get update <br />
If you want to check if the internet connection is available on your freerunner ping the OpenMoko web server with:<br />
neo# ping 88.198.93.221<br />
neo# ping wiki.openmoko.org<br />
If the first ping works and the second doesn't then check the DNS server settings (see [[USB Networking]]).<br />
<br />
==== Setting Time and Date ====<br />
Set the time and date on from your linux box with<br />
<pre><br />
ssh root@openmoko "date -us @`date -u +%s`"<br />
</pre><br />
sync the hardware clock with the system time to make your change persist over reboots:<br />
<pre><br />
# hwclock --systohc<br />
</pre><br />
If you want to set the time with a NTP Client install the following package, if you have a network connection available (see [[USB Networking]])<br />
<pre><br />
# apt-get install ntpdate<br />
# ntpdate-debian<br />
</pre><br />
For further detail see [[Setting Date and Time]].<br />
<br />
== Usage ==<br />
=== Size Root File System ===<br />
If you want to install e.g. [[Twinkle]] and [[Navit]] on QtMoko the size of internal NAND memory is not sufficient (Twinkle need > 100MB). By creating symbolic links some memory problems can be avoided. <br />
{{Note|'''(Size Root Filesystem)''' Create symbolic links from root file system to SD-card to save internal memory.If some folders are symb-linked to SD-Card (with e.g. ext2 partition), e.g.<br />
# mkdir /media/card/share<br />
# mkdir /media/card/share/navit<br />
# ln -s /media/card/share/navit /usr/share/navit <br />
It recommended to be an ext2-partition. After creating symb-links install software.}}<br />
<br />
Consider installing QtMoko on MircroSD instead with [[Qi]], if you want to make use of debian applications that exceed NAND memory capacity.<br />
<br />
=== Login ===<br />
If you want to login to your FreeRunner set up a network connection (see [[USB Networking]]) with USB cable and start:<br />
desktop# ssh -X -l root 192.168.0.202<br />
or if hostname is defined in <tt>/etc/hosts</tt><br />
desktop# ssh -X -l root openmoko<br />
=== Installation of Applications ===<br />
If you want to install applications (e.g. <tt>myapplication</tt>) login on your freerunner <br />
# apt-get install myapplication<br />
Replace <tt>myapplication</tt> by the package name of application name you want to start, e.g. if you want to install the command line editor <tt>vim</tt>.<br />
# apt-get install vim<br />
==== Navit ====<br />
<br />
===== Navit Installation =====<br />
If you want to install e.g. the application [[Navit]], you have to install the following packages. Navit needs and X-Server and it will run under [[QX]].<br />
# apt-get install flite<br />
# apt-get install unzip<br />
The zip-package is necessary to unzip the [http://www.openmobile.nl/media/download_gallery/navit-qtm.zip navit-qtm.zip] package. <br />
# cd /media/card<br />
# mkdir download<br />
# cd download<br />
# wget http://www.openmobile.nl/media/download_gallery/navit-qtm.zip<br />
# cd /<br />
During <tt>unzip</tt> you will be asked to replace <tt>/opt/qtmoko/bin/ppp-network</tt>. This has to be done to solve problems with DNS over GPRS. Backup <tt>ppp-network</tt> file before unzipping <tt>navit-qtm.zip</tt>. <br />
# cp /opt/qtmoko/bin/ppp-network /opt/qtmoko/bin/ppp-network.bak<br />
# unzip /media/card/download/navit-qtm.zip<br />
# rm /media/card/download/navit-qtm.zip<br />
Unzipping the file will overwrite the following files too:<br />
/opt/qtmoko/etc/qx/favourites.conf<br />
/opt/qtmoko/etc/qx/profiles.conf<br />
{{Note|Unzip extracts and overwrites the network settings files mentioned above. Due to this fact the usb0 MAC address changes for the USB connection to your freerunner. E.g. under Ubuntu 10.04 the new network interface for usb0 has to configure again}}<br />
<br />
Now you have to restart your Freerunner, but you can also try from the commandline of your neo:<br />
# echo 1 > /proc/sys/vm/overcommit_memory<br />
After restart you can start [[Navit]] under [[QX]].<br />
[[Image:QX_Navit1.png|100px|thumb|Navit in QX Main Menu]]<br />
<br />
===== Download Maps =====<br />
Create a folder <tt>MapsNavit</tt> on your SD card<br />
# mkdir /media/card/MapsNavit<br />
The navit QT package [http://www.openmobile.nl/media/download_gallery/navit-qtm.zip navit-qtm.zip] from http://www.openmobile.nl the <tt>navit.xml</tt> is predefined for benelux maps and will try to load <tt>osm_benelux.bin</tt> that should be store at<br />
/media/card/MapsNavit/osm_benelux.bin<br />
If you want to use map for another country you can just store a downloaded [[Navit]]-Map in that folder and rename it <tt>osm_benelux.bin</tt>. If the map name should make sense, then you have to edit the <tt>navit.xml</tt>. See [[Navit]]-manual for details. You can find the <tt>navit.xml</tt> at:<br />
# /usr/share/navit/navit.xml<br />
Create the folder <tt>.navit</tt> in the home directory on your FR and copy <tt>navit.xml</tt> to directory:<br />
# cd ~<br />
# mkdir .navit<br />
# cp /usr/share/navit/navit.xml .navit/navit.xml <br />
If you have the editor <tt>vim</tt> installed then edit the file at line 376 approx.:<br />
# vim ~/.navit/navit.xml<br />
If you have downloaded the file <tt>germany.bin</tt> your mapset-tags should look like this:<br />
<pre><br />
<!-- Mapset template for openstreetmaps --><br />
<mapset enabled="yes"><br />
<map type="binfile" enabled="yes" data="/media/card/MapsNavit/germany.bin"/><br />
</mapset><br />
</pre><br />
<br />
===== Starting Navit =====<br />
[[Image:QX_Navit_Launch.png|100px|thumb|Launch Navit in QX]]<br />
* Open Main Menu by clicking on the green Q-Topia "Q"-Box.<br />
* Open Applications (4 Boxes, red, yellow, green, blue)<br />
* Scroll down and open QX<br />
* Select Navit<br />
* Click on the white Paper Icon on the bottom left to open the context menu of the QX application.<br />
* Select Launch to start Navit.<br />
* Exit with AUX-Button without stopping navit<br />
<br />
=== VoIP ===<br />
==== Integrated VoIP-Client ====<br />
QtMoko has an integrated VoIP-Client, which would be perfect to use a SIP-Account to do free of charge mobile communication world wide. But at the moment the integrated VoIP-Client does not work, due to some strange problems in Version v24 (see [http://qtmoko.org/wiki/Main_Page QtMoko-Wiki] for current status of development).<br />
<br />
[http://wiki.openmoko.org/wiki/Android_usage Android on Freerunner] has an integrated SIP-Client [[SipDroid]] that has strange audio problems as well (see http://sipdroid.org ). May some underlying problem <br />
* the integrated VoIP-Client and<br />
* [http://www.google.de/search?q=Sipdroid+Audio+Problem SIPdroid Audio Problem]<br />
have in common.<br />
<br />
==== Twinkle ====<br />
See [[Twinkle]] for further details or the official Website [http://www.twinklephone.com/ http://www.twinklephone.com/]<br />
<pre><br />
apt-get install twinkle<br />
</pre><br />
For installation (>100MB) it would be necessary to install QtMoko on MircoSD.<br />
<br />
== Links ==<br />
* [http://qtmoko.org/wiki/Main_Page Qt Wiki]<br />
* [http://sourceforge.net/projects/qtmoko/files/ Qt Download]<br />
<br />
[[Category:Qt Moko| ]]</div>Dareushttp://openmoko.org/wiki/User_talk:DareusUser talk:Dareus2010-08-14T16:26:02Z<p>Dareus: </p>
<hr />
<div>hi, why you delete Czech joke?<br />
sorry, I was wrong I corrected everything now, thank you!</div>Dareushttp://openmoko.org/wiki/JokesJokes2010-08-14T16:25:12Z<p>Dareus: /* Jokes in English */</p>
<hr />
<div>= Jokes in English =<br />
<br />
'''Q: Why did OM cross the road?'''<br />
<br />
A: To get to another toolkit :)<br />
<br />
'''Q: How many OM devs does it take to change a lightbulb?'''<br />
<br />
A: Well first we need to abandon the old lightbulb holder because at a later date we may not be able to plug a floodlight in, bring in a new lightbulb holder and adapt it to multiple floodlights, meanwhile the engineering team has realized that this will only run green floodlights and has started rewiring the whole house.. :) The burnt out lightbulb is due to be fixed at a later date :) <br />
<br />
'''Q: What is the difference between a professional photographer and OM user?'''<br />
<br />
A: The OM user has to flash more often :)<br />
<br />
'''Q: Why did the OM newbie log onto #openmoko?'''<br />
<br />
A: Because they had not read:<br />
*# the wiki, and<br />
*# the topic<br />
As then they would know you slide your finder up on the keyboard to get the numbers to enter your sim pin.<br />
<br />
'''Q: What's the difference between an iphone and a freerunner?'''<br />
<br />
A: One works but takes away your freedom, the other is free but needs your work<br />
<br />
Knock, Knock<br />
Who's There?<br />
A Neo User<br />
A Neo User<br />
<br />
'''Q: What did the Neo say to the insomniac?'''<br />
<br />
A: At least when you go to sleep you know you'll wake up!<br />
<br />
'''Ancient chinese proverb:''' "Neo owner is man carrying wall charger"<br />
<br />
'''Q: What's the difference between a brick and a freerunner?'''<br />
<br />
A: The brick is heavier... slightly.<br />
<br />
A: The brick comes in different colors.<br />
<br />
A: You can't de-brick the brick.<br />
<br />
A: A brick doesn't have to be recharged every twelve hours<br />
<br />
A: A brick will reliably perform it's intended function out of the box, no configuration required.<br />
<br />
A: You don't have to constantly re-flash / update the software on a brick<br />
<br />
A: The brick will not buzz<br />
<br />
A: The brick won't stop working after a day or two<br />
<br />
A: The brick is waterproof<br />
<br />
A: Bricks are cheap, reliable, and widely available.<br />
<br />
A: A brick isn't designed to make phone calls.<br />
<br />
'''Q: And what's the similarity?'''<br />
<br />
A: The probability they ever reliably will.<br />
<br />
'''OM2008.9 and FSO walk into a bar.'''<br />
<br />
"How are you? How are you?" asks FSO.<br />
<br />
"Buzzzzzzz" says OM2008.9<br />
<br />
''' A Freerunner, an iPhone and a CG900 walk into a bar.'''<br />
<br />
"I wish I had your prestige" says the CG900<br />
<br />
"I wish I had your price" says the iPhone<br />
<br />
"Waitaminute, gotta reboot quickly" says the Freerunner<br />
<br />
'''Q: How to switch off this phone?'''<br />
<br />
A: You have to write program :)<br />
<br />
<!--consider using this kind of formatting:--><br />
;Q What if somebody important calls?:A Err..<br />
<br />
;A Because it messes up with the normal order in which people read things.:Q Why is top-posting prohibited on our mailing lists?<br />
<br />
;Q What is your new year resolution?:A 640x480.<br />
<br />
;Q It looks like every HW problem in the Freerunner is solved with a larger capacitor. What do you think went wrong in the design process? :A. I think it was a lack of capacity.<br />
<br />
<br />
'''E-mail quotes:'''<br />
<br />
Hello,<br />
<br />
<br />
Yesterday I accidentally put my OM phone near LCD TV (Samsung).<br />
<br />
SW on OM is QT Extended and when I press power button (to wake up mobile) TV immediately turn off.<br />
<br />
I tried again and TV changed channel. So, on my phone this behavioure is repeatable.<br />
<br />
Is it normal behavioure?<br />
<br />
Thanks in advance<br />
<br />
Mile<br />
<br />
<br />
<br />
Steve Mosher on the Community ML:<br />
<br />
When OM throws a party nobody leaves with a buzz.<br />
<br />
<br />
<br />
<br />
Dr. H. Nikolaus Schaller on community ML:<br />
<br />
I have finally found where the shape and visual appearance of the Neo1973 and Freerunner come from:<br />
http://maps.google.com/maps?ll=54.897579,23.882423&z=16&t=h&hl=en<br />
<br />
<br />
'''IRC quotes:'''<br />
<br />
[16:03] <jadams_> does 2008.8 support the neo yet?<br />
<br />
<AntonTakk> i don't want another phone that would just need a bubble on top to look like an apple mouse<br />
<playya_> AntonTakk, a apple mouse has less buttons<br />
<br />
<Rampentpancake> can i run openmoko as a live cd?<br />
<br />
<Rampentpancake> like is it a bootable linux distribution?<br />
<br />
<sybren> DocScrutinizer: apt as replacement for opkg on SHR?<br />
<DocScrutinizer> sybren: sure. even a 20 year old glass of jellyfisch could replace opkg<br />
<br />
'''Motivator'''<br />
[http://www.om.vptt.ch/site/wp-content/uploads/2008/11/poster81947927.jpg]<br />
<br />
'''Accessories'''<br />
* [http://lists.openmoko.org/pipermail/support/attachments/20081201/5bc502e1/attachment-0001.jpg Freerunner anti-theft-protection]<br />
<br />
'''Fantasy release announcements:'''<br />
* New distribution: [http://scap.linuxtogo.org/files/2c3159f3e1a2622fd56fe29d2f222d9c.png OpenmokoMe Millenium Edition] !<br />
* New hardware: [http://newstechnica.com/2008/09/22/free-software-foundation-announces-gnuphone/ the GnuPhone].<br />
<br />
= Openmoko Jokes in Other Languages =<br />
<br />
As a special page, I'd like all languages to be on the same page.<br />
<br />
== Finnish ==<br />
<br />
[http://www.1songlyrics.com/k/kummeli/jumankauta-juu-n--s-p-iv--.html Kummeli-assosiaatio]<br><br />
”GTA nolla kakkonen on, luureista ehkä voittamaton;<br><br />
pientä laittoo se vaatii vaan, sitten baanalle brassailemaan<br><br />
...<br><br />
Jumankauta juu nääs päivää, ei ole huolen häivää;<br><br />
toolkitit kun tunnelmaa tuo, bassfix ja buzzfix soundit luo”<br><br />
<br />
(saa jatkaa/kehitellä)<br />
<br />
== Czech ==<br />
<br />
[http://joejoe.blog.root.cz/2010/08/07/retezovka-co-tady-pohledavate/]<br><br />
aplikace mobile windws 6.5 - windows mobile suxx, pořiď si konečně pořádný telefon, třeba brokenmoko<br />
<br />
== ... ==<br />
<br />
[[Category:Funny and ironic stuff]]</div>Dareushttp://openmoko.org/wiki/JokesJokes2010-08-14T16:23:58Z<p>Dareus: Undo revision 82048 by Dareus (Talk)</p>
<hr />
<div>= Jokes in English =<br />
<br />
'''Q: Why did OM cross the road?'''<br />
<br />
A: To get to another toolkit :)<br />
<br />
'''Q: How many OM devs does it take to change a lightbulb?'''<br />
<br />
A: Well first we need to abandon the old lightbulb holder because at a later date we may not be able to plug a floodlight in, bring in a new lightbulb holder and adapt it to multiple floodlights, meanwhile the engineering team has realized that this will only run green floodlights and has started rewiring the whole house.. :) The burnt out lightbulb is due to be fixed at a later date :) <br />
<br />
'''Q: What is the difference between a professional photographer and OM user?'''<br />
<br />
A: The OM user has to flash more often :)<br />
<br />
'''Q: Why did the OM newbie log onto #openmoko?'''<br />
<br />
A: Because they had not read:<br />
*# the wiki, and<br />
*# the topic<br />
As then they would know you slide your finder up on the keyboard to get the numbers to enter your sim pin.<br />
<br />
'''Q: What's the difference between an iphone and a freerunner?'''<br />
<br />
A: One works but takes away your freedom, the other is free but needs your work<br />
<br />
Knock, Knock<br />
Who's There?<br />
A Neo User<br />
A Neo User<br />
<br />
'''Q: What did the Neo say to the insomniac?'''<br />
<br />
A: At least when you go to sleep you know you'll wake up!<br />
<br />
'''Ancient chinese proverb:''' "Neo owner is man carrying wall charger"<br />
<br />
'''Q: What's the difference between a brick and a freerunner?'''<br />
<br />
A: The brick is heavier... slightly.<br />
<br />
A: The brick comes in different colors.<br />
<br />
A: You can't de-brick the brick.<br />
<br />
A: A brick doesn't have to be recharged every twelve hours<br />
<br />
A: A brick will reliably perform it's intended function out of the box, no configuration required.<br />
<br />
A: You don't have to constantly re-flash / update the software on a brick<br />
<br />
A: The brick will not buzz<br />
<br />
A: The brick won't stop working after a day or two<br />
<br />
A: The brick is waterproof<br />
<br />
A: Bricks are cheap, reliable, and widely available.<br />
<br />
A: A brick isn't designed to make phone calls.<br />
<br />
'''Q: And what's the similarity?'''<br />
<br />
A: The probability they ever reliably will.<br />
<br />
'''OM2008.9 and FSO walk into a bar.'''<br />
<br />
"How are you? How are you?" asks FSO.<br />
<br />
"Buzzzzzzz" says OM2008.9<br />
<br />
''' A Freerunner, an iPhone and a CG900 walk into a bar.'''<br />
<br />
"I wish I had your prestige" says the CG900<br />
<br />
"I wish I had your price" says the iPhone<br />
<br />
"Waitaminute, gotta reboot quickly" says the Freerunner<br />
<br />
'''Q: How to switch off this phone?'''<br />
<br />
A: You have to write program :)<br />
<br />
<!--consider using this kind of formatting:--><br />
;Q What if somebody important calls?:A Err..<br />
<br />
;Q Why is top-posting prohibited on our mailing lists?:A Because it messes up with the normal order in which people read things.<br />
<br />
;Q What is your new year resolution?:A 640x480.<br />
<br />
;Q It looks like every HW problem in the Freerunner is solved with a larger capacitor. What do you think went wrong in the design process? :A. I think it was a lack of capacity.<br />
<br />
<br />
'''E-mail quotes:'''<br />
<br />
Hello,<br />
<br />
<br />
Yesterday I accidentally put my OM phone near LCD TV (Samsung).<br />
<br />
SW on OM is QT Extended and when I press power button (to wake up mobile) TV immediately turn off.<br />
<br />
I tried again and TV changed channel. So, on my phone this behavioure is repeatable.<br />
<br />
Is it normal behavioure?<br />
<br />
Thanks in advance<br />
<br />
Mile<br />
<br />
<br />
<br />
Steve Mosher on the Community ML:<br />
<br />
When OM throws a party nobody leaves with a buzz.<br />
<br />
<br />
<br />
<br />
Dr. H. Nikolaus Schaller on community ML:<br />
<br />
I have finally found where the shape and visual appearance of the Neo1973 and Freerunner come from:<br />
http://maps.google.com/maps?ll=54.897579,23.882423&z=16&t=h&hl=en<br />
<br />
<br />
'''IRC quotes:'''<br />
<br />
[16:03] <jadams_> does 2008.8 support the neo yet?<br />
<br />
<AntonTakk> i don't want another phone that would just need a bubble on top to look like an apple mouse<br />
<playya_> AntonTakk, a apple mouse has less buttons<br />
<br />
<Rampentpancake> can i run openmoko as a live cd?<br />
<br />
<Rampentpancake> like is it a bootable linux distribution?<br />
<br />
<sybren> DocScrutinizer: apt as replacement for opkg on SHR?<br />
<DocScrutinizer> sybren: sure. even a 20 year old glass of jellyfisch could replace opkg<br />
<br />
'''Motivator'''<br />
[http://www.om.vptt.ch/site/wp-content/uploads/2008/11/poster81947927.jpg]<br />
<br />
'''Accessories'''<br />
* [http://lists.openmoko.org/pipermail/support/attachments/20081201/5bc502e1/attachment-0001.jpg Freerunner anti-theft-protection]<br />
<br />
'''Fantasy release announcements:'''<br />
* New distribution: [http://scap.linuxtogo.org/files/2c3159f3e1a2622fd56fe29d2f222d9c.png OpenmokoMe Millenium Edition] !<br />
* New hardware: [http://newstechnica.com/2008/09/22/free-software-foundation-announces-gnuphone/ the GnuPhone].<br />
<br />
= Openmoko Jokes in Other Languages =<br />
<br />
As a special page, I'd like all languages to be on the same page.<br />
<br />
== Finnish ==<br />
<br />
[http://www.1songlyrics.com/k/kummeli/jumankauta-juu-n--s-p-iv--.html Kummeli-assosiaatio]<br><br />
”GTA nolla kakkonen on, luureista ehkä voittamaton;<br><br />
pientä laittoo se vaatii vaan, sitten baanalle brassailemaan<br><br />
...<br><br />
Jumankauta juu nääs päivää, ei ole huolen häivää;<br><br />
toolkitit kun tunnelmaa tuo, bassfix ja buzzfix soundit luo”<br><br />
<br />
(saa jatkaa/kehitellä)<br />
<br />
== Czech ==<br />
<br />
[http://joejoe.blog.root.cz/2010/08/07/retezovka-co-tady-pohledavate/]<br><br />
aplikace mobile windws 6.5 - windows mobile suxx, pořiď si konečně pořádný telefon, třeba brokenmoko<br />
<br />
== ... ==<br />
<br />
[[Category:Funny and ironic stuff]]</div>Dareushttp://openmoko.org/wiki/JokesJokes2010-08-14T08:51:58Z<p>Dareus: the joke now is in the right order and the spam has been removed</p>
<hr />
<div>= Jokes in English =<br />
<br />
'''Q: Why did OM cross the road?'''<br />
<br />
A: To get to another toolkit :)<br />
<br />
'''Q: How many OM devs does it take to change a lightbulb?'''<br />
<br />
A: Well first we need to abandon the old lightbulb holder because at a later date we may not be able to plug a floodlight in, bring in a new lightbulb holder and adapt it to multiple floodlights, meanwhile the engineering team has realized that this will only run green floodlights and has started rewiring the whole house.. :) The burnt out lightbulb is due to be fixed at a later date :) <br />
<br />
'''Q: What is the difference between a professional photographer and OM user?'''<br />
<br />
A: The OM user has to flash more often :)<br />
<br />
'''Q: Why did the OM newbie log onto #openmoko?'''<br />
<br />
A: Because they had not read:<br />
*# the wiki, and<br />
*# the topic<br />
As then they would know you slide your finder up on the keyboard to get the numbers to enter your sim pin.<br />
<br />
'''Q: What's the difference between an iphone and a freerunner?'''<br />
<br />
A: One works but takes away your freedom, the other is free but needs your work<br />
<br />
Knock, Knock<br />
Who's There?<br />
A Neo User<br />
A Neo User<br />
<br />
'''Q: What did the Neo say to the insomniac?'''<br />
<br />
A: At least when you go to sleep you know you'll wake up!<br />
<br />
'''Ancient chinese proverb:''' "Neo owner is man carrying wall charger"<br />
<br />
'''Q: What's the difference between a brick and a freerunner?'''<br />
<br />
A: The brick is heavier... slightly.<br />
<br />
A: The brick comes in different colors.<br />
<br />
A: You can't de-brick the brick.<br />
<br />
A: A brick doesn't have to be recharged every twelve hours<br />
<br />
A: A brick will reliably perform it's intended function out of the box, no configuration required.<br />
<br />
A: You don't have to constantly re-flash / update the software on a brick<br />
<br />
A: The brick will not buzz<br />
<br />
A: The brick won't stop working after a day or two<br />
<br />
A: The brick is waterproof<br />
<br />
A: Bricks are cheap, reliable, and widely available.<br />
<br />
A: A brick isn't designed to make phone calls.<br />
<br />
'''Q: And what's the similarity?'''<br />
<br />
A: The probability they ever reliably will.<br />
<br />
'''OM2008.9 and FSO walk into a bar.'''<br />
<br />
"How are you? How are you?" asks FSO.<br />
<br />
"Buzzzzzzz" says OM2008.9<br />
<br />
''' A Freerunner, an iPhone and a CG900 walk into a bar.'''<br />
<br />
"I wish I had your prestige" says the CG900<br />
<br />
"I wish I had your price" says the iPhone<br />
<br />
"Waitaminute, gotta reboot quickly" says the Freerunner<br />
<br />
'''Q: How to switch off this phone?'''<br />
<br />
A: You have to write program :)<br />
<br />
<!--consider using this kind of formatting:--><br />
;Q What if somebody important calls?:A Err..<br />
<br />
;A. Because it messes up with the normal order in which people read things.:Q. Why is top-posting prohibited on our mailing lists?<br />
<br />
;Q What is your new year resolution?:A 640x480.<br />
<br />
;Q It looks like every HW problem in the Freerunner is solved with a larger capacitor. What do you think went wrong in the design process? :A. I think it was a lack of capacity.<br />
<br />
<br />
'''E-mail quotes:'''<br />
<br />
Hello,<br />
<br />
<br />
Yesterday I accidentally put my OM phone near LCD TV (Samsung).<br />
<br />
SW on OM is QT Extended and when I press power button (to wake up mobile) TV immediately turn off.<br />
<br />
I tried again and TV changed channel. So, on my phone this behavioure is repeatable.<br />
<br />
Is it normal behavioure?<br />
<br />
Thanks in advance<br />
<br />
Mile<br />
<br />
<br />
<br />
Steve Mosher on the Community ML:<br />
<br />
When OM throws a party nobody leaves with a buzz.<br />
<br />
<br />
<br />
<br />
Dr. H. Nikolaus Schaller on community ML:<br />
<br />
I have finally found where the shape and visual appearance of the Neo1973 and Freerunner come from:<br />
http://maps.google.com/maps?ll=54.897579,23.882423&z=16&t=h&hl=en<br />
<br />
<br />
'''IRC quotes:'''<br />
<br />
[16:03] <jadams_> does 2008.8 support the neo yet?<br />
<br />
<AntonTakk> i don't want another phone that would just need a bubble on top to look like an apple mouse<br />
<playya_> AntonTakk, a apple mouse has less buttons<br />
<br />
<Rampentpancake> can i run openmoko as a live cd?<br />
<br />
<Rampentpancake> like is it a bootable linux distribution?<br />
<br />
<sybren> DocScrutinizer: apt as replacement for opkg on SHR?<br />
<DocScrutinizer> sybren: sure. even a 20 year old glass of jellyfisch could replace opkg<br />
<br />
'''Motivator'''<br />
[http://www.om.vptt.ch/site/wp-content/uploads/2008/11/poster81947927.jpg]<br />
<br />
'''Accessories'''<br />
* [http://lists.openmoko.org/pipermail/support/attachments/20081201/5bc502e1/attachment-0001.jpg Freerunner anti-theft-protection]<br />
<br />
'''Fantasy release announcements:'''<br />
* New distribution: [http://scap.linuxtogo.org/files/2c3159f3e1a2622fd56fe29d2f222d9c.png OpenmokoMe Millenium Edition] !<br />
* New hardware: [http://newstechnica.com/2008/09/22/free-software-foundation-announces-gnuphone/ the GnuPhone].<br />
<br />
= Openmoko Jokes in Other Languages =<br />
<br />
As a special page, I'd like all languages to be on the same page.<br />
<br />
== Finnish ==<br />
<br />
[http://www.1songlyrics.com/k/kummeli/jumankauta-juu-n--s-p-iv--.html Kummeli-assosiaatio]<br><br />
”GTA nolla kakkonen on, luureista ehkä voittamaton;<br><br />
pientä laittoo se vaatii vaan, sitten baanalle brassailemaan<br><br />
...<br><br />
Jumankauta juu nääs päivää, ei ole huolen häivää;<br><br />
toolkitit kun tunnelmaa tuo, bassfix ja buzzfix soundit luo”<br><br />
<br />
(saa jatkaa/kehitellä)<br />
<br />
== ... ==<br />
<br />
[[Category:Funny and ironic stuff]]</div>Dareushttp://openmoko.org/wiki/Freerunner_Navigation_Board_v2Freerunner Navigation Board v22010-07-13T16:44:53Z<p>Dareus: </p>
<hr />
<div>The second version of the [[Freerunner Navigation Board]] will include lots of new stuff to play with, while still providing the same feature set as the first version.<br />
<br />
=Features=<br />
==Top side==<br />
===3D Gyroscope ITG-3200)===<br />
The new ITG-3200 digital gyroscope detects rotations and measures their angular velocicy. This enables the FR to be used as game controller or to improve navigation capabilities without GPS.<br />
<br />
===3D Magnetometer HMC5843===<br />
A magnetometer senses magnetic fields. It can be used as compass for navigation purposes or to sense fields from other magnetic sources.<br />
<br />
===Air pressure/temperature sensor: BMP085===<br />
[insert nice description here]<br />
<br />
==Bottom side==<br />
===4ch Programmable LED Controller===<br />
This chip can source or sink current for up to four LEDs with a maximum of 25mA per LED. In addition to simple on/off states it can be programmed to blink or fade individual channels or a group of channels. Since the chip does everything on its own, it will continue to work even if the host cpu suspends. This allows the often requested feature <del>to drain the battery even faster</del> to notify users of incoming SMS or missed phone calls by blinking a LED even if the phone is suspended. A blink frequency down to once every 10 seconds and a widely adjustable duty cycle allows for very short flashes to save battery power.<br />
<br />
===1kHz – 68MHz Programmable oscillator===<br />
This is, well, a programmable oscillator from which one frequency output and the output enable pin are available at testpoints. My intention was to use it as 38kHz oscillator to generate the carrier frequency of common infrared remote controls. The output enable can be connected to a GPIO. After implementing a small driver, this should work as a generic remote control solution using lirc.<br />
<br />
===16 bit Analog to Digital Converter===<br />
This chip was used on the FRNBv1 to digitize analog gyroscope outputs. The FRNBv2 does not use it for own purposes, so it is completely under user's control.<br />
<br />
===Touch Sensor===<br />
The MPR121 from Freescale Semiconductor is a multi channel proximity capacitive touch sensor controller. Up to twelve sensor areas could be connected, but due to space constraints, only eight channels are accessible at solder pads.<br />
It is not guaranteed that the chip will work as intended, but I think it's worth to test it.<br />
<br />
<br />
=Availability=<br />
The board will be availabe to purchase starting from the middle of august. It comes in three tastes:<br />
* CAB: Completely assembled board. Just add some wires and you're ready<br />
* DIY: Do it yourself! the PCB and all components needed to get your hands dirty<br />
* PCB: The bare PCB. You are free to buy only what you need.<br />
<br />
The CAB and DIY packages miss the programmable oscillator and the analog to digital converter chips because they are rather expensive and can't be used without additional electronics. If you need their functionality it's possible to add them later on because they come in leaded packages and are hand solderable.<br />
<br />
==Pricing (estimates)==<br />
* CAB: probably in the Range of 75€ to 80€<br />
* DIY: about 50€<br />
* PCB: about 7€</div>Dareushttp://openmoko.org/wiki/Main_PageMain Page2010-05-07T13:49:21Z<p>Dareus: Undo revision 81000 by Eugenegriffin (Talk) SPAM</p>
<hr />
<div>{{Languages|Main Page}}__NOTOC__<br />
__NOEDITSECTION__[[Image:Neo front 3.gif|right]]<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
'''Openmoko™''' is a project dedicated to delivering mobile phones with an open source software stack. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.<br />
<br />
* [[Introduction]]<br />
* [[Why Openmoko|Why Openmoko?]]<br />
<br />
[[More Information]]<br />
<br />
===Get Involved===<br />
Openmoko is a project driven by a community of passionate and intelligent volunteers. If you have the ability, please contribute to our cause. Openmoko's ambitions far exceed the resources available. <br />
<br />
* [[Community Resources]]<br />
* [[Gta02-core|Create a new hardware revision of the gta02 hardware]]<br />
* [[Create User Manuals]] for [[Distributions]] and [[Applications]]<br />
* Enhance the multi-device multi-vendor [[FSO]] middleware.<br />
<br />
===How To Purchase===<br />
The Neo FreeRunner is sold by various [[distributors]] around the world.<br />
<br />
See [[Getting Openmoko]] for more information.<br />
<br />
----<br />
<br />
====Latest News====<br />
<br />
{{News}}<br />
[[News Archive|more news...]]<br />
<br />
----</div>Dareushttp://openmoko.org/wiki/Main_PageMain Page2010-04-16T12:52:41Z<p>Dareus: Undo SPAM revision 80749 by Kenneth131 (Talk)</p>
<hr />
<div>{{Languages|Main Page}}__NOTOC__<br />
__NOEDITSECTION__[[Image:Neo front 3.gif|right]]<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
'''Openmoko™''' is a project dedicated to delivering mobile phones with an open source software stack. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.<br />
<br />
* [[Introduction]]<br />
* [[Why Openmoko|Why Openmoko?]]<br />
<br />
[[More Information]]<br />
<br />
===Get Involved===<br />
Openmoko is a project driven by a community of passionate and intelligent volunteers. If you have the ability, please contribute to our cause. Openmoko's ambitions far exceed the resources available. <br />
<br />
* [[Community Resources]]<br />
* [[Gta02-core|Create a new hardware revision of the gta02 hardware]]<br />
* [[Create User Manuals]] for [[Distributions]] and [[Applications]]<br />
* Enhance the multi-device multi-vendor [[FSO]] middleware.<br />
<br />
===How To Purchase===<br />
The Neo FreeRunner is sold by various [[distributors]] around the world.<br />
<br />
See [[Getting Openmoko]] for more information.<br />
<br />
----<br />
<br />
====Latest News====<br />
<br />
{{News}}<br />
[[News Archive|more news...]]<br />
<br />
----</div>Dareushttp://openmoko.org/wiki/Community_UpdatesCommunity Updates2010-03-02T14:05:52Z<p>Dareus: </p>
<hr />
<div>{{Languages}}<br />
This page gives you access to some regular updates released by the projects, OM or community. All communications channels of the Openmoko community are listed at the [[Community Resources]] page. <br />
<br />
The official Openmoko updates (discontinued early 2009) can be found in [[Weekly Engineering News]].<br />
<br />
You can see the latest edition [[Community Updates/Latest|here]]<br />
<br />
= Post launch series =<br />
* DRAFT: [[Community Updates/Draft_2010-04-01]]<br />
* [[Community Updates/2010-03-01]]<br />
* [[Community Updates/2010-02-10]]<br />
* [[Community Updates/2010-01-14]]<br />
* [[Community Updates/2009-12-31]]<br />
* [[Community Updates/2009-12-09]]<br />
* [[Community Updates/2009-11-25]]<br />
* [[Community Updates/2009-11-11]]<br />
* [[Community Updates/2009-10-28]]<br />
* [[Community Updates/2009-10-14]]<br />
* [[Community Updates/2009-09-30]]<br />
* [[Community Updates/2009-09-16]]<br />
* [[Community Updates/2009-09-02]]<br />
* [[Community Updates/2009-08-19]]<br />
* [[Community Updates/2009-08-06]]<br />
* [[Community Updates/2009-07-23]]<br />
* [[Community Updates/2009-07-09]]<br />
* [[Community Updates/2009-06-25]]<br />
* [[Community Updates/2009-05-22]]<br />
* [[Community Updates/2009-04-30]]<br />
* [[Community Updates/2009-04-17]]<br />
* [[Community Updates/2009-04-05]]<br />
* [[Community Updates/2009-03-20]]<br />
* [[Community Updates/2009-03-06]]<br />
* [[Community Updates/2009-02-20]]<br />
* [[Community Updates/2009-02-06]]<br />
* [[Community Updates/2009-01-23]]<br />
* [[Community Updates/2009-01-12]]<br />
* [[Community Updates/2008-12-29]]<br />
* [[Community Updates/2008-12-15]]<br />
* [[Community Updates/2008-12-01]]<br />
* [[Community Updates/2008-11-16]]<br />
* [[Community Updates/2008-11-02]]<br />
* [[Community Updates/2008-10-19]]<br />
* [[Community Updates/2008-10-03]]<br />
* [[Community Updates/2008-09-17]] - Activity since launch<br />
<br />
== Rules for community updates ==<br />
After May 22nd 2009 OM stopped working on community updates. These rules are here to make it possible for the community to keep the updates running.<br />
<br />
The draft of the news will be listed here but not on the main page until it gets released. (example, see [[Community Update Draft]] ). Upon the release of the current updates a new page should be created. The news will be added there. On release, the link will be set on the main page. Detailed instructions below.<br />
<br />
'''Adding news'''<br />
# Don't expect someone else to add it, add it yourself and make it nice<br />
# Add links to blog posts, applications, mailing list posts that you think are worth to announce to the whole community<br />
<br />
'''Releasing'''<br />
# If it's The Release Date and you notice the news has not been released, DO IT! Don't expect someone else to do it for you.<br />
# When you release, move the content of Talk: page to the actual wikipage.<br />
# Add a link to the released update page to http://wiki.openmoko.org/index.php?title=Community_Updates<br />
# Prepare the draft page for the next community news: captions, dates etc.. Releasing news on Thursdays every two weeks sound's good to me.<br />
# Send a post to the community mailing list with the link to the released news and the draft of the next news.<br />
<br />
= Ramp up to launch series =<br />
<br />
Even though Openmoko strives to keep the community informed of the development progress, Openmoko does not provide delivery dates. Instead, Openmoko Inc. reports and discusses the project on a day to day basis, using the [http://lists.openmoko.org/pipermail/community/ openmoko-community mailing list]. Developers will wish to follow the progress on the [http://lists.openmoko.org/pipermail/openmoko-kernel/ openmoko-kernel mailing list] and the [http://lists.openmoko.org/pipermail/devel/ devel mailing list]. Major updates notices are sent to the [http://lists.openmoko.org/pipermail/announce/ announce mailing list].<br />
<br />
As FreeRunners started shipping, that series of Community Updates mostly related to the expected release date has been taken over by a more community-oriented newsletter.<br />
<br />
* [http://lists.openmoko.org/pipermail/community/2008-June/019384.html 2008-06-14 - When it will be possible to buy Openmoko?]<br />
* [http://lists.openmoko.org/pipermail/community/2008-June/018887.html 2008-06-10 - SMT is running!]<br />
* [http://lists.openmoko.org/pipermail/community/2008-June/018575.html 2008-06-05 - Cleared to start Mass production]<br />
* [http://lists.openmoko.org/pipermail/community/2008-May/017531.html 2008-05-20 - Whats up with the freerunner mass production?]<br />
* [http://lists.openmoko.org/pipermail/community/2008-April/015189.html 2008-04-14 - next costumers location]<br />
* [http://lists.openmoko.org/pipermail/community/2008-April/015080.html 2008-04-11 - FreeRunner Pricing and PVT update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-April/014928.html 2008-04-07 - Any updates on the PVT status?]<br />
* [http://lists.openmoko.org/pipermail/community/2008-March/014361.html 2008-03-25 - Production status Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-February/013555.html 2008-02-25 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-February/013356.html 2008-02-14 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-February/013280.html 2008-02-10 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-January/012821.html 2008-01-24 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-January/012499.html 2008-01-10 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-January/012357.html 2008-01-02 - Community Update]<br />
<br />
[[Category:Community Update| ]]<br />
[[Category:Community]]</div>Dareushttp://openmoko.org/wiki/Community_Updates/LatestCommunity Updates/Latest2010-03-02T14:03:59Z<p>Dareus: Redirecting to Community Updates/2010-03-01</p>
<hr />
<div>#REDIRECT [[Community Updates/2010-03-01]]</div>Dareushttp://openmoko.org/wiki/Talk:AndroidTalk:Android2010-01-18T14:29:11Z<p>Dareus: /* Suspend */</p>
<hr />
<div>== Redirect? ==<br />
<br />
Q: Shouldn't this page be removed and just redirected to [[Android on Freerunner]]? Or am I missing something? --[[User:JohnSullivan|JohnSullivan]] 16:51, 26 January 2009 (UTC)<br />
<br />
A: I refactored thos pages and separated the content between installation ([[Android on Freerunner]]), development ([[Android porting]]) and usage ([[Android usage]]). I think it's more clear than before where there was duplicate content and content for different audiances mixed. --[[User:Jernst|jernst]] 17:09, 26 January 2009 (UTC)<br />
<br />
Can we rename the [[Android on Freerunner]] page then? The name doesn't say anything about installation... How about, [[Android Installation]], if that's what you are aiming for. There's plenty of info on that page that isn't directly related to installation, and now that I'm actually playing with Android I'm finding the separation confusing.--[[User:JohnSullivan|JohnSullivan]] 18:20, 16 May 2009 (UTC)<br />
<br />
== Scanning for Files That Use the ARMv5TE ISA ==<br />
<br />
"exit -1" does not work with every /bin/sh. Anyway, if you want to give a hint, make it look like this:<br />
<pre><br />
if [ $# -ne 1 ]; then<br />
echo "usage: $0 android-directoy"<br />
exit 255<br />
fi<br />
</pre><br />
<br />
== New Images (10th November) ==<br />
<br />
Sean uploaded new Images today (10th November), but I can't find a changelog :-(<br />
<br />
== Android compared to OpenMoko OS? ==<br />
<br />
As a layman (ie. non-Hacker) I would personally love to see an indepth comparison between the Android OS and the OpenMoko OS, from the point of view of the user / consumer, as of the moment.<br />
<br />
In other words, I would love to see (for example) what I would be getting if I installed Android on the Freerunner, ''feature-wise'', as opposed to keeping the already installed OS. I think I would ''also'' be interested if it would be a good idea, ''feature-wise'', to ditch the T-Mobile G1's (aka. HTC Dream's) native Android installation for OpenMoko OS.<br />
<br />
You know, just to get the competitive spirit going ;)<br />
<br />
(Btw, right now an unlocked HTC Dream and a Freeruner both cost US$399...) --[[User:Lemi4|Lemi4]] 01:22, 18 February 2009 (UTC)<br />
<br />
== Running speed? ==<br />
<br />
Does Android really run this slow or is my Freerunner in bad shape? There is a half second delay between clicking and anything happening on screen. The API finger-painting demo is also laughably slow. On the other hand, the SurfaceView Overlay runs at (what I consider) a reasonable speed for the hardware.<br />
<br />
==Suspend==<br />
<br />
I have the latest Panicking image, with that my FR goes into suspend mode even if plugged-in and when I click the power button to wake it up, it appears immediately the unlock screen in which you have to enter your unlock movement.<br />
<br />
It's like power was pressed two times at once: one for waking up and the other to show the unlock screen.<br />
<br />
It's quite annoying because you can't see the charging percentage when you wake it up or other notifications because you immediately go further than that screen.<br />
<br />
It's just my problem?<br />
<br />
[[User:Dareus|Dareus]] - 2010-01-16-T-11:27<br />
<br />
I don't know what do you mean by "Panicking image", but images from [http://code.google.com/p/android-on-freerunner/] work well.<br />
Looks like your problem is addressed in [http://code.google.com/p/android-on-freerunner/issues/detail?id=23]<br />
<br />
[[User:Skliarie|Skliarie]] - 2010-01-16-T-19:03<br />
<br />
With panicking images I mean images from Micheal Trimarchi [http://panicking.kicks-ass.org/download/].<br />
<br />
[[User:Dareus|Dareus]] - 2010-01-18-T-14:29</div>Dareushttp://openmoko.org/wiki/Manuals/AndroidManuals/Android2010-01-16T11:31:48Z<p>Dareus: /* From Vcard */</p>
<hr />
<div>{{Languages|Android usage}}<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
[[Image:android.png]]<br />
<br />
= Introduction = <br />
<br />
{{Note|The Android for [[Neo_FreeRunner_GTA02_Hardware|FreeRunner]] development now takes place [http://code.google.com/p/android-on-freerunner/ here]. It has it's own wiki as well.}}<br />
<br />
This page is dedicated to the daily usage of Android on the [[Neo 1973]] and [[Neo FreeRunner]] handsets.<br />
<br />
The information here has been updated for the following release : [http://freerunner.android.koolu.com/release-files Koolu Beta7 Android release]. It is advisable to update to the latest release.<br />
<br />
One can find general information (porting/development) about Android on Neo phones here : [[Android]]<br />
<br />
== Using this guide ==<br />
<br />
*1 If you see a command prompt like this (#), you must run a command as user '''root''' on the connected system<br />
<br />
#<br />
<br />
If you see a command prompt like this ($), you can run the command as a regular user<br />
<br />
$<br />
<br />
*2 When you see the command<br />
<br />
adb <br />
<br />
It is assumed that you have 'adb' installed on your pc and it is in your search path, like in /usr/bin or ~/bin. If not so, you need to change to the directory you downloaded the binary to. Issue the same commands but when ever adb appears replace it with <br />
<br />
./adb<br />
<br />
adb connects your system to Android but you need to make sure you have set it up correctly first. Make sure your FreeRunner was booted while being plugged in to a USB port. (Not necessary starting Koolu beta 7) <br />
Then run the following commands:<br />
<br />
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0 (or see below for USB network setup)<br />
# adb kill-server<br />
# ADBHOST=192.168.0.202 adb devices<br />
<br />
''adb help'' gives extensive info<br />
<br />
One should now have no trouble using adb.<br />
<br />
= Getting started =<br />
<br />
Installing Android on Openmoko Freerunner, creates a phone fit for use! Of course the port is not finished yet, a lot has to be done, but for now we can live with the workarounds. <br />
<br />
==Buttons and Keyboard ==<br />
<br />
=== The Power button ===<br />
<br />
* To turn the phone '''on'''; press and hold the power button for about 5 seconds<br />
<br />
* To put the phone to '''sleep''' (and so lock it): hold the power button for about 1 second<br />
<br />
* To '''wake''' the phone from sleep: tap the power button once, then once more to unlock the screen<br />
<br />
* To turn the phone''' off''': First wake it from sleep, then hold the power button for about 2 seconds. Choose 'Power off' in the menu that appears then click 'OK' Use the back button (aux) to delete the menu if one wants to continue. <br />
<br />
* Tap the power button once to get the on screen keyboard. In many applications it also brings extra options.<br />
<br />
''Times and actions taken from Koolu beta 7''<br />
<br />
=== The Aux button ===<br />
The aux button is configured as the back button.<br />
If the application recognizes the back action, like the browser, it goes a page or action back. If not recognized, one leaves the application to the previous situation. Note the application is not killed. It stays active.<br />
<br />
<br />
=== The Home Button ===<br />
<br />
The G1 and G2 Android phones have a home button, a long press on this button creates a window with all the running applications. <br />
<br />
There is no clear key now, to show the running applications. Sometimes by chance a window with icons of the running applications appears, and then one can jump to a different running application.<br />
<br />
I suggest to create this button from a two second press on the aux button. A window with the icons of the running applications will appear. By tapping on the wanted application we can than jump to the running application. <br />
<br />
''Koolu beta7 observation''<br />
<br />
=== The Keyboard ===<br />
Works, can be brought up with short press to power button.<br />
<br />
== Making a call ==<br />
<br />
Once the phone has started you will see a 'Dialer' icon on the desktop. Tap it and you will be presented with a dialing keypad. Enter the number you wish to dial and then touch the bar containing the number to call. If you make a mistake entering the number you can touch the backspace arrow to the right of the bar.<br />
<br />
Caveats<br />
* The volume level when in a voice call is very low<br />
<br />
==Sending an SMS==<br />
<br />
Works in Koolu beta 7<br />
<br />
== Copy and pasting ==<br />
<br />
Android has a copy and paste feature built in to it. By touching and holding on a text entry box for about 2 seconds the copy & paste menu will appear.<br />
<br />
= Subsystems =<br />
<br />
<br />
=== Accelerometers ===<br />
Works, can be tested with simple game called [http://andappstore.com/AndroidPhoneApplications/apps/8872 Amazed] which is installed on current Koolu images.<br />
<br />
Android makes no use of the accelerometers yet :(<br />
<br />
''Koolu beta7 observation''<br />
<br />
=== Bluetooth ===<br />
Works, latest kernels need permissions for second rfkill interface in init.rc to turn it on.<br />
<br />
=== GPS ===<br />
Works, you can [[#Install new software|install]] [http://www.andnav.org AndNav2] (AndNav2 is installed on current Koolu images) to test it.<br />
AndNav2 is e beta version and the useable period is over. <br />
<br />
Proper working of GPS can observed with YGPS Satellites. It shows signal strength and location of each satellite.<br />
<br />
It is currently not possible to disable the GPS from the UI once activated.<br />
<br />
''Observed in Koolu beta 7''<br />
<br />
=== GPRS ===<br />
<br />
To set up GPRS you need to enter the correct settings for your network: Tap the Application tab followed by Settings > Wireless controls > Mobile networks > Access Point Names. Now if you press the power button, a menu will appear allowing you to add a 'New APN'. Touch this then add your network's GPRS & MMS settings.<br />
<br />
{{Note| At versions before Koolu beta 7 it is not possible to bring up Android's keyboard to enter the information. <br />
Update to this version (or later) if you have this problem. <br />
Otherwise install 'aKeyUI' then copy and paste the information, starting with the APN which can also be used as the Name}}Once you have entered your APN details it maybe necessary to follow this procedure to start GPRS (you will only need to do this once):<br />
<br />
Turn on Aeroplane mode, reboot, turn off Aeroplane mode<br />
<br />
You may also have to carry out the [http://wiki.openmoko.org/wiki/Android_usage#DNS_Fix DNS fix] described below.<br />
<br />
''GPRS not yet tested with Koolu beta 7''<br />
<br />
==== APN settings ====<br />
<br />
You can find most networks 'mcc' and 'mnc' numbers [http://android.v-dh.nl/internet.php here]<br />
<br />
* O2 UK - Pay as you go<br />
<br />
Enter these details to set up GPRS:<br />
<br />
carrier="o2-UK-PAYG" (Name - can be anything)<br />
mcc="234"<br />
mnc="10"<br />
apn="payandgo.o2.co.uk"<br />
user="payandgo"<br />
server="Not set"<br />
password="password"<br />
type="default"<br />
<br />
These details are also correct o2 settings but don't enter them, they stop GPRS from working properly at the moment.<br />
<br />
mmsc="http://mmsc.mms.02.co.uk:8002"<br />
proxy="193.113.200.195"<br />
port="9201"<br />
mmsproxy="193.113.200.195"<br />
mmsport="9201"<br />
<br />
* T-Mobile UK<br />
<br />
Enter these details to set up GPRS:<br />
<br />
carrier="T-Mobile-UK" (Name - can be anything)<br />
mcc="234"<br />
mnc="30"<br />
apn="general.t-mobile.uk"<br />
user="user"<br />
server="149.254.1.10"<br />
# server="149.254.201.132" (alternate server)<br />
password="wap"<br />
type="default"<br />
<br />
* Orange France<br />
Source : [http://www.planete-android.com/index.php/parametrage-operateurs-francais.html French Network parameter]<br />
<br />
GPRS settings (work): <br />
apn="orange"<br />
user="orange"<br />
password="orange"<br />
mcc="208"<br />
mnc="01"<br />
type="default"<br />
<br />
MMS settings (untested) :<br />
apn="orange.acte"<br />
proxy="192.168.10.200"<br />
port="8080"<br />
user="orange"<br />
password : "orange"<br />
mmsc="http://mms.orange.fr"<br />
mms port="8080" <br />
mcc="208"<br />
mnc"01"<br />
type="mms"<br />
<br />
Force use of Orange DNS in the ip-up script located in /system/etc/ppp :<br />
/system/bin/setprop "net.gprs.dns1" "194.051.003.056"<br />
<br />
<br />
* Cingular/Att U.S. (working with dns fix(14.6-cupcake), other than sending mms)<br />
<br />
apn="wap.cingular"<br />
username="wap@cingulargprs.com"<br />
pass="cingular1"<br />
mmsc="mmsc.cingular.com"<br />
mms proxy="wireless.cingular.com"<br />
mms port = 80<br />
mcc= 310<br />
mnc= 410<br />
<br />
== Wifi ==<br />
<br />
Wifi works on the koolu 7 distribution, but is a bit stubborn, one has to kick it to start, and when the signal is out of reach, it keeps the connection, instead of rescanning for a new access points.<br />
DNS is resolved properly, and the keyboard works in Koolu beta 7 <br />
<br />
Below is a beautiful work around for pre beta 6 versions:<br />
<br />
=== Wifi Pre beta seven ===<br />
<br />
Although wifi works, there are two problems; one, you can't bring up a keyboard to enter your encryption key and two, Android does not obtain the DNS settings properly from the router. Both can be worked around.<br />
<br />
==== Solution one ====<br />
<br />
This involves [http://wiki.openmoko.org/wiki/Android_usage#Copy_and_pasting copying and pasting] the network key into the key field. These instructions use the aKeyUI,beautiful work aroun app but you could do it with the standard Note pad app.<br />
<br />
Install [http://andappstore.com/AndroidPhoneApplications/apps/4642 aKeyUI] this app allows you to enter text and copy it to a clipboard, which you can then paste into any test field:<br />
<br />
Change directory to where you downloaded the app then install:<br />
<br />
# adb install aKeyUI.apk<br />
<br />
Touch the Application tab to display your installed apps, aKeyUI should be one of them. Load it up, enter the key for your wireless network and click copy.<br />
<br />
Now go to 'Settings' > 'Wireless controls' > 'Wi-Fi settings' and you should see your wireless network listed there. Touch it and when it asks you for the key, long-touch the key field and select paste.<br />
<br />
Caveats<br />
* The keyboard seems to have a limited number of characters, making this solution useless if your network key contains one of the missing ones.<br />
<br />
Now you are connected but you need the [http://wiki.openmoko.org/wiki/Android_usage#DNS_Fix DNS fix.]<br />
<br />
==== Solution two ====<br />
<br />
Boot your FreeRunner while connected to USB then run these commands:<br />
<br />
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0<br />
# adb kill-server<br />
# ADBHOST=192.168.0.202 adb devices<br />
<br />
# adb shell mount -o remount,rw /dev/root /<br />
# adb pull /etc/wifi/wpa_supplicant.conf wpa_supplicant.conf<br />
<br />
You will now have the wpa_supplicant.conf file in your working directory, change its ownership so you can edit it (unless you edit it as root):<br />
<br />
# chown YOUR_USER:YOUR_GROUP wpa_supplicant.conf <br />
<br />
Now you can edit it to contain your wireless details, then push it back to the FreeRunner. For example add an uncommented section like this:<br />
<br />
network={<br />
ssid="example"<br />
proto=WPA<br />
key_mgmt=WPA-PSK<br />
pairwise=CCMP TKIP<br />
group=CCMP TKIP WEP104 WEP40<br />
psk=06b4be19da289f475aa46a33cb793029d4ab3db7a23ee92382eb0106c72ac7bb<br />
priority=2<br />
}<br />
<br />
Save your changes, change the owner back to root and push it back to the FreeRunner:<br />
<br />
# chown root:root wpa_supplicant.conf<br />
# adb push wpa_supplicant.conf /etc/wifi<br />
<br />
Reboot the FreeRunner:<br />
<br />
# adb shell sync<br />
# adb shell reboot<br />
<br />
If you've changed the wpa_supplicant.conf file, it will need to be deleted in /data/misc/wifi/wpa_supplicant.conf<br />
<br />
You now just need the DNS fix<br />
<br />
==== DNS Fix ====<br />
<br />
Connect to Android using adb and pull your init.rc:<br />
<br />
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0<br />
# adb kill-server<br />
# ADBHOST=192.168.0.202 adb devices<br />
# adb pull /init.rc init.rc<br />
<br />
# chown YOUR_USER:YOUR_GROUP init.rc<br />
<br />
Now find this part of your your init.rc, and add new lines containing the DNS value to the [https://www.opendns.com/ OpenDNS] servers:<br />
<br />
# Setup the DNS server for USB<br />
#setprop net.dns1 192.168.0.200<br />
setprop net.dns1 208.67.222.222<br />
setprop net.dns2 208.67.220.220<br />
<br />
Change the ownership back to root and push it back to your FreeRunner:<br />
<br />
# chown root:root init.rc<br />
# adb shell mount -o remount,rw /dev/root /<br />
# adb push init.rc /init.rc<br />
# adb shell sync<br />
# adb shell reboot<br />
<br />
= Applications =<br />
<br />
=== Alarm ===<br />
Works.<br />
<br />
<br />
== Contacts ==<br />
<br />
=== Importing ===<br />
==== From Vcard ====<br />
# [[#Install new software|install]] [http://www.dusystems.com/importContacts.html "Android Contacts Import"] (this application is also available from [[#AndAppStore|AndAppStore]])<br />
# export your contact(s) as a vcard file from your contact application<br />
# [[#Copy files|copy]] the file to your phone /sdcard/ directory<br />
# on your phone run the ImportContacts application, choose the file you copied and select import. Wait until the phone says x vcards imported<br />
<br />
That's it if you don't see your contacts, make sure you selected "view all contacts" in the contacts application options (contacts > power button > Display group > All contacts)<br />
<br />
It imports only names and telephone numbers, everything else is not imported.<br />
<br />
==== From SIM ====<br />
Works, Contacts->menu->Settings->SIM contacts importer.<br />
<br />
=== Synchronization ===<br />
<br />
== Calendar ==<br />
<br />
=== Importing ===<br />
<br />
=== Synchronization ===<br />
<br />
== Files ==<br />
<br />
=== Copying ===<br />
You can copy files to your phone using either <br />
* [[#USB mass storage|USB mass storage]]<br />
<br />
This option is not (yet) available in Koolu beta 7 <br />
<br />
or, from the command line using<br />
<br />
* the [[Android debug bridge]] to copy files to your phone :<br />
ADBHOST=192.168.0.202 ./adb push file.txt /sdcard/<br />
<br />
== Media ==<br />
Can play OGG audio files and view pictures with the default applications<br />
<br />
= Others =<br />
<br />
<br />
<br />
== Suspend ==<br />
Waking up your phone might be a little bit tricky at the moment, there are several recipe/hints submitted by different people :<br />
* 1-2s press of power button goes to sleep, wake up with long power button press, don't use screen timeouts, disable it in Settings->Sound & display->Screen timeout->Never timeout.<br />
* Michael Trimarchi's images allow resume from suspend after two short presses. However, sometimes it takes a few tries for the phone to wake up.<br />
* For me resume works best if i long press power until the main screen appears and the short power press that unlocks screen.<br />
* During suspend the phone seems to wake up make an audible click and go back to sleep.<br />
<br />
==USB==<br />
=== USB networking ===<br />
The general [[USB Networking]] guide should help you talk to your FreeRunner using IP over USB. However, please note that Android doesn't come with an ssh server installed by default. In order to gain shell access without an additional ssh server you can follow the instructions on the [[Android debug bridge]] page.<br />
<br />
=== USB Host mode ===<br />
* [http://code.google.com/p/android-on-freerunner/downloads/list http://code.google.com/p/android-on-freerunner/downloads/list] Build Version 0.1.1<br />
<pre><br />
echo 1 > /sys/class/i2c-adapter/i2c-0/0-0073/neo1973-pm-host.0/hostmode<br />
echo host > /sys/devices/platform/s3c-ohci/usb_mode<br />
</pre><br />
<br />
{{todo|If you know how to change the USB mode with Android, please explain it here.}}<br />
<br />
=== USB keyboard ===<br />
I bought a mini USB keyboard that for my Neo, if someone has simple directions to use it with android, please explain it here.<br />
<br />
=== USB mass storage ===<br />
This setting is named "Enable USB mass storage". If you don't find it on Settings -> SD card & phone storage, you have to unhide it with [http://www.4shared.com/account/file/76203324/508fa871/Anycut.html Anycut]. Install it then make a new shortcut Activity -> SD Card. Use this new shortcut to activate the option. This is not persistent after a reboot. See also [http://rivviepop.wordpress.com/2008/11/19/mount-your-g1-android-sd-card-automatically-rc29-rc30/]<br />
<br />
{{todo|This doesn't seem to work with the Neo FreeRunner and current Android images.}}<br />
<br />
= Software installation and updates =<br />
For initial Android flashing, take a look at: [[Android on Freerunner]]<br />
<br />
== Install new software ==<br />
=== Manual install ===<br />
Applications are packaged in .apk packages, to install a package (downloaded on your computer) do <br />
<br />
./adb install app.apk<br />
<br />
After making sure you can talk to your phone using the [[Android debug bridge]]<br />
<br />
=== Package managers ===<br />
==== Android Market Place ====<br />
Currently it is not possible to use the Android Market Place with the Neo Freerunner.<br />
<br />
==== AndAppStore ====<br />
AndAppStore is an alternate source for Android software and works on the Neo Freerunner. It is installed by default in current Koolu images but you can [[#Manual install|install manually]] their [http://andappstore.com/AndroidPhoneApplications/apps/7661 client].<br />
<br />
=== Update software (without reflashing) ===<br />
<br />
= Troubleshooting =<br />
<br />
== Android Debug Bridge ==<br />
<br />
To assist in debugging and to gain shell access to the phone with Android, you can use the instructions found here: [[Android debug bridge]]<br />
<br />
== SD Card unavailable ==<br />
<br />
<br />
Type in the the Android Terminal emulator (under Development Tools)<br />
<br />
setprop EXTERNAL_STORAGE_STATE mounted<br />
<br />
or run <br />
<br />
adb shell setprop EXTERNAL_STORAGE_STATE mounted <br />
<br />
with the freerunner connected to a computer which has the Android SDK.<br />
<br />
= Links =<br />
<br />
[[Category:Android]]</div>Dareushttp://openmoko.org/wiki/Talk:AndroidTalk:Android2010-01-16T11:27:29Z<p>Dareus: /* Suspend */</p>
<hr />
<div>== Redirect? ==<br />
<br />
Q: Shouldn't this page be removed and just redirected to [[Android on Freerunner]]? Or am I missing something? --[[User:JohnSullivan|JohnSullivan]] 16:51, 26 January 2009 (UTC)<br />
<br />
A: I refactored thos pages and separated the content between installation ([[Android on Freerunner]]), development ([[Android porting]]) and usage ([[Android usage]]). I think it's more clear than before where there was duplicate content and content for different audiances mixed. --[[User:Jernst|jernst]] 17:09, 26 January 2009 (UTC)<br />
<br />
Can we rename the [[Android on Freerunner]] page then? The name doesn't say anything about installation... How about, [[Android Installation]], if that's what you are aiming for. There's plenty of info on that page that isn't directly related to installation, and now that I'm actually playing with Android I'm finding the separation confusing.--[[User:JohnSullivan|JohnSullivan]] 18:20, 16 May 2009 (UTC)<br />
<br />
== Scanning for Files That Use the ARMv5TE ISA ==<br />
<br />
"exit -1" does not work with every /bin/sh. Anyway, if you want to give a hint, make it look like this:<br />
<pre><br />
if [ $# -ne 1 ]; then<br />
echo "usage: $0 android-directoy"<br />
exit 255<br />
fi<br />
</pre><br />
<br />
== New Images (10th November) ==<br />
<br />
Sean uploaded new Images today (10th November), but I can't find a changelog :-(<br />
<br />
== Android compared to OpenMoko OS? ==<br />
<br />
As a layman (ie. non-Hacker) I would personally love to see an indepth comparison between the Android OS and the OpenMoko OS, from the point of view of the user / consumer, as of the moment.<br />
<br />
In other words, I would love to see (for example) what I would be getting if I installed Android on the Freerunner, ''feature-wise'', as opposed to keeping the already installed OS. I think I would ''also'' be interested if it would be a good idea, ''feature-wise'', to ditch the T-Mobile G1's (aka. HTC Dream's) native Android installation for OpenMoko OS.<br />
<br />
You know, just to get the competitive spirit going ;)<br />
<br />
(Btw, right now an unlocked HTC Dream and a Freeruner both cost US$399...) --[[User:Lemi4|Lemi4]] 01:22, 18 February 2009 (UTC)<br />
<br />
== Running speed? ==<br />
<br />
Does Android really run this slow or is my Freerunner in bad shape? There is a half second delay between clicking and anything happening on screen. The API finger-painting demo is also laughably slow. On the other hand, the SurfaceView Overlay runs at (what I consider) a reasonable speed for the hardware.<br />
<br />
==Suspend==<br />
<br />
I have the latest Panicking image, with that my FR goes into suspend mode even if plugged-in and when I click the power button to wake it up, it appears immediately the unlock screen in which you have to enter your unlock movement.<br />
<br />
It's like power was pressed two times at once: one for waking up and the other to show the unlock screen.<br />
<br />
It's quite annoying because you can't see the charging percentage when you wake it up or other notifications because you immediately go further than that screen.<br />
<br />
It's just my problem?<br />
<br />
[[User:Dareus|Dareus]] - 2010-01-16-T-11:27</div>Dareushttp://openmoko.org/wiki/Talk:AndroidTalk:Android2010-01-16T11:27:07Z<p>Dareus: </p>
<hr />
<div>== Redirect? ==<br />
<br />
Q: Shouldn't this page be removed and just redirected to [[Android on Freerunner]]? Or am I missing something? --[[User:JohnSullivan|JohnSullivan]] 16:51, 26 January 2009 (UTC)<br />
<br />
A: I refactored thos pages and separated the content between installation ([[Android on Freerunner]]), development ([[Android porting]]) and usage ([[Android usage]]). I think it's more clear than before where there was duplicate content and content for different audiances mixed. --[[User:Jernst|jernst]] 17:09, 26 January 2009 (UTC)<br />
<br />
Can we rename the [[Android on Freerunner]] page then? The name doesn't say anything about installation... How about, [[Android Installation]], if that's what you are aiming for. There's plenty of info on that page that isn't directly related to installation, and now that I'm actually playing with Android I'm finding the separation confusing.--[[User:JohnSullivan|JohnSullivan]] 18:20, 16 May 2009 (UTC)<br />
<br />
== Scanning for Files That Use the ARMv5TE ISA ==<br />
<br />
"exit -1" does not work with every /bin/sh. Anyway, if you want to give a hint, make it look like this:<br />
<pre><br />
if [ $# -ne 1 ]; then<br />
echo "usage: $0 android-directoy"<br />
exit 255<br />
fi<br />
</pre><br />
<br />
== New Images (10th November) ==<br />
<br />
Sean uploaded new Images today (10th November), but I can't find a changelog :-(<br />
<br />
== Android compared to OpenMoko OS? ==<br />
<br />
As a layman (ie. non-Hacker) I would personally love to see an indepth comparison between the Android OS and the OpenMoko OS, from the point of view of the user / consumer, as of the moment.<br />
<br />
In other words, I would love to see (for example) what I would be getting if I installed Android on the Freerunner, ''feature-wise'', as opposed to keeping the already installed OS. I think I would ''also'' be interested if it would be a good idea, ''feature-wise'', to ditch the T-Mobile G1's (aka. HTC Dream's) native Android installation for OpenMoko OS.<br />
<br />
You know, just to get the competitive spirit going ;)<br />
<br />
(Btw, right now an unlocked HTC Dream and a Freeruner both cost US$399...) --[[User:Lemi4|Lemi4]] 01:22, 18 February 2009 (UTC)<br />
<br />
== Running speed? ==<br />
<br />
Does Android really run this slow or is my Freerunner in bad shape? There is a half second delay between clicking and anything happening on screen. The API finger-painting demo is also laughably slow. On the other hand, the SurfaceView Overlay runs at (what I consider) a reasonable speed for the hardware.<br />
<br />
==Suspend==<br />
<br />
I have the latest Panicking image, with that my FR goes into suspend mode even if plugged-in and when I click the power button to wake it up, it appears immediately the unlock screen in which you have to enter your unlock movement.<br />
<br />
It's like power was pressed two times at once: one for waking up and the other to show the unlock screen.<br />
<br />
It's quite annoying because you can't see the charging percentage when you wake it up or other notifications because you immediately go further than that screen.<br />
<br />
It's just my problem?<br />
<br />
[[User:Dareus|Dareus]] - 2010-01-16-T-12:27</div>Dareushttp://openmoko.org/wiki/Talk:Automatic_emulation_in_UbuntuTalk:Automatic emulation in Ubuntu2010-01-16T11:20:07Z<p>Dareus: </p>
<hr />
<div>cogito (not realy needed) is gone by hardy<br />
<br />
== Missing 'qemu' target ==<br />
<br />
The Makefile downloaded from http://www.rwhitby.net/files/openmoko/Makefile doesn't contain the "qemu" target, nor does it do anything when just calling "make".<br />
<br />
[[User:Sybren|sybren]] 11:25, 27 June 2009 (UTC)<br />
<br />
== Build failure ==<br />
<br />
On Kubuntu 9.04 "make qemu" fails with:<br />
<br />
make[2]: Leaving directory `/home/sybren/speeltuin/freerunner/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/home/sybren/speeltuin/freerunner/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Trying alternative sources<br />
Kernel is... not found<br />
make: *** [download-images] Error 255<br />
<br />
[[User:Sybren|sybren]] 11:56, 27 June 2009 (UTC)<br />
<br />
== Problems ==<br />
If you have any problems, just add it here<br><br />
--[[User:Twistedclone|Twistedclone]]<br />
<br />
OS: Ubuntu 8.04<br />
I run the following sequence of commands to run my QEMU<br />
<pre><br />
$ svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973<br />
$ cd qemu-neo1973<br />
$ sudo aptitude install gcc-3.4 libsdl1.2-dev lynx netpbm<br />
$ ./configure --target-list=arm-softmmu --cc=/usr/bin/gcc-3.4<br />
$ make<br />
$ openmoko/download.sh<br />
$ openmoko/flash.sh<br />
$ arm-softmmu/qemu-system-arm -M gta01 -m 130 -mtdblock openmoko/openmoko-flash.image -kernel openmoko/openmoko-kernel.bin -usb -show-cursor<br><br />
</pre><br />
Emulator appears with Boot menu.<br/><br />
While Booting it get hanged out with the following errors<br />
<pre><br />
_______________________Errors or Emulator Screen_______________<br />
sc32410-sdi sc32410-sdi : CMD[FAIL(-100)] #2 op:CMD8<br />
error: command timeout<br />
...<br />
...<br />
...<br />
Freeing init memory: 128kb<br />
/bin/sh: can't access tty; Job Control Tunned off<br />
/ #JFFS2 notice: (227) check_node_data: wrong data CRC in data node at 0x00899b4c: read d5ebdb50 calculated 0x880615c2<br />
JFFS2 warning: (227) jffs2_do_read_inode_internal: Truncating into #1111 to 71415<br />
56 bytes failed because it only had 2510848 bytes to start with <br><br />
<br />
_______________Errors on Terminal_______________<br />
qasim@qasim-desktop:~/openmoko/qemu-neo1973$ arm-softmmu/qemu-system-arm -M gta01 -m 130 -mtdblock openmoko/openmoko-flash.image -kernel openmoko/openmoko-kernel.bin -usb -show-cursor<br />
neo_gsm_switch: GSM disabled.<br />
pcf_write: charging in Qualification Mode.<br />
pcf_write: charge voltage 4.20V.<br />
neo_lcd_rst_switch: LCD reset.<br />
jbt6k74_command: Display on.<br />
neo_vib_switch: Buzz, buzz.<br />
neo_vib_switch: Vibrator stopped.<br />
neo_bl_switch: LCD Backlight now on.<br />
s3c_timers_write: Bad register 0x40<br />
neo_bl_intensity: LCD Backlight now at 20/64.<br />
s3c_adc_write: Bad register 0x8<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
s3c_mmci_writew: Bad register 0x38<br />
neo_bl_intensity: LCD Backlight now at 0/64.<br />
_____________________________________________<br />
</pre><br />
Does anyone has any idea how to fix this up?<br />
<br />
<br />
<br />
After issuing the command 'make qemu' in Gutsy, the installation eventually borks with<br />
<pre><br />
make[2]: Leaving directory `/usr/local/src/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/usr/local/src/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Kernel is... not found<br />
make: *** [download-images] Error 255<br />
</pre><br />
[[User:BioGeek|BioGeek]] 02:03, 27 March 2008 (CET)<br />
<br />
Do you still have the problem?<br />
<br />
[[User:Dolfje|Dolfje]] 20:54, 9 April 2008 (CEST)<br />
<br />
I tested this today (uImage-2.6.24+svnr4301-r4251-r5-om-gta01.bin) on '''hardy'''. Qemu doesn't compile with gcc4 you need:<br />
sudo aptitude install gcc-3.4<br />
After the init process started, became the emulation extremely slow. It takes more than 15 minutes<br />
to boot the GUI on 2GHz CPU and you have to klick & hold the mouse several seconds to see<br />
any visual response. It would be great if there was a easy way to get a shell,<br />
i.e. why the serial port (ctrl+shift-3) doesn't have a getty & co attached?<br /><br />
Can anybody confirm this?<br />
--[[User:Captn|Captn]] 12:29, 18 April 2008 (CEST)<br />
<br />
<br />
Hi, just to tell that the ''Install ipkg package'' part is not effective since there is no room to install the .ipk on the QEmu (say ROM image) device.<br />
<br />
Have any idea on how to get over it or to enable the automatic memory allocation on QEmu if allowed?<br />
<br />
--[[User:VdeGrandpré|VdeGrandpré]] 17:37, 12 mai 2008 (EST)<br />
<br />
I have compiled the Qemu source just fine on Ubuntu Hardy, but when the emulator started it showed up with an unusual QT theme. After the nice picture with the two boots there appeared a message line "No network" in the middle of the screen and 4 icons (cellphone, Q, star and lock). The buttons below the icons are unresponsive. They show a change in the background color when I click them with the mouse, but then nothing happens. Even if I press them for several seconds as noted above. Has the Openmoko theme been accidentally replaced by a non-working QT theme or did I configure something wrong on my end?<br />
<br />
Thomas<br />
<br />
--[[User:Xaos|Xaos]] 15:06, July 7th, 2008 (CST)<br />
<br />
Thomas, I got the same thing when I tried. On the #openmoko IRC channel, lindi and I (with help) got this to work:<br />
<br />
1. After building qemu with "make qemu", close the emulator and:<br />
<br />
2. modify the file: build/qemu/openmoko/env as follows (you may need to adjust these values as time goes by for different images):<br />
kernel_wildcard="testing-om-gta01-20081008.uImage.bin"<br />
# rootfs_wildcard="Open?oko-openmoko-*image*-om-gta01.rootfs.jffs2"<br />
rootfs_wildcard="testing-om-gta01-20081008.rootfs.jffs2"<br />
uboot_wildcard="gta01bv4-u-boot.bin"<br />
#download_dir="http://buildhost.openmoko.org/distro/unstable/Neo1973/deploy/glibc/images/neo1973/"<br />
download_dir="http://downloads.openmoko.org/distro/"<br />
<br />
3. Download the above .jffs2 file (build the URL with the download_dir and the rootfs_wildcard values) to images/openmoko/<br />
<br />
4. run "make flash-qemu-official"<br />
<br />
5. run "make run-qemu-snapshot" or "make run-qemu"<br />
<br />
<br />
--[[User:Schafdog|schafdog]] 15:10, July 1th 2008 (CST)<br />
<br />
Built succesfully on a Fedora Linux 9. Trying to run on the linux box but with the XServer on OS X. It doesn't react to any keypress. Now tried it locally. The keypress works, but stil having some issues to get openmoko up.<br />
<br />
<br />
<br />
Ubuntu 8.04 Hardy Heron, it was also necessary to "apt-get install libgnutls-dev".<br />
--[[User:Newkirk|Newkirk]] 20:37, 20 July 2008 (UTC)<br />
<br />
When I try to download .jffs2 file, it's write "404. File is not found"<br />
<br />
This is not look like as Openmoko on screens:<br />
<br />
[[Image:Openmoko2.png|thumb|Wrong image?|left]]<br />
<br style="clear:both"/><br />
[[User:Robotex|Robotex]] 02:43, 7 August 2008 (UTC)<br />
<br />
<br />
--[[User:David]] 12:57, 28 August 2008<br />
I have problems with the step no. 3:<br />
3. Download the above .jffs2 file (build the URL with the download_dir and the rootfs_wildcard values) to images/openmoko/<br />
the webpages:<br />
-http://downloads.openmoko.org/distro/releases/<br />
-[http://buildhost.openmoko.org/daily/]<br />
doesn't exist anymore..<br />
<br />
ditto, still. can I just make all or sumpin and make it locally from source?<br />
<br />
<br />
--[[User:Wolfsolver]]<br />
Hi all,<br />
I found the file on http://buildhost.automated.it/OM2007.2/, so use following lines in file build/qemu/openmoko/env<br />
rootfs_wildcard="Openmoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080721-om-gta01.rootfs.jffs2"<br />
download_dir="http://buildhost.automated.it/OM2007.2/"<br />
and all works....<br />
<br />
<br />
--[[User:Joe]]<br />
Allso tried to run the makefile. After fixing the problem with the download_dir (by setting it to http://downloads.openmoko.org/distro/testing/) and removing the _dev parameter from the calls to "most_recent" and "download" methods the make script finishes successfully.<br />
However, there seems to be no working kernel installed on the nand. Every time I select boot from the menu, it says <br />
<pre><br />
## Booting kernel from Legacy Image at 30100000 ...<br />
Image Name: openmoko/2.6.28-oe1+gitr34240a1c<br />
Created: 2009-02-08 19:37:42 UTC<br />
Image Type: ARM Linux Kernel Image (uncompressed)<br />
Data Size: 1980124 Bytes = 1.9 MB<br />
Load Address: 30008000<br />
Entry Point: 30008000<br />
Verifying Checksum ... OK<br />
Loading Kernel Image ... OK<br />
OK<br />
ERROR: image overwritten - must RESET the board to recover.<br />
</pre><br />
before it reboots my virtual phone.<br />
I also tried to nand write.e different kernel images. None of them worked. Any help apprechiated.<br />
-- 14:51, 21 February 2009 (UTC)<br />
<br />
--[[User:bimo]] 15 April 2009<br />
I have similar problem with Twistedclone, after I run "make qemu"<br />
<br />
<pre><br />
make[2]: Leaving directory `/home/bhe/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/home/bhe/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Trying alternative sources<br />
Kernel is... not found<br />
make: *** [download-images] Error 255<br />
</pre><br />
<br />
Does anyone has any idea how to fix this up?<br />
FYI, I'm running Ubuntu 8.10 as a guest OS on my virtualbox, Mac OS X as the host.<br />
<br />
--[[User:Hackedd]] 15 June 2009<br />
I have excactly the same problem as bimo reported 15 April 2009, except I'm running Ubuntu directly, not in a VM.<br />
Any thoughts on how to fix this?<br />
<br />
--[[User:bjneuman]] 1 July 2009 Problem still exists. Ubuntu 9.04<br />
<br />
<pre><br />
make[2]: Leaving directory `/home/ben/projects/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/home/ben/projects/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Trying alternative sources<br />
Kernel is... not found<br />
make: *** [download-images] Error 255<br />
</pre><br />
<br />
--[[User:sriranjan]] 6 July 2009 Problem still exists. Ubuntu 8.10<br />
<br />
<pre><br />
make[2]: Leaving directory `/home/ben/projects/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/home/ben/projects/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Trying alternative sources<br />
Kernel is... not found<br />
make: *** [download-images] Error 255<br />
</pre><br />
<br />
Could some one please suggest how to solve this?<br />
<br />
--[[User:Yewang|Yewang]] 13:09, 21 July 2009 (UTC) I'm having the same problem as the above four users. Is it because the online resource that is trying to download is not available any more?<br />
<pre><br />
make[2]: Leaving directory `/home/ye21867/openmoko/build/qemu/arm-softmmu' <br />
make[1]: Leaving directory `/home/ye21867/openmoko/build/qemu' <br />
[ -e images/openmoko ] || mkdir -p images/openmoko <br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env <br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh ) <br />
Retrieving available builds list... <br />
Trying alternative sources <br />
Kernel is... not found <br />
make: *** [download-images] Error 255 <br />
</pre><br />
<br />
--[[User:Roelant]] 17:52, 28 July 2009 (UTC) I' m having the same problems as many more of you. It is again the error that is posted by Yewang.<br />
<br />
<pre><br />
make[2]: Leaving directory `/home/roelant/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/home/roelant/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Trying alternative sources<br />
Kernel is... not found<br />
make: *** [download-images] Error 255<br />
</pre><br />
<br />
-- [[User:Oringo]] Thu Jul 30 20:51:54 UTC 2009 For all users that get the [download-images] Errors. This is what you have to do. Edit build/qemu/openmoko/env (it's a symbolic link to the svn trunk's env file), and change these lines to look like the following:<br />
<br />
<pre><br />
kernel_wildcard="uImage-*-om-gta01.bin"<br />
rootfs_wildcard="*-om-gta01.rootfs.jffs2"<br />
uboot_wildcard="u-boot-gta01bv4-*.bin"<br />
</pre><br />
<br />
<br />
--[[User:Mohamed|Mohamed]] 19:57, 23 October 2009 (UTC)<nowiki>After booting the qemu emulator need username and password how can I fix that? </nowiki><br />
<br />
<br />
<br />
<br />
[[Category:Emulation]]<br />
<br />
<br />
--[[User:Ma7moud0000|Ma7moud0000]] 20:04, 23 October 2009 (UTC)<br />
Hi all I have a problem with this : After " make qemu " appear error ;<br />
<pre><br />
( cd build/qemu && arm-softmmu/qemu-system-arm \<br />
-M gta01 -m 130 -usb -show-cursor \<br />
-usbdevice keyboard \<br />
-mtdblock openmoko/openmoko-flash.image \<br />
-sd openmoko/openmoko-sd.image \<br />
-kernel openmoko/openmoko-kernel.bin )<br />
/bin/sh: line 1: arm-softmmu/qemu-system-arm: No such file or directory<br />
make: *** [run-qemu] Error 127</div>Dareushttp://openmoko.org/wiki/Automatic_emulation_in_UbuntuAutomatic emulation in Ubuntu2010-01-16T11:19:50Z<p>Dareus: move section /* Problems */ to talk page</p>
<hr />
<div>{{Languages|Automatic emulation in Ubuntu}}<br />
[[Image:Qemu-ubuntu1.png|thumb|emulation of Openmoko running on Ubuntu]]<br />
<br />
This is a tutorial for getting an emulation environment on an Ubuntu system.<br />
<br />
== Installation ==<br />
<br />
You have to know that there is a great tool to get it running on a linux system, namely the [[MokoMakefile]]. This is a sort of wrapper round several instructions, so it is easy to set up and maintain a development environment. If you build the whole [[MokoMakefile]], you will need approximately 12GB, a swap+ram memory of about 1GB and minimum 5 hours time. But we will only build it for Qemu (the emulator that I will use) and that needs (on my system) only 890mb and a 15 min of your time.<br />
<br />
To get it running, you will have to tweak your ubuntu a little bit (This will not damage other programs, everything will work as before).<br />
* Configure your sources (System -> Administration -> Software Sources) to include:<br />
** Canonical-supported Open Source software (main)<br />
** Community-maintained Open Source software (universe)<br />
* Open your terminal (Applications -> Accessories -> Terminal).<br />
* Enter following command and select NO when it asks to install dash as /bin/sh (You will have to enter your password)<br />
sudo dpkg-reconfigure dash<br />
* Install the needed programs on Hardy Heron 8.04 (You will have to enter your password):<br />
sudo apt-get install monotone git-core git-svn git-email \<br />
git-cvs git-arch gitk python-dev ccache m4 sed bison make cvs gawk \<br />
libc6-dev g++ subversion sharutils docbook openjade quilt libmpfr-dev \<br />
libpcre3-dev texinfo texi2html libboost-date-time-dev libboost-filesystem-dev \<br />
libboost-regex-dev libboost-test-dev libboost-dev zlib1g-dev build-essential \<br />
dh-make debhelper devscripts gcc-3.4 lynx netpbm libsdl1.2-dev dosfstools \<br />
help2man python-psyco lynx<br />
<br />
* Looks like for 8.10 libgnutls-dev also needs to be added, when you see vnc compile errors. sudo apt-get install libgnutls-dev<br />
<br />
* For older versions (git-svn git-email git-cvs git-arch gitk are replaced by cogito)<br />
sudo apt-get install monotone git-core cogito python-dev ccache m4 sed bison \<br />
make cvs gawk libc6-dev g++ subversion sharutils docbook openjade quilt \<br />
libmpfr-dev libpcre3-dev texinfo texi2html libboost-date-time-dev \<br />
libboost-filesystem-dev libboost-regex-dev libboost-test-dev libboost-dev \<br />
zlib1g-dev build-essential dh-make debhelper devscripts gcc-3.4 netpbm \<br />
libsdl1.2-dev dosfstools help2man python-psyco lynx<br />
<br />
<br />
Voila your system is ready to get the install Openmoko.<br />
<br />
Now we will install Openmoko in a directory by downloading the MokoMakefile in it and build it.<br />
* Create a directory and go into the directory:<br />
mkdir openmoko<br />
cd openmoko<br />
* Get the MokoMakefile (Currently down due to fires in California. Use the link below instead):<br />
wget http://www.rwhitby.net/files/openmoko/Makefile<br />
<br />
If that doesn't work, try<br />
<br />
wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile<br />
<br />
* Make the MokoMakefile and tell it, you want to install it for qemu:<br />
make qemu<br />
<br />
This will download the necessary files of the latest release and build them following the MokoMakefile. After that it will start into the emulator for the first time. Voila you have now successfully installed openmoko onto your ubuntu system.<br />
<br />
===Creating a menu item for Openmoko (optional)===<br />
<br />
You can create a menu item for starting Openmoko by doing the following:<br />
<br />
*Open the terminal (Applications->Accessories->Terminal)<br />
<br />
*Go to the openmoko directory:<br />
<br />
cd ~/openmoko<br />
<br />
*open the file moko.sh with '''gedit''':<br />
<br />
gedit moko.sh<br />
<br />
*insert the following text into the file:<br />
<br />
#!/bin/bash<br />
cd ~/openmoko<br />
make run-qemu<br />
<br />
*Press "save" and close gedit<br />
<br />
*then run the following commands:<br />
chmod +x moko.sh<br />
alacarte<br />
<br />
*and add a menu item with these values:<br />
**Name: Openmoko<br />
**Command: ~/openmoko/moko.sh<br />
<br />
**If you want to you can add an appropriate icon by clicking on the image on the top left. You can download some useful images here:<br />
***[http://wiki.openmoko.org/wiki/Artwork Artwork in the Openmoko wiki]<br />
***[http://openclipart.org/media/tags/openmoko Openmoko at the Open Clip Art Library]<br />
<br />
==Help with running Openmoko in Qemu==<br />
<br />
If you have created a menu item you can start Openmoko through the applications menu of Ubuntu. If you have not, you can start it by:<br />
<br />
* Open your terminal (Applications->Accessories->Terminal).<br />
* Go to the directory:<br />
cd openmoko<br />
* starting with the MokoMakefile<br />
make run-qemu<br />
<br />
The first screen of Openmoko will show a nice picture of the Openmoko logo which will be followed<br />
almost immediately by the BOOT MENU, this is done by the bootloader.<br />
<br />
In the BOOT MENU you can choose different options. To select an option you have to press enter (=aux) and to execute it, hit space (=power). The default selection will boot Openmoko.<br />
Thus if the BOOT MENU shows, you just have to hit the space bar and the phone software will load.<br />
<br />
While booting Openmoko the progress will be shown in text mode. Depending on your computer's performance it might take a while (some minutes even) to complete the boot. When complete you will see the graphical interface as will be shown on the phone itself (but slightly larger due to the larger pixelsize of your screen).<br />
<br />
A few pointers on using Openmoko:<br />
* You can select the icon that looks like "+" for a list of applications you can run.<br />
* You can select the icon that looks like "three gears" for a list of applications that are running now. Here you can also terminate unwanted applications when you are unable to do so from within the application itself.<br />
* You can select the icon that looks like a "house" to get back to the first home screen.<br />
* The statusbar at the top is always shown and by clicking on the top-left corner you can switch to another application that is already running. The "Home" application is always running and clicking on it will bring you back to the home screen.<br />
<br />
See [[Qemu]] for more advanced information on running Openmoko in Qemu.<br />
<br />
==Installing ipk packages==<br />
First you need a xxx.ipk package, see [[toolchain]] on how to compile an application for the ARM CPU and create the package.<br />
<br />
Note that if at this point you have the Openmoko Qemu running, it is probably wise to terminate it first.<br />
Then you can install the xxx.ipk package for access by the Qemu emulator with:<br />
<br />
cd openmoko<br />
mkdir -p build/tmp/deploy/glibc/ipk/a<br />
cp xxx.ipk build/tmp/deploy/glibc/ipk/a/xxx_a.ipk<br />
make qemu-copy-package-xxx<br />
<br />
''Note: for some reason qemu-copy-package-xxx looks for above source file.<br />
Maybe this part can be improved, or a different command can overcome the problem of creating this directory.''<br />
<br />
When above make command was succesful the next time you start Openmoko Qemu,<br />
you still need to make the installed application available in the application list.<br />
For this you can select from within Openmoko the terminal application<br />
(Select icon that looks like "+" for the list of available applicaitons, select "Applications" and select the "Terminal").<br />
In this terminal double-click, so you can type in the commands:<br />
opkg install /media/mmcblk0/xxx_a.ipk<br />
exit<br />
After the "exit" command you should return to the Task list, in which the newly<br />
added application should be listed under a name which was choosen when building the ipk package.<br />
<br />
== Updating Openmoko==<br />
* Open your terminal (Applications->Accessories->Terminal).<br />
* Go to the directory:<br />
cd openmoko<br />
* Update with the MokoMakefile<br />
make qemu<br />
<br />
== Configurations/OS ==<br />
<br />
=== OS X/Kubuntu ===<br />
<br />
I'm running the Neo-Qemu in the Qtopia-Image in VMWare Fusion on a MacBook Pro (2x2.6GHz, 4GB), so it's an emulator in an emulator. Speed is acceptable. Be sure to look at the end of this page for the right filesystem image to flash. A main point in compiling Neo-Qemu is the gcc 3.x. For some reason it did not install on my Mac, but I think I can live with the emu-in-emu solution for a while.<br />
<br />
--[[User:Cweise|moerkby]] 11:00, 9 October 2008 (UTC)<br />
<br />
<br />
=== Ubuntu Karmic (9.10) with gcc 4.4.1 ===<br />
Thanks for this page, I could bring up qemu on Ubuntu. I had to do the following changes however:<br />
* Apply the qemu-cvs.patch from http://bugs.gentoo.org/show_bug.cgi?id=160627 on qemu-neo1973 dir (in openmoko/trunk/src/host)<br />
* Remove the check for GCC 3.x in the moko makefile (i.e, add --disable-gcc-check as suggested)<br />
* The values of wildcards in openmoko/trunk/src/host/qemu-neo1973/openmoko/env didn't work for me, I changed the following variables:<br />
<pre><br />
##; kernel_wildcard="testing-om-gta01-*.uImage.bin"<br />
##; rootfs_wildcard="testing-om-gta01-*.rootfs.jffs2"<br />
##; uboot_wildcard="gta01bv4-u-boot.bin"<br />
<br />
kernel_wildcard="uImage-2.6.24+git20080424-r0-om-gta01.bin"<br />
rootfs_wildcard="Openmoko-scaredycat-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080710-om-gta01.rootfs.jffs2"<br />
uboot_wildcard="u-boot-gta01bv3-1.3.1+svnr4297+gitb29661fc1151077776454288051bc9a488351ce8-r3.bin"<br />
</pre><br />
<br />
I got the values by manually browsing the site: http://buildhost.automated.it/OM2007.2 and choosing the seemingly recent ones..<br />
<br />
--[[User:Karthickgururaj|Karthickgururaj]] 13:55, 15 January 2010 (UTC)</div>Dareushttp://openmoko.org/wiki/Main_PageMain Page2010-01-12T17:14:03Z<p>Dareus: </p>
<hr />
<div>{{Languages|Main Page}}<br />
__NOTOC__<br />
__NOEDITSECTION__[[Image:Neo front 3.gif|right]]<br />
<div style="padding: 2.5ex; text-align: center; font: bold x-large sans">Openmoko™ - Open. Mobile. Free.</div><br />
<br />
'''Openmoko™''' is a project dedicated to delivering mobile phones with an [[Source Code|open source software stack]]. Openmoko is currently selling the [[Neo FreeRunner]] phone to advanced users and will start selling it to the general public as soon as the software is more developed.<br />
<br />
* [[Introduction]]<br />
* [[Why Openmoko|Why Openmoko?]]<br />
<br />
[[More informations]]<br />
<br />
===Get Involved===<br />
Openmoko is a project driven by a community of passionate and intelligent volunteers. If you have the ability, please contribute to our cause. Openmoko's ambitions far exceed the resources available. <br />
<br />
* [[Community Resources|Community Portal]]<br />
* [[Gta02-core|Create a new hardware revision of the gta02 hardware]]<br />
* [[Create User Manuals]] for [[Distributions]] and [[Applications]]<br />
* Enhance the multi-device multi-vendor [http://www.freesmartphone.org FSO] middleware used as [[OpenmokoFramework]].<br />
===How To Purchase===<br />
The Neo FreeRunner is sold by various [[distributors]] around the world.<br />
<br />
See [[Getting Openmoko]] for more information.<br />
<br />
----<br />
<br />
====Latest News====<br />
<br />
{{News}}<br />
[[News Archive|more news...]]<br />
<br />
----</div>Dareushttp://openmoko.org/wiki/DistributionsDistributions2010-01-08T17:19:52Z<p>Dareus: /* See also */ SPAM delete</p>
<hr />
<div>{{Languages|Distributions}}<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
{| class="wikitable" style="float:left;width:200px;background-color:#FF6600;text-align:center;border-collapse:collapse;font-weight:bold"<br />
|<font color=white>Distributions</font><br />
|-<br />
! style='background-color:#333333;color:#FFFFFF'|<br />
<div align=left><br />
* <font color='#BBBBBB'>Openmoko (official)</font><br />
** [[Om 2009]]<br />
** [[Om 2008]]<br />
** [[Om 2007.2]]<br />
* <font color='#BBBBBB'>Om Community</font><br />
** [[Android]]<br />
** [[Debian]]<br />
** [[Gentoo]]<br />
** [[Hackable:1]]<br />
** [[Mer]]<br />
** [[Neovento]]<br />
** [[OpenWrt]]<br />
** [[Qt Extended Improved]]<br />
** [[SHR]]<br />
</div><br />
|-<br />
|}<br />
== About distributions ==<br />
Openmoko distributions are designed to run on various mobile devices, with the primary aim of supporting Openmoko Inc.'s [[GTA01:Neo 1973|Neo 1973]] and [[Neo FreeRunner]] phones. They are GNU/Linux distributions -- complete operating systems including user applications. You can install any of them on your phone or even have a dualboot system with two distributions installed. For downloads see [[Download]], for installation instructions see [[Flashing the Neo FreeRunner]].<br />
<br />
Besides, Openmoko distributions also run on [[Supported devices|other]] mobile devices and some other software distributions also run on the phones of Openmoko Inc.<br />
<br />
=== Choosing a distribution ===<br />
<br />
According to a survey from August 2009 [[SHR]] is by far the most used distribution (60%), followed by Om (15%, [[Om 2007]], [[Om 2008]] and [[Om 2009]] counted as one distribution), [[Debian]] (6%), the Debian-based [[Hackable:1]] (6%), [[Qt Extended Improved]] (5%) and [[Android]] (4%).[http://doodle.com/sd2c8d8snr23eeqq] As the development of Om 2009 basically stopped after this poll even more people might switch to [[SHR]].<br />
<br />
=== Please note ===<br />
<br />
* Stable in the FreeRunner world does not mean the same thing as stable in the Debian world.<br />
* Most distributions use the same bootloader, kernel, drivers and hardware. Therefore, the same low level bugs are commonly found in all distributions. The latest and greatest software usually has most bug fixes, plus a whole set of new fresh bugs.<br />
* Most of these distributions also have package repositories. It is a BAD idea to feed from another distribution's repository. E.g. see [[installing alien package]]s.<br />
* Upgrade path between these distributions are mostly not tested, thus updating by changing the feeds will most likely end in broken packages or even an unbootable system. It is advisable to reflash the whole filesystem with [[dfu-util]] to switch between the different distributions, with the reminder that a dual-boot setup (e.g. via [[Booting from SD|MicroSD]] or [[Booting from NFS|NFS]]) can be used.<br />
* [[Marketing Mistakes]] and pre-installed distributions.<br />
<br />
<br />
== Overview ==<br />
<br />
=== Android ===<br />
{{Template:Works on Android}}<br />
[http://code.google.com/android/ Android] is a software stack for mobile devices developed by the [http://www.openhandsetalliance.com/ The Open Handset Alliance.] Openmoko is fully supporting Android running on the Freerunner.<br />
<br />
Android has now reached a point where it is usable on the FreeRunner as an everyday phone, there are, however, still some caveats. Check out the main Android section of the wiki for more info.<br />
<br />
{{Main|Android}}You can also visit the user web page for [http://wiki.openmoko.org/wiki/User:Seanmcneil3 Sean McNeil] for some more info.<br />
<br />
=== Debian ===<br />
{{Template:Works on Debian}}<br />
[[Debian]] is "the universal operating system". It comes with thousands and thousands of packages (most of them designed for desktops or servers so far). So in the words of Joachim "nomeata" Breitner from the [http://wiki.debian.org/Teams/DebianFSO pkg-fso] team, this is not really a distribution in the Openmoko sense of the word, but rather a different underlying system for Openmoko distributions. At the moment, we ship the software from the FSO stack, but hopefully we’ll also have, for example, the SHR software in our archive. So for now, Debian is a different way of installing FSO, which takes more space and provides more programs :-)<br />
<br />
{{Main|Debian}}<br />
<br />
=== Gentoo ===<br />
{{Template:Works on Gentoo}}<br />
[[Gentoo]] is all about choices. When installing Gentoo, this is made clear to you several times -- you can choose how much you want to compile yourself, how to install Gentoo, what system logger you want, etc. Gentoo is a fast, modern metadistribution with a clean and flexible design. Gentoo is built around free software and doesn't hide from its users what is beneath the hood. Portage, the package maintenance system which Gentoo uses, is written in Python, meaning you can easily view and modify the source code. Gentoo's packaging system uses source code (although support for precompiled packages is included too) and configuring Gentoo happens through regular textfiles. In other words, openness everywhere.<br />
<br />
{{Main|Gentoo}}<br />
<br />
=== Hackable:1 ===<br />
{{Template:Works on Hackable:1}}<br />
Hackable1 is a community distribution for hackable devices like the Neo Freerunner. It is based on Debian and 2007.2 userland which has been abandoned by Openmoko. It follows the GNOME mobile platform. <br />
{{Main|Hackable:1}}<br />
<br style="clear: both"><br />
=== Mer ===<br />
{{Template:Works on Mer}}<br />
[[Mer]] is a distribution based on [[Maemo]].<br />
<br style="clear: both"><br />
=== Mokotouch ===<br />
{{Template:Works on Mokotouch}}<br />
[[MokoTouch]] wants to be a replacement for the OM Distribution. It will contain apps for system settings and other useful apps like, mail client, Photo and Maps Viewer and maybe other fun things. It's fully written in C++ using Qt 4.5 Embedded. and it runs using Framebuffer, so no X11 Required. http://th30z.netsons.org/mokotouch/index.html <br />
<br />
[http://www.youtube.com/watch?v=yr821OgnvYc Video]<br />
<br style="clear: both"><br />
=== neovento ===<br />
{{Template:Works on noevento}}<br />
[[neovento]] (ex FYP) is a [[Debian|Debian on Freerunner]] based [[Distributions|distribution]] which uses [http://lxde.org/ LXDE] and [[Zhone]] on top. It is a [http://freeyourphone.de FreeYourPhone.de] community project. <br />
<br />
{{Main|neovento}}<br />
<br style="clear: both"><br />
<br />
=== OpenWrt ===<br />
{{Template:Works on OpenWrt}}<br />
[[OpenWrt]] is described as a Linux distribution for embedded devices.<br />
<br />
Instead of trying to create a single, static firmware, [[OpenWrt]] provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developer, [[OpenWrt]] is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.<br />
<br />
[[OpenWrt]] development trunk now supports s3c24xx, CPU used in [[Freerunner]].<br />
<br />
Mainly due to the usage of uClibc instead of glibc as libc implementation, OpenWrt can boot from NAND with enlightenment window manager within 1 minute 7 seconds using u-boot (NOR) bootloader.<br />
<br />
* [http://www.openwrt.org OpenWrt website]<br />
* [http://dev.openwrt.org OpenWrt development site]<br />
<br />
{{Main|OpenWrt}}<br />
<br />
=== Qalee ===<br />
{{Works on Qalee}}<br />
[[Qalee]] is a phone environment developed in Qt4 above the fso stack. It works on the freerunner under any distribution that supports Qt4. It's not finished yet but you can test a preview version with the official Qalee distributon. This release includes no new features, but many fixes for things that didn’t work or were incomplete in 0.0.2. You can read full [http://think-free.homelinux.org/wordpress/ announcement], or take a look at some of changes:<br />
* Qalee is now based on shr instead of debian.<br />
* clock widget now shows a calendar when clicked.<br />
* status panel widget shows gsm network name and power and internet connection status while on wifi or gprs.<br />
* screen menu : you can now choose the background picture with a cover-flow effect, letting the backlight always on now works.<br />
* network menu : all entries work, gsm one is a little buggy though.<br />
* Wifi works despite the the bug in the kernel 2.6.29 opened for 4 month.<br />
* application menu : to launch application just click on it :) when launched the button becomes green, to close it, press the close button which becomes red and click on the application you want to close<br />
* power button supports suspend on short press, or menu on longer press.<br />
* phone application is now litephone modified to use Qalee’s buttons.<br />
* GorshPlayer is broken, if you have Qt4.5.2 librairies with phonon working on shr, tell me (?)//FIXME<br />
* keyboard is still literky.<br />
* Themable interface allows you to change some colours of the interface.<br />
<br>WARNING :<br><br />
Qalee is in pre-alpha stage, a lot of thinks are not coded yet, other are broken, some may be changed. It's just a preview version of the current work!<br />
http://www.qalee.org<br />
<br />
=== Qt Extended Improved ===<br />
Qt Extended has had several names. The current name is <b>Qt Extended Improved</b>. An Openmoko-based community develops Qt Extended Improved as a Free Software project. Qt Extended Improved builds on the foundation of Qt Extended/Qtopia/Qt by Qt Software/Trolltech. Qt Extended Improved provides a robust telephony stack, a webkit based browser and other smartphone features.<br />
<br />
On 5th March 2009 Qt Software released Qt Extended 4.4.3. On 3rd March 2009 Qt Software announced that Qt Extended 4.4.3 would be the last release of the Qt Extended product. Prior to version 4.3, Qt Extended was known as Qtopia.<br />
<br />
{{Main|Qt Extended Improved}}<br />
<br />
{{Template:Works on QtMoko}}<br />
Another branch of development after discontinued Qt Extended is [http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:<br />
* QT Moko has better X support, which is much faster then X4,<br />
* in QT Moko the AUX can bring menu for X application, <br />
* QT Moko includes an X terminal with virtual keyboard and matchbox window manager<br />
* in QT Moko with the X-Server support you can use X application like [http://www.tangogps.org/gps/articles/7-Installation.html#extended TangoGPS] as GPS application.<br />
<br />
{{Main|QT Moko}}<br />
<br />
=== SHR ===<br />
{{Template:Works on SHR}}<br />
SHR is a community driven distribution. It contains some basic EFL based applications which make use of the FSO. There currently is an [[EFL_Documentation|EFL]] (with elementary) dialer, messages and contacts application programmed in C, as well as a nice Settings-GUI in Python. As of April 12th, 2009, there is no stable release of this distribution yet, as the SHR team doesn't feel it to be good enough. You can find images though on the [http://shr.bearstech.com/shr-testing SHR buildhost].<br />
<br />
{{Main|SHR}}<br />
<br />
=== Slackware ===<br />
{{Template:Works on Slackware}}<br />
As of release 12.2, Slackware is now officially supported on the Neo Freerunner<br />
[http://armedslack.org/]<br />
--[[User:Djdas|djdas]] 15:54, 13 June 2009 (UTC)There aren't any confirmations of ArmedSlack running on Freerunner either on the website or the official ML, do you have any link pointing on that?<br />
<br style="clear: both"><br />
=== Abandoned ===<br />
<br />
==== FDOM (FAT and Dirty Openmoko) ====<br />
{{Template:Works on FDOM}}<br />
[[FDOM]] was a distribution based on [[Om 2008]], updated with many ready-to-use applications and with fixes posted in the mailing lists. <br />
<br />
{{Main|FDOM}}<br />
<br style="clear: both"><br />
<br />
==== Om series ====<br />
* '''[[Om 2009]]''' was intended to be the new distro; it is not a simple follow-on from [[Om 2008]]. It is based on the [http://freesmartphone.org freesmartphone.org] milestone 5.5 framework. Development of Om 2009 was ended and developers moved on to work on other distros instead.<br />
<br />
{{Main|Om2009}}<br />
<br />
* '''[[Om 2008]]''' was released on August 8, 2008, to replace 2007.2. Prior to that, its codename was ASU (April/August Software Update). This is still the name of the branch in the version control system. This distribution integrates the [http://trolltech.com/products/qtopia Qtopia] phone stack with a set of new Openmoko applications based on the Enlightenment Foundation Libraries ([[EFL_Documentation|EFL]]). Qtopia being a more mature product than the GNOME Mobile stack, the standard phone applications (dialer, contacts, calculator, calendar) work better than in 2007.2. The Qtopia used in 2008.8 was ported to run on X11, contrary to standard Qtopia which uses the framebuffer. This allows non-Qt applications to safely share the screen with Qt applications. <br />
<br />
{{Main|Om 2008}}<br />
<br />
* '''[[Om 2007.2]]''' was the first distribution created by Openmoko. The interface was totally finger-oriented, optimized for 285ppi, and very orange. It used the GTK+ stack, which is part of the [http://www.gnome.org/mobile/ GNOME Mobile] platform. This distribution is now considered obsolete and not being worked on by Openmoko Inc or by OpenedHand. <br />
<br />
{{Main|Om 2007.2}}<br />
<br />
=== Others / unreleased ===<br />
* The [http://www.neopwn.com/software.php NeoPwn] network auditng system's core is a modified Linux 2.6.24 kernel, with cross-compiled module driver support for the numerous compatible addon devices running on a FULL Debian (ARMEL) operating system. The filesystem has been optimized for performance and size and includes the NeoPwn menu system and several GUI dialogs for hardware control and attack automation. ''Status: Unknown, the GPL requires source code to be distributed only to customers''.<br />
* [http://runningbear.org/trac RunningBear] is an innovative, yet free and open-source Operating System for hackable devices driven by Bearstech. Lightweight, Portable, Secure, Friendly and Useful. ''Status: In development''.<br />
* [http://pokylinux.org/ Poky] and Sato, by OpenedHand/Intel. An open source platform build tool derived from OE. It is a complete software development environment for the creation of Linux devices. It enables you to design, develop, build, debug, and test a complete, modern, software stack using Linux, the X Window System and GNOME Mobile based application frameworks for both ARM and x86 based platforms. ''Status: The "Nightly Build" Image works fine on Neo Freerunner, but phone functionality doesn't.''<br />
* [http://pyneo.org/ PyNeo] pyneo is a stack for mobile devices excessivly using dbus, glib and evas. Pyneo is NO distribution but a middleware or framework like FSO which itself developed from a very early version of pyneo. Current pyneo images are entirely based on debian instead of oe. ''Status: still active and in development! ask around on #pyneo.org ''<br />
* [http://www.quantum-step.com/ mySTEP] by Openmoko distributor Golden Delicious Computers is based on GNUstep and brings a Objective-C API to the Neo. Core GUI frameworks are "Foundation" & "AppKit". It has been shown on FOSDEM 2008, LinuxTag 2008 and SYSTEMS 2008 to run on the Neo 1973. If someone reengineers UIKit, (open) source code compatibility to iPhone apps appears achievable. ''Status: slow progress behind the scenes''<br />
* [http://www.archmobile.org/ Archlinux] is a distribution that follows the KISS principle.<br />
<br />
== Features by distribution/release target ==<br />
<br />
Generally, distributions can differ on one or more of the following components:<br />
* The bootsplash screen image. This is purely decorative.<br />
* The bootloader. Theoretically, any version of ''uboot'' could be used with any distribution. In the future ''Qi'' will replace ''uboot''.<br />
* The kernel. GNU/Linux kernels versions 2.6.24, 2.6.26 or 2.6.28 can be found. Some have modules compiled in, others have modules compiled separately. If compiled separately, modules can be distributed in the same package file as the kernel or separately.<br />
* Middleware: daemons to handle GSM calls or GPS, sound system, personal information storage and so on. Qt and Android have their own subsystems, FreeSmartphone.Org (FSO) is working towards a standard-based Free Software one.<br />
* Display driver. The original ''Qt Extended'' uses the framebuffer, most other distributions today use ''X11''.<br />
* Libraries and application framework (widget toolkit and and graphical environment) : EFL, Qt, Gtk+ or Java ?<br />
* Basic telephony applications: voice calls, SMS, alarm clock...<br />
* Smartphone applications: GPS, media player, simple games, web browser...<br />
* Open source applications: more games, scientific, you name it...<br />
<br />
=== Hardware Support ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]<br />
|-<br />
| GTA01 || ?? || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || ?? || ??<br />
|-<br />
| GTA02 || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Connectivity ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]<br />
|-<br />
| Telephony || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} || {{Yes}}<br />
|-<br />
| SMS || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} || {{Yes}}<br />
|-<br />
| [[GPRS]] || {{Yes}}? || Not through UI || Not through UI|| {{Yes}} || {{Yes}} || {{Yes}} (1) || Not through UI || {{Yes}}<br />
|-<br />
| [[WiFi]] || {{Yes}}? || {{Yes}} (*) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || Not through UI || {{Yes}}<br />
|-<br />
| VoIP || {{no}} || ?? || ?? || ?? || {{Yes}} (1) || {{Yes}} || ?? || {{no}}<br />
|-<br />
| Bluetooth || {{no}} || {{Yes}} (*) || {{Yes}} (*) || {{Yes}} (*) || {{Yes}} (*) || {{Yes}} (*) || {{Yes}} || {{Yes}}<br />
|-<br />
| GPS || {{Yes}} (1) || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} (1) || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Power ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]<br />
|-<br />
| Suspend || {{Yes}} || {{Yes}} || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}<br />
|-<br />
| Resumes on Event || {{Yes}} || ?? || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| Functions after Resume || {{Yes}} || {{Yes}} || ?? || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== User Interaction ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]<br />
|-<br />
| Finger friendly || {{Yes}} || Partially || Partially || {{Yes}} || {{Yes}} || {{Yes}} [[Illume|(1)]] || {{Yes}} || {{Yes}}<br />
|-<br />
| Accelerometer || {{Yes}} (1) || {{Yes}} [[Rotate|(1)]][[Gestures|(1)]] || {{No}} || {{Yes}} || {{No}} || {{Yes}} || ?? || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Applications ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]<br />
|-<br />
| Terminal || {{Yes}} || {{Yes}} (1) || Basic (2) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}}<br />
|-<br />
| PIM || {{No}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} || {{Yes}} (1) || ?? || ??<br />
|-<br />
| Phonebook || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} || {{Yes}}<br />
|-<br />
| Dialer || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} || {{Yes}}<br />
|-<br />
| Web Browser || {{Yes}} (1) || {{Yes}} (1) || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
| Mail Client || {{Yes}} (1) || {{Yes}} || ? || {{Yes}} || {{Yes}} || {{Yes}} (1) || {{Yes}} || {{Yes}}<br />
|-<br />
| XMPP Client || {{Yes}} (1) || {{Yes}} [[Pidgin|(1)]] || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} (1) || || ??<br />
|-<br />
| Media Player || {{Yes}} (1) || {{Yes}} (1) || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} (1) || ?? || {{Yes}}<br />
|-<br />
|}<br />
<br />
=== Toolkits / Runtimes ===<br />
{|class="wikitable" border="1" cellpadding="5" cellspacing="0" width=100%<br />
! width=10%| !! width=8%|[[Om 2009]] !! width=8%|[[Om 2008]] !! width=8%|Om 2007.2 !! width=8%|[[SHR]] !! width=8%|[[Qt Extended Improved]] !! width=8%|[[Debian]] !! width=8%|[[Gentoo]] !! width=8%|[[Android]]<br />
|-<br />
| GTK+ || {{Yes}} || {{Yes}} || {{Yes}} || {{Yes}} || {{No}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| Qt/Qt Extended || {{Yes}} || {{Yes}} || {{No}} || {{Yes}}? || {{Yes}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| Middleware || FSO || qtopia-x11 || gsmd/neod || FSO || Qt Extended || FSO || FSO || ??<br />
|-<br />
| [[Java]] || ?? || {{Yes|Jalimo}} || {{Yes|Jalimo}} || {{Yes|Jalimo}} || ?? || {{Yes|CacaoVM, JamVM}} || ?? || ??<br />
|-<br />
| [[Python]] || {{Yes}} || {{Yes}} || {{Yes}} || {{yes}} || {{Yes}} || {{Yes}} || {{Yes}} || ??<br />
|-<br />
| [[Mono]] || ?? || {{Yes}} (1) || {{Yes}} (1) || {{no}} || ?? || {{Yes}} (1) || ?? || ??<br />
|-<br />
| [[Ruby]] || ?? || {{Yes}} || ?? || ?? || ?? || {{Yes}} (1) || {{Yes}} (1) || ??<br />
|}<br />
<br />
Footnotes:<br />
<br />
(1) works, but need additional software to be installed<br />
<br />
(2) unusable due to lack of certain keyboard characters. [[Switching_Keyboards#Matchbox_keyboard|Various fixes available.]]<br />
<br />
(*) unstable<br />
<br />
==Quick download page==<br />
<br />
[[Download]]<br />
<br />
== See also ==<br />
<br />
* Mickey Lauer's post "[http://www.vanille-media.de/site/index.php/2008/06/28/gtk-asu-fso-tmtla/ GTK, ASU, FSO, TMTLA!]" describes the differences between distributions 2007.2, ASU and FSO.<br />
<br />
* Latest news and tips are in [[Community Updates]]<br />
<br />
* [[Kustomizer]] is a script to change your Om 2009 or Om 2008.12 to a usable phone<br />
<br />
[[Category:Distributions| ]]</div>Dareushttp://openmoko.org/wiki/ApplicationsApplications2010-01-08T17:19:15Z<p>Dareus: /* External links */ SPAM deleted</p>
<hr />
<div>{{Languages|Applications}}<br />
This is the wiki's master application list for the Openmoko smartphones. <br />
<br />
== How to register new applications ?==<br />
<br />
This list can not be exhaustive, as new things are showing up every week. This page is here to help spreading awareness about applications. Here are instructions on how to add a specific application to this list. There are many ways to go<br />
<br />
Method 1 (preferred):<br />
* Register your application at http://opkg.org. You will get a package number there, for example 33.<br />
* Notify the community mailing list.<br />
* Come back here, click on "edit" next to the appropriate section title, then add a line like:<br />
<pre>* {{opkg.org|33|Application name}} A short description</pre><br />
<br />
Method 2: Just link to wherever the application is hosted.<br />
* Click on "edit" next to the appropriate section title, add a line like:<br />
<pre>* [http://your.host.domain/the/path/to/app/page.html Application name] A short description</pre><br />
<br />
Method 3: Create a new page in this wiki.<br />
* Click on "edit" next to the appropriate section title, then add a line like:<br />
<pre>* [[Application name]] A short description</pre><br />
* The application name will appear in red, click on it to create and edit the new page.<br />
<br />
== Audio ==<br />
<br />
* [http://www.faltantornillos.net/proyectos/gnu/brightPlayer/brightPlayerGTK0.2.tar.gz Bright Player] - Fast, lightweight and easy random music player.<br />
* [http://rzr.online.fr/q/esd boxar] - Touchscreen as a finger friendly piano -- [[User:RzR]]<br />
* [[Dictator]] - Record mic, incoming GSM-sound, or a whole Phonecall<br />
* {{opkg.org|55|ePiano}} - epiano is going to be a virtual piano<br />
* [[Fingertier]] - minimal and finger friendly music player<br />
* [[Fourier]]- Realtime frequency analysis of sound data.<br />
* [[Guitartune]] - Tune musical Instruments.<br />
* [[GTick]] - GTick is a metronome application written for GNU/Linux<br />
* [[Intone]] - Elementary based mplayer frontend (for audio files).<br />
* {{opkg.org|271|JaMoko}} Jamoko is a Jamendo player for OpenMoko.<br />
* [[Mokoko]]- Play music.<br />
* {{opkg.org|151|MokoPod}} - Retrieve and listen to podcasts <br />
* [[PodPooch]] - Retrieve and listen to podcasts - fork of MokoPod<br />
* [[Neoqplayer]] - Renamed as GorshPlayer: a multimedia player written in Qt4: play and retreive podcasts feeds, more reactive interface, now able to play videos ( in svn ).<br />
* [http://fisoft.eu/standa/openmoko/omshuffle_0.1_arm.ipk omShuffle] - Inspired by Bright Player with volume control. Needs mplayer to work.<br />
* [[Openmoko-mediaplayer2]] - Play music and video (mp3...)<br />
* [[Openmokast]] - Play audio stream and slideshow stream<br />
* [[Podboy]] - A Podcast player (Python/Elementary/Gstreamer/SQLite)<br />
* {{opkg.org|265|PyRadio}} TUI program in python for receiver stream of internet radio.<br />
* [[Pythm]] - Audio player GUI using mplayer and mpd as backend.<br />
* [[PyRok]] - Audio player which uses Gstreamer for playback and Pygame for GUI.<br />
* [[Satan]] - Create your own music!<br />
* [[Streamtuner]] - Listen to Internet Radio Stations<br />
* [[Streamripper]] - Record from Internet Radio Stations<br />
* {{opkg.org|297|quickplay}} A light weight mp3 player/frontend for Ampache [http://ampache.org/ ampache.org]<br />
* [[Voicenote]] - Voicenote is a script which allows to record any sound from the microphone into a wav file. It can play the created files too. It is intended to be an easy and quick way to do so.<br />
<br />
== BlueTooth ==<br />
* [[Coypu]] - Utility for send file via BlueTooth<br />
<br />
== Games ==<br />
<br />
* [[Acceleroids]] Shoot-the-asteroids game<br />
* {{opkg.org|169|Black Sheep}} Fight insomnia!<br />
* [[CellHunter]] - A game you earn points by collecting cells (in english now).<br />
* [http://unsyncopated.com/BrainSolvent/Doom%20Port DOOM]- Classic FPS. Freerunner/1973<br />
* [[Duke Nukem 3D]] - Legendary First Person Shooter.<br />
* [[Freerunner LightSaber]]-Application as iphone LightSaber.<br />
* [[Games/Om 2007.2]] - Many small games on Om 2007.2<br />
* [[Gnuboy]] - An emulator for the handheld gaming all-time bestseller.<br />
* {{opkg.org|149|I'm Rich}} I'm Rich application<br />
* [[Kobodeluxe]] - A top-view space shooter, available from 2008.8 repositories.<br />
* [[Liquid War]]-Liquid War is a truly original multiplayer wargame.<br />
* [[MBAC]]- MBAC is "Moko Bulls and Cows", a classic game for openmoko written in pygtk similar to mastermind.<br />
* [[Moko-sudoku]] - Another sudoku puzzle game.<br />
* [[Neomis]] - A computer version of the well-known electronic game named Simon. <br />
* [[NumberX]] - A mathematical puzzle game that will challenge your mental math abilities!<br />
* {{opkg.org|121|Mokomaze}} Ball-in-the-labyrinth game<br />
* [[Numptyphysics]] - A drawing puzzle game.<br />
* [[Om 2008.8 Sudoku]] - Number placement based puzzle game<br />
* {{opkg.org|136|OpenMiaoCat}} OpenMiaoCat, like OpenMooCow, makes your phone became a cat!<br />
* [[openmokontrol]] Program to control a TCP/IP connected X11 server with the accelerometers, especially games.<br />
* [[OpenMooCow]] - OpenMooCow reads information out of your accelerometers. Now, if you turn the phone upside down and back again, it "moos" like one of the little toys.<br />
* [[OpenTTD]] - OpenTransportTycoonDeluxe, ported to openmoko, using only GPLed datafiles.<br />
* [[OpenVibe]] - The first opensource vibrator.<br />
* [[Pingus]] - Pingus is a lemmings clone with penguins.<br />
* [http://scalde.free.fr/index.php?option=com_content&view=article&id=93:pong-pogresses&catid=43:openmoko&Itemid=66 Pong progresses]- This is a little pong game for the openmoko freerunner. The screen is devided in halves, so you can touch the right half to move the paddle right and the left half to move it left.<br />
* {{opkg.org|60|ScummVM}} ([[Scummvm|Wiki]]) Virtual Machine for several classic graphical point-and-click adventure games<br />
* [[XBill]] - Little action game to stop Bill from installing Windows(tm) on computers.<br />
* [[Xlogical]]-A puzzle based game where you turn spinners to move balls around.<br />
* [[XSkat]] - XSkat lets you play the card game Skat defined by the official Skat Order.<br />
<br />
== GPS ==<br />
* [[a-gps GUI]] - Graphical User Interface for [http://en.wikipedia.org/wiki/Assisted_GPS assisted GPS]. GSM-network cell locations are provided by [[Cellhunter]] and this data can be used to locate you. It uses u-blox a-gps to initialize your GPS chip.<br />
* {{opkg.org|268|Advanced Geocaching Tool for Linux}} - "Towards paperless geocaching" - [[Advanced Geocaching Tool for Linux|User Manual]]<br />
* [[bicirutas]] - This application looks for mtb routes in www.bicirutas.net (routes in Spain, Portugal, United Kingdom, France, Italy and Germany). It gets the current position from the gps system and downloads nearby routes. Then you can follow them with tangogps application.<br />
* {{opkg.org|175|BikeAtor}} - Like TangoGPS BikeAtor can display OSM Maps. The Speedometer displays the most interesting values of the trip.<br />
* [[GPS Sight]] - Display GPS information, location, tracks, etc, without maps.<br />
* [[Gpsdcontrol]]-A simple python script for start or stop gpsd daemon with a button on the desktop.<br />
* [[Gpsdrive]] - Car (bike, etc) navigation system<br />
* [[Gtkaddpoi]] - Utility for add a POI to TangoGPS using address or coordinates and export to Navit or to .kml file.<br />
* {{opkg.org|162|gvSIG Mobile}} - This is an unofficial port of gvSIG Mobile (http://www.gvsig.gva.es/) to the Openmoko platform. Supports: GPS, WMS, ArcIMS, tiles (OSM etc) and Shapefiles, all in a variety of projections. Version 0.1.5 includes a great feature to perform synchronization with a remote PostGIS database. [http://gvsigmobileonopenmoko.wordpress.com/ Homepage].<br />
* [[Idle Hands]] - Give a task to you based on your location<br />
* [http://www.mumpot.org/ mumpot] - Display map (OSM), routing, OSM editing, a bit of live editing<br />
* [[Navit]] - Car navigation system with routing engine<br />
* [[Om 2008.8 Locations]] - (aka Splinter) - Location sharing based on GPS and SMS<br />
* [http://code.google.com/p/omgps omgps] - High performance, UBX binary or ogpsd as GPS data provider, layered maps, AGPS online, track replay, scratch on map, ruler and lat/lon grid, basic sounding. etc.<br />
* [[OpenBmap]]-a free and open map of wireless communicating objects (e.g. cellular antenna, Wi-Fi, Bluetooth). It provides tools to mutualize data, create and access this map.<br />
* [[openBmap-locator]] - Estimate your location based on the GSM signals, uses openBmap data for its geolocation<br />
* [[Pyroute]] - Pyroute is a routing program written in Python. It features mobile phone GUI for maps, GPS, and routing.<br />
* [[QMapControl]] - Display maps (OSM..) and add points, lines...<br />
* [[QNavitCtl]] - send coordinates to Navit via dbus (position, destination, map center)<br />
* [[Qpegps]] - Display map with current position<br />
* [[SGTL|Simple Geocaching Tool for Linux]] - A geocaching application which shows you the direction.<br />
* [[sms-sentry]] - locate a lost or stolen phone<br />
* [[TangoGPS]] - Display map (OSM..), record GPS tracks...<br />
* [[Travel Diary]] - a simple application to save little diary entries to a csv file and send this to a server (that can generate a .kml file or show a map or do whatever...)<br />
<br />
== Graphics ==<br />
<br />
* [[Flash|Gnash]]-Play flash file on Neo<br />
* [[Gpe-scap]] - Take screenshots<br />
* [[Neon]] - Image viewer<br />
* [[OMView]] - Image viewer<br />
* [[Orrery]] - Displays the night sky<br />
* [[PyPenNotes]] - Write notes using pen and touchscreen<br />
<br />
== Internet ==<br />
===Web browsers===<br />
* [http://www.dillo.org/ Dillo] - Multiplatform fast and small web browser ([http://misc.andi.de1.cc/dillo/ .ipk]).<br />
* fennec<br />
* [[Midori]] - Webkit based web browser<br />
* [[Minimo]] - Mozilla based web browser<br />
* [http://www.netsurf-browser.org/ netsurf]-A new browser for Neo FreeRunner.<br />
* [[Openmoko-browser2]] - The original Openmoko web browser<br />
* [http://code.google.com/p/pyqt-browser/ pyqt-browser] - modified the sample code from python-pyqt4 and changed it to use webkit for web browsing. <br />
* woosh<br />
<br />
===VOIP===<br />
* [[Linphone]] - Voice over IP<br />
* [[Twinkle]] - Voice over IP<br />
<br />
===Email clients===<br />
* [http://www.claws-mail.org/ claws-mail] email client available in shr-unstable<br />
* [[Openmoko Mail]] - E-mail client<br />
* [[Qtmail]] - Default mail program on Om 2008.8<br />
<br />
===Offline wikipedia===<br />
* {{opkg.org|128|Evopedia}} - a powerful Wikipedia reader (download dumps in [http://www.reitwiessner.de/openmoko/evopedia.html its official site])<br />
* [[Mokopedia]] - Read small Wikipedia dumps offline<br />
* [[Offline Wikipedia reader]] - store the entire content of wikipedia (single-language, excluding images), on a single 8GB microSD card<br />
<br />
===IM===<br />
* [[CenterIM]] - Instant messaging client (terminal-based).<br />
* [[Pidgin]] - Instant messaging client (ICQ, MSN, Jabber, Yahoo and more.)<br />
<br />
===other===<br />
* [http://opkg.networld.to/networld-ported/ettercap-ng_0.7.3-r3_armv4t.opk ettercap-ng] MITM (fixed link)<br />
* {{opkg.org|205|GPRSModem}} - Converts your neo in a GPRS modem.<br />
* [[Openmokast]] - Play audio stream and slideshow stream<br />
* [[PyFeedRead]] - RSS feed reader<br />
* [[TwitterMoko]] - A Twitter client for Openmoko<br />
<br />
== Office ==<br />
* dates - a simple calendar<br />
* [[e-tasks]] - An elementary task manager<br />
* [[Epdfview]] - PDF reader.<br />
* Evince - Document reader for PDF, PS, DJVU and more.<br />
* [[FBReader]] - E-book reader program (TXT, FB2, HTML and more)<br />
* [[GPE contacts]]<br />
* [[Gutenflash]] - Fast text reader by scrolling text<br />
* [[OMoney]] - A bookkeeping application<br />
* [[Pisi]] - PIM synchronization<br />
<br />
== Settings ==<br />
<br />
* [[KnjMokoOPKG]] - A graphical frontend to OPKG.<br />
* [[KnjMokoWifi]] - Wifi setup tool<br />
* [[Lint-wifi]] - Wifi setup tool<br />
* [[Mofi]] - Wifi setup tool<br />
* [[Mokonnect]] - Connection manager<br />
* [[momtools]] - an application to control Wifi, gprs and some other stuff<br />
* [[Om 2008.8 Installer]] - Graphical software installer<br />
* [[Opkg]] - Command line software installer<br />
* {{opkg.org|285|opkg.py}} - Command line software installer for www.opkg.org packages<br />
* [[Sephora]] - Settings manager<br />
* [[SettingsGUI]] - Edit various settings<br />
* [[Timezone|tzdata]]- Customise your time zone setting.<br />
* [[Wicd]] - Wifi setup tool<br />
* [[Wlan]] - Wlan is an application to manage wireless connection on the Freerunner<br />
* [[ZOMG!]] - A graphical package manager (opkg frontend -> should work on any distro)<br />
<br />
== System ==<br />
* [[Aphasia]] - A system built on Erlang and a vertical application for people with apahasia.<br />
* [http://www.pierrox.net/auimd/ AUIMD] - AUIMD is a PyQt graphical user interface for mobile devices.<br />
* [[Auxlaunch]] - Finger-friendly app launcher and window switcher<br />
* [[Display Locker]] - Screen lock<br />
* [http://fso-control.projects.openmoko.org/ fso-control] - Popup Power menu to shutdown/suspend/reboot.<br />
* [[Gwaterpas]] - levelling tool using accelerometer<br />
* [[Gestures]] - Detect movement and display information, rotate screen<br />
* [[Keychain]] - SSH keys<br />
* {{opkg.org|253|libaxel}} - Library for easy use accelerometer.<br />
* [[MokoFEM]] - Monitors GSM information<br />
* [[Mokostat]] - Monitors battery<br />
* [[omkeys_functions]] - Remap AUX key bindings<br />
* [[Openmoko Bluetooth remote controller|ReMoko]] - Control stuff via BlueTooth<br />
* [[Pexpect]]-a pure Python module for spawning child applications; controlling them; and responding to expected patterns in their output. <br />
* [[Rotate]] - Rotate screen when phone is rotated<br />
* [[Siglaunchd]] - A daemon that listens to dbus signals and launches appliactions upon arrival.<br />
* [[Ts calibrate]] - Calibrates touchscreen<br />
* [[Vala-terminal]] - Command prompt with tabs<br />
* [[Web-Manager]] - Control your phone by a web interface from your PC<br />
* [http://wiki.openmoko.org/wiki/Minimoko xminimokostatus] Battery- / GSM-Status Display on Root Window (Part of Minimoko)<br />
* [[Zedlock]] - Screen locker<br />
<br />
== Telephony ==<br />
* [[Dialer/2007.2]] - The dialer application in Om 2007.2<br />
* Launcher<br />
* [[Litephone]] Easy to use, single window phone application written in Qt.<br />
* [[Openmoko SMS Middleware]]- SMS middleware is a Openmoko middleware software for additional features related to SMS. Plugin architecture and Python based code gives this project lots of flexibility and enchancebility.<br />
* [[Paroli]] -Paroli is an integrated phone application based on Tichy (and so also written in python). <br />
<br />
== Utility ==<br />
<br />
* {{opkg.org|176|CoovaChilli}} - It turns your phone's WiFi network into an Ad-Hoc Hotspot!<br />
* [http://openmoko.huber-computer.de/ DWDWetter] Fetches weather information from dwd (First Register at dwd!)<br />
* [[Enotes]] - Enotes is the implementation of a TODOlist manager written with elementary to appear better with distribution that use illume, like SHR.<br />
* [[Enscribi]]-a handwriting recognition input method for Linux. It's mainly developed for the Openmoko Freerunner smartphone.<br />
* [http://projects.openmoko.org/projects/ffalarms/ FFAlarm] is a program to set multiple alarms a day using a finger friendly user interface<br />
* {{opkg.org|57|fido}} - [[fido]] is a todo list\note manager written with elementary<br />
* [[GridPad]]-GridPad is an alternative input method for entering text with your finger, a Simple Character Recognizer Software.<br />
* [[HP48 Series RPN Calculator]] - Calculator with many functions<br />
* [[LED clock]] - When an Openmoko is sitting unused at night, turn it into an alarm clock with large 7-segment digits on a black background in landscape mode. <br />
* [http://meuk.spritesserver.nl/lightsaber-0.1.tgz The Lightsaber]. Pre-alpha starwaresque orphanware.<br />
* [[Literki]] - alternative keyboard<br />
* [[MokoGeocaching]] - Utility for add a POI to TangoGPS using geocaching.com <br />
* [[Mokometeo]] is a widget which fetches the weather forecast from yahoo, for a list of cities<br />
* [[NeoCon]] - neocon is a handy serial console utility (not only) for u-boot. The main feature of neocon is actually that you can give it a list of devices and it will pick one that works.<br />
* [[NeoLight]] - NeoLight turns your phone into a flashlight.<br />
* [[NeoTool]] NeoTool is a bash script for your desktop system to provide a friendly GUI frontend to some common management tasks.<br />
* [[OpenWrt]]-basic support for the Openmoko "Freerunner"! Kernel (2.6.28) is building and booting.<br />
* [http://projects.openmoko.org/projects/otp4neo/ OTP4Neo] One time password generator<br />
* [[Pimlico]]-Pimlico is a suite of lightweight Personal Information Management (PIM) applications designed primarily for handheld and mobile devices<br />
* [[QSuunto-Lite]] display dive log information from Suunto Dive computers (that work with divetools-ab)<br />
* [[qwo]]- An alternative input method.<br />
* [[ShortOm]] - Graphical launcher for shell or application, with editable config file, and log result page.<br />
* {{opkg.org|263|spoje}} Program for searching a transport link.(mainly is used for Czech transport)<br />
* [[sortdesk]] sort your om-desktop in categories<br />
* [[Unison]] - Unison is a file-synchronization tool for Unix and Windows. It determines all differences between two directory trees and lets the user decide, how to proceed with every differing file. <br />
* [http://techiem2.net/index.php?/archives/10-Freerunner-USB-Mode-Control-Program.html usbmode]-a quick pygtk program. <br />
* [[Wrench]] - Modual used utility enlightenment_remote.<br />
* [[Yaouh!]] - Yet Another OSM Updater H.<br />
* [[Auto Home]] - Home automation using the Free runner (Openmoko)<br />
* {{opkg.org|279|Babiloo}} - Dictionary utility with voice capability<br />
* {{opkg.org|284|Fltk World Clock}} - Displays the time in different timezones (needs fltk)<br />
* {{opkg.org|298|Fltk Hacker's Diet}} - Helps you maintain, decrease or increase your weight (needs fltk)<br />
* {{opkg.org|306|Fltk Cocktail Bar}} - a Cocktail Bar application<br />
* {{opkg.org|309|Fltk WW Point Cal}} - Calculate the Weight Watches Points of a given food<br />
<br />
==Setting Application==<br />
* [[GTA02 sysfs]]- sysfs is a filesystem that is mounted on /sys which contains various fake "files" that are actually filled by a variety of drivers and other kernel subsystems. You can use it to change settings and behaviours of the kernel and drivers dynamically.<br />
* [[Wmiconfig]]- wmiconfig is a tool written by Atheros Communications Inc to configure the Ar6k WIFI chip used in the Neo Freerunner. This is a standalone C executable, released under GPL v2.<br />
<br />
== Video ==<br />
* [[intone-video]] - an mplayer video frontend<br />
* [http://katastrophos.net/andre/blog/software/quasar-media-player/ Quasar] - a mplayer frontend for X11.<br />
* [[Video Player]] - Using Mplayer on Openmoko smartphones.<br />
<br />
== daemon ==<br />
* [[Lscd]] - LSC library/daemon on Linux System.<br />
* [[PyPhonelog]] - daemon uses the framework to track and log all the calls made to and from the moko.<br />
<br />
== An automatic list of application-related wiki pages ==<br />
<br />
The pages linked above are all maintained manually. We also maintain an automatic categorization system by tagging wiki pages. Here is the list of application-related pages in this wiki. Normally, every page listed below should be also listed above in the same category. The converse is false: there are applications without a wiki page.<br />
<br />
=== Applications in this Wiki: ===<br />
<categorytree mode=pages depth=2 hideroot=on>Applications</categorytree><br />
<br />
== Where to find more applications? ==<br />
<br />
At [http://opkg.org opkg.org] !<br />
<br />
Not all Openmoko apps are listed on this wiki - there are much more [http://projects.openmoko.org/softwaremap/ projects at the Openmoko GForge] than the wiki can list, not to mention self-hosted applications on their own websites. Actually the phones can run most Linux based Free Software, using for example the [[Debian]] distribution. The [http://handhelds.freshmeat.net/browse/1038/ mobile phones section of Freshmeat] may be a interesting place to look.<br />
<br />
Note also that there are many packages in the repository that are not installed by default. If what you want is a classic, chances are that it is already packaged. Suppose you want to install Perl:<br />
opkg list|grep perl<br />
opkg install perl<br />
<br />
More application download related pages:<br />
<br />
* [[Community Repository]]<br />
* [[Users Repositories]]<br />
<br />
<div style="clear:both">&nbsp;</div><br />
<br />
== Where to find full distributions ? ==<br />
<br />
* [[Download]]: for complete system downloads<br />
<br />
== The usual warnings ==<br />
<small><br />
* Some of these software are developed by Openmoko Inc. and some are contributed by the community. Any problems with community contributed software should be reported to the individual software developer rather than the Openmoko core team.<br />
* Most programs listed here are not mature/stable, but only useable/beta.<br />
* Many programs listed here are not yet packaged for your distribution and integrated in its repositories. Whichever it is.<br />
* Installing experimental software from the internet is certain to break things. Running it as root is a very insecure thing to do. Kown that you will be burned, have backups, and be ready to apologize to everybody in your phone contact list in case they receive strange SMSs...<br />
</small><br />
<br />
==See also==<br />
* [[Hall of Fame]]<br />
<br />
==External links==<br />
* [http://code.google.com Google code projects] tagged with:<br />
** [http://code.google.com/hosting/search?q=label%3Afreerunner&filter=0&start=0 Tag FreeRunner]<br />
** [http://code.google.com/hosting/search?q=label%3Afreerunner&filter=0&start=0 Tag Openmoko]<br />
* [http://www.opkg.org opkg.org] - A software directory for Openmoko phones<br />
<br />
[[Category:Applications| ]]<br />
[[Category:Basic End User]]</div>Dareushttp://openmoko.org/wiki/Phone_PrefixesPhone Prefixes2009-10-07T16:43:31Z<p>Dareus: /* List of countries */</p>
<hr />
<div>This page will eventually include all the prefixes you use for your countries (and service providers) in /etc/phone-utils.conf.<br />
<br />
At first it'll be useful for other users, but when it'll be big enough we'll be able to set it up automatically according to your country.<br />
<br />
Just fix this list according to your country info.<br />
<br />
This is *only* about numbers that may show up on inbound call like<br />
+49 179 345345<br />
but you were lazy and didn't fill in the full number in your contacts, like<br />
0 179 345345<br />
So the idea is phone-utils expands your contacts number to match the inbound call number. Any "*" won't help here at all as it will not show up on the inbound number, and any <br />
0011(Voice_calls)0015 (Fax_calls_- Telstra)<br />
entry as well won't help as you probably won't see faxcalls inbound either (or at least you had that code stored together with the actual number in your contacts then)<br />
<br />
Use a '|' (pipe) in order to split between multiple options for that specific field. The leftmost option in each pipe chain is the default option.<br />
<br />
'''IMPORTANT:'''--[[User:Tomhacohen|Tom Hacohen]] 18:35, 3 October 2009 (UTC) This list was generated from http://www.kropla.com/dialcode.htm using sed, it may have errors, please verify your country has exactly the 4 segments required (i.e one '=' sign and 2 ',' sign)<br />
<br />
('''NOTICE:''' don't forget to add a single space before each line you enter)<br />
<br />
= List of countries =<br />
#Format: Country_Name = Country_Code, International_Prefix, National_Prefix<br />
Afghanistan = 93, 00, 0<br />
Albania = 355, 00, 0<br />
Algeria = 213, 00, 7<br />
American_Samoa = 1684, 011, 1<br />
Andorra = 376, 00, <br />
Angola = 244, 00, 0<br />
Anguilla = 1264, 011, 1<br />
Antarctica = 672, , <br />
Antigua = 1268, 011, 1<br />
Argentina = 54, 00, 0<br />
Armenia = 374, 00, 8<br />
Aruba = 297, 00, <br />
Ascension = 247, 00, <br />
Australia = 61, 0011|0015|0018|0019, 0<br />
Australian_External_Territories = 672, 00, 0<br />
Austria = 43, 00, 0<br />
Azerbaijan = 994, 00, 8<br />
Bahamas = 1242, 011, 1<br />
Bahrain = 973, 00, <br />
Bangladesh = 880, 00, 0<br />
Barbados = 1246, 011, 1<br />
Barbuda = 1268, 011, 1<br />
Belarus = 375, 810, 8<br />
Belgium = 32, 00, 0<br />
Belize = 501, 00, 0<br />
Benin = 229, 00, <br />
Bermuda = 1441, 011, 1<br />
Bhutan = 975, 00, <br />
Bolivia = 591, 0010|0011|0012|0013, 010|011|012|013<br />
Bosnia = 387, 00, 0<br />
Herzegovina = 387, 00, 0<br />
Botswana = 267, 00, <br />
Brazil = 55, 0014|0015|0021|0023|0031, 014|015|021|023|031|0<br />
British_Virgin_Islands = 1284, 011, 1<br />
Brunei_Darussalam = 673, 00, 0<br />
Bulgaria = 359, 00, 0<br />
Burkina_Faso = 226, 00, <br />
Burundi = 257, 00, <br />
Cambodia = 855, 001, 0<br />
Cameroon = 237, 00, <br />
Canada = 1, 011, 1<br />
Cape_Verde_Islands = 238, 0, <br />
Cayman_Islands = 1345, 011, 1<br />
Central_African_Republic = 236, 00, <br />
Chad = 235, 15, <br />
Chatham_Island_(New_Zealand) = 64, 00, <br />
Chile = 56, 00, 0<br />
China, 86, 00, 0<br />
Christmas_Island = 61-8, 0011, 0<br />
Cocos_Keeling_Islands = 61, 0011, 0<br />
Colombia = 57, 005|007|009|#555|#999, 03|05|07|09<br />
Comoros = 269, 00, <br />
Congo = 242, 00, <br />
Zaire = 243, 00, <br />
Cook_Islands = 682, 00, 00<br />
Costa_Rica = 506, 00, <br />
Ivory_Coast = 225 , 00, 0<br />
Croatia = 385, 00, 0<br />
Cuba = 53, 119, 0<br />
Cuba_(Guantanamo_Bay) = 5399, 00, 0<br />
Curaçao = 599, 00, <br />
Cyprus = 357, 00, <br />
Czech_Republic = 420 , 0095200, <br />
Denmark = 45, 00, <br />
Diego_Garcia = 246, 00, <br />
Djibouti = 253, 00, <br />
Dominica = 1767, 011, 1<br />
Dominican_Republic = 1809|1829 , 011, 1<br />
East_Timor = 670, 00, <br />
Easter_Island = 56, 00, <br />
Ecuador = 593 , 00, 0<br />
Egypt = 20, 00, 0<br />
El_Salvador = 503, 00|144,<br />
Ellipso(Mobile_Satellite_service) = 8812, 8813, 00, <br />
EMSAT_(Mobile_Satellite_service) = 88213, , <br />
Equatorial_Guinea = 240, 00, <br />
Eritrea = 291, 00, 0<br />
Estonia = 372, 00, 0<br />
Ethiopia = 251, 00, 0<br />
Falkland_Islands_(Malvinas) = 500, 00, <br />
Faroe_Islands = 298, 00, <br />
Fiji_Islands = 679, 00, <br />
Finland = 358, 00|990|994|999, 0<br />
France = 33, 00|40|50|70|90, 0<br />
French_Antilles = 596, 00, <br />
French_Guiana = 594, 00, <br />
French_Polynesia = 689, 00, <br />
Gabonese_Republic = 241, 00, <br />
Gambia = 220, 00, <br />
Georgia = 995, 810, 8<br />
Germany = 49, 00 , 0<br />
Ghana = 233, 00, <br />
Gibraltar = 350, 00, <br />
Global_Mobile_Satellite_System_(GMSS) = 881|8810|8811|8812|8813|8816|8817|8818|8819, 00, <br />
Globalstar(Mobile_Satellite_Service) = 8818|8819, 00, <br />
Greece = 30, 00 , <br />
Greenland = 299, 00, <br />
Grenada = 1473, 011, 1<br />
Guadeloupe = 590, 00, <br />
Guam = 1671, 011, 1<br />
Guantanamo_Bay = 5399, 00, 0<br />
Guatemala = 502, 00|130|147,<br />
Guinea-Bissau = 245, 00, <br />
Guinea = 224, 00, 0<br />
Guyana = 592, 001, 0<br />
Haiti = 509, 00, 0<br />
Honduras = 504, 00, 0<br />
Hong_Kong = 852, 001|0080|009, <br />
Hungary = 36, 00, 06<br />
ICO_Global(Mobile_Satellite_Service) = 8810|8811, 00, <br />
Iceland = 354 , 00, 0<br />
India = 91, 00 , 0<br />
Indonesia = 62, 001|007|017, 0<br />
Inmarsat, 870, 00, <br />
Inmarsat(Atlantic_Ocean_- East) = 871, 00, <br />
Inmarsat(Atlantic_Ocean_- West) = 874, 00, <br />
Inmarsat(Indian_Ocean) = 873, 00, <br />
Inmarsat(Pacific_Ocean) = 872, 00, <br />
International_Freephone_Service = 800, , <br />
International_Shared_Cost_Service_(ISCS) = 808, , <br />
Iran = 98, 00, 0<br />
Iraq = 964, 00, 0<br />
Ireland = 353, 00|048, 0<br />
Iridium(Mobile_Satellite_service) = 8816|8817, 00, <br />
Israel = 972, 00|012|013|014, 0<br />
Italy = 39, 00,<br />
Jamaica = 1876, 011, 1<br />
Japan = 81, 001|010|0061|0041, 0<br />
Jordan = 962, 00, 0<br />
Kazakhstan = 7, 810, 8<br />
Kenya = 254, 000|006|007, 0<br />
Kiribati = 686, 00, 0<br />
Korea_(North) = 850, 00, 0<br />
Korea_(South) = 82, 001|002|00700, 0|082<br />
Kuwait = 965, 00, 0<br />
Kyrgyz_Republic = 996, 00, 0<br />
Laos = 856, 00, 0<br />
Latvia = 371, 00, <br />
Lebanon = 961, 00, 0<br />
Lesotho = 266, 00, 0<br />
Liberia = 231, 00, 22<br />
Libya = 218, 00, 0<br />
Liechtenstein = 423, 00, <br />
Lithuania = 370, 00, 8<br />
Luxembourg = 352, 00, <br />
Macao = 853, 00, 0<br />
Macedonia = 389, 00, 0<br />
Madagascar = 261, 00, 0<br />
Malawi = 265, 00, <br />
Malaysia = 60, 00, 0<br />
Maldives = 960, 00, 0<br />
Mali_Republic = 223, 00, 0<br />
Malta = 356, 00, 21<br />
Marshall_Islands = 692, 011, 1<br />
Martinique = 596, 00, 0<br />
Mauritania = 222, 00, 0<br />
Mauritius = 230, 020, 0<br />
Mayotte_Island = 269, 00, <br />
Mexico = 52, 00, 01<br />
Micronesia = 691, 011, 1<br />
Midway_Island = 1808, 011, 1<br />
Moldova = 373, 00, 0<br />
Monaco = 377, 00, 0<br />
Mongolia = 976, 001, 0<br />
Montenegro = 382, 99, 0<br />
Montserrat = 1664, 011, 1<br />
Morocco = 212, 00, <br />
Mozambique = 258, 00, 0<br />
Myanmar = 95, 00, <br />
Namibia = 264, 00, 0<br />
Nauru = 674, 00, 0<br />
Nepal = 977, 00, 0<br />
Netherlands = 31, 00, 0<br />
Netherlands_Antilles = 599, 00, 0<br />
Nevis = 1869, 011, 1<br />
New_Caledonia = 687, 00, 0<br />
New_Zealand = 64, 00, 0<br />
Nicaragua = 505, 00, 0<br />
Niger = 227, 00, 0<br />
Nigeria = 234 , 009, 0<br />
Niue = 683, 00, 0<br />
Norfolk_Island = 672, 00, <br />
Saipan = 1670, 011, 1<br />
Rota = 1670, 011, 1<br />
Tinian = 1670, 011, 1<br />
Norway = 47, 00, <br />
Oman = 968, 00, 0<br />
Pakistan = 92, 00, 0<br />
Palau = 680, 011, <br />
Palestinian_Settlements = 970, 00, 0<br />
Panama = 507, 00|088|055|, 0<br />
Papua_New_Guinea = 675, 05, <br />
Paraguay = 595, 002, 0<br />
Peru = 51, 00, 0<br />
Philippines = 63, 00, 0<br />
Poland = 48, 00, 0<br />
Portugal = 351, 00|882,<br />
Puerto_Rico = 1787|1939, 011, 1<br />
Qatar = 974 , 00, 0<br />
Réunion_Island = 262, 00, 0<br />
Romania = 40, 00|022, 0<br />
Russia = 7, 810, 8<br />
Rwandese_Republic = 250, 00, 0<br />
St. Helena = 290, 00, <br />
St. Kitts/Nevis = 1869, 011, 1<br />
St. Lucia = 1758, 011, 1<br />
St. Pierre_& Miquelon = 508, 00, 0<br />
St. Vincent_& Grenadines = 1784, 011, 1<br />
Samoa = 685, 0, 0<br />
San_Marino = 378, 00, 0<br />
São_Tomé and_Principe = 239, 00, 0<br />
Saudi_Arabia = 966, 00, 0<br />
Senegal_ = 221, 00, 0<br />
Serbia = 381, 99, 0<br />
Seychelles_Republic = 248, 00, 0<br />
Sierra_Leone = 232, 00, 0<br />
Singapore = 65, 001|002|008|012|013|018|019, <br />
Slovak_Republic = 421, 00, 0<br />
Slovenia = 386, 00, 0<br />
Solomon_Islands = 677, 00, <br />
Somali_Democratic_Republic = 252, 00, <br />
South_Africa = 27, 00, 0<br />
Spain = 34, 00, <br />
Sri_Lanka = 94, 00, 0<br />
Sudan = 249, 00, 0<br />
Suriname = 597, 00, <br />
Swaziland = 268, 00, <br />
Sweden = 46, 00, 0<br />
Switzerland = 41, 00, 0<br />
Syria = 963, 00, 0<br />
Taiwan = 886, 002, <br />
Tajikistan = 992, 810, 8<br />
Tanzania = 255, 000|005|006, 0<br />
Thailand = 66, 001|008|009, 0<br />
Thuraya(Mobile_Satellite_service) = 88216, , <br />
Timor_Leste = 670, , <br />
Togolese_Republic = 228, 00, <br />
Tokelau = 690, 00, <br />
Tonga_Islands = 676, 00, <br />
Trinidad_& Tobago = 1868, 011, 1<br />
Tunisia = 216, 00, 0<br />
Turkey = 90 , 00, 0<br />
Turkmenistan = 993, 810, 8<br />
Turks_and_Caicos_Islands = 1649, 011, 1<br />
Tuvalu = 688, 00, <br />
Uganda = 256, 000|005|007, 0<br />
Ukraine = 380, 810, 8<br />
United_Arab_Emirates = 971, 00, 0<br />
United_Kingdom = 44, 00, 0<br />
United_States_of_America = 1, 011, 1<br />
US_Virgin_Islands = 1340, 011, 1<br />
Universal_Personal_Telecommunications_(UPT) = 878, , <br />
Uruguay = 598, 00, 0<br />
Uzbekistan = 998, 810, 8<br />
Vanuatu = 678, 00, <br />
Vatican_City = 39, 379, 00, <br />
Venezuela = 58, 00, 0<br />
Vietnam = 84, 00, 0<br />
Wake_Island = 808, 00, <br />
Wallis_and_Futuna_Islands = 681, 19, <br />
Yemen = 967, 00, 0<br />
Zambia = 260 , 00, 0<br />
Zanzibar = 255, 000, 0<br />
Zimbabwe = 263 , 00, 0<br />
<br />
[[Category:GSM]]<br />
[[Category:Add-on data]]</div>Dareushttp://openmoko.org/wiki/ApplicationsApplications2009-09-11T10:45:58Z<p>Dareus: /* Internet */ typo</p>
<hr />
<div>{{Languages|Applications}}<br />
This is the wiki's master application list for the Openmoko smartphones. <br />
<br />
== How to register new applications ?==<br />
<br />
This list can not be exhaustive, as new things are showing up every week. This page is here to help spreading awareness about applications. Here are instructions on how to add a specific application to this list. There are many ways to go<br />
<br />
Method 1 (preferred):<br />
* Register your application at http://opkg.org. You will get a package number there, for example 33.<br />
* Notify the community mailing list.<br />
* Come back here, click on "edit" next to the appropriate section title, then add a line like:<br />
<pre>* {{opkg.org|33|Application name}} A short description</pre><br />
<br />
Method 2: Just link to wherever the application is hosted.<br />
* Click on "edit" next to the appropriate section title, add a line like:<br />
<pre>* [http://your.host.domain/the/path/to/app/page.html Application name] A short description</pre><br />
<br />
Method 3: Create a new page in this wiki.<br />
* Click on "edit" next to the appropriate section title, then add a line like:<br />
<pre>* [[Application name]] A short description</pre><br />
* The application name will appear in red, click on it to create and edit the new page.<br />
<br />
== Audio ==<br />
<br />
* [http://www.faltantornillos.net/proyectos/gnu/brightPlayer/brightPlayerGTK0.2.tar.gz Bright Player] - Fast, lightweight and easy random music player.<br />
* [[Dictator]] - Record mic, incoming GSM-sound, or a whole Phonecall<br />
* {{opkg.org|55|ePiano}} - epiano is going to be a virtual piano<br />
* [[Fingertier]] - minimal and finger friendly music player<br />
* [[Fourier]]- Realtime frequency analysis of sound data.<br />
* [[Guitartune]] - Tune musical Instruments.<br />
* [[GTick]] - GTick is a metronome application written for GNU/Linux<br />
* [[Intone]] - Elementary based mplayer frontend (for audio files).<br />
* [[Mokoko]]- Play music.<br />
* {{opkg.org|151|MokoPod}} - Retrieve and listen to podcasts <br />
* [[Neoqplayer]] - Renamed as GorshPlayer: a multimedia player written in Qt4: play and retreive podcasts feeds, more reactive interface, now able to play videos ( in svn ).<br />
* [http://fisoft.eu/standa/openmoko/omshuffle_0.1_arm.ipk omShuffle] - Inspired by Bright Player with volume control. Needs mplayer to work.<br />
* [[Openmoko-mediaplayer2]] - Play music and video (mp3...)<br />
* [[Openmokast]] - Play audio stream and slideshow stream<br />
* [[Pythm]] - Audio player GUI using mplayer and mpd as backend.<br />
* [[PyRok]] - Audio player which uses Gstreamer for playback and Pygame for GUI.<br />
* [[Satan]] - Create your own music!<br />
* [[Streamtuner]] - Listen to Internet Radio Stations<br />
* [[Streamripper]] - Record from Internet Radio Stations<br />
* [[Voicenote]] - Voicenote is a script which allows to record any sound from the microphone into a wav file. It can play the created files too. It is intended to be an easy and quick way to do so.<br />
* [http://rzr.online.fr/q/esd boxar] - Touchscreen as a finger friendly piano -- [[User:RzR]]<br />
* {{opkg.org|271|JaMoko}} Jamoko is a Jamendo player for OpenMoko.<br />
----<br />
<br />
== BlueTooth ==<br />
* [[Coypu]] - Utility for send file via BlueTooth<br />
----<br />
<br />
== Games ==<br />
<br />
* [[Games/Om 2007.2]] - Many small games on Om 2007.2<br />
* [[Om 2008.8 Sudoku]] - Number placement based puzzle game<br />
* [[Moko-sudoku]] - Another sudoku puzzle game.<br />
* {{opkg.org|60|ScummVM}} ([[Scummvm|Wiki]]) Virtual Machine for several classic graphical point-and-click adventure games<br />
* [[Kobodeluxe]] - A top-view space shooter, available from 2008.8 repositories.<br />
* [[Pingus]] - Pingus is a lemmings clone with penguins.<br />
* [[Duke Nukem 3D]] - Legendary First Person Shooter.<br />
* [[Numptyphysics]] - A drawing puzzle game.<br />
* [[Gnuboy]] - An emulator for the handheld gaming all-time bestseller.<br />
* [[XBill]] - Little action game to stop Bill from installing Windows(tm) on computers.<br />
* [[Xlogical]]-A puzzle based game where you turn spinners to move balls around.<br />
* [[Liquid War]]-Liquid War is a truly original multiplayer wargame.<br />
* [http://unsyncopated.com/BrainSolvent/Doom%20Port DOOM]- Classic FPS. Freerunner/1973<br />
* [[MBAC]]- MBAC is "Moko Bulls and Cows", a classic game for openmoko written in pygtk similar to mastermind.<br />
* [[OpenVibe]] - The first opensource vibrator.<br />
* [[OpenTTD]] - OpenTransportTycoonDeluxe, ported to openmoko, using only GPLed datafiles.<br />
* [http://scalde.free.fr/index.php?option=com_content&view=article&id=93:pong-pogresses&catid=43:openmoko&Itemid=66 Pong progresses]- This is a little pong game for the openmoko freerunner. The screen is devided in halves, so you can touch the right half to move the paddle right and the left half to move it left.<br />
* [[OpenMooCow]] - OpenMooCow reads information out of your accelerometers. Now, if you turn the phone upside down and back again, it "moos" like one of the little toys.<br />
* [[Freerunner LightSaber]]-Application as iphone LightSaber.<br />
* [[CellHunter]] - A game you earn points by collecting cells (in english now).<br />
* [[XSkat]] - XSkat lets you play the card game Skat defined by the official Skat Order.<br />
* {{opkg.org|136|OpenMiaoCat}} OpenMiaoCat, like OpenMooCow, makes your phone became a cat!<br />
* {{opkg.org|149|I'm Rich}} I'm Rich application<br />
* {{opkg.org|121|Mokomaze}} Ball-in-the-labyrinth game<br />
* [[Acceleroids]] Shoot-the-asteroids game<br />
* {{opkg.org|169|Black Sheep}} Fight insomnia!<br />
----<br />
<br />
== GPS ==<br />
* {{opkg.org|268|Advanced Geocaching Tool for Linux}} - "Towards paperless geocaching" - [[Advanced Geocaching Tool for Linux|User Manual]]<br />
* [[SGTL|Simple Geocaching Tool for Linux]] - A geocaching application which shows you the direction.<br />
* [[GPS Sight]] - Display GPS information, location, tracks, etc, without maps.<br />
* [[Gpsdrive]] - Car (bike, etc) navigation system<br />
* [[Om 2008.8 Locations]] - (aka Splinter) - Location sharing based on GPS and SMS<br />
* [[Navit]] - Car navigation system with routing engine<br />
* [[TangoGPS]] - Display map (OSM..), record GPS tracks...<br />
* [[Pyroute]] - Pyroute is a routing program written in Python. It features mobile phone GUI for maps, GPS, and routing.<br />
* [http://www.mumpot.org/ mumpot] - Display map (OSM), routing, OSM editing, a bit of live editing<br />
* [[QMapControl]] - Display maps (OSM..) and add points, lines...<br />
* [[Qpegps]] - Display map with current position<br />
* [[Idle Hands]] - Give a task to you based on your location<br />
* [[Gtkaddpoi]] - Utility for add a POI to TangoGPS using address or coordinates and export to Navit or to .kml file.<br />
* [[Gpsdcontrol]]-A simple python script for start or stop gpsd daemon with a button on the desktop.<br />
* [[OpenBmap]]-a free and open map of wireless communicating objects (e.g. cellular antenna, Wi-Fi, Bluetooth). It provides tools to mutualize data, create and access this map.<br />
* {{opkg.org|162|gvSIG Mobile}} - This is an unofficial port of gvSIG Mobile (http://www.gvsig.gva.es/) to the Openmoko platform. gvSIG Mobile for Openmoko is currently a GPS-enabled projection-aware map viewer. [http://gvsigmobileonopenmoko.wordpress.com/ Homepage].<br />
* {{opkg.org|175|BikeAtor}} - Like TangoGPS BikeAtor can display OSM Maps. The Speedometer displays the most interesting values of the trip.<br />
* {{opkg.org|178|bicirutas}} - This application looks for mtb routes in www.bicirutas.net (routes in Spain, Portugal, United Kingdom, France, Italy and Germany). It gets the current position from the gps system and downloads nearby routes. Then you can follow them with tangogps application.<br />
* [http://code.google.com/p/omgps omgps] - High performance, UBX binary or ogpsd as GPS data provider, layered maps, AGPS online, track replay, scratch on map, ruler and lat/lon grid, basic sounding. etc.<br />
* [[Travel Diary]] - a simple application to save little diary entries to a csv file and send this to a server (that can generate a .kml file or show a map or do whatever...)<br />
* [[QNavitCtl]] - send coordinates to Navit via dbus (position, destination, map center)<br />
* [[a-gps GUI]] - uses cellhunter data to locate you, then uses u-blox a-gps to initialize your GPS chip<br />
* [[sms-sentry]] - locate a lost or stolen phone<br />
* [[bicirutas]] - download bicycle routes<br />
<br />
== Graphics ==<br />
<br />
* [[Orrery]] - Displays the night sky<br />
* [[OMView]] - Image viewer<br />
* [[PyPenNotes]] - Write notes using pen and touchscreen<br />
* [[Gpe-scap]] - Take screenshots<br />
* [[Flash|Gnash]]-Play flash file on Neo<br />
* [[Neon]] - Image viewer<br />
<br />
----<br />
<br />
== Internet ==<br />
===Web browsers===<br />
* [http://www.dillo.org/ Dillo] - Multiplatform fast and small web browser ([http://misc.andi.de1.cc/dillo/ .ipk]).<br />
* fennec<br />
* [[Midori]] - Webkit based web browser<br />
* [[Minimo]] - Mozilla based web browser<br />
* [http://www.netsurf-browser.org/ netsurf]-A new browser for Neo FreeRunner.<br />
* [[Openmoko-browser2]] - The original Openmoko web browser<br />
* [http://code.google.com/p/pyqt-browser/ pyqt-browser] - modified the sample code from python-pyqt4 and changed it to use webkit for web browsing. <br />
* woosh<br />
<br />
===VOIP===<br />
* [[Twinkle]] - Voice over IP<br />
* [[Linphone]] - Voice over IP<br />
<br />
===Email clients===<br />
* [[Openmoko Mail]] - E-mail client<br />
* [http://www.claws-mail.org/ claws-mail] email client available in shr-unstable<br />
* [[Qtmail]] - Default mail program on Om 2008.8<br />
<br />
===Offline wikipedia===<br />
* [[Mokopedia]] - Read small Wikipedia dumps offline<br />
* [[Offline Wikipedia reader]] - store the entire content of wikipedia (single-language, excluding images), on a single 8GB microSD card<br />
* evopedia<br />
<br />
===IM===<br />
* [[Pidgin]] - Instant messaging client (ICQ, MSN, Jabber, Yahoo and more.)<br />
* [[CenterIM]] - Instant messaging client (terminal-based).<br />
<br />
===other===<br />
* [[Openmokast]] - Play audio stream and slideshow stream<br />
* [[PyFeedRead]] - RSS feed reader<br />
* [[TwitterMoko]] - A Twitter client for Openmoko<br />
* [http://we.trekbeyond.org/~kd8ikt/moko/shr_pkgz/ ettercap-ng] DEAD LINK<br />
* {{opkg.org|205|GPRSModem}} - Converts your neo in a GPRS modem.<br />
<br />
== Office ==<br />
* dates - a simple calendar<br />
* [[e-tasks]] - An elementary task manager<br />
* [[Epdfview]] - PDF reader.<br />
* Evince - Document reader for PDF, PS, DJVU and more.<br />
* [[FBReader]] - E-book reader program (TXT, FB2, HTML and more)<br />
* [[GPE contacts]]<br />
* [[Gutenflash]] - Fast text reader by scrolling text<br />
* [[OMoney]] - A bookkeeping application<br />
* {{opkg.org|191|PISI}} - PISI is synchronizing (PIM) information<br />
<br />
== Settings ==<br />
<br />
* [[Mofi]] - Wifi setup tool<br />
* [[Mokonnect]] - Connection manager<br />
* [[Lint-wifi]] - Wifi setup tool<br />
* [[KnjMokoWifi]] - Wifi setup tool<br />
* [[KnjMokoOPKG]] - A graphical frontend to OPKG.<br />
* [[Om 2008.8 Installer]] - Graphical software installer<br />
* [[Opkg]] - Command line software installer<br />
* [[Sephora]] - Settings manager<br />
* [[SettingsGUI]] - Edit various settings<br />
* [[Wicd]] - Wifi setup tool<br />
* [[ZOMG!]] - A graphical package manager (opkg frontend -> should work on any distro)<br />
* [[Timezone|tzdata]]- Customise your time zone setting.<br />
* [[momtools]] - an application to control Wifi, gprs and some other stuff<br />
* [[Wlan]] - Wlan is an application to manage wireless connection on the Freerunner<br />
<br />
== System ==<br />
* [[Aphasia]] - A system built on Erlang and a vertical application for people with apahasia.<br />
* [http://www.pierrox.net/auimd/ AUIMD] - AUIMD is a PyQt graphical user interface for mobile devices.<br />
* [[Auxlaunch]] - Finger-friendly app launcher and window switcher<br />
* [[Display Locker]] - Screen lock<br />
* [[Gwaterpas]] - levelling tool using accelerometer<br />
* [[Gestures]] - Detect movement and display information, rotate screen<br />
* [[Keychain]] - SSH keys<br />
* [[MokoFEM]] - Monitors GSM information<br />
* [[Mokostat]] - Monitors battery<br />
* [[Openmoko Bluetooth remote controller|ReMoko]] - Control stuff via BlueTooth<br />
* [[Rotate]] - Rotate screen when phone is rotated<br />
* [[Vala-terminal]] - Command prompt with tabs<br />
* [[Ts calibrate]] - Calibrates touchscreen<br />
* [[Zedlock]] - Screen locker<br />
* [http://fso-control.projects.openmoko.org/ fso-control] - Popup Power menu to shutdown/suspend/reboot.<br />
* [[omkeys_functions]] - Remap AUX key bindings<br />
* [[Siglaunchd]] - A daemon that listens to dbus signals and launches appliactions upon arrival.<br />
* [[Pexpect]]-a pure Python module for spawning child applications; controlling them; and responding to expected patterns in their output. <br />
* {{opkg.org|253|libaxel}} - Library for easy use accelerometer.<br />
----<br />
<br />
== Telephony ==<br />
* [[Dialer/2007.2]] - The dialer application in Om 2007.2<br />
* [[Openmoko SMS Middleware]]- SMS middleware is a Openmoko middleware software for additional features related to SMS. Plugin architecture and Python based code gives this project lots of flexibility and enchancebility.<br />
* [[Paroli]] -Paroli is an integrated phone application based on Tichy (and so also written in python). <br />
* [[Litephone]] Easy to use, single window phone application written in Qt.<br />
----<br />
<br />
== Utility ==<br />
* [[Unison]] - Unison is a file-synchronization tool for Unix and Windows. It determines all differences between two directory trees and lets the user decide, how to proceed with every differing file. <br />
* [[HP48 Series RPN Calculator]] - Calculator with many functions<br />
* [[qwo]]- An alternative input method.<br />
* {{opkg.org|57|fido}} - [[fido]] is a todo list\note manager written with elementary<br />
* [http://meuk.spritesserver.nl/lightsaber-0.1.tgz The Lightsaber]. Pre-alpha starwaresque orphanware.<br />
* [[NeoTool]] NeoTool is a bash script for your desktop system to provide a friendly GUI frontend to some common management tasks.<br />
* [[NeoCon]] - neocon is a handy serial console utility (not only) for u-boot. The main feature of neocon is actually that you can give it a list of devices and it will pick one that works.<br />
* [http://techiem2.net/index.php?/archives/10-Freerunner-USB-Mode-Control-Program.html usbmode]-a quick pygtk program. <br />
* [[Enotes]] - Enotes is the implementation of a TODOlist manager written with elementary to appear better with distribution that use illume, like SHR.<br />
* [[LED clock]] - When an Openmoko is sitting unused at night, turn it into an alarm clock with large 7-segment digits on a black background in landscape mode. <br />
* [[MokoGeocaching]] - Utility for add a POI to TangoGPS using geocaching.com <br />
* [[Wrench]] - Modual used utility enlightenment_remote.<br />
* [[Yaouh!]] - Yet Another OSM Updater H.<br />
* [[ShortOm]] - Graphical launcher for shell or application, with editable config file, and log result page.<br />
* [[Pimlico]]-Pimlico is a suite of lightweight Personal Information Management (PIM) applications designed primarily for handheld and mobile devices<br />
* [http://projects.openmoko.org/projects/otp4neo/ OTP4Neo] One time password generator<br />
* [http://projects.openmoko.org/projects/ffalarms/ FFAlarm] is a program to set multiple alarms a day using a finger friendly user interface<br />
* [[OpenWrt]]-basic support for the Openmoko "Freerunner"! Kernel (2.6.28) is building and booting.<br />
* [[Enscribi]]-a handwriting recognition input method for Linux. It's mainly developed for the Openmoko Freerunner smartphone.<br />
* [[GridPad]]-GridPad is an alternative input method for entering text with your finger, a Simple Character Recognizer Software.<br />
* [[sortdesk]] sort your om-desktop in categories<br />
* [[Mokometeo]] is a widget which fetches the weather forecast from yahoo, for a list of cities<br />
* {{opkg.org|176|CoovaChilli}} - It turns your phone's WiFi network into an Ad-Hoc Hotspot!<br />
* [http://openmoko.huber-computer.de/ DWDWetter] Fetches weather information from dwd (First Register at dwd!)<br />
* [[QSuunto-Lite]] display dive log information from Suunto Dive computers (that work with divetools-ab)<br />
* [[Literki]] - alternative keyboard<br />
<br />
==Setting Application==<br />
* [[Wmiconfig]]- wmiconfig is a tool written by Atheros Communications Inc to configure the Ar6k WIFI chip used in the Neo Freerunner. This is a standalone C executable, released under GPL v2.<br />
* [[GTA02 sysfs]]- sysfs is a filesystem that is mounted on /sys which contains various fake "files" that are actually filled by a variety of drivers and other kernel subsystems. You can use it to change settings and behaviours of the kernel and drivers dynamically.<br />
<br />
== Video ==<br />
<br />
* [[Video Player]] - Using Mplayer on Openmoko smartphones.<br />
* [http://katastrophos.net/andre/blog/software/quasar-media-player/ Quasar] - a mplayer frontend for X11.<br />
<br />
<br />
<br />
<br />
----<br />
<br />
== daemon ==<br />
* [[PyPhonelog]] - daemon uses the framework to track and log all the calls made to and from the moko.<br />
* [[Lscd]] - LSC library/daemon on Linux System.<br />
<br />
== An automatic list of application-related wiki pages ==<br />
<br />
The pages linked above are all maintained manually. We also maintain an automatic categorization system by tagging wiki pages. Here is the list of application-related pages in this wiki. Normally, every page listed below should be also listed above in the same category. The converse is false: there are applications without a wiki page.<br />
<br />
<div style="border: solid 1px black; padding: 1ex"><b>Applications in this Wiki:</b><br />
<categorytree mode=pages depth=2 hideroot=on>Applications</categorytree><br />
</div><br />
<br />
<br />
== Where to find more applications? ==<br />
<br />
At [http://opkg.org opkg.org] !<br />
<br />
Not all Openmoko apps are listed on this wiki - there are much more [http://projects.openmoko.org/softwaremap/ projects at the Openmoko GForge] than the wiki can list, not to mention self-hosted applications on their own websites. Actually the phones can run most Linux based Free Software, using for example the [[Debian]] distribution. The [http://handhelds.freshmeat.net/browse/1038/ mobile phones section of Freshmeat] may be a interesting place to look.<br />
<br />
Note also that there are many packages in the repository that are not installed by default. If what you want is a classic, chances are that it is already packaged. Suppose you want to install Perl:<br />
opkg list|grep perl<br />
opkg install perl<br />
<br />
More application download related pages:<br />
<br />
* [[Community Repository]]<br />
* [[Users Repositories]]<br />
<br />
<div style="clear:both">&nbsp;</div><br />
<br />
== Where to find full distributions ? ==<br />
<br />
* [[Download]]: for complete system downloads<br />
<br />
== The usual warnings ==<br />
<small><br />
* Some of these software are developed by Openmoko Inc. and some are contributed by the community. Any problems with community contributed software should be reported to the individual software developer rather than the Openmoko core team.<br />
* Most programs listed here are not mature/stable, but only useable/beta.<br />
* Many programs listed here are not yet packaged for your distribution and integrated in its repositories. Whichever it is.<br />
* Installing experimental software from the internet is certain to break things. Running it as root is a very insecure thing to do. Kown that you will be burned, have backups, and be ready to apologize to everybody in your phone contact list in case they receive strange SMSs...<br />
</small><br />
<br />
See also [[Hall of Fame]]<br />
<br />
[[Category:Applications| ]]<br />
[[Category:Basic End User]]</div>Dareushttp://openmoko.org/wiki/Talk:Main_PageTalk:Main Page2009-09-07T11:59:18Z<p>Dareus: Undo revision 75656 by Tlissy12 (Talk) spam</p>
<hr />
<div>== Page goal ==<br />
<br />
I think the functions should be limited to:<br />
<br />
1. Orient visitors, as a large fraction of them enter by this page (bookmarkability). We separate between newcomers, users and developers, so 3 boxes here.<br />
<br />
2. Announce news and upcoming events. One box.<br />
<br />
--[[User:MinhHaDuong|MinhHaDuong]] 10:29, 1 August 2008 (UTC)<br />
<br />
== Earlier Page Design ==<br />
<br />
Earlier page design was a lot better than the current state. Why we changed to this one. We are missing so much here. Specially the new visitors wont be able to get to the all the content that this Wiki has to offer.<br />
<br />
Please revert<br />
--[[User:Kunaldeo|Kunaldeo]] 07:22, 7 August 2008 (UTC)<br />
<br />
:Thanks for the feedback! The wiki maintainers team have agreed that there was too much content on the main page, so we removed much of the content for developpers. Could you please tell us what you are missing on this page? Is there some specific content you would like to see here? We will probably be able to add it in again. --[[User:Marko Knöbl|Marko Knöbl]] 12:55, 7 August 2008 (UTC)<br />
<br />
::I can figure out everything, but I feel The complete intro section was very useful "Introduction to Openmoko,Meet the original core team, Software Distributions New Framework Initiative License, Why Openmoko?" --[[User:Kunaldeo|Kunaldeo]] 17:18, 7 August 2008 (UTC)<br />
<br />
:::I added a link to [[Why Openmoko]] in the "New to Openmoko?" box. I think this is a useful page, thanks for pointing this out! Please note that most of the section "Introduction to Openmoko" and the link to "Software Distributions" are still present. On the mailing list some have said that the contents of "Meet the original core team" and "license" are too specific for content of the main page, and I agree with that. I can't say anything about "New Framework Initiative" as I'm not a developer. Probably someone else can check if a link to this page is useful? --[[User:Marko Knöbl|Marko Knöbl]] 20:48, 7 August 2008 (UTC)<br />
<br />
== Design notes ==<br />
<br />
Please try to keep these elements in the top part of the screen (above the fold): Page title, motto, welcome statement, objective project definition, product picture, search box (not there yet !).<br />
<br />
Please try to keep also on the page (not necessarily above the fold): links to other official information sources (trac, mailing lists, etc.), language chooser, more elaborated mission statement (historical overview), philosophical position, top level navigation within the wiki.<br />
<br />
--[[User:MinhHaDuong|MinhHaDuong]] 10:29, 1 August 2008 (UTC)<br />
<br />
Please keep the language chooser on the top of the page.<br />
<br />
Consider that not all the people in the world are familiar with English. An only-English wiki is considered as an index of a poor project. Please read my comment on the Translation point.<br />
<br />
Thank you<br />
<br />
--[[User:Panta|Panta]] 22:59, 25 August 2008 (UTC)<br />
<br />
== 2007.2 link ==<br />
<br />
In the software categories<br />
The link to the 2007.2 distribution goes to a picture of the software stack. That is not very appealing. Maybe this link should point to a software description (as the link to ASU, FSO, Qtopia does).<br />
<br />
--[[User:Feydreva|Feydreva]] 11:20, 1 August 2008 (ET)<br />
<br />
:Thanks for pointing this out! I changed the link. --[[User:Galadh|Galadh]] 22:23, 3 August 2008 (UTC)<br />
<br />
== Nav Bar on left ==<br />
<br />
The Nav bar on the left is out of date, incorrect and has duplications.<br />
<br />
Software is linked to a Developers page?<br />
There are two community links/<br />
There is a Press Coverage on the left and in the new part<br />
What exactly is Technical, the whole site is technical.<br />
<br />
There are many more items that make the nav bar on the left confusing, unproductive, incorrect and it needs to be fixed or wacked. Brenda seems to be attached to it or afraid to change it as this has come up before and all we got were lame excuses as to why it is like it is.<br />
<br />
Please change it or remove it.<br />
<br />
:I've made a few suggestions to the sidebar on [[MediaWiki_talk:Sidebar | its talk page]]. I think this discussion is probably best kept there. --[[User:Kbjorgensen|KB Jørgensen]] 19:11, 25 August 2008 (UTC)<br />
<br />
== Translations ==<br />
<br />
The continuous updating of pages result as an impossible-to-solve game to people who likes to localize wikie's pages.<br />
<br />
Also, people visiting the site, may find outdated pages, thinking the project is dead or not so alive.<br />
<br />
Please, consider to use a translation friendly wiki like anwiki (www.anwiki.com) used for build Ulteo's site (www.ulteo.com).<br />
<br />
Alternatively, you can consider to find a way to comunicate to guests and translators if a page is outdated or not and put a link to the right english page.<br />
<br />
Thank you and excuse my poor english: I can assure you I speak a more correct italian ;)<br />
--[[User:panta|panta]] 11:17, 5 August 2008 (UTC)<br />
<br />
I have added language Hindi in the template, but its not getting reflected here.<br />
--[[User:Kunaldeo|Kunaldeo]] 08:39, 23 October 2008 (UTC)<br />
<br />
It takes a while for template changes to propagate, [http://www.mediawiki.org/wiki/Manual:Job_queue the mediawiki engine is not completely synchronous]. [[User:MinhHaDuong|MinhHaDuong]] 10:46, 23 October 2008 (UTC)<br />
<br />
== Love the new design! ==<br />
<br />
Looks great!<br />
<br />
== Link to Jokes ==<br />
<br />
I think the link to [[Jokes]] does not fit the box "New to Openmoko?". People who are new to this project won't get most of these jokes. May I delete this link? --[[User:Marko Knöbl|Marko Knöbl]] 11:20, 10 December 2008 (UTC)<br />
<br />
I deem the link frontpage worthy because humor a good way to go deeply to the heart of things that can hardly be said otherwise (but not sidebar worthy of course it is not an essential navigation page). I added the link in that box because it belongs somewhere visible and I had no idea as to where else to put it, so any alternative placement suggestion should be considered. And it is true that even I don't get all the jokes, but newbies should get about half of them if they have the geek hacker subculture. What do you other guys think ? [[User:MinhHaDuong|MinhHaDuong]] 14:57, 10 December 2008 (UTC)<br />
<br />
:Thanks for your explanation! If we really want this on the main page I'd rather put it into the "for Users" box under "Openmoko community". Would that be okay? --[[User:Marko Knöbl|Marko Knöbl]] 13:02, 12 December 2008 (UTC)<br />
<br />
::I've just moved it. I hope it's okay.--[[User:Marko Knöbl|Marko Knöbl]] 09:53, 20 December 2008 (UTC)<br />
<br />
== Boasting freedom ==<br />
<br />
I think it would be a good idea to provide a link near the top where people can learn more about the 'freedom' that's boasted about. Many site visitors (including GNU/Linux users) will not be aware of the benefits and importance of what we mean by "freedom" for software users.<br />
<br />
Descripts of "rebuild the house" and linking "open source" to a page about getting source code are ways to get programmers interested, but I think it would be very unlikely for a non-hacker visitor to openmoko.org to discover how giving source code to hackers helps them, and why software freedom affects their lives.<br />
<br />
The no-work way to fix this would be to make the big word "free", or an eary mention of "freedom", a link to an existing explanation such as gnu.org's[http://www.gnu.org/philosophy/free-sw.html] or FSFE's.[http://fsfeurope.org/documents/freesoftware]<br />
<br />
When someone has time, this could be replaced with a page on openmoko.org with a more specific explanation of how why freedom is essential for mobile phones and mobile computing, and what benefits this leads to. [[User:Ciaran|Ciaran]] 23:22, 5 January 2009 (UTC)<br />
<br />
== duel licensing ==<br />
<br />
Any plans to duel license the wiki content under both CC-by-sa and GFDL?? Perhaps?????????? [[User:Wikademia|Wikademia]]</div>Dareushttp://openmoko.org/wiki/CellhunterCellhunter2009-08-19T08:52:28Z<p>Dareus: /* Summary */</p>
<hr />
<div>'''Cellhunter''' is set up like a game to find GSM network cells. Your provider has transmitters at many different locations in country. Your mobile phone connects to this transmitters. A GSM network cell is an area, in which your mobile phone connect to a certain transmitter, that is responsible for this GSM network cell.The identification of the network cells and the strength of signal in different locations of the GSM network cells are available data on your Freerunner (mobile phone). The project has the objective to collect the GPS location of GSM network cells.<br />
<br />
You collect points for finding and uploading especially new GPS locations of GSM network cells.<br />
<br />
If this project is finished, then the rough GPS location can be identified just by calculating the current distances (strength of signals) to the currently used GSM phone network cells and other available GSM network cells (GSM network cell neigbours are available for the phone but not used for communication at the moment, maybe later, when you move to an other GSM cell).<br />
<br />
===Advantages of the Cellhunter Data===<br />
The big advantage is, that the rough location can be retrieved even when there are GPS satellites are not available (e.g. in a building).<br />
<br />
GPS information are more precise. The freerunner has determine 3 options to locate and determine changes in the location:<br />
* Location via GPS Receiver -> most detailled information on location<br />
* Location via GSM Cell identification (Cellhunter will provide a major contribution to this)<br />
* Changes in location by calibrating the accelerometer (see [[Technical:Accelerometer Fundamentals]]) in car for GPS changes during the time in which satellites are available and application of accellerometer in a tunnel where no GSM network cell information and no GPS satellite information are available.<br />
<br />
Car navigation systems like Navit on the Freerunner get the GPS location via the GPS daemon. The results of cellhunter could help to improve the GPS daemon, so that a rough GPS location can be send to [Navit] even if the is no GPS satellite information available. The advantage is, that the applications like [[Navit]] or [[TangoGPS]] do not have to be change.<br />
<br />
===GPSD and Accuracy (suggestion for further implementation)===<br />
Accuracy of the signal should be later available may be on an other GPSD port so that applications can make use of that (Accuracy: GPS, GSM, ACCEL or a real value from 0 location not available and 1 exact information on location.<br />
<br />
===GSM cells and GSM Cell Neighbours===<br />
The current GPS location of phone (Freerunner with SHR distro) provides to the CellHunter a GSM network profile of the currently used GSM network cells and its neighbours. This collected information is especially valuable for road segments where GSM network connection is available and no GPS satellites are available.<br />
<br />
===Cellhunter Profile of road segments with GSM and without GPS connection===<br />
Lets consider a road connection between A and B with GPS satellite connection in A and B and no satellite connection between A and B (e.g. a tunnel or very narrow road with high buildings around). <br />
<br />
The GPS location (4452 N 1129 E) can be mapped to profile of available GSM network cells<br />
(e.g. ''GSM Cell 1'' will strength ''s<sub>1</sub>'', ... ,''GSM Cell 4'' will strength ''s<sub>4</sub>''). The profiles can be normalized to values between 0 and 1 so that they can be compared better. 1 is the value of the cell with the strongest signal, that is used for the current GSM network connection to your provider. 0 is a strength of a signal to a neighbour cell that is not available. Only GSM Cell IDs are part of the '''GSM network location profile''' that have a value greater than 0.<br />
<br />
Driving from A to B and collecting the accelerometer info GPS speed before an location A. This is used for estimating the location without GPS data in between A and B.<br />
The collection of the accelerometer info is additional information for determining changes in the speed. Best would be a constant speed from A to B for mapping the GSM network profile between A and B. The location can be retrieved by mapping the current connection profile to GSM network cells to the collected data of GPS location.<br />
<br />
Calibrating of the accelerometer is necessary according to driving direction, because accelerometer data is dependent on position of freerunner (e.g. lying or upright position of phone). <br />
<br />
[[Image:Cellhunter.png|left]]<br />
<br />
===Summary===<br />
CellHunter is just a game at the moment, to find a maximum of unknown ID of GSM network cells, <br />
which you can play in groups to [http://78.47.116.33/~hole/cellhunter/ collect points] jointly.<br />
The objective is to collect GSM cell IDs with the GPS location (GPS mapping to GSM Cell profile).<br />
<br />
Even it is designed as a game, it has a great potential for improving car navigation systems. <br />
<br />
Further Information can be found at http://cellhunter.omoco.de<br />
<br />
<br />
CellHunter is available in German and English.<br />
<br />
<br />
Screenshots:<br />
<br />
[[Image:Cellhunter_0_2_0_welcome_german.png|240px]]<br />
[[Image:Cellhunter_0_4_1_screenshot_deutsch.png|240px]]<br />
<br />
[[Category:GPS Applications]]<br />
[[Category:GSM]]</div>Dareushttp://openmoko.org/wiki/FSO_ResourcesFSO Resources2009-08-18T07:53:16Z<p>Dareus: /* Automatic way */</p>
<hr />
<div>== Resource management conception ==<br />
<br />
Here goes some introductory text shamelessly borrowed from [http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/usage-intro.html;hb=HEAD FSO specs].<br />
<br />
One of the most important aspects of middleware for mobile devices is saving energy. To do this, the system needs to make sure that peripherals are only powered when they are actually in use by at least one application. In order to support multiple concurrent applications, it is not possible to leave peripheral control up to individual applications — otherwise one application could shut down e.g. a GPS receiver, while another application still wants to access it.<br />
<br />
FSO introduces the concept of resources. A resource is a high-level entity with a name and a state. The name is used to identify a resource (e.g. WiFi), the state is describing its condition (e.g. enabled). It is important to understand that a resource not necessarily correlates to a peripheral device. Although enabling a resource such as Bluetooth most likely has the consequence of powering up a device, there may as well be more to it, such as launching a low level device handling services or allocating related resources.<br />
<br />
=== Resource Policies ===<br />
<br />
Once in a while, reference counted handling of resources gets in your way, for example when you are running legacy applications or want to configure or debug peripherals. In that case it may become necessary for a resource to be always enabled or always disabled. While not recommended, it is possible to switch from automatic resource control to manual control by calling SetResourcePolicy. Valid values are auto (which is the default on system startup), enabled, and disabled.<br />
<br />
== List of FSO resources ==<br />
=== WiFi ===<br />
Unless this resource is enabled you've no eth0 and wifi module is completely unpowered.<br />
<br />
=== Display ===<br />
While this resource is kept the display won't be blanked.<br />
<br />
=== TEST ===<br />
A test resource<br />
<br />
=== Bluetooth ===<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
=== GSM ===<br />
The same for GSM modem<br />
<br />
=== CPU ===<br />
Default rules.yaml checks for this resource to disable automatic suspend when it's requested.<br />
<br />
=== GPS ===<br />
Same idea as WiFi/Bluetooth<br />
<br />
== Resource management ==<br />
It would be nice to have a command to list the current state of all<br />
resources. Unfortunately, such an utility is yet to be written. See [http://trac.freesmartphone.org/ticket/461]. First take on implementing the desired functionality can already be downloaded from [http://trac.freesmartphone.org/raw-attachment/ticket/461/lsfsor.py].<br />
<br />
=== Manual way ===<br />
With the help of SHR Settings or an appropriate [[OpenmokoFramework/mdbus|mdbus]] call (example: <code>mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy Bluetooth enabled</code>) you set resource policy to "enabled". Do not forget that way you'll lose power since it will leave the corresponding device powered all the time.<br />
<br />
Be aware this is "throwing switch the hard way". If you set policy to "disabled" then is IS disabled. Same for "enabled".<br />
<br />
So this method is highly deprecated as long as you don't know *exactly* what you do.<br />
<br />
=== Automatic way ===<br />
Use the <code>fsoraw</code> (created per Joerg's request [http://trac.freesmartphone.org/ticket/393]) utility. With it you can automatically request the necessary resource before starting a command and release it when it's finished (<em>this will happen even if it was killed with SIGKILL</em>).<br />
<br />
Typical basic use:<br />
fsoraw -r CPU,Display mokomaze<br />
Start a game (or any other app) and avoid auto-suspend and display-blank<br />
<br />
Especially recommended for WiFi since due to the bugs in the firmware and the driver full power-cycle of the module is often advantageous.<br />
<br />
Example command (works for open, WEP and WPA/WPA2 networks, automatically determining the network it can connect to, just add all the networks you use to the config):<br />
fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf<br />
due to bug still present currently you need to also do to keep wifi useable<br />
rmmod ar6000 && modprobe ar6000<br />
<br />
Bluetooth scan for nearby devices example:<br />
fsoraw -r Bluetooth -- bash -c "sleep 1; hcitool scan"<br />
<br />
[[Category:FSO]]</div>Dareushttp://openmoko.org/wiki/Configure_Om_2009_for_Austrian_useConfigure Om 2009 for Austrian use2009-08-16T09:10:25Z<p>Dareus: /* Startup */</p>
<hr />
<div>== Installing ==<br />
* have at least 1 hour of time ready, for the whole procedure<br />
* download exactly these versions of '''[[Om 2009]]''' from z0ph<br />
'''1.''' [http://work.zoff.cc/openmoko/om2009/de_at/qi.udfu] qi boot loader<br />
<br />
'''2.''' [http://work.zoff.cc/openmoko/om2009/de_at/uImage-2.6.28.bin] kernel (kernöl)<br />
<br />
'''3.''' [http://work.zoff.cc/openmoko/om2009/de_at/rootfs.jffs2] root image<br />
<br />
<br />
these are the original names of the files:<br />
<br />
qi-s3c2442-1.0.2+gitr3b8513d8b3d9615ebda605de4bda18371aa3f359.udfu<br />
<br />
fso-paroli-image-om-gta02.jffs2 (daily testing image from 16-Jun-2009 04:35 88M)<br />
<br />
uImage-2.6.28-stable+gitr0+f19f259d3c1afde8eae53983fd19f61831927413-r3-om-gta02.bin<br />
<br />
<br />
* download customize pack from z0ph<br />
'''4.''' [http://work.zoff.cc/openmoko/om2009/de_at/customize_pack.tar.gz] customize pack <br />
* if you want it quick, you can instead download customize pack[http://work.zoff.cc/openmoko/om2009/de_at/customize_pack_no_maps.tar.gz] without navit maps, its much smaller<br />
* flash '''[[qi]]''', '''[[kernel]]''' and root image to your neo (i tested this on '''[[GTA02]]'''v6). Detailed instructions for [[Flashing_the_Neo_Freerunner|Freerunner]]<br />
* unpack the customize pack to your SD-Card (to /media/card). don't do this under windows!! or your execute bits will get lost (you have been warned)<br />
<br />
== Startup ==<br />
* boot up your neo, and let it run until paroli has logged in to your GSM net<br />
* then shutdown the neo (press and hold power button for a few seconds)<br />
* boot up your neo again, and let paroli log in to your GSM network again.<br />
<br />
== Localize for AT ==<br />
* for '''GOD's sake try NOT to get any phonecalls''' while you do this part<br />
* if at ANY time you get messages "would you like to unload this module, bla bla" just press "yes" !!<br />
* now connect your neo with usb and login via ssh<br />
* start (as root on your neo):<br />
<br />
cd /media/card/<br />
./init_om2009.sh<br />
<br />
* this will take some time !! have coffee ready :-)<br />
* just before this script is done, you have to comfigure [[E17]] again.<br />
# select "Deutsch" als language (then press next)<br />
# select "paroli-serenity" as profile (then press next)<br />
# select "systemstandard" as menüs (then press next)<br />
# don't checkbox any applications in Quick Launch (then press next)<br />
* now wait for the customize script to finish<br />
* hopefully no errors have occured<br />
<br />
== Test it ==<br />
* reboot your neo, and let paroli settle down and login to your GSM network<br />
* now navit should have austrian maps, and speak in german to you :-)<br />
* date and time should also be correct<br />
<br />
== Feedback ==<br />
* please give some feedback, even if you don't like it<br />
<br />
== Upgrade (for the brave) ==<br />
* if you are brave you can try now<br />
opkg update<br />
opkg upgrade</div>Dareushttp://openmoko.org/wiki/Configure_Om_2009_for_Austrian_useConfigure Om 2009 for Austrian use2009-08-16T09:09:57Z<p>Dareus: /* Installing */</p>
<hr />
<div>== Installing ==<br />
* have at least 1 hour of time ready, for the whole procedure<br />
* download exactly these versions of '''[[Om 2009]]''' from z0ph<br />
'''1.''' [http://work.zoff.cc/openmoko/om2009/de_at/qi.udfu] qi boot loader<br />
<br />
'''2.''' [http://work.zoff.cc/openmoko/om2009/de_at/uImage-2.6.28.bin] kernel (kernöl)<br />
<br />
'''3.''' [http://work.zoff.cc/openmoko/om2009/de_at/rootfs.jffs2] root image<br />
<br />
<br />
these are the original names of the files:<br />
<br />
qi-s3c2442-1.0.2+gitr3b8513d8b3d9615ebda605de4bda18371aa3f359.udfu<br />
<br />
fso-paroli-image-om-gta02.jffs2 (daily testing image from 16-Jun-2009 04:35 88M)<br />
<br />
uImage-2.6.28-stable+gitr0+f19f259d3c1afde8eae53983fd19f61831927413-r3-om-gta02.bin<br />
<br />
<br />
* download customize pack from z0ph<br />
'''4.''' [http://work.zoff.cc/openmoko/om2009/de_at/customize_pack.tar.gz] customize pack <br />
* if you want it quick, you can instead download customize pack[http://work.zoff.cc/openmoko/om2009/de_at/customize_pack_no_maps.tar.gz] without navit maps, its much smaller<br />
* flash '''[[qi]]''', '''[[kernel]]''' and root image to your neo (i tested this on '''[[GTA02]]'''v6). Detailed instructions for [[Flashing_the_Neo_Freerunner|Freerunner]]<br />
* unpack the customize pack to your SD-Card (to /media/card). don't do this under windows!! or your execute bits will get lost (you have been warned)<br />
<br />
== Startup ==<br />
* boot up your neo, and let it run until paroli has logged in to your GSM net<br />
* then shout neo down (press and hold power button for a few seconds)<br />
* boot up your neo again, and let paroli log in to your GSM network again.<br />
<br />
== Localize for AT ==<br />
* for '''GOD's sake try NOT to get any phonecalls''' while you do this part<br />
* if at ANY time you get messages "would you like to unload this module, bla bla" just press "yes" !!<br />
* now connect your neo with usb and login via ssh<br />
* start (as root on your neo):<br />
<br />
cd /media/card/<br />
./init_om2009.sh<br />
<br />
* this will take some time !! have coffee ready :-)<br />
* just before this script is done, you have to comfigure [[E17]] again.<br />
# select "Deutsch" als language (then press next)<br />
# select "paroli-serenity" as profile (then press next)<br />
# select "systemstandard" as menüs (then press next)<br />
# don't checkbox any applications in Quick Launch (then press next)<br />
* now wait for the customize script to finish<br />
* hopefully no errors have occured<br />
<br />
== Test it ==<br />
* reboot your neo, and let paroli settle down and login to your GSM network<br />
* now navit should have austrian maps, and speak in german to you :-)<br />
* date and time should also be correct<br />
<br />
== Feedback ==<br />
* please give some feedback, even if you don't like it<br />
<br />
== Upgrade (for the brave) ==<br />
* if you are brave you can try now<br />
opkg update<br />
opkg upgrade</div>Dareushttp://openmoko.org/wiki/Talk:MdbusTalk:Mdbus2009-08-16T09:07:32Z<p>Dareus: /* Strange proble */</p>
<hr />
<div>I like tutorials, but I have not found proper place to highlight interesting tutorials:<br />
<br />
==making a phone call==<br />
(from discussion of Sten Kvamme and Michael 'Mickey' Lauer at devel malinglist)<br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.Resource.Enable<br />
</pre><br />
<br />
This will not work, since mdbus will register to the bus and vanish right <br />
afterwards, meaning the resource will be released immediately (if noone else <br />
has requested it). Try setting the policy to always-enabled:<br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage<br />
org.freesmartphone.Usage.SetResourcePolicy "GSM" "enabled"<br />
</pre><br />
<br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.GSM.Device.SetAntennaPower boolean:True<br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.GSM.Network.Register<br />
</pre><br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/Phone \<br />
org.freesmartphone.Phone.CreateCall string:0123456789 \<br />
string:GSM boolean:True<br />
</pre><br />
<br />
should work -- although I'd rather use the ogsmd subsystem here, in which case it would be:<br />
<br />
<pre><br />
mdbus -s -org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.GSM.Initiate "+49123456789" "voice"<br />
</pre><br />
<br />
<br />
==Realtime clock==<br />
<pre><br />
#!/usr/bin/env python<br />
<br />
import dbus<br />
import time<br />
<br />
# Wakeup in 60 seconds<br />
wakeuptime=str(time.time()+60)<br />
<br />
system_bus = dbus.SystemBus()<br />
<br />
rtc_object = system_bus.get_object('org.freesmartphone.odeviced', '/org/freesmartphone/Device/RealTimeClock/0')<br />
rtc_interface = dbus.Interface(rtc_object, dbus_interface='org.freesmartphone.Device.RealTimeClock')<br />
rtc_interface.SetWakeupTime(wakeuptime)<br />
</pre><br />
<br />
==Strange problem==<br />
<br />
I'm on latest SHR unstable and I'm having some problems using dbus (mdbus too). Every time I mdbus -s something it prints some lines like this<br />
<br />
Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged<br />
<br />
I don't know what to do to keep using mdbus, because this is pretty annoying.<br />
<br />
[[User:Dareus|Dareus]]</div>Dareushttp://openmoko.org/wiki/FAQ/itFAQ/it2009-08-16T08:54:45Z<p>Dareus: /* Q: Qual'è la logica dietro l'esclusione del WiFi? */</p>
<hr />
<div>Domande e Risposte che sembrano non trovarsi in nessuna categoria.<br />
<br />
== Introduzione == <br />
<br />
=== Q: Cos'è Openmoko e Neo1973? ===<br />
A: Openmoko è una piattaforma software, un tentativo di creare il primo stack software per cellulari totalmente aperti del mondo. Il [[FIC]] [[Neo1973]] è il primo telefono Openmoko completamente supportato.<br />
<br />
=== Q: Dove posso comprare un [[Neo1973]]? ===<br />
<br />
A: 'Quando è pronto' per gli sviluppatori, settembre per il mercato di massa - Vedere [[Neo1973]] per le info più aggiornate. [[Neo1973]] sarà diffuso ovunque. Ci sarà anche [http://lists.openmoko.org/pipermail/community/2007-January/001216.html distribuzione nell'UE].<br />
Per essere informato di quando è disponibile, '''iscriviti''' a [http://lists.openmoko.org/mailman/listinfo/announce la mailing list di annunci].<br />
<br />
=== Q: Quanto? === <br />
<br />
A: $350 per il Developer's Kit - Fase 1. Comprende:<br />
<ul><br />
<li>Il telefono Neo1973</li><br />
<li>Batteria</li><br />
<li>Headset</li><br />
<li>Caricatore</li><br />
<li>Custodia di trasporto</li><br />
<li>Stiletto</li><br />
<li>Cordicella</li><br />
<li>Scheda 512 MB MicroSD</li><br />
<li>Cavo USB per connessione</li><br />
<li>Garanzia e manuale di istruzioni</li><br />
</ul><br />
<br />
$75 per il Car Kit. Include:<br />
<ul><br />
<li>Montaggio sul parabrezza e supporto per il dispositvo</li><br />
<li>Caricatore per auto</li><br />
<li>Antenna esterna</li><br />
</ul><br />
<br />
$200 per il Hacker's Lunchbox. Comprende:<br />
<ul><br />
<li>Sviluppo/[[Debug_Board_v1/it|Board di debug]]</li><br />
<li>Batteria</li><br />
<li>Caricatore per la scheda di sviluppo</li><br />
<li>FPC (per connettersi alla porta jtag)</li><br />
<li>Strap da spalla</li><br />
<li>Cavo debug (USB)</li><br />
</ul><br />
<br />
=== Q: Cosa farà? ===<br />
<br />
A: Il cellulare Fase 1 presto disponibile è solo per gli sviluppatori. Non è adatto agli utenti finali, avrà delle funzionalità d base come un telefono con touchscreen. Poche altre cose funzioneranno, lo sviluppo del software continuerà fino al rilascio per il mercato globale.<br />
<br />
Gli interessati dovrebbero:<br />
<br />
* Sapere che ci sarà un dispositivo con una cpu più veloce, sistema gsm etc. 6 mesi dopo<br />
* Divertirsi ad hackerare i dispositivi.<br />
* Essere in grado di districarsi nei prototipi software e hardware senza troppa documentazione.<br />
* Condividere il sogno di un dispositivo libero.<br />
* Non aspettarsi un dispositivo a livello di consumatore.<br />
* Avere nuove idee per esplorare l'era dell'informatica mobile<br />
* Avere 350 dollari.<br />
<br />
Idealmente dovrebbero anche:<br />
<br />
* Potere trovare bugs e inviare patch.<br />
* Adorare collaborare con una comunità migliorando il software.<br />
<br />
== Software ==<br />
<br />
=== Q: Può il software fare/connettersi a... ===<br />
A: Al momento, la risposta è praticamente sempre no. Il cellulare è al momento una piccola box linux con un touchscreen, un dialer funzionante e qualche applicazione di test.<br />
La maggior parte non funziona in nessun modo che sarebbe adeguato agli utenti.<br />
Se vuoi aggiungere una funzione o una richiesta, allora guarda le applicazioni esistenti o aggiungine una, o aggiungi la richiesta alla pagina delle applicazioni.<br />
<br />
=== Q: C'è una lista e una descrizione del software Openmoko? ===<br />
<br />
A: Guarda [[Openmoko/it|Openmoko]] e [[OpenmokoFramework/it|OpenmokoFramework]]<br />
<br />
=== Q: E' completamente libero/open source? ===<br />
<br />
A: Il [[Gpsd]] in userspace userà il plugin binario per [[:Category:Neo1973 Hardware#AGPS|Hammerhead AGPS]] e [[:Category:Neo1973 Hardware#GSM.2FGPRS|il modem GSM]] è un sottosistema a parte attaccato a S3C2410 UART1. Altrimenti è completamente libero. Vedi [[MokoMakefile/it|MokoMakefile]] e [[Development resources/it | Risorse di sviluppo]].<br />
<br />
=== Q: Come installo e gestisco software su Openmoko? ===<br />
<br />
A: ipkg: http://handhelds.org/moin/moin.cgi/Ipkg<br />
<br />
=== Q: Posso compilare programmi per il Neo1973? ===<br />
<br />
A: Leggi [[Toolchain/it|Toolchain]].<br />
<br />
=== Q: C'è un emulatore disponibile per Openmoko? ===<br />
<br />
*XorA pensa che se la tua prima domanda è "c'è un emulatore"<br />
allora non hai mai sviluppato nulla :-)<br />
<br />
====QEMU====<br />
QEMU può ora emulare il Neo1973. Il [[MokoMakefile]] ha il supporto per costruire, flashare e eseguire automaticamente [[Openmoko under QEMU/it|l'emulatore Neo1973]].<br />
<br />
“make qemu” creerà qemu-neo1973, scarica le ultime immagini ufficiali di openmoko, le inserisce in un flash NAND virtuale ed esegue l'emulatore.<br />
<br />
====Xoo====<br />
Un altro è [http://projects.o-hand.com/xoo Xoo]. Koen dice: "Xoo dovrebbe andare bene per la maggior parte delle applicazioni che saranno sviluppate, dato che non hanno bisogno di accedere direttamente al gsm uart. Se sei tosto potresti usare qemu + xoo, ma questo non emulerà comunque tutti i dettagli hardware (ad esempio l'accesso disallineato)".<br />
<br />
Aggiornamento: Stefan Schmidt ha ridimensionato il [[Neo1973/it|Neo1973]] Mock-up e ha scritto una piccola descrizione per Xoo. Con parole sue:<br />
<br />
Non è affatto realmente usabile, dato che ti serve una risoluzione dello schermo davvero alta per far entrare l'intera immagine sullo schermo. E ovviamente il dpi è sbagliato. Nemmeno i bottoni perchè non riesce a ricordare dove si trovano.<br />
<br />
http://www.datenfreihafen.org/~stefan/OpenMoko/neo1973-xoo-device.tar.bz2<br />
<br />
Esegui con 'xoo --device /path/to/neo1973.xml'<br />
<br />
Alcuni dettagli maggiori [[Getting_Openmoko_working_on_host_with_Xoo/it|qui]].<br />
<br />
====Xephyr====<br />
O usare Xephyr direttamente con programmi compilati localmente (come matchbox da svn + openmoko):<br />
Xephyr -screen 480x640 -nolisten tcp -ac :1 &<br />
export DISPLAY=:1<br />
export LD_LIBRARY_PATH=/usr/local/lib<br />
matchbox-window-manager -display $DISPLAY -use_titlebar no \<br />
-use_super_modal yes -use_lowlight yes -use_dialog_mode static \<br />
-use_cursor yes &<br />
matchbox-panel --geometry=480x44 --end-applets=clock &<br />
openmoko-footer &<br />
openmoko-taskmanager &<br />
<br />
=== Q: Dove posso trovare tutorial tipo per un 'Hello, world' su Openmoko? ===<br />
<br />
A: Questo dovrebbe introdurti bene:<br />
http://www.gtk.org/tutorial/<br />
<br />
=== Q: Le applicazioni PalmOS possono essere portate su Openmoko? ===<br />
<br />
A: Fare sì che app normali scritte per l'OS "Garnet" girino su Linux non è poi così difficile. Un emulatore per questo sta per far parte della piattaforma ACCESS di Linux.<br />
<br />
Le apps PalmOS generalmente sono molto difficili da 'portare'. Alcuni programmi particolari fatti bene lo possono rendere possibile.<br />
<br />
L'ACCESS Linux Platform comprenderà POSE, un emulatore che emulerà un dispositivo palmare su una macchina Linux. Quest'emulatore è in giro da tempo; ci si aspetta che andrà anche su Openmoko, ma è stata considerata una scorciatoia a breve termine piuttosto che una soluzione duratura.<br />
<br />
=== Q: Ha Java? ===<br />
A: Lo potrà avere, se ci aiutate a farlo funzionare. Alcuni buoni punti per dare un'occhiata possono essere [http://projects.openmoko.org/projects/java-pkg/ projects.openmoko.org] e [https://phoneme.dev.java.net/ PhoneME].<br />
<br />
=== Q: Quali sono le parti X11 importanti? ===<br />
<br />
A: Leggi il [http://lists.openmoko.org/pipermail/community/2007-January/001353.html xdpyinfo output].<br />
<br />
=== Q: Openmoko gira su un altro hardware? ===<br />
<br />
Puoi eseguirlo su un [[How_to_run_Openmoko_Apps_on_PC/it|PC]]. Si sta lavorando su [http://www.datenfreihafen.org/~stefan/weblog//archives/2007/02/#e2007-02-18T15_27_07.txt OpenEZX e HTC]. Adesso ha il supporto per [http://dominion.kabel.utwente.nl/koen/cms/openmoko-running-on-an-ipaq iPaq hx4700] e [http://hackndev.com/node/701 Palm TX].<br />
<br />
=== Q: Quali sono i requisiti hardware per girare Openmoko? (Andrà su IXI?) ===<br />
<br />
=== Q: Invece perchè non sviluppate sulla piattaforma Maemo? ===<br />
<br />
Dato che non posso parlare per il team Openmoko, vale la pena di far presente che maemo è una risoluzione solo fissa. Ovvero, ho sentito, cambierà nel futuro, ma non adesso. Il layout attuale di Maemo è inoltre ottimizzato per grandi schermi, non per quelli molto piccoli. La maggior parte delle apps Maemo di terze parti che esistono dovranno essere modificate per lavorare su dimensioni diverse. Infine, una quantità di componenti software del Nokia 770 e N800 non sono a sorgente aperto. --gopi<br />
<br />
In aggiunta, secondo la Nokia, Maemo è progettata per portare l'esperienza di un desktop su un tablet Internet. Molti paradigmi desktop semplicemente non funzionano su un cellulare. Comunque, condividiamo davvero molto della tecnologia di base (gtk, dbus, eds, gconf, per dirne alcuni) con Maemo, quindi in definitiva non è un team per reinventare la ruota.<br />
<br />
=== Q: Sarà possibile usare le comuni applicazioni VoIP come Skype sulla piattaforma Openmoko? ===<br />
<br />
A: Forse. Problemi hardware significa che non funzionerà bene sul Neo1973. (la latenza tipica del GPRS è troppo alta). Inoltre, Skype è un'applicazione a sorgente chiuso, che non fornisce binari che sono adatti per Openmoko. I venditori di Skype ovviamente potrebbero scegliere di fornire binari per i telefoni Openmoko. Comunque, molti termini di servizio dei provider telefonici precludono l'utilizzo del VoIP sulla linea dei loro servizi GSM.<br />
<br />
=== Q: Stessa domanda per applicazioni di Instant Messaging come MSN Messeger ===<br />
<br />
A: Molto probabile. MSN anche è closed source ma ci sono molte implementazioni aperte (molte delle quali hanno un'architettura di plugin e supportano anche l'uso di più di un protocollo IM, persino simultaneamente) come ad esempio GAIM (ora Pidgin) per IM. Il GPRS sicuramente comporta una discreta quantità di lag ma non dovrebbe essere un problema per una semplice chat testuale fra due utenti.<br />
<br />
== Neo1973 Hardware == <br />
<br />
=== Q: C'è una descrizione dell'hardware [[:Category:Neo1973 Hardware | Neo1973]] ? ===<br />
<br />
A: Leggi [[:Category:Neo1973 Hardware | Neo1973 Hardware]] e [[Disassembling Neo1973/it|Disassembling Neo1973]]<br />
<br />
=== Q: E le sue dimensioni? ===<br />
<br />
A: 120.7 x 62 x 18.5 mm, Enterà tutta in una lattina di coca-cola. (4.75 * 2.4 * 0.72 ")<br />
<br />
=== Q: Quanto pesa? ===<br />
<br />
A: 185g, (6.5 once).<br />
<br />
=== Q: Ha una fotocamera? ===<br />
<br />
A: No, vedere [[:Category:Neo1973 Hardware | Neo1973]] per dettagli di cosa include (e [[Wish List - Hardware]] per ciò che si vuole nel futuro.) Vedere anche [[FAQ/it#USB]].<br />
<br />
=== Q: Qual è la logica dietro l'esclusione del WiFi? ===<br />
<br />
A: Non era disponibile nessun dispositivo WiFi open source che consumasse poco quando il cellulare fu progettato. Un dispositivo WiFi chiuso sarebbe stato restrittivo per sviluppatori e utenti. Vedi anche [[FAQ/it#USB]].<br />
<br />
Vedere anche:<br />
I [http://lists.openmoko.org/pipermail/community/2006-November/000050.html commenti] di [[Sean Moss-Pultz]]<br />
<br />
[[Neo1973|Phase 1+]] potrà includere il WiFi [[WiFi_support_in_Openmoko/it|se si trova un chipset adatto]].<br />
<br />
=== Q: Ha il bluetooth? ===<br />
<br />
A: Si!<br />
<br />
=== Q: E' venduto con uno stiletto? ===<br />
<br />
A: Si, ma non c'è nessun supporto di sostegno sul telefono per questo.<br />
<br />
<br />
=== Q: Dove sono i bottoni? ===<br />
<br />
Il bottone di accensione è piccolo e circolare, appena accanto al connettore USB. [[Neo1973 Power button/it|Neo1973 Power button]] il bottone Ausiliario è rettangolare in alto a sinistra del telefono. (su telefoni neri assomiglia ad una porta IRDA). [[Neo1973 AUX button/it|Neo1973 AUX button]]<br />
<br />
=== Q: Come inserisco testo?? ===<br />
<br />
A: Usa l'applicazione di tastiera fornita.<br />
<br />
A: Usa la tastiera bluetooth.<br />
<br />
A: Per altre tecniche ed idee leggi [[Wishlist:Text_Input]].<br />
<br />
=== Q: Posso registrare chiamate e/o eseguire file audio durante le telefonate? ===<br />
<br />
A: Si, il percorso audio da GSM verso/dal microfono e le casse è completamente controllabile dall'utente. Ad esempio è possibile registrare le chiamate (entambi gli interlocutori) e implementare un meccanismo di risposta. Anche usando testo->parola dovrebbe essere possibile, oppure modificare la propria voce. Attualmente non c'è nessun software installato per farlo.<br />
<br />
=== Q: Quanto dura la batteria? ===<br />
<br />
A: Non ci sono state parole per questo per molto tempo, ma leggi [[Neo1973 Power Management#Approximate_power_draw_of_various_subsystems|queste stime]] per una vaga idea. Più dettagli sulla batteria [[Neo1973 Battery/it|qui]].<br />
<br />
=== USB ===<br />
<br />
==== Q: Cosa posso fare con la porta USB sul Neo1973? ====<br />
A: Caricare il telefono, comunicare con esso tramite il seriale USB, o la rete USB.<br />
<br />
A: Inserire dispositivi esterni, come wifi, fotocamere, o dispositivi di archiviazione di massa.<br />
<br />
==== Q: Cosa non posso fare con l'USB? ====<br />
<br />
L'USB del neo non ha l'output. Questo significa che non puoi usare dispositivi con bus USB senza una sorta di hub o cavo.<br />
Questo è dovuto al fatto che aggiungere un erogatore di energia a 5V nel dispositivo avrebbe aggiunto complessità, dimensione e costo.<br />
<br />
Molti dispositivi progettati con USB no funzionano senza almeno una quantità indicativa di energia a 5v dal bus USB. Pochi hub USB funzioneranno senza un'energia di 5v dall'host, ma quelli alimentati richiedono semplici modifiche elettroniche per funzionare.<br />
<br />
==== Q: Perchè è supportato solo USB1.1? ====<br />
<br />
A: Il processore ha USB 1.1 al suo interno. Uno con USB2 al suo interno sarebbe stato più costoso.<br />
<br />
==== Q: Il Neo può caricarsi e usare dispositivi su un hub USB contemporaneamente? ====<br />
<br />
A: <br />
*Quando il Neo è connesso ad una porta su un hub USB, inizierà a ricaricarsi. Se l'hub è alimentato, allora si caricherà velocemente (3 ore), altrimenti intorno alle 12h.<br />
<br />
*Se colleghi il Neo alla porta host di un hub USB puoi usare dispositivi su quell'hub ma il Neo non si ricaricherà. (Alcuni/molti hub USB non accettano un host senza energia come valido, a causa del bisogno del cavo sottostante.)<br />
<br />
*Questo perchè il socket host sugli hub USB non è alimentato.<br />
<br />
Lo sviluppo dei prodotti FIC sta organizzando di fornire qualcosa che risolverà in modo conveniente questo problema.<br />
<br />
La porta USB sul Neo non è propriamente una porta host USB supportata, tutte le porte host USB devono fornire 5v - nonostante i dispositivi alimentati o gli hub possono non trarre alcuna corrente da essi, possono rifiutarsi di funzionare. (Il Belink Tetrahub è un esempio di hub che non andrà.)<br />
<br />
Una soluzione è un cavo con tre uscite.<br />
<br />
Un'uscita si inserisce nel Neo. Un'altra in una porta di un hub alimentato, o il caricatore Neo. Un'uscita si inserisce nella porta host di un hub.<br />
<br />
Il caricatore/dispositivo USB ha +5v o 0v connessi in un cavo semplice, collegato alle altre uscite.<br />
<br />
Per un cavo più complesso, quando il socket host non è inserito, il cavo agisce come un semplice cavo USB.<br />
<br />
==== Q: Quali sono le specifiche delle porte USB sul [[Neo1973/it|Neo1973]]? Come si confronta con USB On-The-Go? ====<br />
<br />
A: Il [[Neo1973/it|Neo1973]] avrà un mini-USB-B, e potrà funzionare come host e come dispositivo. NON sarà USB On-The-Go. OTG è una specifica complessa, e comprende molto più di un socket AB, anche componenti elettrici e software che non possono trovarsi sul S3C2410.<br />
<br />
Ti servirà un cavo Mini-B verso regular-B (notare che questo non è conforme in realtà allo standard USB: un cavo supportato deve avere un plug A o Mini-A su un'uscita, e B o Mini-B sull'altra).<br />
<br />
=== Q: Ci sono dei LEDs sul Neo 1973? ===<br />
<br />
A: Il [[Neo1973/it|Neo1973]] v1 non avrà LED a parte la retroillumazione dello schermo.<br />
<br />
=== Q: Sarà fornita una porta JTAB? ===<br />
<br />
A: L' "Hacker's Lunchbox" renderà facili questo genere di cose.<br />
<br />
E' correntemente presunto che l'Hacker's Lunchbox conterrà la [[Debug Board/it | Debug Board]]. [[Connecting Neo1973 with Debug Board v2/it|Connettere Neo con la Debug Board v2]] spiega come collegarla al telefono.<br />
<br />
=== Q: Cosa ci possiamo aspettare dalle versioni future? ===<br />
<br />
A: Una CPU più veloce, un GSM (EDGE?) più veloce, forse anche porte USB alimentate, USB2, wifi, e fotocamera. Non sono stati rilasciati dettagli ancora. Più info su aggiornamenti hardware dovrebbero essere disponibili a maggio. Ci sarà anche 5 dispositivi Openmoko in più - alcuni non telefoni nel senso tradizionale - annunciati dalla FIC a settembre.<br />
<br />
==Networking/Connettività==<br />
<br />
=== Q: Posso allacciarmi ad una rete Ethernet (wired o meno( tramite un router con Bluetooth attivo? ===<br />
<br />
A: Si - guarda [http://gentoo-wiki.com/HOWTO_Configure_a_bluetooth_network_access_point questo howto per come confgurare un computer linux per agire come un router] e [[Bluetooth Support/it | Il supporto Bluetooth]].<br />
<br />
=== Q: Quali provider forniscono il GSM richiesto per il Neo1973? ===<br />
<br />
A: Leggi [[Neo1973 compatible cellphone providers/it|Neo1973 compatible cellphone providers]]<br />
<br />
=== Q: Openmoko funzionerà senza problemi su Mac OS X?? ===<br />
<br />
A: Ci sono state discussioni in proposito sulla mailing list. C'è la motivazione, e ci sono sviluppatori interessati. Non essendo un utente Mac OS X, non ne so abbastanza per riassumere la discussione e rispondere alla domanda. Qualcuno può farlo?<br />
to summarize the discussion to answer this question. Can someone please fill in?<br />
<br />
A: Per IP over connettività USB, è pianificato di migliorare/adattare il driver AJZaurusUSB, ammettendo ssh in Openmoko.<br />
<br />
A: Ci si aspetta che l'interoperatività basata su SyncML (Bluetooth/USB) per contatti ed eventi possa essere raggiunta con una patch alle tabelle di configurazione dell'Apple iSync.<br />
<br />
A: C'è un'implementazione aperta di Cocoa (GNUstep) che si prefigge di eseguire apps compatibili con MacOS X (sorta di binari universali PPC/x86/ARM) sui dispositivi Openmoko: mySTEP.<br />
<br />
==Misc==<br />
<br />
=== Q: Sulle liste di lists.openmoko.org, le repliche devono essere aggiunte sopra o sotto il testo originale? ===<br />
<br />
A: Per favore rispondere SOTTO il post.<br />
<br />
=== Q: Come faccio a sapere se una domanda o argomento è già stato discussio sulle liste? ===<br />
<br />
A: Cercando negli archivi, ad esempio con Google:<br />
<br />
site:openmoko.org text<br />
<br />
Ad esempio, per cercare l'accelerometro:<br />
<br />
site:openmoko.org accelerometer<br />
<br />
Se vuoi solo leggere le mail "ufficiali" dalla gente di FIC o di Openmoko:<br />
site:openmoko.org text "at fic.com.tw"<br />
site:openmoko.org text "at openmoko.org"<br />
<br />
Ad esempio per cercare "release date" (data di rilascio) dalla FIC:<br />
<br />
site:openmoko.org "release date" "at fic.com.tw"<br />
Altrimenti puoi usare [http://www.google.it/coop/cse?cx=017507431580478583395%3Astsl7lhxzbc il motore di ricerca personalizzato Openmoko] creato usando [http://www.google.it/coop/ Google Co-op].<br />
<br />
{{Languages|FAQ}}<br />
<br />
[[Category:Basic End User/it]]</div>Dareushttp://openmoko.org/wiki/Talk:MdbusTalk:Mdbus2009-08-16T08:53:11Z<p>Dareus: </p>
<hr />
<div>I like tutorials, but I have not found proper place to highlight interesting tutorials:<br />
<br />
==making a phone call==<br />
(from discussion of Sten Kvamme and Michael 'Mickey' Lauer at devel malinglist)<br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.Resource.Enable<br />
</pre><br />
<br />
This will not work, since mdbus will register to the bus and vanish right <br />
afterwards, meaning the resource will be released immediately (if noone else <br />
has requested it). Try setting the policy to always-enabled:<br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ousaged /org/freesmartphone/Usage<br />
org.freesmartphone.Usage.SetResourcePolicy "GSM" "enabled"<br />
</pre><br />
<br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.GSM.Device.SetAntennaPower boolean:True<br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.GSM.Network.Register<br />
</pre><br />
<br />
<pre><br />
mdbus -s org.freesmartphone.ogsmd /org/freesmartphone/Phone \<br />
org.freesmartphone.Phone.CreateCall string:0123456789 \<br />
string:GSM boolean:True<br />
</pre><br />
<br />
should work -- although I'd rather use the ogsmd subsystem here, in which case it would be:<br />
<br />
<pre><br />
mdbus -s -org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device \<br />
org.freesmartphone.GSM.Initiate "+49123456789" "voice"<br />
</pre><br />
<br />
<br />
==Realtime clock==<br />
<pre><br />
#!/usr/bin/env python<br />
<br />
import dbus<br />
import time<br />
<br />
# Wakeup in 60 seconds<br />
wakeuptime=str(time.time()+60)<br />
<br />
system_bus = dbus.SystemBus()<br />
<br />
rtc_object = system_bus.get_object('org.freesmartphone.odeviced', '/org/freesmartphone/Device/RealTimeClock/0')<br />
rtc_interface = dbus.Interface(rtc_object, dbus_interface='org.freesmartphone.Device.RealTimeClock')<br />
rtc_interface.SetWakeupTime(wakeuptime)<br />
</pre><br />
<br />
==Strange proble==<br />
<br />
I'm on latest SHR unstable and I'm having some problems using dbus (mdbus too). Every time I mdbus -s something it prints some lines like this<br />
<br />
Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged<br />
<br />
I don't know what to do to keep using mdbus, because this is pretty annoying.<br />
<br />
[[User:Dareus|Dareus]]</div>Dareushttp://openmoko.org/wiki/Talk:Flashing_the_GSM_FirmwareTalk:Flashing the GSM Firmware2009-08-16T07:51:16Z<p>Dareus: /* Using scp from desktop */</p>
<hr />
<div>'''please refer to this very wikipage regarding -oo and flowcontrol'''<br />
Stephan_schmidt had exactly same issue and we fixed it yesterday, using these modifications<br />
<br />
<br />
WARNING : Flash failed ! From Sleg on 2008/11/25 :<br />
<br />
<br />
I had a problem during flashing my firmware ... I started again the module by typing 's3c24xx-gpio b7=1' as said in the wiki, and it started to flash the firmware. While it was flashing (I could see the progress ...) I failed by a 'Flash operation timeout'<br />
<br />
The GSM module seems to not respond anymore :'(<br />
<br />
If I retry, I get :<br />
<br />
root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 FLUID_FLOWCONTROL=h fluid.exe \<br />
> -oO -b 115200 \<br />
> -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0<br />
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.<br />
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok<br />
Bootloader: <br />
<br />
But nothing append even if I start the module by typing in another terminal 's3c24xx-gpio b7=1'<br />
<br />
Can somebody please help me ??<br />
sleg AT tsleg -DOT- com<br />
<br />
<br />
'''Thanks to Stefan Schmidt on the kernel mailing list'''<br />
My GSM went back !<br />
<br />
here is what I did :<br />
(Without FLOWCONTROL and with -oo to choose the ROM bootloader)<br />
<br />
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk<br />
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk<br />
Installing fluid (0.0+svn20070817-r2) to root...<br />
Configuring fluid<br />
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk<br />
Downloading http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk<br />
Multiple packages (s3c24xx-gpio and s3c24xx-gpio) providing same name marked HOLD or PREFER. Using latest.<br />
Installing s3c24xx-gpio (1.0+svnr4130-r2.1) to root...<br />
Configuring s3c24xx-gpio<br />
root@om-gta02:~# wget http://people.openmoko.org/joerg/calypso_moko_FW/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0<br />
Connecting to 10.194.51.41:3128 (10.194.51.41:3128)<br />
gsm_ac_gp_fd_pu_em_c 100% |**************************************************************************************************| 5419k 00:00:00 ETA<br />
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
root@om-gta02:~# cd /usr/sbin<br />
root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -b 115200 -f $HOME/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0<br />
FLUID Revision 2.27, (23 Aug 2004). Copyright Texas Instruments, 2001-2004.<br />
Reading image file: '/home/root/gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-moko10.m0' (2138kB) ok<br />
Bootloader: (reset target) (ROM, version ?) ok<br />
Checksumming (269 * 8kB = 2152kB): ok<br />
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok<br />
Program: (31 sectors, 243*8k=1944k) (******************) ok<br />
root@om-gta02:/usr/sbin# <br />
<br />
And to wake up the GSM in another ssh window :<br />
<br />
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
<br />
----<br />
<br />
<br />
<br />
<br />
<br />
i recive instead of<br />
<br />
"Program: (34 sectors, 267*8k=2136k) (*******************) ok"<br />
<br />
this<br />
<br />
"Program: (0 sectors, 0*8k=0k) () ok"<br />
<br />
iam currently reflashing the old firmware, that seems to work.<br />
<br />
iam using an non-us gsm-freerunner (recived yesterday so most likely the latest hardwar)<br />
<br />
thakoman<br />
<br />
<br />
<br />
[2008-11-19 04:46:39] <Wonka> DocScrutinizer: flashing to moko10-beta2 went though cleanly, i already had working ppp connects with the previously non-working SIM.<br />
<br />
[2008-11-19 04:48:24] <Wonka> DocScrutinizer: but there are still problems... more often than not, the GSM chip does not answer. pppd opens the device, gets "AT command interpreter ready", utters "AT\n" and gets nothing. power off, power on, reset on, reset off, try gain... sometimes it works, but mostly not.<br />
<br />
<br />
<br />
O2 UK prepay 3G SIM works with moko10-beta2, was previously not <br />
detected. T-mobile UK prepay SIM and old Orange UK contract SIM work <br />
with both old and new. Testing so far is cursory at best, but looks good.<br />
[quote: Alastair Johnson on devel-ML]<br />
<br />
[2008-11-21] <br />
I flashed 6 out of our 8 Freerunner V.6 according to the GSM/Flashing- guide. I had no problems and the previously useless 3G- SIMs are <br />
working fine now. It seems like the 3G- SIM Issue, our beloved #666, is solved. You should point it out clearly. I heard a lot of users complain about this. The solution is simple and well hidden on the website. By the way, i have new 3G- SIM cards of the following german providers running without problems (O2, T- Mobile, E-Plus, Vodafone). Before the flashing procedure the Vodafone cards were not detected. Good work guys... thanks! <br />
[[User:Reiner|Reiner]]<br />
<br />
== Works now with new gsm firmware moko10beta2 with O2 in Germany ==<br />
<br />
Very great, I can make calls now after waiting for 5 month, big surprise :).<br />
Thanks a lot! <br />
--[[User:Kevin|Kevin]] 15:18, 20 November 2008 (UTC)<br />
<br />
<br />
<br />
I'm very happy to be able to report that the update went smoothly for<br />
me (without yielding any surplus "building materials") and that a new<br />
O2 SIM from http://freesim.o2.co.uk/ which never worked in my<br />
Freerunner before now seems to be working fine. Great work!<br />
<br />
Tom<br />
<br />
-- <br />
<br />
Thomas White<br />
Department of Materials Science and Metallurgy<br />
Electron Microscopy Group (PhD Student)<br />
University of Cambridge / Downing College<br />
<br />
<br />
<br />
<br />
<br />
<br />
The flash worked without a hitch for me and now I am able to use a Vodafone<br />
prepaid SIM in my 850MHz unit while back in Europe. I am running Om2008.9<br />
with the 20081023 FDOM modifications applied.<br />
<br />
Great job!<br />
<br />
-Jacob<br />
<br />
<br />
<br />
<br />
<br />
<br />
Hello!<br />
<br />
Replying under subject Success :)<br />
I've combined what Michael said (few echo 1 >> .... and echo 0 >> .... <br />
in the other terminal) and Joerg's suggestion (-oo instead of -oO) and<br />
it worked perfectly. The upgrade to moko10 was done.<br />
<br />
So I can confirm the freerunner now works with Simobil's (Slovenian <br />
GSM operator) SIM.<br />
<br />
Great job and thanks to all that took the time to do it.<br />
<br />
Boštjan<br />
<br />
== State SD-image? ==<br />
<br />
Any update on a SD-image for GSM flashing?<br />
<br />
<br />
[joerg 2008-12-10 02:43:32]<br />
<br />
We're busy on this. Follow wiki instructions, or come up with an automatism by yourself. Expect any update on january.<br />
<br />
== microSD size issue 4Gb KO, 1Gb Ok ==<br />
<br />
I use a usd 4Gb that boots well with Qi, but don't with NOR, this kind of usd can't be used then for flashing.<br />
I nevertheless did the test and i confirm that it worked only when i used a smaller 1Gb usd.<br />
<br />
[Philippelhardy 2009-06_27]<br />
<br />
== bug #1024 ==<br />
[Tebra 2009-01-13 07:45]<br />
<br />
Hi. Are you working on moko11 to fix #1024 bug?<br />
Because of that bug I can't use android distribution.<br />
<br />
== German/Vodafone ==<br />
<br />
Got a new Vodafone Prepaid SIM-Card. Didn't work with QTExtended nor with Android until I've used the procedure to upgrade the GSM-Firmware. Looks like it's not just "swiss sim cards".<br />
Regards, --[[User:Rtreffer|Rtreffer]] 17:14, 25 January 2009 (UTC)<br />
<br />
== Broken GTA01bv4 GSM Modem Fix ==<br />
<br />
I recently had to do a special process to recover my GTA01bv4 after breaking the gsm modem with a failed flash. The process is actually fairly simple.<br />
<br />
* Unplug USB and remove the battery for about 10s to ensure that the GSM chipset is powered off, then replace the battery and re-connect the USB<br />
* boot up from a distro that is neutered so that it does not access or turn on the gsm modem at all<br />
* issue this stty command twice:<br />
stty 0:4:18b2:8a00:0:0:7f:15:4:0:0:0:0:0:0:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 -F /dev/ttySAC0<br />
* issue this fluid command:<br />
FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -od13,13 -vvv -b115200 -f $HOME/filename.m0<br />
* in another ssh session, issue this command:<br />
echo 1 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
<br />
After this, the flashing proceeded as expected, and all seems alright. I'll have to push a new distro to it to be certain, but all looks good so far.<br />
[[User:Quinn Storm|Quinn Storm]] 22:39, 16 March 2009 (UTC)<br />
<br />
Added note about battery removal. [[User:Mmontour|Mmontour]] 01:51, 17 March 2009 (UTC)<br />
<br />
== Flash using uSD card image worked! ==<br />
I'm now able to use my "MobilePlus" (Mobistar network) SIM which failed to register previously.<br />
Thanks for this excellent tool!<br />
<br />
--[[User:M8ram|M8ram]] 15:16, 26 April 2009 (UTC)<br />
<br />
Successful update here. Didn't fix unregistering SIM card under Android. I'll test few more things. --[[User:Mikeful|Mikeful]] 22:06, 18 June 2009 (UTC)<br />
<br />
== What is FLUID? ==<br />
Please create a link to an explanation of what FLUID is when FLUID is first mentioned at the top of the page.<br />
<br />
==The name of the page ==<br />
The name of this page is GSM/Flashing, which may be confused with [[Flashing_the_Neo_FreeRunner]] ?<br />
You could call it Firmware/Flashing (which breaks a lot of links .. and you need a stub.. )<br />
<br />
--[[User:Pike|pike]] 00:07, 18 May 2009 (UTC)<br />
<br />
==Remove uSD - optional ? ==<br />
<br />
At the bottom of par.3, it reads<br />
<br />
''>>You may can now remove bat and uSD''<br />
<br />
.. ("may"/"can") - "if you want to". I don't see a reason why you should ? <br />
<br />
I did notice I couldn't get into the NoR menu without twiddling around with battery and sim; but not sure what was going on there.<br />
<br />
--[[User:Pike|pike]] 00:07, 18 May 2009 (UTC)<br />
<br />
== ===== Visibility of the final Messagge "D_O_N_E" ===== ==<br />
<br />
<br />
<br />
At the end of flashing process the final message "D_O_N_E" in green over black, it's not so readable. In general if yous see a green messagge, also if you cannot read it well, you can safely reboot, the Flashing process it's done.<br />
--[[User:Apertum|Apertum]] 13:18, 18 May 2009 (UTC)<br />
<br />
See http://pike.kw.nl/files/documents/pike/personal/photoos/2009/20090518/DSCN0644.JPG : i guess 'D_O_N_E' is more appropriately described 'when the console turns green'.<br />
--[[User:Pike|Pike]] 13:18, 18 May 2009 (UTC)<br />
<br />
That's been the rationale of doing it this way ;-)<br />
/jOERG<br />
<br />
== Suggestion for uSD Instruction Steps ==<br />
<br />
On the second step of the uSD Installation procedure with dd command, i suggest to add this text:<br />
<br />
''Before proceding '''make sure that the uSD memory is NOT already formatted'''. With simple GUI like Gparted o QParted, you can unmount the right uSD partitions, and remove all the partition to have a simple uSD not formatted (the right formatted partition will be automatically transferred with the next 'dd' image transfer command).''<br />
<br />
Because i've seen that if i have an already Ext2/3 formatted uSD (or any other partition), the 'dd' Command it's not working tranferring the image.--[[User:Apertum|Apertum]] 21:03, 18 May 2009 (UTC)<br />
<br />
The original istructions to dd to physical device will overwrite whatever filesystem may have been on uSD, incl. partition-table/MBR. If dd is not working, you encounter some different problem, maybe caused by not correctly unmounting all partitions, or by a typo in dd. The instructions cover these cases as well.<br />
<br />
-- [[User:JOERG|jOERG]] 2009-05-19 00:05<br />
<br />
== Suggestion: Add a big Note Sticky at the beginning of the page to avoid editing the page ==<br />
<br />
Suggestion: add a very big Note Sticky at the beginning of the page to avoid editing the page by the community.<br />
<br />
The beginnig phrase: "This is NO communtity driven page, please be reluctant and careful with edits. Thanks " must be a lot bigger to avoid errors, IMHO.--[[User:Apertum|Apertum]] 21:11, 18 May 2009 (UTC)<br />
<br />
---<br />
seems there's no way to place a warning big enough for everybody anywhere on the page. Probably will lock eventually.<br />
<br />
-- [[User:JOERG|jOERG]] 2009-05-19 00:05<br />
<br />
You can add a simple:<br />
<br />
{{Warning | '''This is NO communtity driven page, please be reluctant and careful with edits. Thanks''' }}<br />
<br />
It's a lot more visibile and clear, IMHO. Anyway a lock it's safer, of course.<br />
--[[User:Apertum|Apertum]] 22:34, 18 May 2009 (UTC)<br />
<br />
== Using scp from desktop ==<br />
I don't have a card reader so I tried the scp command suggested. However, at the end it returns <br />
<br />
scp: /dev/mmcblk0: truncate: Invalid argument<br />
<br />
ALternatively, I mounted the desktop PC folder with the image using nfs and dd from there.<br />
-- [[User:fmartins]] 2009-08-15<br />
<br />
I'm quite sure you're using a wrong command, what's your input?<br />
<br />
usage of scp:<br />
scp IP:path_to_orig_file IP:path_to_to_dest_file<br />
<br />
[[User:Dareus|Dareus]]</div>Dareushttp://openmoko.org/wiki/Talk:IntoneTalk:Intone2009-08-14T10:02:33Z<p>Dareus: </p>
<hr />
<div>=Album art=<br />
<br />
Currently the album art is retrieved by a cover.jpg file in the song dir, what about trying to load it from id3 tags?<br />
much less files needed, no directories needed, maybe faster?<br />
<br />
[[User:Dareus|Dareus]]</div>Dareushttp://openmoko.org/wiki/Openmoko_Local_GroupsOpenmoko Local Groups2009-08-13T12:31:38Z<p>Dareus: /* America */</p>
<hr />
<div>'''Openmoko Local Groups...'''<br />
<br />
* can be used for developers to meet and get to know each other<br />
* can be used for developing<br />
* may provide the room for real-life discussions away from mailinglists/wiki<br />
* can support early support handling their GTA01Bv4 and exchange experiences<br />
* fasten the community's cohesion<br />
* give motivation<br />
<br />
Note that the list below is manually maintained. To make sure you don't miss a group, please check the [[:Category:Openmoko_Local_Groups|Openmoko local groups category]] too. If you happen to find any missing groups, please add them here.<br />
<br />
Note the list below was created during the Neo 1973 era. When the Neo FreeRunner came out, a different type of local group came into existence, as a result of discounts available with volume purchases. To find these local groups visit [[group sales|here]]<br />
<br />
== Africa ==<br />
* South Africa<br />
**[[Openmoko_Local_Groups: Cape Town|Cape Town]]<br />
* Egypt<br />
**[[Openmoko_Local_Groups: Tanta|Tanta]]<br />
**[[Openmoko_Local_Groups: Cairo|Cairo]]<br />
* Algeria - الجزائر<br />
**[[Openmoko_Local_Groups: Ouahran|ouahran]]<br />
<br />
== America ==<br />
<br />
* Brasil<br />
** [[Openmoko_Local_Groups: Belo Horizonte|Belo Horizonte]]<br />
** [http://www.neodroid.com Neodroid - Comunidade Brasileira do Openmoko Freerunner]<br />
<br />
* Argentina <br />
** Buenos Aires<br />
* Canada<br />
** Alberta<br />
*** [[Openmoko_Local_Groups: Calgary|Calgary]]<br />
*** [[Openmoko_Local_Groups: Edmonton|Edmonton]]<br />
*** [[Openmoko_Local_Groups: Pincher Creek|Pincher Creek]]<br />
** British Columbia<br />
*** [[Openmoko Local Groups: Victoria|Victoria]]<br />
*** [[Openmoko_Local_Groups: Vancouver|Vancouver]]<br />
** Ontario<br />
*** [[Openmoko_Local_Groups: Ottawa|Ottawa]]<br />
*** [[Openmoko_Local_Groups: Toronto|Toronto]]<br />
** Quebec<br />
*** [[Openmoko_Local_Groups: Montreal|Montreal]]<br />
<br />
* Colombia<br />
** [[Openmoko_Local_Groups: Bogota|Bogotá]]<br />
<br />
* México<br />
** [[Openmoko_Local_Groups: Ciudad de México|Ciudad de México]]<br />
** [[Openmoko_Local_Groups: Cuernavaca|Cuernavaca]]<br />
** [[Openmoko_Local_Groups: Monterrey|Monterrey]]<br />
<br />
<br />
* USA<br />
** Alabama<br />
*** [[Openmoko_Local_Groups: Alabama|Alabama]]<br />
** Arizona<br />
*** [[Openmoko_Local_Groups: Arizona|Arizona]]<br />
** Arkansas<br />
*** [[Openmoko_Local_Groups: Arkansas|Arkansas]]<br />
** California<br />
*** [[Openmoko_Local_Groups: San Diego|San Diego]]<br />
*** [[Openmoko_Local_Groups: San Francisco|San Francisco]]<br />
*** [[Openmoko_Local_Groups: Sacramento|Sacramento]]<br />
*** [[Openmoko_Local_Groups: Los Angeles|Los Angeles]]<br />
*** [[Openmoko_Local_Groups: Santa Barbara|Santa Barbara]]<br />
** Colorado<br />
*** [[Openmoko_Local_Groups: Colorado Springs|Colorado Springs]]<br />
*** [[Openmoko_Local_Groups: Denver|Denver]]<br />
** District of Columbia<br />
*** [[Openmoko_Local_Groups: Washington DC Metro | Washington DC Metro]]<br />
** Florida<br />
*** [[Openmoko_Local_Groups: Central Florida | Central Florida]]<br />
** Georgia<br />
*** [[Openmoko_Local_Groups: Atlanta | Atlanta]]<br />
** Illinois<br />
*** [[Openmoko_Local_Groups: Chicago|Chicago]]<br />
** Indiana<br />
*** [[Openmoko_Local_Groups: Bloomington|Bloomington]]<br />
** Iowa<br />
*** [[Openmoko_Local_Groups: Iowa-Ames | Iowa-Ames]]<br />
** Massachusetts<br />
*** [[Openmoko_Local_Groups: Boston|Boston]]<br />
*** [[Openmoko_Local_Groups: Boston/old|Boston/old]]<br />
** Michigan<br />
*** [[Openmoko_Local_Groups: Detroit|Detroit]]<br />
** Missouri<br />
*** [[Openmoko_Local_Groups: St. Louis|St. Louis]]<br />
** Nevada<br />
*** [[Openmoko_Local_Groups: Las Vegas|Las Vegas]]<br />
** New Jersey<br />
*** [[Openmoko_Local_Groups: Stevens Institute of Technology, Hoboken NJ | Stevens Institute of Technology, Hoboken NJ ]]<br />
** New York<br />
*** [[Openmoko_Local_Groups: NYC Metro | NYC Metro]]<br />
** North Carolina<br />
*** [[Openmoko Local_Groups: Charlotte | Charlotte]]<br />
** North Dakota<br />
*** [[Openmoko_Local_Groups: Fargo]]<br />
** Ohio<br />
*** [[Openmoko_Local_Groups: Cleveland|Cleveland]]<br />
*** [[Openmoko_Local_Groups: Cincinnati|Cincinnati]]<br />
** Oregon<br />
*** [[Openmoko_Local_Groups: Eugene|Eugene]]<br />
*** [[Openmoko_Local_Groups: Portland|Portland]]<br />
** Pennsylvania<br />
*** [[Openmoko_Local_Groups: Pittsburgh|Pittsburgh]]<br />
** Texas<br />
*** [[Openmoko_Local_Groups: North Texas|North Texas]]<br />
*** [[Openmoko_Local_Groups: Central Texas|Central Texas]]<br />
*** [[Openmoko_Local_Groups: East Texas|East Texas]]<br />
** Utah<br />
*** [[Openmoko_Local_Groups: Salt Lake|Salt Lake]]<br />
** Virginia<br />
*** [[Openmoko_Local_Groups: Virginia|Virginia]]<br />
** Washington<br />
*** [[Openmoko_Local_Groups: Washington|Pacific Northwest]]<br />
<br />
* Uruguay<br />
** [[Openmoko_Local_Groups: Montevideo|Montevideo]]<br />
<br />
* [[Openmoko Local Groups: Venezuela|Venezuela]]<br />
** [[Openmoko_Local_Groups: Caracas|Caracas]]<br />
<br />
* Cincinnati<br />
** [[Openmoko Local Groups: Cincinnati]]<br />
<br />
== Asia ==<br />
* Belarus<br />
** [[Openmoko_Local_Groups: Minsk|Minsk]]<br />
* Pakistan<br />
** [[Openmoko_Local_Groups: Islamabad|Islamabad]]<br />
* India<br />
** [[Openmoko_Local_Groups: Bangalore|Bangalore]]<br />
** [[Openmoko_Local_Groups: Delhi|Delhi]]<br />
** [[Openmoko_Local_Groups: Hyderabad|Hyderabad]]<br />
** [[Openmoko_Local_Groups: Bikaner|Bikaner]]<br />
** [[Openmoko_Local_Groups: Mumbai|Mumbai]]<br />
* Singapore<br />
** [[Openmoko_Local_Groups: Singapore|Singapore]]<br />
* Kazakhstan<br />
** [[Openmoko_Local_Groups: Karaganda|Karaganda]]<br />
* China<br />
** [[Openmoko_Local_Groups: China|China]]<br />
* Taiwan<br />
** [[Openmoko_Local_Groups: Taiwan|Taiwan]]<br />
<br />
== Europe ==<br />
<br />
* Austria<br />
** [[Openmoko_Local_Groups: Vienna|Vienna]]<br />
** [[Openmoko_Local_Groups: Innsbruck|Innsbruck]]<br />
<br />
* [[Openmoko_Local_Groups: Belgium|Belgium]]<br />
** [[Openmoko_Local_Groups: Antwerp|Antwerp]]<br />
** [[Openmoko_Local_Groups:_Brussels|Brussels]]<br />
<br />
* [[Openmoko_Local_Groups: Belarus|Belarus]]<br />
<br />
* [[Openmoko_Local_Groups: Czech|Czech]]<br />
<br />
* [[Openmoko_Local_Groups:_Denmark|Denmark]]<br />
** [[Openmoko_Local_Groups: Aalborg|Aalborg]]<br />
** [[Openmoko_Local_Groups: Copenhagen|Copenhagen]]<br />
** [[Openmoko_Local_Groups: Sydjylland|Sydjylland]]<br />
<br />
*[[Openmoko_Local_Groups: Estonia|Estonia]]<br />
** [[Openmoko_Local_Groups: Kuressaare|Kuressaare]]<br />
<br />
* [[Openmoko_Local_Groups: Finland|Finland]]<br />
** [[Openmoko_Local_Groups: Helsinki|Helsinki]]<br />
<br />
* [[Openmoko_Local_Groups: France|France]]<br />
** [[Openmoko Local Groups: Alsace|Alsace]]<br />
** [[Openmoko_Local_Groups: Grenoble|Grenoble]]<br />
** [[Openmoko_Local_Groups: Lyon|Lyon]]<br />
** [[Openmoko Local Groups: Marseille|Marseille]]<br />
** [[Openmoko_Local_Groups: Paris|Paris]]<br />
** [[Openmoko_Local_Groups: Rennes|Rennes]]<br />
** [[Openmoko_Local_Groups: Toulouse|Toulouse]]<br />
<br />
* Germany<br />
** [[Openmoko_Local_Groups: Aachen|Aachen]]<br />
** [[Openmoko_Local_Groups: Berlin|Berlin]]<br />
** [[Openmoko_Local_Groups: Bielefeld|Bielefeld]]<br />
** [[Openmoko_Local_Groups: Braunschweig|Braunschweig]]<br />
** [[Openmoko_Local_Groups: Dortmund|Dortmund]]<br />
** [[Openmoko_Local_Groups: Dresden|Dresden]]<br />
** [[Openmoko_Local_Groups: Duesseldorf|Duesseldorf]]<br />
** [[Openmoko_Local_Groups: Erlangen-Nuernberg|Erlangen-Nuernberg]]<br />
** [[Openmoko_Local_Groups: Frankfurt Main|Frankfurt Main]]<br />
** [[Openmoko_Local_Groups: Freiburg im Breisgau|Freiburg im Breisgau]]<br />
** [[Openmoko_Local_Groups: Hamburg|Hamburg]]<br />
** [[Openmoko_Local_Groups: Ingolstadt|Ingolstadt]]<br />
** [[Openmoko_Local_Groups: Karlsruhe|Karlsruhe]]<br />
** [[Openmoko_Local_Groups: Krefeld|Krefeld]]<br />
** [[Openmoko_Local_Groups: Munich|München]]<br />
** [[Openmoko_Local_Groups: OWL|OWL]]<br />
** [[Openmoko_Local_Groups: Rülzheim|Rülzheim]]<br />
** [[Openmoko_Local_Groups: Stuttgart|Stuttgart]]<br />
** [[Openmoko_Local_Groups: Trier|Trier]]<br />
** [[Openmoko_Local_Groups: Ulm|Ulm]]<br />
<br />
* Greece<br />
** [[Openmoko_Local_Groups: Athens|Athens]]<br />
<br />
* Hungary<br />
** [[Openmoko_Local_Groups: Budapest|Budapest]]<br />
<br />
* Iceland<br />
** [[Openmoko_Local_Groups: Reykjavík|Reykjavík]]<br />
<br />
* Ireland<br />
** [[Openmoko_Local_Groups: Ireland|Ireland]]<br />
<br />
* Italy<br />
** [[Openmoko_Local_Groups: Milan|Milan]]<br />
** [[Openmoko_Local_Groups: Turin|Turin]]<br />
** [[Openmoko_Local_Groups: Padova|Padova]]<br />
** [[Openmoko_Local_Groups: Friuli Venezia Giulia |Friuli Venezia Giulia ]]<br />
<br />
* Lithuania<br />
** [[Openmoko_Local_Groups: Lithuania|Lithuania]]<br />
<br />
* [[Openmoko_Local_Groups:_Netherlands|Netherlands]]<br />
** [[Openmoko_Local_Groups: Amsterdam|Amsterdam]]<br />
** [[Openmoko_Local_Groups: Den Haag|Den Haag/The Hague]]<br />
** [[Openmoko_Local_Groups: Eindhoven|Eindhoven]]<br />
** [[Openmoko_Local_Groups: Ede|Ede]]<br />
<br />
* [[Openmoko_Local_Groups:_Norway|Norway]]<br />
** [[Openmoko_Local_Groups:_Oslo|Oslo]]<br />
** [[Openmoko_Local_Groups: Trondheim|Trondheim]]<br />
<br />
* Poland<br />
** [[Openmoko_Local_Groups: Warsaw|Warsaw]]<br />
** [[Openmoko_Local_Groups: Szczecin|Szczecin]]<br />
<br />
* [[Openmoko_Local_Groups:_Portugal|Portugal]]<br />
** [[Openmoko_Local_Groups: Braga|Braga]]<br />
** [[Openmoko Local Groups: Lisboa]]<br />
<br />
* Romania<br />
** [[Openmoko_Local_Groups: Bucharest|Bucharest]]<br />
<br />
* [[Openmoko Local Groups: Russia|Russia]] [http://www.linuxphone.ru | Портал русскоязычных пользователей]<br />
** [[Openmoko_Local_Groups: Moscow|Moscow]]<br />
** [[Openmoko_Local_Groups: Saint-Petersburg|Saint-Petersburg]]<br />
** [[Openmoko_Local_Groups: Ulyanovsk|Ulyanovsk]]<br />
<br />
* [[Openmoko_Local_Groups: Sardegna|Sardegna]]<br />
<br />
* [[Openmoko_Local_Groups: Scotland|Scotland]]<br />
<br />
* Slovakia<br />
** [[Openmoko_Local_Groups: Bratislava|Bratislava]]<br />
<br />
* [[Openmoko_Local_Groups:_Spain|Spain]]<br />
** [[Openmoko_Local_Groups: Madrid|Madrid]]<br />
** [[Openmoko_Local_Groups: Tenerife|Santa Cruz de Tenerife]]<br />
** [[Openmoko_Local_Groups: Baleares|Islas Baleares]]<br />
<br />
* Spain<br />
** [[Openmoko_Local_Groups: Valencia|Valencia]]<br />
<br />
* Sweden<br />
** [[Openmoko_Local_Groups: Gothenburg|Gothenburg]]<br />
** [[Openmoko_Local_Groups: Linkoping|Linköping]]<br />
** [[Openmoko_Local_Groups: Stockholm|Stockholm]]<br />
** [[Openmoko_Local_Groups: Umea|Umeå]]<br />
<br />
* [[Openmoko_Local_Groups: Switzerland|Switzerland]]<br />
** [[Openmoko_Local_Groups: Bern|Bern]]<br />
** [[Openmoko_Local_Groups: Zurich|Zurich]]<br />
<br />
* UK<br />
** England<br />
*** [[Openmoko_Local_Groups: Birmingham|Birmingham]]<br />
*** [[Openmoko_Local_Groups: Cambridge|Cambridge]]<br />
*** [[Openmoko_Local_Groups: London|London]]<br />
*** [[Openmoko_Local_Groups: Manchester|Manchester]]<br />
*** [[Openmoko_Local_Groups: East Midlands|East Midlands]]<br />
** Scotland<br />
*** [[Openmoko_Local_Groups: Fife|Fife]]<br />
*** [[Openmoko_Local_Groups: Edinburgh|Edinburgh]]<br />
<br />
* Ukraine<br />
** [[Openmoko_Local_Groups: Lugansk|Lugansk]]<br />
<br />
== Oceania ==<br />
<br />
* Australia<br />
** [[Openmoko_Local_Groups: Adelaide|Adelaide]]<br />
** [[Openmoko_Local_Groups: Canberra|Canberra]]<br />
** [[Openmoko_Local_Groups: Melbourne|Melbourne]]<br />
** [[Openmoko_Local_Groups: Perth|Perth]]<br />
** [[Openmoko_Local_Groups: Sydney|Sydney]]<br />
<br />
* New Zealand<br />
** [[Openmoko_Local_Groups: Auckland|Auckland]]<br />
** [[Openmoko_Local_Groups: Wellington|Wellington]]<br />
** [[Openmoko_Local_Groups: Christchurch|Christchurch]]<br />
<br />
<br />
== How to edit local group lists ==<br />
<br />
{|border="1"<br />
!<br />
!Has Device<br />
|-<br />
|If you have a device, on your local group's page, please add:<br />
|[[Image: Moko.jpg|center]]<br />
<br />
<br />
<br />
<nowiki>[[Image: Moko.jpg|center]]</nowiki> <br />
|-<br />
!<br />
!Has Debug Board<br />
|-<br />
|If you have a debug board, please add:<br />
|[[Image: MokoBox.jpg|center]]<br />
<br />
<br />
<br />
<nowiki>[[Image: MokoBox.jpg|center]]</nowiki> <br />
|}<br />
<br />
Such as with [[Openmoko_Local_Groups:_Singapore | Singapore]] or [[Openmoko_Local_Groups:_San_Francisco | San Francisco]]<br />
<br />
[[Category:Community]]<br />
[[Category:Openmoko Local Groups]]</div>Dareushttp://openmoko.org/wiki/SHR_User_ManualSHR User Manual2009-08-12T16:53:22Z<p>Dareus: /* opkg upgrade issues */</p>
<hr />
<div>{{Languages|SHR User Manual}}<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
<br />
I consider this a draft already, please [[Talk:SHR_User_Manual|Comment here]] --[[User:Vanous|Vanous]] 11:47, 6 August 2009 (UTC)<br />
<br />
New SHR users, readers, please do report improvements, discrepancies or missing features to vanous @ penguin . cz<br />
<br />
<br />
==SHR Introduction==<br />
<br />
Welcome to '''[[SHR]]''', the world of community driven distribution for (not only) OpenmokoNeo phones.<br />
<br />
'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install onto your Freerunner to use is as a daily phone. It's filled with prepackaged software that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. SHR unstable is a testing environment before software get stabilized and it is the main testing ground for [[FSO]] releases. SHR testing images (currently not available) provide as much stability as possible for day-to-day usage.<br />
<br />
'''SHR''' has been evolving from a simple release of customized software into a full distribution. Therefore, in SHR you can choose from several different graphical toolkits (for example GTK or EFL), different phone managers (SHR or Zhone), web browsers and other programs.<br />
<br />
The SHR Team is busy with system maintenance and software building so you can concentrate on programming, using and [http://shr-project.org/trac/report reporting bugs].<br />
<br />
[http://shr-project.org SHR Project page]<br />
<br />
==SHR Specific==<br />
<br />
At this point, there are some applications and procedures that are purely specific to SHR and would not run on another distribution. For example the phone applications (Dialer, Messages and Contacts) and SHR Settings depend heavily on the ophonekitd daemon.<br />
<br />
As SHR is based on [[FSO]], basically any application using FSO has a chance to run, should all required libraries be available.<br />
<br />
==Stability==<br />
<br />
While many people use SHR as their daily phone, there are still occasional glitches and issues. This hurts the most when GSM stops working but this happens less and less. We wish you to have the best experiences with SHR.<br />
<br />
==Installation==<br />
<br />
===Getting SHR===<br />
<br />
First, determine which model of phone you have, the GTA01(neo1973) or the GTA02(FreeRunner).<br />
<br />
You need to download two files for your version as above, kernel and root filesystem. Depending whether you will be installing into the internal nand memory or on µSD card, you need to either get .jffs2 file for nand or .tar.gz file for µSD.<br />
<br />
At this point, there are no recent testing images so for the GTA02 Freerunner you need to download the images of unstable release from http://build.shr-project.org/shr-unstable/images/om-gta02/<br />
<br />
- Get the latest kernel: [http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin uImage-om-gta02-latest.bin]<br />
<br />
- Get the root filesystem, for nand: [http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.jffs2 shr-image-om-gta02.jffs2], (for µSD): [http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.tar.gz shr-image-om-gta02.tar.gz]<br />
<br />
These are full images. You can also choose image with less packages, marked as '''lite''' which can be upgraded to the full image by running<br />
<br />
opkg update<br />
opkg task-shr-apps task-shr-games task-shr-gtk<br />
<br />
===Source code===<br />
<br />
View the sources at http://git.shr-project.org/git/<br />
<br />
<br />
===Image content===<br />
{|class="wikitable" border="1" cellpadding="0" cellspacing="0" width=100%<br />
<br />
! width=16%| !! width=42%|Full image content !! width=42%|SHR-Image LITE Content<br />
|-<br />
| Window Manager || <br />
* illume<br />
||<br />
* illume<br />
|-<br />
| Engine ||<br />
* frameworkd<br />
||<br />
* frameworkd<br />
|-<br />
| Telephony || <br />
* Dialer (Call/Receive, DTMF, Speaker mode)<br />
* SIM Contacts (Call/Modify/Create/...)<br />
* SIM Messages (Receive/Compose/Answer/...)<br />
* Pyphonelog (received/emitted/missed calls logging)<br />
|| <br />
* Dialer (Call/Receive, DTMF, Speaker mode)<br />
* SIM Contacts (Call/Modify/Create/...)<br />
* SIM Messages (Receive/Compose/Answer/...)<br />
* Pyphonelog (received/emitted/missed calls logging)<br />
|-<br />
| GPS || <br />
* TangoGPS<br />
|| <br />
* TangoGPS<br />
|-<br />
| Utilities ||<br />
* Calculator<br />
* Alarm<br />
* GPE Scap (Take screenshot)<br />
* GPE File Manager<br />
* GPE Sketchbook<br />
* vala-terminal<br />
||<br />
* Calculator<br />
* Alarm<br />
* GPE File Manager<br />
* vala-terminal<br />
<br />
|-<br />
<br />
| Media ||<br />
<br />
* Vagalume<br />
* Intone <br />
||<br />
* pythm <br />
<br />
|-<br />
<br />
| Internet ||<br />
* Pidgin<br />
* Midori (Browser) <br />
||<br />
<br />
|-<br />
<br />
| Games ||<br />
* Numptyphysics <br />
||<br />
|-<br />
| Settings ||<br />
* SHR Settings<br />
* Mokonnect (Network Manager) <br />
|| <br />
* SHR Settings<br />
<br />
<br />
<br />
|-<br />
|}<br />
<br />
===Installation on Flash===<br />
<br />
In order to install your SHR distribution directly to your Freerunner Flash memory (NAND), you need to get the desired filesystem file ( .jffs2 ) as described above and flash your device using the dfu-util tool.<br />
<br />
Please visit [[Flashing_the_Neo_FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.<br />
<br />
Command to flash the filesystem and the kernel<br />
<br />
dfu-util -a rootfs -R -D shr-image-om-gta02.jffs2<br />
dfu-util -a kernel -R -D uImage-om-gta02-latest.bin<br />
<br />
===Installation on µSD Card===<br />
<br />
Installing SHR on your µSD Card depends on the Bootloader you are using, uBoot or Qi.<br />
<br />
In simply words, difference between both systems resides on how you must prepare your µSD Card and files you use to fill them:<br />
<br />
If you use uBoot, you need to create two partitions. First partition, not so big, in FAT16 where you have to place the kernel file (uImage-om-gta02-latest.bin) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (shr-image-om-gta02.tar.gz).<br />
<br />
If you use Qi, you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (shr-image-om-gta02.tar.gz). In this case Qi Bootloader is going to look for the kernel image into the /boot directory for file named uImage-GTA02.bin .<br />
<br />
Please visit links bellow for detailed information and tips:<br />
<br />
For [[Booting from SD | uBoot]] and for [[Qi]].<br />
<br />
===SHR version===<br />
<br />
Shell you ever later wonder what version of SHR you have actually installed, please run<br />
<br />
cat /etc/shr-version<br />
<br />
or check SHR Settings -> Other -> Image information<br />
<br />
==Running SHR==<br />
===Booting===<br />
Press the power button shortly once to start the Freerunner. Booting splash screen will appear. First boot after new installation takes always a bit longer. Sometimes, it is recommended to reboot after this first boot, to make sure all packages got initialized properly.<br />
<br />
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]<br />
<br />
===Initial Setup===<br />
<br />
[[Image:SHR-Setup-Language.png|200px|thumb|Initial setup]]<br />
On the first boot, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. You are able to choose preferred language of the desktop environment, Illume SHR themed profile or select default menu (only one at the moment). <br />
<br />
On the Add icon screen you can add icons for some application. If you add a terminal based application like mplayer, you will see an icon but no application running upon click, as it will run in the background. <br />
Last screen allow settin up quick launch applications.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Setup-Profile.png|200px|thumb|Theme profile]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Setup-Menu.png|200px|thumb|Menu]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Setup-Add-Icons.png|200px|thumb|Add icons]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
<br />
[[Image:SHR-Setup-Quick-Launch.png|200px|thumb|Quick launch]]<br />
<br />
|}<br />
<br />
===SIM Auth===<br />
<br />
[[Image:SHR-SIM-Auth.png|200px|thumb|SIM Auth]]<br />
SIM Pin is asked for upon start up.<br />
<br />
===First look===<br />
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]<br />
'''Illume desktop''' is default home screen of the SHR desktop. Application files located in /usr/share/applications are displayed here. All applications are ran fullscreen and you can switch between them by using the Task switcher in the Top Shelve or by using the < left or right > arrows in the Top Shelve.<br />
<br />
The Illume desktop can be easily customized - slide the Top Shelve down and tap the Settings icon (Wrench).<br />
<br />
{{Note|TIP: for better access of the Settings icon, tap and hold the Settings icon, then drag it to the right.}}<br />
<br />
'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to preview more options on the right hand side.<br />
<br />
The little applets in the Top Shelve (for example Battery, GSM, Bluetooth etc.) are called '''Shelve gadgets''' and you can configure whether they are visible (on the front part of the top shelve) or hidden (you can access them by sliding the top shelve) through Illume Settings -> Display -> Shelve gadget.<br />
<br />
Some screens are not resized properly to fit the Freerunner's display - for example the Wallpapper setting. This is a known bug already reported upstream.<br />
<br />
<!-- [[Image:SHR-Top-Shelve.png|200px|thumb|Top Shelve]] --><br />
<br />
===Phone applications===<br />
<br />
Besides other software, SHR comes with 4 main phone applications: Dialer, Contacts, Messages and Phone log.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Dialer.png|200px|thumb|Dialer]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contacts.png|200px|thumb|Contacts]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contacts-Options.png|200px|thumb|Contact options]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contact-Add.png|200px|thumb|Add new contact]]<br />
|}<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Mesages.png|200px|thumb|Messages]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Messages-Options.png|200px|thumb|Messages options]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Message-View.png|200px|thumb|View message]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Message-View-chars.png|200px|thumb|Unicode support]]<br />
<br />
|}<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Mesages-Options.png|200px|thumb|Message options]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Phonelog.png|200px|thumb|Phonelog]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Dialer-Active.png|200px|thumb|Active call]]<br />
<br />
|}<br />
<br />
Upon a missed call or an unread message there is a Notifier that presents a screen with button to run Messages or Phonelog application, or you can simply close the Notifier with the Top Shelve cross.<br />
<br />
===Post-Installation Script===<br />
After flashing your Openmoko Freerunner you can do some modification mentioned below in this manual. The shell commands are collected in a [[SHR post-installation]] that you can transfer to your Freerunner via ''scp'' and execute it with ''sh''. <br />
Please go through the script and check if the applications to be installed is that want you want. If do not understand, what is going on in the script, proceed with this manual and select every step manually. If understand the script it might save you some time:<br />
desktop#<br />
scp SHRpostinstallation.sh root@192.168.0.202/home/root/SHRpostinstallation.sh <br />
Start the shell script on you Freerunner with:<br />
neo# sh /home/root/SHRpostinstallation.sh<br />
<br />
===Under the hood===<br />
<br />
SHR is based on linux kernel and Openembedded. XGlamo 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 ophonekitd daemon is run with X server start up and it communicates with FSO via d-bus. SHR phone applications talk to ophonekitd 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 libframeworkd-phonegui-efl library, Phonelog is an extra application written in python-gtk.<br />
<br />
===First steps===<br />
<br />
Right after installation and first boot you might want to do a few initial steps:<br />
====Network Connection====<br />
''Establish network connection'' and SSH into your Freerunner. The root account uses no password by default. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi. If you use USB, some setup is required on the desktop side, please read [[USB_Networking]]. For Wifi, you can use [[#Network manager|Network Manager]]<br />
<br />
====GSM Network====<br />
''Check if GSM is working correctly'' - observe the GSM gadget in the Top Shelve and see reported signal of your GSM operator. If GSM Gadget seems not be running, click ''Settings'' and later on ''Phone''. Move ''GSM Antenna'' to ''On''.<br />
<br />
====Audio: Volume====<br />
''Check and set call volume'' - this is handled by alsa state files in /usr/share/shr/scenarii/ . To customize speaker volume edit /usr/share/shr/scenarii/gsmheadset.state and change control 4. Values between from 105 to 120 might be sufficient.<br />
<br />
Shell you want to alter more parameters be aware that each file is a set of value for the 94 parameters. Some of the important ones are:<br />
<br />
Control 48: internal mic of the tel (set to 2 or 3)<br />
Control 4 : internal speaker (set from 110 to 120)<br />
Control 49: headset mic<br />
Control 3 : headset speaker<br />
<br />
====Alarm====<br />
The default alarm clock application <tt>elementary-alarm</tt> is not working properly. You may want to remove it and install working alarm application called <tt>ffalarm</tt>:<br />
<br />
opkg remove -force-depends elementary-alarm<br />
opkg install ffalarms<br />
<br />
====Init opkg database====<br />
''Initialize opkg database'' in order to install some applications from SHR repositories or from other sources, for example [[http://opkg.org opkg.org]]. While still being online, you need to first run<br />
<br />
opkg update<br />
<br />
Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through.<br />
<br />
Do this only once or after every opkg update:<br />
<br />
opkg list > packages.txt<br />
<br />
Then you can search quickly for package name, for example for navit:<br />
<br />
grep navit packages.txt<br />
<br />
====SwapSpace====<br />
The Freerunner has only 128mb ram, when this is used up applications get killed. This is particularly bad while doing opkg upgrade.<br />
<br />
WARNING: this mights kill your sd card, since there might be a lot of read/writes to the same spot. <br />
<br />
dd if=/dev/zero of=/swapfile bs=1024 count=65536<br />
<br />
Add a line to fstab so next time you boot there will be swap<br />
<br />
echo "/swapfile swap swap defaults 0 0">> /etc/fstab <br />
<br />
Make swap<br />
<br />
mkswap /swapfile<br />
<br />
Make the swap file work now:<br />
<br />
swapon /swapfile<br />
<br />
====Changing root password====<br />
<br />
SHR is shipped without root password (just press enter)<br />
<br />
This is very dangerous if you connect using wifi, or USB. You need to activate the root password:<br />
<br />
passwd<br />
<br />
then type your selected password (2 times)<br />
<br />
====Locate Phone by getting SMS with GPS location==== <br />
Install '''sms-sentry''' to be able to locate your phone in case of lost or theft:<br />
<br />
opkg install sms-sentry<br />
<br />
Then, upon sending an sms with text sentry:location to your Freerunner, the phone will turn on GPS, wait for a fix and send back sms with current location.<br />
<br />
[[Cellhunter]] is a project with the objective to collect GPS location of GSM network cells. If this project is finished then sms-sentry could send the a rough GPS location just by identifying the current distances (strength of signal) to the available GSM network cells, even when the GPS satellites are not available (e.g. in a house).<br />
<br />
===Localization===<br />
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]<br />
<br />
You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in Illume Top Shelve go to Wrench (Settings) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.<br />
<br />
You can list all available languages by running:<br />
<br />
opkg list | grep glibc-locale-<br />
<br />
And install the language of your choice (for example czech):<br />
<br />
opkg install glibc-locale-cs<br />
<br />
After this, the Language Settings of Illume will offer Czech. <br />
<br />
<br />
This will localize the Illume environment and will also set correct lang environment variable. If you wish to have translations for other applications, you need to install them again (presuming they are available):<br />
<br />
This will install czech localisation for SHR phone applications, SHR Settings and TangoGps:<br />
<br />
opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs<br />
<br />
For localized terminal environment (ssh login) set lang variables set /etc/profile, example for Czech language:<br />
<br />
export LANG=cs_CZ<br />
export LC_ALL=cs_CZ<br />
<br />
<br />
The Illume keyboard offers english dictionary correction by default. You can list all the dictionaries available for installation:<br />
<br />
opkg list | grep illume-dic<br />
<br />
<br />
If your language is not available and english is bothering you, you can set an empty dictionary:<br />
<br />
echo "" > /usr/lib/enlightenment/modules/illume/dicts/None.dic<br />
<br />
By using it, it will get filled by the words you use and after time will start helping and correcting your typing.<br />
<br />
===Date and time===<br />
<br />
Timezone is automatically retrieved from the GSM network. Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically after several minutes.<br />
<br />
Time can set time also manually.<br />
<br />
Via SHR-Settings -> Date/time -> Set time<br />
<br />
From linux based desktop:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
You can also set the hardware clock to the system time:<br />
<br />
hwclock --systohc<br />
<br />
===File transfer===<br />
<br />
After you have established network connection, it is very easy to access and transfer files. The easiest solution is to use Konqueror or Nautilus on your desktop computer and type the following on your location bar. This should provide you with a view of the client's file system on Konqueror or Nautilus and you can easily drag-drop and copy-paste files.<br />
<br />
sftp://root@192.168.0.202<br />
<br />
===Data synchronization===<br />
[[Image:SHR-PISI.png|200px|thumb|PISI Contact Sync]]<br />
[[Image:SHR-PISI-dates.png|200px|thumb|PISI Calendar Sync]]<br />
<br />
You can synchronize your contacts and appointments data with various sources. The sync can by done by program called [http://pisi.projects.openmoko.org/ PISI] . SIM contacts and calendar entries are currently possible to sync on SHR. You can also synchronize OPIMD contacts, these data are however so far no used in the current shr phone applications, but are used by for example Litephone.<br />
<br />
For calendar install dates<br />
<br />
opkg install dates<br />
<br />
Supported Contacts data sources:<br />
* SIM via DBUS (e.g. SHR)<br />
* QTopia address book (e.g. OM 2008.12)<br />
* LDAP (read only)<br />
* VCF files (local / webdav)<br />
* Google contacts<br />
* OPIMD<br />
<br />
Supported Calendar data sources:<br />
* Google calendars<br />
* ICalendar files (local / webdav)<br />
<br />
To install PISI, run <br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="left";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:80%; text-align:left " | <br />
<br />
opkg install http://www.opkg.org/packages/1_python-vobject_0.8.1_armv4t.ipk http://www.opkg.org/packages/0_python-webdav_0.1.2_armv4t.ipk python-sqlite3 python-pygtk python-pygobject python-pycairo python-netserver python-netclient http://www.opkg.org/packages/1_python-gdata_1.3.0_armv4t.ipk python-misc http://www.opkg.org/packages/0_python-ldap_2.3.6_armv4t.ipk http://www.opkg.org/packages/1_python-dateutil_1.4.1_armv4t.ipk http://www.opkg.org/packages/openldap_2.3.43_armv4t.ipk http://projects.openmoko.org/frs/download.php/887/pisi_0.4.4_armv4t.ipk<br />
<br />
| <br />
<br />
|}<br />
<br />
Configuration example, .pisi/conf to sync contacts and calendar with google calendar and contacts with google mail:<br />
<br />
[googleCalendar]<br />
description=My Google Calendar<br />
module=calendar_google<br />
user=user@gmail.com<br />
password=secret<br />
calendarid=user@gmail.com<br />
<br />
[pimlicodates]<br />
description= Pimlico Dates<br />
module=calendar_ics<br />
path=/home/root/.evolution/calendar/local/system/calendar.ics<br />
<br />
[googlecontacts]<br />
description=Google Contacts Account<br />
module=contacts_google<br />
user=user@gmail.com<br />
password=secret<br />
<br />
[remoteIcs]<br />
description= Remote ICS on Webdav<br />
module=calendar_remoteics<br />
url=http://webdav.davserver.net/private/pim/<br />
file=remotecalendar.ics<br />
username=<LOGIN><br />
password=<PASSWORD><br />
<br />
[shrsim]<br />
description=SHR SIM Card Contacts<br />
module=contacts_dbussim<br />
max_simentries = 250<br />
simentry_name_maxlength=18<br />
<br />
Another way of importing contacts via Vcard file is possible with [gopher://gopher.fnordpol.de/9/data/DbusAccessScripts_0.0.0.tar.gz this] script written by [[User:Zem#DBus_Access_Scripts|Zem]].<br />
<br />
===Reporting bugs===<br />
<br />
SHR is a work in progress. Shell you experience issues, please report them back to SHR. With your report provide logs from<br />
<br />
/var/log/ophonekitd<br />
/var/log/frameworkd<br />
<br />
To report a bug, please go to http://shr-project.org/trac/report<br />
<br />
Check if the bug is already reported. If no, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on.<br />
<br />
==Car Navigation==<br />
''Navit'' is a car navigation system with routing engine. It can calculate a route and do on screen and voice road navigation. Maps need to be downloaded beforehand, please check [http://wiki.navit-project.org/index.php/Main_Page#Maps Navit website]. You can get Openstreetmaps through [http://maps.navit-project.org/download/ Navit map extractor], after you download the map it needs to be specified in the .navit/navit.xml file.<br />
<br />
===Add opkg feed===<br />
To install <tt>navit</tt> as a car navigation system on your freerunner you have to add the feed for the installer <tt>opkg</tt><br />
http://download.navit-project.org/navit/openmoko/svn/<br />
You can do this by: <br />
echo src navit http://download.navit-project.org/navit/openmoko/svn > /etc/opkg/navit-feed.conf<br />
opkg update<br />
<br />
===Install Navit===<br />
Install [[Navit]]:<br />
opkg install navit<br />
Navit will be auto-updated when you run <tt>opkg upgrade</tt> later.<br />
<br />
===Workaround libgps===<br />
Navit on SHR has in the currently available version (08/2009) a <tt>libgps</tt> problem. You solve this by: <br />
opkg install libgps17<br />
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16<br />
<br />
===Install Maps===<br />
Use [http://maps.navit-project.org/download/ Navit pre-processed OSM maps]. With your browser on desktop:<br />
* Navigate to the region you want, <br />
* mark a rectangle for your map (e.g. for Germany) and click select the rectanglular map. <br />
* then click on download and save the file to <tt>country.bin</tt> (e.g. <tt>germany.bin</tt>) on your desktop computer.<br />
* copy the file to on your freerunner. Because of the size of the maps you copy map to the Micro-SD card on your freerunner. Create a directory for the maps and copy the files from desktop to freerunner:<br />
mkdir /media/card/maps<br />
scp germany.bin root@192.168.0.202:/media/card/maps<br />
* Create a directory <tt>.navit</tt> and copy the <tt>navit.xml</tt> to this directory:<br />
mkdir /home/root/.navit <br />
cp /usr/share/navit/navit.xml /home/root/.navit/navit.xml<br />
* Add and enable the map for the application in navit by changing the lines (at approx line number 370)<br />
<!-- Mapset template for openstreetmaps --><br />
<mapset enabled="yes"><br />
<map type="binfile" enabled="yes" data="/media/card/maps/*.bin"/><br />
</mapset><br />
Disable unused mapset sections by setting enabled to <tt>no</tt>, e.g. the pre-installed sample maps at line 370 in <tt>navit.xml</tt>.<br />
<mapset enabled="no"><br />
<xi:include href="$NAVIT_SHAREDIR/maps/*.xml"/><br />
</mapset><br />
<br />
===Start Navit===<br />
Start <tt>Navit</tt> on your Freerunner for your first test. For further configuration details see [[Navit]].<br />
<br />
===No sound after installing Navit===<br />
<br />
Navit tends to depend on speech-dispatcher and after a suspend, the freerunner does not ring anymore for incoming calls or messages, it only vibrates. To correct this remove speech-dispatcher:<br />
<br />
opkg remove -force-depends speech-dispatcher<br />
<br />
==SHR Settings==<br />
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]<br />
<br />
SHR Settings is the main setting application of SHR. In the background it uses [[FSO]] specific dbus calls as well as low level commands. The graphical interface is Elementary-Python based. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).<br />
<br />
While some settings are persistent over reboots, other are not.<br />
<br />
===Main Screen===<br />
Main screen is divided into few categories, which contain modules. Every SHR Settings module has specified task - control GSM antenna power, set actual time etc. <br />
<br />
===Settings: Phone===<br />
Here you can check if the GSM antenna is on and if your phone number is shown when you call someone.<br />
<br />
'''GSM'''<br />
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.<br />
<br />
To list available providers, click on Operators button. Scanning can take some time. After while, list of operators should pop up.<br />
<br />
You can't connect to operators marked [forbidden]. After failed connect, message is displayed.<br />
<br />
Selecting operator from list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.<br />
<br />
'''Call'''<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]<br />
<br />
|}<br />
<br />
You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")<br />
<br />
'''SIM'''<br />
<br />
Here you can view some informations about your SIM card and clean phone and messagebooks.<br />
<br />
'''Others'''<br />
<br />
'''Profile'''<br />
<br />
Here you can select current profile, which device should use to determine ring tone etc.<br />
<br />
'''Current profile'''<br />
<br />
Here you can adjust properties of currently used profile. Available settings: ring tone, ring volume, ring vibration, ring loop, ring length, message tone, message volume, message vibration, message loop, message length.<br />
<br />
To change ring tone, click on "Change" button.<br />
<br />
To use your own ring tone, place it in /usr/share/sounds directory.<br />
<br />
After selecting sid tune as ring tone, there are available controls to select tune number from file.<br />
<br />
<br />
This is changing settings in /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
ring-volume # Ring Volume control 0 (mini) to ? maxi)<br />
ring-length # min time for ringtone. Must be greater than the duration of you ringtone<br />
ring-loop # define the number of loop of ringtone to play<br />
ring-tone: "ringtone_ringnroll.ogg" # .ogg example<br />
ring-tone: "Arkanoid_PSID.sid" # .sid example, use default tune<br />
ring-tone: "Arkanoid_PSID.sid;tune=2" # .sid example, plays the second tune of that<br />
<br />
If you like to test a .sid you can play it using this command on the FR:<br />
<br />
gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink<br />
<br />
Note that it's a ! used and not a | to construct the gstreamer pipe command.<br />
<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]<br />
<br />
|}<br />
<br />
===Settings: Connectivity===<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]<br />
|}<br />
<br />
<br />
'''WiFi'''<br />
<br />
With "WiFi radio" toggle you can set, if wifi module should be powered. WiFi radio has to be turned on before trying to connect to WiFi network, unless you try to connect through Mokonnect which is capable of powering it up.<br />
<br />
'''GPRS'''<br />
<br />
To enter APN, login and password fields, just click on actual value (default: "internet"). Keyboard will pop up.<br />
If you don't know APN, login and passwork, ask your provider.}}<br />
<br />
{{Note|You can also use Mokonnect to manage your Gprs connection}}<br />
<br />
To connect to GPRS network, just click "Connect" button. Entered values will be saved after successful connection.<br />
<br />
'''USB'''<br />
<br />
With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.<br />
<br />
'''Bluetooth'''<br />
<br />
To power up Bluetooth module, swith "Bluetooth radio" toggle to "On". After that, "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.<br />
<br />
===Settings: GPS===<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]<br />
|}<br />
<br />
<br />
<br />
'''GPS'''<br />
<br />
By default, GPS is turned on only when requested (when you turn on TangoGPS, Navit, omgps or other GPS app). That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.<br />
<br />
'''GPS information'''<br />
<br />
This page can be used to monitor GPS status. If some value isn't known, then "unknown" is displayed.<br />
<br />
You can also view information about every visible satellite and check, which are used for getting fix. To do that, just click "Satellite details".<br />
<br />
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.<br />
<br />
===Settings: Date/time===<br />
<br />
[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]<br />
<br />
'''Time'''<br />
<br />
Here you can view and set actual time. By default, time is just displayed, To adjust it, click on "Set time".<br />
<br />
After finishing adjusting, click "OK" button.<br />
<br />
'''Date'''<br />
<br />
This module displays current date.<br />
<br />
===Settings: Power===<br />
<br />
'''Battery'''<br />
<br />
This module displays informations about battery state - charge, voltage, remaining time etc. To update data, click "Update" button.<br />
<br />
Here you also force enable 500mA charging.<br />
<br />
'''Display'''<br />
<br />
With this slider you can easily tweak backlight power.<br />
<br />
{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 100%.}}<br />
<br />
'''Power'''<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Power.png |200px|thumb|Power]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]<br />
|}<br />
<br />
Here you can turn on or off automatic dimming or suspend after idle timeout (see: Timeouts module)<br />
<br />
'''Timeouts'''<br />
<br />
Here you can set up values of idle timeouts used by device. Timeouts are reached in this order: idle -> idle dim -> idle prelock -> lock -> suspend. Idle, idle prelock and lock aren't used by default in SHR at the moment. This setting changes parameters in /etc/frameworkd.conf :<br />
<br />
[odeviced.idlenotifier]<br />
suspend = 20<br />
lock = 2<br />
idle_prelock = 12<br />
idle = 10<br />
idle_dim = 20<br />
<br />
===Settings: Services===<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]<br />
|}<br />
<br />
Here is listed every interesting script from /etc/init.d/ directory.<br />
<br />
After clicking on some, you can either start, restart or stop service and view result.<br />
<br />
===Settings: Others===<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Others.png |200px|thumb|Others]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Splash-Preview.png |200px|thumb|Splash preview]]<br />
|}<br />
<br />
'''Splash'''<br />
<br />
With this selector you can select theme used by shr-splash at boot and shutdown. After clicking "Preview", selected boot image will be displayed for 5 seconds.<br />
<br />
'''PIM'''<br />
<br />
Module used by opimd developers. Doesn't have influence on behaviour of default SHR image.<br />
<br />
Every opimd domain has different backends to store it's data. The domain reads data from every backend and writes data to the default backend. So with the selector in shr-settings you can choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.<br />
<br />
'''Userspace backups'''<br />
<br />
Here you can either archive or restore your files and configurations.<br />
<br />
'''Image information'''<br />
<br />
This module contains basic information about installed image - name of buildhost, used revision, branch and time of build.<br />
<br />
'''Theming'''<br />
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]<br />
Find available themes by running <br />
<br />
opkg list | grep theme-illume<br />
<br />
install it by<br />
<br />
opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen<br />
<br />
http://opkg.org has a very fast theme called nEo<br />
<br />
opkg install http://www.opkg.org/packages/e-wm-theme-neo_0.2_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/elementary-theme-neo_0.2_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/etk-theme-neo_0.2_armv4t.ipk<br />
opkg install -force-overwrite http://www.opkg.org/packages/libframeworkd-phonegui-efl-theme-neo_0.2_armv4t.ipk<br />
<br />
If you also want the GTK+ Applications to fit in with the rest of the Systems look execute<br />
<br />
opkg install http://www.opkg.org/packages/gtk-theme-neo_0.1_armv4t.ipk<br />
<br />
For a completely monolithic look additionally execute<br />
<br />
opkg install -force-overwrite http://www.opkg.org/packages/gpe-theme-neo_0.1_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/icon-theme-neo_0.2_armv4t.ipk<br />
<br />
Please observe the command line output when installing these themes, since it will tell you how to activate the themes.<br />
<br />
{{Note|some of the theme packages have to be reinstalled after an opkg upgrade.}}<br />
<br />
Reverting back can be done by <br />
<br />
opkg install e-wm-theme-illume-sixteen shr-theme-gtk-e17lookalike -force-reinstall<br />
opkg install libframeworkd-phonegui-efl0 e-wm-theme-default etk-theme-shr shr-theme -force-reinstall<br />
<br />
==FSO Resources==<br />
<br />
FSO is in control of each device. These are called resources. If the software wanting to use the device is capable of requesting this resource via d-bus, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through SHR Setting or you can use fsoraw command. (Using fsoraw is faster and better then running dbus commands)<br />
<br />
opkg install fsoraw<br />
<br />
Example of usage fsoraw:<br />
<br />
fsoraw -r Display mokomaze<br />
<br />
'''Wifi'''<br />
<br />
Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the network manager to set up networks, Mokonnect will power Wifi up automatically when needed.<br />
<br />
'''Bluetooth'''<br />
<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
'''GPS'''<br />
<br />
The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off<br />
<br />
'''GSM'''<br />
<br />
You need to have this resource requested to have GSM module powered.<br />
<br />
'''Display'''<br />
<br />
While this resource is requested the display won't be blanked and suspend is disabled.<br />
<br />
'''CPU'''<br />
<br />
Default rules.yaml checks for this resource to disable automatic suspend when it's requested. While this resource is kept suspend is disabled (but screen can be blanked).<br />
<br />
'''Test'''<br />
<br />
A test resource<br />
<br />
==Network manager==<br />
<br />
While there are several ways of networking - Wifi, USB, Bluetooth and Gprs - By default, USB networking is enabled in /etc/network/interfaces.<br />
<br />
Enhanced configuration is possible through direct editing of /etc/network/interfaces or through Mokonnect.<br />
<br />
Connmand daemon with Mokonnect are the recommended user level applications for setting up networking. At the moment, Mokonnect can manage USB, Wifi and Gprs connections, as well as routing and NAT. Wifi device is not required to be manually turned on via SHR-Settings as Mokonnect will automatically enable the device when needed and disable after use.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-Mokonnect.png|200px|thumb|Mokonnect]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokonnect-Wifi.png|200px|thumb|Mokonnect Wifi]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokonnect-Wifi-Scan.png|200px|thumb|Mokonnect Wifi Scan]]<br />
<br />
<br />
|}<br />
<br />
==Bluetooth==<br />
<br />
Bluetooth can be used for several different applications - file transfer, networking, HIDD, music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better then for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if it is not around, making it quite difficult to use.<br />
<br />
Don't forget you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On, where you can also make the bluetooth device visible.<br />
<br />
SHR user bluez4 which completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see http://wiki.openmoko.org/wiki/Manually_using_Bluetooth for detailed information about using bluetooth and also for list of supported devices.<br />
<br />
===OBEX file transfer===<br />
<br />
There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:<br />
<br />
opkg install obexpush<br />
<br />
Default receiving path (editable in /etc/default/opd_args ) doesn exist, so create it<br />
<br />
mkdir /var/obexpush<br />
<br />
Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush<br />
<br />
To send some files, first scan for devices:<br />
<br />
hcitool scan<br />
Scanning ...<br />
00:16:41:F5:A5:BC laptop<br />
<br />
Then send it onto bt address found in the scan:<br />
<br />
obextool push image.jpg 00:16:41:F5:A5:BC 10<br />
<br />
It would be nice to install the [[Coypu]] utility to send files via Bluetooth<br />
<br />
opkg install http://minucci.net/file/opkg/coypu_0.1_all.opk<br />
<br />
but at the moment the version mentioned above starts but does not work under SHR.<br />
<br />
===Connect Bluetooth keyboard===<br />
<br />
hidd --search<br />
<br />
===Pairing===<br />
<br />
This comes from http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner<br />
<br />
Now, you must pair the bluetooth headset with your Freerunner. Make sure the bluetooth chip is powered up (can be done through the Connectivity section in the SHR-Unstable settings manager) and that bluetoothd is running:<br />
/etc/init.d/bluetooth start<br />
Now, to actually pair the bluetooth headset, you will need the simple-agent script. If you already have it, excellent. If you, like me, do not, then you can get it here: http://dl.getdropbox.com/u/453116/simple-agent<br />
<br />
Put it in /usr/bin/ and run ===chmod a+x /usr/bin/simple-agent===<br />
<br />
Now put your headset into pairing mode and run <br />
<br />
hcitool scan<br />
<br />
Find your headset and use its address in the command <br />
<br />
simple-agent hci0 XX:XX:XX:XX:XX:XX<br />
<br />
If you give a third parameter (what it is doesn't matter) to simple-agent, it will disconnect then reconnect to the headset (reset pairing).<br />
<br />
===GSM phonealls with bluetooth headset===<br />
<br />
Your bluetooth headset device must be paired first.<br />
<br />
====Configuring bluez====<br />
<br />
Older SHR releases you need to uncomment <tt>SCORouting=PCM</tt> setting in <tt>[General]</tt> section of<br />
<br />
/etc/bluetooth/audio.conf<br />
<br />
like this:<br />
<br />
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA) <br />
# Defaults to HCI <br />
SCORouting=PCM <br />
<br />
do not forget to restart bluetoothd after that.<br />
<br />
/etc/init.d/bluetooth stop<br />
/etc/init.d/bluetooth start<br />
<br />
====Configuring FSO====<br />
<br />
Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in<br />
<br />
/etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).<br />
<br />
You need to restart FSO for the changes to take effect.<br />
<br />
/etc/init.d/frameworkd restart<br />
<br />
example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:<br />
<br />
message-length: 7<br />
message-tone: notify_message.wav<br />
message-vibration: 1<br />
message-volume: 10<br />
ring-loop: 1<br />
ring-tone: ringtone_ringnroll.wav<br />
ring-vibration: 1<br />
ring-volume: 10<br />
bt-headset-enabled: 1<br />
bt-headset-address: 00:09:DD:31:92:98<br />
<br />
====Connecting and reconnecting the bt device====<br />
<br />
You might need to get the bluetooth headset connected manually on the beginning and also after suspend:<br />
<br />
mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect<br />
<br />
where xx_xx_xx_xx_xx_xx is address of the device, for example:<br />
<br />
mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect<br />
<br />
Hopefully, your bluetooth headset now works. Good luck!<br />
<br />
==System Customizing==<br />
<br />
===Changing the splash screen===<br />
<br />
list available splash screen themes<br />
<br />
opkg list | grep splash-theme<br />
<br />
and install one of the available themes<br />
<br />
opkg install shr-splash-theme-dontpanic<br />
<br />
Then go to SHR Settings -> Others -> Themes. Here you can preview installed themes and change the default one.<br />
<br />
===Install functional alarm application===<br />
<br />
opkg remove -force-depends elementary-alarm; opkg install ffalarms<br />
<br />
===Enable mouse cursor=== <br />
<br />
edit line 121 of /etc/X11/Xinit and erase -hide-cursor<br />
<br />
ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} -mouse tslib -root-ppm /usr/share/pixmaps/xsplash-vga.ppm vt1"<br />
<br />
===Improve speed of Elementary applications===<br />
<br />
Set the Elementary rendering engine used for Evas to x11-16 (Software X11 16bpp engine, may have bugs and will be lower quality, but faster):<br />
echo -e "#!/bin/sh\n\nexport ELM_ENGINE=x11-16" > /etc/profile.d/set-elm-engine.sh<br />
<br />
<br />
Additionally in the SHR-Unstable repositories there are theme packages optimized for 16bpp color. Both packages can be installed with the following command:<br />
<br />
opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen<br />
<br />
You can then append the /etc/profile.d/set-elm-engine.sh with:<br />
<br />
# Set Optimized theme<br />
export ELM_THEME=sixteen<br />
<br />
You can also then change Illume to use the sixteen theme by clicking the wrench->Look->Theme-illume-sixteen->OK. Then switch Illume to use the 16bpp Engine by clicking the wrench->Advanced(you will need to drag and slide the top menu)->Engine->Software_16->OK. This should give you a much faster interface without the low quality look the default SHR themes have at this lower color depth.<br />
<br />
Read http://trac.enlightenment.org/e/wiki/Elementary<br />
<br />
If you try to change Wallpaper or Theme and Illume keeps on crashing, it might be caused by the whole Illume running in Software_16 mode. Go to Illume Settings, slide the icon bar and select Advanced. There tap on Engine and select Software. After this, you can change your Wallpaper or Theme. Selecting Software_16 later on again will speed up the desktop's response (though causing it to be a bit uglier).<br />
<br />
===Speedup of suspend and wake up===<br />
<br />
I you are using Qi and installation on µSD card, you can change the kernel parameter loglevel=1 1 in /boot/append-GTA02 . For u-boot and installation in nand just type<br />
<br />
klogd -c 1<br />
<br />
into the console. This saves you from 3 seconds worth of console output on every resume.<br />
<br />
If you like the effect of this command and want it to be executed at every startup, you just have to log into your phone and type the following:<br />
<br />
cat > /etc/init.d/resumespeedup << EOF<br />
#!/bin/sh<br />
/sbin/klogd -c 1<br />
EOF<br />
chmod +x /etc/init.d/resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc1.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc2.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc3.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc4.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc5.d/S06resumespeedup<br />
<br />
===Opimd utils===<br />
<br />
Opimd utils is a set of several testing scripts to play with the new opimd backends. It also provides opimd-messages program and mainly new opimd-notifier that is much better then the standard one.<br />
<br />
opkg install opimd-utils<br />
<br />
===opkg upgrade issues===<br />
<br />
As '''opkg''' had some '''issues''' recently, installation might get broken due to that. You can fix it or prevent by using the following scripts<br />
<br />
Safe update packages:<br />
<br />
#!/bin/sh<br />
<br />
opkg list_upgradable | awk '!/(kernel|Multiple)/ {print $1}' | \<br />
while read line; do<br />
echo "installing pack $line"<br />
opkg install $line -force-reinstall<br />
done<br />
<br />
<br />
Force reinstall all installed packages<br />
<br />
#!/bin/sh<br />
<br />
opkg list_installed | awk '!/(kernel|Multiple)/ {print $1}' | \<br />
while read line; do<br />
echo "installing pack $line"<br />
opkg install $line -force-reinstall<br />
done<br />
<br />
<br />
===Random errors===<br />
No icons, no GSM functions etc. - this is mostly due to '''errors on your uSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.<br />
<br />
For reboot into nand and fix 1st partition of ext2 on your card<br />
<br />
fsck.ext2 /dev/mmcblk0p1<br />
<br />
===Replace dropbear with openssh===<br />
<br />
Set password<br />
passwd<br />
<br />
Install ssh server (and sftp)<br />
opkg install openssh-sshd openssh-sftp-server openssh-scp -force-depends<br />
<br />
Remove dropbear and start openssh<br />
<br />
screen<br />
opkg remove dropbear -force-depends; /etc/init.d/sshd start<br />
<br />
You will get disconnected from the ssh session, wait until keys get generated and log in again<br />
<br />
===Video playback===<br />
<br />
Install intone-video<br />
<br />
opkg install elementary libsqlite3-0 http://www.opkg.org/packages/intone-video_0.11_arm.ipk<br />
<br />
If intone complaints about missing libraries, please run <br />
#!/bin/sh<br />
cd /usr/lib<br />
ls *ver-svn-02*|while read nombre<br />
do<br />
final="`echo $nombre | sed s/-ver-svn-02/-ver-pre-svn-01/`"<br />
ln -s /usr/lib/$nombre /usr/lib/$final<br />
done<br />
<br />
On your desktop, encode your video:<br />
<br />
mencoder video-file -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf scale=320:240,eq2=1.2:0.5:-.025,rotate=2 -oac mp3lame -lameopts br=64:cbr -o video-file-FR.avi<br />
<br />
Adding=== freerunner to your hosts=== file for a name resolving:<br />
<br />
You can use the name <tt>neo</tt> if you added the host <tt>neo</tt> in <tt>/etc/hosts</tt> on your desktop computer (add the following line for host <tt>neo</tt> assuming that the IP-address of your freerunner is <tt>192.168.0.202</tt>.<br />
echo "192.168.0.202 neo neo" >> /etc/hosts<br />
<br />
You can then access your freerunner like this:<br />
<br />
ssh root@neo<br />
<br />
Which is shorter then this:<br />
<br />
ssh root@192.168.0.202<br />
<br />
==Installing Software==<br />
<br />
You can use opkg for installing software packages or you can try SHR Installer from http://git.shr-project.org/git/?p=shr-installer.git;a=summary . It requires packagekitd<br />
<br />
opkg install packagekitd<br />
<br />
If you wan to use opkg after you used the installer, make sure packagekitd is not running<br />
<br />
killall packagekitd <br />
<br />
'''Cool applications'''<br />
<br />
SHR comes with only few preinstalled applications but it's repository provides more cool stuff. Also, there are applications that are not in SHR repos at the moment but can still be installed. The following few examples are here just to spark your interest:<br />
<br />
'''SHR Launcher'''<br />
<br />
[[Image:Launcher.png|200px|thumb|SHR Launcher]]<br />
Launcher is elementary based alternative home screen application and event notifier for SHR. It displays current time, has a user tweak-able launcher with categories and features missed calls and messages applets.<br />
<br />
opkg install libsqlite3-0 http://www.opkg.org/packages/launcher_0.23_arm.ipk<br />
<br />
For '''PIM''' applications you can get dates for calendar, tasks for todos, neote for notes:<br />
<br />
opkg install dates tasks<br />
<br />
opkg install http://neote.googlecode.com/files/neote_0.2.0-r0_all.ipk<br />
<br />
GPE contacts saves the contacts in a SQLite database that can be synchronized with VCard files. Gpe-contacts don't allow you to dial directly via shr-dialer. Install gpe-contacts:<br />
<br />
opkg install gpe-contacts<br />
<br />
After installation you'll find to icons with ''MyVCard''. If you want to remove it, delete the file <tt>/usr/share/applications/edit-vcard.desktop</tt><br />
<br />
'''Litephone'''<br />
<br />
[[Image:SHR-Litephone.png|200px|left|thumb|Litephone]]<br />
<br />
Litephone is new alternative set of phone applications written in Qt. In it's single application interface it provides basic phone functionality (contacts, calls, messages, phone log, settings). It's main advantage is that it uses opimd for storage of the user data.<br />
<br />
opkg install http://pvtrace.com/litephone/libqtcore4_4.4.3-r3_armv4t.ipk<br />
opkg install http://pvtrace.com/litephone/libqtxml4_4.4.3-r3_armv4t.ipk<br />
opkg install http://pvtrace.com/litephone/libqtdbus4_4.4.3-r3_armv4t.ipk <br />
opkg install http://pvtrace.com/litephone/libqtgui4_4.4.3-r3_armv4t.ipk <br />
opkg install http://pvtrace.com/litephone/qt4-x11-free_4.4.3-r3_armv4t.ipk<br />
opkg install http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk <br />
<br />
'''Mokomaze''' is an excelent eye-candy game using accelerators embedded in your device.<br />
<br />
opkg install mokomaze<br />
<br />
If you tweak the exec procedure in /usr/share/applications/mokomaze.desktop into this:<br />
fsoraw -r Display mokomaze<br />
the screen will not blank while playing.<br />
<br />
'''CellHunter''' is a game to collect information about mobile phone cells. This information can later be used to roughly determine your position without powering on the GPS chip. [http://78.47.116.33/~hole/cellhunter/ CellHunter homepage]<br />
<br />
opkg install cellhunter<br />
<br />
'''OMGps''' and '''TangoGPS''' are GPS application showing you your position on a map (Openstreetmap, Google maps etc.). You can track your position, save it and use later, save and view points of interest, images or measure your trip. OMGps allows you to overlay different maps on top of each other, set GPS into different modes (walking, car, flying). Maps are downloaded online and used even in offline. <br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-TangoGPS-OSM.png|200px|thumb|TangoGPS]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-OMGPS-GM.png |200px|thumb|OMGps]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokomaze.png|200px|thumb|Mokomaze]]<br />
<br />
<br />
|}<br />
<br />
'''Screenshots''' can be made with ''gpe-scap''(available by default in SHR full image). To take a screenshot, run gpe-scan from shell while connected in via ssh.<br />
<br />
<br />
'''Literki''' is full qwerty keyboard with configurable layout, always transparent, therefore applications don't need to redraw screens and popup is therefore very fast. The keys are big enough for everyday use with your fat fingers. To pop up the keyboard: slide your finger upwards from the bottom right corner. To hide the keyboard: slide your finger down on the keyboard. [http://www.opkg.org/package_232.html Opkg page]<br />
<br />
opkg install http://pvtrace.com/literki_0.0.2-r3_armv4t.ipk<br />
<br />
[[Category:SHR]]</div>Dareushttp://openmoko.org/wiki/Talk:Manuals/SHRTalk:Manuals/SHR2009-08-10T10:39:22Z<p>Dareus: </p>
<hr />
<div>This is the infrastructural page of the SHR User Manual.<br />
Decisions of discussions should go here.<br />
<br />
<br />
===Sources of info===<br />
<br />
http://shr-project.org/trac/wiki/Tweaks<br />
<br />
http://shr-project.org/trac/wiki/Customize<br />
<br />
http://wiki.openmoko.org/wiki/SHR<br />
<br />
http://openmoko.opendevice.org/~dos/manual/<br />
<br />
===Base ground===<br />
<br />
SHR Unstable will be used for this manual.<br />
<br />
===Screenshots===<br />
<br />
Screenshots should be based on one, default theme: Illume-SHR.<br />
<br />
===Questions for discussion===<br />
<br />
name of this guide/manual/introduction/howto...<br />
<br />
===Manuals standardisation===<br />
<br />
Hi! I'm one of the wiki maintainers here. I have recently started an effort to standardise manuals on this wiki - see http://n2.nabble.com/organizing-manuals-on-the-wiki-tp3302919p3302919.html for my posts to the documentation mailing list. I'm planning to create some standards for writing manuals which would become part of the [[Openmoko Wiki Editing Guidelines]]. For the SHR manual implementing those standards would mean that some parts of the section "Installation" would be moved to individual device-manuals. Furthermore this manual would probably be moved to a page like [[Manuals/SHR]]. What do you think about this? I'd appreciate any comments from you. --[[User:Marko Knöbl|Marko Knöbl]] 21:55, 24 July 2009 (UTC)<br />
<br />
I am ok with this but let the draft develop here as part of the cofundus project till August 31st --[[User:Rakshat|Rakshat]] 09:18, 27 July 2009 (UTC)<br />
<br />
Hi, i am the writer of this page. I have previously already moved the page to Manuals/SHR but i can see that you moved it back. I don't really care about the location as the wiki is only part of the release. --[[User:Vanous|Vanous]] 09:10, 29 July 2009 (UTC)<br />
<br />
===Work in progress===<br />
<br />
Started adding screenshots and texts. At this point, i don't care about formatting at all. --[[User:Vanous|Vanous]] 09:41, 29 July 2009 (UTC)<br />
<br />
Formatted already. Typo corrections welcomed --[[User:Vanous|Vanous]] 10:57, 31 July 2009 (UTC)<br />
<br />
Added SHR Settings screenshots, need to be formatted --[[User:Vanous|Vanous]] 13:09, 31 July 2009 (UTC)<br />
<br />
The Car Navigation system (Navit) section may be better lower down the Manual, in the application section. --[[User:Rakshat|Rakshat]] 18:27, 8 August 2009 (UTC)<br />
<br />
hihi, didn't read your comment but moved it already :))) will move it even further after things get a bit clearer here :)<br />
--[[User:Vanous|Vanous]] 09:37, 9 August 2009 (UTC)<br />
<br />
Vanous's note not to forget this:<br />
<br />
settings for /etc/phone-utils.conf. I know this file has to do with<br />
making sure that the phone can resolve both an international phone<br />
number and a normal phone number to the correct contact (i.e. incoming<br />
calls/messages for +31612345*** and 0612345*** will both be<br />
recognised as coming from one contact).<br />
<br />
More info (although the configuration file has moved since then):<br />
http://n2.nabble.com/Full-contact-name-handling-in-calls---messages-td2935624.html<br />
--[[User:Vanous|Vanous]] 09:37, 9 August 2009 (UTC)<br />
<br />
The Navit section will need to be reviewed as SHR-u provides navit (older version i think). For now it's good though.<br />
<br />
==Table of contents==<br />
<br />
I think that the toc should be on the left for consistency. right alignment is good for rtl language (not english or other western languages)<br />
[[User:Dareus|Dareus]]</div>Dareushttp://openmoko.org/wiki/SHR_User_ManualSHR User Manual2009-08-10T08:51:08Z<p>Dareus: align left for consistence</p>
<hr />
<div>{{Languages|SHR User Manual}}<br />
{| align="left"<br />
| __TOC__<br />
|}<br />
<br />
<br />
I consider this a draft already, please [[Talk:SHR_User_Manual|Comment here]] --[[User:Vanous|Vanous]] 11:47, 6 August 2009 (UTC)<br />
<br />
New SHR users, readers, please do report improvements, discrepancies or missing features to vanous @ penguin . cz<br />
<br />
<br />
==SHR Introduction==<br />
<br />
Welcome to '''[[SHR]]''', the world of community driven distribution for (not only) OpenmokoNeo phones.<br />
<br />
'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install onto your Freerunner to use is as a daily phone. It's filled with prepackaged software that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. SHR unstable is a testing environment before software get stabilized and it is the main testing ground for [[FSO]] releases. SHR testing images (currently not available) provide as much stability as possible for day-to-day usage.<br />
<br />
'''SHR''' has been evolving from a simple release of customized software into a full distribution. Therefore, in SHR you can choose from several different graphical toolkits (for example GTK or EFL), different phone managers (SHR or Zhone), web browsers and other programs.<br />
<br />
The SHR Team is busy with system maintenance and software building so you can concentrate on programming, using and [http://shr-project.org/trac/report reporting bugs].<br />
<br />
[http://shr-project.org SHR Project page]<br />
<br />
==SHR Specific==<br />
<br />
At this point, there are some applications and procedures that are purely specific to SHR and would not run on another distribution. For example the phone applications (Dialer, Messages and Contacts) and SHR Settings depend heavily on the ophonekitd daemon.<br />
<br />
As SHR is based on [[FSO]], basically any application using FSO has a chance to run, should all required libraries be available.<br />
<br />
==Stability==<br />
<br />
While many people use SHR as their daily phone, there are still occasional glitches and issues. This hurts the most when GSM stops working but this happens less and less. We wish you to have the best experiences with SHR.<br />
<br />
==Installation==<br />
<br />
===Getting SHR===<br />
<br />
First, determine which model of phone you have, the GTA01(neo1973) or the GTA02(FreeRunner).<br />
<br />
You need to download two files for your version as above, kernel and root filesystem. Depending whether you will be installing into the internal nand memory or on µSD card, you need to either get .jffs2 file for nand or .tar.gz file for µSD.<br />
<br />
At this point, there are no recent testing images so for the GTA02 Freerunner you need to download the images of unstable release from http://build.shr-project.org/shr-unstable/images/om-gta02/<br />
<br />
- Get the latest kernel: [http://build.shr-project.org/shr-unstable/images/om-gta02/uImage-om-gta02-latest.bin uImage-om-gta02-latest.bin]<br />
<br />
- Get the root filesystem, for nand: [http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.jffs2 shr-image-om-gta02.jffs2], (for µSD): [http://build.shr-project.org/shr-unstable/images/om-gta02/shr-image-om-gta02.tar.gz shr-image-om-gta02.tar.gz]<br />
<br />
These are full images. You can also choose image with less packages, marked as '''lite''' which can be upgraded to the full image by running<br />
<br />
opkg update<br />
opkg task-shr-apps task-shr-games task-shr-gtk<br />
<br />
===Source code===<br />
<br />
View the sources at http://git.shr-project.org/git/<br />
<br />
<br />
===Image content===<br />
{|class="wikitable" border="1" cellpadding="0" cellspacing="0" width=100%<br />
<br />
! width=16%| !! width=42%|Full image content !! width=42%|SHR-Image LITE Content<br />
|-<br />
| Window Manager || <br />
* illume<br />
||<br />
* illume<br />
|-<br />
| Engine ||<br />
* frameworkd<br />
||<br />
* frameworkd<br />
|-<br />
| Telephony || <br />
* Dialer (Call/Receive, DTMF, Speaker mode)<br />
* SIM Contacts (Call/Modify/Create/...)<br />
* SIM Messages (Receive/Compose/Answer/...)<br />
* Pyphonelog (received/emitted/missed calls logging)<br />
|| <br />
* Dialer (Call/Receive, DTMF, Speaker mode)<br />
* SIM Contacts (Call/Modify/Create/...)<br />
* SIM Messages (Receive/Compose/Answer/...)<br />
* Pyphonelog (received/emitted/missed calls logging)<br />
|-<br />
| GPS || <br />
* TangoGPS<br />
|| <br />
* TangoGPS<br />
|-<br />
| Utilities ||<br />
* Calculator<br />
* Alarm<br />
* GPE Scap (Take screenshot)<br />
* GPE File Manager<br />
* GPE Sketchbook<br />
* vala-terminal<br />
||<br />
* Calculator<br />
* Alarm<br />
* GPE File Manager<br />
* vala-terminal<br />
<br />
|-<br />
<br />
| Media ||<br />
<br />
* Vagalume<br />
* Intone <br />
||<br />
* pythm <br />
<br />
|-<br />
<br />
| Internet ||<br />
* Pidgin<br />
* Midori (Browser) <br />
||<br />
<br />
|-<br />
<br />
| Games ||<br />
* Numptyphysics <br />
||<br />
|-<br />
| Settings ||<br />
* SHR Settings<br />
* Mokonnect (Network Manager) <br />
|| <br />
* SHR Settings<br />
<br />
<br />
<br />
|-<br />
|}<br />
<br />
===Installation on Flash===<br />
<br />
In order to install your SHR distribution directly to your Freerunner Flash memory (NAND), you need to get the desired filesystem file ( .jffs2 ) as described above and flash your device using the dfu-util tool.<br />
<br />
Please visit [[Flashing_the_Neo_FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.<br />
<br />
Command to flash the filesystem and the kernel<br />
<br />
dfu-util -a rootfs -R -D shr-image-om-gta02.jffs2<br />
dfu-util -a kernel -R -D uImage-om-gta02-latest.bin<br />
<br />
===Installation on µSD Card===<br />
<br />
Installing SHR on your µSD Card depends on the Bootloader you are using, uBoot or Qi.<br />
<br />
In simply words, difference between both systems resides on how you must prepare your µSD Card and files you use to fill them:<br />
<br />
If you use uBoot, you need to create two partitions. First partition, not so big, in FAT16 where you have to place the kernel file (uImage-om-gta02-latest.bin) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (shr-image-om-gta02.tar.gz).<br />
<br />
If you use Qi, you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (shr-image-om-gta02.tar.gz). In this case Qi Bootloader is going to look for the kernel image into the /boot directory for file named uImage-GTA02.bin .<br />
<br />
Please visit links bellow for detailed information and tips:<br />
<br />
For [[Booting from SD | uBoot]] and for [[Qi]].<br />
<br />
===SHR version===<br />
<br />
Shell you ever later wonder what version of SHR you have actually installed, please run<br />
<br />
cat /etc/shr-version<br />
<br />
or check SHR Settings -> Other -> Image information<br />
<br />
==Running SHR==<br />
===Booting===<br />
Press the power button shortly once to start the Freerunner. Booting splash screen will appear. First boot after new installation takes always a bit longer. Sometimes, it is recommended to reboot after this first boot, to make sure all packages got initialized properly.<br />
<br />
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]<br />
<br />
===Initial Setup===<br />
<br />
[[Image:SHR-Setup-Language.png|200px|thumb|Initial setup]]<br />
On the first boot, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. You are able to choose preferred language of the desktop environment, Illume SHR themed profile or select default menu (only one at the moment). <br />
<br />
On the Add icon screen you can add icons for some application. If you add a terminal based application like mplayer, you will see an icon but no application running upon click, as it will run in the background. <br />
Last screen allow settin up quick launch applications.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Setup-Profile.png|200px|thumb|Theme profile]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Setup-Menu.png|200px|thumb|Menu]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Setup-Add-Icons.png|200px|thumb|Add icons]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
<br />
[[Image:SHR-Setup-Quick-Launch.png|200px|thumb|Quick launch]]<br />
<br />
|}<br />
<br />
===SIM Auth===<br />
<br />
[[Image:SHR-SIM-Auth.png|200px|thumb|SIM Auth]]<br />
SIM Pin is asked for upon start up.<br />
<br />
===First look===<br />
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]<br />
'''Illume desktop''' is default home screen of the SHR desktop. Application files located in /usr/share/applications are displayed here. All applications are ran fullscreen and you can switch between them by using the Task switcher in the Top Shelve or by using the < left or right > arrows in the Top Shelve.<br />
<br />
The Illume desktop can be easily customized - slide the Top Shelve down and tap the Settings icon (Wrench).<br />
<br />
{{Note|TIP: for better access of the Settings icon, tap and hold the Settings icon, then drag it to the right.}}<br />
<br />
'''Illume settings''' provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to preview more options on the right hand side.<br />
<br />
The little applets in the Top Shelve (for example Battery, GSM, Bluetooth etc.) are called '''Shelve gadgets''' and you can configure whether they are visible (on the front part of the top shelve) or hidden (you can access them by sliding the top shelve) through Illume Settings -> Display -> Shelve gadget.<br />
<br />
Some screens are not resized properly to fit the Freerunner's display - for example the Wallpapper setting. This is a known bug already reported upstream.<br />
<br />
<!-- [[Image:SHR-Top-Shelve.png|200px|thumb|Top Shelve]] --><br />
<br />
===Phone applications===<br />
<br />
Besides other software, SHR comes with 4 main phone applications: Dialer, Contacts, Messages and Phone log.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Dialer.png|200px|thumb|Dialer]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contacts.png|200px|thumb|Contacts]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contacts-Options.png|200px|thumb|Contact options]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contact-Add.png|200px|thumb|Add new contact]]<br />
|}<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Mesages.png|200px|thumb|Messages]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Messages-Options.png|200px|thumb|Messages options]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Message-View.png|200px|thumb|View message]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Message-View-chars.png|200px|thumb|Unicode support]]<br />
<br />
|}<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Mesages-Options.png|200px|thumb|Message options]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Phonelog.png|200px|thumb|Phonelog]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Dialer-Active.png|200px|thumb|Active call]]<br />
<br />
|}<br />
<br />
Upon a missed call or an unread message there is a Notifier that presents a screen with button to run Messages or Phonelog application, or you can simply close the Notifier with the Top Shelve cross.<br />
<br />
===Under the hood===<br />
<br />
SHR is based on linux kernel and Openembedded. XGlamo 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 ophonekitd daemon is run with X server start up and it communicates with FSO via d-bus. SHR phone applications talk to ophonekitd 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 libframeworkd-phonegui-efl library, Phonelog is an extra application written in python-gtk.<br />
<br />
===First steps===<br />
<br />
Right after installation and first boot you might want to do a few initial steps:<br />
<br />
'''Establish network connection''' and SSH into your Freerunner. The root account uses no password by default. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi. If you use USB, some setup is required on the desktop side, please read [[USB_Networking]]. For Wifi, you can use [[#Network manager|Network Manager]]<br />
<br />
'''Check if GSM is working correctly''' - observe the GSM gadget in the Top Shelve and see reported signal of your GSM operator <br />
<br />
'''Check and set call volume''' - this is handled by alsa state files in /usr/share/shr/scenarii/ . To customize speaker volume edit /usr/share/shr/scenarii/gsmheadset.state and change control 4. Values between from 105 to 120 might be sufficient.<br />
<br />
Shell you want to alter more parameters be aware that each file is a set of value for the 94 parameters. Some of the important ones are:<br />
<br />
Control 48: internal mic of the tel (set to 2 or 3)<br />
Control 4 : internal speaker (set from 110 to 120)<br />
Control 49: headset mic<br />
Control 3 : headset speaker<br />
<br />
'''Initialize opkg database''' in order to install some applications from SHR repositories or from other sources, for example [[http://opkg.org opkg.org]]. While still being online, you need to first run<br />
<br />
opkg update<br />
<br />
Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through.<br />
<br />
Do this only once or after every opkg update:<br />
<br />
opkg list > packages.txt<br />
<br />
Then you can search quickly for package name, for example for navit:<br />
<br />
grep navit packages.txt<br />
<br />
'''SwapSpace'''<br />
<br />
The Freerunner has only 128mb ram, when this is used up applications get killed. This is particularly bad while doing opkg upgrade.<br />
<br />
WARNING: this mights kill your sd card, since there might be a lot of read/writes to the same spot. <br />
<br />
dd if=/dev/zero of=/swapfile bs=1024 count=65536<br />
<br />
Add a line to fstab so next time you boot there will be swap<br />
<br />
echo "/swapfile swap swap defaults 0 0">> /etc/fstab <br />
<br />
Make swap<br />
<br />
mkswap /swapfile<br />
<br />
Make the swap file work now:<br />
<br />
swapon /swapfile<br />
<br />
'''Changing root password'''<br />
<br />
SHR is shipped without root password (just press enter)<br />
<br />
This is very dangerous if you connect using wifi, or USB. You need to activate the root password:<br />
<br />
passwd<br />
<br />
then type your selected password (2 times)<br />
<br />
Install '''sms-sentry''' to be able to locate your phone in case of lost or theft:<br />
<br />
opkg install sms-sentry<br />
<br />
Then, upon sending an sms with text sentry:location to your Freerunner, the phone will turn on GPS, wait for a fix and send back sms with current location.<br />
<br />
===Localization===<br />
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]<br />
<br />
You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in Illume Top Shelve go to Wrench (Settings) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.<br />
<br />
You can list all available languages by running:<br />
<br />
opkg list | grep glibc-locale-<br />
<br />
And install the language of your choice (for example czech):<br />
<br />
opkg install glibc-locale-cs<br />
<br />
After this, the Language Settings of Illume will offer Czech. <br />
<br />
<br />
This will localize the Illume environment and will also set correct lang environment variable. If you wish to have translations for other applications, you need to install them again (presuming they are available):<br />
<br />
This will install czech localisation for SHR phone applications, SHR Settings and TangoGps:<br />
<br />
opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs<br />
<br />
For localized terminal environment (ssh login) set lang variables set /etc/profile, example for Czech language:<br />
<br />
export LANG=cs_CZ<br />
export LC_ALL=cs_CZ<br />
<br />
<br />
The Illume keyboard offers english dictionary correction by default. You can list all the dictionaries available for installation:<br />
<br />
opkg list | grep illume-dic<br />
<br />
<br />
If your language is not available and english is bothering you, you can set an empty dictionary:<br />
<br />
echo "" > /usr/lib/enlightenment/modules/illume/dicts/None.dic<br />
<br />
By using it, it will get filled by the words you use and after time will start helping and correcting your typing.<br />
<br />
===Date and time===<br />
<br />
Timezone is automatically retrieved from the GSM network. Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically after several minutes.<br />
<br />
Time can set time also manually.<br />
<br />
Via SHR-Settings -> Date/time -> Set time<br />
<br />
From linux based desktop:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
You can also set the hardware clock to the system time:<br />
<br />
hwclock --systohc<br />
<br />
===File transfer===<br />
<br />
After you have established network connection, it is very easy to access and transfer files. The easiest solution is to use Konqueror or Nautilus on your desktop computer and type the following on your location bar. This should provide you with a view of the client's file system on Konqueror or Nautilus and you can easily drag-drop and copy-paste files.<br />
<br />
sftp://root@192.168.0.202<br />
<br />
===Data synchronization===<br />
[[Image:SHR-PISI.png|200px|thumb|PISI Contact Sync]]<br />
[[Image:SHR-PISI-dates.png|200px|thumb|PISI Calendar Sync]]<br />
<br />
You can synchronize your contacts and appointments data with various sources. The sync can by done by program called [http://pisi.projects.openmoko.org/ PISI] . SIM contacts and calendar entries are currently possible to sync on SHR.<br />
<br />
For calendar install dates<br />
<br />
opkg install dates<br />
<br />
Supported Contacts data sources:<br />
* SIM via DBUS (e.g. SHR)<br />
* QTopia address book (e.g. OM 2008.12)<br />
* LDAP (read only)<br />
* VCF files (local / webdav)<br />
* Google contacts<br />
<br />
Supported Calendar data sources:<br />
* Google calendars<br />
* ICalendar files (local / webdav)<br />
<br />
To install PISI, run <br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="left";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:80%; text-align:left " | <br />
<br />
opkg install http://www.opkg.org/packages/0_python-ldap_2.3.6_armv4t.ipk python-misc python-netclient python-netserver python-pycairo python-pygobject python-pygtk python-sqlite3 http://www.opkg.org/packages/1_python-vobject_0.8.1_armv4t.ipk http://www.opkg.org/packages/0_python-webdav_0.1.2_armv4t.ipk http://www.opkg.org/packages/1_python-gdata_1.3.0_armv4t.ipk http://www.opkg.org/packages/1_python-dateutil_1.4.1_armv4t.ipk http://www.opkg.org/packages/openldap_2.3.43_armv4t.ipk http://projects.openmoko.org/frs/download.php/841/pisi_0.3_armv4t.ipk<br />
<br />
| <br />
<br />
|}<br />
<br />
Configuration example, .pisi/conf to sync contacts and calendar with google calendar and contacts with google mail:<br />
<br />
[googleCalendar]<br />
description=My Google Calendar<br />
module=calendar_google<br />
user=user@gmail.com<br />
password=secret<br />
calendarid=user@gmail.com<br />
<br />
[pimlicodates]<br />
description= Pimlico Dates<br />
module=calendar_ics<br />
path=/home/root/.evolution/calendar/local/system/calendar.ics<br />
<br />
[googlecontacts]<br />
description=Google Contacts Account<br />
module=contacts_google<br />
user=user@gmail.com<br />
password=secret<br />
<br />
[remoteIcs]<br />
description= Remote ICS on Webdav<br />
module=calendar_remoteics<br />
url=http://webdav.davserver.net/private/pim/<br />
file=remotecalendar.ics<br />
username=<LOGIN><br />
password=<PASSWORD><br />
<br />
[shrsim]<br />
description=SHR SIM Card Contacts<br />
module=contacts_dbussim<br />
max_simentries = 250<br />
simentry_name_maxlength=18<br />
<br />
Another way of importing contacts via Vcard file is possible with [gopher://gopher.fnordpol.de/9/data/DbusAccessScripts_0.0.0.tar.gz this] script written by [[User:Zem#DBus_Access_Scripts|Zem]].<br />
<br />
===Reporting bugs===<br />
<br />
SHR is a work in progress. Shell you experience issues, please report them back to SHR. With your report provide logs from<br />
<br />
/var/log/ophonekitd<br />
/var/log/frameworkd<br />
<br />
To report a bug, please go to http://shr-project.org/trac/report<br />
<br />
Check if the bug is already reported. If no, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on.<br />
<br />
==Car Navigation==<br />
===Add opkg feed===<br />
To install <tt>navit</tt> as a car navigation system on your freerunner you have to add the feed for the installer <tt>opkg</tt><br />
http://download.navit-project.org/navit/openmoko/svn/<br />
You can do this by: <br />
echo src navit http://download.navit-project.org/navit/openmoko/svn > /etc/opkg/navit-feed.conf<br />
opkg update<br />
<br />
===Install Navit===<br />
Install [[Navit]]:<br />
opkg install navit<br />
Navit will be auto-updated when you run <tt>opkg upgrade</tt> later.<br />
<br />
===Workaround libgps===<br />
Navit on SHR has in the currently available version (08/2009) a <tt>libgps</tt> problem. You solve this by: <br />
opkg install libgps17<br />
ln -s /usr/lib/libgps.so.17 /usr/lib/libgps.so.16<br />
<br />
===Install Maps===<br />
Use [http://maps.navit-project.org/download/ Navit pre-processed OSM maps]. With your browser on desktop:<br />
* Navigate to the region you want, <br />
* mark a rectangle for your map (e.g. for Germany) and click select the rectanglular map. <br />
* then click on download and save the file to <tt>country.bin</tt> (e.g. <tt>germany.bin</tt>) on your desktop computer.<br />
* copy the file to on your freerunner. Because of the size of the maps you copy map to the Micro-SD card on your freerunner. Create a directory for the maps and copy the files from desktop to freerunner:<br />
mkdir /media/card/maps<br />
scp germany.bin root@192.168.0.202:/media/card/maps<br />
* Create a directory <tt>.navit</tt> and copy the <tt>navit.xml</tt> to this directory:<br />
mkdir /home/root/.navit <br />
cp /usr/share/navit/navit.xml /home/root/.navit/navit.xml<br />
* Add and enable the map for the application in navit by changing the lines (at approx line number 370)<br />
<!-- Mapset template for openstreetmaps --><br />
<mapset enabled="yes"><br />
<map type="binfile" enabled="yes" data="/media/card/maps/*.bin"/><br />
</mapset><br />
Disable unused mapset sections by setting enabled to <tt>no</tt>, e.g. the pre-installed sample maps at line 370 in <tt>navit.xml</tt>.<br />
<mapset enabled="no"><br />
<xi:include href="$NAVIT_SHAREDIR/maps/*.xml"/><br />
</mapset><br />
<br />
===Start Navit===<br />
Start <tt>Navit</tt> on your Freerunner for your first test. For further configuration details see [[Navit]].<br />
<br />
===No sound after installing Navit===<br />
<br />
Navit tends to depend on speech-dispatcher and after a suspend, the freerunner does not ring anymore for incoming calls or messages, it only vibrates. To correct this remove speech-dispatcher:<br />
<br />
opkg remove -force-depends speech-dispatcher<br />
<br />
==SHR Settings==<br />
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]<br />
<br />
SHR Settings is the main setting application of SHR. In the background it uses [[FSO]] specific dbus calls as well as low level commands. The graphical interface is Elementary-Python based. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).<br />
<br />
While some settings are persistent over reboots, other are not.<br />
<br />
'''Main Screen'''<br />
Main screen is divided into few categories, which contain modules. Every SHR Settings module has specified task - control GSM antenna power, set actual time etc. <br />
<br />
'''Phone'''<br />
<br />
'''GSM'''<br />
<br />
<br />
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.<br />
<br />
To list available providers, click on Operators button. Scanning can take some time. After while, list of operators should pop up.<br />
<br />
You can't connect to operators marked [forbidden]. After failed connect, message is displayed.<br />
<br />
Selecting operator from list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.<br />
<br />
'''Call'''<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]<br />
<br />
|}<br />
<br />
You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")<br />
<br />
'''SIM'''<br />
<br />
Here you can view some informations about your SIM card and clean phone and messagebooks.<br />
<br />
'''Others'''<br />
<br />
'''Profile'''<br />
<br />
Here you can select current profile, which device should use to determine ring tone etc.<br />
<br />
'''Current profile'''<br />
<br />
Here you can adjust properties of currently used profile. Available settings: ring tone, ring volume, ring vibration, ring loop, ring length, message tone, message volume, message vibration, message loop, message length.<br />
<br />
To change ring tone, click on "Change" button.<br />
<br />
To use your own ring tone, place it in /usr/share/sounds directory.<br />
<br />
After selecting sid tune as ring tone, there are available controls to select tune number from file.<br />
<br />
<br />
This is changing settings in /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
ring-volume # Ring Volume control 0 (mini) to ? maxi)<br />
ring-length # min time for ringtone. Must be greater than the duration of you ringtone<br />
ring-loop # define the number of loop of ringtone to play<br />
ring-tone: "ringtone_ringnroll.ogg" # .ogg example<br />
ring-tone: "Arkanoid_PSID.sid" # .sid example, use default tune<br />
ring-tone: "Arkanoid_PSID.sid;tune=2" # .sid example, plays the second tune of that<br />
<br />
If you like to test a .sid you can play it using this command on the FR:<br />
<br />
gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink<br />
<br />
Note that it's a ! used and not a | to construct the gstreamer pipe command.<br />
<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]<br />
<br />
|}<br />
<br />
<br />
<br />
'''Connectivity'''<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]<br />
|}<br />
<br />
<br />
'''WiFi'''<br />
<br />
With "WiFi radio" toggle you can set, if wifi module should be powered. WiFi radio has to be turned on before trying to connect to WiFi network, unless you try to connect through Mokonnect which is capable of powering it up.<br />
<br />
'''GPRS'''<br />
<br />
To enter APN, login and password fields, just click on actual value (default: "internet"). Keyboard will pop up.<br />
If you don't know APN, login and passwork, ask your provider.}}<br />
<br />
{{Note|You can also use Mokonnect to manage your Gprs connection}}<br />
<br />
To connect to GPRS network, just click "Connect" button. Entered values will be saved after successful connection.<br />
<br />
'''USB'''<br />
<br />
With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.<br />
<br />
'''Bluetooth'''<br />
<br />
To power up Bluetooth module, swith "Bluetooth radio" toggle to "On". After that, "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.<br />
<br />
'''GPS'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]<br />
|}<br />
<br />
<br />
<br />
'''GPS'''<br />
<br />
By default, GPS is turned on only when requested (when you turn on TangoGPS, Navit, omgps or other GPS app). That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.<br />
<br />
'''GPS information'''<br />
<br />
This page can be used to monitor GPS status. If some value isn't known, then "unknown" is displayed.<br />
<br />
You can also view information about every visible satellite and check, which are used for getting fix. To do that, just click "Satellite details".<br />
<br />
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.<br />
<br />
'''Date/time'''<br />
<br />
[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]<br />
<br />
'''Time'''<br />
<br />
Here you can view and set actual time. By default, time is just displayed, To adjust it, click on "Set time".<br />
<br />
After finishing adjusting, click "OK" button.<br />
<br />
'''Date'''<br />
<br />
This module displays current date.<br />
<br />
'''Power'''<br />
<br />
'''Battery'''<br />
<br />
This module displays informations about battery state - charge, voltage, remaining time etc. To update data, click "Update" button.<br />
<br />
Here you also force enable 500mA charging.<br />
<br />
'''Display'''<br />
<br />
With this slider you can easily tweak backlight power.<br />
<br />
{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 100%.}}<br />
<br />
'''Power'''<br />
<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Power.png |200px|thumb|Power]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]<br />
|}<br />
<br />
Here you can turn on or off automatic dimming or suspend after idle timeout (see: Timeouts module)<br />
<br />
'''Timeouts'''<br />
<br />
Here you can set up values of idle timeouts used by device. Timeouts are reached in this order: idle -> idle dim -> idle prelock -> lock -> suspend. Idle, idle prelock and lock aren't used by default in SHR at the moment. This setting changes parameters in /etc/frameworkd.conf :<br />
<br />
[odeviced.idlenotifier]<br />
suspend = 20<br />
lock = 2<br />
idle_prelock = 12<br />
idle = 10<br />
idle_dim = 20<br />
<br />
'''Services'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]<br />
|}<br />
<br />
Here is listed every interesting script from /etc/init.d/ directory.<br />
<br />
After clicking on some, you can either start, restart or stop service and view result.<br />
<br />
'''Others'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Others.png |200px|thumb|Others]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Splash-Preview.png |200px|thumb|Splash preview]]<br />
|}<br />
<br />
'''Splash'''<br />
<br />
With this selector you can select theme used by shr-splash at boot and shutdown. After clicking "Preview", selected boot image will be displayed for 5 seconds.<br />
<br />
'''PIM'''<br />
<br />
Module used by opimd developers. Doesn't have influence on behaviour of default SHR image.<br />
<br />
Every opimd domain has different backends to store it's data. The domain reads data from every backend and writes data to the default backend. So with the selector in shr-settings you can choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.<br />
<br />
'''Userspace backups'''<br />
<br />
Here you can either archive or restore your files and configurations.<br />
<br />
'''Image information'''<br />
<br />
This module contains basic information about installed image - name of buildhost, used revision, branch and time of build.<br />
<br />
==Theming==<br />
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]<br />
Find available themes by running <br />
<br />
opkg list | grep theme-illume<br />
<br />
install it by<br />
<br />
opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen<br />
<br />
http://opkg.org has a very fast theme called nEo<br />
<br />
opkg install http://www.opkg.org/packages/e-wm-theme-neo_0.2_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/elementary-theme-neo_0.2_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/etk-theme-neo_0.2_armv4t.ipk<br />
opkg install -force-overwrite http://www.opkg.org/packages/libframeworkd-phonegui-efl-theme-neo_0.2_armv4t.ipk<br />
<br />
If you also want the GTK+ Applications to fit in with the rest of the Systems look execute<br />
<br />
opkg install http://www.opkg.org/packages/gtk-theme-neo_0.1_armv4t.ipk<br />
<br />
For a completely monolithic look additionally execute<br />
<br />
opkg install http://www.opkg.org/packages/gpe-theme-neo_0.1_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/icon-theme-neo_0.2_armv4t.ipk<br />
<br />
Please observe the command line output when installing these themes, since it will tell you how to activate the themes.<br />
<br />
{{Note|some of the theme packages have to be reinstalled after an opkg upgrade.}}<br />
<br />
Reverting back can be done by <br />
<br />
opkg install e-wm-theme-illume-sixteen shr-theme-gtk-e17lookalike -force-reinstall<br />
opkg install libframeworkd-phonegui-efl0 e-wm-theme-default etk-theme-shr shr-theme -force-reinstall<br />
<br />
==FSO Resources==<br />
<br />
FSO is in control of each device. These are called resources. If the software wanting to use the device is capable of requesting this resource via d-bus, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through SHR Setting or you can use fsoraw command. (Using fsoraw is faster and better then running dbus commands)<br />
<br />
opkg install fsoraw<br />
<br />
Example of usage fsoraw:<br />
<br />
fsoraw -r Display mokomaze<br />
<br />
'''Wifi'''<br />
<br />
Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the network manager to set up networks, Mokonnect will power Wifi up automatically when needed.<br />
<br />
'''Bluetooth'''<br />
<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
'''GPS'''<br />
<br />
The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off<br />
<br />
'''GSM'''<br />
<br />
You need to have this resource requested to have GSM module powered.<br />
<br />
'''Display'''<br />
<br />
While this resource is requested the display won't be blanked and suspend is disabled.<br />
<br />
'''CPU'''<br />
<br />
Default rules.yaml checks for this resource to disable automatic suspend when it's requested. While this resource is kept suspend is disabled (but screen can be blanked).<br />
<br />
'''Test'''<br />
<br />
A test resource<br />
<br />
==Network manager==<br />
<br />
While there are several ways of networking - Wifi, USB, Bluetooth and Gprs - By default, USB networking is enabled in /etc/network/interfaces.<br />
<br />
Enhanced configuration is possible through direct editing of /etc/network/interfaces or through Mokonnect.<br />
<br />
Connmand daemon with Mokonnect are the recommended user level applications for setting up networking. At the moment, Mokonnect can manage USB, Wifi and Gprs connections, as well as routing and NAT. Wifi device is not required to be manually turned on via SHR-Settings as Mokonnect will automatically enable the device when needed and disable after use.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-Mokonnect.png|200px|thumb|Mokonnect]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokonnect-Wifi.png|200px|thumb|Mokonnect Wifi]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokonnect-Wifi-Scan.png|200px|thumb|Mokonnect Wifi Scan]]<br />
<br />
<br />
|}<br />
<br />
==Bluetooth==<br />
<br />
Bluetooth can be used for several different applications - file transfer, networking, HIDD, music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth applications is better then for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if it is not around, making it quite difficult to use.<br />
<br />
Don't forget you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On, where you can also make the bluetooth device visible.<br />
<br />
SHR user bluez4 which completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. While hidd and dund are still provided, pand is not. Please see http://wiki.openmoko.org/wiki/Manually_using_Bluetooth for detailed information about using bluetooth and also for list of supported devices.<br />
<br />
'''OBEX file transfer'''<br />
<br />
There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:<br />
<br />
opkg install obexpush<br />
<br />
Default receiving path (editable in /etc/default/opd_args ) doesn exist, so create it<br />
<br />
mkdir /var/obexpush<br />
<br />
Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush<br />
<br />
To send some files, first scan for devices:<br />
<br />
hcitool scan<br />
Scanning ...<br />
00:16:41:F5:A5:BC laptop<br />
<br />
Then send it onto bt address found in the scan:<br />
<br />
obextool push image.jpg 00:16:41:F5:A5:BC 10<br />
<br />
'''Connect Bluetooth keyboard'''<br />
<br />
hidd --search<br />
<br />
'''Pairing'''<br />
<br />
This comes from http://wiki.openmoko.org/wiki/Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner<br />
<br />
Now, you must pair the bluetooth headset with your Freerunner. Make sure the bluetooth chip is powered up (can be done through the Connectivity section in the SHR-Unstable settings manager) and that bluetoothd is running:<br />
/etc/init.d/bluetooth start<br />
Now, to actually pair the bluetooth headset, you will need the simple-agent script. If you already have it, excellent. If you, like me, do not, then you can get it here: http://dl.getdropbox.com/u/453116/simple-agent<br />
<br />
Put it in /usr/bin/ and run '''chmod a+x /usr/bin/simple-agent'''<br />
<br />
Now put your headset into pairing mode and run <br />
<br />
hcitool scan<br />
<br />
Find your headset and use its address in the command <br />
<br />
simple-agent hci0 XX:XX:XX:XX:XX:XX<br />
<br />
If you give a third parameter (what it is doesn't matter) to simple-agent, it will disconnect then reconnect to the headset (reset pairing).<br />
<br />
'''GSM phonealls with bluetooth headset<br />
'''<br />
'''Configuring bluez'''<br />
<br />
Older SHR releases need to uncomment '''SCORouting=PCM''' setting in '''[General]''' section of<br />
<br />
/etc/bluetooth/audio.conf<br />
<br />
like this:<br />
<br />
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA) <br />
# Defaults to HCI <br />
SCORouting=PCM <br />
<br />
do not forget to restart bluetoothd after that.<br />
<br />
/etc/init.d/bluetooth stop<br />
/etc/init.d/bluetooth start<br />
<br />
'''Configuring FSO'''<br />
<br />
Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in<br />
<br />
/etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).<br />
<br />
You need to restart FSO for the changes to take effect.<br />
<br />
/etc/init.d/frameworkd restart<br />
<br />
example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:<br />
<br />
message-length: 7<br />
message-tone: notify_message.wav<br />
message-vibration: 1<br />
message-volume: 10<br />
ring-loop: 1<br />
ring-tone: ringtone_ringnroll.wav<br />
ring-vibration: 1<br />
ring-volume: 10<br />
bt-headset-enabled: 1<br />
bt-headset-address: 00:09:DD:31:92:98<br />
<br />
'''Connecting and reconnecting the bt device'''<br />
<br />
You might need to get the bluetooth headset connected manually on the beginning and also after suspend:<br />
<br />
mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect<br />
<br />
where xx_xx_xx_xx_xx_xx is address of the device, for example:<br />
<br />
mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect<br />
<br />
Hopefully, your bluetooth headset now works. Good luck!<br />
<br />
==System Customizing==<br />
<br />
'''Changing the splash screen'''<br />
<br />
list available splash screen themes<br />
<br />
opkg list | grep splash-theme<br />
<br />
and install one of the available themes<br />
<br />
opkg install shr-splash-theme-dontpanic<br />
<br />
Then go to SHR Settings -> Others -> Themes. Here you can preview installed themes and change the default one.<br />
<br />
'''Install functional alarm application'''<br />
<br />
opkg remove -force-depends elementary-alarm; opkg install ffalarms<br />
<br />
'''Enable mouse cursor''' <br />
<br />
edit line 121 of /etc/X11/Xinit and erase -hide-cursor<br />
<br />
ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} -mouse tslib -root-ppm /usr/share/pixmaps/xsplash-vga.ppm vt1"<br />
<br />
'''Improve speed of Elementary applications'''<br />
<br />
Set the Elementary rendering engine used for Evas to x11-16 (Software X11 16bpp engine, may have bugs and will be lower quality, but faster):<br />
echo -e "#!/bin/sh\n\nexport ELM_ENGINE=x11-16" > /etc/profile.d/set-elm-engine.sh<br />
<br />
<br />
Additionally in the SHR-Unstable repositories there are theme packages optimized for 16bpp color. Both packages can be installed with the following command:<br />
<br />
opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen<br />
<br />
You can then append the /etc/profile.d/set-elm-engine.sh with:<br />
<br />
# Set Optimized theme<br />
export ELM_THEME=sixteen<br />
<br />
You can also then change Illume to use the sixteen theme by clicking the wrench->Look->Theme-illume-sixteen->OK. Then switch Illume to use the 16bpp Engine by clicking the wrench->Advanced(you will need to drag and slide the top menu)->Engine->Software_16->OK. This should give you a much faster interface without the low quality look the default SHR themes have at this lower color depth.<br />
<br />
Read http://trac.enlightenment.org/e/wiki/Elementary<br />
<br />
If you try to change Wallpaper or Theme and Illume keeps on crashing, it might be caused by the whole Illume running in Software_16 mode. Go to Illume Settings, slide the icon bar and select Advanced. There tap on Engine and select Software. After this, you can change your Wallpaper or Theme. Selecting Software_16 later on again will speed up the desktop's response (though causing it to be a bit uglier).<br />
<br />
'''Speedup of suspend and wake up'''<br />
<br />
I you are using Qi and installation on µSD card, you can change the kernel parameter loglevel=1 1 in /boot/append-GTA02 . For u-boot and installation in nand just type<br />
<br />
klogd -c 1<br />
<br />
into the console. This saves you from 3 seconds worth of console output on every resume.<br />
<br />
If you like the effect of this command and want it to be executed at every startup, you just have to log into your phone and type the following:<br />
<br />
cat > /etc/init.d/resumespeedup << EOF<br />
#!/bin/sh<br />
/sbin/klogd -c 1<br />
EOF<br />
chmod +x /etc/init.d/resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc1.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc2.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc3.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc4.d/S06resumespeedup<br />
ln -s ../init.d/resumespeedup /etc/rc5.d/S06resumespeedup<br />
<br />
'''Opimd utils'''<br />
<br />
Opimd utils is a set of several testing scripts to play with the new opimd backends. It also provides opimd-messages program and mainly new opimd-notifier that is much better then the standard one.<br />
<br />
opkg install opimd-utils<br />
<br />
'''opkg upgrade issues'''<br />
<br />
As '''opkg''' had some '''issues''' recently, installation might get broken due to that. You can fix it or prevent by using the following scripts<br />
<br />
Safe update packages:<br />
<br />
#!/bin/sh<br />
<br />
opkg list_upgradable | awk '!/(kernel|Multiple)/ {print $1}' | \<br />
while read line; do<br />
echo "installing pack $line"<br />
opkg install $line -force-reinstall<br />
done<br />
<br />
<br />
Force reinstall all installed packages<br />
<br />
#!/bin/sh<br />
<br />
opkg list_installed | awk '!/(kernel|Multiple)/ {print $1}' | \<br />
while read line; do<br />
echo "installing pack $line"<br />
opkg install $line -force-reinstall<br />
done<br />
<br />
<br />
'''Random errors''', No icons, no GSM functions etc. - this is mostly due to '''errors on your uSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.<br />
<br />
For reboot into nand and fix 1st partition of ext2 on your card<br />
<br />
fsck.ext2 /dev/mmcblk0p1<br />
<br />
'''Replace dropbear with openssh'''<br />
<br />
Set password<br />
passwd<br />
<br />
Install ssh server (and sftp)<br />
opkg install openssh-sshd openssh-sftp-server openssh-scp -force-depends<br />
<br />
Remove dropbear and start openssh<br />
<br />
screen<br />
opkg remove dropbear -force-depends; /etc/init.d/sshd start<br />
<br />
You will get disconnected from the ssh session, wait until keys get generated and log in again<br />
<br />
'''Video playback'''<br />
<br />
Install intone-video<br />
<br />
opkg install elementary libsqlite3-0 http://www.opkg.org/packages/intone-video_0.11_arm.ipk<br />
<br />
If intone complaints about missing libraries, please run <br />
#!/bin/sh<br />
cd /usr/lib<br />
ls *ver-svn-02*|while read nombre<br />
do<br />
final="`echo $nombre | sed s/-ver-svn-02/-ver-pre-svn-01/`"<br />
ln -s /usr/lib/$nombre /usr/lib/$final<br />
done<br />
<br />
On your desktop, encode your video:<br />
<br />
mencoder video-file -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf scale=320:240,eq2=1.2:0.5:-.025,rotate=2 -oac mp3lame -lameopts br=64:cbr -o video-file-FR.avi<br />
<br />
Adding''' freerunner to your hosts''' file for a name resolving:<br />
<br />
You can use the name <tt>neo</tt> if you added the host <tt>neo</tt> in <tt>/etc/hosts</tt> on your desktop computer (add the following line for host <tt>neo</tt> assuming that the IP-address of your freerunner is <tt>192.168.0.202</tt>.<br />
echo "192.168.0.202 neo neo" >> /etc/hosts<br />
<br />
You can then access your freerunner like this:<br />
<br />
ssh root@neo<br />
<br />
Which is shorter then this:<br />
<br />
ssh root@192.168.0.202<br />
<br />
==Installing Software==<br />
<br />
You can use opkg for installing software packages or you can try SHR Installer from http://git.shr-project.org/git/?p=shr-installer.git;a=summary . It requires packagekitd<br />
<br />
opkg install packagekitd<br />
<br />
If you wan to use opkg after you used the installer, make sure packagekitd is not running<br />
<br />
killall packagekitd <br />
<br />
'''Cool applications'''<br />
<br />
SHR comes with only few preinstalled applications but it's repository provides more cool stuff. Also, there are applications that are not in SHR repos at the moment but can still be installed.<br />
<br />
'''SHR Launcher'''<br />
<br />
[[Image:Launcher.png|200px|thumb|SHR Launcher]]<br />
Launcher is elementary based alternative home screen application and event notifier for SHR. It displays current time, has a user tweak-able launcher with categories and features missed calls and messages applets.<br />
<br />
opkg install libsqlite3-0 http://www.opkg.org/packages/launcher_0.23_arm.ipk<br />
<br />
For '''PIM''' applications you can get dates for calendar, tasks for todos, neote for notes:<br />
<br />
opkg install dates tasks<br />
<br />
opkg install http://neote.googlecode.com/files/neote_0.2.0-r0_all.ipk<br />
<br />
'''Litephone'''<br />
<br />
[[Image:SHR-Litephone.png|200px|left|thumb|Litephone]]<br />
<br />
Litephone is new alternative set of phone applications written in Qt. In it's single application interface it provides basic phone functionality (contacts, calls, messages, phone log, settings). It's main advantage is that it uses opimd for storage of the user data.<br />
<br />
opkg install http://pvtrace.com/litephone/libqtcore4_4.4.3-r3_armv4t.ipk<br />
opkg install http://pvtrace.com/litephone/libqtxml4_4.4.3-r3_armv4t.ipk<br />
opkg install http://pvtrace.com/litephone/libqtdbus4_4.4.3-r3_armv4t.ipk <br />
opkg install http://pvtrace.com/litephone/libqtgui4_4.4.3-r3_armv4t.ipk <br />
opkg install http://pvtrace.com/litephone/qt4-x11-free_4.4.3-r3_armv4t.ipk<br />
opkg install http://pvtrace.com/litephone/litephone_0.0.1-r2_armv4t.ipk <br />
<br />
'''Mokomaze''' is an excelent eye-candy game using accelerators embedded in your device.<br />
<br />
opkg install mokomaze<br />
<br />
If you tweak the exec procedure in /usr/share/applications/mokomaze.desktop into this:<br />
fsoraw -r Display mokomaze<br />
the screen will not blank while playing.<br />
<br />
'''CellHunter''' is a game to collect information about mobile phone cells. This information can later be used to roughly determine your position without powering on the GPS chip. [http://78.47.116.33/~hole/cellhunter/ CellHunter homepage]<br />
<br />
opkg install cellhunter<br />
<br />
'''OMGps''' and '''TangoGPS''' are GPS application showing you your position on a map (Openstreetmap, Google maps etc.). You can track your position, save it and use later, save and view points of interest, images or measure your trip. OMGps allows you to overlay different maps on top of each other, set GPS into different modes (walking, car, flying). Maps are downloaded online and used even in offline. <br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-TangoGPS-OSM.png|200px|thumb|TangoGPS]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-OMGPS-GM.png |200px|thumb|OMGps]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokomaze.png|200px|thumb|Mokomaze]]<br />
<br />
<br />
|}<br />
<br />
'''Navit''' is a car navigation system with routing engine. It can calculate a route and do on screen and voice road navigation. Maps need to be downloaded beforehand, please check [http://wiki.navit-project.org/index.php/Main_Page#Maps Navit website]. You can get Openstreetmaps through [http://maps.navit-project.org/download/ Navit map extractor], after you download the map it needs to be specified in the .navit/navit.xml file.<br />
<br />
'''Literki''' is full qwerty keyboard with configurable layout, always transparent, therefore applications don't need to redraw screens and popup is therefore very fast. The keys are big enough for everyday use with your fat fingers. To pop up the keyboard: slide your finger upwards from the bottom right corner. To hide the keyboard: slide your finger down on the keyboard. [http://www.opkg.org/package_232.html Opkg page]<br />
<br />
opkg install http://pvtrace.com/literki_0.0.2-r3_armv4t.ipk<br />
<br />
[[Category:SHR]]</div>Dareushttp://openmoko.org/wiki/Talk:ApplicationsTalk:Applications2009-08-05T15:00:42Z<p>Dareus: /* Popularity contest */</p>
<hr />
<div>"Gutenflash" is listed twice under OM2007, although the page does not seem to be editable by normal registered users. --Infoport<br />
<br />
:Thanks for pointing this out. I have changed it. --[[User:Marko Knöbl|Marko Knöbl]] 22:46, 26 August 2008 (UTC)<br />
<br />
== aircrack ==<br />
<br />
hi<br><br />
What about <s>porting aircrack to the openmoko architectures and perhaps</s> writing a GUI for it? (zenity could be a nice GUI tool, I don't really know because I've never used it) --[[User:Jn|Jn]] 17:15, 16 June 2009 (UTC)<br />
<br />
== Popularity contest ==<br />
<br />
How about a ranking system of sorts, so you can sort applications based on votes/downloads/etc.? This would make it easier to find the really useful applications and sort out the buggy betas. I guess there should be more metadata to sort on, like distro compatibility. --[[User:Kbjorgensen|KB Jørgensen]] 09:17, 5 August 2009 (UTC)<br />
<br />
I think that it could be a good idea, just sorting would be great...<br />
[[User:Dareus|Dareus]]</div>Dareushttp://openmoko.org/wiki/Community_Updates/2009-08-06Community Updates/2009-08-062009-07-24T17:11:54Z<p>Dareus: </p>
<hr />
<div>{{Improve}}<br />
{{Note|Use Disscuss page for discussion. If you are planning longer edition, please use <nowiki>{{Editing|your_username_here|date_here|editing_summary_here}}<br />
tag. Remember to remove it (or put between <nowiki> tags ) right after you save your work.</nowiki>}}<br />
<!--{{Editing|[[User:Leadman|LeadMan]]|17:35, 20 July 2009 (UTC)|Community Update Draft conforming to OM Wiki editing guidlines}}--><br />
<br />
<!--First difference: date format - it is more logic to use format 'YYYY-MM-DD'--><br />
Take a moment and look at Discussion page to get a clue on how to contribute to Community Updates while following OM wiki editing guidelines please.<br />
Please fill in everything you think the community should know. On 8th August this content will be _moved_ to http://wiki.openmoko.org/wiki/Community_Updates/2009-08-06, FEEL FREE TO DO IT on 8th, also post a note on the community mailing list!<br />
<br />
====='''Period 2009-07-24 to 2009-08-06'''=====<br />
<br />
==Distributions==<br />
* '''[distro name]''' - notes<br />
<br />
==Applications== <br />
===New Applications===<br />
{{ApplicationBox|<br />
Name=Exampleapp 0.0.1|<br />
Description=Exampleapp 0.0.1 is an application to do some stuff..|<br />
Screenshot=System_boot.png|<br />
Homepage=http://wiki.openmoko.org/|<br />
TestedOn=Om2009T5<!--Om 2009 Tester's signature here-->,Om2008.8<!--Om2008 Tester's signature here-->,SHR<!--SHR Tester's signature here-->|<br />
PackageName=[http:// www.some.srv/path_to/Exampleapp.ipk Exampleapp]<br />
}}<br />
<br />
===Application Updates===<br />
{{ApplicationBox|<br />
Name=Exampleapp 0.0.1|<br />
Description=Exampleapp 0.0.1 is an application to do some stuff...<br />
* new example feature 1<br />
* new example feature 2|<br />
Screenshot=System_boot.png|<br />
Homepage=http://wiki.openmoko.org/|<br />
TestedOn=Om2009T5,Om2008.8,SHR|<br />
PackageName=Exampleapp<br />
}}<br />
<br />
==Community==<br />
Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc..<br />
<br />
==Event News==<br />
<br />
* '''2009-07-08''' - [Example Event] Description of example event<br />
<br />
[[Category:Community Update]]</div>Dareushttp://openmoko.org/wiki/Talk:USB_NetworkingTalk:USB Networking2009-07-14T13:24:50Z<p>Dareus: </p>
<hr />
<div>= Driver options in kernel config =<br />
Hi, I didn't want to change it in case I was wrong, but I believe that the options to configure your<br />
desktop as a host are not in "USB Support" as the article says:<br />
"Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the usbnet driver homepage."<br />
Aren't the options in <pre>Device Drivers -> Network Device Support -> USB Network Adapters</pre><br />
Can someone confirm this? I don't want to send people in the wrong direction, but that is the way it is in my system. Thanks. [[User:Mmanjos|Mmanjos]] 15:36, 4 November 2007 (CET)<br />
<br />
= Thoughts on USB networking in the final product =<br />
<br />
There was some discussion on the #openmoko IRC channel on how to approach the USB networking automatic setup eventually in the final product.<br />
<br />
The Neo's IP will probably need to remain static, and chosen, as it is now, from some local address space. I would personally suggest to change to using an address higher in the 192.168.0.0 space, say, 192.168.19.73 (ehhehe) to reduce chance of conflicts. (Or use link-local space?)<br />
* I don't think the 192.168.0.0 space is very problematic if network is configured as 192.168.0.192/26 instead of 192.168.0.0/24, as explained in the Debian example I've just enhanced in the page. [[User:OlivierBerger|OlivierBerger]] 07:35, 25 July 2008 (UTC)<br />
<br />
Anyway, for the casual user, and even comfort-seeking geeks, OpenMoko will need to provide DHCP service. It will probably be also a good idea to run a DNS proxy, since that way the host doesn't need to care about changing DNS servers, and the caching is a good idea anyway for high latency GPRS. I'd suggest dnsmasq, which is simple and can handle both tasks. I assume the Neo will do IP masquerading for the USB host when it's acting as its default gateway.<br />
<br />
Now, the DHCP server should obviously serve up a local address to the USB host when connected (assuming here most hosts will use DHCP by default to configure the USB network device, which I think is a valid assumption, and if some don't, we can't help things automagically anyway).<br />
<br />
What's more complicated is when to give a default gateway and a DNS server address. You don't want to do it all the time, that would screw with simple use cases (detailed more below).<br />
<br />
== Suggested policies ==<br />
<br />
At this point I suggest, based on the aforementioned IRC discussion, the following policy:<br />
<br />
1) If the device is plugged into a host, and the device is not on-line with GPRS, do not go on-line, and only give a private address (no default route/dns) to host.<br />
<br />
2) If the phone is told to go on-line with GPRS (or, in the future, other mobile protocols) and it's presently hooked up to a USB host with only a local network connection, query the user if they want to use the Internet also from the computer. If yes, run the interface down, then up again, thus triggering the host to make a new DHCP query. Now serve up default gateway and dns information too.<br />
<br />
3) If the phone is told to go off-line while routing a network connection to a USB host, cycle the interface again and only serve up a local address. Possibly ask if the user really wants to disconnect considering the tether.<br />
<br />
4) If the phone is presently on-line with GPRS, and it's plugged into a host, initialize with only the local network connection, query the user (with a dialog or less obtrusively with a suitable panel button or panel GPRS menu changing appearance) whether they want to use the connection from the computer too. If yes, cycle interface, serve up default gateway and dns. Remove the query if usb disconnected.<br />
<br />
== Use cases ==<br />
<br />
The rationale for not serving up a default route too eagerly is that this device charges from USB, people will probably sync it via USB, and they don't want any hassle doing that. Use cases to demonstrate:<br />
<br />
1) John wants to sync addressbooks between his home desktop and the Neo. He uses USBnet for this, because where he lives, GPRS is crazy expensive, and besides, he doesn't want to have internet-visible servers on the desktop. He hooks the Neo up, and only wants local data transfer capabilities. What he doesn't want is to lose access to his broadband, so serving up default gateway and DNS would make him angry.<br />
<br />
2) Shirley has CommunitasticoMoko installed on her Neo, and thus is on-line via GPRS pretty much constantly. (Yes, Shirley lives in some more GPRS-friendly area.) Shirley wants to load up new music from her desktop to the phone, so she hooks the Neo up. Even though GPRS is on-line for CommunitasticoMoko, she doesn't want the desktop to suddenly lose her home broadband access. She gets asked (in the more or less obtrusive ways above) if she'd like to provide Internet access to the host. She doesn't care about the question, just transfers the files, unhooks, and is on the go. The query disappears, not bothering her anymore.<br />
<br />
3) Shirley's CommunitasticoMoko buddy Roxanne hooks the Neo up to her laptop. As she is also on-line via GPRS, she gets the query. She first thinks to only sync up the address books of her laptop and the Neo, but while doing that, she decides to go surfing for a bit too. Up till now, she's had a local network between the devices, but as she acknowledges to the Neo that yes, she wants on-line, the laptop will get a default gateway and a DNS server, and surfing she goes.<br />
<br />
4) Matt just wants to charge his Neo up. He couldn't care less about any networking, let alone the Neo interfering with his existing network connections. He hooks the Neo up, and the local network is initialized. That's of little consequence to Matt, but he gets the phone charged.<br />
<br />
5) Tom is charging his Neo via his laptop at home, when his home broadband is cut off by a road crew. He has reasonable GPRS pricing, so he wants it up as a backup. He tells the Neo to go on-line, whereupon he is asked, since the Neo is already plugged in, if he wants to share the connection to his laptop. And yes he does. The Neo cycles the interface, and the laptop gets an Internet connection.<br />
<br />
== Open questions == <br />
<br />
How to deal with Bluetooth and WiFi routing (for GTA02) in conjuction? Probably you'd not want to serve up default gateway per default if you're BT tethered, however, user might want to have one device BT tethered and another USB tethered. So perhaps best to leave the option open to share the connection via USB even if BT tethering is active, though especially in this case the option shouldn't be obtrusive; it'd probably be a rare use case.<br />
<br />
=== Additional use cases ===<br />
<br />
There is another use cases I'd like to suggest for consideration:<br />
<br />
* Bertrand (who has a good broadband connection at home) lives in Expensive GPRS Country and has no Bluetooth / WLAN. He wants to plug his phone into his computer and run ipkg updates via his broadband connection. His PC is serving as a DHCP server and/or bridges all traffic through its interfaces (with STP preventing loops).<br />
<br />
Suggested policy:<br />
* Before the phone assigns itself a local address, it asks for a DHCP address. If that fails, a link local address according to RFC 3927 is assigned.<br />
<br />
= Operation on Gentoo =<br />
<br />
One way of doing routing and NAT was recently added to the Wiki. I followed the lead of the other examples and did it this way:<br />
<br />
# Neo1973<br />
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )<br />
postup() {<br />
case "${IFVAR}" in <br />
"usb0") <br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
echo 1 > /proc/sys/net/ipv4/ip_forward<br />
iptables -P FORWARD ACCEPT<br />
return 0;;<br />
esac<br />
return 0<br />
}<br />
predown() {<br />
case "${IFVAR}" in <br />
"usb0") <br />
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
echo 0 > /proc/sys/net/ipv4/ip_forward<br />
return 0;;<br />
esac<br />
return 0<br />
}<br />
<br />
If the intent is to have the NATing and routing turn on and off as the neo is plugged and unplugged, this is probably an approach that is more like that than the other way.<br />
<br />
== Dealing with NetworkManager ==<br />
<br />
NetworkManager (the default for [http://www.sabayonlinux.org/ sabayon]) bypasses /etc/conf.d/net.usb0 by default. You need to modify /etc/conf.d/rc (or /etc/rc.conf on OpenRC) from<br />
RC_PLUG_SERVICES="!net.*"<br />
to somehing like<br />
RC_PLUG_SERVICES="!net.eth* !net.wlan*"<br />
<br />
(see http://gentoo-wiki.com/HOWTO_NetworkManager)<br />
<br />
= Rewrite =<br />
<br />
I have rewritten this page for accuracy and clarity. I took out redundant stuff, and tried to make it much clearer based upon my networking experience and discussions with users having problems in the #openmoko IRC channel. I tried to avoid and remove first person comments (although made some myself). <br />
<br />
The first section is very deliberate, since the ordering of this page was illogical, having gathered many random comments. This allows user to step through the parts and make sure each is right before moving on. There are further explanations that could be added - instead of a subnet, an explicit device route could be added for the .202 host, over USB. which avoids most routing problems (unless your desktop is also .202). I hope though even without that, this covers most scenarios. I intend to rewrite some of the other pages in the same way.<br />
<br />
= Changing flow =<br />
<br />
Miohtama, I'm not entirely happy about your unjustified reordering. The page was structured in order to carefully explain to new users how to make it work, and for it be a very precise guide for helping those on IRC having problems - users I deal with. I don't believe that your changes really facilitate that. Putting stuff together because it seems to might superficially seem like a good idea, but it's not always.<br />
<br />
== Overlapping subnets ==<br />
<br />
<br />
Please don't keep adding assertions that overlapping subnets don't work, or that assumptions are being made that they are different. It does work, with a sufficiently small subnet for the FR (as the examples show). Adding comments about insisting that users change their LAN subnets is unnecessary, and makes it that much harder for users - where this page was originally.<br />
<br />
<br />
== Latest changes ==<br />
I found out that with my Kubuntu 8.10 without the «auto usb0» option in /etc/network/interfaces the USB networking wasn't able to work automatically.<br />
Adding that line makes everything work fine: plug-in the NEO, it gets recognized, give ssh openmoko and you're done. No problems with default networkmanager.<br />
So my question is: why do you think that option should not be there?<br />
<br />
<br />
== displaying desktop application on freeruner ==<br />
If you consider, that you want to see your desktop application on Freerunner you have to install openssh-ssh server instead dropbear and then you can <br />
<pre><br />
ssh -X login@192.168.0.200<br />
xclock<br />
</pre><br />
<br />
==Script==<br />
sudo iptables -F <br><br />
sudo ifconfig usb0 192.168.0.200 netmask 255.255.255.0<br><br />
sudo route add 192.168.0.202 usb0<br><br />
sudo iptables -I INPUT 1 -s 192.168.0.202 -j ACCEPT<br><br />
sudo iptables -I OUTPUT 1 -s 192.168.0.200 -j ACCEPT<br><br />
sudo iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br><br />
sudo echo 1 > /proc/sys/net/ipv4/ip_forward<br><br />
<br />
== no inet in interfaces ==<br />
I think the inet label in interfaces for eth1 (when openmoko is on eth1 like Ubuntu 9.04) causes the host (laptop) to try to make a connection to the internet via the openmoko device. This could be just the opposite of what you want. I'm not an expert on this but removing inet in interfaces for the openmoko devices fixed my problem. Any comments on this? [[User:Pander|Pander]] 08:49, 16 June 2009 (UTC)<br />
<br />
I merely checked on /etc/udev/rules.d which interface would be used ( eth1 ) Then went to System/Administration/Network and there gave the address netmask and the default gateway for eth1 -- simple and no problem. The default GW is the gateway of the system. On laptop like you did. All works well Internet for laptop and contact with Freerunner.<br />
<br />
Did not check yet if i can go to the internet from the Freerunner via eth1, wlan is OK <br />
<br />
Carig Philippines --[[User:Frank|frank]] 14:50, 17 June 2009 (UTC)<br />
<br />
= Ubuntu Instructions =<br />
<br />
I find the 8.10 instructions clearer and more to the point than the 9.04 ones. Moreover, the 9.04 ones don't feature actual routing, so I'd suggest deleting the 9.04 section, and adding a note to the 8.10 sections that with Qi, it's eth1 and not usb0. Also, one question: does anyone know if the routing given by the iptables commands in the 8.10 section can also be achieved just by using the System > Administration > Network > eth1 > IPv4 Settings > Routes dialog? --[[User:Ockham|Ockham]] 18:55, 5 July 2009 (UTC)<br />
<br />
==Using network-manager on systems using udev==<br />
following these steps i found that iptables is not set correctly (cannot reach the web from FR) i tried manually executing <br />
sudo /usr/local/sbin/freerunner-usb-add.sh<br />
and everything i got was<br />
Cannot find device "00:00:22:55:bb:00"<br />
what's wrong?<br />
<br />
--[[User:Dareus|Dareus]] 15:24, 14 July 2009 (CET)</div>Dareushttp://openmoko.org/wiki/Talk:JokesTalk:Jokes2009-07-11T08:39:27Z<p>Dareus: </p>
<hr />
<div>proposed for deletion?<br />
<br />
are YOU joking?<br />
<br />
[[User:Dareus]]<br />
<br />
<br />
removed proposed for deletion tag --[[User:Rakshat|Rakshat]] 06:11, 11 July 2009 (UTC)</div>Dareushttp://openmoko.org/wiki/Talk:JokesTalk:Jokes2009-07-10T17:48:31Z<p>Dareus: New page: proposed for deletion? are YOU joking? Dareus</p>
<hr />
<div>proposed for deletion?<br />
<br />
are YOU joking?<br />
<br />
Dareus</div>Dareushttp://openmoko.org/wiki/Hardware:Neo_1973:Alternate_CasesHardware:Neo 1973:Alternate Cases2009-04-06T16:20:37Z<p>Dareus: </p>
<hr />
<div>{{Languages|:Category:Neo1973 alternate cases}}<br />
<br />
This page is a repository for alternate case designs for the [[Neo 1973]], intended to be designed, built and fitted by the community/the phone's owner. Many specific suggestions can be found in [[Wish List - Hardware#Casing]] and corresponding links.<br />
<br />
Each alternate case design suggestion needs some or all of: a description, intended uses, design options, a 3D model in an open format (e.g. [http://en.wikipedia.org/wiki/STL_(file_format) .stl], .blend (Blender), .obj (Wavefront), [http://en.wikipedia.org/wiki/Art_of_Illusion .aoi (Art of Illusion)] ), rendered images of the intended design, materials, components and information regarding interfacing electronically to components within the phone.<br />
<br />
== Case schematics ==<br />
<br />
The [[CAD models]] of the [[Neo 1973]] and [[Neo FreeRunner]] have been published under a Creative Commons License: see [[Neo1973 case schematics]].<br />
<br />
== Manufacture ==<br />
<br />
There are numerous rapid prototyping companies that will very cheaply make small run components from various polymers, including:<br />
<br />
[http://ponoko.com Ponoko] - requires EPS files (makes 2D flat cut-outs)<br />
<br />
[http://rapidobject.com Rapid Object] - requires STL or VRML (for extra detailed models) files<br />
<br />
[http://www.rapidprototyping.co.nz Rapid Prototyping New Zealand] - 3D powder based printer, not particularly well suited to this application.<br />
<br />
[http://www.redeyerpm.com/Default.aspx Red Eye RPM] - requires STL files<br />
<br />
Other materials may require traditional manufacturing techniques including milling, forging, injection-moulding, either by the user or short-run companies such as:<br />
<br />
[http://emachineshop.com/ eMachine Shop] - Requires companies own MS Windows based drawing software<br />
<br />
[http://www.msersen.net/msgme.php?p={$pagef}&c={$setcount}/ (4 axis) gantry style cnc router for hire. Click for inquiries]<br />
<br />
[http://techshop.ws Techshop]<br />
<br />
[http://www.shapeways.com/ Shapeways]<br />
<br />
==Cost Example==<br />
Rapid Object charge from 1.9 Euros per cm^3 of material (photosensitive polymer) used, plus postage. The case for the Neo looks to be about 1.5mm thick, so conservatively, the back of the case will be approximately:<br><br />
120 x 60 x 1.5<br><br />
+ 120 x 9 x 1.5 x 2 (2 sides)<br><br />
= 10,800<br><br />
+ 3,240<br />
<br />
= 14,040 mm^3<br />
<br />
~ 14 cm^3<br />
<br />
~ 26 Euros<br />
<br />
and the front will be (allowing for the screen hole):<br><br />
(120 x 60 - 43 x 58) x 1.5<br><br />
+ 120 x 9 x 1.5 x 2 (2 sides)<br><br />
= 7,059<br><br />
+ 3,240<br />
<br />
= 10,299 mm^3<br />
<br />
~ 10cm^3<br />
<br />
~ 19 Euros<br />
<br />
==Notes==<br />
Some users may want combinations of the variants listed - popular/simple options such as Stylus Mount/Different speaker orientation/Extra battery/Extra storage may be combined into one model. This should be taken into account when creating 3D models; i.e. it will simplify things later if the addition of (say) a solar panel, does not encroach on the area used for a touch strip, etc.<br />
<br />
== Design Variant Suggestions ==<br />
Some of these are a copy of requests in [[Wish List - Hardware#Casing]], some are from ideas thrown up in the community mailing list.<br />
<br />
Many of these cannot be implemented without some design changes to the phone PCB. As mentioned in [[Expansion Back]]<br />
<br />
=== Alternate Case Suggestion Format ===<br />
* 1 Rendered images<br />
** Images & any videos<br />
** [[Image:Neo1973.png]]<br />
* 2 3D model<br />
** Open format, as suggested previously.<br />
** See [[Neo1973 case schematics]] for standard Neo1973 case design<br />
* 3 Etching templates<br />
* 4 Materials<br />
* 5 Processes<br />
* 6 Interest<br />
** who's interested in this design<br />
<br />
[[Category:Neo1973 alternate cases| ]]</div>Dareushttp://openmoko.org/wiki/PythmPythm2009-03-31T10:04:47Z<p>Dareus: /* Ideas, Feature Requests */</p>
<hr />
<div>{{ApplicationBox|<br />
Name=Pythm|<br />
Description=Pythm is a media player frontend, designed to control mplayer or mpd with one GUI on the FreeRunner. As of writing, you need to download [https://docs.openmoko.org/trac/ticket/2011 python-mokoui] separately.|<br />
Screenshot=Pythm.png|<br />
Homepage=http://projects.openmoko.org/projects/pythm/|<br />
TestedOn=-|<br />
PackageName=-<br />
}}<br />
<br />
==Introduction==<br />
Pythm is a gui that can be used to play music. At the moment there are two "backends" supported:<br />
* Using the mplayer program on the device. <br />
* Using the music player daemon (mpd) on any host in the network via wifi or GPRS.<br />
Other Backends can be written and integrated into the application, if needed or wanted.<br />
<br />
==Configuring Pythm==<br />
Pythm can be configured using a simple config-file (ini-like syntax). This file can be found here:<br />
/etc/pythm.conf<br />
You can edit the file in place or copy it to<br />
~/.pythm/pythm.conf<br />
The file is splitted in three sections:<br />
<br />
===Global Settings===<br />
Here you can configure, what backends shall be used. one of them could be the default backend that is loaded on program start. If you do not specify a default backend, no backend is started, but you can choose to start one on the gui then, or both.<br />
[pythm]<br />
# backends to show in backend list<br />
backends=mpd,mplayer<br />
# the default backend to use, can be either<br />
# mpd or mplayer, or omitted<br />
# backend=mpd<br />
<br />
===MPD specific settings===<br />
In this section you can specify where your mpd server runs and how to authenticate with the server.<br />
[mpd]<br />
# mpd host<br />
host=localhost<br />
# mpd port<br />
port=6600<br />
# mpd password if used.<br />
#password=verysecret<br />
<br />
===Mplayer settings===<br />
For Mplayer usage, you can define your directory that contains your music files. You can define valid file endings, so the file browser will filter out not matched items. The filters can be used to hide specific items. Be careful when you use them, errors will not be handled if a regular expression is invalid. The renice-value is used to change the process priority mplayer that will be started in the background.<br />
[mplayer]<br />
# renice val for mplayer process<br />
renice=19<br />
# directory containing music (the start folder for the browser)<br />
musicdir=~<br />
# allowed file endings in browse mode, comma separated<br />
endings=ogg,mp3<br />
# filters to exclude in file browser. applied to files and directories<br />
# using regular expressions. use filtersN for more entries<br />
# default is to ignore all elements that start with a ".".<br />
filters0=\..*<br />
<br />
<br />
==Screenshots==<br />
* [http://projects.openmoko.org/docman/view.php/198/480/play-view.png Playback controls view]<br />
* [http://projects.openmoko.org/docman/view.php/198/481/playlist-view.png Playlist]<br />
* [http://projects.openmoko.org/docman/view.php/198/482/browsing-view.png File/Library Browsing]<br />
* [http://projects.openmoko.org/docman/view.php/198/483/backend-view.png Backend View]<br />
<br />
==Ideas, Feature Requests==<br />
Here you can put your Feature-ideas.<br />
* configure Pythm using the gui, not the config file.<br />
* mpd package for the freerunner, perhaps someone can do this?<br />
* build a gui using efl/etk<br />
* build a Gstreamer backend<br />
* interface to desktop media players to be able to transfer files between openmoko and the desktop media player, MTP is a standard for this but it is a USB device interface so might not be appropriate, iPod is another option<br />
* disable suspend when playing<br />
* avoid the user to import the collection every app start<br />
* better volume handling<br />
* better volume level (currently there's only one step from 'too low' and 'ear bleeding')<br />
* make buttons bigger<br />
<br />
==Known Problems==<br />
* bug in pygtk on the FreeRunner: http://docs.openmoko.org/trac/ticket/1718 - This is fixed, but some old Distributions still have this problem.<br />
* i18n: gettext support not implemented, planning<br />
* mplayer-backend: random mode not implemented<br />
<br />
==Reporting Bugs==<br />
Report bugs using the gforge-bugtracker-system:<br />
https://projects.openmoko.org/tracker/?group_id=198<br />
<br />
==New pythm==<br />
See:<br />
* http://www.opkg.org/package_1.html<br />
* http://lists.openmoko.org/nabble.html#nabble-td2164014i40<br />
<br />
[[Category:Audio Applications]]</div>Dareushttp://openmoko.org/wiki/PythmPythm2009-03-31T10:03:42Z<p>Dareus: /* Ideas, Feature Requests */</p>
<hr />
<div>{{ApplicationBox|<br />
Name=Pythm|<br />
Description=Pythm is a media player frontend, designed to control mplayer or mpd with one GUI on the FreeRunner. As of writing, you need to download [https://docs.openmoko.org/trac/ticket/2011 python-mokoui] separately.|<br />
Screenshot=Pythm.png|<br />
Homepage=http://projects.openmoko.org/projects/pythm/|<br />
TestedOn=-|<br />
PackageName=-<br />
}}<br />
<br />
==Introduction==<br />
Pythm is a gui that can be used to play music. At the moment there are two "backends" supported:<br />
* Using the mplayer program on the device. <br />
* Using the music player daemon (mpd) on any host in the network via wifi or GPRS.<br />
Other Backends can be written and integrated into the application, if needed or wanted.<br />
<br />
==Configuring Pythm==<br />
Pythm can be configured using a simple config-file (ini-like syntax). This file can be found here:<br />
/etc/pythm.conf<br />
You can edit the file in place or copy it to<br />
~/.pythm/pythm.conf<br />
The file is splitted in three sections:<br />
<br />
===Global Settings===<br />
Here you can configure, what backends shall be used. one of them could be the default backend that is loaded on program start. If you do not specify a default backend, no backend is started, but you can choose to start one on the gui then, or both.<br />
[pythm]<br />
# backends to show in backend list<br />
backends=mpd,mplayer<br />
# the default backend to use, can be either<br />
# mpd or mplayer, or omitted<br />
# backend=mpd<br />
<br />
===MPD specific settings===<br />
In this section you can specify where your mpd server runs and how to authenticate with the server.<br />
[mpd]<br />
# mpd host<br />
host=localhost<br />
# mpd port<br />
port=6600<br />
# mpd password if used.<br />
#password=verysecret<br />
<br />
===Mplayer settings===<br />
For Mplayer usage, you can define your directory that contains your music files. You can define valid file endings, so the file browser will filter out not matched items. The filters can be used to hide specific items. Be careful when you use them, errors will not be handled if a regular expression is invalid. The renice-value is used to change the process priority mplayer that will be started in the background.<br />
[mplayer]<br />
# renice val for mplayer process<br />
renice=19<br />
# directory containing music (the start folder for the browser)<br />
musicdir=~<br />
# allowed file endings in browse mode, comma separated<br />
endings=ogg,mp3<br />
# filters to exclude in file browser. applied to files and directories<br />
# using regular expressions. use filtersN for more entries<br />
# default is to ignore all elements that start with a ".".<br />
filters0=\..*<br />
<br />
<br />
==Screenshots==<br />
* [http://projects.openmoko.org/docman/view.php/198/480/play-view.png Playback controls view]<br />
* [http://projects.openmoko.org/docman/view.php/198/481/playlist-view.png Playlist]<br />
* [http://projects.openmoko.org/docman/view.php/198/482/browsing-view.png File/Library Browsing]<br />
* [http://projects.openmoko.org/docman/view.php/198/483/backend-view.png Backend View]<br />
<br />
==Ideas, Feature Requests==<br />
Here you can put your Feature-ideas.<br />
* configure Pythm using the gui, not the config file.<br />
* mpd package for the freerunner, perhaps someone can do this?<br />
* build a gui using efl/etk<br />
* build a Gstreamer backend<br />
* interface to desktop media players to be able to transfer files between openmoko and the desktop media player, MTP is a standard for this but it is a USB device interface so might not be appropriate, iPod is another option<br />
* disable suspend when playing<br />
* avoid the user to import the collection every app start<br />
* make the 'random' checkbox work<br />
* better volume handling<br />
* better volume level (currently there's only one step from 'too low' and 'ear bleeding')<br />
* make buttons bigger<br />
<br />
==Known Problems==<br />
* bug in pygtk on the FreeRunner: http://docs.openmoko.org/trac/ticket/1718 - This is fixed, but some old Distributions still have this problem.<br />
* i18n: gettext support not implemented, planning<br />
* mplayer-backend: random mode not implemented<br />
<br />
==Reporting Bugs==<br />
Report bugs using the gforge-bugtracker-system:<br />
https://projects.openmoko.org/tracker/?group_id=198<br />
<br />
==New pythm==<br />
See:<br />
* http://www.opkg.org/package_1.html<br />
* http://lists.openmoko.org/nabble.html#nabble-td2164014i40<br />
<br />
[[Category:Audio Applications]]</div>Dareushttp://openmoko.org/wiki/Flashing_the_GSM_FirmwareFlashing the GSM Firmware2009-03-17T10:02:32Z<p>Dareus: /* Introduction */</p>
<hr />
<div>{{Languages|GSM/Flashing}}<br />
((please also refer to [http://lists.openmoko.org/pipermail/devel/2008-November/003150.html this thread on devel-ML]))<br />
==Introduction==<br />
<br />
This is a step-by-step description of how the firmware is upgraded on a Neo with FLUID running on the device. Note that this process tolerates almost no variations. Stray from the instructions at your own peril. Instructions based on a posting by Werner (http://lists.openmoko.org/pipermail/openmoko-devel/2008-April/002605.html), thanks.<br />
<br />
Please note: Update to MOKO9-beta firmware isn't recommended by OM, and probably won't fix any recent issues like [http://docs.openmoko.org/trac/ticket/1024 #1024] at all. Use the latest firmware version instead.<br />
<br />
Please see http://people.openmoko.org/joerg/calypso_moko_FW for more recent FW-images.<br />
<br />
Please see http://people.openmoko.org/joerg/calypso_moko_FW/all_version__CHANGELOG.txt for changelog.<br />
<br />
For now there is some moko11, which should fix #666 (compatibility with some 3G sim cards), and also has a new command AT+CSIM. It also includes fixes related to hardware flow control and wakeup interrupt.<br />
<br />
This version is not supposed to fix [http://docs.openmoko.org/trac/ticket/1024 #1024] (constant re-registrations leading to lost calls and messages). For a workaround use a distro where deep sleep mode can be deactivated.<br />
<br />
We are planning to include this version in the factory image of the A7 run.<br />
<br />
We recommend you don't update by following this procedure, unless you feel very comfortable with commandline. Don't miss-spell any FLUID command!<br />
<br />
There is an SD-image, that greatly simplifies the whole GSM-update process - we suggest everybody who's not feeling completely comfortable with the procedure described herein use the image instead (not applicable to gta01 owners).<br />
<br />
'''Warning: there are chances to _irrecoverably_ damage your GSM modem calibration data, thus rendering it useless on messing around with FLUID! Use only the commands from this wiki page!'''<br />
<br />
The GSM-firmware didn't differ from GTA01 to GTA02, as the GSM-hardware didn't either. This means you can flash MOKO11 (or any other recent GSM-FW) to GTA01 as well.<br />
According to mwester, this worked for him to update from MOKO1 on a GTA01Bv4 to MOKO10b2, by following the steps described herein (if the main firmware can't be started, see troubleshooting section for additional instructions).<br />
<br />
Any reports on successful update, as well as problems encountered, or SIMs seen to work after update, all highly appreciated. Please add to the "discussion" tab of this wikipage. Thanks!<br />
<br />
==Phase 1: Preparations==<br />
<br />
* Download and install a distribution to your device that gives you SSH access. We recommend the fso-console image:<br />
<pre><br />
mickey@amethyst$ cd /tmp<br />
mickey@amethyst$ wget http://people.openmoko.org/mickey/images/openmoko-fso-console-image-glibc-ipk--20081028-om-gta02.rootfs.jffs2.summary<br />
mickey@amethyst$ dfu-util -a rootfs -R -D ./openmoko-fso-console-image-glibc-ipk--20081028-om-gta02.rootfs.jffs2.summary<br />
mickey@amethyst$ wget http://people.openmoko.org/mickey/images/uImage-2.6.24+r10+gitr75999+54524f4531c8b262431b794fea610d81bb351c86-r10-om-gta02.bin<br />
mickey@amethyst$ dfu-util -a kernel -R -D ./uImage-2.6.24+r10+gitr75999+54524f4531c8b262431b794fea610d81bb351c86-r10-om-gta02.bin<br />
</pre><br />
* Install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk on your device:<br />
<pre><br />
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/fluid_0.0+svn20070817-r2_armv4t_eabi.ipk<br />
</pre><br />
* Install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk on your device:<br />
<pre><br />
root@om-gta02:~# opkg install http://people.openmoko.org/joerg/calypso_moko_FW/s3c24xx-gpio_1.0+svnr4130-r2.1_armv4t.ipk<br />
</pre><br />
* Download <br />
http://people.openmoko.org/joerg/calypso_moko_FW/moko11/calypso-moko11.m0<br />
and place it into the /home/root directory:<br />
<pre><br />
root@om-gta02:~# cd $HOME<br />
root@om-gta02:~# wget http://people.openmoko.org/joerg/calypso_moko_FW/moko11/calypso-moko11.m0<br />
</pre><br />
<br />
==Phase 2: The Lobotomy==<br />
<br />
* Make sure '''nothing''' is accessing the GSM modem. If you're using the fso-console image from the link above, this will happen automagically on boot. On other systems, kill processes as you see fit (for FSO it's zhone, frameworkd and gsm0710muxd; for SHR it's ophonekitd, frameworkd and gsm0710muxd). If you're using a stable (or andy-tracking) kernel from Feb 26 or later on GTA02, see below for simplified instructions on powering the modem on/off.<br />
<br />
* Power off the modem:<br />
<pre><br />
root@om-gta02:~# echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
root@om-gta02:~# echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
root@om-gta02:~# s3c24xx-gpio b7=0<br />
root@om-gta02:~# stty 0:4:18b2:8a00:0:0:7f:15:4:0:0:0:0:0:0:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 -F /dev/ttySAC0<br />
root@om-gta02:~# stty 0:4:18b2:8a00:0:0:7f:15:4:0:0:0:0:0:0:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 -F /dev/ttySAC0<br />
root@om-gta02:~# echo -en "AT@POFF\r" >/dev/ttySAC0; sleep 1; echo -en "AT@POFF\r" >/dev/ttySAC0<br />
</pre><br />
<br />
* Launch the FLUID binary:<br />
<pre><br />
root@om-gta02:~# cd /usr/sbin<br />
root@om-gta02:/usr/sbin# FLUID_PORT=/dev/ttySAC0 fluid.exe \<br />
-oo -od13,13 -b 115200 \<br />
-f $HOME/calypso-moko11.m0<br />
</pre><br />
It should say something like this (takes a few seconds to load the file):<br />
<pre><br />
FLUID Revision 2.27, ...<br />
Bootloader: (reset target)<br />
</pre><br />
(this fluid command works even if the previous flashing was aborted and you have a broken and non-functional gsm-firmware due to this, as it uses the calypso ROM bootloader instead of the firmware bootloader. But in the case of non-functional gsm-firmware there's no way to power off the modem with AT@POFF command, therefore GTA02 users need to follow "modern kernel" (they might work even with older kernels) instructions and GTA01 users the troubleshooting section. Changing the -b to some lower baudrate might improve stability of flashing-process - the bootloader does autobaud, so you're free to use any rate)<br />
<br />
* Start a second SSH session and start the modem:<br />
<pre><br />
root@om-gta02:~# s3c24xx-gpio b7=1<br />
</pre><br />
<br />
FLUID should now say something like this (it will take a couple of minutes to finish):<br />
<br />
<pre><br />
(fluid, version 3) ok<br />
Checksumming (269 * 8kB = 2152kB): ok<br />
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok<br />
Program: (34 sectors, 267*8k=2136k) (*******************) ok<br />
</pre><br />
<br />
'''Note: If you get this instead: MESSAGE: File cmd.m0 not found, then you didn't do the ''cd /usr/sbin''. Please pay attention ;-)'''<br />
<br />
If FLUID does nothing, curse your bad luck and repeat the reset sequence, this is the whole 'echo 0/1, b7=0/1 stuff'.<br />
<br />
* To verify that everything went well, do this in either of the two sessions:<br />
<pre><br />
root@om-gta02:~# cat /dev/ttySAC0 &<br />
root@om-gta02:~# echo -en 'AT\r' >/dev/ttySAC0<br />
root@om-gta02:~# echo -en 'AT+CGMR\r' >/dev/ttySAC0<br />
+CGMR: "GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko11"<br />
root@om-gta02:~# kill %1<br />
</pre><br />
<br />
In some case you may receive this:<br />
<br />
<pre><br />
(fluid, version 3) ok<br />
Checksumming (269 * 8kB = 2152kB): ok<br />
Flash Detect: (0xEC, 0x22A0) Samsung K5A3240CT ok<br />
Program: (0 sectors, 0*8k=0k) () ok<br />
</pre><br />
<br />
It means the checksums of all sectors in calypso's FW and the new file to flash are identical. Probably you're trying to flash same version of FW that's already installed.<br />
<br />
Never downgrade to a version earlier than Moko6, or you will render the GSM unusable (certain internal data structures changed between Moko5 and Moko6).<br />
<br />
With modern kernels on GTA02 you can use this single command to "Power off the modem":<br />
<pre><br />
echo 0 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
</pre><br />
To "start the modem" you need to issue:<br />
<pre><br />
echo 1 >/sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
</pre><br />
<br />
==Troubleshooting==<br />
<br />
Some users weren't able to complete the upgrade since they got an error while the firmware was uploading in the GSM chip (like ''Flash operation timeout'').<br />
<br />
However a solution [http://n2.nabble.com/problems-with-calypso-firmware-update-tp1565196p1566012.html has been found] and it allows to use again the GSM modem.<br />
(please note this topic resides on [http://lists.openmoko.org/pipermail/devel/2008-November/003150.html devel-ML]. Don't spread over multiple lists please, as it won't help in getting a response to your request just in time, and most people following the main thread likely will miss your postings anyway)<br />
<br />
Use the following fluid command:<br />
<br />
<pre><br />
FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -od13,13 -b 115200 -f $HOME/calypso-moko11.m0<br />
</pre><br />
(Without FLOWCONTROL and with -oo to choose the ROM bootloader)<br />
<br />
Then on a ''second ssh session'' please use this instead of the gpio command:<br />
<pre><br />
echo 0 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
echo 1 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
</pre><br />
The firmware download should start now.<br />
<br />
=== Half-flashed GTA01bv4 GSM Modem ===<br />
<br />
For GTA01 the process of flashing when the main firmware is absent is more complicated as we have no easy way to power-cycle the modem.<br />
<br />
I recently had to do a special process to recover my GTA01bv4 after breaking the gsm modem with a failed flash. The process is actually fairly simple.<br />
<br />
* Unplug USB and remove the battery for about 10s to ensure that the GSM chipset is powered off, then replace the battery and re-connect the USB<br />
* boot up from a distro that is neutered so that it does not access or turn on the gsm modem at all (this is a really important prerequisitive, as nothing should turn on the modem by touching MODEM_ON line until fluid is ready to connect to it); one can do that simply by disabling start of ophonekitd (and to be on the safe side framworkd too) on SHR<br />
* issue this stty command twice:<br />
stty 0:4:18b2:8a00:0:0:7f:15:4:0:0:0:0:0:0:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0 -F /dev/ttySAC0<br />
* cd /usr/sbin<br />
* issue this fluid command (replace $HOME/filename.m0 with path to firmware you want to flash):<br />
FLUID_PORT=/dev/ttySAC0 fluid.exe -oo -od13,13 -b115200 -f $HOME/filename.m0<br />
* in another ssh session, issue this command:<br />
echo 1 > /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on<br />
<br />
After this, the flashing proceeded as expected. You don't need to do any special checks to ensure you have successfully flashed; if fluid reports everything is ok, it is actually ok.<br />
<br />
== uSD-card Image ==<br />
There's a beta version for flashing MOKO11 to GTA02 Freerunner only.<br />
* Download and untar http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz .<br />
<br />
* (apply `sudo` or use root-terminal according to your taste ;)<br />
* Insert a uSD to your PC, `umount` all uSD-partitions that might have been automounted (use `mount` or `df -h` to check). Do not use "safely remove" for this.<br />
<br />
* `dd` the image "flash-moko11-2.image" to the physical(!) uSD-device (this will erase all data from your uSD!). `Sync` or `eject <device>`.<br />
<br />
* Insert uSD to your FR, boot from NOR-U-Boot to uSD, wait until green "d_o_n_e" shows on screen (takes some 6min). Remove bat and uSD, or login via ssh. `mickeyterm` will access modem.<br />
<br />
NOTE: If you don't have a uSD reader on your PC, you can `dd` from neo: install task-base-smbfs, u(n)mount /media/card, mount the directory in which you have the "flash-moko11-2.image" file and do the dd stuff. This will take about 12 minutes.<br />
<br />
[[Category:GSM]]<br />
[[Category:GSM]]</div>Dareushttp://openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2009-03-16T15:33:44Z<p>Dareus: /* Connecting your FreeRunner to your computer */</p>
<hr />
<div>{{Languages|SHR}}<br />
{{Distributions|SHR}}<br />
{{SHR}}<br />
<br />
== Why SHR exists ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a community driven distribution composed of the [[OpenmokoFramework|FSO]] and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the [[Openmoko2007.2]] GTK software in combination with the new [[OpenmokoFramework|FSO]], but things have changed.<br />
<br />
====Why not just use plain FSO?====<br />
[[FSO]] is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.<br />
<br />
FSO is by far the most stable & usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application.)<br />
<br />
FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.<br />
<br />
Other people are supposed to put a front end on FSO. So that's what we're doing.<br />
<br />
==Feature overview==<br />
<br />
In the overview below are all the essential features and their status for the currect '''out of the box''' SHR testing distribution (2009-03-03+modules+updates). Green indicates that this part is well functioning, 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.<br />
<br />
{| cellspacing="0" class="sortable wikitable" border="1" style="font-size: 85%; text-align: left; width: auto;"<br />
|-<br />
! Category<br />
! Name<br />
! Functionality<br />
! Comments<br />
|-<br />
| System<br />
| Power Management<br />
| style="background:#88FF88;"| Suspend<br />
| when slow, use [[Qi]]<br />
|-<br />
| System<br />
| Package manager<br />
| style="background:#FFDD88;"| Installing and upgrading packages<br />
| style="background:#FFDD88;"| [http://trac.shr-project.org/trac/ticket/314 SHR ticket #314]<br />
|-<br />
| System<br />
| Keyboard<br />
| style="background:#FFDD88;"| Offer stylus and finger friendly keyboards<br />
| style="background:#FFDD88;"| install alternative keyboards [http://trac.shr-project.org/trac/ticket/200 SHR ticket #200]<br />
|-<br />
| GSM<br />
| Network<br />
| style="background:#88FF88;"| Connect via SIM and PIN<br />
|<br />
|-<br />
| GSM<br />
| Network<br />
| style="background:#FF8888;"| Flight mode<br />
| style="background:#FF8888;"| [http://trac.shr-project.org/trac/ticket/333 SHR ticket #333]<br />
|-<br />
| GSM<br />
| Dailer<br />
| style="background:#88FF88;"| Receiving Call<br />
|<br />
|-<br />
| GSM<br />
| Dailer<br />
| style="background:#88FF88;"| Making Call<br />
|<br />
|-<br />
| GSM<br />
| Phone Log<br />
| style="background:#88FF88;"| Overview Log (In, Out, Answered, All)<br />
| style="background:#FF8888;"| should be in SHR Illume theme<br />
|-<br />
| GSM<br />
| Phone Log<br />
| style="background:#88FF88;"| Making reply Call from Log<br />
|<br />
|-<br />
| GSM<br />
| Phone Log<br />
| style="background:#FF8888;"| Sending reply SMS from Log<br />
|<br />
|-<br />
| GSM<br />
| SMS<br />
| style="background:#88FF88;"| Receiving SMS<br />
|<br />
|-<br />
| GSM<br />
| SMS<br />
| style="background:#88FF88;"| Selecting SMS from Overview<br />
|<br />
|-<br />
| GSM<br />
| SMS<br />
| style="background:#88FF88;"| Viewing SMS<br />
|<br />
|-<br />
| GSM<br />
| SMS<br />
| style="background:#88FF88;"| Sending new SMS<br />
|<br />
|-<br />
| GSM<br />
| SMS<br />
| style="background:#88FF88;"| Sending reply SMS<br />
|<br />
|-<br />
| GSM<br />
| SMS<br />
| style="background:#FF8888;"| Making reply Call<br />
|<br />
|-<br />
| GSM<br />
| SMS<br />
| style="background:#88FF88;"| Deleting SMS<br />
|<br />
|-<br />
| GSM<br />
| GPRS<br />
| style="background:#FF8888;"| Configuring and Enabling TCP/IP<br />
|<br />
|-<br />
| Shared<br />
| Contacts<br />
| style="background:#88FF88;"| Reading SIM contacts<br />
|<br />
|-<br />
| Shared<br />
| Contacts<br />
| style="background:#88FF88;"| Selecting SIM contact from Overview<br />
|<br />
|-<br />
| Shared<br />
| Contacts<br />
| style="background:#88FF88;"| Editing SIM contact<br />
|<br />
|-<br />
| Shared<br />
| Contacts<br />
| style="background:#88FF88;"| Deleting SIM contact<br />
| does not stay at position in list<br />
|-<br />
| Shared<br />
| Contacts<br />
| style="background:#FF8888;"| Quick lookup contact with keyboard<br />
|<br />
|-<br />
| Shared<br />
| Contacts<br />
| style="background:#88FF88;"| Calling contact<br />
|<br />
|-<br />
| Shared<br />
| Contacts<br />
| style="background:#88FF88;"| Sending SMS to contact<br />
|<br />
|-<br />
| WiFi<br />
| Ethernet<br />
| style="background:#88FF88;"| Configuring and Enabling TCP/IP<br />
| 1) Settings->Internet->WiFi radio=On 2) Mofi<br />
|-<br />
| WiFi<br />
| MoFi<br />
| style="background:#FFDD88;"| Network Manager<br />
| style="background:#FFDD88;"| [http://trac.shr-project.org/trac/ticket/338 SHR ticket #338]<br />
|-<br />
| GPS<br />
| Service<br />
| style="background:#88FF88;"| Receiving GPS data<br />
| automatically turned on<br />
|-<br />
| USB<br />
| Ethernet<br />
| style="background:#88FF88;"| Configuring and Enabling TCP/IP<br />
| style="background:#FF8888;"| done automatically with insecure password<br />
|-<br />
| Audio<br />
| Headset<br />
| style="background:#FF8888;"| Handsfree calling<br />
| headphones work, microphone does not work<br />
|-<br />
|}<br />
<br />
== Install ==<br />
<br />
Installing SHR is very easy. I will explain how to install the [http://build.shr-project.org/shr-testing/images/om-gta02/ testing] version of SHR for GTA02 (Freerunner). It is stable enough for a daily use. Stable version will be available soon ([http://blog.shr-project.org/ Stable announcement]), [http://build.shr-project.org/shr-unstable/images/om-gta02/?C=M;O=D unstable] (for the adventurous testers) is also available, but read [http://blog.shr-project.org/2009/03/time-for-testing.html this blog announcement] on why this is currently not recommended.<br />
<br />
I suppose that you know how to use [http://wiki.openmoko.org/wiki/NeoTool NeoTool]<br />
<br />
- the [[Qi]] bootloader (optional, u-boot should work as well)<br />
<br />
- the [http://build.shr-project.org/shr-testing/images/om-gta02/uImage-om-gta02-latest.bin kernel]<br />
<br />
- the root filesystem ([http://build.shr-project.org/shr-testing/images/om-gta02/shr-lite-image-om-gta02.jffs2 flash image] or [http://build.shr-project.org/shr-testing/images/om-gta02/shr-lite-image-om-gta02.tar.gz tarball])<br />
<br />
You can view the sources [http://git.shr-project.org/git/ here].<br />
<br />
== Connecting your FreeRunner to your computer ==<br />
For the next configuration steps, you will need to type some commands. It is much easier to type on a real keyboard than on a touch screen. <br />
So you need to connect your FR to you computer, and make a bridge to internet.<br />
Use the [[USB Networking]] page for help about configuring your host computer.<br />
NOTE: On first boot after flashing, USB networking can not work. If it's happening, simply reboot and try again.<br />
<br />
== Setting local time ==<br />
As any linux system, the UTC time is used by the system. First of all, adjust this time:<br />
date -u -s 010220052009<br />
Fri Jan 2 20:05:00 UTC 2009<br />
<br />
Then, you need to "localise" your system. <br />
Search for the appropriate country with:<br />
opkg list | grep tzdata<br />
<br />
then install the one corresponding to your area. <br />
opkg install tzdata-europe<br />
<br />
Then select your city (search the city available in /usr/share/zoneinfo/your-country, example Paris)<br />
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime<br />
<br />
You can fully localise your system by installing the glibc-binary-localedata correponding to your langage. Search the ones available with:<br />
opkg list | grep glibc-binary-localedata<br />
<br />
install with (example for France)<br />
opkg install glibc-binary-localedata-fr-fr<br />
<br />
== Changing root password ==<br />
SHR is shipped without root password (just press enter)<br />
<br />
This is dangerous if you connect using USB. You need to activate the root password:<br />
<br />
passwd<br />
<br />
and type your selected password (2 times)<br />
<br />
== Customize the RingTone ==<br />
You need to have a file containing the RingTone you want for your FR. You can find some at [http://wiki.openmoko.org/wiki/Ringtones#svn.openmoko.org_ringtones RingTone]<br />
<br />
Then transfer it to your FR :<br />
scp file root@192.168.0.202:/usr/share/sounds/<br />
<br />
Now you can select ringtone in SHR Settings.<br />
<br />
== Sound Control ==<br />
<br />
Up to now, there is no graphical interface to control the sound<br />
=== Mic and HP ===<br />
The first idea is to use alsamixer; bad idea! There are 94 controls, and your modifications will be lost at the next reboot.Finding documentation is not easy. Here is my understanding: <br />
Scenari are used for each case. They are located in /usr/share/openmoko/scenarios/<br />
- capturehandset.state <br />
- gsmheadset.state <br />
- headset.state <br />
- voip-handset.state<br />
- gsmhandset.state<br />
- gsmspeakerout.state<br />
- stereoout.state<br />
<br />
Each file is a set of value for the 94 parameters. I have identified some:<br />
<br />
- Control 48: internal mic of the tel (set to 2 or 3)<br />
<br />
- Control 4 : internal speaker (set from 110 to 120)<br />
<br />
- Control 49: headset mic<br />
<br />
- Control 3 : headset speaker<br />
<br />
<br />
<br />
Generic info to the Neo soundsystem:<br />
<br />
* [[Neo 1973 audio subsystem]]<br />
* [[Neo alsamixer#Settings_Descriptions|Neo alsamixer - Settings Descriptions]]<br />
* [[Neo Freerunner audio subsystem]]<br />
<br />
=== Ringing ===<br />
<br />
<br />
You can define a short ringtone, repeated many times, or a long one, repeated 1 time<br />
<br />
File: /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameter: ring-volume # Ring Volume control 0 (mini) to ? maxi)<br />
Parameter: ring-length # min time for ringtone. Must be greater than the duration of you ringtone<br />
<br />
File: /etc/freesmartphone/opreferences/schema/phone.yaml<br />
Parameter: ring-loop # define the number of loop of ringtone to play<br />
<br />
=== Message alert ===<br />
File: /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
Parameter: message-volume # Ring Volume control 0 (mini) to ? maxi)<br />
Parameter: message-length # min time for message alert. Must be greater than the duration of you message alert<br />
<br />
File: /etc/freesmartphone/opreferences/schema/phone.yaml<br />
Parameter: message-loop # define the number of loop of incoming message music to play<br />
<br />
<br />
<br />
<br />
== Known Issues ==<br />
=== Phone ===<br />
<br />
GSM network is lost after one day of uptime: restart your FR once a day!<br />
<br />
=== Address Book ===<br />
<br />
SHR is not implementing a PIM (Personal Information Manager) yet. Work is in progress, but to included in SHR testing this has some consequences on daily use:<br />
<br />
* Only contacts on the SIM card are available.<br />
<br />
* It is not possible to import a Vcard file.<br />
** It seems to be possible with [gopher://gopher.fnordpol.de/9/data/DbusAccessScripts_0.0.0.tar.gz this] script written by [[User:Zem#DBus_Access_Scripts|Zem]].<br />
<br />
== More Information ==<br />
<br />
Visit:<br />
* [http://blog.shr-project.org Blog]<br />
* [http://trac.shr-project.org Trac (Bugtracker)]<br />
* [http://git.shr-project.org Git (Sourcecode-repository)]<br />
* [http://build.shr-project.org Buildhost (Downloads)]<br />
* [http://shr-project.org/trac/wiki/Tweaks Tweaks (On the Wiki)]<br />
* [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel SHR Development Mailing List]<br />
<br />
[[Category:SHR]]</div>Dareushttp://openmoko.org/wiki/Main_Page/itMain Page/it2009-02-23T10:32:15Z<p>Dareus: </p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
{{Languages|Main Page}}<br />
<br><br />
<DIV ALIGN=CENTER><big>'''[[Openmoko/it|Openmoko]]™ Open. Mobile. Free.'''</big><br></DIV><br />
<BR><br />
<br />
==<font color=75d806>Introduzione ad Openmoko</font>==<br />
<br />
[[Image:GTA02.gif |100px|left|frontside]]<br />
<br />
[[Openmoko/it|Openmoko]]™, che nasce come progetto [http://it.wikipedia.org/wiki/Open_source Open Source] sotto [[License/it| licenza GPL e LGPL ]] dedicato al rilascio di uno stack open software su piattaforme mobili, ha consegnato il primo prodotto, il Neo1973, il 9 Luglio 2007 e ha quindi conferito il progetto in una start-up company con uno scopo: creare ottimi prodotti mobile utilizzando lo stack Openmoko: Open. Mobile. Free.<br />
<br />
Lo stack Openmoko, che include un server X completo, consente ad utenti e sviluppatori di trasformare piattaforme hardware mobile in prodotti unici. La nostra licenza fornisce a sviluppatori ed utenti la libertà dalla tortura dell'accecamento tramite il "ferro rovente sugli occhi", libertà di personalizzare esternamente i propri dispositivi o rifarli modificandoli radicalmente, di cambiare la carta da parati o ricostruire l'intera casa da zero! Gli garantisce la libertà, per esempio, di trasformare il telefono in un dispositivo medico, o in un dispositivo di vendita, o la libertà di installare semplicemente il proprio software preferito. Oltre a rendere libero il software sui nostri dispositivi, abbiamo anche rilasciato i nostri files CAD sotto licenza Creative Commons. Liberando il codice sotto GPL, abbiamo dato alla community degli sviluppatori FOSS la possibilità di "rifarlo da capo". Liberando i files CAD abbiamo dato a designer industriali ed ingegneri la stessa opportunità.<br />
<br />
<br />
==<font color=75d806>I Prodotti Openmoko</font>==<br />
[[image:FIC-neo1973 small.jpg|100px|left|frontside]]<br />
<br />
{{Bar/it}}<br />
<br />
Il primo prodotto Openmoko, il [[Neo1973/it|Neo1973]], venduto esclusivamente tramite [https://direct.openmoko.com/ Il Negozio Online Openmoko]. Esaurito agli inizi di Febbraio 2008.<br />
<br />
Openmoko ha iniziato la vendita del Neo FreeRunner (GTA02), la seconda versione del Neo, il 3 Luglio 2008. Guarda anche nei [[GroupSales|gruppi di acquisto]] per ottenere uno sconto e dei gadget extra. Se hai appena ricevuto il tuo FreeRunner, vai su [[Getting Started with your Neo FreeRunner/it|Iniziare con il tuo Neo FreeRunner]] per dei consigli.<br />
<br />
==<font color=75d806>Sviluppa con noi Openmoko</font>==<br />
<br />
{| class="wikitable" cellspacing="4" cellpadding="6" width=100%<br />
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | <font color="white" >Guide per gli Sviluppatori</font><br />
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |<font color="white" >Test/Emulazione</font><br />
|-<br />
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |<br />
===<font color=white>Sviluppatori </font>===<br />
* [[Toolchain|utilizzare la toolchain]]<br />
* <font color=white>VMware</font><br />
* [[Python|introduzione a python]]<br />
* [[Openmoko under QEMU|Openmoko sotto Qemu]]<br />
<br />
===<font color=white>Integrazione di Sistema e personalizzazione di una distribuzione</font>===<br />
* [[OpenEmbedded|OE-The distribution building framework]]<br />
* [[MokoMakefile/it|Costruire Openmoko utilizzando MokoMakefile ]]<br />
<br />
===<font color=white>Basso livello / sviluppo del sistema </font>===<br />
* <font color=white>Basso Livello</font><br />
* [[u-boot]] <font color=white>-The bootloader we use, including docs to our modifications</font><br />
* [[kernel/it]] <font color=white>-Il Kernel Linux utilizzato, inclusa la documentazione alle nostre modifiche</font><br />
* [[gsmd/it]] <font color=white> - il Demone GSM che gestisce il modem GSM</font><br />
* [[agpsd]] <font color=white>-the AGPS (Assisted GPS) daemon</font><br />
<br />
|valign="top" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |<br />
===<font color=white>Prove</font>===<br />
*[[GSM unit test]]<br />
*[[GSM 850 test]]<br />
*[[GSM unit test]]<br />
*[[Test Cases]]<br />
*[[Test Plans]]<br />
*[[Test Reports]]<br />
<font color=white> ※</font> [[:Category: Test | See More About Test]]<br />
<br />
===<font color=white>Emulazione</font>===<br />
*[[Getting Openmoko working on host with Xephyr]]<br />
*[[Test_Openmoko Emulation with chroot image]]<br />
|}<br />
<br />
<br />
<br />
==<font color=75d806>La community Openmoko</font>==<br />
Chiunque può unirsi al progetto Openmoko e contribuire a disegnare prodotti open. Unisciti a noi e collabora ad un [[Development resources/it | progetto]], incluso il Wiki di Openmoko. Leggi la [[Help:Contents | wiki editing help]]page per ottenere informazioni su come contribuire a questo wiki.<br />
<br />
Puoi partire dalla pagina di [[introduction/it|introduzione]], dalle foto, dai video o dalla Openmoko Wiki Official Index Page. Come al solito possono essere d'aiuto le [[FAQ/it | Frequently Asked Questions]] (FAQ) e le [http://lists.openmoko.org/mailman/listinfo/| mailing list].<br />
<br />
{| class="wikitable" cellspacing="4" cellpadding="6" width=100%<br />
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600; " | <font color="white" >Novità</font><br />
! width=50% style="background:#ff6600;border-left:5px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #ff6600;" |<font color="white" >Community & Eventi</font><br />
|-<br />
|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |<br />
==<font color=white>Per iniziare</font>==<br />
*[[Getting Started with your Neo FreeRunner/it|Iniziare con il tuo Neo FreeRunner]]<br />
*[[Getting Started with your Neo1973/it|Primi passi con il tuo Neo1973]]<br />
==<font color=white>Snapshot</font>==<br />
*<font color=white>[[Snapshot_review|Qui]] è possibile trovare le recensioni delle snapshot build giornaliere, mentre [http://downloads.openmoko.org/recommended/ qui] troverete le immagini kernel e root recensite.<br />
Si noti che il set raccomandato non è sempre l'ultimo disponibile, ma il più stabile, utilizzabile e funzionale.</font><br />
|valign="TOP" style="background:#333333;border-left:5px solid white;border-right:5px solid white;border-bottom:0px solid white; border:1px solid #cccccc; " |<br />
<br />
==<font color=white>Aggiornamenti per la Community</font>==<br />
<font color=white>Per gli ultimi aggiornamenti, si vedano i [[Community_Updates|Community Updates]]</font><br />
<br />
<font color=ffffff> ※</font>[[:Category:Community| Altre Informazioni sulla Community...]]<br />
<br />
==<font color=white>Uno sguardo d'insieme al wiki</font>==<br />
*<font color=white>Per un panorama generale del Wiki Openmoko, si vedano le [[Openmoko Wiki Official Index Page]].</font><br />
==<font color=white>Eventi</font>==<br />
*[[Summer of Code 2008]]<br />
*[[Openmoko Education/zh tw]]<br />
*[[Events:FOSDEM 2008]]<br />
*[[OpenLab]]<br />
<br />
<font color=ffffff> ※</font>[[:Category:Event| Altre informazioni sugli Eventi...]]<br />
<br />
|}<br />
<br />
<br />
==<font color=75d806>Primi passi con il Wiki Openmoko</font>==<br />
Il Wiki Openmoko è open. Chiunque può utilizzarlo. Ci si trovano informazioni come: documentazione hardware e software, elenchi di bug, novità per la community di Openmoko e molto altro ancora. Utilizza il nostro wiki, modificalo. contribuisci con contenuti di valore, ed aiuta gli altri. Per un quadro d'insieme del Wiki Openmoko, basta visitare la [[Openmoko Wiki Official Index Page|Openmoko Wiki Official Index Page]].<br />
<br />
* Leggi le [[Openmoko Wiki Editing Guidelines]]<br />
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]<br />
* [http://meta.wikimedia.org/wiki/Help:Wikitext_reference MediaWiki Wikitext Reference]<br />
* Quando si aggiunge una nuova pagina, occorre far riferimento alla [[Openmoko Wiki Categories Index Page|Openmoko Wiki Categories Index Page]] per inserirla nella giusta categoria.<br />
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]</div>Dareushttp://openmoko.org/wiki/Setting_Date_and_TimeSetting Date and Time2009-01-09T11:38:53Z<p>Dareus: /* Setting date/time from your linux box */</p>
<hr />
<div>Linux systems (such as the FreeRunner) prefer that the system clock be set to universal time (UTC). Then, you will need to configure the timezone to display the time adjusted to local time.<br />
<br />
See [[Timezone]] for instructions on changing the time zone.<br />
<br />
For more information on Linux timekeeping, see [http://www.linuxsa.org.au/tips/time.html Linux, Clocks, and Time]. (But ignore mentions of ''/etc/sysconfig/clock''. That doesn't apply to the Openmoko environment.)<br />
<br />
== Setting the date/time using "date" ==<br />
<br />
To change the date on your FreeRunner, issue one of the following commands:<br />
<br />
date -s ''MMDDhhmm''<br />
date -s ''MMDDhhmmYYYY''<br />
date -s ''MMDDhhmmYYYY.ss''<br />
<br />
where ''MM'' is the month, 01-12; ''DD'' is the day, 01-31; ''hhmm'' is the time, 0000-2359; ''YYYY'' is the optional year, and ''.ss'' is the optional seconds.<br />
<br />
== Setting date/time from your linux box ==<br />
<br />
<pre><br />
ssh root@openmoko "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
</pre><br />
<br />
== Setting date/time with a python GUI ==<br />
<br />
Tested on Neo1973 (OM2007.2), the 'time-man' tool is at <br />
<br />
http://free-opensource.qvantel.net/mediawiki//index.php/Time-tool<br />
<br />
== Setting your local timezone ==<br />
<br />
To have your FreeRunner display time appropriate to your local timezone, update the /etc/localtime symlink to point to the file in /usr/share/zoneinfo that represents your timezone. For example, in an SSH session to the phone, or in a terminal running on the phone:<br />
<br />
# ls -l /etc/localtime<br />
lrwxrwxrwx 1 root root 27 Jul 10 23:05 /etc/localtime -> /usr/share/zoneinfo/PST8PDT<br />
# ln -s /usr/share/zoneinfo/CST6CDT /etc/localtime<br />
<br />
(Based on [http://n2.nabble.com/Date-%2B-NTP-tp675145p675163.html this post on the support mailing list])<br />
<br />
You may want to try this if the above returns something like "file exists".<br />
# ln -sf /usr/share/zoneinfo/CST6CDT /etc/localtime<br />
the -f (--force) removes existing destination files. (CQ).<br />
<br />
== Setting the date/time automatically with NTP ==<br />
<br />
If your FreeRunner is connected to the internet, you can instead set the time automatically:<br />
<br />
<code><br />
opkg install ntpclient<br/><br />
ntpclient -s -h pool.ntp.org<br />
</code><br />
<br />
If your FreeRunner is connecting to the internet through a USB host, make sure you allow UDP traffic to pass through on port 123 (NTP) on your host machine or you may get a "no route to host" error from ntpclient.<br />
<br />
Have a look over [https://wiki.muc.ccc.de/openmoko#freerunner1 over here] where this process is automated whilst udhcpc is started, which happens automatically for wifi connections initiated by Mofi and friends.<br />
<br />
== Syncing the hardware clock ==<br />
<br />
No matter which method you used above, sync the hardware clock with the system time to make your change persist over reboots:<br />
<br />
hwclock --systohc<br />
<br />
Note: if you run the [[ASU]] image, hwclock will not work. Instead you can use: <br />
<br />
echo "W\n" > /var/spool/at/trigger<br />
<br />
Here is a link from the community mailing list for using hwclock with the [[ASU]] image<br />
:http://lists.openmoko.org/pipermail/community/2008-July/023786.html<br />
<br />
== Setting the date/time automatically with gps ==<br />
<br />
[http://projects.openmoko.org/projects/gpv/ GPS Sight] has a button to sync the hardware clock to the gps clock.<br />
<br />
First you have to make sure gps works on you neo. You can do that by following the steps in the [[Getting_Started_with_your_Neo_FreeRunner#Use_the_GPS]].<br />
<br />
The second step is to install GPS Sight:<br />
<br />
# opkg install http://projects.openmoko.org/frs/download.php/227/gpssight_0.8.4_freerunner.armv4t.ipk<br />
<br />
The last step is the actual syncing of the clock. For this, simply run the GPS Sight program from the main menu, wait for it to find the gps time and click the button labeled "Sync clock".<br />
<br />
== Future Work ==<br />
<br />
Presumably it might also be possible to use gpspipe (or something else) to set the date once you have a gps fix automatically? In addition, the phone stack should set the date, time, and timezone once connected to a network.<br />
<br />
[[Category:Settings]]<br />
[[Category:Advanced End User]]</div>Dareushttp://openmoko.org/wiki/Talk:USB_NetworkingTalk:USB Networking2008-12-23T10:02:11Z<p>Dareus: </p>
<hr />
<div>= Driver options in kernel config =<br />
Hi, I didn't want to change it in case I was wrong, but I believe that the options to configure your<br />
desktop as a host are not in "USB Support" as the article says:<br />
"Both options are available in the Device Drivers -> USB support -> USB Network Adapters. For more info see the usbnet driver homepage."<br />
Aren't the options in <pre>Device Drivers -> Network Device Support -> USB Network Adapters</pre><br />
Can someone confirm this? I don't want to send people in the wrong direction, but that is the way it is in my system. Thanks. [[User:Mmanjos|Mmanjos]] 15:36, 4 November 2007 (CET)<br />
<br />
= Thoughts on USB networking in the final product =<br />
<br />
There was some discussion on the #openmoko IRC channel on how to approach the USB networking automatic setup eventually in the final product.<br />
<br />
The Neo's IP will probably need to remain static, and chosen, as it is now, from some local address space. I would personally suggest to change to using an address higher in the 192.168.0.0 space, say, 192.168.19.73 (ehhehe) to reduce chance of conflicts. (Or use link-local space?)<br />
* I don't think the 192.168.0.0 space is very problematic if network is configured as 192.168.0.192/26 instead of 192.168.0.0/24, as explained in the Debian example I've just enhanced in the page. [[User:OlivierBerger|OlivierBerger]] 07:35, 25 July 2008 (UTC)<br />
<br />
Anyway, for the casual user, and even comfort-seeking geeks, OpenMoko will need to provide DHCP service. It will probably be also a good idea to run a DNS proxy, since that way the host doesn't need to care about changing DNS servers, and the caching is a good idea anyway for high latency GPRS. I'd suggest dnsmasq, which is simple and can handle both tasks. I assume the Neo will do IP masquerading for the USB host when it's acting as its default gateway.<br />
<br />
Now, the DHCP server should obviously serve up a local address to the USB host when connected (assuming here most hosts will use DHCP by default to configure the USB network device, which I think is a valid assumption, and if some don't, we can't help things automagically anyway).<br />
<br />
What's more complicated is when to give a default gateway and a DNS server address. You don't want to do it all the time, that would screw with simple use cases (detailed more below).<br />
<br />
== Suggested policies ==<br />
<br />
At this point I suggest, based on the aforementioned IRC discussion, the following policy:<br />
<br />
1) If the device is plugged into a host, and the device is not on-line with GPRS, do not go on-line, and only give a private address (no default route/dns) to host.<br />
<br />
2) If the phone is told to go on-line with GPRS (or, in the future, other mobile protocols) and it's presently hooked up to a USB host with only a local network connection, query the user if they want to use the Internet also from the computer. If yes, run the interface down, then up again, thus triggering the host to make a new DHCP query. Now serve up default gateway and dns information too.<br />
<br />
3) If the phone is told to go off-line while routing a network connection to a USB host, cycle the interface again and only serve up a local address. Possibly ask if the user really wants to disconnect considering the tether.<br />
<br />
4) If the phone is presently on-line with GPRS, and it's plugged into a host, initialize with only the local network connection, query the user (with a dialog or less obtrusively with a suitable panel button or panel GPRS menu changing appearance) whether they want to use the connection from the computer too. If yes, cycle interface, serve up default gateway and dns. Remove the query if usb disconnected.<br />
<br />
== Use cases ==<br />
<br />
The rationale for not serving up a default route too eagerly is that this device charges from USB, people will probably sync it via USB, and they don't want any hassle doing that. Use cases to demonstrate:<br />
<br />
1) John wants to sync addressbooks between his home desktop and the Neo. He uses USBnet for this, because where he lives, GPRS is crazy expensive, and besides, he doesn't want to have internet-visible servers on the desktop. He hooks the Neo up, and only wants local data transfer capabilities. What he doesn't want is to lose access to his broadband, so serving up default gateway and DNS would make him angry.<br />
<br />
2) Shirley has CommunitasticoMoko installed on her Neo, and thus is on-line via GPRS pretty much constantly. (Yes, Shirley lives in some more GPRS-friendly area.) Shirley wants to load up new music from her desktop to the phone, so she hooks the Neo up. Even though GPRS is on-line for CommunitasticoMoko, she doesn't want the desktop to suddenly lose her home broadband access. She gets asked (in the more or less obtrusive ways above) if she'd like to provide Internet access to the host. She doesn't care about the question, just transfers the files, unhooks, and is on the go. The query disappears, not bothering her anymore.<br />
<br />
3) Shirley's CommunitasticoMoko buddy Roxanne hooks the Neo up to her laptop. As she is also on-line via GPRS, she gets the query. She first thinks to only sync up the address books of her laptop and the Neo, but while doing that, she decides to go surfing for a bit too. Up till now, she's had a local network between the devices, but as she acknowledges to the Neo that yes, she wants on-line, the laptop will get a default gateway and a DNS server, and surfing she goes.<br />
<br />
4) Matt just wants to charge his Neo up. He couldn't care less about any networking, let alone the Neo interfering with his existing network connections. He hooks the Neo up, and the local network is initialized. That's of little consequence to Matt, but he gets the phone charged.<br />
<br />
5) Tom is charging his Neo via his laptop at home, when his home broadband is cut off by a road crew. He has reasonable GPRS pricing, so he wants it up as a backup. He tells the Neo to go on-line, whereupon he is asked, since the Neo is already plugged in, if he wants to share the connection to his laptop. And yes he does. The Neo cycles the interface, and the laptop gets an Internet connection.<br />
<br />
== Open questions == <br />
<br />
How to deal with Bluetooth and WiFi routing (for GTA02) in conjuction? Probably you'd not want to serve up default gateway per default if you're BT tethered, however, user might want to have one device BT tethered and another USB tethered. So perhaps best to leave the option open to share the connection via USB even if BT tethering is active, though especially in this case the option shouldn't be obtrusive; it'd probably be a rare use case.<br />
<br />
=== Additional use cases ===<br />
<br />
There is another use cases I'd like to suggest for consideration:<br />
<br />
* Bertrand (who has a good broadband connection at home) lives in Expensive GPRS Country and has no Bluetooth / WLAN. He wants to plug his phone into his computer and run ipkg updates via his broadband connection. His PC is serving as a DHCP server and/or bridges all traffic through its interfaces (with STP preventing loops).<br />
<br />
Suggested policy:<br />
* Before the phone assigns itself a local address, it asks for a DHCP address. If that fails, a link local address according to RFC 3927 is assigned.<br />
<br />
= Operation on Gentoo =<br />
<br />
One way of doing routing and NAT was recently added to the Wiki. I followed the lead of the other examples and did it this way:<br />
<br />
# Neo1973<br />
config_usb0=( "192.168.0.200 netmask 255.255.255.0" )<br />
postup() {<br />
case "${IFVAR}" in <br />
"usb0") <br />
iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
echo 1 > /proc/sys/net/ipv4/ip_forward<br />
iptables -P FORWARD ACCEPT<br />
return 0;;<br />
esac<br />
return 0<br />
}<br />
predown() {<br />
case "${IFVAR}" in <br />
"usb0") <br />
iptables -D POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24<br />
echo 0 > /proc/sys/net/ipv4/ip_forward<br />
return 0;;<br />
esac<br />
return 0<br />
}<br />
<br />
If the intent is to have the NATing and routing turn on and off as the neo is plugged and unplugged, this is probably an approach that is more like that than the other way.<br />
<br />
== Dealing with NetworkManager ==<br />
<br />
NetworkManager (the default for [http://www.sabayonlinux.org/ sabayon]) bypasses /etc/conf.d/net.usb0 by default. You need to modify /etc/conf.d/rc (or /etc/rc.conf on OpenRC) from<br />
RC_PLUG_SERVICES="!net.*"<br />
to somehing like<br />
RC_PLUG_SERVICES="!net.eth* !net.wlan*"<br />
<br />
(see http://gentoo-wiki.com/HOWTO_NetworkManager)<br />
<br />
= Rewrite =<br />
<br />
I have rewritten this page for accuracy and clarity. I took out redundant stuff, and tried to make it much clearer based upon my networking experience and discussions with users having problems in the #openmoko IRC channel. I tried to avoid and remove first person comments (although made some myself). <br />
<br />
The first section is very deliberate, since the ordering of this page was illogical, having gathered many random comments. This allows user to step through the parts and make sure each is right before moving on. There are further explanations that could be added - instead of a subnet, an explicit device route could be added for the .202 host, over USB. which avoids most routing problems (unless your desktop is also .202). I hope though even without that, this covers most scenarios. I intend to rewrite some of the other pages in the same way.<br />
<br />
= Changing flow =<br />
<br />
Miohtama, I'm not entirely happy about your unjustified reordering. The page was structured in order to carefully explain to new users how to make it work, and for it be a very precise guide for helping those on IRC having problems - users I deal with. I don't believe that your changes really facilitate that. Putting stuff together because it seems to might superficially seem like a good idea, but it's not always.<br />
<br />
== Overlapping subnets ==<br />
<br />
<br />
Please don't keep adding assertions that overlapping subnets don't work, or that assumptions are being made that they are different. It does work, with a sufficiently small subnet for the FR (as the examples show). Adding comments about insisting that users change their LAN subnets is unnecessary, and makes it that much harder for users - where this page was originally.<br />
<br />
<br />
== Latest changes ==<br />
I found out that with my Kubuntu 8.10 without the «auto usb0» option in /etc/network/interfaces the USB networking wasn't able to work automatically.<br />
Adding that line makes everything work fine: plug-in the NEO, it gets recognized, give ssh openmoko and you're done. No problems with default networkmanager.<br />
So my question is: why do you think that option should not be there?</div>Dareushttp://openmoko.org/wiki/Talk:OrreryTalk:Orrery2008-12-20T10:00:33Z<p>Dareus: /* FSO stack */</p>
<hr />
<div>==Accelerometers==<br />
nice!<br />
I like it<br />
<br />
will it use the accelerometers to show the night sky 'behind' the phone? So you can pan the view by turning around or looking up?<br />
<br />
(KY): Really, to do this right, we'd need a compass sensor in the<br />
Freerunner, in addition to the accelerometers, I think. Otherwise,<br />
how do you set the azimuth? If the gta03 has a camera, and if it is able<br />
to detect stars, we might have some options then. For what it's<br />
worth, there is an Android application called skyMap that uses the<br />
G1 accelerometers and compass to do exactly what you are suggesting here.<br />
The implementation is terrible, though - the display is terribly jittery,<br />
due to poor filtering of the accelerometers, and the compass information<br />
apparently isn't corrected for magnetic declination, so it there is<br />
a ~20 degree error in the azimuth it chooses to display, as least<br />
where I live.<br />
<br />
==FSO stack==<br />
Has anyone successfully tested it with FSO?<br />
<br />
<br />
A: Yes, I have (with FSO and with SHR)<br />
it doesn't work because you do not have the /usr/lib/libpopt.so.0 file<br />
you can mail me, or Ken Young (the creator of this great app) and we will mail you the file<br />
<br />
a few days ago another problem appeared on my SHR; when i launch it on the phone (via desktop icon or via terminal) i get an error, but when i ssh in and do for example DISPLAY=:0 /usr/bin/orrery -d /usr/share/orrery/ it does work<br />
<br />
<br />
Ken Young said he intended to support Orrery on every distribution, so he will fix this.<br />
<br />
Bug report: Same problem here (libpopt already installed)<br />
<br />
(KY): I've ordered another Freerunner on which I will install SHR,<br />
and see if I can cure these problems. I'll also make it use<br />
Gypsy for GPS access, rather than gpsd (gpsd will still be used<br />
when running atop 200x.x distributions, of course). I would VERY<br />
MUCH appreciate it if people who have trouble getting this application<br />
to run would tell me about the problem at orrery.moko@gmail.com.<br />
<br />
<br />
<br />
I did a little test on SHR and that's waht came out:<br />
<pre><br />
root@om-gta02 ~ $ export DISPLAY=:0<br />
root@om-gta02 ~ $ gdb /usr/bin/orrery -d /usr/share/orrery/<br />
GNU gdb 6.8<br />
Copyright (C) 2008 Free Software Foundation, Inc.<br />
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html><br />
This is free software: you are free to change and redistribute it.<br />
There is NO WARRANTY, to the extent permitted by law. Type "show copying"<br />
and "show warranty" for details.<br />
This GDB was configured as "arm-angstrom-linux-gnueabi"...<br />
(gdb) run<br />
Starting program: /usr/bin/orrery<br />
config: No such file or directory<br />
Full file name was "/media/card/orrery/config"<br />
/media/card/orrery/starNames.dat: No such file or directory<br />
opening Hipparcos star catalog.: No such file or directory<br />
<br />
Program exited with code 0377.<br />
(gdb)<br />
</pre><br />
could it be related to the impossbility to run orrery on shr?<br />
<br />
[[User:Dareus]]</div>Dareus