Openmoko - User contributions [en]

Wishlist/Accessories

2009-03-09T16:06:59Z

Dcorking: /* Bike kit */ link proposed solutions

{{Hardware Wishlist}}
This is a page detailing accessories that may be of use for your Neo1973.

This is both accessories that do not exist, and existing devices that may be good to add to a web-store.

Advertising on this page is permitted, but keep it brief and factual.

=Existing devices=

==Storage Devices==

* '''Seagate's DAVE (Digital Audio Video Experience)''' with Bluetooth 2.0 WiFi 802.11b/g and USB-on-the-go-Interface (USB-OTG) http://www.seagate.com/docs/pdf/marketing/po_DAVE.pdf

==Input Devices==

===Pedometer===

There are (at least) two uses for a Bluetooth pedometer as a Neo1973 accessory:

* As an input device for exercise-monitoring software

* A pedometer combined with a compass (see [[Wish_List_-_Hardware#Digital_compass]]) would allow the positioning software to perform [http://en.wikipedia.org/wiki/Dead_reckoning dead reckoning] when the GPS signal has been lost. The US Army's [http://www.army-technology.com/projects/land_warrior/ Land Warrior system] already does this. (Maybe the pedometer is partly redundant with the accelerometers for dead reckoning tasks? See the [http://www.autospectator.com/modules/news/article.php?storyid=9942 SiRFDiRect announcement].)

=Wishlist=
==Special covers==
Different special covers could be made available with features like:
* A standard slip-on or clip-on template (possibly with buttons) to make the touch-screen blind accessible
* Small metal frame for protection (like Siemens M65, only with more style)
* Case with mirror on the back, for putting on makeup/checking appearance or helping with self-portraits with an integrated camera.
* Option to completely design printable case styles, perhaps with engraving. Ability to share these on a 'community' site.
* Solar powered recharger (perhaps as extendable/unfoldable [[Expansion Back]]).
* Rubber protection like available for iPod, of course in different colors and transparency.
* Underwater case. This could be a housing that fits around a normal FreeRunner like the kinds for digital cameras. Alternatively, it could be an actual case that the FreeRunner guts fits into.
* Screen Protector: A simple and very easy to produce screen protector, like the one on my iPaq:

Protector Flipped up image: http://www.pocketpcthoughts.com/images/ppct-ipaq6900-preview-small-01.jpg

Protector Flipped down image: http://www.pocketpcthoughts.com/images/ppct-ipaq6900-preview-small-06.jpg

This serves the dual purpose of protecting the screen from scratches, and stopping user's ear/face from accidentally pressing buttons while talking.
* Scratch-proof protector a la [[InvisibleShield]]

==Car kit==
A car kit with a cradle which simultaneously recharges the device.

==Bike kit==
Sporting a GPS, the phone would be ideal to have mounted by a bracket on the bike handle bars. Viewable from your position over the handlebars. Snap-on/snap-off, and some locking mechanism that actually keeps the phone from getting airborne on a hard break. Also, a basic spring on the bracket, making bumps softer on the phone. This type of bracket would cost peanuts to make.
Should also include a padded and waterproof pack that you can place the phone inside, keeping it (somewhat) safe from the elements.
Would also be really cool if it was possible to create a dynamo that can charge the phone, like old school bike headlights.
=== Cadence ===
Something to measure the Cadence like a normal bike computer would be great.
=== Heartbeat ===
Have the possibility to measure the heartbeat would make it a great accessory for training :)
;See also
*[[Biking]]
*[[User:ThomasT#Bicycle Computer]]

==Charger conversion connector==
A flexible converter allowing you to recharge the Neo1973 with power from many DC sources such as other devices chargers.
Problems are that it may overload the DC source. It may require sensing of the input voltage, and reducing load if the voltage drops by a factor. Ideally the device should accept input voltage in the range of around 3.3v-28V in either polarity.

==Ability to connect a USB keyboard to the phones USB port==

It has a USB port. There are USB keyboards everywhere. It would be great to be able to ssh anywhere over wifi with a regular sized keyboard.

'''Portability'''

I think it should all be seen within the context of portability.
Have a keyboard incorporated, hinged along the long side, as noted elsewhere, with a micro-switch that induces hibernation on closing to conserve power.
Limit the touch screen function to different aspects of the file system and peripheral aspects - in other words, don't limit it to a phone.
Those of us on the go need a phone, yes, but a lot more.
And all of society is evolving in this direction, so the product needs to also to survive.

USB2 - obviously, could be employed for something like this:

[http://www.techpin.com/new-32gb-usb-flash-drives-from-corsair/]

on which an entire OS with a massive /home partition could be carried round on a keyring.

Why try to crowd it all onto one screen when all you have to do is make an alteration in the size of your belt mounted, carry pouch.

The world needs the portable office, not just the portable phone.

--

Weaver.

==Make the stylus laser-pen recharge its batteries from phone while "docked"==

The stylus pen with built in laser pointer and flashlight seemed too big to be able to be attached to the phone while it is not being used, according to the demonstration video. If that is the case, make a slot on the phone where one can "dock" the pen while not using it. Make the phone recharge the batteries in the pen while the pen is docked to the phone.

==USB laser pointer==

Make a laser pointer that plugs into the USB connector and controlled in the same through the same interface that that wold make the FreeRunner a presentation remote control.

==Bluetooth earpiece with possible both-ears use==

It will be like a regular bluetooth speaker, but with another (wired or wireless) speaker in the other ear for music listening and telephony. The main, bulky piece with bluetooth could have a multi-purpose button: for answering calls when it whispers the name of the caller in my ears, or to raise/lower the volume of music or telephone call.

Would be nice to have them for the left-handed too.

==Make a VGA and/or DVI out connector==

The screen on the phone is small. But if it had a VGA out connector, we could connect an ordinary full sized monitor to it. It already has a USB connector. Imagine the coolness of attaching a usb keyboard and a 22" widescreen monitor to your ''phone'' and then viewing youtube videos through the phones wlan connection. You wouldn't have to carry around your laptop anymore since usb keyboards and vga monitors are availible practically everywhere.

This also may be used to show the conference presentations. There is enough memory in the phone to store the average presentation (the pdf or maybe even html formats could be used). Having the VGA port would transform it into very lightweight tool that could even replace a laptop for some people. It may be OK to have the same VGA resolution as presentations are usually prepared with the big fonts and figures.

== Pouch ==
The pouch could have external or internal place to keep the stylus.

== USB camera ==
A camera connected to the usb port.

== AUX button flashlight ==
Replace the indicator LED beneath the AUX button with a high brightness LED that can be used as a flashlight.

[[Category:Hardware ideas]]

Biking

2009-03-09T15:47:14Z

Dcorking: /* Commercial Chargers */ +link

The collection of information useful for biking with a Neo.

== Bike Mounts ==

* André Gaul [http://andre.web-yard.de/blog/2008/08/03/neo-freerunner-rocks-hard-rides-free/ documented a complete mounting kit]
* It's just a prototype :) but with some foam around the handlebar and careful positioning to avoid bumps, a [http://www.xmission.com/~bmidgley/neobike.jpg basic attachment] like this might work and makes it easy to "pinch" the screen when you need to finger tap something. [http://blogs.thehumanjourney.net/finds/entry/20080306 Something similar].
* [http://www.rabenfrost.net/openmoko/bikemount/ Images of an interesting bike mount]
* Another mount: [http://comiles.eu/~natanael/wordpress/2008/09/10/fahrradhalterung-fur-den-freerunner/ Description/Parts list (in German)] and [http://comiles.eu/~natanael/wordpress/2008/09/10/bilder-vom-fahrrad-freerunner/ Pictures]
* And [http://blog.printf.net/articles/2008/08/11/an-openmoko-bike-ride another one] "which I don't recommend very highly; I've had the phone come off it (without major damage, which is good) twice now while riding over rough road."

== Power Supply ==
If you want to keep the GPS running and have the screen always on or staying on with a long timeout, you'll need a way to supplement power.

=== Charging via hub ===
Connecting a hub ([http://nabendynamo.de/ Nabendynamo]) like the [http://www.peterwhitecycles.com/schmidt.asp SON] to a self-made or prebuilt charger can supply your device while biking.

The FreeRunner has three different [[Forcing_fast_charge_mode|charging modes]]: 100mA, 500mA and 1A. 100mA seems to be too low, as it is said, that the FreeRunner draws 100mA current even when it is switched off. A hub dynamo provides 500mA. If you want to use your lights while charging you need to connect the lights in series to the charger. At least the SON will increase the voltage and still delivers the same current. But you need a bypass circuit in case of less current draw of the charger when the battery is full.

Using an USB connection with that ID resistor for 1A mode provides the advantages that the charging mode is automatically correct.
This might be important if you stop frequently and so cause some kind of power "disconnect" and you do not want
to select the charge mode all the time. 1A mode does not harm the hub dynamo but if the dynamo can provide the 500mA also
at higher voltages, you can gain more charge current than in 500mA mode if you have a switching regulator.
For example if the dynamo would provide 10V 500mA and you would have a 100% efficient regulator,
you would have 5V 1A.

==== Commercial Chargers ====
* [[Zzing]]
* [http://www.jawetec.de/index.php?content=bikecharger&framing=radsport JaWeTec Bike Charger]
* There is a prototype of a hub featuring built-in USB-out which will hopefully be ready for mass market soon.
* The [http://www.ikonglobal.com/ ''Pedal & Power''] rim dynamo supplies 12 V and may be useful with an appropriate 12 V to USB adaptor, like [http://www.maplin.co.uk/Module.aspx?ModuleNo=228257&doy=9m3&C=SO&U=strat15 Maplin's A23JH]

==== self-made chargers ====
* [http://www.heise.de/kiosk/archiv/ct/07/23/190 Article (German) in c't 23/2007, page 190]
* maybe 6V [http://www.forumslader.de/6V-Version-des-Rad-Forum-Ladegeraets.125.0.html Forumslader] (You need at least one diode in series to be within the maximum ratings of the power managment IC and the FET switches in FreeRunner.)
* [http://www.iki.fi/~msmakela/electronics/dynamo5v/ Makela]

Linear regulator above might be replaced by [http://www.dimensionengineering.com/DE-SW050.htm DE-SW050].

=== Alternatives ===
If you decide to try solar, it's recommended to get a flexible panel and attach it to your backpack or something like that. One nice advantage here is it might also charge even when you're not moving. It's unlikely anything below 7 watts will keep things running. (5v * 1A = 5W).

It might work with an dynamo outside the hub like the one on the [http://www.reelight.com reelight], but it looks like their coil produces only 3vAC so it makes sense to use a custom coil.

An extra battery like [http://www.dealextreme.com/details.dx/sku.3060 Rechargeable USB Emergency Power Backup Pack 2400mAh $14.43] can also be useful for extending battery life-time.

== Software for biking ==

* [[TangoGPS]] + [http://blogs.thehumanjourney.net/finds/entry/20080826 OSM Cycle data]
* [[Navit]]
* [http://wiki.openstreetmap.org/index.php/Rana Rana] (uses [[Installing Pyroute|Pyroute]])
* [http://www.neo1973-germany.de/wiki/pylgrim pylgrim] bitmap map viewer. Dead.
* [[The_Bicycle_Motion_Information_Displayer]]
* [http://wiki.openstreetmap.org/index.php/Mumpot Mumpot]

=== See also ===
* [[GPS applications]]

== Heart Rate Monitor ==

According to [http://www.mail-archive.com/community@lists.openmoko.org/msg11248.html mailing list discussions] some heart rate monitors use [http://thisisant.com/index.php?section=5 ANT]. Due to the modern chip cases building a reliable homemade receiver seems to be difficult.

=== HRM Links ===
* [http://www.mikrocontroller.net/articles/Pulsuhrempf%C3%A4nger_mit_AVR_Butterfly German Microcontroller Wiki], Circuit diagram and DSP Simulation.

== Other Hardware ==
* [http://www.obico.de oBiCo] - An open bicycle linux computer - seems to be alive, but nothing there yet.

[[Category:Add-on data]]

Template:Gta01

2009-02-26T13:52:54Z

Dcorking: link

__NOTOC__
__NOEDITSECTION__

{| class="wikitable" cellspacing="2" cellpadding="2" style="padding: 0%; margin:0em 0em 1em 0em; border:1px solid #ffffff; background:#ffffff; width:100%;"
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:30% " |
[[Image:Ghostbackup.png|left]]
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:35% " |
<div align="left">
===Introduction===
*[[Neo 1973 hardware]]
*[[Disassembling Neo1973]]
*[[Getting Started with your Neo1973]]
===Hardware component===
*[[GTA01 revisions]]
=====Audio=====
*[[Neo1973 audio subsystem]]
*[[LM4857]]
=====Battery=====
*[[Neo1973 Battery]]
*[[Neo 1973 Battery Charging Logic]]
=====Power=====
*[[Neo1973 GTA01 Power Management]]
</div>
! style="background:#ffffff;border-left:1px solid #9999cc;border-right:1px ; border-top:2px solid 75d806; border:1px solid #ffffff; width:35% " |
<div align=left>

=====USB=====
*[[Neo1973 USB host]]
=====Debug Board=====
*[[Neo1973 Debug Board v2]]
*[[Neo1973 Debug Board v3]]
=====Accessory=====
*[[Car phone holder for neo1973]]
*[[Related Hardware]]
=====Neo1973:Alternate Cases=====
*[[Hardware:Neo1973:Alternate Cases]]
※[[:Category:Neo1973 alternate cases|See more about Neo 1973 Alternate Cases]]
</div>
|}
----

GTA01:Neo 1973

2009-02-26T13:51:24Z

Dcorking: cat sort

{{Languages|GTA01:Neo 1973}}

{{Neo1973}}

The '''Neo 1973''' (internal codename [[GTA01 revisions|GTA01]]) is the first phone designed to run Openmoko.
It is a phone that can be used with any [[GSM]] operator, and it is manufactured by '''FIC''' who instigated the Openmoko project.
This pages contains all GTA01 related topic of wiki. Press the following links, you can easily find the page you want.

Note that the Neo 1973 can not currently run the [[Om_2008.9_Update|Om 2008.9]] software (the latest release). Currently the developers are working on a major infrastructure change (debian style package management) which will enable them to port Om 2008.9 to GTA01. However, their primary focus is on getting all hardware working for the Neo Freerunner. Community contributions are welcome. It is likely it will be some months before any 2008.x release works on the 1973. In the mean time, users are encouraged to use 2008.2 or FSO.

The Openmoko developers are still actively developing for the Neo 1973.

{{Gta01}}

[[Category:Neo1973 Hardware| ]]

User:Dcorking

2007-08-24T17:04:46Z

Dcorking: /* Friday, August 24, 2007 */ no sound today!

I am David Corking.

I have a [[P1 Owners|P1]] device.

* IRC: irc.freenode.net #openmoko (nick: dcorking)

* Website: http://dcorking.com/

* Company website: http://www.corking-project.co.uk/

* Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==

===Friday, August 24, 2007===

Played (games) a bit with the new UI. Very impressive. It needs a few tweaks which I should write up in bugzilla as enhancement requests. Some nice semi-hidden features:

* Press {{aux}} to return to Today
* Press and hold {{aux}} to open Dialer
* Press and hold {{power}} to get a pop-up menu that includes not only power settings, but screenshot, and landscape orientation
* Flick scroll in Today application launcher and open applications menu. Tap and hold to stop scrolling. Scrolling is very clumsy with fingertips, but great with a stylus.
* In Dialer, press and hold '*' to get '+'

Today's tips:
* <tt>mrxvt</tt> does not open the new on screen keyboard. Instead, open Input Manager from the Applications menu, and tap the white target in the panel
* If using Terminal in [[Mac OS X]] to control the U-Boot command line, don't copy and paste: it seems to paste strange characters into the console, and causes the session to lock up.

I got the panel to crash - but I have forgotten how I did it.

I have had ''no sound'' all day today, despite several reboots. Only unusual thing was first few boots today were without a USB power source—hard to image that is the cause, especially as it is tethered to the laptop now, and still no sound. By no sound, I mean no GUI sound effects, and <tt>madplay</tt> is not working.

===Thursday, August 23, 2007===

Got Terminal.app to talk to the U-Boot console. This will be useful for setting kernel boot parameters, and also for erasing the rootfs flash partition. Wrote it up at [[Mac OS X#USB Serial with Terminal]].

===Wednesday, August 22, 2007===

Headset jack does not accept a standard 3.5 mm headset or iPod dock plug. Need to make an adapter to play podcasts or use hands-free in my car.

The battery icon is showing around 70% charged, even though it ought to be fully charged.
cat /sys/devices/platform/s3c2410-i2c/i2c-0/0-0008/battvolt
3843

UI (tap feedback) sounds come from the headset and the speaker.

Managed to cause the headset (but not the speaker) to make weird phone-related noises by using the new Dialer. Closing the dialer didn't stop it. Fiddling with the new Today app and dialer, I managed to cause X and gsmd to crash. On IRC, DPThought told me that gsmd is broken in the snapshot, but so hhf423 recommended I use ipkg.<blockquote> dcorking: if you do the ipkg update etc. with that .08 release, gsmd gets somewhat more stable, but audio switching still does not work</blockquote>Also on IRC, I read about nice screenshots of the new GUI:
* http://scap.linuxtogo.org/

Did not need to reboot to recover from the crash.
cd /etc/init.d/
./xserver-nodm start
was sufficient to restart X, the matchbox desktop and openmoko-today application.

Reproduced the [[madplay]] crash - here is the console output immediately after the crash:
root@fic-gta01:/media/card$ madplay -v 02--Symphony\ No\ 9\ in\ D\ Minor\ Op\ 125_\ Allegro\ ma\ non\ troppo--Philharmonia\ Baroque\ Orchestra-lofi.mp3
MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
Title: Symphony No 9 in D Minor Op 12
Artist: Philharmonia Baroque Orchestra
Album: Beethoven - Opferlied and Symp
Track: 2
Year: 2007
Genre: Classical
Comment: www.magnatune.com/artists/pbo
00:01:34 Layer III, 32 kbps, 22050 Hz, single channel, no CRC
3604 frames decoded (0:01:34.1), -9.4 dB peak amplitude, 0 clipped samples
root@fic-gta01:/media/card$

Turns out the problem was that the music file got truncated in transfer. There seems to be trouble writing data quickly (that is at USB 1.1 speeds) to the microSD card:
[http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 Bugzilla Bug 677 - I/O errors on heavy microSD writes]

===Tuesday, August 21, 2007===

Played a 15 minute low bit rate MP3 on microSD card through the speaker (madplay controlled via screens under ssh). It seemed to die after 3 or 4 minutes, but works ok on desktop iTunes.

Flashed to 2007.2 snapshot - this has the new finger-oriented GUI from OpenedHand:
* [http://buildhost.openmoko.org/snapshots/2007.08/images/OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2 OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2]
* [http://buildhost.openmoko.org/snapshots/2007.08/images/uImage-2.6.21.5-r3-fic-gta01.bin uImage-2.6.21.5-r3-fic-gta01.bin]

Looks great.

===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to [http://openmoko.togaware.com/survivor/TouchScreen.html#799 Graham Williams's survivor website ], I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-24T16:57:10Z

Dcorking: /* Openmoko diary (most recent first) */ todays entry

I am David Corking.

I have a [[P1 Owners|P1]] device.

* IRC: irc.freenode.net #openmoko (nick: dcorking)

* Website: http://dcorking.com/

* Company website: http://www.corking-project.co.uk/

* Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==

===Friday, August 24, 2007===

Played (games) a bit with the new UI. Very impressive. It needs a few tweaks which I should write up in bugzilla as enhancement requests. Some nice semi-hidden features:

* Press {{aux}} to return to Today
* Press and hold {{aux}} to open Dialer
* Press and hold {{power}} to get a pop-up menu that includes not only power settings, but screenshot, and landscape orientation
* Flick scroll in Today application launcher and open applications menu. Tap and hold to stop scrolling. Scrolling is very clumsy with fingertips, but great with a stylus.
* In Dialer, press and hold '*' to get '+'

Today's tips:
* <tt>mrxvt</tt> does not open the new on screen keyboard. Instead, open Input Manager from the Applications menu, and tap the white target in the panel
* If using Terminal in [[Mac OS X]] to control the U-Boot command line, don't copy and paste: it seems to paste strange characters into the console, and causes the session to lock up.

I got the panel to crash - but I have forgotten how I did it.

===Thursday, August 23, 2007===

Got Terminal.app to talk to the U-Boot console. This will be useful for setting kernel boot parameters, and also for erasing the rootfs flash partition. Wrote it up at [[Mac OS X#USB Serial with Terminal]].

===Wednesday, August 22, 2007===

Headset jack does not accept a standard 3.5 mm headset or iPod dock plug. Need to make an adapter to play podcasts or use hands-free in my car.

The battery icon is showing around 70% charged, even though it ought to be fully charged.
cat /sys/devices/platform/s3c2410-i2c/i2c-0/0-0008/battvolt
3843

UI (tap feedback) sounds come from the headset and the speaker.

Managed to cause the headset (but not the speaker) to make weird phone-related noises by using the new Dialer. Closing the dialer didn't stop it. Fiddling with the new Today app and dialer, I managed to cause X and gsmd to crash. On IRC, DPThought told me that gsmd is broken in the snapshot, but so hhf423 recommended I use ipkg.<blockquote> dcorking: if you do the ipkg update etc. with that .08 release, gsmd gets somewhat more stable, but audio switching still does not work</blockquote>Also on IRC, I read about nice screenshots of the new GUI:
* http://scap.linuxtogo.org/

Did not need to reboot to recover from the crash.
cd /etc/init.d/
./xserver-nodm start
was sufficient to restart X, the matchbox desktop and openmoko-today application.

Reproduced the [[madplay]] crash - here is the console output immediately after the crash:
root@fic-gta01:/media/card$ madplay -v 02--Symphony\ No\ 9\ in\ D\ Minor\ Op\ 125_\ Allegro\ ma\ non\ troppo--Philharmonia\ Baroque\ Orchestra-lofi.mp3
MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
Title: Symphony No 9 in D Minor Op 12
Artist: Philharmonia Baroque Orchestra
Album: Beethoven - Opferlied and Symp
Track: 2
Year: 2007
Genre: Classical
Comment: www.magnatune.com/artists/pbo
00:01:34 Layer III, 32 kbps, 22050 Hz, single channel, no CRC
3604 frames decoded (0:01:34.1), -9.4 dB peak amplitude, 0 clipped samples
root@fic-gta01:/media/card$

Turns out the problem was that the music file got truncated in transfer. There seems to be trouble writing data quickly (that is at USB 1.1 speeds) to the microSD card:
[http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 Bugzilla Bug 677 - I/O errors on heavy microSD writes]

===Tuesday, August 21, 2007===

Played a 15 minute low bit rate MP3 on microSD card through the speaker (madplay controlled via screens under ssh). It seemed to die after 3 or 4 minutes, but works ok on desktop iTunes.

Flashed to 2007.2 snapshot - this has the new finger-oriented GUI from OpenedHand:
* [http://buildhost.openmoko.org/snapshots/2007.08/images/OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2 OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2]
* [http://buildhost.openmoko.org/snapshots/2007.08/images/uImage-2.6.21.5-r3-fic-gta01.bin uImage-2.6.21.5-r3-fic-gta01.bin]

Looks great.

===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to [http://openmoko.togaware.com/survivor/TouchScreen.html#799 Graham Williams's survivor website ], I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-23T15:10:48Z

Dcorking: /* Monday, August 20, 2007 */ typo

I am David Corking.

I have a [[P1 Owners|P1]] device.

* IRC: irc.freenode.net #openmoko (nick: dcorking)

* Website: http://dcorking.com/

* Company website: http://www.corking-project.co.uk/

* Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==

===Thursday, August 23, 2007===

Got Terminal.app to talk to the U-Boot console. This will be useful for setting kernel boot parameters, and also for erasing the rootfs flash partition. Wrote it up at [[Mac OS X#USB Serial with Terminal]].

===Wednesday, August 22, 2007===

Headset jack does not accept a standard 3.5 mm headset or iPod dock plug. Need to make an adapter to play podcasts or use hands-free in my car.

The battery icon is showing around 70% charged, even though it ought to be fully charged.
cat /sys/devices/platform/s3c2410-i2c/i2c-0/0-0008/battvolt
3843

UI (tap feedback) sounds come from the headset and the speaker.

Managed to cause the headset (but not the speaker) to make weird phone-related noises by using the new Dialer. Closing the dialer didn't stop it. Fiddling with the new Today app and dialer, I managed to cause X and gsmd to crash. On IRC, DPThought told me that gsmd is broken in the snapshot, but so hhf423 recommended I use ipkg.<blockquote> dcorking: if you do the ipkg update etc. with that .08 release, gsmd gets somewhat more stable, but audio switching still does not work</blockquote>Also on IRC, I read about nice screenshots of the new GUI:
* http://scap.linuxtogo.org/

Did not need to reboot to recover from the crash.
cd /etc/init.d/
./xserver-nodm start
was sufficient to restart X, the matchbox desktop and openmoko-today application.

Reproduced the [[madplay]] crash - here is the console output immediately after the crash:
root@fic-gta01:/media/card$ madplay -v 02--Symphony\ No\ 9\ in\ D\ Minor\ Op\ 125_\ Allegro\ ma\ non\ troppo--Philharmonia\ Baroque\ Orchestra-lofi.mp3
MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
Title: Symphony No 9 in D Minor Op 12
Artist: Philharmonia Baroque Orchestra
Album: Beethoven - Opferlied and Symp
Track: 2
Year: 2007
Genre: Classical
Comment: www.magnatune.com/artists/pbo
00:01:34 Layer III, 32 kbps, 22050 Hz, single channel, no CRC
3604 frames decoded (0:01:34.1), -9.4 dB peak amplitude, 0 clipped samples
root@fic-gta01:/media/card$

Turns out the problem was that the music file got truncated in transfer. There seems to be trouble writing data quickly (that is at USB 1.1 speeds) to the microSD card:
[http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 Bugzilla Bug 677 - I/O errors on heavy microSD writes]

===Tuesday, August 21, 2007===

Played a 15 minute low bit rate MP3 on microSD card through the speaker (madplay controlled via screens under ssh). It seemed to die after 3 or 4 minutes, but works ok on desktop iTunes.

Flashed to 2007.2 snapshot - this has the new finger-oriented GUI from OpenedHand:
* [http://buildhost.openmoko.org/snapshots/2007.08/images/OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2 OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2]
* [http://buildhost.openmoko.org/snapshots/2007.08/images/uImage-2.6.21.5-r3-fic-gta01.bin uImage-2.6.21.5-r3-fic-gta01.bin]

Looks great.

===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to [http://openmoko.togaware.com/survivor/TouchScreen.html#799 Graham Williams's survivor website ], I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-23T15:08:29Z

Dcorking: /* Openmoko diary (most recent first) */ microSD fast write issue

I am David Corking.

I have a [[P1 Owners|P1]] device.

* IRC: irc.freenode.net #openmoko (nick: dcorking)

* Website: http://dcorking.com/

* Company website: http://www.corking-project.co.uk/

* Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==

===Thursday, August 23, 2007===

Got Terminal.app to talk to the U-Boot console. This will be useful for setting kernel boot parameters, and also for erasing the rootfs flash partition. Wrote it up at [[Mac OS X#USB Serial with Terminal]].

===Wednesday, August 22, 2007===

Headset jack does not accept a standard 3.5 mm headset or iPod dock plug. Need to make an adapter to play podcasts or use hands-free in my car.

The battery icon is showing around 70% charged, even though it ought to be fully charged.
cat /sys/devices/platform/s3c2410-i2c/i2c-0/0-0008/battvolt
3843

UI (tap feedback) sounds come from the headset and the speaker.

Managed to cause the headset (but not the speaker) to make weird phone-related noises by using the new Dialer. Closing the dialer didn't stop it. Fiddling with the new Today app and dialer, I managed to cause X and gsmd to crash. On IRC, DPThought told me that gsmd is broken in the snapshot, but so hhf423 recommended I use ipkg.<blockquote> dcorking: if you do the ipkg update etc. with that .08 release, gsmd gets somewhat more stable, but audio switching still does not work</blockquote>Also on IRC, I read about nice screenshots of the new GUI:
* http://scap.linuxtogo.org/

Did not need to reboot to recover from the crash.
cd /etc/init.d/
./xserver-nodm start
was sufficient to restart X, the matchbox desktop and openmoko-today application.

Reproduced the [[madplay]] crash - here is the console output immediately after the crash:
root@fic-gta01:/media/card$ madplay -v 02--Symphony\ No\ 9\ in\ D\ Minor\ Op\ 125_\ Allegro\ ma\ non\ troppo--Philharmonia\ Baroque\ Orchestra-lofi.mp3
MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
Title: Symphony No 9 in D Minor Op 12
Artist: Philharmonia Baroque Orchestra
Album: Beethoven - Opferlied and Symp
Track: 2
Year: 2007
Genre: Classical
Comment: www.magnatune.com/artists/pbo
00:01:34 Layer III, 32 kbps, 22050 Hz, single channel, no CRC
3604 frames decoded (0:01:34.1), -9.4 dB peak amplitude, 0 clipped samples
root@fic-gta01:/media/card$

Turns out the problem was that the music file got truncated in transfer. There seems to be trouble writing data quickly (that is at USB 1.1 speeds) to the microSD card:
[http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=677 Bugzilla Bug 677 - I/O errors on heavy microSD writes]

===Tuesday, August 21, 2007===

Played a 15 minute low bit rate MP3 on microSD card through the speaker (madplay controlled via screens under ssh). It seemed to die after 3 or 4 minutes, but works ok on desktop iTunes.

Flashed to 2007.2 snapshot - this has the new finger-oriented GUI from OpenedHand:
* [http://buildhost.openmoko.org/snapshots/2007.08/images/OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2 OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2]
* [http://buildhost.openmoko.org/snapshots/2007.08/images/uImage-2.6.21.5-r3-fic-gta01.bin uImage-2.6.21.5-r3-fic-gta01.bin]

Looks great.

===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to [Graham Williams's survivor website http://openmoko.togaware.com/survivor/TouchScreen.html#799], I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

Talk:Mac OS X

2007-08-23T14:49:39Z

Dcorking: refactor old questions - usbnet seems a little tricky on mac os x :)

== Comments on AJZaurus USB ==

First, thanks for all the hard work, it got my Neo happy and booting.

Some comments:
* some indication when the "refresh" button is pushed that it's doing something. (Checking, downloading, etc)
* what the status means. (F seems to mean "flashed". C means Downloaded?)
* maybe some sanity checking? (Making sure the rootfs and kernel and uBoot aren't incompatible?)

[[User:Historybuff|Historybuff]] 19:46, 4 August 2007 (CEST)

:I think that [[User:hns|hns]] addressed at least the first two features in version 0.5.3. Now the GUI shows 'Cached and Flashed'. --[[User:Dcorking|Dcorking]] 16:49, 23 August 2007 (CEST)

== Why AJZaurusUSB? ==

Q: MacOS X does work perfectly fine without AJZaurusUSB. It supports USB-Net. What do i need AJZaurusUSB for? --[[User:Deep-Thought|Deep-Thought]] 18:26, 16 August 2007 (CEST)

A: You might have deleted the Apple CDC drivers from your system. They interfere with the RNDIS/Ethernet Gadget. 17:57, 19 August 2007

==AJZaurusUSB - everchanging Ethernet interface issue==

''NOTE: it appears that after each reboot of the OpenMoko you get a new interface on the Mac (this is under investigation).''[http://wiki.openmoko.org/index.php?title=MacOS_X&diff=next&oldid=16732] I am experiencing the same behaviour. [[User:Cayco|Cayco]]

:I too have the ever-changing Ethernet interface issue. [[User:Historybuff|Historybuff]] 19:46, 4 August 2007 (CEST)

::''Each time i plug the device in, i get a new device. But traffic on the mailing list suggest this will be fixed with static mac-addresses.'' --[[User:Deep-Thought|Deep-Thought]] 18:26, 16 August 2007 (CEST)

:::Has been solved in 0.5.3 17:57, 19 August 2007

::::My usbnet has showed up first as <tt>en3</tt>, and another time as <tt>en4</tt>, but it is not ever-changing. I am using 0.5.3. No doubt there is something strange in Darwin internals, but I can live with it. --[[User:Dcorking|Dcorking]] 16:49, 23 August 2007 (CEST)

Mac OS X

2007-08-23T13:57:39Z

Dcorking: /* USB Serial with Terminal */ typo

Welcome to the OpenMoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 (and maybe other OM devices) with Mac.

= Flashing to your device =
To operate the Phase 1 devices, you need to flash a root file system first.

NOTE: you need an Intel Mac to run dfu-util since it is currently broken on big-endian machines (PowerPC).

Here is a detailled instruction:
# download the latest version of AJZaurusUSB from http://www.dsitri.de/wiki.php?page=AJZaurusUSB
# install
# run 'sudo kextload /System/Library/Extensions/AJZaurusUSB.kext' from Terminal (or reboot your Mac as described - but you do not need to configure AJZaurusUSB it before flashing the OpenMoko)
# download the latest version of OpenMoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# [V1.0 only: create a new Folder at "~/Library/Caches/OpenMoko Flasher"]
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# [V1.0 and V1.1 only: open the Console application and show the console.log]
# Now, on your OpenMoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# if it fails), unplug the OpenMoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the OpenMoko and continue configuring AJZaurusUSB

The dfu-utils tool is included in the OpenMoko Flasher application; you can access it as ''OpenMoko Flasher.app/Contents/MacOS/dfu-util'' ; alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore

= Connecting to your device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB</tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #
When you boot Linux on the smartphone, or if the smartphone powers down, Mac OS X will show a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

MacOS X does not provide such a driver for RNDIS/Ethernet Gadget. But you can use an open source (GPL) universal driver http://www.dsitri.de/wiki.php?page=AJZaurusUSB which is developed for handheld devices like iPAQ, Sharp Zaurus, and Motorola A760. Download it and install according to manual found inside of the package.

After reboot, you should have a new Ethernet interface in your System Preferences/Network. Set up the network manually for that interface by using these addresses:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200
Subnet: 255.255.255.0
Router: 192.168.0.202
</pre>
This might conflict with some WLAN routers which also use the 192.168.0.0 network.

You should be able to connect to your Neo! Try using ping 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.

NOTE: the software is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

== Telnet, ssh, SMB ==

To Be Done.

=== ssh ===

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection and for a password on each other. This is "root" unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the OpenMoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== Bluetooth ==

To Be Done. See also: [[Bluetooth_Support#PPP_Networking]].

== WiFi ==

To Be Done.

= Synchronizing =

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the OpenMoko through Terminal/ssh.

= Sharing connection =

== Mac as a server ==

Here is described how to enable your Mac to serve as a internet router for your OpenMoko device.

=== Bluetooth ===

This could help:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking

http://www.macosxhints.com/article.php?story=20051220221237711

=== USB ===

If you install AJZaurusUSB driver you should be able to set up your Mac as a router (not tested).

== Neo1973 as a server ==

To Be Done.

= Developing software =

== Using virtualization software==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

== Natively ==

There are some efforts to get through process of compiling OE and OpenMoko under mac: [[OpenMoko_under_QEMU_on_MacOSX]]

[[Category:Developer software]]

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword OpenMoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

Mac OS X

2007-08-23T13:54:22Z

Dcorking: /* USB Serial */ change Darwin Ports to MacPorts (darwinports site is decommissioned) added section for Terminal.app

Welcome to the OpenMoko page devoted to MacOS X users!

Here you can find notes of using Neo1973 (and maybe other OM devices) with Mac.

= Flashing to your device =
To operate the Phase 1 devices, you need to flash a root file system first.

NOTE: you need an Intel Mac to run dfu-util since it is currently broken on big-endian machines (PowerPC).

Here is a detailled instruction:
# download the latest version of AJZaurusUSB from http://www.dsitri.de/wiki.php?page=AJZaurusUSB
# install
# run 'sudo kextload /System/Library/Extensions/AJZaurusUSB.kext' from Terminal (or reboot your Mac as described - but you do not need to configure AJZaurusUSB it before flashing the OpenMoko)
# download the latest version of OpenMoko Flasher from http://www.dsitri.de/wiki.php?page=OpenMoko%20Flasher
# [V1.0 only: create a new Folder at "~/Library/Caches/OpenMoko Flasher"]
# press the Refresh button (which loads the list of packages on the server)
# select and load the rootfs (takes some minutes for approx. 40 MByte)
# [V1.0 and V1.1 only: open the Console application and show the console.log]
# Now, on your OpenMoko, hold the AUX button while pressing the Power button for 5 seconds
# the BOOT menu should appear
# connect the USB cable
# Press the Flash button
# the BOOT menu screen on the OM should show an indication that it has been switched to DFU mode
# if it fails), unplug the OpenMoko shortly and replug and try again (experience shows that it is needed up to three times)
# if it successfully flashed, you should be able to boot the OpenMoko and continue configuring AJZaurusUSB

The dfu-utils tool is included in the OpenMoko Flasher application; you can access it as ''OpenMoko Flasher.app/Contents/MacOS/dfu-util'' ; alternatively, you can compile dfu-util manually as described at http://wiki.openmoko.org/wiki/User:SNMoore

= Connecting to your device =

== USB Serial ==

It is possible to access the U-Boot [[Bootloader]] serial console from a Mac. You can use the Terminal application on Mac OS X, or <tt>minicom</tt> from [http://finkproject.org/ Fink] or [http://www.macports.org/ MacPorts] (formerly Darwin Ports.)

The USB driver creates cu and tty character devices, for example
$ ls -la /dev/tty.usb*
crw-rw-rw- 1 root wheel 10, 18 Aug 23 14:10 /dev/tty.usbmodem00000001
$ ls -la /dev/cu.usb*
crw-rw-rw- 1 root wheel 10, 19 Aug 23 14:10 /dev/cu.usbmodem00000001

=== USB Serial with minicom ===

The <tt>minicom</tt> program from the [http://www.macports.org/ MacPorts] collection can be used to access the USB serial port <tt>/dev/cu.usbmodem00000001</tt> (numbering may vary.)

First install the program (assuming you already have MacPorts installed):

sudo port install minicom

Then launch it in configuration mode (the -s flag):

sudo minicom -s

Under "Serial Port Setup", set the Device to "/dev/cu.usbmodem00000001" and set Bps to "115200 8N1". Under "Modem and Dialing", enter empty strings for "Init string", "Reset string", and "Hang-up string". Save the setup as default ("dfl") then Exit.

You should now be able to access the bootloader console. You should exit from Minicom before disconnecting the smartphone, or else you will get an error about unplugging a USB device while it is in use.

=== USB Serial with Terminal ===

The built in Mac Terminal application <tt>Terminal.app</tt> can be used to access the USB serial port <tt>/dev/tty.usbmodem00000001</tt> (numbering may vary.)

An easy way to do this is to configure the terminal with Script Editor, as described in the short article, [http://www.macosxhints.com/article.php?story=20061109133825654 ''Use 'screen' as a serial terminal emulator''](macosxhints.com). Then,

# Press and hold {{aux}} and then press and hold {{power}} for 5 seconds
# Press {{aux}} to select <tt>Set console to USB<tt> in the U-Boot menu, and {{power}} to execute it
# Start the serial terminal application. You should see a U-Boot command line prompt, such as
In: usbtty
Out: usbtty
Err: usbtty
DEVICE_CONFIGURED: 1
Enabling automatic fast charge
GTA01Bv4 #

When you boot Linux on the smartphone, or if the smartphone powers down, you will get a USB Device Unplug Notice, "The USB device has been unplugged while an application was still active. This can result in loss of data." This error is probably harmless.

== USB Networking ==

You can telnet, SSH, SMB or do whatever you want if you install software that enables you to set up TCP/IP network over your USB connection.

MacOS X does not provide such a driver for RNDIS/Ethernet Gadget. But you can use an open source (GPL) universal driver http://www.dsitri.de/wiki.php?page=AJZaurusUSB which is developed for handheld devices like iPAQ, Sharp Zaurus, and Motorola A760. Download it and install according to manual found inside of the package.

After reboot, you should have a new Ethernet interface in your System Preferences/Network. Set up the network manually for that interface by using these addresses:
<pre>
IP-V4: manual
IP-Addr: 192.168.0.200
Subnet: 255.255.255.0
Router: 192.168.0.202
</pre>
This might conflict with some WLAN routers which also use the 192.168.0.0 network.

You should be able to connect to your Neo! Try using ping 192.168.0.202 and the roundtrip time should be between 1 and 2 ms.

NOTE: the software is sometimes a bit flaky, and a reboot of the Mac seems to bring it back. It is especially critical about hot unplugging the OM and sleep modes of MacBooks. This may even result in a Kernel Panic.

== Telnet, ssh, SMB ==

To Be Done.

=== ssh ===

After making the USB connection work, start ssh:

ssh -l root 192.168.0.202

If you don't have installed the key, it will ask for a "yes" on the first connection and for a password on each other. This is "root" unless you change it.

MacBook-hns:~ hns$ ssh -l root 192.168.0.202
root@192.168.0.202's password:
root@fic-gta01:~$ hostname
fic-gta01
root@fic-gta01:~$

NOTE: the ssh daemon (dropbear 0.49) on the OpenMoko appears to have a bug when sending the exit status back to the client. From time to time you receive an exit status of 255.

== Bluetooth ==

To Be Done. See also: [[Bluetooth_Support#PPP_Networking]].

== WiFi ==

To Be Done.

= Synchronizing =

This is not done yet. Possible solutions are SyncML or ZMacSync http://www.dsitri.de/wiki.php?page=ZMacSync

ZMacSync does not yet synchronize but allows more easy access to the OpenMoko through Terminal/ssh.

= Sharing connection =

== Mac as a server ==

Here is described how to enable your Mac to serve as a internet router for your OpenMoko device.

=== Bluetooth ===

This could help:

http://wiki.openmoko.org/wiki/Bluetooth_Support#Networking

http://www.macosxhints.com/article.php?story=20051220221237711

=== USB ===

If you install AJZaurusUSB driver you should be able to set up your Mac as a router (not tested).

== Neo1973 as a server ==

To Be Done.

= Developing software =

== Using virtualization software==

You can use Parallels or VMWare to install your favourite Linux distribution and then develop just as on Linux.

There are some drawback since AFAIK dfu-util may not work correctly in such environments.

== Natively ==

There are some efforts to get through process of compiling OE and OpenMoko under mac: [[OpenMoko_under_QEMU_on_MacOSX]]

[[Category:Developer software]]

= Other Resources =

== Search Software Repositories ==

[[http://www.versiontracker.com/php/qs.php?action=search&str=openmoko&srchArea=macosx Keyword OpenMoko]] at VersionTracker

== Discussion Fora ==

[[http://www.oesf.org/forums/index.php?showforum=63 Mac Issues Forum]] at Open Embedded Software Foundation (was Zaurus User Group)

Template:Power

2007-08-23T13:41:02Z

Dcorking: Template:POWER moved to Template:Power: easier to type {{power}} in running text

<small-caps>POWER</small-caps>

Template:Power

2007-08-23T13:38:48Z

Dcorking: Template for the hardware POWER button

<small-caps>POWER</small-caps>

Neo1973 compatible cellphone providers

2007-08-22T14:03:02Z

Dcorking: /* United Kingdom */ 3 rumour

{|align=right
|__TOC__
|}
The Neo1973 uses quad-band [[GSM]] (850/900/1800/1900 MHz) so any GSM provider in the world should be compatible. In general, when you are looking for a mobile solution in your region, you would need to be aware of:
* the ''network coverage'' of available providers
* different ''tariffs'' of these providers
and choose the one that is right for you. If you haven't had any experience with GSM coverage in your area, you may want to inquire locally from the available providers and people you know that may already have experienced GSM at your location. You may also want to subscribe to our mailing list. If you have doubts about the coverage for your area, you may want to borrow a GSM phone or buy an inexpensive one so that you can get a feel for how the Neo1973 will work in your area. You can help keep your cost down by using a prepaid card for your testing.

Here is some information on Prepaid GSM cards:
* [http://www.prepaidgsm.net/ PrePaidGSM - worldwide overview about GSM prepaid offers]
Think twice before choosing a tariff with long duration contracts (more than 12 months), because prices for the GPRS data tariffs are ''likely'' to lower in many countries. Also, long duration contracts are mostly combined with hardware (ie: free or steeply discounted phone with a 24 or 36 month contract). It will be worth your while to shop around for competing offers from the different providers in your area.

We chose the GSM network format for the Neo1973 because GSM is in use by more countries than any other mobile phone standard. As a result, you will have better coverage with the Neo1973, and we felt that it was the best choice for our OpenMoko devices. When the Neo1973 is successful, and we believe that it will be, we will be developing new devices that we will be bringing to market. They will be running OpenMoko and supporting additional mobile phone network standards as well. So if GSM is not available in your area (ie: some areas in the USA), OpenMoko will be bringing other options to market in the future.

Below is a list of Neo1973-compatible providers around the world. Please help by filling this out ''alphabetically'':

There is also a [[Carriers]] page that should be merged with this section.

==Argentina==
* [http://www.movistar.com.ar/ Movistar]
* [http://www.personal.com.ar/ Personal]
* [http://www.cti.com.ar/ CTI]

== Belgium ==
* [http://www.proximus.be/ Proximus]
* [http://www.base.be/ Base]
* [http://www.mobistar.be/LanguageIndex.html Mobistar]

== Canada ==
* [http://www.fido.ca/ Fido]
* [http://www.icewireless.ca/ IceWireless]
* [http://www.rogers.ca/ Rogers]

== China ==
* China Mobile
* China Unicom (CHINA UNICOM GSM)

== Czech Republic ==

* [http://www.vodafone.cz/ Vodafone]
* [http://www.cz.o2.com/ o2]
* [http://www.t-mobile.cz/ T-mobile]

== Denmark ==
* Sonofon ([http://www.sonofon.dk/english/index.shtml English] - [http://www.sonofon.dk/ Danish])
* TDC A/S ([http://tdc.com English] - [http://privat.tdc.dk/mobil/ Danish])
* Telia DK ([http://telia.dk/privat/produkter/mobil/ Danish])

== Estonia ==

* [http://www.emt.ee/ EMT]
* [http://www.tele2.ee/ Tele2] - Very low rates for GPRS. You can get 3GB of bandwidth for 675EEK(~43€) per month.
* [http://www.elisa.ee/ Elisa] - With M-internet plan you get free access to Elisa wifi hotspots

== Finland ==

* [http://www.cubio.fi Cubio]
* [http://www.dnafinland.fi Dna] - Also a roaming network operator (Network operated under the name Dna Networks Ltd)
* [http://www.elisa.fi Elisa] - Also a roaming network operator.
* [http://www.go.fi Go mobile]
* [http://www.hesburger.fi/heseliittyma/ Hesburger] - Do you want sim card(s) with that?
* [http://www.kolumbus.fi Kolumbus] - Strangely they don't offer their website in English, but they're a part of the Elisa.
* [http://www.teliasonera.com Teliasonera] - Also a roaming network operator.
* [http://www.tele.fi Telefinland] - They haven't got an English site, but they're part of the Teliasonera.
* [http://www.gsm.aland.fi/ Ålands Mobiltelefon] - Only in the Åland Islands in the southwestern Finland. Also a roaming network operator.

== France ==

All:
* [http://www.sfr.fr SFR]
* [http://www.bouyguestelecom.fr/ Bouygues]
* [http://www.orange.fr Orange]

== Germany ==
All:
* [http://www.vodafone.de/ Vodafone]
* [http://www.o2online.de/ o2]
* [http://www.eplus.de/ E-Plus]
* [http://www.t-mobile.de/ T-mobile]
== India ==
All GSM:
* [http://www.airtel.in/ Airtel]
* Vodafone
* [http://www.ideacellular.com/ Idea]
* Reliance GSM
* BPL Mobile
* Spice
* [http://www.bsnl.co.in/ BSNL]
* [http://www.hutch.in/ Hutch]

== Japan ==

According to the [http://www.gsmworld.com/roaming/gsminfo/cou_jp.shtml GSM-Association] there is no GSM in Japan, except for UMTS.

== Latvia ==
* [http://www.lmt.lv/ LMT]
* [http://www.bite.lv/ Bitė]
* [http://www.tele2.lv/ Tele2]

== Lithuania ==
* [http://www.omnitel.lt/ Omnitel]
* [http://www.bite.lt/ Bitė]
* [http://www.tele2.lt/ Tele2]

== Netherlands ==
All.
* [http://www.vodafone.nl/ Vodafone]
* [http://www.telfort.nl/ Telfort]
* [http://www.orange.nl/ Orange]
* [http://www.t-mobile.nl/ T-mobile]
* [http://www.kpn.com/mobiel KPN]
* [http://www.hi.nl/ Hi]
(There are more)

For a breakdown of SIM-only plans, go to [http://www.bellen.com/mobiel_overzicht/default.asp?taal=nl&land=nl&prgr=4 Bellen.com]

== New Zealand ==
* [http://www.vodafone.co.nz/ Vodafone]

== Norway ==
* [http://www.netcom.no/ NetCom] (GSM900/1800 & UMTS)
* [http://www.networknorway.no/ Network Norway] (GSM900)
* [http://www.telenormobil.no/ Telenor] (GSM900/1800 & UMTS)

== Poland ==

* [http://www.eragsm.pl/ Era]
* [http://www.plusgsm.pl/ Plus]
* [http://www.orange.pl/ Orange] - europe wide provider
* [http://www.playmobile.pl/ Play]

== Romania ==

* [http://www.vodafone.ro Vodafone] (226-01; GSM900)
* [http://www.orange.ro Orange] (226-10; GSM900)
* [http://www.cosmote.com Cosmote] (226-06; GSM1800)

* [http://www.zapp.ro/ Zapp] is running CDMA (Qualcomm style) and as such it is incompatible with [[Neo1973]].

== Russia ==
=== global ===
* [http://www.beeline.ru/ Билайн]/BeeLine (GSM900/1800)
* [http://megafon.ru/ МегаФон]/MegaFon (GSM900/1800)
* [http://www.mts.ru МТС]/MTS (GSM900/1800)
=== regional ===
* [http://www.smarts.ru/ СМАРТС]/SMARTS (GSM900/1800)
* [http://www.tele2.ru TELE2] (GSM900/1800)
* [http://www.u-tel.ru/ Ютел]/Utel (GSM900/1800)
* [http://www2.sibirtelecom.ru/857 Сибирьтелеком]/Sibirtelecom (GSM-900/1800)
* [http://www.ncc.nnov.ru/ НСС]/NSS (GSM900/1800)
* [http://www.bwc.ru/ Байкалвестком]/Baykalvestcom (GSM900/1800)

== Slovak Republic ==
All:
* [http://www.orange.sk/ Orange]
* [http://www.sk.o2.com/ o2]
* [http://www.t-mobile.sk/ T-mobile]

== South Africa ==

* [http://www.vodacom.co.za/ Vodacom]
* [http://www.mtn.co.za/ MTN]
* [http://www.cellc.co.za/ Cell C]

== Spain ==

* [http://www.vodafone.es/ Vodafone]
* [http://www.movistar.es/ Movistar]

== Sweden ==

Operators with their own physical networks:
* [http://comviq.se/ Comviq/Tele2]
* [http://www.telia.se/ Telia]
* [http://www.tre.se/ 3]
* [http://www.telenor.se Telenor]

Virtual Operators:
* [http://www.tangomini.se TangoMini]
* [http://www.halebop.se Halebop]
* [http://www.djuice.se Djuice]

== Switzerland ==
(all)
* [http://www.swisscom-mobile.ch/ Swisscom Mobile]
* [http://www.sunrise.ch/ Sunrise]
* [http://www.orange.ch/ Orange]

== Taiwan ==

* Chunghwa Telecom
* Far EasTone Telecommunications Co Ltd
* KG Telecom
* MobiTai
* Taiwan Mobile Co.Ltd

== Ukraine ==
* [http://www.umc.ua/ UMC] (including virtual [http://www.jeans.com.ua/ Jeans], [http://www.ekotel.com.ua/ Ecotel])
* [http://www.kyivstar.net/ Kyivstar] (including virtual [http://www.djuice.com.ua/ DJUICE], [http://mobilych.com.ua/ Mobilych])
* [http://www.life.com.ua/ life:)]
* [http://www.beeline.ua/ Beeline]
* [http://gsm.goldentele.com/ Golden Telecom]
* [http://www.privatmobile.com.ua/ PrivatMobile]

== United Kingdom ==
* [http://www.vodafone.co.uk/ Vodafone]
* [http://www.o2.co.uk/ O2]
* [http://www.orange.co.uk/ Orange]
* [http://www.t-mobile.co.uk/ T-mobile]
* [http://www.three.co.uk/ 3] ''There is a rumour that 3 use technology that blocks detect phones that are not capable of 3G from their 2G network. If this rumour is true, then 3 would not really be compatible with the GSM-only Neo1973

== United States ==

* [[Carriers/ATT|AT&T]] - (Was Cingular)
* [[Carriers/CellularOne|Cellular One/Dobson Cellular]] - Their Prepaid Cellular page says it works with any GSM phone. However according to Wikipedia [http://en.wikipedia.org/wiki/Dobson_Cellular] they are possibly being acquired by AT&T, so it's unknown whether they will stay GSM or not.
* [[Carriers/TMobile|T-Mobile]]
* Other (more local) GSM-network providers can be found at [http://www.gsmworld.com/roaming/gsminfo/cou_us.shtml GSMworld.com]
* [http://www.unicel.com/ UNICEL] - Has just been purchased by Verizon Wireless (Aug/1/07), they are planning on take down their GSM Network except to support roaming GSM customers. GSM customers will be transition to CDMA. :(
* Wikipedia has a list of providers and technologies [http://en.wikipedia.org/wiki/List_of_United_States_mobile_phone_companies here]. Only GSM networks are compatible with the Neo1973.
* [http://www.prepaidgsm.net/en/usa.html PrepaidGSM.net information about GSM prepaid cards in the USA]

== Uruguay ==

* [http://www.ancel.com.uy/ Ancel] -

== Venezuela ==

* [http://www.digitel.com.ve/ Digitel] - This works on the 900Mhz band.
* [http://www.movistar.com.ve/ Movistar] - Previously named Telcel. It is moving from CDMA to GSM, but currently all its new phones are GSM. They work on the 850 Mhz band.

== Rest of World (Africa, Asia, Australia, Europe, South America) ==

* almost all use GSM thus they are compatible

(More info available at: [http://www.gsmworld.com/roaming/gsminfo/index.shtml GSMworld.com])
{{Languages|Neo1973_compatible_cellphone_providers}}

[[Category:Information]]

Neo1973 compatible cellphone providers

2007-08-22T14:01:40Z

Dcorking: /* United Kingdom */ rumour about 3 blocking 2G only phones

{|align=right
|__TOC__
|}
The Neo1973 uses quad-band [[GSM]] (850/900/1800/1900 MHz) so any GSM provider in the world should be compatible. In general, when you are looking for a mobile solution in your region, you would need to be aware of:
* the ''network coverage'' of available providers
* different ''tariffs'' of these providers
and choose the one that is right for you. If you haven't had any experience with GSM coverage in your area, you may want to inquire locally from the available providers and people you know that may already have experienced GSM at your location. You may also want to subscribe to our mailing list. If you have doubts about the coverage for your area, you may want to borrow a GSM phone or buy an inexpensive one so that you can get a feel for how the Neo1973 will work in your area. You can help keep your cost down by using a prepaid card for your testing.

Here is some information on Prepaid GSM cards:
* [http://www.prepaidgsm.net/ PrePaidGSM - worldwide overview about GSM prepaid offers]
Think twice before choosing a tariff with long duration contracts (more than 12 months), because prices for the GPRS data tariffs are ''likely'' to lower in many countries. Also, long duration contracts are mostly combined with hardware (ie: free or steeply discounted phone with a 24 or 36 month contract). It will be worth your while to shop around for competing offers from the different providers in your area.

We chose the GSM network format for the Neo1973 because GSM is in use by more countries than any other mobile phone standard. As a result, you will have better coverage with the Neo1973, and we felt that it was the best choice for our OpenMoko devices. When the Neo1973 is successful, and we believe that it will be, we will be developing new devices that we will be bringing to market. They will be running OpenMoko and supporting additional mobile phone network standards as well. So if GSM is not available in your area (ie: some areas in the USA), OpenMoko will be bringing other options to market in the future.

Below is a list of Neo1973-compatible providers around the world. Please help by filling this out ''alphabetically'':

There is also a [[Carriers]] page that should be merged with this section.

==Argentina==
* [http://www.movistar.com.ar/ Movistar]
* [http://www.personal.com.ar/ Personal]
* [http://www.cti.com.ar/ CTI]

== Belgium ==
* [http://www.proximus.be/ Proximus]
* [http://www.base.be/ Base]
* [http://www.mobistar.be/LanguageIndex.html Mobistar]

== Canada ==
* [http://www.fido.ca/ Fido]
* [http://www.icewireless.ca/ IceWireless]
* [http://www.rogers.ca/ Rogers]

== China ==
* China Mobile
* China Unicom (CHINA UNICOM GSM)

== Czech Republic ==

* [http://www.vodafone.cz/ Vodafone]
* [http://www.cz.o2.com/ o2]
* [http://www.t-mobile.cz/ T-mobile]

== Denmark ==
* Sonofon ([http://www.sonofon.dk/english/index.shtml English] - [http://www.sonofon.dk/ Danish])
* TDC A/S ([http://tdc.com English] - [http://privat.tdc.dk/mobil/ Danish])
* Telia DK ([http://telia.dk/privat/produkter/mobil/ Danish])

== Estonia ==

* [http://www.emt.ee/ EMT]
* [http://www.tele2.ee/ Tele2] - Very low rates for GPRS. You can get 3GB of bandwidth for 675EEK(~43€) per month.
* [http://www.elisa.ee/ Elisa] - With M-internet plan you get free access to Elisa wifi hotspots

== Finland ==

* [http://www.cubio.fi Cubio]
* [http://www.dnafinland.fi Dna] - Also a roaming network operator (Network operated under the name Dna Networks Ltd)
* [http://www.elisa.fi Elisa] - Also a roaming network operator.
* [http://www.go.fi Go mobile]
* [http://www.hesburger.fi/heseliittyma/ Hesburger] - Do you want sim card(s) with that?
* [http://www.kolumbus.fi Kolumbus] - Strangely they don't offer their website in English, but they're a part of the Elisa.
* [http://www.teliasonera.com Teliasonera] - Also a roaming network operator.
* [http://www.tele.fi Telefinland] - They haven't got an English site, but they're part of the Teliasonera.
* [http://www.gsm.aland.fi/ Ålands Mobiltelefon] - Only in the Åland Islands in the southwestern Finland. Also a roaming network operator.

== France ==

All:
* [http://www.sfr.fr SFR]
* [http://www.bouyguestelecom.fr/ Bouygues]
* [http://www.orange.fr Orange]

== Germany ==
All:
* [http://www.vodafone.de/ Vodafone]
* [http://www.o2online.de/ o2]
* [http://www.eplus.de/ E-Plus]
* [http://www.t-mobile.de/ T-mobile]
== India ==
All GSM:
* [http://www.airtel.in/ Airtel]
* Vodafone
* [http://www.ideacellular.com/ Idea]
* Reliance GSM
* BPL Mobile
* Spice
* [http://www.bsnl.co.in/ BSNL]
* [http://www.hutch.in/ Hutch]

== Japan ==

According to the [http://www.gsmworld.com/roaming/gsminfo/cou_jp.shtml GSM-Association] there is no GSM in Japan, except for UMTS.

== Latvia ==
* [http://www.lmt.lv/ LMT]
* [http://www.bite.lv/ Bitė]
* [http://www.tele2.lv/ Tele2]

== Lithuania ==
* [http://www.omnitel.lt/ Omnitel]
* [http://www.bite.lt/ Bitė]
* [http://www.tele2.lt/ Tele2]

== Netherlands ==
All.
* [http://www.vodafone.nl/ Vodafone]
* [http://www.telfort.nl/ Telfort]
* [http://www.orange.nl/ Orange]
* [http://www.t-mobile.nl/ T-mobile]
* [http://www.kpn.com/mobiel KPN]
* [http://www.hi.nl/ Hi]
(There are more)

For a breakdown of SIM-only plans, go to [http://www.bellen.com/mobiel_overzicht/default.asp?taal=nl&land=nl&prgr=4 Bellen.com]

== New Zealand ==
* [http://www.vodafone.co.nz/ Vodafone]

== Norway ==
* [http://www.netcom.no/ NetCom] (GSM900/1800 & UMTS)
* [http://www.networknorway.no/ Network Norway] (GSM900)
* [http://www.telenormobil.no/ Telenor] (GSM900/1800 & UMTS)

== Poland ==

* [http://www.eragsm.pl/ Era]
* [http://www.plusgsm.pl/ Plus]
* [http://www.orange.pl/ Orange] - europe wide provider
* [http://www.playmobile.pl/ Play]

== Romania ==

* [http://www.vodafone.ro Vodafone] (226-01; GSM900)
* [http://www.orange.ro Orange] (226-10; GSM900)
* [http://www.cosmote.com Cosmote] (226-06; GSM1800)

* [http://www.zapp.ro/ Zapp] is running CDMA (Qualcomm style) and as such it is incompatible with [[Neo1973]].

== Russia ==
=== global ===
* [http://www.beeline.ru/ Билайн]/BeeLine (GSM900/1800)
* [http://megafon.ru/ МегаФон]/MegaFon (GSM900/1800)
* [http://www.mts.ru МТС]/MTS (GSM900/1800)
=== regional ===
* [http://www.smarts.ru/ СМАРТС]/SMARTS (GSM900/1800)
* [http://www.tele2.ru TELE2] (GSM900/1800)
* [http://www.u-tel.ru/ Ютел]/Utel (GSM900/1800)
* [http://www2.sibirtelecom.ru/857 Сибирьтелеком]/Sibirtelecom (GSM-900/1800)
* [http://www.ncc.nnov.ru/ НСС]/NSS (GSM900/1800)
* [http://www.bwc.ru/ Байкалвестком]/Baykalvestcom (GSM900/1800)

== Slovak Republic ==
All:
* [http://www.orange.sk/ Orange]
* [http://www.sk.o2.com/ o2]
* [http://www.t-mobile.sk/ T-mobile]

== South Africa ==

* [http://www.vodacom.co.za/ Vodacom]
* [http://www.mtn.co.za/ MTN]
* [http://www.cellc.co.za/ Cell C]

== Spain ==

* [http://www.vodafone.es/ Vodafone]
* [http://www.movistar.es/ Movistar]

== Sweden ==

Operators with their own physical networks:
* [http://comviq.se/ Comviq/Tele2]
* [http://www.telia.se/ Telia]
* [http://www.tre.se/ 3]
* [http://www.telenor.se Telenor]

Virtual Operators:
* [http://www.tangomini.se TangoMini]
* [http://www.halebop.se Halebop]
* [http://www.djuice.se Djuice]

== Switzerland ==
(all)
* [http://www.swisscom-mobile.ch/ Swisscom Mobile]
* [http://www.sunrise.ch/ Sunrise]
* [http://www.orange.ch/ Orange]

== Taiwan ==

* Chunghwa Telecom
* Far EasTone Telecommunications Co Ltd
* KG Telecom
* MobiTai
* Taiwan Mobile Co.Ltd

== Ukraine ==
* [http://www.umc.ua/ UMC] (including virtual [http://www.jeans.com.ua/ Jeans], [http://www.ekotel.com.ua/ Ecotel])
* [http://www.kyivstar.net/ Kyivstar] (including virtual [http://www.djuice.com.ua/ DJUICE], [http://mobilych.com.ua/ Mobilych])
* [http://www.life.com.ua/ life:)]
* [http://www.beeline.ua/ Beeline]
* [http://gsm.goldentele.com/ Golden Telecom]
* [http://www.privatmobile.com.ua/ PrivatMobile]

== United Kingdom ==
* [http://www.vodafone.co.uk/ Vodafone]
* [http://www.o2.co.uk/ O2]
* [http://www.orange.co.uk/ Orange]
* [http://www.t-mobile.co.uk/ T-mobile]
* [http://www.three.co.uk/ 3] ''There is a rumour that 3 use technology that detect that a phone is not capable of 3G, and to block it from their network, to save on 2G access costs that they pay to another operator. If this rumour is true, then 3 would not really be compatible with the GSM-only Neo1973

== United States ==

* [[Carriers/ATT|AT&T]] - (Was Cingular)
* [[Carriers/CellularOne|Cellular One/Dobson Cellular]] - Their Prepaid Cellular page says it works with any GSM phone. However according to Wikipedia [http://en.wikipedia.org/wiki/Dobson_Cellular] they are possibly being acquired by AT&T, so it's unknown whether they will stay GSM or not.
* [[Carriers/TMobile|T-Mobile]]
* Other (more local) GSM-network providers can be found at [http://www.gsmworld.com/roaming/gsminfo/cou_us.shtml GSMworld.com]
* [http://www.unicel.com/ UNICEL] - Has just been purchased by Verizon Wireless (Aug/1/07), they are planning on take down their GSM Network except to support roaming GSM customers. GSM customers will be transition to CDMA. :(
* Wikipedia has a list of providers and technologies [http://en.wikipedia.org/wiki/List_of_United_States_mobile_phone_companies here]. Only GSM networks are compatible with the Neo1973.
* [http://www.prepaidgsm.net/en/usa.html PrepaidGSM.net information about GSM prepaid cards in the USA]

== Uruguay ==

* [http://www.ancel.com.uy/ Ancel] -

== Venezuela ==

* [http://www.digitel.com.ve/ Digitel] - This works on the 900Mhz band.
* [http://www.movistar.com.ve/ Movistar] - Previously named Telcel. It is moving from CDMA to GSM, but currently all its new phones are GSM. They work on the 850 Mhz band.

== Rest of World (Africa, Asia, Australia, Europe, South America) ==

* almost all use GSM thus they are compatible

(More info available at: [http://www.gsmworld.com/roaming/gsminfo/index.shtml GSMworld.com])
{{Languages|Neo1973_compatible_cellphone_providers}}

[[Category:Information]]

User:Dcorking

2007-08-22T13:55:01Z

Dcorking: /* Wednesday, August 22, 2007 */ /etc/init.d/xserver-nodm start

I am David Corking.

I have a [[P1 Owners|P1]] device.

* IRC: irc.freenode.net #openmoko (nick: dcorking)

* Website: http://dcorking.com/

* Company website: http://www.corking-project.co.uk/

* Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==

===Wednesday, August 22, 2007===

Headset jack does not accept a standard 3.5 mm headset or iPod dock plug. Need to make an adapter to play podcasts or use hands-free in my car.

The battery icon is showing around 70% charged, even though it ought to be fully charged.
cat /sys/devices/platform/s3c2410-i2c/i2c-0/0-0008/battvolt
3843

UI (tap feedback) sounds come from the headset and the speaker.

Managed to cause the headset (but not the speaker) to make weird phone-related noises by using the new Dialer. Closing the dialer didn't stop it. Fiddling with the new Today app and dialer, I managed to cause X and gsmd to crash. On IRC, DPThought told me that gsmd is broken in the snapshot, but so hhf423 recommended I use ipkg.<blockquote> dcorking: if you do the ipkg update etc. with that .08 release, gsmd gets somewhat more stable, but audio switching still does not work</blockquote>Also on IRC, I read about nice screenshots of the new GUI:
* http://scap.linuxtogo.org/

Did not need to reboot to recover from the crash.
cd /etc/init.d/
./xserver-nodm start
was sufficient to restart X, the matchbox desktop and openmoko-today application.

Reproduced the [[madplay]] crash - here is the console output immediately after the crash:
root@fic-gta01:/media/card$ madplay -v 02--Symphony\ No\ 9\ in\ D\ Minor\ Op\ 125_\ Allegro\ ma\ non\ troppo--Philharmonia\ Baroque\ Orchestra-lofi.mp3
MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
Title: Symphony No 9 in D Minor Op 12
Artist: Philharmonia Baroque Orchestra
Album: Beethoven - Opferlied and Symp
Track: 2
Year: 2007
Genre: Classical
Comment: www.magnatune.com/artists/pbo
00:01:34 Layer III, 32 kbps, 22050 Hz, single channel, no CRC
3604 frames decoded (0:01:34.1), -9.4 dB peak amplitude, 0 clipped samples
root@fic-gta01:/media/card$

===Tuesday, August 21, 2007===

Played a 15 minute low bit rate MP3 on microSD card through the speaker (madplay controlled via screens under ssh). It seemed to die after 3 or 4 minutes, but works ok on desktop iTunes.

Flashed to 2007.2 snapshot - this has the new finger-oriented GUI from OpenedHand:
* [http://buildhost.openmoko.org/snapshots/2007.08/images/OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2 OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2]
* [http://buildhost.openmoko.org/snapshots/2007.08/images/uImage-2.6.21.5-r3-fic-gta01.bin uImage-2.6.21.5-r3-fic-gta01.bin]

Looks great.

===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to [Graham Williams's survivor website http://openmoko.togaware.com/survivor/TouchScreen.html#799], I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-22T13:47:14Z

Dcorking: /* Wednesday, August 22, 2007 */ madplay crash

I am David Corking.

I have a [[P1 Owners|P1]] device.

* IRC: irc.freenode.net #openmoko (nick: dcorking)

* Website: http://dcorking.com/

* Company website: http://www.corking-project.co.uk/

* Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==

===Wednesday, August 22, 2007===

Headset jack does not accept a standard 3.5 mm headset or iPod dock plug. Need to make an adapter to play podcasts or use hands-free in my car.

The battery icon is showing around 70% charged, even though it ought to be fully charged.
cat /sys/devices/platform/s3c2410-i2c/i2c-0/0-0008/battvolt
3843

UI (tap feedback) sounds come from the headset and the speaker.

Managed to cause the headset (but not the speaker) to make weird phone-related noises by using the new Dialer. Closing the dialer didn't stop it. Fiddling with the new Today app and dialer, I managed to cause X and gsmd to crash. On IRC, DPThought told me that gsmd is broken in the snapshot, but so hhf423 recommended I use ipkg.<blockquote> dcorking: if you do the ipkg update etc. with that .08 release, gsmd gets somewhat more stable, but audio switching still does not work</blockquote>Also on IRC, I read about nice screenshots of the new GUI:
* http://scap.linuxtogo.org/

Reproduced the [[madplay]] crash - here is the console output immediately after the crash:
root@fic-gta01:/media/card$ madplay -v 02--Symphony\ No\ 9\ in\ D\ Minor\ Op\ 125_\ Allegro\ ma\ non\ troppo--Philharmonia\ Baroque\ Orchestra-lofi.mp3
MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
Title: Symphony No 9 in D Minor Op 12
Artist: Philharmonia Baroque Orchestra
Album: Beethoven - Opferlied and Symp
Track: 2
Year: 2007
Genre: Classical
Comment: www.magnatune.com/artists/pbo
00:01:34 Layer III, 32 kbps, 22050 Hz, single channel, no CRC
3604 frames decoded (0:01:34.1), -9.4 dB peak amplitude, 0 clipped samples
root@fic-gta01:/media/card$

===Tuesday, August 21, 2007===

Played a 15 minute low bit rate MP3 on microSD card through the speaker (madplay controlled via screens under ssh). It seemed to die after 3 or 4 minutes, but works ok on desktop iTunes.

Flashed to 2007.2 snapshot - this has the new finger-oriented GUI from OpenedHand:
* [http://buildhost.openmoko.org/snapshots/2007.08/images/OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2 OpenMoko-openmoko-devel-image-glibc-P1-August-Snapshot-20070819-fic-gta01.rootfs.jffs2]
* [http://buildhost.openmoko.org/snapshots/2007.08/images/uImage-2.6.21.5-r3-fic-gta01.bin uImage-2.6.21.5-r3-fic-gta01.bin]

Looks great.

===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to [Graham Williams's survivor website http://openmoko.togaware.com/survivor/TouchScreen.html#799], I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

Neo 1973

2007-08-22T11:14:27Z

Dcorking: linkage and mild refactoring

[[Image:FIC-neo1973 small.jpg|120px|right]]
The [[Neo1973 Hardware | Neo1973]] is the first phone designed to run [[OpenMoko]].
It is a phone that can be used with any [[GSM]] operator, and it is manufactured by [[FIC]] who instigated the [[OpenMoko]] project.

If you just received a Neo1973 here are some suggestions for [[Getting_Started_with_your_Neo1973 | getting started]].

[[Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]] have more information on the hardware.

See [[OpenMoko]], [[OpenMokoFramework]], [[MokoMakefile]] and [[Development resources]] for more information about source code.

See [[FAQ]] for other Frequently Asked Questions.

== Phase 0 (GTA01Bv3) ==
:''Main article [[Neo1973 Phase 0]]
:''See also [[Wishlist:Neo1973_P0_Review]]
36 developers have received their devices. [http://lists.openmoko.org/pipermail/announce/2007-March/000006.html]

== Phase 1 (GTA01Bv4) ==
:''Main article [[Neo1973 Phase 1]]
You can order from https://direct.openmoko.com/ now. See also the [[Group Order]] page.

The Neo Base costs $300, the Neo Advanced costs $450.

See [[Neo1973_Hardware#GTA01Bv4|Neo1973 Hardware]] for what components GTA01B_v04 contains.

Neo Base -- everything the mobile application developer needs to enjoy
the benefits of the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card
* Mini USB Connectivity Cable

Neo Advanced -- everything the mobile device hacker wants to get down
and dirty with the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh) (2x)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card (2x)
* Mini USB Connectivity Cable (2x)
* Debug Flex Cable
* Debug Board v2 (JTAG and serial console)
* Ruggedized Toolbox with shoulder strap
* Guitar Pick (for opening case)
* Torx T6 screwdriver

You do not need the Advanced package to do normal kernel, or application development, only perhaps hacking on [[u-boot]].

As described in [http://lists.openmoko.org/pipermail/community/2007-June/006005.html Sean's post on mailing list] (with some adjustments/corrections).

== "Phase 2" (GTA02, "Mass Market") ==

GTA02 (AKA: The Mass Market Neo1973) is on schedule to go on sale in
October. It will have the following new hardware components:[http://lists.openmoko.org/pipermail/community/2007-July/008458.html]

* 802.11 b/g WiFi
* Samsung 2442 SoC
* SMedia 3362 Graphics Accelerator
* 2 3D Accelerometers
* 256MB Flash
* 1700mAh Battery
* Faster CPU - S3C2442/400
* LEDs illuminating the two buttons.

It will also lose:
* One speaker, becoming mono.

We will sell this device through multiple channels. Direct from
openmoko.com, the price will be $450 for the Neo Base and $600 for Neo Advanced.

Adds to the Phase 1 phone (see [[Neo1973:_GTA01Bv4_versus_GTA02_comparison|side by side comparison]]):
* 2D/3D-Graphics-Accelerator
* 2 Accelerometers (model and number is uncertain)
* Faster CPU - S3C2442/400
* WiFi: [http://lists.openmoko.org/pipermail/announce/2007-April/000012.html Atheros AR6K] (see also [http://lists.openmoko.org/pipermail/community/2007-April/004934.html])
** Above from [http://sicherheitsschwankung.de/gallery/v/openmoko/IMG_8662-slide.JPG.html] '' and other sources
* There will be no changes in the external housing, but internal plastics change. http://lists.openmoko.org/pipermail/community/2007-July/008458.html] [[http://lists.openmoko.org/pipermail/community/2007-March/004255.html]

<span id="bottom"></span>

{{Languages|Neo1973}}

[[Category:Neo1973 Hardware| ]]
[[Category:Neo1973_Phase_0_related| ]]
[[Category:Neo1973_Phase_1_related| ]]
[[Category:Neo1973_Phase_2_related| ]]

Neo 1973

2007-08-22T11:14:03Z

Dcorking: linkage and mild refactoring

[[Image:FIC-neo1973 small.jpg|120px|right]]
The [[Neo1973 Hardware | Neo1973]] is the first phone designed to run [[OpenMoko]].
It is a phone that can be used with any [[GSM]] operator, and it is manufactured by [[FIC]] who instigated the [[OpenMoko]] project.

If you just received a Neo1973 here are some suggestions for [[Getting_Started_with_your_Neo1973 | getting started]].

[[Neo1973 Hardware | Neo1973 Hardware]] and [[Disassembling Neo1973]] have more information on the hardware.

See [[OpenMoko]], [[OpenMokoFramework]], [[MokoMakefile]] and [[Development resources]] for more information about source code.

See [[FAQ]] for other Frequently Asked Questions.

== Phase 0 (GTA01Bv3) ==
:''Main article [[Neo1973 Phase0]]
:''See also [[Wishlist:Neo1973_P0_Review]]
36 developers have received their devices. [http://lists.openmoko.org/pipermail/announce/2007-March/000006.html]

== Phase 1 (GTA01Bv4) ==
:''Main article [[Neo1973 Phase 1]]
You can order from https://direct.openmoko.com/ now. See also the [[Group Order]] page.

The Neo Base costs $300, the Neo Advanced costs $450.

See [[Neo1973_Hardware#GTA01Bv4|Neo1973 Hardware]] for what components GTA01B_v04 contains.

Neo Base -- everything the mobile application developer needs to enjoy
the benefits of the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card
* Mini USB Connectivity Cable

Neo Advanced -- everything the mobile device hacker wants to get down
and dirty with the first freed phone, the Neo1973:

* Neo1973 (GTA01B_v4)
* Battery (1200mAh) (2x)
* Stylus
* Headset
* Phone Pouch
* Lanyard
* SanDisk 512MB MicroSD Card (2x)
* Mini USB Connectivity Cable (2x)
* Debug Flex Cable
* Debug Board v2 (JTAG and serial console)
* Ruggedized Toolbox with shoulder strap
* Guitar Pick (for opening case)
* Torx T6 screwdriver

You do not need the Advanced package to do normal kernel, or application development, only perhaps hacking on [[u-boot]].

As described in [http://lists.openmoko.org/pipermail/community/2007-June/006005.html Sean's post on mailing list] (with some adjustments/corrections).

== "Phase 2" (GTA02, "Mass Market") ==

GTA02 (AKA: The Mass Market Neo1973) is on schedule to go on sale in
October. It will have the following new hardware components:[http://lists.openmoko.org/pipermail/community/2007-July/008458.html]

* 802.11 b/g WiFi
* Samsung 2442 SoC
* SMedia 3362 Graphics Accelerator
* 2 3D Accelerometers
* 256MB Flash
* 1700mAh Battery
* Faster CPU - S3C2442/400
* LEDs illuminating the two buttons.

It will also lose:
* One speaker, becoming mono.

We will sell this device through multiple channels. Direct from
openmoko.com, the price will be $450 for the Neo Base and $600 for Neo Advanced.

Adds to the Phase 1 phone (see [[Neo1973:_GTA01Bv4_versus_GTA02_comparison|side by side comparison]]):
* 2D/3D-Graphics-Accelerator
* 2 Accelerometers (model and number is uncertain)
* Faster CPU - S3C2442/400
* WiFi: [http://lists.openmoko.org/pipermail/announce/2007-April/000012.html Atheros AR6K] (see also [http://lists.openmoko.org/pipermail/community/2007-April/004934.html])
** Above from [http://sicherheitsschwankung.de/gallery/v/openmoko/IMG_8662-slide.JPG.html] '' and other sources
* There will be no changes in the external housing, but internal plastics change. http://lists.openmoko.org/pipermail/community/2007-July/008458.html] [[http://lists.openmoko.org/pipermail/community/2007-March/004255.html]

<span id="bottom"></span>

{{Languages|Neo1973}}

[[Category:Neo1973 Hardware| ]]
[[Category:Neo1973_Phase_0_related| ]]
[[Category:Neo1973_Phase_1_related| ]]
[[Category:Neo1973_Phase_2_related| ]]

Neo1973 Phase 2

2007-08-22T11:08:51Z

Dcorking: There will eventually be an article here, until then redirect to Neo1973

#redirect [[Neo1973#"Phase 2" (GTA02, "Mass Market")]]
There will eventually be an article here, until then redirect to the main hardware page

OpenMoko2007.2

2007-08-22T10:45:08Z

Dcorking: typo

'''OM 2007.2''' is the second version of the OpenMoko distribution. Development began on 2007-07-26.

Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.

An official announcement was made by Sean Moss-Pultz on August 20:
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

==FAQ==

=== Q: What are differences between 2007.1 and 2007.2? ===

* UI redesigned for small and recessed screen
* Simplified visuals for performance
* Simplified UI
* More interactions including finger scrolling
* [[Today|openmoko-today]] rewritten; supports AUX and POWER buttons for navigation
* Updated upstream packages

=== Q: Where to get snapshot images? ===

* [[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article

* Official snapshots and ipkg repository:
** http://buildhost.openmoko.org/snapshots/2007.08/

=== Q: Where are official releases? ===

No official releases yet, just official snapshots. The first release is targetted for October, 2007.

=== Q: My mrxvt (terminal) fonts are huge. ===

Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:
#define MIN_XFT_FONT_SIZE (2)
and rebuild mrxvt & openmoko-devel-image.

End edit /etc/mrxvt/mrxvt.conf
Mrxvt.xftSize: 4
Mrxvt.xftHint: 1

==Building 2007.2==

=== How to build ===

The MokoMakefile is now able to build OM-2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building OM-2007.2 in the same way that you previously built images (i.e. according to http://wiki.openmoko.org/wiki/MokoMakefile). Make sure you set the generation correctly at the top of the file.

'''Please note that this is no official guide on how to build OM-2007.2. I am just making my first steps getting this to compile and think it would be a [http://en.wikipedia.org/wiki/Proprietary_software waste of time] of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.'''

Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. Use Bitbake 1.8.6 not a SVN version from the stable branch (otherwise you will get problems with checking out repositories) and the ''org.openembedded.dev'' branch of OE.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.

==== openmoko-libs FTBFS ====
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

==== Building glibc fails with a segfault in QEMU ====

If your build aborts and you see something like this:

NOTE: package glibc-2.5: started
NOTE: package glibc-2.5-r6: task do_package: started
NOTE: preparing tree for binary locale generation
NOTE: generating locale en_US (UTF-8)
qemu: uncaught target signal 11 (Segmentation fault) - exiting

...

NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed

Try editing your local.conf file. Change:

ENABLE_BINARY_LOCALE_GENERATION = "1"

to

ENABLE_BINARY_LOCALE_GENERATION = "0"

and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.

Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:

PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"
SRCDATE_qemu-native = 20070701

==== libxml2-native fails with xmlCatalogPtr errors ====

Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:

--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100
@@ -219,7 +219,7 @@
*
* Whether the Catalog support is configured in
*/
-#if 0
+#if 1
#define LIBXML_CATALOG_ENABLED
#endif

On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.

=== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ===

'''Note that the normal [[MokoMakefile]] can build OM-2007.2 now, so there is no need to use the procedure below. The nslu2-linux master makefile is designed for building various OE distributions, and is likely to produce something different from the standard OpenMoko images.
'''

'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
help2man \
libc6-dev libglib2.0-dev libtool libxext-dev\
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

Ubuntu 7.04 comes with monotone 0.31. You could just go with that and do a mtn db migrate but this takes hours so the easier way would be to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

If you're using MokoMakefile for building OM2007.1 you probably have fresh OE.mtn for version 0.31 already downloaded. So you can just make symlink to the OE.mtn in your OM2007.1 build directory.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn

To save even more bandwith you can also use already donwloaded source files from OM2007.1. Just make a symlink to OM2007.1 sources directory. Something like this.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/sources downloads

Go build ;)
make openmoko-devel-image

* If you an encounter an error with monotone similar to the following:

mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema

Then you need to upgrade nslu2-linux.mtn Use the following command:

# mtn --db monotone/nslu2-linux.mtn db migrate

== Flashing with MokoMakefile ==
Since MokoMakefile has not been adjusted to use the new build layout you cannot use it. As a quick hack to make flashing local built image possible again try this:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

Where you should replace <MY_NEW_BUILD_DIR> with the full path to your build directory (the one where ''conf/local.conf'' lives in). Running the image should work, too. :-)

With this changes kernel and uboot image are picked up correctly. However the name of the root filesystem image has changed in OM-2007.2 and the current scripts will not pick it up any more. Just edit ''$OM_DIR/build/qemu/openmoko/env'' and change the line saying:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== Pre-built snapshot images ==
* http://ipkg.nslu2-linux.org/feeds/openmoko/images/

* http://buildhost.openmoko.org/OM2007.2/snapshots/2007.08/ (Confirmed working)

* http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/

* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-22T10:44:29Z

Dcorking: update

'''OM 2007.2''' is the second version of the OpenMoko distribution. Development began on 2007-07-26.

Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.

An official announcement was made by Sean Moss-Pulz on August 20:
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

==FAQ==

=== Q: What are differences between 2007.1 and 2007.2? ===

* UI redesigned for small and recessed screen
* Simplified visuals for performance
* Simplified UI
* More interactions including finger scrolling
* [[Today|openmoko-today]] rewritten; supports AUX and POWER buttons for navigation
* Updated upstream packages

=== Q: Where to get snapshot images? ===

* [[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article

* Official snapshots and ipkg repository:
** http://buildhost.openmoko.org/snapshots/2007.08/

=== Q: Where are official releases? ===

No official releases yet, just official snapshots. The first release is targetted for October, 2007.

=== Q: My mrxvt (terminal) fonts are huge. ===

Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:
#define MIN_XFT_FONT_SIZE (2)
and rebuild mrxvt & openmoko-devel-image.

End edit /etc/mrxvt/mrxvt.conf
Mrxvt.xftSize: 4
Mrxvt.xftHint: 1

==Building 2007.2==

=== How to build ===

The MokoMakefile is now able to build OM-2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building OM-2007.2 in the same way that you previously built images (i.e. according to http://wiki.openmoko.org/wiki/MokoMakefile). Make sure you set the generation correctly at the top of the file.

'''Please note that this is no official guide on how to build OM-2007.2. I am just making my first steps getting this to compile and think it would be a [http://en.wikipedia.org/wiki/Proprietary_software waste of time] of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.'''

Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. Use Bitbake 1.8.6 not a SVN version from the stable branch (otherwise you will get problems with checking out repositories) and the ''org.openembedded.dev'' branch of OE.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.

==== openmoko-libs FTBFS ====
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

==== Building glibc fails with a segfault in QEMU ====

If your build aborts and you see something like this:

NOTE: package glibc-2.5: started
NOTE: package glibc-2.5-r6: task do_package: started
NOTE: preparing tree for binary locale generation
NOTE: generating locale en_US (UTF-8)
qemu: uncaught target signal 11 (Segmentation fault) - exiting

...

NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed

Try editing your local.conf file. Change:

ENABLE_BINARY_LOCALE_GENERATION = "1"

to

ENABLE_BINARY_LOCALE_GENERATION = "0"

and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.

Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:

PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"
SRCDATE_qemu-native = 20070701

==== libxml2-native fails with xmlCatalogPtr errors ====

Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:

--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100
@@ -219,7 +219,7 @@
*
* Whether the Catalog support is configured in
*/
-#if 0
+#if 1
#define LIBXML_CATALOG_ENABLED
#endif

On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.

=== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ===

'''Note that the normal [[MokoMakefile]] can build OM-2007.2 now, so there is no need to use the procedure below. The nslu2-linux master makefile is designed for building various OE distributions, and is likely to produce something different from the standard OpenMoko images.
'''

'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
help2man \
libc6-dev libglib2.0-dev libtool libxext-dev\
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

Ubuntu 7.04 comes with monotone 0.31. You could just go with that and do a mtn db migrate but this takes hours so the easier way would be to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

If you're using MokoMakefile for building OM2007.1 you probably have fresh OE.mtn for version 0.31 already downloaded. So you can just make symlink to the OE.mtn in your OM2007.1 build directory.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn

To save even more bandwith you can also use already donwloaded source files from OM2007.1. Just make a symlink to OM2007.1 sources directory. Something like this.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/sources downloads

Go build ;)
make openmoko-devel-image

* If you an encounter an error with monotone similar to the following:

mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema

Then you need to upgrade nslu2-linux.mtn Use the following command:

# mtn --db monotone/nslu2-linux.mtn db migrate

== Flashing with MokoMakefile ==
Since MokoMakefile has not been adjusted to use the new build layout you cannot use it. As a quick hack to make flashing local built image possible again try this:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

Where you should replace <MY_NEW_BUILD_DIR> with the full path to your build directory (the one where ''conf/local.conf'' lives in). Running the image should work, too. :-)

With this changes kernel and uboot image are picked up correctly. However the name of the root filesystem image has changed in OM-2007.2 and the current scripts will not pick it up any more. Just edit ''$OM_DIR/build/qemu/openmoko/env'' and change the line saying:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== Pre-built snapshot images ==
* http://ipkg.nslu2-linux.org/feeds/openmoko/images/

* http://buildhost.openmoko.org/OM2007.2/snapshots/2007.08/ (Confirmed working)

* http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/

* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)

[[Category:OpenMoko2007.2| ]]

OpenMoko2007.2

2007-08-22T10:44:06Z

Dcorking: update + small refactoring

'''OM 2007.2''' is the second version of the OpenMoko distribution. Development began on 2007-07-26.

Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.

An official announcement was made by Sean Moss-Pulz on August 21:
* http://lists.openmoko.org/pipermail/announce/2007-August/000018.html

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

==FAQ==

=== Q: What are differences between 2007.1 and 2007.2? ===

* UI redesigned for small and recessed screen
* Simplified visuals for performance
* Simplified UI
* More interactions including finger scrolling
* [[Today|openmoko-today]] rewritten; supports AUX and POWER buttons for navigation
* Updated upstream packages

=== Q: Where to get snapshot images? ===

* [[OpenMoko2007.2#Pre-built_snapshot_images|Unofficial images]] listed at the bottom of this article

* Official snapshots and ipkg repository:
** http://buildhost.openmoko.org/snapshots/2007.08/

=== Q: Where are official releases? ===

No official releases yet, just official snapshots. The first release is targetted for October, 2007.

=== Q: My mrxvt (terminal) fonts are huge. ===

Edit src/feature.h to set MIN_XFT_FONT_SIZE to lower value:
#define MIN_XFT_FONT_SIZE (2)
and rebuild mrxvt & openmoko-devel-image.

End edit /etc/mrxvt/mrxvt.conf
Mrxvt.xftSize: 4
Mrxvt.xftHint: 1

==Building 2007.2==

=== How to build ===

The MokoMakefile is now able to build OM-2007.2 images. If you use this new version of the MokoMakefile, you can ignore everything below and just continue building OM-2007.2 in the same way that you previously built images (i.e. according to http://wiki.openmoko.org/wiki/MokoMakefile). Make sure you set the generation correctly at the top of the file.

'''Please note that this is no official guide on how to build OM-2007.2. I am just making my first steps getting this to compile and think it would be a [http://en.wikipedia.org/wiki/Proprietary_software waste of time] of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.'''

Follow the [http://www.openembedded.org/wiki/GettingStarted getting started] steps of OpenEmbedded. Use Bitbake 1.8.6 not a SVN version from the stable branch (otherwise you will get problems with checking out repositories) and the ''org.openembedded.dev'' branch of OE.

Put the following in your local.conf

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

ENABLE_BINARY_LOCALE_GENERATION = "1"
GLIBC_GENERATE_LOCALES = "en_GB.UTF-8"

Replace "${HOME}/oe" with the path to where your "org.openembeded.dev" folder lives. For the other entries have a look at ''conf/local.conf.sample'' about their meaning.

Run ''bitbake <package name>'' (e.g. openmoko-devel-image).

=== Build issues ===

==== Wrong certificate ====
You may get something like this while the bitbake recipes are parsed:

Error validating server certificate for 'https://libw100.svn.sf.net:443':
- The certificate hostname does not match.
Certificate information:
- Hostname: *.svn.sourceforge.net
- Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
- Issuer: Equifax Secure Certificate Authority, Equifax, US
- Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.

==== openmoko-libs FTBFS ====
Some applications have not been fully modified to build with the new libraries of OpenMoko and still need the old-style ''openmoko-libs'' package. ''libmokogsm'' which is needed for ''openmoko-libs'' then fails to build. As a workaround you can remove the not yet ported applications that need ''openmoko-libs'' making it unneccessary itself. To do this edit ''packages/tasks/openmoko-taks.bb'' and find the following lines:

.
.
.
openmoko-terminal \
matchbox-panel-2 \
matchbox-panel-2-applets \
matchbox-applet-inputmanager \
# openmoko-appmanager \
matchbox-keyboard \
matchbox-stroke \
openmoko-keyboard \
.
.
.

Now put a hash (''#'') before ''openmoko-terminal'' and ''openmoko-keyboard''. You can verify that ''openmoko-libs'' is not needed any more by issuing ''bitbake -g openmoko-devel-image'' (= creates a dependency graph). There should be no mentioning of ''openmoko-libs'' in the file ''task-depends.dot''. '''Please note that the graphicall terminal and the virtual keyboard will be missing now.''' You can still have terminal access by following the [[USB Networking]] guide. For keyboard input in Qemu add the ''-usbdevice keyboard'' switch.

==== gtk+ fails building w/ gtkcombobox.c ====

If you get these errors:

gtkcombobox.c: In function 'gtk_combo_box_size_request':
gtkcombobox.c:1859: warning: unused variable 'font_desc'
gtkcombobox.c:1858: warning: unused variable 'metrics'
gtkcombobox.c:1857: warning: unused variable 'context'
gtkcombobox.c:1855: warning: unused variable 'arrow_size'
gtkcombobox.c:1854: warning: unused variable 'font_size'
gtkcombobox.c: In function 'gtk_combo_box_size_allocate':
gtkcombobox.c:1962: error: 'arrow_size' undeclared (first use in this function)
gtkcombobox.c:1962: error: (Each undeclared identifier is reported only once
gtkcombobox.c:1962: error: for each function it appears in.)
gtkcombobox.c:1965: error: 'font_desc' undeclared (first use in this function)
gtkcombobox.c:1966: error: 'context' undeclared (first use in this function)
gtkcombobox.c:1967: error: 'metrics' undeclared (first use in this function)
gtkcombobox.c:1969: error: 'font_size' undeclared (first use in this function)

Go to your /build/tmp/work/fic-gta01-angstrom-linux-gnueabi/gtk+-2.10.14-r3/gtk+-2.10.14/gtk directory, and patch gtkcombobox.c with the following:

Thanks to rmoravcik in #openmoko (patch was taken from http://pastebin.ca/654717 )

--- gtkcombobox.c 2007-08-12 20:30:07.000000000 +0200
+++ gtkcombobox.c 2007-08-12 20:29:58.000000000 +0200
@@ -1948,6 +1948,12 @@
gtk_combo_box_size_allocate (GtkWidget *widget,
GtkAllocation *allocation)
{
+ gint font_size;
+ gint arrow_size;
+ PangoContext *context;
+ PangoFontMetrics *metrics;
+ PangoFontDescription *font_desc;
+
GtkComboBox *combo_box = GTK_COMBO_BOX (widget);
gint focus_width, focus_pad;
GtkAllocation child;

==== Building glibc fails with a segfault in QEMU ====

If your build aborts and you see something like this:

NOTE: package glibc-2.5: started
NOTE: package glibc-2.5-r6: task do_package: started
NOTE: preparing tree for binary locale generation
NOTE: generating locale en_US (UTF-8)
qemu: uncaught target signal 11 (Segmentation fault) - exiting

...

NOTE: Tasks Summary: Attempted 271 tasks of which 0 didn't need to be rerun and 1 failed.
ERROR: '/home/moko/oe/org.openembedded.dev/packages/glibc/glibc_2.5.bb' failed

Try editing your local.conf file. Change:

ENABLE_BINARY_LOCALE_GENERATION = "1"

to

ENABLE_BINARY_LOCALE_GENERATION = "0"

and restart the build. This may have some effect on internationalization (you will see a warning indicating that), but at least the build will continue. Thanks to rwhitby for the tip.

Alternatively, as suggested by XorA in #openmoko, if you are running a 64-bit host distribution, try forcing a different QEMU rev, also in local.conf:

PREFERRED_VERSION_qemu-native = "0.9.0+cvs20070701"
SRCDATE_qemu-native = 20070701

==== libxml2-native fails with xmlCatalogPtr errors ====

Go to your build/tmp/work/i686-linux/libxml2-native-2.6.29-r1/libxml2-2.6.29/include/libxml/ directory and patch xmlversion.h with the following:

--- xmlversion.h 2007-08-17 10:45:42.000000000 +0100
+++ xmlversion.h 2007-08-17 10:51:36.000000000 +0100
@@ -219,7 +219,7 @@
*
* Whether the Catalog support is configured in
*/
-#if 0
+#if 1
#define LIBXML_CATALOG_ENABLED
#endif

On my system the libxml2-native-2.6.29-r1 directory is in a directory named i686-linux, yours may be different. I believe this patch to be a workaround to make libxml2-native build. I am not yet sure what the consequences of enabling XML catalogue support are.

=== How to build using nslu2-linux MasterMakefile (Ubuntu 7.04) ===

'''Note that the normal [[MokoMakefile]] can build OM-2007.2 now, so there is no need to use the procedure below. The nslu2-linux master makefile is designed for building various OE distributions, and is likely to produce something different from the standard OpenMoko images.
'''

'''Check that your /bin/sh (ls -l /bin/sh) is not linked to dash rather than bash.''' Using dash will cause you pain. This is true for a standard install of Ubuntu 7.04 (at least when installing from Live CD). If your /bin/sh points to /bin/dash, correct it with (as root):
ln -sf /bin/bash /bin/sh

Note: on http://www.openembedded.org/wiki/OEandYourDistro are better instructions for Ubuntu to make sh be bash.

Create your $OMDIR directory (note that you can change ~/OM-2007.2 to any directory you like):
mkdir ~/OM-2007.2 ; cd ~/OM-2007.2

Grab the nslu2-linux [http://www.nslu2-linux.org/wiki/Development/MasterMakefile MasterMakefile]:
wget http://www.nslu2-linux.org/Makefile

This will make sure you'll have all the required packages:
sudo apt-get install \
autoconf automake automake1.9 \
bison \
ccache cogito \
cvs \
diffstat \
docbook \
flex \
gcc g++ gawk gcj gettext git-core \
help2man \
libc6-dev libglib2.0-dev libtool libxext-dev\
m4 make \
patch pkg-config \
python python-dev python2.4 python2.4-dev python-psyco \
sed \
sharutils \
texinfo texi2html \
unzip \
subversion \
sysutils \
texinfo \
bzip2

Ubuntu 7.04 comes with monotone 0.31. You could just go with that and do a mtn db migrate but this takes hours so the easier way would be to download a suitable mtn db from http://www.openembedded.org/snapshots/ and use this.
mkdir -p monotone
wget http://www.openembedded.org/snapshots/\
OE-this-is-for-mtn-<your mtn version>.mtn.bz2 -O monotone/nslu2-linux.mtn.bz2
bunzip2 monotone/nslu2-linux.mtn.bz2

If you're using MokoMakefile for building OM2007.1 you probably have fresh OE.mtn for version 0.31 already downloaded. So you can just make symlink to the OE.mtn in your OM2007.1 build directory.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/OE.mtn monotone/nslu2-linux.mtn

To save even more bandwith you can also use already donwloaded source files from OM2007.1. Just make a symlink to OM2007.1 sources directory. Something like this.

(current directory(pwd) is /path/to/OM2007.2)
ln -s /path/to/OM2007.1/sources downloads

Go build ;)
make openmoko-devel-image

* If you an encounter an error with monotone similar to the following:

mtn: misuse: database monotone/nslu2-linux.mtn is laid out according to an old schema

Then you need to upgrade nslu2-linux.mtn Use the following command:

# mtn --db monotone/nslu2-linux.mtn db migrate

== Flashing with MokoMakefile ==
Since MokoMakefile has not been adjusted to use the new build layout you cannot use it. As a quick hack to make flashing local built image possible again try this:

Find the following lines in the MokoMakefile:

flash-qemu-local: stamps/qemu stamps/openmoko-devel-image
( cd build/qemu && openmoko/flash.sh ../tmp/deploy/images )

And replace them with:

flash-qemu-local: stamps/qemu
( cd build/qemu && openmoko/flash.sh <MY_NEW_BUILD_DIR>/tmp/deploy/glibc/images/fic-gta01 )

Where you should replace <MY_NEW_BUILD_DIR> with the full path to your build directory (the one where ''conf/local.conf'' lives in). Running the image should work, too. :-)

With this changes kernel and uboot image are picked up correctly. However the name of the root filesystem image has changed in OM-2007.2 and the current scripts will not pick it up any more. Just edit ''$OM_DIR/build/qemu/openmoko/env'' and change the line saying:

rootfs_wildcard="openmoko-*.rootfs.jffs2"

to

rootfs_wildcard="OpenMoko-*.rootfs.jffs2"

Now it will work correctly again.

== Pre-built snapshot images ==
* http://ipkg.nslu2-linux.org/feeds/openmoko/images/

* http://buildhost.openmoko.org/OM2007.2/snapshots/2007.08/ (Confirmed working)

* http://buildhost.openmoko.org/OM2007.2/tmp/deploy/glibc/images/fic-gta01/

* http://buildhost.openmoko.org/snapshots/2007.08/ (Official snapshots and ipkg repository)

[[Category:OpenMoko2007.2| ]]

User:Dcorking

2007-08-22T10:20:29Z

Dcorking: diary update

Carriers/TMobile

2007-08-22T09:30:49Z

Dcorking: US only so far

In the United States, T-Mobile (an affiliate of Deutsche Telekom) offers [[GSM]] [[SIM]] cards on pre-pay and pay monthly plans.

T-Mobile also offers GSM service (with GPRS) in other countries, not yet listed in this article.

== United States ==

A cursory glance on [http://www.t-mobile.com/shop/plans http://www.t-mobile.com/shop/plans at 08:58 UTC 2007-07-26] indicated that without entering zip code data two types of plans are available. 2-year contract plans (I think you have to talk to some for the 1 year plans) and Prepaid plans.

=== Contract Plans ===
* 08:58 UTC 2007-07-26 It seemed to me all there contract plans are 2 year terms unless you try to get one by calling or visiting a store [http://www.t-mobile.com/shop/plans/ "For a 1-year contract, call 1-877-387-4324 or visit one of our T-Mobile stores" at the bottom of the page]
* 08:58 UTC 2007-07-26 They have either Individual/Regular Individual/MyFav Family/Regular or Family/MyFav plans
* 08:58 UTC 2007-07-26 Mobile To Mobile "...Note: Service in North and South Carolina, Iowa (area codes 319, 563, and 712), Wisconsin (area code 608), and Michigan (area code 906) is provided by T-Mobile roaming partners so calls will not be rated as mobile-to-mobile in these areas. Calls from or to locations outside of the US will not be rated as mobile-to-mobile."
* Needs more info..

=== Prepaid Plans ===
[http://www.t-mobile.com/shop/plans/Default.aspx?plancategory=4 http://www.t-mobile.com/shop/plans/Default.aspx?plancategory=4]
* 08:58 UTC 2007-07-26 Unpleasantly they have a gold status that gives one different refill values than normal users.
* 08:58 UTC 2007-07-26 I expect those that expend large amounts of money get gold status.

{| border="1"
!Refill value !! Premium Minutes !! Cost/Min !! Min Use Avoid Waste !! Expiration !! Gold Premium Minutes !! Gold Premium Expiration
|-
| $10 || 30min || 33.3cent/min || ~1min/3day avg || 90days || gold+5min || gold+330days
|-
| $25 || 130min || 19.2cent/min || ~4min/3day avg || 90days || gold+20min || gold+330days
|-
| $50 || 400min || 12.5cent/min || ~9min/2day avg || 90days || gold+60min || gold+330days
|-
| $100 || 1000min || 10.0cent/min || || 1year || gold+0min || gold+0days
|}

* 08:58 UTC 2007-07-26 You lose your number after 90 days of no service... "...To keep your mobile number active, refill within 90 days after your minutes expire. After 90 days, your account will be canceled and you will lose your phone number. If you want to restart service, you will need to activate new service."

* '''Inside Information:''' If you want to buy prepaid plans, it is best to go with the $100 gold plan. The catch is there is a $10 activation fee, so you end up paying $110 to get a SIM card with 1000 minutes valid for 1 year. Their base line phone is $30 (2007-08-01) if you want a backup phone.

* Look into the T-Mobile Flex plan: Pay as you go $39.99 for 1000 minutes, evenings and weekends free! No contracts (or so the salesman said). Still costs $20 to buy a sim card from the store.
*T-mobile Flex-plan : It is the same as a plan (MyFav, Individual plan etc etc) expect you pay 5$ more, and there is no contract, you can quit whenever you want. You can add Sidekick on it if you want.

=== Data Access Plans ===

* T-Mobile does not offer data plans on pre-pay accounts ''Information from T-Mobile Store in the US on 2007-08-01''

* GPRS data access in the US works fine with Phase 1 phone and instructions on [[Manually_using_GPRS]]

* FIXME: Add information here

[[Category:Carriers]]

Carriers/TMobile

2007-08-22T09:27:24Z

Dcorking: United States only so far

== United States ==

A cursory glance on [http://www.t-mobile.com/shop/plans http://www.t-mobile.com/shop/plans at 08:58 UTC 2007-07-26] indicated that without entering zip code data two types of plans are available. 2-year contract plans (I think you have to talk to some for the 1 year plans) and Prepaid plans.

== Contract Plans ==
* 08:58 UTC 2007-07-26 It seemed to me all there contract plans are 2 year terms unless you try to get one by calling or visiting a store [http://www.t-mobile.com/shop/plans/ "For a 1-year contract, call 1-877-387-4324 or visit one of our T-Mobile stores" at the bottom of the page]
* 08:58 UTC 2007-07-26 They have either Individual/Regular Individual/MyFav Family/Regular or Family/MyFav plans
* 08:58 UTC 2007-07-26 Mobile To Mobile "...Note: Service in North and South Carolina, Iowa (area codes 319, 563, and 712), Wisconsin (area code 608), and Michigan (area code 906) is provided by T-Mobile roaming partners so calls will not be rated as mobile-to-mobile in these areas. Calls from or to locations outside of the US will not be rated as mobile-to-mobile."
* Needs more info..

== Prepaid Plans ==
[http://www.t-mobile.com/shop/plans/Default.aspx?plancategory=4 http://www.t-mobile.com/shop/plans/Default.aspx?plancategory=4]
* 08:58 UTC 2007-07-26 Unpleasantly they have a gold status that gives one different refill values than normal users.
* 08:58 UTC 2007-07-26 I expect those that expend large amounts of money get gold status.

{| border="1"
!Refill value !! Premium Minutes !! Cost/Min !! Min Use Avoid Waste !! Expiration !! Gold Premium Minutes !! Gold Premium Expiration
|-
| $10 || 30min || 33.3cent/min || ~1min/3day avg || 90days || gold+5min || gold+330days
|-
| $25 || 130min || 19.2cent/min || ~4min/3day avg || 90days || gold+20min || gold+330days
|-
| $50 || 400min || 12.5cent/min || ~9min/2day avg || 90days || gold+60min || gold+330days
|-
| $100 || 1000min || 10.0cent/min || || 1year || gold+0min || gold+0days
|}

* 08:58 UTC 2007-07-26 You lose your number after 90 days of no service... "...To keep your mobile number active, refill within 90 days after your minutes expire. After 90 days, your account will be canceled and you will lose your phone number. If you want to restart service, you will need to activate new service."

* '''Inside Information:''' If you want to buy prepaid plans, it is best to go with the $100 gold plan. The catch is there is a $10 activation fee, so you end up paying $110 to get a SIM card with 1000 minutes valid for 1 year. Their base line phone is $30 (2007-08-01) if you want a backup phone.

* Look into the T-Mobile Flex plan: Pay as you go $39.99 for 1000 minutes, evenings and weekends free! No contracts (or so the salesman said). Still costs $20 to buy a sim card from the store.
*T-mobile Flex-plan : It is the same as a plan (MyFav, Individual plan etc etc) expect you pay 5$ more, and there is no contract, you can quit whenever you want. You can add Sidekick on it if you want.

== Data Access Plans ==

* T-Mobile does not offer data plans on pre-pay accounts ''Information from T-Mobile Store in the US on 2007-08-01''

* GPRS data access in the US works fine with Phase 1 phone and instructions on [[Manually_using_GPRS]]

* FIXME: Add information here

[[Category:Carriers]]

GUI Style Guidelines

2007-08-22T08:57:11Z

Dcorking: /* Using GTK+ and libmokoui */ sp

== Abstract ==

OpenMoko is a platform targeted at small screen devices. This means that many of the usual desktop pardigms of windows and menus do not apply very well due to the limited space. Different form factors mean that displays on these devices are often at different orientations and aspect ratios. The OpenMoko platform tries to address some of these differences by providing a framework in which application authors do not need to be too concerned about the final layout of their application.

== Top Level Overview ==

OpenMoko applications are designed as a number of "pages", which may have a number of relationships between them. Each page contains one task, such as selecting a contact or viewing a calendar.

=== Layout Abstraction ===

Pages that are not affected by changes in other pages are known as Primary pages. These work independently of any other pages. Pages which are affected by changes in a primary page are known as secondary pages. For example, in a contacts application, the primary page would be the list of contacts. Secondary pages would be the pages that display information about the selected contact.

Every page has a label, icon and content associated with it. This is used to identify and display the page when necessary.

The relationships between pages are described in a model created when the application is started. The application then instantiates a further object which acts as the view and controller to the model. This deals with creating the initial layout of the application.

== Neo1973 Layout ==

On this form factor, the layout is portrait and constrained by a very small screen size. To accommodate this, all pages are full screen and the target area for buttons must be as large as possible. Borders and spacing between widgets is kept to a minimum to ensure best use of available screen estate.

[[Image:contacts-main-guidelines.png]]

* '''1) [[GUI_Style_Guidelines#Toolbars | Toolbar]]''' -- Additional actions related to the current page.
* '''2) [[GUI_Style_Guidelines#Filter/Search | Filter/Search]]''' -- Filtering options for the current page.
* '''3) [[GUI_Style_Guidelines#Pages | Pages Navigation]]''' -- Method to switch between pages.
* '''4) Title''' -- The window title is not part of the application itself. It is embedded into the main panel and is automatically set to the current applications name. It also serves as a quick way to navigate between open applications.

=== Pages ===

Switching between pages is achieved by a series of tabs laid horizontally across the bottom of the screen. Each tab contains an icon depicting the purpose of the page it is attached to.

=== Toolbars ===

Toolbars appear at the top of the screen, with tool buttons expanded to fill the space available. This ensures maximum target hit area. There should be no more than four items in a toolbar.

=== Filter/Search ===

The filter/search bar is an optional component, composed of three widgets. A toggle button switches between filter (combo box) and search (entry box). Typing in the search box should re-filter the data after each keypress.

== Input Considerations ==

=== Keyboard ===

For devices which require on screen keyboards, the keyboard will automatically appear whenever a widget that requires key input is focused.

=== Touch Screen ===

The touch screen should be used for single click (tap) and drag options only. A tap and hold will activate button three on the mouse ("right" click). The "double click" action is strongly discouraged.

== General Application Guidelines ==

=== Data Persistence ===

All applications that manipulate data should aim to follow the "instant apply" model so that there is no need for the user to explicitly save any data entered.

=== State Persistence ===

Applications should save their state if possible between sessions. This might include current view details or "unsaved" data.

== Using GTK+ and libmokoui ==

GTK+ is a C library that uses GObject for pseudo object orientation. This allows it to be very portable and flexible.

=== General Guidelines ===

OpenMoko code mostly uses the c99 standard for C.

Spacing,widgets sizes and fonts '''must not''' be hard coded into OpenMoko applications. OpenMoko is a framework for small screen devices, which may include anything as small as QVGA (320x240) to 800x600. Therefore, for applications to work on these different resolutions, programs must not hard code anything to do with the specific appearance of widgets.

=== Programming Guidelines ===
Most on screen elements such as buttons and entry boxes are sub classed from the GtkWidget base class. The normal practice is to cast up from this class. For this reason, all the creator functions return GtkWidget rather than the class of which they are creating.

{{Languages|GUI_Style_Guidelines}}
[[Category:User Interfaces]]

Wishlist/Bible Reader

2007-08-21T11:21:33Z

Dcorking: threading, linking

Most handheld platforms have some sort of bible, or religeous text reader. An excellent example would be bible+ for the palm platform. A good generic approach so that the reader was designed to read any religeous text would be a good idea.

:''This is probably redundant if a good generic ebook [[reader]] can be be found/developed. What are compelling advantages of a "bible reader" over an "ebook reader"?

::Most religeous texts are broken into separate books. Another issue is that individuals may want to see dual language versions with a religeous text (IE, for the new testament, greek/english). Beyond the segmentation into books, each verse of a religeous text is usually noted. If I were reading a traditional book, I wouldn't care what verse I was reading, but with a religeous text, the verse/line pairing is important. I am fairly sure that these approaches are true of all abrahamic religeons, however, I would suspect that they are also true of other religeons as well.

Ts calibrate

2007-08-20T21:27:02Z

Dcorking: link to some ipks

'''''ts_calibrate''''' is a graphical tool to calibrate the touch sensor. The app asks the user to tap a sequence of 5 cross-hairs with a stylus. It recalibrates the touchscreen, then exits.

As of August 2007, it is typically included in the OpenMoko root filesystem, but does not appear in the graphical menus. You can run it from an [[ssh]] or [[GTKTerm2]] command line.

It is a C program, ts_calibrate.c, and appears to be part of the [[xcalibrate]] package.

==Upstream==

:''I am not sure where the upstream sources of this come from. Could someone add that please? It appears to be also distributed by OpenEmbedded, Familiar and GPE. --[[User:Dcorking|Dcorking]] 18:37, 20 August 2007 (CEST)

==Usage notes==

You probably won't get good results with a finger or fingernail - so try to have a stylus handy.

==External links==
* http://openmoko.togaware.com/survivor/TouchScreen.html
* http://handhelds.org/packages/xcalibrate/

Ts calibrate

2007-08-20T16:37:48Z

Dcorking: what it does

'''''ts_calibrate''''' is a graphical tool to calibrate the touch sensor. The app asks the user to tap a sequence of 5 cross-hairs with a stylus. It recalibrates the touchscreen, then exits.

As of August 2007, it is typically included in the OpenMoko root filesystem, but does not appear in the graphical menus. You can run it from an [[ssh]] or [[GTKTerm2]] command line.

It is a C program, ts_calibrate.c, and appears to be part of the [[xcalibrate]] package.

==Upstream==

:''I am not sure where the upstream sources of this come from. Could someone add that please? It appears to be also distributed by OpenEmbedded and GPE. --[[User:Dcorking|Dcorking]] 18:37, 20 August 2007 (CEST)

==Usage notes==

You probably won't get good results with a finger or fingernail - so try to have a stylus handy.

==External links==
* http://openmoko.togaware.com/survivor/TouchScreen.html

User:Dcorking

2007-08-20T16:25:33Z

Dcorking: /* Monday, August 20, 2007 */

I am David Corking.

I have a [[P1 Owners|P1]] device.

Website: http://dcorking.com/

Company website: http://www.corking-project.co.uk/

Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==
===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to [Graham Williams's survivor website http://openmoko.togaware.com/survivor/TouchScreen.html#799], I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-20T16:14:48Z

Dcorking: /* Openmoko diary (most recent first) */ ts_calibrate

I am David Corking.

I have a [[P1 Owners|P1]] device.

Website: http://dcorking.com/

Company website: http://www.corking-project.co.uk/

Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==
===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

When I flashed this image on Saturday, I calibrated the touchscreen with my fingernail. Unfortunately I was often missing targets by a few pixels, so thanks to Graham Williams's survivor website, I found that I could run [[ts_calibrate]] from the command line, this time with the stylus, and after 5 taps, things were working much better!

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream, and tried another one instead.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-20T15:55:22Z

Dcorking: blog

I am David Corking.

I have a [[P1 Owners|P1]] device.

Website: http://dcorking.com/

Company website: http://www.corking-project.co.uk/

Blog: http://voip4linux.infogami.com/blog/

==Openmoko diary (most recent first) ==
===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream and try another one.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-20T15:54:27Z

Dcorking: /* Monday, August 20, 2007 */ [http://www.gnome.org/projects/gedit/ gedit]

I am David Corking.

I have a [[P1 Owners|P1]] device.

Website: http://dcorking.com/

Company website: http://www.corking-project.co.uk/

Blog: http://voip4linux.infogami.com/

==Openmoko diary (most recent first) ==
===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

I ran [http://www.gnome.org/projects/gedit/ gedit] remotely from the Mac (using the Neo as the X server, with instructions on [[USB Networking#Remote apps on neo]]) It looked remarkably good and was responsive to the stylus and the on-screen keyboard.

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream and try another one.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

User:Dcorking

2007-08-20T15:22:04Z

Dcorking: my openmoko diary

I am David Corking.

I have a [[P1 Owners|P1]] device.

Website: http://dcorking.com/

Company website: http://www.corking-project.co.uk/

Blog: http://voip4linux.infogami.com/

==Openmoko diary (most recent first) ==
===Monday, August 20, 2007===

Device is working beautifully, tethered to my MacBook by USB.

There is a new graphic for battery status - it looks like an empty battery, with a pronged cable plugged into it. I don't know if this means 'charging', or 'fully charged', or something else.

Remote terminal by ssh from the MacBook into the Neo worked first time - it is a bit disconcerting to have an IP login with no password, but great to have a fully functioning Linux console, in a computer that is as powerful as my first Linux desktop system 9 years ago (bar hardware screen acceleration.)

Despite the speed and storage of the system, most of the common unix utilities come from the cut down [[BusyBox]] toolkit, rather than the more functional GNU utilities.

Read that AUX wakes up the screen when it has gone to sleep. When in Linux, press and hold for 5 seconds to get a stylus menu including 'power off'. Press and hold for 9 seconds otherwise to halt.

I [http://wiki.openmoko.org/wiki/Special:Contributions/Dcorking helped] tidy up the openmoko wiki.

===Sunday, August 19, 2007===

The screen is blank - nothing was happening! So I tested briefly with a BL-5C battery from my Nokia phone. I wanted to put the FIC battery in the Nokia phone to charge, but it is much thicker than the BL-5C, so the Nokia phone cover does not go back on.

Charged my deeply discharged device for most of the day with the dumb APC charger. Then, still connected to the charger, I booted and played with the UI and the stylus. The battery indicator showed a little over half full, but very quickly discharged, showing red and then shutting down.

I plugged into the MacBook (which is configured not to sleep) and left it overnight.

===Saturday August 18, 2007===
Briefly tested the new P1 device with a charged Nokia BL-5C [[battery]]

Put the FIC battery in the phone, and charged for approx. 8 hours with an APC dumb USB charger. Surprised to see that the phone boots as soon as power is applied to the USB socket (this is as designed.)

Installed AJZaurusUSB and OpenMoko Flasher on my [[Mac OS X]] Intel MacBook. Discovered that the Neo1973 IR port was in fact the AUX button (no IR - as designed.) Flashed the device with a recent kernel and rootfs.
* openmoko-devel-image-fic-gta01-20070803091138.rootfs.jffs2
* uImage-2.6.21.6-moko11-r1_0_0_2388_-fic-gta01.bin
(the image I first wanted did not seem to be visible to OpenMoko Flasher, so I decided not to swim upstream and try another one.)

Booted into an attractive high resolution graphical interface.

Pressed the power button, the screen went blank. I didn't know if it was powered off—it turns out it wasn't, and it deeply discharged the battery overnight.

END

Talk:Screen Grabber

2007-08-20T14:44:34Z

Dcorking: removed duplicate material, see Screen Shots

==Discussion==

Getting Started with your Neo 1973

2007-08-20T14:05:16Z

Dcorking: /* Buttons */ links

This is a guide of some first steps for those who have just received their first [[Neo1973]] phone. [[Shipment 1]] has some specifics limited to that batch.

== Hardware ==

=== Assembly ===

'''A short demonstration is available on Google video: [http://video.google.de/videoplay?docid=-8343770443102960945 Open the back cover, remove the battery, remove the SIM card, remove the micro-SD card, insert the micro-SD card, insert the SIM card, insert the battery, close the back cover]'''

The micro-SD slot is underneath the SIM slot, which is underneath the battery. To access any of these, you need to open the back cover of the phone.

The [[SIM]] card and the [[micro-SD]] memory card are optional; SIM is needed only for cell network functionality and memory card for extra storage.

==== Back cover ====

Remove the back cover by putting your fingernail or a guitar pick in the small recess on the top of the Neo and pulling gently (see just the first step of [[Disassembling Neo1973]]).

When you are done, close the back cover by inserting the pins of the cover into the holes on the bottom of the Neo and pressing the top of the case gently.

==== Battery ====

To remove the [[battery]], lift its bottom edge with your fingernail.

Before closing the cover, insert the battery by pushing it against the three metal springs with the contacts aligned and pressing the bottom edge of the battery down into the case.

==== SIM card (optional) ====

The [[SIM card]] is obtained from a cell network operator. The slot for the SIM card is found just under the battery. The metallic card holder has arrows and text indicating which way to push it to lock and unlock it - make sure you don't open it with force when it's locked or it may break.

Click the holder unlocked and open it up. To remove the SIM card, slide it out of the holder.

When you're done with the micro-SD slot, slide the SIM card into its holder so that the pads make contact when you close the holder. Push the holder firmly against the springs, then lock it - otherwise the card will not be detected.

To check in Linux if the SIM card is inserted correctly, you can have a look in gsmd logs or use the instructions detailed in the [[Manually using GSM]] page and issue the ''AT+CIMI'' command.

==== Micro-SD card (optional) ====

You should have received a [[micro-SD]] memory card with your phone. You might want to copy some mp3 (or better Ogg Vorbis) files to it to try media playback.

The micro-SD slot is right under the SIM slot. Gently slide the micro-SD holder toward the battery contacts to unlock it. Lift up the holder. To remove a card, simply slide it out.

To insert a card, slide it into the holder the metal contacts first and away from the holder. Rotate the holder shut, press it firmly against the springs, and gently slide the holder away from the battery contacts to lock it closed.

The card should automatically be available under /media/card the next time you boot. You can test it and your audio drivers at the same time by playing an mp3 or ogg from it (see [[Neo1973 Audio Subsystem]]).

=== Buttons ===

The [[Neo1973 Power Button|power button]] is on the lower right-hand side, and the [[Neo1973 AUX Button|AUX button]] is on the top-left.

=== Accessories ===

==== Stylus ====

The stylus as shipped has three batteries in it, providing for the laser pointer and flashlight LEDs. A set of replacement batteries is also included. The stylus can be twisted open in middle to access the batteries.

To use the ballpoint or stylus head, turn the bottom part of the stylus to either direction.

==== Headset ====

The Neo ships with a stereo headset including a microphone and a push button. The plug is a standard 2.5 mm four-conductor version, though it differs from standard 3.5 mm headphones. The black socket is on the left side of the phone, and the last millimeter is somewhat firmer so make sure you push the plug all the way.

==== Lanyard ====

The provided lanyard can be attached to the hole in the bottom part of the phone. Put the loose end through the phone, through the two metal loops in the lanyard, between the metal loops and back through the first metal loop.

=== Powering up the phone ===
[[Image:Neo1973_uboot_splash.jpg|200px|thumb|bootloader splash screen]]
Just hitting the power button (depending on your [[u-boot]] version you have to press for >= 5 seconds) should get the phone first into the bootloader, then boot the kernel, and get into X/OpenMoko. The shipped battery typically has enough charge to boot up directly without charging through the usb cable first.

Once you have pressed the power button sufficiently long, the vibrator makes a short pulse and the screen backlight turns on. You can now release the power button and watch the phone booting.

If the battery is not sufficiently charged, the phone will not turn on, even if the usb cable is plugged in.

=== Flashing the Neo1973 GTA01Bv4 ===
The GTA01Bv4 devices that are currently shipping do not boot out of the box. Flashing the phone with the latest kernel and [[Userspace root image|supporting file system ("rootfs")]] is required before the phone will successfully boot.

Read more information at about [[Flashing openmoko]]. MacOS X users please also refer to [[MacOS_X]].

=== Powering down the phone ===

==== While in bootloader mode, or if the phone has crashed ====

If you press the power button for 9 seconds, the phone will switch off. You can notice this by the backlight going dark.

==== While running a full linux system with userspace ====

In this mode, a power-button press of 5 seconds will be sufficient. After this, the init process will take care of safely shutting down the phone, which might take up to 20 extra seconds. The X server should get killed, you should drop back to a (garbled) console, and it should finally switch off - much like a regular Linux PC.

=== Battery charging ===
:''See also [[Neo1973 Battery Charger]]
The [[Neo1973]] supports two charging modes: One 100mA charge mode (called pre-charge) and 500mA (called fast charge). Charging is always done via the USB socket. You can use any USB-A to USB-mini-B cable to connect the phone to any USB host.

==== While in u-boot ====

While you are in u-boot mode, the phone only charges with 100mA by default. (This will change in one of the future revisions).

However, using the u-boot console you can manually enable fast charging. See [[U-boot#Battery_charger_related]] for more information.

==== While in Linux ====

As soon as the phone is connected via USB cable, it will charge. However, the default charging current is only 100mA, way too little if you want to operate the phone and charge at the same time.

If your USB upstream port is capable of supplying 500mA, then it will configure the Neo1973 accordingly and use 500mA charging mode. You can notice this by the following line in the kernel log (/var/log/messages) of the laptop/desktop your Neo1973 is hooked up to
usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet

== Getting shell access on the phone ==

=== By using the terminal emulator and on-screen keyboard ===

"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.

With newer images, the keyboard comes up when you tap the white box in the top bar.

You can choose between different keyboard layouts and the stroke recognizer by dragging from the white box and releasing it to the right of the box.

From the desktop, choose "Active tasks->rxvt" to get a root shell.

[[Terminal]] is in the top level menu in recent images.

=== By using Ethernet emulation over a USB cable ===

The standard Neo1973 Linux [[kernel]] has support for the "cdc_ether USB gadget", i.e. a standard implementation of how to emulate an Ethernet device over USB.

The following description is for generic *NIX system. For setting up connectivity specifically on a MacOS X machine, refer to [[MacOS_X]] (because there is no usb0 and you need a special kernel driver first).

As soon as the kernel is up and running, and you have the phone connected via USB, you should get a '''usb0''' device on your host.

The Phone will have the IPv4 address 192.168.0.202/24. You can run `ifconfig` in the terminal on the phone to verify this (this is optional, just check it if it doesn't work given the instructions below)

If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear. If not, see [[USB_Networking]] for more details.

On the '''host PC''', you should then configure your interface to 192.168.0.200 by using
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then you should be able to
# ping 192.168.0.202

and last, but not least
# ssh root@192.168.0.202

Once you press 'enter' (empty password), you should now have a root login.

See [[USB_Networking]] for more details, including instructions on how to automatically setup masquerading so that your phone can get access to the internet through the host PC.

=== By using the debug board/serial/JTAG ===

Please see [[Debug Board#Usage_Instructions]]

== Getting access to the bootloader console ==

Please see [[u-boot#Using_usbtty_from_Linux]]

== Using Audio ==
=== Enable Internal Speaker and Mic in Phone Calls ===
If you got no Speaker and Mic during a Call you need to load the "gsmhandset.state" alsa-configfile

alsactl -f /etc/alsa/gsmhandset.state restore

Maybe you need to load another .state file for playing mp3 or a BT-Headset see in /etc/alsa/

To hear something you can find an .au file (or convert a .wav into an .au by using the sox tool):

sox ringtone_thereisnophone.wav -t raw -r 8012 -u -b -c 1 rigtone_thereisnophone.au

copy it to the device and run

cat ringtone_thereisnophone.au > /dev/dsp

== Useful commands in Linux ==

=== Suspending ===

Writing "mem" into ''/sys/power/state'' tells Linux to suspend - it will enter a low power mode where only the GSM and RAM are powered up and the CPU sleeps. It will persist in this state until a wake-up event arrives. Some currently enabled wake-up events are: AUX or POWER key press, USB cable detect.

If you're connected over ssh, sshd will stop responding when the OS suspends, so to avoid locking up your ssh client, use the command
# (sleep 1; echo mem > /sys/power/state) & exit

=== Initial backup ===

After getting your new Neo1973 booted for the first time you might want to make a back up of the original flash chip contents on your PC, before you overwrite the flash with a custom image or just update to a newer build.

{{note|For phase 0 developers only (GTA01Bv4 shippment 0, '''not > 0 '''): This is a good idea because there are parts in the root filesystem that can't be distributed over internet so they are only found in the shipped ROM (see the [[GPS]] driver).}}

One easy way to back up all of the Flash, that doesn't require installing any special software, is with ''netcat'' over the [[USB Networking|USB ethernet]]. The following commands can be used for that.
{|
! On the host !! On the target
|-
|<pre>
$ netcat -l -p 20000 > mtdblock0
$ netcat -l -p 20000 > mtdblock1
$ netcat -l -p 20000 > mtdblock2
$ netcat -l -p 20000 > mtdblock3
$ netcat -l -p 20000 > mtdblock4
</pre>
|<pre>
# cat /dev/mtdblock0 | nc 192.168.0.200 20000
# cat /dev/mtdblock1 | nc 192.168.0.200 20000
# cat /dev/mtdblock2 | nc 192.168.0.200 20000
# cat /dev/mtdblock3 | nc 192.168.0.200 20000
# cat /dev/mtdblock4 | nc 192.168.0.200 20000
</pre>
|}

This stores the five NAND partitions in files named mtdblock*. Knowing the partition layout (u-boot "mtdparts" command or Linux dmesg) you can restore the whole flash with it.

=== Setting date and time ===

To set the date and time you need to open a terminal or ssh to the device. To set the date and time to August 9 19:02 2007 type:

# date -s 080919022007

The screensaver might turn on as you execute this command - just tap the screen to get back.

Now, you need to synchronize the time with the hardware date/time by typing:

# hwclock --systohc

=== Where to from here ===

You'll probably want to play with some of the interesting hardware in this device. Obviously, you can explore the applications available through the touch-screen interface. But for those who prefer doing things more in the raw from a shell prompt, you can [[Manually_using_GSM | manually use GSM]], [[Manually_using_SMS | manually use SMS]], or you can start playing with the [[GPS]].

<span id="bottom">{{Languages|Getting_Started_with_your_Neo1973}}</span>

[[Category:Documentation]]
[[Category:Neo1973_Phase_1_related]]

Getting Started with your Neo 1973

2007-08-20T13:58:22Z

Dcorking: /* Battery charging */ :''See also Neo1973 Battery Charger

This is a guide of some first steps for those who have just received their first [[Neo1973]] phone. [[Shipment 1]] has some specifics limited to that batch.

== Hardware ==

=== Assembly ===

'''A short demonstration is available on Google video: [http://video.google.de/videoplay?docid=-8343770443102960945 Open the back cover, remove the battery, remove the SIM card, remove the micro-SD card, insert the micro-SD card, insert the SIM card, insert the battery, close the back cover]'''

The micro-SD slot is underneath the SIM slot, which is underneath the battery. To access any of these, you need to open the back cover of the phone.

The [[SIM]] card and the [[micro-SD]] memory card are optional; SIM is needed only for cell network functionality and memory card for extra storage.

==== Back cover ====

Remove the back cover by putting your fingernail or a guitar pick in the small recess on the top of the Neo and pulling gently (see just the first step of [[Disassembling Neo1973]]).

When you are done, close the back cover by inserting the pins of the cover into the holes on the bottom of the Neo and pressing the top of the case gently.

==== Battery ====

To remove the [[battery]], lift its bottom edge with your fingernail.

Before closing the cover, insert the battery by pushing it against the three metal springs with the contacts aligned and pressing the bottom edge of the battery down into the case.

==== SIM card (optional) ====

The [[SIM card]] is obtained from a cell network operator. The slot for the SIM card is found just under the battery. The metallic card holder has arrows and text indicating which way to push it to lock and unlock it - make sure you don't open it with force when it's locked or it may break.

Click the holder unlocked and open it up. To remove the SIM card, slide it out of the holder.

When you're done with the micro-SD slot, slide the SIM card into its holder so that the pads make contact when you close the holder. Push the holder firmly against the springs, then lock it - otherwise the card will not be detected.

To check in Linux if the SIM card is inserted correctly, you can have a look in gsmd logs or use the instructions detailed in the [[Manually using GSM]] page and issue the ''AT+CIMI'' command.

==== Micro-SD card (optional) ====

You should have received a [[micro-SD]] memory card with your phone. You might want to copy some mp3 (or better Ogg Vorbis) files to it to try media playback.

The micro-SD slot is right under the SIM slot. Gently slide the micro-SD holder toward the battery contacts to unlock it. Lift up the holder. To remove a card, simply slide it out.

To insert a card, slide it into the holder the metal contacts first and away from the holder. Rotate the holder shut, press it firmly against the springs, and gently slide the holder away from the battery contacts to lock it closed.

The card should automatically be available under /media/card the next time you boot. You can test it and your audio drivers at the same time by playing an mp3 or ogg from it (see [[Neo1973 Audio Subsystem]]).

=== Buttons ===

The power button is on the lower right-hand side, and the AUX button is on the top-left.

=== Accessories ===

==== Stylus ====

The stylus as shipped has three batteries in it, providing for the laser pointer and flashlight LEDs. A set of replacement batteries is also included. The stylus can be twisted open in middle to access the batteries.

To use the ballpoint or stylus head, turn the bottom part of the stylus to either direction.

==== Headset ====

The Neo ships with a stereo headset including a microphone and a push button. The plug is a standard 2.5 mm four-conductor version, though it differs from standard 3.5 mm headphones. The black socket is on the left side of the phone, and the last millimeter is somewhat firmer so make sure you push the plug all the way.

==== Lanyard ====

The provided lanyard can be attached to the hole in the bottom part of the phone. Put the loose end through the phone, through the two metal loops in the lanyard, between the metal loops and back through the first metal loop.

=== Powering up the phone ===
[[Image:Neo1973_uboot_splash.jpg|200px|thumb|bootloader splash screen]]
Just hitting the power button (depending on your [[u-boot]] version you have to press for >= 5 seconds) should get the phone first into the bootloader, then boot the kernel, and get into X/OpenMoko. The shipped battery typically has enough charge to boot up directly without charging through the usb cable first.

Once you have pressed the power button sufficiently long, the vibrator makes a short pulse and the screen backlight turns on. You can now release the power button and watch the phone booting.

If the battery is not sufficiently charged, the phone will not turn on, even if the usb cable is plugged in.

=== Flashing the Neo1973 GTA01Bv4 ===
The GTA01Bv4 devices that are currently shipping do not boot out of the box. Flashing the phone with the latest kernel and [[Userspace root image|supporting file system ("rootfs")]] is required before the phone will successfully boot.

Read more information at about [[Flashing openmoko]]. MacOS X users please also refer to [[MacOS_X]].

=== Powering down the phone ===

==== While in bootloader mode, or if the phone has crashed ====

If you press the power button for 9 seconds, the phone will switch off. You can notice this by the backlight going dark.

==== While running a full linux system with userspace ====

In this mode, a power-button press of 5 seconds will be sufficient. After this, the init process will take care of safely shutting down the phone, which might take up to 20 extra seconds. The X server should get killed, you should drop back to a (garbled) console, and it should finally switch off - much like a regular Linux PC.

=== Battery charging ===
:''See also [[Neo1973 Battery Charger]]
The [[Neo1973]] supports two charging modes: One 100mA charge mode (called pre-charge) and 500mA (called fast charge). Charging is always done via the USB socket. You can use any USB-A to USB-mini-B cable to connect the phone to any USB host.

==== While in u-boot ====

While you are in u-boot mode, the phone only charges with 100mA by default. (This will change in one of the future revisions).

However, using the u-boot console you can manually enable fast charging. See [[U-boot#Battery_charger_related]] for more information.

==== While in Linux ====

As soon as the phone is connected via USB cable, it will charge. However, the default charging current is only 100mA, way too little if you want to operate the phone and charge at the same time.

If your USB upstream port is capable of supplying 500mA, then it will configure the Neo1973 accordingly and use 500mA charging mode. You can notice this by the following line in the kernel log (/var/log/messages) of the laptop/desktop your Neo1973 is hooked up to
usb0: full speed config #1: 500 mA, Ethernet Gadget, using CDC Ethernet

== Getting shell access on the phone ==

=== By using the terminal emulator and on-screen keyboard ===

"Click" (using a stylus) the top-left arrow icon to get a drop-down menu with "Media", "Settings", "Utilities" and "Desktop". Choose "Utilities->Panel->Input Manager", and a keyboard icon will appear on the top bar. You can get an on-screen keyboard at any time by choosing it.

With newer images, the keyboard comes up when you tap the white box in the top bar.

You can choose between different keyboard layouts and the stroke recognizer by dragging from the white box and releasing it to the right of the box.

From the desktop, choose "Active tasks->rxvt" to get a root shell.

[[Terminal]] is in the top level menu in recent images.

=== By using Ethernet emulation over a USB cable ===

The standard Neo1973 Linux [[kernel]] has support for the "cdc_ether USB gadget", i.e. a standard implementation of how to emulate an Ethernet device over USB.

The following description is for generic *NIX system. For setting up connectivity specifically on a MacOS X machine, refer to [[MacOS_X]] (because there is no usb0 and you need a special kernel driver first).

As soon as the kernel is up and running, and you have the phone connected via USB, you should get a '''usb0''' device on your host.

The Phone will have the IPv4 address 192.168.0.202/24. You can run `ifconfig` in the terminal on the phone to verify this (this is optional, just check it if it doesn't work given the instructions below)

If you plug a USB cable into a laptop running Linux, you'll likely see the "cdc_ether" kernel module being loaded and a usb0 network interface appear. If not, see [[USB_Networking]] for more details.

On the '''host PC''', you should then configure your interface to 192.168.0.200 by using
# ifconfig usb0 192.168.0.200 netmask 255.255.255.0

Then you should be able to
# ping 192.168.0.202

and last, but not least
# ssh root@192.168.0.202

Once you press 'enter' (empty password), you should now have a root login.

See [[USB_Networking]] for more details, including instructions on how to automatically setup masquerading so that your phone can get access to the internet through the host PC.

=== By using the debug board/serial/JTAG ===

Please see [[Debug Board#Usage_Instructions]]

== Getting access to the bootloader console ==

Please see [[u-boot#Using_usbtty_from_Linux]]

== Using Audio ==
=== Enable Internal Speaker and Mic in Phone Calls ===
If you got no Speaker and Mic during a Call you need to load the "gsmhandset.state" alsa-configfile

alsactl -f /etc/alsa/gsmhandset.state restore

Maybe you need to load another .state file for playing mp3 or a BT-Headset see in /etc/alsa/

To hear something you can find an .au file (or convert a .wav into an .au by using the sox tool):

sox ringtone_thereisnophone.wav -t raw -r 8012 -u -b -c 1 rigtone_thereisnophone.au

copy it to the device and run

cat ringtone_thereisnophone.au > /dev/dsp

== Useful commands in Linux ==

=== Suspending ===

Writing "mem" into ''/sys/power/state'' tells Linux to suspend - it will enter a low power mode where only the GSM and RAM are powered up and the CPU sleeps. It will persist in this state until a wake-up event arrives. Some currently enabled wake-up events are: AUX or POWER key press, USB cable detect.

If you're connected over ssh, sshd will stop responding when the OS suspends, so to avoid locking up your ssh client, use the command
# (sleep 1; echo mem > /sys/power/state) & exit

=== Initial backup ===

After getting your new Neo1973 booted for the first time you might want to make a back up of the original flash chip contents on your PC, before you overwrite the flash with a custom image or just update to a newer build.

{{note|For phase 0 developers only (GTA01Bv4 shippment 0, '''not > 0 '''): This is a good idea because there are parts in the root filesystem that can't be distributed over internet so they are only found in the shipped ROM (see the [[GPS]] driver).}}

One easy way to back up all of the Flash, that doesn't require installing any special software, is with ''netcat'' over the [[USB Networking|USB ethernet]]. The following commands can be used for that.
{|
! On the host !! On the target
|-
|<pre>
$ netcat -l -p 20000 > mtdblock0
$ netcat -l -p 20000 > mtdblock1
$ netcat -l -p 20000 > mtdblock2
$ netcat -l -p 20000 > mtdblock3
$ netcat -l -p 20000 > mtdblock4
</pre>
|<pre>
# cat /dev/mtdblock0 | nc 192.168.0.200 20000
# cat /dev/mtdblock1 | nc 192.168.0.200 20000
# cat /dev/mtdblock2 | nc 192.168.0.200 20000
# cat /dev/mtdblock3 | nc 192.168.0.200 20000
# cat /dev/mtdblock4 | nc 192.168.0.200 20000
</pre>
|}

This stores the five NAND partitions in files named mtdblock*. Knowing the partition layout (u-boot "mtdparts" command or Linux dmesg) you can restore the whole flash with it.

=== Setting date and time ===

To set the date and time you need to open a terminal or ssh to the device. To set the date and time to August 9 19:02 2007 type:

# date -s 080919022007

The screensaver might turn on as you execute this command - just tap the screen to get back.

Now, you need to synchronize the time with the hardware date/time by typing:

# hwclock --systohc

=== Where to from here ===

You'll probably want to play with some of the interesting hardware in this device. Obviously, you can explore the applications available through the touch-screen interface. But for those who prefer doing things more in the raw from a shell prompt, you can [[Manually_using_GSM | manually use GSM]], [[Manually_using_SMS | manually use SMS]], or you can start playing with the [[GPS]].

<span id="bottom">{{Languages|Getting_Started_with_your_Neo1973}}</span>

[[Category:Documentation]]
[[Category:Neo1973_Phase_1_related]]

Neo 1973 Battery Charging Logic

2007-08-20T13:23:30Z

Dcorking: kilohms

The [[Neo1973 Battery]] charging logic is embedded into our [[Neo1973 GTA01 Power Management|PCF50606 Power Management]] Unit (PMU).

The PCF50606 supports a variety of [[Neo1973 Battery]] charging modes, based around the hardware limitations of USB.

Some USB hubs only provide up to 100mA per device.
If more than the available current is drawn from them, they may be reset, or power off.
This resets all devices connected to the USB bus, possibly causing data loss.
So, fast charge mode is only enabled after the Neo is told that it is safe to charge at this current.

An alternative method is used when connected to a more USB-compliant dumb charger. If the Neo measures 48 kΩ +/- 1% between usb pin 5 and ground, it will detect the dumb charger and use it for fast charging.

{{warning|While we have spent a significant amount on various safe-guards such as battery-internal overcurrent/overvoltage protection, manual twisting with low-level charger control aspects is not recommended. It might damage either the [[battery]] or charging circuit.}}

== Charging Modes ==

=== Pre Charge ===

The default mode is what the PMU calls 'Pre Charge'. In which we draw up to 100mA charging current from the USB socket. This mode is safe to use on any USB socket, since the USB specification mandates that 100mA is always available.

However, 100mA charging at a 1200mAh [[Neo1973 Battery]] means around 12hrs charging time, not very practical at all.

=== Fast Charge ===

Fast Charge is what the PMU calls the charging mode in which we draw up to 500mA charging current from the USB socket. This mode can only be used if the USB stack on the host controller has selected a '''USB Configuration''' for the Neo which allows it to draw 500mA.

By default, if you apply +5V to the USB device socket, we draw only 100mA.

==== Fast Charge (CCCV) ====

Fast charging, using first constant current, later constant voltage. This is what we use for our Li-Ion [[Neo1973 Battery]]

==== Fast Charge (CVCC) ====

[[Category:Neo1973 Hardware]]

== Neo1973 emergency charging ==

=== from deep discharged battery ===

A deep discharged battery is one where the terminal voltage is below the minimal voltage threshold. The Neo1973 (specifically: The PCF50606 PMU) will not power-on the device. ''see also [[Neo1973 GTA01 Power Management]]

If you make sure to remove the USB cable and put a deep discharged battery into the Neo1973, the battery can still be charged. All you need to do is to provide 5V to the USB socket, by either connecting the Neo1973 to some USB port or a dumb USB charger.

The battery will charge only with 100mA, and it will take a couple of hours until the battery is again charged to a level where it can power the phone.

{{note|Please do not press the power button before you have waited for something like four hours. If you do so, the phone might [partially] power up, and draw more power than the 100mA supplied by the charger/USB, and so begin discharging itself again.

If you did press the power button,
#remove the battery,
#wait a moment,
#insert the battery
#connect the charger or USB.}}

The procedure to follow is:
# '''Open Case.
# '''Remove Battery.
# '''Wait 20s.''' ''This resets the hardware, and makes sure nothing is drawing current during the next stage.
# '''Plug into a USB host, or USB charger.''' ''At this time, the battery will be charging at a low rate.
# '''Wait 1 hour.''' At this time, the battery will be approximately 5% charged, which should run the Neo for several minutes. ''This time needs to be resolved: it is not quite clear how long to charge a deeply discharged battery before the device is able to request a 500 mA fast charge current.
# '''If you have a USB host, plug it into a port capable of sourcing 500mA and load the appropriate drivers, so the neo can negotiate to draw 500mA.

*If you have a dumb charger, see the [[Bootloader]] page for how to add a u-boot menu entry to turn on fast-charging.

==Proposals for alternative charging schemes==

An alternate method - for example sensing if there is no USB communication from the host for 30 seconds - as may be the case with dumb 'USB chargers' - would need to be used to be compatible with the vast majority of already existing hardware.
This has a small risk of causing buses it is connected to in suspend mode, when they are not active, to crash, and is not compliant with the specification.

:The USB spec requires the host to reply in a much shorter time than 30 seconds. Waiting that long is overkill and would be very annoying if you were trying to charge with something like a [http://www.21st-century-goods.com/page/21st/PROD/AHPG crank charger].

[[Category:Neo1973 Hardware]]

Neo 1973 Battery Charging Logic

2007-08-20T13:20:59Z

Dcorking: typo

The [[Neo1973 Battery]] charging logic is embedded into our [[Neo1973 GTA01 Power Management|PCF50606 Power Management]] Unit (PMU).

The PCF50606 supports a variety of [[Neo1973 Battery]] charging modes, based around the hardware limitations of USB.

Some USB hubs only provide up to 100mA per device.
If more than the available current is drawn from them, they may be reset, or power off.
This resets all devices connected to the USB bus, possibly causing data loss.
So, fast charge mode is only enabled after the Neo is told that it is safe to charge at this current.

An alternative method is used when connected to a more USB-compliant dumb charger. If the Neo measures 48 Ω +/- 1% between usb pin 5 and ground, it will detect the dumb charger and use it for fast charging.

{{warning|While we have spent a significant amount on various safe-guards such as battery-internal overcurrent/overvoltage protection, manual twisting with low-level charger control aspects is not recommended. It might damage either the [[battery]] or charging circuit.}}

== Charging Modes ==

=== Pre Charge ===

The default mode is what the PMU calls 'Pre Charge'. In which we draw up to 100mA charging current from the USB socket. This mode is safe to use on any USB socket, since the USB specification mandates that 100mA is always available.

However, 100mA charging at a 1200mAh [[Neo1973 Battery]] means around 12hrs charging time, not very practical at all.

=== Fast Charge ===

Fast Charge is what the PMU calls the charging mode in which we draw up to 500mA charging current from the USB socket. This mode can only be used if the USB stack on the host controller has selected a '''USB Configuration''' for the Neo which allows it to draw 500mA.

By default, if you apply +5V to the USB device socket, we draw only 100mA.

==== Fast Charge (CCCV) ====

Fast charging, using first constant current, later constant voltage. This is what we use for our Li-Ion [[Neo1973 Battery]]

==== Fast Charge (CVCC) ====

[[Category:Neo1973 Hardware]]

== Neo1973 emergency charging ==

=== from deep discharged battery ===

A deep discharged battery is one where the terminal voltage is below the minimal voltage threshold. The Neo1973 (specifically: The PCF50606 PMU) will not power-on the device. ''see also [[Neo1973 GTA01 Power Management]]

If you make sure to remove the USB cable and put a deep discharged battery into the Neo1973, the battery can still be charged. All you need to do is to provide 5V to the USB socket, by either connecting the Neo1973 to some USB port or a dumb USB charger.

The battery will charge only with 100mA, and it will take a couple of hours until the battery is again charged to a level where it can power the phone.

{{note|Please do not press the power button before you have waited for something like four hours. If you do so, the phone might [partially] power up, and draw more power than the 100mA supplied by the charger/USB, and so begin discharging itself again.

If you did press the power button,
#remove the battery,
#wait a moment,
#insert the battery
#connect the charger or USB.}}

The procedure to follow is:
# '''Open Case.
# '''Remove Battery.
# '''Wait 20s.''' ''This resets the hardware, and makes sure nothing is drawing current during the next stage.
# '''Plug into a USB host, or USB charger.''' ''At this time, the battery will be charging at a low rate.
# '''Wait 1 hour.''' At this time, the battery will be approximately 5% charged, which should run the Neo for several minutes. ''This time needs to be resolved: it is not quite clear how long to charge a deeply discharged battery before the device is able to request a 500 mA fast charge current.
# '''If you have a USB host, plug it into a port capable of sourcing 500mA and load the appropriate drivers, so the neo can negotiate to draw 500mA.

*If you have a dumb charger, see the [[Bootloader]] page for how to add a u-boot menu entry to turn on fast-charging.

==Proposals for alternative charging schemes==

An alternate method - for example sensing if there is no USB communication from the host for 30 seconds - as may be the case with dumb 'USB chargers' - would need to be used to be compatible with the vast majority of already existing hardware.
This has a small risk of causing buses it is connected to in suspend mode, when they are not active, to crash, and is not compliant with the specification.

:The USB spec requires the host to reply in a much shorter time than 30 seconds. Waiting that long is overkill and would be very annoying if you were trying to charge with something like a [http://www.21st-century-goods.com/page/21st/PROD/AHPG crank charger].

[[Category:Neo1973 Hardware]]

Neo 1973 Battery Charging Logic

2007-08-20T13:16:13Z

Dcorking: rework

The [[Neo1973 Battery]] charging logic is embedded into our [[Neo1973 GTA01 Power Management|PCF50606 Power Management]] Unit (PMU).

The PCF50606 supports a variety of [[Neo1973 Battery]] charging modes, based around the hardware limitations of USB.

Some USB hubs only provide up to 100mA per device.
If more than the available current is drawn from them, they may be reset, or power off.
This resets all devices connected to the USB bus, possibly causing data loss.
So, fast charge mode is only enabled after the Neo is told that it is safe to charge at this current.

An alternative method is used when connected to a more USB-compliant dumb charger for the is used. If the Neo measures 48 Ω +/- 1% between usb pin 5 and ground, it will detect the dumb charger and use it for fast charging.

{{warning|While we have spent a significant amount on various safe-guards such as battery-internal overcurrent/overvoltage protection, manual twisting with low-level charger control aspects is not recommended. It might damage either the [[battery]] or charging circuit.}}

== Charging Modes ==

=== Pre Charge ===

The default mode is what the PMU calls 'Pre Charge'. In which we draw up to 100mA charging current from the USB socket. This mode is safe to use on any USB socket, since the USB specification mandates that 100mA is always available.

However, 100mA charging at a 1200mAh [[Neo1973 Battery]] means around 12hrs charging time, not very practical at all.

=== Fast Charge ===

Fast Charge is what the PMU calls the charging mode in which we draw up to 500mA charging current from the USB socket. This mode can only be used if the USB stack on the host controller has selected a '''USB Configuration''' for the Neo which allows it to draw 500mA.

By default, if you apply +5V to the USB device socket, we draw only 100mA.

==== Fast Charge (CCCV) ====

Fast charging, using first constant current, later constant voltage. This is what we use for our Li-Ion [[Neo1973 Battery]]

==== Fast Charge (CVCC) ====

[[Category:Neo1973 Hardware]]

== Neo1973 emergency charging ==

=== from deep discharged battery ===

A deep discharged battery is one where the terminal voltage is below the minimal voltage threshold. The Neo1973 (specifically: The PCF50606 PMU) will not power-on the device. ''see also [[Neo1973 GTA01 Power Management]]

If you make sure to remove the USB cable and put a deep discharged battery into the Neo1973, the battery can still be charged. All you need to do is to provide 5V to the USB socket, by either connecting the Neo1973 to some USB port or a dumb USB charger.

The battery will charge only with 100mA, and it will take a couple of hours until the battery is again charged to a level where it can power the phone.

{{note|Please do not press the power button before you have waited for something like four hours. If you do so, the phone might [partially] power up, and draw more power than the 100mA supplied by the charger/USB, and so begin discharging itself again.

If you did press the power button,
#remove the battery,
#wait a moment,
#insert the battery
#connect the charger or USB.}}

The procedure to follow is:
# '''Open Case.
# '''Remove Battery.
# '''Wait 20s.''' ''This resets the hardware, and makes sure nothing is drawing current during the next stage.
# '''Plug into a USB host, or USB charger.''' ''At this time, the battery will be charging at a low rate.
# '''Wait 1 hour.''' At this time, the battery will be approximately 5% charged, which should run the Neo for several minutes. ''This time needs to be resolved: it is not quite clear how long to charge a deeply discharged battery before the device is able to request a 500 mA fast charge current.
# '''If you have a USB host, plug it into a port capable of sourcing 500mA and load the appropriate drivers, so the neo can negotiate to draw 500mA.

*If you have a dumb charger, see the [[Bootloader]] page for how to add a u-boot menu entry to turn on fast-charging.

==Proposals for alternative charging schemes==

An alternate method - for example sensing if there is no USB communication from the host for 30 seconds - as may be the case with dumb 'USB chargers' - would need to be used to be compatible with the vast majority of already existing hardware.
This has a small risk of causing buses it is connected to in suspend mode, when they are not active, to crash, and is not compliant with the specification.

:The USB spec requires the host to reply in a much shorter time than 30 seconds. Waiting that long is overkill and would be very annoying if you were trying to charge with something like a [http://www.21st-century-goods.com/page/21st/PROD/AHPG crank charger].

[[Category:Neo1973 Hardware]]

Talk:Neo 1973 Battery Charging Logic

2007-08-20T13:01:48Z

Dcorking: User:Speedevil|'s article suggested pre-charging for 1 hour. The suggestions in this article suggested to pre-charge for 2-4 hours.

==Time to pre-charge a deep discharged battery?==
[[User:Speedevil|Speedevil]]'s article suggested pre-charging for 1 hour. The suggestions in this article (before I imported those from Speedevil) suggested to pre-charge for 2-4 hours. Is there a way to choose the most effective time, and if so, is there clearer way to explain this to users? --[[User:Dcorking|Dcorking]] 15:01, 20 August 2007 (CEST)

Neo 1973 Battery Charging Logic

2007-08-20T12:52:16Z

Dcorking: /* from deep discharged battery */ slight rework + move procedure from Neo1973 Charging

The [[Neo1973 Battery]] charging logic is embedded into our [[:Category:Neo1973 Hardware#Power_Management|PCF50606 PMU]] (Power Management Unit).

The PCF50606 supports a variety of [[Neo1973 Battery]] charging modes, based around the hardware limitations of USB.

USB hubs may only provide up to 100mA per device.
If more than the available current is drawn from them, they may be reset, or power off.
This resets all devices connected to the USB bus, possibly causing data loss.
So, fast charge mode is only enabled after the Neo is told that it is safe to charge at this current.

An alternative method is used if the proper charger for the Neo is used.
If the neo measures 48kohm +/- 1% between usb pin 5 and ground, it will detect the dumb charger and use it for fast charging.

An alternate method - for example sensing if there is no USB communication from the host for 30 seconds - as may be the case with dumb 'USB chargers' - would need to be used to be compatible with the vast majority of already existing hardware.
This has a small risk of causing busses it is connected to in suspend mode, when they are not active, to crash, and is not compliant with the specification.

:The USB spec requires the host to reply in a much shorter time than 30 seconds. Waiting that long is overkill and would be very annoying if you were trying to charge with something like a [http://www.21st-century-goods.com/page/21st/PROD/AHPG crank charger].

{{warning|While we have spent a significant amount on various safe-guards such as battery-internal overcurrent/overvoltage protection, manual twisting with low-level charger control aspects is not recommended. It might damage either the [[battery]] or charging circuit.}}

== Charging Modes ==

=== Pre Charge ===

The default mode is what the PMU calls 'Pre Charge'. In which we draw up to 100mA charging current from the USB socket. This mode is safe to use on any USB socket, since the USB specification mandates that 100mA is always available.

However, 100mA charging at a 1200mAh [[Neo1973 Battery]] means around 12hrs charging time, not very practical at all.

=== Fast Charge ===

Fast Charge is what the PMU calls the charging mode in which we draw up to 500mA charging current from the USB socket. This mode can only be used if the USB stack on the host controller has selected a '''USB Configuration''' for the Neo which allows it to draw 500mA.

By default, if you apply +5V to the USB device socket, we draw only 100mA.

==== Fast Charge (CCCV) ====

Fast charging, using first constant current, later constant voltage. This is what we use for our Li-Ion [[Neo1973 Battery]]

==== Fast Charge (CVCC) ====

[[Category:Neo1973 Hardware]]

== Neo1973 emergency charging ==

=== from deep discharged battery ===

A deep discharged battery is one where the terminal voltage is below the minimal voltage threshold. The Neo1973 (specifically: The PCF50606 PMU) will not power-on the device. ''see also [[Neo1973 GTA01 Power Management]]

If you make sure to remove the USB cable and put a deep discharged battery into the Neo1973, the battery can still be charged. All you need to do is to provide 5V to the USB socket, by either connecting the Neo1973 to some USB port or a dumb USB charger.

The battery will charge only with 100mA, and it will take a couple of hours until the battery is again charged to a level where it can power the phone.

{{note|Please do not press the power button before you have waited for something like four hours. If you do so, the phone might [partially] power up, and draw more power than the 100mA supplied by the charger/USB, and so begin discharging itself again.

If you did press the power button,
#remove the battery,
#wait a moment,
#insert the battery
#connect the charger or USB.}}

The procedure to follow is:
# '''Open Case.
# '''Remove Battery.
# '''Wait 20s.''' ''This resets the hardware, and makes sure nothing is drawing current during the next stage.
# '''Plug into a USB host, or USB charger.''' ''At this time, the battery will be charging at a low rate.
# '''Wait 1 hour.''' At this time, the battery will be approximately 5% charged, which should run the Neo for several minutes. ''This time needs to be resolved: it is not quite clear how long to charge a deeply discharged battery before the device is able to request a 500 mA fast charge current.
# '''If you have a USB host, plug it into a port capable of sourcing 500mA and load the appropriate drivers, so the neo can negotiate to draw 500mA.

*If you have a dumb charger, see the [[Bootloader]] page for how to add a u-boot menu entry to turn on fast-charging.

Openmoko supported devices

2007-08-03T12:49:46Z

Dcorking: htc

This page details hardware that openmoko can run on, and the current status on that platform.

*[[Neo1973]] Fully supported.

* Treo 650 [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ up and limping.]

* Palm TX [http://www.palminfocenter.com/news/9371/openmoko-running-on-a-palm-tx/ with some issues.]

* Motorola E680i [http://www.motorolafans.com/forums/viewtopic.php?p=93003&highlight=#93003 kind of.]

* [http://en.wikipedia.org/wiki/HTC_Universal HTC Universal] dialer works [http://linuxtogo.org/~htcpxa/htcuniversal/index.html code:linuxtogo] [http://www.handhelds.org/moin/moin.cgi/UniversalStatus status:handhelds.org]

[[Category:Documentation]]

Openmoko supported devices

2007-08-03T12:47:28Z

Dcorking: added HTC Universal

This page details hardware that openmoko can run on, and the current status on that platform.

*[[Neo1973]] Fully supported.

* Treo 650 [http://blog.mikeasoft.com/2007/07/01/openmoko-on-a-treo-650/ up and limping.]

* Palm TX [http://www.palminfocenter.com/news/9371/openmoko-running-on-a-palm-tx/ with some issues.]

* Motorola E680i [http://www.motorolafans.com/forums/viewtopic.php?p=93003&highlight=#93003 kind of.]

* [http://en.wikipedia.org/wiki/HTC_Universal HTC Universal] dialer works [http://linuxtogo.org/~htcpxa/htcuniversal/index.html linuxtogo] [http://www.handhelds.org/moin/moin.cgi/UniversalStatus handhelds.org]

[[Category:Documentation]]