http://openmoko.org/api.php?action=feedcontributions&user=Pnaulls&feedformat=atomOpenmoko - User contributions [en]2024-03-28T13:45:23ZUser contributionsMediaWiki 1.19.24http://openmoko.org/wiki/BluetoothBluetooth2010-02-09T20:05:47Z<p>Pnaulls: /* See also */</p>
<hr />
<div>[http://en.wikipedia.org/wiki/Bluetooth Bluetooth] is the wireless local connectivity standard supported by current Openmoko devices [[Neo FreeRunner]] and [[Neo1973]].<br />
<br />
== Applications ==<br />
<br />
See [[Manually using Bluetooth]], which also explains pand networking for setting up a tcp/ip over bluetooth.<br />
<br />
== Safe Bluetooth connection through shaking of two devices ==<br />
<br />
The [http://lists.openmoko.org/pipermail/announce/2007-June/000013.html accerelators] of the Neo should make it possible to realize the following idea:<br />
<br />
Take two Neos and shake them together => the synchronized shake establishes a safe Bluetooth connection between the two devices.<br />
<br />
http://eis.comp.lancs.ac.uk/fileadmin/eis/publication/2007-ShakeImp.pdf<br />
<br />
A demo video: http://www.youtube.com/watch?v=ktJC0S4_X58<br />
<br />
For further information take a look on:<br />
http://www.heise.de/newsticker/meldung/99142<br />
http://www.mayrhofer.eu.org/home<br />
<br />
<br />
== See also ==<br />
* [[GSM]] for remote wireless connectivity<br />
* [[USB]] for wired local connectivity<br />
* [[Software Bluetooth HID Keyboard]]<br />
* [[Openmoko Bluetooth remote controller]]<br />
<br />
[[Category:Bluetooth]]<br />
[[Category:Standard]]</div>Pnaullshttp://openmoko.org/wiki/Main_PageMain Page2010-02-03T17:43:19Z<p>Pnaulls: </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 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|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>Pnaullshttp://openmoko.org/wiki/Talk:More_informationsTalk:More informations2010-02-03T17:42:43Z<p>Pnaulls: Talk:More informations moved to Talk:More Information: "informations" is not a word.</p>
<hr />
<div>#REDIRECT [[Talk:More Information]]</div>Pnaullshttp://openmoko.org/wiki/Talk:More_InformationTalk:More Information2010-02-03T17:42:43Z<p>Pnaulls: Talk:More informations moved to Talk:More Information: "informations" is not a word.</p>
<hr />
<div>#REDIRECT [[Talk:Main Page]]</div>Pnaullshttp://openmoko.org/wiki/More_informationsMore informations2010-02-03T17:42:42Z<p>Pnaulls: More informations moved to More Information: "informations" is not a word.</p>
<hr />
<div>#REDIRECT [[More Information]]</div>Pnaullshttp://openmoko.org/wiki/More_InformationMore Information2010-02-03T17:42:42Z<p>Pnaulls: More informations moved to More Information: "informations" is not a word.</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 />
</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>Pnaullshttp://openmoko.org/wiki/Main_PageMain Page2010-02-03T17:42:08Z<p>Pnaulls: "Informations" is not a word</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 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|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>Pnaullshttp://openmoko.org/wiki/Talk:Community_Updates/2009-08-19Talk:Community Updates/2009-08-192009-08-07T18:30:10Z<p>Pnaulls: Please do basic spell check. Firefox underlines words for you in red. Also fix links - you don't need underlines.</p>
<hr />
<div>==Welcome==<br />
Here you can get a clue on how to contribute to Community updates, while conforming to wiki editing guidelines. You can take a look at [[Community Update Draft]], to have a feel how coming update draft would look like, if we follow all these standardised wiki guidelines. Feel free to discuss here about this topic, maybe we achieve consensus before next CU. Everybody is welcome to help. Following are main topics which should be covered.<br />
<br />
==Guidelines==<br />
Conform to [[Openmoko Wiki Editing Guidelines]]. These guidelines covers most of uncertain cases an editor might run into while editing wiki pages. It takes half an hour to dig through this, but is worth to do it at least summarily.<br />
<br />
==Editing==<br />
Conform to [[Help:Editing]]<br />
<br />
==Templates==<br />
Conform to [[Templates]]. Especially when it comes to handy Semantic boxes, like Template:ApplicationBox:<BR><br />
<pre><nowiki><br />
{{ApplicationBox|<br />
Name=[[Gpe-FileManager]]|<br />
Description=A file manager application with MIME types and remote access support from the the GPE Palmtop Environment (GPE) project.|<br />
Screenshot=Gpe-filemanager.png|<br />
Homepage=http://gpe.linuxtogo.org|<br />
TestedOn=Om2008.8|<br />
PackageName=gpe-filemanager<br />
}}<br />
</nowiki></pre><br />
If application/something else has its own wiki page, put its name in double square brackets:<br />
<br />
==Links==<br />
Keep in mind the difference between [http://meta.wikimedia.org/wiki/Help:Link#Interwiki_links internal] and [http://meta.wikimedia.org/wiki/Help:Link#External_links external] links. Try to use them properly, accordingly to their destination<br />
<br />
==Date format==<br />
Dates in article body text should all have the same format. Use one standarized date format. Current version of media wiki software is {{CURRENTVERSION}}. When it will be 1.15+ we can use unified date format, which would be represented accordingly to predefined user's preferences, while showing some default format for not registered users. (Is there any chance for upgrading this wiki version?) Here is nice example of [http://www.mediawiki.org/wiki/Help:Variables#Formatting date formatting]<br />
<br />
You might wonder which date format to choose? Many will say: 'use "DD, month YYYY" because it is easy to read for human'. But I say it is easy to read only for those humans born in UK or USA. For the rest of world, people's brain has to do additional task of translating english_month's_name into your local_month's_name. Another argument of mine is that there are plenty of countries where official date format is YYYY-MM-DD, MM-DD-YYYY or else. So, how to achieve consensus? Answer is simple: use international [http://en.wikipedia.org/wiki/ISO_8601 ISO_8601] standard. In short it says:<br />
<br />
''"The signature feature of ISO 8601 date and time representations is the ordering of date and time values from the most to the least significant or, in plain terms, from the largest (the year) to the smallest (the second)."''<br />
<br />
Thus, as a conclusion, official date format for Community updates should be '''YYYY-MM-DD'''. Additionally this is most natural format for sorting purposes.<br />
<br />
==Filling "Edit Summary" field==<br />
Many wiki editors do not fill in "Edit Summary" filed under "edit" box. This summary becomes very handy when it comes to later version comparison. Always fill in "edit summary" field when editing wiki pages. All you need to type there are 3~4 words of comment, and really makes life easier for wiki administrators.<br />
<br />
It's a good idea to set your user preferences (under Editing) to "Prompt me when entering a blank edit summary". If you really want to keep it empty, you can just confirm the message or enter a blank space to avoid the message.<br />
<br />
It is also quick and quite good habit to prefix summary with +/-/= depending upon you add/delete/edit content.<br />
<br />
==Creating new templates==<br />
Using Template:ApplicationBox is great idea! Why not create similar templates for other parts of CU? The disadvantage of this way would be little more code to fill, but all entries in particular part of CU would have similar layout. Following this idea [[Template:DistributionBox]] is currently being developed. You can see preview on [[Community Update Draft]] in Distribution section. <br />
* Currently there is voting ongoing on [mailto:community@lists.openmoko.org community] mailing list. Come on in and vote for your favourite template, or leave comment here!<br />
<br />
==Community Update releasing process==<br />
And last but not least...In fact it is pretty important: never copy/paste contents of CU to release the page! Instead always use "move" button on top of wiki page. This "button" is intended for this action and by using it you save all editions and contributions history.<br />
<br />
==Mailing list interface==<br />
Often there is a need to provide link pointing to discussion on a mailing list. Services providing web interface to mailing lists (like nabble.com) were [http://lists.openmoko.org/pipermail/community/2009-June/050363.html reported] many times to break discussion threads in mail clients. Remember, mailing lists were designed to be used with mail clients, not with web forums. If you need to provide link to discussion on mailing list for those who are not subscribed, use mailing list archives.<br />
* Go to http://lists.openmoko.org/<br />
* choose mailing: list http://lists.openmoko.org/mailman/listinfo/community<br />
* choose Archives: http://lists.openmoko.org/pipermail/community/<br />
* choose by: Thread/Subject/Author/Date<br />
* provide link to [http://lists.openmoko.org/pipermail/community/2009-July/051949.html post] that in your opinion should be provided in CU.</div>Pnaullshttp://openmoko.org/wiki/QtMokoQtMoko2009-07-31T17:19:16Z<p>Pnaulls: Formatting</p>
<hr />
<div>===QT Moko===<br />
QT Moko is Debian distribution for Openmoko Freerunner phone. Phone and user interface is based on [http://wiki.openmoko.org/wiki/Qt_Extended_Improved QT Extended Improved] formerly known as Qtopia. <br />
<br />
[http://activationrecord.net/radekp/qtmoko/ QT Moko]. Special feature are:<br />
* QT Moko has better X support, which is much faster than 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 />
===Download===<br />
Download the following files from [http://activationrecord.net/radekp/qtmoko/download/] to you desktop computer:<br />
* [http://activationrecord.net/radekp/qtmoko/download/qtmoko-debian-v5.jffs2 qtmoko-debian-v5.jffs2] or later versions <br />
* [http://activationrecord.net/radekp/qtmoko/download/uImage-v5.bin uImage-v5.bin] or later versions <br />
<br />
===Installation===<br />
If you flash the freerunner with a kernel image from QT Moko, then you must install the kernel and the root file system. If you have [[Qi]] installed then you can install the QT Moko 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 />
<br />
Switch off your freerunner and press 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>. Otherwise the freerunner will start to boot the installed operating system.<br />
If you want to flash the kernel image (you will need to be root on you PC) then you have to start the following command in the 30sec your see the BOOT MENU:<br />
<br />
# dfu-util -a kernel -R -D uImage-v5.bin<br />
<br />
and finally the root fs with this one:<br />
<br />
# dfu-util -a rootfs -R -D qtmoko-debian-v5.jffs2<br />
<br />
===First Boot===<br />
After finishing the installation without errors you have to start the freerunner and calibrate the touch screen. The you see the installed ''QT Moko'' on your device. <br />
[[Image:qtmokomain.png|200px|thumb|QT Moko after first boot]]<br />
<br />
===Login===<br />
If you want to login to your freerunner set up 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 />
<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 />
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 />
<br />
[[Category:Distributions]]</div>Pnaullshttp://openmoko.org/wiki/Neo_FreeRunner_Hardware_IssuesNeo FreeRunner Hardware Issues2009-07-30T17:06:12Z<p>Pnaulls: /* Poor Audio Quality (FIXED) */</p>
<hr />
<div>{{Neo FreeRunner Menu}}<br />
<br />
This is a community-written page that discusses '''hardware issues''' with the FreeRunner/[[GTA02]] device. Information here is unofficial (and possibly incorrect) unless otherwise stated. Corrections and clarifications from Openmoko employees would be greatly appreciated.<br />
<br />
Please '''DON'T PANIC''' when reading this page. Please give Openmoko employees time to investigate these issues and to develop a solution. Some of the items may turn out to be non-issues, or may have software workarounds. The FreeRunner's software is still under heavily development and can help fix most of this problems.<br />
<br />
Please always file a bug report on the issues and mention the bug report number in this page. Otherwise it is impossible to check if a bug has been fixed or not.<br />
<br />
=== Active Issues ===<br />
<br />
==== Poor Audio Quality (FIXED) ====<br />
<br />
Please use http://docs.openmoko.org/trac/attachment/ticket/2121/gsmhandset.state.new<br />
for *all* Neo Freerunner. (2009-04-27 jOERG)<br />
<br />
Issue: The person on the other end of a GSM phone call may experience poor audio quality, to the point where he/she cannot carry on a normal conversation.<br />
<br />
There are three related aspects to this issue:<br />
* Call is too quiet (mixer settings for mic and/or earpiece are set too low)<br />
* Caller hears a loud echo of their own voice [http://docs.openmoko.org/trac/ticket/1267 #1267]<br />
* Buzzing noise caused by GSM radio interference [http://docs.openmoko.org/trac/ticket/883 #883] [http://docs.openmoko.org/trac/ticket/1352 #1352]<br />
<br />
<br />
Affects: all devices but only some users (depending on many factors)<br />
<br />
The source of the GSM buzz has been [http://lists.openmoko.org/pipermail/hardware/2008-August/000415.html identified]. It's a mere hw-issue, depending on the way you hold the device, and the local situation created by network settings made by the GSM-provider (mainly 1800/1900 seems to be affected), as well as your position relative to basestation. There is no way to fix GSM buzz by mixer-setting modifications. So all suggested settings here may improve a little the volume of buzz during you're *not* speaking only, while relative ratio of buzz/voice level while speaking can't be changed by mixer settings.<br />
<br />
Some [http://lists.openmoko.org/pipermail/hardware/2008-August/000451.html hidden Calypso commands] may help with the echo problem.<br />
<br />
hexedit, ghex /opt/Qtopia/plugins/phonevendors/libficgta01vendor.so<br />
search "AT%N0125" and change to "AT%N0187"<br />
<br />
Workarounds:<br />
<br />
# Using a bluetooth headset is a possibility.<br />
# Using external GSM-antenna will stop buzz.<br />
<br />
<br />
Due to the multiple factors influencing the result of a single test, it's nearly impossible to find a setup that lets you compare for a decent "before / after" result. If you ever took an old analog TV portable to a place where you had to fiddle around with the antenna to try and make the snow and shadows vanish off the picture, you might have gotten a slight idea of what it's like to reproduce the same situation for decent tests. So probably most of the suggested alsa-improvements are mere random results. Even if they worked for provider A evidently, this doesn't mean there's any improvement by using same settings for provider B.<br />
<br />
This being said, here they are:<br />
<br />
# Better mixer settings: One confirmed good settings are here: http://www.mail-archive.com/support@lists.openmoko.org/msg00564.html. Please change accordingly in /usr/share/openmoko/scenarios/gsmhandset.state. Should eliminate/lessen echo and buzz problems. [[Neo alsamixer]] is the main article for setting the mixer settings.<br />
<br />
===== Better set of mixer settings =====<br />
<br />
Regarding 2. in the previous paragraph, here are my further tweaked settings:<br />
<br />
[mic volume & buzz problem]<br />
* 'Mono Playback Volume' (95)<br />
* 'Mono Sidetone Playback Volume' (2)<br />
* 'Mic2 Capture Volume' (3)<br />
[speaker volume & echo problem]<br />
* 'Speaker Playback Volume' (112)<br />
* 'Bypass Playback Volume' (5)<br />
<br />
Lowering Mono Sidetone eliminated the buzz problem better. Please try out and report if you have good success... --[[User:TimoJyrinki|TimoJyrinki]] 08:19, 16 October 2008 (UTC)<br />
<br />
==== Can't boot with discharged or missing battery (FIXED) ====<br />
<br />
Issue: Neo FreeRunner requires battery power to boot, because Neo FreeRunner consumes too much current while booting to boot with only a charger. Since charging isn't enabled until the Neo FreeRunner has booted, this means that a discharged battery can not be charged. Some versions of uBoot don't continue booting and just charge bat (red LED flashes constantly) when probing bat voltage shows it's too weak to start FR. Let the device sit and charge for an hour, then reboot.<br />
<br />
Affects: All A5, older A6. With change of Vsys buffer capacitor to 100uF this issue has been fixed for good.<br />
<br />
Fixed(?) with [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003799.html Werner Almesberger patches] - [http://lists.openmoko.org/pipermail/commitlog/2008-July/005403.html more here] [http://lists.openmoko.org/pipermail/community/2008-July/023392.html additional information]<br />
<br />
I think this patch finally fixes the problem:<br />
[http://www.abanet.ch/~hug/moko/uboot-battery/ Philipp Hugs patches]<br />
<br />
Workarounds:<br />
<br />
#First test if your FR starts with no bat inserted. If it does you can forget about this whole topic.<br />
# Make sure that the battery never discharges completely<br />
# Use [[:Image:Nokia-charging-stand.jpg|external stand-alone charger]] (compatible with the Nokia BL-5C battery)<br />
# Boot the FreeRunner with an [[Neo_FreeRunner_Battery#Compatible_Replacement_Batteries|alternative battery]], or with a spare GTA01 or GTA02 battery, plug USB power, then switch to the empty battery.<br />
# Boot the FreeRunner with a 4.5VDC external power source (steady hand and great care involved), plug USB power, then insert the empty battery.<br />
## Oscilloscope digital clip probes fit perfectly on the Freerunner's battery connectors. Make sure polarity is correct!<br />
# Some users have reported that Neo FreeRunner '''is''' able to boot on USB power alone using the NOR u-boot, thus: press AUX, plug USB power, select boot. Reports of success would be appreciated.<br />
## Does work with sequence described. If after pressing boot it just turns off again (happened a few times), then: press AUX, plug in USB power, cycle through the menu a few times to keep it from turning off without booting, after a minute or so press boot. [[User:Imrehg|Imrehg]] 08:34, 10 September 2008 (UTC)<br />
## This does indeed work with sequence described. After pressing boot, the screen went blank for a few seconds, but then the beast came to life again. That saved the day! [[User:Edictor|Edictor]]<br />
## Trifirmed. Neither USB connection nor wall charger was able to wake my phone. But in NOR u-boot it worked (connected to the computer). I think this trick hasn't failed to anyone. --[[User:Flamma|Flamma]] 12:11, 17 September 2008 (UTC)<br />
## Unfortunately this is not working for me. My FreeRunner has been off for a few weeks and completely dead. I tried various combinations of holding aux and plugging in to both wall and computer, no luck. Tried with and without the battery in place, no luck. Aux and power button / just power / aux then power. No luck... --[[User:Safire|Safire]] 6 November 2008<br />
## This is working ! It has prevent me from buying an external power charger. My freerunner had its battery discharged for about 2 weeks now, and I was able to boot and charge it. --[[User:JRD|JRD]] 23:37, 12 November 2008 (UTC)<br />
## It has worked for me ! I have booted to 2008.9 Om with discharged battery (after connecting the FR to power supply and waiting a few minutes until AUX button red light stopped flashing) using the NOR boot menu. Tried the same with NAND boot menu and worked also !!! Then I could charge the battery. -- [[User:Emsyr|Emsyr]] 3:23, 20 November 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection = plug USB power (FR <-> PC) + press power button. However I cannot shutdown correctly. --[[User:Cynan|Cynan]] 13:43, 9 December 2008 (UTC)<br />
## I can boot to 2008.9 without battery and with USB connection: press AUX button, then plug USB power, then press power button (keeping AUX pressed). NOTE that battery was fully charged. The problem wasn't battery but corrupted environment in NAND u-boot: with battery IN, no access to NOR u-boot<br />
## Both my friend's freerunner and mine was completely discharged. This trick failed. Finally booted the freerunner with a BL-5C battery from an old nokia n-gage. With the power connected I then switched the batteries. --[[User:Unlotto|Unlotto]] 14:27, 25 January 2009 (UTC)<br />
## Another confirmation that this works. You may use the computer-USB cable or the AC adapter. I held AUX, plugged in the USB, and the NOR boot menu started before I even hit the Power button. For some reason, I have to cycle through the menu once before I choose boot, otherwise it will power off as soon as it loads the kernel. I booted it, let it start up fully, and it continued charging. After a minute or two, as a test I shut down and tried rebooting normally. There was enough power in the battery at that point to boot normally from the AC adapter. Note, I did not encounter this problem (using the AC adapter) until after I "upgraded" from the pre-installed May 2008 u-boot to the December 2008 u-boot; perhaps that is relevant. --Robolange 05:53, 1 February 2008 (UTC)<br />
## This did ''not'' work for me (with the 1.3.2-moko12 u-boot). However, I was able to "jumpstart" my Freerunner with a bench supply and some micro-clips, as suggested above. (Worried I would fry something, I tried at lower voltages first, but it didn't start up until I set the supply to 4.5v, with the OM USB charger also attached.) Once it was well into the Linux kernel boot sequence I removed the clips and put in the battery to charge. --[[User:Wiml|Wiml]] 05:30, 9 April 2009 (UTC)<br />
See also:<br />
:[[Neo_FreeRunner_Battery|Neo FreeRunner Battery]]<br />
<br />
==== Battery discharges when charging completes ====<br />
<br />
Issue: If the Neo FreeRunner has been charging, when charging completes, it seems to drain the battery and not turn on charging again. This seems to be bug of PMU-registers setup, that shows up when PMU has to handle bat autonomously (=suspend). There might be issues our current scheme relies on wake-interrupt at bat-full which doesn't succeed, or something like that.<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
This has been fixed in linux. See<br />
http://docs.openmoko.org/trac/ticket/1158<br />
<br />
==== Suspend/resume corrupts SD card's partition table ====<br />
<br />
Issue: Suspend/resume corrupts the partition table of the SD card<br />
<br />
Affects: Unknown.<br />
<br />
Status:<br />
<br />
[[https://docs.openmoko.org/trac/ticket/1802#comment:6 Patched kernel]] might solve the problem<br />
<br />
Workarounds:<br />
<br />
# [[https://docs.openmoko.org/trac/ticket/1802#comment:5 Script]] as a temporary workaround<br />
<br />
See also:<br />
<br />
:[[https://docs.openmoko.org/trac/ticket/1802 trac ticket]]<br />
<br />
==== Some SIMs Don't Work ====<br />
<br />
Issue: There are reports that some users cannot register with their GSM network when using certain SIM cards. See for example http://lists.openmoko.org/pipermail/community/2008-July/020370.html<br />
<br />
It is possible that there is more than one issue involved here. The observed problems ''might'' (i.e. some items are only speculation at this point) be caused by:<br />
<br />
* User error, not inserting the SIM in the correct orientation or not sliding the holder to the 'locked' position<br />
<br />
* Software issues that result in a locked SIM (not properly prompting the user for a PIN and then passing this to the SIM)<br />
<br />
* Mechanical issues with the SIM holder that prevent the pins from making reliable contact with the pads on the SIM. Note that only 6 of the 8 pins are used, and the remaining two are not connected.<br />
<br />
* Electrical incompatibility (some tests show problems with 1.8V SIMs while 2.9V ones work OK)<br />
<br />
* Firmware bugs in the TI Calypso GSM chipset. Note that one issue in this category was found and fixed on the GTA01 devices (#666 in Trac), and that specific problem should not affect the FreeRunner.<br />
<br />
* Defective SIMs, i.e. ones that do not comply with the applicable standards and are acknowledged as being defective by the carrier (even if they happen to work in some phones).<br />
<br />
* You may have true 3G operating at 2100 and your sim doesn't fallback to GSM. The Phone works on 850/1800/1900 or 900/1800/1900.<br />
<br />
See also:<br />
* http://wiki.openmoko.org/wiki/Carriers/ATT<br />
* http://wiki.openmoko.org/wiki/Carriers/Rogers<br />
<br />
Affects: Only a subset of users (details unknown).<br />
<br />
Status: Fixed in GSM firmware moko10-beta2 or later. See [[GSM/Flashing]] for instructions. Please add your information to [[FreeRunner_unable_to_work_with_3G_SIM_cards]] or [[GSM network registration]]<br />
<br />
Workarounds:<br />
<br />
# Please document your existing SIM card and provider in the table [[FreeRunner_unable_to_work_with_3G_SIM_cards|here]].<br />
# If the table mentioned above shows any SIM cards known to work with your provider, make note of these numbers.<br />
# Contact your network provider and request a new SIM card. You may wish to print out the table mentioned above and bring it with you to the store.<br />
# Add your experience with the new SIM card to the table mentioned above.<br />
<br />
=== Known/Accepted Issues ===<br />
<br />
This section lists items that are acknowledged as being less than ideal, but are considered to be acceptable in the shipping product. They will not be discussed in detail on this page.<br />
<br />
* Poor performance + slow bus speed of the Glamo GPU - discussed to death on the mailing lists and IRC.<br />
** stable-2.6.26 branch of kernel has wait states lowered, core speed increased from 50MHz to 80MHz and memory speed from 80MHz to 90MHz (the latter is also in stable branch) - these lessen the problem a bit, though it's slow still<br />
* [http://lists.openmoko.org/pipermail/hardware/2008-April/000055.html GPS antenna switch] driven out-of-spec - does not appear to have a significant effect on device performance<br />
* Poor low-frequency audio response with low-impedance headphones, e.g. as discussed in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2008-March/001999.html (NOTE - this thread refers to pre-mass-production devices)<br />
** Can be fixed to an semi-acceptable level (if not high fidelity most probably) by adjusting "Bass Volume" to full (15) and "Bass Filter" to "100Hz @ 8kHz" (bass will be boosted <= 600Hz when playing back at 48kHz) or "200Hz @ 8kHz" (<= 1200Hz @ 48kHz). The default is 130Hz @ 48kHz and does not help much with the more wider scope of low frequencies.<br />
** Ideally someone would record output and find out which setting produces best output, ie. compensating for the loss of low frequencies without boosting too high frequencies with this "bass" boost.<br />
<br />
Actually with 16 Ohm headphones the cutoff frequency is more than 2kHz, so even 1200Hz @ 48kHz seems to be not appropriate.<br />
If you have 30 Ohm, it might be just correct setting.<br />
<br />
=== Resolved Issues ===<br />
<br />
These are issues that have been discussed in the past, but have been fixed (or turned out not to be a problem) for the mass-produced devices.<br />
<br />
* Excessive LED current - Some early units lacked a current-limiting resistor for the LEDs. This has been fixed for the production units.<br />
* Battery life - At this time it appears that the FreeRunner battery life will be acceptable once suspend/resume support has been implemented in software.<br />
* slow GPS TTFF - see [[GPS Problems]]<br />
==== Empty NOR Flash ====<br />
<br />
Issue: NOR flash (backup copy of u-boot) is not programmed. [http://docs.openmoko.org/trac/ticket/1568 #1568]<br />
<br />
Affects: Unknown - maybe only 1 or 2 devices? Also need to confirm that the bug report was from a mass-production unit rather than an earlier prototype.<br />
<br />
Status: Solved. The new devices are tested better if they have the NOR flashed programmed and aren't shipped if the test fail.<br />
<br />
Workarounds: Use the NAND copy of u-boot and be careful not to brick the device unless a debug-board is available.<br />
<br />
<br />
==== Debug board has wrong vendor/product ID ====<br />
<br />
Issue: A debug board is not reporting the expected USB Vendor/Product ID.<br />
<br />
Affects: Only [http://lists.openmoko.org/pipermail/device-owners/2008-July/001775.html one report] has been seen so far.<br />
<br />
Status: Probably a single case scenario.<br />
<br />
Workarounds: Edit configuration files (e.g. openocd.conf) to use the IDs that the board is reporting.<br />
<br />
== List of "Current issues" Imported from the "Community update page" ==<br />
(to be sorted)<br />
<br />
The information below has been collected from various sources, feel free to add questions and comments here.<br />
<br />
===GPS Performance of the FreeRunner===<br />
The poor GPS performance on the FreeRunner has been traced to an<br />
interaction between the microSD card and the GPS unit. A software<br />
and a hardware fixes are available, see [[GPS Problems]].<br />
<br />
===GTA02 battery status===<br />
While writing a device driver for the new battery which provides an accurate counter of the charge state of the [[GTA02]], the driver developer discovered that the device driver does not get a reading of the charge state due to a very long response time with only one I/O signal when trying to read the charge state. To be able to read the battery status properly, it has been written that it will be necessary to re-design that part of the GTA02 for hardware version GTA02A5 to use two I/O signals to reduce the response time (one for transmitting commands, one for receiving data?). This was fixed two months ago (see [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=957#c1 Bug 957]).<br />
<br />
<br />
<br />
=== SMedia 3362 Documentation & OpenGL ES Drivers ===<br />
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and Openmoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).<br />
<br />
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation Openmoko developers will be writing themselves, not the technical documentation SMedia have provided Openmoko with. The Openmoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)<br />
<br />
<br />
<br />
=== Draws too much current from USB ===<br />
It may be that the Neo draws too much current from your USB host/hub, and that the USB host/hub switches off to prevent damages. <br />
<br />
The behaviour is controlled by a complex interaction between soft- and hardware, see [[Forcing fast charge mode]] and [[USB host]]. It may be that the host negotiates more power than the Hub is willing to provide. In case of problems, try to limit the current to e.g. 400mA.<br />
<br />
<br />
[[Category:Neo FreeRunner Hardware]]</div>Pnaullshttp://openmoko.org/wiki/GPS_ProblemsGPS Problems2009-07-30T15:21:54Z<p>Pnaulls: /* Solutions */</p>
<hr />
<div>See GPS for details on how to evaluate the [[Neo FreeRunner GPS]] with command line utilities.<br />
<br />
=== Problem: it takes a long time (10min+) before the FreeRunner gets first GPS data ===<br />
<br />
It was found that the Openmoko FreeRunner GPS has a long Time To First Fix (TTFF) when there is an SD card in the phone. [http://lists.openmoko.org/pipermail/community/2008-July/021774.html This thread] indicates that there is interference from the SD card slot: TTFF is much shorter without an inserted SD card.<br />
<br />
::More specific: the GPS signal level drops by 20dB, i.e. a factor of 100. Signal strength of a GPS satellite above your head is around -127dBm. Needed strength for a first fix is -145dBm with a minimum of three satellites. Once the GPS chip has a fix, it can operate at signal levels of -157dBm, thus making it possible to operate while there is data transfer from/to the SD card.<br />
::''(From http://lists.openmoko.org/pipermail/community/2008-July/022202.html )''<br />
<br />
=== Solutions ===<br />
<br />
{{Note|It seems that in the newer version of the hardware, a compensating capacitor is now present. So this problem should be fixed with newer devices. First noticed on 20080724 and confirmed on 20080830. You can check if it has the fix by looking for the capacitor beneath the SD card, as shown in [[Media:Gta02 gps 10pf rework sop.pdf|this PDF file]].}}<br />
<br />
A [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003777.html software workaround] has been released as a kernel patch and may be acquired simply by doing an "opkg update" and "opkg upgrade" and then rebooting your FreeRunner. This workaround effectively turns off the SD card clock when the SD card is not being used. You can then use the SD card simultaneously with GPS, except for the first approximately 30 seconds.<br />
<br />
Openmoko is soliciting the assistance of the community to test the effectiveness of this software fix. The experiment consists of a series of measurements in different conditions, prior to applying the software fix and then after applying the software fix. Please visit [[FreeRunner GPS Software Fix TTFF Measurement Test]] for instructions to participate and to see the results so far of this test.<br />
<br />
Openmoko has examined a hardware solution: soldering a 10 pf capacitor between SD card pin 5 (clk) and pin 6 (Vss) [[Image:Gta02 gps 10pf rework sop.pdf]] and more detailed [[Image:SOP_for_GPS_capacitor_rework.pdf|GPS issue SD clcok pin capacitor rework guide]]. This effectively restores GPS performance to the levels obtained without the SD card inside. The rework is not suggested to end users without hardware soldering technique and equipment. This rework is done on all the new fabricated Neo FreeRunners<br />
<br />
==== Hardware mod related ====<br />
<br />
See: <br />
* [[Shop:Speedevil|Speedevil's Shop]] for a UK service to perform this operation on your freerunner, or globally shipped 10pF capacitor. <br />
<br />
* [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=490-1278-1-ND Digikey] for the capacitor.<br />
<br />
=== Discussion ===<br />
<br />
The following is based on [http://lists.openmoko.org/pipermail/community/2008-July/022180.html Alasal's post] to the community mailing list. <br />
<br />
;What is TTFF?<br />
:TTFF means Time To First Fix of the GPS. This is the time the GPS needs to get the first clue on where you are on planet earth. So you have to do this only once. After you have a FF (first fix), you can get more fixes without any problems with the SD card in the phone.<br />
<br />
<br />
;So if we have a first fix, the SD card doesn't block the GPS anymore?<br />
:Yes, the SD card doesn't block the GPS if we have a first fix. (Some people even claim it's more stable)<br />
<br />
<br />
;Why do we need a first fix?<br />
: According to [http://lists.openmoko.org/pipermail/community/2008-July/020705.html Al Johnson], the Antares4 chip on the GTA02 doesn't have the memory needed to store almanac and ephemeris, last known position or time. This means that every start is a true cold start. It [http://lists.openmoko.org/pipermail/community/2008-July/020772.html is possible] to save location, almanac and ephemeris at GPS shut down, and restore these information at the next startup, but that does not seem implemented yet.<br />
<br />
<br />
;Does the lower signal also affect accuracy?<br />
:It is a good deal more jittery. However, if you drive around in a city you will get a lot more error from signal reflections than from the jitter.<br />
:''(From http://lists.openmoko.org/pipermail/community/2008-July/022209.html )''<br />
<br />
<br />
;Do they have a solution?<br />
:Yes. There is already a highly alpha software workaround. The software just turns off the SD card clock when the SD card is not being used. They are also examining a hardware solution.<br />
::The software fix is still in testing. Expect first results this noon (''Thursday, 17th July 2008'') (Taipeh time).<br />
::Also, the hardware fix needed is rather easy. No need to open the shielding or housing. We are working on a document which gives you detailed instructions.<br />
::''(From http://lists.openmoko.org/pipermail/community/2008-July/022242.html )''<br />
<br />
<br />
;Do we have to return our FreeRunners to Openmoko?<br />
:Probably not, because the software workaround should work too.<br />
<br />
;But we can't read from the SD card when the GPS is on?<br />
:Wrong, you will be able to read the SD card when the GPS is on. The clock for the SD card used to run constantly. Now the kernel turns it off when the SD card is not in use. As long as you are not constantly reading from the SD card, you should see much better first fix times. Obtaining a GPS fix does not affect SD performance.<br />
<br />
;Did Openmoko test the GPS with a SD card in it?<br />
:Yes.<br />
<br />
;Why didn't they find it while testing the FreeRunner?<br />
:Because they have to do the tests with a fake GPS signal and with that signal it worked (In a fab you don't have a decent GPS signal). They have already modified the test, so it corresponds to the GPS signal better.<br />
<br />
== Information about faulty antennas ==<br />
<br />
* If removing the SD card doesn't help and you suspect your antenna, try unplugging and replugging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this also applies to the Freerunner, since it's the same case)<br />
<br />
* Also note that there is a trac ticket for this issue: [http://docs.openmoko.org/trac/ticket/1542 #1542]<br />
<br />
* [[FreeRunner GPS antenna repair SOP]] indicates that some (rare?) units may have bad soldering, and includes a guide to fix. This will presumably void your warranty.<br />
<br />
[[Category:Neo FreeRunner solved GPS problems]]</div>Pnaullshttp://openmoko.org/wiki/GPS_ProblemsGPS Problems2009-07-30T15:21:34Z<p>Pnaulls: /* Information about faulty antennas */</p>
<hr />
<div>See GPS for details on how to evaluate the [[Neo FreeRunner GPS]] with command line utilities.<br />
<br />
=== Problem: it takes a long time (10min+) before the FreeRunner gets first GPS data ===<br />
<br />
It was found that the Openmoko FreeRunner GPS has a long Time To First Fix (TTFF) when there is an SD card in the phone. [http://lists.openmoko.org/pipermail/community/2008-July/021774.html This thread] indicates that there is interference from the SD card slot: TTFF is much shorter without an inserted SD card.<br />
<br />
::More specific: the GPS signal level drops by 20dB, i.e. a factor of 100. Signal strength of a GPS satellite above your head is around -127dBm. Needed strength for a first fix is -145dBm with a minimum of three satellites. Once the GPS chip has a fix, it can operate at signal levels of -157dBm, thus making it possible to operate while there is data transfer from/to the SD card.<br />
::''(From http://lists.openmoko.org/pipermail/community/2008-July/022202.html )''<br />
<br />
=== Solutions ===<br />
<br />
{{Note|It seems that in the newer version of the hardware, a compensating capacitor is now present. So this problem should be fixed with newer devices. First noticed on 20080724 and confirmed on 20080830. You can check if it has the fix by looking for the capacitor beneath the SD card, as shown in [[Media:Gta02 gps 10pf rework sop.pdf|this PDF file]].}}<br />
<br />
A [http://lists.openmoko.org/pipermail/openmoko-kernel/2008-July/003777.html software workaround] has been released as a kernel patch and may be acquired simply by doing an "opkg update" and "opkg upgrade" and then rebooting your FreeRunner. This workaround effectively turns off the SD card clock when the SD card is not being used. You can then use the SD card simultaneously with GPS, except for the first approximately 30 seconds.<br />
<br />
Openmoko is soliciting the assistance of the community to test the effectiveness of this software fix. The experiment consists of a series of measurements in different conditions, prior to applying the software fix and then after applying the software fix. Please visit [[FreeRunner GPS Software Fix TTFF Measurement Test]] for instructions to participate and to see the results so far of this test.<br />
<br />
Openmoko has examined a hardware solution: soldering a 10 pf capacitor between SD card pin 5 (clk) and pin 6 (Vss) [[Image:Gta02 gps 10pf rework sop.pdf]] and more detailed [[Image:SOP_for_GPS_capacitor_rework.pdf|GPS issue SD clcok pin capacitor rework guide]]. This effectively restores GPS performance to the levels obtained without the SD card inside. The rework is not suggested to end users without hardware soldering technique and equipment. This rework is done on all the new fabricated Neo FreeRunners<br />
<br />
Openmoko <br />
<br />
<br />
<br />
==== Hardware mod related ====<br />
<br />
See: <br />
* [[Shop:Speedevil|Speedevil's Shop]] for a UK service to perform this operation on your freerunner, or globally shipped 10pF capacitor. <br />
<br />
* [http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail?name=490-1278-1-ND Digikey] for the capacitor.<br />
<br />
=== Discussion ===<br />
<br />
The following is based on [http://lists.openmoko.org/pipermail/community/2008-July/022180.html Alasal's post] to the community mailing list. <br />
<br />
;What is TTFF?<br />
:TTFF means Time To First Fix of the GPS. This is the time the GPS needs to get the first clue on where you are on planet earth. So you have to do this only once. After you have a FF (first fix), you can get more fixes without any problems with the SD card in the phone.<br />
<br />
<br />
;So if we have a first fix, the SD card doesn't block the GPS anymore?<br />
:Yes, the SD card doesn't block the GPS if we have a first fix. (Some people even claim it's more stable)<br />
<br />
<br />
;Why do we need a first fix?<br />
: According to [http://lists.openmoko.org/pipermail/community/2008-July/020705.html Al Johnson], the Antares4 chip on the GTA02 doesn't have the memory needed to store almanac and ephemeris, last known position or time. This means that every start is a true cold start. It [http://lists.openmoko.org/pipermail/community/2008-July/020772.html is possible] to save location, almanac and ephemeris at GPS shut down, and restore these information at the next startup, but that does not seem implemented yet.<br />
<br />
<br />
;Does the lower signal also affect accuracy?<br />
:It is a good deal more jittery. However, if you drive around in a city you will get a lot more error from signal reflections than from the jitter.<br />
:''(From http://lists.openmoko.org/pipermail/community/2008-July/022209.html )''<br />
<br />
<br />
;Do they have a solution?<br />
:Yes. There is already a highly alpha software workaround. The software just turns off the SD card clock when the SD card is not being used. They are also examining a hardware solution.<br />
::The software fix is still in testing. Expect first results this noon (''Thursday, 17th July 2008'') (Taipeh time).<br />
::Also, the hardware fix needed is rather easy. No need to open the shielding or housing. We are working on a document which gives you detailed instructions.<br />
::''(From http://lists.openmoko.org/pipermail/community/2008-July/022242.html )''<br />
<br />
<br />
;Do we have to return our FreeRunners to Openmoko?<br />
:Probably not, because the software workaround should work too.<br />
<br />
;But we can't read from the SD card when the GPS is on?<br />
:Wrong, you will be able to read the SD card when the GPS is on. The clock for the SD card used to run constantly. Now the kernel turns it off when the SD card is not in use. As long as you are not constantly reading from the SD card, you should see much better first fix times. Obtaining a GPS fix does not affect SD performance.<br />
<br />
;Did Openmoko test the GPS with a SD card in it?<br />
:Yes.<br />
<br />
;Why didn't they find it while testing the FreeRunner?<br />
:Because they have to do the tests with a fake GPS signal and with that signal it worked (In a fab you don't have a decent GPS signal). They have already modified the test, so it corresponds to the GPS signal better.<br />
<br />
== Information about faulty antennas ==<br />
<br />
* If removing the SD card doesn't help and you suspect your antenna, try unplugging and replugging the internal GPS connector. (See [[Disassembling_Neo1973]] about 2/3 of the way down. (this also applies to the Freerunner, since it's the same case)<br />
<br />
* Also note that there is a trac ticket for this issue: [http://docs.openmoko.org/trac/ticket/1542 #1542]<br />
<br />
* [[FreeRunner GPS antenna repair SOP]] indicates that some (rare?) units may have bad soldering, and includes a guide to fix. This will presumably void your warranty.<br />
<br />
[[Category:Neo FreeRunner solved GPS problems]]</div>Pnaullshttp://openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunnerGetting Started with your Neo FreeRunner2009-07-30T15:17:57Z<p>Pnaulls: /* Annotated references */</p>
<hr />
<div>{{Languages|Getting Started with your Neo FreeRunner}}<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc; width:75% " |<br />
<p align="left"><br />
Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of Openmoko. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.</p><br />
<br />
<p align="left"><br />
Some Frequently Asked Questions for new owners are featured in the [[FAQ#Getting_Started_with_your_Neo_FreeRunner|FAQ]].<br />
</p><br />
<br />
! style="background:#fcfcfc; width:25% " |<br />
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]<br />
|}<br />
{{Neo FreeRunner Menu}}<br />
<br />
== Package Contents ==<br />
<br />
[[Image:Openmokset.jpg|left|400px|thumb|Inside the package]]<br />
<br /><br />
: [[Image:Circle2.gif|10px]] Neo FreeRunner<br />
: [[Image:Circle2.gif|10px]] Stylus<br />
: [[Image:Circle2.gif|10px]] Battery<br />
: [[Image:Circle2.gif|10px]] Charger<br />
: [[Image:Circle2.gif|10px]] USB Cable (A -> Mini-B 5-pole)<br />
: [[Image:Circle2.gif|10px]] [[Thank You green card]]<br />
<div style="clear: both">&nbsp;</div><br />
<br />
{{Note|<br />
== Get the source code == <br />
The software included in this product contains copyrighted software that is licensed under the [http://downloads.openmoko.org/sources/Om2008.9-Lite.iso GPL]. A complete corresponding source code or CD-ROM ISO image with the GPL license is available for download [http://downloads.openmoko.org/sources/Om2008.9-Lite.iso here]. You may also obtain the same corresponding CD-ROM by sending a money order or check for $10 to any one of our [http://downloads.openmoko.org/sources/Om2008.9-Lite.iso distributors].<br />
<br />
Please write “source for Neo FreeRunner ” in the memo line of your payment.<br />
}}<br />
<br />
== Setting up the hardware, getting to know the Neo FreeRunner physically ==<br />
<br />
<br />
<br />
===Installing the Micro-SD card, the SIM card, and the Battery ===<br />
<br />
[[Image:Circle2.gif|10px]] Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use a credit card (or your fingernail, if you have strong fingernails) to prise off the rear cover at the slot on top of the device.<br />
<br />
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|Open the case like this.|center]]</td><br />
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Opening !|center]]</td><br />
</tr><br />
</table><br />
<br />
<br />
[[Image:Circle2.gif|10px]] Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.<br />
<br />
[[Image:Circle2.gif|10px]] Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.<br />
<br />
<br />
[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here.|center]]<br />
<br />
[[Image:Circle2.gif|10px]] Lift up on the SIM card holder.<br />
<br />
[[Image:Circle2.gif|10px]] The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this, though it's strongly deprecated. Refer to [http://people.openmoko.org/joerg/sdcard-handle/ this photo footage] for a simple yet handy little hack involving some scotchtape, to make your life easier.<br />
<br />
[[Image:Circle2.gif|10px]] Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo FreeRunner.<br />
<br />
[[Image:Circle2.gif|10px]] Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.<br />
<br />
[[Image:Circle2.gif|10px]] Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.<br />
<br />
[[Image:Circle2.gif|10px]] Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.<br />
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;"><br />
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]</td><br />
<td style="padding: 1px 1em 0; background: #ffffff;"><br />
[[Image:Engchang.jpg|392px|thumb|Some models look like this, the little blob is not a defect|center]]</td><br />
</tr><br />
</table><br />
<br />
[[Image:Circle2.gif|10px]] Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.<br />
<br />
[[Image:Circle2.gif|10px]] Replace the rear cover on the FreeRunner.<br />
<br />
<br />
<br />
{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"<br />
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font><br />
|-<br />
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |<br />
<div align=left><br />
[http://video.google.de/videoplay?docid=-8343770443102960945 A short video] is also available. It was shot using the previous version of the Neo, but the installation procedure remains the same.<br />
</div><br />
<br />
|}<br />
<br />
===Charging the Neo FreeRunner===<br />
<br />
Before using the Neo FreeRunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger at 1000mA or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.<br />
<br />
Neo FreeRunner '''does NOT charge when powered off''', so be sure to turn it on and allow it to boot all the way to the GUI (Graphical User Interface). This should happen automatically when you plug in USB power, either from a computer or the provided charger. If it does not, you can turn the power on manually by pressing and holding the power button, which is located just below the USB jack.<br />
<br />
Although the provided charger is rated at 2A, the maximum charge rate of the Neo FreeRunner is 1A, and thus the charge rate with the charger is less than the charger capacity.<br />
<br />
The provided charger includes three "national" plugs. The default is North America, with alternative U.K (3 square pins) and Euro (two round pins) adapters. To install the alternative power adapters, depress the latch in the cover (on the opposite side of the charger from the product information label) and slide the cover outward. Note that the two North American pins do not come out; the other adapters slide over them, and snap into place. The two-pin Euro adapter is removed in the same way as the cover. The three-pin U.K. adapter is removed by '''gently''' pressing the dummy ground pin (black) '''toward the end of the adapter with the cord''' and then sliding it off the adapter.<br />
<br />
Charging an empty battery at 100mA takes 12~15 hours *), at 500mA (PC) takes 2~3 hours, and at 1000mA (wallcharger) takes 1.5~3hours. (90%~100%) <br>*) charging with 100mA will occur only if device is suspended, as otherwise system takes more power than the 100mA provided by USB power source, and your battery never reaches full capacity or even drains slowly.<br />
<br />
{{Note|See [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware Issues]] about not allowing the battery to discharge completely.}}<br />
<br />
===Buttons and connectors===<br />
<br />
<table width="80%" style="clear: both; border-collapse: collapse" valign="top"><br />
<tr><br />
<td style="width: 25px">&nbsp;</td><br />
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Power Button, USB and external GPS Antenna (left to right)|center]]</td><br />
<td style="width: 25px">&nbsp;</td><br />
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Button and headset jack (left to right)|center]]</td><br />
</tr><br />
<tr><br />
<td></td><br />
<td>'''Power'''<br />
Tapping the power button suspends the GTA02.<br />
<br />
Holding the power button shutsdown the device.</td><br />
<td></td><br />
<td>'''Aux'''<br />
Tapping or holding the Aux button locks the screen.<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
'''Booting'''<br />
<br />
[[Booting the Neo FreeRunner]] takes about 2 minutes overall, so patience is in order. The longest step comes after the Linux boot messages in very small fonts have scrolled by, at the graphical "openmoko" sunrise page.<br />
<br />
'''Phone Jack'''<br />
<br />
The phone jack is a 2.5mm connector with four contacts: stereo + MIC. It is compatible with the headsets used by Motorola smartphones (A780,A1200, ...) and the V-360.<br />
<br />
More information on [[Headset]] page.<br />
<br />
===Unlocking the screen===<br />
<br />
When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.<br />
<br />
===Identifying which revision you have===<br />
You will want to determine which revision of the phone you have<br />
<br />
* remember your date code, the bottom of your shipping box should have a sticker stating it.<br />
* read [[Finding_hardware_revision]]<br />
<br />
These two are important, as they allow you to know which image is flashed on you phone at the factory (c.f. [[Distributions]] and [[Neo_FreeRunner_Hardware#History]]).<br />
<br />
== Image Issue==<br />
<br />
Because the software changes so rapidly and the phones were imaged during mass production, we don't ship the newest image with phones. <br />
There are two different kinds of images shipped with the phones: <br />
<br />
1. [[Om 2007.2]]<br />
<br />
2. [[Om 2008.9]]<br />
<br />
But according to the [[FAQ]] and [[Distributions]] pages, all phones ship with [[Om 2007.2]]. This distribution is no longer supported, so before even getting your feet wet, you'll probably want to switch to something else, especially since the FreeRunner is not really usable as a mobile phone with these old distributions.<br />
<br />
Switching to another distribution is easy if you have a computer with a USB port and internet connectivity that can run the dfu-util utility. Most current Linux distros have packaged dfu-util, so if you use Linux you can probably just get it from your distro's repository. The next step is to choose which Openmoko distribution to switch to. See [[Distributions]] for information about the alternatives.<br />
<br />
That page will point you to the files to download, and to the instructions for installing them using dfu-util.<br />
<br />
==For Om 2007.2==<br />
<br />
Please notice it is strongly recommended to update to any recent distro (probably the first thing you should do with your FR after some hours of drooling and playing), as the info herein is completely out of date, as is the software this is about.<br />
See [http://wiki.openmoko.org/wiki/Distributions#SHR_-_Stable_Hybrid_Release Distributions]<br />
<br />
===Navigating menus and applications===<br />
====Today Page====<br />
<br />
[[Image:Todaypage_reduced_true.png|200px|right]] Openmoko starts by displaying the "Today" page, which is your home page. Icons in the top row indicate the status of the phone. The bottom row consists of three tabs. The tab with a house on the left leads to the "Today" page you're viewing now. The central tab leads to the "Launch Task" page, which is the main menu used to start applications. The tab with gears on the right leads to the "Running Tasks" page, which is used to deal with currently open windows and applications.<br />
<br />
<br clear=all /><br />
<br />
[[Image:Todaypage_reduced_false.png|right|200px|]] The "Today" page is empty, as shown above, when you first start Openmoko. We explain below how to turn on the "full view", displayed to the right. In the full view, a second row of icons give quick links to commonly-used applications such as the dialer, the adressbook, mailbox and calendar. The main body of the screen displays a clock and other useful information.<br />
<br />
See [[Today/2007.2]] for more information about the Today page and customization.<br />
<br />
<br clear=all /><br />
<br />
====Launch Task Page====<br />
<br />
{{stub}}<br />
<br />
[[Image:LaunchTasks.png|right|200px]] This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.<br />
<br />
Current categories are [PIM Suite], [[Om_2007.2_Applications|Applications]], [[Games/Om 2007.2|Games]], Utilities, and All.<br />
<br />
<br clear=all /><br />
<br />
====Running Tasks Page====<br />
<br />
{{stub}}<br />
<br />
[[Image:RunningTasks.png|right|200px]] This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.<br />
<br />
<br clear=all /><br />
<br />
====Exiting from and switching to an Application====<br />
<br />
Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.<br />
<br />
Alternatively, you can cycle through active applications using the AUX button<br />
<br />
Clicking the top-left of the screen displays the drop down ''task menu''. This menu lists all active applications and allows to switch directly to any one. ''Note:'' If the task menu is not shown, click and hold the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".<br />
<br />
=== Using the terminal ===<br />
<br />
To start a console from "Today" page, click the middle tab at the bottom of the screen to display the "Launch applications" page, then select Terminal in the "Applications" submenu. The multitaps keyboard slides up (and down) from the bottom of the screen automatically when you touch the screen.<br />
<br />
====Setting date and time====<br />
<br />
From the terminal, type the following, but replace ''MM'' with the month (01-12); ''DD'' with the day (01-31); ''hhmm'' with the time (0000-2359); ''YYYY'' with the year (optional); and ''.ss'' with the seconds (optional).<br />
<br />
date -s ''MMDDhhmmYYYY.ss''<br />
<br />
To make the change persist between reboots, sync the hardware clock with the updated system time.<br />
<br />
hwclock --systohc<br />
<br />
See [[Setting Date and Time]] for more discussion, including synchronizing with an NTP server.<br />
<br />
Note: UNIX traditionally sets the system clock to GMT (UTC) or "Zulu" (Z time zone). So I use the stanza:<br />
date -u MMDDhhmmYYYY.ss (well, I usually ignore the seconds)<br />
Then I can set the local time using the techniques described elsewhere. iceworm<br />
<br />
==== Accessing the microSD card ====<br />
<br />
Mounted at /media/card by default.<br />
<pre><br />
mount /media/card<br />
</pre><br />
If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc. To setup the package management to write on the microSD card when installing new software follow the [[Package_management | package management guide]].<br />
<br />
fox example :<br />
<pre><br />
Filesystem 1k-blocks Used Available Use% Mounted on<br />
rootfs 252544 153560 98984 61% /<br />
/dev/root 252544 153560 98984 61% /<br />
/dev/root 252544 153560 98984 61% /dev/.static/dev<br />
udev 2048 76 1972 4% /dev<br />
/dev/mmcblk0p1 3362 1794 1568 53% /media/card<br />
/dev/mmcblk0p2 476382 157368 294419 35% /media/mmcblk0p2<br />
tmpfs 61928 380 61548 1% /var/volatile<br />
tmpfs 61928 0 61928 0% /dev/shm<br />
</pre><br />
<br />
== For Om 2008.12 ==<br />
<br />
=== Entering the SIM PIN ===<br />
<br />
Some SIM cards require a PIN code to be entered. If your SIM card is like this, you will see a screen like this after the FreeRunner boots:<br />
[[Image:Enterpin.jpg|center]]<br />
The keypad in the lower part of the screen shows only letters, and your PIN is probably numeric. Switch to other keypads by stroking downwards on the screen with the stylus. Then enter your PIN. If you enter a wrong digit, you can backspace by stroking the screen to the left with the stylus. (Keep trying if it doesn't seem to work.) Finally, having composed the correct PIN, tap on the composed number with the stylus. This will enter it into the dialog box where it needs to be. After a brief pause, you will then see the word "Enter" at the top right of the keypad. Tap it. The PIN will then be checked, and if all is well, the Home Screen (next section) will be displayed.<br />
<br />
=== The Home screen ===<br />
<br />
With the bare-bones installation, the home screen looks like this.<br />
[[Image:Homescreen.jpg|center]]<br />
<br />
=== Terminal ===<br />
<br />
In Om 2008.12, no terminal app is installed by default. To get to a command prompt, you need to set up USB-based networking and use SSH; see next section. Before trying to ssh into the FreeRunner, go into the Settings app and set "Suspend" to "off". The default is to go into suspend mode after 30 seconds without activity on the touchscreen, and when in suspend mode, the FreeRunner does not respond to commands sent over the ssh session.<br />
<br />
== Set up USB-based networking, SSH and update ==<br />
<br />
Openmoko allows TCP/IP-over-USB networking for your phone. The main advantages of this are<br />
* You don't need to set-up GPRS or WLAN network connection for the phone software to reach the Internet<br />
* You can SSH from your computer into the phone shell and comfortably do low-level tasks using your computer's terminal software and real keyboard instead of the tiny screen and touchscreen keyboard<br />
<br />
Naturally, the phone must be connected to your computer with USB cable.<br />
<br />
===Connect with the Neo FreeRunner===<br />
<br />
This is discussed in the [[USB_Networking|USB Networking]] section.<br />
<br />
===Update with the package manager===<br />
<br />
In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intervals.<br />
<br />
There are two main methods of doing this:<br />
* upgrading with the package manager '''[[Opkg]]'''<br />
* or manually flashing the device (see [[Flashing the Neo FreeRunner]]).<br />
<br />
There are three layers to the software on the FreeRunner:<br />
<br />
* [[uboot|uBoot]]: Think of u-boot as a combination of the BIOS and Grub on a PC.<br />
* Kernel: The Linux kernel<br />
* Root Filesystem: The rest of the system<br />
<br />
Note that ''uboot'', the ''kernel'' and the ''root filesystem'' may all be flashed to update them. For uboot, this is the only possibility (see [[Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader]]). The advantage of flashing the kernel manually rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.<br />
<br />
{{Warning| UPGRADING TO DAILY KERNELS FROM THE DEVELOPMENT BRANCH MAY BREAK THINGS. That said, assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with<br />
<br />
# opkg update<br />
# opkg -test upgrade<br />
# opkg upgrade<br />
<br />
The first updates the repository information, telling opkg what packages are available. The second allows you to see what the package manager wants to do. The third upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.<br />
}}<br />
<br />
'''Important:''' If you have followed the Getting Started Guide this far, but opkg upgrades do not appear to be happening. Try checking the .conf files in the /etc/opkg/ directory. If you see four URLs pointing at<br />
<nowiki>http://buildhost.openmoko.org/</nowiki>, this is your problem. <nowiki>http://buildhost.openmoko.org/</nowiki> is no longer supported. If you're running Om 2007.2 (the stock distribution that comes with the Freerunner according to the [[FAQ]]), you'll need to edit those files to point to an unofficial [[Users Repositories|User Repository]]. Or, you could install another [[Distributions|distribution]] (which is probably the best bet in the long run).<br />
<br />
<br />
<br />
Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use. Xserver must be updated over ssh to complete succesfully. Dropbear can be updated over ssh with the proper command:<br />
<br />
nohup opkg upgrade dropbear &<br />
<br />
Or upgrade it directly in the FreeRunner terminal.<br />
<br />
opkg upgrade dropbear<br />
<br />
When updating over ssh, the session will be interrupted, but the command should complete successfully(check nohup.out on your device to verify), and you should be able to reconnect within a few seconds.<br />
<br />
Another (better) option is to start a screen session before the upgrade with:<br />
<br />
screen<br />
<br />
After losing the ssh connection and login in again via ssh reconnect to the running screen session with:<br />
<br />
screen -x<br />
<br />
Then connect to the FreeRunner via ssh and type:<br />
<br />
opkg upgrade<br />
<br />
And run this command :<br />
<br />
depmod<br />
<br />
Alternatively you can upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal.<br />
<br />
If you do your first upgrade in two installments like this, it will go more smoothly.<br />
<br />
It will be possible in the future to update uboot with opkg, but this has not yet been implemented.<br />
<br />
=== Installing applications ===<br />
<br />
There are many applications you can install - check out the [[Repositories]] for a list of packages, an example of how to add a repository using scaredy cat as an example can also be found here. A list of pre-installed and available packages with descriptions can be found here - [[Available Packages]].<br />
Or you can check [[Applications]] page to get applications developed from community.<br />
<br />
If you want to install any application on Neo, there three steps:<br />
<br />
'''<br />
1. Download the applicatiion you want to install on Neo.<br />
<br />
2. scp the opkg/ipk file to the root of Neo.<br />
<br />
3. Use Opkg command to intall opkg files.'''<br />
<br />
By following example you can install web browser on Neo:<br />
<br />
The calendar can be installed with<br />
<br />
<br />
First download and unpack it on your GNU/Linux host:<br />
<br />
<pre><br />
wget http://www.ginguppin.de/files/minimo.tar.bz2<br />
tar jvxf minimo.tar.bz2<br />
</pre><br />
<br />
Copy it over to the FreeRunner:<br />
<pre><br />
scp minimo_* root@192.168.0.202:/tmp<br />
</pre><br />
<br />
Then on the FreeRunner:<br />
<pre><br />
opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk<br />
</pre><br />
<br />
You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]<br />
<br />
=== Importing contacts ===<br />
<br />
If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.<br />
<br />
==The next steps==<br />
<br />
Congratulations for setting up your Neo FreeRunner. There are many more resources to help free your phone:<br />
<br />
===Customize the interface===<br />
home screen clock, keyboard<br />
<br />
The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:<br />
<br />
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false<br />
# /etc/init.d/xserver-nodm restart<br />
<br />
If you rather have a regular clock instead of the digital one, do this instead:<br />
<br />
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false<br />
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false<br />
# /etc/init.d/xserver-nodm restart<br />
<br />
REMOVE CLICK SOUND VIA /etc/pulse/session<br />
<br />
More information about today screen customization at [[Today/2007.2]].<br />
<br />
Also, if you prefer having a full keyboard, using matchbox's qwerty keybord, see [[Switching_Keyboards#Matchbox_keyboard|these instructions]]. Then you may also see [http://lists.openmoko.org/pipermail/community/2008-July/021296.html these], which describe a way to add an applet allowing the showing/hiding of that keyboard.<br />
<br />
===Use the GPS===<br />
You can see [[Manually using GPS]] to get more information about GPS. Or download [[TangoGPS]] from [http://www.tangogps.org/downloads/tangogps_0.9.3-r1_armv4t.ipk tangogps.org].<br />
<br />
There were critical [[GPS Problems]] earlier that are largely fixed in newest kernels, see the instructions above to install the updates. More information is on the [[GPS]] page.<br />
<br />
===Play with WLAN, GPRS and Bluetooth===<br />
<br />
There are plenty of development opportunities to integrate these functions in the Openmoko software.<br />
<br />
'''WLAN''': See [[Wireless Networking]]<br />
<br />
'''GPRS''': See [[Manually using GPRS]]<br />
<br />
'''Bluetooth''': See [[Manually using Bluetooth]]<br />
<br />
=== Testing a new distribution ===<br />
<br />
For the feature of Openness, you can flash any Linux [[Distributions]] into FreeRunner. You can testing a new distribution by following ways:<br />
<br />
* [[Booting from SD]].<br />
* Boot from the built-in NAND flash memory.<br />
** [[NeoTool]] gives you a GUI to flash and backup.<br />
** [http://code.google.com/p/om-manager/ om-manager] is another GUI to flash, backup and [[Community_Updates/December_29th%2C_2008#New_applications|more]].<br />
<br />
=== Welcome to the community ===<br />
<br />
The release of the FreeRunner in the summer 2008 has led the community into a new period of rapid growth. The resources available are summarized on the [[Community Resources]]. These are always exciting and interesting times to live in when the balance between Chaos and Order tilts towards change.<br />
<br />
As an entry point, the [http://lists.openmoko.org/pipermail/community/ openmoko community mailing list] is perhaps the most active. As of July 2008, its volume amounts to dozens of messages per day. Read the [[Community_Updates]] for a digest. Openmoko people are there too. You may ask for help on the [[https://lists.openmoko.org/mailman/listinfo/support support mailing list]].<br />
<br />
Or if you use IRC, there is always a good group in the channel #openmoko on FreeNode.<br />
<br />
The links on the top-right of this page lead to the sister sites in the Openmoko community:<br />
* Home and Wiki lead to the same Main Page on the wiki. It needs cleaning, we know...<br />
* Doc leads to the bug ''Trac''king system.<br />
* Planet goes to the collection of Openmoko-relatd blogs.<br />
* Projects is the GForge, free hosting for application developers.<br />
* Lists is the listing of all the public mailing lists on lists.openmoko.org.<br />
<br />
== Annotated references ==<br />
<br />
* [[Neo FreeRunner]]. The top-level view of the specifications.<br />
* [[Neo FreeRunner GTA02 Hardware]]. The detailed specifications.<br />
* [[GTA02 Openness]]. Ultimate chip-level specifications, data sheets and hardware documentation.<br />
* [[Distributions]]. Strengths and weaknesses of the various distributions available for the Neo.<br />
* [[FAQ#Getting_Started_with_your_Neo_FreeRunner|FAQ]].<br />
<br />
To search this wiki with Google, use the following search term:<br />
<br />
<search term> site:http://wiki.openmoko.org/wiki/<br />
<br />
[[Category:Neo FreeRunner Hardware| ]]<br />
[[Category:Basic End User]]</div>Pnaullshttp://openmoko.org/wiki/I2C_CompassI2C Compass2009-07-30T00:16:46Z<p>Pnaulls: Your browser provides a spell check, let's try and use it.</p>
<hr />
<div>== Announcement ==<br />
I <strike>intend to</strike> will build a I2C Compass module that fits into the cavity upwards the sim card holder and right of the battery.<br />
<br />
{{InProgress}}<br />
<br />
'''Further announcements and updates can be found on the discussion page.'''<br><br />
Don't miss out on it, by now there's actually almost more info there than there is here. Until I can get to overhaul this page, the discussion page should be considered the main info counter on this.<br />
<br />
===Benefits===<br />
While the GPS does provide heading information, it computes said by drawing a line between the current and last position generated. Thus it is obvious that the heading generated will:<br />
* a) Fall behind increasingly with tightness of turn<br />
* b) Be increasingly jittery and inaccurate with decreasing forward speed, as the GPS-inherent jitter will be more and more pronounced. <br />
Therefore it is desirable to have a device installed which generates heading directly from the earth magnetic field instead of by comparison of position.<br />
<br />
=== Limitations === <br />
Unlike the GPS, the magnetic compass module is affected by magnetic variation. Also the module will be next to useless pending implementation of its software.<br />
<br />
== Details ==<br />
The module will most likely consist of a HMC6352 or preferably the 3-axis HMC5843 module on a tiny PCB. <br />
The HMC6352 in principle does not need any additional periphery to function. If the nearby radio circuits should turn out to interfere with the compass function, the addition of two resistors and two capacitors may prove necessary, which should have ample room in the space available. The HMC5843 needs a little more periphery but it should still be manageable in the space available Connections will be made by soldering wires to the test points on top of the main FR PCB. <br />
<br />
=== Caveats ===<br />
*It is possible if unlikely that the compass module could itself throw interference into the GPS module. In this case, a decoupling capacitor in the power circuit of the compass module may be necessary.<br />
*It is possible that the shielding of the nearby GPS and GSM modules renders the magnetic field unusable to a HMC6352, or that the HMC6352, even decoupled, emits interference that render either the GPS or the GSM unusable if mounted in that position, either of which would lead to the project having to be given up since there is no other place inside the casing where the chip could be mounted. <br />
<br />
=== Request for Contributions ===<br />
I would appreciate contributions in the form of software, especially patches to frontends and gpsd to have them make use of the module. I intend to try and write a module myself, but I don't make any promises yet. '''See first and next paragraph!'''<br />
<br />
== Status ==<br />
Feasibility assessment is complete.<br />
Hardware development is under way.<br />
=== Next Step(s) ===<br />
In that order<br />
* Find out about how the i2c bus can be made use of in linux<br />
* <strike>Find out if a kernel module exists for this chip</strike> I've checked and came up blank.<br />
* Order one or more ICs for testing purposes<br />
* Etch a test board<br />
* If none exists, get started on the kernel module<br />
<br />
== Purchase ==<br />
The module is (obviously) not available for purchase yet.<br />
<br />
''' Whether or not I proceed to production state with this project depends largely on expression of interest by the community. '''<br />
<br />
=== Pricing ===<br />
Please note that these are preliminary figures which may well go either up or down. I will try to find volume discount prices on ICs and post more accurate price/order count relations asap.<br />
*The end price for the complete module will probably be in the range of 40-60 USD exc S/H. <br />
*Bare PCBs will range in the area of 1.50 to 2.00 USD + S/H. <br />
*DIY-Kits with IC and PCB will range between 30 and 50 USD depending on order count.<br />
<br />
=== Minimum Order Count ===<br />
Preliminary minimum order counts are in the range of 40 PCBs. Ordering less PCBs is uneconomical.<br />
=== Pre-Order ===<br />
Non-binding pre-order is open effective immediately in the discussion thread of this page.<br />
<br />
== Links and Resources ==<br />
*[http://www.magneticsensors.com/datasheets/HMC5843.pdf HMC5843 Datasheet]<br />
*[http://www.sparkfun.com/datasheets/Components/HMC6352.pdf HMC6352 Datasheet]<br />
<br />
[[Category:Hardware]]</div>Pnaullshttp://openmoko.org/wiki/Openmoko_on_HTC-DreamOpenmoko on HTC-Dream2009-07-30T00:14:04Z<p>Pnaulls: Sensible formatting</p>
<hr />
<div>== Introduction ==<br />
HTC-Dream is a android based phone.<br />
Android is running on top of a Linux kernel.<br />
So we have basically no work to do using this kernel to boot an Openmoko user space.<br />
This work is done.<br />
I booted an Openmoko user space.<br />
The way to do it on your own is described below.<br />
<br />
=== Working ===<br />
* USB-Ethernet<br />
* Framebuffer console<br />
<br />
== Setup the rootfs ==<br />
* In this example setup I used a SD-Card as root partition.<br />
* In order to follow this guide format a SD-Card (just like installing Openmoko on Neo Freerunner).<br />
** First partition: vfat<br />
** Second partition: ext2 (root)<br />
* mount it and extract http://downloads.openmoko.org/distro/releases/Om2008.12/Om2008.12-om-gta02.rootfs.tar.gz to it<br />
<br />
== Bootloader ==<br />
You need to install fastboot.<br />
In order to do this, you will have need to have "root" on the existing Android device or already have a developer version of the bootloader installed.<br />
<br />
== Kernel ==<br />
=== Building new kernel ===<br />
Use 2.6.29 from android.git.kernel.org. 2.6.27 rebooted after a few minutes without any reason.<br />
<br />
export HACK_DIR=`pwd`<br />
git clone git://android.git.kernel.org/kernel/msm.git<br />
<nowiki>wget http://wiki.openmoko.org/images/3/3b/Openmoko-htc-dream-kernel-config.txt</nowiki><br />
cp Openmoko-htc-dream-kernel-config.txt msm/.config<br />
cd msm<br />
make CROSS_COMPILE=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/bin/ ARCH=arm<br />
sudo make CROSS_COMPILE=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/bin/ ARCH=arm modules_install<br />
sudo mv /lib/modules/2.6-29-openmoko-htc-dream /mnt/foo/lib/modules/<br />
sync<br />
umount /mnt/foo<br />
<br />
=== Building boot.img ===<br />
<br />
mkdir $HACK_DIR/mk_boot_img<br />
cd $HACK_DIR/mk_boot_img<br />
<nowiki>wget http://wiki.openmoko.org/images/9/92/Mkbootimg.bin</nowiki><br />
<nowiki>wget http://wiki.openmoko.org/images/f/f6/Newramdisk.cpio.gz</nowiki><br />
mv Newramdisk.cpio.gz newramdisk.cpio.gz<br />
sudo cp Mkbootimg.bin /usr/bin/mkbootimg<br />
mkbootimg --cmdline "console=tty0 no_console_suspend=1 root=/dev/mmcblk0p2 rootdelay=2 fbcon=rotate:1" \<br />
--kernel $HACK_DIR/msm/arch/arm/boot/zImage \<br />
--ramdisk ./newramdisk.cpio.gz -o openmoko-boot.img<br />
<br />
=== Flashing boot.img ===<br />
* Start into fastboot<br />
* execute<br />
fastboot flash boot openmoko-boot.img<br />
* restart then handy<br />
fastboot reboot<br />
<br />
== WLAN ==<br />
* http://bobcopeland.com/android_wifi.html<br />
<br />
[[Category:Distributions]]</div>Pnaullshttp://openmoko.org/wiki/Manuals/AndroidManuals/Android2009-07-27T01:18:58Z<p>Pnaulls: /* The Home Button */</p>
<hr />
<div>{{Languages|Android usage}}<br />
<br />
{|align=right<br />
|__TOC__<br />
|}<br />
[[Image:android.png]]<br />
<br />
= Introduction = <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 />
==== 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 />
{{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>Pnaullshttp://openmoko.org/wiki/Community_Updates/2009-07-09Community Updates/2009-07-092009-07-25T10:34:21Z<p>Pnaulls: /* Distributions */</p>
<hr />
<div>====='''Period June 25nd to July 9th, 2009'''=====<br />
<br />
==Distributions==<br />
<br />
* '''[http://activationrecord.net/radekp/qtmoko/ QtMoko V3]''' - QT moko is a Debian distribution for the Openmoko FreeRunner phone. Phone and user interface are based on QT Extended, formerly known as Qtopia. Version V3 should be stable as a daily phone. Latest changes include:<br />
** upgrade to QT 4.5.2 which should improve speed<br />
** merge from other QtMoko branches with many bug fixes<br />
** added nice new QtMaze game<br />
** fixed problem so that apt-get should work out of the box now<br />
<br />
* '''[http://activationrecord.net/radekp/qtmoko/download/ Experimental QtMoko X4]''' - new QtMoko images that are based on Debian and that now support running X application from Qtopia. You have to use QX launcher which will allow you to start X applications in fullscreen. You can exit the application when you press the touchscreen for 5 seconds. The application will then be paused and you can either kill it or continue. The support for switching tasks between Qtopia and X application is still missing.<br />
** images are called x4 (because of X windows support), images without X will be called v4<br />
** logging should now work<br />
** better UI speed<br />
** rotation should work<br />
** apt-get should work out of the box<br />
** new application QX which is used as launcher for X applications<br />
** included TangoGPS and ScummVM<br />
** /dev/mmcblk0p1 mounts to /media/card now and /dev/mmcblk0p4 as swap<br />
<br />
* '''[[OpenWrt]]''' - Mirko Vogt and the OpenWrt team have released OpenWrt for the Neo/FreeRunner devices. They provide flashable [http://nanl.de/files/openwrt/openmoko/ images]. Mind - that, as usual for OpenWrt - the default IP of your device will be "192.168.1.1" and the only running service will be <telnet> on port 23. After logging in and setting a password, <telnetd> is getting replaced through <sshd> (port 22).<br />
** kernel 2.6.30.1 is running <br />
** clean, stable and accelerated graphics system<br />
** GPS works<br />
** performance tuned<br />
** software added/upgraded<br />
** a beautiful bootsplash<br />
** phone calls are possible, thanks to paroli<br />
* A new release of FSO is around the corner, see [[OpenmokoFramework/Status Update 7|Openmoko Framework Team Status Report 2009.7]]<br />
<br />
==Applications== <br />
===New Applications===<br />
<br />
* '''[http://github.com/Sektor/mqutim/ mqutIM]''' - instant messenger for QtMoko. Only ICQ protocol is currently supported.<br />
* '''[http://github.com/Sektor/noxchat/ NoxChat]''' - IRC client for QtMoko.<br />
* '''[http://code.google.com/p/neote/ Neote 0.2.0]''' - note taking application. Its interface aims to be easy and finger friendly. It's written in Python/Elementary and uses SQLite for storing data. Notes can be organized using custom categories that you can add, rename and delete at any time. Currently, only text note type is available. It should run on any system with a revision of python-elementary equal or greater to 40756. Looks like at time of this writing SHR-unstable is the only candidate. Future plans:<br />
** Draw notes<br />
** Record voice notes<br />
<br />
===Application Updates===<br />
<br />
* '''[http://code.google.com/p/elmdentica/ Elmdentica 0.5.1]''' - the µ-blogging (identi.ca, twitter, other twitter like api µ-blogs) client for your Free Smartphone. You can take a look at the screenshot [http://blog.1407.org/2009/07/09/elmdentica-release-051/ here]<br />
** pretty bubbles with icons and temporal references<br />
** repeat (or retweet) what other say and reply to others<br />
** counter which warns if you type more than 140 characters<br />
** multiple account support (only one active at each moment)<br />
** Fixed some bugs<br />
** added a domain editor<br />
** supports links in status messages (but does nothing with them)<br />
<br />
* '''[http://projects.openmoko.org/frs/?group_id=260&release_id=542 ffalarms 0.2.3]''' is a program to set multiple alarms a day using a finger friendly user interface (hence the name). Three clicks to set an alarm time. Progressive volume. Switch off though four buttons puzzle. LED night clock included. ffalarms 0.2.3 includes:<br />
**rewritten using Vala/libeflvala/Elementary (same features as 0.2.2)<br />
**avoids suspend and keeps display on during alarm on FSO platform (such as SHR)<br />
**note: will not stop alarms added by previous versions of ffalarms<br />
<br />
* '''[http://gvsigmobileonopenmoko.wordpress.com/ gvSIG Mobile 0.1.4]''' - Mobile GIS <br />
** [http://gvsigmobileonopenmoko.wordpress.com/2009/06/24/with-the-new-courier-mode-openmoko-actively-guides-you-through-the-city/ Courier Mode] - produce and display tours of an area, or use the eature to measure your distance from a point / region<br />
**GUI tweaks including full screen mode<br />
**Arabic translation, thanks to Nawfal Cherqui<br />
**Support for German coordinate systems (EPSG:31466 to EPSG:31469)<br />
<br />
==Community==<br />
* On 2008-07-04, according to '''[http://www.openmoko.com/press/Openmoko_20080702.pdf press release]''', Openmoko has opened it's online store for purchase of the Openmoko Neo FreeRunner. Thus this date is considered as official FreeRunner birthday day. Happy birthday FreeRunner!<br />
* Opened Czech Openmoko community portal: '''http://www.openmoko.cz''' and moved [http://www.jabber.cz Jabber] conference from openmoko@chat.linjab.net to openmoko@muc.openmoko.cz<br />
* Kimaidou, author of [[Mokometeo]], has created a google '''[http://code.google.com/p/mokometeo/source/checkout code]''' page with a mercurial repository. Thus you all are encouraged to commit the improvements.<br />
* David Reyes has uploaded the '''[http://www.tuxbrain.com/en/content/buzz-fix-party-barcelona-movie video]''' made at Barcelona Buzz fix party and also made subtitles in English. Sure it can be improved but at least will let follow the conversations for those who are not familiar with Spanish.<br />
* Pictures with comments of the last Buzz fix party on Madrid can be found '''[http://www.tuxbrain.com/en/content/buzz-fix-party-madridphotos here]'''.<br />
<br />
==Event News==<br />
<br />
* '''2009-07-25''' '''[https://penta.debconf.org/dc9_schedule/events/376.en.html The Debconf9]''' buzz fix party has been scheduled on Saturday.<br />
* '''2009-07-18''' '''[http://openmoko.cz/www/index.php/pages/read/2/Openmoko_sraz_prednaska_a_buzzfix_party_v_Beroun Linux meeting Beroun]''' Czech Openmoko community meeting and buzz fix party in Beroun.<br />
<br />
[[Category:Community Update]]</div>Pnaullshttp://openmoko.org/wiki/Community_UpdatesCommunity Updates2009-07-25T10:33:31Z<p>Pnaulls: </p>
<hr />
<div>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 />
= Post launch series =<br />
* DRAFT: [[Community Updates/Draft 2009-08-06]]<br />
* [[Community Updates/July 23, 2009]]<br />
* [[Community Updates/July 9, 2009]]<br />
* [[Community Updates/June 25, 2009]]<br />
* [[Community Updates/May 22, 2009]]<br />
* [[Community Updates/April 30, 2009]]<br />
* [[Community Updates/April 17, 2009]]<br />
* [[Community Updates/April 05, 2009]]<br />
* [[Community Updates/March 20, 2009]]<br />
* [[Community Updates/March 6, 2009]]<br />
* [[Community Updates/February 20, 2009]]<br />
* [[Community Updates/February 6, 2009]]<br />
* [[Community Updates/January 23th, 2009]]<br />
* [[Community Updates/January 12th, 2009]]<br />
* [[Community Updates/December 29th, 2008]]<br />
* [[Community Updates/December 15th, 2008]]<br />
* [[Community Updates/December 1st, 2008]]<br />
* [[Community Updates/November 16th, 2008]]<br />
* [[Community Updates/November 2nd, 2008]]<br />
* [[Community Updates/October 19th, 2008]]<br />
* [[Community Updates/October 3rd, 2008]]<br />
* [[17th September, 2008 - Activity since launch]]<br />
<br />
== Rules for community updates ==<br />
After May 22dnd 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 in the Talk page of the next Community Update page (example, see http://wiki.openmoko.org/wiki/Talk:Community_Updates/June_25%2C_2009 ). The news will be added there. On release, the content of that page is moved to be the content of the actual page ( http://wiki.openmoko.org/wiki/Community_Updates/June_25%2C_2009 ). Detailed instructions below.<br />
<br />
'''Adding news'''<br />
# Don't trust that someone else will add it, add it yourself and make it clean<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 trust that someone else will 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 14th June, 2008 - When it will be possible to buy Openmoko?]<br />
* [http://lists.openmoko.org/pipermail/community/2008-June/018887.html 10th June, 2008 - SMT is running!]<br />
* [http://lists.openmoko.org/pipermail/community/2008-June/018575.html 5th June, 2008 - Cleared to start Mass production]<br />
* [http://lists.openmoko.org/pipermail/community/2008-May/017531.html May 20, 2008 - Whats up with the freerunner mass production?]<br />
* [http://lists.openmoko.org/pipermail/community/2008-April/015189.html April 14, 2008 - next costumers location]<br />
* [http://lists.openmoko.org/pipermail/community/2008-April/015080.html April 11, 2008 - FreeRunner Pricing and PVT update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-April/014928.html April 7, 2008 - Any updates on the PVT status?]<br />
* [http://lists.openmoko.org/pipermail/community/2008-March/014361.html March 25, 2008 - Production status Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-February/013555.html February 25, 2008 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-February/013356.html February 14, 2008 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-February/013280.html February 10, 2008 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-January/012821.html January 24, 2008 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-January/012499.html January 10, 2008 - Community Update]<br />
* [http://lists.openmoko.org/pipermail/community/2008-January/012357.html January 2, 2008 - Community Update]<br />
<br />
[[Category:Community Update| ]]<br />
[[Category:Community]]</div>Pnaullshttp://openmoko.org/wiki/Community_Updates/2009-05-22Community Updates/2009-05-222009-06-08T00:11:12Z<p>Pnaulls: /* Distributions */</p>
<hr />
<div>====='''Period 01, May ~ 22, May, 2009'''=====<br />
<br />
==Distributions==<br />
<br />
* '''[[Om 2009]]''' There have been new additions to features and bug fixes to the last image. The latest testing release-4 for May 22th is available [http://downloads.openmoko.org/distro/testing/NeoFreerunner/ here]<br />
<br />
* '''[[Neovento]]''' (formerly FYP) This release has some new features like Zhemes which allows you to change the Zhone/LXDE theme easily and also it's less memory hungry than the ones before.<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047147.html Hackable:1]''' now offers phone functionality and SMS plus a full PIM suite consisting of contacts, calendar and todo list manager, plus a timesheet time tracker application and more. The detailed steps for installation are [http://www.hackable1.org/wiki/Installation here]<br />
<br />
==Applications== <br />
===New Applications===<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047366.html Podboy 0.0.1]''' - pre-alpha release is a podcast aggregator/player written in Python/Elementary<br />
<br />
* '''[http://www.opkg.org/package_213.html notifier 0.2]''' - This is a simple & great python application to remind you if you miss a call. It's really basic with no spectacular features. More features (Treviño patch) and discussions can be found [http://n2.nabble.com/little-today-app-for-shr-tp2757153p2757153.html here]<br />
<br />
* '''[http://code.google.com/p/omgps/ omgps]'''It is a GPS application, written in C and python (as plugin language). Dependencies are: GTK+, glib, dbus, FSO frameworkd, etc<br />
<br />
===Application Updates===<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047561.html Online level editor for Mokomaze]''' Editor is written in JavaScript. Your browser must support <canvas> tag<br />
**http://mokomaze.projects.openmoko.org/editor/<br />
<br />
* '''[[openBmap]] [[OpenBmap#0.3.0|0.3.0]]''', GSM/GPS logger to build a free database of GSM cells coverage. Focus: quality of data.<br />
**Major highlight: beta Neighbour cells log now stable and activated! The neighbour cells are taken into account for statistics and map coverage generation.<br />
**All the changes [[OpenBmap#0.3.0|here]].<br />
**On the project side, there is now a [http://twitter.com/openBmap/ twitter feed]. It gets updated every time uploaded logs start getting processed.<br />
**Package available in FSO and SHR feeds, [http://www.opkg.org/package_186.html opkg.org] and [http://sourceforge.net/project/showfiles.php?group_id=218065&package_id=310952 sourceforge].<br />
<br />
* '''[http://www.opkg.org/package_141.html MokoGeocaching 0.4]''' This is a little gtk python script that searches the geocaching.com site for caches near your current position or a user specified lattitude and longitude and add the cache as a poi in TangoGPS. <br />
<br />
* '''[http://www.opkg.org/package_191.html PISI 0.2]''' Enhancements to calendar synchronization,contacts synchronization<br />
<br />
* '''[http://blog.1407.org/2009/05/02/omnewrotate-054-is-out/ OMNewRotate 0.5.4]''' You can get more details [http://lists.openmoko.org/pipermail/community/2009-May/046996.html here]<br />
<br />
* '''[http://mokomaze.projects.openmoko.org/ Mokomaze 0.5.1]''' with completely new physics and graphics engines is released. Packages can be downloaded [http://www.opkg.org/package_121.html here]<br />
<br />
* '''[http://www.opkg.org/package_207.html Dictator 0.2]''' has been released with some [http://wiki.openmoko.org/wiki/Dictator improvements] <br />
<br />
* '''[http://www.opkg.org/package_154.html Acceleroids v0.1.3]''' released<br />
** added support of new kernels<br />
** .desktop file fixed<br />
<br />
* '''[http://www.opkg.org/package_190.html Intone (0.51)]''' Elementary based mplayer frontend. Discussions on the testing of this version can be found [http://n2.nabble.com/Intone-%280.51%29-Elementary-mplayer-frontend---updated-20-May-tp2587826p2587826.html here]<br />
<br />
* '''[http://www.opkg.org/package_211.html e-tasks (0.20)]''' Elementary based tasks manager has been updated to save notes with tasks.<br />
* '''[http://www.opkg.org/package_115.html guitartune (0.35)]''' GTK musical instrument tuner has been updated.<br />
<br />
==Community==<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047467.html Confundus call recorder competition]''' There were two results to this<br />
** http://wiki.openmoko.org/wiki/Call_Recorder by Tom<br />
** http://wiki.openmoko.org/wiki/Dictator by Matthias<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047138.html FrOSCon 2009]''': Call for Participation The Free and Open Source Software Conference, an annual event held at the University of Applied Sciences Bonn-Rhein-Sieg, Germany. The fourth edition of FrOSCon will take place on August 22nd/23rd 2009<br />
<br />
* Weekly Kernel Update for '''[http://lists.openmoko.org/pipermail/devel/2009-May/005539.html May 12]''' and '''[http://lists.openmoko.org/pipermail/devel/2009-May/005595.html May 19]'''<br />
<br />
* '''[http://twit.tv/floss69 Interview]''' of Sean Moss-Pultz and Christopher Hall for Twit TV and FLOSS weekly<br />
<br />
* '''[http://www.tuxbrain.net/en/node/10 DebConf9 Neo FreeRunner Special Offer]''' Openmoko, Jon "maddog" Hall, and Tuxbrain wants to thank the Debian community for their great work offering a DebConf Neo FreeRunner special pack, only for [http://debconf9.debconf.org DebConf9] attendants.[http://www.tuxbrain.net/en/node/10 DebConf9 The link] includes a video of maddog explaining the offer. <br />
<br />
* '''[http://risto.kurppa.fi/blog/its-time-to-contribute-to-om2009-paroli/ It’s time to contribute to OM2009 & Paroli]''' Risto H. Kurppa makes a clear explanation on how and why contribute to the new Openmoko OS release.<br />
<br />
* '''[http://n2.nabble.com/New-Life-in-Openmoko-Phones-tt2934354ef1958.html New Life in Openmoko Phones]''' Wolfgang Spraul announce another big step in opening the Openmoko Hardware publishing board outline, footprints and netlist under Creative Commons Share-Alike license. He also introduce the [[Gta02-core| GTA02-core project].<br />
<br />
* There was an '''[http://lists.openmoko.org/pipermail/devel/2009-May/005489.html update on progress of DRI]''' for the FreeRunner's graphics chip.<br />
<br />
*'''[http://www.tuxbrain.com/en/node/17 Watching DVB-H TV on Neo]''' Video of one of the guys of Openmoko-spain Jose Luis Garduño <br />
<br />
*'''[http://www.tuxbrain.com/en/node/18 Opeta is moving!]''' Miguel Angel from [http://www.mokardu.com Mokardu project] show us the first movements of the first Openmoko brained Tank, it turns because there is is only one motor inside, the other is on the way, has to be replaced after some ... hum ... see your own in this [http://www.miquelangel.info/download/movies/burning.mpg short mpg video]<br />
<br />
==Event News==<br />
<br />
* '''2009-05-22/24''' [http://www.shr-project.org/trac/wiki/FSOSHRUDCON'09 FSOSHRUDCON'09] | Joint FSO/SHR Users and Developers Convention 2009 | to be held in Essen Horst Germany<br />
<br />
* '''2009-06-25/26''' [http://proj3.moeaidb.gov.tw/nmipo/content/getfile.aspx?sn=C24E0F585A9A41DDAF83A1713CED2D0F OPEN SOURCE IN MOBILE 2009] | to be held in Westin Taipei Taiwan | Openmoko Sean will give a speech<br />
<br />
* '''2009-07-02/05''' [http://lvee.org/en/main LVEE 2009] | The 5th International conference of developers and users of free / open source software “Linux Vacation / Eastern Europe” to be held in Grodno (Belarus)<br />
<br />
<br />
[[Category:Community Update]]</div>Pnaullshttp://openmoko.org/wiki/Community_transitionCommunity transition2009-06-07T16:57:18Z<p>Pnaulls: /* History */</p>
<hr />
<div>== History ==<br />
<br />
Sean Moss-Pultz (CEO of Openmoko Inc.) decided that the best path forward for the phone business is to turn the future of the Freerunner over to the community. (See the [http://lists.openmoko.org/pipermail/community/2009-June/048903.html announcement] for details)<br />
<br />
In brief :<br />
* The Neo Freerunner development is now fully performed by the [[Gta02-core]] project<br />
* The community has permission to use the Openmoko brand/trademark for their efforts<br />
* Openmoko Inc. will continue to provide funding for operating the infrastructure (Wiki, GIT, Trac, Planet, ...)<br />
<br />
== Wish List ==<br />
<br />
List here for what kinds of things OM can do to smooth this transition.<br />
* continue to funding the infrastructure<br />
* promote and sell the Freerunner<br />
* create the Openmoko foundation ?<br />
<br />
<br />
== FAQ ==<br />
<br />
=== I'm using OM2008/2009 now. Will this distribution still be maintained ? Should I switch ? How ? What will change, what do I have to learn/unlearn ? ===<br />
''please answer here'' (Om2008 hadn't maintained for a while before that announcement. Now only maintained distro by Openmoko is Om2009)<br />
<br />
=== What will happen with FSO ? Will development continue ? Will a distribution carry it ? ===<br />
''please answer here''<br />
<br />
=== What will happen with Paroli ? Will development continue ? Will a distribution carry it ? ===<br />
''please answer here''<br />
<br />
=== How will the kernel be maintained ? ===<br />
<br />
The kernel will be maintained by a group of volunteers. The main change now is that more than one person will be able to commit. The list of committers will be published soon.<br />
<br />
These are the [https://docs.openmoko.org/trac/milestone/stable-kernel-2009.1 most important bugs] that need to be fixed now.<br />
<br />
'''This is the complete [https://docs.openmoko.org/trac/query?status=accepted&status=assigned&status=in_testing&status=new&status=reopened&component=System+Software&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component report]''' with all the bugs (some of them might be invalid, please ask on IRC or in the mailing list before trying to fix one).<br />
<br />
There is a current ongoing effort to get basic GTA02 support in the mainstream Linux kernel, the patches have been sent. Once this basic support is ready other drivers can be submitted as well. Many of the drivers need additional work to be suitable for upstream inclusion.<br />
<br />
=== Will Openmoko continue selling FreeRunners ? For how long ? ===<br />
''please answer here''<br />
<br />
=== I have a purchase/return/warranty/etc. in progress with Openmoko Inc. or a distributor. What will happen ? ===<br />
''please answer here''<br />
<br />
=== I have buzz/#1024/no bass/etc. Can I still get it fixed ? How ? ===<br />
''please answer here''<br />
<br />
=== Will the Openmoko Internet resources, Wiki, mailing lists, SVN, git, downloads, people, trac, etc., be shut down ? ===<br />
<br />
No. Openmoko Inc. has committed to continuing to support the community by funding the resources available on openmoko.org. <br />
<br />
From Sean's email [http://lists.openmoko.org/pipermail/community/2009-June/048903.html announcement]: ''"Openmoko Inc. then will act as the sponsor of this effort. We will continue to fund all necessary server infrastructure..."''<br />
<br />
=== Will "project B" continue ? ===<br />
''please answer here''<br />
<br />
=== What's the future of Open phone hardware without Openmoko Inc. ? ===<br />
''please answer here''</div>Pnaullshttp://openmoko.org/wiki/GSM_buzzGSM buzz2009-05-24T13:53:21Z<p>Pnaulls: Update link</p>
<hr />
<div>GSM buzz has been an issue with GTA02, it has been discussed in several posts on the community mailing list. One early one is here [http://lists.openmoko.org/nabble.html#nabble-td1509627|a1509627]. <br />
<br />
The big-C_rework_SOP_rc2.pdf can be found here [http://people.openmoko.org/joerg/GSM_EMI_noise/] as can a user's post of their result, from here [http://anyotherkey.googlepages.com/c]<br />
<br />
Openmoko will support those offering a diy and encourage hardware volunteers. Fix it / buzz fix parties have been taking place.<br />
<br />
There is still a problem though, as the wired mic causes buzz [http://lists.openmoko.org/nabble.html#nabble-td2509041]<br />
<br />
A bluetooth headset may be one solution.<br />
<br />
== See also ==<br />
<br />
* [[Neo_FreeRunner_Hardware_Issues#Poor_Audio_Quality_.28FIXED.29|Hardware Issues]] - detailed discussion of problem and solutions.<br />
<br />
{{Languages|GSM}}<br />
<br />
[[category:GSM]]</div>Pnaullshttp://openmoko.org/wiki/Buzz_FixBuzz Fix2009-05-24T13:50:55Z<p>Pnaulls: Already a page on this</p>
<hr />
<div>#REDIRECT [[GSM buzz]]</div>Pnaullshttp://openmoko.org/wiki/Community_Updates/2009-05-22Community Updates/2009-05-222009-05-20T20:16:06Z<p>Pnaulls: _Basic_ grammar and spell check. Come on - Firefox will tell you about 1/2 of these.</p>
<hr />
<div>====='''Period 01, May ~ 22, May, 2009'''=====<br />
<br />
==Distributions==<br />
<br />
* '''[[Om 2009]]''' There have been new additions to features and bug fixes to the last image. The latest testing image for May 9th is available [http://downloads.openmoko.org/distro/testing/NeoFreerunner/ here]<br />
<br />
* '''[[Neovento]]''' (formerly FYP) This release has some new features like Zhemes which allows you to change the Zhone/LXDE theme easily and also it's less memory hungry than the ones before<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047147.html Hackable:1]''' now offers phone functionality and sms plus a full PIM suite consisting of contacts, calendar and todo list manager, plus a timesheet time tracker application and more.The detailed steps for installation are [http://www.hackable1.org/wiki/Installation here]<br />
<br />
==Applications== <br />
===New Applications===<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047366.html Podboy 0.0.1]''' - pre-alpha release is a podcast aggregator/player written in Python/Elementary<br />
<br />
* '''[http://www.opkg.org/package_213.html notifier 0.2]''' - This is a simple & great python application to remind you if you miss a call. It's really basic with no spectacular features. More features (Treviño patch) and discussions can be found [http://n2.nabble.com/little-today-app-for-shr-tp2757153p2757153.html here]<br />
<br />
===Application Updates===<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047561.html Online level editor for Mokomaze]''' Editor is written in JavaScript. Your browser must support <canvas> tag<br />
**http://mokomaze.projects.openmoko.org/editor/<br />
<br />
* '''[http://www.opkg.org/package_186.html openBmap 0.3.0]''' The details of the release can be found [http://lists.openmoko.org/pipermail/community/2009-May/047514.html here]<br />
<br />
* '''[http://www.opkg.org/package_141.html MokoGeocaching 0.4]''' This is a little gtk python script that searches the geocaching.com site for caches near your current position or a user specified lattitude and longitude and add the cache as a poi in TangoGPS. <br />
<br />
* '''[http://www.opkg.org/package_191.html PISI 0.2]''' Enhancements to calendar synchronization,contacts synchronization<br />
<br />
* '''[http://blog.1407.org/2009/05/02/omnewrotate-054-is-out/ OMNewRotate 0.5.4]''' You can get more details [http://lists.openmoko.org/pipermail/community/2009-May/046996.html here]<br />
<br />
* '''[http://mokomaze.projects.openmoko.org/ Mokomaze 0.5.1]''' with completely new physics and graphics engines is released. Packages can be downloaded [http://www.opkg.org/package_121.html here]<br />
<br />
* '''[http://www.opkg.org/package_207.html Dictator 0.2]''' has been released with some [http://wiki.openmoko.org/wiki/Dictator improvements] <br />
<br />
* '''[http://www.opkg.org/package_154.html Acceleroids v0.1.3]''' released<br />
** added support of new kernels<br />
** .desktop file fixed<br />
<br />
* '''[http://www.opkg.org/package_190.html Intone (0.51)]''' Elementary based mplayer frontend. Discussions on the testing of this version can be found [http://n2.nabble.com/Intone-%280.51%29-Elementary-mplayer-frontend---updated-20-May-tp2587826p2587826.html here]<br />
<br />
==Community==<br />
<br />
*'''[http://lists.openmoko.org/pipermail/community/2009-May/047467.html Confundus call recorder competition]''' There were two results to this<br />
** http://wiki.openmoko.org/wiki/Call_Recorder by Tom<br />
** http://wiki.openmoko.org/wiki/Dictator by Matthias<br />
<br />
* '''[http://lists.openmoko.org/pipermail/community/2009-May/047138.html FrOSCon 2009]''': Call for Participation The Free and Open Source Software Conference, an annual event held at the University of Applied Sciences Bonn-Rhein-Sieg, Germany. The fourth edition of FrOSCon will take place on August 22nd/23rd 2009<br />
<br />
* Weekly Kernel Update for '''[http://lists.openmoko.org/pipermail/devel/2009-May/005539.html May 12]''' and '''[http://lists.openmoko.org/pipermail/devel/2009-May/005595.html May 19]'''<br />
<br />
* '''[http://twit.tv/floss69 Interview]''' of Sean Moss-Pultz and Christopher Hall for Twit TV and FLOSS weekly<br />
<br />
* '''[http://www.tuxbrain.net/en/node/10 DebConf9 Neo FreeRunner Special Offer]''' Openmoko, Jon "maddog" Hall, and Tuxbrain wants to thank the Debian community for their great work offering a DebConf Neo FreeRunner special pack, only for [http://debconf9.debconf.org DebConf9] attendants.[http://www.tuxbrain.net/en/node/10 DebConf9 The link] includes a video of maddog explaining the offer. <br />
<br />
*'''[http://risto.kurppa.fi/blog/its-time-to-contribute-to-om2009-paroli/ It’s time to contribute to OM2009 & Paroli]''' Risto H. Kurppa makes a clear explanation on how and why contribute to the new Openmoko OS release.<br />
<br />
*'''[http://n2.nabble.com/New-Life-in-Openmoko-Phones-tt2934354ef1958.html New Live in Openmoko Phones]''' Wolfgang Spraul announce another big step in opening the Openmoko Hardware publishing board outline, footprints and netlist under Creative Commons Share-Alike license. He also introduce the [http://wiki.openmoko.org/wiki/Gta02-core gta02-core project].<br />
<br />
==Event News==<br />
<br />
* '''2009-05-22/24''' [http://www.shr-project.org/trac/wiki/FSOSHRUDCON'09 FSOSHRUDCON'09] | Joint FSO/SHR Users and Developers Convention 2009 | to be held in Essen Horst Germany<br />
<br />
* '''2009-06-25/26''' [http://proj3.moeaidb.gov.tw/nmipo/content/getfile.aspx?sn=C24E0F585A9A41DDAF83A1713CED2D0F OPEN SOURCE IN MOBILE 2009] | to be held in Westin Taipei Taiwan | Openmoko Sean will give a speech<br />
<br />
* '''2009-07-02/05''' [http://lvee.org/en/main LVEE 2009] | The 5th International conference of developers and users of free / open source software “Linux Vacation / Eastern Europe” to be held in Grodno (Belarus)</div>Pnaullshttp://openmoko.org/wiki/User_talk:WowgoldgateUser talk:Wowgoldgate2009-05-20T19:38:53Z<p>Pnaulls: This page was marked for "speedy" deletion 5 months ago, which tells me no one is taking any kind of ownership of the wiki for such matters. Useless.</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Robin7894User talk:Robin78942009-05-20T19:35:04Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Robin7894User talk:Robin78942009-05-19T19:40:20Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/Qtopia_/_Qt_Extended_on_FreeRunnerQtopia / Qt Extended on FreeRunner2009-05-13T03:27:23Z<p>Pnaulls: /* Current status */</p>
<hr />
<div>{{Languages|Qtopia_on_FreeRunner}}<br />
<br />
This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.<br />
<br />
__TOC__<br />
<br />
== Current status ==<br />
<br />
* The most recent version is [[Qt Extended Improved]].<br />
<br />
* On 3 March 2009 Qt software has discontinued Qt Extended. See http://www.qtsoftware.com/about/news/qt-software-discontinues-qt-extended for more details.<br />
<br />
* Qt software announced that has discontinued QT Extended as a standalone product, integrating it into QT.<br />
<br />
<br />
Check [http://wiki.openmoko.org/wiki/Qt_Extended_4.4.3 QtExtended 4.4.3] for more info on the latest (and final) release.<br />
<br />
On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.<br />
<br />
This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.<br />
<br />
There are other third-party GPS applications available:<br />
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps] (/!\ non-compatible with 4.4.x --[[User:Xc8|Xc8]] 22:28, 6 February 2009 (UTC))<br />
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)] (! Not working on 4.4.2 --[[User:AlecTBM|AlecTBM]] 20:00 GMT +01:00 10 February 2009)<br />
<br />
([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)<br />
<br />
You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)<br />
<br />
'''What is in the latest release (QtExtended 4.4.2)?'''<br />
<br />
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].<br />
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on WebKit<br />
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)<br />
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]<br />
* GPS API<br />
* USB net/storage switching<br />
* GTalk support<br />
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-English languages in the keyboard]<br />
<br />
<br />
[http://www.qtsoftware.com/about/news/qt-software-discontinues-qt-extended Qt Extended will be discontinued as a stand-alone product] March 2009 after the release of version 4.4.3<br />
and selected features will be migrated into the Qt framework.<br />
<br />
== Installation ==<br />
<br />
=== Installation option 1: Flash Qtopia to FreeRunner ===<br />
<br />
Download the image mentioned above, then follow the instructions in the {{Main|Flashing the Neo FreeRunner}}<br />
<br />
=== Installation option 2: Install Qtopia on a microSD card ===<br />
<br />
Installation Requirements:<br />
<br />
# SSH shell access to the FreeRunner through USB interface or WLAN.<br />
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)<br />
<br />
==== Prepare the SD card ====<br />
<br />
See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:<br />
<br />
<pre><br />
mount /dev/mmcblk0p1 /media/card<br />
mkdir /media/card/boot<br />
<br />
mkdir /media/mmcblk0p2<br />
mount /dev/mmcblk0p2 /media/mmcblk0p2<br />
</pre><br />
<br />
This will set you up properly for the installation of the root filesystem and the kernel in the steps below.<br />
<br />
==== Unpack the Qtopia Root Filesystem Image ====<br />
<br />
Download the [[Latest Images#Qtopia images|Qtopia Flash image]] to your Linux box and extract its contents:<br />
<br />
tar xzf qtopia-4.3.2-gta02-flash-*.tgz<br />
<br />
You should now have two files:<br />
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin<br />
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2<br />
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".<br />
<br />
==== Create a compressed tarball ====<br />
<br />
Next, tar up the root filesystem:<br />
<br />
# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .<br />
<br />
Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.<br />
<br />
==== Install the root filesystem ====<br />
<br />
Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:<br />
<br />
scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/<br />
<br />
Log in to your FreeRunner and unpack the root filesystem:<br />
<br />
<pre><br />
cd /media/mmcblk0p2<br />
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm -f /media/mmcblk0p2/boot/*<br />
</pre><br />
<br />
'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.<br />
<br />
==== Install the kernel ====<br />
<br />
From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.<br />
<br />
Some versions of u-boot look for <B>uImage</B> and not <b>uImage.bin</b> you may have to remove the .bin extension to get it to boot.<br />
<br />
<pre><br />
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin<br />
scp uImage.bin root@192.168.0.202:/media/card/boot/<br />
scp uImage.bin root@192.168.0.202:/media/card/<br />
</pre><br />
<br />
==== Tell Qtopia it is running from the SD Card ====<br />
<br />
Lorn Potter on the mailing lists pointed this out:<br />
<br />
Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.<br />
<br />
You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way<br />
<br />
Another user's solution to this is the following:<br />
<br />
Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf (the file path seems to have changed to /opt/Trolltech in newer versions)<br />
And change the [MountPoint0] section so it resembles this:<br />
<pre><br />
[MountPoint0]<br />
Name[] = SD Card<br />
Path=/dev/mmcblk0p1<br />
Removable = 0<br />
Applications = 0<br />
Documents = 0<br />
ContentDatabase = 0<br />
</pre><br />
<br />
=== Installation option 3: alternative procedure to install Qtopia on a microSD card ===<br />
<br />
As in option 2, the goal is to install Qtopia on a microSD card.<br />
We describe the complete procedure using:<br />
<br />
* Ubuntu 8.10<br />
* SanDisk microSD to USB adapter<br />
* Qt Extended 4.4.2 2008/10/31<br />
<br />
==== Format the microSD card ====<br />
<br />
The first step is to create an 8 MB partition for the kernel and use the remaining space for the root file system. Proceed as follows:<br />
<br />
Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.<br />
<br />
CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!<br />
<br />
<pre><br />
sudo umount /dev/sdb1<br />
<br />
sudo fdisk /dev/sdb<br />
</pre><br />
<br />
I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:<br />
<br />
<pre><br />
/dev/sdb1 1 9 9040+ 6 FAT16<br />
/dev/sdb2 10 984 982800 83 Linux<br />
</pre><br />
<br />
Save your partition table and quit fdisk. Format the partitions appropriately:<br />
<br />
<pre><br />
sudo mkfs.vfat /dev/sdb1<br />
sudo mkfs.ext3 /dev/sdb2<br />
</pre><br />
<br />
==== Download the latest Qt Extended ====<br />
<br />
Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:<br />
<br />
<pre><br />
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98<br />
tar -zxvf qtextended-4.4.2-gta02-flash.tgz<br />
</pre><br />
<br />
==== Copy the kernel image to the microSD card ====<br />
<br />
First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:<br />
<br />
<pre><br />
sudo mkdir /media/card<br />
sudo mount /dev/sdb1 /media/card<br />
sudo mkdir /media/card/boot<br />
</pre><br />
<br />
Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:<br />
<br />
<pre><br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin<br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage<br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin<br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage<br />
</pre><br />
<br />
Wait for data to be written to the microSD card and unmount the first partition:<br />
<br />
<pre><br />
sync<br />
sudo umount /dev/sdb1<br />
</pre><br />
<br />
==== Copy the jffs2 root file system to the microSD card ====<br />
<br />
That step is a bit complicated. First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:<br />
<br />
<pre><br />
sudo modprobe mtd <br />
sudo modprobe jffs2 <br />
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.<br />
sudo modprobe mtdchar <br />
sudo modprobe mtdblock<br />
</pre><br />
<br />
Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:<br />
<br />
<pre><br />
cat /proc/mtd<br />
dev: size erasesize name<br />
mtd0: 039a4000 00020000 "mtdram test device"<br />
</pre><br />
<br />
Now copy the jffs2 file system to the fake MTD device:<br />
<br />
<pre><br />
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0<br />
</pre><br />
<br />
Create a mount point, mount the fake MTD device, and check that the content seems right:<br />
<br />
<pre><br />
sudo mkdir /mnt/tmp<br />
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp<br />
ls /mnt/tmp<br />
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/<br />
boot/ etc/ lib/ mnt/ proc/ sys/ usr/<br />
</pre><br />
<br />
Mount the second partition of the microSD card and copy the root file system to it:<br />
copy root file system to sd card using tar<br />
<br />
<pre><br />
sudo mkdir /media/rootfs<br />
sudo mount /dev/sdb2 /media/rootfs<br />
cd /mnt/tmp<br />
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)<br />
</pre><br />
<br />
Warnings about "implausibly old time stamp" don't seem to cause any trouble.<br />
<br />
Use "sync" to make sure that all data is written to the microSD card:<br />
<br />
<pre><br />
sync<br />
</pre><br />
<br />
Inspect contents of second partition:<br />
<br />
<pre><br />
ls /media/rootfs<br />
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/<br />
boot/ etc/ lib/ mnt/ proc/ sys/ usr/<br />
</pre><br />
<br />
Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:<br />
<br />
<pre><br />
sudo rm -f /media/rootfs/boot/*<br />
</pre><br />
<br />
Wait for data to be written to the microSD card and unmount the second partition:<br />
<br />
<pre><br />
sync<br />
sudo umount /dev/sdb2<br />
</pre><br />
<br />
==== Test Qtopia ====<br />
<br />
Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into U-Boot, and select the option to boot from microSD card.<br />
<br />
=== Installation option 4: updating from source ===<br />
<br />
{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}<br />
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:<br />
<br />
==== Download files ====<br />
* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)<br />
<pre><br />
cd /<br />
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz<br />
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz<br />
</pre><br />
<br />
* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/<br />
<br />
Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/<br />
<br />
* once dowloaded untar it<br />
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre><br />
<br />
<br />
==== Build Qtopia ====<br />
* make a "build" dir<br />
<pre><br />
mkdir build<br />
cd build<br />
</pre><br />
<br />
* configure and make:<br />
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01<br />
make<br />
</pre><br />
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:<br />
<pre><br />
make install<br />
</pre><br />
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.<br />
<br />
For compiling qt-extended 4.4.2, you may need to use the following commands:<br />
<pre><br />
* cd build<br />
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt<br />
* bin/qbuild image<br />
</pre><br />
<br />
This forces building qt as well which resolved problems with the qbuild test using all the system ram.<br />
<br />
==== Booting into Qtopia ====<br />
<br />
Now shutdown the FreeRunner<br />
<br />
shutdown -h now<br />
<br />
Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])<br />
<br />
* Press and hold Power button<br />
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.<br />
* A boot menu will appear.<br />
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.<br />
<br />
Qtopia should now boot.<br />
<br />
'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run<br />
<br />
umount /dev/mmcblk0p2<br />
fsck.ext3.e2fsprogs /dev/mmcblk0p2<br />
<br />
This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.<br />
<br />
=== Internationalization ===<br />
<br />
Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.<br />
<br />
Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].<br />
<br />
=== Software packages feeds ===<br />
<br />
Installation of more software packages with the package manager tool found the Settings folder needs servers, which offer these packages, like<br />
<br />
* http://qtextended.org/packages/feed/4.4.1/neo (default)<br />
* ...<br />
<br />
Install packages into Qt extended through the package manager, which only allows packages via web servers, seems to be the only way at the moment.<br />
(No way to download a package seperately and install the file.)<br />
<br />
== Bugs ==<br />
<br />
See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).<br />
<br />
Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.<br />
<br />
=== Suspend /Resume ===<br />
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.<br />
<br />
=== Bugs in 4.4.1 ===<br />
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox<br />
* Timezone & time on latest Qt 4.4.1<br />
* The first item in a list is missing the top half<br />
<br />
=== Bugs in 4.4.2 ===<br />
* Cannot connect to a WPA protected WLAN, because wpa_supplicant of the previous connection is left running. Try a [http://www.qtsoftware.com/developer/task-tracker/index_html?method=entry&id=241864 fixed /opt/Trolltech/Qtopia/bin/lan-network script].<br />
<br />
== Links ==<br />
<br />
* [http://qtextended.org/ Qtextended.org]<br />
* [http://doc.trolltech.com/qtextended4.4/ Qt Extended Developer Resources]<br />
<br />
<br />
[[Category:Qtopia]]</div>Pnaullshttp://openmoko.org/wiki/Qtopia_/_Qt_Extended_on_FreeRunnerQtopia / Qt Extended on FreeRunner2009-05-13T03:23:45Z<p>Pnaulls: /* Current status */</p>
<hr />
<div>{{Languages|Qtopia_on_FreeRunner}}<br />
<br />
This page provides instructions on how to install Qtopia/Qt Extended (proper, not the [[ASU]] or [[QtopiaOnX11]] efforts) on the GTA02 (FreeRunner) phone. It is similar to the [[Qtopia on Neo1973]] page.<br />
<br />
__TOC__<br />
<br />
== Current status ==<br />
<br />
* The most recent version is [[Qt Extended Improved]].<br />
<br />
* On 3 March 2009 Qt software has discontinued Qt Extended. See http://www.qtsoftware.com/about/news/qt-software-discontinues-qt-extended for more details.<br />
<br />
* Qt software announced that has discontinued QT Extended as a standalone product, integrating it into QT.<br />
<br />
<br />
Check [http://wiki.openmoko.org/wiki/Qt_Extended_4.4.3 Qt_Extended_4.4.3] for more info on the latest (and final) release.<br />
<br />
On 31 October 2008, Trolltech released the [http://qtextended.org/modules/mydownloads/visit.php?lid=98 Qtopia ROM flash image containing the rootfs] for the Openmoko Neo FreeRunner (gta02) containing the Qtopia 4.4.2 release (GPL version). This runs on the [http://qtextended.org/modules/mydownloads/visit.php?lid=91 mwebster ROM flash image containing the kernel]. At release time, 4.4.2 & current mwester's kernel mismatched, please clarify the previous sentence. Hypnotize has released [http://lists.openmoko.org/pipermail/community/2008-November/035245.html Qt Extended 4.4.2 images for the Neo FreeRunner] that work better.<br />
<br />
This image can successfully make and receive calls and text messages. It can read all contacts from the SIM card (which the updated 2007.2 does not appear to be able to do). It contains apps that appear to be more stable than the ones found in the 2007.2 image. It has multiple input methods that appear to be more mature. It does have a webkit based web browser and an GPS "Mapping Demo" application.<br />
<br />
There are other third-party GPS applications available:<br />
* [http://blog.wolfman.com/articles/2008/08/27/porting-xgps-to-qtopia-for-the-freerunner xgps] (/!\ non-compatible with 4.4.x --[[User:Xc8|Xc8]] 22:28, 6 February 2009 (UTC))<br />
* [http://www.linux4.be/fr/roadmap.html RoadMap (experimental)] (! Not working on 4.4.2 --[[User:AlecTBM|AlecTBM]] 20:00 GMT +01:00 10 February 2009)<br />
<br />
([[TangoGPS]] does not work on QtExtended, because it depends upon an Xserver)<br />
<br />
You can find all the Qtopia images [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6 here] (including Qtextended/Qtopia 4.4 for FreeRunner and Neo1973!)<br />
<br />
'''What is in the latest release (QtExtended 4.4.2)?'''<br />
<br />
Qtopia 4.4 has been released with the name of [http://doc.trolltech.com/qtextended4.4/release-4-4-2.html QtExtended 4.4].<br />
* a [http://n2.nabble.com/qtopia-update-tp832851p832888.html browser] based on WebKit<br />
* [http://n2.nabble.com/-qtopia--rotate-screen--tp841805p841841.html screen rotation in the settings application] (so no automatic rotation)<br />
* [http://n2.nabble.com/Echo-issue-on-OM2008.08-potentially-solved-tp791642.html noise reduction]<br />
* GPS API<br />
* USB net/storage switching<br />
* GTalk support<br />
* [http://n2.nabble.com/forum/Permalink.jtp?root=841805&post=1083388&page=y better support for non-English languages in the keyboard]<br />
<br />
<br />
[http://www.qtsoftware.com/about/news/qt-software-discontinues-qt-extended Qt Extended will be discontinued as a stand-alone product] March 2009 after the release of version 4.4.3<br />
and selected features will be migrated into the Qt framework.<br />
<br />
== Installation ==<br />
<br />
=== Installation option 1: Flash Qtopia to FreeRunner ===<br />
<br />
Download the image mentioned above, then follow the instructions in the {{Main|Flashing the Neo FreeRunner}}<br />
<br />
=== Installation option 2: Install Qtopia on a microSD card ===<br />
<br />
Installation Requirements:<br />
<br />
# SSH shell access to the FreeRunner through USB interface or WLAN.<br />
# A Desktop Linux distro (to unpack the .jffs2 image, I ran Ubuntu under VMWare)<br />
<br />
==== Prepare the SD card ====<br />
<br />
See the [[Booting from SD#Prepare the SD card| Preparing the SD Card]] section of the [[Booting from SD]] page for partitioning and formatting instructions. After you complete the "Formatting the SD Card" steps, return here and execute the following:<br />
<br />
<pre><br />
mount /dev/mmcblk0p1 /media/card<br />
mkdir /media/card/boot<br />
<br />
mkdir /media/mmcblk0p2<br />
mount /dev/mmcblk0p2 /media/mmcblk0p2<br />
</pre><br />
<br />
This will set you up properly for the installation of the root filesystem and the kernel in the steps below.<br />
<br />
==== Unpack the Qtopia Root Filesystem Image ====<br />
<br />
Download the [[Latest Images#Qtopia images|Qtopia Flash image]] to your Linux box and extract its contents:<br />
<br />
tar xzf qtopia-4.3.2-gta02-flash-*.tgz<br />
<br />
You should now have two files:<br />
#uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin<br />
#qtopia-4.3.2-gta02-rootfs-07172049.jffs2<br />
Now, mount the root file system from the jffs2 using the commands found [[Userspace root image#Mounting the JFFS2 image on a loop back device (Block Memory MTD Emulation) |here]]. However, in the mount command, substitute the image filename for "/dev/mtdblock0".<br />
<br />
==== Create a compressed tarball ====<br />
<br />
Next, tar up the root filesystem:<br />
<br />
# tar czf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz -C <mountpoint> .<br />
<br />
Where ''<mountpoint>'' is the location where the jff2 filesystem was mounted. Note the space and the period after the mountpoint.<br />
<br />
==== Install the root filesystem ====<br />
<br />
Transfer this compressed tarball to the second partition of the MicroSD that is mounted on the FreeRunner:<br />
<br />
scp qtopia-4.3.2-gta02-rootfs-07172049.tar.gz root@192.168.0.202:/media/mmcblk0p2/<br />
<br />
Log in to your FreeRunner and unpack the root filesystem:<br />
<br />
<pre><br />
cd /media/mmcblk0p2<br />
tar xzf qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm qtopia-4.3.2-gta02-rootfs-07172049.tar.gz<br />
rm -f /media/mmcblk0p2/boot/*<br />
</pre><br />
<br />
'''''Note:''''' the last step removes the kernel image from the second partition. For some reason, U-Boot cannot find the uImage.bin file in the first partition if a kernel image exists in the second partition boot/ directory.<br />
<br />
==== Install the kernel ====<br />
<br />
From your Linux box, rename <tt>uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin</tt> to <tt>uImage.bin</tt> and copy it to the boot directory on the first partition of the MicroSD card. Depending on the version of U-Boot you have installed, this may not work. To prevent any possible issues, copy it to the <tt>/media/card</tt> directory as well. There is plenty of room on the first partition to have <tt>uImage.bin</tt> in both locations.<br />
<br />
Some versions of u-boot look for <B>uImage</B> and not <b>uImage.bin</b> you may have to remove the .bin extension to get it to boot.<br />
<br />
<pre><br />
mv uImage-2.6.24+git18+9c058ff0d2641df3c36fc3300acb72078d2c41d4-r0-om-gta02.bin uImage.bin<br />
scp uImage.bin root@192.168.0.202:/media/card/boot/<br />
scp uImage.bin root@192.168.0.202:/media/card/<br />
</pre><br />
<br />
==== Tell Qtopia it is running from the SD Card ====<br />
<br />
Lorn Potter on the mailing lists pointed this out:<br />
<br />
Qtopia was designed to be run from the root partition on a flash chip, not from a removable sd card.<br />
<br />
You would have to edit the etc/default/Trolltech/Storage.conf file to make it forget about the sd /dev node, to be able to run it this way<br />
<br />
Another user's solution to this is the following:<br />
<br />
Edit this file: /opt/Qtopia/etc/default/Trolltech/Storage.conf (the file path seems to have changed to /opt/Trolltech in newer versions)<br />
And change the [MountPoint0] section so it resembles this:<br />
<pre><br />
[MountPoint0]<br />
Name[] = SD Card<br />
Path=/dev/mmcblk0p1<br />
Removable = 0<br />
Applications = 0<br />
Documents = 0<br />
ContentDatabase = 0<br />
</pre><br />
<br />
=== Installation option 3: alternative procedure to install Qtopia on a microSD card ===<br />
<br />
As in option 2, the goal is to install Qtopia on a microSD card.<br />
We describe the complete procedure using:<br />
<br />
* Ubuntu 8.10<br />
* SanDisk microSD to USB adapter<br />
* Qt Extended 4.4.2 2008/10/31<br />
<br />
==== Format the microSD card ====<br />
<br />
The first step is to create an 8 MB partition for the kernel and use the remaining space for the root file system. Proceed as follows:<br />
<br />
Insert microSD card into adapter, and plug adapter into Ubuntu computer. If any partitions on the microSD card mount automatically, unmount them.<br />
<br />
CAUTION: Make sure you know which device your microSD card is. You don't want to perform these steps on your main hard disk!<br />
<br />
<pre><br />
sudo umount /dev/sdb1<br />
<br />
sudo fdisk /dev/sdb<br />
</pre><br />
<br />
I assume you know how to use fdisk. Delete any existing partitions, then create two new partitions, the first of size +8M, the second using all remaining space. Set the file system type of the first partition to FAT16 (type '6'). Your partition table should look like this:<br />
<br />
<pre><br />
/dev/sdb1 1 9 9040+ 6 FAT16<br />
/dev/sdb2 10 984 982800 83 Linux<br />
</pre><br />
<br />
Save your partition table and quit fdisk. Format the partitions appropriately:<br />
<br />
<pre><br />
sudo mkfs.vfat /dev/sdb1<br />
sudo mkfs.ext3 /dev/sdb2<br />
</pre><br />
<br />
==== Download the latest Qt Extended ====<br />
<br />
Visit [http://qtextended.org/modules/mydownloads/viewcat.php?cid=6:Qtopia] and get the appropriate file. The Qtopia ROM flash images contain both the file system and the kernel image:<br />
<br />
<pre><br />
wget http://qtextended.org/modules/mydownloads/visit.php?lid=98<br />
tar -zxvf qtextended-4.4.2-gta02-flash.tgz<br />
</pre><br />
<br />
==== Copy the kernel image to the microSD card ====<br />
<br />
First mount the first partition, which is the boot partition, of the microSD card, and make a /boot subdirectory:<br />
<br />
<pre><br />
sudo mkdir /media/card<br />
sudo mount /dev/sdb1 /media/card<br />
sudo mkdir /media/card/boot<br />
</pre><br />
<br />
Depending on your version of U-Boot, the kernel image might be expected at the root of the boot partition, or in the /boot directory. Also, the image file name might be expected to have a .bin extension, or not. We create all four variations:<br />
<br />
<pre><br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage.bin<br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/uImage<br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage.bin<br />
sudo cp testing-om-gta02-20081029.uImage.bin /media/card/boot/uImage<br />
</pre><br />
<br />
Wait for data to be written to the microSD card and unmount the first partition:<br />
<br />
<pre><br />
sync<br />
sudo umount /dev/sdb1<br />
</pre><br />
<br />
==== Copy the jffs2 root file system to the microSD card ====<br />
<br />
That step is a bit complicated. First we need to make a fake MTD device in RAM so that we can mount the jffs2 root file system:<br />
<br />
<pre><br />
sudo modprobe mtd <br />
sudo modprobe jffs2 <br />
sudo modprobe mtdram total_size=59024 # default is 4 MByte - set to max.<br />
sudo modprobe mtdchar <br />
sudo modprobe mtdblock<br />
</pre><br />
<br />
Next we're going to copy onto this fake device. Make sure there are no other MTD devices on your computer and change the device numbers below as necessary:<br />
<br />
<pre><br />
cat /proc/mtd<br />
dev: size erasesize name<br />
mtd0: 039a4000 00020000 "mtdram test device"<br />
</pre><br />
<br />
Now copy the jffs2 file system to the fake MTD device:<br />
<br />
<pre><br />
sudo dd if=qtextended-4.4.2-gta02-rootfs-10302135.jffs2 of=/dev/mtd0<br />
</pre><br />
<br />
Create a mount point, mount the fake MTD device, and check that the content seems right:<br />
<br />
<pre><br />
sudo mkdir /mnt/tmp<br />
sudo mount -t jffs2 /dev/mtdblock0 /mnt/tmp<br />
ls /mnt/tmp<br />
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/<br />
boot/ etc/ lib/ mnt/ proc/ sys/ usr/<br />
</pre><br />
<br />
Mount the second partition of the microSD card and copy the root file system to it:<br />
copy root file system to sd card using tar<br />
<br />
<pre><br />
sudo mkdir /media/rootfs<br />
sudo mount /dev/sdb2 /media/rootfs<br />
cd /mnt/tmp<br />
sudo tar -cf - . | (cd /media/rootfs && sudo tar -xpvf -)<br />
</pre><br />
<br />
Warnings about "implausibly old time stamp" don't seem to cause any trouble.<br />
<br />
Use "sync" to make sure that all data is written to the microSD card:<br />
<br />
<pre><br />
sync<br />
</pre><br />
<br />
Inspect contents of second partition:<br />
<br />
<pre><br />
ls /media/rootfs<br />
bin/ dev/ home/ media/ opt/ sbin/ tmp@ var/<br />
boot/ etc/ lib/ mnt/ proc/ sys/ usr/<br />
</pre><br />
<br />
Note: There was a report that some versions of U-Boot cannot find the kernel image file in the first partition if a kernel image exists in the second partition boot/ directory. I have not confirmed this but there is no need for it so it seems safest to delete it now:<br />
<br />
<pre><br />
sudo rm -f /media/rootfs/boot/*<br />
</pre><br />
<br />
Wait for data to be written to the microSD card and unmount the second partition:<br />
<br />
<pre><br />
sync<br />
sudo umount /dev/sdb2<br />
</pre><br />
<br />
==== Test Qtopia ====<br />
<br />
Remove the microSD card from the USB adapter, install it in the Neo FreeRunner, boot into U-Boot, and select the option to boot from microSD card.<br />
<br />
=== Installation option 4: updating from source ===<br />
<br />
{{note|This will upgrade only opt/Qtopia directory, you should use opkg update/upgrade for the rest}}<br />
Original Qtopia images (the distribution released by Trolltech, not ASU) are rarely released as a rootfs image, but the source code is often updated. If you want to reflash your OM with the latest version of Qtopia you might build it from sources. This has been explained in [http://lists.openmoko.org/pipermail/community/2008-August/024785.html this thread] of the community mailing list. Summing up:<br />
<br />
==== Download files ====<br />
* get the latest toolchain released by trolltech: http://www.qtopia.net/modules/mydownloads/singlefile.php?lid=38 and unzip it on your PC (as root)<br />
<pre><br />
cd /<br />
wget http://qtopia.net/downloads/neo/arm920t-eabi-ficgta01-toolchain.tgz<br />
tar xvzf arm920t-eabi-ficgta01-toolchain.tgz<br />
</pre><br />
<br />
* get the latest snapshot from trolltech: ftp://ftp.trolltech.com/qtopia/snapshots/<br />
<br />
Since qtopia was renamed in qtextended you could find the snapshots on http://qtextended.org/downloads/snapshots/<br />
<br />
* once dowloaded untar it<br />
<pre>tar xvzf qtopia-opensource-src-4.3.2-snapshot-20080806.tar.gz</pre><br />
<br />
<br />
==== Build Qtopia ====<br />
* make a "build" dir<br />
<pre><br />
mkdir build<br />
cd build<br />
</pre><br />
<br />
* configure and make:<br />
<pre>../qtopia-opensource-src-4.3.2-snapshot-20080806/configure -device ficgta01<br />
make<br />
</pre><br />
This will take some time (couple hours). Note that the option "-device ficgta01" should work for both neo and freerunner. Then:<br />
<pre><br />
make install<br />
</pre><br />
will make a root directory into the ''build'' directory. There you can find an ''image'' that directory should be copied to /opt/Qtopia of your phone with scp. once done restart qpe or whole phone.<br />
<br />
For compiling qt-extended 4.4.2, you may need to use the following commands:<br />
<pre><br />
* cd build<br />
* $QTOPIA_DEPOT_PATH/configure -device neo -verbose -build-qt -force-build-qt<br />
* bin/qbuild image<br />
</pre><br />
<br />
This forces building qt as well which resolved problems with the qbuild test using all the system ram.<br />
<br />
==== Booting into Qtopia ====<br />
<br />
Now shutdown the FreeRunner<br />
<br />
shutdown -h now<br />
<br />
Log into U-Boot in the NAND Flash to boot from the MicroSD card: (instructions from [[Booting the Neo FreeRunner]])<br />
<br />
* Press and hold Power button<br />
* Then while still pressing the Power button, press and hold AUX button for 5 to 8 seconds.<br />
* A boot menu will appear.<br />
* Press the AUX button to select "[[Boot from sd card|Boot from MicroSD]]" and then press the Power button to execute.<br />
<br />
Qtopia should now boot.<br />
<br />
'''''Note:''''' you may get a kernel panic which says that "optional features not supported". If this is the case, boot back into 2007.2 and run<br />
<br />
umount /dev/mmcblk0p2<br />
fsck.ext3.e2fsprogs /dev/mmcblk0p2<br />
<br />
This will clean up the file system and clear recovery flags in ext3 that ext2 does not support, then try booting from the MicroSD again.<br />
<br />
=== Internationalization ===<br />
<br />
Qtopia comes with support for German and American English, and users from other countries will find that Qtopia's predictive keyboard makes writing in another language near impossible. One way to disable the predictive keyboard is to simply replace /opt/Qtopia/etc/dict/en_US/common.dawg and words.dawg with empty files (after backing them up). Qtopia normally looks in these files for words to suggest, and if it doesn't find any words that fit, it simply shows what you actually wrote.<br />
<br />
Adding characters to the keyboard requires modifications to the source code, as described [http://www.qtopia.net/modules/newbb_plus/viewtopic.php?topic_id=512&forum=16 here].<br />
<br />
=== Software packages feeds ===<br />
<br />
Installation of more software packages with the package manager tool found the Settings folder needs servers, which offer these packages, like<br />
<br />
* http://qtextended.org/packages/feed/4.4.1/neo (default)<br />
* ...<br />
<br />
Install packages into Qt extended through the package manager, which only allows packages via web servers, seems to be the only way at the moment.<br />
(No way to download a package seperately and install the file.)<br />
<br />
== Bugs ==<br />
<br />
See [http://trolltech.org/developer/task-tracker/index_html?method=front Trolltech's tracker] ([http://trolltech.org/developer/task-tracker/index_html?method=advsearch&searchstr=&bugs=on&sugs=on&product=2&functionalarea=&versionfound=&versionfixed=&priority=-1&status=0&resolution=-1 Qtopia Tracker]).<br />
<br />
Bug reports should be sent to qt-bugs@trolltech.com or by web form at http://trolltech.com/bugreport-form.<br />
<br />
=== Suspend /Resume ===<br />
It seems that suspend/resume only works when the FreeRunner has been connected to a powersource (only a few seconds if sufficient). If you boot from battery, it will never suspend until you have plugged it in at least for a couple of seconds.<br />
<br />
=== Bugs in 4.4.1 ===<br />
* Boot and Shutdown Splash will not work because splash-write was not compiled into Busybox<br />
* Timezone & time on latest Qt 4.4.1<br />
* The first item in a list is missing the top half<br />
<br />
=== Bugs in 4.4.2 ===<br />
* Cannot connect to a WPA protected WLAN, because wpa_supplicant of the previous connection is left running. Try a [http://www.qtsoftware.com/developer/task-tracker/index_html?method=entry&id=241864 fixed /opt/Trolltech/Qtopia/bin/lan-network script].<br />
<br />
== Links ==<br />
<br />
* [http://qtextended.org/ Qtextended.org]<br />
* [http://doc.trolltech.com/qtextended4.4/ Qt Extended Developer Resources]<br />
<br />
<br />
[[Category:Qtopia]]</div>Pnaullshttp://openmoko.org/wiki/Talk:Main_PageTalk:Main Page2009-05-07T12:55:57Z<p>Pnaulls: </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)</div>Pnaullshttp://openmoko.org/wiki/User_talk:Robin7894User talk:Robin78942009-05-07T12:54:35Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Robin7894User talk:Robin78942009-05-05T16:14:30Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Edward2603User talk:Edward26032009-05-05T16:13:50Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Edward2603User talk:Edward26032009-05-02T13:59:37Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Robin7894User talk:Robin78942009-04-19T00:46:28Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Edward2603User talk:Edward26032009-04-19T00:46:08Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Robin7894User talk:Robin78942009-04-10T13:39:37Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/User_talk:Edward2603User talk:Edward26032009-04-10T02:40:37Z<p>Pnaulls: Removing all content from page</p>
<hr />
<div></div>Pnaullshttp://openmoko.org/wiki/Kernel-plansKernel-plans2009-04-07T02:09:23Z<p>Pnaulls: Kernel-plans moved to Kernel Plans: Less odd title</p>
<hr />
<div>#REDIRECT [[Kernel Plans]]</div>Pnaullshttp://openmoko.org/wiki/Kernel_PlansKernel Plans2009-04-07T02:09:23Z<p>Pnaulls: Kernel-plans moved to Kernel Plans: Less odd title</p>
<hr />
<div>This document explains the current kernel plan for the GTA01/GTA02 kernel. The idea is to share the motivations behind the actual decisions. This is a draft, and the relevant suggestions will be incorporated into it.<br />
<br />
We would like to try this model for one or two months and if we find we are doing something wrong we will update the plans.<br />
<br />
== Patch review process ==<br />
<br />
If the patch has not issues that we can tell and it is relevant it will be applied. If we can tell it is a good patch right away or that it is a critical fix we will just apply the patch.<br />
<br />
Otherwise we will allow for two days before applying non-trivial patches to allow for community feedback and for feedback from subsystem maintainers. In the ideal case we would get ACKs from other developers (like "i like this patch") but we don't know if we can count on this.<br />
<br />
<br />
<br />
== Use tags and not forks for stable kernels ==<br />
<br />
We hope that developers actually care about the development branch. If they care, they will helps us reject patches that will likely cause trouble because it will break things. We will also get more testing.<br />
<br />
We will tag stable kernels in the repository.<br />
<br />
We know that people like forks and code that does not change often, but the linear model is working with upstream kernel (with a lot more people involved of course).<br />
<br />
We could fork the current Andy-tracking into a stable kernel. But, should we really do it? People could fork a stable tree and cherry-pick changes.<br />
<br />
== Upstream Linux kernel ==<br />
<br />
We should have very basic GTA02 support upstream soon. Once we get to reach this milestone we will check what drivers can be included.<br />
<br />
== Issues to solve ==<br />
<br />
=== Define how to keep track of the upstream kernel ===<br />
<br />
How to up-level the kernel to latest upstream version? (We can delay this decision for a few days).<br />
<br />
=== Patchwork ===<br />
<br />
We have a patchwork installation ( http://patchwork.openmoko.org ) requested by Angus but it still have some issues. It would be nice to use it in the future.<br />
<br />
See:<br />
<br />
* http://ozlabs.org/~jk/projects/patchwork/ (Patchwork)<br />
* http://patchwork.ozlabs.org (Patchwork in use)</div>Pnaullshttp://openmoko.org/wiki/User_talk:WowgoldgateUser talk:Wowgoldgate2009-04-01T03:49:26Z<p>Pnaulls: Replacing page with '{{Delete|spam|--Benjamin}}'</p>
<hr />
<div>{{Delete|spam|--[[User:Benjamin|Benjamin]]}}</div>Pnaullshttp://openmoko.org/wiki/Om_2008_InstallerOm 2008 Installer2009-03-30T04:29:09Z<p>Pnaulls: /* How to add a Repository ? */</p>
<hr />
<div>{{Om 2008.8}}<br />
<br />
==Introduction==<br />
The Openmoko Installer (Codename: [http://code.google.com/p/om-assassin/ Assassin]) is a tool for ''installing'', ''updating'' and ''uninstalling'' programs on your Neo. <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 />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:Install.png|200px|thumb|categories]]<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:Install1.png|200px|thumb|choose program]]<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:Installer4.png|200px|thumb|install application]]<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:Om2008 installer2.png|200px|thumb|install application]]<br />
|}<br />
<br />
==Install an Application ==<br />
'''Installer''' needs an internet connection to install applications for the repositories. This can be done via WiFi (currently unstable), [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB], [[GPRS]] or [[How_to_use_bluetooth_to_transfer_data_between_Neo_and_Desk-top|Bluetooth]].<br />
<br />
<br />
'''[1]''' Make sure you are connected to the internet and launch '''Installer'''. <br />
<br />
'''[2]''' At launch, '''Installer''' will initially refresh a list of installable programs. After refresh is complete, press the '''INSTALL''' button from the bottom bar to view a list of Categories. This is also the default page of the Installer application.<br />
<br />
'''[3]''' Select a Category from the category list, then select a package to install.<br />
<br />
'''[4]''' In the package information page, press the image box and confirm to begin.<br />
<br />
'''[5]''' Once the progress bar shows '''Done''', you will return to the Installer default page. Installation is then complete.<br />
<br />
* To ''update'' or ''uninstall'' packages, simply replace step '''[2]''' with the desired function '''UPDATE''' or '''UNINSTALL''' and repeat steps '''[3]''' through '''[5]'''.<br />
<br />
== How to add a Repository ? ==<br />
<br />
Adding a repository allows the package manager to install softwares beyond those included in the original distribution. More power, but also more risk of breakage. Never add feeds which are not for your installed distribution base. If you don't want to add a repository, you can still try to install an application with:<br />
<br />
opkg url_to_app.ipk<br />
<br />
The community-repository is installed by default in [[Om2008.8 | Om 2008.8]]. Others are listed in the [[Users Repositories]] page. To add a feed, create a file named (for example) 'community-repos.conf' in the directory '/etc/opkg' containing a src (or src/gz to pull the gzipped package list) directive like:<br />
<br />
<nowiki>src community-repos http://downloads.openmoko.org/repository/Multiverse/</nowiki><br />
<br />
Changes to the list of repositories made in '/etc/opkg' will be taken into account when the list of package is refreshed by:<br />
<br />
opkg update<br />
<br />
Another way to add repositories is to use the package manager itself and install a 'repository package'. Given that no other repository is proposed this way yet, the status of this functionality is unclear at present. Please edit this paragraph if you have more information.<br />
<br />
== Features ==<br />
* '''Installer''' is a specialized GUI front-end of [http://packagekit.org/ Packagekit] over DBus interface.<br />
<br />
* '''Installer''' should be run with stable network conditions and power supply. Once '''Installer''' is launched, it actively tries to connect to installed repositories. Timeout will make it unresponsive if the network condition is not stable. If you do not have access to WiFi, a [http://svn.openmoko.org/developers/tick/Test_env_script_GTA02A5/setneo USB] connection is recommended.<br />
<br />
* '''Installer''' refreshes the package meta-data every 2 days.<br />
<br />
* The default Packagekit backend on Neo is [[opkg]], but it is not restricted to opkg. <br />
<br />
* You can also talk with Packagekit through DBus.<br />
<br />
* '''Installer''' will launch packagekitd automatically, which will lock the libopkg to avoid synchronization trouble. Normally, the packagekitd terminates itself after about 5 minutes. If you want to use 'opkg', you may terminate '''Installer''' and:<br />
<br />
killall packagekitd<br />
<br />
== See also ==<br />
[1] Installer project - http://code.google.com/p/om-assassin/<br />
<br />
[2] Packagekit project - http://packagekit.org/<br />
<br />
[3] Opkg package management - [[Opkg]]<br />
<br />
[4] List of [[Users Repositories]]<br />
<br />
[[Category:Settings Applications]]<br />
[[Category:Om 2008.8]]</div>Pnaullshttp://openmoko.org/wiki/OMViewOMView2009-03-30T04:26:33Z<p>Pnaulls: /* Download and installation */</p>
<hr />
<div>{{application|OMView}}<br />
[[Image:omview_thumbs.png|thumb]]<br />
<br />
<br />
== Overview ==<br />
OMView is a simple image viewer for the openmoko platform. It supports touchscreen gestures, thumbnail view and raw files. It is intended to be lightweight, fast and easy to use. It depends on the [http://www.enlightenment.org/ EFL].<br />
The Project is hosted on [http://projects.openmoko.org/projects/omview/ projects.openmoko.org].<br />
<br />
== Download and installation ==<br />
The Viewer is now available in the [[Community Repository]] which means you can use the graphical installer on [[Om2008.8 | Om 2008.8]] and you don't need to update it by hand:<br />
<br />
opkg install omview<br />
<br />
If you don't have the community repository enabled or you want the most recent version you can install from web:<br />
<br />
opkg install http://projects.openmoko.org/frs/download.php/405/omview_r32_armv4t.ipk<br />
<br />
In post r27 releases, the theme is included in the ipk, no need to download it extra.<br />
<br />
== Usage ==<br />
<br />
[[Image:omview_files.png|thumb]]<br />
* Omview has three modes: directory view, thumbnail view, and fullscreen image view.<br />
* It understands five touchpad gestures: right, up, left, down, click. To use these just move your finger or stylus for at least 50px in one direction.<br />
* In fullscreen view images are automatically scaled and rotated. Not by exif orientation data but only by image dimensions, so that an image takes as much space on the screen while beeing fully visible. This means landscape images are rotated, portait images are left the way they are.<br />
<br />
Directory and thumbnail view always show 6 items at the same time with the other items beeing on the previous/next pages. The statusbar on the bottom shows the path and below the subdirectory count/file count/page<br />
{| border=1 cellspacing=0 cellpadding=4<br />
!Gesture<br />
!Directory View<br />
!Thumbnail View<br />
!Fullscreen<br />
|-<br />
|left<br />
|previous page<br />
|previous page<br />
|previous image<br />
|-<br />
|right<br />
|next page<br />
|next page<br />
|next image<br />
|-<br />
|up<br />
|change to parent directory<br />
|change to directory view<br />
|change to thumbnail view<br />
|-<br />
|down<br />
|change to thumbnail view<br />
|change to fullscreen view<br />
|<br />
|-<br />
|click<br />
|change to clicked directory<br />
|show clicked image<br />
|toggle 1:1 zoom<br />
|}<br />
<br />
== Known Bugs and Limitations==<br />
<br />
* thumbnail creation is slower than image viewing and takes much space (~ 100K per image) to free this space just delete .thumbnail folder in the home dir.<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[OMView]]|<br />
Description=Fast and simple image viewer. |<br />
Screenshot=Omview thumbs.png|<br />
Homepage=http://projects.openmoko.org/projects/omview/|<br />
TestedOn=Om 2008.8|<br />
PackageName=omview<br />
}}<br />
</onlyinclude><br />
<br />
[[Category:Graphics Applications]]</div>Pnaullshttp://openmoko.org/wiki/Video_PlayerVideo Player2009-03-30T03:32:19Z<p>Pnaulls: /* Mode Switching */</p>
<hr />
<div>Not a proper 'app' page, just an overview<br />
<br />
=FreeRunner=<br />
It plays mpeg-4 320x240 stretched fullscreen, however other formats will require transcoding.<br />
<br />
==Playback==<br />
The default media player doesn't seem to handle video very well, but mplayer does OK.<br />
<br />
=== Using standard Mplayer ===<br />
It can be installed with the following command:<br />
opkg install mplayer<br />
<br />
=== Using the Glamo XV acceleration ===<br />
This only applies to GTA02 hardware which uses Glamo graphical chip. <br />
<br>First of all you'll need special version of Mplayer with glamo support.<br />
<br>You can download it from here: http://downloads.tuxfamily.org/3v1deb/openmoko/mplayer-glamo.tar.bz2<br />
<br>Just copy files inside the archive with:<br />
<pre><br />
cp mplayer /usr/bin/mplayer<br />
cp input.conf ~/.mplayer/input.conf<br />
</pre><br />
<br />
File shoud be preencoded with something like this:<br />
<pre>mencoder file_to_encode.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 \<br />
-vf scale=320:240,eq2=1.2:0.5:-0.25,rotate=2 -oac mp3lame -ofps 15 -lameopts br=64:cbr \<br />
-o file_for_openmoko</pre><br />
<br />
It can be played with:<br />
<pre>mplayer -vo xover:glamo -fs your_file.avi</pre><br />
<br />
Please refer to: http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ for more details.<br />
<br />
* I gave a try to the above how-to and it doesn't work on my FR. Playing the preencoded movie just displays a green screen with garbage on the top. -- [[User:Pini|Pini]] Sun Dec 7 13:08:42 UTC 2008<br />
<br />
=== Controlling MPlayer from the Touchscreen ===<br />
Create a file in /home/root/.mplayer/input.conf with this content:<br />
# Freerunner Optimizations<br />
MOUSE_BTN0 vo_fullscreen<br />
MOUSE_BTN0_DBL q<br />
Now, you can toggle the fullscreen by tapping the screen and exit from mplayer by touble-tapping the LCD.<br />
Accelerometers or hardware buttons could help more.<br />
<br />
=== Playback helper script ===<br />
<br />
Create a script named 'vidplay' in your home directory with the following commands:<br />
#!/bin/sh<br />
xrandr -display :0 --output default --mode 240x320<br />
mplayer -vo fbdev "$1" > /dev/null<br />
xrandr -display :0 --output default --mode 480x640<br />
reset<br />
<br />
Make the script executable:<br />
chmod 755 /home/root/vidplay<br />
<br />
Known issues with this approach:<br />
*The output isn't in a proper window, so background stuff sometimes flickers through.<br />
*When done on the local terminal the keyboard is obscured so you can't exit. SSH works quite well.<br />
*240x320 mode has some quirks:<br />
**The gamma/brightness/contrast is weird. Encoding adjustments into the media is a workaround.<br />
**Vertical banding (as seen in landscape position) is quite noticeable.<br />
*Using CTRL-C to exit vidplay doesn't reset the screen; use 'q' instead.<br />
<br />
Despite these issues, it proves that the horsepower is there and it can be done.<br />
<br />
=== Another derivated method : works like a charm for me ! ===<br />
No ssh, no xrandr, no script needed, juste mplayer and qwerty keyboard :<br />
Like it's said in the "Getting started with FreeRunner" wiki page, you have to install the full qwerty keyboard, see [http://www.ginguppin.de/node/15 these instructions].<br />
After that, you can go to Terminal and type :<br />
mplayer vid/my_video.avi<br />
Mplayer starts in full screen, if your video is optimized like below 240x320 it's work like a charm and to quit just use the power button.<br />
<br />
Only issue : You can't forward/backward/pause...<br />
<br />
==Example - Big Buck Bunny==<br />
===PC===<br />
Download the source (no need to start with the giant full resolution version)<br />
<br />
cd /tmp<br />
wget http://proyectos.pixelamigo.com/open/movies/BigBuckBunny/unofficial_PSP/big_buck_bunny_480p_AVC_FW33.mp4<br />
<br />
Test the video filter settings (-vf crop=...) often omitting the last "rotate=2" (Optional, but recommended for long videos).<br />
<br />
mplayer big_buck_bunny_480p_AVC_FW33.mp4 -vf crop=720:480:-1:-1,scale=320:-2,rotate=2 -zoom<br />
<br />
Transcode it:<br />
<br />
mencoder big_buck_bunny_480p_AVC_FW33.mp4 -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 \<br />
-vf crop=720:480:0:0,scale=320:-2,eq2=1.2:0.5:-0.25,rotate=2 -oac mp3lame -lameopts br=64:cbr \<br />
-o big_buck_bunny_320.avi<br />
<br />
or if it doesn't work (for me the image and the colours aren't ok) replace scale=320:-2 by scale=320:240<br />
<br />
=== FreeRunner===<br />
Transfer the resulting 27M file from the PC to the FreeRunner's MicroSD card<br />
scp user@192.168.0.200:/tmp/big_buck_bunny_320.avi /media/card<br />
<br />
Play it<br />
/home/root/vidplay /media/card/big_buck_bunny_320.avi<br />
<br />
==Other Info==<br />
<br />
To rotate the screen:<br />
xrandr -o 0<br />
xrandr -o 1<br />
<br />
=Neo1973=<br />
<br />
Video is problematic on [[Neo 1973]].<br />
<br />
On the minus side.<br />
*The CPU is certainly not fast enough to decode 480*640 video.<br />
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.<br />
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.<br />
However.<br />
<br />
On the positive side.<br />
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.<br />
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.<br />
*If not, then it almost certainly will be possible at 12fps.<br />
<br />
==Mode Switching==<br />
For switching between QVGA and VGA mode do the following with a compatible kernel:<br />
<br />
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga<br />
<br />
vice versa:<br />
<br />
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3<br />
<br />
Taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html<br />
<br />
To avoid console blanking type:<br />
<br />
echo -e '\033[9;0]' > /dev/ttyX<br />
<br />
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.<br />
<br />
To avoid kernel output in vt do<br />
<br />
echo 0 > /proc/sys/kernel/printk<br />
<br />
==User Reports==<br />
From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].<br />
<br />
400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.<br />
<br />
With sound, this drops to 18fps.<br />
<br />
There are optimisations for mplayer that look promising to get 25fps with sound.<br />
<br />
==Playback using 480x640 / 640x480==<br />
<br />
To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:<br />
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32<br />
<br />
Also working okay:<br />
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 352 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=200:abitrate=32<br />
<br />
You can playback the file using:<br />
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi><br />
<br />
You may also want to use:<br />
-autosync 30 -vf scale -zoom -xy 640 -vf rotate=1<br />
<br />
=Transcoding=<br />
To make your videos/DVDs compatible use mencoder like this:<br />
Find out the -vf cropping parameters with<br />
mplayer input.avi -vf cropdetect<br />
let it run a few seconds and insert the given cropping values into this command<br />
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi<br />
To encode a DVD first find out the -vf cropping parameters with<br />
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000<br />
let it run a few seconds and insert the given cropping values into this command<br />
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi<br />
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.<br />
<br />
=Frontend=<br />
==gnome-mplayer==<br />
'''Source Code released: No'''<br />
<br />
As a nice GUI gnome-mplayer can be recommended.<br />
<br />
On Debian you can install it from repository:<br />
# apt-get install gnome-mplayer<br />
<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Video Player|mplayer]]|<br />
Description=The popular command line video player.|<br />
Screenshot=Mplayer.png|<br />
Homepage=http://www.mplayerhq.hu|<br />
<br />
TestedOn=Om 2008.8 (default repository)|<br />
PackageName=mplayer|<br />
Source Code released=No|<br />
<br />
}}<br />
</onlyinclude><br />
<br />
== DeforaOS Player ==<br />
'''Source Code released: Yes'''<br />
<br />
It provides another GUI to mplayer.<br />
<br />
It was released first there:<br />
http://people.defora.org/~khorben/share/Openmoko/deforaos-player_0.1.0_armv4t.ipk<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[DeforaOS Player|deforaos-player]]|<br />
Description=The DeforaOS media player, a frontend to mplayer|<br />
Screenshot=Player.png|<br />
Homepage=http://www.defora.org/os/project/display/336/Player|<br />
<br />
TestedOn=Om 2008.8|<br />
PackageName=deforaos-player|<br />
Source Code released=Yes|<br />
<br />
}}<br />
</onlyinclude><br />
<br />
[[Category:Video Applications]]<br />
[[Category:Debian]]<br />
[[Category:Om 2008.8]]</div>Pnaullshttp://openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunnerGetting Started with your Neo FreeRunner2009-03-25T02:28:34Z<p>Pnaulls: </p>
<hr />
<div>{{Languages|Getting Started with your Neo FreeRunner}}<br />
<br />
{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; background:#eeeeee; width:100%;floating="center"; "<br />
! style="background:#fcfcfc; width:75% " |<br />
<p align="left"><br />
Thank you for purchasing this Developer release of Neo FreeRunner. The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of Openmoko. This guide will help you get to know your Neo FreeRunner and how to start using your Neo FreeRunner.</p><br />
<br />
<p align="left"><br />
Some Frequently Asked Questions for new owners are featured in the [[FAQ#Getting_Started_with_your_Neo_FreeRunner|FAQ]].<br />
</p><br />
<br />
! style="background:#fcfcfc; width:25% " |<br />
[[Image:Freerunner box.png|200px|thumb|Neo FreeRunner Package]]<br />
|}<br />
{{Neo FreeRunner Menu}}<br />
<br />
== Package Contents ==<br />
<br />
[[Image:Openmokset.jpg|left|400px|thumb|Inside the package]]<br />
<br /><br />
: [[Image:Circle2.gif|10px]] Neo FreeRunner<br />
: [[Image:Circle2.gif|10px]] Stylus<br />
: [[Image:Circle2.gif|10px]] Battery<br />
: [[Image:Circle2.gif|10px]] Charger<br />
: [[Image:Circle2.gif|10px]] USB Cable (A -> Mini-B 5-pole)<br />
: [[Image:Circle2.gif|10px]] [[Thank You green card]]<br />
<div style="clear: both">&nbsp;</div><br />
<br />
{{Note|<br />
== Get the source code == <br />
The software included in this product contains copyrighted software that is licensed under the [http://downloads.openmoko.org/sources/Om2008.9-Lite.iso GPL]. A complete corresponding source code or CD-ROM ISO image with the GPL license is available for download [http://downloads.openmoko.org/sources/Om2008.9-Lite.iso here]. You may also obtain the same corresponding CD-ROM by sending a money order or check for $10 to any one of our [http://downloads.openmoko.org/sources/Om2008.9-Lite.iso distributors].<br />
<br />
Please write “source for Neo FreeRunner ” in the memo line of your payment.<br />
}}<br />
<br />
== Setting up the hardware, getting to know the Neo FreeRunner physically ==<br />
<br />
<br />
<br />
===Installing the Micro-SD card, the SIM card, and the Battery ===<br />
<br />
[[Image:Circle2.gif|10px]] Remove the rear cover of the Neo FreeRunner by first holding the Neo FreeRunner on the side and then use your fingernail to prise off the rear cover at the slot on top of the device.<br />
<br />
<table width="80%" style="clear: both; border: 1px solid #ffffff; border-collapse: collapse; padding: 0.2em; margin: 0; font-size: 100%; margin: 0 1px;"><br />
<tr valign="top" style="background: #ffffff"><br />
<td style="width: 50%; white-space: nowrap; padding: 4px 1em 0 0.5em; border-right: 1px solid #ffffff;">[[Image:menu13.jpg|233px|thumb|Open the case like this.|center]]</td><br />
<td style="padding: 1px 1em 0; background: #ffffff;">[[Image:menu14.jpg|250px|thumb|Opening !|center]]</td><br />
</tr><br />
</table><br />
<br />
<br />
[[Image:Circle2.gif|10px]] Now you should be able to locate the combined SIM and Micro-SD card holder at the bottom of the battery compartment.<br />
<br />
[[Image:Circle2.gif|10px]] Unlock the SIM card holder by sliding the metal clip down, towards the USB socket, with your fingernail. Use caution, as these parts are delicate and could be damaged by forcing them in the wrong direction.<br />
<br />
<br />
[[Image:menu11.jpg|260px|thumb|Put the SIM card and SD card here.|center]]<br />
<br />
[[Image:Circle2.gif|10px]] Lift up on the SIM card holder.<br />
<br />
[[Image:Circle2.gif|10px]] The Micro-SD card holder is held in place by a latch on either side. It is easiest to open the Micro-SD card holder by releasing these latches one at a time rather than by lifting from the middle, as lifting from the middle tends to increase the latching pressure. A small screwdriver or knife can be used for this.<br />
<br />
[[Image:Circle2.gif|10px]] Insert the Micro-SD card into the Micro-SD card holder. Note that on the inside of metal part of the holder there are little holding tabs for the card. Slide the card in these holders (on the metal part) before closing the card holder. Note that the electrical contacts should face down and towards the edge of the Neo FreeRunner.<br />
<br />
[[Image:Circle2.gif|10px]] Close the Micro-SD card holder, making sure that both latches of the holder are securely fastened.<br />
<br />
[[Image:Circle2.gif|10px]] Insert the SIM card into the SIM card holder, taking care to slide inside the two metal tabs in the cover. Note that the electrical contacts should face down and that the cut corner should be closest to the external GPS Antenna Socket.<br />
<br />
[[Image:Circle2.gif|10px]] Close the SIM card holder and lock it by sliding the metal clip towards the external GPS Antenna Socket on the FreeRunner.<br />
<br />
[[Image:FR_SIM_SD_open.jpg|457px|thumb|SIM and SD holders open, with cards in place|center]]<br />
<br />
[[Image:Circle2.gif|10px]] Insert the battery into the battery compartment, aligning the electrical contacts on the battery with the electrical contacts in the battery compartment. Insert the side with the electrical contacts first.<br />
<br />
[[Image:Circle2.gif|10px]] Replace the rear cover on the FreeRunner.<br />
<br />
<br />
<br />
{| class="wikitable" style="background#00CC00;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #00CC00; float:right; margin: 0 0 1em 1em;"<br />
! style="background:#00cc00;border-left:1px solid white;border-right:5px solid white;border-top:0px solid white; border:1px solid #00CC00;" |<font color=white>Tips</font><br />
|-<br />
!style="background:#ffffff;border-left:1px solid white;border-right:1px solid white;border-top:0px solid white; border:1px solid #FFFFff;" |<br />
<div align=left><br />
[http://video.google.de/videoplay?docid=-8343770443102960945 A short video] is also available. It was shot using the previous version of the Neo, but the installation procedure remains the same.<br />
</div><br />
<br />
|}<br />
<br />
<br />
<br />
===Charging the Neo FreeRunner===<br />
<br />
Before using the Neo FreeRunner for the first time, you should charge the battery completely. The battery can be charged using the provided charger at 1000mA or from a powered USB port capable of providing 500mA worth of current. Most computers will be able to charge the FreeRunner without any problems.<br />
<br />
Neo FreeRunner '''does NOT charge when powered off''', so be sure to turn it on and allow it to boot all the way to the GUI (Graphical User Interface). This should happen automatically when you plug in USB power, either from a computer or the provided charger.<br />
<br />
Although the provided charger is rated at 2A, the maximum charge rate of the Neo FreeRunner is 1A, and thus the charge rate with the charger is less than the charger capacity.<br />
<br />
The provided charger includes three "national" plugs. The default is North America, with alternative U.K (3 square pins) and Euro (two round pins) adapters. To install the alternative power adapters, depress the latch in the cover (on the opposite side of the charger from the product information label) and slide the cover outward. Note that the two North American pins do not come out; the other adapters slide over them, and snap into place. The two-pin Euro adapter is removed in the same way as the cover. The three-pin U.K. adapter is removed by '''gently''' pressing the dummy ground pin (black) '''toward the end of the adapter with the cord''' and then sliding it off the adapter.<br />
<br />
Charging an empty battery at 100mA takes 12~15 hours, at 500mA takes 2,5~3,5 hours, and at 1000mA takes 1.5~2.5 hours. (90%~100%) [to be confirmed]<br />
<br />
{{Note|See [[Neo_FreeRunner_Hardware_Issues|Neo FreeRunner Hardware Issues]] about not allowing the battery to discharge completely.}}<br />
<br />
===Buttons and connectors===<br />
<br />
<table width="80%" style="clear: both; border-collapse: collapse" valign="top"><br />
<tr><br />
<td style="width: 25px">&nbsp;</td><br />
<td style="width: 370px">[[Image:menu9.jpg|370px|thumb|Power Button, USB and external GPS Antenna (left to right)|center]]</td><br />
<td style="width: 25px">&nbsp;</td><br />
<td style="width: 370px">[[Image:menu8.jpg|370px|thumb|AUX Button and phone jack (left to right)|center]]</td><br />
</tr><br />
<tr><br />
<td></td><br />
<td>'''Power'''<br />
Tapping the power button exits the current application.<br />
<br />
Holding the power button brings up a menu allowing you to:<br />
* Power on and off the GPS, wifi, GSM, and bluetooth antennae<br />
* Change power management mode to:<br />
** Dim first then lock<br />
** Dim only, don't lock<br />
** Disabled<br />
* Lock the screen<br />
* Shutdown the device.</td><br />
<td></td><br />
<td>'''Aux'''<br />
Tapping the Aux button hides or shows the currently running application.<br />
<br />
Holding the Aux button brings up a menu allowing you to:<br />
<br />
* Hide and show the title bar (Fullscreen toggle)<br />
* Alternate wide or tall display modes (Swap Orientation)<br />
* Save the content of the screen as an image file (Screenshot)<br />
</td><br />
</tr><br />
</table><br />
<br />
<br />
'''Booting'''<br />
<br />
[[Booting the Neo FreeRunner]] takes about 2 minutes overall, so patience is in order. The longest step comes after the Linux boot messages in very small fonts have scrolled by, at the graphical "openmoko" sunrise page.<br />
<br />
'''Phone Jack'''<br />
<br />
The phone jack is a 2.5mm connector with four contacts: stereo + MIC. It is compatible with the headsets used by Motorola smartphones (A780,A1200, ...) and the V-360.<br />
<br />
More information on [[Headset]] page.<br />
<br />
===Unlocking the screen===<br />
<br />
When the screen is locked, you should see a Matrix-style green graphic with the Openmoko symbol in the middle of the bottom of the screen along with lock and unlock symbols. If you drag the Openmoko symbol to the unlock symbol at the top then the screen will become unlocked.<br />
<br />
===Identifying which revision you have===<br />
You will want to determine which revision of the phone you have<br />
<br />
* remember your date code, the bottom of your shipping box should have a sticker stating it.<br />
* read [[Finding_hardware_revision]]<br />
<br />
These two are important, as they allow you to know which image is flashed on you phone at the factory (c.f. [[Distributions]] and [[Neo_FreeRunner_Hardware#History]]).<br />
<br />
== Image Issue==<br />
<br />
Because the software changes so rapidly and the phones were imaged during mass production, we don't ship the newest image with phones. <br />
There are two different kinds of images ship as default images. <br />
<br />
1. [[Om 2007.2]]<br />
<br />
2. [[Om 2008.9]]<br />
<br />
<br />
But according to the [[FAQ]] and [[Distributions]] pages, all phones ship with [[Om 2007.2]]. This distribution is no longer supported, so once you get your feet wet, you'll probably want to switch to something else.<br />
<br />
=For Om 2007.2=<br />
<br />
==Navigating menus and applications==<br />
====Today Page====<br />
<br />
[[Image:Todaypage_reduced_true.png|200px|right]] Openmoko starts by displaying the "Today" page, which is your home page. Icons in the top row indicate the status of the phone. The bottom row consists of three tabs. The tab with a house on the left leads to the "Today" page you're viewing now. The central tab leads to the "Launch Task" page, which is the main menu used to start applications. The tab with gears on the right leads to the "Running Tasks" page, which is used to deal with currently open windows and applications.<br />
<br />
<br clear=all /><br />
<br />
[[Image:Todaypage_reduced_false.png|right|200px|]] The "Today" page is empty, as shown above, when you first start Openmoko. We explain below how to turn on the "full view", displayed to the right. In the full view, a second row of icons give quick links to commonly-used applications such as the dialer, the adressbook, mailbox and calendar. The main body of the screen displays a clock and other useful information.<br />
<br />
See [[Today/2007.2]] for more information about the Today page and customization.<br />
<br />
<br clear=all /><br />
<br />
====Launch Task Page====<br />
<br />
{{stub}}<br />
<br />
[[Image:LaunchTasks.png|right|200px]] This page displays a menu of available applications. You may choose a category of applications to display to simplify the screen, or choose to display them all.<br />
<br />
Current categories are [PIM Suite], [[Om_2007.2_Applications|Applications]], [[Games/Om 2007.2|Games]], Utilities, and All.<br />
<br />
<br clear=all /><br />
<br />
====Running Tasks Page====<br />
<br />
{{stub}}<br />
<br />
[[Image:RunningTasks.png|right|200px]] This page displays currently-running tasks. Any individual task may be terminated by selecting it and then clicking on the garbage-can icon to close it. All tasks may be terminated by clicking on any one of them and then clicking on the "folder" icon in the upper right (expect this to change in future releases). Any task may be rejoined by selecting it and then selecting the "return" icon at the middle top.<br />
<br />
<br clear=all /><br />
<br />
====Exiting from and switching to an Application====<br />
<br />
Any time an application is running, you can simply click the device's power button and the application will exit, returning you to the Today page.<br />
<br />
Alternatively, you can cycle through active applications using the AUX button<br />
<br />
Clicking the top-left of the screen displays the drop down ''task menu''. This menu lists all active applications and allows to switch directly to any one. ''Note:'' If the task menu is not shown, click and hold the [[#Aux|Aux]] button to bring up the Aux menu, and select "Toggle Fullscreen".<br />
<br />
== Using the terminal ==<br />
<br />
To start a console from "Today" page, click the middle tab at the bottom of the screen to display the "Launch applications" page, then select Terminal in the "Applications" submenu. The multitaps keyboard slides up (and down) from the bottom of the screen automatically when you touch the screen.<br />
<br />
===Setting date and time===<br />
<br />
From the terminal, type the following, but replace ''MM'' with the month (01-12); ''DD'' with the day (01-31); ''hhmm'' with the time (0000-2359); ''YYYY'' with the year (optional); and ''.ss'' with the seconds (optional).<br />
<br />
date -s ''MMDDhhmmYYYY.ss''<br />
<br />
To make the change persist between reboots, sync the hardware clock with the updated system time.<br />
<br />
hwclock --systohc<br />
<br />
See [[Setting Date and Time]] for more discussion, including synchronizing with an NTP server.<br />
<br />
Note: UNIX traditionally sets the system clock to GMT (UTC) or "Zulu" (Z time zone). So I use the stanza:<br />
date -u MMDDhhmmYYYY.ss (well, I usually ignore the seconds)<br />
Then I can set the local time using the techniques described elsewhere. iceworm<br />
<br />
=== Accessing the microSD card ===<br />
<br />
Mounted at /media/card by default.<br />
<pre><br />
mount /media/card<br />
</pre><br />
If you have multiple partitions on the card, the first (/dev/mmcblk0p1) will be mounted at /media/card, the second at /media/mmcblk0p2, the third at /media/mmcblk0p3 etc. To setup the package management to write on the microSD card when installing new software follow the [[Package_management | package management guide]].<br />
<br />
fox example :<br />
<pre><br />
Filesystem 1k-blocks Used Available Use% Mounted on<br />
rootfs 252544 153560 98984 61% /<br />
/dev/root 252544 153560 98984 61% /<br />
/dev/root 252544 153560 98984 61% /dev/.static/dev<br />
udev 2048 76 1972 4% /dev<br />
/dev/mmcblk0p1 3362 1794 1568 53% /media/card<br />
/dev/mmcblk0p2 476382 157368 294419 35% /media/mmcblk0p2<br />
tmpfs 61928 380 61548 1% /var/volatile<br />
tmpfs 61928 0 61928 0% /dev/shm<br />
</pre><br />
<br />
== Set up USB-based networking, SSH and update ==<br />
<br />
Openmoko allows TCP/IP-over-USB networking for your phone. The main advantages of this are<br />
* You don't need to set-up GPRS or WLAN network connection for the phone software to reach the Internet<br />
* You can SSH from your computer into the phone shell and comfortably do low-level tasks using your computer's terminal software and real keyboard instead of the tiny screen and touchscreen keyboard<br />
<br />
Naturally, the phone must be connected to your computer with USB cable.<br />
<br />
===Connect with the Neo FreeRunner===<br />
<br />
This is discussed in the [[USB_Networking|USB Networking]] section.<br />
<br />
===Update with the package manager===<br />
<br />
In order to keep the FreeRunner up-to-date with the latest features and bug-fixes, it is advisable update the software at regular intervals.<br />
<br />
There are two main methods of doing this:<br />
* upgrading with the package manager '''[[Opkg]]'''<br />
* or manually flashing the device (see [[Flashing the Neo FreeRunner]]).<br />
<br />
There are three layers to the software on the FreeRunner:<br />
<br />
* [[uboot|uBoot]]: Think of u-boot as a combination of the BIOS and Grub on a PC.<br />
* Kernel: The Linux kernel<br />
* Root Filesystem: The rest of the system<br />
<br />
Note that ''uboot'', the ''kernel'' and the ''root filesystem'' may all be flashed to update them. For uboot, this is the only possibility (see [[Flashing_the_Neo_FreeRunner#Flashing_the_boot_loader]]). The advantage of flashing the kernel manually rather than using opkg seems to be speed. The disadvantage of flashing the root file system is that it wipes out all local modifications, including /home. If /home is moved to the SD disk, this is no longer a problem.<br />
<br />
{{Warning| UPGRADING TO DAILY KERNELS FROM THE DEVELOPMENT BRANCH MAY BREAK THINGS. That said, assuming that your FreeRunner can access the internet (see above), the kernel and other packages can be updated with<br />
<br />
# opkg update<br />
# opkg -test upgrade<br />
# opkg upgrade<br />
<br />
The first updates the repository information, telling opkg what packages are available. The second allows you to see what the package manager wants to do. The third upgrades all packages for which a newer version is available. '''At the moment, some signature files are missing (404 errors), which opkg complains about, but this is cosmetic.''' The repositories will still update with the missing signature files.<br />
}}<br />
<br />
'''Important:''' If you have followed the Getting Started Guide this far, but opkg upgrades do not appear to be happening. Try checking the .conf files in the /etc/opkg/ directory. If you see four URLs pointing at<br />
<nowiki>http://buildhost.openmoko.org/</nowiki>, this is your problem. <nowiki>http://buildhost.openmoko.org/</nowiki> is no longer supported. If you're running Om 2007.2 (the stock distribution that comes with the Freerunner according to the [[FAQ]]), you'll need to edit those files to point to an unofficial [[Users Repositories|User Repository]]. Or, you could install another [[Distributions|distribution]] (which is probably the best bet in the long run).<br />
<br />
<br />
<br />
Note that running opkg upgrade on a factory-fresh phone will upgrade dropbear (the ssh software) and various xserver packages, and neither upgrades elegantly while in use. Xserver must be updated over ssh to complete succesfully. Dropbear can be updated over ssh with the proper command:<br />
<br />
nohup opkg upgrade dropbear &<br />
<br />
Or upgrade it directly in the FreeRunner terminal.<br />
<br />
opkg upgrade dropbear<br />
<br />
When updating over ssh, the session will be interrupted, but the command should complete successfully(check nohup.out on your device to verify), and you should be able to reconnect within a few seconds.<br />
<br />
Another (better) option is to start a screen session before the upgrade with:<br />
<br />
screen<br />
<br />
After loosing the ssh connection and login in again via ssh reconnect to the running screen session with:<br />
<br />
screen -x<br />
<br />
Then connect to the FreeRunner via ssh and type:<br />
<br />
opkg upgrade<br />
<br />
And run this command :<br />
<br />
depmod<br />
<br />
Alternatively you can upgrade the xserver packages via ssh and then upgrade the rest from the FreeRunner's terminal.<br />
<br />
If you do your first upgrade in two installments like this, it will go more smoothly.<br />
<br />
It will be possible in the future to update uboot with opkg, but this has not yet been implemented.<br />
<br />
=== Installing applications ===<br />
<br />
There are many applications you can install - check out the [[Repositories]] for a list of packages, an example of how to add a repository using scaredy cat as an example can also be found here. A list of pre-installed and available packages with descriptions can be found here - [[Available Packages]].<br />
Or you can check [[Applications]] page to get applications developed from community.<br />
<br />
If you want to install any application on Neo, there three steps:<br />
<br />
'''<br />
1. Download the applicatiion you want to install on Neo.<br />
<br />
2. scp the opkg/ipk file to the root of Neo.<br />
<br />
3. Use Opkg command to intall opkg files.'''<br />
<br />
By following example you can install web browser on Neo:<br />
<br />
The calendar can be installed with<br />
<br />
<br />
First download and unpack it on your GNU/Linux host:<br />
<br />
<pre><br />
wget http://www.ginguppin.de/files/minimo.tar.bz2<br />
tar jvxf minimo.tar.bz2<br />
</pre><br />
<br />
Copy it over to the FreeRunner:<br />
<pre><br />
scp minimo_* root@192.168.0.202:/tmp<br />
</pre><br />
<br />
Then on the FreeRunner:<br />
<pre><br />
opkg install /tmp/minimo_0.02\+cvs20070626-r0_armv4t.ipk<br />
</pre><br />
<br />
You'll probably also want to [[Switching Keyboards|change the keyboard]] including the [[Switching Keyboards#How_to_add_a_keyboard_toggle_button|keyboard toggle applet]]<br />
<br />
=== Importing contacts ===<br />
<br />
If you can export your contacts to VCard format, either multiple files or single file containing all of them, you may use the script on [[Import Vcf Contacts]] page to bring them to Neo.<br />
<br />
<br />
<br />
==The next steps==<br />
<br />
Congratulations for setting up your Neo FreeRunner. There are many more resources to help free your phone:<br />
<br />
===Customize the interface===<br />
home screen clock, keyboard<br />
<br />
The stock [[Openmoko2007.2]] image flashed onto the Neo FreeRunner is really just the bare bones. For example, you don't have the clock and the quick-launch icons showing. Here's how you can change that:<br />
<br />
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false<br />
# /etc/init.d/xserver-nodm restart<br />
<br />
If you rather have a regular clock instead of the digital one, do this instead:<br />
<br />
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/reduced false<br />
# dbus-launch gconftool-2 -t boolean -s /desktop/poky/interface/digital_clock false<br />
# /etc/init.d/xserver-nodm restart<br />
<br />
REMOVE CLICK SOUND VIA /etc/pulse/session<br />
<br />
More information about today screen customization at [[Today/2007.2]].<br />
<br />
Also, if you prefer having a full keyboard, using matchbox's qwerty keybord, see [[Switching_Keyboards#Matchbox_keyboard|these instructions]]. Then you may also see [http://lists.openmoko.org/pipermail/community/2008-July/021296.html these], which describe a way to add an applet allowing the showing/hiding of that keyboard.<br />
<br />
===Use the GPS===<br />
You can see [[Manually using GPRS]] to get more information about GPS. Or download [[TangoGPS]] from [http://www.tangogps.org/downloads/tangogps_0.9.3-r1_armv4t.ipk tangogps.org].<br />
<br />
There were critical [[GPS Problems]] earlier that are largely fixed in newest kernels, see the instructions above to install the updates. More information is on the [[GPS]] page.<br />
<br />
===Play with WLAN, GPRS and Bluetooth===<br />
<br />
There are plenty of development opportunities to integrate these functions in the Openmoko software.<br />
<br />
'''WLAN''': See [[Wireless Networking]]<br />
<br />
'''GPRS''': See [[Manually using GPRS]]<br />
<br />
'''Bluetooth''': See [[Manually using Bluetooth]]<br />
<br />
=== Testing a new distribution ===<br />
<br />
For the feature of Openness, you can flash any Linux [[Distributions]] into FreeRunner. You can testing a new distribution by following ways:<br />
<br />
* [[Booting from SD]].<br />
* Boot from the built-in NAND flash memory.<br />
** [[NeoTool]] gives you a GUI to flash and backup.<br />
** [http://code.google.com/p/om-manager/ om-manager] is another GUI to flash, backup and [[Community_Updates/December_29th%2C_2008#New_applications|more]].<br />
<br />
=== Welcome to the community ===<br />
<br />
The release of the FreeRunner in the summer 2008 has led the community into a new period of rapid growth. The resources available are summarized on the [[Community Resources]]. These are always exciting and interesting times to live in when the balance between Chaos and Order tilts towards change.<br />
<br />
As an entry point, the [http://lists.openmoko.org/pipermail/community/ openmoko community mailing list] is perhaps the most active. As of July 2008, its volume amounts to dozens of messages per day. Read the [[Community_Updates]] for a digest. Openmoko people are there too. You may ask for help on the [[https://lists.openmoko.org/mailman/listinfo/support support mailing list]].<br />
<br />
Or if you use IRC, there is always a good group in the channel #openmoko on FreeNode.<br />
<br />
The links on the top-right of this page lead to the sister sites in the Openmoko community:<br />
* Home and Wiki lead to the same Main Page on the wiki. It needs cleaning, we know...<br />
* Doc leads to the bug ''Trac''king system.<br />
* Planet goes to the collection of Openmoko-relatd blogs.<br />
* Projects is the GForge, free hosting for application developers.<br />
* Lists is the listing of all the public mailing lists on lists.openmoko.org.<br />
<br />
== Annotated references ==<br />
<br />
* [[Neo FreeRunner]]. The top-level view of the specifications.<br />
* [[Neo FreeRunner GTA02 Hardware]]. The detailed specifications.<br />
* [[GTA02 Openness]]. Ultimate chip-level specifications, data sheets and hardware documentation.<br />
* [[Distributions]]. Strengths and weaknesses of the various distributions available for the Neo.<br />
* [[FAQ#Getting_Started_with_your_Neo_FreeRunner]]. Answers.<br />
<br />
To search this wiki with Google, use the following search term:<br />
<br />
<search term> site:http://wiki.openmoko.org/wiki/<br />
<br />
[[Category:Neo FreeRunner Hardware| ]]<br />
[[Category:Basic End User]]</div>Pnaullshttp://openmoko.org/wiki/Template:DistributionsTemplate:Distributions2009-03-25T02:26:53Z<p>Pnaulls: </p>
<hr />
<div>{{{1|--}}} is one of the many distributions that currently work on the Openmoko phones. You can compare a distribution with an Operating System on normal computers. It gives the phone all the software needed for operating. For more information about the different flavors, see [[distributions]]<br />
-----</div>Pnaullshttp://openmoko.org/wiki/ParoliParoli2009-03-25T02:16:03Z<p>Pnaulls: /* Only the package */</p>
<hr />
<div>In a few words one could say: paroli is a new approach to application development on the Openmoko phones.<br />
Paroli is based on top of the [[OpenmokoFramework|FSO framework]] and enables the use of it via a core and several services.<br />
<br />
For more information please visit [http://www.paroli-project.org/ Paroli website]<br />
<br />
== Getting the sources ==<br />
<br />
git clone http://git.paroli-project.org/paroli.git/<br />
<br />
==biggest changes:==<br />
- a launcher was introduced allowing the launching of paroli-applications from within paroli itself.<br />
- the dbus interface is optional and both modes should work.<br />
<br />
- closing application windows from within the window-manager does not kill the process anymore<br />
<br />
- introduction of a preliminary audio service allowing to mute calls (a test service for non-fso environments was also added).<br />
<br />
- a reworked version of the dialer was added<br />
<br />
- works on an error-message service have begun<br />
<br />
- works on a service checking for changes in the fso have begun and many small fixes in the code<br />
<br />
===[paroli] weekly update week 10 of 2009===<br />
here an overview if the highlights of the things the paroli team has been working on in week 9 and the first part of week 10:<br />
<br />
-the msgs application is in and being shipped in every build<br />
you can view, send, receive, answer to and forward messages<br />
also it will offer you to save any unknown number to your phonebook<br />
<br />
-the people application is in and also being shipped every day<br />
you can view, edit and directly call a contact<br />
<br />
- the call logs i.e. the i/o application is also being shipped<br />
you can view your call logs and directly return the call<br />
also it will offer you to save any unknown number to your phonebook<br />
<br />
- dtmf in tele<br />
<br />
- ussd in tele<br />
you can receive and send simple ussd messages. NOTE: a very ugly window <br />
will open with the message written in very small letters, but it works. <br />
We will have a look into this a bit later.<br />
<br />
- small reworks on the lists we use<br />
<br />
- gsm and battery icons<br />
<br />
- muting ringtone when incoming call<br />
<br />
- muting call (mutes microphone)<br />
<br />
- Charlie did a complete rework of the service class so that there <br />
should not be any errors due to services not waiting for one another anymore<br />
<br />
and lots of other small things that would make this an endless list :) <br />
<br />
what will we do next:<br />
we will focus on some details that had been neglected so far such as<br />
- finally getting some scrolling or paging to work in our lists<br />
- getting some secondary actions associated with our list items<br />
- look at how we can go about a settings application as discussed on <br />
this list earlier<br />
- make certain internal adjustments to classes and applications to allow <br />
more flexibility<br />
- getting an image that works out of the box again<br />
<br />
===7 days update Feb 13 ~ Feb 20===<br />
<br />
<br />
- gotten daily build unstable images which by now boot directly into paroli<br />
<br />
http://downloads.openmoko.org/distro/unstable/NeoFreerunner/fso-paroli-image-om-gta02.jffs2<br />
<br />
http://downloads.openmoko.org/distro/unstable/NeoFreerunner/uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin<br />
<br />
They do come with bugs and issues sometimes critical like today when paroli hangs because a resource in the framework is not available at paroli launch. This will be gone tomorrow.<br />
<br />
- Fixed lots of bugs and issues such as:<br />
-- unicode in message reading<br />
-- loading messages from the SIM and saving incoming messages in the <br />
phone automatically<br />
-- made all our lists automatically react to changes in items etc<br />
-- gui issues such as the PIN dialog<br />
-- got rid of the green topbar ;) <br />
-- muting ringtone on incoming call<br />
-- muting call in call (also as of tomorrow again)<br />
<br />
- moved most of the Milestone two tickets[1] to testing<br />
<br />
and<br />
<br />
- were feverishly working on the stuff for the next milestone[2]<br />
<br />
What are we planning to do next?<br />
<br />
- keep on fixing issues in MS2<br />
- continue working towards MS3<br />
- get the kbd to match paroli on the image<br />
- get messaging and contacts up and running as soon as possible to allow <br />
brave testers to use paroli daily ... any volnteers ? ;) <br />
<br />
--if anyone is interested in helping out with paroli, contribute code or test or or or ... Let us know! [mailto:mirko@openmoko.com|Mirko]]<br />
<br />
==Installation==<br />
<br />
on its own image (FSO MS 5 based):<br />
<br />
kernel:<br />
[http://downloads.openmoko.org/distro/unstable/NeoFreerunner/uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin kernel]<br />
<br />
image:<br />
[http://downloads.openmoko.org/distro/unstable/NeoFreerunner/fso-paroli-image-om-gta02.jffs2 paroli-image]<br />
<br />
===Only the package===<br />
In order to get the package from unstable you'll need to add a file:<br />
<br />
create a file in the '''/etc/opkg''' folder with the content:<br />
<br />
<nowiki>src/gz openmoko-unstable-armv4t http://downloads.openmoko.org/repository/unstable/armv4t</nowiki><br />
<br />
Then do an opkg-update and opkg install paroli.<br />
<br />
This should get you the newest version.<br />
<br />
==Downloads==<br />
<br />
You can downloads paroli from :<br />
[http://downloads.freesmartphone.org/fso-milestone5/feeds//armv4t/paroli_0.2.1+gitr7a2fdc16174258e9276e7c2d80f500b4dd624442-r0_armv4t.ipk http://downloads.freesmartphone.org/fso-milestone5/feeds//armv4t/paroli_0.2.1+gitr7a2...442-r0_armv4t.ipk]<br />
<br />
or from:<br />
<br />
http://downloads.openmoko.org/distro/experimental/ <br />
<br />
<br />
[[Category:FSO]]</div>Pnaullshttp://openmoko.org/wiki/ParoliParoli2009-03-25T02:14:31Z<p>Pnaulls: /* Installation */</p>
<hr />
<div>In a few words one could say: paroli is a new approach to application development on the Openmoko phones.<br />
Paroli is based on top of the [[OpenmokoFramework|FSO framework]] and enables the use of it via a core and several services.<br />
<br />
For more information please visit [http://www.paroli-project.org/ Paroli website]<br />
<br />
== Getting the sources ==<br />
<br />
git clone http://git.paroli-project.org/paroli.git/<br />
<br />
==biggest changes:==<br />
- a launcher was introduced allowing the launching of paroli-applications from within paroli itself.<br />
- the dbus interface is optional and both modes should work.<br />
<br />
- closing application windows from within the window-manager does not kill the process anymore<br />
<br />
- introduction of a preliminary audio service allowing to mute calls (a test service for non-fso environments was also added).<br />
<br />
- a reworked version of the dialer was added<br />
<br />
- works on an error-message service have begun<br />
<br />
- works on a service checking for changes in the fso have begun and many small fixes in the code<br />
<br />
===[paroli] weekly update week 10 of 2009===<br />
here an overview if the highlights of the things the paroli team has been working on in week 9 and the first part of week 10:<br />
<br />
-the msgs application is in and being shipped in every build<br />
you can view, send, receive, answer to and forward messages<br />
also it will offer you to save any unknown number to your phonebook<br />
<br />
-the people application is in and also being shipped every day<br />
you can view, edit and directly call a contact<br />
<br />
- the call logs i.e. the i/o application is also being shipped<br />
you can view your call logs and directly return the call<br />
also it will offer you to save any unknown number to your phonebook<br />
<br />
- dtmf in tele<br />
<br />
- ussd in tele<br />
you can receive and send simple ussd messages. NOTE: a very ugly window <br />
will open with the message written in very small letters, but it works. <br />
We will have a look into this a bit later.<br />
<br />
- small reworks on the lists we use<br />
<br />
- gsm and battery icons<br />
<br />
- muting ringtone when incoming call<br />
<br />
- muting call (mutes microphone)<br />
<br />
- Charlie did a complete rework of the service class so that there <br />
should not be any errors due to services not waiting for one another anymore<br />
<br />
and lots of other small things that would make this an endless list :) <br />
<br />
what will we do next:<br />
we will focus on some details that had been neglected so far such as<br />
- finally getting some scrolling or paging to work in our lists<br />
- getting some secondary actions associated with our list items<br />
- look at how we can go about a settings application as discussed on <br />
this list earlier<br />
- make certain internal adjustments to classes and applications to allow <br />
more flexibility<br />
- getting an image that works out of the box again<br />
<br />
===7 days update Feb 13 ~ Feb 20===<br />
<br />
<br />
- gotten daily build unstable images which by now boot directly into paroli<br />
<br />
http://downloads.openmoko.org/distro/unstable/NeoFreerunner/fso-paroli-image-om-gta02.jffs2<br />
<br />
http://downloads.openmoko.org/distro/unstable/NeoFreerunner/uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin<br />
<br />
They do come with bugs and issues sometimes critical like today when paroli hangs because a resource in the framework is not available at paroli launch. This will be gone tomorrow.<br />
<br />
- Fixed lots of bugs and issues such as:<br />
-- unicode in message reading<br />
-- loading messages from the SIM and saving incoming messages in the <br />
phone automatically<br />
-- made all our lists automatically react to changes in items etc<br />
-- gui issues such as the PIN dialog<br />
-- got rid of the green topbar ;) <br />
-- muting ringtone on incoming call<br />
-- muting call in call (also as of tomorrow again)<br />
<br />
- moved most of the Milestone two tickets[1] to testing<br />
<br />
and<br />
<br />
- were feverishly working on the stuff for the next milestone[2]<br />
<br />
What are we planning to do next?<br />
<br />
- keep on fixing issues in MS2<br />
- continue working towards MS3<br />
- get the kbd to match paroli on the image<br />
- get messaging and contacts up and running as soon as possible to allow <br />
brave testers to use paroli daily ... any volnteers ? ;) <br />
<br />
--if anyone is interested in helping out with paroli, contribute code or test or or or ... Let us know! [mailto:mirko@openmoko.com|Mirko]]<br />
<br />
==Installation==<br />
<br />
on its own image (FSO MS 5 based):<br />
<br />
kernel:<br />
[http://downloads.openmoko.org/distro/unstable/NeoFreerunner/uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin kernel]<br />
<br />
image:<br />
[http://downloads.openmoko.org/distro/unstable/NeoFreerunner/fso-paroli-image-om-gta02.jffs2 paroli-image]<br />
<br />
===Only the package===<br />
In order to get the package from unstable you'll need to add a file:<br />
<br />
create a file in the '''/etc/opkg''' folder with the content:<br />
<br />
src/gz openmoko-unstable-armv4t http://downloads.openmoko.org/repository/unstable/armv4t<br />
<br />
Then do an opkg-update and opkg install paroli.<br />
<br />
This should get you the newest version.<br />
<br />
==Downloads==<br />
<br />
You can downloads paroli from :<br />
[http://downloads.freesmartphone.org/fso-milestone5/feeds//armv4t/paroli_0.2.1+gitr7a2fdc16174258e9276e7c2d80f500b4dd624442-r0_armv4t.ipk http://downloads.freesmartphone.org/fso-milestone5/feeds//armv4t/paroli_0.2.1+gitr7a2...442-r0_armv4t.ipk]<br />
<br />
or from:<br />
<br />
http://downloads.openmoko.org/distro/experimental/ <br />
<br />
<br />
[[Category:FSO]]</div>Pnaullshttp://openmoko.org/wiki/Template:ApplicationTemplate:Application2009-03-23T05:04:59Z<p>Pnaulls: "goto" is not a word.</p>
<hr />
<div>{{{1|--}}} is one of the applications that runs on the Openmoko [[Phones]]. For a list of all applications, visit [[Applications]]</div>Pnaullshttp://openmoko.org/wiki/KnjrepositoryKnjrepository2009-03-23T03:36:50Z<p>Pnaulls: /* How to use */</p>
<hr />
<div>== Packages for development ==<br />
<br />
The knjRepository includes the following interesting packages:<br />
<br />
# '''php526''' - PHP 5.2.6 CLI support, which enables you to write CLI-scripts for your OpenMoko. It also includes PDO (SQLite3) support.<br />
# '''php526-gtk2''' - [[PHP-GTK]] enables you to write GTK-applications in PHP.<br />
# '''ruby1.8''' - Enables you to use Ruby scripts on your OpenMoko.<br />
# '''libgtk2-ruby1.8''' - Enables Ruby to use Gtk.<br />
# '''libsqlite3-ruby1.8''' - Enables you to use SQLite3-databases in Ruby.<br />
# '''libglade2-ruby1.8''' - Enables you to use Glade with Gtk-applications in Ruby.<br />
# '''ruby1.8-icalendar''' - A Ruby-lib for parsing iCal-files.<br />
# '''ruby1.8-googlecalendar''' - A Ruby-lib for working with a Google Calendar.<br />
<br />
<br />
(and a lot of other Ruby-extensions like SOAP and WSDL)<br />
<br />
A list of all the packages can be found [http://downloads.kaspernj.org/openmoko/repository/ here].<br />
<br />
== Application packages ==<br />
# '''[[KnjMokoWifi]]''' - An application for configuring the wireless interface in the OpenMoko-phone. It works with WPA, WEP and no-encryption. It supports profiles, so you dont have to remember passwords for each wireless access point used. It is written in PHP-GTK. Furthermore it can disable the routing-gateway on the USB-networking interface, making the default gateway WiFi. It can also start a DHCP-request to obtain an IP address and so on for the wireless interface.<br />
# '''[[KnjMokoOPKG]]''' - A graphical frontend for OPKG.<br />
# '''[[knjMokoCalendar]]''' - An application for viewing your Google Calendar on your OpenMoko phone written in Ruby. This application is still kind of unstable, since there isn't implemented any error handling.<br />
# '''[[knjMokoSettings]]''' - An application which allows a user to carry out various administrative tasks on their phone, such as restarting the X-server, rebooting the phone, turning off/on the Wifi and more, via a graphical interface.<br />
<br />
== How to use ==<br />
<br />
You can configure your phone to use the repository by doing the following:<br />
<br />
wget <nowiki>http://downloads.kaspernj.org/openmoko/repository/knjrepository.conf</nowiki> -O /etc/opkg/knjrepository.conf<br />
opkg update<br />
<br />
(ignore the signature errors)<br />
<br />
<br />
Then if you want to install PHP-GTK, you can do this:<br />
opkg install php526 php526-gtk2<br />
<br />
<br />
Or if you want Ruby with Gtk-support:<br />
opkg install ruby1.8 libgtk2-ruby1.8 libglade2-ruby1.8 libsqlite3-ruby<br />
<br />
== Made by ==<br />
<br />
The repository has been set up and is maintained by [mailto:k@spernj.org Kasper Johansen].<br />
<br />
The PHP-packages has been packaged by Derick Rethans.<br />
<br />
The Ruby-packages has been packaged by Kero van Gelder.<br />
[[Category:Guides]]<br />
[[Category:Applications]]</div>Pnaullshttp://openmoko.org/wiki/Video_PlayerVideo Player2009-03-22T16:27:10Z<p>Pnaulls: Fix lame formatting</p>
<hr />
<div>Not a proper 'app' page, just an overview<br />
<br />
=FreeRunner=<br />
It plays mpeg-4 320x240 stretched fullscreen, however other formats will require transcoding.<br />
<br />
==Playback==<br />
The default media player doesn't seem to handle video very well, but mplayer does OK.<br />
<br />
=== Using standard Mplayer ===<br />
It can be installed with the following command:<br />
opkg install mplayer<br />
<br />
=== Using the Glamo XV acceleration ===<br />
This only applies to GTA02 hardware which uses Glamo graphical chip. <br />
<br>First of all you'll need special version of Mplayer with glamo support.<br />
<br>You can download it from here: http://downloads.tuxfamily.org/3v1deb/openmoko/mplayer-glamo.tar.bz2<br />
<br>Just copy files inside the archive with:<br />
<pre><br />
cp mplayer /usr/bin/mplayer<br />
cp input.conf ~/.mplayer/input.conf<br />
</pre><br />
<br />
File shoud be preencoded with something like this:<br />
<pre>mencoder file_to_encode.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 \<br />
-vf scale=320:240,eq2=1.2:0.5:-0.25,rotate=2 -oac mp3lame -ofps 15 -lameopts br=64:cbr \<br />
-o file_for_openmoko</pre><br />
<br />
It can be played with:<br />
<pre>mplayer -vo xover:glamo -fs your_file.avi</pre><br />
<br />
Please refer to: http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ for more details.<br />
<br />
* I gave a try to the above how-to and it doesn't work on my FR. Playing the preencoded movie just displays a green screen with garbage on the top. -- [[User:Pini|Pini]] Sun Dec 7 13:08:42 UTC 2008<br />
<br />
=== Controlling MPlayer from the Touchscreen ===<br />
Create a file in /home/root/.mplayer/input.conf with this content:<br />
# Freerunner Optimizations<br />
MOUSE_BTN0 vo_fullscreen<br />
MOUSE_BTN0_DBL q<br />
Now, you can toggle the fullscreen by tapping the screen and exit from mplayer by touble-tapping the LCD.<br />
Accelerometers or hardware buttons could help more.<br />
<br />
=== Playback helper script ===<br />
<br />
Create a script named 'vidplay' in your home directory with the following commands:<br />
#!/bin/sh<br />
xrandr -display :0 --output default --mode 240x320<br />
mplayer -vo fbdev "$1" > /dev/null<br />
xrandr -display :0 --output default --mode 480x640<br />
reset<br />
<br />
Make the script executable:<br />
chmod 755 /home/root/vidplay<br />
<br />
Known issues with this approach:<br />
*The output isn't in a proper window, so background stuff sometimes flickers through.<br />
*When done on the local terminal the keyboard is obscured so you can't exit. SSH works quite well.<br />
*240x320 mode has some quirks:<br />
**The gamma/brightness/contrast is weird. Encoding adjustments into the media is a workaround.<br />
**Vertical banding (as seen in landscape position) is quite noticeable.<br />
*Using CTRL-C to exit vidplay doesn't reset the screen; use 'q' instead.<br />
<br />
Despite these issues, it proves that the horsepower is there and it can be done.<br />
<br />
=== Another derivated method : works like a charm for me ! ===<br />
No ssh, no xrandr, no script needed, juste mplayer and qwerty keyboard :<br />
Like it's said in the "Getting started with FreeRunner" wiki page, you have to install the full qwerty keyboard, see [http://www.ginguppin.de/node/15 these instructions].<br />
After that, you can go to Terminal and type :<br />
mplayer vid/my_video.avi<br />
Mplayer starts in full screen, if your video is optimized like below 240x320 it's work like a charm and to quit just use the power button.<br />
<br />
Only issue : You can't forward/backward/pause...<br />
<br />
==Example - Big Buck Bunny==<br />
===PC===<br />
Download the source (no need to start with the giant full resolution version)<br />
<br />
cd /tmp<br />
wget http://proyectos.pixelamigo.com/open/movies/BigBuckBunny/unofficial_PSP/big_buck_bunny_480p_AVC_FW33.mp4<br />
<br />
Test the video filter settings (-vf crop=...) often omitting the last "rotate=2" (Optional, but recommended for long videos).<br />
<br />
mplayer big_buck_bunny_480p_AVC_FW33.mp4 -vf crop=720:480:-1:-1,scale=320:-2,rotate=2 -zoom<br />
<br />
Transcode it:<br />
<br />
mencoder big_buck_bunny_480p_AVC_FW33.mp4 -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 \<br />
-vf crop=720:480:0:0,scale=320:-2,eq2=1.2:0.5:-0.25,rotate=2 -oac mp3lame -lameopts br=64:cbr \<br />
-o big_buck_bunny_320.avi<br />
<br />
or if it doesn't work (for me the image and the colours aren't ok) replace scale=320:-2 by scale=320:240<br />
<br />
=== FreeRunner===<br />
Transfer the resulting 27M file from the PC to the FreeRunner's MicroSD card<br />
scp user@192.168.0.200:/tmp/big_buck_bunny_320.avi /media/card<br />
<br />
Play it<br />
/home/root/vidplay /media/card/big_buck_bunny_320.avi<br />
<br />
==Other Info==<br />
<br />
To rotate the screen:<br />
xrandr -o 0<br />
xrandr -o 1<br />
<br />
=Neo1973=<br />
<br />
Video is problematic on [[Neo 1973]].<br />
<br />
On the minus side.<br />
*The CPU is certainly not fast enough to decode 480*640 video.<br />
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.<br />
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.<br />
However.<br />
<br />
On the positive side.<br />
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.<br />
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.<br />
*If not, then it almost certainly will be possible at 12fps.<br />
<br />
==Mode Switching==<br />
For switching between QVGA and VGA mode do the following with a compatible kernel:<br />
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga<br />
vice versa:<br />
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3<br />
taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html<br />
<br />
To avoid console blanking type<br />
echo -e '\033[9;0]' > /dev/ttyX<br />
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.<br />
<br />
To avoid kernel output in vt do<br />
echo 0 > /proc/sys/kernel/printk<br />
<br />
==User Reports==<br />
From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].<br />
<br />
400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.<br />
<br />
With sound, this drops to 18fps.<br />
<br />
There are optimisations for mplayer that look promising to get 25fps with sound.<br />
<br />
==Playback using 480x640 / 640x480==<br />
<br />
To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:<br />
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32<br />
<br />
Also working okay:<br />
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 352 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=200:abitrate=32<br />
<br />
You can playback the file using:<br />
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi><br />
<br />
You may also want to use:<br />
-autosync 30 -vf scale -zoom -xy 640 -vf rotate=1<br />
<br />
=Transcoding=<br />
To make your videos/DVDs compatible use mencoder like this:<br />
Find out the -vf cropping parameters with<br />
mplayer input.avi -vf cropdetect<br />
let it run a few seconds and insert the given cropping values into this command<br />
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi<br />
To encode a DVD first find out the -vf cropping parameters with<br />
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000<br />
let it run a few seconds and insert the given cropping values into this command<br />
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi<br />
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.<br />
<br />
=Frontend=<br />
==gnome-mplayer==<br />
'''Source Code released: No'''<br />
<br />
As a nice GUI gnome-mplayer can be recommended.<br />
<br />
On Debian you can install it from repository:<br />
# apt-get install gnome-mplayer<br />
<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Video Player|mplayer]]|<br />
Description=The popular command line video player.|<br />
Screenshot=Mplayer.png|<br />
Homepage=http://www.mplayerhq.hu|<br />
<br />
TestedOn=Om 2008.8 (default repository)|<br />
PackageName=mplayer|<br />
Source Code released=No|<br />
<br />
}}<br />
</onlyinclude><br />
<br />
== DeforaOS Player ==<br />
'''Source Code released: Yes'''<br />
<br />
It provides another GUI to mplayer.<br />
<br />
It was released first there:<br />
http://people.defora.org/~khorben/share/Openmoko/deforaos-player_0.1.0_armv4t.ipk<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[DeforaOS Player|deforaos-player]]|<br />
Description=The DeforaOS media player, a frontend to mplayer|<br />
Screenshot=Player.png|<br />
Homepage=http://www.defora.org/os/project/display/336/Player|<br />
<br />
TestedOn=Om 2008.8|<br />
PackageName=deforaos-player|<br />
Source Code released=Yes|<br />
<br />
}}<br />
</onlyinclude><br />
<br />
[[Category:Video Applications]]<br />
[[Category:Debian]]<br />
[[Category:Om 2008.8]]</div>Pnaullshttp://openmoko.org/wiki/Video_PlayerVideo Player2009-03-22T15:57:45Z<p>Pnaulls: /* Using the Glamo XV acceleration */</p>
<hr />
<div>Not a proper 'app' page, just an overview<br />
<br />
=FreeRunner=<br />
It plays mpeg-4 320x240 stretched fullscreen, however other formats will require transcoding.<br />
<br />
==Playback==<br />
The default media player doesn't seem to handle video very well, but mplayer does OK.<br />
<br />
=== Using standard Mplayer ===<br />
It can be installed with the following command:<br />
opkg install mplayer<br />
<br />
=== Using the Glamo XV acceleration ===<br />
This only applies to GTA02 hardware which uses Glamo graphical chip. <br />
<br>First of all you'll need special version of Mplayer with glamo support.<br />
<br>You can download it from here: http://downloads.tuxfamily.org/3v1deb/openmoko/mplayer-glamo.tar.bz2<br />
<br>Just copy files inside the archive with:<br />
<pre><br />
cp mplayer /usr/bin/mplayer<br />
cp input.conf ~/.mplayer/input.conf<br />
</pre><br />
<br />
File shoud be preencoded with something like this:<br />
<pre>mencoder file_to_encode.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 \<br />
-vf scale=320:240,eq2=1.2:0.5:-0.25,rotate=2 -oac mp3lame -ofps 15 -lameopts br=64:cbr \<br />
-o file_for_openmoko</pre><br />
<br />
It can be played with:<br />
<pre>mplayer -vo xover:glamo -fs your_file.avi</pre><br />
<br />
Please refer to: http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ for more details.<br />
<br />
* I gave a try to the above how-to and it doesn't work on my FR. Playing the preencoded movie just displays a green screen with garbage on the top. -- [[User:Pini|Pini]] Sun Dec 7 13:08:42 UTC 2008<br />
<br />
=== Controlling MPlayer from the Touchscreen ===<br />
Create a file in /home/root/.mplayer/input.conf with this content:<br />
# Freerunner Optimizations<br />
MOUSE_BTN0 vo_fullscreen<br />
MOUSE_BTN0_DBL q<br />
Now, you can toggle the fullscreen by tapping the screen and exit from mplayer by touble-tapping the LCD.<br />
Accelerometers or hardware buttons could help more.<br />
<br />
=== Playback helper script ===<br />
<br />
Create a script named 'vidplay' in your home directory with the following commands:<br />
#!/bin/sh<br />
xrandr -display :0 --output default --mode 240x320<br />
mplayer -vo fbdev "$1" > /dev/null<br />
xrandr -display :0 --output default --mode 480x640<br />
reset<br />
<br />
Make the script executable:<br />
chmod 755 /home/root/vidplay<br />
<br />
Known issues with this approach:<br />
*The output isn't in a proper window, so background stuff sometimes flickers through.<br />
*When done on the local terminal the keyboard is obscured so you can't exit. SSH works quite well.<br />
*240x320 mode has some quirks:<br />
**The gamma/brightness/contrast is weird. Encoding adjustments into the media is a workaround.<br />
**Vertical banding (as seen in landscape position) is quite noticeable.<br />
*Using CTRL-C to exit vidplay doesn't reset the screen; use 'q' instead.<br />
<br />
Despite these issues, it proves that the horsepower is there and it can be done.<br />
<br />
=== Another derivated method : works like a charm for me ! ===<br />
No ssh, no xrandr, no script needed, juste mplayer and qwerty keyboard :<br />
Like it's said in the "Getting started with FreeRunner" wiki page, you have to install the full qwerty keyboard, see [http://www.ginguppin.de/node/15 these instructions].<br />
After that, you can go to Terminal and type :<br />
mplayer vid/my_video.avi<br />
Mplayer starts in full screen, if your video is optimized like below 240x320 it's work like a charm and to quit just use the power button.<br />
<br />
Only issue : You can't forward/backward/pause...<br />
<br />
==Example - Big Buck Bunny==<br />
===PC===<br />
Download the source (no need to start with the giant full resolution version)<br />
cd /tmp<br />
wget http://proyectos.pixelamigo.com/open/movies/BigBuckBunny/unofficial_PSP/big_buck_bunny_480p_AVC_FW33.mp4<br />
<br />
Test the video filter settings (-vf crop=...) often omitting the last "rotate=2" (Optional, but recommended for long videos).<br />
mplayer big_buck_bunny_480p_AVC_FW33.mp4 -vf crop=720:480:-1:-1,scale=320:-2,rotate=2 -zoom<br />
<br />
Transcode it<br />
mencoder big_buck_bunny_480p_AVC_FW33.mp4 -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 \<br />
-vf crop=720:480:0:0,scale=320:-2,eq2=1.2:0.5:-0.25,rotate=2 -oac mp3lame -lameopts br=64:cbr \<br />
-o big_buck_bunny_320.avi<br />
<br />
or if it doesn't work(for me the image and the colours aren't ok) replace scale=320:-2 by scale=320:240<br />
<br />
=== FreeRunner===<br />
Transfer the resulting 27M file from the PC to the FreeRunner's MicroSD card<br />
scp user@192.168.0.200:/tmp/big_buck_bunny_320.avi /media/card<br />
<br />
Play it<br />
/home/root/vidplay /media/card/big_buck_bunny_320.avi<br />
<br />
==Other Info==<br />
<br />
To rotate the screen:<br />
xrandr -o 0<br />
xrandr -o 1<br />
<br />
=Neo1973=<br />
<br />
Video is problematic on [[Neo 1973]].<br />
<br />
On the minus side.<br />
*The CPU is certainly not fast enough to decode 480*640 video.<br />
*The display is portrait, which means that an additional rotation step is needed for most landscape video, adding to CPU usage.<br />
*Downloading an arbitrary video, and playing it without transcoding it, then playing it later will not be possible.<br />
However.<br />
<br />
On the positive side.<br />
*The LCD can be switched to a 240*320 stretch mode, which is much less taxing.<br />
*Re-encoding video to rotate it, and scale to 320*240, and encoding with a low CPU use codec such as MPEG-1 may well make half-screen doubled videos playable at 25fps.<br />
*If not, then it almost certainly will be possible at 12fps.<br />
<br />
==Mode Switching==<br />
For switching between QVGA and VGA mode do the following with a compatible kernel:<br />
chvt 4 && echo qvga-normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset qvga<br />
vice versa:<br />
echo normal > /sys/devices/platform/s3c24xx-spi-gpio.1/spi0.0/state && fbset vga && chvt 3<br />
taken from http://lists.openmoko.org/pipermail/neo1973-hardware/2007-October/000267.html<br />
<br />
To avoid console blanking type<br />
echo -e '\033[9;0]' > /dev/ttyX<br />
where 'X' is your terminal number - for example if you did chvt 4 then /dev/tty4 is your terminal.<br />
<br />
To avoid kernel output in vt do<br />
echo 0 > /proc/sys/kernel/printk<br />
<br />
==User Reports==<br />
From a conversation with XorA, in the [irc://freenode.com/#openmoko IRC channel].<br />
<br />
400kbps mpeg4 works on a 200Mhz neo (without sound) on prerotated 240*320 ffmpeg codec videos, at 25fps, using stock mplayer.<br />
<br />
With sound, this drops to 18fps.<br />
<br />
There are optimisations for mplayer that look promising to get 25fps with sound.<br />
<br />
==Playback using 480x640 / 640x480==<br />
<br />
To get best speed on GTA01 (best size-speed-resolution-codec trade-off I could find - doesn't mean it's perfect though) crosscode using:<br />
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 240 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32<br />
<br />
Also working okay:<br />
mencoder <sourcefile> -o <targetfile.avi> -ofps 13 -vf scale -zoom -xy 352 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=mp3:vcodec=h263p:autoaspect=1:vbitrate=200:abitrate=32<br />
<br />
You can playback the file using:<br />
mplayer -sws 0 -nodouble -vo sdl -fs -framedrop <tagetfile.avi><br />
<br />
You may also want to use:<br />
-autosync 30 -vf scale -zoom -xy 640 -vf rotate=1<br />
<br />
=Transcoding=<br />
To make your videos/DVDs compatible use mencoder like this:<br />
Find out the -vf cropping parameters with<br />
mplayer input.avi -vf cropdetect<br />
let it run a few seconds and insert the given cropping values into this command<br />
mencoder input.avi -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output2.avi<br />
To encode a DVD first find out the -vf cropping parameters with<br />
mplayer -dvd-device /path/to/dvd dvd:// -vf cropdetect -sb 50000000<br />
let it run a few seconds and insert the given cropping values into this command<br />
mencoder -dvd-device /path/to/dvd dvd:// -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=300 -vf crop=xx:xx:xx:xx,rotate=2,scale=-2:320 -oac mp3lame -lameopts br=64:cbr -o output.avi<br />
This will rotate the video/DVD, scale it and encode it to mpeg4 with a bitrate of 300kBit/s. Works like a charm.<br />
<br />
=Frontend=<br />
==gnome-mplayer==<br />
'''Source Code released: No'''<br />
<br />
As a nice GUI gnome-mplayer can be recommended.<br />
<br />
On Debian you can install it from repository:<br />
# apt-get install gnome-mplayer<br />
<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[Video Player|mplayer]]|<br />
Description=The popular command line video player.|<br />
Screenshot=Mplayer.png|<br />
Homepage=http://www.mplayerhq.hu|<br />
<br />
TestedOn=Om 2008.8 (default repository)|<br />
PackageName=mplayer|<br />
Source Code released=No|<br />
<br />
}}<br />
</onlyinclude><br />
<br />
== DeforaOS Player ==<br />
'''Source Code released: Yes'''<br />
<br />
It provides another GUI to mplayer.<br />
<br />
It was released first there:<br />
http://people.defora.org/~khorben/share/Openmoko/deforaos-player_0.1.0_armv4t.ipk<br />
<br />
<onlyinclude><br />
{{ApplicationBox|<br />
Name=[[DeforaOS Player|deforaos-player]]|<br />
Description=The DeforaOS media player, a frontend to mplayer|<br />
Screenshot=Player.png|<br />
Homepage=http://www.defora.org/os/project/display/336/Player|<br />
<br />
TestedOn=Om 2008.8|<br />
PackageName=deforaos-player|<br />
Source Code released=Yes|<br />
<br />
}}<br />
</onlyinclude><br />
<br />
[[Category:Video Applications]]<br />
[[Category:Debian]]<br />
[[Category:Om 2008.8]]</div>Pnaulls