http://wiki.openmoko.org/api.php?action=feedcontributions&user=Sybren&feedformat=atomOpenmoko - User contributions [en]2024-03-19T08:16:18ZUser contributionsMediaWiki 1.19.24http://wiki.openmoko.org/wiki/SHR_User_ManualSHR User Manual2009-11-22T14:15:08Z<p>Sybren: /* Improve speed of Elementary applications */ Removed the X11-16 section as it's no longer supported by SHR.</p>
<hr />
<div>{{Languages|SHR User Manual}}<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==SHR Introduction==<br />
<br />
Welcome to '''[[SHR]]''', a community driven distribution for (not only) Openmoko Neo phones.<br />
<br />
[[Image:SHR-Logo.png|200px|thumb|center|SHR]]<br />
<br />
{{Note|As SHR doesn't provide testing images at the moment this manual was based on unstable images available on the beginning of August 2009. The unstable images get changed very often - the download location changes, default applications change, bugs get hunted and fixed, meaning that some parts of this manual are already outdated.<br />
Some users write their SHR experiences on their user page:<br />
* [[User:Klaszlo|Klaszlo]]}}<br />
<br />
'''SHR''' (Stable Hybrid Release) is here to provide you with Root FileSystem images that you can easily install onto your phone to use as a daily phone. There are many prepackaged programs available that can be installed upon demand by users, it can also be used by developers as a base image for customized and flavored distribution or release. SHR unstable is a testing environment before software get stabilized and it is the main testing ground for [[FSO]] releases. SHR testing images (currently not available) provide as much stability as possible for day-to-day usage.<br />
<br />
SHR users, readers of this manual, please report improvements, discrepancies or missing features on this page to <tt>vanous @ penguin . cz</tt>. Thank you.<br />
<br />
[http://shr-project.org SHR Project page]<br />
<br />
==Installation==<br />
<br />
===Getting SHR===<br />
<br />
First, determine which model of phone you have, the GTA01 (Neo 1973) or the GTA02 (Neo FreeRunner).<br />
<br />
You need to download two files for your version as above: kernel and root filesystem. Depending whether you will be installing into the internal [[NAND memory]] or on [[µSD]] card, you need to either get .jffs2 file for NAND or .tar.gz file for µSD.<br />
<br />
At this point, there are no recent testing images; so for the GTA02 Neo FreeRunner you need to download the images of the? unstable release from http://build.shr-project.org/shr-unstable/images/om-gta02/<br />
<br />
- Get the latest kernel from the above linkpage. Starts with uImage-...<br />
<br />
- Get the root filesystem, for NAND: [http://build.shr-project.org/shr-unstable/images/om-gta02/full-om-gta02.jffs2 full-om-gta02.jffs2], for µSD: [http://build.shr-project.org/shr-unstable/images/om-gta02/full-om-gta02.tar.gz full-om-gta02.tar.gz]<br />
<br />
The above are '''full''' images. You can also choose images with less packages, marked as '''lite''' which can be upgraded to the full image by running<br />
<br />
opkg update<br />
opkg install task-shr-apps task-shr-games task-shr-gtk<br />
<br />
The 20090808-om-gta02 image doesn't have the <tt>opkg</tt> command, use <tt>opkg-cl</tt>. After an <tt>opkg-cl update</tt> and <tt>opkg-cl upgrade</tt> the command <tt>opkg</tt> works normally.<br />
<br />
- '''Get the kernel modules.''' From the same page, download the modules to match your kernel (their dates should be the same). Put that file on the FreeRunner and run<br />
<br />
gzip -dc modules-...tar.gz | tar -xf - -C /<br />
depmod -a<br />
<br />
Editors note: Running depmon should not be necessary, if it's needed, please report a bug. Recommending of the depmod command will be removed in near future.<br />
<br />
===Installation on Flash===<br />
<br />
In order to install your SHR distribution directly to your Freerunner Flash memory (NAND), you need to get the desired filesystem file ( <tt>.jffs2</tt> ) as described above and flash your device using the <tt>dfu-util</tt> tool.<br />
<br />
Please visit [[Flashing the Neo FreeRunner]] for more details about flashing and see [[Dfu-util]] for detailed information about the dfu-util.<br />
<br />
Commands to flash the filesystem and the kernel:<br />
<br />
for the Neo FreeRunner:<br />
<br />
sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a rootfs -R -D full-om-gta02.jffs2<br />
sudo dfu-util -d [[USB Product IDs|0x1d50:0x5119]] -a kernel -R -D uImage-om-gta02-latest.bin<br />
<br />
for the Neo 1973:<br />
<br />
sudo dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a rootfs -R -D full-om-gta01.jffs2<br />
sudo dfu-util -d [[USB Product IDs|0x1457:0x5119]] -a kernel -R -D uImage-om-gta01-latest.bin<br />
<br />
===Installation on µSD Card===<br />
<br />
Installing SHR on your µSD Card depends on the Bootloader you are using, ''uBoot'' or ''Qi''.<br />
<br />
In simply words, difference between both systems resides on how you must prepare your µSD Card and files you use to fill them:<br />
<br />
* If you use ''uBoot'', you need to create two partitions. First partition, not so big, in FAT16 or ext2 where you have to place the kernel file (<tt>uImage-om-gta02-latest.bin</tt>) and second partition in ext2 or ext3 where you have to uncompress the filesystem file (<tt>shr-image-om-gta02.tar.gz</tt>).<br />
<br />
* If you use ''Qi'', you only need an ext2 partition into your µSD Card where you uncompress the filesystem image file (<tt>shr-image-om-gta02.tar.gz</tt>). In this case Qi Bootloader is going to look for the kernel image into the <tt>/boot</tt> directory for file named <tt>uImage-GTA02.bin</tt> .<br />
<br />
Please visit links below for detailed information and tips:<br />
*For [[Booting from SD | uBoot]] and for [[Qi]].<br />
<br />
===SHR version===<br />
<br />
Should you ever later wonder what version of SHR you have actually installed, please run<br />
<br />
cat /etc/shr-version<br />
<br />
or check SHR Settings -> Other -> Image information<br />
<br />
===Booting===<br />
Press the power button shortly to start the phone. The booting splash screen will appear. The first boot after a new installation always takes a bit longer. It is recommended to reboot after this first boot, to make sure all packages got initialized properly.<br />
<br />
[[Image:Shr-boot-preview.png|200px|thumb|center|SHR Boot Splash screen]]<br />
<br />
===Initial Setup===<br />
<br />
[[Image:SHR-Setup-Language.png|200px|thumb|Initial setup]]<br />
On the first boot, Setup is automatically initiated to walk the user through basic setup of the Enlightenment desktop environment. You are able to choose preferred language of the desktop environment, Illume SHR themed profile or select default menu (only one at the moment). <br />
<br />
On the Add icon screen you can add icons for some application. If you add a terminal based application like mplayer, you will see an icon but no application running upon click, as it will run in the background. <br />
Last screen allow settin up quick launch applications.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Setup-Profile.png|200px|thumb|Theme profile]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Setup-Menu.png|200px|thumb|Menu]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Setup-Add-Icons.png|200px|thumb|Add icons]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
<br />
[[Image:SHR-Setup-Quick-Launch.png|200px|thumb|Quick launch]]<br />
<br />
|}<br />
<br />
==Running SHR==<br />
<br />
===SIM Auth===<br />
<br />
[[Image:SHR-SIM-Auth.png|200px|thumb|center|SIM Auth]]<br />
SIM Pin is asked for upon start up.<br />
<br />
===First look===<br />
[[Image:SHR-First-Look.png|200px|thumb|Desktop screen]]<br />
'''Illume desktop''' is the default home screen of the SHR desktop. Application files located in /usr/share/applications are displayed here. All applications are ran fullscreen and you can switch between them by using the Task switcher in the top shelf or by using the '''<''' left or right '''>''' arrows in the top shelf.<br />
<br />
===Phone applications===<br />
<br />
Besides other software, SHR comes with 4 main phone applications: ''Dialer'', ''Contacts'', ''Messages'' and ''Phone log''.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Dialer.png|200px|thumb|Dialer]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contacts.png|200px|thumb|Contacts]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contacts-Options.png|200px|thumb|Contact options]]<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Contact-Add.png|200px|thumb|Add new contact]]<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Mesages.png|200px|thumb|Messages]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Messages-Options.png|200px|thumb|Messages options]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Message-View.png|200px|thumb|View message]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
[[Image:SHR-Message-View-chars.png|200px|thumb|Unicode support]]<br />
<br />
|}<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " | <br />
[[Image:SHR-Mesages-Options.png|200px|thumb|Message options]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Phonelog.png|200px|thumb|Phonelog]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:25% " |<br />
<br />
[[Image:SHR-Dialer-Active.png|200px|thumb|Active call]]<br />
<br />
|}<br />
<br />
Upon a missed call or an unread message there is a notifier that presents a screen with button to run Messages or Phonelog application, or you can simply close the Notifier with the Top Shelf cross.<br />
<br />
<br />
<br />
===First steps===<br />
<br />
Right after installation and first boot you might want to do a few initial steps:<br />
====Network Connection====<br />
''Establish network connection'' and SSH into your phone. The <tt>root</tt> account uses no password by default. You can establish connection either via USB to your desktop and enable NAT or you can connect through Wifi. If you use USB, some setup is required on the desktop side, please read [[USB_Networking]]. For Wifi, you can use [[#Network manager|Network Manager]]<br />
<br />
====GSM Network====<br />
''Check if GSM is working correctly'' - observe the GSM gadget in the Top Shelve and see reported signal of your GSM operator. If GSM Gadget seems not be running, click ''Settings'' and later on ''Phone''. Move ''GSM Antenna'' to ''On''.<br />
<br />
====Audio: Volume====<br />
''Check and set call volume'' - this is handled by alsa state files in <tt>/usr/share/shr/scenarii/</tt> . To customize speaker volume edit <tt>/usr/share/shr/scenarii/gsmhandset.state</tt> and change <tt>control 4</tt>. Values between from 105 to 120 might be sufficient:<br />
<br />
vi /usr/share/shr/scenarii/gsmhandset.state<br />
<br />
control.4 {<br />
comment.access 'read write'<br />
comment.type INTEGER<br />
comment.count 2<br />
comment.range '0 - 127'<br />
iface MIXER<br />
name 'Speaker Playback Volume'<br />
value.0 116<br />
value.1 116<br />
}<br />
<br />
Should you want to alter more parameters be aware that each file is a set of value for the 94 parameters. Some of the important ones are:<br />
<br />
Control 48: internal mic of the tel (set to 2 or 3)<br />
Control 4 : internal speaker (set from 110 to 120)<br />
Control 49: headset mic<br />
Control 3 : headset speaker<br />
<br />
====Initializing the opkg database====<br />
''Initialize the opkg database'' in order to install some applications from SHR repositories or from other sources, for example [[http://opkg.org opkg.org]]. While still being online, you need to first run<br />
<br />
opkg update<br />
<br />
Searching in the opkg database can take a long time. You can speed things up by dumping the database into a file and grepping it through.<br />
<br />
Do this only once or after every opkg update:<br />
<br />
opkg list > packages.txt<br />
<br />
Then you can search quickly for package name, for example for navit:<br />
<br />
grep navit packages.txt<br />
<br />
=====20090808 Image opkg startup=====<br />
In the 20090808 Image, opkg update does not work you will get: -sh: opkg: not found.<br />
<br />
There is a missing opkg symlink to opkg-cl. this is fixed in the SHR repositories. <br />
<br />
To update:<br />
<br />
opkg-cl update<br />
<br />
And to upgrade<br />
<br />
opkg-cl upgrade<br />
<br />
opkg should work fine now.<br />
<br />
====SwapSpace====<br />
{{Main|SwapSpace}}<br />
When the RAM is used up, applications get killed. This is particularly bad while doing opkg upgrade. Therefore you might want to create a swap space. Read [[SwapSpace]]<br />
<br />
====Changing root password====<br />
<br />
SHR is shipped without root password (just press enter)<br />
<br />
This is very dangerous if you connect using wifi, or USB. You need to activate the root password:<br />
<br />
passwd<br />
<br />
then type your selected password (2 times)<br />
<br />
<br />
A much more convenient way might be to install your public-key to ~/.ssh/authorized_keys. You can find your public-key of you host at location:<br />
<br />
/path/file <br />
<br />
For running <br />
cmd | ssh root@neo anycommand<br />
from your host this might be even mandatory, e.g if you want to pipe anything to the ssh.<br />
<br />
===Localization===<br />
<br />
==== Localize SHR manually ====<br />
<br />
[[Image:SHR-Illume-Settings-Languages.png|200px|thumb|Setting Language]]<br />
<br />
You can change the language of the SHR desktop environment by using the Settings of Illume. For Example, for Czech language: in the Illume top shelf go to Wrench (Settings) -> Language -> Language Settings -> and choose: Čeština. If your language is not in the menu you can install by using opkg.<br />
<br />
You can list all available languages by running:<br />
<br />
opkg list | grep glibc-locale-<br />
<br />
And install the language of your choice (for example czech):<br />
<br />
opkg install glibc-locale-cs<br />
<br />
After this, the Language Settings of Illume will offer Czech. <br />
<br />
This will localize the Illume environment and will also set correct lang environment variable. If you wish to have translations for other applications, you need to install them again (presuming they are available):<br />
<br />
This will install czech localisation for SHR phone applications, SHR Settings and TangoGps:<br />
<br />
opkg install libframeworkd-phonegui-efl-locale-cs shr-settings-locale-cs tangogps-locale-cs<br />
<br />
For localized terminal environment (ssh login) set lang variables set /etc/profile, example for Czech language:<br />
<br />
export LANG=cs_CZ<br />
export LC_ALL=cs_CZ<br />
<br />
<br />
The Illume keyboard offers english dictionary correction by default. You can list all the dictionaries available for installation:<br />
<br />
opkg list | grep illume-dic<br />
<br />
If your language is not available and english is bothering you, you can set an empty dictionary:<br />
<br />
echo "" > /usr/lib/enlightenment/modules/illume/dicts/None.dic<br />
<br />
By using it, it will get filled by the words you use and after time will start helping and correcting your typing.<br />
<br />
[[Image:Illume-keyboards-terminal-dutch-nl-screenshot.png| Dutch terminal virtual keyboard|256px|thumb]]<br />
Furthermore you can install a different keyboard with a layout which fits your language or alternatives for the default keyboards like the numerical one. The localized [[Illume keyboard]]s are available in the SHR repository under the name ''illume-keyboard-LANG''.<br />
<br />
Note that sometimes after an upgrade of Illume has taken place, these keyboards have to be installed again before the become available again. Removing these packages will restore the availability of the respective original keyboards.<br />
<br />
==== German (and Austria) Language ====<br />
Find a hopefully [[Configure_SHR_for_German-speaking_use|stable SHR German language version]] with Austrian Maps [[Configure_SHR_for_German-speaking_use|here]]. The configuration can be used for any <br />
German speaking country. The Austrian maps for [[Navit]] can be replaced and Navit is "speaking" German. Navit is configured with a preselect of country "Austria" (see [[Navit]]), There are some differences between dictionary de_AT (Austria) and de_DE (Germany).<br />
<br />
===Date and time===<br />
<br />
The local timezone is automatically retrieved from the GSM network. Date and time are automatically set from GPS or Network. The easiest way of setting the time for the first time is to run TangoGps (GPS & Map icon) and obtaining GPS fix. Time will then be set automatically after several minutes.<br />
<br />
Time can set time also manually.<br />
<br />
Via SHR-Settings -> Date/time -> Set time<br />
<br />
From linux based desktop:<br />
<br />
ssh root@192.168.0.202 "date -u -s `date -u +%m%d%H%M%Y.%S`"<br />
<br />
You can also set the hardware clock to the system time:<br />
<br />
hwclock --systohc<br />
<br />
It is possible to instruct framework on how to set the time and timezone in /etc/frameworkd.conf :<br />
<br />
[otimed]<br />
# a list of time/zone sources to use or NONE<br />
timesources = GPS,NTP<br />
zonesources = GSM<br />
# use an ip address here, otherwise DNS resolution will block<br />
ntpserver = 134.169.172.1<br />
<br />
To disable automatic date/zone settings, simply create an empty [otimed] section in /etc/frameworkd.conf<br />
<br />
===File transfer===<br />
<br />
After you have established network connection, it is very easy to access and transfer files. The easiest solution is to use Konqueror or Nautilus on your desktop computer and type the following on your location bar. This should provide you with a view of the client's file system on Konqueror or Nautilus and you can easily drag-drop and copy-paste files.<br />
<br />
sftp://root@192.168.0.202<br />
<br />
===Reporting bugs===<br />
<br />
SHR is a work in progress. If you experience issues, please report them back to SHR. With your report provide logs from<br />
<br />
/var/log/ophonekitd<br />
/var/log/frameworkd<br />
<br />
To report a bug, please go to http://shr-project.org/trac/report<br />
<br />
Check if the bug is already reported. If not, add a ticket, be as much precise as you can in the title and the description, in what circumstances the issue happened and so on.<br />
<br />
==Settings==<br />
===SHR Settings===<br />
[[Image:SHR-Settings-main.png|200px|thumb|SHR Settings]]<br />
<br />
SHR Settings is the main setting application of SHR. It provides an easy way of setting up your phone to your liking - from phone related settings, to requesting resources in order to prevent screen dim or suspend (for example while using GPS).<br />
<br />
Please refer to [http://wiki.openmoko.org/wiki/FSO_Resources#Automatic_way this wiki page] about a better way to manage preventing screen dim or suspend.<br />
<br />
While some settings are persistent over reboots, others are not.<br />
<br />
====Main Screen====<br />
The main screen is divided into eight categories, which contain several modules. Every SHR Settings module has a specified task - for example controlling the GSM antenna power, setting the time etc. <br />
<br />
====Settings: Phone====<br />
Here you can set if the GSM antenna is on and if your phone number is shown when you call someone.<br />
<br />
'''GSM'''<br />
In GSM settings you can turn off and on GSM module. After turning off antenna, whole GSM modem is turned off.<br />
<br />
To list available providers, click on Operators button. Scanning can take some time. After a while, a list of operators should pop up.<br />
<br />
You can't connect to operators marked [forbidden]. After a connection failure, a message is displayed.<br />
<br />
Selecting an operator from the list also changes modem registration mode to manual. It won't register to other network, even if some is available and has better signal strengh. To return to automatic mode, click "Automatic" button in operator list.<br />
<br />
'''Call'''<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Phone.png|200px|thumb|Phone settings]]<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-List-providers.png|200px|thumb|List providers]]<br />
<br />
|}<br />
<br />
You can set if your phone number should be displayed to other party. You can either depend on network decision ("By network") or force it manually ("Manual")<br />
<br />
'''Phoneutils'''<br />
<br />
For the default SHR phone applications to be able to correctly parse incoming calls/messages and match them with your contacts, you will need to set the right country code for your location. (for example 42 for Czech republic) for more info, please go to: http://wiki.openmoko.org/wiki/Phone_Prefixes<br />
<br />
'''SIM'''<br />
<br />
Here you can view some informations about your SIM card and clean phone and messagebooks.<br />
<br />
'''Others'''<br />
<br />
'''Profile'''<br />
<br />
Here you can select the current profile, which the device should use to determine ring tone etc.<br />
<br />
'''Current profile'''<br />
<br />
Here you can adjust properties of the currently used profile. Available settings: ring tone, ring volume, ring vibration, ring loop, ring length, message tone, message volume, message vibration, message loop, message length.<br />
<br />
To change the ring tone, click the "Change" button.<br />
<br />
To use your own ring tone, place it in /usr/share/sounds directory.<br />
<br />
After selecting a sid tune as the ring tone, there are available controls to select tune number from the file.<br />
<br />
This is changing settings in /etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
ring-volume # Ring Volume control 0 (mini) to ? maxi)<br />
ring-length # min time for ringtone. Must be greater than the duration of you ringtone<br />
ring-loop # define the number of loop of ringtone to play<br />
ring-tone: "ringtone_ringnroll.ogg" # .ogg example<br />
ring-tone: "Arkanoid_PSID.sid" # .sid example, use default tune<br />
ring-tone: "Arkanoid_PSID.sid;tune=2" # .sid example, plays the second tune of that<br />
<br />
If you like to test a .sid you can play it using this command on the FR:<br />
<br />
gst-launch filesrc location=Arkanoid_PSID.sid ! siddec tune=2 ! alsasink<br />
<br />
Note that it's a ! used and not a | to construct the gstreamer pipe command.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Profiles.png|200px|thumb|Profiles]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Profiles-Ringtones.png|200px|thumb|Ringtones]]<br />
<br />
|}<br />
<br />
====Settings: Connectivity====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Connectivity.png |200px|thumb|Connectivity top]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Connectivity2.png |200px|thumb|Connectivity bottom]]<br />
|}<br />
<br />
<br />
'''WiFi'''<br />
<br />
With the "WiFi radio" toggle you can set, if the wifi module is powered. WiFi radio has to be turned on before trying to connect to a WiFi network, unless you try to connect through [[Mokonnect]] which is capable of powering it up.<br />
<br />
'''GPRS'''<br />
<br />
To enter APN, login and password fields, just click on the actual value (default: "internet"). Keyboard will pop up.<br />
If you don't know APN, login and passwork, ask your provider.}}<br />
<br />
{{Note|You can also use Mokonnect to manage your GPRS connection}}<br />
<br />
To connect to the GPRS network, just click the "Connect" button. Entered values will be saved after successful connection.<br />
<br />
'''USB'''<br />
<br />
With this toggle you can switch USB port between device (Neo to PC) or host (device to Neo) modes.<br />
<br />
'''Bluetooth'''<br />
<br />
To power up Bluetooth module, switch the "Bluetooth radio" toggle to "On". After that, the "Visibility" toggle should arrive - set it to "On" if you want your FR to be visible by other Bluetooth devices on scanning.<br />
<br />
====Settings: GPS====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-GPS.png |200px|thumb|center|GPS]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-GPS-Satelites.png |200px|thumb|GPS Satelite details]]<br />
|}<br />
<br />
<br />
<br />
'''GPS'''<br />
<br />
By default, GPS is turned on only when requested (when you turn on TangoGPS, Navit, omgps or other GPS app). That state corresponds to "Auto" setting. After changing to "Manual", you can force set it to on or off.<br />
<br />
'''GPS information'''<br />
<br />
This page can be used to monitor GPS status. If some value isn't known, then "unknown" is displayed.<br />
<br />
You can also view information about every visible satellite and check, which are used for getting a fix. To do that, click "Satellite details".<br />
<br />
'''Remove AGPS data'''<br />
If you experience problems with GPS, turn it off, click "Remove AGPS data" and reboot your Neo.<br />
Assisted GPS ([[aGPS]]) support GPS receiver to find position by non-satellite information.<br />
<br />
'''Save downloaded maps of TangoGSP on Memory Card'''<br />
<br />
By default, TangoGPS will save your downloaded maps in /home/root/Maps. But it'll be inconvenient if you flashing again. You can change the path of folder Maps into a folder we created in Memory Card by using Config (Map Repositories) of TangoGPS.<br />
<br />
Otherwise, if you have a problem that can't change in that way. Don't be upset, there's another way. First you create a folder <tt>Maps</tt> on Memory Card: <br />
mkdir /media/mmcblk0/Maps<br />
Then you have to delete folder <tt>Maps</tt> in your home directory (e.g <tt>/home/root/Maps</tt> if it exists. <br />
rm -R /home/root/Maps<br />
Then we'll create a symbolic link ("-s") for the created Maps folder on Memory Card in your the home directory of root on the Phone by <br />
ln -s /media/mmcblk0/Maps /home/root/Maps<br />
That should be fine. From now, everytime when you download new maps, it'll be saved directly to folder <tt>Maps</tt> on Memory Card.<br />
<br />
<i>Note:</i> repeat the second and the third step (remove Maps in home/root and create link) have to be repeated if you want to link to the downloaded maps for TangoGPS after flashing phone.<br />
<br />
====Settings: Date/time====<br />
<br />
[[Image:SHR-Settings-Date-Time.png |200px|thumb|Date & Time]]<br />
<br />
'''Time'''<br />
<br />
Here you can view and set the time. By default, the time is just displayed, To adjust it, click on "Set time".<br />
<br />
After finishing adjusting, click the "OK" button.<br />
<br />
'''Date'''<br />
<br />
This module displays the current date.<br />
<br />
====Settings: Power====<br />
<br />
'''Battery'''<br />
<br />
This module displays informations about battery state - charge, voltage, remaining time etc. To update the data, click the "Update" button.<br />
<br />
Here you can also force enable 500mA charging.<br />
<br />
'''Display'''<br />
<br />
With this slider you can easily set the backlight brightness.<br />
<br />
{{Note|This setting isn't permanent over sessions. At boot backlight is set back to 100%.}}<br />
<br />
'''Power'''<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Power.png |200px|thumb|Power]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Timeouts.png |200px|thumb|Timeouts]]<br />
|}<br />
<br />
Here you can turn on or off automatic dimming or suspend after idle timeout (see: Timeouts module)<br />
<br />
'''Timeouts'''<br />
<br />
Here you can set up values of idle timeouts used by the device. Timeouts are reached in this order: idle -> idle dim -> idle prelock -> lock -> suspend. Idle, idle prelock and lock aren't used by default in SHR at the moment. This setting changes parameters in /etc/frameworkd.conf :<br />
<br />
[odeviced.idlenotifier]<br />
suspend = 20<br />
lock = 2<br />
idle_prelock = 12<br />
idle = 10<br />
idle_dim = 20<br />
<br />
====Settings: Services====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Services.png |200px|thumb|center|Services]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Service-restart.png |200px|thumb|Services debug screen]]<br />
|}<br />
<br />
Here is listed every interesting script from /etc/init.d/ directory.<br />
<br />
After clicking on one, you can either start, restart or stop the service and view the result.<br />
<br />
====Settings: Others====<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " |<br />
<br />
[[Image:SHR-Settings-Others.png |200px|thumb|Others]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:50% " | <br />
<br />
[[Image:SHR-Settings-Splash-Preview.png |200px|thumb|Splash preview]]<br />
|}<br />
<br />
'''Splash'''<br />
<br />
With this selector you can select the theme used by shr-splash at boot and shutdown. After clicking "Preview", the selected boot image will be displayed for 5 seconds.<br />
<br />
'''PIM'''<br />
<br />
Module used by opimd developers. Doesn't have influence on behaviour of default SHR image.<br />
<br />
Every opimd domain has different backends to store its data. The domain reads data from every backend and writes data to the default backend. So with the selector in shr-settings you can choose the backend that stores newly generated data, it doesn't copy or move existing data to a different backend.<br />
<br />
'''Userspace backups'''<br />
<br />
Here you can either archive or restore your files and configurations.<br />
<br />
'''Image information'''<br />
<br />
This module contains basic information about the installed image - name of buildhost, used revision, branch and time of build.<br />
<br />
'''Theming'''<br />
[[Image:SHR-Neo-Theme.png|200px|thumb|Neo theme]]<br />
Find available themes by running <br />
<br />
opkg list | grep theme-illume<br />
<br />
install it by<br />
<br />
opkg install e-wm-theme-illume-sixteen elementary-theme-sixteen<br />
<br />
http://opkg.org has a very fast theme called nEo<br />
<br />
opkg install http://www.opkg.org/packages/e-wm-theme-neo_0.2_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/elementary-theme-neo_0.2_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/etk-theme-neo_0.2_armv4t.ipk<br />
opkg install -force-overwrite http://www.opkg.org/packages/libframeworkd-phonegui-efl-theme-neo_0.2_armv4t.ipk<br />
<br />
If you also want the GTK+ Applications to fit in with the rest of the Systems look execute<br />
<br />
opkg install http://www.opkg.org/packages/gtk-theme-neo_0.1_armv4t.ipk<br />
<br />
For a completely monolithic look additionally execute<br />
<br />
opkg install -force-overwrite http://www.opkg.org/packages/gpe-theme-neo_0.1_armv4t.ipk<br />
opkg install http://www.opkg.org/packages/icon-theme-neo_0.2_armv4t.ipk<br />
<br />
Please observe the command line output when installing these themes, since it will tell you how to activate the themes.<br />
<br />
{{Note|some of the theme packages have to be reinstalled after an opkg upgrade.}}<br />
<br />
Reverting back can be done by <br />
<br />
opkg install e-wm-theme-illume-sixteen shr-theme-gtk-e17lookalike -force-reinstall<br />
opkg install libframeworkd-phonegui-efl0 e-wm-theme-default etk-theme-shr shr-theme -force-reinstall<br />
<br />
=== Illume settings ===<br />
<br />
The Illume desktop can be easily customized - slide the top shelf down and tap the Settings icon (Wrench).<br />
<br />
{{Note|TIP: for better access of the Settings icon, tap and hold the Settings icon, then drag it to the right.}}<br />
<br />
'''Illume settings''' (the wrench) provides various options to alter the desktop environment. You can change sizes of elements, single or double click, wallpaper. To access all the various options, open Illume Settings and slide the visible icons to the left, to preview more options on the right hand side.<br />
<br />
The little applets in the top shelf (for example Battery, GSM, Bluetooth etc.) are called '''shelf gadgets''' and you can configure whether they are visible (on the front part of the top shelf) or hidden (you can access them by sliding the top shelf) through Illume Settings -> Display -> Shelf gadget.<br />
<br />
Some screens are not resized properly to fit the phone's display - for example the Wallpapper setting. This is a known bug already reported upstream.<br />
<br />
<!-- [[Image:SHR-Top-Shelve.png|200px|thumb|Top Shelf]] --><br />
<br />
==FSO Resources==<br />
<br />
FSO is in control of each device. These are called ''resources''. If the software wanting to use the device is capable of requesting this resource via <tt>d-bus</tt>, FSO will do this, otherwise you might need to power the device manually. After the requested resource is released, FSO will power it down. Manual resource request can be done through ''SHR Setting'' or you can use <tt>fsoraw</tt> command. (Using fsoraw is faster and better then running dbus commands)<br />
<br />
opkg install fsoraw<br />
<br />
Example of usage fsoraw:<br />
<br />
fsoraw -r Display mokomaze<br />
<br />
See [[FSO Resources]] for more details on using the following resources:<br />
<br />
'''Wifi'''<br />
<br />
Unless this resource is enabled you've no eth0 and wifi module is completely un-powered. Use the network manager to set up networks, [[Mokonnect]] will power Wifi up automatically when needed.<br />
<br />
'''Bluetooth'''<br />
<br />
You need to have this resource requested to have bluetooth module powered.<br />
<br />
'''GPS'''<br />
<br />
The fso-gpsd is a daemon waiting for gsmd connections, automatically powering the device on and off. When a connection exists, it powers up the GSM. In SHR Settings you can switch GPS completely off SHR Settings -> GPS -> Manual > Off<br />
<br />
'''GSM'''<br />
<br />
You need to have this resource requested to have GSM module powered.<br />
<br />
'''Display'''<br />
<br />
While this resource is requested the display won't be blanked and suspend is disabled.<br />
<br />
'''CPU'''<br />
<br />
Default rules.yaml checks for this resource to disable automatic suspend when it's requested. While this resource is kept suspend is disabled (but screen can be blanked).<br />
<br />
'''Test'''<br />
<br />
A test resource<br />
<br />
==Network manager==<br />
<br />
While there are several ways of networking - Wifi, USB, Bluetooth and Gprs - By default, USB networking is enabled in <tt>/etc/network/interfaces</tt>.<br />
<br />
Enhanced configuration is possible through direct editing of /etc/network/interfaces or through [[Mokonnect]].<br />
<br />
The <tt>connmand</tt> daemon with Mokonnect are the recommended user level applications for setting up networking. At the moment, Mokonnect can manage USB, Wifi and Gprs connections, as well as routing and NAT. The Wifi device is not required to be manually turned on via SHR-Settings as Mokonnect will automatically enable the device when needed and disable it after use.<br />
<br />
{| class="wikitable" cellspacing="0" cellpadding="0" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #c0c0c0; background:#eeeeee; floating="center";width:100%; "<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " |<br />
[[Image:SHR-Mokonnect.png|200px|thumb|Mokonnect]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokonnect-Wifi.png|200px|thumb|Mokonnect Wifi]]<br />
<br />
! style="background:#fcfcfc;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:0px solid #222222; width:33% " | <br />
<br />
[[Image:SHR-Mokonnect-Wifi-Scan.png|200px|thumb|Mokonnect Wifi Scan]]<br />
<br />
<br />
|}<br />
<br />
==Bluetooth==<br />
<br />
Bluetooth can be used for several different applications - file transfer, networking, HIDD, music playing (A2DP), calling etc. In some occasions, the devices need to be authorized - paired. At the moment, support for some bluetooth functions is better than for others - it is possible to do all mentioned above with the notice that phone calls with bluetooth headset are always routed to the bluetooth even if it is not around, making it quite difficult to use.<br />
<br />
Don't forget you need to turn the bluetooth radio on in SHR Settings -> Connectivity -> Bluetooth Radio: On, where you can also make the bluetooth device visible.<br />
<br />
SHR uses bluez4 which is completely different from bluez3. The bluetoothd is taking care of most of the bluetooth now. Please see [[Manually using Bluetooth]] for detailed information about using bluetooth and also for a list of supported devices.<br />
<br />
===OBEX file transfer===<br />
<br />
There are several obex programs allowing file transfer, all in console at the moment. Obexpush installs obextool, and opd daemon:<br />
<br />
opkg install obexpush<br />
<br />
Default receiving path (editable in /etc/default/opd_args ) does not exist, so create it<br />
<br />
mkdir /var/obexpush<br />
<br />
Files are then received automatically, no notice, no confirmation... they just silently appear in /var/obexpush<br />
<br />
To send some files, first scan for devices:<br />
<br />
hcitool scan<br />
Scanning ...<br />
00:16:41:F5:A5:BC laptop<br />
<br />
Then send it onto bt address found in the scan:<br />
<br />
obextool push image.jpg 00:16:41:F5:A5:BC 10<br />
<br />
===Connect Bluetooth keyboard===<br />
<br />
hidd --search<br />
<br />
Editors note: This is the old bluez3 way, but it works. New bluez4 way will replace this.<br />
<br />
===Pairing===<br />
<br />
This comes from [[Manually_using_Bluetooth#Once_Again.2C_Bluetooth_Headset_on_Freerunner]]<br />
<br />
Now, you must pair the bluetooth headset with your phone. Make sure the bluetooth chip is powered up (can be done through the Connectivity section in the SHR-Unstable settings manager) and that bluetoothd is running:<br />
/etc/init.d/bluetooth start<br />
Now, to actually pair the bluetooth headset, you will need the simple-agent script. If you already have it, excellent. If you, like me, do not, then you can get it here: http://dl.getdropbox.com/u/453116/simple-agent<br />
<br />
Put it in /usr/bin/ and run ===chmod a+x /usr/bin/simple-agent===<br />
<br />
Now put your headset into pairing mode and run <br />
<br />
hcitool scan<br />
<br />
Find your headset and use its address in the command <br />
<br />
simple-agent hci0 XX:XX:XX:XX:XX:XX<br />
<br />
If you give a third parameter (what it is doesn't matter) to simple-agent, it will disconnect then reconnect to the headset (reset pairing).<br />
<br />
<br />
<br />
===GSM phone calls with bluetooth headset===<br />
<br />
Your bluetooth headset device must be paired first.<br />
<br />
====Configuring bluez====<br />
<br />
Older SHR releases you need to uncomment <tt>SCORouting=PCM</tt> setting in <tt>[General]</tt> section of<br />
<br />
/etc/bluetooth/audio.conf<br />
<br />
like this:<br />
<br />
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA) <br />
# Defaults to HCI <br />
SCORouting=PCM <br />
<br />
do not forget to restart bluetoothd after that.<br />
<br />
/etc/init.d/bluetooth stop<br />
/etc/init.d/bluetooth start<br />
<br />
====Configuring FSO====<br />
<br />
Now we must tell frameworkd that you have a bluetooth headset. Headset parameters should be set in<br />
<br />
/etc/freesmartphone/opreferences/conf/phone/default.yaml<br />
<br />
Parameters bt-headset-enabled and bt-headset-address (see opreferences/schema/phone.yaml for semantics).<br />
<br />
You need to restart FSO for the changes to take effect.<br />
<br />
/etc/init.d/frameworkd restart<br />
<br />
example of my /etc/freesmartphone/opreferences/conf/phone/default.yaml:<br />
<br />
message-length: 7<br />
message-tone: notify_message.wav<br />
message-vibration: 1<br />
message-volume: 10<br />
ring-loop: 1<br />
ring-tone: ringtone_ringnroll.wav<br />
ring-vibration: 1<br />
ring-volume: 10<br />
bt-headset-enabled: 1<br />
bt-headset-address: 00:09:DD:31:92:98<br />
<br />
====Re-Connecting the bt device====<br />
<br />
You might need to get the bluetooth headset connected manually on the beginning and also after suspend:<br />
<br />
mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect<br />
<br />
where xx_xx_xx_xx_xx_xx is address of the device, for example:<br />
<br />
mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect<br />
<br />
Hopefully, your bluetooth headset now works. Good luck!<br />
<br />
==System Customizing==<br />
<br />
===Changing the splash screen===<br />
<br />
list available splash screen themes<br />
<br />
opkg list | grep splash-theme<br />
<br />
and install one of the available themes<br />
<br />
opkg install shr-splash-theme-dontpanic<br />
<br />
Then go to SHR Settings -> Others -> Themes. Here you can preview installed themes and change the default one.<br />
<br />
===Enable mouse cursor=== <br />
<br />
edit line 121 of /etc/X11/Xinit and erase -hide-cursor<br />
<br />
ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} -mouse tslib -root-ppm /usr/share/pixmaps/xsplash-vga.ppm vt1"<br />
<br />
<br />
<br />
===Speedup of suspend and wake up===<br />
<br />
Some setup types of the bootloader are causing slow suspending and waking up through a long console output. ([http://shr-project.org/trac/ticket/351 bug report]) This occurs when using the the Qi bootloader in combination with an installation on an SD card and when using the u-boot bootloader. <br />
<br />
I you are using Qi and installation on a µSD card, you can change the kernel parameter loglevel=1 in /boot/append-GTA02.<br />
<br />
===Opimd utils===<br />
<br />
Opimd utils is a set of several testing scripts to play with the new opimd backends. It also provides opimd-messages program and mainly new opimd-notifier <br />
that is much better then the standard one.<br />
<br />
For further Information refer to the corresponding [[Opimd|Wiki Page]].<br />
opkg install opimd-utils<br />
<br />
{{Note| opimd-utils isn't announced yet! It can eat your cat! Don't touch it unless you are opimd developer or you are writing app with opimd support.<br />
<br />
'''NOTE 2:''' In order to have sound and vibration on incoming message when using opimd interface, you have to patch oeventsd with patch available at [http://openmoko.opendevice.org/~dos/opimd/oeventsd/]<br />
<br />
'''NOTE 3:''' For testing and development opimd recommended distribution is ''upgraded'' SHR unstable.<br />
}}<br />
<br />
===opkg upgrade issues===<br />
<br />
As '''opkg''' had some '''issues''' recently, installation might get broken due to that. You can fix it or prevent by using the following scripts<br />
<br />
Safe update packages:<br />
<br />
#!/bin/sh<br />
<br />
for pkg in `opkg list_upgradable | awk '!/(kernel|Multiple)/ {print $1}'`<br />
do<br />
echo "installing pack $pkg"<br />
opkg install $pkg -force-reinstall<br />
done<br />
<br />
<br />
Force reinstall all installed packages:<br />
<br />
#!/bin/sh<br />
<br />
for pkg in `opkg list_installed | awk '!/(kernel|Multiple)/ {print $1}'`<br />
do<br />
echo "installing pack $pkg"<br />
opkg install $pkg -force-reinstall<br />
done<br />
<br />
===Random errors===<br />
No icons, no GSM functions etc. - this is mostly due to '''errors on your µSD''' card. Remove your card and fix it in card reader or by booting to another partition (nand) or by reboot and mount read only, then run fsck.<br />
<br />
For reboot into nand and fix 1st partition of ext2 on your card<br />
<br />
fsck.ext2 /dev/mmcblk0p1<br />
<br />
===Replace dropbear with openssh===<br />
<br />
Set password<br />
passwd<br />
<br />
Install ssh server (and sftp)<br />
opkg install openssh-sshd openssh-sftp-server openssh-scp -force-depends<br />
<br />
Remove dropbear and start openssh<br />
<br />
screen<br />
opkg remove dropbear -force-depends; /etc/init.d/sshd start<br />
<br />
You will get disconnected from the ssh session, wait until keys get generated and log in again.<br />
{{Note|'''Remove old SSH Key from <tt>.ssh/known_hosts</tt>:''' On your Linux box you will find a file <tt>known_host</tt> in the subdirectory <tt>.ssh/</tt> in you home directory. This contains a ssh key for the connection to your phone. If new keys are generated or if you flash your phone with SHR then you have to remove the line with <tt>openmoko</tt> or the IP-address of your phone from the file. Otherwise you might not be able to login in again until the former key is removed from <tt>known_hosts</tt>. If several distributions are alternately used on the same particular phone, it may be more convenient to copy the key files from one phone distribution to the rest. }}<br />
<br />
<br />
<br />
===Adding your phone to your hosts=== <br />
<br />
You can add your phone to your hosts file for a name resolving:<br />
<br />
You can use the name <tt>neo</tt> if you added the host <tt>neo</tt> in <tt>/etc/hosts</tt> on your desktop computer (add the following line for host <tt>neo</tt> assuming that the IP-address of your phone is <tt>192.168.0.202</tt>.<br />
echo "192.168.0.202 neo neo" >> /etc/hosts<br />
<br />
You can then access your phone like this:<br />
<br />
ssh root@neo<br />
<br />
Which is shorter than this:<br />
<br />
ssh root@192.168.0.202<br />
<br />
==Installing Software==<br />
<br />
You can use opkg for installing software packages or you can try SHR Installer from http://git.shr-project.org/git/?p=shr-installer.git;a=summary . It requires packagekitd<br />
<br />
opkg install packagekitd<br />
<br />
If you wan to use opkg after you used the installer, make sure packagekitd is not running<br />
<br />
killall packagekitd <br />
<br />
'''Cool applications'''<br />
<br />
SHR comes with only a few preinstalled applications but its repository provides more cool stuff. Also, there are applications that are not in SHR repos at the moment but can still be installed. The following few examples are here just to spark your interest:<br />
<br />
'''[[Paroli]]''' is available in SHR images, you can install it:<br />
<br />
opkg install paroli<br />
<br />
fix the conf files that the paroli installer messes with (might get fixed in the next couple of days.)<br />
<br />
cp /etc/old_frameworkd.conf /etc/frameworkd.conf<br />
cp /etc/freesmartphone/oevents/old_rules.yaml /etc/freesmartphone/oevents/rules.yaml<br />
<br />
now if you want to disable the shr phone apps without removing them comment all of the lines out in <br />
<br />
/etc/X11/Xsession.d/89notifier and /etc/X11/Xsession.d/80ophonekitd<br />
<br />
if you want the bind-home to ease upgrades add this line to fstab.<br />
<br />
/media/card/bind-home /home/root none bind 0 0<br />
<br />
You should now have a functional paroli on SHR setup. Once you have a working setup I would advise against doing opkg upgrades and only upgrade specific packages when needed.<br />
<br />
<br />
[[Category:SHR]]</div>Sybrenhttp://wiki.openmoko.org/wiki/StorageSpeedStorageSpeed2009-07-03T15:49:00Z<p>Sybren: </p>
<hr />
<div>Here is the result of a little speed test I ([[User:Sybren|sybren]]) performed on the NAND and my 2 GB micro-SD card:<br />
<br />
SD (Transcend 2GB uSD card):<br />
<br />
root@moko ~ $ hdparm -tT /dev/mmcblk0p2<br />
<br />
/dev/mmcblk0p2:<br />
Timing cached reads: 46 MB in 2.05 seconds = 22.45 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 4 MB in 4.54 seconds = 902.06 kB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
<br />
NAND:<br />
<br />
root@moko ~ $ hdparm -tT /dev/mtdblock6<br />
<br />
/dev/mtdblock6:<br />
Timing cached reads: 50 MB in 2.06 seconds = 24.26 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 6 MB in 3.20 seconds = 1.88 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
<br />
So it appears that the NAND (/dev/mtdblock6) is roughly twice as fast as the SD card. The test was run on a Neo Freerunner (hardware revision A6) using SHR Unstable, kernel 2.6.29-rc3. Wifi and GSM were enabled, and the device was hooked up to my desktop computer using USB. GPS was disabled, as was GPRS.</div>Sybrenhttp://wiki.openmoko.org/wiki/StorageSpeedStorageSpeed2009-07-03T15:48:48Z<p>Sybren: </p>
<hr />
<div>Here is the result of a little speed test I ([[User:Sybren|sybren]]) performed on the NAND and my 2 GB micro-SD card:<br />
<br />
SD (Transcend 2GB uSD card):<br />
<br />
root@moko ~ $ hdparm -tT /dev/mmcblk0p2<br />
<br />
/dev/mmcblk0p2:<br />
Timing cached reads: 46 MB in 2.05 seconds = 22.45 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 4 MB in 4.54 seconds = 902.06 kB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
root@moko ~ $ hdparm -tT /dev/mtdblock6<br />
<br />
NAND:<br />
<br />
root@moko ~ $ hdparm -tT /dev/mtdblock6<br />
<br />
/dev/mtdblock6:<br />
Timing cached reads: 50 MB in 2.06 seconds = 24.26 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 6 MB in 3.20 seconds = 1.88 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
<br />
So it appears that the NAND (/dev/mtdblock6) is roughly twice as fast as the SD card. The test was run on a Neo Freerunner (hardware revision A6) using SHR Unstable, kernel 2.6.29-rc3. Wifi and GSM were enabled, and the device was hooked up to my desktop computer using USB. GPS was disabled, as was GPRS.</div>Sybrenhttp://wiki.openmoko.org/wiki/StorageSpeedStorageSpeed2009-07-03T15:48:28Z<p>Sybren: Added hdparm commands</p>
<hr />
<div>Here is the result of a little speed test I ([[User:Sybren|sybren]]) performed on the NAND and my 2 GB micro-SD card:<br />
<br />
SD (Transcend 2GB uSD card):<br />
<br />
root@moko ~ $ hdparm -tT /dev/mmcblk0p2<br />
/dev/mmcblk0p2:<br />
Timing cached reads: 46 MB in 2.05 seconds = 22.45 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 4 MB in 4.54 seconds = 902.06 kB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
root@moko ~ $ hdparm -tT /dev/mtdblock6<br />
<br />
NAND:<br />
<br />
root@moko ~ $ hdparm -tT /dev/mtdblock6<br />
/dev/mtdblock6:<br />
Timing cached reads: 50 MB in 2.06 seconds = 24.26 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 6 MB in 3.20 seconds = 1.88 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
<br />
So it appears that the NAND (/dev/mtdblock6) is roughly twice as fast as the SD card. The test was run on a Neo Freerunner (hardware revision A6) using SHR Unstable, kernel 2.6.29-rc3. Wifi and GSM were enabled, and the device was hooked up to my desktop computer using USB. GPS was disabled, as was GPRS.</div>Sybrenhttp://wiki.openmoko.org/wiki/StorageSpeedStorageSpeed2009-07-03T15:47:10Z<p>Sybren: </p>
<hr />
<div>Here is the result of a little speed test I ([[User:Sybren|sybren]]) performed on the NAND and my 2 GB micro-SD card:<br />
<br />
SD (Transcend 2GB uSD card):<br />
<br />
root@moko ~ $ hdparm -tT /dev/mmcblk0p2<br />
<br />
/dev/mmcblk0p2:<br />
Timing cached reads: 46 MB in 2.05 seconds = 22.45 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 4 MB in 4.54 seconds = 902.06 kB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
root@moko ~ $ hdparm -tT /dev/mtdblock6<br />
<br />
NAND:<br />
<br />
/dev/mtdblock6:<br />
Timing cached reads: 50 MB in 2.06 seconds = 24.26 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 6 MB in 3.20 seconds = 1.88 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
<br />
So it appears that the NAND (/dev/mtdblock6) is roughly twice as fast as the SD card. The test was run on a Neo Freerunner (hardware revision A6) using SHR Unstable, kernel 2.6.29-rc3. Wifi and GSM were enabled, and the device was hooked up to my desktop computer using USB. GPS was disabled, as was GPRS.</div>Sybrenhttp://wiki.openmoko.org/wiki/StorageSpeedStorageSpeed2009-07-03T15:44:31Z<p>Sybren: Added hdparm test</p>
<hr />
<div>Here is the result of a little speed test I ([[User:Sybren|sybren]]) performed on the NAND and my 2 GB micro-SD card:<br />
<br />
SD:<br />
<br />
root@moko ~ $ hdparm -tT /dev/mmcblk0p2<br />
<br />
/dev/mmcblk0p2:<br />
Timing cached reads: 46 MB in 2.05 seconds = 22.45 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 4 MB in 4.54 seconds = 902.06 kB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
root@moko ~ $ hdparm -tT /dev/mtdblock6<br />
<br />
NAND:<br />
<br />
/dev/mtdblock6:<br />
Timing cached reads: 50 MB in 2.06 seconds = 24.26 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
Timing buffered disk reads: 6 MB in 3.20 seconds = 1.88 MB/sec<br />
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate ioctl for device<br />
<br />
So it appears that the NAND (/dev/mtdblock6) is roughly twice as fast as the SD card. The test was run on a Neo Freerunner (hardware revision A6) using SHR Unstable, kernel 2.6.29-rc3</div>Sybrenhttp://wiki.openmoko.org/wiki/Neo_FreeRunner_HardwareNeo FreeRunner Hardware2009-07-03T15:40:44Z<p>Sybren: Added section about the SD card reader.</p>
<hr />
<div>{{Languages|Neo FreeRunner GTA02 Hardware}}<br />
<br />
{{gta02menu}}<br />
<br />
The [[Neo FreeRunner]] phone is the second hardware platform to take advantage of the Openmoko software stack. You can find specifications of the hardware by reviewing this introduction page and the pages in the category as shown at the bottom of this page.<br />
<br />
For basic details please see the Customer-oriented specifications.<br />
<br />
=Photos=<br />
<gallery><br />
Image:Gta02a5 pcba cs.JPG|component (back) side NOTE: GTA02 A5 PCBA Component Side photo<br />
Image:Gta02a5 pcba ps.JPG|display (top) side NOTE: GTA02 A5 PCBA Print Side photo<br />
Image:GTA02 A5 PCB CS.jpg|component (back) side NOTE: GTA02 A5 PCB Component Side photo<br />
Image:GTA02 A5 PCB PS.jpg|display (top) side NOTE: GTA02 A5 PCB Print Side photo<br />
Image:SimpleComponentDiagram.jpg|Simplified Hardware Component Diagram<br />
</gallery><br />
<br />
<br />
=Features=<br />
*Display- Topply o2.8, 480 x 640 pixels, VGA, 200 NIT minimum, resistance type touch<br />
<br />
*User Interface Navigation- Touch screen on LCD, 2 control “buttons”, 1 Power button, 1 Aux for 911 emergency call<br />
<br />
*Built-in 802.11b/g Radio (Atheros chipset AR6001 Flash version)<br />
<br />
*Built-in Bluetooth 2.0 + EDR (CSR and support PCM audio , BC4 firmware version)<br />
<br />
*Built-in 2D/3D graphics acceleration chip (S-Media 3362)<br />
<br />
*2 built-in Tri-Axis sensors (ST accelerometer LIS302DL)<br />
<br />
*Built-in GPS Radio – -130 dBm with internal antenna, -157 dBm tracking on chipset specification, TTFF under 40 seconds with -130 dBm signal strength, and tracking (u-Blox)<br />
<br />
*Antenna – Specialized antenna for best in hand hold GPS, GPRS and Wi-Fi/Bluetooth performance are required, -105dBm on receiving, Tx 30dbm+2 on GSM<br />
<br />
*External Antennae – MMCX GPS connector<br />
<br />
*GPRS Radio –GSM/GPRS radio. A Pre-PTCRB certified module will be preferred<br />
<br />
*Linux – Linux kernel 2.6.24 or later Openmoko kernel<br />
<br />
*USB - Client and Host-mode switchable (to be used for software downloading), provide host 5V power<br />
<br />
*Power- Normal mode power will be via 1200 mAh battery with built-in coulomb counter, could charge via specialized charger. Internal Lithium Ion or Lithium Polymer battery will keep device in standby mode. Battery life (Approximation/Ideal Target) Standby time 70h Hrs (GSM) Talk time (Backlight off) Up to 3-4 hrs(GSM)<br />
<br />
*LED- LED indicator under Aux/Power button key<br />
<br />
=Hardware Specification=<br />
<br />
[http://downloads.openmoko.org/developer/schematics/GTA02/Schematics_Freerunner-GTA02_A5-A7cumulative_public_RC0.pdf Full schematics] are available.<br />
<br />
===Hardware Electrical===<br />
<br />
*400/500 MHz Samsung 2442B Processor/SOC (400 minimum, ARM920T core, ARMv4T)<br />
*Unbrickable dual Boot code in NAND FLASH and 2MB NOR FLASH<br />
*128 MB SDRAM total, 64 MB CPU internal, 64 MB external<br />
*256MB NAND Flash MCP package.<br />
<br />
=== Display ===<br />
* Topploy VGA, 16 bit color depth<br />
* resolution: 480 x 640 pixels<br />
* size: 43mm x 58mm (1.7” x 2.27”)<br />
* diagonal: 72.2mm (2.84”)<br />
* Transmissive display: good readability in high ambient light is essential<br />
* White LED backlight. Required brightness is 200 NIT minimum.<br />
* Resistance type touch panel.<br />
<br />
=== WiFi 802.11 b/g transceiver ===<br />
*Must have GPL support source or GPL compatible policy<br />
*TX power at 11 Mbps: 13 dBm minimum<br />
*RX sensitivity at 11 Mbps: -89 dBm desired, -83 dBm minimum<br />
*AP mode desirable, not required<br />
*WEP and WPA supported<br />
*Atheros preferred because of its GPL policy<br />
<br />
=== Serial interfaces (UART) ===<br />
*Three serial interfaces are required<br />
*Console<br />
*A-GPS or GPS<br />
*GSM/GPRS<br />
<br />
=== Accelerometer ===<br />
* 2x accelerometer required<br />
* Could support interrupt while suspend or power save mode<br />
* 3 axis sensing<br />
<br />
=== A-GPS ===<br />
*GPS chipset receiver and antenna<br />
*Sensitivity at Antenna port: -157 dBm tracking on chipset specification<br />
*LNA and SAW filter for maximum interference protection<br />
*Cold start time to first fix: 40 sec typical at -130 dBm, 60 sec max<br />
*Must support GPL for Assist-GPS function with open API<br />
*Industry quality GPS<br />
*Could fit in GTA01 GPS area on the PCB<br />
<br />
=== GPS Antenna Performance ===<br />
*Antenna is passive and internal; 15 mm x 15 mm ceramic patch is nominal design<br />
*Antenna LNA and SAW filter are required to meet GPS performance<br />
*15 mm square ground plane (minimum 1 mm ground border around patch) (TBA)<br />
*There will be one external GPS antenna connector (MMCX)<br />
*C/N ratio should higher than 35 on production testing<br />
<br />
=== Buttons ===<br />
*Touch screen over LCD is primary data entry mechanism<br />
*Two “hard” buttons: Power button (on side of Neo1973) is a mechanical switch actuated by a plastic pushbutton in a hole in the housing. Aux (911) button on the top of the device, both of these buttons, when pushed by the operator, are binary inputs (on/off or pressed/not pressed) to the software. The effect of each button is determined by the application software in the device<br />
*Buttons may need to be backlit<br />
*50000 cycles on hardware specification<br />
<br />
=== Sound outputs ===<br />
*Speaker in box (need good volume and acoustic behavior in noisy environments)<br />
*Audio is monophonic<br />
*Max volume: 100 dB at 5 cm to assure good performance in environment.<br />
*Support earphone with mic by jack<br />
<br />
=== Power Design Requirements===<br />
*Software-based power management unit preferred<br />
*NXP PCF series preferred<br />
*Need support charge from USB function<br />
*Need support powered by USB function<br />
*Power switch: Neo1973 will have a power switch, for power on/off and suspend<br />
* Power/Aux switch must be backlit<br />
*Switch controls whether device is running or suspended by presses of the switch<br />
*Switch does not shut off the power; it only suspends/resumes the device<br />
*Internal Li-Ion or Li-Polymer battery is included. This battery supplies standby power to the device eliminates the rebooting of the device when local power is again reapplied. Battery is 1200 ma-hr.<br />
*Battery life (Approximation) Ideal/Target Standby time 150-200 Hrs (GSM) Talk time (Backlight off) Up to 4 hrs(GSM)<br />
*Estimated current draw for the entire device when in suspend mode (and ALL peripherals are turned off or set for deep sleep) is <5 mA at 3.6 volts (Li-Ion terminal voltage).<br />
*GSM module deep sleep(alive and keep contact with base station) stage should take less than 8mA<br />
*Battery will reach half capacity (~600 mAh) with 500 charge-discharge cycles. This will occur in less than 2 years of daily service.<br />
*When powered continuously, Neo1973 must suspend (to low power mode) based either on observed low battery voltage condition or a configurable time delay.<br />
*Neo1973 must monitor battery status while suspended and resume automatically if the charger is inserted.<br />
*Primary power connection: 1200mAh battery<br />
*USB charger have ID pin 47.5k pull down for Openmoko identification<br />
*Indicators: an LED indicator visible from the side of the unit will illuminate when charging or have missing incoming call<br />
<br />
=== GSM/GPRS ===<br />
*850/1800/1900 and 900/1800/1900 MHz bands must be supported<br />
*Design should allow for multi-band version (850/900 MHz)<br />
*Module based GPRS transceiver could meet PTCRB and appropriate FCC certifications. It preferred that the module be pre-certified with PTCRB or OTA test<br />
*FCC/CE certification required for GSM/GPRS part<br />
<br />
=== GSM-GPRS Antenna Performance ===<br />
*-105 dBm receiving on each channel (GSM/PCS)<br />
*30+2 dBm transmission on GSM channel<br />
<br />
=== SD card reader ===<br />
<br />
*One micro-SD card reader, compatible with SD and SDHC.<br />
<br />
A small speed test can be found on the [[StorageSpeed]] page.<br />
<br />
=== Wi-Fi Modules ===<br />
*Must support GPL driver<br />
*Atheros AR6k preferred<br />
*Flash version required<br />
<br />
=== Wi-Fi Antenna Performance ===<br />
*The Wi-Fi antenna with TX 13 to 15 dBm<br />
*RX -89 to -83 dBm @802.11b 11Mbps or an equivalent performance antenna<br />
<br />
=== Bluetooth ===<br />
*CSR BC4 or later solutions<br />
<br />
=== USB ===<br />
*Neo FreeRunner GTA02 will have USB, client/host. Using USB 1.1<br />
*Provides USB host 5v power<br />
*Could be powered by USB<br />
<br />
=== Microphone ===<br />
1 microphone is in the device<br />
<br />
=== Firmware Image ===<br />
*Using Linux 2.6.24 or later<br />
*Could support booting from NAND or from NOR<br />
*Shipping image should come with basic phone function<br />
*Could do full firmware upgrade by USB cable<br />
<br />
=== PSN ===<br />
*Device will have a PSN (product serial number) printed on the product label and machine readable in system NAND memory<br />
<br />
=== IMEI ===<br />
*Production phase should have IMEI code written<br />
<br />
= Package Specification =<br />
*Weight: ~133 grams with battery.<br />
*4-in-1 laser pen passed RoHs and safety regulation for laser equipment safety<br />
*1x 512MB microSD Card ([http://www.sandisk.com/ SanDisk] / [http://www.transcendusa.com/ Transcend] [http://www.transcendusa.com/Support/DLCenter/Datasheet/TSxxUSD.pdf TS512MUSD])<br />
*1x USB cable Standard A to mini-B connector<br />
*1x 1200mAh smart/gauge battery<br />
*Quick start guide<br />
*5v USB power cord w/100-240 switchable power plug<br />
*Safety card, warranty card<br />
*Package could pass 1m to 1.5m drop test<br />
*AC USB charger,100v-240v, Passed UL and all required safety regulations<br />
*Must pass FCC/CE certification<br />
*Must pass NCC certification for Taiwan import regulation<br />
*RoHS Compatible<br />
*WEEE Report required<br />
<br />
= Life Cycle Specification =<br />
<br />
=== Product Life ===<br />
The product is designed to last a minimum of 2 years.<br />
<br />
=== Operating Temperature ===<br />
*Target operating range is –10°C to +60°C<br />
<br />
=== Storage Temperature ===<br />
*-15 deg C to +70 deg C<br />
<br />
=== ESD ===<br />
The device can withstand a 4.0kV contact discharge and 8.0kV air<br />
<br />
=== Drop test ===<br />
Should pass 1m direct drop to concrete ground or 1.5m on slide with carpet<br />
<br />
<br />
= GTA02 Hardware Component Selection =<br />
<br />
== Physical Dimensions ==<br />
* 120.7 x 62.0 x 18.5 mm (4.752 x 2.441 x 0.728 inch)<br />
* 110 +/- 5 g (4 ounces) without battery <br><br />
<br />
== Main components ==<br />
=== Processor ===<br />
The main Processor (CPU) of the Neo1973 GTA02 is a [[Samsung S3C2442B B54]] (running at 400 MHz)<br />
<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 Samsung SC32442B]<br />
* User Manual: [http://210.118.57.197/Products/Semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/SC32442/um_s3c2442b_rev12.pdf Samsung SC32442B]<br />
* Core: ARM920T<br />
* Instruction Set: ARMv4<br />
* Built-in 64MB SDRAM<br />
* Built-in 256 MB NAND<br />
* GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/GTA02v4/gpio.txt<br><br />
* Evaluation board: [http://www.meritech.co.kr/products/product_view.php?num=52 S3C2442 EVB]<br />
<br />
=== Power Management ===<br />
A NXP PCF50633 04 N3 is used for [[Neo1973_Power_Management|power management]].<br />
<br />
* NXP PMU index: [http://www.nxp.com/products/power_management/pmu/index.html NXP PMU index page]<br><br />
* Product Datasheet: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf NXP PCF50633 Product Data Sheet]<br><br />
* Product User manual: [http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633UM_6.pdf NXP PCF50633 User Manual]<br><br />
**Special thanks to NXP for providing a complete user manual and for supporting all developers<br />
**Datasheet/User manual usage [http://lists.openmoko.org/pipermail/community/2008-March/013898.html was legally authorized by NXP]<br />
* Connected to: S3C2442 via I2C, client address is 0x08. <br><br />
* Driver Source: https://svn.openmoko.org/trunk/src/target/kernel/patches/pcf50633.patch<br><br />
<br />
=== Flash ===<br />
==== NAND Flash ====<br />
256MB integrated Samsung NAND flash inside the 2442 multi-chip package, attached to the S3C2442 NAND controller<br />
<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=229&partnum=SC32442 S3C2442]<br />
* Data Sheet: S3C2442 B54 comes with 256 MB NAND MCP package<br />
* Connected to: S3C2442 NAND controller<br><br />
<br />
==== NOR Flash ====<br />
<br />
16MBit ST M58WR016KB706E NOR flash for 'unbrickable emergency boot' feature.<br />
<br />
* Product Homepage: [http://www.st.com/stonline/products/families/memories/fl_nor_mob/index.htm ST Mobile Flash NOR/Mobile Terminal]<br />
* Data Sheet: [http://www.numonyx.com/Documents/Datasheets/M58WRxxxKTB.pdf M58WR016]<br />
* Connected to: S3C2442 NAND controller<br><br />
<br />
=== SDRAM ===<br />
128MB SDRAM (64MB inside 2442 MCP, 1x Samsung K4M51323PC) attached to S3C2442 SDRAM controller<br />
* Product Homepage: [http://www.samsung.com/global/business/semiconductor/productInfo.do?fmly_id=136&partnum=K4M51323PC Samsung K4M51323PC]<br />
* Data Sheet: [http://www.samsung.com/global/system/business/semiconductor/product/2007/6/11/MobileSDRAM/MobileSDRSDRAM/512Mbit/K4M51323PC/ds_k4m51323pc.pdf Samsung K4M51323PC]<br />
* Connected to: S3C2442 <br><br />
<br />
== GSM/GPRS ==<br />
The [[GSM]] (including GPRS) modem is Texas Instruments Calypso based.<br />
<br />
* Connected to: S3C2442 UART1 (full-uart, RxD, TxD, CTS, RTS), /dev/ttySAC0 in userspace<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br />
* Accessible GSM/GPRS antenna jack (if battery cover is removed)<br><br />
<br />
=== CALYPSO ASIC digital baseband ===<br />
Unfortunately we cannot provide many details on the GSM chipset due to very tight [http://en.wikipedia.org/wiki/Non-disclosure_agreement NDA]s. However, this is not neccessarily required, since it interfaces using a standard UART serial line with the S3C2442. On that interface, [http://www.3gpp.org/ftp/Specs/archive/07_series/07.05/ GSM 07.05], [http://www.3gpp.org/ftp/Specs/archive/07_series/07.10/ GSM 07.10] and other standardized protocols are used.<br />
<br />
The NDAd documentation for the calypso, [http://cryptome.org/ti-calypso1.pdf register definition ] and [http://cryptome.org/ti-calypso2.pdf hardware definition ] was leaked onto a public forum on the 4th of March by persons or persons unknown.<br />
The legality of reading these files may vary according to your local laws, as may generating code from them.<br />
<br />
<br />
*Calypso D751992AZHH<br><br />
*The firmware within GTA02 should be moko6 or later (internal code name)<br />
<br />
=== TI TWL3025BZGMR analog baseband ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12295&contentId=4703 TWL3014]<br><br />
<br />
=== TI TRF6151 (GSM/PCS) RF Transceiver ===<br />
*Product Homepage: [http://focus.ti.com/general/docs/wtbu/wtbuproductcontent.tsp?templateId=6123&navigationId=12296&contentId=4701 TRF6151] <br><br />
GPRS Class12/CS4 <br><br />
<br />
== AGPS ==<br />
u-blox ANTARIS 4 chip<br />
* Connected to: S3C2442 UART2, /dev/ttySAC1 in userspace<br />
* Driver: none needed, talks standard NMEA<br />
* u-blox Antaris 4 Protocol [http://www.u-blox.com/customersupport/antaris_doc.html Protocol download page]<br />
* ATR0635 Datasheet: [http://www.u-blox.com/products/Data_Sheets/ATR0630_35_SglChip_Data_Sheet(GPS.G4-X-06009).pdf u-blox ATR0635]<br><br />
<br />
== Accelerometers ==<br />
Two [[ST LIS302DL]]<br />
* Homepage: http://www.st.com/stonline/products/literature/ds/12726/lis302dl.htm<br />
* Datasheet: http://www.st.com/stonline/products/literature/ds/12726.pdf<br />
* Connected to: S3C2442 via SPI interface<br />
* S3C2442 SPI EINT interrupt inputs<br><br />
<br />
== Graphics/3D Acceleration ==<br />
<br />
Smedia Glamo 3362.<br />
* Homepage: http://www.smediatech.com/product3362.htm<br />
* Driver: http://git.openmoko.org/?p=kernel.git;a=commit;h=911c6fab17f81ea2fdc6ad5e6173ce72bfe01ec4<br />
* Data sheet: This is not available, as it is under NDA. It will likely never be available. (Source: Raster - IRC). It is possible that the glamo chip features may be usable even without a NDA, see [http://unadventure.wordpress.com/2008/06/08/accelerating-in-my-pocket/ the hack here]<br />
* Connected to: S3C2442 Address/Data bus <br><br />
<br />
=== microSD ===<br />
The GTA02 has one microSD aka Transflash slot. Using the Glamo 3362 MMC/SD controller<br />
<br />
* It should support SDHC, and 4GB card has been tested. Anyone with 8GB card? MicroSD slot is [[Disassembling_Neo1973#Opening_back_cover|under battery]].<br />
* 8 Gb Transcend microSDHC class 4 card confirmed working on GTA02 (using [https://docs.openmoko.org/trac/ticket/1743 #1743]).<br />
* Connected to: Glamo 3362 MMC/SD controller<br />
* Driver: Check svn for the SMedia driver with SD implementation<br />
* [[Supported microSD cards]]<br />
* Specifications: [http://www.sdcard.org/about/memory_card/pls/ SD Simplified Specification], [http://www.mmca.org/compliance/buy_spec/AN_MMCA050419.pdf MMC (partial)], [http://www.sandisk.com/Assets/File/OEM/Manuals/manual-rs-mmcv1.0.pdf MMC (product manual)]<br />
* SANDISK 128 MB/512 MB and some 4G SDHC card been verified could work on GTA02<br><br />
<br />
== LCD Module (LCM) ==<br />
Toppoly (tpo) 2.8" diagonal (1.7" x 2.27" - 43mm x 58mm) 480x640 TD028TTEC1 module, using a Toshiba JBT6K74 TFT<br />
LCD Driver Chipset.<br><br />
* Homepage: [http://www.tpo.biz/ENG/business-eng/Activer-Matrix-VGA.htm Activer-Matrix-VGA.htm]<br />
* Specification: FIXME<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-jbt6k74.patch<br />
* Backlight Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-backlight.patch<br />
* Connected to: Glamo3362 LCM interface and Glamo3362 SPI Interface<br><br />
<br />
==== Touch Screen ====<br />
* Connected to: S3C2442 touchscreen controller<br />
* Driver: http://git.openmoko.org/?p=kernel.git;a=blob_plain;f=drivers/input/touchscreen/s3c2410_ts.c;hb=andy-tracking<br />
<br />
== Bluetooth Module==<br />
Delta DFBM-CS320 Class2 Module, using CSR BlueCore4<br />
<br />
* Data Sheet: [http://www.datasheet4u.com/download.php?id=571424 2.DFBM-CS320.pdf]<br />
* CSR Data Sheet: [http://www.csrsupport.com/download/2302/CS-101564-DSP10%20BlueCore4-ROM%20Product%20Data%20Sheet.pdf CS-101564-DSP10 BlueCore4-ROM Product Data Sheet.pdf]<br />
* Driver: Stock Linux Kernel BlueZ<br />
* Connected to: S3C2442 USB Host controller (OHCI)<br />
* PM Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-power_control.patch<br><br />
<br />
=== Bluetooth Audio ===<br />
This one is wired via PCM bus from the CSR Bluetooth chip to the Wolfson codec.<br><br />
<br />
== WiFi Module==<br />
<br />
Accton (WLAN 802.11b/g SiP-M WM3236AQ(Flash Ver:2.0 Atheros AR6001GZ)<br />
* Connected to: S3C2442 SDIO Host controller<br><br />
* Datasheet: [http://www.accton.com/products/Datasheet/WM3236A.AQ.pdf Accton 3236AQ datasheet]<br><br />
* Driver: http://svn.openmoko.org/developers/sameo/patches/<br><br />
<br />
== Vibrator ==<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/gta01-vibrator.patch<br />
* Connected to: S3C2442 GPIO<br />
<br />
== USB Host ==<br />
The USB Host controller is inside the S3C2442<br />
* Driver: Stock Linux kernel ohci_hcd<br />
* USB version 1.1<br />
* Supply USB 5v in Host mode using usb power switch AAT1275IRN-5.0-T1<br />
** http://www.analogictech.com/products/digitalfiles/AAT1275.pdf<br />
* A net EN_USBHOST is controlled by PMU GPIO "GPO", this one signal when asserted (high)<br />
** enables generation of 5V for external device using a charge pump<br />
** enables connection of 15K pulldowns to D+ and D- to allow device insertion and removal detection for host mode<br />
** DISABLES the path for USB power to charge the battery<br />
<br />
It should also be possible to use host mode with externally-provided<br />
power. This will allow the FreeRunner to be connected to a USB device<br />
and be powered and charging the battery if present at the same<br />
time. This method is called the Y-cable and was invented by [[User:JOERG|Joerg Reisenweber]]. For<br />
additional info and circuit diagrams see<br />
[[Specialized_USB_cables#How_to_make_a_USB_cable_for_powering_attached_USB_devices_and_charging_the_Neo_while_in_host_mode_.28aka_Y-Cable.29|Specialized<br />
USB Cables]].<br />
<br />
* Connect 0V, d+, d-, +5 to your USB device<br />
* Connect a 15k ohm resistor between d+ and ground<br />
* Connect a 15k ohm resistor between d- and ground<br />
* Connect 0V, +5 to your >1A power source<br />
** If your power source was not the Openmoko 1A charger, additionally connect a 47K ohm 5% resistor between the ID pin and ground to pretend to be the 1A charger.<br />
<br />
In addition you need to make sure EN_USBHOST signal that enables the physical Host mode power generation and disables the USB -> PMU charging path is deasserted. This may be taken care of automatically shortly by detection of the 48K resistor on a USB insertion leading to forcing EN_USBHOST deasserted. The charge pump that generates the 5V in host mode doesn't seem to mind getting external 5V given to it, but the real issue is that the battery will not be charged at all if we leave EN_USBHOST asserted since one of its jobs is to stop that happening.<br />
<br />
== USB Device ==<br />
The USB Device controller is inside the S3C2442<br />
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2410_udc.patch<br />
* Please see [[USB Product IDs]] on information about which Vendor/Product IDs we use<br />
* 1200mAh lithium battery charges when connected to powered host.<br />
* Mini-AB connector similar to [http://www.cypressindustries.com/shoponline/proddetail.asp?prod=CCMUSBAB-32005-700&cat=34 this one].<br />
<br />
== I2C Devices ==<br />
I2C is a simple communication standard intended to move small amounts of data a few inches between chips.<br />
Please see [[I2C | Neo I2C Devices]] for more information & a list of devices & the addresses currently in use & documented for the Neo1973.<br><br />
<br />
== Audio ==<br />
See also: [[Neo1973 Audio Subsystem]]<br />
<br />
=== Wolfson Codec ===<br />
There's a [[WM8753]] Wolfson Microelectronics CODEC (This is not a 'smart' codec that can interpret MP3/... it is a simple dumb 'sound card'.)<br />
* Product Homepage: http://www.wolfsonmicro.com/products/WM8753/<br />
* Data Sheet: [http://www.wolfsonmicro.com/uploads/documents/en/WM8753.pdf WM8753.pdf]<br />
* Connected to: S3C2442 IIS interface (PCM data), S3C2442 I2C (Control)<br />
<br />
[[Category:Hardware]]<br />
<br />
=== Mono Amplifier ===<br />
There's a National Semiconductor [[LM4853]] Mono Amplifier at the analog audio output of the WM8753<br />
<br />
* Product Homepage: [http://www.national.com/pf/LM/LM4853.html LM4853.html]<br />
* Data Sheet: [http://www.national.com/ds.cgi/LM/LM4853.pdf LM4853.pdf]<br />
* Connects to (LM4853 pin):<br />
** S3C2442 GPIO: HP_IN, AMP_SHUT (shutdown);<br />
** Wolfson WM8753: LOUTL (LEFTIN), LOUTR (RIGHTIN);<br />
** speaker4102: (LEFTOUT/BLTOUT-, BLTOUT+);<br />
** headset-jack: ring 2 (RIGHTOUT), ring 3 (LEFTOUT/BLTOUT-) via 1uF-33R each<br />
<br />
=== Analog wired Headset ===<br />
There's a four-ring 2.5mm stereo jack which provides connectivity to old-fashioned wired headsets.<br />
<br />
The headsets used by Motorola smartphones (A780,A1200, ...) and the V-360 have a compatible configuration, as does the headset for an LG muziq 570.<br />
<br />
ring<br><br />
1(base): GND<br><br />
2: right out<br><br />
3: left out<br><br />
4(tip): mic + HOLD-button(press:short to GND)<br />
<br />
=== Buttons ===<br />
The Neo1973 GTA02 features two buttons:<br />
* [[Neo1973 Power Button|The Power Button]]<br />
* [[Neo1973 AUX Button|The "Aux" button]]<br />
<br />
== Case ==<br />
The case for the FreeRunner is all black, as seen on the front page of the wiki.<br />
<br />
Openmoko has released the CAD files for the case of the Neo1973 and Neo FreeRunner. These were created using Pro/ENGINEER (also called Pro/E). They are available in the Pro/E (.asm/.prt) format, but alternative formats are also available.<br />
<br />
<br />
We welcome your assistance in providing other formats. If you are able to convert CAD files from Pro/E format to other formats, please contact [mailto:michael@openmoko.org]. We are especially interested in the DXF format and in images rendered from these files.<br />
<br />
* [http://downloads.openmoko.org/CAD/NeoFreeRunner_ProE.zip The original Pro/E (.asm/.prt) format]<br />
<br />
[http://downloads.openmoko.org/developer/CAD/ Browse CAD directory]<br />
<br />
=Accessory=<br />
<br />
== Stylus ==<br />
<br />
Using 4-in-1 laser pen<br />
*Vendor: [http://www.quarton.com/laser_pen.html Quarton XPII]<br />
*GTA02 standard setup comes with [http://www.quarton.com.tw/laser_pen_infiniter_xp_2.html QUARTON XPII 4-in-1 laser pen]<br />
<br />
== Battery ==<br />
The [[Neo FreeRunner (GTA02) Battery]] is mechanically and electrically compatible with the [[Neo1973 GTA01 Battery]], as well as limited compatibility with a Nokia BL6C battery.<br />
According to [http://lists.openmoko.org/pipermail/community/2007-February/003758.html this] post on the mailinglist.<br />
[http://wiki.openmoko.org/index.php?title=Image:Neo1973-with-BL5C-battery.png Photo] of the battery inside the Neo1973.<br />
<br />
* GTA02 using the smart battery based on TI bq27000 chipset<br />
* SANYO UF653450S 1200mAh cell.<br><br />
* Battery schematics: [http://people.openmoko.org/tony_tu/GTA02/hardware/GTA02/CT-GTA02.pdf GTA02 Smart Battery Schematics]<br />
<br />
== microSD Card ==<br />
<br />
GTA02 should come with one of following microSD card<br />
<br />
* [http://www.transcendusa.com/ Transcend] 512MB microSD card<br />
* [http://www.sandisk.com/ SanDisk] 512MB microSD card<br><br />
<br />
== Charger ==<br />
<br />
AKII Technology Charger<br />
<br />
*Model: [http://www.ak2.com.tw/pd_main.asp?sg_id=11 A10P1-05MP]<br />
*Input: 100-240v~ /0.3A<br />
*Output: +5v up to 2.0A<br />
*Add 47.5k 1% resistor between ID pin and ground for openmoko charger identification<br><br />
<br />
= History =<br />
<br />
== GTA02v1 ==<br />
First generation of prototypes that was given to internal Openmoko software developers. Total 30 pcs fabricated.<br />
<br />
*It is working just fine, but still based on 2440, with external NAND/SDRAM and no NOR flash<br />
*Using the PCF50633 05 N3 due to 04 N3 not available, rework power for basic schematics verification<br />
*Using GTA01 SIM socket<br />
*Add external debug port<br />
*Still using Global locate A-GPS<br />
* ATAG_REVISION: 0310<br />
<br />
== GTA02v2 ==<br />
Second generation of prototypes, Total 50 pcs run at Taipei SMT factory MOUNT<br />
<br />
*Ideal is have 256 MB NAND on Samsung package, Due to chip availability Start using S3C2442 B43<br />
*Using correct PMU PCF50633 04 N3<br />
*Change new SIM socket<br />
*Change to u-blox A-GPS<br />
*Change LCM power from 3.3v to 1.8v<br />
*USB power switch layout/pin assignment mistake, could not verify USB host supply 5v function<br />
*GPS function verified ok with good sensitivity<br />
* ATAG_REVISION: 0320<br />
<br />
== GTA02v3 ==<br />
Production verification version, 2007/10/11 28 pcs fabricate at FIC SuZhou<br />
<br />
*Still using S3C2442 B43 for hardware verification<br />
*Using control pilot run to verify S3C2442 B54 chips<br><br />
* ATAG_REVISION: 0330<br />
<br />
== GTA02v4 ==<br />
Mass production release candidate version 1<br />
<br />
2 weeks after v3 gerber out, release the v4 gerber, and 2007/10/20 20 pcs fabricate at FIC SuZhou<br />
<br />
*Change LCM power from 1.8v to 3.3v for display stability issue<br />
*fabricate another 200 pcs for yield rate/production verification<br />
*fabricate 50 pcs with S3C2442 B43 (128 MB NAND) for quality comparsion<br />
*USB host power chip have some output voltage stability issues with Vb/Vcc comes from different power source, need layout change to fix the issue<br />
*Battery Coulomb design not working on A4<br />
* ATAG_REVISION: 0340<br />
<br />
== GTA02v5 ==<br />
Mass production candidate version 2/Mass production version<br />
<br />
* First batch fabricate 2008/1/14 at FIC SuZhou<br />
* Mass production A5 trial run start from 2008 March, including some resistor/capacitor change compare with inital 100 pcs prototypes A5, and prototypes for GTA02 developers was tracked in the [[Prototypes| Prototypes Page]]<br />
* Coulomb counter issue fixed<br />
* USB host power switch fixed<br />
* Need add capacitor for PMU Vbat input for stability issue, this could be done by direct SMT or hand rework<br />
* Need rework (still using SMT in production) add capacitor for PMU Vbat input for PMU stability issue.<br />
* Need manual rework GSM IR UART path a 100k pull down for better GSM deep sleep<br />
* ATAG_REVISION: 0350<br />
<br />
===GTA02 mass Production version change list===<br />
*PMU's LED power error: PMU potential damage issue<br />
*NOR FLASH enable WP: User can write data into NOR FLASH.<br />
*CE CS/RS fine tune: Audio's background noise too high<br />
*I2C pull high resistor: The resistor is too high and signal is distorted<br />
*GSM leakage current: TX_MODEM has a pull high resistor on IO_3V3<br />
*Power consumption: Disable keep active function<br />
*SDIO clock and esd protect resistor<br />
*Refer to Datasheet: R1526 to 33K<br />
*GSM modem on pin: The R1018 is too small and has some leakage current<br />
*LED driving transistor: When GPIO is on, the transistor will be draw more current on LED. This is component change fix, do not need change PCB or re-work.<br />
<br />
== GTA02v6 ==<br />
Mass production candidate version 3/Mass production version<br><br />
<br />
A6 will be fine tune version of A5, only minor [http://downloads.openmoko.org/schematics/GTA02/ schematic] change for better product quality and version control. Capacitor and resistor change A6 also on mass production A5<br><br />
<br />
*First 100 pcs start from 2008 mid April, and factory make component placement mistake on GSM, second 100 pcs PCB arrive time TBD.<br />
*Add capacitor space for Vbat, reduce the SMT effort<br />
*Add GSM IR resistor for better GSM deep sleep<br />
*Reserve 3 GPIO for hardware version control<br />
*Fixed LEDs power usage (from about 150mW of v5 to about 25mW)<br />
* ATAG_REVISION: 0360<br />
<br />
=== GTA02 A5 to A6 changes ===<br />
*Power Glitch on VB_SYS: Add capacitor on layout, Mass production A5 also apply this change.<br />
*G-sensor separate these interrupt pins: At A5, each accelerometer INT1/INT2 connected to same line, at A6 only INT1 was connected.<br />
*GSM_modem power source Reduce power's ripple when the phone is talking<br />
*Keep active Disable keep active function, just fine tune<br />
*GPIO for version control<br />
*GSM RX_IR has some noise Add resistor and reduce GSM RX_IR noise and gsm can't enter suspend mode easily, apply on mass production A5.<br />
*LED driving transistor apply on mass production A5.<br />
*LCM's VDDIO We can totally power off LCM's power, save about extra 1mA.<br />
<br />
= Debug Board =<br />
<br />
== Debug Board Connector definition ==<br />
<br />
This is the connector used to connect the [[Debug Board]] and possibly other hardware.<br />
<br />
Connections are:<br />
* 39 - GND<br />
* 38 - STDI<br />
* 37 - _RESET<br />
* 36 - STMS<br />
* 35 - STCK<br />
* 34 - STDO<br />
* 33 - GSM_EN<br />
* 29 - _STRST<br />
* 19 - X_I2C_SCL (H-TP4703)<br />
* 18 - X_I2C_SDA (H-TP4704)<br />
* 17 - SPI_CLK0<br />
* 16 - SPI_MOSI0<br />
* 15 - SPI-MISO0<br />
* 14 - SS0<br />
* 13 - EINT3 (H-TP4705)<br />
* 3 - CONSOLE_TXD (H-TP4701)<br />
* 2 - CONSOLE_RXD (H-TP4702)<br />
<br />
Information from [http://people.openmoko.org/roh/Debugport_GTA01bv4.png].<br />
<br />
= Distinguishing hardware revisions =<br />
== Inside the [[Bootloader]] ==<br />
Every hardware revision has its own u-boot image type. Thus, the bootloader has the revision hard-coded.<br />
The hardware revision is passed on to the kernel via the ATAG mechanism (ATAG_REVISION)<br />
<br />
== Inside the [[Kernel]] ==<br />
The kernel receives the ATAG_REVISION during bootup, and saves its contents in the "system_rev" global variable.<br />
<br />
== From Userspace ==<br />
The kernel exports the system_rev variable in /proc/cpuinfo as "Revision :" line.<br />
<br />
= Certification =<br />
<br />
== FCC ==<br />
*For US Import<br />
** 850/1800/1900 Band, FCC ID: EUNGTA02<br />
** 900/1800/1900 Band, FCC ID: EUNGTA02E<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02_850_1800_1900/ FCC test report(GTA02)]<br />
** [http://people.openmoko.org/tony_tu/GTA02/certificate/EUNGTA02E_900_1800_1900/ FCC test report(GTA02E)]<br />
<br />
== CE ==<br />
*For Europe<br />
**Registration number: M528583V-EO<br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/CE/ CE report and certificate]<br />
<br />
== NCC ==<br />
*For Taiwan Import<br />
**NCC certification number: CCAF08DG0080T0<br />
**[http://people.openmoko.org/tony_tu/GTA02/certificate/NCC NCC report and certificate]<br />
<br />
[[Category:Neo FreeRunner Hardware| ]]</div>Sybrenhttp://wiki.openmoko.org/wiki/Talk:Automatic_emulation_in_UbuntuTalk:Automatic emulation in Ubuntu2009-06-27T11:56:38Z<p>Sybren: </p>
<hr />
<div>cogito (not realy needed) is gone by hardy<br />
<br />
== Missing 'qemu' target ==<br />
<br />
The Makefile downloaded from http://www.rwhitby.net/files/openmoko/Makefile doesn't contain the "qemu" target, nor does it do anything when just calling "make".<br />
<br />
[[User:Sybren|sybren]] 11:25, 27 June 2009 (UTC)<br />
<br />
== Build failure ==<br />
<br />
On Kubuntu 9.04 "make qemu" fails with:<br />
<br />
make[2]: Leaving directory `/home/sybren/speeltuin/freerunner/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/home/sybren/speeltuin/freerunner/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Trying alternative sources<br />
Kernel is... not found<br />
make: *** [download-images] Error 255<br />
<br />
[[User:Sybren|sybren]] 11:56, 27 June 2009 (UTC)</div>Sybrenhttp://wiki.openmoko.org/wiki/Talk:Automatic_emulation_in_UbuntuTalk:Automatic emulation in Ubuntu2009-06-27T11:43:26Z<p>Sybren: /* Build failure */ new section</p>
<hr />
<div>cogito (not realy needed) is gone by hardy<br />
<br />
== Missing 'qemu' target ==<br />
<br />
The Makefile downloaded from http://www.rwhitby.net/files/openmoko/Makefile doesn't contain the "qemu" target, nor does it do anything when just calling "make".<br />
<br />
[[User:Sybren|sybren]] 11:25, 27 June 2009 (UTC)<br />
<br />
== Build failure ==<br />
<br />
On Kubuntu 9.04 "make qemu" fails with:<br />
<br />
make[2]: Leaving directory `/home/sybren/speeltuin/freerunner/openmoko/build/qemu/arm-softmmu'<br />
make[1]: Leaving directory `/home/sybren/speeltuin/freerunner/openmoko/build/qemu'<br />
[ -e images/openmoko ] || mkdir -p images/openmoko<br />
ln -sf `pwd`/openmoko/trunk/src/host/qemu-neo1973/openmoko/env images/openmoko/env<br />
( cd images && ../openmoko/trunk/src/host/qemu-neo1973/openmoko/download.sh )<br />
Retrieving available builds list...<br />
Trying alternative sources<br />
Kernel is... not found<br />
make: *** [download-images] Error 255</div>Sybrenhttp://wiki.openmoko.org/wiki/Talk:Automatic_emulation_in_UbuntuTalk:Automatic emulation in Ubuntu2009-06-27T11:25:28Z<p>Sybren: /* Missing 'qemu' target */</p>
<hr />
<div>cogito (not realy needed) is gone by hardy<br />
<br />
== Missing 'qemu' target ==<br />
<br />
The Makefile downloaded from http://www.rwhitby.net/files/openmoko/Makefile doesn't contain the "qemu" target, nor does it do anything when just calling "make".<br />
<br />
[[User:Sybren|sybren]] 11:25, 27 June 2009 (UTC)</div>Sybrenhttp://wiki.openmoko.org/wiki/Talk:Automatic_emulation_in_UbuntuTalk:Automatic emulation in Ubuntu2009-06-27T11:23:52Z<p>Sybren: /* Missing 'qemu' target */ new section</p>
<hr />
<div>cogito (not realy needed) is gone by hardy<br />
<br />
== Missing 'qemu' target ==<br />
<br />
The Makefile downloaded from http://www.rwhitby.net/files/openmoko/Makefile doesn't contain the "qemu" target, nor does it do anything when just calling "make".</div>Sybrenhttp://wiki.openmoko.org/wiki/Talk:LinphoneTalk:Linphone2009-06-27T10:55:46Z<p>Sybren: /* Broken download link */</p>
<hr />
<div>I am new to OpenMoko and am trying to install LinPhone as per these instructions. I consistently receive, even after opkg update and opkg upgrade, the following errors:<br />
<br />
parseVersion: ERROR: epoch in version is not number<br />
<br />
As well as lots of errors like:<br />
<br />
Package xyz version 1.2.3 has no architecture specified, defaulting to om-gta02.<br />
<br />
Is the repository for LinPhone not up to date, not compatible with 2008.9, not compatible with Neo Freerunner?<br />
<br />
I think you have to add a line like ''arch general 50'' in the file ''/etc/opkg/arch.conf'' after add new repository with file ''general-feed.conf''<br />
but i have some problem too with upgrade of some packages<br />
<br />
== broken layout ==<br />
<br />
somehow after my last edit the layout got messed up. sorry for that. i am not reverting to last version as this one is messed up as well at the moment. maybe the wiki itself has some problems. anyway, feel free to revert the changes if it restores the layout...<br />
<br />
== Manual download of package ==<br />
<br />
I find this workarround. I dind't add the repository to opkg, but i download manually all package.<br />
<br />
In this way installation goes find.<br />
bye<br />
Emmanuele<br />
<br />
== Broken download link ==<br />
<br />
The URL http://rabenfrost.net/celtune/ipk doesn't exist any more. http://rabenfrost.net/celtune/ appears to contain no Linphone packages.<br />
<br />
[[User:Sybren|sybren]] 10:55, 27 June 2009 (UTC)</div>Sybrenhttp://wiki.openmoko.org/wiki/Talk:LinphoneTalk:Linphone2009-06-27T10:55:27Z<p>Sybren: /* Broken download link */ new section</p>
<hr />
<div>I am new to OpenMoko and am trying to install LinPhone as per these instructions. I consistently receive, even after opkg update and opkg upgrade, the following errors:<br />
<br />
parseVersion: ERROR: epoch in version is not number<br />
<br />
As well as lots of errors like:<br />
<br />
Package xyz version 1.2.3 has no architecture specified, defaulting to om-gta02.<br />
<br />
Is the repository for LinPhone not up to date, not compatible with 2008.9, not compatible with Neo Freerunner?<br />
<br />
I think you have to add a line like ''arch general 50'' in the file ''/etc/opkg/arch.conf'' after add new repository with file ''general-feed.conf''<br />
but i have some problem too with upgrade of some packages<br />
<br />
== broken layout ==<br />
<br />
somehow after my last edit the layout got messed up. sorry for that. i am not reverting to last version as this one is messed up as well at the moment. maybe the wiki itself has some problems. anyway, feel free to revert the changes if it restores the layout...<br />
<br />
== Manual download of package ==<br />
<br />
I find this workarround. I dind't add the repository to opkg, but i download manually all package.<br />
<br />
In this way installation goes find.<br />
bye<br />
Emmanuele<br />
<br />
== Broken download link ==<br />
<br />
The URL http://rabenfrost.net/celtune/ipk doesn't exist any more. http://rabenfrost.net/celtune/ appears to contain no Linphone packages.</div>Sybrenhttp://wiki.openmoko.org/wiki/User:SybrenUser:Sybren2009-06-27T10:52:38Z<p>Sybren: </p>
<hr />
<div>Home: http://stuvel.eu/<br />
<br />
Photos: http://www.flickr.com/photos/sybrenstuvel/<br />
<br />
OpenStreetMap account: http://www.openstreetmap.org/user/Sybren and http://wiki.openstreetmap.org/wiki/User:Sybren<br />
<br />
Owned hardware: Neo Freerunner using SHR unstable</div>Sybrenhttp://wiki.openmoko.org/wiki/User:SybrenUser:Sybren2009-06-27T10:52:07Z<p>Sybren: New page: Home: http://stuvel.eu/ Photos: http://www.flickr.com/photos/sybrenstuvel/ OpenStreetMap account: http://www.openstreetmap.org/user/Sybren and http://wiki.openstreetmap.org/wiki/User:Syb...</p>
<hr />
<div>Home: http://stuvel.eu/<br />
<br />
Photos: http://www.flickr.com/photos/sybrenstuvel/<br />
<br />
OpenStreetMap account: http://www.openstreetmap.org/user/Sybren and http://wiki.openstreetmap.org/wiki/User:Sybren</div>Sybren