Openmoko - User contributions [en]

SHR

2009-08-12T18:04:31Z

Kero:

{{Languages|SHR}}
{{Distributions|SHR}}

'''SHR''' (Stable Hybrid Release) is a community driven distribution based on the [[FSO]] framework. SHR can use several different graphical toolkits, for example GTK or EFL. At first, SHR was introduced in order to use the [[Om 2007.2]] GTK software in combination with the new FSO, but things have changed.
[[Image:Shr-tnc01.jpg|right|thumb|300px|Full Image with [[Edje|custom Background]] ]]

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

{| cellspacing="0" class="sortable wikitable" border="1" style="font-size: 85%; text-align: left; width: auto;"
|-
! Category
! Name
! Functionality
! Comments
|-
| System
| Power Management
| style="background:#88FF88;"| Suspend
| when slow, use [[Qi]]
|-
| System
| Package manager
| style="background:#88FF88;"| Installing and upgrading packages
| Works well. For packages not in the repository, just ask for them to be added via the trac
|-
| System
| Keyboard
| style="background:#FFDD88;"| Offer stylus and finger friendly keyboards
| style="background:#FFDD88;"| install alternative keyboards [http://trac.shr-project.org/trac/ticket/200 SHR ticket #200]
|-
| GSM
| Network
| style="background:#88FF88;"| Connect via SIM and PIN
|
|-
| GSM
| Network
| style="background:#FF8888;"| Flight mode
| style="background:#FF8888;"| [http://trac.shr-project.org/trac/ticket/333 SHR ticket #333]
|-
| GSM
| Dailer
| style="background:#88FF88;"| Receiving Call
| no way to adjust (double) audio in and audio out
|-
| GSM
| Dailer
| style="background:#88FF88;"| Making Call
| no way to adjust (double) audio in and audio out
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Overview Log (In, Out, Answered, All)
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Display Missed Calls
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Making reply Call from Log
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Sending reply SMS from Log
|
|-
| Shared
| Phone Log
| style="background:#88FF88;"| Creating new SIM contact from Log
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Receiving SMS
| style="background:#FFDD88;"| multipart SMS not concatenated [http://trac.shr-project.org/trac/ticket/121 SHR ticket #121]
|-
| GSM
| SMS
| style="background:#88FF88;"| SIM phonebook lookup for SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| View overview of received SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Selecting SMS from Overview
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Viewing SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Writing SMS
|
|-
| GSM
| SMS
| style="background:#FFDD88;"| Sending new SMS
| style="background:#FF8888;"| multipart SMS not being sent [http://trac.shr-project.org/trac/ticket/121 SHR ticket #121]
|-
| GSM
| SMS
| style="background:#FFDD88;"| Sending reply SMS
| style="background:#FF8888;"| multipart SMS not being sent [http://trac.shr-project.org/trac/ticket/121 SHR ticket #121]
|-
| GSM
| SMS
| style="background:#88FF88;"| Making reply Call
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Deleting SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Storing received contact in contacts
|
|-
| GSM
| GPRS
| style="background:#88FF88;"| Configuring and Enabling GPRS
| Settings->Connectivity: GPRS connect
|-
| Shared
| Contacts
| style="background:#88FF88;"| Reading SIM contacts
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Selecting SIM contact from Overview
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Creating new SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Editing SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Deleting SIM contact
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Quick lookup contact with keyboard
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Calling contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Sending SMS to contact
|
|-
| Shared
| Contacts
| style="background:#FF8888;"| Sending contact via SMS to contact
|
|-
| WiFi
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling TCP/IP
| 1) Settings->Connectivity->WiFi radio=On 2) Mokonnect
|-
| GPS
| Service
| style="background:#88FF88;"| Receiving GPS data
| automatically turning on
|-
| USB
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling TCP/IP
| done automatically with insecure password
|-
| Audio
| Headset
| style="background:#FF8888;"| Handsfree calling
| headphones work, microphone does not work (needs checking!)
|-
|}

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

== More Information ==

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

[[Category:SHR| ]]

Supported microSD cards

2009-08-10T18:52:25Z

Kero:

{{todo|Maybe reformat table, see discussion page}}

There are a plethora of Transflash / microSD / microSDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 16GB microSDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a post-september 4th kernel which applies our kernel patchset rev2832 or higher.

Booting from microSDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with microSDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you want to exchange your SD card more often: [http://people.openmoko.org/joerg/sdcard-handle/ Jörg] has a nice sticky tape trick to do this with no hassle.

If you use a card not listed here, please add to this table.

== SD card issue ==

A small amount of users may see the following error when trying to use the SD card via the bootloader:

Error after cmd: 0xfffffffc No MMC card found

(You can provoke this by logging into the bootloader via USB serial connection and running the 'mmcinit' command.)

It is possible that the connector contacts do not reach the card properly. In my case I was able to bend the contacts a little bit more upwards (using the tip of a nail file) and then the card worked without problems.

== Cards by Vendor ==
{| class="wikitable" border=1
|-
! Vendor !! Model !! Capacity !! Speed !! [[u-boot]] 1.1.6 !! linux 2.6.17.14-fic5 !! [[u-boot]] 1.2.0-moko8 svn1915 !! [[u-boot]] 1.3.2-moko12 !! linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) !! OM2008.9's kernel !! Status
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || {{no}} || {{yes}} || {{no}} || 1.3.1 did not || {{yes}} || ||
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 6 || {{no}} || {{no}} || {{no}} || 1.3.1 did not || {{no}} || ||
|-
| Apacer || microSDHC-4GB || 4GB (SDHC) || class 6? || || {{no}} || || || {{no}} || {{no}} || I/O errors
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}} || ||
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || || || ||
|-
| Kingston || [[Supported_microSD_cards/SD-C02G|SD-C02G]] || 2GB || ? || ? || {{yes}} || || {{yes}} || {{no}} || {{no}} (see [[Supported_microSD_cards/SD-C02G|SD-C02G]] ) ||
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || || || {{no}} ||
|-
| Kingston || SDC4/8GB || 8GB SDHC || Class 4 || {{yes}} || || || || {{yes}} || {{yes}} ||
|-
| Kingston || SDC16GB || 16GB SDHC || Class 2 || || || || || || {{yes}} ||
|-
| Memory Master || || 4Gb || || || || || || || {{no}} IO errors prevent Debian installation. Looks like [http://docs.openmoko.org/trac/ticket/2025 #2025] to me || IO errors
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB (SDHC)|| Class 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}} ||
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || || || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-002G-E11M || 2GB || || || || || || || || I'll soon give it a try. --[[User:Sol|Sol]] 20:33, 31 March 2009 (UTC)
|-
| SanDisk || SDSDQ-2048-E11MK || 2GB || || || || || detects size incorrectly with U-Boot 1.3.2-moko12 (Aug 26 2008 - 08:24:58) : see http://docs.openmoko.org/trac/ticket/1815#comment:6 || || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || {{yes}} || {{yes}} || || There is no way to boot this uSD via QI
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || || || ||
|-
| SanDisk || SDSDQ-8192-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || boot needs "sleep 1" between mmcinit and ext2load || || ||
|-
| SanDisk || [http://www.sandisk.com/Products/Item(2630)-SDSDQY-8192-A11M-SanDisk_Mobile_Ultra_microSDHC_8GBCard.aspx SDSDQY-8192-E11M/A11M] || 8GB (SDHC) || 6 || ? || {{yes}} || ? || || || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || || || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 2 || || || || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || || || ||

|-
| SanDisk || SDSDQ7-8192-E11M || 8GB (SDHC) || 4 || ? || ? || ? || {{yes}} || {{yes}} || ? ||
|-
| SanDisk || [http://uk.sandisk.com/Products/ProductInfo.aspx?ID=2702 SDSDQ-016G-E11M] || 16GB (SDHC) || Class 2 || untested || untested || untested || {{yes}}, [[SanDisk/SDSDQ-016G-E11M|see details]] || {{yes}} kernel 2.6.24mw, [[SanDisk/SDSDQ-016G-E11M|see details]] || untested, but should work.|| [[SanDisk/SDSDQ-016G-E11M|WiP]]
|-
| Silicon Power || SP004GBSTH006V10 || 4GB (SDHC) || 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}} ||
|-
| Silicon Power || SP004GBSTH006V30 || 4GB (SDHC) || 6 || ? || ? || ? || {{yes}} || {{yes}} || ? ||
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || || || ||
|-
| Toshiba || ? || 8GB || 4 || {{yes}} || {{yes}} || ?|| ?|| should work||{{yes}} ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| [http://www.transcendusa.com/ Transcend] || [http://www.transcendusa.com/Support/DLCenter/Datasheet/TSxxUSD.pdf TS512MUSD] '''(shipped with FreeRunner)''' || 512MB || || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || || || ||
|-
| Transcend || TS1GUSDC || 1GB (SDC) || || ? || I/O errors while trying to install Om2008.8 rootfs.tar.gz, looks like [https://docs.openmoko.org/trac/ticket/1743 #1743] || ? || ? || ? || ||
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || || || {{no}}, see [http://docs.openmoko.org/trac/ticket/2025 bug #2025] ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008) || ||
|-
| Transcend || TS8GUSDHC6 || 8GB (SDHC) || Class 6 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008) || ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || {{yes}} since kernel of 30-Sep-2008 || ||
|-
| Transcend || TS16GUSDHC6 || 16GB (SDHC) || Class 6 || ? || ? || ? || {{yes}} || linux 2.6.28+29 (OM2009) || ||
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| Verbatim || 47206 || 4GB (SDHC) || Class 6|| || {{yes}} (surely) || {{yes}} (surely) || {{yes}} || {{yes}} || {{yes}} (surely) ||
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || {{yes}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ||
|-
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) || OM2008.9's kernel ||
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)

[[Category:MicroSD]]

Supported microSD cards

2009-08-10T18:51:17Z

Kero:

{{todo|Maybe reformat table, see discussion page}}

There are a plethora of Transflash / microSD / microSDHC (Secure Digital High Capacity) cards out there.

The Neo FreeRunner supports up to 16GB microSDHC cards.

Some microSD cards appear to be too slow to work with the current default settings of the glamo driver, so some specific parameters must be set in uboot to use them (see https://docs.openmoko.org/trac/ticket/1743, and corresponding notes in the tables bellow).

There had been a [http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 bug] in the SD device driver (s3cmci) which caused some trouble. Please make sure you use a post-september 4th kernel which applies our kernel patchset rev2832 or higher.

Booting from microSDHC requires a u-boot from 2008-07-23 or later. '''But pay attention''' : there are problems with microSDHC cards at suspend time. More details from [[Booting from SD#Booting_from_SDHC_.2F_suspend_problems|Booting from SD]]

Note that most vendors are using an irritating way of labeling the capacity of their cards (They are using the factor 1000 instead of 1024 for KB and MB). Therefore the real capacity of these cards will be about 5% less than the vendor's specification. For example, cards labelled ''6 GB'' will only have 5.7 GB of storage capacity.

If you want to exchange your SD card more often: [http://people.openmoko.org/joerg/sdcard-handle/ Jörg] has a nice sticky tape trick to do this with no hassle.

If you use a card not listed here, please add to this table.

== SD card issue ==

A small amount of users may see the following error when trying to use the SD card via the bootloader:

Error after cmd: 0xfffffffc No MMC card found

(You can provoke this by logging into the bootloader via USB serial connection and running the 'mmcinit' command.)

It is possible that the connector contacts do not reach the card properly. In my case I was able to bend the contacts a little bit more upwards (using the tip of a nail file) and then the card worked without problems.

== Cards by Vendor ==
{| class="wikitable" border=1
|-
! Vendor !! Model !! Capacity !! Speed !! [[u-boot]] 1.1.6 !! linux 2.6.17.14-fic5 !! [[u-boot]] 1.2.0-moko8 svn1915 !! [[u-boot]] 1.3.2-moko12 !! linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) !! OM2008.9's kernel !! Status
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 4 || {{no} || {{yes}} || {{no}} || 1.3.1 did not || {{yes}} || ||
|-
| A-Data || microSDHC-8GB || 8GB (SDHC) || class 6 || {{no}} || {{no}} || {{no}} || 1.3.1 did not || {{no}} || ||
|-
| Apacer || microSDHC-4GB || 4GB (SDHC) || class 6? || || {{no}} || || || {{no}} || {{no}} || I/O errors
|-
| Corsair || CMFSDMICRO-512 || 512MB || || {{no}} || {{yes}} || || || || ||
|-
| Dane-Elec || DA-SDMC-2048-R || 2GB || ? || ? || ? || ? || ? || {{yes}} || ||
|-
| extreMemory || AE56-1280R || 128MB || || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| extreMemory || H256MS05 || 256MB || 60x || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| hama || 55371 || 256MB || || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| Intuix || IXMSDM128B60X || 128MB || 60x || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| Kingston || SD-C512 || 512MB || ? || {{no}} || {{yes}} || || || || ||
|-
| Kingston || SD-C01G || 1GB || ? || {{yes}} || ? || || || || ||
|-
| Kingston || [[Supported_microSD_cards/SD-C02G|SD-C02G]] || 2GB || ? || ? || {{yes}} || || {{yes}} || {{no}} || {{no}} (see [[Supported_microSD_cards/SD-C02G|SD-C02G]] ) ||
|-
| Kingston || SDC4 (N0043-012.A00LF) || 4GB || ? || ? || FSO MS2 / Linux 2.6.24: I/O Errors while formatting [http://wiki.openmoko.org/wiki/Special:Emailuser/varacanero Contact me here] || || || || {{no}} ||
|-
| Kingston || SDC4/8GB || 8GB SDHC || Class 4 || {{yes}} || || || || {{yes}} || {{yes}} ||
|-
| Kingston || SDC16GB || 16GB SDHC || Class 2 || || || || || || {{yes}} ||
|-
| Memory Master || || 4Gb || || || || || || || {{no}} IO errors prevent Debian installation. Looks like [http://docs.openmoko.org/trac/ticket/2025 #2025] to me || IO errors
|-
| Patriot || PSF128MCSD-RC || 128MB || ? || {{no}} || ? || || || || ||
|-
| Patriot || PSF8GMCSDHC4 || 8GB (SDHC)|| Class 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}} ||
|-
| PNY || P-MICROSD512-BX || 512MB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| PNY || P-MICROSD2GB-BX (card marked with MM8GR02GUACY) || 2GB || slow ? || ? || ? (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743] but apparently not enough) || ? || || || ||
|-
| Pretec || || 128MB || ? || ? || {{yes}} || || || || ||
|-
| SanDisk || SDSDQ-128 || 128MB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || unknown || 256MB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || unknown || 512MB || || {{yes}} || {{yes}} || || || || ||
|-
| SanDisk || SDSDQ-1024-E10M || 1GB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQU-2048-E10M || 2GB || || {{yes}} || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-002G-E11M || 2GB || || || || || || || || I'll soon give it a try. --[[User:Sol|Sol]] 20:33, 31 March 2009 (UTC)
|-
| SanDisk || SDSDQ-2048-E11MK || 2GB || || || || || detects size incorrectly with U-Boot 1.3.2-moko12 (Aug 26 2008 - 08:24:58) : see http://docs.openmoko.org/trac/ticket/1815#comment:6 || || ||
|-
| SanDisk || SDSDQ-4096-E11M || 4GB (SDHC) || || ? || {{yes}} || ? || {{yes}} || {{yes}} || || There is no way to boot this uSD via QI
|-
| SanDisk || SDSDQ-6144-E11M || 6GB (SDHC) || || ? || {{yes}} || {{no}} || || || ||
|-
| SanDisk || SDSDQ-8192-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || boot needs "sleep 1" between mmcinit and ext2load || || ||
|-
| SanDisk || [http://www.sandisk.com/Products/Item(2630)-SDSDQY-8192-A11M-SanDisk_Mobile_Ultra_microSDHC_8GBCard.aspx SDSDQY-8192-E11M/A11M] || 8GB (SDHC) || 6 || ? || {{yes}} || ? || || || ||
|-
| SanDisk || SDSDQR-8192-E12M || 8GB (SDHC) || 4 || ? || {{yes}} || ? || || || ||
|-
| SanDisk || SDSDQR-8192-???? || 8GB (SDHC) || 6 || ? || {{yes}} || {{yes}} || || || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 2 || || || || {{yes}} || {{yes}} || ||
|-
| SanDisk || SDSDQ-008G-E11M || 8GB (SDHC) || 4 || ? || {{yes}} || || || || ||

|-
| SanDisk || SDSDQ7-8192-E11M || 8GB (SDHC) || 4 || ? || ? || ? || {{yes}} || {{yes}} || ? ||
|-
| SanDisk || [http://uk.sandisk.com/Products/ProductInfo.aspx?ID=2702 SDSDQ-016G-E11M] || 16GB (SDHC) || Class 2 || untested || untested || untested || {{yes}}, [[SanDisk/SDSDQ-016G-E11M|see details]] || {{yes}} kernel 2.6.24mw, [[SanDisk/SDSDQ-016G-E11M|see details]] || untested, but should work.|| [[SanDisk/SDSDQ-016G-E11M|WiP]]
|-
| Silicon Power || SP004GBSTH006V10 || 4GB (SDHC) || 4 || ? || ? || ? || {{yes}} || {{yes}} || {{yes}} ||
|-
| Silicon Power || SP004GBSTH006V30 || 4GB (SDHC) || 6 || ? || ? || ? || {{yes}} || {{yes}} || ? ||
|-
| Toshiba || SD-512R2W || 512MB || || {{no}} || {{yes}} || || || || ||
|-
| Toshiba || ? || 8GB || 4 || {{yes}} || {{yes}} || ?|| ?|| should work||{{yes}} ||
|-
| Transcend || TS128MUSD || 128MB || || {{no}} || {{yes}} || || || || ||
|-
| Transcend || TS256MUSD80 || 256MB || 80x || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| [http://www.transcendusa.com/ Transcend] || [http://www.transcendusa.com/Support/DLCenter/Datasheet/TSxxUSD.pdf TS512MUSD] '''(shipped with FreeRunner)''' || 512MB || || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} ||
|-
| Transcend || MM4GRO1GUACY || 1GB || || ? || {{yes}} || ? || || || ||
|-
| Transcend || TS1GUSDC || 1GB (SDC) || || ? || I/O errors while trying to install Om2008.8 rootfs.tar.gz, looks like [https://docs.openmoko.org/trac/ticket/1743 #1743] || ? || ? || ? || ||
|-
| Transcend || TS4GUSDHC6 (card marked with MM8GR04GUACY) || 4GB (SDHC) || Class 6 || ? || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || || || {{no}}, see [http://docs.openmoko.org/trac/ticket/2025 bug #2025] ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008) || ||
|-
| Transcend || TS8GUSDHC6 || 8GB (SDHC) || Class 6 || ? || ? || ? || {{yes}} || linux 2.6.24+git37+d744c88c14 (2007.2 kernel as of Aug 28, 2008) || ||
|-
| Transcend || TS8GUSDHC4 || 8GB (SDHC) || Class 4 || ? || ? || ? || {{yes}} || {{yes}} since kernel of 30-Sep-2008 || ||
|-
| Transcend || TS16GUSDHC6 || 16GB (SDHC) || Class 6 || ? || ? || ? || {{yes}} || linux 2.6.28+29 (OM2009) || ||
|-
| Verbatim || 47225 || 1GB || || {{no}} || {{yes}} || {{yes}} || || || ||
|-
| Verbatim || 47206 || 4GB (SDHC) || Class 6|| || {{yes}} (surely) || {{yes}} (surely) || {{yes}} || {{yes}} || {{yes}} (surely) ||
|-
| vox-fon || 1 GB || 1GB || || {{no}} || {{yes}} || || || || ||
|-
| (Intenso) || ? || 4GB (SDHC) || || {{no}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ? || {{yes}} || {{yes}} (Some work needed to get it running, see [https://docs.openmoko.org/trac/ticket/1743 #1743]) || ||
|-
| Vendor || Model || Capacity || Speed || [[u-boot]] 1.1.6 || linux 2.6.17.14-fic5 || [[u-boot]] 1.2.0-moko8 svn1915 || [[u-boot]] 1.3.2-moko12 || linux 2.6.24+git75969 (2008.8 kernel as of Sept. 4, 2008) || OM2008.9's kernel ||
|}

Note that cards with a "'''no'''" may still work at times, but that we just have found their behaviour too erratic to consider acceptable.
(Also note that this is a bug in our version of u-boot. The cards are probably fine.)

[[Category:MicroSD]]

Stable Hybrid Release

2009-03-15T10:40:24Z

Kero:

{{Languages|SHR}}
{{Distributions|SHR}}
{{SHR}}

== Why SHR exists ==
The [[Stable Hybrid Release]] (SHR) is intended to be a community driven distribution composed of the [[OpenmokoFramework|FSO]] and some basic applications, that can be configured to use several different graphical toolkits, for example GTK or EFL. SHR is based on the FSO build. At first, SHR was introduced in order to use the [[Openmoko2007.2]] GTK software in combination with the new [[OpenmokoFramework|FSO]], but things have changed.

====Why not just use plain FSO?====
[[FSO]] is the initiative by Mickey Lauer and crew to create a good [[D-Bus]] infrastructure which runs on the neos, among other devices.

FSO is by far the most stable & usable release, if all you want is a phone. (I mean *all*. It just has a dialer, which is a demo application.)

FSO is never intended on its own to be a full image, it's just the infrastructure and a demo app.

Other people are supposed to put a front end on FSO. So that's what we're doing.

==Feature overview==

In the overview below are all the essential features and their status for the currect '''out of the box''' SHR testing distribution (2009-03-03+modules+updates). Green indicates that this part is well functioning, red indicates a known requirement which will be implemented later on and orange indicates functionality that can (and should) be fixed easily in the distribution for known fixes are available.

{| cellspacing="0" class="sortable wikitable" border="1" style="font-size: 85%; text-align: left; width: auto;"
|-
! Category
! Name
! Functionality
! Comments
|-
| System
| Power Management
| style="background:#88FF88;"| Suspend
| when slow, use [[Qi]]
|-
| System
| Package manager
| style="background:#FFDD88;"| Installing and upgrading packages
| style="background:#FFDD88;"| [http://trac.shr-project.org/trac/ticket/314 SHR ticket #314]
|-
| System
| Keyboard
| style="background:#FFDD88;"| Offer stylus and finger friendly keyboards
| style="background:#FFDD88;"| install alternative keyboards [http://trac.shr-project.org/trac/ticket/200 SHR ticket #200]
|-
| GSM
| Network
| style="background:#88FF88;"| Connect via SIM and PIN
|
|-
| GSM
| Network
| style="background:#FF8888;"| Flight mode
| style="background:#FF8888;"| [http://trac.shr-project.org/trac/ticket/333 SHR ticket #333]
|-
| GSM
| Dailer
| style="background:#88FF88;"| Receiving Call
|
|-
| GSM
| Dailer
| style="background:#88FF88;"| Making Call
|
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Overview Log (In, Out, Answered, All)
| style="background:#FF8888;"| should be in SHR Illume theme
|-
| GSM
| Phone Log
| style="background:#88FF88;"| Making reply Call from Log
|
|-
| GSM
| Phone Log
| style="background:#FF8888;"| Sending reply SMS from Log
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Receiving SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Selecting SMS from Overview
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Viewing SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending new SMS
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Sending reply SMS
|
|-
| GSM
| SMS
| style="background:#FF8888;"| Making reply Call
|
|-
| GSM
| SMS
| style="background:#88FF88;"| Deleting SMS
|
|-
| GSM
| GPRS
| style="background:#FF8888;"| Configuring and Enabling TCP/IP
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Reading SIM contacts
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Selecting SIM contact from Overview
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Editing SIM contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Deleting SIM contact
| does not stay at position in list
|-
| Shared
| Contacts
| style="background:#FF8888;"| Quick lookup contact with keyboard
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Calling contact
|
|-
| Shared
| Contacts
| style="background:#88FF88;"| Sending SMS to contact
|
|-
| WiFi
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling TCP/IP
| 1) Settings->Internet->WiFi radio=On 2) Mofi
|-
| WiFi
| MoFi
| style="background:#FFDD88;"| Network Manager
| style="background:#FFDD88;"| [http://trac.shr-project.org/trac/ticket/338 SHR ticket #338]
|-
| GPS
| Service
| style="background:#88FF88;"| Receiving GPS data
| automatically turned on
|-
| USB
| Ethernet
| style="background:#88FF88;"| Configuring and Enabling TCP/IP
| style="background:#FF8888;"| done automatically with insecure password
|-
| Audio
| Headset
| style="background:#FF8888;"| Handsfree calling
| headphones work, microphone does not work
|-
|}

== Install ==

Installing SHR is very easy. I will explain how to install the [http://build.shr-project.org/shr-testing/images/om-gta02/ testing] version of SHR for GTA02 (Freerunner). It is stable enough for a daily use. Stable version will be available soon ([http://blog.shr-project.org/ Stable announcement]), [http://build.shr-project.org/shr-unstable/images/om-gta02/?C=M;O=D unstable] (for the adventurous testers) is also available, but read [http://blog.shr-project.org/2009/03/time-for-testing.html this blog announcement] on why this is currently not recommended.

I suppose that you know how to use [http://wiki.openmoko.org/wiki/NeoTool NeoTool]

- the [[Qi]] bootloader (optional, u-boot should work as well)

- the [http://build.shr-project.org/shr-testing/images/om-gta02/uImage-om-gta02-latest.bin kernel]

- the root filesystem ([http://build.shr-project.org/shr-testing/images/om-gta02/shr-lite-image-om-gta02.jffs2 flash image] or [http://build.shr-project.org/shr-testing/images/om-gta02/shr-lite-image-om-gta02.tar.gz tarball])

You can view the sources [http://git.shr-project.org/git/ here].

== Connecting your FreeRunner to your computer ==
For the next configuration steps, you will need to type some commands. It is much easier to type on a real keyboard than on a touch screen.
So you need to connect your FR to you computer, and make a bridge to internet.
Use [http://wiki.openmoko.org/wiki/USB_Networking this page].
NOTE: On first boot after flashing, USB networking can not work. If it's happening, simply reboot and try again.

== Setting local time ==
As any linux system, the UTC time is used by the system. First of all, adjust this time:
date -u -s 010220052009
Fri Jan 2 20:05:00 UTC 2009

Then, you need to "localise" your system.
Search for the appropriate country with:
opkg list | grep tzdata

then install the one corresponding to your area.
opkg install tzdata-europe

Then select your city (search the city available in /usr/share/zoneinfo/your-country, example Paris)
ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime

You can fully localise your system by installing the glibc-binary-localedata correponding to your langage. Search the ones available with:
opkg list | grep glibc-binary-localedata

install with (example for France)
opkg install glibc-binary-localedata-fr-fr

== Changing root password ==
SHR is shipped without root password (just press enter)

This is dangerous if you connect using USB. You need to activate the root password:

passwd

and type your selected password (2 times)

== Customize the RingTone ==
You need to have a file containing the RingTone you want for your FR. You can find some at [http://wiki.openmoko.org/wiki/Ringtones#svn.openmoko.org_ringtones RingTone]

Then transfer it to your FR :
scp file root@192.168.0.202:/usr/share/sounds/

Now you can select ringtone in SHR Settings.

== Sound Control ==

Up to now, there is no graphical interface to control the sound
=== Mic and HP ===
The first idea is to use alsamixer; bad idea! There are 94 controls, and your modifications will be lost at the next reboot.Finding documentation is not easy. Here is my understanding:
Scenari are used for each case. They are located in /usr/share/openmoko/scenarios/
- capturehandset.state
- gsmheadset.state
- headset.state
- voip-handset.state
- gsmhandset.state
- gsmspeakerout.state
- stereoout.state

Each file is a set of value for the 94 parameters. I have identified some:

- Control 48: internal mic of the tel (set to 2 or 3)

- Control 4 : internal speaker (set from 110 to 120)

- Control 49: headset mic

- Control 3 : headset speaker

Generic info to the Neo soundsystem:

* [[Neo 1973 audio subsystem]]
* [[Neo alsamixer#Settings_Descriptions|Neo alsamixer - Settings Descriptions]]
* [[Neo Freerunner audio subsystem]]

=== Ringing ===

You can define a short ringtone, repeated many times, or a long one, repeated 1 time

File: /etc/freesmartphone/opreferences/conf/phone/default.yaml

Parameter: ring-volume # Ring Volume control 0 (mini) to ? maxi)
Parameter: ring-length # min time for ringtone. Must be greater than the duration of you ringtone

File: /etc/freesmartphone/opreferences/schema/phone.yaml
Parameter: ring-loop # define the number of loop of ringtone to play

=== Message alert ===
File: /etc/freesmartphone/opreferences/conf/phone/default.yaml
Parameter: message-volume # Ring Volume control 0 (mini) to ? maxi)
Parameter: message-length # min time for message alert. Must be greater than the duration of you message alert

File: /etc/freesmartphone/opreferences/schema/phone.yaml
Parameter: message-loop # define the number of loop of incoming message music to play

== Known Issues ==
=== Phone ===

GSM network is lost after one day of uptime: restart your FR once a day!

=== Address Book ===

SHR is not implementing a PIM (Personal Information Manager) yet. Work is in progress, but to included in SHR testing this has some consequences on daily use:

* Only contacts on the SIM card are available.

* It is not possible to import a Vcard file.
** It seems to be possible with [gopher://gopher.fnordpol.de/9/data/DbusAccessScripts_0.0.0.tar.gz this] script written by [[User:Zem#DBus_Access_Scripts|Zem]].

== More Information ==

Visit:
* [http://blog.shr-project.org Blog]
* [http://trac.shr-project.org Trac (Bugtracker)]
* [http://git.shr-project.org Git (Sourcecode-repository)]
* [http://build.shr-project.org Buildhost (Downloads)]
* [http://shr-project.org/trac/wiki/Tweaks Tweaks (On the Wiki)]
* [http://lists.projects.openmoko.org/mailman/listinfo/shr-devel SHR Development Mailing List]

[[Category:SHR]]

MokoMakefile

2008-08-03T12:38:34Z

Kero:

{{Languages|MokoMakefile}}

MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.

Unlike the manual process described at [[Building Openmoko from scratch]], MokoMakefile does not install anything into your system (it can and should be started as normal user).
MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of Openmoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Openmoko2007.2#How_to_build|official Openmoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build both OM-2007.2 and QTopia-X11 images.

MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the Openmoko images into it and run it. These commands can also be used without downloading and building the whole Openmoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].

== Requirements for building Openmoko ==
Independent on whether MokoMakefile or a manual process is used to setup an Openmoko build environment, there are several requirements which must be fulfilled in order for the Openmoko build to succeed:

* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.

* Disk space: You need about 12 GB of available disk space for the Openmoko build to succeed (see below for a tip on how to reduce this).

* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.

=== Required software ===

Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://wiki.openembedded.net/index.php/OEandYourDistro but they may be outdated, incomplete and do not cover everything which Openmoko needs to build.

A good guide is [[Building Openmoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building Openmoko from scratch]]

If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of Openmoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.

==== Package requirements by distribution ====
Your distribution needs to provide these commands in order for OpenEmbedded to start building:
subversion texi2html texinfo help2man

Openmoko needs the development packages (with header files, development libraries and tools) in order to finish building:
ncurses zlib (or libz) OpenSSL GTK++

Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.

===== Debian / Ubuntu =====
sudo apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk zip unzip cogito

sudo apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev
# To prevent errors in host validation
sudo apt-get install ca-certificates
# For Openmoko 2007.2 using BitBake-1.8.8:
sudo apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg
# For building faster
sudo apt-get install quilt python-psyco ccache
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.
sudo apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools

# On Ubuntu 8.04, the following was required instead of cogito
sudo apt-get install git-core
# Ubuntu links /bin/sh to /bin/dash, but some scripts fail because they use pushd and popd, which dash does not support
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh

# This may be needed only for ASU
sudo apt-get install libxtst-dev

===== SuSE =====
For building Openmoko on 10.3, you need
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm

See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]

10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.

==== For all distributions ====
As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.

If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:
ENABLE_BINARY_LOCALE_GENERATION = "0"

===== Proxy =====
Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.

== Building Openmoko with MokoMakefile ==

=== Preparations ===
Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):
mkdir ~/moko ; cd ~/moko

=== MokoMakefile ===
Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile

{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}

=== Environment ===
Set up the environment:

make setup

If you want to make the ASU or FSO instead of the OM2007.2, see [[Distributions]], you need to edit your Makefile. Change OM_GIT_BRANCH to one of the following:
OM_GIT_BRANCH := org.openmoko.dev # OM2007.2
OM_GIT_BRANCH := org.openmoko.asu.dev # ASU
OM_GIT_BRANCH := org.openmoko.asu.stable # ASU stable
OM_GIT_BRANCH := org.openembedded.dev # FSO

If you are building for the Neo1973 GTA01, then also do this
make setup-machine-neo
If you are building for the Freerunner GTA02, then also do this
make setup-machine-freerunner

=== Building ===
Before starting a lengthy make process, check the Tips section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image
(or use "make openmoko-qtopia-x11-image" if you're building the ASU)
(or use "make fso-image" if you're building the FSO)

''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973

This will set up the recommended directory structure as described in [[Building Openmoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

==Updating the environment==
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To make sure that any recent changes to the build directory structure have been applied:
make setup

3 - To update the Openmoko repository checkout and the MokoMakefile patches to the latest version:
make update

A quick way to rebuild a new image with the latest updates:
make update-makefile && make setup update openmoko-devel-image

==Build issues==
First, make sure that the problem is reproducible after running

make update-makefile && make setup && make update

then run

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

and finally

make openmoko-devel-image

With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.
You can then [[Flashing openmoko||flash these.]]

If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [http://wiki.openmoko.org/wiki/Development_resources#IRC IRC].

If you have chronic build problems, cleaning your environment variables and re-running the build from scratch may help. The following script should remove all non-essential variables; you should also manually trim your path to the minimum.
`env | grep -Ev '^SHELL=|^TERM=|^OLDPWD=|^USER=|^USERNAME=|^PATH=|^EDITOR=|^LANG=|^HOME=|^DISPLAY=|^_=' | sed 's/^$.*$=.*/unset \1/'`

(you must include the backtics).
Note that on some boxes it is necessary to call "make" by typing "/usr/bin/make" afterwards.

On current ubuntu boxes another trick is necessary:
glibc_2.6.1 fails to build since it is unable to generate the necessary locales until you type in the following line:
sudo sysctl -w vm.mmap_min_addr=0
Note that this temporarily disables a new security vulnerability check that has entered /etc/sysctrl - but that makes problems with loads of applications.
To re-enable this check do the following:
sudo sysctl -w vm.mmap_min_addr=65536
See the talk page of this article for more details on this solution.

===Known MokoMakefile errors ===
==== SVN Server Certificate Errors ====
If you get an error like the following:
<pre>
NOTE: Fetch svn://svn.projects.openmoko.org/svnroot/;module=assassin;proto=https
Error validating server certificate for 'https://svn.projects.openmoko.org:443':
- The certificate is not issued by a trusted authority. Use the
fingerprint to validate the certificate manually!
Certificate information:
- Hostname: projects.openmoko.org
- Valid: from Thu, 05 Jun 2008 01:02:42 GMT until Tue, 02 Dec 2008 01:02:42 GMT
- Issuer: http://www.cacert.org, Root CA
- Fingerprint: a5:7d:4e:37:e8:94:ee:ba:c1:e8:e9:4b:33:cb:34:91:a9:6d:d3:84
(R)eject, accept (t)emporarily or accept (p)ermanently? svn: OPTIONS of 'https://svn.projects.openmoko.org/svnroot/assassin': Server certificate verification failed: issuer is not trusted (https://svn.projects.openmoko.org)
</pre>

It means you haven't yet accepted the server certificate for the SVN server. To remedy this, execute the following commands, and hit "p" (to permanently accept the certificate) when prompted:
<pre>
cd /tmp
svn co https://svn.projects.openmoko.org/svnroot/assassin
rm -rf assassin
cd -
</pre>

==== exposure_svn and Subversion 1.5.0 ====

If you get an error like this:

<code>
"NameError: global name 'log' is not defined"
</code>

There's a bug with subversion 1.5.0 -- downgrade to 1.4.x (or check out the latest subversion sources and use those as they're fixed) and re-fetch the sources.

===Fixes for distribution/environment-specific or isolated issues===

Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

==Tips==
*Make sure umask is set to 0022 before you run "make setup"

*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly. As of 10/16/07, this appears to be present in local.conf by default.

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC)

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"

* To not build any binary locales at all, add this to local.conf:
ENABLE_BINARY_LOCALE_GENERATION = "0"

* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building <code>openmoko-devel-image</code>, run <code>make build-package-package-index</code>.

[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.

* Make sure you do not have . in your PATH, this causes an "unrecognized option -Qy" error when building g++spec

=== Useful commands ===
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.

; make openmoko-devel-image : build the full development image

; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries

; make openmoko-toolchain : builds [[toolchain]]

; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[Openmoko under QEMU]]).

; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.

; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].

; make build-package-<package name> : buids ''<package name>'' package

; make update-makefile : updates MokoMakefile

; make clean-package-<foo>: cleans the "<foo>" package

; make setup : to make sure that any recent changes to the build directory structure have been applied

; make update : to update the Openmoko repository checkout and the MokoMakefile patches to the latest version

; make setup-machine-neo : setup for GTA01 version of Neo1973

; make setup-machine-freerunner : setup for GTA02 version of Freerunner

==Developing with MokoMakefile==

{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR/build
. ../setup-env
bitbake -c unpack openmoko-messages
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
''...make the changes...''
cd -
bitbake openmoko-messages

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/openembedded/packages/mycoolpackage
quilt add trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/openembedded/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/openembedded/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update openmoko-devel-image

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [[Building a hello world application|Hello World!]] tutorial available too.

==Testimonials==
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".

Project page:
http://mokomakefile.projects.openmoko.org/

[[Category:Openmoko]]
[[Category:Applications]]
[[Category:Application Developer]]

Gsmd

2008-02-16T02:55:43Z

Kero:

[[gsmd]] is the [[GSM]] daemon running in background of an OpenMoko phone, managing the traditional 'phone' parts (voice/sms/gprs communication links) of the phone.

Further technical details and API documentation in progress, is available [[Gsmd/document |here]].

== Usage ==

=== On the phone ===
gsmd is usually started as a background daemon when booting by the /etc/init.d/gsmd script, in this case gsmd outputs debug messages to the file "/tmp/gsm.log" (stdout and stderr is redirected there).

For debugging purposes gsmd can be run in foreground mode, options can be queried like:
<pre>
> gsmd --help
gsmd - (C) 2006 by Harald Welte <laforge@gnumonks.org>
This program is FREE SOFTWARE under the terms of GNU GPL

Usage:
-v --version Display program version
-d --daemon Deamonize
-h --help Display this help message
-p dev --device dev Specify serial device to be used
-s spd --speed spd Specify speed in bps (9600,38400,115200,...)
-F --hwflow Hardware Flow Control (RTS/CTS)
-L --leak-report Leak Report of talloc memory allocator
-l file --logfile file Specify a logfile to log to
</pre>

If your GSM modem is attached to ttySAC0 (like in the [[:Category:Neo1973 Hardware | Neo1973]]), invoke it as e.g.:
> gsmd -p /dev/ttySAC0 -s 115200 -F
(baud rate seems to be autodetected by the modem)

=== From host PC===
With recent [[uboot]] (svn > r2885), the gsm modem can be powered on and connected to uboot's serial console from uboot itself. Thus allowing the host PC to interact directly with the modem. Some notes about getting gsmd running in this manner is [[User:Miki/hosted_gsmd|here]].

== libgsmd ==

libgsmd is a library with C language API for application programs. Programs using this library can use the phone, e.g. make phone calls, receive incoming calls, register to the network, etc.

== libgsmd-tool ==

libgsmd-tool is a small demo application that can be used to demonstrate the usage of the libgsmd API.

== Usage ==

libgsmd-tool has multiple modes.

=== Usage of shell mode ===

Shell mode provides a simple text-based command interface for making voice calls.

The shell mode can be started using

libgsmd-tool -m shell

It can be used like in the following example:

<pre>
> src/util/libgsmd-tool -m shell
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

?
A Answer incoming call
D Dial outgoing number
H Hangup call
O Power On
o Power Off
r Register to network
R Register to given operator (R=number)
U Unregister from netowrk
P Print current operator
L Detect available operators
Q Read signal quality
T Send DTMF Tone
n Print subscriber numbers
pd PB Delete (pb=index)
pr PB Read (pr=index)
prr PB Read Range (prr=index1,index2)
pf PB Find (pf=indtext)
pw PB Write (pw=index,number,text)
ps PB Support
pm PB Memory
pp PB Set Memory (pp=storage)
pRr Retrieve Readrg Records
pRf Retrieve Find Records
sd SMS Delete (sd=index,delflg)
sl SMS List (sl=stat)
sr SMS Read (sr=index)
ss SMS Send (ss=ask_ds,number,text|["text"])
sw SMS Write (sw=stat,number,text)
sm SMS Storage stats
sM SMS Set preferred storage (sM=mem1,mem2,mem3)
sc SMS Show Service Centre
sC SMS Set Service Centre (sC=number)
q Quit

O
# EVENT: PIN request (type=1) Please enter PIN: 6582
r
# EVENT: Netreg searching for network
EVENT: Netreg registered (home network)

D03024033902
# Dial 03024033902
EVENT: Call Progress: UNKNOWN
EVENT: Call Progress: PROCEED
EVENT: Call Progress: SYNC
EVENT: Call Progress: ALERT
H
# Hangup
EVENT: Call Progress: DISCONNECT
EVENT: Call Progress: RELEASE

EVENT: Incoming call type=2!
EVENT: Incoming call clip=`"03024033902"'
EVENT: Incoming call type=2!
A
# Answer
RSTR=`OK'
H
# Hangup
RSTR=`OK'
</pre>

=== Usage of atcmd mode ===

The atcmd mode is a passthrough-mode. Passthrough means that it accepts [[GSM 07.07]] commands, passes them through the daemon to the phone, and returns you the response. this is very useful for debugging.

The atcmd mode can be started using

libgsmd-tool -m atcmd

Usage is like in the following example:

<pre>
> src/util/libgsmd-tool -m atcmd
libgsm-tool - (C) 2006 by Harald Welte
This program is Free Software and has ABSOLUTELY NO WARRANTY

AT+CPAS
STR=`AT+CPAS'
RSTR=`+CPAS: 0'
AT+COPS=?
STR=`AT+COPS=?'
RSTR=`+COPS: (2,"E-Plus","E-Plus","26203"),(3,"o2 - de","o2 - de","26207"),(3,"Vodafone.de","Vodafone","26202"),(3,"T-Mobile D","TMO D","26201")'
</pre>

== Network related functions ==
Operator selection functions were implemented and merged into SVN head[http://lists.openmoko.org/pipermail/gsmd-devel/2007-September/000216.html]:

The new commands in libgsmd-util are as followings:
R - Register to given operator (R=number)
P - Print current operator
L - Detect available operators
Q - Read signal quality

This is implemented by the functions with "_opers_" naming.
== Currently missing ==

(please add items to this list if you're missing more features)

* Phone related functions
** Airplane mode / gsmd stop (this will be done outside gsmd, by using runlevels / upstart)
** Capability to set-up Emergency Calls, even if the device does not hold a SIM card
** obtain manufacturer/model/revision/IMEI
** Ability to notify user if the SIM card is locked (or even automagically unlock it?)

* SMS related features
** send SMS
** receive SMS
** obtain IMSI
** access to SIM-card stored SMS - ''No longer missing - see help''

* SIM related functions
** read phonebook entry - ''No longer missing - see help''
** write phonebook entry - ''No longer missing - see help''

* GPRS related functions
** set up GPRS link, use it via separate DLC of TS07.10 multiplex

* gsmd internal infrastructure
** fine-grained event subscriptions (rather than wildcard-subscribe)
** possibility to specify log-level from command line
** logfile re-opening on SIGUSR1 or SIGHUP (logrotate)
** permission handling
** d-bus interface

== Implementation Thoughts ==

== Testing framework ==

Emulating/mocking the firmware, gsmd and libgsmd can be tested for functionality; on any machine.
See [[User:Kero|Kero's page]] or go directly to [http://chmeee.dyndns.org/om/testing_gsmd.html the (lib)gsmd testing page].

== State tracking ==

gsmd needs to do apropriate state tracking of the underlying GSM hardware. For many of the state transition we only get events from the GSM Modem, but don't have apropriate query commands. Thus, assuming gsmd runs all the time, applications can come and go, but still have an idea about the current state of the modem, even if they missed the initial state transitions.

Also, gsmd state tracking allows us to allow for safer interoperability of multiple applications. If i.e. one applications has just started an outgoing call, gsmd can detect another application who intends to interfere with that and deny access

=== device power state ===

* modem completely off, not responding to AT commands
* modem responding to AT commands, but powered off (CFUN=0)
* modem responding to AT commands, in some power saving mode
* modem responding to AT commands, powered on, fully operational (CFUN=1)

=== Suspend power state ===

It must also configure the modem so that it can on appropriate events wake the system from sleep.

=== network registration state ===

* not registered to any network, not trying to register
* not registred to any network, searching/trying to register
* registered to home network (including cellID)
* registered to roaming network (including cellID)

=== ciphering indication state ===

* ciphering indications not supported by modem
* ciphering indications supported, but disabled in SIM
* ciphering indications supported, ciphering active
* ciphering indications supported, ciphering inactive

=== call state ===

* idle
* busy

Sources of gsmd are kept in [[OpenMoko svn]] in src/target/gsm directory.

{{Languages | Gsmd}}

[[Category:Software]]
[[Category:Implemented]]

User:Kero

2008-02-16T02:52:50Z

Kero:

Favourite programming language: Ruby

Previous PDA experience: familiar-linux on iPAQ

interested in pim-suites; ecal+dbus+gtk seems enough to build some nice pim applications on OpenMoko.

== Ruby ==

Ruby including '''cairo (as of Oct 20)''', gtk2 and glade2 bindings available! See link below.

dbus seems nice, but there is a clear lack of which libs provide which interfaces over dbus in openmoko/openembedded.

esd/dbus as evolution server seems nice (but is it right?) Revolution (Ruby-evolution) also works.
However, the underlying iCal/VCard s*cks bigtime. A business card is ''not'' an entry in my address book.
An appointment in iCal is OK-ish, but making an appointment is still impossible, even with RFC 2446 in place.
Perhaps GUIs just do not show what a user is supposed to do.

But the whole world uses it, so I guess I have no real alternative.

== Testing framework for gsmd/libgsmd ==

Because I find (lib)gsmd lacking in stability, I wrote a little proof of concept for a testing framework in
[http://rspec.info/ Rspec], which you can find [http://chmeee.dyndns.org/om/testing_gsmd.html on my own server].
The framework emulates/mocks the firmware. This way, you can run the tests on any linux PC.

Any user can write a test for functionality that should work (typically, when they find a bug; developers have
higher responsiblities). The behaviour of a test should be predictable. The behaviour of firmware can be set per test,
and the behaviour of the application should be put in the When/Then steps of the framework.

== External Page ==

[http://chmeee.dyndns.org/om/ Kero's external OpenMoko page] providing screenshots and the ruby feed (and some other code).

User:Kero

2007-10-21T18:58:25Z

Kero:

User:Kero

2007-10-04T21:58:50Z

Kero:

Favourite programming language: Ruby

Previous PDA experience: familiar-linux on iPAQ

interested in pim-suites; ecal+dbus+gtk seems enough to build some nice pim applications on OpenMoko.

----

looked at dbus right now

next is libecal/evolution

Ruby including gtk2 and glade2 bindings available! See link below

----

[http://chmeee.dyndns.org/om/ Kero's external OpenMoko page] providing screenshots and (ruby) code.

MokoMakefile

2007-08-31T21:40:31Z

Kero:

==MokoMakefile==
MokoMakefile is a fully automated way of setting up an OpenMoko development environment. It is an invaluable tool for getting new developers up and running with a build environment which is configured the same as all the other existing developers. It brings the same repeatability to build environment creation and maintenance as that which OpenEmbedded brings to the main task of actually building embedded software distributions.

Note that MokoMakefile does *not* replace bitbake, or svn, or monotone, or openembedded, or qmake, or anything else. It is a wrapper around all that to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by OpenMoko. Note that you need about 12 GB of available disk space for MokoMakefile to succeed (see below for a tip on how to reduce this to . Please check that your RAM + swap partition space is greater than 512 MB (around 1GB?). Note that the initial build can take 5 hours (on 2GHz core2duo without multiprocessor optimization) to several days.

MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of OpenMoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[Building_OpenMoko_from_scratch|official OpenMoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.

The MokoMakefile is able to build either OM-2007.1 or OM-2007.2 images. The core team chooses the default, but you can select one or the other at the top of the Makefile.

=== Installation ===

==== With Qemu ====
This is an easy and good way to install a local version of openmoko on your linux computer(ubuntu). This is mostly the fastest way to get things working (approximatly 15 min)

see [[MokoMakefile#QEMU]]

==== Manually ====
Here are the steps to use it:

1 - Make sure your build host is set up according to:
http://www.openembedded.org/wiki/OEandYourDistro
2 - Create your $OMDIR directory (note that you can change ~/moko to any directory you like):
mkdir ~/moko ; cd ~/moko
3 - Grab MokoMakefile:
wget http://www.rwhitby.net/files/openmoko/Makefile

If that doesn't work, try

wget http://svn.nslu2-linux.org/svnroot/mokomakefile/trunk/Makefile

note: If you want to compile for the old version 2007.1 instead of the new
version edit the top of the Makefile. Edit the lines at the top to
look like this:
OPENMOKO_GENERATION = 2007.1
#OPENMOKO_GENERATION = 2007.2
On kubuntu and Debian Etch I also had to apt-get install help2man

4 - Set up the environment:
make setup
5 - Start building. Before starting a lengthy make process, check in Tips section about how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:
make openmoko-devel-image

This will set up the recommended directory structure as described in [[Building OpenMoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.

Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.

===Updating the environment===
For easy maintenance of your build environment the following commands are available.

1 - To update the MokoMakefile to the latest version:
make update-makefile

2 - To make sure that any recent changes to the build directory structure have been applied:
make setup

3 - To update the OpenMoko repository checkout and the MokoMakefile patches to the latest version:
make update

A quick way to rebuild a new image with the latest updates:
make update-makefile && make setup update openmoko-devel-image

===Reporting Problems===

First, make sure that the problem is reproducible after running

make update-makefile && make setup && make update

then running

make clean-package-<foo>

(where you replace <foo> with the name of the package which is failing)

then running

make all

If you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [http://wiki.openmoko.org/wiki/Development_resources#IRC IRC].

===Known MokoMakefile errors===

If you experience the following after changing from OM-2007.1 to OM-2007.2:

Patch bitbake-1.6.6-om3.patch does not apply (enforce with -f)

then type "make clobber-patches" to fix it. There was a period of 24 hours when there was a bug in the MokoMakefile which causes this problem. Once the patches have been clobbered, they will re-download and the problem will not reoccur.

===Work-arounds===

Work-arounds for temporary or isolated problems should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.

===Tips===
*You can reduce the amount of consumed disk space significantly by adding
INHERIT += "rm_work"
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly.

*If you an encounter an error with monotone similar to the following:
mtn: misuse: database /home/''username''/moko/OE.mtn is laid out according to an old schema
Then you need to upgrade OE.mtn Use the following command while in ~/moko:
# mtn --db OE.mtn db migrate

*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.
rm sources/<package>*
cd build
. ../setup-env
bitbake -crebuild <package>
after that your build might just work again.

*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.
Edit the local.conf and add the following lines:
PARALLEL_MAKE = "-j 4"
BB_NUMBER_THREADS = "4"

Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.

*For amd64 host users you need the patch from http://bugs.openembedded.org/show_bug.cgi?id=1765 to build db3-native

* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.

* To prevent building tons of locales, add a line like this to local.conf:
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"

===QEMU===
The MokoMakefile now has support for automatically building, flashing, and running [[OpenMoko under QEMU|the new Neo1973 emulator]] (which is based on QEMU).

====Install in Ubuntu (7.04)====
Make sure your build host is set up according to:
http://www.openembedded.org/wiki/OEandYourDistro
make a new directory:
mkdir openmoko
cd openmoko
install the dependencies:
sudo apt-get install gcc-3.4 lynx netpbm libsdl1.2-dev dosfstools
get the openmokofile:
wget http://www.rwhitby.net/files/openmoko/Makefile
build it for Qemu:
make qemu
This will build openmoko for Qemu. Once that is completed, it will automatic run it into the emulator. After you have closed it and want to run openmoko again, you should use the following command:
make run-qemu

remark: If you want to calibrate your screen,
look at http://onlinedev.blogspot.com/2007/08/calibrating-openmoko-v20072.html

====Others====

Dependencies:

*gcc 3.4 or 3.3 ('apt-get install gcc-3.4' in Ubuntu 7.04)
*lynx ('apt-get install lynx' in Ubuntu 7.04)
*netpbm ('apt-get install netpbm' in Ubuntu 7.04)
*sdl-devel ('apt-get install libsdl1.2-dev' in Ubuntu .704)
*mkdosfs ('apt-get install dosfstools' in Debian 4.0)

“'''make qemu'''” will build qemu-neo1973, download the latest official OpenMoko images, flash the images into the virtual NAND flash, create an empty virtual SD card, and run the emulator (you still need to install the makefile as mentioned above, however). If this is all you want to do, then you don't even need monotone installed on the machine, and you don't need to download the OpenEmbedded monotone database. Just make sure you don't type "make setup" (as that will invoke all the monotone and openembedded stuff).

Other targets are “'''make download-images'''” (to download the latest official images), “'''make flash-qemu-official'''” (to flash those images) and “'''make flash-qemu-local'''” (which will flash your latest locally built images), which can then be followed by “''''make run-qemu'''” or “'''make run-qemu-snapshot'''” to run the emulator with the most recently flashed images. You can also use “''''make qemu-copy-package-''foo'''''” to copy the <code>.ipk</code> file for package ''foo'' to the virtual SD card, and later use “''''ipkg install /media/mmcblk0/''file'''''” from within the emulated Neo1973 to install the package.

You're also invited to read more about how to run [[OpenMoko under QEMU]] in the article dedicated to this subject.

===Developing with MokoMakefile===

{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}

For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.

To make in-tree changes and have them built and used by qemu:

cd $OMDIR/openmoko
quilt new descriptive-patch-name.patch
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify
...make the changes...
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there

Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!

To build the changes and have them used by qemu:

make build-qemu
make flash-qemu-local
make run-qemu

If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):

cd $OMDIR/build
. ../setup-env
bitbake -c unpack openmoko-messages
cd ../build/tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/
...make the changes...
cd -
bitbake openmoko-messages

Then continue with MokoMakefile usage.

If you want to add an application to your openmoko distribution, do this:
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:
cd $OMDIR/openmoko/
quilt new mycoolpackage.patch
mkdir trunk/oe/packages/mycoolpackage
quilt add trunk/oe/packages/mycoolpackage/mycoolpackage_1.bb
quilt edit trunk/oe/packages/mycoolpackage/mycoolpackage_1.bb

The file should have the following content:
DESCRIPTION = "This is a cool package"
SECTION = "username/mycoolpackage"
PV = "1"

inherit autotools

SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"

Explanation:
* DESCRIPTION - Just a short text explaining the package
* SECTION - I have no clue, but I'll use username/mycoolpackage for now
* PV - Package Version
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.

This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do
$OMDIR/openmoko# quilt edit trunk/oe/packages/tasks/task-openmoko.bb
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.

Now run
quilt refresh
cd ..
make update all

And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.

=== Hello World application ===

There is a [http://wiki.openmoko.org/wiki/Building_a_hello_world_application Hello World!] tutorial available too.

===Testimonials===
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", and "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system".

Project page:
http://mokomakefile.projects.openmoko.org/

{{Languages|MokoMakefile}}

[[Category:Developer]]
[[Category:Guides]]

Openmoko Local Groups: Netherlands

2007-07-31T20:34:52Z

Kero:

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Ordered version
!Location
!Other
|-
|[[User:CathodioN|Geert Schuring]]
|Java EE, XML, UML
|Would like to develop Server components
|
|Ede, Gelderland
|willing to organize stuff i.e. meeting location/whatever.
|-
|[[User:Kero|Kero]]
|Ruby
|dbus and pim applications
|Base GTA01BV4
|Eindhoven
|
|-
|[[User:Ericsmith|Eric Smith]]
|Perl, Linux, VoIP
|
|
|Amsterdam
|Share Ideas, VoIP, GPS, SyncML
|-
|[[User:das_nl|Daniel Peptu]]
| C/C++, Java, .Net, Python
|(EN) I am watching this project growing for more than 8 months. I am desperately waiting for my Adv. kit.
|Adv. kit GTA01BV4
|Den Haag
|
|-
|[[User:Boudewijn|Boudewijn]]
|general
|Looking for some participants in a group order
|
|Zwolle
|
|-
|}

Openmoko Local Groups: Netherlands

2007-07-26T14:31:10Z

Kero: /* Possible Participants */

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
|-
|[[User:CathodioN|Geert Schuring]]
|Java EE, XML, UML
|Would like to develop Server components
|Ede, Gelderland
|willing to organize stuff i.e. meeting location/whatever.
|-
|[[User:Kero|Kero]]
|Ruby
|dbus and pim applications
|Eindhoven
|
|-
|}

Openmoko Local Groups: Netherlands

2007-07-26T14:30:55Z

Kero: /* Possible Participants */

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
|-
|[[User:CathodioN|Geert Schuring]]
|Java EE, XML, UML
|Would like to develop Server components
|Ede, Gelderland
|willing to organize stuff i.e. meeting location/whatever.
|-
|[[User:Kero]]
|Ruby
|dbus and pim applications
|Eindhoven
|
|-
|}

Openmoko Local Groups: Netherlands

2007-07-26T14:30:36Z

Kero: /* Possible Participants */

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
|-
|[[User:CathodioN|Geert Schuring]]
|Java EE, XML, UML
|Would like to develop Server components
|Ede, Gelderland
|willing to organize stuff i.e. meeting location/whatever.
|-
|[[Kero]]
|Ruby
|dbus and pim applications
|Eindhoven
|
|-
|}

Openmoko Local Groups: Netherlands

2007-07-26T14:30:24Z

Kero:

=== Possible Participants ===
{|border=1
!Name
!Skills
!Level of Interest
!Location
!Other
|-
|[[User:CathodioN|Geert Schuring]]
|Java EE, XML, UML
|Would like to develop Server components
|Ede, Gelderland
|willing to organize stuff i.e. meeting location/whatever.
|-
|[Kero]
|Ruby
|dbus and pim applications
|Eindhoven
|
|-
|}

PIM Storage

2007-03-12T20:50:44Z

Kero: /* Use Cases */

== Overview ==
PIM storage describes a means of storing data in an extensible and cross-referencable way.

== Goals & Objectives ==
* Method to exchange data between all applications completely transparent
* Personal data security / encryption
* Great bidirectional sync of personal data
* Easy method for [[Backup|backup]] (ideally this should be automatic)
* Real-time incremental search
* Autocomplete of personal data information

== Use Cases ==
* I would like to attach arbitrary data to a contact (AKA: custom fields)
* I would like some level of integration with automatic switching of profiles. For example, it would be cool to automatically backup my personal data to my desktop PC when I get home.
* I want to type the first few numbers of a phone number and be presented a list of matching contacts.
** I'd rather take a person, choose home/work, choose land-line/mobile and not bother with numbers anymore. Useful when I'm on my way to meet that person, or the person has his/her birthday, i.e. the person is already listed on my screen!
* I want to add a contact to multiple groups (AKA: categories)
* I want to be able to send my contact info to other OpenMoko devices over bluetooth

== Constraints ==
(TBD)

== Implementation Recommendations ==
* This will be based on [http://projects.o-hand.com/eds Embedded EDS], this way we will can directly use Evolution data, get OpenSync for free, and eventually be able to talk to a Microsoft Exchange Server using the Novell Connector.

== Interactions ==
* Embedded EDS needs libglade2, [[dbus]], and libdb.

== Unresolved Issues ==
* Synchronizing w/ Outlook
* Synchronizing w/ MacOS X
* Synchronizing w/ Google services

Possible solutions:
* mokod - An OpenMoko daemon to run on host operating systems

== Questions and Answers ==
Q: When will an Embedded EDS specification be available? i.e. How I can get applications to store and retrieve data from in it, in a compatible way?

PIM Storage

2007-03-12T20:47:01Z

Kero: /* Questions and Answers */

== Overview ==
PIM storage describes a means of storing data in an extensible and cross-referencable way.

== Goals & Objectives ==
* Method to exchange data between all applications completely transparent
* Personal data security / encryption
* Great bidirectional sync of personal data
* Easy method for [[Backup|backup]] (ideally this should be automatic)
* Real-time incremental search
* Autocomplete of personal data information

== Use Cases ==
* I would like to attach arbitrary data to a contact (AKA: custom fields)
* I would like some level of integration with automatic switching of profiles. For example, it would be cool to automatically backup my personal data to my desktop PC when I get home.
* I want to type the first few numbers of a phone number and be presented a list of matching contacts.
* I want to add a contact to multiple groups (AKA: categories)
* I want to be able to send my contact info to other OpenMoko devices over bluetooth

== Constraints ==
(TBD)

== Implementation Recommendations ==
* This will be based on [http://projects.o-hand.com/eds Embedded EDS], this way we will can directly use Evolution data, get OpenSync for free, and eventually be able to talk to a Microsoft Exchange Server using the Novell Connector.

== Interactions ==
* Embedded EDS needs libglade2, [[dbus]], and libdb.

== Unresolved Issues ==
* Synchronizing w/ Outlook
* Synchronizing w/ MacOS X
* Synchronizing w/ Google services

Possible solutions:
* mokod - An OpenMoko daemon to run on host operating systems

== Questions and Answers ==
Q: When will an Embedded EDS specification be available? i.e. How I can get applications to store and retrieve data from in it, in a compatible way?

User:Kero

2007-02-27T00:07:45Z

Kero:

Favourite programming language: Ruby

Previous PDA experience: familiar-linux on iPAQ

interested in pim-suites; ecal+dbus+gtk seems enough to build some nice pim applications on OpenMoko.

----

looking at dbus right now

next is libecal/evolution

gtk, glade, cairo seem rather workable.

----

[http://chmeee.dyndns.org/om/ Kero's external OpenMoko page] providing screenshots and (ruby) code.

User:Kero

2007-02-27T00:07:32Z

Kero:

Favourite programming language: Ruby

Previous PDA experience: familiar-linux on iPAQ

interested in pim-suites; ecal+dbus+gtk seems enough to build some nice pim applications on OpenMoko.

----

looking at dbus right now

next is libecal/evolution

gtk, glade, cairo seem rather workable.

----

[http://chmeee.dyndns.org/om/ Kero's external OpenMoko page] provding screenshots and (ruby) code.

User:Kero

2007-02-27T00:05:22Z

Kero:

Favourite programming language: Ruby
Previous PDA experience: familiar-linux on iPAQ
interested in pim-suites

looking at dbus right now
next is libecal/evolution
gtk, glade, cairo seem rather workable.

ecal+dbus+gtk seems enough to build some nice pim applications on OpenMoko.

[http://chmeee.dyndns.org/om/ My OpenMoko page]

User:Kero

2007-02-24T15:42:23Z

Kero:

Kero, Ruby, iPAQ, interest in pim-suites, looking at dbus right now. [http://chmeee.dyndns.org/om/ My OpenMoko page]

User:Kero

2007-02-24T15:33:51Z

Kero:

Kero, Ruby, iPAQ, interest in pim-suites, looking at dbus right now.